Database Develop

[Q] OTA Update with custom recovery?

Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?

Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.

mrcobain said:
Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?
Click to expand...
Click to collapse
Flash stock recovery first.

MediocreFred said:
Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.
Click to expand...
Click to collapse
i think you have to install stock recovery and maybe relock bootloader

skinsfanbdh said:
i think you have to install stock recovery and maybe relock bootloader
Click to expand...
Click to collapse
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.

MediocreFred said:
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.
Click to expand...
Click to collapse
abort and restore you backup

Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)

MediocreFred said:
Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)
Click to expand...
Click to collapse
you may be able to get it to install if your on a stock rom but im not sure about it

Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.

MediocreFred said:
Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.
Click to expand...
Click to collapse
or just flash the ruu for your phone

But, doesn't flashing the RUU wipe apps/data? I'd like to do this in the least destructive way possible. If I can get away with just flashing original recovery, installing the OTA update and flashing CWM back, I'll be happy.

yes it will. if you can get away with that then go for it

I have cwm installed on my htc one and I couldn't ruu my one back to a stock image. It would freeze up during the flash image process in the beginning.

No harm in trying the 401 or 707 recoveries ... if OTA doesnt work, just hard reboot and flash another
AND REMEMBER - NO NEED TO RELOCK FOR OTA UPDATES !

Ok got this to work and here's how, it goes without saying that this was my experience and the steps I used and I by no means accept any responsibility for any of these steps functioning on any other device...
I was using TWRP 2.5 and was rooted but otherwise was still on the stock rom that my developer edition shipped with.
I went here and downloaded the stock recovery for .16.
I opened the rar file which included other bat files to push the recovery but I didn't use that. I went to the fastboot folder and pulled the recovery.img file and dropped it in my M7 all in one tool kit folder under data and recoveries.
I then plugged in the phone and opened the toolkit and flashed my own recovery and followed the directions in the toolkit. After reboot the device came up and wanted to load the update which I let it do.
It went through and loaded and the scroll bar went all the way to the end and stuck. I waiting ten minutes and when it didn't restart I held the power button for about 15 seconds (until buttons stopped flashing) and the device screen went blank and I let go of the power button.
At this point it went through a couple screens where it appeared to be loading the update. Scroll bar went to the end and the device restarted and did that again. On the third restart it did a full boot and was good.
I then went back to the toolkit and flashed the TWRP recovery and then after reboot I went into recovery and flashed supersu to get root back.
Not sure if this helps anyone but wanted to share my experience...
MG

Issue after rooting with Stumproot and Autorec - Knock on crashing

Hello,
I rooted my stock phone (Verizon, 4.4.2, VS98027A, Kernal: 3.4.0-perf) using Stumproot, than installed SuperSU and used Autorec to install TWRP. I succesfully created a Nandroid backup and transferred this to my PC for safekeeping. I also took the opportunity to transfer all pics and backup all my apps, texts, etc. But I'm having an issue where the phone will freeze when I try to knock on (or wake it in general) and boot to the verizon logo and restart.
I planned on flashing a new rom to the phone (I need something super stable like CM) - Would that possible fix the issue? I read somewhere else that this problem is caused by Autorec, but I can I fix it properly?
Thanks for the help, complete noob here.

furry007 said:
Hello,
I rooted my stock phone (Verizon, 4.4.2, VS98027A, Kernal: 3.4.0-perf) using Stumproot, than installed SuperSU and used Autorec to install TWRP. I succesfully created a Nandroid backup and transferred this to my PC for safekeeping. I also took the opportunity to transfer all pics and backup all my apps, texts, etc. But I'm having an issue where the phone will freeze when I try to knock on (or wake it in general) and boot to the verizon logo and restart.
I planned on flashing a new rom to the phone (I need something super stable like CM) - Would that possible fix the issue? I read somewhere else that this problem is caused by Autorec, but I can I fix it properly?
Thanks for the help, complete noob here.
Click to expand...
Click to collapse
Your problem was using AutoRec. I've said it throughout a few threads, and others have stated that AutoRec causes issues on 27A.
You should be using a bumped recovery, not the old 2.7.0.0 recovery found in AutoRec. Try flashing blastagator's latest bumped recovery (Reboot to recovery to make sure thew new recovery loads up first), then the 27A bootstack, and then flash the boot image I posted in one of MicorMods' threads.
I'll make it easy for you:
Recovery (If you can't get the recovery to flash, you will have to adb it manually, or use MicorMod's tool): http://blastagator.ddns.net/twrp/2-8-5-1.php
27A bootstack: http://www.mediafire.com/download/jbswp6k7vwiijvx/bouchigo_VS980-27A_bootstack.zip
MD5: a25e8745be420e7286ed84127496d5d1
Boot image: http://www.mediafire.com/download/xa24h6fln972mz7/Fix_Rooted_Status_LG_G2-VS980-27A_v2.zip
MD5: 29c3c830e3147687db9ba3534fa8b481

Thank you!
So if I understood correctly, transfer the blastagator vs980 recovery and MD5 to my phone. Reboot into recovery, then flash this bumped recovery file.
Then transfer the 27A bootstack and boot image you posted onto my phone. Boot into TWRP that I currently have installed, select these 2 files, and flash the phone correct?

furry007 said:
Thank you!
So if I understood correctly, transfer the blastagator vs980 recovery and MD5 to my phone. Reboot into recovery, then flash this bumped recovery file.
Then transfer the 27A bootstack and boot image you posted onto my phone. Boot into TWRP that I currently have installed, select these 2 files, and flash the phone correct?
Click to expand...
Click to collapse
Just transfer all the files at once to a folder on your phone. Boot into recovery, flash blastagator's recovery, reboot recovery (there's an option in twrp that reboots into recovery without having to leave recovery) to make sure the new recovery loads up. Now proceed to flash the bootstack and boot image files.

Thanks! Will give this a shot and report back

T stuck in recovery mode,ROM not installing,5% battery.

So I decided to install cyanogenmod WhiteNeo ROM on my xperia T
did the entire process alright.
for recovery, CWM din't work so downloaded app from playsore and got TWRP from there.
the followed the steps from here to reach till step 8 from wiki.cyanogen guide.
stuck at step 8. DOn't get how to perform it because it is confusing.
altenrately sentthe zip package to sd card and tried there but says Error executing updater binary in zip.
I am stuck.
5%battery left.
and I dont know what to do.
can't even get out of Recovery mode.
device is unresponsive when connected to USB and is powered off.
can anyone please sort this out and explain in simple words how to get out of this mess?
p.s: if battery expires,then what happens?

tried installing stock firmware using flashtool
but
07/014/2015 19:14:54 - ERROR - Error in processHeader
all the time
googled all the solutions
none works
help please?

You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.

WhiteNeo said:
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
Click to expand...
Click to collapse
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.

aber96crombie said:
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
Click to expand...
Click to collapse
Reverting to stock FOTA and getting official CM recovery (which won't flash anything but official CM builds and gapps) can be done with flashtool and a suitable ftf or using a Terminal command that you will find on the last pages of my CM12.1 thread for Xperia T.
TWRP version should be visible in settings or what one would call a "status bar".
And the force-closing gapps are just the result of a broken or outdated recovery. I've already been reported the same issue after creating a FOTAKernel TWRP for a friend.
You should be able to flash official CM12 gapps from Cyanogen Recovery.. Just google those.

recovery will not stick on 6.0.1

I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks

jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.

all i have now is stock recovery. whats the best way to manually install twrp

go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.

Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse

Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk

when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.

arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp

jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.

This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.

scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.

simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help

jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine

[SOLVED] Latest beta OTA (NPD90G) won't stop booting to recovery

Just signed up for the beta program a couple of days ago, downloaded/installed Preview 4 with no issues. I recall it booting back to TWRP, a script ran in TWRP, and then the phone rebooted back to system. Everything was OK at that point, other than I lost root and TWRP. I reflashed TWRP with fastboot, SuperSU via TWRP, and now I'm back in business.
I got the notification a few minutes ago that Preview 5 was now available for me to install. It downloaded, rebooted to TWRP...and nothing. The script didn't run this time like it did last time. Plus, every time I try to boot back to system it goes right back into recovery.
...help?

Same thing for me. I had to run the preview 4 twrp zip
Sent from my Nexus 6 using XDA-Developers mobile app

Gromlakh said:
Just signed up for the beta program a couple of days ago, downloaded/installed Preview 4 with no issues. I recall it booting back to TWRP, a script ran in TWRP, and then the phone rebooted back to system. Everything was OK at that point, other than I lost root and TWRP. I reflashed TWRP with fastboot, SuperSU via TWRP, and now I'm back in business.
I got the notification a few minutes ago that Preview 5 was now available for me to install. It downloaded, rebooted to TWRP...and nothing. The script didn't run this time like it did last time. Plus, every time I try to boot back to system it goes right back into recovery.
...help?
Click to expand...
Click to collapse
You could flash the stock recovery from a factory image then follow the instructions on this page to flash the OTA which will preserve data, but if you don't care about data you could flash the factory image fromthis page. If you don't need the device ASAP you could also wait for RatchetPanda to upload a flashable system on this thread, but IDK how long that'll be (although he's generally pretty fast).

Good news: got the phone to boot by going to bootloader first, then telling it to boot to system from there. So the phone works again, but the update didn't stick.
Will try flashing stock recovery in a bit. Thanks!
Sent from my Nexus 6 using Tapatalk

mrjiggywiggy said:
You could flash the stock recovery from a factory image then follow the instructions on this page to flash the OTA which will preserve data, but if you don't care about data you could flash the factory image fromthis page. If you don't need the device ASAP you could also wait for RatchetPanda to upload a flashable system on this thread, but IDK how long that'll be (although he's generally pretty fast).
Click to expand...
Click to collapse
One quick question: I have the phone booted back up now, and I can get back to recovery (TWRP) whenever I want. The OTA flash instructions from the first link say to use stock recovery + adb sideload to flash. Can I just flash the OTA from TWRP and not mess with stock recovery? I would assume yes, but I figured I'd at least ask the dumb question first before my phone starts bootlooping on me after a bad flash.
EDIT: Never mind, found the answer: apparently not.

Gromlakh said:
One quick question: I have the phone booted back up now, and I can get back to recovery (TWRP) whenever I want. The OTA flash instructions from the first link say to use stock recovery + adb sideload to flash. Can I just flash the OTA from TWRP and not mess with stock recovery? I would assume yes, but I figured I'd at least ask the dumb question first before my phone starts bootlooping on me after a bad flash.
EDIT: Never mind, found the answer: apparently not.
Click to expand...
Click to collapse
nope

Problem ultimately solved by flashing the zip from here: http://forum.xda-developers.com/nexus-6/general/android-n-preview-5-beta-npd90g-t3421459 (method 1). Everything is working just fine now.