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.
Related
Forgive my noobishness. I've actually lurked xda boards for years and used the EXCELLENT user made guides for all my phones. However, I'm at a complete loss and nothing I've searched, read, or tried has worked and it's consumed my entire day and left me with no phone at all. I cannot believe this phone can be dead unless there's some physical problem so I'm really hoping someone can walk me back to normal.
I bought a new S4 from T-Mobile on Labor Day (obviously I'm in the US). 2 days ago I rooted it successfully using Jimmy Mcgee's video and the various links including mattlgroff's and k0nane's threads. No problems whatsoever. After I did that I used Ti Backup and backed up the apps just in case, then I ran the moderate version of the Truly Clean script and did a factory reset. Everything was perfect. Then...
My wireless data stopped connecting. But that's not my current problem.
I decided to unroot and go back to factory to a) see if something I did was causing the data issue or b) take it back for an exchange at the store. I started with the K0nane and the Samersh72 guides, but frankly tried so many things and failed I don't know were I went wrong. First I tried M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Then I tried Samsung-Updates.com-KERNEL-SGH-M919-TMB-M919UVUAMDL-1366964131.tar
Then I tried the one I did to root it OUDHS-Recovery-jfltetmo-1.0.3.3.tar
Mostly I have gotten a NAND writing fail in Odin with everything I tried (yes I tried making sure Kies is off, the original usb cable, and another PC) which then locks me out of the recovery boot screen and gives me some yellow triangle between a phone and a pc with an error about the stock firmware and tells me to connect to Kies. I can fix that by flashing this PIT file CSB_signed_Fusion3_EUR_0325_V2.pit which allows me to go back to the OUDhs recovery screen.
Also Kies will no longer connect to this device and it says driver install failure when I connect it to the PC (except it stell charges, using the stock cable still).
Dear god someone help me, and I will buy you a beverage. I'm doing instant email notifications of replies. PLEASE.
I'm not sunk yet. I'm rereading the FAQs and guides and I'm going to start over to where I was able to get the rooted version to work. I know the CWM recovery is working so we'll see.
Pull out battery for a while, then go to download mode (vol down+home+power) and flash stock fw in odin.
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2
diodaq said:
Pull out battery for a while, then go to download mode (vol down+home+power) and flash stock fw in odin.
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Ok I will try that. Also I am now trying to flash Samsung-Updates.com-SGH-M919-TMB-M919UVUAMDL-1366964131\M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
I am getting a little farther in the Odin process but it still says fail right after
aboot.mbn
Also I originally followed Jonny's video and only flashed the cwm custom recovery though odin. I flashed the rooted zip file from my phone's internal sd card like in the video. Now I can't get to the internal memory so I tried saving the zip file (the one I used to root it) on the ext sd card. I'm unable to flash that rooted zip from the ext sd card because the phone wants to reboot as soon as it starts doing so.
Is there a way to flash that rooted zip file (or a stock one) from an external sd card?
Is there a way to flash that rooted zip file through odin?
All you have to do is get into download mode and flash stock mdl tar with odin. After it's finished, it'll go into recovery by itself and wipe some small cache partition by itself, after it does that, hold onto the volume up button and get into recovery again and do a factory reset. This is so you don't go into a bootloop. Now get CF auto root and flash it so ur rooted. Next flash a custom recovery and ur all set. It's really easy to do.
norml said:
All you have to do is get into download mode and flash stock mdl tar with odin. After it's finished, it'll go into recovery by itself and wipe some small cache partition by itself, after it does that, hold onto the volume up button and get into recovery again and do a factory reset. This is so you don't go into a bootloop. Now get CF auto root and flash it so ur rooted. Next flash a custom recovery and ur all set. It's really easy to do.
Click to expand...
Click to collapse
So far I have been totally unable to get odin to flash a stock tar or any tar since I did the first one 2 days ago. Always, fail.
mattwood440 said:
So far I have been totally unable to get odin to flash a stock tar or any tar since I did the first one 2 days ago. Always, fail.
Click to expand...
Click to collapse
Are you loading the stock tar by clicking PDA?
norml said:
Are you loading the stock tar by clicking PDA?
Click to expand...
Click to collapse
Yes. Also when it fails, it locks me out of the recovery mode. Can you tell me what happens when you flash a new PIT file? Doing that alone does not get a FAIL message and it brings back the recovery screen. However, when I select the pit file it automatically selects the re-partition option which the k0nane says is a no-no (at least for flashing the pda, not sure about the pit which is why I'm asking).
mattwood440 said:
Yes. Also when it fails, it locks me out of the recovery mode. Can you tell me what happens when you flash a new PIT file? Doing that alone does not get a FAIL message and it brings back the recovery screen. However, when I select the pit file it automatically selects the re-partition option which the k0nane says is a no-no (at least for flashing the pda, not sure about the pit which is why I'm asking).
Click to expand...
Click to collapse
Pit file basically means repartitining the storage chip of your device. Yes odin will automatically check repartition when flashing pit files. Flashing pit file is serious business. I recommend following the unbrick/ unroot thtead in the general section. Its pretty precise and I think since you are getting repeated fails in odin you will have to flash pit file.
You will be fine if you follow the instructions there precisely.
Sent from my GT-I9500 using xda app-developers app
OMG it worked. K0nane's procedure worked on a different pc. Dowloaded a fresh Kies but didn't install any of the extra stuff with it. Downloaded, extracted, and ran odin as admin. Hooked it up. Downloaded and extracted the UVUAMDL tar. Put that in the pda box and hit start. Mine would immediately FAIL but this one kept working, and working, and working and reboote. Why why why? I've been at this for about 16 hours. That makes no sense. Thanks anyway. I'll try the other root method when I'm feeling brave again.
Hello all!
First off I would just like to say thank you, thank you, thank you. I have been a long time lurker on these forums (since the evo) and have gotten a lot of useful information from here. Now to my issue. I have had no phone for two weeks now, and have been doing search after search. I upgraded my phone to 4.3 (it was mk2) and rooted it via motochopper. So my dumbass tried to flash a custom rom with kn0x0ut and it failed. The phone rebooted and now will boot up to the samsung custom screen. You can hear the att boot up sound but no image. I can get into odin mode and stock recovery. When I am in odin it says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMC BURST MODE enabled
I have tried sideloading the stock MJ9 and MK2 files to no avail. I really hope somebody can help me, I don't know how much longer i can go without a phone. Thanks guys and Merry Christmas!!!
yea sounds like bricked you cant flash roms on 4.3 yet take it to best buy that has a samsung center and just tell them samsung sent you here because my phone all of a sudden was acting up and they will flash it back to factory for you thats what i had to do
gtj0 said:
OK, If you're stuck with an incomplete flash, here are some steps you can try to get to MJ9...
These instructions assume you started with MJ6.
First, make sure you can boot into recovery. If not, download and apply the MJ6 recovery.
recovery-mj6.tar.md5
It should apply without error. If not, report the failure.
Download and extract the following files...
mf3-emergency-part-1.tar.md5.7z
mf3-emergency-part-2.tar.md5.7z
If you don't already have it, download the mf3-mj9 update file...
update-mf3-mj9.zip
Start Odin, connect your phone and boot into Download mode.
Flash mf3-emergency-part-1.tar.md5 which contains modem.bin, NON-HLOS.bin and system.img.ext4.
The flash of system.img.ext4 WILL FAIL at the end. That's OK.
Reboot the phone back into Download mode and restart Odin.
Flash mf3-emergency-part-2.tar.md5 which contains cache.img.ext4.
The flash WILL FAIL at the end. That's OK.
The phone should now reboot to recovery by itself and apply a small update. If it fails, stop and report.
The phone should now reboot to a black screen with the pulsing notification LED.
Reboot into recovery mode and flash update-mf3-mj9.zip. I recommend sideloading instead of flashing from sdcard because the sdcard method reboots the phone whether the update was successful or not and you lose the error messages.
Reboot the phone and let it initialize.
You should now have MJ9.
Click to expand...
Click to collapse
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
I was on MK2 using the 3.7 beta of SS when I couldn't get it to boot anymore. Tried the modified method outlined above, everything worked except after step 7, it never rebooted to recovery on it's own and installed a small update. Decided to try Kies, says it can do emergency firmware recovery but it hasn't worked yet. Any help would be appreciated as I'm not sure I can get the handset replaced since I got it at Walmart.
It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
sl1200md3 said:
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
Click to expand...
Click to collapse
dolph8886 said:
It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
Click to expand...
Click to collapse
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!
FINALLY
dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
FINALLY LONG SEARCH OVER FOR THIS FIX JUST ONE QUESTION WILL THE RECOVERY FAIL AS WELL?
tonyc0642 said:
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!
Click to expand...
Click to collapse
hi i have the exact same problem....i dont know how to start adb on windows 7...arrgh...
Thanks to the everyone for this
It saved my ass..I put the zips on a sd and installed.Back on mk2 and rooted.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I tried the above mentioned but after I flash the second file and reboot, it goes into kies , no recovery mode. Odin is still available. Also thanks for all the quick responses fellas yall are the best.
***UPDATE*** flashed the recovery but the sideload failed. Tried to turn it on and the Samsung lolgo came on, then went black. After a a few minutes the phone pops up on the computer and I can access the internal phone memory and the sd card.
I am really not sure, I believe that it will work if you do this process again.
No Idea if this makes any difference but, pay close attention to the process at least until the sideloading of the update.
Do not let the device attempt to boot with this firmware mismatch as this may cause issues. (This is the only conclusion I can come to as this process does work)
If the device automatically reboots then press and hold volume up to enter recovery or volume down to enter download mode.
If manual reboot or powering on then press and hold volume up or down respectively then press power until the device starts and release power button to avoid a reset.
SOLVED!!!
Thank you so much @dolph8886!!!1 You are the BEST!!! :good: :victory: :highfive:
This helped me, fixed my softbrick, hope this helps! Remember to thank the author if it works
http://forum.xda-developers.com/showthread.php?t=2621279
ok here it goes i tried to flash twrp using goo but now i have no stock recovery can someone help me please im on mk2 running 4.3 and rooted
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?
I need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
donelam304 said:
I need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
Click to expand...
Click to collapse
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Bryotch said:
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Click to expand...
Click to collapse
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
donelam304 said:
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
Click to expand...
Click to collapse
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Bryotch said:
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Click to expand...
Click to collapse
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
donelam304 said:
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
Click to expand...
Click to collapse
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
donelam304 said:
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
Click to expand...
Click to collapse
thanks so much by the way. I greatly appreciate the assistance.
My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Re-download the stock rom and flash it
Meboyzram said:
Re-download the stock rom and flash it
Click to expand...
Click to collapse
i did that lol thats when it says "model dismatch fail"
Do you have custom recovery?
Do you have a custom recovery?
Do you have the right and the newest Odin Version?
Did you try it with another transfercable or USB-Port?
Do you have the newest samsung drivers?
Did you have any Odin problems like this before?
My suggestion:
Just do a full wipe on your phone. Downlad the newest Odin Version. Get your device into download mode (maybe try different transfercables or USB Ports and the newest samsung drivers) and see if it works now.
If yes, flash the right Bootloader and Modem for your device and then flash the rom you wanted to flash.
If this didnt work, (and you have a custom recovery) try to reinstall the rom without any backups via the recovery at first and check afterwards, if the device is now recognized by Odin.
Good luck
JustAnotherAndroid said:
My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Click to expand...
Click to collapse
I guess you still have twrp installed.
1. Step: go to TWRP and wipe everything except your SD-Card
2. Step: enter download mode on your device and then plug your usb in (maybe try a different usb-port or even another computer, or another usb cable)
3. Step:Flash the newest bootloader & modem in one step.
4. Step: Enter TWRP again and flash the firmware.zip via the installation process
I dont have TWRP, but i got it fixed, somehow my roomate got it, thanks anyways guys
So all he got was my phone to turn on, im still having this model dismatch fail issue..
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
ProtoDeVNan0 said:
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
Click to expand...
Click to collapse
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
If system.img by itself will flash successfully and Your phone won't boot then add slowly more files to that tar file (boot.img, recovery.img etc)
You could also try looking for a pit file for Your phone and then flash it with it. Pit file usually fixes most problems even broken partitions.
And make sure that You put that tar file in AP/PDA.
If nothing above works then send me screenshots of ODIN and the file that You're trying to flash. Maybe I'll notice something. But I hope You'll fix it
JustAnotherAndroid said:
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
Click to expand...
Click to collapse
So I tried, and i get some invalid file error
These are the files that are in the AP one
https://gyazo.com/a72785631ad62d412a8c40eb464d3126
I found out my problem, i was still uing the modified version of odin that i used to root my phone