Database Users

[SOLVED] local updates (update.zip, update.app) after root and unroot not working

Hello guys,
I have general issue updating locally (DLOAD) my P8 Lite, from root or SD, full update.app or incremental update.zip.
System always says: Sorry OTA update package (update.app or update.zip) not found and phone restarts
I had root but already unrooted. Tried to go back manually with adb to B052, didn´t help.
Any advice would be appreciated.

Ing.King said:
Hello guys,
I have general issue updating locally (DLOAD) my P8 Lite, from root or SD, full update.app or incremental update.zip.
System always says: Sorry OTA update package (update.app or update.zip) not found and phone restarts
I had root but already unrooted. Tried to go back manually with adb to B052, didn´t help.
Any advice would be appreciated.
Click to expand...
Click to collapse
Do you have stock recovery or TWRP?
Local update is not possible with TWRP. If you have TWRP you need to flash stock recovery, before trying the local update.

Well, I never installed different recovery, everything is default.

So after I renamed packages to something else, from e.g. update.zip to Update.zip1, and then back to update.zip, it started to work. While update I had DLOAD folder located both SD and root.

pmp said:
Do you have stock recovery or TWRP?
Local update is not possible with TWRP. If you have TWRP you need to flash stock recovery, before trying the local update.
Click to expand...
Click to collapse
how can i find a stock recovery?

same problem here. i have it on root of sd named update.app what do i have to do? rename it update.zip ?

Get a USB cable and plug it into a computer then restart the phone into recovery you should find it boots Huawei standard recovery if not you will have to flash it
EDIT turn off the phone then press volume up whilst pressing volume up press the power button keep holding volume up recovery should load

Post deleted

I've always used TWRP to flash stock updates. After flashing you have stock recovery and it's unrooted.

dereppsteiner said:
how can i find a stock recovery?
Click to expand...
Click to collapse
Here you can find a table with all Huawei firmware in it. Find one (F3) for your device (for example, ale-l21 europe region: ALE-L21C432) and download the FULL version. Then use Huawei Update Extractor to get just the recovery.img (right click on it > Extract)

Stock Recovery?

Does anyone have or know where to get a stock recovery image for the BTV-W09?

When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.

I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.

If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).

I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.

I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.

Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.

Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.

Is it possible to update to B381 (via OTA update) having a custom recovery?

Hi all,
I currently have a P9 Lite with VNS-L31C432B371 firmware installed.
Recently, I received the VNS-L31C432B381 update via OTA. Unfortunately, when the phone reboots into recovery mode, the update does not even start; instead, I get redirected to the custom recovery (TWRP 3.1.0.-2, system partition read-only) "homescreen".
Is there a way to update to B381 without wiping the entire phone?
Thank you for your time.

The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery

SALVO9 said:
The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery
Click to expand...
Click to collapse
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?

_n0153_ said:
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?
Click to expand...
Click to collapse
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.

JHD94 said:
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.
Click to expand...
Click to collapse
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.

_n0153_ said:
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.
Click to expand...
Click to collapse
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know

okaar said:
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know
Click to expand...
Click to collapse
well, if you flash your oeminfo zip, you should get it back

mjz2cool said:
well, if you flash your oeminfo zip, you should get it back
Click to expand...
Click to collapse
I only have old oeminfo.img packages, do you know how I can build one? There is a PRODUCT.img but it is considerably bigger than the oeminfo package that I have seen.
I flashed all the old B370 files, update.zip and update...hw_eu.zip, with DC Phoneix (a non free tool but saved me from.a bricked phone). After that, I flashed the new package and got the Security settings and Developer Options to work again.

Bricked, wiped chinese BTV-DL09 4G

Long story short; I wiped system and everything on this device, so all I really have on it working now is TWRP. The official FullOTA updates fail in TWRP, erecovery fails, and recovery in hisuite fails. I assume the last two will fail because of the third party recovery. So I guess I'm wondering if anyone can point me in the direction of the official recovery that I can fastboot flash, or any other way to reload the ROM?
Full story; I got this new tablet last week, and I unlocked, installed TWRP, and rooted successfully. Then I broke google services with a dodgy gapps install that I didn't need, couldnt figure out how to unflash it, and wiped everything like an idiot.
Thanks if anyone can help.
Update; I guess the root of the problem is that I'm unable to mount /data? Any actions I take in TWRP give me the error "Failed to mount '/data'", including if I do a wipe data or try to change the file system. I've used "Huawei Update Extractor" to see if there is a data.img, but it looks like no.
Update 2: Still not sure what this was all about, but I extracted system.img from "Huawei Update Extractor" and fastboot flashed that, and it looks like everything is working again. Haven't checked TWRP to see if it still gives errors on the data partition, but I'm at least in the OS and google play services are working.

Download latest firmware for your device from Huawei server and extract it. Make a new folder on external sdcard, named dload. Copy extracted file (update.app) in this folder. Power off device and turn it on using 3 button method: volume up + volume down + power - old all 3 buttons simultaneously.
It will start the update/flash process. It will install factory firmware on your device.
When you download Firmware, in the archive you will find these steps (PDF file).
Next time you can try this
Sent from my BTV-DL09 using Tapatalk

30adi said:
Download latest firmware for your device from Huawei server and extract it. Make a new folder on external sdcard, named dload. Copy extracted file (update.app) in this folder. Power off device and turn it on using 3 button method: volume up + volume down + power - old all 3 buttons simultaneously.
It will start the update/flash process. It will install factory firmware on your device.
When you download Firmware, in the archive you will find these steps (PDF file).
Next time you can try this
Click to expand...
Click to collapse
Wrong. He installed TWRP so there is not a functional recovery.
The right thing is to extract the Recovery from the Update.app and flash it, then use the dload method.

nicolap8 said:
Wrong. He installed TWRP so there is not a functional recovery.
The right thing is to extract the Recovery from the Update.app and flash it, then use the dload method.
Click to expand...
Click to collapse
Actually, I did try that, but I put stock recovery back on and and tried the dload method, it still failed int he same way as with TWRP installed.
What ended up working was extracting system.img from the update and fastboot flashing it. Not very intuitive. I am still getting "Failed to mount '/data'" errors in TWRP now, but haven't looked much into it yet. That is weird, I guess if everything is working it is more a problem with TWRP, because if everything is running and booting /data should be fine.

P9 lite custom rom setup troubles + softbrick

Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?

hexahive said:
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
Click to expand...
Click to collapse
http://www.meticulus.co.vu/p/hi6250-custom-rom-installation.html

Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?

hexahive said:
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
Click to expand...
Click to collapse
You must already be on EMUI 5 to install EMUI5 based ROMs.