HELP PLZ! i think i broke my phone! - Galaxy S II Q&A, Help & Troubleshooting

guys i cant believe it! i just bought my phone today my new s2 and i downloaded the root file to flash via odin, turns out it was a root for 4.04 ics but i had 4.03 so it soft bricked, i downloaded another firmware from samsung for my phone and when i tried to flash via odin it always failed, i reset my pc, reinstalled drivers everything but it just didnt went trought, so i found a tutorial on how to download a pit file and repartition and i did, it also failed, but when i took the battery and tried to turn it on it didnt!! i think i just killed it! omg plz help meee i want to kill me right now! is there is something i can do? plz guys understand me! iam an idiot! sorry!
PD: i think that what i did wrong is i flashed the .pit file of a l9100g for not reading the thing , iam so f¨¨¨ckin dumb!! what can i do? where can it be repaired?
heres the odin log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> modem.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!

Can u get into Download mode atleast? If not, get a USB Jig or make one. Then, flash a stock firmware via Odin.
"To err is human, to forgive is divine"
Sent from my SGS II

immortalneo said:
Can u get into Download mode atleast? If not, get a USB Jig or make one. Then, flash a stock firmware via Odin.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
nope, its dead, will try, thanks
are you sure it will help ? my phone doesn't even boot

JTAG (or motherboard replacement if it isn't JTAG'able). Jig has a 0.0000000000000000000000000001% chance of working (but you may as well try it anyway).

MistahBungle said:
JTAG (or motherboard replacement if it isn't JTAG'able). Jig has a 0.0000000000000000000000000001% chance of working (but you may as well try it anyway).
Click to expand...
Click to collapse
May I know how you came to that conclusion? Is it because he flashed the PIT file?
"To err is human, to forgive is divine"
Sent from my SGS II

Correct. May as well try a jig, but highly unlikely to work. Classic case of what happens when you don't search/read/learn/understand the processes. This thread should be stickied & n00bs forced to read it whenever they log on for the first couple of weeks after they join.

MistahBungle said:
This thread should be stickied & n00bs forced to read it whenever they log on for the first couple of weeks after they join.
Click to expand...
Click to collapse
True.. better safe than sorry...
"To err is human, to forgive is divine"
Sent from my SGS II

Wait. Everything may not be over yet.
Plug in the wall charger, and wait for a couple of minutes. If the phone goes to the battery screen at least, then no worries, it will be fixed. If it doesn't, you have permanently bricked your s2 because the memory is corrupt+the phone now doesn't know what to do if the power button is pressed.
Try what I have told you and report back.
Sent from my GT-I9100 using Tapatalk 2

Hidden Username said:
Wait. Everything may not be over yet.
Plug in the wall charger, and wait for a couple of minutes. If the phone goes to the battery screen at least, then no worries, it will be fixed. If it doesn't, you have permanently bricked your s2 because the memory is corrupt+the phone now doesn't know what to do if the power button is pressed.
Try what I have told you and report back.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
did this with no responde
but guys why the hell odin didnt flash my phone? it was of the kernel??
i dont know wh y it bricked because the process failed!
now that its permantly bricked what is the process to fix it? it is expensive??

alvaro761991 said:
did this with no responde
but guys why the hell odin didnt flash my phone? it was of the kernel??
i dont know wh y it bricked because the process failed!
now that its permantly bricked what is the process to fix it? it is expensive??
Click to expand...
Click to collapse
Simple... flashing the wrong file (and possibly PIT file)..
U can either give it for JTAGing (costs around $25 I guess), or take it to a Service Centre (where they are likely to replace the motherboard).
Oh, by the way, tried using a Jig?
"To err is human, to forgive is divine"
Sent from my SGS II

alvaro761991 said:
did this with no responde
but guys why the hell odin didnt flash my phone? it was of the kernel??
now that its permantly bricked what is the process to fix it? it is expensive??
Click to expand...
Click to collapse
I bricked my phone and went to the store i bought it from and they fixed it. So If you still have warranty then you are good to go.

Chekhn said:
I bricked my phone and went to the store i bought it from and they fixed it. So If you still have warranty then you are good to go.
Click to expand...
Click to collapse
Make sure to be proper and courteous when you go to them, don't have an arrogant attitude like "You HAVE to fix my phone"
It worked wonders for me before with anyone including the police when they waived my parking ticket.
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 04:29 PM ---------- Previous post was at 04:28 PM ----------
$25 only? Hmm I didn't know it was so cheap!
Sent from my GT-I9100 using Tapatalk 2

Hidden Username said:
$25 only? Hmm I didn't know it was so cheap!
Click to expand...
Click to collapse
Not from my personal experience mate! Read it here on XDA..
"To err is human, to forgive is divine"
Sent from my SGS II

I've seen jtagging mentioned.....don't go there unless you REALLY have to. I've read in another thread that using a jtag involves soldering the device to.....whatever it needs to be attached to. If this process doesn't solve the issue and you still need to take the phone to Samsung repair, this soldering WILL be noticed, and WILL be used as a 'get out clause' by Samsung and enable them to refuse warranty repair.......be warned.....only jtag if Samsung can't/won't help.....
Sent from my GT-I9100 using Xparent Green Tapatalk 2

keithross39 said:
I've seen jtagging mentioned.....don't go there unless you REALLY have to. I've read in another thread that using a jtag involves soldering the device to.....whatever it needs to be attached to. If this process doesn't solve the issue and you still need to take the phone to Samsung repair, this soldering WILL be noticed, and WILL be used as a 'get out clause' by Samsung and enable them to refuse warranty repair.......be warned.....only jtag if Samsung can't/won't help.....
Sent from my GT-I9100 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
that was my last option but had to go with it, in my country we dont get warranty for celphones, PERU YAY!, i went to a mall and this guy had a jtag so i leaved my phone and tomorrow it will be fixed , will keep you up tomorrow guys! btw! never ever gonna try root or do whatever with my phone! i learned my lesson!! thanks for the help and the replies! very suportive community ily guys!

alvaro761991 said:
that was my last option but had to go with it, in my country we dont get warranty for celphones, PERU YAY!, i went to a mall and this guy had a jtag so i leaved my phone and tomorrow it will be fixed , will keep you up tomorrow guys! btw! never ever gonna try root or do whatever with my phone! i learned my lesson!! thanks for the help and the replies! very suportive community ily guys!
Click to expand...
Click to collapse
All the best!
Don't fear to root or flash.. Just fear ignorance and carelessness...
"To err is human, to forgive is divine"
Sent from my SGS II

You got it in one fella.....we are supportive here (or most of us are anyway).....
Do your android homework, don't rush into anything.....search read learn.....BEFORE you start. If you're not sure of something, ask a question....
I had my first smartphone for a year (Galaxy W) I ran stock for 5 months before I found XDA...
After I started researching it was another month before I felt confident enough to go ahead with it all.....that was 8 months ago....since then I've rooted 2 Galaxy S2s and a Galaxy Tab 2.7....all with the help and information found on XDA (and the occasional question on a specific forum) I've even been able to compile a tutorial over on the W forum which has been 'stickyed' that has helped a number of people root cwm and cusROM their Ws.....all because of help and info on XDA.....
Sent from my GT-I9100 using Xparent Green Tapatalk 2

Related

[Q] SGS3 dead. Download mode only, nothing else

What happened:
last night I was working late while reading WhatsApp groups messages from time to time. I noticed the battery reached ~30% then decided to charge the phone. Few minutes later, all of sudden Samsung logo appeared, I thought it was restarting but it keeps freezing on that screen.
What I noticed:
1. Few minutes before it died, I noticed the performance was poor.
I disabled "power saving" to unleash the processor and see what happen.
my S3 looked as if it was gaining some power then losing it. this is when I decided to leave it charging. I spent many years troubleshooting PCs, I'm new to PDAs but I felt that there's big thing happening and the phone will show that sooner or later!
2. I can't access recovery mode. Only download mode is accessible.
3. in download mode, product name is empty
What I did so far:
I'm trying to flash with stock I9300XXELLA, I have (bootloader, PDA, MODEM & CSC)
I used two different releases of Odin:
1. Odin v3.04 error
with (re-partition) selected:
Code:
<ID:0/020> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXELLA.tar.md5 is valid.
<OSM> CSC_I9300OXAELLA_BTU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Set PIT file..
<ID:0/020> DO NOT TURN OFF TARGET!!
<ID:0/020> Can't open the specified file. (Line: 2564)
<ID:0/020> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
w/out (re-partition)
he error is (There is no PIT partition)
Code:
<ID:0/020> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXELLA.tar.md5 is valid.
<OSM> CSC_I9300OXAELLA_BTU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Get PIT for mapping..
<ID:0/020>
<ID:0/020> There is no PIT partition.
<ID:0/020> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
2. Odin v3.07 error
with (re-partition) selected:
Code:
<ID:0/020> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXELLA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAELLA_BTU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Set PIT file..
<ID:0/020> DO NOT TURN OFF TARGET!!
<ID:0/020> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
w/out re-partition:
(There is no PIT partition)
Code:
<ID:0/020> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXELLA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAELLA_BTU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Get PIT for mapping..
<ID:0/020>
<ID:0/020> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm newb to this, I appreciate your help.
try this.. i dont know if it ll work ...
download this file http://checkrom.com/threads/resurrec...%84%A2-v4.896/
get into odin and flash this file into your phone through the download mode ... if everything works it should boot into cwm recovery .. then wipe data\factory reset , wipe cache , wipe dalvik cache and reboot ... wait 15 mins and it should work!! Good Luck!
@galaxys3lover : I'm trying this now.
What I did so far:
after the PIT partition error. I downloaded the PIT file of 16GB SGS3.
Started flashing with Odin with re-partition selected. It stucks on "Get PIT mapping.."
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXELLA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAELLA_BTU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
I searched about the error on the fourms and found many members say it's better to use odin on windows XP, so I installed windows XP on VMware and tried flushing ,, however I still get the same error.
@galaxys3lover
not working, same errors. it looks like sudden death
I have same issue with two of SG3 devices, it's sucks
My nephew has the same issue, but he's not rooted.
Sent from my GT-I9300 using xda app-developers app
if flashing the stock ROM and pit file fails, the only option is to replace the motherboard. that's all there is to it
I only flashed this PDA file:
I9300XXEMA2
Where can I find the CSC and or pit files?
on sammobile
Had Same Exact problem, waiting for someone good reply... desperately.. tried every thing to do with odin no lock pit file error.. don't really want to go to service center.. waiting for some genius xda users guide

samsung gt-b5512 stuck at white screen after inserting wrong firmware

heloo sir i am new to this forum and my problem is that my samsung gt-b5512 stucks at white screen during booting when i press the power button
this happens due to wrong firmware flashing of another galaxy y model and after then when i flashed it with the right firmware files of b5512 this below message occurs .so sir please help me because i know you can
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> DefaultCalDataWithBoot_B5512JXLA1_REV00.tar.md5 is valid.
<OSM> PDA_B5512JPLA3_REV00.tar.md5 is valid.
<OSM> MODEM_B5512JXLA1_REV00.tar.md5 is valid.
<OSM> GT-B5512-MULTI-CSC-OJPLA3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

[Q] S3 rooting + flashing, not working in Odin (PIT error)

Hi,
I've got a question about the Samsung Galaxy S3 (i9300). Before this issue it was completely original (not rooted or anything like that).
A few dags ago the phone didn't start. The battery was full (of course), the Samsung logo (with the device type etc, not the animated logo) appeared but it did nothing else. I've waited a long time, and still nothing has happened. So I Googled a lot on many sites on how to fix this problem.
I ended up with the solution 'Flash the stock ROM', so I went to sammobile (and later to samsung-updates.com) to find the original stock ROM, created by Samsung.
I found it, and tried to flash it (I put the phone in download mode (device info in the left upper corner), and the downloadmode is enabled, and I received a notification in Odin (I tried v1.85 and I'm using v3.09 right now) that says 'Added'.
This stock ROM (flashing-process) didn't work so I kept on Googling and found some solutions. I've downloaded custom ROM's and tried to download ClockworkMod recovery (I wanted to install this so I could wipe the phone and reinstall the stock ROM). Unfortunatly it didn't work.
This is the error that I get from Odin (when trying to flash the Stock ROM):
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNL1_I9300ZTOUGNK2_I9300UBUGNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried to install CWM Recovery with Odin, but I ended up with another error (as you can see in the PNG file that I uploaded with this thread).
Can anyone help me with restoring this phone to factory settings (and stock ROM)?
Thanks in advance!
Explanation for the screenshots (uploaded to this thread):
screen1.png: different files that I tried since the first ones didn't work (PIT files, ROM'S and CWM Recovery).
screen2.png: attempt to flash Stock ROM.
screen3.png: error after flashing Stock ROM.
screen4.png attempt to install CWM Recovery.
Seems, that you must rebuild your partitions. Look here.
rp158 said:
Seems, that you must rebuild your partitions. Look here.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I downloaded the ZIP file from Mega, and unpacked in (and configurated it exactly like in his screenshot), but I can't find the PIT file.
Any idea where I can find that?
Without the PIT file I'm getting an error.
When I download another PIT file from the internet for this device, I get this error: (FYI: I tried 3 different PIT files):
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance!
CB95 said:
Hi,
Thanks for your reply.
I downloaded the ZIP file from Mega, and unpacked in (and configurated it exactly like in his screenshot), but I can't find the PIT file.
Any idea where I can find that?
Without the PIT file I'm getting an error.
When I download another PIT file from the internet for this device, I get this error: (FYI: I tried 3 different PIT files):
Thanks in advance!
Click to expand...
Click to collapse
There are two versions 4.1.2 and 4.3 the pit file is in the 4.1.2 download but can be used on both roms
tallman43 said:
There are two versions 4.1.2 and 4.3 the pit file is in the 4.1.2 download but can be used on both roms
Click to expand...
Click to collapse
Hi,
Thanks for your quick reply. I really appreciate it.
I downloaded the 4.1 version en copied the mx.pit file to the 4.3 directory.
When I configure everything exactly like the screenshot (in the other thread, link is in first post in this thread), I still get an error:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I attached an screenshot of my Odin configuration, could you please take a look at that?
Thanks in advance!
CB95 said:
Hi,
Thanks for your quick reply. I really appreciate it.
I downloaded the 4.1 version en copied the mx.pit file to the 4.3 directory.
When I configure everything exactly like the screenshot (in the other thread, link is in first post in this thread), I still get an error:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I attached an screenshot of my Odin configuration, could you please take a look at that?
Thanks in advance!
Click to expand...
Click to collapse
Yep it failed on Re-Partition (pit file) looks like you may need service repair. Try using Odin 1.85 from here >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 << If fails service repair recommended.
tallman43 said:
Yep it failed on Re-Partition (pit file) looks like you may need service repair. Try using Odin 1.85 from here >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 << If fails service repair recommended.
Click to expand...
Click to collapse
Thanks for your reply.
What do you mean by that (service repair)?
Should I use Odin 1.85 to flash it, or do you mean that the phone is broken and need to be repaired by Samsung?
Another question: in Odin 3.09 there is an option (checkbox) that says 'NAND Erase', should I check this while following the tutorial (first reply on this thread)?
Thanks!
CB95 said:
Thanks for your reply.
What do you mean by that (service repair)?
Should I use Odin 1.85 to flash it, or do you mean that the phone is broken and need to be repaired by Samsung?
Another question: in Odin 3.09 there is an option (checkbox) that says 'NAND Erase', should I check this while following the tutorial (first reply on this thread)?
Thanks!
Click to expand...
Click to collapse
DO NOT CHECK NAND ERASE!!
Service repair ie get Samsung or a service repair shop to fix it.
tallman43 said:
DO NOT CHECK NAND ERASE!!
Service repair ie get Samsung or a service repair shop to fix it.
Click to expand...
Click to collapse
Thanks for your reply.
I tried to flash it with Odin 1.85, and I got the following error:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I tried to flash the firmware version 4.1.3, I got this error (Odin 1.85):
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So it looks like I should contact a repair center.
Anyway, thank you all for your replies and help, I appreciate it!

Samsung S5690 (Galaxy Xcover) Boot loop (Samsung animation logo)

Hi,
This device has the android stock rom (don't know which version) and the stock recovery.
Tried to flash it via odin but no hope, always getting FAIL message. tried all versions of ODIN, even with PIT file, but same results.
Could it be a hadware issue (NAND defective ?).
Any help appreciated.
What caused the bootloop? What part of the flash is it failing on? Not knowing what version was on it before would probably be why you are having issues with reloading the original firmware. The firmware you load in Odin should be the same version or newer and from the correct region or carrier, if it is specific to one. Very unlikely it is a hardware issue.
es0tericcha0s said:
What caused the bootloop?
Click to expand...
Click to collapse
Don't know (device belongs to a friend, he said a virus caused the bootloop-not right IMO-)
es0tericcha0s said:
What part of the flash is it failing on?
Click to expand...
Click to collapse
Odin3 v1.83 - v3.04 :
<ID:0/014> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-S5690_Bootloader_XXKL1.tar.md5 is valid.
<OSM> GT-S5690_PDA_XXKL1.tar.md5 is valid.
<OSM> GT-S5690_Phone_XXKL1.tar.md5 is valid.
<OSM> GT-S5690_CSC_PROKL1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> Complete(Write) operation failed.
<ID:0/014> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Odin3 v3.07 - v3.10:
<ID:0/014> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-S5690_Bootloader_XXKL1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-S5690_PDA_XXKL1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-S5690_Phone_XXKL1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-S5690_CSC_PROKL1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Removed!!
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
es0tericcha0s said:
Not knowing what version was on it before would probably be why you are having issues with reloading the original firmware. The firmware you load in Odin should be the same version or newer and from the correct region or carrier, if it is specific to one. Very unlikely it is a hardware issue.
Click to expand...
Click to collapse
So I must try with every available firmware out there ?
Firmware used:
GT-S5690_XXKL1_XXKL1_PROKL1_home (Includes: (Bootloader, CSC, PDA, Phone) Files)
gt-s5690_xxld3_xxld3_neekk8_home (Includes: (CSC, PDA, Phone) Files)
gt-s5690_xxlg3_xxlg3_dbtlf1_home (Includes: (CSC, PDA, Phone) Files)
Stock Recovery:
E:failed to mount /data (Invalid argument)
-- Applying Multi-CSC --
Note: even a hard reset does nothing (obviously).
Any solutions guys

S3 NAND Fail

Hi! My rooted S3 started to reboot randomly and suddenly one day stopped working. It's stuck on the "Samsung Galaxys3 GT-I9300" screen. I'm able to enter download mode and recovery mode. I can't use factory reset/wipe data because as soon as it starts the phone reboots.
I've tried several guides to no avail, I just can't get it to work. Kies can't see the phone, but Odin works. Even tried cleaning the power button just in case, but I think that only works for the samsung logo loop. Last thing I tried was a "GT-I9300XXEMG4_KOR_MULTI_FACTORY". This is what happens:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I'm at a loss. The phone worked flawlessly (rooted) for more than a year and suddenly this happens. Maybe when the random reboots started I could have done something, but what's done it's done. I've read that I could try changing the motherboard, but they are kinda expensive for something I don't know if it will even work. Tried different computers, USB cables, but it's always the same. I remember I had the avast anti theft app, but I don't know if this is what's preventing me from wiping the data or fixing the phone.

Categories

Resources