[Q] Installing cwm recovery after phone goes into boot loops? - Galaxy S 4 Q&A, Help & Troubleshooting

So I went to far with my S4 with xposed frameworks and got it stuck in boot loop. Being a fool I never installed a custom recovery. What I'm wondering is whether it is safe or not to install a custom recovery to fix my problem by uninstalling xposed fireworks?

A recovery and a rom are two independant things. So just flash away.

Lennyz1988 said:
A recovery and a rom are two independant things. So just flash away.
Click to expand...
Click to collapse
Thank you very much, i thought the rom and recovery where two separate things but wasn't 100% sure and didn't want to risk hard bricking it. Worked like a charm and so did the xposed disabler. Back to normal now

Related

Phone soft-bricks upon flashing any Touchwiz-based rom?

Hi XDA, I'm a relatively new owner to Android phones (3 weeks) and have a problem that I can't find any leads on.
I cannot flash any Touchwiz-based ROMS without the phone going into a boot loop and having to reflash via Odin. I know that AOSP ROMS work fine because I use goomanager to flash CM10, Carbon, and Liquid smooth previously. The problem only occurs with touchwiz roms. Here is the rundown of how I noticed the problem:
I download Crash ROM and move it to my internal SD card. I install TWRP via goomanager. I then use goomanager to wipe the data, cache, and dalvik cache, and to install the Crash ROM zip. The phone gets to the samsung logo then gets stuck in a boot loop.
I reflash it through Odin using the tutorial at GalaxyS4root and it boots fine. I use goomanager to reinstall TWRP and try flashing it through TWRP instead, again doign a full wipe of the data, system, cache, and dalvik cache. Same thing occurs and I reflash through Odin.
Fast-forward to last night; I decide to try another Touchwiz rom, this time Wicked ROM. I download it and put it on the internal SD card; using TWRP I wipe it again, and install it. Aroma Installer comes up and I make sure to select AT&T as my carrier. I get to the end of the installation and the phone reboots. This time its much worse than it was with Crash ROM, the phone is vibrating to signal it starting up, but the screen stays blank and then a few seconds later it vibrates again. This repeats constantly and the phone also couldn't boot into recovery mode (but it could boot to download mode). So I tried reflashing it twice, but the issue persisted. Through google I determined it to be a stuck power button. I've returned the phone to AT&T to be replaced for faulty hardware and am awaiting its return.
So now is where I ask you guys. I've spent a solid hour googling this and nothing related to my problem comes up. So does anyone have any experience with the S4 not being able to flash touchwiz based roms? Or could anyone point me to any leads as to why this would occur that I can investigate further?
Thanks for the help.
-Tryer
EDIT: I'm pretty sure it wasn't MF3 because I could flash certain ROMS fine.
You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?
DeadlySin9 said:
You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?
Click to expand...
Click to collapse
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.
Tryer1234 said:
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.
Click to expand...
Click to collapse
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.
Aou said:
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.
Click to expand...
Click to collapse
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?
Tryer1234 said:
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?
Click to expand...
Click to collapse
when the device reboots after the aroma install, i would pull the battery, replace it and use the 3-button combo to enter custom recovery. then i'd flash the loki-doki zip. thats just me though. i hate aroma.
http://lmgtfy.com/?q=what+is+loki+doki
also: http://forum.xda-developers.com/showthread.php?t=2292157

[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.

S5 Recovery Bootloop

Hey guys need a hand with something,
I was just in the process of flashing a blisspop 5.1 to my galaxy s5 and now Ive ran into difficulties. Phone did a full boot and launched perfectly however when I was restoring my apps through google play I accidentally hit quit and exited the installation. So therefore to restart the process (as I didn't know another way) I hit factory reset. Phone rebooted however it tried to reboot into recovery but the recovery wouldnt boot (twrp) and the trwp screen just kept flashing. Pulled the battery and it rebooted to recovery again with the same bootloop issue. I can get into download mode and am thinking of reflashing twrp but need help before I brick my phone!
Thanks!
95thfallout said:
Hey guys need a hand with something,
I was just in the process of flashing a blisspop 5.1 to my galaxy s5 and now Ive ran into difficulties. Phone did a full boot and launched perfectly however when I was restoring my apps through google play I accidentally hit quit and exited the installation. So therefore to restart the process (as I didn't know another way) I hit factory reset. Phone rebooted however it tried to reboot into recovery but the recovery wouldnt boot (twrp) and the trwp screen just kept flashing. Pulled the battery and it rebooted to recovery again with the same bootloop issue. I can get into download mode and am thinking of reflashing twrp but need help before I brick my phone!
Thanks!
Click to expand...
Click to collapse
you may flash TWRP again in odin and after that I suggest you flash ktoonsez.zip TWRP after that so you have a stable TWRP
imfuzzyyy said:
you may flash TWRP again in odin and after that I suggest you flash ktoonsez.zip TWRP after that so you have a stable TWRP
Click to expand...
Click to collapse
Would it be better to reflash twrp or should I flash stock firmware? I really don't want to lose this phone as I bought it less than a month ago.
95thfallout said:
Would it be better to reflash twrp or should I flash stock firmware? I really don't want to lose this phone as I bought it less than a month ago.
Click to expand...
Click to collapse
you may flash the TWRP first if the problem still persist then the only choice you have is to flash stock firm then reflash TWRP, then after that I suggest you flash in TWRP the TWRP by ktoonsez because it in zip file most of us s5 user uses his TWRP
also dont be afraid as it would not hardbrick your device as long as you can access in download you are always safe., first day of my s5 I root it already and flash custom rom
95thfallout said:
Would it be better to reflash twrp or should I flash stock firmware? I really don't want to lose this phone as I bought it less than a month ago.
Click to expand...
Click to collapse
Flash twrp 2.8.5.0 by Odin
Flashed TWRP this morning with odin and the phone booted right into the rom. Thanks for the help guys.
95thfallout said:
Flashed TWRP this morning with odin and the phone booted right into the rom. Thanks for the help guys.
Click to expand...
Click to collapse
good for you dont forget to hit thanks on my post hehe
imfuzzyyy said:
good for you dont forget to hit thanks on my post hehe
Click to expand...
Click to collapse
sorry forgot your top one
95thfallout said:
sorry forgot your top one
Click to expand...
Click to collapse
NP happy flashing again

Stuck in "Safestrap"?

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.

S7 Edge Bootloop After Xposed Install

I made a mistake when installing xposed on my G935F and am now stuck in a bootloop.
I downloaded the xposed uninstaller to undo my install and fix my mistake, but I'm unable to boot into recovery.
Do I have to reflash it via odin?
Note: I downloaded the sdk 23 arm64 version, but I didn't wipe data like the guide said to do (didn't see that guide until after I flashed, I was following another guide).
Thanks.
Why are you unable to boot into recovery? And not wiping data would not prevent the phone booting as long as you installed the correct Xposed framework. Did you install Wanam's arm64 version here or the official one? If you installed the official version in rovo89's thread then that is why you're getting a boot loop. Unless things have changed, that doesn't work on Touchwiz roms and causes bootloops, hence why Wanam made a separate version.
Beefheart said:
Why are you unable to boot into recovery? And not wiping data would not prevent the phone booting as long as you installed the correct Xposed framework. Did you install Wanam's arm64 version here or the official one? If you installed the official version in rovo89's thread then that is why you're getting a boot loop. Unless things have changed, that doesn't work on Touchwiz roms and causes bootloops, hence why Wanam made a separate version.
Click to expand...
Click to collapse
I used the official one version.
I have no idea, but I tried the recovery boot sequence so many times and I can't get it to boot into recovery. What should I do?
Reset your phone (volume down & power for 7-10 seconds) then remove your fingers and press volume up & home & power to boot into recovery. If you have TWRP installed (and I assume you do unless you used Flashfire to flash Xposed) there is no reason it shouldn't work. Installing Xposed, even if you used the incorrect version, would have absolutely no effect on the recovery partition.
Beefheart said:
Reset your phone (volume down & power for 7-10 seconds) then remove your fingers and press volume up & home & power to boot into recovery. If you have TWRP installed (and I assume you do unless you used Flashfire to flash Xposed) there is no reason it shouldn't work. Installing Xposed, even if you used the incorrect version, would have absolutely no effect on the recovery partition.
Click to expand...
Click to collapse
That still doesn't work for me.
I used flashfire the first time and it didn't work (some guide on xda said to use it). It booted fine after that. I then reverted back to flashify and booted into twrp to flash it, and after that it just sat on the S7 edge boot screen endlessly.
I kept trying and managed to boot into recovery. I flashed the xposed uninstaller and its now running again. Thanks for the help!
l33t p1mp said:
I kept trying and managed to boot into recovery. I flashed the xposed uninstaller and its now running again. Thanks for the help!
Click to expand...
Click to collapse
Use this Xposed
https://www.dropbox.com/s/2q69cpwxz...arm64-custom-build-by-wanam-20160504.zip?dl=0
"And on that bombshell!"
Sent from my Echoe powered AEL driven G935F

Categories

Resources