only rebooting in recovery - LG Optimus 4X HD

hi, i have Rooted original rom,. unlocked with clockwork mod recovery.
tonight my phone got a OTA 20B,
i tried to install in but my phone is now only rebooting to recovery, is there a way to bypass?

makkie88 said:
hi, i have Rooted original rom,. unlocked with clockwork mod recovery.
tonight my phone got a OTA 20B,
i tried to install in but my phone is now only rebooting to recovery, is there a way to bypass?
Click to expand...
Click to collapse
How many different threads are we going to get from people asking this same question?
Don't accept an OTA update on a modified phone! If you want it then flash the original .kdz then OTA update then redo root and recovery.

Related

failed OTA 4.4.4 keeps rebooting into recovery

i have a tmobile xt1053 and i tried installing the OTA 4.4.4 update. it went right into recovery and didn't update. now everytime I boot the phone up a min or two in, it just turns off into recovery. Is there any way to fix this? I dont care for the update, just want it to stay on. i'm rooted, stock with a few xposed mods.
Unlocked bootloader with custom recovery? If so, taking an OTA will always fail.
killerb777 said:
i have a tmobile xt1053 and i tried installing the OTA 4.4.4 update. it went right into recovery and didn't update. now everytime I boot the phone up a min or two in, it just turns off into recovery. Is there any way to fix this? I dont care for the update, just want it to stay on. i'm rooted, stock with a few xposed mods.
Click to expand...
Click to collapse
There are two ways you can go about it. Either let it load up and install a file explorer (I use Root Explorer)(would have to do this quick). Then quickly go the the cache folder on the root of the sd card and delete the OTA. The other way would be to enter the recovery menu manually and clear cache. The second way would probably be the easiest way. Please note though that you will be prompted to download the OTA again. To avoid this you may want to consider freezing MotorolaOTA 1.0 service.
this is the way to fix your problem
nhizzat said:
Unlocked bootloader with custom recovery? If so, taking an OTA will always fail.
Click to expand...
Click to collapse
Correct. Go here and do what it says to get back to good -
http://www.reddit.com/r/MotoX/comments/2c8vb5/guide_updating_your_bootloaderunlocked_moto_x_to/
in short, you have to flash stock recovery, then let the phone reboot and install the ota, then you can finish by reflashing custom recovery and get root back. good luck!
thanks guys. before I could see your posts i just tried to wipe cache in recovery and it booted with an unsuccessful error. seems to be working now.

[Q] Boot Loop for Moto X Developer Edition (cause by Lollipop 5.1 update?)

Hi, I have a Moto X 2013 Developer Edition with bootlocker unlocked and stock rom with Android 4.4.4. It's root, has TWRP and SuperSU.
Since last week my phone is shutting down almost always after power on (only a few times it keeps power on for a few hours), and restarting in TWRP recovery mode.
Do you know what could be the cause of this boot loop?
I suspect it has something to do with the Lollipop Update to 5.1, cause I start getting this boot loop after the update option was shown in my phone (I didn't accept the update at first).
I tried installing again SuperSu (thinking that maybe root was disabled), but without luck. The phone continue with this boot loop.
I also tried installing now the Lollipop Update to see if that resolve the issue, unfortunately after the update is downloaded and I accept the install, the phone shutdown and it boots in TWRP again (so the updated doesn't install).
Hope my problem was explained well and anybody can help cause my phone is really unusable like this.
Thanks in advance!
You're only suppose to install stock ota's using stock recovery not custom recovery. It's best (if you can) flash back to stock if you know how.
Sent from my XT1055 using Tapatalk
can you please tell me how to flash stock recovery
Thanks for your response. Do you mean to flash stock recovery? or full stock rom?
Just in case, I don't need/want to install lollipop, only want to avoid this kind of boot loop and stay at 4.4.4. I'll only install 5.1 it if that fix the issue /but as I say I can't do it because after download and try to install, it power down the phone and goes to twrp recovery).
Thanks for your help!
ninguno2 said:
Thanks for your response. Do you mean to flash stock recovery? or full stock rom?
Just in case, I don't need/want to install lollipop, only want to avoid this kind of boot loop and stay at 4.4.4. I'll only install 5.1 it if that fix the issue /but as I say I can't do it because after download and try to install, it power down the phone and goes to twrp recovery).
Thanks for your help!
Click to expand...
Click to collapse
It's best that you flash back to fully stock rom. If you can flash back to 4.4.4
Sent from my XT1055 using Tapatalk
What if they disabled the update app, wouldn't that stop the update from trying to install and cause it to reboot into twrp
Sent from my XT1060 using Tapatalk 2
TRY THIS POST
http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
I USED OPTION 1 i.e USED THE TOOL KIT ...
Hi cdiamon, sorry asking again, but there is something I don't understand.
I have original stock rom 4.4.4. I only unlock bootloader (I have the developer edition), put twrp and root the phone. Why the suggestion is to flash back to 4.4.4 to resolve the issue? Didn't I'm already at stock rom?
By the way do you think the problem is because twrp and/or root by supersu? If yes, can't i simply uninstall supersu or remove twrp in some way?
B.E.McAllister and praty, thanks both for your answers, I'll look at them too.
Thanks in advance!
ninguno2 said:
Hi, I have a Moto X 2013 Developer Edition with bootlocker unlocked and stock rom with Android 4.4.4. It's root, has TWRP and SuperSU.
Since last week my phone is shutting down almost always after power on (only a few times it keeps power on for a few hours), and restarting in TWRP recovery mode.
Do you know what could be the cause of this boot loop?
I suspect it has something to do with the Lollipop Update to 5.1, cause I start getting this boot loop after the update option was shown in my phone (I didn't accept the update at first).
I tried installing again SuperSu (thinking that maybe root was disabled), but without luck. The phone continue with this boot loop.
I also tried installing now the Lollipop Update to see if that resolve the issue, unfortunately after the update is downloaded and I accept the install, the phone shutdown and it boots in TWRP again (so the updated doesn't install).
Hope my problem was explained well and anybody can help cause my phone is really unusable like this.
Thanks in advance!
Click to expand...
Click to collapse
The problem is you have twrp on your phone when the phone is trying to update. You need to flash stock recovery then take update. Or keep twrp and disable update app.
monkeytools said:
The problem is you have twrp on your phone when the phone is trying to update. You need to flash stock recovery then take update. Or keep twrp and disable update app.
Click to expand...
Click to collapse
Hi monkeytools. thanks for the explanation. I think I'll disable update app then.
Just to know, is there any way to uninstall TRWP without flashing stock recovery and loosing all of my configuration?
Thanks in advance!
ninguno2 said:
Hi monkeytools. thanks for the explanation. I think I'll disable update app then.
Just to know, is there any way to uninstall TRWP without flashing stock recovery and loosing all of my configuration?
Thanks in advance!
Click to expand...
Click to collapse
You don't loose anything by flashing recovery. That is if you just flash recovery or fastboot recovery.

did anyone get a security update on their m7 this morning?

I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
devsk said:
I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
Click to expand...
Click to collapse
Should post this question here: http://forum.xda-developers.com/showthread.php?t=2305490
and the answer is probably yes since I don't see why T-mobile USA would push an ota update only to you
7.18.531.35 is the t-mobile US equivalent of 7.17.1540.35 which is the latest version with the stagefright 1.0 vulnerability fixed.
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
Click to expand...
Click to collapse
You need to be on 100% stock rom including stock recovery to install ota updates. Better to return to stock using a ruu before applying the update imo since many users soft bricked their phones when attempting to install lollipop ota updates on stock rooted phones. If you need the RUU, look in the RUU collection thread, there is a 7.18.531.2 RUU posted there (link in my signature). Don't forget that questions should be posted in the q&a section, not in general. :good:
Thanks for your help. I found the RUU for my version. So, since I need to go back to RUU flash, I will need to re-setup my phone from scratch again just for getting this OTA....sucks!!
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system and destroy my recovery but keep my /data and /sdcard. I can recover from that much faster than doing RUU and set up from scratch!!
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
I should have made a recovery.img from the original stock recovery partition. Do you know if I can find the stock recovery here somewhere?
devsk said:
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system
Click to expand...
Click to collapse
It is, you'll loose root every time you do an ota update.
and destroy my recovery
Click to expand...
Click to collapse
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
Click to expand...
Click to collapse
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
Click to expand...
Click to collapse
No, the updater-script will only work with stock recovery
I should have made a recovery.img from the original stock recovery partition.
Click to expand...
Click to collapse
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
Do you know if I can find the stock recovery here somewhere?
Click to expand...
Click to collapse
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
alray said:
It is, you'll loose root every time you do an ota update.
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
No, the updater-script will only work with stock recovery
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
Click to expand...
Click to collapse
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
devsk said:
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
Click to expand...
Click to collapse
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
alray said:
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
Click to expand...
Click to collapse
Awesome!! :good::good:

OTA update

I just recovered my phone with twrp recovery and the root is now gone so my phone is not currently rooted. And there is an OTA update. But I can't install it. It takes me to tarp recovery. So any help. What if I delete the twrp recovery and then install update?
ameerhamza193 said:
I just recovered my phone with twrp recovery and the root is now gone so my phone is not currently rooted. And there is an OTA update. But I can't install it. It takes me to tarp recovery. So any help. What if I delete the twrp recovery and then install update?
Click to expand...
Click to collapse
You must have stock recovery to install ota update along with an unmodified /system files, unmodified /data/preload files.
return to stock using a RUU before applying the ota is probably the safer way to go now with lollipop updates if you want to avoid a bootloop.

Update b357

Hi,
Today I received ota update to b357 for my nem L51.
Could not install it since I have custom recovery + root + unlocked bootloader.
How can I update?
My idea would be:
Flash stock recovery + recovery2 from fastboot
Install ota
Flash again TWRP
Will it work? Don't know if my bootloader will lock again after ota update...
Thanks in advance
Unroot first, Flash stock boot.img and stock recovery then download ota and reboot.
Thanks shashank1320!
I flashed stock boot + recovery and then updated my phone.
Unfortunately OTA update restored my bootloader and I had to unlock it again.
Anyway after unlocking I flashed TWRP recovery and rooted with Magisk with no issues.
deframat said:
Thanks shashank1320!
I flashed stock boot + recovery and then updated my phone.
Unfortunately OTA update restored my bootloader and I had to unlock it again.
Anyway after unlocking I flashed TWRP recovery and rooted with Magisk with no issues.
Click to expand...
Click to collapse
Hi @deframat,
I'm in the same situation as you were: from B350 I have to update to B357 and I will go the same route you did. However, since you stated that the OTA update restored your bootloader, this means you had to install all over again all your apps and settings. I wonder if I make a Titanium backup of everything, will I be able to restore the phone as it was before the update? Any drawbacks I'm unaware of?
Thank you
Hi Wallace108,
I don't use Titanium backup because I prefer a fully fresh install when flashing new fw.
Anyway since this update is quite light (only security patch and other small improvements) I think you will have no problem if you restore some backed up apps.

Categories

Resources