Wednesday, November 26, 2014
Monday, November 24, 2014
Samsung s3 i9300 & Note2 N7100 & i9500 s4 Dead boot repair solution & imei null solution only for i9300
Procedure:
* Download samsung s3 boot card maker Here
* Extract it on desktop
* Take a card reader insert memory card into the card reader nd connect it to the pc
* From the extracted folder run Diskdump2.exe
* Select generic storage Device. pictures below follw it
* Now to write the scripts folle the below given picr
Now done yu are succesfully created Dead boot memorycard
To continue further
Requerments:
* Z3X samsung Box or SPT Box (i used z3x)
* special UART Cable (300k or 500k uartcable)
* Download teraterm-4.78 From Here
* Fully charged battery
Dead boot Reapairing procedure
* Download nd extract teraterm-4.78 on desktop
* From extracted folder run ttermpro.exe there select serial port nd change the serial port to z3x serial
port lik below givin in the picr
*After Select The Serial Port Press Ok Button den Go To Setup Click Serial Port Option
Select Baud Rate 115200 Then Press Ok Button lik below givn in the picr
* Now insert the created boot card to the mobile
* Connect the Uart cable via z3x box
* Now Insert the battery nd wait for 5min if the procces didnt start discnnt the mobile close ttermpro agin try it.
* if it run success yu vil the result below given lik this.
* if yu get this error at the end [Patch Stop] This is not Rom Code. yu cant fix yur mobile yu have to change yur emmc chip
* After done this yur mobile must me n download mode or white screen if white screen manually put into download mode.
* After dead boot repair mine white screen i manually put into download mode pir below
* Now update your mobile with factory firmware with PIT file lik below given n the picr.Factory firmwareDownload Here
* After update complete yur mobile may not have imei .imei null or yur mobile will not boot bcoz of dead boot repair. yur efs must be corrupted
* To Fix this prob first root yur mobile Download from here (flash it through odin select as odin)
* Now Download this EfS repair file nd flash it through odin select as odin yur mobile must boot
but the imei become lik this 004999010640000
I9300_Repair_efs.tar.rar
* if yur imei is null yu cant repair using this box so 1st yu have to repair the efs using above givn file. if yur imei bcome lik tis oly (004999010640000) yu can repair using z3x or othr samsung tool
* Now follw the picr to repair imei problem.
* After IMEI Repair
I hope this post wil helpful for lotz of dem
* Download samsung s3 boot card maker Here
* Extract it on desktop
* Take a card reader insert memory card into the card reader nd connect it to the pc
* From the extracted folder run Diskdump2.exe
* Select generic storage Device. pictures below follw it
* Now to write the scripts folle the below given picr
Now done yu are succesfully created Dead boot memorycard
To continue further
Requerments:
* Z3X samsung Box or SPT Box (i used z3x)
* special UART Cable (300k or 500k uartcable)
* Download teraterm-4.78 From Here
* Fully charged battery
Dead boot Reapairing procedure
* Download nd extract teraterm-4.78 on desktop
* From extracted folder run ttermpro.exe there select serial port nd change the serial port to z3x serial
port lik below givin in the picr
*After Select The Serial Port Press Ok Button den Go To Setup Click Serial Port Option
Select Baud Rate 115200 Then Press Ok Button lik below givn in the picr
* Now insert the created boot card to the mobile
* Connect the Uart cable via z3x box
* Now Insert the battery nd wait for 5min if the procces didnt start discnnt the mobile close ttermpro agin try it.
* if it run success yu vil the result below given lik this.
Quote:
pit_check_integrity: invalid pit.(0x0)
pit_check_integrity: invalid pit.(0x0)
update_guid_partition_table: There is no pit binary.
fsd_reclaim 1283: MST is not recognized(mst.magic=0x0)
fsd_reclaim 1284: MST is not recognized
fsd_reclaim 1599: Error(nErr=0x0)
fsd_reclaim 1604: j4fs_rw_start is set to default value(128KB)
j4fs_open 153: Error(nErr=0x40000000)
j4fs_read_file_bootloader 355: j4fs panic
load_j4fs_param: 'param.j4fs' does not exist, make new one..
j4fs_write_file_bootloader 184: j4fs panic
fail
j4fs_read_file_bootloader 355: j4fs panic
load_j4fs_param: debug level file does not exist..*INCORRECT!*
init_fuel_gauge: battery is not detected, do not init fuelgauge
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3a
PMIC_ID = 0x2
PMIC_IRQSRC = 0x0
PMIC_STATUS1 = 0x10
PMIC_STATUS2 = 0x0
PMIC_PWRON = 0x2
PMIC_IRQ1 = 0x27
PMIC_IRQ2 = 0x0
s5p_check_keypad: keypad value=0x0
s5p_check_reboot_mode: INFORM3 = 0 ... skip
s5p_check_upload: MAGIC CODE=d1b0f038
microusb_get_attached_device: STATUS1:0x3c, 2:0x0
s5p_check_download: update mode=0
j4fs_read_file_bootloader 355: j4fs panic
s5p_check_tzsw: invalid tzsw type! dummy?
scr_draw_image: draw 'download_error.jpg'...
j4fs_read_file_bootloader 355: j4fs panic
read_param_file: 'download_error.jpg' j4fs read failed!
fimd_div:13, div:1, FB_SOURCE_CLOCK:800000000, FB_PIXEL_CLOCK:57153600
a2, 60, 90,
pit_check_integrity: invalid pit.(0x0)
update_guid_partition_table: There is no pit binary.
fsd_reclaim 1283: MST is not recognized(mst.magic=0x0)
fsd_reclaim 1284: MST is not recognized
fsd_reclaim 1599: Error(nErr=0x0)
fsd_reclaim 1604: j4fs_rw_start is set to default value(128KB)
j4fs_open 153: Error(nErr=0x40000000)
j4fs_read_file_bootloader 355: j4fs panic
load_j4fs_param: 'param.j4fs' does not exist, make new one..
j4fs_write_file_bootloader 184: j4fs panic
fail
j4fs_read_file_bootloader 355: j4fs panic
load_j4fs_param: debug level file does not exist..*INCORRECT!*
init_fuel_gauge: battery is not detected, do not init fuelgauge
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3a
PMIC_ID = 0x2
PMIC_IRQSRC = 0x0
PMIC_STATUS1 = 0x10
PMIC_STATUS2 = 0x0
PMIC_PWRON = 0x2
PMIC_IRQ1 = 0x27
PMIC_IRQ2 = 0x0
s5p_check_keypad: keypad value=0x0
s5p_check_reboot_mode: INFORM3 = 0 ... skip
s5p_check_upload: MAGIC CODE=d1b0f038
microusb_get_attached_device: STATUS1:0x3c, 2:0x0
s5p_check_download: update mode=0
j4fs_read_file_bootloader 355: j4fs panic
s5p_check_tzsw: invalid tzsw type! dummy?
scr_draw_image: draw 'download_error.jpg'...
j4fs_read_file_bootloader 355: j4fs panic
read_param_file: 'download_error.jpg' j4fs read failed!
fimd_div:13, div:1, FB_SOURCE_CLOCK:800000000, FB_PIXEL_CLOCK:57153600
a2, 60, 90,
* if yu get this error at the end [Patch Stop] This is not Rom Code. yu cant fix yur mobile yu have to change yur emmc chip
Quote:
TN default
<OK>
<OK>
[DVFS] INT(1) : 0
DRAM Type : LPDDR2 8G
[DVFS] MIF(3) : 0
[EPLL][VPLL][CLK_DIV] OK
<OK>
[LOCK SW/HW]ARM:0/0 INT:0/0 G3D:0/0 MIF:0/0 SHIFT:0/0
[DVFS] ARM(0) : 5
[DVFS] INT(1) : 0
[DVFS] G3D(2) : 0
[DVFS] MIF(3) : 0
[SD_INIT
SDMMC_HighSpeedONE]
SD_READ: 20000 20000 0x40008000 -> 668484 usec
<OK>
Inp32(uAddr) : 0xea00007e
FW Booting
[Patch Stop] This is not Rom Code.
<OK>
<OK>
[DVFS] INT(1) : 0
DRAM Type : LPDDR2 8G
[DVFS] MIF(3) : 0
[EPLL][VPLL][CLK_DIV] OK
<OK>
[LOCK SW/HW]ARM:0/0 INT:0/0 G3D:0/0 MIF:0/0 SHIFT:0/0
[DVFS] ARM(0) : 5
[DVFS] INT(1) : 0
[DVFS] G3D(2) : 0
[DVFS] MIF(3) : 0
[SD_INIT
SDMMC_HighSpeedONE]
SD_READ: 20000 20000 0x40008000 -> 668484 usec
<OK>
Inp32(uAddr) : 0xea00007e
FW Booting
[Patch Stop] This is not Rom Code.
* After done this yur mobile must me n download mode or white screen if white screen manually put into download mode.
* After dead boot repair mine white screen i manually put into download mode pir below
* Now update your mobile with factory firmware with PIT file lik below given n the picr.Factory firmwareDownload Here
* After update complete yur mobile may not have imei .imei null or yur mobile will not boot bcoz of dead boot repair. yur efs must be corrupted
* To Fix this prob first root yur mobile Download from here (flash it through odin select as odin)
* Now Download this EfS repair file nd flash it through odin select as odin yur mobile must boot
but the imei become lik this 004999010640000
I9300_Repair_efs.tar.rar
* if yur imei is null yu cant repair using this box so 1st yu have to repair the efs using above givn file. if yur imei bcome lik tis oly (004999010640000) yu can repair using z3x or othr samsung tool
* Now follw the picr to repair imei problem.
* After IMEI Repair
I hope this post wil helpful for lotz of dem
Wednesday, November 19, 2014
Download Pangu Jailbreak to Jailbreak iPhone, iPad and iPod touch running
Pangu Download
A group of Chinese hackers calling themselves “PanGuTeam” have released the a jailbreak for iOS 8 – iOS 8.1, making it the first jailbreak for iOS 8, and also iPhone 6, iPhone 6 Plus, iPad Air 2 and iPad mini 3. It works with all the iOS 8 – 8.1 compatible devices:
- iPhone 6, iPhone 6 Plus, iPhone 5s, iPhone 5c, iPhone 5 and iPhone 4s
- iPad Air, iPad 4, iPad 3 and iPad 2
- Retina iPad mini, 1st gen iPad mini
- 5th generation iPod touch
Download Pangu Jailbreak to Jailbreak iPhone, iPad and iPod touch running iOS 8 – iOS 8.1:
Latest version:
Older versions:
- Pangu 8 1.1.0
- Windows version – [Official]
How to Jailbreak iOS 8.1 – iOS 8.0.x with Pangu
If you need help on how to use Pangu to jailbreak your iPhone, iPad or iPod touch running iOS 8.0.x – iOS 8.1, follow our latest step-by-step guide.
To Jailbreak iOS 7.1.2 – iOS 7:
Pangu also supports the following devices running on iOS 7.1 – iOS 7.1.2:
- iPhone 5s, iPhone 5c, iPhone 5, iPhone 4S and iPhone 4
- iPad Air, iPad 4, iPad 3, iPad 2
- iPad mini, Retina iPad mini
- iPod touch 5G
Download Pangu Jailbreak to Jailbreak iPhone, iPad and iPod touch running iOS 7 – iOS 7.1.2:
Direct download link for all the older version of Pangu jailbreak:
- Pangu 1.2.0
- Pangu 1.1.0
- Pangu 1.0.0 [Windows]
How to Jailbreak iOS 7.1 – iOS 7.1.2 with Pangu
If you need help, follow our latest step-by-step guide to jailbreak your iOS device.
If you’re on iOS 7.0.6 or lower then check this webpage for links to the latest tutorials on how to jailbreak your iOS device.
As always, let us know how it goes in the comments.
