Related
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
Are you on the correct bootloader 10.26.1.18 as is required?
EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
I've not heard of this ocurring (my own tab has been running for a while now; no issues of this sort).
Are you on the latest ROM build (01/29)? Have you flashed the appropriate gapps?
Are you on the latest boot loader?
Any apps installed which could cause issue?
If it happens when plugged in to USB, is isb OK on your PC/Mac?
Have you used titanium backup to restore system level stuff from a non compatible build?
Do this,
Go back to stock (latest release from asus) and observe for an hour or two. Any issues? If not then flash ROM + gapps and wipe. Don't sign in and don't restore apps. Any issues? Then sign in and restore. Any issues? And so on and so forth until.you find the break point.
Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Pershoot once the new CM11 was first flashed the TF701 would freeze during the setup steps well before any 3rd party apps could be installed. After a number of attempts I manage to get through set up and the system becomes a lttle more stable but then freezes after a few more minutes. I can conform that the correct gapps has been flashed using the link on the associated thread and no additional apps except the ones included on the ROM have been flashed. The system freezes without being plugged into the PC via USB and as mentioned before I am coming from sdbags stock rooted 4.3 ROM and have not used titanium back up at all.
A couple of additional point
1) I have tried to reflash sdbags ROM again but it now gets stuck on a bootloop.
2) I noticed that my install of CM11 is not able to access either an SD card placed in the dock or MicroSD placed in the tab despite the system recognising when they are inserted or removed on the task bar.
3) Because the system freezes so quickly it tabvery difficult to transfer a new ROM downloaded to my PC over to the TF701 because the moment it freezes the PC can't communicate with the tab.
Apologies if this reply is a little onerous - any help would be greatly appreciated and thank you both again for your prompt response to my.request for help.
Kind regards,
East
Hold down Volume Down and Power and read the bootloader version from the top left.
EastPatel said:
Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Click to expand...
Click to collapse
That's the wrong BL to be on. I don't believe sdbags' ROM updates BL. You must do it via Asus's update.
Go back to stock recovery and follow asus's procedure to update yourself to their latest 10.26.1.18 (4.3) build.
Dear SD Bags & Pershoot,
Apologies for not responding to your feedback sooner - Its been a busy week at work.
I will follow your advise and update the bootloader via the ASUS website and try to reinstall the rom again over the weekend or early next week and I will update this thread with the results. Once again apologies for not following the instructions more carefully.
Many thanks & kind regards,
East
Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East
EastPatel said:
Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East
Click to expand...
Click to collapse
I have a work around for Sky Go on rooted devices You didn't ask.
PM Please.
Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?
Jrockstar867 said:
Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?
Click to expand...
Click to collapse
Kernel needs recompiling with fixes in it - not a huge job but something I have on my todo list - won't be for a while though.
Is there a thread I can subscribe to to get the latest news??
Sent from my Transformer TF701
guys, can anyone knows how to revert to android 4.4.2 android 5.0.1 with? updated firmware bass headphones disappeared, this problem occurs not only at me. who are important sound in the headphones do not advise upgraded. ASUS disappointed by this update.
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
BerndHhn said:
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
Click to expand...
Click to collapse
I tried to downgrade the firmware. but in the new android 5.0.1 bootloader and recovery, and this does not take recovery firmware based on Android 4.4.2. And here is the update on the official website for ME572C, but only TW version, WW firmware not yet available. http://www.asus.com/ru/supportonly/ASUS MeMO Pad (ME572C)/HelpDesk_Download/
Yeah
I installed this night.
Sound is fine.
Tested on Audio Out and Bluetooth, but unfortunately no root possibility yet.
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Frisian said:
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Click to expand...
Click to collapse
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
Thats awful for you. Can't you get into any recovery anymore? Perhaps flash the 5.0.1. again?
I'm not going to try to downgrade but I wish I hadn't installed lollipop. I really like this tablet and everything worked perfectly. Now I have to rotate the screen manually. I cheked the sensors with a diagnostic tool and they are working fine. It's the software. It isn't known what triggers the bug so it could happen at any time or never. Nice work google.
Hopefully we'll have root and custom mods in the near future.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
If you can boot back into the download screen, you can probably reflash the newest firmware.
pWEN said:
If you can boot back into the download screen, you can probably reflash the newest firmware.
Click to expand...
Click to collapse
does not work, bootloader killed, dependent on Intel Inside logo.
Hi, i try at the moment downgrade from the me581cl. It looks good. You can look at my thread Root with downgrade for the intel developer tool.
The highest importent file is the ifwi.bin.
You can it flash with fastboot flash dnx .....
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) with the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
kanagawaben said:
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) to the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
Click to expand...
Click to collapse
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
gmaxjp said:
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
Click to expand...
Click to collapse
I did a factory reset and the WW 5.0.1 seems stable again now. Would still like to return to a rooted 4.4.2 if possible though.
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Myuboku said:
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Click to expand...
Click to collapse
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
gmaxjp said:
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
Click to expand...
Click to collapse
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Myuboku said:
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Click to expand...
Click to collapse
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
tycoo said:
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
Click to expand...
Click to collapse
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Myuboku said:
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Click to expand...
Click to collapse
Ya, that might be true.
tycoo said:
Ya, that might be true.
Click to expand...
Click to collapse
Also as i know, there is a person who has service firmwares. As he explained, when flashing service lollipop firmware, it somehow unlocks bootloader(i can be mistaken at this part), and makes it possible to install any android firmware.
Hello,
This is a short (hopefully) guide on how to downgrade your Moto X 2013 from Android 5.1 to 4.4.4 (and lower).
The procedure is fairly simple and takes about 10-15 minutes, once you get the files you need.It does however needs some technical understanding of how to use fastboot, command prompt and eventually unlocking your bootloader.Fairly strong reading skills recommended.
WIth that said, make sure you read thorough and even few times before you take any actions.
This method has now been proven to be working by multiple people, on many different versions of Moto X 2013, including GPE
Disclaimer
Although this procedure has been tested by me and some friends numerous times, it still has some risk involved.You MUST be aware of the potential risks of modifying your phone software and performing actions that may lead to complete defunct of your device.
As you may expect I will not take any responsibility or be accountable for any damage or loss you may incur by following this guide.
Performing a system downgrade WILL void your warranty and it is NOT supported by Motorola/Lenovo or their service network.
I also recommend you read This post by KidJoe about the potential risks that downgrade might involve.
This guide has came up being needed as many people were afraid to downgrade after reading the post of KidJoe and I don't blame them, it is possible something to go wrong and you end up with non-working device.
HOWEVER, this has been tested on more than 10 separate Moto X 2013 and more than 12 times on my own device, which makes me to believe that it's generally safe.
Prerequisites
You need your bootloader unlocked.Motorola and their bootloader does NOT support downgrading and it will spit errors in fastboot.
WHEN YOU UNLOCK YOUR BOOTLOADER ALL YOUR PERSONAL DATA ON YOUR DEVICE WILL BE LOST.MAKE SURE YOU BACKUP YOUR FILES AND THEN PROCEED.
You can find how to unlock your bootloader HERE or just use the search here in the forums, plenty of info on that matter.
If you cannot or don't want to unlock your bootloader, then you CANNOT downgrade.
Files Needed
For this tutorial we`ll do downgrade from 5.1 to 4.4.4.This is the safest downgrade and it will be successful if you follow all the steps w/o any skipping.
The Android image used is for XT1052, but if you got different model, you can find the image for your own model and use that instead.
1.First you need a signed image of Android 4.4.4 for Moto X 2013.You can find one Filefactory or RetailEU here <=> RetailGB here <=> RetailDE here
If you want to download the image faster, use the Yandex-hosted images, FileFactory is slow.
2.Motorola Device Drivers: You can find them Here
3.Motorola Fastboot and generic adb/fastboot tools package: You can find it attached to this post or click Here
Flashing your device
0.Charge your device's battery to at least 35%.
1.Extract the archive with the signed images somewhere (in this case I`ll use C:\temp , but you can use any drive or directory if you so desire).
2.Extract the android-tools archive in the same directory.You should have boot.img, recovery.img, system.img and mfastboot in same directory.
3.Reboot your device in bootloader (Power your device off -> Hold Volume Down and Press Power button -> then release).
!!THIS WILL DELETE YOUR USER FILES EVEN IF YOU HAVE YOUR BOOTLOADER ALREADY UNLOCKED!!!
4.Open a command prompt and navigate to C:\temp and execute the following commands:
Code:
mfastboot erase cache
mfastboot erase userdata
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot erase userdata
mfastboot reboot
DO NOT skip erasing the userdata, doing so , you'll most likely end up with soft brick.Just don't do it.
Result
Congratz, now you have successfully downgraded your device to Android 4.4.4
The device will take some time the first boot to create dalvik cache and some other stuff, but it should not take more than 5 minutes.
When your device boots, it will ask you at some point to downgrade the motorola services bla bla, agree to that, your device will reboot and it will tell you that the downgrade was successful.I did this more than 10 times, seems to be totally safe.
Any feedback will be appreciated, you may ask questions, but don't expect me to answer to every single one.
If I missed something, I'll add up/fix as soon as I can.
FAQ
What if I want to downgrade to Android 4.4.2 / 4.3 / 4.2.2 ?
This is possible, the procedure is the same as listed above.You just have to know that if you do such downgrade, you should never update via OTA update, at any cost.This will corrupt the bootloader of your device and you won't be able to restore it.If you downgrade to anything below 4.4.4 and you want at some point to upgrade, you should do it ONLY by official signed image and NOT OTA.
You've been warned.
I can't find the exact same firmware that my device runs, eg. AsiaRetail.Is it possible to use firmware image from a different region/operator?
While it's recommended to use your exact firmware image, it is not necessary. You can use an image from other region, but you should follow some simple rule. Try to stick to the same phone model, eg XT1052 firmware.
I updated via OTA but I've recently rooted and installed a custom rom. Is it necessary to go back to stock 5.1 to downgrade?
No need, as long as your custom rom/kernel didn't mess with the fs of the partitions.
Why is this flashing procedure cut down, omg there are other commands that I've read in other guides and they say that I must flash modem, fsg, delete some magical modem states, why you didn't include these?!?
While it is true that other guides suggest you flash modem, fsg and some other things, these are mainly driven from the Motorola's own procedure xml file, flashing these is not necessary at all, this is used to repair eventual errors in these parts, but usually there is no problem there at all.
Another thing is that these parts are cross-compatible and leaving them as they are is perfectly fine.
How do I go back to 5.1 stock?
1.Do NOT update by OTA, just to be on the safe side.
2. Use the same procedure as described, but with image of 5.1 instead.
How do I disable the OTA notifications?
1. If you're rooted, then just delete or revoke permissions of /system/priv-app/3c_ota.apk
2. If you're not rooted, then don't install the Motorola Update Services from the Play Store. If you already updated them, then just uninstall the update and that's all.
I'm getting "Not enough space" errors, when I try to flash the system.img.I'm using mfastboot, but still the same problem?!?
Use this and it will work:
mfastboot flash system system.img -P
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
legend.in.boxers said:
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
Click to expand...
Click to collapse
Having custom recovery doesn't affect anything. This process will flash the stock recovery.
You don't need to enter any mode in the list, just leave the phone in the bootloader menu.
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
SanD-82 said:
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
Click to expand...
Click to collapse
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
I also have a problem with the optimising apps bug every time I reboot. Going to downgrade today. Hopefully everything will go well
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
SanD-82 said:
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
Click to expand...
Click to collapse
That's not the case either, it was set to never keep it on during sleep and scaning always available was not allowed.The wifi just wont go off durring sleep and that's it.Tried all possible settings to no avail.Actually wifi was the 2nd highest battery consumer in the stats after the screen.This problem does not exist in 4.4.4.
I see...
It's actually hard to see how in 2015, Android keeps having these deal breaker issues...
I somehow feel that the best version of my xt1058 was when it was at 4.2.2... After the subsequent updates, bugs started to appear, and on 5.1 i got the first big issue...
Sent from my XT1058
Works!
Successfully downgraded. Thank you so much!
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
SanD-82 said:
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
Click to expand...
Click to collapse
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
IS Android 4.4.2 or 4.2.2 files avalable for indian moto x (xt1052 asian retail)
liveroy said:
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
Click to expand...
Click to collapse
WHere can i find those files??
visheshjotshi said:
WHere can i find those files??
Click to expand...
Click to collapse
Check the first post, the File Factory link, you can find tons of images there, the moto x 2013 is codenamed Ghost, if there is no model listed.
Good Luck.
Cant find files
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
visheshjotshi said:
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
Click to expand...
Click to collapse
Try searching 4pda.
Also, you don't need exactly your original firmware to begin with, it's recommended, but not necessary.
Thank you for this information. I dont have the wifi bug. But i have the mobile data bug. (Even turning it off it still continues to sap battery)
Sent from my XT1052 using XDA Free mobile app
I was looking for a post like this becouse my WiFi doesn't work on XT1058 5.1... i thought was a Lollipop related issue so wanted to downgrade to 4.4.4 and see if the problem really was related to android version, but it isn't. I downgraded successfully from 5.1 to 4.4.4 with your tutorial, but the WiFi problem persist. Now i know i'm really screwed up becouse i tried i believe everything possible... airplane mode, factory reset, cache wipe, full wipe, custom rom, custom kernel, android 5.1, android 4.4.4, different AP's and routers, delete supplicant conf... So i don't know what to do. Te specific problem is that WiFi can see available networks, but randomly some of them disappear and others show up, and when i try to connect por ex to my home network, it says "connecting" and then "saved", with all networks happens the same. Does anyone has a clue? BTW, thanks for your post!
Download the archive from this link https://app.box.com/s/idnxxhunecvtxf1mbqve0bpooyogvxng
unzip it on your device and copy the files to /persist.You need root to do that. Set the permissions to rw-r-r--- and rw-rw---- for the .bt_nv.bin
Reboot and see if something changes.
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
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