Had SafeStrap, went to install a new ROM tonight and didn't notice it was not for NC5. It loaded up a fancy boot animation and wouldn't load, so I wiped it. Put a NC5 rom on my sd card, put it into the phone and now no matter what I can't get past the logo. I can boot into recovery, but when I flash a ROM, same thing it just gets stuck on the logo when booting. What is the next step to unbrick? I see nothing for NC5 around.
thekidkid32 said:
Had SafeStrap, went to install a new ROM tonight and didn't notice it was not for NC5. It loaded up a fancy boot animation and wouldn't load, so I wiped it. Put a NC5 rom on my sd card, put it into the phone and now no matter what I can't get past the logo. I can boot into recovery, but when I flash a ROM, same thing it just gets stuck on the logo when booting. What is the next step to unbrick? I see nothing for NC5 around.
Click to expand...
Click to collapse
if you can't get back into safe-strap then the quickest thing is gonna be to odin back to stock and re root/install bb and SS and then restore from the safestrap backup you didn't make
http://forum.xda-developers.com/showthread.php?t=2735172
flash the nc5-no wipe root with towel root,install superSU,install busybox,and then safestrap
Thanks just wanted to make sure I was on the right track. Turns out I had the odin for mk2 and nc5 which was causing issues. All back up and running now thanks!
Related
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
swing4thefence said:
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
Click to expand...
Click to collapse
Are you installing to the stock slot?
Yes. I have gotten the impression that you can ONLY install to the stock slot.
swing4thefence said:
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
Click to expand...
Click to collapse
Assuming you are using Safestrap correctly.... check your downloads.
Also, slimkat is not compatible with your phone unless you are on mdk which I doubt. There is a process by which you can get the GPE ROM to run on our device if you aren't on mdk but I suspect all you did was flash the zip. We can't use AOSP Roms and if your going by the list of Roms in this thread http://forum.xda-developers.com/showthread.php?t=2297370 you will find most of them to be incompatible. There is no reason that Hyperdrive would get stuck in a bootloop unless there were something wrong with the install or your download.
liljoe727 said:
Assuming you are using Safestrap correctly.... check your downloads.
Also, slimkat is not compatible with your phone unless you are on mdk which I doubt. There is a process by which you can get the GPE ROM to run on our device if you aren't on mdk but I suspect all you did was flash the zip. We can't use AOSP Roms and if your going by the list of Roms in this thread http://forum.xda-developers.com/showthread.php?t=2297370 you will find most of them to be incompatible. There is no reason that Hyperdrive would get stuck in a bootloop unless there were something wrong with the install or your download.
Click to expand...
Click to collapse
Your right. I "Just flashed" I Odined back to stock and tried again, this time following the isntructions for flashing Hyperdrive and it's working fine. Imagine that! All i had to do was read the instructions.
swing4thefence said:
Your right. I "Just flashed" I Odined back to stock and tried again, this time following the isntructions for flashing Hyperdrive and it's working fine. Imagine that! All i had to do was read the instructions.
Click to expand...
Click to collapse
That usually helps ; )
Well here's the story..... So I want to install a custom ROM via SS, the install goes without issue. (I'm running stock NK1 Rooted at the time) I go to install a ROM , and It fails, so I go to reboot the device, and Its back into a bootloop. No big deal, iv'e delt with this before... .I attempt to flash it back to stock NC5 to root it and start over, the flash succeeds, but when I try to boot it i just get the "Samsung Galaxy S4" logo and it sits there doing nothing, and I cant boot into recovery for some reason, just goes back to ODIN mode. Is there anything that can be done?
Alex_Tisler said:
Well here's the story..... So I want to install a custom ROM via SS, the install goes without issue. (I'm running stock NK1 Rooted at the time) I go to install a ROM , and It fails, so I go to reboot the device, and Its back into a bootloop. No big deal, iv'e delt with this before... .I attempt to flash it back to stock NC5 to root it and start over, the flash succeeds, but when I try to boot it i just get the "Samsung Galaxy S4" logo and it sits there doing nothing, and I cant boot into recovery for some reason, just goes back to ODIN mode. Is there anything that can be done?
Click to expand...
Click to collapse
Try a reflash via Odin. It may help. Which image are you flashing?
Sent from the gap between universes.
Hey guys I need some help. I have a Verizon Galaxy S4 with NK1. I rooted it by flashing back to NC5 and then rooting then flashing back to NK1, that part worked perfectly fine. I then wanted to install a recovery so I used the CWM app and thats where things went wrong. After doing so it said it did it successfully but when I clicked boot into recovery so I can install CM12 it did not boot into recovery it instead booted straight to the Odin screen with the Android logo in the middle and below it saying "Downloading", and also has the text in the top left corner.
I am hoping someone has an answer on how to fix this.
Thanks!
Also to add onto that I am able to boot up my phone normally its not that its stuck in a boot loop where I can't get past that point. It only happens when I try to go into recovery mode that it take me to the Odin screen. When I do the steps for booting into Recovery it shows the samsung logo and then the blue text that usually comes up in the top left corner flashes for a millisecond and then the screen transitions to the Odin screen
No cm based roms & only safestrap for custom recovery. Spend some time reading what you can & can't do to your phone
rrrrrrredbelly said:
No cm based roms & only safestrap for custom recovery. Spend some time reading what you can & can't do to your phone
Click to expand...
Click to collapse
Is there any other way I can factory reset my phone and wipe it completely because I can't go into recovery mode.
Have you installed safestrap?
rrrrrrredbelly said:
Have you installed safestrap?
Click to expand...
Click to collapse
Yessir I installed it, what would be the next step?
Read how to use it. If you installed the recovery (not just the apk), reboot your phone and you'll see the screen and directions how to enter ss recovery.
From there you'll be able to wipe your phone.
Not sure how it'll work with you trying to install cwm. If this doesn't work, odin'ing back to stock and starting over might be your next option (unless someone else can suggest something)
Aslo, if you're stuck in that boot, you can pull the battery,
then hold the volume down, home and power to get the the download screen,
choose restart the phone
this worked for me when I was in a boot loop
This won't fix your recovery mode issue though, but you'll be able to use your phone in the mean time
Selling my galaxy S4 which is running cm12.1 rom and the guy who bought it wants me to keep it on cm and keep the bootloader on the mdk build.
for some reason i thought it would be a good idea to go into the phone, go to backup and recovery area and do a factory reset. the phone rebooted, and now its just looping at the TWRP screen. it just flashes it every few seconds, doesn't seem to be rebooting the phone, just recovery. if i pull the battery and throw it back in, phone will try and boot back into recovery and I have the same issue.
is there a way to reflash TWRP via odin? or even clockwork mod? just need something to get into recovery with or how else can i fix this? I really want to avoid doing an odin flash back to stock MDK, then rerooting and then reflashing a cm12.1 rom.
I had a 5.0.1 ROM installed on the stock slot on safestrap. The phone worked but I could no longer go into safestrap to change the ROM so I tried to flash a stock ROM with Odin. I flashed I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 but now there is no recovery and it gets stuck in the red Verizon splash screen. Any help is appreciated!
Fixed it
I fixed it by using http://forum.xda-developers.com/showthread.php?t=2735172 and doing the full-wipe option. After reboot, I turned it off, removed battery, microsd card, and sim card and then it worked.