Stuck in "Safestrap"? - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

I followed the instructions here http://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery <3e> LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.

PhreeqQitsikk said:
I followed the instructions here http://forum.xda-developers.com/ver...t/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.
Click to expand...
Click to collapse
S5 doesn't have a custom recovery per se, so any app that "reboots to recovery" will go to the Android stock recovery which your in. You can't flash anything of value in there, and can't install a custom recovery. You should just be able to turn the phone off then on again to get back to the stock rom, right?
It's been so long since I've done it, but won't safestrap only install on kitkat? Doors it even work in lollipop? Must people use flashfire I think

I should probably mention now that I got it fixed. Following more instructions in that thread, I did everything in the order of the first step again, using ODIN, flashed back to NC2 (I think? Going off memory) rooted, installed Safestrap, flashed MOAR, and the OC4 firmware, and here I am.

Related

[Q] Problem with TWRP

I installed twrp a couple of weeks ago and all seemed well.
Tonight I needed to get into recovery to flash the system update, and it seems my recovery isn't working, all I get is the android on his back with an exclamation point over it. I then used wugs toolkit to unroot my device and flash the stock image.. which was successful, but still I have no recovery. As a last resort, I used the toolkit again to re-root, this time ticking the box to enable the installation of cwm, when it it got to the point of the process that cwm would be installed, it said something along the lines of "opening twrp" .. it finished it's process, I'm rooted, but without recovery.
I'm at a loss. Is there a way to force cwm or something?
*disclaimer*
My device was plugged into my pc while attempting to get into recovery.
I just went ahead and reinstalled twrp, and it let me boot into recovery to install the the update zip. I'd still like to know why twrp failed in the first place, it's not a good feeling knowing that your recovery might not be there when you need it.

[Q] E:failed to mount /sdcard

Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!
What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?
Ysosrslawl said:
Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!
Click to expand...
Click to collapse
It sounds like you flashed philz touch recovery witch will not work with the VZW S5 you need to flash SafeStrap Recovery. You might need to Odin back to stock and re root your device to get it back to normal first.
chrisbass said:
What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?
Click to expand...
Click to collapse
I didn't flash anything when I first started rooting the phone I just used towelroot, then when the OTA messed it up I went and did the NCG to NE9 method using odin and towelroot. But every time I went into recovery, it has been the same. It wasn't until I used the toolkit from the forums that installed safestrap and busybox did I actually get a different recovery, but even if I reboot into recovery it still takes me to the stock one first and then on reboot i can access safestrap.
Yes, that's how safestrap works, through a process called "bootstrapping". It never replaces your stock recovery so when you boot into recovery it'll always be stock but upon boot you'll be presented with the safestrap option.....totally normal
On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.
Ysosrslawl said:
On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.
Click to expand...
Click to collapse
Your other option is what I have done. I first went the safestrap route but installed rom on rom slot before finding out about the bugz in safestrap. So I odined back to stock. Instead of installing something with bugz in it I rooted, installed supersu and Xposed framework with some modules. Wanam module gives you most of the customizations found in custom roms. Tons of other modules for pretty much anything you want to tweak. Works like a champ on stock system.

Boots back to TWRP after flashing a rom

So I am going to trade in my phone soon and as part of it I need to go back to stock. I was on a stock rooted ROM for today and when I got home I saw it had a software update. I figured Id just install it but then after clicking on it remembered that I would lose root in the upgrade and didnt want to deal with that. It had booted me into TWRP as soon as I clicked on the update and so I just turned the phone off and then on cause I figured nothing tried to actually install so it would be fine. Instead of booting the OS, it booted straight into TWRP. So I figured it had set a flag and wouldnt boot unless the update finished installing, so I would just wipe everything and re-flash a new ROM again. Did that, but I still boot straight into TWRP. Can anyone help me get back to a bootable OS state where I can use the phone again? I know it is kinda retarded to click on a software update on a rooted device, but I never thought it would completely break my ability to boot and still wouldnt even work if I wiped everything and re-installed the ROM or tried a different ROM.
My guess is that as soon as I clicked on the update it set a flag in the bootloader itself, because this issue persists even after wiping and flashing. And if I try to boot into the bootloader it actually boots me into TWRP. Should I try to use ADB in recovery and push a flashable bootloader onto the device and then try re-flashing the bootloader?

AT&T wiped, need to flash stock?

900A, AT&T, WAS 4.4.4. I rooted my phone with towelroot by downgrading via ODIN then reflashing 4.4.4. I've had the phone for a year and wanted to experiment with some custom roms--specifically Twi5ted Lollipop. The version I found last night was V3. Anyways I followed the instructions of installing safestrap then attempting to create a partition to host the mod. Every time I tried to boot the partition I would wait 12 minutes with nothing but a black screen (I presume a bootloop.) After reading some posts here I found it requires a clean flash--not a dirty flash. So I used safestrap to backup, then I wiped it and installed the mod. Nothing--still black screen. I then attempted to restore the backup I saved--fails every time.
At this point being the noob I am, I started to get very concerned. I went into advanced wipe and for some reason selected 'system' and wiped it. After a reboot, it shows the Samsung logo, goes blank, vibrates then goes back to the Samsung logo. I went into the standard bootloader and attempted to restore to factory settings but there is nothing to restore of course cause I wiped everything.
I'm currently at work bored as heck cause my phone is wiped. I can still go into download mode thankfully. Should I have no problems flashing stock via ODIN when I get home on my lunch break? Which stock firmware should I flash for this phone?
Thanks!
http://forum.xda-developers.com/galaxy-s5/help
yes, wrong section, but hopefully the post is moved soon.
since you have a G900A, make sure you only flash an older 4.4.2 firmware, so you can still root. the newer 5.0 firmwares are currently unrootable.

SM-G900A Successfully rooted, installed safestrap 3.75, can't install a rom

Hey,
I'm new to this device. I use a OPO as my daily driver but I grabbed this phone as a replacement for my dad. I wanted to give him some Cyanogenmod or some other nice AOSP lollipop rom, so I rooted it with towelroot and installed safestrap 3.75. So far, so good. I made a backup of the stock rom. Tried installing Blisspop and GApps, seemed to go okay... at least I thought it did, maybe not. Anyway it didn't work on reboot it took me to the safestrap screen, I pushed continue, it rebooted and took me to the Android System Recovery, rebooted, back to the safestrap screen, pushed recovery to go back into safestrap recovery. I couldn't find my backup to restore. Tried wiping and reinstalling blisspop, tried slim, cm, each time now it gives me "error executing updater binary in zip" and "error flashing zip".
Any ideas?
Also, if more info is needed, let me know. Sorry if I left something out.
Gargoyle nargle said:
Hey,
I'm new to this device. I use a OPO as my daily driver but I grabbed this phone as a replacement for my dad. I wanted to give him some Cyanogenmod or some other nice AOSP lollipop rom, so I rooted it with towelroot and installed safestrap 3.75. So far, so good. I made a backup of the stock rom. Tried installing Blisspop and GApps, seemed to go okay... at least I thought it did, maybe not. Anyway it didn't work on reboot it took me to the safestrap screen, I pushed continue, it rebooted and took me to the Android System Recovery, rebooted, back to the safestrap screen, pushed recovery to go back into safestrap recovery. I couldn't find my backup to restore. Tried wiping and reinstalling blisspop, tried slim, cm, each time now it gives me "error executing updater binary in zip" and "error flashing zip".
Any ideas?
Also, if more info is needed, let me know. Sorry if I left something out.
Click to expand...
Click to collapse
Just did some more reading.... silly me... sorry for the stupid question.
For anyone that find themselves in my shoes, the AT&T variant g900a can use asop roms because the bootloader can't be unlocked.

Categories

Resources