Fix: semi bricked/bricked SPH-L710 Sprint S3 - Sprint Samsung Galaxy S III

when I 1st rooted my s3 on 4.3, I messed it up lol I fixed it this way, which is installing a clean slate of 4.3 OTA via Odin...mine was a semi brick and keyboard was somehow gone as well, so this was my only choice:
1st download my bundle I made here
-once downloaded, extract the bundle preferably to your open desktop or wherever is easiest for you to guide through
your phone must have USB debugging mode enabled if you haven't done it already
-settings>more>developer options>enable usb debugging
-if you've never done this before, you'll have to go to: settings>more>about device>build number (tap on build number several times until the countdown states you're now a developer, once done press back once and developer options will now be present)
now once that's done, pull the battery, reinsert the battery and reboot into recovery by: holding volume up/home and power keys
once in recovery, do a factory data/cache wipe (fully wipe it out!)
now once that's done, pull your battery, reinsert your battery, hold: volume down/home and power keys and you'll be prompted with a warning and to press volume up to proceed, press volume up...this is "download mode"
on your computer, open the extracted bundle and run Odin 3.09 and make sure ONLY "auto reboot" and "f. reset time" boxes are checked
-connect your phone via usb cord and the ID: com will now light up and indicate it has detected your phone (if not, you'll need samsung drivers which can be found here)
-once recognized, load the necessary file by checking the box by the AP tab and then clicking the AP tab and load the .tar.md5 file in the bundled folder...this may take a few seconds, it's a large file so be patient
-once file is loaded, hit the "start" button and DO NOT INTERRUPT THIS PROCESS! once it's finished, again this is a large file and will take some time to finish, you'll see a "PASS" in Odin and also in the log box it will say "all threads completed (succeed 1/fail 0)
your phone will now reboot itself and restart with a freshly installed 4.3 OTA operating system! if it fails, try again and if it fails again, your phone may just be beyond repair...heard they can make a nice paper weight decoration lol GOOD LUCK!
To Reroot your phone: use my rooting guide

Nice post, I am sure that it will save someone.

Thanks OP!
I had a software brick and it worked out perfectly

phone_dude said:
Thanks OP!
I had a software brick and it worked out perfectly
Click to expand...
Click to collapse
thanks for the feedback and glad it worked! if you're looking to root it again, I have a guide up as well on doing that for 4.3, you won't brick by following that guide

Question, will doing this while on 4.3 and reinstalling 4.3 reset Knox counters? Or is there anyways yet to return to an unroofed stock with all Knox trips reset?
Sent from my SPH-L710 using Tapatalk

it should...this would be just like going to the sprint service techs and having them completely wipe and reinstall the 4.3 ota firmware like new

THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.

beejmeister said:
THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.
Click to expand...
Click to collapse
thanks for the compliments and glad it worked out for you, that's all that matters

Count my @$$ as saved
Well, looks like you saved my @$$. My phone noted that there was an update for cyanogenmod.... and bricked on reboot.

hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:

mister-crackers said:
hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:
Click to expand...
Click to collapse
just saw your post...glad it worked for you! let me know how you make out on your next tasks bro!

"Process com.android.phone has stopped"
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.

neadams99 said:
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.
Click to expand...
Click to collapse
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall

Followed your steps using ODIN -passed- stuck on s'sng logo
goku2778 said:
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall
Click to expand...
Click to collapse
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.

neadams99 said:
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.
Click to expand...
Click to collapse
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back

2nd attempt failed.
goku2778 said:
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back
Click to expand...
Click to collapse
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?

neadams99 said:
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?
Click to expand...
Click to collapse
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin

can get into DL mode passed ODIN but then stuck w/logo
goku2778 said:
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin
Click to expand...
Click to collapse
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <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> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?

neadams99 said:
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <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> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?
Click to expand...
Click to collapse
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back

Not getting past Samsung logo
goku2778 said:
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back
Click to expand...
Click to collapse
So so Sorry, if you were in CA, I'd come by so you could do it yourself. I;d even pay you good money. OK, sorry, I was freakin out, brah.
I did use ODIn and waited for a long time and the Samsung logo just hangs there. There is no progress, nothing. I can't get to the signing into Google or anything at all.
You said, " THEN you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu." But I cant get past the logo. I see the "Samsung" for two secs, then "Samsung Galaxy Slll" then the Sprint logo goes by with music, then back to the "Samsung" logo where it sits forever. This is killing me.

Related

[Q] noob who thinks he has .PIT trouble

Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
re: pit file
WetbehindEars said:
Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Click to expand...
Click to collapse
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Misterjunky said:
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Click to expand...
Click to collapse
Sorry, I should have mentioned all of that...
As far as I know, I cannot enter into any type of recovery... the only thing that's working right now is download mode, no other button combinations work (volume up+home+on gives me the "Firmware upgrade encountered an issue" story, same with volume up+volume down+power). So I have no way of doing a wipe, unless there's something else I can do. Is there a way I can wipe the phone remotely, from my computer?
A couple other specifics that I should have mentioned in OP:
This phone is only five days old and has not be rooted or modded at all up until yesterday.
I've never put an SD card into the phone (though I have one handy, if there's something I need to do that requires one).
elesbb said:
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Atmazzz said:
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Click to expand...
Click to collapse
Thanks, I haven't tried a different usb port... I'll try that when I get home. The USB cable I'm using is the brand new Samsung cable that came with the phone, I don't think it's the problem but I'll give it a try anyway.
Thanks!
Edit:
After some more digging, I think I might have NAND rw corruption issues (since I can boot into download mode but not into any kind of recovery/bootloader mode). I get this notion from reading http://forum.xda-developers.com/showthread.php?t=1457458, which isn't for the GS4 but I figure it's probably a good diagnostic tool for both. In the thread, Phistachio says that reflashing the kernel (and if that fails, the bootloader) will fix the problem. Will this fix the problem for the GS4 as well?
At this point, I will try a different USB port and/or cable and if that fails, I'll try reflashing the kernel.
Does that sound good?
WetbehindEars said:
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Click to expand...
Click to collapse
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
re: cable, usb port, drivers
WetbehindEars said:
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
Click to expand...
Click to collapse
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Misterjunky said:
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Click to expand...
Click to collapse
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
WetbehindEars said:
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
Click to expand...
Click to collapse
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
elesbb said:
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
Click to expand...
Click to collapse
Yeah, the USB was probably already busy powering the fan and didn't want any of my Odin nonsense.
Thanks again for all the help!

[Q] Major issues flashing new ROM, help needed badly!

Hi.
First off, I've had my sgh-t999 since launch. I rooted it, and put TWRP recovery on it. I have used multiple roms over the past year with no problems at all.
I recently went to switch to a new rom. (new version of IOKP, upgrading from old infamous rom)
steps I took:
1. Placed rom on SD
2. Booted into Recovery
3. Wiped dalvik, and did full data wipe
4. flashed rom, success
5. Rom got stuck loading and wouldn't work.
Figured I needed to reinstall the rom, as this has happened to me before on previous phones.
6. Tried to reboot into recovery, Phone would not allow me to go into recovery, the blue text appeared at the top, but the phone would reboot itself after a second of the blue text leaving. (I tried adjusting the length of time I kept the buttons pressed down, both shorter and longer, to no avail.)
7. I looked up how to fix this. I used odin and the stock T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 to flash it back to stock.
8. The phone booted fine and I was back like normal. HOWEVER, I had no 4g, no wifi, my home button didn't work, and I had a lot of other errors.
9. I figured I should try to use a different stock rom, however ODIN began giving me error messages.
<ID:0/007> boot.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> recovery.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> system.img.ext4
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what USB port I use I get the same error. I even downloaded a .PIT file and tried to flash again. Same error message.
10. Now my phone is stuck. I cannot get into the phone, I cannot get into recovery, and when in download mode it reads "Firmware upgrade encountered an issue."
11. Kies doesn't even recognize my phone.
I am at a loss for what I need to do.
In case it helps my "download mode" screen says
sgh-t999
6 counts
binary:samsung official
status:custom
secureboot:enable
warranty bit:1
bootloader ap swerv: 1
Does anyone have any idea where I should go from here? I hate being stuck. I also use my phone for work, and am losing money the longer I go without it. If anyone can provide help, I would be forever grateful.
What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk
serio22 said:
What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Stock 4.3: T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 was the file I had flashed. My phone booted up, but I had no 4g and no wifi. I hooked it up to odin again to reflash the same firmware, and my phone is now stuck at the black screen that says firmware update error.
Every time I use odin it returns an error no matter what stock firmware I try and use. I tried a .PIT file in combination with T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5, and it still returned an error.

Guess what? I bricked my SGH-i317M :)

I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> Firmware update start..
<ID:0/003> sboot.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)
idoit said:
I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> Firmware update start..
<ID:0/003> sboot.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)
Click to expand...
Click to collapse
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
dicksteele said:
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
Click to expand...
Click to collapse
By reading around, I was getting the impression that I need to flash .pit file along with the stock ROM but as I don't want to get things worse I was reluctant to do it. My searches for odin package without sboot.bin takes me no where. Not that I am a super Android toddler but any help is certainly more than appreciated. Well Ok, I'm noob. admit it. :good:
Edit: I found out about N7100UBALJ2_N7100TCEALJ1_TCE ROM from http://forum.xda-developers.com/showthread.php?t=2523366 but not sure if that solves the problem or that's relevant as it's for N7100 and mine is SGH-i317m... same family but who knows maybe different ROMs! ?
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Don't use a pit file. That partitions all of your phone.
rangercaptain said:
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Click to expand...
Click to collapse
Update: I uploaded the recovery.log file from TWRP by accessing with adb in recovery mode.
Nothing happens when I connect it to PC in normal mode... I mean just connecting it as it is. (NOT in recovery mode or download mode).
Right now, I am in Windows and when I connect it in download mode, I try to adb but it says device not found. In recovery mode, I can adb but as I said in first post, I can't read or write. MicroSD is not recognized, so I can't put stock ROM there either. Is there any hope to get my phone back?
Don't use a pit file. That partitions all of your phone.
Click to expand...
Click to collapse
Well, I did try to flash a pit file from here, but it fails with same NAND Write error!
I have a good news.
So I went to /dev/block folder when ADBing and noticed mmcblk0 device. I manually mounted mmcblk0p1 and yoohoo it is mounted. It means now i can put my TWRP backup files there and run TWRP restore. Is that a good idea?! Does it make sense at all? I mean I am desperate for any way to get this thing back, a shadow of hope is huge for me too now.
Update: Ahhh damn it! I mount the MicroSD from adb to /external_sdcard (this is the folder where it used to mount my external microSD) in TWRP. Using File Manager provided by TWRP, I confirm the folder is there. But when I go to Restore section, it doesn't show any partition and it doesn't let me choose external memory. It's like this:
- Internal Memory (0MB)
- External Memory (0MB)
- USB OTG (0MB)
Any thoughts? I feel I am so close but not there yet.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
rangercaptain said:
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
Click to expand...
Click to collapse
Alright, done.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Click to expand...
Click to collapse
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Now to report back the result from Kies FER:
I follow the instructions word by word. As the screenshot shows, Kies tells me to put phone into "Recovery mode"by pressing on power button. Well, either Samsung doesn't know what recovery mode is or ... Anyways, I take battery out and etc and boot to normal phone by pressing on power button... and "Free Upgrade"button is still grayed out. I go to Recovery mode (Power + Home + Volume Up) and it is still grayed out. (first screenshot attached below)
It's only in Odin Download mode (Power + Home + Volume Down and then Volume Up) that it becomes available.
After some time, the following error appears. I have done it a couple of times now and I restarted my Windows too. but no dice.
(second screenshot attached below)
idoit said:
Alright, done.
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Click to expand...
Click to collapse
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
dicksteele said:
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
Click to expand...
Click to collapse
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
idoit said:
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
Click to expand...
Click to collapse
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
dicksteele said:
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
Click to expand...
Click to collapse
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms, 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
Awesome on the firmware site BTW !
dicksteele said:
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
Awesome on the firmware site BTW !
Click to expand...
Click to collapse
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
Hi Guy, my problem is that my phone lost baseband version and IMEI number. I download the stock rom: TLS_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3; The rom did not fix the issue. After I install it, the baseband version and IMEI number still shown Null. Could you please help me? Thousands thanks!
Click to expand...
Click to collapse
This was posted long before the 4.1.2 came around, but you have all the guts there when trying to roll back to 4.1.1 not even aware that there might be a new bootloader added on 4.1.2 I317MVLBMA3 update and returning back to 4.1.1 is quite risky
If you did not touch your device before using rooted kernels and/or custom. I suggests that you must stay on 4.1.2.
Click to expand...
Click to collapse
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
You won't lose your baseband or IEMI. What you are doing is returning your phone to 100% factory stock (except for the 4.3 bootloader). You can deal with any other issues as they arise/if they arise from a working phone easier than you can from a borked phone.
Why eight hours to download?
idoit said:
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
​
​
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
Click to expand...
Click to collapse
The losing the IMEI was because of a different issue I believe.... The /efs partition holds all the important cel info. As long as that's not hosed you're fine...
OMNIROM should not have touched that.
Backing up your /efs can be done a couple of ways.
http://www.xda-developers.com/android/backup-your-efs-partition-with-easy-to-use-app/
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
idoit said:
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
Click to expand...
Click to collapse
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
dicksteele said:
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
Click to expand...
Click to collapse
This is being downloaded quickly. Until that download is finished, I knew yesterday I downloaded I317M_BWC_I317MVLALJ2_I317MOYAALJ2_Original (Similar to the one you just said to download but for Bell). You're right, this one doesn't have sboot.bin but it does have boot.img. Anyways, I tried to flash it with Odin3 v3.04, and it fails on me!
Firmware update start...
boot.img
NAND Write Start!
Complete(Write) operation failed.​
Now, I have no idea what to do next! Wow, phones and even products from big companies like Samsung are so fragile.
[Off-topic]
Boy, these last 3 days had been hectic. First this happened to my Phone. Then today, when I was in Windows (which I rarely use, I went on Disk Management and made my C partition active). Stupid Windows, wiped all my partition table!!! And now my laptop is a piece of brick too. Oh boy, you know, when it rains it pours!

[Q] Stuck in bootloop, Odin keeps failing

Hey everyone, hoping someone can help me out here.
Recently I decided to set my S3 back to stock after running Cyanogenmod for quite some time. Somewhere along the way, I must have grabbed a wrong file, but one thing led to another and my phone got stuck on the Samsung logo while booting. I am able to get my phone into download mode and have tried to flash any rom I can through Odin, but it fails every time. I have even gone and got the official firmware from the Samsung site and it still fails. Here is the error:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Anybody have any ideas what I'm doing wrong? Thanks
Odin is failing because you are trying to downgrade the bootloader.
What bootloader is on your phone? You have an i747 or i747m?
I have the i747
With an i747 and the fact that Odin is giving an error when trying to flash a stock LK3 ROM, you must have at least a 4.3 bootloader. This means that you cannot use Odin to flash a stock ATT 4.3 or ATT 4.4 ROM unless the ROM has been specifically compiled for use in Odin.
Do not make anymore attempts to to flash the stock LK3 ROM as this may brick your phone.
If you still have a custom recovery on your phone, flash any custom ROM and let us know the baseband.
We're all here to help.
Is there any way to get into recovery mode other than holding the volume up, home, and power buttons? The volume up button on my phone has been broken for quite some time and it took me a while to even find a way to get into download mode so I could attempt to use Odin.
VctrEco12 said:
Is there any way to get into recovery mode other than holding the volume up, home, and power buttons? The volume up button on my phone has been broken for quite some time and it took me a while to even find a way to get into download mode so I could attempt to use Odin.
Click to expand...
Click to collapse
Do you have a ROM on your phone?
Do you mean a ROM in a zip folder that I could flash through recovery? Because I think the only one I have on my phone is the one that could this big mess up
Sorry, I should not have used such ambiguous wording.
Does your phone have a ROM installed that will let you boot to the phone's desktop?
Not sure if this helps but you may be able to use this to flash a ROM and recovery: http://wiki.cyanogenmod.org/w/Insta..._custom_recovery_on_Galaxy_S_III_.28AT.26T.29
Do you have a USB jig?
audit13 said:
Sorry, I should not have used such ambiguous wording.
Does your phone have a ROM installed that will let you boot to the phone's desktop?
Click to expand...
Click to collapse
That I don't really know about. Is there a way to figure that out? Right now if I just boot the phone, it gets to the Samsung logo and just stays there, never goes any farther. Never makes it to the home screen.
Also, thank you for all your help so far, apparently I don't know as much as I thought I did..
Your phone could have a ROM installed but you probably need to get into recovery to wipe the cache, Dalvik, and data.
I suggest putting a custom rom such as CM10.2 onto an external SD card and try to get into recovery to flash the new ROM. Make sure you wipe cache, dalvik, and data before installing CM10.2.
Ok I will try that and hopefully something will happen. Do you know of a way to get into recovery other than the button combo since I don't have a functioning volume up button and also can't get to the home screen to boot to recovery from there.
Not sure but fastboot commands could work in download mode.
Those commands are given through ADB, correct? I installed ADB and it doesn't show up in the list of devices. I think that since the phone is stuck in a bootloop, it never gets to a point where it can be recognized and receive commands. It also doesn't get recognized in download mode.
When you connect it in download mode, are the drivers installing? Or were they installed from when you first used Odin?
You may have to try and get into recovery using the recovery keys. You have a USB jig?
I uninstalled the original drivers and let it reinstall once I plugged it in, but it still is not recognized. And no, I don't have a jig, I found a program that acts like one that puts it in download mode once I plug it in.
Putting the phone into download via USB program? That would be very helpful for many users. Do you have a link to the program?
I assume you could not get into recovery mode on your phone. Do you have the Touch version of CWM on your phone?
audit13 said:
Putting the phone into download via USB program? That would be very helpful for many users. Do you have a link to the program?
I assume you could not get into recovery mode on your phone. Do you have the Touch version of CWM on your phone?
Click to expand...
Click to collapse
Correct, I cannot get to recovery by using the volume up, home, and power buttons. I was hoping there could be some other program or commands to help me get to it since ADB won't recognize my phone.
And here is the link to the forum with the program that forces it into download mode. It even picks up my phone in a boot loop
http://forum.gsmhosting.com/vbb/f777/samsung-300k-tool-force-enter-download-mode-via-usb-1718796/
Interesting. I don't have a s3 to try it with but I will definitely keep it around
Do you have any hidden tricks to get into recovery mode without using the volume buttons? It seems like all my problems could be solved if I can get to recovery and flash a ROM, but that broken volume button is preventing me...
Sorry, I just know the button combination or from a booted ROM.
Too bad Samsung doesn't readily support fastboot commands.

Looking for a debrick.img for Android 5.1.1

Is anyone able to point me in the right direction or is willing to make one?
The i747 does not have a stock 5.1.1 rom; therefore, there is no debrick image for a 5.1.1 rom.
What bootloader is on the phone? Did any of the images from the debrick thread boot the phone?
Does installing 5.1 change your bootloader?
As in Cyanogenmod 12.1?
Softbricked my S3, and I'm not sure which way to attempt to recover/debrick & would appreciate any advice.
SGH I747 (ATT)
rooted 2 years ago just after 4.3 OTA updated, flashed with CM 11.
Had that on there for almost a year, got bored & installed carbonrom.
Beginning of december, flashed CM 12.1.
A week ago it got stuck on the boot logo.
Still able to get into both Recovery & download modes.
Clockwork mod 6.0.4.7
trying to flash from a new image or wipe & factory restore both give me
Code:
detected file system ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching unconditionally
E: error in /storage/sdcard1/cm-12.1-201511117-sna[status 0] installation aborted
trying to use Odin, it gives me
Code:
<ID:0/003> Added!!
<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> recovery.img
but never does anything, even hours later.
At unplug, I get
Code:
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The info on the download screen is
Code:
odin mode
product name: sgh-i747
custom binary download: yes (6 counts)
current binary: custom
system status: custom
qualcomm secureboot: enable
warranty bit: 1
bootloader ap swrev: 2
My guess from another thread is that the /system and /data partitions are not wiped properly, causing those partitions to be formatted with read-only (R/O) permissions rather than read-write (R/W)? But those files are definitely not right for my phone, so what now?
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
audit13 said:
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
Click to expand...
Click to collapse
Good to know.
Thanks.
But how do I get twrp onto the phone?
was actually trying to put twrp on with odin, but that's not working.
The downloads I've seen are for:
app-phone doesnt boot
odin- aint working
TWRP Install - Requires TWRP 2.8.4 or higher already installed
dd Install Method - oh, didn't see that one. I'll try that & let you know.:laugh:
---------- Post added at 06:54 AM ---------- Previous post was at 06:16 AM ----------
well, I'm not figuring it out....
As per the twrp page, tried: dd if=/sdcard/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
tried: dd if=/storage/sdcard1/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
did ls (hey it's like linux!)
got possible locations: external_sd, sd-ext, sdcard, also looked under mnt.
file not found error
cd'ed & ls'ed to /storage/sdcard1/ there it frickken is!
ran the command there, sans path, and still get file not found error
arrrrgh.
Try this:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy
very detailed response, thanks. I've tried most of that, as some thread I was reading said that twrp probably has the capability to fix the issue, and CWM definitely doesn't.
Odin never really does anything, though. How long should I wait?
This step is the one I haven't done "7) open Odin 3.07 and uncheck everything except f. reset time;" Just left everything alone the multiple times I tried. Hopefully that'll make a difference.
Tried 3.07, 3.09, 3.10.6. I'll try again.
By default in Odin 3.07, only auto reboot and f reset time are checked.
What do you mean when you say Odin does nothing? Does the phone appear as a com device in Odin? Are there error messages in Odin during the flash process?
never gives anything other than:
Code:
<ID:0/003> Added!!
<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> recovery.img
not at a windows computer for a couple days. stuck on linux mint with no internet. has heimdall & adb, though....
have twrp img & tar, cm12.1, and gapps on the sdcard.
All I can suggest is to try and get access to a pc or try VMware with win7.
Tried again last night for about 12 hours, no response from Odin.
Decided to give jtag a shot.
Contacted the jtag guy & gave him all the above info.
He says
"Unfortunately there are many indicators that your phone has a hardware failure.... Most likely a failed emmc memory chip.
1) the phone getting stuck on boot logo for no reason.
2) Odin not flashing...
3) files not found or... Not being able to do.
These are all indicators that the emmc memory chip is toast...... The biggest clue is finding the phone stuck on boot logo... Out of nowhere for no reason.
Jtag would not be able to fix it.
Thank you"
:crying::crying::crying::crying::crying::crying:
Thanks for the help.
Might sell the remains.
16G I747 blue, normal wear & tear, small chip in one corner, the case covers it.
2 stock batteries
1 7800mah best4power battery
1 otterbox defender modified to hold extended battery without the turtleback
any offers?
i suggest trying on a Windows machine before giving up. I am not convinced the memory is damaged.
That was on a windows machine...
Odin recognizes the phone but it won't flash twrp? Have you tried different USB cables and USB ports?
I found that my s4 and s3 would fail to flash if I don't use the USB cable that came with my Samsung or LG phones.
yes to both cable & ports.
bought an LG K7, which I mostly hate, and can not root.
keeping my S3, looking for someplace cheap to replace the chip.
I bought my lg k7 today(LGMS330)metropcs i rooted it in 2 mins.with xda's KINGROOT..then removed Kingroot with WOLFDROIDS script...and now im running BUSYBOX STERICSON 1.24.1 and ChainFires SUPERSU 2.49..IT KILLS me when people cant root there devices...i did this ALL in the BURGERKING BATHROOM GOIN BOO BOO
Ok so i rooted my darn k7 ...but like a jackars i bricked it...no TWRP...NO KDZ FIRMWARE...CAN ANYONE PLEASE ...PRETTY PLEASE SEND ME A LINK TO THE METROPCS variant of the LG K7 (TRIBUTE 5) KDZ STOCK FIRMWARE..I JUST BOUGHT A $150 ELECTRONIC PAPERWEIGHT...the k7 is so new there is no support anywhere...in fact all u really find is the ads for the debut of the device in stores ...major noob mistake..im truly embarassed..PLZ HELP
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
just got a $150 paperweight...lg ms330 i do hate you now...
o4tuna said:
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
Click to expand...
Click to collapse
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
AbErCrMbPlAyA said:
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
Click to expand...
Click to collapse
I had a amazing talk with the lg develeopers yesterday....since I am in the same boat since my lg k7 is bricked....I ask them for the kdz firmware so I can reflash my phone....you wanna know what they told me?
first they ask: whats a kdz file?
their answer: We don't make those thing you need the official lg tools to update your device firmware....so we cant help you...
Me: I am extremely pissed now since they are lying to me & then I showed them a link from their server to DOWNLOAD a kdz file firmware for another device that I had....
their answer: we dont know what you are talking about...sorry we can't help you!
I even went to my nearby metropcs store & explained to him what happen...
first. he didn't understand the following:
1-bootloader
2. boot image
3. recovery mode
4. download mode
5. kdz firmware
6. bricked & softed-bricked
the f-cking guy told me I can't do anything, but "report my phone lost or stolen" so I can get a new one....
How the hell are these idiots getting jobs when they have NO IDEA what to do on how to fix a phone
My level of anger is now over 9000.....

Categories

Resources