Related
Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.
I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.
Hi guys, I am only a very junior user who randomly flash his phone but most of the time I want my phone to be stable for work. I have had the situation since the recent OTA available, suffered a lot, would like to seek any help or advice.
I have a L09C635B361, Japan version. I updated to Android 7 via OTA, then unlocked / rooted under the instructions in this forum, forgot which exact thread though. Never thought of flashing any customized rom so I haven't realized the update problem until the recent OTA update (from B361 to B382) released. I got the push, downloaded B382 OTA package, restart to TWRP, then the flash was failed in TWRP screen. Restart again, the system notified there was a recent update failure. Then I installed Firmware Finder, downloaded the 3 update zip files, restart back to TWRP, still failed installing. Please refer to the failure screenshot for detailed reson. I have no idea what it said and how I should do differently.
No other way to go, I backed up my system, then wiped my phone, reset to factory mode, but brand new system was very strange: only voice input, no keyboard, missing several key functions such as camera. So I have to restore to my previous system, everything worked well except I can't open "clock".
Right now I am looking at system notification of B382 all the time, but I can't figure out how to get it updated, I don't mind if there's a way enables me go back to stock rom, but it's really hard to find the stock firmware for C635......
Thanks, appreciate your help in advance.
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
xMrTROLLIPOPx said:
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
Click to expand...
Click to collapse
Thanks bro. I will try the entire process when I have a backup phone.
One more thing is when I first tried to wipe phone, failed for several times. Plus the TWRP flashing error, I have suspect that there's something wrong with my partition information or format error. Can anyone help me to eliminate the possibility by the screenshot please?
On the other hand, I found 3 zip files on Firmware for same version update. Which one should I flash? If I need to flash all of the 3, is there a sequence?
The screenshot for the 3 zip files.
oushouseki said:
The screenshot for the 3 zip files.
Click to expand...
Click to collapse
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
lostunsunghero said:
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
Click to expand...
Click to collapse
Well, it ended up with paying 20USD to some "pro"s on taobao.com to unbrick my P9...sigh...am I too old to do this :crying:
I have a SIM free UK P9. Early on in its life it received updates happily but I have still not received Nougat and I'm still on the September 2016 Security Patch from Google. I've never rooted or tampered with the device, so where are my updates? Are Huawei simply too busy with other phones to bother updating flagships from only last year?
It is unacceptable to me that a £450 device from a manufacturer purportedly looking to compete with the big guns in the premium phone space cannot be bothered to keep its older handsets up to date. How is a user supposed to put his trust in a company when they seem to forget about their older devices once newer ones are released onto the market?
Meanwhile a friend of mine with a SIM free Samsung Galaxy Note 4 (!) has June's security patches.
Small wonder people don't take Huawei seriously. This P9 is a lovely device with great battery life and is still (for my usage) an excellent handset; however I will not be buying another Huawei until I am confident that they are willing to maintain support for older devices. So far it seems that some people in different parts of the world on various carriers *do* get updates (or at least have more recent ones) but Huawei seem incapable of rolling them out consistently and across the board.
Disappointing.
Anyone else have any thoughts on this? I don't wish to put Huawei down too much as I think they bring some interesting things to the market but one of my biggest bugbears is where manufacturers forget that after-sales support and updates are some of the things that contribute to people's perception of a company. Might as well just buy Doogees and Vernees off Banggood without it.
Don't wait huawei to send update,use firmware finder from play store,or dload method,or hisuite method,all these methods are officially safe and keep your warranty. What your build number ?
Build number is EVA-L09C432B182.
I'm not really into flashing ROMs these days as i don't want to mess anything up. I don't want to flash firmware that isn't UK SIM free either, and if I haven't had that update OTA then I assume it simply hasn't been released.
I don't have a PC anyway as I sold my Surface Pro and now only have a MacBook.
Use firmware finder from play store,and firmware finder proxy,it is the easy way,only search for the rom u want and let your system update search for update by using proxy,if from MM to nougat u will not loose anything.
You'd have to guide me through that step by step as to be honest I don't entirely understand anything other than the bit about using something from the Play Store
OK so I worked this out. The only firmware it says is approved for my device is the next up on the list - EVAL09C432B330-LOG.
This downloads fine through the stock Huawei update menu (as if i am just doing a normal update) and the phone reboots but then the installation fails, whether I choose the full package or standard update option.
leoni1980 said:
OK so I worked this out. The only firmware it says is approved for my device is the next up on the list - EVAL09C432B330-LOG.
This downloads fine through the stock Huawei update menu (as if i am just doing a normal update) and the phone reboots but then the installation fails, whether I choose the full package or standard update option.
Click to expand...
Click to collapse
do you have a way to get the files from firmware finder onto your SD card? If so create a folder called DLOAD on the root directory and then put the update file in that folder. Power off the phone and hold all three buttons (power and vol+/-) until you get the firmware updating screen.
Let me know if it still fails.
Thanks. Will doing this cause any mismatches in future and stop me being able to receive OTA updates, or affect Android Pay?
I have put the update.zip in a folder called dload in the root of the SD but neither the boot method of installation nor the dialler method seems to find it. I've tried with a different update.zip with the same result
leoni1980 said:
I have put the update.zip in a folder called dload in the root of the SD but neither the boot method of installation nor the dialler method seems to find it. I've tried with a different update.zip with the same result
Click to expand...
Click to collapse
Who told u that??, incorrect my friend,extract the update.zip and put only update.app inside dlod folder in the root of your sd card,it is explain hunderds of time everywhere
Hi, this isn't all that clear in the other instructions I've read, and historically flashing update.zip from the root of an SD card is quite a typical way to flash software, so you can understand the confusion!
Are you sure this will work? Other threads online indicate that flashing is much more difficult than this and requires unlocking the bootloader. Am I missing something here?
I also tried this but failed on my phone. I put the update.app in the dload folder but always fails after about 14%
leoni1980 said:
Hi, this isn't all that clear in the other instructions I've read, and historically flashing update.zip from the root of an SD card is quite a typical way to flash software, so you can understand the confusion!
Are you sure this will work? Other threads online indicate that flashing is much more difficult than this and requires unlocking the bootloader. Am I missing something here?
Click to expand...
Click to collapse
after you download the zip file and then unzip it. Put thr UPDATE.APP in the dload folder on your internal memory. and then perform the update.
sprouts4all said:
I also tried this but failed on my phone. I put the update.app in the dload folder but always fails after about 14%
Click to expand...
Click to collapse
try redownloading the file.
sprouts4all said:
I also tried this but failed on my phone. I put the update.app in the dload folder but always fails after about 14%
Click to expand...
Click to collapse
Just to let you know, after downloading a bazillion files and trying every method under the sun I finally got this to work. It is now running B386 firmware.
Using the manual update method didn't work for me; the steps I had to follow are as follows:
With Firmware Finder, choose the B386 full OTA package - check for compatibility first (it said mine was compatible with it) and choose to install via proxy. Set up your WiFi to run the localhost/8080 proxy settings as instructed by FF. While the file is downloading, remove the proxy settings from your WiFi, allow it to reconnect and continue the download.
I then just left the phone to its own thing. I was actually watching a video in the background when it rebooted itself and began the installation process, which didn't fail as I expected it to.
Everything seems to be running fine now.
Thanks to the person in this thread who suggested using Firmware Finder.
leoni1980 said:
Just to let you know, after downloading a bazillion files and trying every method under the sun I finally got this to work. It is now running B386 firmware.
Using the manual update method didn't work for me; the steps I had to follow are as follows:
With Firmware Finder, choose the B386 full OTA package - check for compatibility first (it said mine was compatible with it) and choose to install via proxy. Set up your WiFi to run the localhost/8080 proxy settings as instructed by FF. While the file is downloading, remove the proxy settings from your WiFi, allow it to reconnect and continue the download.
I then just left the phone to its own thing. I was actually watching a video in the background when it rebooted itself and began the installation process, which didn't fail as I expected it to.
Everything seems to be running fine now.
Thanks to the person in this thread who suggested using Firmware Finder.
Click to expand...
Click to collapse
What firmware was you on before. I have tried this method with other versions but no luck. I will try with the B386.
sprouts4all said:
What firmware was you on before. I have tried this method with other versions but no luck. I will try with the B386.
Click to expand...
Click to collapse
I was on B182. If you're on the exact same firmware as me then try the steps above exactly and you might have more luck. I also deleted all old downloaded update files before I commenced with it.
Thanks
leoni1980 said:
I was on B182. If you're on the exact same firmware as me then try the steps above exactly and you might have more luck. I also deleted all old downloaded update files before I commenced with it.
Thanks
Click to expand...
Click to collapse
Still didnt work, went to install but failed. Says incompatible firmware
Follow these like i just did
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
mazsuper said:
Follow these like i just did
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
Click to expand...
Click to collapse
Didn't work, managed to get to B360 but now Huawei apps are missing including camera
goto b300 then b182 then follow above instructions , and rtfm
skip 361 and goto 378 via hisuite update
Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
SideSkroll said:
Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
Click to expand...
Click to collapse
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
zgfg said:
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
Click to expand...
Click to collapse
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
SideSkroll said:
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
Click to expand...
Click to collapse
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
zgfg said:
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
Click to expand...
Click to collapse
Thank you. Thats exactly what I was looking for. I really appreciateyour help.
Btw, no one should have the "hide extensions for known file types" checkbox marked...
Edit: Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
SideSkroll said:
....Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
Click to expand...
Click to collapse
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
SideSkroll said:
Thats exactly what I was looking for...
Click to expand...
Click to collapse
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
zgfg said:
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
Click to expand...
Click to collapse
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
SideSkroll said:
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
Click to expand...
Click to collapse
This small OTA bringing Patch02 over b540 installs even over TWRP (but that was not the case for OTA from eg b535 to b540)
Cannot discuss/compare battery for Omni Pie, since not using Omni
Problem with Camera app does not show on stock Oreo. Even if the app was somehow ported from Huawei, there are maybe problems with integration to Omni.
Various Huawei/Mate models come with different cameras, but there is only one OK Omni ROM (with one Camera app) given to work on all Huawei/Mate models
Btw, somebody else also complained about issues with Camera (and GPS) and decided to go back to stock Oreo.
Similarly, issues you described about black notifications or so must be related to the custom ROM, theme or so.
As a general rule:
- for installing OK ROM, you flash System partition, and nothing else
- you also wipe Data partitiom (containing all your installed apps, incl Magisk Manager, also containing your user settings)
It does not affect any other partition.
Therefore, changes given by NW patch persist - without, you will have (also in that OK ROMs) problems with SIM card(s) and connecting to the network
Also, Magisk, which was flashed to Ramdisk, persists. You must only install Magisk Manager again, because it is user apo, installed to Data partition that was wiped
You must check on the OK side how they advice installing the updates of OK ROMs
(It is questionable if they will get updates any more, since OK team switched to development of ROMs which install over the stock Pie, whereas on P9 you have no stock Pie - only Oreo, and most likely, we will never see stock Pie for P9.
Just check when OK team released last ROM for stock Oreo, and compare with their releases of OK ROMs for stock Pie:
https://openkirin.net/download/
Hence IMO, for updating the OK ROM (if/when it comes), you will again just need to flash its System and to wipe Data (and then to reinstall user apps like Magisk Manager).
Hopefully, you can backup and restore some apps and settings by Titanium.
Whether you don't need to wipe Data for such update - check from the OK support.
On the Open Kirin site you will find Support pages (Faq, HowTo) and also a link to the live Telegram channel
Updating from an update fileI have been seeing a lot of posts about people not receiving the OTA on their phone, and got tired of linking my instructions, so I decided to make a separate post
Download the version that you need from the Asus Zenfone 8 Support page (Note that if you are not on the latest Android 11 firmware (30.12.112.72), you will not be able to Android 12. So you need to do these steps with the latest Android 11, and then re-do them for the Android 12 firmware)
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
not work for me :/
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
eVen123 said:
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
Click to expand...
Click to collapse
I think that what is needed is to update to the latest firmware, then Android 12. So if you are already on Android 11, but not latest firmware, install it with the instructions, then do the same to update to Android 12's latest version.
drum94 said:
not work for me :/
Click to expand...
Click to collapse
What part does not work? Please be more specific and also, you should re-read the steps more carefully, in case you missed something
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
drum94 said:
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
Click to expand...
Click to collapse
It also depends what prefix your installation has. See the first letters
UL-...
If you are from some other region, it could be that UL- is not a fitting upgrade option for you. As far as I can tell, it's not possible to tell which of the versions you have.
I give you the build number which is marked in the software information:
RKQ1.2021022.002.30.12.112.72
I have the right version or not suddenly?
Thank you for the quick tutorial. I was doing this via fastboot till now.
However: I upgraded to the latest firmware BEFORE Android 12. No issues.
Then I upgraded to the Android 12 firmware: stuck. Gave me some kind of ram dump, reboot returned me to the same error: bootloop. I was able to reboot and get to the bootloader. After selecting "recovery" it actually booted Android. And now for the weird part: it looks like I have a mix of Android 11 and Android 12 now! The phone is all but unusable for how slow it is. But the main UI looks like Android 11 still, but things like the reboot screen now look like Android 12. Bizarre...
I was at least able to enable ADB debug again, so I think I will be able to recover the phone. Still a weird issue though. Don't know if flashing with fastboot would have prevented it...
If anything fails, you can always try the Asus flash script it will solve most of the issues with your phone, just note that it installs Android 11 (30.11.51.115)
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
EDIT: nvm, I saw your other reply, you alreay tried that. Were you able to get it working again?
Going from WW-30.12.112.82 to WW-31.1004.0404.107 worked flawlessly, i did not lose settings or data on that upgrade (but I want to stress that a good backup is STILL a very good thing to have!) It then started downloading the 31.1010.0410.43 upgrade on its own. (shown in the ui as SKQ1.210821.001.31.1010.0410.43)
Why didn't I upgrade to the latest one myself? Simple: I goofed up and downloaded the older one.
change the name in UL-ASUS_I006D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Hi, has anyone tried to upgrade a firmware that has Magisk and TWRP installed? Today Android 13 has been released for the Zenfone 8, but I wouldn't really like to do something really dumb such as upgrading, rebooting to recovery to reinstall Magisk only to discover that TWRP has been replaced by the stock recovery and the phone completely erases any data it has stored.
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Rokcy98 said:
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Click to expand...
Click to collapse
Thank you! As this is my first phone with A/B slots, I wasn't completely sure about how to proceed. I'll follow your instructions! The only thing I don't get is where is TWRP stored and why it won't be overwritten by the update.
EDIT: installed successfully, thanks!