[Q] 900V Odin Mode Loop - About to lose my mind

jmorehouse

Member
Aug 21, 2007
12
0
0
Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.

I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.

He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!

Thanks!
 

ludeawakening

Senior Member
Dec 7, 2010
1,389
2,059
153
Gadsden, Alabama
Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.

I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.

He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!

Thanks!
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware with Odin so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.
 
Last edited:
  • Like
Reactions: Savagerun

jmorehouse

Member
Aug 21, 2007
12
0
0
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
 

jmorehouse

Member
Aug 21, 2007
12
0
0
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
Tried flashing your stock rom and below is the output from Odin...

Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!! 
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 

ludeawakening

Senior Member
Dec 7, 2010
1,389
2,059
153
Gadsden, Alabama
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.

And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.

---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------

Tried flashing your stock rom and below is the output from Odin...

Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!! 
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117#none
 
Last edited:
  • Like
Reactions: Savagerun

jmorehouse

Member
Aug 21, 2007
12
0
0
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.

And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.

---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------


Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers #
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 

ludeawakening

Senior Member
Dec 7, 2010
1,389
2,059
153
Gadsden, Alabama
Yes sometimes the cable does make a difference. You can try downloading the file again, although, getting a bad download from XDA is pretty rare. I'm not familiar with Odin failing to flash a file. I've never had it happen to me.

Sent from my SM-G900V using XDA Free mobile app
 

jmorehouse

Member
Aug 21, 2007
12
0
0
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It is a stock cable. Installed the latest version of the drivers taken from Samsung Kies 3.2.14113.3 (2014-11-20) for Windows and got the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!! 
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 

ludeawakening

Senior Member
Dec 7, 2010
1,389
2,059
153
Gadsden, Alabama
I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?

Sent from my SM-G900V using XDA Free mobile app
 

jmorehouse

Member
Aug 21, 2007
12
0
0
I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?

Sent from my SM-G900V using XDA Free mobile app
That is correct. It shows it on COM3.
 

ludeawakening

Senior Member
Dec 7, 2010
1,389
2,059
153
Gadsden, Alabama
Nice "thorough"job helping out the op!! :thumbup:

Sent from my SM-G900V using XDA Free mobile app
Thank you. If I do step in to help, I'm the type that will not give up on someone until either the issue is solved, or it's deemed that there is a hardware issue or something and nothing can be done. I remember what it was like being lost on trying to do this stuff. I researched and studied for a long time on how Android works, so I might as well put all that gained knowledge to good use by helping people now. And that's what an awesome community like XDA does, we help each other. :)
 

ludeawakening

Senior Member
Dec 7, 2010
1,389
2,059
153
Gadsden, Alabama
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.

If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19
 
Last edited:

jmorehouse

Member
Aug 21, 2007
12
0
0
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.

If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?