I have managed to get myself into a pickle. Trying to revert back to stock today I flashed a stock ROM via Odin. This worked but put the phone in a boot loop, so I booted into recovery and tried a factory reset. However, this crashed. I can now boot into download mode, but not recovery. The phone now is stuck in a very slow boot loop, not getting past the SGS2 splash screen (the one which has the yellow triangle).
I have tried re-installing stock roms via Odin. Odin says success, but the phone still won't get past the spash screen and won't let me boot into recovery either.
I have spent hours today searching for guidance, and have tried everything I have found but am not having to admit defeat and ask for help.
I have tried flashing different versions of stock and different kernels without success. Any ideas on what else I can try?
Thanks in advance,
Andy
I have managed to get myself into a pickle. Trying to revert back to stock today I flashed a stock ROM via Odin. This worked but put the phone in a boot loop, so I booted into recovery and tried a factory reset. However, this crashed. I can now boot into download mode, but not recovery. The phone now is stuck in a very slow boot loop, not getting past the SGS2 splash screen (the one which has the yellow triangle). <br />
<br />
I have tried re-installing stock roms via Odin. Odin says success, but the phone still won't get past the spash screen and won't let me boot into recovery either. <br />
<br />
I have spent hours today searching for guidance, and have tried everything I have found but am not having to admit defeat and ask for help.<br />
<br />
I have tried flashing different versions of stock and different kernels without success. Any ideas on what else I can try?<br />
<br />
Thanks in advance, <br />
<br />
Andy
Click to expand...
Click to collapse
Ok. No problem. Your problem looks simple but i need to know your phone model.
Is your phone GT I9100 or GT I9100G?
Swyped from my Samsung Galaxy SII
Jokesy said:
Ok. No problem. Your problem looks simple but i need to know your phone model.
Is your phone GT I9100 or GT I9100G?
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
It is the GT-I9100.
Thanks.
awicks said:
It is the GT-I9100.
Thanks.
Click to expand...
Click to collapse
1. Visit here : forum.xda-developers.com/showthread.php?t=1419102
Download the .tar Odin Noob proof edition. It looks like this:
CM9 Resurrection Edition for use with Odin:
20120420: Download
20120330: Download
Download the first one (20120420), then flash via Odin.
Swyped from my Samsung Galaxy SII
Jokesy said:
Download the first one (20120420), then flash via Odin.
Click to expand...
Click to collapse
Have just tried that but it failed:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.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> Can't open the serial(COM) port.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is now stuck in download mode with the progress bar at approx 90%.
Andy
awicks said:
Have just tried that but it failed:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.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> Can't open the serial(COM) port.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is now stuck in download mode with the progress bar at approx 90%.
Andy
Click to expand...
Click to collapse
any news or still stuck here?
Swyped from my Samsung Galaxy SII
awicks said:
Have just tried that but it failed:
<snip>
The phone is now stuck in download mode with the progress bar at approx 90%.
Andy
Click to expand...
Click to collapse
Posted up the wrong Odin log. Let's try again.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> modem.bin
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Andy
I left it for over 45 mins and nothing happened. I have tried again and received the same error message.
Andy
awicks said:
I left it for over 45 mins and nothing happened. I have tried again and received the same error message.
Andy
Click to expand...
Click to collapse
What version of Odin are you using?
Swyped from my Samsung Galaxy SII
ODIN 3 v3.04
awicks said:
ODIN 3 v3.04
Click to expand...
Click to collapse
use Odin 1.85
Swyped from my Samsung Galaxy SII
awicks said:
Have just tried that but it failed:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.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> Can't open the serial(COM) port.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is now stuck in download mode with the progress bar at approx 90%.
Andy
Click to expand...
Click to collapse
This is obviously a communication problem, maybe your USB cable is damaged ?
Try different cable because I had a similar problem with my previous SGS 1
Hope it will help you
leech4 said:
This is obviously a communication problem, maybe your USB cable is damaged ?
Try different cable because I had a similar problem with my previous SGS 1
Hope it will help you
Click to expand...
Click to collapse
That was the wrong Odin log I pasted. I pasted the correct one a few posts later.
I have now tried both Odin 3.04 and 1.85. 3.04 throws a 'fail' message whilst 1.85 just hangs at the same stage. I have again left it for over an hour and nothing has happened.
Will keep trying things.
awicks said:
That was the wrong Odin log I pasted. I pasted the correct one a few posts later.
I have now tried both Odin 3.04 and 1.85. 3.04 throws a 'fail' message whilst 1.85 just hangs at the same stage. I have again left it for over an hour and nothing has happened.
Will keep trying things.
Click to expand...
Click to collapse
Ok. No Problem
1. Reboot PC
1. Make sure Kies is not running in background?
2. Try using the Odin 3.0.4, the latest version 3.0.7 (some people have reported success with it after Odin 1.85 stucked) and let see what happens.
If it still does not flash then,
Visit this thread: http://forum.xda-developers.com/showthread.php?t=1457458
I have worked out that I can flash stock via Odin without issue. However, everytime I try to flash that version of CM recommended the flash fails.
I have checked (numerous times, just in case) that Kies is not running in the background.
I will have a go at the method mentioned in the linked thread - thanks.
Andy
Odd. As I was posting that last message, I heard the very pleasing SGS2 bootup tone and the phone is now showing the flashing 'S' logo - something I haven't seen for about ten hours! I had just flashed stock (for the nth time today!) and something has worked differently. At the moment I have not got past the 'S' logo, and still cannot boot into recovery but it seems like progress!
Andy
awicks said:
I have worked out that I can flash stock via Odin without issue. However, everytime I try to flash that version of CM recommended the flash fails.
I have checked (numerous times, just in case) that Kies is not running in the background.
I will have a go at the method mentioned in the linked thread - thanks.
Andy
Click to expand...
Click to collapse
Ok. Use the tutorial in the thread. Let me know if things work out for you.
PS: I don't know why the CM didn't work. I've used it to solve similar issues on this forum already.
Good luck
I have had a go at using the instructions in the linked thread, but so far without any luck. I have not yet managed to get hold of the .pit file, so haven't had a go with that. I will also have a go at flashing the GB ROM as well to see if that makes any difference.
Any other ideas?
awicks said:
I have had a go at using the instructions in the linked thread, but so far without any luck. I have not yet managed to get hold of the .pit file, so haven't had a go with that. I will also have a go at flashing the GB ROM as well to see if that makes any difference.
Any other ideas?
Click to expand...
Click to collapse
No ideas until you try every solution there. You are still missing the .pit file etc.
Swyped from my Samsung Galaxy SII
SUCCESS!!
I had corrupted the /data partition, so whenever anything tried to access any part of that partition the phone froze. To rectify it I used the pit files from this thread: http://forum.xda-developers.com/showthread.php?t=1667886 and moved the data partition be enough to completely avoid the section that was corrupted. I then flashed the recovery ROM as instructed in this thread: http://forum.xda-developers.com/showthread.php?t=1457458 and the phone is now booting.
I have now reinstalled CWM and CM9 so I am back up and running. The only downside of this process is that the internal memory pf my phone is now smaller due to the unused space left by shifting the data partition. If this causes me a problem down the line, I might re-partition using a pit file that doesn't shift the /data partition as much, and keep trying to see what the minimum shift is in order to avoid the corrupt part of the file system.
Thanks for all of your help,
Andy
Related
Hi forum,
I'm having big problems with my galaxy tab 10.1 p7510. I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot. Went into android recovery and wiped cache, some errors appeared and I wasn't able to turn on the tab for about a day. I held down the power button for a really long time and it went into a boot loop. Was able to get into recovery again, wiped cache again; since then I couldn't get into recovery any longer. But, I have been able to get into download mode. I downloaded the latest ROM (and the one before it) from sammobile.com; tried flashing both using odin 1.83, 1.85, and 1.87. Tried two different computers and various usb ports for each computer. installed drivers and kies, made sure kies was disabled when attempting flash. Result is always the same:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7510XABLPL_P7510UELPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I really don't know what else to do.
Should note, when i power off and power on, some red text appears quick (can't see it) and it automatically goes into download mode. At the top it says, "reason no kernel"
Please help!
Jim
focusbob said:
I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot.
Click to expand...
Click to collapse
What exactly were you transferring? Were you flashing a new ROM, restoring a backup or adding an update?
No, I was just transferring videos from pc to tab via usb. It froze, but I think it was when I tried to clear cache in android recovery that things went down hill. There are some known problems with factory resets with galaxy tabs due to a faulty chip. Maybe it was that? who knows. I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
focusbob said:
I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
Click to expand...
Click to collapse
In that case, congratulations and better luck next time.
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
aeinola said:
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
Click to expand...
Click to collapse
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Parva4 said:
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Click to expand...
Click to collapse
Send it for repairs and wait for several weeks to get it back? Very tempting. :cyclops: Lets call that plan B.
If i can do something to wake this baby up today or tomorrow i'll take it.
It sounds like you somehow softbricked your phone without even rooting it lol.
Anyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Instructions for unrooting: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-galaxy-s3-i9300/
Hope this helps!
chunghanjie92 said:
IAnyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Click to expand...
Click to collapse
I did try that and it did not work. Maybe i did something wrong? Dont know... Im pretty sure the problem is with broken partition. I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Do not use pit or repartition unless you know what you are doing.
jje
Sent from my GT-I9300 using xda premium
aeinola said:
I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Click to expand...
Click to collapse
NEVER CHECK RE-PARTITION trololololo .... and never use PIT unless you are know what you doing.
Wow! These "never use PIT unless you are know what you doing"-comments are really helpful. Thank you guys! :good:
Follow the instructions on this site:
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/
The site tells you how to root a phone (look at the picture to see what you need/don't need to check; usually all you need to check is Auto-Reboot and nothing else)
After the phone's rooted you can download a ROM from this site http://samsung-updates.com/device/?id=GT-I9300 and flash it into the phone using the same method you flashed the file to root your phone
Thanks for the help. Odin says: "There is no PIT partition" and FAILS.
So i NEED to Re-Partition, any help would be appreciated.
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.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>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
aeinola said:
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.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>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
Click to expand...
Click to collapse
Same thing for me, and I'm stuck with this problem for 2 months now!!!
I read that for some reason unknown, some S3 got these fuc*** motherboards!!!
If u can solve this without samsung service center, please post!!!:good:
Of course you can manage it without Samsng Service center, if you want.
The procedure is:
1. download to PC the I9300 Service Manual;
2. buy motherboard;
3. replace it by yourself.
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Which version of ODIN did you use? What kind of file(s) were you trying to flash?
Sent from my GT-I9300 using Tapatalk
I'm not sure but think it was Mobile Odin 3.65 and I was trying to flash CWM touch from xda.
Additionally, I think my battery charge may now be low after many attempts to recover it but will that matter bearing in mind I'm using Odin on my PC and the phone is connected to the PC by USB cable?
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
JJEgan said:
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
matrixmainframe said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
Click to expand...
Click to collapse
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
JJEgan said:
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
Click to expand...
Click to collapse
Kies is not installed on my computer and I have tried Odin versions 1.83, 1.85, 3.04, 3.06, 3.07 and 3.09.
I have also tried 'Samsung_USB_Drivers_1.5.27.0.exe' and 'SAMSUNG_USB_Driver_for_Mobile_Phones.exe' and remembering to uninstall then reboot and then install.
On one occasion it got as far as (can't remember the exact words) "Get PIT Mapping" but then just stopped there.
I cannot believe I have done anything other than corrupt the CWM recovery because all I did was try to flash CWM Touch and as soon as I pressed OK the screen went black with the word "Samsung Galaxy SIII GT-I9300". Those words just stay there because since then I can't switch the phone off. I thought that if I just reflashed CWM via Odin on my computer I would be able to get back into recovery mode and just restore my backup.
Appears I am mistaken and have ruined a very new and vey expensive phone.
The only other thing I seem to recall is that before I tried the Mobile Odin flash the battery was below 50% charge but I'm not sure if that's relevant?
This is usually a wrong file flash symptom .
JJEgan said:
This is usually a wrong file flash symptom .
Click to expand...
Click to collapse
Do you mean I'm trying to flash something I shouldn't?
Initially I tried to flash CWM Recovery but then decided just to try and get it back the way it was by trying to flash Android 4.1.2 again.
The file I have been using is "KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5" which I believe is from Sammobile and which is, I believe again, the ROM that the Galaxy S3 comes pre-installed with. Do you think it worthwhile me trying some other ROM?
I have been doing a lot more web research and some say that the battery charge should be more than 80%. Does this matter?
Won't the battery have been charging all the while the phone was plugged into into the Computer via the USB lead?
If I buy a separate charger and charge my battery to 100% do you think the Odin reflash will work then?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_HOME.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_HOME.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
llcoolveer said:
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
Click to expand...
Click to collapse
Nice to know I'm not alone but sorry you're having the same problem. Have sat down to do some more web searching and will let you know if I find a solution
Service centre new motherboard .
JJEgan said:
Service centre new motherboard .
Click to expand...
Click to collapse
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
llcoolveer said:
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
Click to expand...
Click to collapse
Please can you tell me what is "OG Recovery"?
Thanks
matrixmainframe said:
Please can you tell me what is "OG Recovery"?
Thanks
Click to expand...
Click to collapse
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
llcoolveer said:
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
Click to expand...
Click to collapse
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
matrixmainframe said:
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
Click to expand...
Click to collapse
I couldn't also....only when my battery was full charged....:good:
Succes....
The end
Okay, I started this thread so will end it now as follows:
1 Thank you to all those who offered help/advice/suggestions.
1a Some people do not read posts properly because even though I had specifically stated that I could not get into recovery mode some people proceeded to tell me to go into recovery mode and restore my rom.
2 Whilst I have recovered the full use of my phone I can no longer root it but that's ok because at least I have a phone that is comparable to the vast majority who choose not to root.
3 I will explain how I rescued it but obviously I don't really understand what the result is other than a usable phone so please don't copy.
4 Whilst I have no doubt one could damage a motherboard, that could only be done with very specialist software that most people would not have so the advice of some that I needed a new motherboard was ill informed. If you don't know the answer don't offer an unhelpful answer. Recommending a new motherboard is like a motorist taking his car into a garage with a blown fuse and the mechanic saying the only cure is a new car.
5 After a lot of research I found one lone website that explained that from July 2013 Samsung introduced a change to their ROMs which introduced an efs 2 file. Additionally it appears that once you have flashed/upgraded to an efs2 ROM you cannot then go back to an efs ROM.
6 This is above my understanding but I do know I did go from efs to efs2 and when I then encountered a problem I thought it a good idea to go back to my original (efs) ROM which I now believe caused my problem.
7 I did not know if I had found the answer but as I believed my phone was a paperweight at that point anyway I had nothing to lose and downloaded the GT-I9300.pit file and flashed with repartition selected. I then flashed Android 4.3 knowing it would be an efs2 ROM and my phone is now working again.
8 However, although my phone is now working again, I find that I cannot install a custom recovery nor can I root the phone but that is a small price to pay to have a brand new S3 working again.
9 Whilst it may not be wise to mess about with the pit file, it seems nothing can be lost to give it a go because even if it doesn't work you can still go for the new motherboard option happy in the knowledge you have tried everything.
10 I may start a new thread for advice on that matter but for the time being I'm just relieved to have my phone back and I stress again that it did work for my specific problem and whilst it might work for you please only do it knowing it may not work for your problem.
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Use this if it fails it needs service repair >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Happened the same too me and i have CM11 too... If you get a fix contact me please
emnt said:
Happened the same too me and i have CM11 too... If you get a fix contact me please
Click to expand...
Click to collapse
Try the above rescue firmware as suggested above make sure you know what you are doing before flashing.. Exactly same advice if that doesn't work service required partition corrupt..Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
blackbeardtwenty said:
The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen,
Click to expand...
Click to collapse
Hardware issue, either damaged or corrupt emmc chip.
tallman43 said:
.Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
Click to expand...
Click to collapse
Yeah, that was a desperate attempt at trying another root file which was recommended in another post. I initially used:
I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5
and this worked fine last month, but now I'm back to square one again. Any ideas on other PIT files or root files I can download which might do the trick?
Thanks for your comments so far, you're all a bunch of wizards...
So I unfortunately bricked my galaxy S4, but I am having issues unbricking it. I downloaded the full wipe and PIT file from http://forum.xda-developers.com/showthread.php?t=2735172 , installed the samsung drivers, booted into download mode, and set up both files, but whenever I hit start this occurs.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I have tried installing and uninstalling the drivers, and tried different USB ports. However, everytime I plug it in, it installs drivers even though they are already installed, Am I doing something wrong? I am not unplugging the phone in the middle of it at all, so I dont know why there is the Removed and Added at the end, even though the device is still plugged in and in download mode when both pop up. I need my phone to be usable soon so help is GREATLY appreciated.
Endstepper said:
So I unfortunately bricked my galaxy S4, but I am having issues unbricking it. I downloaded the full wipe and PIT file from http://forum.xda-developers.com/showthread.php?t=2735172 , installed the samsung drivers, booted into download mode, and set up both files, but whenever I hit start this occurs.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I have tried installing and uninstalling the drivers, and tried different USB ports. However, everytime I plug it in, it installs drivers even though they are already installed, Am I doing something wrong? I am not unplugging the phone in the middle of it at all, so I dont know why there is the Removed and Added at the end, even though the device is still plugged in and in download mode when both pop up. I need my phone to be usable soon so help is GREATLY appreciated.
Click to expand...
Click to collapse
Your phone isn't a 32 Gb model is it? The PIT file from that post is for 16 Gb. I don't even think they made the S4 in 32 Gb. What version of Odin are you using. I just did this same procedure 3 or 4 days ago and it all went perfectly using Odin v3.09. Also make sure you md5 check the PIT file and ROM file you downloaded, that is always very important. When you add the PIT file to the PIT box it should automatically check the box for repartition, so you can check that too. I'm not a developer or an expert by any means but I am a technician, so these are just some things I could think of off the top of my head from when I did this a few days back. Hopefully one of the more experienced experts will chime in too.
Endstepper said:
So I unfortunately bricked my galaxy S4, but I am having issues unbricking it. I downloaded the full wipe and PIT file from http://forum.xda-developers.com/showthread.php?t=2735172 , installed the samsung drivers, booted into download mode, and set up both files, but whenever I hit start this occurs.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I have tried installing and uninstalling the drivers, and tried different USB ports. However, everytime I plug it in, it installs drivers even though they are already installed, Am I doing something wrong? I am not unplugging the phone in the middle of it at all, so I dont know why there is the Removed and Added at the end, even though the device is still plugged in and in download mode when both pop up. I need my phone to be usable soon so help is GREATLY appreciated.
Click to expand...
Click to collapse
Try flashing it using a different USB (Non-3.0) port. Check how far it gets. Then try using Heimall. A free Odin alternative. Then If It doesn't reboot try a battery pull and hold the button to enter download mode, but then click restart instead/
npjohnson said:
Try flashing it using a different USB (Non-3.0) port. Check how far it gets. Then try using Heimall. A free Odin alternative. Then If It doesn't reboot try a battery pull and hold the button to enter download mode, but then click restart instead/
Click to expand...
Click to collapse
After switching from odin 3.09 to 3.07 the flash went through, so everything is up and running. Also my phone is a 16gb model, and I was downloading the full wipe file directly from the thread, so I'm not sure why it wasn't working. Thanks for the help though
Endstepper said:
After switching from odin 3.09 to 3.07 the flash went through, so everything is up and running. Also my phone is a 16gb model, and I was downloading the full wipe file directly from the thread, so I'm not sure why it wasn't working. Thanks for the help though
Click to expand...
Click to collapse
Glad you got it going. Even files from XDA threads can download faulty, it has happened to me before. So as a good measure performing a md5checksum is a good idea. Most of the folks here who post those links provide the md5 check value so you can ensure your download is clean. I am a Linux user so it's easy to do in Linux from the terminal. Now you can install Safestrap and Hyperdrive ROM to really have some fun! Enjoy!
Same problem
Endstepper said:
After switching from odin 3.09 to 3.07 the flash went through, so everything is up and running. Also my phone is a 16gb model, and I was downloading the full wipe file directly from the thread, so I'm not sure why it wasn't working. Thanks for the help though
Click to expand...
Click to collapse
I am having the same problem that you are/did. Am I reading this correct all you did was download odin 3.07 and flashed the file that goes in AP and it worked fine?
FireMedic1234 said:
I am having the same problem that you are/did. Am I reading this correct all you did was download odin 3.07 and flashed the file that goes in AP and it worked fine?
Click to expand...
Click to collapse
You need the PIT file too. You put that in the PIT box and the tar.md5 in the AP box. I was able to make everything work perfectly using Odin 3.09. Not sure why the OP had an issue with it but if 3.07 works then that's all that really matters.
Thank you
robn30 said:
You need the PIT file too. You put that in the PIT box and the tar.md5 in the AP box. I was able to make everything work perfectly using Odin 3.09. Not sure why the OP had an issue with it but if 3.07 works then that's all that really matters.
Click to expand...
Click to collapse
Thanks. I tried to do the update on Hyperdrive to 18, and weird stuff started happening. I went through all the install options and while it was installing it quit at 30% and went back to safe strap. I tried to reboot it through safestrap and it kept saying there is no system installed. Eventually I tried it anyways and it booted up, and it was Hyperdrive 18. then the wifi didn't work so I tried the old patches for 17 that didn't work, so i tired flashing 17 and was going to wait for 18 and the install did the same thing it quit at 30%. I have no idea what the hell is going on so I figured I'd wipe in and start fresh, but when I woke up this morning, the wifi on 18 works. I am lost.
FireMedic1234 said:
Thanks. I tried to do the update on Hyperdrive to 18, and weird stuff started happening. I went through all the install options and while it was installing it quit at 30% and went back to safe strap. I tried to reboot it through safestrap and it kept saying there is no system installed. Eventually I tried it anyways and it booted up, and it was Hyperdrive 18. then the wifi didn't work so I tried the old patches for 17 that didn't work, so i tired flashing 17 and was going to wait for 18 and the install did the same thing it quit at 30%. I have no idea what the hell is going on so I figured I'd wipe in and start fresh, but when I woke up this morning, the wifi on 18 works. I am lost.
Click to expand...
Click to collapse
It doesn't sound like it flashed properly at all. I am still running RLS 17.1 but it is as smooth as can be. Which Odin Version are you using? What Safestrap version are you running? I used Odin 3.09 and am running Safestrap 3.72. Also make sure you use the USB cable that came with your phone, I have always had success in doing so. Make sure you md5 checksum all your downloads to ensure they are clean and not faulty. Lastly make sure that before rebooting to the system you also install SuperSU from Safestrap and if using Hyperdrive 17 the NC5 Modules. Here is a great video for doing everything.
https://www.youtube.com/watch?v=2bDe_-mB7Rw