P9 lite stock firmware - Android Q&A, Help & Troubleshooting

Hello,i have only recently started playing with my phone and ive hit a wall and im trying to find the stock firmware for my model but i cannot,since i followed many outdated guides and guidelines my os is deleted
and although i can use stock recovery or twrp when i try to flash the update.zip i though was the correct one i get error 7 cannot update from update.zip,if i try the stock recovery i get failed at 11% with reason update missing although i placed the .app in the dload in the root of the sd card!
My device is a Huawei P9 lite VNS-L21C432B380 and i would appreciate if someone can point me to its stock firmware and any extra tip to get my bearings as to how i can reverse the bricking i caused to my phone
Thanks in advance!!!

Related

Huawei G Play Mini Hard Bricked ~ Help

Hello, so a few days ago, I tried installing LineageOS on my Huawei G Play Mini, model chc-u01. As I was inexperienced I eventually messed my phone, and now it has no OS at all (I wasn't even smart enough to backup). I've been trying to install official firmware with no luck, using either the dload method, the original huawei recovery, and twrp recovery (honor 4x version).
When I try installing an official rom using the dload method, it seems to work right until the end, where it gets stuck. I don't get any error, it just simply gets stuck right before ending.
When I try installing from an update.zip using stock recovery, I get a "cust fail" error. It also says something about country/vendor.
TWRP just fails everytime, whenever I try to install any rom at all. Probably because it's an old version. Can't install a newer one, for some reason.
I never changed my phone's firmware, ever since I bought it. It came with Android 4.4 Kit Kat.
Can anyone help me? I've been trying to fix this for almost a week now, with no luck.

Help returning to stock

Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help
djmills.uk said:
Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help[/QUOTE]
use this
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
and follow the guide for flash update.
This is how i got back from lineage to stock on mate 10 pro. use the correct file from http://pro-teammt.ru.
Click to expand...
Click to collapse
esnar said:
use this
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
and follow the guide for flash update.
This is how i got back from lineage to stock on mate 10 pro. use the correct file from http://pro-teammt.ru.
Click to expand...
Click to collapse
Thanks. I will try that. I fortunately the exact version I had installed is not on the site hopefully using the latest version for the same phone will work.
I will let you know thanks.
esnar said:
use this
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
and follow the guide for flash update.
This is how i got back from lineage to stock on mate 10 pro. use the correct file from http://pro-teammt.ru.
Click to expand...
Click to collapse
OK. Tried doing the parts about the public zip and hw zip and they are not found on the site so I'm hoping that doesn't matter on this phone. Did you have the same result?
EDIT: Nevermind, i was being an idiot, downloading the files now
All working as new now, but newer firmware. Thank you so much for your help!
Back to stock
djmills.uk said:
Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help[/QUOTE]
Hi
Could you tell me how you removed the root, I am having the same problem on my Mate 10 Lite, I want to return to stock, but it eludes me all the time because of root. I have used what should be non-rooted backups, but they say root. The only backup that worked ended up turning my phone into another unit so no luck there either. Would love to hear how you did it?
Click to expand...
Click to collapse
Hi i am trying to flash stock on my mate 10 pro, bla l29 c432 131. could u help?
Trying to flash bla l29 c432 137.
Have full ota and data and hw.
How did u manage to do it?
And relocked bootloader?
Tried uppdat.App on otg usb device, it finds the usb but not the upgrade
Update. Zip 2gb extract to dload and then move that "dload" folder?
Extract zip to usb root directory?
Thx
djmills.uk said:
Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help[/QUOTE]
hi, i tried to follow the thread, but its already edited, now my mate 10 pro is still in customized rom. do you still have the instruction? please help
Click to expand...
Click to collapse

How to use recovery features & firmware (eRecovery/dload/HWOTA/recovery)

I can turn this into a guide if we get the right info.
I have used DC-Unlocker to unlock bootloader and FRP.
I installed v20 Phh Generic System Image via fastboot flash system.
my FRP is locked now and bootloader unlocked, and oem unlock greyed out.
i am investigating a solution and maybe it can help others.
Recovery:
can flash updates if bootloader and frp is unlocked
eRecovery:
i can connect to wifi, but no firmware is found
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
HWOTA:
seems to be a method used on older devices - not sure if it will work to flash this device.
the sh. script seems fairly straightforward so maybe it can be modded to work with this device
Device: SHT-W09 M5 8.4 (eu)
Build Number: 8.0.0.151 (C432)
OS: Stock 151 with Phh GSI applied
ive never had a device this difficult to recover. samsung had odin to flash firmware, nexus 5/7/9 always had a way out - when i was building roms for moto xoom it wasnt this difficult.
Good luck man, it seems like when this thing bootloops, it activates some sort of defense mechanism that makes recovery particularly challenging.
I bootlooped after editing my vendor/build.prop file. DLoad method failed. Flashing partitions via fastboot failed. Stock recovery failed. TWRP became available, and I got it working...but no partitions would mount r/w. I paid to use Funky Huawei's unbrick tool, and it failed.
Funky Huawei's eRecovery method is basically all that worked for me. But I paid to use it (I still have a few weeks remaining on a pass).
These instructions, which don't involve payment to Funky Huawei, might or might not work:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
Thanks for the alternative method.
I tried with hisuite using firmware finder, it uses the same funky DNS server. When I start the process the download works fine then on hisuite it says installing, does nothing then fails. After I reboot (usb in pc, all 3 buttons) it shows a usb symbol - installing but hangs at 5% for ages.
I tried with a portable router with ERecovery and it did not work unfortunately still failed to get info
I had to result to funkyhuawei who have now added SHT-W09C432 to their system.
In the 30 days I have this I'm tdetermined to find alternative solutions to fix this issue like all other devices tend to have.
I battled it out with Huawei support and there's no chance of an frp key - at least first 3 attempts. Also tried to get them tonexplqin ERecovery but said it's for insiders only just for service repairs. They have no regard for helping developers.
I was trying to figure out where the file get stored on ERecovery so if we could adb push to it and hold vol down + up + power to recover the device. I found i could pull from /dload (not internal/externalsd) which contained firmware_update_dload.zip but when uncompressed e enwbti be referenced to Qualcomm chips.
Any ideas on patching the recovery or boot image to prevent frp lock?
I also tried to see if there is a way from adb (while OS is running) to flip the OEM unlock back to on but there's nothing in system/global/settings that represents that.
It's strange because frp should not lock if you log back into the same account.
LOGMD said:
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
.
Click to expand...
Click to collapse
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
OK, thanks for this info, of course I thought that this device would be as easy to utdate then my much older M2-801L via dload which worked every time. And thanks for the tool tip, I'm looking into that thread as well :good:
Butch1326 said:
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank You for the info.
Used it to update my CMR-AL19 and worked like a charme
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
Sorry for the late reply had some busy months!
So from what I remember it's because the UPDATE.APP was too big. I tried recreating the update.app without the non-essentials but I couldn't get it working.
Huawei support when I asked about how to update via recovery just kept saying it's only for technicians at Huawei so they won't help me in any way!

How do I flash rebranded Mate 10 ALP-L29 firmware?

I rebranded and flashed my Mate 10 about 6 months ago, but ever since then I haven't received any OTA updates. That was my first mistake, shoulda got an OTA version firmware... I'm not sure if being rebranded is going to cause any issues. Bootloader is unlocked, and I've recently installed TWRP.
Now I wanted to update to Pie/EMUI 9, then found out its just the beta version... so I'm just wanting to get the latest build of EMUI 8. Firmware finder says for c636 is 8.0.0.134....
I've searched all over XDA and google and youtube, and can't find any one place to give enough detail and resources to get this done.
I've tried downloading the firmware about 3 or 4 times. Firmware finder on android, I think funkyhuawei or firmwarefinder online, potentially someones Mega link, and somewhere else. It seems sometimes different sites have different resources. My most recent downloads have 2 packages, the update.zip, and the Update_full_ALP-L29_hw_spcseas.zip. Now i'm looking at firmware finder again, they say theres another update_data_full_public.zip which I haven't got yet.
I'm just not sure if I need it all, or if some parts are unnecessary, or maybe I don't even need the fullMF-OTA version, maybe just the OTA version...
Then when it comes to execution, I've found all sorts of varying methods and I'm open to any. ADB, TWRP, eRecovery, I don't care. I've recently tried TWRP with these 2 packages I've got, and I get an error: 9.. and haven't fully identified what that means just yet.
Other methods I've seen are tricking the eRecovery into downloading the firmware from localhost aka the phones own storage. Haven't tried it yet, because firmware finder gets errors while downloading, even without pausing or stopping and on good signal wireless.
I've also read about extracting Update.app files from these zips, and it just gets messier and messier.
(Much more difficult than my old Oneplus One, just download a rom and flash it in twrp, then flash modding .zips and other things afterwards if you want)
TL;DR:
I want to update my ALP-L29C636 Mate 10 manually with TWRP to 8.0.0.134. I just need a version that will get me OTA updates again. It's also rebranded.
I need to know how many .zips I need, which ones and where to get them.
I need to know what to flash it with, TWRP, or ADP or eRecovery and what steps for that method.
Looking forward to hearing your suggestions. Thanks in advance!

Huawei Enjoy 5 soft brick (i think!)

Hello, I have bought and sold a few phones and flashed custom roms, run adb and fastboot etc. So although I class myself as a noob I do have some experience.
Well I recently bought a Huawei Enjoy 5 that will not boot into Android thinking it would be a nice little project, the seller said he tried to flash ios onto it and in the process deleted the system files.
It will boot into the bootloader and stock recovery and I can use adb and fastboot. If I just press the power switch it will boot to a splash screen and stop.
The bootloader is unlocked.
The model is Huawei TIT-TL00
The Build Number is TIT-TL00C01B133
I can't find a vendor country but assume it to be UK or EU.
There is not an awful lot of info for these phones but I did read they are similar to other models, Honor 5X Play, Holly 2 Plus and Y6 Pro but I don't want to flash the wrong rom.
I have managed to download a few stock roms but not C01B133. I have B122, B132 and B202h which are all for that model. But I read downgrading can hard brick them.
I also read that to flash the rom you have to extract the zip and then look in the extracted folder for the UPDATE.APP file. I can't find that file so think I am doing something wrong but I'm not sure what.
Any help would be great. If I can just get the UPDATE.APP file I would try to flash the rom but I don't know where to look.
Many thanks
Amazingly I managed to flash a Rom on this tonight. B203 official Rom. Extracted all the files and although they looked nothing like the files everyone describes I installed the dload folder onto the sd card and gave it a go. It flashed a Chinese Rom with all sorts of bloatware but no Google so I assume it is for the Chinese market. And the time on the screen was Chinese time. Luckily there was an English option to select so I spent some time setting it up. However it won't recognize any SIM and I'm not sure why, but at least it's running Android now.
Unfortunately I couldn't get any further with this because when I installed the rom it relocked the bootloader. So unless someone has any success getting them unlocked then I'm stuffed.?

Categories

Resources