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!
Related
OK--1st post EVER in a forum, so I feel like I'm gonna get layed into,
but here goes:
Just got Epic Touch two days ago and felt I needed root so I downloaded
and used the EL29 Odin one-click method of flashing the stock rooted ROM.
This was yesterday. No problems. Took 15 minutes. I installed some apps,
then I installed ROM Manager And tried to use it to install CW, but I'm not sure if that was successful, as I tried to do a couple of NAND backups from within the GUI
of ROM Manager and failed both times, going to the stock android recovery screen.
I think I pulled the battery both times.
Then I installed Widget Locker, was playing around with that for a bit, took
a photo and tried to attach it to a text response, then the phone locked while
I was sending that. Pulled battery, wont get past Samsung startup screen.
Looked around a bit, decided to try and reflash using the one-click method.
I get:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> recovery.bin
every time. BTW, I cannot access anything with VolUP+power buttons.
I've tried different combos of that, always Samsung boot screen hang.
I can get into Odin, and Odin sees my device. but never has the device indicated
that anything is happening. No progress bar.
Also, I have tried the two USB cables that i have in all the ports of my computer,
but I do not have another handy.
So I poked around and found this:
http://forum.xda-developers.com/showthread.php?t=1492771
which suggested I individually flash ROM, kernel, and modem.
none of that has worked, either.
Flashing the modem does get a green progress bar(in Odin, not on the device),
but then it hangs at--
<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> modem.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
flashing kernel yields:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_KERNEL_PDA.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!!
...and a hang.
So....... haven't foud anything else adressing this. Lotta stuff out there about
careless ICS/CWM brickers, but I didn't do anything fancy, did I?
Just stock rooted, 5 hours of use and blammo.
Thanks for the assistance.
Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?
Edit: If you need them, the samsung drivers are here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Please remove kies prior to installing them. In any case, you should probably uninstall what you have now and install the driver suite if it's still not working, then reboot the pc and try again. Sometimes the drivers aren't working correctly and require a reinstall.
I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure.
Sent from my SPH-D710 using XDA
I think what Rocket meant to say is not use Rom Manager any more.
Sent from my SPH-D710 using XDA
RE:
>> Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?<<<<
I have BOTH installed...but Kies I only installed midway (i.e. this morning)
through troubleshooting. nonetheless i will uninstall/reboot/reinstall/reboot
with these guys. Which is better?
And YES, EVERY time i've tried something with either EL29 oneclick or 1.85 regular Odin, I have always started Odin first, and then plugged the phone in.
If I plug the phone in before putting it in download mode, it just displays an empty battery charging icon, and cannot be turned off except by removing battery.
RE:
>>>>I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure. <<<<<<<<<<
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Thanks for the replies.
iguai said:
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Click to expand...
Click to collapse
It sounds like you're ok but Kies needs to go, it conflicts with the regular drivers and causes issues using odin. Goood luck and let us know how it goes.
make sure the samsung drivers are on you PC/Laptop. make sure your computer sees your phone. I have read that sometimes trying different USB ports and cables can be helpful as well when using Odin. hope this helps.
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
iguai said:
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
Click to expand...
Click to collapse
You're likely bricked. Sorry. Rom Manager has been bad for almost all Samsung phones.
Sent from my SPH-D710 using XDA
Allow your phone to charge for SEVERAL hours.
Follow this guide to the letter: http://forum.xda-developers.com/showthread.php?t=1274337
Flash this rom which has root: http://forum.xda-developers.com/showthread.php?t=1703406
If you follow this correctly and your phone does not boot. You are bricked.
Sounds like somehow you reversed the modem or rom and flashed them between the phone and pda (which I hope you didn't because you are bricked if you did... but its good in away because you can take it back and say look what I woke to...).
Let us know if it works...
Edit- and if it does boot, don't ever try to install cwm with rom manager on this phone.
No dice. I am, however, going to give it one more try on a friends computer this evening. That's my last throw though, I think, unless I get some fresh inspiration.
I'll report back tomorrow.
OK---I gave it everything, and no dice.
This phone was bricked.
I believe using ROMManager to try and install CWM f'd some things,
and perhaps when I was trying to do individual flashes
in Odin I flashed a modem in PDA.
Thanks for all responses.
Tried everything and nothing
So I wasn't trying anything crazy with my phone, left it charging, and went to check the time and it was off, tried turning it on and nothing.
I was running CM10 Beta 2... so I went into recovery mode, tried to run do wipe factory reset, wipe dalvik, wipe cache, flash the CM10 again, and it was getting stuck.
Mounted usb on pc and tried to save some files to flash the full tar through odin, in the middle of that copy it failed, so I tried to odin the tar anyway and it was getting stucked.
Tried flashing modem separately - stuck on Wait 2 mintues...
Tried flashing kernel separately - stuck on NAND Write Start!!
Tried flashing rom - stuck
Tried flashing pit file - stuck
Tried one click - stuck
The thing is that I can't just say to samsung service that I didn't do anything to the phone, because when you try to boot in recovery it shows CWM 6..., but only one line, it doesn't really load cwm.
So even if I use a usb jig to reset odin counter, they'll notice I had done some stuff to the phone, even when I wasn't really doing anything when it crashed.
Any new way to fix the phone? I don't have insurance or anything, so I might be pretty much screwed
Anything else I could do? Thank you very much!
I figured I would post this as a basic how to for people who brick their phones because they are in a similar situation.
Sprint Samsung Galaxy Note II SPH L900
Used this root method because it was for Samsung Note II owners who already had Android 4.3.*,
http://honai-android.blogspot.com/2013/06/how-to-root-galaxy-note-2-sprint-sph.html
Installed TWRP but it didn't stick to Download mode. I could boot into TWRP when my phone was up even after rebooting but could not boot the device directly into TWRP to access my custom recovery image.
Installed Perseus and Macks Rom AllStar V5.0 after saving them to my SD Card and did this after booting into TWRP from within my stock ROM.
Like an idiot I didn't read all the comments on ChainFire 3D when I was searching root 3d because I'm on a big kick right now of making it all 3d like.
Instead of flashing ChainFire 3d from recovery I used my in rom option since I had all my root programs running nicely and thought why not its just a button click instead of rebooting into TWRP. There was my mistake.
Alright so now I am bricked out of my phone in a boot loop. Nothing is happening but ChainFire said when you install not to freak out if your phone hangs for awhile, pull the battery after two minutes. Well I did and still bricked in a boot loop.
Scour the forums and Internet because I know I still have access to my phone through Odin. I don't have debug mode turned on so I can't even create an ADB shell to my device. That was my first through, run ADB shell, launch TWRP and restore my custom recovery. Would have worked except I had no way of getting to TWRP. Tried installing the Samsung ToolKit. Couldn't recognize my device.
Opened Odin back up and thought why not try to flash TWRP and have it reboot, maybe TWRP will launch. Well I don't know if that would have worked or not because every time I tried to reflash TWRP Odin encountered an error.
Alright, abandoned that idea and did some more research. I knew I could still flash to my phone but I didn't have anything to reset the caches to install another ROM and I didn't want to install something else where things could go potentially worse. I needed my damn phone back. Boom! Found some very helpful articles on restoring to stock and found the stock recovery one click solutions.
I am making this so lengthy in case you are going through something similar where you are stuck in a boot loop, locked out of TWRP but can still flash to your phone with Odin.
These two threads were massive help and they take you to the file locations:
http://forum.xda-developers.com/showthread.php?t=2116490
http://www.sxtpdevelopers.com/showthread.php?t=154
I restarted my phone in download mode which was a little tricky because when I put the battery in it would start booting. Had to make sure volume down, home and power were pressed while sliding the battery in. It's tricky but you can do it with one hand and use the other to insert the battery. Don't give up just because if you put the battery in your phone automatically boots!
I used this specific file. http://rwilco12.com/Files/Devices/S...Unrooted/SPH-L900_MA5_853599_Stock_Nodata.exe
I didn't know if my phone was MA5 or MA7. I was worried that something would be off if I downloaded the wrong one but I chose MA5 oneclick exe and it did the trick. I used the Rooted version that didn't delete my data so when the phone came back on all my changes were still there. Everything from the kernel was gone but my settings and etc were unaffected.
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
So anyways, there are some resources and an additional thread. I'm pretty tech savvy but when the damn thing bricked I wasn't for sure what to do. Hopefully this is semi helpful for someone.
*Cliff Notes:
If you brick yourself out of your Sprint Samsung Galaxy Note 2 (II) and you can't access recovery, go download one of these oneclick solutions from sextape or garwynn (big ups to you guys) and reflash it from download mode using their programs. If you rooted your phone using Odin you will feel right at home with their software and it is no big deal. Phone will be back up in no time.
Edit: So after I got back to my stock ROM and tried to reflash my previous roms they wouldn't stick. E Signature verification kept failing but I still had root. Used CWM Recovery straight out of the app store and rebooted in recovery. Wiped everything. Used the esignature toggle and disabled it. Bam was able to reinstall roms and I am back to tinkering
The title was misleading. I thought you meant a hard brick. What you encountered was a soft brick aka bootloop. Thanks for writing it up for the noobs though.
Sent from my SPH-L900 using Tapatalk 4
Yes title is misleading but great post for us thats need it
Thank u much for ur time to make this
SGN2
I bricked my sph l900 also..I had 4.3 rooted then went to jellybomb had a back up of my 4.3 rooted. Flashed back to it and it's now stuck in note 2 animation. Can't get into recovery or adb. Plz can anyone help ?
Sent from my SM-N900P using xda app-developers app
Is there a fix ?
Sent from my SM-N900P using xda app-developers app
odin oneclick failure
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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>
<OSM> All threads completed. (succeed 0 / failed 1)
kevo7000 said:
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to use the original Samsung USB cable.:good:
new battery issue
gizmoscoop said:
You need to use the original Samsung USB cable.:good:
Click to expand...
Click to collapse
I used every cable I owned oven the original cable for my Note 2. I ended up taking it to sprint and replaced it. With this new note I've had two batteries completely fry. 100 % but will not power on without charger.smh
What is it that you did when the onclick kept failing?!!?
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
I keep running the NA5 Stock NoData exe and it keeps failing
OK so I found this on the S2 forums but not anywhere else, so I figured I'll post this here, just in case somebody's ODIN failed.
Credits goes to @Hopper8 for the original thread on the S2 forums. Thank him there!
This guide is provided for information only. I will not be held responsible if you cause any damage, software or hardware, to your phone by following the guide. You are choosing to follow this guide, and as such, you choose to accept any responsibility for any mishap that may occur.
WARNING: Do not follow this guide if you think (or even suspect) that your USB port may be faulty in any way (ie, slow charging, loose connection among other faults). If your USB port is faulty, it must be fixed before flashing, or you are in danger of hard-bricking your phone. If the connection to the computer fails even for a moment, at best the flash will fail, and at worst the phone will need a new motherboard.
WARNING #2: If at all possible, make sure you have a backup of your efs. Efs is the folder which contains your imei. No imei =no signal. Flashing a ROM may corrupt the efs folder, in which case the backup will be invaluable. If you do not have a working backup of your efs folder, I am not responsible if you choose to follow this guide and your efs becomes corrupt.
Symptoms
This guide is for people who find themselves in the situation where:
The phone currently will not boot.
The phone can only enter download mode (If it can’t do that, see the section below.)
If, for whatever reason, an Odin flash fails.
It assumes you know the basics of Odin flashing. If not, see here.
No download mode?
If your phone won’t enter download mode, you can try three things:
A USB jig. Don’t pin your hopes on this, they rarely succeed in this scenario.
‘Jump starting’ – You might need someone else to give you a hand for this. Take the battery out of your phone and wait 30 seconds. Now, press the button combination to enter download mode, and with this combination still depressed, get someone to put the battery back in. Hopefully this will jolt your phone into download mode.
Take out the phone battery, and re-insert it, but don’t turn the phone on. Now, plug in the charger while holding the volume down button. Keep holding volume down till you enter download mode.
If your phone won’t enter download mode, and will do nothing but get hot when you attempt to do anything to it (charge it, turn it on), then your motherboard is in need of replacement.
Your options
I’ve seen a lot of people, when their Odin flash fails, either:
Give up. Not a good option.
Flash a .pit file. That should be used as an absolute last resort. There’s a lot to try before getting to that stage! If a flash of a .pit file fails in Odin, your phone is well and truly unrecoverable, and you will need a motherboard (MB) replacement.
Send their phone to a service centre. That costs money (& you’re without a phone for a week or so).
Read on and hopefully you will be able to recover your phone without spending anything.
What to do
Keep flashing via Odin. You don't really have a choice. As for the files to flash: It’s worth trying to flash a range of stock ROM’s and custom kernels. I recommend downloading a stock firmware from SamMobile for your device. I recommend 4.1.2 Jellybean since it doesn't contain Knox. But if u prefer 4.3 or 4.4 Kitkat, go ahead. See here for the stock ROM’s.
As for custom kernels: If you manage to flash a custom kernel onto your phone, that means you probably have a custom recovery, from which you can either restore a nandroid backup, or flash a custom ROM. Even still:
Your best bet is to continue to attempt to flash Stock ROMs for your model variant and region.
Now that you have chosen a file to flash, continue on.
If Odin won't recognise the phone ...if it does, continue to 'Preliminary Steps'
Firstly, keep trying. Many users will find that Odin will recognise the phone in download mode eventually, but this will take perseverance. Note that if you do get Odin to recognise your phone in download mode, attempt to flash a stock ROM then. Don't unplug it thinking 'you'll try again later'.
Things to try if the phone isn't recognised by Odin:
Open Odin without the phone plugged in. Enter Download mode without the phone plugged in. Now, plug the phone in and wait a few seconds.
Didn't work? Try again in a different USB port. Still didn't work? Try all the USB ports, and then a different computer. If that doesn't work:
Uninstall the USB drivers using Revo Uninstaller. This program can remove the registry edits from the drivers, giving you a completely clean install of the drivers. Reinstall the USB drivers: Latest version here. If you are using Windows 8, I strongly recommend you try Windows 7/XP. These drivers don’t usually work with Windows 8. (See here if you’re on Windows 8.) Otherwise, use the linked file to the Samsung USB drivers.
If you're still not having any luck, then follow these steps: (Credits to 4-2ndtwin)
1. Turn off both the computer and phone. Fully shut down.
2. Disconnect phone from computer: the USB cable from both the computer and phone.
3. Boot up the computer. Log in and let it settle.
4. Start up Odin and let it settle.
5. Put phone in download mode.
6. Connect phone to a USB port.
If that doesn't work, keep repeating those steps, with different USB ports on your PC/laptop. Change the USB cable you're using, multiple times (preferably use the cable that came with the phone) (I've found that the cable that came with the phone isn't very durable. If possible, use a new cable.) If all that doesn't work, start again at 'If Odin won't recognise the phone' on a different computer. Keep persevering
Now assuming you can get your phone into download mode, and is recognised by Odin:
Preliminary steps
Odin failing a flash usually isn’t a failure of the software itself. It’s usually to do with the way the flash is set up. Before we get on to the troubleshooting steps: you must always- i.e. every flash:
Run Odin as an administrator in Windows (only for Windows 7. This doesn’t apply for Windows XP). Yes, Odin is Windows only. If you use Linux/a Mac, you’ll need to use someone else’s Windows computer.
Ensure Kies is installed on your computer but you must kill all Kies running services in the Windows task manager. Most people have 4 running continuously. I personally only have 2, so don’t stress if you can’t find 4 to kill.
Make sure you're not using a USB hub of any description.
If you haven’t done those steps on your previous Odin flash, it’s worth flashing again making sure you do those three things. Still didn’t work?
Troubleshooting steps
Things to do:
Change the USB cable you’re using. Preferably, use the original cable that came with the phone. If you’re already using the original cable, change to another, genuine, Note 2 cable. Try at least 3 different cables.
Try different USB ports on your computer. You have to be using a mainboard (powered) port. Try as many of those as you have on your computer.
Use different versions of Odin. Try them all, but particularly 1.3, 1.85, 3.04 and 3.07. Make sure to extract the Odin files before using them. (Go to the original thread to download, I can't upload files from the XDA app)
Reinstall the Samsung USB drivers. If you are using Windows 8, I strongly recommend you try Windows 7/XP. These drivers don’t usually work with Windows 8. (See here if you’re on Windows 8.) Otherwise, use the linked file.
Turn off all antivirus/antimalware/antispyware/firewalls. I advise downloading all files you need before doing this step so you’re not without antivirus whilst downloading files. I’m not responsible if you do manage to get a computer virus during this time.
Check the rom/kernel you download, making sure it’s not a corrupted file. The best way to do this is to check the MD5 sum using md5summer. If you don’t have the MD5 sum, then you can use WinRar, 7Zip, or IZarc to test the file. If any tests (MD5 or the 7Zip test) fail, then you need to re-download the file. Test the new file before using it.
Run Windows update on the computer you’re using.
What now?
Ok, so if you’ve got to the bottom of the list, but you’re still having failed flashes:
Use a different computer. Now, run through the list again. Yes, the whole list. Try everything all over again on the new computer. Didn’t work? Try again on one more computer. Keep persevering, the feeling you’ll get when your Note 2 is back to life will be worth it
Last Resort
What if… Ok, so you genuinely can’t get anything to work. This really is a last resort. It’ll be either up to you to choose whether:
You research the flashing of .pit files. Note that your phone will be stuffed if it fails. Full stop. Motherboard replacement. Ask yourself “if Odin won’t flash a ROM without failing, why will it flash a .pit successfully?"
You take your phone to a service centre.
Many thanks to keithross39 for proofreading & editing this guide (On the original S2 thread.)
Credits:
MistahBungle, on whose posts these troubleshooting steps are based.
keithross39, for his guide on replacing the USB port.
Intratech, for his guides on the basics of Odin flashing & stock ROM collection.
4-2ndtwin, for his troubleshooting steps if Odin won't recognise the phone.
SamHaLeKe, for the updated Samsung USB drivers.
daerragh, for the Windows 8 drivers.
N7105 stock pit file here.
N7105 flashable zip for repartitioning here.
N7100 flashable zip for repartitioning here.
HOPE THIS HELPS
P.S. this is why I never use ODIN. Data runs through a cable, which might disconnect any moment. My tip, get a custom recovery using ROM Toolbox or something, and flash your ROM/Kernel from there. Only use ODIN for stock ROMs.
P.S. Again, thank the original thread author, don't thank me!
Hi
Please check that all information is correct for your phone. I used information snippets from over 25 XDA threads, and they may be pertinent to an S2. For example, are all those Odin versions compatible with a Note 2 and the associated firmware? I don't know, but you need to know. (You also didn't attach the zip file of Odin files that I did).
It may also be helpful to link my original post so people can continue reading the thread, it may be helpful to someone to read past the first post. (i.e., credits to Hopper8 for his >original post<)
Hopper8 said:
Hi
Please check that all information is correct for your phone. I used information snippets from over 25 XDA threads, and they may be pertinent to an S2. For example, are all those Odin versions compatible with a Note 2 and the associated firmware? I don't know, but you need to know. (You also didn't attach the zip file of Odin files that I did).
It may also be helpful to link my original post so people can continue reading the thread, it may be helpful to someone to read past the first post. (i.e., credits to Hopper8 for his >original post<)
Click to expand...
Click to collapse
Can't upload files with xda app. I'll check everything to make sure it works with the Note 2. Thanks for the tip
N7105 rocking AOSB with AGNi kernel,
Sent from the "China who bans Google"
Click "Thanks" if I was of any help!
@Irwenzhao
Lovely guide for troubleshooting. Really appreciated.
By the way I have a question.
As you know I have re-partitoned my phone.
So what if I want to return to stock rom and I flash with pit on odin and odin fails?
Then I would need a motherboard replacement? [emoji33]
Sent from my N7100 using Tapatalk
smeet.somaiya said:
@Irwenzhao
Lovely guide for troubleshooting. Really appreciated.
By the way I have a question.
As you know I have re-partitoned my phone.
So what if I want to return to stock rom and I flash with pit on odin and odin fails?
Then I would need a motherboard replacement? [emoji33]
Sent from my N7100 using
Click to expand...
Click to collapse
Yep. u fail a pit file flash, your device's gone. That's why I recommend using a recovery flashable file to repartition, it's safer.
P.S. don't thank me, thank Hopper8 in his original thread for making this guide.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Irwenzhao said:
Yep. u fail a pit file flash, your device's gone. That's why I recommend using a recovery flashable file to repartition, it's safer.
P.S. don't thank me, thank Hopper8 in his original thread for making this guide.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
Okay. So better I make a zip to revert to stock partitions too. Would be safer then.
Sent from my N7100 using Tapatalk
---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------
But I know 1user whose odin flashes were failing even with the pit. But he was able to recover his phone by flashing a factory firmware.
@tnt4ever just want to confirm with you did your odin fail even with the pit file? A few days ago when you made the mistake of downgrading to MJ5?
Sent from my N7100 using Tapatalk
smeet.somaiya said:
Okay. So better I make a zip to revert to stock partitions too. Would be safer then.
Sent from my N7100 using Tapatalk
---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------
But I know 1user whose odin flashes were failing even with the pit. But he was able to recover his phone by flashing a factory firmware.
@tnt4ever just want to confirm with you did your odin fail even with the pit file? A few days ago when you made the mistake of downgrading to MJ5?
Sent from my N7100 using Tapatalk
Click to expand...
Click to collapse
Read his experience
smeet.somaiya said:
Okay. So better I make a zip to revert to stock partitions too. Would be safer then.
Sent from my N7100 using Tapatalk
---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------
But I know 1user whose odin flashes were failing even with the pit. But he was able to recover his phone by flashing a factory firmware.
@tnt4ever just want to confirm with you did your odin fail even with the pit file? A few days ago when you made the mistake of downgrading to MJ5?
Sent from my N7100 using Tapatalk
Click to expand...
Click to collapse
I think that's cause stock firmware flashes a .pit file too.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Irwenzhao said:
I think that's cause stock firmware flashes a .pit file too.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
Nope. It doesn't. But, I read the thread which @singhpratik87 had linked up in his post here.
I found that there is one in a thousand chance of pit to fail. It's a small file takes hardly miliseconds to flash. Unless your connection fails the pit won't fail.
Sent from my N7100 using Tapatalk
smeet.somaiya said:
Nope. It doesn't. But, I read the thread which @singhpratik87 had linked up in his post here.
I found that there is one in a thousand chance of pit to fail. It's a small file takes hardly miliseconds to flash. Unless your connection fails the pit won't fail.
Sent from my N7100 using Tapatalk
Click to expand...
Click to collapse
And this is why I dislike ODIN, unstable connections.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Irwenzhao said:
What to do
Keep flashing via Odin. You don't really have a choice. As for the files to flash: It’s worth trying to flash a range of stock ROM’s and custom kernels. I recommend downloading a stock firmware from SamMobile for your device. I recommend 4.1.2 Jellybean since it doesn't contain Knox. But if u prefer 4.3 or 4.4 Kitkat, go ahead. See here for the stock ROM’s.
Click to expand...
Click to collapse
I have an unbranded GT-N7100 and on the Sammobile site I don't know which firmware country to select. I am in US, I got the phone off ebay, stuck at the second boot screen-flashing samsung or is it ok to use this rom here? i.e. [ROM][STOCk][JB][4.1.2]JZO54K.N7000DXLSE-OLB[25-04-2013]
hi i just want to ask and not start a new thread thogh, can i flash a stock rom from sammobile / live.samsung... and flash it with odin. i know the knox part, i have already tripped it though.
or will it be useless when i flash a custom rom over it with twrp/ cwm/ philz?
Hi,
my N7100 have a stroke and now stuck in boot screen, trying to flash the phone with stock firmware download from Sammobile (N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_HOME.tar), Odin v3.07 and v3.09 but failed.
Odin log as below
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
please help
thongkh said:
Hi,
my N7100 have a stroke and now stuck in boot screen, trying to flash the phone with stock firmware download from Sammobile (N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_HOME.tar), Odin v3.07 and v3.09 but failed.
Odin log as below
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
please help
Click to expand...
Click to collapse
Hello,
Same for me. Please help : http://forum.xda-developers.com/gal...samsung-screen-failed-to-mount-t2965275/page2
Side54723 said:
Hello,
Same for me. Please help : http://forum.xda-developers.com/gal...samsung-screen-failed-to-mount-t2965275/page2
Click to expand...
Click to collapse
Seem like you having the same problem like me, i have not tried CWM yet, will try soon hope mine can be fixed with CWM
UPDATE 16Dec2014
tried to flash PhilZ Touch 6 Recovery, but failed. :crying:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help :silly:
jayinc11 said:
I have an unbranded GT-N7100 and on the Sammobile site I don't know which firmware country to select. I am in US, I got the phone off ebay, stuck at the second boot screen-flashing samsung or is it ok to use this rom here? i.e. [ROM][STOCk][JB][4.1.2]JZO54K.N7000DXLSE-OLB[25-04-2013]
Click to expand...
Click to collapse
That's for the Samsung Galaxy Note (1).
I have a stock Galaxy S3 from T-mobile SGH-T999.A few days ago the phone began to randomly turn off. Yesterday when I went to restart the phone it got stuck in a boot loop. It will display the Samsung logo then keep trying to reboot until I pull the battery. The power button is not stuck. I have tried removing the battery, micro sd card & sim card. When I try to go into recovery mode I get KERNEL PANIC UPLOAD MODE on the screen. I can get into download mode. I believe my firmware is either 4.1.1 or 4.1.2. I tried several versions of Odin and flashing 3 versions of the firmware 4.1.1, 4.1.2 & 4.3 Each time I get a fail message from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Write)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Thank you!
If you put the battery in and it tries to boot up on its own, is almost definitely the power button.
Aside from that, if you have kies installed on your computer, uninstall it. It interferes with odin and prevents it from flashing.
DocHoliday77 said:
If you put the battery in and it tries to boot up on its own, is almost definitely the power button.
Aside from that, if you have kies installed on your computer, uninstall it. It interferes with odin and prevents it from flashing.
Click to expand...
Click to collapse
Thanks for the reply. The phone does not try to restart when I put the battery in. I uninstalled Kies but no luck. I have tried on a Windows 7 computer and a Windows XP computer too. Could the pit file be corrupt? Any real way to tell if it's hardware or software related?
You can try to flash with re-partition checked. I dont think youd need a pit file since Odin sees and looks like it can use the one already on your device. You can use the .pit file if you like. Shouldnt hurt anything to try. If that doesnt help it take, it may be a hw problem after all. Its hard to be certain though...
DocHoliday77 said:
You can try to flash with re-partition checked. I dont think youd need a pit file since Odin sees and looks like it can use the one already on your device. You can use the .pit file if you like. Shouldnt hurt anything to try. If that doesnt help it take, it may be a hw problem after all. Its hard to be certain though...
Click to expand...
Click to collapse
Still no luck.
Would the error message on the recovery screen help? This is what i see when I try to boot into recovery mode.
I get the android dude in the middle of the screen with the message KERNEL PANIC UPLOAD MODE
At the top of the screen it reads:
Kernel Panic!
KRAIT INFO
Panic caller: ext4_handle_error+0x8c/0x98
Panic msg: EXT4-fs (device mmcblk0p14): panic forced after err
Thread: e2fsck:116
Wait...
Done!
Ive never seen that before tbh, and this is just a guess, but judging by the Panic caller and Panic msg the filesystem is corrupted. I would think the re-partitioning would have solved that though. (Did you try both with and without the actual PIT file?)
And just in case you didn't already know, mmcblk0p14 is the system partition. (Where the OS is located)
If you are still under warranty you may not want to try this, but see if you can just flash TWRP recovery from Odin. If you can, we can attempt to format the partition manually. I dont have high hopes that it would work since Odin should do this anyway, but it may be worth a shot.
If you are still under warranty though, you should probably try to get a replacement that way.
Also, and this is a long shot, you could try different versions of Odin. You can find them through the link in my sig. Try 3.07, 3.09 and 1.85. Probably wont make a difference, but you never know.
There is a high possibility you are dealing with a hardware failure though. If that is the case theres really not much we will be able to do. Lets hope for a little luck!
DocHoliday77 said:
Ive never seen that before tbh, and this is just a guess, but judging by the Panic caller and Panic msg the filesystem is corrupted. I would think the re-partitioning would have solved that though. (Did you try both with and without the actual PIT file?)
And just in case you didn't already know, mmcblk0p14 is the system partition. (Where the OS is located)
If you are still under warranty you may not want to try this, but see if you can just flash TWRP recovery from Odin. If you can, we can attempt to format the partition manually. I dont have high hopes that it would work since Odin should do this anyway, but it may be worth a shot.
If you are still under warranty though, you should probably try to get a replacement that way.
Also, and this is a long shot, you could try different versions of Odin. You can find them through the link in my sig. Try 3.07, 3.09 and 1.85. Probably wont make a difference, but you never know.
There is a high possibility you are dealing with a hardware failure though. If that is the case theres really not much we will be able to do. Lets hope for a little luck!
Click to expand...
Click to collapse
The phone is out of warranty, it's almost 2 years old. I have tried several versions of Odin, different computers, different USB cables. I did try both ways, with and without the actual PIT file.
How do I flash TWRP recovery? Could you provide instructions as I'm a newbie at this!
Thank you for your time and effort helping me!
Download the recovery from the link in my sig. (The .tar or .tar.md5) then flash with Odin exactly as you would with the firmware.
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
If that works you can then use the built in file manager to backup any important files to your external sd card if you still need to do this.
You will also want to download a stock based rom and put that on the external sd card.
DocHoliday77 said:
Download the recovery from the link in my sig. (The .tar or .tar.md5) then flash with Odin exactly as you would with the firmware.
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
If that works you can then use the built in file manager to backup any important files to your external sd card if you still need to do this.
You will also want to download a stock based rom and put that on the external sd card.
Click to expand...
Click to collapse
Thanks Doc, which recovery file do you recommend I use?
Its personal preference really. I prefer TWRP, but theres nothing wrong with CWM. Use the latest.
so, i decided to flash back to 5.1.1 but i have unfortunately was not be able to pull this move from some weird error.
After many attempts here's what I've done.
I used the Flashable Tar for 6.0.1 MM and after awhile for my experience i went and tried to flash back to OL1 5.1.1 the latest rev and now i was stuck with Odins "Set Partition" or "BootLoader" wont flash or format nothing phase,
After i rebooted the phone, i noticed i could still access TWRP and Download mode and left with nothing to flash but going to TWRP and charge my phone....
In Twrp i was left with its "Unable to mount" and "Invalid arguement" issues after each little label for trying to mount and everything from the log, i've tried zip from a OTG and that didn't work even sideloading wouldn't help. I was left with nothing and it kept confusing.
My drivers were up to day, i tried a different Odin 10.7 and even tried Kies but that didn't even work so.
I made another attempt with Odin one more time and i was left with this log.
for flashing the 5.1.1 again G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.md5
it goes to
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
It would hang from this point doing nothing, and sometimes even after words it would say "Set Partition" or "Bootloader" in bold, and when i reset the phone to go back into "TWRP" it sends me this response.
<ID:0/010> __XmitData_Write
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
I'm ultimately stumped,
So earlier which took about 1-2 hours to finally figure this out, i've tried wiping data,cache and etc or anything for that matter, and then I received a slew of "Failed to mount '/data' (Invalid argument)" and "Unable to mount storage" when trying to flash anything. Surprisingly enough, my internal memory shows up as 0mb aswell, then i went to "Wipe" - "Format Data"- "Yes" and it formatted with it's function and i rebooted back into Twrp it reads its original storage but i'm still left with no way to boot up completely.
sometime after i've tried flashing the 6.0.1 tar and i recieved this
6.0.1\ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar.md5
<ID:0/010> Removed!!
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
hangs again, left with "Set Partition" and i restart the phone
<ID:0/010> __XmitData_Write
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
I have googled around XDA and around the general web, and I see a lot flashing for PIT or extracting the tar to make odin read it and attempt to flash it 1by1 but im not sure how to entirely do that I'd like this to be as easy as possible since i only have very little knowledge for Attempts to solve this.
I am not sure where to find the other files, let alone Bootloader for the MM stock flashable 6.0.1 or the 5.1.1 latest rev, I have the stock tar but not the rest.
I am genuinely asking for help, with someone that has maybe had this issue, or what can be done to solve it.
Any help would be vastly appreciated.
so, i've tried multple tars and nothing has worked for me it is always stuck that one file sboot.bin i've tried the OL1 5.1.1 and 6.0.1 stock tar it just isnt cutting it, BUT what i've notcied is that i was able to flash the Renegade rom in TWRP via OTG and it worked, iwas able to access the phone like usual and everything was written just fine but im still lost as to why it wont flash that sboot.bin file. i practically cant reset or reformat my phone.
How bout restarting the computer, Maybe a differnt one. How many times have you flashed that phone? Maybe this might start happening to others time will tell. personally i dont like odin I only use it only when needed to reset update firmware or recovery update. Its not often. Is your cable wore out hey at least you got the renegade rom and can flash something.
You know you can't downgrade right? Once you update you can't go back.
Saafir said:
That is not entirely true. And you can always JTAG back even, lol.
Click to expand...
Click to collapse
Yes. Regardless, your going to break something if you flash different bootloaders.
how would i be able to do that? i've tried different cables and im now trying the different odin and twrp im scared it will just keep saying sboot.bin forever i mean it was just a simple flash mm6.0.1 tar from the threads not the official one :/ and then downgradin didnt let me is there a way i can log that?
provided any links? or bootloader files?
I was able to flash back to 5.1.1 via offical TAR with no bricking, many people have done the same, granted, usually this isnt possible, but has worked for me many times now on customer devices as well as once on my own, just to test it lol.
can u send me your tar file? by chance?
anderd said:
I was able to flash back to 5.1.1 via offical TAR with no bricking, many people have done the same, granted, usually this isnt possible, but has worked for me many times now on customer devices as well as once on my own, just to test it lol.
Click to expand...
Click to collapse
could you send methe tar file by chance?
IAmTechFreq said:
could you send methe tar file by chance?
Click to expand...
Click to collapse
Here. I did the downgrade 6.0.1 to 5.1.1 too with no problem.
http://www.sammobile.com/firmwares/download/60059/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR/
So for right now I'm still unable to flash the Tars still. Even with the same and different tar I downloaded. I've tried different cables, computers, I just i don't seem to figure this out.... What do I do? Is there a way to capture an Odin log or even on my phone??
The xmit data writ happens after I restart my phone because it just hangs or freezes on the sboot.bin file or item..... Is there a way to flash it seperately??? I'm still some how running the 6.0.1 renegade custom rom tho and everything else is fine
Evidence
Pics of evidence
Try this one.
https://www.androidfilehost.com/?fid=24345424848486725
I recommend getting a pit file and flashing it. You seem to be having partition issues as noted by the TWRP error logs when it tries to mount things.
I made one awhile ago, it's for the 32GB variant if that's what you have try and Google search for it. Don't ask me for it because I'll have to Google search too but don't have the time right this second.
Sent from my SM-G920P using Tapatalk
elesbb said:
I recommend getting a pit file and flashing it. You seem to be having partition issues as noted by the TWRP error logs when it tries to mount things.
I made one awhile ago, it's for the 32GB variant if that's what you have try and Google search for it. Don't ask me for it because I'll have to Google search too but don't have the time right this second.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
If you have the 32GB variant, here is a PIT file I made awhile back that has helped and worked for others.
http://forum.xda-developers.com/attachment.php?attachmentid=3582475&d=1450575695
Sorry for such late replyss, and yes i have the 32Gb version, and it just says or i've been seeing that appears in Odin as well, the "Set Partition" or "Bootloader" i wil ltry out that PIT file and see if it works and etc and will keep you updated.
elesbb said:
If you have the 32GB variant, here is a PIT file I made awhile back that has helped and worked for others.
http://forum.xda-developers.com/attachment.php?attachmentid=3582475&d=1450575695
Click to expand...
Click to collapse
@elesbb, do you want me to put this up on my Android File Host account, so it doesn't get lost? PM me if you do.
thank you so much~ @elesbb This actually flashed completely trhoguh and it worked for me c: i just i was so just , i can't believe it worked i couldnt thank you enough c: seriously saved my life lol
Well problem solved always glad to follow along figure out what worked. I have the same phone lol.
The PIT File flash fixed it then well good to know. Good luck to you on you way.
IAmTechFreq said:
thank you so much~ @elesbb This actually flashed completely trhoguh and it worked for me c: i just i was so just , i can't believe it worked i couldnt thank you enough c: seriously saved my life lol
Click to expand...
Click to collapse
So you flashed the PIT file then flashed Stock TAR and it all worked?
Saafir said:
So what did we learn from this? Always make a nandroid?
Click to expand...
Click to collapse
Nandroid can't restore partition information. Only PIT can lol.