Just rooted my s4 using saferoot, got goomanager to install twrp recovery, installed, didn't do a reboot as it was prompted to (I think it was supposed to reboot anyhow) and said "Recovery has been installed" click the reboot recovery through goo, a couple gapps crash, and reboots into normal recovery, that says error and I'm able to boot my phone up still?
Help?
Did you have goo manager reinstall twrp? If you use goo, there is no reboot required. Try again and report back.
cruise350 said:
Did you have goo manager reinstall twrp? If you use goo, there is no reboot required. Try again and report back.
Click to expand...
Click to collapse
I just rooted and this would be my first time putting twrp on this phone, I rooted past phones but I used Odin so I'm used to flashing things and I was told by a friend who rooted the s4 that with my model (UEMK2) to do the saferoot route and get goo manager to install twrp, so I did that, I have root access I checked with root checker, and when I went to install twrp, it downloaded, said "recovery installed" and I went to check just to make sure by using goo manager's Reboot Recovery option, but instead I got Android normal recovery, it first said "no command" then it says "error" and then I get the normal options for android recovery, I can safely just boot out of it and start my phone though, should I try and flash twrp or?
Yes, try to reflash twrp. I used safe root to reroot after running the MK2 stock tar last week and used goo manager to install twrp with no problems so it does work. Try again.
cruise350 said:
Yes, try to reflash twrp. I used safe root to reroot after running the MK2 stock tar last week and used goo manager to install twrp with no problems so it does work. Try again.
Click to expand...
Click to collapse
Yeah I got it to work haha thank you so much!
Related
Hey Guys,
I just rooted my i9505 via CF-Auto-Root and it worked like a charm. The next thing I did was to flash Philz Recovery, at first it auto reboot and it never went into recovery, so I followed the steps to re-flash it without the auto reboot and force it into recover. It loaded into Philz Recovery perfectly fine, now when I reboot, it gave me the option to disable auto flash recovery, so I selected yes.
After that I was never able to get into Recovery Mode ever again. All it does is says Recovery Booting in the top left corner and then restarts and loads into the OS. I followed the steps again to re-flash Philz with auto reboot unchecked and it still failed to get into recover. I then tried CWM and TWRP (via Odin), but all of these gave me the same problem and failed to get into recover.
I then tried SGS4 Flasher but still the same question.
Anyone here who has this problem before and know the fix or is able to recommend another method?
Was able to fix it. Had to flash the original stock Recovery back on and then re-flash a custom recovery. Not sure what happen but was able to install TWRP on without an issue, maybe something in Philz Recovery that stuffed it up.
OK! Looks like it is not working correctly. For me to get access to a custom recovery, I have to flash the stock recovery via Odin and then flash a custom recovery to get it working EVERYTIME. It will boot into Philz, CWM and TWRP only once, then you need to flash stock recovery and do the process all over again.
So it looks like the recovery gets over written each time even if you select "yes - disable flash recovery" in Philz Recovery. Anyone know of another way to disable flash recovery?
Z-Blade said:
OK! Looks like it is not working correctly. For me to get access to a custom recovery, I have to flash the stock recovery via Odin and then flash a custom recovery to get it working EVERYTIME. It will boot into Philz, CWM and TWRP only once, then you need to flash stock recovery and do the process all over again.
So it looks like the recovery gets over written each time even if you select "yes - disable flash recovery" in Philz Recovery. Anyone know of another way to disable flash recovery?
Click to expand...
Click to collapse
with a root explorer, go to system/recovery-from-boot.p and rename it to recovery-from-boot.p.bak
samersh72 said:
with a root explorer, go to system/recovery-from-boot.p and rename it to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Thanks for responding samersh. To lessen the pain of constantly flashing the recovery via Odin on my PC, I bought Mobile Odin Pro. However, it looks like when I flashed using Mobile Odin Pro, it fixed my issue.
I checked \System\ and there was no recovery-from-boot.p there. So it is confirmation that this has been fixed. Thanks again for responding.
Hello
I just tried switching my recovery. I had an autoloki recovery and didnt think id have to reflash lokidoki but i clicked reboot recovery and now everytime i try to boot into recovery, it says unauthorized software and at the top it says secure boot kernel. What should i do? I have tired reflashing cwm but it didnt fix it and goomanager says that there is no recovery for me.
thanks guys
skullassfreak said:
Hello
I just tried switching my recovery. I had an autoloki recovery and didnt think id have to reflash lokidoki but i clicked reboot recovery and now everytime i try to boot into recovery, it says unauthorized software and at the top it says secure boot kernel. What should i do? I have tired reflashing cwm but it didnt fix it and goomanager says that there is no recovery for me.
thanks guys
Click to expand...
Click to collapse
edit fixed with dd if=/recovery.img of=/dev/block/mmcblk0p21
Good deal .you could've also just used Goo manager for
re installing TWRP or
Rom manager for CWM and then find your Auto loki recovery again
Sent from my ATT S4 MF3 using Tapatalk
I'm having a strange time with my phone, I rooted the phone, by the guides on xda, everything went well, superSu was installed,
then I tried to flash a new recovery and a new kernel, but nothing worked, after some searching I found this AutoRec tool, it worked
the recovery changed to TWRP, so I tried to flash dorimanx again, and again nothing changed, the flashing was done, but after reboot still
no change with the kernel.
So I checked if the device is rooted, I did this on the begining of the process and it was, now, it showed that the device isn;t rooted.
Now I have a TWRP recovery, without root, and when I try to root, I have to press "apply update from adb..." but I dont have thing option anymore,
Thanks a lot for your help!
maxwellz said:
I'm having a strange time with my phone, I rooted the phone, by the guides on xda, everything went well, superSu was installed,
then I tried to flash a new recovery and a new kernel, but nothing worked, after some searching I found this AutoRec tool, it worked
the recovery changed to TWRP, so I tried to flash dorimanx again, and again nothing changed, the flashing was done, but after reboot still
no change with the kernel.
So I checked if the device is rooted, I did this on the begining of the process and it was, now, it showed that the device isn;t rooted.
Now I have a TWRP recovery, without root, and when I try to root, I have to press "apply update from adb..." but I dont have thing option anymore,
Thanks a lot for your help!
Click to expand...
Click to collapse
You can still root with custom recovery the difference is you need to go to advanced and sideload to be able to apply the root.zip, you can also look for the flashable supersu.zip and flash it from recovery and that will root your device
Sent from my LG-D800 using XDA Premium 4 mobile app
Thanks for your reply, I gained back the root.
Downloaded from PlayStore some app called Rebooted - went to recovery [TWRP if it has any influence] and flashed Dorimanx kernel,
the flashing is over, but nothing new... it just doesnt install nothing... so strange..
Anyone please?
maxwellz said:
Anyone please?
Click to expand...
Click to collapse
I suggest you start over. Not sure if you performed wipes(wipe all except internal).
But
1. flash kdz
2. root
3. autorec
4. wipe wipe wipe(except internal)
5. install
6. profit
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.
Hi. So, I had TWRP on stock rom and my phone was rooted. was messing around trying to install viper4android and i think i clicked wipe data, etc in recovery mode. Phone rebooted and im un-rooted now with SuperSU installed but it says "there is no binary SU installed and superSU cannot install it. This is a problem! "
What do I do now? I can still boot into recovery.
If I have to flash to a stock firmware, is that easy to do? Thanks in advance
AdrMXP said:
Hi. So, I had TWRP on stock rom and my phone was rooted. was messing around trying to install viper4android and i think i clicked wipe data, etc in recovery mode. Phone rebooted and im un-rooted now with SuperSU installed but it says "there is no binary SU installed and superSU cannot install it. This is a problem! "
What do I do now? I can still boot into recovery.
If I have to flash to a stock firmware, is that easy to do? Thanks in advance
Click to expand...
Click to collapse
1. Flash Rom You Want To use in your Device .
2.Download Supersu Binary Zip File from Here http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash it through TWRP recovery
4.Now reboot your cell phone and install SuperSU.