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

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

Related

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

for people trying the beta who want to revert without flashing (especially sprint)

Sprint Downgrade from Android 10 Beta to Android 9 PIE:
MAKE A BACKUP WITH BACKUP BUILT INTO SETTINGS AND MOVE IT TO COMPUTER FROM LG Backup folder
Install python first and make sure to check add to path variables during installation - if you didn't you will have trouble later on
If you get any errors you can look up how to install the cryptography module - it seems to have fixed issues for some users
This is only recommended on Sprint devices as they have no other option. If you are thinking about installing the beta now, I would recommend you don't because final is coming out soon.
I will be putting the commands in " and do not include the " in what commands you execute
1. LG USB Drivers 4.4.2 http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
2. Download LGLAF and extract to desktop https://anonfile.com/7aa2z8Ean2/lglaf-develop_zip
3. Put your phone in Download Mode
a.) Power off your phone
b.) Plug in the cable connected to your computer and start holding volume up at the same time
4a. (At this point there are 2 ways, I recommend trying the first one first)
Open lglaf-develop folder and open a Powershell / cmd line
Make sure the path at the top is the folder directly leading to the lglaf.py file
(Shift Key + right mouse) and type: "python lglaf.py" then hit ENTER
If it says python is not recognized
4b. Open a normal command prompt and type "where python"
Copy the path (except for the /python.exe at the end)
Go to lglaf.py > open with > find another app > paste in path and select the python.exe file and click open
5. Type "!SABS 0" or "!SABS 1" to switch between A/B slots. You will have to test to see which one your in, no harm can be done by switching to already active slot.
6.Type "!CTRL POFF"
7.Type "exit"
The device will power off after you unplug the USB cable.
Don't worry if it takes a very long time to boot up - just hold power button for like 10 seconds and wait
Important: everytime you want to update, switch to the PIE slot so that the other slot gets updated and you have an official version to revert to.
Wait we can actually flash the android 10 beta? on the US sprint version 0o, how? i thought android 10 beta was for korean version only.
siulmagic said:
Wait we can actually flash the android 10 beta? on the US sprint version 0o, how? i thought android 10 beta was for korean version only.
Click to expand...
Click to collapse
There's a guide on v50 forum: how to install leaked v50 sprint bets
Join the telegram group for the files. Just search up v50 or g8 in the search bar inside of the app. Join the one with a bit over 100 members
antintin said:
There's a guide on v50 forum: how to install leaked v50 sprint bets
Join the telegram group for the files. Just search up v50 or g8 in the search bar inside of the app. Join the one with a bit over 100 members
Click to expand...
Click to collapse
Can you please link the telegram group?
antintin said:
There's a guide on v50 forum: how to install leaked v50 sprint bets
Join the telegram group for the files. Just search up v50 or g8 in the search bar inside of the app. Join the one with a bit over 100 members
Click to expand...
Click to collapse
You cant search groups in telegram, at least it doesnt let me. Just says no messages found
Try searching again it is there, we cant link it because its against xda rules, for some reason.
This is a quick update for those that were running the "hacked" version of android 10 ota. I was able to follow the rollback guid mentioned in the original post and it does work. The only real pain was having to enter the failed pw 30 times to get the device to wipe itself and android 9 to boot.
cas8180 said:
This is a quick update for those that were running the "hacked" version of android 10 ota. I was able to follow the rollback guid mentioned in the original post and it does work. The only real pain was having to enter the failed pw 30 times to get the device to wipe itself and android 9 to boot.
Click to expand...
Click to collapse
You could have entered recovery mode and just factory reset from there. That's what I did.
jericho246 said:
You could have entered recovery mode and just factory reset from there. That's what I did.
Click to expand...
Click to collapse
I don't believe a factory reset will downgrade the OS back to 9 from 10. Just merely wipes the data.
cas8180 said:
I don't believe a factory reset will downgrade the OS back to 9 from 10. Just merely wipes the data.
Click to expand...
Click to collapse
I meant that after rolling-back to Pie, you could have entered recovery mode to wipe your data instead of entering the wrong secure start-up code 30 times.
My Sprint got updated to Android 10 from offical OTA 20d firmware, can I revert back to Pie 9.0 by this method ? Or both slots are 10 now ?
abced123 said:
My Sprint got updated to Android 10 from offical OTA 20d firmware, can I revert back to Pie 9.0 by this method ? Or both slots are 10 now ?
Click to expand...
Click to collapse
You can revert back to pie using this but if you receive another ota after the initial Android 10 update then both slots will be in 10. But I don't see why you would want to
antintin said:
You can revert back to pie using this but if you receive another ota after the initial Android 10 update then both slots will be in 10. But I don't see why you would want to
Click to expand...
Click to collapse
Seriously, this update kinda sucks. I liked Pie better. LG managed to brake more stuff than fixing old ones.
discard
Can i try to unbrick my lg g8 sprint caused ny crossflash?
Sent from my SM-G975W using Tapatalk
Hi guys, was trying to change slots (was following BrandonB1218's bootloader unlock guide) and tried the above method using python to change slots but phone won't start after I disconnected it from the USB cable following above steps. If switching slots was successful I should have gone to slot B which had v50 eng bootloader and a few Pie partitions as instructed in BrandonB1218's guide.
I have tried holding power button for up to 10 minutes, held power + volume down button for a few minutes, tried plugging in the phone while holding volume up and plugging in the phone while holding volume down button but the phone is dead. It was fully charged at the time it powered off when I disconnected it after the '!CTRL POFF' command. Powershell screenshot is attached. Thanks.
Android# said:
Hi guys, was trying to change slots (was following BrandonB1218's bootloader unlock guide) and tried the above method using python to change slots but phone won't start after I disconnected it from the USB cable following above steps. If switching slots was successful I should have gone to slot B which had v50 eng bootloader and a few Pie partitions as instructed in BrandonB1218's guide.
I have tried holding power button for up to 10 minutes, held power + volume down button for a few minutes, tried plugging in the phone while holding volume up and plugging in the phone while holding volume down button but the phone is dead. It was fully charged at the time it powered off when I disconnected it after the '!CTRL POFF' command. Powershell screenshot is attached. Thanks.
Click to expand...
Click to collapse
i have not idea but i hope you figured it out cause i want to crossflash but im worried it might mess my sprint 820um some how, so far i only have bootloader unlocked
blaze2051 said:
i have not idea but i hope you figured it out cause i want to crossflash but im worried it might mess my sprint 820um some how, so far i only have bootloader unlocked
Click to expand...
Click to collapse
Nope, coudn't figure it out but I think the phone stopped charging so it wouldn't enter EDL mode anymore. I ended up selling it on eBay for parts.
Android# said:
Nope, coudn't figure it out but I think the phone stopped charging so it wouldn't enter EDL mode anymore. I ended up selling it on eBay for parts.
Click to expand...
Click to collapse
I see sry to hear that, im still waiting for twrp to flash with adb fastboot and see if we get some lineage Os for the G8/G8x
LGLAF link is down , could you please reupload it?

P10 lite bootloader unlock (June 2020, Windows install)

Damn, it's been a while since I was here. Back then it was mostly about Windows PDAs.
Disclaimer:
Your warranty after this process is void and your phone will tell you it can not be trusted because it's unlocked.
This is what worked for me. I did it on Windows 10. I just went through the process and it was a bit of mixing and matching various guides.
I'm not your tech support, the only one responsible for following this is you.
If any part of this guide doesn't work for you: too bad. Maybe Google or other users can help you with your problem.
Needed:
An internet-enabled PC
Huawei P10 Lite phone
USB to Micro-USB cable
HiSuite https://consumer.huawei.com/en/support/hisuite/
DC-Unlocker (comes with abd & fastboot) https://www.dc-unlocker.com/
Optional: Huawei Driver Tools https://mega.nz/file/qrpBUIKA#zaI8Th0ovgyK48VzFUFAzMNWF2r_R12lNc-uJZsIx4w
Note: I recommend not to buy credits until you've come to the part in my guide which says buy credits.
Install HiSuite
Unzip and install HiSuite on your PC
Start it at the end of the installation (it should show a button with "Start")
Connect the phone to your computer with the USB cable and follow the instructions in HiSuite to install HiSuite on your phone
At the bottom of the (Windows) HiSuite there's an option to do a System Upgrade, mine had the option to install an older version (Android 7 with EMUI 5.1) Install this. (This will take some time)
Note: I've read that some people couldn't downgrade because of modern security fixes. It's possible I didn't run the latest updates, but as far as I'm aware everything was up to date.
The following part might be annoying because HiSuite tries to connect to the phone. I uninstalled it at this point, but I had the Driver Tools installed (and did the Install within said tools).
Phone
Once the phone restarted, go through the set-up as quickly as possible (skip WiFi-setup, decline all optional things and skip account creation)
Go to Settings > System > About Phone > Keep tapping the "Build Number" until you're told you're a developer
Find the developer options (Usually in Settings > System and enable USB/ADB debugging
Open the telephone app and type: *#*#2846579#*#* (it should open a menu automatically after the last *)
Click Background Settings > USB Port Settings and select Manufacture Mode
Once Manufacture Mode is selected, leave the phone untouched
DC-Unlocker, part 1
Unzip the contents of the DC-unlocker zip
Start dc-unlocker2client.exe
In the top left, under "Select manufacturer" change "Huawei modems" to "Huawei phones"
Click the button with the magnifying glass, if you did the previous step hovering should say "Detect phone" on hover
Example out put (this might differ for you, but triple-check a port is detected):
Code:
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM3
Model : Huawei HiSilicon Kirin Android phone
Serial NR. : [redacted]
Firmware : System 5.1.0.78(0VVV)
DC-Unlocker, part 2
Check again if a model and port is shown in both the output and above the big buttons.
In the top right, click About > Buy Credits
DC-Unlocker site
Select your payment processor
By default it creates a new account, unless you've used this service before, you probably want to keep it this way.
Fill in a username and an email address
You need 4 credits (€4 for me) at the time of writing this, but do check the link "How much do I need?"
Hit confirm and go through the payment process, wait until everything is processed (if you use a script blocker, you might want to temporarily disable it).
At the end you should get confirmation page with your username, a password and 4 credits. (Username and password will be mailed too.)
DC-Unlocker, part 3
Go back to DC-Unlocker
In the top right, click "Server" and enter the details you've gotten
Click "Check login" and see if the output window shows your username and the credits you have left (which should be 4 at the time of writing)
In the top right, click "Unlocking" and then click "Read bootloader code"
The output should show you the bootloader code once it's done. Copy this to a textfile and save it (and keep it in the memory).
You can close DC unlocker once you've saved the code.
Don't be lazy and try to copy/paste the commands following in the next section, since you want to keep the code in your memory, as seen in step 6. Besides, I'll show you some shortcuts anyway! Keep in mind that our example code is 1111222233334444 (yours most likely isn't, mine sure wasn't) and that [tab] will mean the tab-key on your keyboard.
PowerShell/Command Prompt
In the folder where you unzipped dc-unlocker2client.exe to, press [shift] on your keyboard and hold it while right-clicking in an empty area underneath the files, then click "Open PowerShell (or command prompt) here".
Whatever command-line you started will open, type ad[tab] and adb.exe should be appear (shows up as .\adb.exe in PowerShell)
Follow this by typing reboot bootloader. So it should show as
Code:
./adb.exe reboot bootloader
(no ./ in command prompt)
Hit [enter] and the phone should reboot to a screen with a white background
Once the bootloader screen shows (white background with the android mascot) type fast[tab] in PowerShell/Command prompt and follow it up by oem unlock[space]
If you still have the bootloader code in memory, right-click in PowerShell/Command prompt to paste it. Your entire line should be
Code:
./fastboot.exe oem unlock 1111222233334444
Hit [enter], the unlocking will start and factory reset your phone. My output was:
Code:
(bootloader) The device will reboot and do factory reset...
OKAY [ 10.330s]
If everything went right you'll see the Huawei/Android bootscreen and then a warning that the phone is "unlocked and can not be trusted" to use or something like that. It'll boot into the OS after that.
I'd like to remind you of the disclaimers at the top, but hopefully this will help some of you going through the process.
Edits
Forgot about USB debugging
Added the warning you get after a successful unlock
Changed the build number tapping sentence
Rewrote a sentence for clarity
Very nice guide, if ppl ask about unlocking we just link this from now on...
This is a very helpful guide, thank you so much! My question is, if I wanted to flash twrp when the bootloader is unlocked, is there a way to upgrade it to Oreo once again without locking the bootloader again? I can't seem to find a twrp tutorial where they use Nougat/Emui 5 to flash twrp, and all the tutorials to upgrade to Oreo/Emui 8 look like they're locking the bootloader once again and I don't really want to waste 4 euros to go back to the start.
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
Thank you for your quick reply! So after the bootloader unlock, did you flash twrp on Android 7? or did you upgrade your phone to Android 8 and flash twrp then? How did you manage to upgrade it to Android 8?
I really appreciate your help with the previous tutorial, I've done everything until the buy credits part (I'm waiting a bit for that part) and I'm planning on getting to the end of the tutorial at least before August. My idea is to upgrade to Android 8 + flash twrp and Magisk, hopefully I'll be able to do all of that!
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Oh, I understand now! One more question (sorry if I'm being annoying, it's my first time playing with a Huawei, I must say that Samsungs are far easier to root/unlock lol): If I follow your method, but after getting the bootloader unlock code and right before unlocking the bootloader, I use HiSuite to upgrade back to Android 8/Emui 8, would the procedure be fine? like, it's totally fine to unlock the bootloader either with android 7 or 8, the only time I need android 7 is to get my code because DC unlocker supports them better, right?
Again, thank you so much!!!
I'm not sure to be honest. But I reverted to 7/EMUI 5 because I read around here on the board that's better for trying to unlock.
Thank you,
Only fastboot.exe oem unlock xxxxx failed with the following error: FAILED (remote: Command not allowed)
finished. total time: 0.022s
This was resolved by going back to settings, developer options and check 'enable oem unlocking'. I didn't read that in your guide.
Syrion said:
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Click to expand...
Click to collapse
Hi, I have the same model. But I can't figure out how to update to EMUI8 again (or which custom recovery works). It doesn't find the update in HiSuite and it doesn't find it via System update. Do you happen to know how? Thank you.
What should I do next?
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
For me, I did get to relock by accident but I confirm that the unlock code is permanent (at least, I did use it 3 times with no problem!)
P10 lite Pinout
I would like to know if they have tried to unlock the bootloader with the Pinout method.
Correcaminos604 said:
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Click to expand...
Click to collapse
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
be-rty said:
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Click to expand...
Click to collapse
Correcaminos604 said:
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
Click to expand...
Click to collapse
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Sam Nakamura said:
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
DC-Unlocker can't find my phone
I followed your instructions, but when I click the magnifying glass on DC-unlocker it says
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM6
===================================================================
But then nothing else is listed .....
My model is WAS-LX1
Correcaminos604 said:
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Click to expand...
Click to collapse
Yeah, it's actually crazy cool that it was patched after all this years, I however read it was primary updated to support the coronavirus warning App framework! That's actually the reason for Huawei to push another last update!
Sounds like a crazy conspiracy theory but was written on their Homepage...
Sent from my Google Pixel 3 XL using XDA Labs
Downgrade option doesn't exist for me in Hisuite. My phone is WAS-LX2 8.0.0.370(C185). The last update I got was on 13 February 2019 with the 2019 Feb security patches. Is there a free way to unlock bootloader?

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

			
				
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容?
您可能需要卸载它们并重新安装,看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题,或者这根本无法解决问题,请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题,无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

			
				
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

Categories

Resources