Related
-This is probably going to be confusing and a bit all over the place, bear with me.-
So, I bought my N8 back in November and directly went in to the dev options and saw OEM Unlock was available.
Now I didn't bother with it and now recently I've been thinking about rooting it, the catch is I've seen countless threads claiming a notorious "RMM"-lock taking place and putting devices in to "Jail".
Here's the sketchy bit:
- I rebooted and checked in DL-Mode and saw no particular line referencing RMM. Then after some reading got buildprop editor and checked what the "ro.security.vaultkeeper.feature" status was; It's 1.
- Rebooted again, double checked and no RMM entry.
- Enabled OEM Unlock and rebooted about 3-6 times (no flashing done) and it booted up fine with the OEM Unlock setting still enabled and present.
- DL Mode still does NOT show any RMM message or line, just "OEM lock" and "FRP lock" are off.
Am I missing some information as to how the "Jail" is triggered or does flashing only trigger the "Jail"?
BTW, here's info on my device:
- N950F, unlocked, Germany
- On latest January Patch, N950FXXU3BRA2
- Non-branded, but marked as DBT
SaadatM said:
-This is probably going to be confusing and a bit all over the place, bear with me.-
So, I bought my N8 back in November and directly went in to the dev options and saw OEM Unlock was available.
Now I didn't bother with it and now recently I've been thinking about rooting it, the catch is I've seen countless threads claiming a notorious "RMM"-lock taking place and putting devices in to "Jail".
Here's the sketchy bit:
- I rebooted and checked in DL-Mode and saw no particular line referencing RMM. Then after some reading got buildprop editor and checked what the "ro.security.vaultkeeper.feature" status was; It's 1.
- Rebooted again, double checked and no RMM entry.
- Enabled OEM Unlock and rebooted about 3-6 times (no flashing done) and it booted up fine with the OEM Unlock setting still enabled and present.
- DL Mode still does NOT show any RMM message or line, just "OEM lock" and "FRP lock" are off.
Am I missing some information as to how the "Jail" is triggered or does flashing only trigger the "Jail"?
BTW, here's info on my device:
- N950F, unlocked, Germany
- On latest January Patch, N950FXXU3BRA2
- Non-branded, but marked as DBT
Click to expand...
Click to collapse
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
sefrcoko said:
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
Click to expand...
Click to collapse
Alright, I'll check that and see if i'm also in the boat.
Odd enough that it toggles itself off automaticallly, that is wondering me.
Weird.
sefrcoko said:
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
Click to expand...
Click to collapse
SaadatM said:
Alright, I'll check that and see if i'm also in the boat.
Odd enough that it toggles itself off automaticallly, that is wondering me.
Click to expand...
Click to collapse
Yep, just as I suspected; Your idea didn't apply @sefrcoko .
I installed TWRP, Magisk, the no-dmverity (in that order) and booted perfectly fine with the following result:
- Dev options were hidden since DATA was formatted
- After opening Dev options the OEM Unlock was still switched on.
That has me thinking if it is either sw or hw related, that some devices lock-up.
SaadatM said:
Yep, just as I suspected; Your idea didn't apply @sefrcoko .
I installed TWRP, Magisk, the no-dmverity (in that order) and booted perfectly fine with the following result:
- Dev options were hidden since DATA was formatted
- After opening Dev options the OEM Unlock was still switched on.
That has me thinking if it is either sw or hw related, that some devices lock-up.
Click to expand...
Click to collapse
You asked what jail was, and I explained it... You're just not in jail. Not every device is affected, and fixes to prevent the issue are being baked into custom roms and .zips now too. Lots of factors at play, hence the monster OEM Unlock thread . RMM seems to be the culprit.
sefrcoko said:
You asked what jail was, and I explained it... You're just not in jail. Not every device is affected, and fixes to prevent the issue are being baked into custom roms and .zips now too. Lots of factors at play, hence the monster OEM Unlock thread . RMM seems to be the culprit.
Click to expand...
Click to collapse
Figured not every device is effected.
Appreciate the input though.
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
I recently got the phone and i have the China version 12/256. Here are few things to take care:
1) Install Google Keyboard first before debloating system apps using adb.
2) Very Important: First update the phone to latest firmware (12.0.13) before you toggle the OEM Unlocking option in developer settings. If you dont update first and have the option toggled and try to install an OTA update the phone will just bootloop unless you clear the data and sign in with mi account again. This will reset the 168 hours time in the software. So always update the phone to latest update.
3) If you are using google pay, go to nfc settings and change the wallet from Mi Wallet to HCE Wallet.
4) The stock TPU cover is loose on the sides. I dont know if its just mine. But better buy another case from aliexpress.
5) DO NOT install global stock rom through fastboot or mi flash tool. It just wont work because of the different versions(regional) of phone. Only install xiaomi.eu ROM using the guide from a post on xda because the install script knows which version your phone is and installs the appropriate system files.
@ingbrzy can you confirm that? :
5) DO NOT install global stock rom through fastboot or mi flash tool. It just wont work because of the different versions(regional) of phone. Only install xiaomi.eu ROM using the guide from a post on xda because the install script knows which version your phone is and installs the appropriate system files.
Click to expand...
Click to collapse
xiaomi.eu is safe to install using fastboot method ?
veimus said:
@ingbrzy can you confirm that? :
xiaomi.eu is safe to install using fastboot method ?
Click to expand...
Click to collapse
It is safe to install. haven't installed it yet but read on forums that it is working.
so I guess
1) unbox your phone
2)update to latest software via settings.
3)factory reset device after that.
3)request bootloader unlock.
4) after 7 days, unlock your bootloader and tooggle that OEM unlock
5)follow instructions on xiaomiEU rom.
is that safe enough? Lmao
PS:
6) Find EDL support near you
avetny said:
so I guess
1) unbox your phone
2)update to latest software via settings.
3)factory reset device after that.
3)request bootloader unlock.
4) after 7 days, unlock your bootloader and tooggle that OEM unlock
5)follow instructions on xiaomiEU rom.
is that safe enough? Lmao
PS:
6) Find EDL support near you
Click to expand...
Click to collapse
1) Update to 12.0.13
2) Sign in to MI Account on device if haven't done yet.
3) Enable Developer settings, Developer Settings> Toggle OEM Unlocking
4) Turn off Wifi, Turn on Mobile Data, Settings> Additional Setting>Developer Settings> Mi Unlock Status> Click Add Account and Device.
5) Download Mi Unlock Tool, Login to same mi account > Turn off device, Hold Volume Down and Power Button ( you will see fastboot screen)> connect the device using USB, You will see the device, Click on Unlock button.
6) It will show wait for 168 hours to unlock.
7)Do not sign out/ change mi account on device or toggle the OEM Unlocking option. If you do you have to start from the beginning.
If you dont see your device in Mi Unlock tool install adb and fastboot drivers.
saisannihith said:
1) Update to 12.0.13
2) Sign in to MI Account on device if haven't done yet.
3) Enable Developer settings, Developer Settings> Toggle OEM Unlocking
4) Turn off Wifi, Turn on Mobile Data, Settings> Additional Setting>Developer Settings> Mi Unlock Status> Click Add Account and Device.
5) Download Mi Unlock Tool, Login to same mi account > Turn off device, Hold Volume Down and Power Button ( you will see fastboot screen)> connect the device using USB, You will see the device, Click on Unlock button.
6) It will show wait for 168 hours to unlock.
7)Do not sign out/ change mi account on device or toggle the OEM Unlocking option. If you do you have to start from the beginning.
If you dont see your device in Mi Unlock tool install adb and fastboot drivers.
Click to expand...
Click to collapse
7) Do not sign out/ change mi account on device or toggle the OEM Unlocking option. (You mean do not switch off anymore?)
Thank you
avetny said:
7) Do not sign out/ change mi account on device or toggle the OEM Unlocking option. (You mean do not switch off anymore?)
Thank you
Click to expand...
Click to collapse
yes. dont toggle it back to off.
saisannihith said:
yes. dont toggle it back to off.
Click to expand...
Click to collapse
Got it !!!
fantastic guide! Thank you !!!
I have flashed mine , it looks fine
Need some more time to evaluate performance
First boot takes awhile , don't panic or remove the cable!
speedtripler said:
I have flashed mine , it looks fine
Need some more time to evaluate performance
First boot takes awhile , don't panic or remove the cable!
Click to expand...
Click to collapse
Which method you follow?? The method from OP?
Post your installation from the beginning please.
With specifications of your phone.
speedtripler said:
First boot takes awhile.
Click to expand...
Click to collapse
My friend doesn’t matter how long it takes to boot up.....as long as you not in fastboot after restart
It seems to be working fine but I need to go outside and test the 5G and 4G signals are still as good as before
It's definitely feels much lighter and smoother
WhatsApp notifications are working properly
There's much less apps in the drawer, Chinese was very bloated , now there's not a Chinese app or character to be found!
Also banking apps are working fine!
speedtripler said:
It seems to be working fine but I need to go outside and test the 5G and 4G signals are still as good as before
It's definitely feels much lighter and smoother
WhatsApp notifications are working properly
There's much less apps in the drawer, Chinese was very bloated , now there's not a Chinese app or character to be found!
Also banking apps are working fine!
Click to expand...
Click to collapse
Please post the instruction how u did it. With full info
Just downloaded and install it from a Windows laptop
You have to wait 168 hours to unlock it and then open the phone in Chinese language to get to the developer options again before you flash , you need to enable usb debugging again!!!
You will need wi-fi to get back in because there's a security check after unlock, it maybe in Chinese but you will figure it out
I had never used a Xiaomi phone before this one , there are literally no downsides anymore....
I'll update if I can find something that doesn't work
speedtripler said:
Just downloaded and install it from a Windows laptop
You have to wait 168 hours to unlock it and then open the phone in Chinese language to get to the developer options again before you flash , you need to enable usb debugging again!!!
You will need wi-fi to get back in because there's a security check after unlock, it maybe in Chinese but you will figure it out
I had never used a Xiaomi phone before this one , there are literally no downsides anymore....
I'll update if I can find something that doesn't work
Click to expand...
Click to collapse
Can you explain the technical reason and the source of the information when you claim that you must update to 12.0.13 before toggling OEM unlock.
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Can you explain why 12.0.13 specifically is required before toggling OEM unlock?
jmikepr said:
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Click to expand...
Click to collapse
EDL guy:
Do it
deleted
jmikepr said:
Can you explain the technical reason and the source of the information when you claim that you must update to 12.0.13 before toggling OEM unlock.
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Can you explain why 12.0.13 specifically is required before toggling OEM unlock?
Click to expand...
Click to collapse
Because my phone went into bootloop. I updated to 12.0.10 and then toggled the OEM Unlocking. While i was waiting for 168 hours, i got 12.0.13 OTA update and i tried installing it. Phone restarted 3-4 times and took me to recovery. I then wiped data and it started again with a factory reset. So iam just warning people to get the latest update before doing this. Also, i do own a POCO F2 Pro and i am quite experienced with flashing ROMS. Developers always ask you to update to latest firmware before flashing as the new ROMs are based on latest firmware.
Xiaomi.eu is not a custom AOSP ROM but just a word of caution.
Sounds like after OTA 12.0.13 phone should be a factory reset it
jmikepr said:
Can you explain the technical reason and the source of the information when you claim that you must update to 12.0.13 before toggling OEM unlock.
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Can you explain why 12.0.13 specifically is required before toggling OEM unlock?
Click to expand...
Click to collapse
The toggle is nonsense
I toggled mine on and off a few times yesterday waiting for update 12.0.13 when I was on 12.0.10
It still unlocked like a charm today
Dear Friend,
I am having issue with S21 Ultra which i purchase just 2 months ago.
I decide to make my device root able , then i have notice that there is no OEM Lock option (Missing) in developer mode.
After searching XDA forum and Google all the setups mention there i have tried to visible OEM Unlocker option but OEM lock option never visible. Even flash stock rom again and again and wait for 168H but still its not visible.
When i go in download mode and try to flash TWRP or any custom rom it show below mention msg.
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"
Can any one guide me what is the issue, i had purchase this product with Full payment then why it is behaving so strange.
google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
EDIT: sorry if you cant see these option list, there could be something different in your case.
Very srtange situation. I have exact same model.
vlubosh said:
google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
View attachment 5580147
EDIT: sorry if you cant see these option list, there could be something different in your case.
Click to expand...
Click to collapse
Thanks brother for your prompt response , i tried this but issue remain same
Samaly01 said:
Thanks brother for your prompt response , i tried this but issue remain same
Click to expand...
Click to collapse
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.
vlubosh said:
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.
Click to expand...
Click to collapse
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....
Samaly01 said:
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....
Click to expand...
Click to collapse
Allow usb debugging in dev.settings
vlubosh said:
Allow usb debugging in dev.settings
Click to expand...
Click to collapse
USB debuggin already allowed ....ADB command work but not fastboot
Samaly01 said:
USB debuggin already allowed ....ADB command work but not fastboot
Click to expand...
Click to collapse
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?
Macusercom said:
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?
Click to expand...
Click to collapse
SIM Card is installed both WIFI and Data is working but issue remain same.
Samaly01 said:
SIM Card is installed both WIFI and Data is working but issue remain same.
Click to expand...
Click to collapse
Try disabling the automatic date and time and set the date to a day at least one week from now
I have observe a very strange thing, when ever I reboot the device and visit develope option Oem Locker appear then again revisit to developer option it disappear again. Only rebooting device option bring oem option just for few minutes.
so then, when you see unlock option reboot right to DL mode and look if you see device unlock
vlubosh said:
so then, when you see unlock option reboot right to DL mode and look if you see device unlock
Click to expand...
Click to collapse
Still same issue
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"
Someone suggested to use Samsung combination file, after searching on google there are only 3 Combination files available U1, U2, U3.
Latest file available is COMBINATION_FAC_FAR0_G998BXXU3AUD3
( I think this not usable on Android 12 version (U4)
Please suggest what option i have left to resolve above mention issue.
Could you try to flash latest Stock rom(Via odin) and try again?
Latest Firmware (SM-G998B_BTU_G998BXXU4CVC4) Flash via Odin...Result same
Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com
vlubosh said:
Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks Brother, but issue is same mine.... no solution
checke my stats in DL mode:
KG state checking
FRP lock off
OEM lock OFF(u)
Warranty void 1
HDM status none
I think you problem is in KG state.
Maybe try to change date as in this tutorial:
First thanks to the creator of the script, original post here! I just systematized the steps:
What you need to have - PC(windows or linux), USB cable, and battery above 60%.
1. Download the starberryperl.
2. Download the deeptesting-junk.pl script.
3. Start the "perl command prompt" (it should be the first result when you type "perl" in window's search box) or just standard CMD.
4. Inside the command prompt change to the directory where you had downloaded the script, example:
Code:
cd C:\Users\Admin\Downloads\RMX3311_Unlock
5. Then change to UTF-8 with:
Code:
chcp 65001
6. Run the commands and follow the instructions from the github page. Take care to replace the dummy SERIALNM/HHH... and IMEI1NUMBERHERE/DDD... with your actual serial number and IMEI1!
Quote of the steps:
- Go to Settings/About Device/Status and copy Serial number and IMEI 1
- Then run in the command prompt:
Code:
perl deeptesting-junk.pl pcb 0xSERIALNM imei IMEI1NUMBERHERE cmd applyLkUnlock
- If the answer is
Code:
{"resultCode":0,"msg":"SUCCESS"}
, continue with
Code:
perl deeptesting-junk.pl pcb 0xSERIALNM imei IMEI1NUMBERHERE cmd checkApproveResult
- If the answer is somethink like
Code:
{"resultCode":0,"msg":"SUCCESS","data":{"unlockCode":"0345af...lots of hexdigits"}}
then go to next step.
7. Now follow the official guide how to unlock.
I did it on RMX3311_11.C.10_EU_202303171905 and work fine, the orange warning at boot is there(about unlocked BL).
The attachment contain the script and the apk from links above.
Backing everything up and going to try it right now, so pissed at Realme for locking us out of the Device.
I don't even care if it bricks anymore, gonna report if it works.
//It's 04:14 am, and it worked. I've followed the Instructions, but had the problem, that the device wasn't getting recognized in fastboot mode.
Problem: Phone does not get recognized in fastboot mode on Windows System
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
Solution:
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, Settings -> windows update -> advanced options -> reset options -> advanced restart.
Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
Thanks for the Guide @b0nb0n3v
/edit: linking here, i've uploaded the boot.img and Oneplus drivers that i used for fastboot mode.
"This phone model does not support deep testing." Is it possible to bypass that screen in the Realme's deep testing app?
Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-) I was able to do just that (and unlock the bootloader on my phone) some two months ago (in...
forum.xda-developers.com
Tried and worked perfectly here! Huge thanks to the creator of the script and the guide!
Oh wow, can we get some development for this device now xd
This is great news! Thank you for posting this!
Worked for me too ! What now ? There arent many ROM available. I need to flash a rom with Call recording. What should I do ? Also is there a way to root ?
Fixed my call recorder issue with BCR module for magisk. Working perfect.
Last thing is battery life. Hope it will be fixed with custom roms.
This is really the worst phone i ever had, with bad battery life an Locked bootloader.
Hi,
I am having trouble with google pay not working because of root i guess. I already cleared cash and had it working twice, but after a while it somehow notices the root and stops working. What am i doing wrong here.
I had similar issues, I've tested if the device passes safetynet and it failed. I've solved it by loading a magisk module, universal safetynet fix 2.4 from here: https://github.com/kdrag0n/safetynet-fix/releases
Now my banking apps and NFC payment work fine. Make sure to put all banking apps in magisk denylist.
wizard8400 said:
I had similar issues, I've tested if the device passes safetynet and it failed. I've solved it by loading a magisk module, universal safetynet fix 2.4 from here: https://github.com/kdrag0n/safetynet-fix/releases
Now my banking apps and NFC payment work fine. Make sure to put all banking apps in magisk denylist.
Click to expand...
Click to collapse
Did the same and it worked a while. I made it work twice, but both times it stopped working after using it a few times.
karayemis said:
Did the same and it worked a while. I made it work twice, but both times it stopped working after using it a few times.
Click to expand...
Click to collapse
I noticed that Play-services is being removed uit denylist by magisk by its self. That mught be the issue
Mine is also unchecked, no issues with banking apps, NFC payments or safetynet. Make sure you select every option under every app so that the blue bar is full and also rename/hide magisk app. Does it pass safetynet?
Yes it passing the test,but somehow play services is being removed from the denylist by its self. I have to select it each time. Also I see that you selected a lot is there any reason for that. I only selected Google Play, play services, Google Pay and wallet
Besed in latest news from realme they stop temporary unlocking for all, to upgrade the server and may be will fix this "exploit"/method. So who unlock it till now is lucky.
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Lightning- said:
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Click to expand...
Click to collapse
They said they'll try to bring back the applications by next week, wait till then
Lightning- said:
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Click to expand...
Click to collapse
Not working for me too, all working but when you click on the "Start deep testing" it reboot and appear the fastboot for a second a reboot instantly on the os.
Waiting next week maybe someone find something
BR4UTAL said:
They said they'll try to bring back the applications by next week, wait till then
Click to expand...
Click to collapse
Any update?
Luigi2201 said:
Any update?
Click to expand...
Click to collapse
Based on this chat, may be this is the end of global BL unlock.