Database Develop

MIUI Global 7.2.4.0.0 uses A LOT of RAM. (?)

Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.

proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0

Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!

androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.

i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..

7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working

Mediapad M3 Lite 8 - Bootloader Unlock Guide

Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:

I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?

I recently have been purchased the LTE version of this device. Although I cannot try this out currently, I probably will in the future so please keep us updated about your experiments for reference!

avkjbl5bak said:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
Click to expand...
Click to collapse
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks

howgies said:
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
Click to expand...
Click to collapse
I have my Mediapad M3 Lite rooted by magisk.
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
I download and installed latest magisk app.
I opened the magic app-> install -> install -> patch the boot image file which I then flashed through fastboot.
I then opened magisk -> install -> Direct install.
Everything works but like me you take a risk in not using the exact boot.img.
I tried and installed TWRP which worked but the volume keys would let me run the script I was trying to rebrand the phone. In the end it isn't necessary to root the phone.

sd26 said:
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
Click to expand...
Click to collapse
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!

nicolap8 said:
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
Click to expand...
Click to collapse
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.

sd26 said:
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
Click to expand...
Click to collapse
if my reply is too poor, report it to mods...
A post like your IS an advice because people read and follow it. What is wrong is not that you write or my opinion but people behaviour
I read the "risk" word but a lot of people would not. This is also the reason I don't wrote the dd command: search and learn! Most of the messages you read here are of people who have broken their own terminal because just followed a post like your, without knowing what are doing.
N

sd26 said:
Everything works but like me you take a risk in not using the exact boot.img.
Click to expand...
Click to collapse
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc

#marcg# said:
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
Click to expand...
Click to collapse
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.

sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I have

avkjbl5bak said:
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
Click to expand...
Click to collapse
Did you ever get and answer to your question about cloning or getting the original factory images. I've been trying on and off for 9months. I have unlocked the bootloader and backed up using TWRP (from the 10inch model), but when I relocked the bootloader everything fell apart... unstable boot loops, etc. not sure if I had to wipe recovery I burned with TWRP or what. Also TWRP does not back-up the data partition I think due to encryption (from other posts I read). My goal was to rebrand a pile of the Chinese version tablets I have to US because we use them in our product, and the US are not available, so rebranding would give me more time before to find a replacement. Any clues would help!!!

sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I successfully rooted my CPN-L09 without loosing fp sensor, have a look here: https://forum.xda-developers.com/mediapad-m3/help/to-patch-boot-img-magisk-v17-3-t3938629

Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex

bigprat9 said:
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
Click to expand...
Click to collapse
You have to use the calculator in landscape mode (turn on auto-rotate) and then the bracket buttons will appear.
So I finally got around to installing this on my stock version. I found 16GB was too limiting and I was hoping to use the SD card to expand the space so I could use it for a few more years. I purchased the code from DC_unlocker.
A couple of things I noticed while following the guide. To enter fastboot mode, holding down the volume down and power button doesn't seem to work. What you to do is while it's off, hold down the volume down button and plug in the microusb cable, while continuing to hold it down. You could also enter fastboot using an ADB command.
Also I couldn't wipe anything before installing the new roms, I got error messages. I'm not sure what that means. Anyways after installing android 9, it seemed to take a very long time to first boot. The graphic animation is going, but I wasn't sure if it was working so I hard reset once, tried to boot again and then waited again, hard reset again and put it down thinking I would have to look into the error messages and when I came back it was up and running.

Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.

lawhec said:
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
Click to expand...
Click to collapse
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .

surdu_petru said:
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
Click to expand...
Click to collapse
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!

lawhec said:
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
Click to expand...
Click to collapse
Thank you very much too

Hello
I followed the steps here to unlock the bootloader with my btv-dl09, that worked fine even its not lite.. :fingers-crossed:
but now, any clues? may i ll try the way of lawhec with
lawhec said:
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
Click to expand...
Click to collapse
but cant find the TWRP 3.3.1-1?
may u Mean
[Recovery][Official] TWRP 3.3.1-10 [G97*0][Snap][3.Jan.20]
[Recovery][Official] TWRP 3.3.1-12 Snapdragon [N97x0][10.Nov.19]
[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J6+/J610F/FN/G/DS
???
if so, why u choose one of these? No Clue for me^^ plz let me know
greetz
ADD: just found
Developed By :letschky
twrp-3.1.1-1-next.img
Jul 13, 2017 | 03:32PM
maybe these? looks pretty old but still working? Oo

T-Mobile OnePlus 6T downgrade process from Q Beta

I have a T-Mobile OnePlus 6T that I used the MSM tool to flash to the International ROM. I then installed the beta builds, but decided to fly even closer to the sun and install the Q Beta dev build.
That last step was too close and the phone ended up having tons of issues - reboots every time the screen went off, network issues, but the biggest was it wouldn't enter the state required to run the MSM tool nor would it allow the option to OEM unlock in the OS. It was a bad time. I was desperate, but in desperation, was able to get myself back and figured I'd share the steps.
Step 1 - Download the Downgrade software and install from the OnePlus Q Beta thread
Step 2 - On reboot, you will get the error that informs you your hardware and software versions don't match
Step 3 - Press the two volume buttons to enter the state required for MSM
Step 4 - Run the MSM of your choosing
And you should be back. It was a bad 24ish hours for the phone, but I'm 100% back now. Hope this helps someone else.

mstrblueskys said:
I have a T-Mobile OnePlus 6T that I used the MSM tool to flash to the International ROM. I then installed the beta builds, but decided to fly even closer to the sun and install the Q Beta dev build.
That last step was too close and the phone ended up having tons of issues - reboots every time the screen went off, network issues, but the biggest was it wouldn't enter the state required to run the MSM tool nor would it allow the option to OEM unlock in the OS. It was a bad time. I was desperate, but in desperation, was able to get myself back and figured I'd share the steps.
Step 1 - Download the Downgrade software and install
Step 2 - On reboot, you will get the error that informs you your hardware and software versions don't match
Step 3 - Press the two volume buttons to enter the state required for MSM
Step 4 - Run the MSM of your choosing
And you should be back. It was a bad 24ish hours for the phone, but I'm 100% back now. Hope this helps someone else.
Click to expand...
Click to collapse
When you say downgrade software, are you referring to previous working ROM ? the msmdownload tool OP file?
your instructions are a bit confusing, first you say you couldnt get into the state to use the msmdownload tool, but at the bottom you say press both volume buttons to get in the msm state? So in other
words you can get into that state...
Also, is it possible you just had a bad install, Has anyone else with T-mo had this issue? It is well possible, I mean even know we are converted, its possible that some very important parts of the ROM
dont allow for convert, and when you install Q Beta, your still left with the P stuff that T-mo wont allow you to change.. But that is just a guess, Its never been officially verified that when we do
the conversion, what doesnt get changed and so on. Guess we just need more peepz to test this out on the T-mo before we throw in the towel on that..........

Eliminater74 said:
When you say downgrade software, are you referring to previous working ROM ? the msmdownload tool OP file?
your instructions are a bit confusing, first you say you couldnt get into the state to use the msmdownload tool, but at the bottom you say press both volume buttons to get in the msm state? So in other
words you can get into that state...
Also, is it possible you just had a bad install, Has anyone else with T-mo had this issue? It is well possible, I mean even know we are converted, its possible that some very important parts of the ROM
dont allow for convert, and when you install Q Beta, your still left with the P stuff that T-mo wont allow you to change.. But that is just a guess, Its never been officially verified that when we do
the conversion, what doesnt get changed and so on. Guess we just need more peepz to test this out on the T-mo before we throw in the towel on that..........
Click to expand...
Click to collapse
I have the T-Mobile version switched to international with msm and it worked fine, I flashed in twrp

peanutpajamas said:
I have the T-Mobile version switched to international with msm and it worked fine, I flashed in twrp
Click to expand...
Click to collapse
Yeah, I should have noted that I was not already bootloader unlocked so I did it through the OnePlus software update tools.

Eliminater74 said:
When you say downgrade software, are you referring to previous working ROM ? the msmdownload tool OP file?
your instructions are a bit confusing, first you say you couldnt get into the state to use the msmdownload tool, but at the bottom you say press both volume buttons to get in the msm state? So in other
words you can get into that state...
Also, is it possible you just had a bad install, Has anyone else with T-mo had this issue? It is well possible, I mean even know we are converted, its possible that some very important parts of the ROM
dont allow for convert, and when you install Q Beta, your still left with the P stuff that T-mo wont allow you to change.. But that is just a guess, Its never been officially verified that when we do
the conversion, what doesnt get changed and so on. Guess we just need more peepz to test this out on the T-mo before we throw in the towel on that..........
Click to expand...
Click to collapse
Yes, that's possible I guess.
And no, the downgrade tool that is listed on the same thread where the beta download lives.

Can't update my ROG Phone II

Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!

HyphenZzX said:
Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293

reg66 said:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293
Click to expand...
Click to collapse
but i don't understand i am already on ww fingerprint???

HyphenZzX said:
but i don't understand i am already on ww fingerprint???
Click to expand...
Click to collapse
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck

reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
hi thank you for the response when i open flash thing it just opens the cmd and closes again? what do i do?
edit never mind its doing it now thanks!

reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
thank you so much it works now quick question can i do manual updates now and get the latest firmware?

HyphenZzX said:
thank you so much it works now quick question can i do manual updates now and get the latest firmware?
Click to expand...
Click to collapse
Well, up until 1910.44, we were able to just download the updates from asus and put them in the root of internal storage... But this changed for many users with the .44 update, so I'm not sure... We'll have to see how the next update goes, but yeah, it'll either be through download of ota or by flashing raw rom... Either way it'll be posted here by someone. Won't be long to wait as China versions already have update .52 update, WW comes shortly after

Hi there I am in a similar situation with a tencent rog 2 purchased on ebay that is on android 9 WW version. Is it possible to flash WW_ZS660KL_17.0240.2107.100_M3.23.44.20-ASUS_1.1.232_Phone-user.raw to get to android 10 immediately? I have attempted it just now but it appears the flashall_AFT.cmd is stuck and i have waited around 20 minutes.
edit: I waited an hour and nothing seemed to happen. so I restarted the phone and it seems like nothing happened at all. Any ideas?

edit: accidental double post

Question How to flash Android 12 onto Asus Zenfone 8 and relock bootloader.

I'd appreciate it someone could provide instructions for a numpty, in a manner that the numpty (myself) can understand.
I unlocked the Bootloader on my Asus Zenfone 8 with a view to flash the stable version of Android 12.
My mistake was not having enough skill to 1. Flash Android 12 and 2 relock the Bootloader. I unlocked the Bootloader by using the official method from the Asus site.
Oh yes, I also retrospectively realised that I lost the ability to use Google Pay and Netflix. Oh, and I may not gain any OTA updates as well.
I've read and re-read countless articles and tried to follow many "how to's" but not being successful ... to me, it seems I'm missing a common sense step that everyone knows so well, that they feel doesn't need to be included in the how to's.
So I'm seeking a fool proof step by step guide for numpties (me) or someone who could step me through it
via DM.
I'm pretty much at the point to pay someone to assist me and sort out my Zenfone with Android 12 and a relocked bootloader.
Thank you in advance for any assistance.
Thomas

Follow the steps to revert back to Android 11 at the bottom of the page. This does not require an open bootloader https://www.asus.com/Content/Android-12-Beta/
You will then be able to place the latest update firmware on the phone with a computer. From that it will detect the update files and start the procedure.

Adaoh said:
Follow the steps to revert back to Android 11 at the bottom of the page. This does not require an open bootloader https://www.asus.com/Content/Android-12-Beta/
You will then be able to place the latest update firmware on the phone with a computer. From that it will detect the update files and start the procedure.
Click to expand...
Click to collapse
Hi Adaoh,
Thank you for the suggestion, but I have another query, before I proceed.
The link provided refers to the Android 11 version WW-30.11.51.115 but the stable version Android 12 version WW-31.1004.0404.81 states on the Asus website that it will only update to this version from Android 11 version WW-30.12.112.72
The Android 12 version referred to in the link provided is WW-31.0803.0403.54 a beta version which is older than the stable Android 12 mentioned above.
Are you aware of a Android 11 version WW-30.12.112.72 image file that can be utilised? I've not found one.
And my bootloader is already unlocked (referring to your comment that this does not require an open bootloader) so I would be seeking step by step instructions how to relock.
I'm keen to update to the Stable Android 12 version as I've read I may not receive any OTA updates, and so in my mind, a stable newer version of Android 12 is superior to an older beta version of Android 12.
Thoughts please?
Thanks for your input.
Thomas

TferThomas said:
Hi Adaoh,
Thank you for the suggestion, but I have another query, before I proceed.
The link provided refers to the Android 11 version WW-30.11.51.115 but the stable version Android 12 version WW-31.1004.0404.81 states on the Asus website that it will only update to this version from Android 11 version WW-30.12.112.72
The Android 12 version referred to in the link provided is WW-31.0803.0403.54 a beta version which is older than the stable Android 12 mentioned above.
Are you aware of a Android 11 version WW-30.12.112.72 image file that can be utilised? I've not found one.
And my bootloader is already unlocked (referring to your comment that this does not require an open bootloader) so I would be seeking step by step instructions how to relock.
I'm keen to update to the Stable Android 12 version as I've read I may not receive any OTA updates, and so in my mind, a stable newer version of Android 12 is superior to an older beta version of Android 12.
Thoughts please?
Thanks for your input.
Thomas
Click to expand...
Click to collapse
Hi, I do not think that there is a script provided like in the Back to Android11 link I gave you. I have used this method to recover my phone from a boot loop, so I think that the OS version does not matter but I am not sure, it is not impossible that it would brick the phone...
if you are still on A11, I did this script when I was on the latest Android 11 build and it reverted me to the old one in the script. So in my opinion it will be fine for whatever the condition of your phone are.
After this script, since you will not have OTA updates because your phone is blacklisted from Asus' servers, you will need to flash the last Android11 (from my understanding) and then once that's done flash a12.
Flashing updates is very simple, just do the last steps I gave in the original post

TferThomas said:
I'd appreciate it someone could provide instructions for a numpty, in a manner that the numpty (myself) can understand.
I unlocked the Bootloader on my Asus Zenfone 8 with a view to flash the stable version of Android 12.
My mistake was not having enough skill to 1. Flash Android 12 and 2 relock the Bootloader. I unlocked the Bootloader by using the official method from the Asus site.
Oh yes, I also retrospectively realised that I lost the ability to use Google Pay and Netflix. Oh, and I may not gain any OTA updates as well.
I've read and re-read countless articles and tried to follow many "how to's" but not being successful ... to me, it seems I'm missing a common sense step that everyone knows so well, that they feel doesn't need to be included in the how to's.
So I'm seeking a fool proof step by step guide for numpties (me) or someone who could step me through it
via DM.
I'm pretty much at the point to pay someone to assist me and sort out my Zenfone with Android 12 and a relocked bootloader.
Thank you in advance for any assistance.
Thomas
Click to expand...
Click to collapse
Try flashing a GSI using Android Flash Tool. Then use adb to reboot it into fastboot mode. Then just do
Code:
fastboot flashing lock

$cronos_ said:
Try flashing a GSI using Android Flash Tool. Then just use adb to reboot it into fastboot mode. Then just do
Code:
fastboot flashing lock
Click to expand...
Click to collapse
Hi $cronos_,
What is a GSI please? As mentioned at the start of my post, the simpler and more detailed the reply the better as I'm the numpty and happy to admit to that.
Thank you
Thomas

Adaoh said:
Hi, I do not think that there is a script provided like in the Back to Android11 link I gave you. I have used this method to recover my phone from a boot loop, so I think that the OS version does not matter but I am not sure, it is not impossible that it would brick the phone...
if you are still on A11, I did this script when I was on the latest Android 11 build and it reverted me to the old one in the script. So in my opinion it will be fine for whatever the condition of your phone are.
After this script, since you will not have OTA updates because your phone is blacklisted from Asus' servers, you will need to flash the last Android11 (from my understanding) and then once that's done flash a12.
Flashing updates is very simple, just do the last steps I gave in the original post
Click to expand...
Click to collapse
Hi Adaoh,
So what you're saying is to follow this link and take me to an older Android 11 version but then flash the most recent Android 11 version, then flash Android 12?
Question for you that has stumped me .... most people on forums and websites quickly gloss over flashing of an Operating System but don't actually go through the exact every step .... are you able to assist here please?
Again, as per the start of my post, I'm the numpty and happy to admit that, but do need to know comprehensively each and every step.
Thank you in advance,
Thomas

TferThomas said:
Hi $cronos_,
What is a GSI please? As mentioned at the start of my post, the simpler and more detailed the reply the better as I'm the numpty and happy to admit to that.
Thank you
Thomas
Click to expand...
Click to collapse
generic system image

TferThomas said:
Hi Adaoh,
So what you're saying is to follow this link and take me to an older Android 11 version but then flash the most recent Android 11 version, then flash Android 12?
Question for you that has stumped me .... most people on forums and websites quickly gloss over flashing of an Operating System but don't actually go through the exact every step .... are you able to assist here please?
Again, as per the start of my post, I'm the numpty and happy to admit that, but do need to know comprehensively each and every step.
Thank you in advance,
Thomas
Click to expand...
Click to collapse
Updating from an update file​Ok, so to update your phone when you can't receive OTAs:
Download the version that you need from the Asus Zenfone 8 Support page
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
Flashing the Stock ROM (Android 11)​Note: doing this will remove any data on your phone, back it up if it is important to you​This also works if your phone is stuck in a bootloop or other problems of the sort​If your question was about the flashing of Android 11 from the Android12 page with the older version, the instructions on the page at the bottom should be enough, but I can try to make them clearer.
Turn off the phone
When the phone is off, press and hold the Volume Up key and the Power button until a screen pops up.
If the phone boots to Android, shut it back off, but this time try lifting the Power button before the Volume Up key, because the power button is like an Enter key, it will take it as if you clicked "yes, continue to android".
Plug the phone in your computer
Decompress the zip file on your computer
Execute the script file that is made for your computer
Windows: update_image.bat
Ubuntu: update_image.sh
MacOS: update_image_for_mac.sh
Wait for the process to finish, it'll take a while. You'll know it is done when the window that openned when you executed one of the script files says something along the lines of "Flashing done, press Enter to reboot"
I hope this helps!

$cronos_ said:
generic system image
Click to expand...
Click to collapse
Thank you!
Thomas

Adaoh said:
Updating from an update file​Ok, so to update your phone when you can't receive OTAs:
Download the version that you need from the Asus Zenfone 8 Support page
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
Flashing the Stock ROM (Android 11)​Note: doing this will remove any data on your phone, back it up if it is important to you​This also works if your phone is stuck in a bootloop or other problems of the sort​If your question was about the flashing of Android 11 from the Android12 page with the older version, the instructions on the page at the bottom should be enough, but I can try to make them clearer.
Turn off the phone
When the phone is off, press and hold the Volume Up key and the Power button until a screen pops up.
If the phone boots to Android, shut it back off, but this time try lifting the Power button before the Volume Up key, because the power button is like an Enter key, it will take it as if you clicked "yes, continue to android".
Plug the phone in your computer
Decompress the zip file on your computer
Execute the file that is made for your computer
Windows: update_image.bat
Ubuntu: update_image.sh
MacOS: update_image_for_mac.sh
Wait for the process to finish, you'll know it is done when the window that openned when you executed one of the scripts says something along the lines of "Flashing done, press Enter to reboot"
I hope this helps!
Click to expand...
Click to collapse
Hi Adaoh,
I am really glad you have taken my request as seriously as this and I thank you for the very specific detailed reply.
I'm going to try this over the next couple of days (I hope) and report back, but really do appreciate this!
Thomas

Adaoh said:
Updating from an update file​Ok, so to update your phone when you can't receive OTAs:
Download the version that you need from the Asus Zenfone 8 Support page
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
Flashing the Stock ROM (Android 11)​Note: doing this will remove any data on your phone, back it up if it is important to you​This also works if your phone is stuck in a bootloop or other problems of the sort​If your question was about the flashing of Android 11 from the Android12 page with the older version, the instructions on the page at the bottom should be enough, but I can try to make them clearer.
Turn off the phone
When the phone is off, press and hold the Volume Up key and the Power button until a screen pops up.
If the phone boots to Android, shut it back off, but this time try lifting the Power button before the Volume Up key, because the power button is like an Enter key, it will take it as if you clicked "yes, continue to android".
Plug the phone in your computer
Decompress the zip file on your computer
Execute the script file that is made for your computer
Windows: update_image.bat
Ubuntu: update_image.sh
MacOS: update_image_for_mac.sh
Wait for the process to finish, it'll take a while. You'll know it is done when the window that openned when you executed one of the script files says something along the lines of "Flashing done, press Enter to reboot"
I hope this helps!
Click to expand...
Click to collapse
Hi Adaoh,
This worked on the second attempt! ..... now the Zenfone 8 is updated to the stable Android 12 OS.
Thank you and made clear runnings for this numpty!
Thomas

$cronos_ said:
Try flashing a GSI using Android Flash Tool. Then just use adb to reboot it into fastboot mode. Then just do
Code:
fastboot flashing lock
Click to expand...
Click to collapse
Hi $cronos_,
I got the Zenfone 8 into recovery mode and connected to the PC and initiated a Windows Powershell and typed the following to confirm the PC could find the Zenfone 8.
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot devices
M4AIB7626606MH7 fastboot
So it found the Zenfone 8
When I tried to Lock the Bootloader I got the following:
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot oem lock
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.005s
And tried your suggested command:
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot flashing lock
...
FAILED (remote: Unrecognized command flashing lock)
finished. total time: 0.005s
Any thoughts on what I am doing wrong please?
Thank you in advance.
Thomas

Hi,
I had the same problem as you, couldn't use Google pay.
All I did was open powershell and use the following command.
fastboot oem asus-csc_lk
Now it's relocked and works as before.
Hope this helps you.
Craig

mef206 said:
Hi,
I had the same problem as you, couldn't use Google pay.
All I did was open powershell and use the following command.
fastboot oem asus-csc_lk
Now it's relocked and works as before.
Hope this helps you.
Craig
Click to expand...
Click to collapse
Hi Craig,
I haven't seen this one before, so will definitely give it a go.
Thank you!
Thomas

mef206 said:
Hi,
I had the same problem as you, couldn't use Google pay.
All I did was open powershell and use the following command.
fastboot oem asus-csc_lk
Now it's relocked and works as before.
Hope this helps you.
Craig
Click to expand...
Click to collapse
Hi Craig,
This sounds really promising so had a go, but was not successful.
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot devices
M4AIB7626606MH7 fastboot
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot oem asus-csc_lk
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.005s
Any thoughts or suggestions would be much appreciated!
Thanks in advance,
Thomas

Hi,
Sorry I forgot to mention that I had followed the steps on the official Asus website to revert back to android 11 before I had run the command, as I wanted Google pay back.
fastboot oem asus-csc_lk
I hadn't tried to relock bootloader with Android 12 installed.
I did see in somewhere on line that the device requires factory reset after command is used. Also you could try some of these codes from following link.
hope you get it sorted.
craig
Relock the Bootloader?
I know asking this question at a very early point would be very foolish, I tried searching various places for the answer but didn't, can anyone from previous experience or with answer tell me how can the Bootloader be locked again? Thanks in...
forum.xda-developers.com

mef206 said:
Hi,
Sorry I forgot to mention that I had followed the steps on the official Asus website to revert back to android 11 before I had run the command, as I wanted Google pay back.
fastboot oem asus-csc_lk
I hadn't tried to relock bootloader with Android 12 installed.
I did see in somewhere on line that the device requires factory reset after command is used. Also you could try some of these codes from following link.
hope you get it sorted.
craig
Relock the Bootloader?
I know asking this question at a very early point would be very foolish, I tried searching various places for the answer but didn't, can anyone from previous experience or with answer tell me how can the Bootloader be locked again? Thanks in...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Craig
That is a good point you raise ..... and believe where I may have stuffed up was not flashing the device back down to Android 11 (currently it has the Stable Android 12). I am presuming this step would wipe the Official Asus Unlock Device App which was downloaded originally, which of course unlocked the bootloader?
Steps taken today:
1. Downloaded the Zipped Android 11 Image and unzipped on the PC.c
2. Put the Zenfone 8 into Fastboot Mode and opened up CMD powershell to confirm it was in Fastboot mode
PS C:\Users\roma_\OneDrive\Desktop\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release_for_google> fastboot devices
M4AIB7626606MH7 fastboot
PS C:\Users\roma_\OneDrive\Desktop\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release_for_google>
3. In the Unzipped Android 11 image found the windows update_image (I checked properties to confirm this was the Windows Batch File (.bat)
4. Right clicked, Run as Administrator.
5. I got this ....
fastboot cmd : fastboot
The script can't be used in this devices,hwid=,project=project FAILED (remote
Press any key to continue . . .
I am so missing something here, no doubt something really simple, but something really frustrating lol.
Any pointers would be appreciated.
Thank you!
Thomas

Hi,
I had done exactly as you have described.
Downloaded zip android 11
Unzipped and just double clicked on bat file whilst phone in fastboot.
Afterwards ran that command after rebooting phone back into fastboot.
Im sorry I can't be of anymore help I can't see why yours is not working the same.
Craig

mef206 said:
Hi,
I had done exactly as you have described.
Downloaded zip android 11
Unzipped and just double clicked on bat file whilst phone in fastboot.
Afterwards ran that command after rebooting phone back into fastboot.
Im sorry I can't be of anymore help I can't see why yours is not working the same.
Craig
Click to expand...
Click to collapse
Hi Craig,
Thank you and good to know I was following the directions.
Got me stumped, but I'll keep at it.
The only thing I am curious about is the unzipped file is in the desktop of my laptop (easy to find) but the desktop is set to back up to OneDrive .....I wondered if that could cause a problem (outside the limits of my ability)?
Thanks again for your input.
Thomas