Related
Ok, so apparently I wrote a huge post and it disappeared because I got logged off.
I posted another long version here.
In short my phone froze while updating and connected to my pc. Pulled everything and now it keeps rebooting. Probably storage related (see link above). No change I made stays after a reboot, app uninstall, file deletion (through root explorer or windows). And here is the thing, I can flash whatever, but it won't do anything.
I tried manual flashing the stock image, it does its thing and then reboots in the same situation.
I tried flashing the individual images using this guide, didn't work.
I tried flashing the stock image using the Galaxy Nexus Toolbox, once again, nothing.
I tried ODIN using:
This guide
And this guide
I even tried creating my own odin file using this guide and one using this guide.
Odin will do stuff for about 25 to 30 minutes. It will then reboot the phone with no changes made. At this point odin will have a square saying RESET!. So after rebooting I check if it will still freeze and reboot by going to settings -> apps. It will freeze and reboot. Pull battery, go into download mode, odin will do some stuff and claim it passed by saying PASS!.
These are the messages posted by odin:
HTML:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ODIN_JRO03C.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
I don't know what to do anymore. Besides get some sleep. Tomorrow I will see if I can get odin to dump some logfiles or something.
Uh, what you said is kinda impossible...
Linux permissions revolve around a 0-1000 scale. Root being 0, and no access being 1000.
Odin uses root privilages, and so does CWM/TWRP.
Anyways, I'd just replace the phone.
You most likely corrupted your internal storage, which is near impossible to fix.
Or you screwed up multiple partitions in just the right way where it'll work, but it wont either.
Sent from my Galaxy Nexus using xda app-developers app
rsjc741 said:
Uh, what you said is kinda impossible...
Linux permissions revolve around a 0-1000 scale. Root being 0, and no access being 1000.
Odin uses root privilages, and so does CWM/TWRP.
Anyways, I'd just replace the phone.
You most likely corrupted your internal storage, which is near impossible to fix.
Or you screwed up multiple partitions in just the right way where it'll work, but it wont either.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What is impossible? That nothing seems to work? Because it sure as hell isn't working.
I did find a way to get zip files on my phone using the toolbox, but flashing cm9.1 didn't work.
I do indeed think my memory is corrupted.
No it is not corrupted. I don't think. I think the permission has been messed up... when you're flashing a Rom, does it give you an error, or does it flash successfully? If successfully, the permission is messed up and you need to figure out how to change the permission using adb, which can be used when in recovery mode. Sadly, I don't know much about permission changing, do this is as far as I could help
Good luck, and I hope you fix your phone
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
kyokeun1234 said:
No it is not corrupted. I don't think. I think the permission has been messed up... when you're flashing a Rom, does it give you an error, or does it flash successfully? If successfully, the permission is messed up and you need to figure out how to change the permission using adb, which can be used when in recovery mode. Sadly, I don't know much about permission changing, do this is as far as I could help
Good luck, and I hope you fix your phone
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
I just tried flashing through cwm again using the temporarily boot from the toolkit. It says:
HTML:
Installing /sdcard/[...].zip
finding update package
opening update package
installing update
fixing fs_size in crypto footer
install from sdcard complete.
And it installed in maybe five seconds.
The crypto thingy has me worried, it's not normal, is it?
Also, I just tried creating a backup with cwm and it said there was an error making a back up image of /system.
One last bump.
Well, I hate to say it, but I think it's a hardware issue. I've seen a few others with the same issue: flashing images seems to work successfully, but they actually didn't flash.
So, just to confirm, you tried flashing the images individually in fastboot and it says "OK" after each one, but nothing ends up being flashed. Is that correct?
efrant said:
Well, I hate to say it, but I think it's a hardware issue. I've seen a few others with the same issue: flashing images seems to work successfully, but they actually didn't flash.
So, just to confirm, you tried flashing the images individually in fastboot and it says "OK" after each one, but nothing ends up being flashed. Is that correct?
Click to expand...
Click to collapse
I was afraid this would be the case. Still weird though how it happened while it was sitting on my desk while connected throught usb.
Anyway, I will be returning it tomorrow.
I could really use some help. Quick story, I was at a wedding today and I pulled my phone out of my pocket only to see the Google logo (I'm unlocked). I thought that was odd, but figured maybe it was a random reboot. Happens, right? But it never actually rebooted. I left it on that screen for maybe half an hour. Then I pulled the batter thinking my latest ROM was acting up so I would just flash back to my last nandroid. Only after pressing Vol+;Vol-;Power I got... nothing. Blank screen. Later, I could see that the LCD was actually powered up (I could see a faint light) on the Fastboot screen but nothing was actually showing. I could, however, use Vol-;Power and see the Odin Mode screen. But if I choose "Start" I go back to the Google logo and then it never boots. Crazy! I pulled the battery and just stuffed it back in my pocket until I could get home and try out ADB. :fingers-crossed:
So I got home, plugged it in and booted it up. No matter what mode I try it won't show up in ADB. I tried the Google screen, I tried the blank screen after the vol+-power and tried the Oden Mode that I could see. None of them will let me use Fastboot or any ADB commands.
I've been searching for over an hour now and haven't found a solution. So, I'm asking now. I'm not a super-user but I'm no n00b for sure. I just don't know what to do now. I can't flash a factory image because I can't get the device to show up in ADB and fastboot. What could I be missing?
Thanks for reading my story. I hope it gives you enough info for ideas on how to help. Some final info:
Model: Toroplus rooted and unlocked
ROM: Last CM Nightly (11/16/12)
Recovery: ClockworkMod 6.0.1.5
I'm seeing three screens. Google, What I think is supposed to be Fastboot and the Odin Mode. Not 100% sure on the terms there, sorry.
I took the battery out all night to let it deep reset. Still nothing. Just sits at the Google screen indefinitely.
What am I missing?
Sent from my Nexus 7 using Tapatalk 2
Had the same thing happen to me. Thought it was the battery, so I tried a different one. No go. Luckily, being unlocked and running different roms, was able to get to recovery, and since I always keep a nandroid of my current rom, I was able to flash it and all is good now.
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
But yours won't go to recovery? That's weird man, don't know what to tell ya.
That's the tough part. If I could just get to recovery I could fix this with no problems. But I can't seem to get it to load up. I'm wondering if there something that can be done from that Odin Mode screen where I can see it says "Download. Do not turn off target." ?
Update:
OK, I guess you can never search enough. I found shabby's guide and realized it might help. I'll try this and see if it will read the device. Wish me luck....
http://forum.xda-developers.com/showthread.php?t=1620036
Good luck, let us know how it goes.
Well, Odin Mode is allowing a connection, and it seems to be writing to the phone (that seems like good news!) BUT it keeps stalling while flashing the radio-cdma image file. I've tried it about 6 times now on two different computers and two different USB cables (one of which is the stock cable) and it won't go past this point. I'm encrouaged that the Odin software (using Odin3 v.1.87) can see it and flash the first images. This is what I'm seeing:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9250XXSPH-L700FH05.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img
<ID:0/004> userdata.img
<ID:0/004> boot.img
<ID:0/004> radio-cdma.img
I can't seem to find another TAR to try though. Shabbypenguin's is the only one I can find. Is it possible to flash the seperate IMGs from the stock FH05 via Google in Odin? I can't seem to find a how-to on that. They all say to flash it in Fastboot, which I can't access.
UPDATE:
Odin would't flash any TARs with the radio-cdma.img in them. I built a new one using MSkips Toolkit and left out the cdma radio, which Odin took and flashed. But no progress on the problem. I think my CDMA radio might be fried? Does this match anyone else's experience with this?
Last report: Took the device to Sprint repair store. Absolutely couldn't fix it so having it replaced. Consider this topic closed.
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!
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!
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).