Database Users

Odin Failure to flash CWM Galaxy S4 ATT

Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2
After spending a few hours here on XDA both searching the site and posting on the help thread, I've come to no solution.
So yesterday due to a level of frustration with the amount of bloat that comes pre-installed on the Samsung devices, I decided I would try to set up a custom rom. I've used the Towelroot site to root the device (enable superuser access and disable Knox,) But wasn't able to install CWM. I've downloaded and installed the CWM Rom Manager and inside that app is an option to install CWM manually. Of course it isn't that easy, because although it says it's installed the recovery, when I boot into recover mode, it is still the stock android recovery mode.
So I turned to Odin. Specifically Odin 3.09. This is where the problems start. I start my phone and enable download mode. The phone is recognized by Odin and I choose the CWM file I have (recover-clockwork-touch-6.0.4.4-jflteatt.tar.) I press start and the process begins, but before long I see FAIL! in red at the top
The message box reads as follows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried using three different usb cables (including the stock s4 cable included in the packaging) and several different ports of course to no avail.
What exactly does FAIL! (Auth) mean? That seems to be the point where it goes south. I've tried other Odin versions and gotten more or less the same result.
Could I be flashing a bad file? Is the CWM.tar not the correct file to flash?
Anyways if anyone has a fix to this particular solution then let me know. Otherwise I'll take really any other viable solution to enabling custom roms on the Galaxy S4 for ATT. I'd like this to be a thread that people see when they google search it, so I won't give up and I'll be sure to post with the best process that I can find!

I think u maybe flashing a bad file or maybe ur choosing wrong option in Odin to flash the recovery, what option did u choose? and also check in the att s4 section as this is not the right forum for ur phone model
Sent from my GT-I9505 using XDA Premium 4 mobile app

dorian2kx said:
I think u maybe flashing a bad file or maybe ur choosing wrong option in Odin to flash the recovery, what option did u choose? and also check in the att s4 section as this is not the right forum for ur phone model
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odin PDA loader and then start. Very simple it seems. I didn't see any particular ATT s4 section but maybe a mod could move me over?

Alright stop what you are doing. Want to kill your phone? Keep going like this.
The stuff you try to flash is NOT for you phone. You don't have an i9505 or an i9500. You have an at&t phone. That's a completely different section on xda.
You need to be in this section.
http://forum.xda-developers.com/galaxy-s4-att/general
You probably need to look for unlocking your bootloader. But I would suggest reading and understanding everything before you do anything like this again. If you want to kill your phone this is the way to do it.

[Q]Flashing Lollipop help

i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything

Is your device unlocked or branded?

Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...

billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.

Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a

i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.

Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10

billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?

Have practically the same situation...
The furthest I've got is the following
Code:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.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)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.

Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*
Rogers is the only carrier who pushed this update, it was pulled shortly after, due to corruption. I had to spend literally ALL day downloading this. I downloaded it 7 times before i got a OTA zip that passes a CRC check and extracted properly. What a pain in the butt it is i had to convert my Telus device to Rogers fully down to modding the EFS to get this done.
Prerequisit: You must be on a 5.1.1 compatible TWRP as well as a 5.1.1 rom when flashing these packages or your going to get stuck in a binary miss match. While there is a fix for this with out the W8 5.1.1 odin packages, it takes a lot of musical flashing. So be sure to be on a compatible 5.1.1 rom, Kernel and TWRP first.
As always, you flash at YOUR OWN RISK. I will of course try to provide support if I am online, If you appreciate how much the pain in my butt was, and you didn't have to do this your self. Click Donate.
The Bootloader MUST be flashed via ODIN 3.10.X or higher. in the BL slot. Hence why its a tar. Sorry no flashables, Samsung locks the boot loader areas to everything but their own signed recovery, from their own signed update.zip
BO8H BL
BOI1 BL
BOI6 BL *LATEST*
The modem is TWRP flashable
BO8H Modem
BOI1 Modem
BOI6 Modem *LATEST*
You can get ODIN 3.10.6 HERE
Samsung USB Drivers HERE
Fingerprint confirmed working by my self. on custom 5.1.1 roms and stock.

You're my hero, lets have sex together

virulentt said:
You're my hero, lets have sex together
Click to expand...
Click to collapse
LOL the new "FIRST!"

-Mr. X- said:
LOL the new "FIRST!"
Click to expand...
Click to collapse
It works thanks a lot haha. No homo btw <3

Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?

anuben said:
Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?
Click to expand...
Click to collapse
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.

-Mr. X- said:
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.
Click to expand...
Click to collapse
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> cm.bin
<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)
<ID:0/005> Removed!!

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> cm.bin
<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)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
redownload the Bootloader, your .tar could be corrupted.

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> cm.bin
<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)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
Yes i flashed it via BL. Whats your actual device.

Worked perfectly for me. So glad to have a working fingerprint scanner on a 5.1.1 custom rom. Thanks
Sent from my SM-G920W8

Easiest way to do it is just make sure the Bootloader is loaded on Odin first on your PC then reboot to recovery and flash the modem package, select reboot and choose Download so it reboots to download mode, plug the phone to usb and flash in Odin and you're done!
Sent from my SM-G925F

I'm now getting some new "not enforcing" red text during boot. Is that expected?

BlackRabbits said:
I'm now getting some new "not enforcing" red text during boot. Is that expected?
Click to expand...
Click to collapse
Yep that's normal.
Sent from my SM-G925F

-Mr. X- said:
Yes i flashed it via BL. Whats your actual device.
Click to expand...
Click to collapse
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3

I've been using Arter97's back-to-n0t3 v3 with his 3.5 kernel, SO SMOOTH I lose around 5 to 7% overnight. You guys should give it a try!
http://forum.xda-developers.com/galaxy-s6/development/to-n0t3-bring-larger-fun-to-flagship-t3179857
http://forum.xda-developers.com/gal...development/arter97-kernel-galaxy-s6-t3171246
*** Download links are on his website (careful, the 3.6 version of his kernel isn't for our device, use the 3.5 g920tw8 one ***
http://arter97.com/browse/S6/
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
that's not for the edge... you could brick your device flashing a non-edge bootloader to an edge one.

anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.

-Mr. X- said:
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.
Click to expand...
Click to collapse
holy fuk i shouldn't be doing drinking and flashing :silly: thank you though. appreciate your help...:good:

Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.

caanda45 said:
Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.
Click to expand...
Click to collapse
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I would flash TWRP on your 5.0.2 device as it sits, then i would choose your 5.1.1 rom of your liking. Put it all on your storage on the phone except the bootloader tar. Flash the rom, modem and what ever else in TWRP. then in the TWRP reboot options reboot directly to download/bootloader. and odin the bootloader. boot the device normally and you're good!
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader

-Mr. X- said:
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader
Click to expand...
Click to collapse
Perfect, I was on that rom for awhile with 5.0.2 and some stuff missing..So the best plan is
1. Re Root and Flash TWRP
2. Back up
3. Flash 5.1.1 Rom
4. Flash Bootloader with Odin
5. Flash Modem with TWRP
And then I should be good to go? Where does the Audio patch come in?
Any other suggestions or order to my plan?
Thanks again for your time and hard work!!!

Samsung galaxy S5 SM-900F Boot loop.

Soo, my S5 SM-900F is having some issues
my odin seems to be working fine, and im using the correct firmware.
but... When i do flash it the problem persist nothing changes, so im sorta stuck in a boot loop
anyone that can help ?

Recovery -> Factory Reset (wipe data).

SSHLord-R said:
Recovery -> Factory Reset (wipe data).
Click to expand...
Click to collapse
Ehmmm??
im not sure you understood me, im stuck in a boot loop.

Citroon said:
Ehmmm??
im not sure you understood me, im stuck in a boot loop.
Click to expand...
Click to collapse
Is the phone stuck on the flashing samsung screen? What exactly did you flash?

justinxfan said:
Is the phone stuck on the flashing samsung screen? What exactly did you flash?
Click to expand...
Click to collapse
I tried flashing with TWRP to a custom cyanogen rom, as per usual.
something must have gone wrong in that process, im stuck in a bootloop
when i try to flash to a stock firmware it's the same thing over again, just another bootloop (i've tried with different types of Odin)

Citroon said:
I tried flashing with TWRP to a custom cyanogen rom, as per usual.
something must have gone wrong in that process, im stuck in a bootloop
when i try to flash to a stock firmware it's the same thing over again, just another bootloop (i've tried with different types of Odin)
Click to expand...
Click to collapse
So to say, it's simply stuck on the "samsung galaxy s5 logo screen" im not going further onto the animation.

Please wipe your phone as you probably dirty flashed. Just factory reset it and you will be back up and running.
Sent from my Nexus 6P using Tapatalk

epeglab said:
Please wipe your phone as you probably dirty flashed. Just factory reset it and you will be back up and running.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
well, i cant really reset it since the only thing i really can do at the momment is flashing trough odin :/

Okay. Download your stock firmware and then flash through Odin. Or u can use the Samsung software as one of my friends did. Either way if u have download mode you have a 99% chance of actually getting it to work.
Sent from my Nexus 6P using Tapatalk

epeglab said:
Okay. Download your stock firmware and then flash through Odin. Or u can use the Samsung software as one of my friends did. Either way if u have download mode you have a 99% chance of actually getting it to work.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The samsung software?
you mean kies?

Yea. I don't know if it's recommend, but it worked for my friend with Odin always failed.
Sent from my Nexus 6P using Tapatalk

epeglab said:
Yea. I don't know if it's recommend, but it worked for my friend with Odin always failed.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
that didn't work either, i have no clue what to do now ;_;

Citroon said:
that didn't work either, i have no clue what to do now ;_;
Click to expand...
Click to collapse
So does Odin actually say fail or does it pass? And is there a message of failure?
Sent from my Nexus 6P using Tapatalk

epeglab said:
So does Odin actually say fail or does it pass? And is there a message of failure?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
There's no message of failure it simply passes as it should, just like when i root or flash any other samsung phone
It's just the boot loop

Can u get into recovery? Or only download mode? Do the button combo to get in if you can. Just trying to see what you can do.
Sent from my Nexus 6P using Tapatalk

epeglab said:
So does Odin actually say fail or does it pass? And is there a message of failure?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
there's no error message, and odin does pass

epeglab said:
Can u get into recovery? Or only download mode? Do the button combo to get in if you can. Just trying to see what you can do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I can get into download mode (hence i can actually get it to do something with Odin) However, when i try to go into recovery the boot loop continues
as in, it does say in the upper left corner that it's booting into recovery but then it bootloops over and over

Same problem with my niece phone. I can go to Download mode but not to recovery mode.
flashed Official rom from SAMmobile with G900FDXS1BPH1_G900FOLC1BOJ1_G900FDXU1BOE1_HOME.tar.md5
passed the Odin but still bootloop.
<ID:0/011> SingleDownload.
<ID:0/011> aboot.mbn
<ID:0/011> NAND Write Start!!
<ID:0/011> sbl1.mbn
<ID:0/011> rpm.mbn
<ID:0/011> tz.mbn
<ID:0/011> sdi.mbn
<ID:0/011> NON-HLOS.bin
<ID:0/011> boot.img
<ID:0/011> recovery.img
<ID:0/011> system.img.ext4
<ID:0/011> modem.bin
<ID:0/011> cache.img.ext4
<ID:0/011> hidden.img.ext4
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Removed!!
<ID:0/011> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/012> Added!!
<ID:0/012> Removed!!

Remove SD card
I had this same problem with download mode working, but recovery mode causing a boot loop.
The boot loop stopped when I tried rebooting without the sd card inserted.
I think I may have been able to insert it back in and access it while recovery was booted, but the problem should be fairly easy to fix if you can still get into download mode and are able to get it stop bootlooping this way.

I have the same issue, tried kies, tried clean and dirty flash, and it just keeps on bootlooping to oblivion.

S4 sgh i337

I was going through the posts and realized how helpful you were to a noob like me who helped me to install a stock custom rom i think i forgot to turn off the updates or something apprently my phone was initially stuck in bootloader the atnt now it wont even show the atnt logo keeping my fingers crossed that i havent screwed my phone
My phone can go in the android system recovery <3e>
LRX22C. I337UCUGOC3
if i am not wrong i cant just install any custom rom since bootloader is still locked i dont know for sure
in the screen below
#manual mode#
--applying multi-csc
applied the csc-code: ATT
Successfully applied multi - CSC
what have i tried uptill now
just wipe data/factory reset
can you help ?

Can you get into recovery mode? If it is just stuck booting to download mode only, then it sounds like you need to ODIN back to stock or use a debrick image. Your bootloader is locked so no TWRP recovery can be installed. You can use flash fire, which is like safe strap sort of, but your phone has to be booted into Android for it to work.

StoneyJSG said:
Can you get into recovery mode? If it is just stuck booting to download mode only, then it sounds like you need to ODIN back to stock or use a debrick image. Your bootloader is locked so no TWRP recovery can be installed. You can use flash fire, which is like safe strap sort of, but your phone has to be booted into Android for it to work.
Click to expand...
Click to collapse
i can get into recovery tried to sideload a rom gives some footer error

y2kyasir said:
i can get into recovery tried to sideload a rom gives some footer error
Click to expand...
Click to collapse
and signature verification error

StoneyJSG said:
Can you get into recovery mode? If it is just stuck booting to download mode only, then it sounds like you need to ODIN back to stock or use a debrick image. Your bootloader is locked so no TWRP recovery can be installed. You can use flash fire, which is like safe strap sort of, but your phone has to be booted into Android for it to work.
Click to expand...
Click to collapse
can you help ??
maybe i am installing not the appropriate rom ?

y2kyasir said:
can you help ??
maybe i am installing not the appropriate rom ?
Click to expand...
Click to collapse
You are on the OC3 bootloader right? Try to install golden eye ROM, which is touchwiz based. Since the bootloader is locked, you can only install touchwiz based ROMs and I think Google play edition ROMs. Trying to install cyogen mod or any other AOSP ROM won't work. Have you tried finding the debrick image or the stock ODIN tar file? With all those errors, I would try one of those routes.

StoneyJSG said:
You are on the OC3 bootloader right? Try to install golden eye ROM, which is touchwiz based. Since the bootloader is locked, you can only install touchwiz based ROMs and I think Google play edition ROMs. Trying to install cyogen mod or any other AOSP ROM won't work. Have you tried finding the debrick image or the stock ODIN tar file? With all those errors, I would try one of those routes.
Click to expand...
Click to collapse
i am on on nb1 since i did try to get it back to stock rom i found in the forums bootloader is locked i dont know about the debrick image but i am sure i did flash the stock odin tar from odin
i had no error everything went smoothly on odin 0 fail
i did download the rom put it odin everything went fine
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!

StoneyJSG said:
You are on the OC3 bootloader right? Try to install golden eye ROM, which is touchwiz based. Since the bootloader is locked, you can only install touchwiz based ROMs and I think Google play edition ROMs. Trying to install cyogen mod or any other AOSP ROM won't work. Have you tried finding the debrick image or the stock ODIN tar file? With all those errors, I would try one of those routes.
Click to expand...
Click to collapse
and i know you are a pro so you can drag my noob ass out of this situation

Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2674223
Is that the file you flashed in ODIN for NB1?
I'm no Android developer or anything, I just know the basic stuff. Most of what I know I learned from the XDA forums here.

StoneyJSG said:
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2674223
Is that the file you flashed in ODIN for NB1?
I'm no Android developer or anything, I just know the basic stuff. Most of what I know I learned from the XDA forums here.
Click to expand...
Click to collapse
yes https://forum.xda-developers.com/showthread.php?t=2674223
yes the rootable odin stock
but not the non root one
is there any specific time you guys are around so i dont have to wait days sorry a bit anxious to get my phone up and going

I am here off and on while I am at work Monday thru Friday 12 p.m. to 6 p.m. though my times will vary.