TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Check out the thread under general tab to use RSD Flasher or House of Moto to install the 4.4.4 FXZ
DB's Moto X
coreno said:
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Click to expand...
Click to collapse
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
samwathegreat said:
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
Click to expand...
Click to collapse
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
coreno said:
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
Click to expand...
Click to collapse
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
samwathegreat said:
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for you help! I am all upgraded and got everything back going to the way it was!
coreno said:
Thanks for you help! I am all upgraded and got everything back going to the way it was!
Click to expand...
Click to collapse
Great!! Glad to hear everything worked out. I sent you a Private message - check your PMs
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
jco23 said:
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
Click to expand...
Click to collapse
And in your case, it was Xposed.
There are several threads (and posts) discussing conditions for taking an OTA. You need stock recovery, have to disable Xposed, and you need to be close enough to stock so the pre-flash verification will pass. Otherwise, the OTA will fail, and/or you'll get stuck in a boot loop.
There is a little more to it as well, but I'll ask you to see the other threads.
Thought I disabled xposed. But perhaps not. I've read other threads. From my understanding, I won't be able to root (or even the quasi-root) on 4.4.4 with a locked boot loader.
Thx for the reply.
Related
I was rooted and running CM6. I tried getting back to a stock 2.2 by flashing the stock image from Rom Manager. I downloaded the 2.2 update from google and it wouldn't update. In the system menu or bootloader I got a little format happy with boot/system and so on. Anyway, doing a nandroid now. Is there anyway to get this phone back to the kernel it shipped with?
You have to flash it with the stock recovery.
I've been using that Universal androot.http://www.androidappjudge.com/2010/08/one-click-root-application-universal_10.html I tried flashing stock 2.2 and I didn't read the two options, I just clicked them and kept going not realizing that I flashed the rooted, superuser version. Does this mean that I'm now rooted forever? When I try flashing stock 2.2 with rom manager It stops @ the android and /!\ symbol. Now it's even doing this with CM.
I'm now wondering how to get rid of whatever crap might be floating around on my phone and why it may not be flashing anymore?
there is nothing wrong, rooting allows you the ability to have super administrative rights. Since all you have done is grant yourself admin rights, the recovery should be the same.
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
glwinkler said:
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
Click to expand...
Click to collapse
Did you wipe? I used 1-click root and I hadn't flashed anything in over a year so I forgot to wipe and I boot looped until I pulled the battery, booted into recovery and wiped. Simple solution but it could be worth mentioning...
So you are saying that, you have the stock recovery now? Triangle with little android? If so, Just download a PASSIMG.zip and flash through bootloader. This will take you to stock.
I have an N1 with locked bootloader and when I wanted to go back to stock(Forgot to get a nandroid of unroot rom). I had to flash a stock recovery. then downloaded the PASSIMG.zip from here http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91+downgrade
This takes me back to ERE76. Then I download an OTA of FRF85B.
I think fix permissions fixed everything. Thanks for the tips!
THIS HELPED TOO:
http://forum.xda-developers.com/showthread.php?t=619153
pretty self explanatory. I used safestrap, unistalled it, when i try to get to the stock recovery i pick it from the fastboot menu using the up vol key and then the phone just boots like normal, never goes to the recovery. any ideas would be hugely appreciated.
zeer.row said:
pretty self explanatory. I used safestrap, unistalled it, when i try to get to the stock recovery i pick it from the fastboot menu using the up vol key and then the phone just boots like normal, never goes to the recovery. any ideas would be hugely appreciated.
Click to expand...
Click to collapse
Are you still rooted? After rooting with any of jcase's methods (i don't know about the 4.4 one), rebooting to recovery just launches the rom without write protect. I'm not 100% sure, but I think you'd have to flash back to stock to recover stock recovery.
Why exactly do you want stock recovery back? Maybe we can work around it to get the results you want.
Also, you should post things like this in the Q&A forum.
JetOhmNet said:
Are you still rooted? After rooting with any of jcase's methods (i don't know about the 4.4 one), rebooting to recovery just launches the rom without write protect. I'm not 100% sure, but I think you'd have to flash back to stock to recover stock recovery.
Why exactly do you want stock recovery back? Maybe we can work around it to get the results you want.
Also, you should post things like this in the Q&A forum.
Click to expand...
Click to collapse
well im worse off now. wiped my system. no rom. no recovery. think im royally screwed.
Yup, safestrap replaces your recovery, and since you nixed safestrap, your phone has nothing to fall back to. You're phone will be fine, I did the same thing when I unrooted and tried to install the 4.4 update. You just need to flash the stock recovery files in RSDLite. Will you loose your data? Sure (or you can save what you want on your computer), but your phone will be fine. Let me know if you get messed up trying to do this.
I have Safestrap 3.7.2 and Lollipop rooted installed. I've googled and googled and can't find an answer to this. I booted into Safestrap to try to figure out how to delete an old NC1 backup I made. I hit the reboot/recovery button once. What a mistake. The phone booted into stock recovery. Now when the phone boots, I get a message saying Safestrap is disabled with the options of recovery or continue. Continue does nothing but gives me a blank screen. Recovery takes me into Safestrap, and I can't get the phone to boot back into Lollipop. If I hit reboot/system, I get the same Safestrap disabled screen. If I hit reboot/recovery, I end up in the stock recovery. It says to wait 10 seconds and it will boot, but all I get is a blank screen. I have Lollipop in the stock ROM slot with no other ROMs loaded. HELP!
Well the only thing I could figure to do was to ODIN back to NC2, use Towelroot to get root, install Busybox and Safestrap 3.75, install the OC1 rooted ROM, and reinstall everything via Titanium Backup. This time once I get the phone set up the way I want I will make sure to make a Safestrap backup. What a pain.
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
voigts said:
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
Click to expand...
Click to collapse
Since you're on Lollipop did you flash the OC1 kernel before leaving Safestrap? http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
voigts said:
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
Click to expand...
Click to collapse
Only thing I can think of is something in your Titanium backup is messing things up. If you happen to flash all that again (not saying to do) but if you do, I would boot into Safestrap (once you install Lollipop) and flash the OC1 kernel to see if it boots ok. (Before you do the Titanium Backup).
Thank you for the replies. I failed to realize that I needed to extract the lollipop file and then flash the SM-N900A_OC1_Kernel_Safestrap_Installer.zip file contained within AFTER flashing the lollipop file. Yes, I get the stupid award for the day. Duh....
I extracted the file, copied to MicroSD card, and then booted into Safestrap and flashed it. Hopefully things will work correctly now. I feel pretty stupid.
I need help myself.. Every time I try to flash any type of zip I get stuck in safestrap disabled
Greetings, all. I'm a big fan of using Xposed modules for my phone, especially YouTube Adaway but since I upgraded via kdz to 5.0.2 this evening I can't get Xposed to run even after reboot using the apk found in the Xposed lollipop thread. I tried to check the log files to be able to post the output here but it won't read those either. Has anyone been able to get this to work and if so, how? Any help is greatly appreciated as the main reasons I root is for ad blocking and titanium backup
lerner17 said:
Greetings, all. I'm a big fan of using Xposed modules for my phone, especially YouTube Adaway but since I upgraded via kdz to 5.0.2 this evening I can't get Xposed to run even after reboot using the apk found in the Xposed lollipop thread. I tried to check the log files to be able to post the output here but it won't read those either. Has anyone been able to get this to work and if so, how? Any help is greatly appreciated as the main reasons I root is for ad blocking and titanium backup
Click to expand...
Click to collapse
Did you flash the zip on the thread also?
I did not
krchi said:
Did you flash the zip on the thread also?
Click to expand...
Click to collapse
My bootloader is still locked so to my knowledge there's not a way to flash a zip without a custom recovery (TWRP, CWM and the like). Maybe I read the thread wrong and you had to both flash the zip and install the apk
Edit: Yes, that is correct, I read it wrong. The zip must be flashed for the framework to install. Is there a way to flash a zip without a custom recovery? This is the first phone I've had with a locked bootloader, all the other ones I just installed a recovery from here and ran/modded it
lerner17 said:
My bootloader is still locked so to my knowledge there's not a way to flash a zip without a custom recovery (TWRP, CWM and the like). Maybe I read the thread wrong and you had to both flash the zip and install the apk
Edit: Yes, that is correct, I read it wrong. The zip must be flashed for the framework to install. Is there a way to flash a zip without a custom recovery? This is the first phone I've had with a locked bootloader, all the other ones I just installed a recovery from here and ran/modded it
Click to expand...
Click to collapse
The L90 of D415 has a unlocked bootloader by deafult, I never unlocked mines and flashed recovery, Just flash this http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150 using Flashify, download the img and open Flashify and select flash recovery then select that image and in that app you should be able to reboot to recovery to flash the xposed zip. Since I've never tried it I dont know how well xposed runs on stock lollipop remember to backup.
krchi said:
The L90 of D415 has a unlocked bootloader by deafult, I never unlocked mines and flashed recovery
Click to expand...
Click to collapse
Thank the gods for that then! I am leaving tomorrow on a trip and need my phone fully functional for the duration (hooray GPS) so just to be safe I'm going to hold off on flashing the custom recovery until I get back on Monday and will also flash the Xposed framework then as well and report back. Thanks for the help! I will update this thread after flashing just in case others are looking for this to say whether or not it worked.
Hello,
I was able to get xposed running well on 5.0.2. However i didnt flash stock kdz, I flashed a modified stock ROM found in the development section (see http://forum.xda-developers.com/lg-l90/development/rom-l90-d415-lollipop-xtreme-v1-0-4-25-t3092813)
After flashing the ROM as described in the link above, i rebooted to recovery. I then flashed the xposed zip file. After that, I wiped cache and dalvik cache (VERY IMPORTANT to avoid any storage errors). Finally I did a normal boot, and it installed perfectly. Hope this helps! Best of luck my friend
Sorry for late response
Turns out my boot loader was in fact unlocked. TWRP through Flashify and then install the zip through there, then install the apk and reboot again. Thank you both so much for the information!
Correction
lerner17 said:
Turns out my boot loader was in fact unlocked. TWRP through Flashify and then install the zip through there, then install the apk and reboot again. Thank you both so much for the information!
Click to expand...
Click to collapse
While Xposed installed and worked it also soft bricked my phone in that I kept getting "unfortunately com.android.phone stopped working". Not sure if it's the program itself or the fix memory leak module I installed. Thankfully I had a backup right before I flashed that zip and it appears my phone is working again. Not sure if I will try to install it again without the memory leak patch or not. Thoughts?
lerner17 said:
While Xposed installed and worked it also soft bricked my phone in that I kept getting "unfortunately com.android.phone stopped working". Not sure if it's the program itself or the fix memory leak module I installed. Thankfully I had a backup right before I flashed that zip and it appears my phone is working again. Not sure if I will try to install it again without the memory leak patch or not. Thoughts?
Click to expand...
Click to collapse
Sadly, this also led me to restore my stock, modded KK backup. What I found to be a temporary fix is to wipe cache/data for the phone apk as well as the SIM Toolkit, then reboot. It appears fixed for some time, but then reappears. This problem seems to arise whenever you use wifi or mobile data, and goes away when you switch them off (at least that was my experience).
I think that the main culprit is the Xposed framework itself. I was told by others it's not fully compatible on stock LP for the L90, but still tried it either way. I got too many mods I like to not use Xposed, so I rolled back to kk. If you can live w/o Xposed then try LP with no framework and see what happens. Best of luck!
jbonilla51 said:
I think that the main culprit is the Xposed framework itself. I was told by others it's not fully compatible on stock LP for the L90, but still tried it either way. I got too many mods I like to not use Xposed, so I rolled back to kk. If you can live w/o Xposed then try LP with no framework and see what happens. Best of luck!
Click to expand...
Click to collapse
How sad I will continue to monitor the Xposed threads then to see if/when it's fully functional with stock Lollipop.
I was in panic mode with my phone yesterday not working because it happened right when my car decided to also quit working so I saw those possible fixes as well and neither worked. Thankfully I backed up through TWRP right before I flashed the Xposed zip so that save my butt,
This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
totallybeachin said:
This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
Click to expand...
Click to collapse
Boot back into TWRP and reflash SU
totallybeachin said:
... re-flashed the ROM, only this time said "no" to the supersu install screen......
Click to expand...
Click to collapse
That's correct. No in twrp - is needed when there is already a SU in the flashed rom.
Probably you have not the most recent version of twrp.
In play store there are apps to check if you have root acces.
You can also go to the launcher and start the superSU app
kwdan said:
Boot back into TWRP and reflash SU
Click to expand...
Click to collapse
It always seems to be the most simple thing!
I'm not generally a stupid person, but this stuff can sure make a girl blush!
Thank you.
Worked like a charm.
Falling in love all over again with my Nexus 6.
.....makes note for NEXT TIME I have been eating dummie bears!
As NLBeev said, you are probably using an outdated version of TWRP. It doesn't ask about su any longer.