So I just attempted to flash my S4 into a newer version. My build is S4 sgh 1337 MK2 from att and I was trying to update to KK so I could install the Hyperdrive rom. I have all my files, and following the instructions it had said that I had to upgrade the baseband from MK2 to NC5. Sure, so I had downloaded a stock rom for NC5 and in the instructions it had said to wipe everything (data, cache,dalvik cache) on the main stock slot (I'm using Safestrap 3.73) and afterwards tried flashing the upgrade but it said unable to open zip file. So I just thought maybe if I swipe to factory reset and then boot up it'll boot up just like new. It didn't, and now I'm stuck on a boot loop or so it seems (It doesn't go through the Samsung Galaxy S4 screen). How can I get out of this? Did I brick it? I was excited to install the rom, and I had read the guide a thousand times and was sure it would work but it didn't.
JavierEGI said:
So I just attempted to flash my S4 into a newer version. My build is S4 sgh 1337 MK2 from att and I was trying to update to KK so I could install the Hyperdrive rom. I have all my files, and following the instructions it had said that I had to upgrade the baseband from MK2 to NC5. Sure, so I had downloaded a stock rom for NC5 and in the instructions it had said to wipe everything (data, cache,dalvik cache) on the main stock slot (I'm using Safestrap 3.73) and afterwards tried flashing the upgrade but it said unable to open zip file. So I just thought maybe if I swipe to factory reset and then boot up it'll boot up just like new. It didn't, and now I'm stuck on a boot loop or so it seems (It doesn't go through the Samsung Galaxy S4 screen). How can I get out of this? Did I brick it? I was excited to install the rom, and I had read the guide a thousand times and was sure it would work but it didn't.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2616221
Check that thread. Follow the instructions under return to stock/Odin. I think nb1 is the best option so you can use towelroot afterwards. I'm pretty sure nc5 is not for an att phone.
Related
Okay,
Ive been rooting and romming for a few years (original Verizon droid, Verizon thunderbolt with Rom Manager (ClockworkMod), An AT&T Samsung SII (ClockworkMod) and was out a year with a stupid RAZR Maxx. Ive used Odin a few times to un-Softbrick my SII so I'm familiar with Odin.
Now I have this Note 3 and of course updated to NC4 before there was root, Just got root about a week ago with Towlroot, added SU, and safestrap 3.75. Ive tried adding Jasmin Rom and Beanstowns rom to my Note but soft bricked it twice and luckily could un-softbrick it with Odin again using the stock tars found here.
I Ive followed the instructions (I believe) for flashing a ROM on my Note but every time it tells me that the flash failed (and of course since Ive wiped everything I have no system left hence my reloading with Odin).
What am I doing wrong?
Ive enabled developer options and checked USB Debugging.
Im on build# KOT49H.N900VVRUVNC4 4.4.2
Thank all.
Using stock rom slot btw.
Sent from my SM-N900V using XDA Premium 4 mobile app
jazzbass_5 said:
Okay,
Ive been rooting and romming for a few years (original Verizon droid, Verizon thunderbolt with Rom Manager (ClockworkMod), An AT&T Samsung SII (ClockworkMod) and was out a year with a stupid RAZR Maxx. Ive used Odin a few times to un-Softbrick my SII so I'm familiar with Odin.
Now I have this Note 3 and of course updated to NC4 before there was root, Just got root about a week ago with Towlroot, added SU, and safestrap 3.75. Ive tried adding Jasmin Rom and Beanstowns rom to my Note but soft bricked it twice and luckily could un-softbrick it with Odin again using the stock tars found here.
I Ive followed the instructions (I believe) for flashing a ROM on my Note but every time it tells me that the flash failed (and of course since Ive wiped everything I have no system left hence my reloading with Odin).
What am I doing wrong?
Ive enabled developer options and checked USB Debugging.
Im on build# KOT49H.N900VVRUVNC4 4.4.2
Thank all.
Click to expand...
Click to collapse
I'm fairly sure any NC4 roms need the NC2 kernel to run properly. Fortunately there is a way to have NC4 firmware with the NC2 kernel. Simply flash the kernel from here and you should be able to flash any kitkat rom for retail note 3.
kinstre11 said:
I'm fairly sure any NC4 roms need the NC2 kernel to run properly. Fortunately there is a way to have NC4 firmware with the NC2 kernel. Simply flash the kernel from here and you should be able to flash any kitkat rom for retail note 3.
Click to expand...
Click to collapse
That's what I thougt but just wanted to be sure, Thank you!! :good:
That didn't work.
Did a flash in Odin to stock N900VVRUCNC4 again
Followed below
Coming From Stock NC4 OTA
Step- 1 - Root Device with TowelRoot
Step- 2 - Install Busybox from play store and install busybox itself
Step- 3 - Install Hashcodes Latest Safestrap (3.75)
Step- 4 - Boot into Safestrap Select Stock Slot
Step- 5 - Wipe Data Factory Reset The Stock Slot
Step- 6 - Flash nc4 deodex rom to the stock slot
Aaaaaaand
Flash failed, So I cant get past step six.
Any Ideas? Also had to re-flash in Odin again cause I wiped factory data, no problems.. lol, just annoying.
Seeing how I don't seem to be locked out of Odin, Isn't there modded TAR I could flash in Odin? or maybe downgrade to NC2?
jazzbass_5 said:
That didn't work.
Did a flash in Odin to stock N900VVRUCNC4 again
Followed below
Coming From Stock NC4 OTA
Step- 1 - Root Device with TowelRoot
Step- 2 - Install Busybox from play store and install busybox itself
Step- 3 - Install Hashcodes Latest Safestrap (3.75)
Step- 4 - Boot into Safestrap Select Stock Slot
Step- 5 - Wipe Data Factory Reset The Stock Slot
Step- 6 - Flash nc4 deodex rom to the stock slot
Aaaaaaand
Flash failed, So I cant get past step six.
Any Ideas? Also had to re-flash in Odin again cause I wiped factory data, no problems.. lol, just annoying.
Click to expand...
Click to collapse
When did you flash NC2 kernel? And no downgrade because of locked bootloader.
Followed the directions and was going to flash it after I tried flashing the rom, tried flashing it first and got an endless verizon logo. I'll try flashing it first again before I load the Rom.
Sent from my SM-N900V using XDA Premium 4 mobile app
Which rom are you trying to install? I'm running JasmineRom 2.0
I tried jasmine and Baja but both fail the flash from safestrap. Tried what was recommended above to install the NC2 firmware but still can't get past the safestrapsafestrap flash. It tells me "flash failed" seconds after I try.
Sent from my SM-N900V using XDA Premium 4 mobile app
Reinstal safestrap, I've never gotten a flash failure?
jazzbass_5 said:
Followed the directions and was going to flash it after I tried flashing the rom, tried flashing it first and got an endless verizon logo. I'll try flashing it first again before I load the Rom.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You after you flash the rom via Safestrap you need to reboot into download mode and flash the NC2 kernel via odin. Did Safestrap say flash failed? Or did you hit the immediate reboot system button?
If it was the latter you need to go back to the Safestrap main menu after flashing and reboot there, it gives you more options.
If it is the former, and there is a problem flashing the rom it may be a bad download. Did you check the md5?
Its the latter of the 2 (therfore I never made it to Odin to flas the NC2 firware), I did not check the md5. I've tried different roms and get a failed flash in safestrap with all of them. I will try again after re-downloading and checking the md and let you know. I'm also going to Uninstall safestrap and reinstall it, maybe roll back from the 3.75 version.
Sent from my SM-N900V using XDA Premium 4 mobile app
If the md5 checks out and it still doesn't flash, you can try reflashing the stock tar via odin > doing a factory reset to clean the system > rerooting > and trying again.
Also try this before wiping system in Safestrap prior to flashing the rom. It is a way to super clean the internal sd.
Ok so now I have a brand new S4. Came in the mail yesterday. So I rooted it. No problem...... went to add a custom rom. (Sacs custom rom to be exact) reboots ok. Galaxy S4 screen. Then the custom rom screen and it stays there........ phone gets extremely hot. I went into recovery. Wiped data. Wiped cache. Wiped dalvik cache. Nothing. So I says ok, forget it. I'm going to Just take the root off and go back to stock firmware. Odin fails to unroot every time. I get Fail (Auth). I downloaded the right tar files to unroot. I even deleted them and re downloaded them. Same results. I'm going crazy because I just got this phone and I can't use it. Any help on what I'm doing wrong? Mind you I've been rooting for years and I've never had this problem before. Also it's a newer S4 that has the Sprint Spark screen. Anything would help. Thanks
sonny82 said:
Ok so now I have a brand new S4. Came in the mail yesterday. So I rooted it. No problem...... went to add a custom rom. (Sacs custom rom to be exact) reboots ok. Galaxy S4 screen. Then the custom rom screen and it stays there........ phone gets extremely hot. I went into recovery. Wiped data. Wiped cache. Wiped dalvik cache. Nothing. So I says ok, forget it. I'm going to Just take the root off and go back to stock firmware. Odin fails to unroot every time. I get Fail (Auth). I downloaded the right tar files to unroot. I even deleted them and re downloaded them. Same results. I'm going crazy because I just got this phone and I can't use it. Any help on what I'm doing wrong? Mind you I've been rooting for years and I've never had this problem before. Also it's a newer S4 that has the Sprint Spark screen. Anything would help. Thanks
Click to expand...
Click to collapse
sph-l720t?? I've heard conflicting reports about compatibility with custom sph-l720 ROMs and spark capable sph-l720t. Best case scenario is you get it to boot, I doubt you will have working Spark functionality, however.
With the galaxy s4 TW custom ROMs you need to reboot recovery after doing your wipes and before flashing your ROM. Also, IIRC, it is best to boot to download mode from fully powered off (maybe even recovery, but I've never needed to do so).
It is also best to be on the newest custom recoveries, like twrp 2.7.0.1 and latest philz (6.25?? not sure on this one)
The steps should look like this.
1 - boot to recovery and do all your wipes.
2 - reboot recovery
3 - flash rom
3.1 wipe dalvik and cache
4 - Boot and let it settle, if you are stuck on the splash screen for longer than 10 minutes chances are it is not going to boot.
Holler back and let us know.
sonny82 said:
Ok so now I have a brand new S4. Came in the mail yesterday. So I rooted it. No problem...... went to add a custom rom. (Sacs custom rom to be exact) reboots ok. Galaxy S4 screen. Then the custom rom screen and it stays there........ phone gets extremely hot. I went into recovery. Wiped data. Wiped cache. Wiped dalvik cache. Nothing. So I says ok, forget it. I'm going to Just take the root off and go back to stock firmware. Odin fails to unroot every time. I get Fail (Auth). I downloaded the right tar files to unroot. I even deleted them and re downloaded them. Same results. I'm going crazy because I just got this phone and I can't use it. Any help on what I'm doing wrong? Mind you I've been rooting for years and I've never had this problem before. Also it's a newer S4 that has the Sprint Spark screen. Anything would help. Thanks
Click to expand...
Click to collapse
If Odin fails then you DID download the wrong tar file. Since you said you just got your phone then you need to know what version you have, there are 2: the L720 & the L720T. If your phone was brand new when you bought it than most likely it is the L720T and none of the roms on this site are compatible with your phone. Some of them will work but you will loose features or have to take extra steps to get the rom working. Once you know which phone you have, you will need to download the correct tar file. If you do have the L720 than the only tar file that will get your phone up and working is the full NAE tar. If you have the L720T then you will need the NC6 ful tar. Any older tar files will fail.
wilzard said:
sph-l720t?? I've heard conflicting reports about compatibility with custom sph-l720 ROMs and spark capable sph-l720t. Best case scenario is you get it to boot, I doubt you will have working Spark functionality, however.
With the galaxy s4 TW custom ROMs you need to reboot recovery after doing your wipes and before flashing your ROM. Also, IIRC, it is best to boot to download mode from fully powered off (maybe even recovery, but I've never needed to do so).
It is also best to be on the newest custom recoveries, like twrp 2.7.0.1 and latest philz (6.25?? not sure on this one)
The steps should look like this.
1 - boot to recovery and do all your wipes.
2 - reboot recovery
3 - flash rom
3.1 wipe dalvik and cache
4 - Boot and let it settle, if you are stuck on the splash screen for longer than 10 minutes chances are it is not going to boot.
Holler back and let us know.
Click to expand...
Click to collapse
it worked!!!!! you are the man!!!! thanks a lot!!!!!
cruise350 said:
If Odin fails then you DID download the wrong tar file. Since you said you just got your phone then you need to know what version you have, there are 2: the L720 & the L720T. If your phone was brand new when you bought it than most likely it is the L720T and none of the roms on this site are compatible with your phone. Some of them will work but you will loose features or have to take extra steps to get the rom working. Once you know which phone you have, you will need to download the correct tar file. If you do have the L720 than the only tar file that will get your phone up and working is the full NAE tar. If you have the L720T then you will need the NC6 ful tar. Any older tar files will fail.
Click to expand...
Click to collapse
cool so where would i find these new tar files?
cruise350 said:
If Odin fails then you DID download the wrong tar file. Since you said you just got your phone then you need to know what version you have, there are 2: the L720 & the L720T. If your phone was brand new when you bought it than most likely it is the L720T and none of the roms on this site are compatible with your phone. Some of them will work but you will loose features or have to take extra steps to get the rom working. Once you know which phone you have, you will need to download the correct tar file. If you do have the L720 than the only tar file that will get your phone up and working is the full NAE tar. If you have the L720T then you will need the NC6 ful tar. Any older tar files will fail.
Click to expand...
Click to collapse
im on L720. now this new NAE tar. will it put me back to stock firmware? because thats what i want to do. no rrot on this phone.
sonny82 said:
im on L720. now this new NAE tar. will it put me back to stock firmware? because thats what i want to do. no rrot on this phone.
Click to expand...
Click to collapse
You can download the NAE tar file from here: http://forum.xda-developers.com/showthread.php?t=2663619
You should use Odin 3.07 or 3.09 to install. Make sure you run Odin in administrator mode.
sonny82 said:
it worked!!!!! you are the man!!!! thanks a lot!!!!!
Click to expand...
Click to collapse
Awesome, dude. Very happy to hear that.
tar files
Where can I get the NC6 tar file. I have the SPH720T , I rooted it fine, then tried to get the native tether to work and now my phone starts up and then gets stuck on the Sprint Sparks screen, I've tried 4 different tar files and all fail. I'm using Odin 3.9
I am currently on the unlocked MDL bootloader, and I am running KANGAKAT 7.0, which is a KitKat 4.4 ROM. My phone is also encrypted, which means that I cannot flash updates due to CWM/TWRP not supporting encryption.
The solution proposed by other users has been to ODIN the stock MK2 recovery onto my phone, use the stock recovery to factory reset my device, then re-flash TWRP and then my new ROM.
However I'm having a problem with these steps. I am able to successfully ODIN the stock MK2 recovery to my device, however whenever I try to boot into recovery, I get the yellow triangle screen stating that I'm running software that is not authorized by AT&T, and stating something to do with my kernel in the top left of the screen.
Is there a step that I am missing? I followed the instructions @ http://forum.xda-developers.com/showthread.php?t=1506697
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
ChrisG683 said:
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
Click to expand...
Click to collapse
Flashing the mdl firmware in Odin will still give you the mdl bootloader. But it'll want to update after you flash so flash another custom rom or freeze the update files before it does so.
Sent from my Nexus 5 using XDA Free mobile app
@ChrisG683 Be sure to turn your wi-fi off and remove your SIM card, that way it can't update. You can put any apps you think you might need on an SD card and install them without having to go to the play store. Once you get things frozen or removed then you'll be good to go. :good:
Thanks guys, I'll be sure to keep that in mind once I get things sorted out.
The newest thing I've figured out is that the MDL stock recovery does not give me the "yellow triangle" error, and it presents me with the option to wipe my device. (I grabbed it from here http://forum.xda-developers.com/showthread.php?t=2429406)
Now I'm just making sure I have a stock MDL ROM ready to ODIN in case I screw up my device =). Hopefully this all works out.
Edit:
Looks like everything went beautifully. The MDL stock recovery wiped my /data partition perfectly, and I was able to reboot into a fresh and clean copy of KANGAKAT 6.0. Then I was able to use a terminal to flash TWRP, did a factory reset, flashed KANGAPOP 1.4, and now you can add me to the list of proud Lollipop users =)
I was able to downgrade the phone to NB1 and root it with Towelroot, and used Safestrap in order to get recovery on the device.
After that, I booted into recovery and installed the GPE 5.0.1 ROM.: http://galaxys4root.com/t-mobile-galaxy-s4-roms/gpe-android-5-0-1-lollipop-rom-for-galaxy-s4/
Now the phone will not go past the S4 splash page, reboots and then goes into the stock recovery. Ive tried factory reset, clearing cache and removing the battery.
Any help is appreciated. I bought this phone for my fiance and am wanting to give it to her soon as a present.
Thank you so much in advance.
I think the problem is that you downgraded.
GDReaper said:
I think the problem is that you downgraded.
Click to expand...
Click to collapse
I couldnt install towelroot on the 4.4.4 version it came with since it said device wasnt supported.
I was following these instructions: http://www.droidviews.com/root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/
It states to downgrade, then root, then go back to the 4.4.4. I thought after the steps I took, I could go straight to a custom ROM.
Thanks
I used CF-Auto-Root to root my device. Since towelroot didn't work for me either.
Maybe the rom did not flash right. Try flashing again.
problem in installing lollipop rom india to samsung i9500
I have installed the newly released lollipop rom to my samsung i9500 through odin. it was successfully flashed but the phone cant restart, it stuck with samsung written on the screen and blue light on...what i should do???
OK, so I recently upgraded to a lollipop ROM on my locked bootloader ATT I337. To get into safestrap now, I have to use NC1 flasher to temporarily flash the NC1 kernel, and then boot into SS, then flash the OC3 kernel to get back. PITA, but it worked. So I tried restoring a backup, and when I rebooted it didn't work (black screen, kept getting FC's of every app, couldn't actually do anything). I rebooted 3 times, after which it seems to be working. Weird. However, if this happens again, how do I get back to safestrap so that I can wipe and reinstall the lollipop ROM? Can I just flash the NC1 kernel via Heimdall/ODIN? If so, which file is it? When I was looking, it seemed like I needed to start from scratch with a full KK flashable package, then upgrade, downgrade, etc, etc.
nola mike said:
OK, so I recently upgraded to a lollipop ROM on my locked bootloader ATT I337. To get into safestrap now, I have to use NC1 flasher to temporarily flash the NC1 kernel, and then boot into SS, then flash the OC3 kernel to get back. PITA, but it worked. So I tried restoring a backup, and when I rebooted it didn't work (black screen, kept getting FC's of every app, couldn't actually do anything). I rebooted 3 times, after which it seems to be working. Weird. However, if this happens again, how do I get back to safestrap so that I can wipe and reinstall the lollipop ROM? Can I just flash the NC1 kernel via Heimdall/ODIN? If so, which file is it? When I was looking, it seemed like I needed to start from scratch with a full KK flashable package, then upgrade, downgrade, etc, etc.
Click to expand...
Click to collapse
Yep, you can flash NC1 kernel in AP slot in ODIN. I'm not sure about Heimdall as I haven't used it.
NC1 kernel: https://www.androidfilehost.com/?fid=23487008491965103
Thanks, hopefully won't have to try it
Just as a bit of an update. I did another safestrap restore, and again ended up booting into the same situation, with black screen, mult FC, etc. Figured out that to exit this, boot into the system bootloader, and from there choose "reboot". For whatever reason, it then boots normally.