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

[XT1058] System Update Failing

I got unlocked bootloader and TWRP installed, with kitkat.
It showed new System update, I confirmed to download, but when it going to install it reboots in recovery,
TWRP, when I try to install the same img that it downloaded it sais
"this package for "ghost" devices"
And I can't update it.
Can someone helps me, the model is XT1058

caioketo said:
I got unlocked bootloader and TWRP installed, with kitkat.
It showed new System update, I confirmed to download, but when it going to install it reboots in recovery,
TWRP, when I try to install the same img that it downloaded it sais
"this package for "ghost" devices"
And I can't update it.
Can someone helps me, the model is XT1058
Click to expand...
Click to collapse
You can't flash the ota while using custom recovery and being rooted, you need the stock recovery and your system needs to be 100% stock. You also can't flash it with twrp and cwm
Sent on my Gummy running Lenoto X

flashallthetime said:
You can't flash the ota while using custom recovery and being rooted, you need the stock recovery and your system needs to be 100% stock. You also can't flash it with twrp and cwm
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
before you go back to stock ware are you located if in the USA could you please pull the 4.4.2 OTA file and post it here please and thank you

Im outside the USA.
I just need to reflash the stock recovery, and then apply OTA and then flash the twrp again?

search the rom of your country and version (in sbf) download it, then open it search for recovery.img, go to fastboot, and fla**** with adb commands:
fastboot flash recovery recovery.img

Trying to apply OTA - Recovery error "No Command"

I've been out of circulation of the whole xda thing for a while with my HTC One M7 (AT&T version) but I decided to convert the thing to GPE and get updated to android 5.1.
The conversion went smoothly using this guide but now I am having some troubles applying the OTA to update to 5.1
I have tried unrooting by using the unroot option on SuperSU and then flash the OTA using stock recovery, only to find that when I want to access stock recovery I get a screen with the android alien lying down and the error "No command".
I figured I could flash the stock recovery with fastboot to fix this (downloaded 5.11.1700.3 from here) but I still get the same screen and error when selecting the recovery option from the fastboot screen.
In a desperate move I also tried flashing CWM and trying to flash the zip file but the OTA fails to install that way.
What am I doing wrong here?
Thanks in advance for your help

Error updating Nexus 6 to 6.0.1

Hi all, new to the forums here. Sorry if this is in the wrong section. So I was trying to update my nexus 6 to 6.0.1 from 6.0 and I got this error
supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing Update...
Source: google/shamu/shamu:6.0/MRA58K/2256973:user/release-keys
Target: google/shamu/shamu:6.0.1/MMB29K/2419427:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8393958:28495c2ab9b8a2210fc396d8af35c29bc885fce9:8398054:bb5e73e0be23e9709b0acfd83db5c62140" has unexpected contents
E: Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Now I looked up status 7 errors and how to fix, but none had pertained to my particular issue, so I figured I'd check before doing anything drastic. For some info, I have rooted, unlocked bootloader, flashed a custom recovery and rom, but when Marshmallow came out, I flashed stock image for 6.0 to my phone through nexus root toolkit, which removed custom recovery, flashed to stock, but kept bootloader unlocked. So now I'm on clean stock 6.0 and I received the OTA and I tried to install it and this is the message I get. Any ideas on how to get my phone to update? Oh, and BTW if it matters, I'm on T-Mobile. Thanks in advanced!

First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.

istperson said:
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
Click to expand...
Click to collapse
Hey, that would be great! The only problem is I'm not particularly skilled in that field lol. Does the boot.img, system.img and radio come from the stock factory image, or do I have to download those separately? And would I install those with a particular program? Thanks, sorry for being such a noob

It's in the factory package mmb29k. Download it, and extract it, you'll have the bootloader, the radio, and a zip file with all the rest. You don't need the bootloader, it hasn't changed since the marshamllow preview. Extract the files from the zip file, then flash radio, boot.img and system.img.
For flashing you need fastboot, but the toolkit already installed it, it just calls it when you push buttons.
As for the flashing, everything is explained in the pinned post.

New B390 OTA update

For VIE-AL10 the new firmware update B390 is out. However, currently I am on B356, rooted and TWRP installed. However, when I do the OTA update it restarts into TWRP (because stock recovery is gone). I can't find a download to stock recovery for B356. How else can I installed this OTA update? I've tried dload folder way but with no avail. Any help would be appreciated.

you wont be able to install stock ota whilst you are rooted with twrp. You are going to have to go back to stock and with no root to do the ota, use this tool its worked for me in the past.
https://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999
PLEASE READ ALL THE THREAD BEFORE USE
if you do have questions ask in that thread

So I decided to wipe and reinstalled my firmware B356. Locked bootloader, no root, no twrp, brand new install. I look into hicare and it doesn't have the option to upgrade to B356. Anyone know why?

go into twrp
advance -> files manager -> /dev/block/platform/hi_mci.0/by-name/
copy recovery2 to SDcard (or other place)
rename copied recovery2 to recovery
recopy the file to /dev/block/platform/hi_mci.0/by-name/
reboot

Deviatorz said:
So I decided to wipe and reinstalled my firmware B356. Locked bootloader, no root, no twrp, brand new install. I look into hicare and it doesn't have the option to upgrade to B356. Anyone know why?
Click to expand...
Click to collapse
It should show updates, set your region to china in hicare after a reboot check it. If still nothing then post in the thread that I left a link for

Sorry for late reply. It started to show the update after a week. Not sure if the other methods worked but it showed up. I have a feeling it's because huawei decided to pull the firmware temporarily.