Hello.
I usually don't post on forums but, I'm having a heck of a time trying to get this resolved. I don't know if this has already been addressed in a thread but I am having a hard time getting my phone to root with Odin.
My device is running Android Version 4.3 and firmware version VRUEMJ9
I attempted following the root steps provided here: http://forum.xda-developers.com/showthread.php?t=2143479 and have run into a roadblock. The code I get when I run the PDA file through Odin is this:
<OSM> CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried doing a factory data reset, clearing the cache partition/wipe, and am still getting a fail. I have not rooted this device previously and notice while I had the device in Downloader mode that the system status says 'custom'. I tried downloading and installing the PIT file for my device and also attempted running No triangle (which will not start up properly).
I have previously rooted devices successfully. But for some reason, I cannot get my Note 2 to cooperate. Any ideas?
jaycue said:
Hello.
My device is running Android Version 4.3 and firmware version VRUEMJ9
I have previously rooted devices successfully. But for some reason, I cannot get my Note 2 to cooperate. Any ideas?
Click to expand...
Click to collapse
When you say 4.3, do you mean the OTA update from Verizon or one of the ROMs from the forum? If it is the OTA, Kingo is the only way currently to root.
Thanks for the response
It's 4.3 OTA. I'll try that other program and see what happens.
Thank you
Another way than Kingo
jcollier said:
When you say 4.3, do you mean the OTA update from Verizon or one of the ROMs from the forum? If it is the OTA, Kingo is the only way currently to root.
Click to expand...
Click to collapse
I disagree -- but I am not an expert.
Please read my problem at http://forum.xda-developers.com/showthread.php?t=2601903
If it sounds like you, then the answer link is posted in that same thread.
TX_Jax said:
I disagree -- but I am not an expert.
Please read my problem at http://forum.xda-developers.com/showthread.php?t=2601903
If it sounds like you, then the answer link is posted in that same thread.
Click to expand...
Click to collapse
I hadn't seen your previous response before I responded on this thread. That said, it sounds like your thread might help the OP.
Related
Hey everyone!! I just need some help with Odin. I have Odin v 3.09 installed. I tried installing a custom ROM on my Galaxy S4 SCH-I545 and screwed it up. I now need to use Odin to flash a stock ROM back on to my phone. I am really confused because Odin keeps saying:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't say try a different port or try another computer because I have done both. Just please help ASAP because I really want my phone back.
:good:Thanks Guys!!!:good:
EDIT:
I fixed this thanks to k1mu. He gave me this. and it worked great. Use the no-wipe ROM.
spence1322 said:
Hey everyone!! I just need some help with Odin. I have Odin v 3.09 installed. I tried installing a custom ROM on my Galaxy S4 SCH-I545 and screwed it up. I now need to use Odin to flash a stock ROM back on to my phone. I am really confused because Odin keeps saying:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't say try a different port or try another computer because I have done both. Just please help ASAP because I really want my phone back.
:good:Thanks Guys!!!:good:
Click to expand...
Click to collapse
Using big fonts doesn't help. :laugh:
You tried to flash ME7. Why? What build were you running prior to your failed flash? What did you try to flash that failed?
Probably CM, AOSP, or some other build that's never going to work..
At this point, I'd suggest installing Samsung Kies and using the emergency firmware recovery.
Then, before flashing ANYTHING ELSE. reading at least the stickies in this and the general forum.
What you did was completely avoidable.
k1mu said:
Using big fonts doesn't help. :laugh:
You tried to flash ME7. Why? What build were you running prior to your failed flash? What did you try to flash that failed?
Probably CM, AOSP, or some other build that's never going to work..
At this point, I'd suggest installing Samsung Kies and using the emergency firmware recovery.
Then, before flashing ANYTHING ELSE. reading at least the stickies in this and the general forum.
What you did was completely avoidable.
Click to expand...
Click to collapse
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
spence1322 said:
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
Click to expand...
Click to collapse
First idea would be stop flashing random builds. You need to find out what build you are on, and flash that through Odin. Once you update to a newer build, you cannot revert back to an older build.
spence1322 said:
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
Click to expand...
Click to collapse
couldn't help yourself?? This is a $600 phone and you have to be sure what you are doing before you proceed. Not sure how to direct you from here.
decaturbob said:
couldn't help yourself?? This is a $600 phone and you have to be sure what you are doing before you proceed. Not sure how to direct you from here.
Click to expand...
Click to collapse
Apparently, based on another thread, he's running MJ7. Hopefully flashing that will get it working.
k1mu said:
Apparently, based on another thread, he's running MJ7. Hopefully flashing that will get it working.
Click to expand...
Click to collapse
with all the information available in these forums and people still proceed with little knowledge on their phones.....blows my mind away.
decaturbob said:
with all the information available in these forums and people still proceed with little knowledge on their phones.....blows my mind away.
Click to expand...
Click to collapse
Look... I'm sorry I don't know everything like you... I'm 15
spence1322 said:
Look... I'm sorry I don't know everything like you... I'm 15
Click to expand...
Click to collapse
I'm 15 as well, but I also make sure to read up on what I'm doing before I destroy my phone.
spence1322 said:
Look... I'm sorry I don't know everything like you... I'm 15
Click to expand...
Click to collapse
Don't want to lecture but being your age makes it doubly important to research....that's how you get to have knowledge.
Sent from my SCH-I545 using XDA Premium 4 mobile app
As the title states, I am currently trying to flash my phone back to stock to fix a soft brick. I was trying to get the latest update since I was on a custom ROM and couldn't get the OTA. I got the firmware from Sammobile, from what I understand to be a reputable place to get them. The flash in Odin seemed to go normally until it had the phone restart, It is now is a loop of flashing the "Galaxy Note II" screen. And I had CWM installed, but I cannot get to the recovery with it in this loop.
Yes, I have read the sticky before posting this. I am doing the only recommended thing I can find to do for this sort problem, flash it back to stock. I have the stock firmware, directly from the link in the sticky, and when I go to start it on Odin this is what I get:
<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> boot.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)
Is there something I'm missing/doing wrong? I have installed a few ROMs before, but I am fairly new to using Odin and flashing the firmware.
I would greatly appreciate any help with this
Thank you!
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I believe that was the problem. I didn't know it needed the PIT for this.
The phone lives again, but it's strange. The flash was almost done, got to the sboot, and failed. My phone had "unsupported version" in red on the Odin screen. I rebooted the phone, it went to the android update screen, and now it is working like it did before all this.
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
It is possible that the usb port I used was bad, I seriously need to remember not to use the front ports for something like this...
I need to read up more on this so I don't screw it up next time.
SFBob9 said:
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
Click to expand...
Click to collapse
It is important to note that if you take the OTA, it WILL relock your bootloader. This means no custom recovery and no custom ROMs.
Working from this thread: http://forum.xda-developers.com/showthread.php?t=2578209
Started with a phone that had the OTA Kitkat update. Tryed this from Surge1223 http://forum.xda-developers.com/showthread.php?t=2726868, didn't work. ended up downgrading (trying) to back MK2 and ended up with phone with no sound.
Came to the " [ODIN][TAR] VRUEMK2 Emergency and No-Wipe Odin tars" thread and tried that. Odin failed on the tar.md5 full wipe file "ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5" as shown in the log below. Tried the pit file too "JFLTE_USA_VZW_16G.pit" just to get the phone to reboot.
At this point I just want a unrooted stock phone. Kitkat would be fine with me, wanted to root for some stuff, but it's not that important right now. Waited for the PASS in ODIN, phone boots fine, still no sound.
Looking for help, thanks.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
You're using the mk2 tar not the nc5 tar, use nc5
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
You're using the mk2 tar not the nc5 tar, use nc5
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Sorry, I linked to the wrong original thread. I was trying to get back to MK2. I corrected the title and link to the thread I was using.
The phone is now on MK2, but with no sound.
Surge1223 said "Flash the NC2 hlos for sound to work and use bypasslkm for wifi" in this thread http://forum.xda-developers.com/showthread.php?t=2726868, but I've not found a real clear (for me) description on how to do those. I was hoping to ODIN back to stock and get the sound back.
thanks.
KitKat OTA keeps failing. Most likely because of what I've already tried and failed to make work.
montejw360 said:
KitKat OTA keeps failing. Most likely because of what I've already tried and failed to make work.
Click to expand...
Click to collapse
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
k1mu said:
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
Click to expand...
Click to collapse
Thanks. Went through this thread [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars and got the phone working again.
Tried the Verizon Software Upgrade program, but the links to it always took me to a blank page.
Where is the "Verizon Mobile" folder? On verizonwireless.com, or here on xda?
montejw360 said:
Thanks. Went through this thread [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars and got the phone working again.
Tried the Verizon Software Upgrade program, but the links to it always took me to a blank page.
Where is the "Verizon Mobile" folder? On verizonwireless.com, or here on xda?
Click to expand...
Click to collapse
On your phone. Plug it in, and the drive will appear. Windows and Mac apps.
k1mu said:
On your phone. Plug it in, and the drive will appear. Windows and Mac apps.
Click to expand...
Click to collapse
saw that come up many times, just never looked at it. good to know, thanks.
k1mu said:
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
Click to expand...
Click to collapse
Can you go into some detail on this? How would the process go with this tool? And why is it a desperation move?
Ovreel said:
Can you go into some detail on this? How would the process go with this tool? And why is it a desperation move?
Click to expand...
Click to collapse
It's a "desperation move" because it wipes everything on the phone, downloads a factory stock image, then flashes it. Basically, it's a emergency recovery tool that shouldn't be used if you care about what's on your phone.
So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!
I think I may have fired my phone.. late last night I was using http://forum.xda-developers.com/galaxy-s4-verizon/general/guide-safestrap-access-odin-t3120483 and I never installed safestarp and flashed the kernel so now my phone only boots to a yellow triangle and says "this is old binary, please update" and under it in red caps says secure fail: Kernel... I feel like I messed up..... this is my only phone and I just and stumped.. Is it just a paper weight now? I was on 5.0.1 and I was rooted...
lucask1018 said:
I think I may have fired my phone.. late last night I was using http://forum.xda-developers.com/galaxy-s4-verizon/general/guide-safestrap-access-odin-t3120483 and I never installed safestarp and flashed the kernel so now my phone only boots to a yellow triangle and says "this is old binary, please update" and under it in red caps says secure fail: Kernel... I feel like I messed up..... this is my only phone and I just and stumped.. Is it just a paper weight now? I was on 5.0.1 and I was rooted...
Click to expand...
Click to collapse
I545VRUGOC1_Neutered_Full_Odin.tar.md5 I ALSO TRIED TO ODIN THIS AND IT JUST FAILS. <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUGOC1_Neutered_Full_Odin.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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and my phone reads
sv rev check fail fused 7 binary 8.... can anybody help me?/..
If you are on OC1 you should have read the disclaimer on the page to which you linked. The file you flashed is not for OC1
Before I can help I have to ask questions. Are you on a keeproot version of 5.0? (NOT OTA). Did you take the OTA for lollipop?
Matthew M. said:
If you are on OC1 you should have read the disclaimer on the page to which you linked. The file you flashed is not for OC1
Before I can help I have to ask questions. Are you on a keeproot version of 5.0? (NOT OTA). Did you take the OTA for lollipop?
Click to expand...
Click to collapse
no I the ota 5.0.1 youre right I should have read it...... im downloading the oct 5.0.1 firmware off samsmobile right now do u think ill be able to odin that, or do u think my phone is screwd? im lost honestly..
lucask1018 said:
no I the ota 5.0.1 youre right I should have read it...... im downloading the oct 5.0.1 firmware off samsmobile right now do u think ill be able to odin that, or do u think my phone is screwd? im lost honestly..
Click to expand...
Click to collapse
The only reason the file you attempted to flash in odin earlier was because it wasn't the right file for your installed firmware. If you can find an SCH-I545 OTA 5.0.1 file to flash then that is your best bet.
Matthew M. said:
The only reason the file you attempted to flash in odin earlier was because it wasn't the right file for your installed firmware. If you can find an SCH-I545 OTA 5.0.1 file to flash then that is your best bet.
Click to expand...
Click to collapse
im downloading the 5.0.1 from sammobile do u think this will work? and why didn't the other one work? I was trying to flash this md5 file called I545VRUGOC1_Neutered_Full_Odin.tar.md5... shouldn't that work?
There is a difference between the Ota and the non Ota 5.0.1, the qfuse counter and some other stuff which prevents you from downgrading. I would only think that it didn't work because of the difference. I can't guarantee anything will work but it's worth a shot since you can't even use the phone atm
Matthew M. said:
There is a difference between the Ota and the non Ota 5.0.1, the qfuse counter and some other stuff which prevents you from downgrading. I would only think that it didn't work because of the difference. I can't guarantee anything will work but it's worth a shot since you can't even use the phone atm
Click to expand...
Click to collapse
im going to work right now but I will try to odin the files from sammobile wheni get home and ill let u know wassup im praying
Matthew M. said:
There is a difference between the Ota and the non Ota 5.0.1, the qfuse counter and some other stuff which prevents you from downgrading. I would only think that it didn't work because of the difference. I can't guarantee anything will work but it's worth a shot since you can't even use the phone atm
Click to expand...
Click to collapse
the update from samsmobile didn't work so I think im ****ed . my fault but it sucks
acutally I got it to work and it is downloading as we speak. hope it goes through half way as we speak