Related
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
orchid18 said:
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
Click to expand...
Click to collapse
Try another usb port (recommended: back of the computer)
and flash again via Odin stock base rom 4.3
P.S: I was getting the similar problem you have. another usb port helped me
Bordo_Bereli51 said:
Try another usb port (recommended: back of the computer)
and flash again via Odin stock base rom 4.3
Click to expand...
Click to collapse
Thanks Yeah I've tried that, I've tried front, back, on a laptop, but Odin still red fails at the writing 'System' (the largest 'chunk' of the tar.md5 file) no matter which 4.3 rom I try
I so upset :crying:
orchid18 said:
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
Click to expand...
Click to collapse
Hello,
For my part, I also encountered problems! the only rom that is passed via ODIN after testing 5 other is:
I9505XXUAMDF_I9505PHNAMD8_PHN
But if Knox! possible that this does not happen either?
*************
For me I do:
1 - Flash with Odin Pit
2 - Flash with ODIN last recovery philz_touch_5.15.8-i9505.zip
3 - Wip full recovery for new rom
4 - Flash the I9505XXUAMDF_I9505PHNAMD8_PHN
And then this happened.
Alan-B said:
Hello,
For my part, I also encountered problems! the only rom that is passed via ODIN after testing 5 other is:
I9505XXUAMDF_I9505PHNAMD8_PHN
But if Knox! possible that this does not happen either?
Click to expand...
Click to collapse
I thought with the official 4.3 new bootloader, we cant downgrade to 4.2.2.
Try another Odin version or extract the .tar file via Winrar (rename it from .tar.md5 to .tar if your file ending at .tar.md5) and flash the system.img.ext4 via this tool http://forum.xda-developers.com/showthread.php?t=2333807 see if you getting error with this tool while flashing the system.img.ext4
and then try to flash again with odin
P.S. While flashing via Odin kill in Task Manager Kies and related process and flash again
Bordo_Bereli51 said:
I thought with the official 4.3 new bootloader, we cant downgrade to 4.2.2.
Try another Odin version or extract the .tar file via Winrar and flash the system.img.ext4 via this tool http://forum.xda-developers.com/showthread.php?t=2333807 see if you getting error with this tool while flashing the system.img.ext4
and then try to flash again with odin
P.S. While flashing via Odin kill in Task Manager Kies and related process and flash again
Click to expand...
Click to collapse
Hey Bordo
Thankyou so much for your suggestion - I will try the individual component flasher later tonight and then write back on what happens
I will also remember to kill Kies with task manager beforehand, before using ODIN or any other flasher :good:
Thankyou so much for your time and effort in trying to help!!!! Much appreciated
I have searched everywhere - Google, XDA, AndroidCentral, everything.
I am very savvy with computers and phones - I'm a programmer myself.
I had CM11 nightly installed for weeks. All of a sudden, my phone restarts itself into an infinite boot loop (doesn't go past the SAMSUNG Galaxy S 4 screen).
I have tried EVERYTHING. Restoring an old nandroid backup, reflashing CM11 and Gapps - nothing.
Every time I try to install the stock firmware - both L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 (acquired directly from Samsung) and L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 (again, direct download) it always fails at the same spot:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I flashed the MK2 modem when flashing the MK2 stock ROM... no dice. Same thing for the NAE modem + ROM.
Please, help me. I have no clue what to do at this point. The only backup I have, which is of Android 4.2.2, also doesn't work. Same bootloop.
I have tried all of the above things with three different version of Odin: 1.805, 3.04 and 3.07.
I re-installed the Samsung USB drivers, in case that was the issue.
I am completely clueless.
The main problem (I believe) is this:
aboot.mbn
Please and thank you.
rpnunez said:
I have searched everywhere - Google, XDA, AndroidCentral, everything.
I am very savvy with computers and phones - I'm a programmer myself.
I had CM11 nightly installed for weeks. All of a sudden, my phone restarts itself into an infinite boot loop (doesn't go past the SAMSUNG Galaxy S 4 screen).
I have tried EVERYTHING. Restoring an old nandroid backup, reflashing CM11 and Gapps - nothing.
Every time I try to install the stock firmware - both L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 (acquired directly from Samsung) and L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 (again, direct download) it always fails at the same spot:
I flashed the MK2 modem when flashing the MK2 stock ROM... no dice. Same thing for the NAE modem + ROM.
Please, help me. I have no clue what to do at this point. The only backup I have, which is of Android 4.2.2, also doesn't work. Same bootloop.
I have tried all of the above things with three different version of Odin: 1.805, 3.04 and 3.07.
I re-installed the Samsung USB drivers, in case that was the issue.
I am completely clueless.
The main problem (I believe) is this:
aboot.mbn
Please and thank you.
Click to expand...
Click to collapse
I know this sounds redundant or maybe you've done this too.
Charge the phone fully - while powered off. Take the battery out for 15 earth minutes. Then run Odin as administrator on your PC 1st (use the full NAE tar put in the PDA slot (in the dev section read the thread for some other tips too)) Then put phone into download mode and then plug into computer
ALSO I know this too sounds silly, but try a brand new USB cable. Can't tell you how many times that has caused problems for me.
Good luck
leaderbuilder said:
I know this sounds redundant or maybe you've done this too.
Charge the phone fully - while powered off. Take the battery out for 15 earth minutes. Then run Odin as administrator on your PC 1st (use the full NAE tar put in the PDA slot (in the dev section read the thread for some other tips too)) Then put phone into download mode and then plug into computer
ALSO I know this too sounds silly, but try a brand new USB cable. Can't tell you how many times that has caused problems for me.
Good luck
Click to expand...
Click to collapse
Thank you for such a quick response!
The phone won't go into the "charging mode" which I know is what you're talking about
The USB cable is fine, every time I flash one of the stock ROMs on the phone I have to re-flash the recovery, so we can cross that one off the list.
Am I not using the correct tar file? The file was zipped in a file entitled "Samsung-Updates.com-SPH-L720-SPR-L720VPUAMDC-1365579188.zip" which I downloaded yesterday.
It's charging now in Philz Recovery. Once it's at 100%, I will take out the battery for 15 minutes (hell, probably even 30! lol) and see what happens.
Any other suggestions my friend? Once again, thank you!
rpnunez said:
Thank you for such a quick response!
The phone won't go into the "charging mode" which I know is what you're talking about
The USB cable is fine, every time I flash one of the stock ROMs on the phone I have to re-flash the recovery, so we can cross that one off the list.
Am I not using the correct tar file? The file was zipped in a file entitled "Samsung-Updates.com-SPH-L720-SPR-L720VPUAMDC-1365579188.zip" which I downloaded yesterday.
It's charging now in Philz Recovery. Once it's at 100%, I will take out the battery for 15 minutes (hell, probably even 30! lol) and see what happens.
Any other suggestions my friend? Once again, thank you!
Click to expand...
Click to collapse
If your phone had an MJA or later - MK2 or NAE bootloader you CANNOT flash any Odin ROM previous because of the Knox bootloader.
You're trying the MDC - that won't work.
Keep the phone charging and try the NAE
Here is a similar post and similar problem with my response (includes the link to the NAE .tar)
leaderbuilder said:
If your phone had an MJA or later - MK2 or NAE bootloader you CANNOT flash any Odin ROM previous because of the Knox bootloader.
You're trying the MDC - that won't work.
Keep the phone charging and try the NAE
Here is a similar post and similar problem with my response (includes the link to the NAE .tar)
Click to expand...
Click to collapse
Ahhh... that makes sense.
I just tried flashing the MDC modem, because I believe my 4.2.2 backup is on MDC...but now I have the weirdest message saying "System software not authorized by Samsung has been found on your phone".
Now I think I messed things up...
I'm downloading the NAE file. Hopefully flashing that will fix everything.
Why can't I just delete *everything*? Like a reformat on a Windows PC? Literally, destroy everything - and just flash the stock NAE firmware?
I appreciate your help now so much my friend. Thank you.
rpnunez said:
Ahhh... that makes sense.
I just tried flashing the MDC modem, because I believe my 4.2.2 backup is on MDC...but now I have the weirdest message saying "System software not authorized by Samsung has been found on your phone".
Now I think I messed things up...
I'm downloading the NAE file. Hopefully flashing that will fix everything.
Why can't I just delete *everything*? Like a reformat on a Windows PC? Literally, destroy everything - and just flash the stock NAE firmware?
I appreciate your help now so much my friend. Thank you.
Click to expand...
Click to collapse
Because of the Knox bootloader you can't wipe everything. Read my other thread as to why. Knox bootloader is in the chips security container and once tripped is not, as of now removable.
Flashing the tar should get you all good to go.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Because of the Knox bootloader you can't wipe everything. Read my other thread as to why. Knox bootloader is in the chips security container and once tripped is not, as of now removable.
Flashing the tar should get you all good to go.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to successfully flash to the TAR you linked me to!
However, I am still stuck in a bootloop...
It won't even let me boot into recovery.
You've been such a help buddy. Any other ideas?
If the tar flashed successfully try power off completely.
Then boot to stock recovery - Power on + Volume up (kind of tricky on the S4, I often miss the right length of time to hold both kind of freaks me out/pissed me off, but eventually after many battery pulls I'll get it on boot. )
Then try a factory reset.
Edit if that fails then try this also:
You can also try to Odin a custom recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/philz_touch_6.08.9-jfltespr.tar.md5 [download mode, odin in PDA slot - do NO check f-reset or autoreboot - once odin is finished do a battery pull]
Then try to get to custom recovery and flash the stock NAE kernel if it doesn't boot
Here's Philz http://forum.xda-developers.com/showpost.php?p=51411121&postcount=1955
leaderbuilder said:
If the tar flashed successfully try power off completely.
Then boot to stock recovery - Power on + Volume up (kind of tricky on the S4, I often miss the right length of time to hold both kind of freaks me out/pissed me off, but eventually after many battery pulls I'll get it on boot. )
Then try a factory reset.
Edit if that fails then try this also:
You can also try to Odin a custom recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/philz_touch_6.08.9-jfltespr.tar.md5 [download mode, odin in PDA slot - do NO check f-reset or autoreboot - once odin is finished do a battery pull]
Then try to get to custom recovery and flash the stock NAE kernel if it doesn't boot
Here's Philz http://forum.xda-developers.com/showpost.php?p=51411121&postcount=1955
Click to expand...
Click to collapse
Can't get to stock recovery - it just says "RECOVERY BOOTING..." then reboots.
Installed Philz Recovery, installed CF-Auto-Root since Philz complained that I wasn't rooted, when I tried to flash the NAE kernel, it says:
Using legacy property environment for update-binary...
Please upgrade to latest binary...
Currently installing kernel
format() expects 4args, got 5
E:Error in /storage/sdcard1/Negalite_NAE_Stock_Kernel.zip (Status 7)
Installation aborted.
Click to expand...
Click to collapse
Why me
That's okay. Status 7 is an updater script error. There are a few things.
Let's try another kernel.
OR another recovery (I keep multiple recoveries on my externaSD for this reason.
Here is Reverepats TWRP You can flash the recovery from recovery and reboot recovery. Say that five times..
Since you did get to custom recovery you're heading the right way.
Try flashing the stock kernel from the TWRP recovery and
You can try another kernel too.
Ktoonsez' latest kernel is here You can grab the 4.4 TW one (take note of the build prop edit you may have to do to get wifi working - that'll require rooting (cf-autoroo) and a root explorer to get to it)
All seems kernel related to me.
Here is a vid on disabling script checking tha may work too. I relize that it's for full ROMs but it may help.
leaderbuilder said:
That's okay. Status 7 is an updater script error. There are a few things.
Let's try another kernel.
OR another recovery (I keep multiple recoveries on my externaSD for this reason.
Here is Reverepats TWRP You can flash the recovery from recovery and reboot recovery. Say that five times..
Since you did get to custom recovery you're heading the right way.
Try flashing the stock kernel from the TWRP recovery and
You can try another kernel too.
Ktoonsez' latest kernel is here You can grab the 4.4 TW one (take note of the build prop edit you may have to do to get wifi working - that'll require rooting (cf-autoroo) and a root explorer to get to it)
All seems kernel related to me.
Here is a vid on disabling script checking tha may work too. I relize that it's for full ROMs but it may help.
Click to expand...
Click to collapse
I tried flashing Recerepats TWRP via Philz... no dice. I guess it's just not my day lol. I tried Odin'ing openrecovery (2 versions) and noooo dice.
So I went back to the Philz 6 (I tried flashing Philz 5 and.. no luck), flashed the kernel you linked to, it flashed fine.
....still in a boot loop. I'm so sorry for taking up your time buddy, you've been such a great help.
I'm guessing I should re-odin the NAE tar now, since the kernel has been modified?
I feel like a mechanic who can't change his own car oil lol. I'm a programmer and write PHP/JavaScript daily, none of these things scare me - but nothing is working!
Ya,
I'd try re-odining the tar again.
Just put in the pda slot as usual, but this time try unchecking the Auto Reboot and F. reset time. and when done just battery pull and restart.
Edit/Add:
Oh and you might still have to 'factory reset' from stock recovery' if it gets stuck on bootloop.
BUT remember the first boot takes a freaking long time - 5-10 earth minutes for first boot! wait and then try the reset if it doesn't get past it
leaderbuilder said:
Ya,
I'd try re-odining the tar again.
Just put in the pda slot as usual, but this time try unchecking the Auto Reboot and F. reset time. and when done just battery pull and restart.
Edit/Add:
Oh and you might still have to 'factory reset' from stock recovery' if it gets stuck on bootloop.
BUT remember the first boot takes a freaking long time - 5-10 earth minutes for first boot! wait and then try the reset if it doesn't get past it
Click to expand...
Click to collapse
Just finished re-odinining the tar file. Nothing. Still in a bootloop.
How can my device be so ruined? All I would do is install new CM nightlies - the right way, too. I remember I was in a shopping market yesterday, everything was nice and dandy, and when I get in my car, this bootloop thing started happening,
I'm baffled by this... I really, really am. With your help, along with other things I've tried, I've tried everything under the sun.
The only thing I haven't thought of is using ADB/working on the phone via command line.
What do you think?
Worth a shot.
One thing though.
Before you give up pull the battery again for about 15+ minutes. then put it back in and then try to Odin. I had to do that on my old Epic a few times.
Couldn't hurt to try adb.
One last thing - in custom recovery (philz say) wipe the cache and then wipe the Dalvik cache (in advanced I think) then try booting again. Sometimes that helps bootloops.
But for sh*ts and giggles how about trying to install a custom ROM? Maybe Negalites's Here's his release version
To install boot to Philz recovery; wipe cache, wipe dalvik and the wipe to install new ROM/Factory reset then select the negalite.zip and run throught the install.
@rpnunez haven't seen a post back. Hope you got it going.
leaderbuilder said:
@rpnunez haven't seen a post back. Hope you got it going.
Click to expand...
Click to collapse
Leaderbuilder, thank you so much for following up like that - it really means alot!
Unfortunately, I tried your latest suggestions, and still nothing - both unchecking Auto Reboot and F. Reset Time + battery pull for 15 mins, and the wiping of the cache and dalvik cache.
I should try flashing a custom ROM, but may I ask why flashing CM + Gapps would be different? I've tried flashing CM countless times :/
Also, could any of this be happening because of Knox? I've read about Knox, but I don't really know much about it. Before I posted this thread, I downloaded a multi-tool kit (Dr. Ketan's Multitool v6 - I followed this guide: http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/) and it was to "reset" the Knox counter, but it didn't get me out of the boot loop.
I just wish there was a "Format" function for my phone lol. Is there anything else you can think of? I really don't understand how a phone can get so... destroyed. No water damage, no fall, nothing - from one moment to the next, boot loop.
Would the stock recovery help? When I flash the NAE tar, I hold Volume Up + Power, I see "RECOVERY BOOTING..." and then... boot loop! Can that give any clues?
What's odd is that it won't go past the Samsung Galaxy S4 screen - it's like a computer not being able to go past the BIOS screen.
Once again, I greatly appreciate your time and effort.
Well you can Odin a custom recovery again. And wipe the crap out of everything - caches, system, DATA for sure do that, wipe to install new ROM. (if you use TWRP - there is an option to use rm vs format which may help in advanced I think.)
Then flash Philz maybe and again try another ROM like Negalite
I'm pretty stumped but that's what I'd do - wipe the sh*t out of it, reboot recovery wipe again then try installing ROM.
leaderbuilder said:
Well you can Odin a custom recovery again. And wipe the crap out of everything - caches, system, DATA for sure do that, wipe to install new ROM. (if you use TWRP - there is an option to use rm vs format which may help in advanced I think.)
Then flash Philz maybe and again try another ROM like Negalite
I'm pretty stumped but that's what I'd do - wipe the sh*t out of it, reboot recovery wipe again then try installing ROM.
Click to expand...
Click to collapse
It's really odd that I can't flash any recovery other than PhilZ "philz_touch_6.25.0-jflte.tar.md5". I can't even flash a slightly older version, "philz_touch_5.18.2-jfltespr.tar.md5". Hell, I've tried all of these:
OUDHS-Recovery-jfltespr-1.0.3.3.tar
openrecovery-twrp-2.7.0.1-jfltespr.tar
openrecovery-twrp-2.6.3.0-jfltespr.tar
clockworkmod_6.0.3.2_jfltespr.img
GalaxyS4-CWM-6.0.4.4-Sprint.tar
openrecovery-twrp-2.6.0.0-jfltespr.tar
And NONE of them work.
In PhilZ, I formatted everything (wipedata, wipe to install new rom, formatted /boot, /preload/ cache, /system, everything that can be formatted - flashed NAE tar again and nothing.
I'm going to go ahead and try to flash Negalite's ROM. I'm about to just take the damn phone to Best Buy because luckily have I have insurance on it... but geez, I really cannot fathom what is going on with this device. But I still want to try a few more things.
Do you know of any ADB commands/guides or something that can perhaps generate a "log file" as to what's going on during the boot process? Or something to that effect?
Thank you for your time my friend. :angel:
Edit/Update:
Flashed Negalite's ROM... nothing. I'm getting tired of looking at the Samsung Galaxy S4 boot screen lol.
Would using "Re-partition" help? Maybe something got partitioned? I'm really running out of ideas..
rpnunez said:
It's really odd that I can't flash any recovery other than PhilZ "philz_touch_6.25.0-jflte.tar.md5". I can't even flash a slightly older version, "philz_touch_5.18.2-jfltespr.tar.md5". Hell, I've tried all of these:
OUDHS-Recovery-jfltespr-1.0.3.3.tar
openrecovery-twrp-2.7.0.1-jfltespr.tar
openrecovery-twrp-2.6.3.0-jfltespr.tar
clockworkmod_6.0.3.2_jfltespr.img
GalaxyS4-CWM-6.0.4.4-Sprint.tar
openrecovery-twrp-2.6.0.0-jfltespr.tar
And NONE of them work.
In PhilZ, I formatted everything (wipedata, wipe to install new rom, formatted /boot, /preload/ cache, /system, everything that can be formatted - flashed NAE tar again and nothing.
I'm going to go ahead and try to flash Negalite's ROM. I'm about to just take the damn phone to Best Buy because luckily have I have insurance on it... but geez, I really cannot fathom what is going on with this device. But I still want to try a few more things.
Do you know of any ADB commands/guides or something that can perhaps generate a "log file" as to what's going on during the boot process? Or something to that effect?
Thank you for your time my friend. :angel:
Edit/Update:
Flashed Negalite's ROM... nothing. I'm getting tired of looking at the Samsung Galaxy S4 boot screen lol.
Would using "Re-partition" help? Maybe something got partitioned? I'm really running out of ideas..
Click to expand...
Click to collapse
Okay, by chance is your device the T model? - the Triband one?
Because I can see and think of no reason why all this wouldn't work unless it was not the Sprint SPH-L720.
leaderbuilder said:
Okay, by chance is your device the T model? - the Triband one?
Because I can see and think of no reason why all this wouldn't work unless it was not the Sprint SPH-L720.
Click to expand...
Click to collapse
I do believe it is the Triband one... it has a SIM card, and I remember seeing options like "GSM, GSM/CDMA, GSM/CDMA/LTE" when selecting network mode or w/e it's called. Is there a way to determine if it is Triband?
Hello, I am relatively inexperienced when it comes to flashing and have managed to brick my s5(rogers(SM-G900W8)canadian). I have looked around and it seems as though in order to get my phone to work I need a pit file for my phone. Problem is, I can't find one. If anyone could help it would be greatly appreciated. Thanks. by the way I have rooted and enabled usb debugging prior to being bricked
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
so that should work?
Well that's the PIT file for your model phone, whether or not it unbricks it depends on what you did to brick it
I bricked it by attempting to flash philz touch recovery in odin 3.09 and it failed. Now I have the message:"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." on my phone, I tried doing exactly that but kies detects my phone but never finishes loading it up. So I tried flashing the stock firmware for my device model and got the same issue I did when attempting to flash the recovery. As far as i know I didn't do anything wrong as i was very careful to select the right files, etc. but clearly I did.
Well you've got nothing to lose by trying the PIT file
Not flashed PIT before so read up on exactly how to do it first, this is the thread I got the link for your phone from
http://forum.xda-developers.com/showthread.php?t=2737448
Tried flashing the file and that failed as well... not looking too good.
I guess my phone's useless now.
Did you check the "Re-Partition" in ODIN?
Are you using the latest version of ODIN3 (3.10.6) ?
Try ODIN3 version 3.0.7 too
(Obviously) Got phone in download mode
Tried just flashing a stock ROM from sammobile
Tried flashing the stock ROM along with the PIT file & Stock ROM together?
tried it all, when trying to flash the pit file as well though it gives me "SECURE CHECK FAIL : PIT" on my phone. whenever I try to flash it it always fails at system.img.ext4 with Complete(Write) operation failed.
I think I know the issue now, I'm using VMware, which apparently doesn't work. Will try on a windows pc in a while. thanks
Ah right, yea always best from a native PC
Let us know if you get it working
It worked and then I installed the newest cyanogenmod.
Alas, let me tell you my tale of woe. And just so you know, I have pretty much called myself every name in the book.
My wife and I both had S4's (I337). We have since moved on to other phones but both of us have kept our S4's. We have decided to give my daughter my wife's old S4 phone. Let me set the stage for you: the phone is (was) already rooted and I had CWM recovery on it. I was also using @iB4STiD 's GoldFinger ROM on both phones. They had the look of the S5. I decideded to go ahead and update the phone before we gave it to her. I went into the ROM and wiped the cache and did the "Install new ROM" box. Everything went smoothly. Well, to my horror, I had forgot the most crucial part -- putting the GoldenEye ROM onto the phone!! I tried to mount the SD card via USB and it would not mount. I then hit the back button and went too far back and the phone rebooted. To add insult to injury, several months ago, my wife's phone went thru a horrible boot loop. Come to find out, the power button was messed up. I had to open the phone up and completely remove the power button! So I cannot boot into recovery since I have no power button to hold.
So I thought I would try ODIN. If I pop the battery and put it back in, hold the volume down button and plug the USB cable in, I can get the phone to boot up and go into ODIN. But now, the ODIN files keep failing saying:
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I know, XDA. I should feel ashamed. But as a father I beseech you on behalf of my daughter to help me get out of this jam.
PS: If you need any information, my other S4 was flashed with the same ROM and is nearly identical to my wife's S4.
Any idea which bootloader version is on the phone?
audit13 said:
Any idea which bootloader version is on the phone?
Click to expand...
Click to collapse
Thankfully still MDL. I never updated the bootloader nor had to worry about safestrap.
I DID IT! I went to SamMobile, made an account, and downloaded the firmware for the phone. Flashed it with Odin and now I'm back in business.
Glad you got it working. I was going to suggest flashing a stock rom via Odin since your bootloader is unlocked.
audit13 said:
Glad you got it working. I was going to suggest flashing a stock rom via Odin since your bootloader is unlocked.
Click to expand...
Click to collapse
Well, now I have another problem. It loaded the original recovery. The recovery I had was CWM with touch since the phone does not have a working power button. I used ADB to log into recovery but I get hung up there without my power button to select the options. I then tried flashing a recovery with ODIN but again I fall into the Auth Fail. I had to go to work but I was reading about putting the recovery.img file in the root of the /sdcard and using Terminal Emulator to flash it in. Any thoughts on that? I also had tried fastboot but it said it was waiting for device and nothing happened.
Try flashing TWRP or CWM using Odin by doing this:
Open Odin, uncheck everything except f.reset time, flash recovery, when you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, boot into recovery using button combination.
audit13 said:
Try flashing TWRP or CWM using Odin by doing this:
Open Odin, uncheck everything except f.reset time, flash recovery, when you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, boot into recovery using button combination.
Click to expand...
Click to collapse
That's the part I'm having problems with. It fails during flashing the recovery. It will say FAIL (Auth). I will probably go ahead and try TWRP if I can find a .tar.md5 file of it. That's the other issue: the CWM file I downloaded was an .img file. I used a tool I found here on XDA to convert it to a .tar.md5 file but it still failed. If I can get a recovery that works via the touchscreen I'll be golden.
Use them latest twrp tar file. Then use twrp to flash the latest img file.
audit13 said:
Use them latest twrp tar file. Then use twrp to flash the latest img file.
Click to expand...
Click to collapse
Do you think this one will work even though it's originally for I9500 series? http://forum.xda-developers.com/showthread.php?t=2375908
Isn't this for the att: https://dl.twrp.me/jflteatt/
Cygwin can convert img to tar.
Hi everyone,
I'm owner of a N9005 International on 5.0 with some problems of media processes. My Files doesn't open in your own app, only in File Explorer. Already Update and Hard Reset the same but problem remains.
I'll try to flash a custom ROM, but i found some problems to make root with CF Auto Root on my device. When i try do the root my odin (Versions 3.09 and 3.10) presents the message:
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
I have all drivers with Kies and Smartswitch.
USB Debbuging is on and Download Mode is on the screen.
I already reboot my PC, changed the cable and USB ports
Recently i Wipe and restore my Note3.
Anyone got an idea?
There's another way to do root without Odin?
Thanks!
Sorry for my poor english :/
Use supersu zip to root .
Its found under SEARCH or GOOGLE .
Have you tried flashing a stock ROM from sammobile.com? If flashing a stock ROM with Odin fails, try different USB ports and USB cables.
Use differnet ROMs, such as firmwares from sammobile , this sometimes happens when you have hardware failure , i mean cable . Try using another USB Cable , I had the same problem but no more with my current cable
audit13 said:
Have you tried flashing a stock ROM from sammobile.com? If flashing a stock ROM with Odin fails, try different USB ports and USB cables.
Click to expand...
Click to collapse
Huy Hyner said:
Use differnet ROMs, such as firmwares from sammobile , this sometimes happens when you have hardware failure , i mean cable . Try using another USB Cable , I had the same problem but no more with my current cable
Click to expand...
Click to collapse
Tks Guys,
Already tryi this. With no sucess,
but, reading some topics here in xda, one comment called my atention. I disabled the Reativation Lock and works. I don't know if this really was the problem. But, it works. Tks a lot. :good:
I had a note 3 bricked by erasing NAND in Odin. eventually I lost access to my phone and I was not able to download the firmware by odin through single file method.
but I searched for tried for 12 hours and found note 3 stock roms here.
You can do that un-brick to stock rom back by finding individually all essential file [AP, CSC, BL, CP] and installing by the odin.
I am very new to android world so if it look dumb to you. ignore. Thumbs for hard work.