Okay, I've read threads and followed the wiki. No matter what, ODIN fails at recovery.bin when I try to downgrade. Here's what I've done so far:
1. Attempted to use all versions of ODIN (1, 1.3, 1.61, 1.7).
2. Attempted to flash with tar.md5 in the phone section. Reboot when hung on factoryfs.rfs. Failed when putting everything back to PDA.
3. Removed SD Card
4. Different cables, different slots.
I am using these files:
PIT: \s1_odin_20100512.pit
TAR: \SPH-D700-DI18-8Gb-REL.tar.md5
This is ODIN's output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DI18-8Gb-REL.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> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> boot.bin
<ID:0/004> recovery.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do here...or have I got a true brick?
Thanks!
I don't think you havea true brick cuz atleast itspicked up by odin...
Did you take the .md5 out of the file name?
Sent from my SPH-D700 using XDA App
jwbryan said:
Okay, I've read threads and followed the wiki. No matter what, ODIN fails at recovery.bin when I try to downgrade. Here's what I've done so far:
1. Attempted to use all versions of ODIN (1, 1.3, 1.61, 1.7).
2. Attempted to flash with tar.md5 in the phone section. Reboot when hung on factoryfs.rfs. Failed when putting everything back to PDA.
3. Removed SD Card
4. Different cables, different slots.
I am using these files:
PIT: \s1_odin_20100512.pit
TAR: \SPH-D700-DI18-8Gb-REL.tar.md5
This is ODIN's output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DI18-8Gb-REL.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> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> boot.bin
<ID:0/004> recovery.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do here...or have I got a true brick?
Thanks!
Click to expand...
Click to collapse
I've always just used the .tar file and never the pit. And also don't forget to uncheck the box that says f reset time.
Yeah, I tried flashing with no PIT and got the same results. I hadn't tried unchecking the f reset time. I re-flashed but it failed at the same place.
Try a different .tar?
Sent from my SPH-D700 using XDA App
http://db.tt/a34ENx0
Sent from my SPH-D700 using XDA App
Gotta be something wrong with that file. Like the other posts said try another tar file
Sent from my Evo Killer!
I'm not sure if the tar file is broken, the md5 checksum passes. But I'll redownload the tar file and post up results later.
Rename the .tar.md5 and get rid of the .md5 so it's just a .tar.. Flash that in PDA, no .pit needed. I had this same issue, too. Renamed the .md5 to .tar and it went smoothly.
It id your cord.... mine did it at first... try to hold the cord at the back of up so the front of it makes a better connection to the board.... don't ask it just worked for me
Sent from my Droid using XDA App
You might need to check the "Re-Partition" check box. I'e gotten similar failures in teh past and pretty much every time I checked that box, the flash succeeded.
Okay, looks like I got it. Here's what I did:
I redownloaded DI18 and DK28. I removed .MD5 from both. Flashed (no PIT) and got the same error.
I downloaded the victory PIT, flashed with either DI18 or DK28 and received the same error.
I downloaded a DK28 Modem.bin, flashed from "Phone", received a pass then a reboot. I still hadn't recovered the device, though.
I then checked "Re-Partition" and Flashed the Victory PIT ONLY. This was successful and rebooted the device. I stopped the boot and put the device back to download mode. I flashed DK28 with no PIT and viola! Device took, rebooted and was back to normal.
Thanks all for the help!
I'm curious what the problem was; seems like it was a corrupted FS and re-partitioning fixed it. Too bad there's not an easy way to troubleshoot that. Wonder if re-partitioning directions should be added to the Wiki?
Again, thanks!
I've attributed it (possibly incorrectly) to the CWM recovery being installed. Every time I've had a flash problem, CWM was installed and re-partitioning it has fixed the flash each time.
Thanks for all the info, I am having the same issue. Lets see if I can get this fixed.
Alain.Alba said:
Any resolution to this issue? I am having the same problem...
Click to expand...
Click to collapse
I was able to resolve, my post from 10 JAN should help. I need to edit the original posting with a solution at some point, I'll try later today.
Either way, here is the relevant part:
I downloaded a DK28 Modem.bin, flashed from "Phone", received a pass then a reboot. I still hadn't recovered the device, though.
I then checked "Re-Partition" and Flashed the Victory PIT ONLY. This was successful and rebooted the device. I stopped the boot and put the device back to download mode. I flashed DK28 with no PIT and viola! Device took, rebooted and was back to normal.
Click to expand...
Click to collapse
So, if you follow that recovery process strictly do this:
1. Flash DK28 Modem.bin using the "Phone" on Odin. <- I don't know how necessary this step is as I've not reproduced the problem since. Really doesn't hurt to do it, but I don't know that its needed. I'd be interested to know if you just did steps 2 and 3 if you were able to recover your device.
2. Put the device back into Download mode. In Odin, check "Re-Partition" and flash a .PIT only (I used the Victory pit). This should reboot the device.
3. Stop the reboot (battery pull at the Samsung screen). In Odin, put the DK28 modem.bin in the "PDA" section and flash. The device should flash, reboot and be recovered.
HTH!
Jason
I jumped the gun on my post, didn't check page two....forgive my newbness. I edited my post after I realized there was a page 2.
BTW, You sir, are a PHONE SAVER! I thank you very much for posting up your fix, there is not much at all about a fix to this issue other than yours.
Phone JUST restarted and seems to be working as normal.
Woot!
You sir are a lifesaver, i did as you said.
1.) I did just the PIT file using victory, checking the repartition and auto boot without putting any PDA file in and got a pass!
2.) I left the PIT file in there, and then added the SPH-D700-EC05-8gb-REL.tar, unchecked repartition and did start again.
Worked flawless!!!!
jwbryan said:
I'm not sure if the tar file is broken, the md5 checksum passes. But I'll redownload the tar file and post up results later.
Click to expand...
Click to collapse
here my man this is my old fathful (well got it from QBking77 or i like to call him obewan) always worked for me good luck persistance is key
well ummmmm wont let me upload hmmmmm
nevermind that was the file i was trying to upload
lack of sleep catching up time for bed (i heard that qbking has a BIG VID planned anyone got any idea what that is about?
Related
OK used Odin to update Epic to EH06. Then used clock work to root. But after rotting epic didn't go into debugging so i used odin to flash back to stock..it work so i followed the same steps but mixed up Tar files and Bricked it...so i flased back to stock and then when flashing to Eb13 phone was removed from odin and Bricked again so now when trying to flash back to stock odin fails at ID:COM...??? HELP please.
jclould1911 said:
OK used Odin to update Epic to EH06. Then used clock work to root. But after rotting epic didn't go into debugging so i used odin to flash back to stock..it work so i followed the same steps but mixed up Tar files and Bricked it...so i flased back to stock and then when flashing to Eb13 phone was removed from odin and Bricked again so now when trying to flash back to stock odin fails at ID:COM...??? HELP please.
Click to expand...
Click to collapse
Sounds like you cable is going bad. Grab another cable from a Blackberry or Palm Pre. And always use the same port that you know works. Also it is best sometimes to Odin with the battery out. When you plug in your cable immediately hold the 1 button and power to put it into download mode with no battery.
OK I tried using Htc cable...Odin still FAILS.
you probably do need to buy a new cord as he says if odin isnt recognizing or is continuing to soft brick then new cord re install drivers for odin
Since it is a COM error it may be the drivers. Heimdall I believe loads it's own drivers so that may work for you. Go to Development and at the top in the stickies check out post 2 of How to fix a semi-bricked Epic.
Sent from my SPH-D700 using XDA App
ok thanks... and heres the odin prob.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EB13-8Gb-REL.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> param.lfs
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and im going to try Heimdall now.
Try downloading a new Odin even if its the same one, and the tar file again
Sent from my SPH-D700 using xda premium
I had problems with different versions of odin and cable combinations. I thought mine was shot too. I finally found a working combination with Odin 1.7 and an aftermarket cable. I've had no problems with this combination on multiple flashes. Don't worry, as long as you can get into Download mode, you are not bricked.
Thanks tried using different combinations of Odin and cables and v1.7 is working but is failing at the end.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EB13-8Gb-REL.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> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> boot.bin
<ID:0/004> recovery.bin
<ID:0/004> zImage
<ID:0/004> factoryfs.rfs
<ID:0/004> datafs.rfs
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help.
It appears you are getting further everytime which is usually an indication of a flaky cable or port. Did you also try it with the battery out?
Sent from my SPH-D700 using XDA App
I also found that it finally worked with the SD card out. I don't know if that's related. It worked first time and every time on 1.7 to flash anything I wanted, but I did have the SD card removed.
The battery out Worked thanks... Does any kno if i can flash Genocide EC05 Kernel 2.0 im running EH17.
jclould1911 said:
The battery out Worked thanks... Does any kno if i can flash Genocide EC05 Kernel 2.0 im running EH17.
Click to expand...
Click to collapse
No. EC05 kernels are not compatible with GB leaks.
Odin fail? Remove battery
kennyglass123 said:
Sounds like you cable is going bad. Grab another cable from a Blackberry or Palm Pre. And always use the same port that you know works. Also it is best sometimes to Odin with the battery out. When you plug in your cable immediately hold the 1 button and power to put it into download mode with no battery.
Click to expand...
Click to collapse
Thank you for this. I was softbricked and tried 3 different computers and four different cables and kept getting fails. It turned out that Odin just didn't want to run until I left the battery out. Back up and running!
please help me someone i had the stock el29 system and tried to root it with this
http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root
but it froze at factoryfs.im so im waited 25 mins then tried doing the odin manually by putting the file in myself then it went all the way to rqt_close then nothing it stuck.
i need to get rooted cause i want this rom but i will take anything now rooted non rooted i just want my phone fixed.
http://forum.xda-developers.com/showthread.php?t=1512419&highlight=fd24
it (auto root) made my phone say "firmware upgrade encountered and issue. please select recovery mode in kies & try again.
my first device. i couldnt connect to odin and computer wouldnt recognize device so i took it to sprint and they gave me a replacement.
i figured it was a bad download or something so i downloaded it again today and it messed this phone up to only this phone connects to pc and is recognized but when i try to upload the rom on the regular odin and not the one click it stuck at rqt_close and im confused as to what to do now. i dont even have to be rooted anymore i just want a rom on this phone i was out of a phone for 5 days for that Rom and its messed me over again.
1st time it stuck at factoryfs.img then i got replacement and it stuck at modem and then i took out battery after it was froze for like 25 mins. please help me!!!
Have you tried a different USB cable and/or computer?
yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me
TamiaSky said:
yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me
Click to expand...
Click to collapse
Can you get into recovery mode?
no i cant get into recovery just that dreadful notice but i can get into download mode, so thats a good thing im guessing.
i get all the way to the end to rqt_close then it says my device has been removed like odin is kicking me out or something. i dont unplug my phone or anything but it gets all the way to the end then says removed then failed
You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?
sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?
sfhub said:
You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?
Click to expand...
Click to collapse
ive tried the auto packages and doing it manually and when i did it manually i made sure tat it was the pda slot and i unchecked the re-partition when it popped up as well then after looking around on the internet still i used one of the 7-zip packages and used the pit file with it and checked re-partition and still nothing. odin gets all the way to the end right after modem and then sticks on rqt_close then says removed now it just did this
<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
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
i really hope you guys can help me. im so serious if i get this fixed ill never try to root this phone again. i dont wanna have to get another replacement phone.
MeWarning said:
sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?
Click to expand...
Click to collapse
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.
Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?
TamiaSky said:
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.
Click to expand...
Click to collapse
Well first if you look in the reference section B in the one you've been trying to Odin(http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root) there's separate tar files for the modem, kernel, and rom. Why don't you try doing each one one at a time to see if anything will succeed.
And if that doesn't work try to Odin one of the leaked stock ICS builds sfhub has also.
This is what happens when I do it manually without the auto package.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
then it freezes
sfhub said:
Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?
Click to expand...
Click to collapse
its the full, and ive never been on ics
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
now i will try the no data and see what happens.
thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.
TamiaSky said:
thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.
Click to expand...
Click to collapse
No problem, just let us know how it goes.
Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery. This will increment your ODIN flash count, but it is better than a phone not working.
sfhub said:
Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery.
Click to expand...
Click to collapse
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?
TamiaSky said:
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?
Click to expand...
Click to collapse
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.
sfhub said:
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.
Click to expand...
Click to collapse
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.
MeWarning said:
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.
Click to expand...
Click to collapse
When you package a modem.bin inside of a .tar.md5 it can flash in both the PDA and Phone slot. It is simpler for the instructions to ask people to always use the PDA slot.
If you flash a modem.bin file itself, then it must go in the Phone slot. If you flash the wrong file in the Phone slot, your phone won't boot. That is why I package things so people always use the PDA slot.
The reason I said "stuck" is because I don't know if it is actually stuck. I am worried because as with my worst fear is bricking my phone. Here is a screenshot of what I am seeing:
(never mind cant post links yet) It looks like this:
(a bunch of stuff)
recover.img
system.img.ext4
then that is where it ends. There is no error message or anything. It would lead me to believe that it is still working. What do I do?
It has not said anything else yet so I dont know what to do. Its been like this for about 10 minutes and not saying anything. I cant imagine it actually taking this long for "system.img.ext4" to get added. Did I do something wrong or what?
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Perseus71 said:
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
Here you go. As far as the version goes I was running the latest version of cyanogenmod. If anyone knows the simplist way to back to stock or even just put another rom on please tell me. I would really just like to gain use of my phone back.
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Perseus71 said:
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Click to expand...
Click to collapse
There is not anything. It just keeps running. I left have left it running since I made this post and still had not moved on. I am a little confused to what you are saying. Could you make it a little more simple or provide links? Thanks.
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Perseus71 said:
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Click to expand...
Click to collapse
Don't know if it helps but I rooted the device around november. I don't remember the version. Due to how long ago it was I remember very little details. I flashed something with odin and thats what I remember. In november I rooted it and put a ROM on it and left it alone till now. So what ever the latest update was in November as what I had. By the way thanks so much for the help. I was really nervous and you are giving me hope. Pardon grammer errors. Typing this on nexus 7 and not use to keyboard
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Perseus71 said:
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Click to expand...
Click to collapse
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
If your talking about the screen I just referred to it says:
odin mode
Product name: SGH-t999
Custom binary download: Yes (1 counts)'
Current binary: Samsung official
Qualcomm secure Secureboot: Enable
Warrenty bit: 0
Bootloader Rp swrev: 1
griffsbrown said:
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
Click to expand...
Click to collapse
My bad, I meant Downloading mode. Its the same thing.
Perseus71 said:
My bad, I meant Downloading mode. Its the same thing.
Click to expand...
Click to collapse
Oh alright I edited my last post with the info so check that
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Perseus71 said:
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Click to expand...
Click to collapse
Alright doing that now. Long download time but I will post back with results later.
griffsbrown said:
Alright doing that now. Long download time but I will post back with results later.
Click to expand...
Click to collapse
Make sure to put the phone in download mode and connecting before launching Odin.
Perseus71 said:
Make sure to put the phone in download mode and connecting before launching Odin.
Click to expand...
Click to collapse
Ok back with results. Download time was a lot shorter then expected. It is the exact same problem as the reason I started this post. It gets to a certain point and just stops loading. That point is "system". The logs I posted already in the thread apply to this as well. When I was first trying it never got further then around 5% but right now with this new method you gave me to try it froze around 40%. Any ideas? Also If its worth mentioning I am using odin3 v1.85
EDIT: For the first time it actually said "fail!". The logs look something like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.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> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(Also if its worth mentioning I switched to Odin3 V3.09 for the sake of seeing if it made a difference
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Perseus71 said:
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Click to expand...
Click to collapse
Froze at the same place. I can post screenshots now so:
http://puu.sh/7I88Y.png
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Perseus71 said:
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Click to expand...
Click to collapse
Ok done. What next?
Try to Flash a custom Recovery via Odin this time. If that goes successful, please flash any custom Rom of your choice via that Custom Rom. I know you are wanting to go back to stock. I need the phone to boot first so I can check something.
I soft bricked my phone somehow, no clue. My phone was fine, battery died with no downloads, or anything running, went to turn it back on after plugging it in to find it bricked at the Samsung start screen.
I've tried restoring it with Kies, which won't recognize my phone is plugged in(??).
I've tried restoring it in Odin with Kies uninstalled, it keeps failing though.
Here's a copy of Odin's log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T889UVBMD1_T889TMBBMD1_935627_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> sboot.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My Note 2 has never been rooted, and I'm completely at a loss as to what has happened. I've tried different USB cords and slots around my laptop, but don't have another computer I can try it on currently.
Also, After trying Kies and Odin I noticed in the top left corner of my Note's screen, KNOX WARRANTY VOID changed from 0 to 1, not sure what that means either!
Any suggestions? I'm lost without my phone!
Edit:
After ODIN fails, my phone says unsupported version also in the top left corner. I've tried 3 different stock ROMs.
Edit 2:
And now I can't get into the boot menu, just the download menu.
Kies also won't recognize that my phone is connected now.
Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.
I've tried at least 4 different firmware versions, and am having no luck with any of them. Should I be looking for one that includes the OTA update from back in the winter?
Androidwizzard said:
Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.
Click to expand...
Click to collapse
I have the same problem. any other sugestions?
Not yet, I've yet to find a firmware that works. :/
Jotapoggi said:
I have the same problem. any other sugestions?
Click to expand...
Click to collapse
FIX
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse
Kittylee, take a look at this video " youtube . com / watch?v=GbAJH_mL6N4" I've downloaded the rar version of the clockwork recovery for my GT-N7100 from this site "galaxynote2root . com / cwm-recovery /" you have to choose the "RAR" version since it's thhe one odin uses.
OBS.: Remove the spaces from the links
It worked for me. try it.
:laugh:
Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse
kittylee said:
Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
Click to expand...
Click to collapse
Which version of andriod is it?
So, I had flashed CM12 and was unable to send text messages.
> Wiped Data / Everything
> Opened ODIN
> Flashed Stock Note 4 Rom
> Fail right away.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any reason why ODIN would be failing to flash back to Stock?
My battery should be at least 60%+, I can enter download mode etc.
I'm just confused on whats going wrong.
Any help would be appreciated it.
Thank you.
Sorry but most likely you can't go back to KitKat. What is your current bootloader version?
You can still restore your CM backup or flash back and check it with Galaxy Tools or Phone Info in Google Play.
If bootloader is OE1 or higher, you might just as well Odin the OJ6 stock tar, wiping as you did, power down, pull battery minimum 30 seconds. Odin with latest 3.10.7 using default options.
BTW, there's usually a messaging fix posted in OP or nearby post by OP in CM threads.
Sent from my SM-N910P using Tapatalk
Not going back to KitKat is fine.
I have seen the fix for sending SMS now for CM12.1, its a shame that it resets itself after a reboot.
I may still stay with CM12.1 for a bit then.
I was able to Flash TWRP Recovery and restore CM12.1 however.
My Bootloader according to Phone Info is: N910PVPU4V0J6
Though, when I leave CM12.1, I am still unsure how to flash back to Stock from here.
I was trying to flash OJ6 Stock before, which was the .tar that was failing to flash.
Thanks your input!
Rooness said:
Not going back to KitKat is fine.
I have seen the fix for sending SMS now for CM12.1, its a shame that it resets itself after a reboot.
I may still stay with CM12.1 for a bit then.
I was able to Flash TWRP Recovery and restore CM12.1 however.
My Bootloader according to Phone Info is: N910PVPU4V0J6
Though, when I leave CM12.1, I am still unsure how to flash back to Stock from here.
I was trying to flash OJ6 Stock before, which was the .tar that was failing to flash.
Thanks your input!
Click to expand...
Click to collapse
I saw ANIE in the fail log you posted. That was the original Sprint Note 4 tar from KitKat.
Do you have the OJ6 full tar?
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
That tar should flash; wipe everything but extSdCard, power down, pull battery 30 seconds and boot into download mode using latest Odin defaults should do it.
Sent from my SM-N910P using Tapatalk
Oh thank you for noticing that!
Swore I was using the proper one.
That is probably why it was failing in the first place.
Downloading now and I'll try in the morning!
Thanks once again, I really appreciate the help.
NP. Verify the md5 against the zip and you should be fine.
Sent from my SM-N910P using Tapatalk