Database Develop

[Q] Rooted 5.0.1, OTA update to T-mo 5.1 offered, failed. How to proceed?

Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!

a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.

So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.

RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/

Rooted Nexus 6 and updating to android 6.0

Hello all,
i rooted my nexus 6 and now that android 6.0 has been release i can't install the upgrade. My phone shows there is a system upgrade available. I have clicked to download the upgrade. Now its showing that a system upgrade has been downloaded and verified. Once i click on install update, it reboots to the teamwin. And to be honest, i don't really know if its taking the updated or how i can upgrade if possible.
can someone help me please?!!!!

Same answer every time. You can't get the OTA if you're rooted.
Options are :
- flash factory image (see sticky roll-up in general)
- flash a pre-rooted zip from recovery.

if you dont want to lose your data. just flash system.img, boot.img and recovery.img of your current build.
you can extract the images from the factory image...

Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it, as I did with my Nexus 10 a couple of years ago.
Your best bet is to use Wugfresh's Nexus Root Toolkit (NRT). Since this is a major upgrade you can't use the "no wipe" option, so you'll lose any data that you haven't backed up first - photos, etc. - so do that before you do anything. Also take a TWRP backup of your current ROM and copy it to your PC so that at least you can recover to where you are now. NRT also has a backup option.
If you tell NRT that your current ROM is MRA58K (Android 6.0) and then tell it to flash stock and unroot, it will pull down all the required files before applying them to your Nexus. You can then re-root if you want to. It's a beautifully-engineered program, pretty well foolproof if you follow the instructions and choose the right ROM for your device.

dahawthorne said:
Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it
Click to expand...
Click to collapse
It cant get to that stage any more.

Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.

dahawthorne said:
Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.
Click to expand...
Click to collapse
OTA zips used to check individual files in system to ensure they matched before updating. It checks either md5 or sha hash. It didn't take account of every file or even files added by the users. so upgrading could cause issues.
Now, it checks the md5/hash of the entire system, which means all files are taken into account.. It will not flash of anything is changed.

Thanks - happy to roll you over to 19,400...

Error applying OTA update from 23.1.A.0.690

I rooted the stock 4.4.4 my Z3C came with (without unlocking the bootloader), and then applied the OTAs as they appeared.
The device is still rooted according to Root Check and on 23.1.A.0.690
Now there is another OTA being offered (only 11.7meg). When it reboots to apply, the progress bar under the graphic only briefly moves to ~10% and the the phone boots fully. But it says "Software update: could not install new software version. please try again" after I enter my pass pattern.
Trying again doesn’t change anything.
Is there a log file or something I can check to debug ?
Edit: used FlashTool http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 to upgrade to the next verson (D5803_23.1.A.0.726_Generic UK) *without* clearing USERDATA. After that reboot (and slightly panicky longer than expected time to flash), a new OTA update appears that was much larger (~10meg). That one downloaded and installed exactly as expected, and I'm now on a couple of versions after that with all my previous data intact.
I did not retain root. giefroot will come to the rescue I'm sure once all the updates are installed. Another 200meg of OTA update just showed up!

What is the purpose of each of the 3 different update zip files ?

Hi,
Sorry of this is a bit of a newbie question but:
What is the purpose of each of the 3 different update zip files ?
And do I have to apply them all - and in what order ?
In my case, I am about to update to B389, and I have downloaded 3 files for VIE-L29C636B389 (currently on VIE-L29C636B130), and I have an update.zip, an update_full_VIE-L29_hw_spcseas.zip and an update_data_full_public.zip.
I was planning on doing the first two by the dload method (with reboots in between), but the update_data_full_public.zip doesn't appear to have an update.app, so how do I load that ? (I do have TWRP on my phone, so could probably figure it out - eventually).
Cheers,
SZ

same question
I read somewhere that it should be flashed in that exact order. i'm guessing that is the same procedure as with auto OTA updates, except now we have rooted phones, so bye-bye to auto updates. I am currently on VIE-L29CB636B387 and i received an automatic Huawei notification of a new version (VIE-L29CB636B388) about a week ago. I tried to update to that version in System Update-Quick Update, but that didn't work (surprise!). There was no issue though as when I rebooted it just went back to 387. However, I now have a red "New Version" notification in my System Update. Please tell me how your upgrade went if you went ahead and flashed 389. I have the three files already from filefinder, i also have TWRP and/or I could use adb fastboot to install. Thanks in advance.

Hey,
I am not sure I want to proceed on the basis of something that somebody 'read somewhere' ....
Anyhow - I've not run these updates yet, as I wanted to backup my phone first, but TWRP keeps blowing up with an error in the middle of the backup, so I am not going to try anything until I get to the bottom of that.
Will let you know if/when I ever go ahead!
Cheers,
SZ

Hi,
TWRP blowing up during NAND backups? thats not a good thing. Upon the advice of a forum member (xzanium) I flashed TWRP 3.1.1-1 instead of TWRP-3.2.1-0-vienna. No hitches so far, solid backups and no hiccups in flashing SuperSU, also got xposed to work seamlessly and other stuff. I hope you are able to resolve the issue you mentioned and get around to getting VIE-L29CB636B389 on your phone.
Well good luck to you, and post here any progress if you would.

SZ,
I have an idea on what the purpose of each of the 3 different update zip files are for and whether you have to apply them all - and in what order.
Since I could make a NAND backup using TWRP without issues, and there was an OTA update notice for an upgrade to VIE-L29CB636B388 which I couldn't upgrade to while rooted, I decided to unroot in order to upgrade to that. First i did the requisite steps - uninstalled the xposed framework and proceeded with the full unroot with SuperSU. Then I performed the dload method to flash the update.app that I extracted from the update.zip.
It was here where i hit a snag. What followed was, I found out that Huawei needs a verified stock rom, meaning it has to be a fullOTA-MF-PV in order that the bootloader could be relocked. So I tried my luck and downloaded the stock ROM VIE-L29C636B370 and flashed that. Success! From there, and several auto upgrades later I was back to L29C636B370. Reinstalling my Google account also locked back FRP. At this point i am full stock EMUI 5
Now, to answer your question. When I tried to upgrade to VIE-L29C636B388 via system update quick update. I only saw one file - update.zip therefore this must the only one needed for incremental patches. The same holds true with update_data_full_public.zip as I later learned when I decided to use the proxy upgrade method in MT filefinder . It applied a 2nd patch. The third file, namely, update_full_VIE-L29_hw_spcseas.zip was not required for this incremental update. In fact, the update process was cut short and an error message appeared that the file could not be located, even though i copied that to the HwOUC folder. It appears that this was deleted before the fullOTA update could finish during the incremental update process. Clearly, this last zip is not necessary for incremental updates. So this must be the package which delivers the rest of the ROM, or the parts of it that needs to be changed.
So, obviously what "I read somewhere" was legit. I hope that answers your question.
cheers!
mm

Looking to flash OK Pie on P9 Any help would be appreciated.

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