Database Users

[HELP] Bricked S4 19505

I was playing with my S4 today and I saw this thread on xda regarding Android 4.3 firmware. http://forum.xda-developers.com/showthread.php?t=2348272
Being cheeky, I decided to install it on my S4. Before I did anything, I backed up my device and transferred the backup from my sd card to my computer so that I have enough space. I then placed the .zip file into my S4 folder and wiped all data, clear cache and proceed to install it. I didnt remember if I clicked Disable Recovery Flash or not. heh After that, I waited for 1 hr but my S4 is stuck at the google startup screen with occasional vibrations of the phone. I tried going to recovery mode and resetted everything, including formatting my card, and hence, losing the .zip file of the custom google edition 4.3 firmware. I dont have anything to reset it coz my whole S4 is empty. So I decided to use Odin and downloaded the international mtar file, but this appeared.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T310XWUAMG3_T310OLBAME6_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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone pls help me? I dont know if it is bricked and if there is way to fix it. Thanks in advance

You can Try flashing a custum recovery and go on from there
Sent from my GT-I9505 using Tapatalk 4 Beta
---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------
Or just reboot your pc
Sent from my GT-I9505 using Tapatalk 4 Beta

make sure kies is unloaded it will interrupt odin
(stop all services and processes in task manager)

Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.

WHat do you mean use a .pit file? Still doesnt wotk..

hazique98 said:
WHat do you mean use a .pit file? Still doesnt wotk..
Click to expand...
Click to collapse
have you tried the bootloop fix from the same thread ?

[q] at&t s4 nc1 help

Ok so im not sure this is where to post this but I'll give it a try. I had a rooted galaxy s4 running NC1 update. I wanted to unroot it and set it back to stock so i can give it to a family member. I followed a guide that told me to flash the NB1 firmware and update to NC1, so i put the phone in download mode and opened ODIN and selected the NB1 tar file, right after i started it there was some text going on on the left of the screen, and after it said something like "boot.img" (I'm not sure what it exactly said but it started with boot.something) it gave an error and odin said it failed. I tried starting the phone up and it said that the firmware update was interrupted and to plug it into kies. I tried following the emergeny firmware update and it wouldn't go through. On the top left of the screen on my S4 it says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRENTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
eMMC BURST MODE: enabled
If anyone can help I would be eternally gratefull, I'm not very android savy yet and i have absolutly no idea on how to fix this.
-Rob

Put the phone in download mode and re-attempt the NB1 flash through Odin. As long as the download mode exists, the phone can be recovered.

jmjoyas said:
Put the phone in download mode and re-attempt the NB1 flash through Odin. As long as the download mode exists, the phone can be recovered.
Click to expand...
Click to collapse
Can you provide me a link to the correct file i should try flashing to it? I do not know if it would make a difference but it was running 4.4.2.

Robbyzbot said:
Can you provide me a link to the correct file i should try flashing to it? I do not know if it would make a difference but it was running 4.4.2.
Click to expand...
Click to collapse
Re flash to NB1 firmware using Odin. The you're back to stock not rooted.
Sent from my SGH-I337 using XDA Free mobile app

thebestiam said:
Re flash to NB1 firmware using Odin. The you're back to stock not rooted.
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
I want to get back to stock, do you have a link to the file i should flash?

Robbyzbot said:
I want to get back to stock, do you have a link to the file i should flash?
Click to expand...
Click to collapse
In the general forum
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
In the general forum
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Should i flash the stock odin tar or the rootable stock odin tar? Do i need the system dump file?

jd1639 said:
In the general forum
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already downloaded that file and i just tried it again, here is what odin says:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_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> aboot.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?

Robbyzbot said:
I already downloaded that file and i just tried it again, here is what odin says:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_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> aboot.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
Click to expand...
Click to collapse
Try different usb ports, the ones in the back of a pc. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try different usb ports, the ones in the back of a pc. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you so much that was my problem, my phone is fixed! You are a life saver!

Robbyzbot said:
Thank you so much that was my problem, my phone is fixed! You are a life saver!
Click to expand...
Click to collapse
no problem, glad you got it fixed
Sent from my Nexus 5 using XDA Free mobile app

[Q] AT&T Galaxy S4 Soft bricked phone-can't ODIN restore

I have been searching threads for 6 hours, but haven't found anything conclusive.
I rooted my phone a while back, but today I decided to install a new custom ROM. I backed up the ROM to my external SD and installed the new one through safestrap. However, when I tried to reboot, I just got stuck on a screen that says samsung and has an open lock.
I am able to get into download mode, but not into recovery. After I boot into download mode, it says write protection:enabled (not sure that is normal, but I thought I would mention it). I open up Odin and the drivers seem to load fine. I have tried a a few versions of ODIN and two different Stock ROMs, but it fails every time. On my phone, after it fails, I get a message that says SW Rev. Check Fail: fused 2, binary: 1.
In ODIN, I get the following:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? I'm getting kind of desperate.

Have you tried another USB cable?.

I have actually. The original cable and just another one I had. Also, tried it on 3 computers.

Should I be loading a PIT file? some places say to do it and others say not to.

marcymtz92 said:
Should I be loading a PIT file? some places say to do it and others say not to.
Click to expand...
Click to collapse
The problem is you're trying to flash mdl firmware and you're not on that version. It looks like you're on mf3. There is no Odin flashable mf3 firmware so I'd suggest you flash the nb1 tar file. See the general forum for the file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

You are freaking amazing. That file totally worked. Thanks so much.

marcymtz92 said:
You are freaking amazing. That file totally worked. Thanks so much.
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app

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

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!

jmorehouse said:
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!
Click to expand...
Click to collapse
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.

ludeawakening said:
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.
Click to expand...
Click to collapse
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 said:
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)?
Click to expand...
Click to collapse
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)

jmorehouse said:
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)?
Click to expand...
Click to collapse
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 ----------
jmorehouse said:
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)
Click to expand...
Click to collapse
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

ludeawakening said:
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 #
Click to expand...
Click to collapse
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)

Is it a factory cable? If it is redownload the file.

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 said:
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)
Click to expand...
Click to collapse
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)

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

ludeawakening said:
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
Click to expand...
Click to collapse
That is correct. It shows it on COM3.

I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app

ludeawakening said:
I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Please and thank you. I am going to try and get another laptop to try it on.

jmorehouse said:
Please and thank you. I am going to try and get another laptop to try it on.
Click to expand...
Click to collapse
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.

jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.

ludeawakening said:
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.
Click to expand...
Click to collapse
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app

Savagerun said:
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
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.

jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
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

ludeawakening said:
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
Click to expand...
Click to collapse
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?

jmorehouse said:
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?
Click to expand...
Click to collapse
You can find a video in this thread http://forum.xda-developers.com/showthread.php?t=2784290
Sent from my SM-G900V using XDA Free mobile app

Bricked while trying to root

OK my problem is i tried to root my s4 using the I337_NC1_Stock_Kernel.tar.md5 in odin.. when flashing to my phone it bricked the phone.. I have tried using odin to reflash the stock firmware to my phone with little luck. I don't really know alot about these phones. I have tired a lot of things with little luck. I have downloaded the pit file and tried using it also alone with the firmware. i am not really sure were to go from here.. I am open to any help
Thanks!

How does using a stock firmware via Odin lead to root? Pit file? Your post can't be real...
Sent from my iPad using Tapatalk

Jleek0151 said:
OK my problem is i tried to root my s4 using the I337_NC1_Stock_Kernel.tar.md5 in odin.. when flashing to my phone it bricked the phone.. I have tried using odin to reflash the stock firmware to my phone with little luck. I don't really know alot about these phones. I have tired a lot of things with little luck. I have downloaded the pit file and tried using it also alone with the firmware. i am not really sure were to go from here.. I am open to any help
Thanks!
Click to expand...
Click to collapse
Are you flashing the nb1 tar file in Odin to return to stock?
http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
cantenna said:
How does using a stock firmware via Odin lead to root? Pit file? Your post can't be real...
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
The post is real. He tried to flash the nc1 kernel. You need that to use towelroot. He shouldn't be using a pit though.
Sent from my Nexus 5 using XDA Free mobile app

Sorry a little confusion. When i tried to flash the file into my phone it failed and bricked my phone. When i tired to Install the stock firmware back on the phone i tired using the pit file like i read in other forms. I don't know much about all the stuff i was just doing what i read that helped other people. Anytime i try to flash any files onto my phone it fails. What im asking is what do i need to do to fix the brick problem. Im not sure if now the kernel file on my phone is missed up now? Do i need to try and flash a actual stock kernel file? I have also read that sometimes the Download mode on the phone gets corrupt and causes file not to flash. Before i started having problems i had 4.2.2 downloaded. I will have a video up shortly showing what im doing in odin with the files.
Thanks

I am downloading this ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_ low_ship_MULTI_CERT.tar.md5 file now.. I will try and flash this onto my phone next and see what that does.. I will use v3.09 of odin also. Is there anything else i should try first before i do this? Im not 100% sure what the difference is between this file and the stock firmware i was using before.
here is the video /watch?v=VWvDj16mA_U&feature=youtu.be
Thanks

Add y o u t u b e . C o m in front of the link.
Sent from my iPhone using Tapatalk

File goes in AP slot in Odin.

I think I was wrong also. I had the newest update that was over the air so that would of been 4.4.4. Is this why I'm having the issues. Is my bootloader locked for good now?
Sent from my iPhone using Tapatalk

Jleek0151 said:
I think I was wrong also. I had the newest update that was over the air so that would of been 4.4.4. Is this why I'm having the issues. Is my bootloader locked for good now?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
You're bootloader was always locked for good. All i337's from day one were. But that's not the issue. Have you flashed the nb1 tar file in Odin? That should work. You're still on a version where you can root and use safestrap.
Sent from my Nexus 9 using XDA Free mobile app

I believe so it always said fails. Goes to "getting pit file for mapping and then fails"
Sent from my iPhone using Tapatalk

Jleek0151 said:
I believe so it always said fails. Goes to "getting pit file for mapping and then fails"
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok, I'm old school so let's start from scratch and rule out a hardware issue. Google Odin 1.85 xda and install that on your pc. Then download the stock Odin tar file from here http://forum.xda-developers.com/showthread.php?p=50912149 edit, if you've download it once before, re-download it
Open Odin on your pc. Then boot into download mode on your device and connect it to your pc. Then run the nb1 tar file in the PDA slot of Odin.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Ok, I'm old school so let's start from scratch and rule out a hardware issue. Google Odin 1.85 xda and install that on your pc. Then download the stock Odin tar file from here http://forum.xda-developers.com/showthread.php?p=50912149 edit, if you've download it once before, re-download it
Open Odin on your pc. Then boot into download mode on your device and connect it to your pc. Then run the nb1 tar file in the PDA slot of Odin.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok im Downloading all the files now.. The files aren't like anything that i have now.. So it will be around an hour before its done.
Thanks a lot I hope it works.

jd1639 said:
Ok, I'm old school so let's start from scratch and rule out a hardware issue. Google Odin 1.85 xda and install that on your pc. Then download the stock Odin tar file from here http://forum.xda-developers.com/showthread.php?p=50912149 edit, if you've download it once before, re-download it
Open Odin on your pc. Then boot into download mode on your device and connect it to your pc. Then run the nb1 tar file in the PDA slot of Odin.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I am downloading the stock 4.4 .tar file is the one you are talking about ?

Jleek0151 said:
I am downloading the stock 4.4 .tar file is the one you are talking about ?
Click to expand...
Click to collapse
If you're downloading it grim the link I gave you, then yes it's the one I'm talking about
Sent from my Nexus 9 using XDA Free mobile app

Alright this is what odin saids when i try to flash anything
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
now this isnt the file im downloading, but this was suppose to be a all in one .tar file for nb1.

Jleek0151 said:
Alright this is what odin saids when i try to flash anything
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Removed!!
Added!!
now this isnt the file im downloading, but this was suppose to be a all in one .tar file for nb1.
Click to expand...
Click to collapse
Ok, Odin can be finicky so don't give up yet. Try different usb ports, 2.0 not 3.0, use the ones in this back of your pc and cables.
Sent from my Nexus 9 using XDA Free mobile app

Alright will do! Once the file downloads I'll switch cables and try a different port. I have used the same one from the beginning.
Sent from my iPhone using Tapatalk

Ok after switching cables and ports and using the old file it got a bit farther but still failed..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on the phone itself in red says SW REV. CHECK FAIL : FUSED :5. BINARY :1

Jleek0151 said:
Ok after switching cables and ports and using the old file it got a bit farther but still failed..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on the phone itself in red says SW REV. CHECK FAIL : FUSED :5. BINARY :1
Click to expand...
Click to collapse
Ok, fused 5 binary 1 just shows you're on the 4.4.4 bootloader. The nb1 tar will work. Keep trying
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
ok, fused 5 binary 1 just shows you're on the 4.4.4 bootloader. The nb1 tar will work. Keep trying
sent from my nexus 9 using xda free mobile app
Click to expand...
Click to collapse
ok im unzipping the file now ill keep you posted.
Thanks!!