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

I have failed at flashing

Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!

mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again

mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628

Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!

Looking to Root - running marshmellow stock

Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.

ccf60 said:
Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.
Click to expand...
Click to collapse
rooting marshmallow..
1. unlock the bootloader(yours is there already)
2. fastboot flash twrp recovery.
3. flash the latest supersu in twrp recovery
4. flash a custom marshmallow kernel, any. this ones new for marshmallow, and is needed.
5. boot up.

simms22 said:
rooting marshmallow..
1. unlock the bootloader(yours is there already)
2. fastboot flash twrp recovery.
3. flash the latest supersu in twrp recovery
4. flash a custom marshmallow kernel, any. this ones new for marshmallow, and is needed.
5. boot up.
Click to expand...
Click to collapse
Thank you.

ccf60 said:
Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.
Click to expand...
Click to collapse
how did you manage to flash stock again after corrupt. mine wont recognize adb while corrupt. please give step by step
nvm. i got it finally

You don't flash with adb, but with fastboot.
The steps are:
1. Turn on phone with pressing vol down and power.
Sent from my Nexus 6 running cyosp using Tapatalk

Help with flashing CM13 to Moto G 2014.

Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.

Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.

phoenix964 said:
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Click to expand...
Click to collapse
while @kushal_10 explained most of the things to do, i would like to remind you that CM13 has inbuilt Root. You just have to enable Developer options, then in Developer Options,under Root Access, choose Apps and ADB. Don't flash SuperSu
Hope I helped you.

kushal_10 said:
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
Click to expand...
Click to collapse
I read somewhere that wiping the system isn't advisory because in case something goes wrong, there will be no way to restore. Can you confirm this?

logo bootloop after Pie upgrade and TWRP flash

1900-1 variant (Android One) with unlocked bootloader. Followed these instructions and it worked fine.
I then flashed TWRP and rebooted (did not install Magisk) and that's when the bootloops started. I was still able to get into TWRP, so I did a factory data reset since I didn't care about my data. Still looping.
Then I followed the first part of those instructions (flash to stock Oreo via fastboot)...still looping, and TWRP is gone. I can't seem to get into stock recovery using the vol+/pwr so I can do an adb sideload of Pie.
Thoughts?

I have a 1900-2 & there is no stock recovery. Go to bootloader & use commands "fastboot boot ((name of recovery img(twrp.img))".
There is several threads on booting out flashing recovery. I never installed the recovery to my phone because I've already seen this problem in other threads. I just use my PC to boot twrp when I need it.

rczrider said:
1900-1 variant (Android One) with unlocked bootloader. Followed these instructions and it worked fine.
I then flashed TWRP and rebooted (did not install Magisk) and that's when the bootloops started. I was still able to get into TWRP, so I did a factory data reset since I didn't care about my data. Still looping.
Then I followed the first part of those instructions (flash to stock Oreo via fastboot)...still looping, and TWRP is gone. I can't seem to get into stock recovery using the vol+/pwr so I can do an adb sideload of Pie.
Thoughts?
Click to expand...
Click to collapse
Download Pie full fastboot package. Check my previous post somewhere here.Then won't install TWRP, only boot to TWRP.

Comby_sk said:
Download Pie full fastboot package. Check my previous post somewhere here.Then won't install TWRP, only boot to TWRP.
Click to expand...
Click to collapse
Thanks! This link to Mega that you posted?
https://forum.xda-developers.com/showpost.php?p=78370069&postcount=5
Is that for the Android One (1900-1) variant? Although I don't suppose it really matters, since I'm not using it with Fi.
EDIT 1: well, it "worked" in that Pie would boot, but it's definitely not for the A1 and upon setup it can't find any wireless networks, so I'm assuming I need the A1 files. I did try to flash back to Oreo, but I'm bootlooping again.
EDIT 2: I flashed stock Oreo 8.1 again. I don't know if I was doing the key combination incorrectly to get into recovery (hold PWR and just once press VOL+) or I needed to flash Oreo again, but I could get into recovery. I tried flashing Pie again, but it failed since I (probably) needed to get the two Oreo OTAs (28.3.4 and 28.3.5) that have been released since the full image (28.3.3). I was, however, able to do a full factory data reset (including userdata and personalization) and that let me boot into Oreo! So I'll try the Pie thing again
EDIT 3: I booted back into Oreo and did the two OTAs. Since I wasn't rooted (only an unlocked bootloader), I did the Pie update via OTA and it worked fine.

No:
https://forum.xda-developers.com/showpost.php?p=78466061&postcount=102