5,594,221 Members 45,535 Now Online
XDA Developers Android and Mobile Development Forum

Samsung s3 i9300 & Note2 N7100 Dead boot solution & imei null solution s3

Tip us?
 
jamesjerss
Old
(Last edited by jamesjerss; 14th February 2014 at 12:55 AM.)
#1  
Junior Member - OP
Thanks Meter 21
Posts: 18
Join Date: May 2011
Location: Nagercoil
Thumbs up Samsung s3 i9300 & Note2 N7100 Dead boot solution & imei null solution s3

Samsung s3 i9300 & Note2 N7100 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.

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,


* 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.


* 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 firmware Download 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












The Following 8 Users Say Thank You to jamesjerss For This Useful Post: [ Click to Expand ]
 
neusys
Old
#2  
Junior Member
Thanks Meter 0
Posts: 10
Join Date: Jan 2011
Location: SP
Thank you for your great solution.

I have revive several i9300 by your solution.

But i have facing 1 big problem, the phone which i revive by this method only have Emergency Call after upgrade the firmware to official samsung 4,3 roms. phone was okay when under 4.1.2 firmware. (XXEMA2)

Imei is good n Serial is good. (Some phones have Serial 000000000).

another issue is Phone dun have product name under download mode.
 
jamesjerss
Old
#3  
Junior Member - OP
Thanks Meter 21
Posts: 18
Join Date: May 2011
Location: Nagercoil
Quote:
Originally Posted by neusys View Post
Thank you for your great solution.

I have revive several i9300 by your solution.

But i have facing 1 big problem, the phone which i revive by this method only have Emergency Call after upgrade the firmware to official samsung 4,3 roms. phone was okay when under 4.1.2 firmware. (XXEMA2)

Imei is good n Serial is good. (Some phones have Serial 000000000).

another issue is Phone dun have product name under download mode.

For Emergency Call fix run Samsung tool there repair/ run network repair

for serial nubr 000000 fix yu hav to repair baseband 1st try to write serial nubr using samsung tool or repair using asanam dongle.

Still same hardware issue may b
 
neusys
Old
#4  
Junior Member
Thanks Meter 0
Posts: 10
Join Date: Jan 2011
Location: SP
Well done. Thanks for your help again. All problem have been solved.

Do i need to create new memory card for note2 N7100 ?

is it the same procedure for note2 N7100 also ?
 
eatsleep
Old
#5  
eatsleep's Avatar
Senior Member
Thanks Meter 35
Posts: 193
Join Date: Jun 2013
Location: ▂ ▃ ▅ ▆ █ , Where ever's Free WiFi
Hey Man (or more likely to be a woman )
Don't you think it is a bad idea to post your imei in public?
Bad things can happen
Unused Ram is wasted Ram


Phones:
Samsung Galaxy SIII Gt-i9300
Android Revolution HD 40.0
Googy max 2 (whatever is the latest, Googy_anas updates it too much )
Philz Recovery
 
silverbox750
Old
#6  
Member
Thanks Meter 3
Posts: 42
Join Date: Dec 2010
Default done all the steps but process wont start

i got dead s3 and i followed all the above steps and im using spt box for the final process but nothings happend.
i waited for 15 minuts,tried many times but same..?
any help..?
 
neusys
Old
#7  
Junior Member
Thanks Meter 0
Posts: 10
Join Date: Jan 2011
Location: SP
how about for N7100, is there same procedure and same SDCARD used on i9300 ?
 
carabus.adrian.daniel
Old
#8  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Mar 2014
Default n 7100 with no rom

i have an n7100 that looks exactly as your s3 in the two pictures. when i turn it on it shows the exact scrambled image,and when entered in boot mode,this is what i get:
ODIN MODE (red)
PRODUCT NAME: GT-N7100
CUSTOM BINARYDOWNLOAD: No
CURENT BINARY:Samsung Official
SYSTEM STATUS: Custom
KNOX WARANTY VOID: 0
AP SWREV:

THAT IS THE EXACT MESAGE,NOTHING PLUS OR MINUS
when i flash whit odin,it sais no pit partition. i need help with the files and procedure
 
Dare85
Old
#9  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Jan 2012

 
DONATE TO ME
super thx
 
jamesjerss
Old
#10  
Junior Member - OP
Thanks Meter 21
Posts: 18
Join Date: May 2011
Location: Nagercoil
Quote:
Originally Posted by carabus.adrian.daniel View Post
i have an n7100 that looks exactly as your s3 in the two pictures. when i turn it on it shows the exact scrambled image,and when entered in boot mode,this is what i get:
ODIN MODE (red)
PRODUCT NAME: GT-N7100
CUSTOM BINARYDOWNLOAD: No
CURENT BINARY:Samsung Official
SYSTEM STATUS: Custom
KNOX WARANTY VOID: 0
AP SWREV:

THAT IS THE EXACT MESAGE,NOTHING PLUS OR MINUS
when i flash whit odin,it sais no pit partition. i need help with the files and procedure
yours may b a hardware issue . emmc chip problem yu hav to replace it

The Following User Says Thank You to jamesjerss For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes