Related
Hi all,
As we know, Alcatel Idol 4s Android and Alcatel Idol 4s with Windows 10 (called Idol 4 Pro in Europe) are completely different phones but both named Idol 4s in US
I purchased online an Alcatel Idol 4s with Windows 10, 6071W. Snapdragon 820, 64Gb, 3.5Gb, Amoled screen, USB-C connector, Single SIM, SD slot but it is locked to T-Mobile.
I confirmed it has a clean ESN but I cannot find an online provider to unlock it.
Most providers don't list this phone model or the Idol 4s they reference to is the Android version only.
I paid for cellunlocker (which I found to be reliable in the past) but replied that they cannot find the IMEI in their database and to try again after several weeks...
Does anyone know a safe place to have it unlocked?
Any advice would be much appreciated.
tbrcan said:
Hi all,
As we know, Alcatel Idol 4s Android and Alcatel Idol 4s with Windows 10 (called Idol 4 Pro in Europe) are completely different phones but both named Idol 4s in US
I purchased online an Alcatel Idol 4s with Windows 10, 6071W. Snapdragon 820, 64Gb, 3.5Gb, Amoled screen, USB-C connector, Single SIM, SD slot but it is locked to T-Mobile.
I confirmed it has a clean ESN but I cannot find an online provider to unlock it.
Most providers don't list this phone model or the Idol 4s they reference to is the Android version only.
I paid for cellunlocker (which I found to be reliable in the past) but replied that they cannot find the IMEI in their database and to try again after several weeks...
Does anyone know a safe place to have it unlocked?
Any advice would be much appreciated.
Click to expand...
Click to collapse
go to this link to unlock
HOW TO UNLOCK SIM, UNBRICK, FIX RAMDOM REBOOT LOOP ON ALCATEL IDOL WINDOWS
1. requirements
1. QPST & QSDM
2. CUSTOM ROM FROM THIS LINK: forums.windowscentral.com/windows-phones/476813-custom-rom-alcatel-idol-4s
3. XQN FILE LINK:
4. WINDOWS ASSESMENT DEVELOPMENT KIT
5. emmcdl.exe
STEPS:
2. reboot to download mode by holding volume down and power on key
extract the rom to folder and copy emmcdl to that folder
open cmd and navigate to rom folder
the execute this commad (emmcdl -p COM15 -f <Idol4S_PRO_WIN_NPRG7627.bin> -x <path to xml>\rawprogram0.xml) without bracket
replace:
COM15 = with your qualcomm port value
Idol4S_PRO_WIN_NPRG7627.bin = with your rom filehorse bin file
wait for some few menutes......
after flash completed, boot the phone and reboot to BDS Menu (PWR&VOL+).
scroll down, select fastboot and open device manager update adb device driver
extract fastboot folder
open cmd and navigate to fatstboot folder
execute the following command (one after the other)
- fastboot erase MODEM_FSC
- fastboot erase MODEM_FS1
- fastboot erase MODEM_FS2
- fastboot erase MODEM_FSG
1. reboot to factory mode: powerON&VolumeUP key until electric spark logo with gear appears.
open cmd and navigate to C:\program file (x86)\windows kit\10\tool\bin\i386
then execute the command (ffutool -setbootmode 1 factory)
in device manager, qualcomm hs-usb diagnostic 9001 port will appear (if not, update the driver)
open QPST Configuration, make sure your COM port is detected and open QPST Software Download
in restore tab select downloaded xqn file and restore.
repeat step 2 and allow device to boot..
thats all you have successfully unlock sim lock
NOTE: the instructions are too rough, sorry for that just manage it or ask me
https://forum.xda-developers.com/wi...windows-10-mobile-t3736731/page8#post83405343
I am looking for a solution to the problem too...same phone, Alcatel Idol 4s with Windows. I have contacted several unlock sites to no avail. If you have any success, please let me know!
Heya I had the same experience with cellunlocker.net today. They said it could take weeks or months. =/
For what it's worth, I have the same problem with a Tmobile Alcatel Idol 4S windows phone. I even got an account with Tmobile for 40 days etc to get the unlock straight from them, and after waiting 40 days, ultimately they also could not give me the unlock. It's pretty frustrating because it's a great phone, but I have Zero bars of service from T mobile at home so staying with them simply isn't an option. If anyone has any ideas on what can be done, please reply.
Alcatel ONE TOUCH IDOL 4S data connection locked
Hi, I have similar Problem, I purchased the Alcatel Idol S4 Windows Phone unlocked in the US and try to use a sim from the Philippine Globe-Tele Company. All works but the data connection is blocked. Is there any different option to unlock the data connection? Because the phone calls work... If anyone has an Idea how to unlock the data connection I would be happy...
The same here.
Idol 4S T-Mobile from USA to Finland.
T-Mobile has terminated the phone and apparently also that part of their database.
I'll try to hack it and then tell if it works.
(I may need to buy several if I keep on bricking the phones))
Got Solution for Data Connection
Cyber.Angel said:
The same here.
Idol 4S T-Mobile from USA to Finland.
T-Mobile has terminated the phone and apparently also that part of their database.
I'll try to hack it and then tell if it works.
(I may need to buy several if I keep on bricking the phones))
Click to expand...
Click to collapse
After heavily searching for a solution I managed to make it... I added several APN and MMS settings and oh wonder one was the solution and data connection is running now...
here is the page I got it from, should work..
...s://apn.how/
...s://apn.how/philippines/globe/alcatel/4221-idol-4#mccmnc
Hope this helps! Cheers!
Cyber.Angel said:
The same here.
Idol 4S T-Mobile from USA to Finland.
T-Mobile has terminated the phone and apparently also that part of their database.
I'll try to hack it and then tell if it works.
(I may need to buy several if I keep on bricking the phones))
Click to expand...
Click to collapse
Hi, did you manage to unlock this device?
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
XT1965-6 with "global rom", how was it done, and how can I safely install ROM's on it
I just received a new G7 plus, china variant, with “global rom” which was bought from AliExpress at a supper low price, And I wish to figure out what was installed on it so I can install new roms safely by myself.
The phone is XT1965-6, it’s a 4GB/128GB with dual sim at only $160.
It’s a totally original phone with all the accessories, original box, papers etc.
I’ve asked the seller, but the installation was done by some “professional”.
The phone came with unlocked bootloader. When trying to enter the recovery I get the "No command" text and bad android icon, but I can use “fastboot boot twrp-*.img” and get into TWRP.
Where I did a full backup of all the partitions from A slot.
So before I start installing new TWRP and roms on it, I wish to fully know how this phone was installed so I could roll back in case I get stuck in soft brick (and know what not to do to get into hard brick)
This is the data I found in the phone:
From fastboot:
bl: mbm-3.0-lake_retcn-c12e284-190306
baseband: M636_08.23.02.46r lake_chinadsds_cust
product/variant: lake xt1965-6 128gb put
serial zy22xxxxx
From recovery:
starts with "No command" and bad android icon then managed to get to this:
lake_retail/lake:9/ppw29.98-107/34744
ro.bootloader=MBM-3.0-lake_retcn-c12e284-190306
from the system:
hardware version=pvt
model number= xt1965-6
android 9 patch may 1 2019
baseband version= m636_08.23.02.46R lake_chinadsds_cust
kernel 4.4.153-perf-g4ef1214-02524-ge6df629 #1 fri may 24 11:32:20 cdt 2019
build number ppw29.98-107
It looks like the everything is written as chines except for the system.
I found the flowing Firmware Flash File for the XT1965-6:
XT1965-6_LAKE_RETCN_9.0_PCW29.27-51 (with files from July 2019)
XT1965-6_LAKE_RETCN_9.0_PCW29.27-73 (with files from the March 2019)
1) On my phone I see PPW29.98-107 and these are PCW and they have different sub numbers. So, does any of these images where used in my phone?
2) I believe that fastbooting any of these two files should work, but then I will probably end up with some chines system. What do you think?
3) I saw that build number ppw29.98-107 is written here (https://www.getdroidtips.com/moto-g7-plus-stock-firmware/) as XT1965-2 firmware. Could it be that they just installed the system.img files from a XT1965-2 firmware over the Chinese firmware?
4) What do you think will happen if I flash a full firmware of XT1965-2 over this phone?
5) If I do 4, will the TWRP backup be able to restore me exactly to the current state of the phone?
6) Which operations should I avoid so I will not run into hard brick?
7) What do you think may happen if I just install the lineage-16.0-UNOFFICIAL over this phone?
8) Any other ideas on what I better do next will be very welcome.
Thanks,
Zohar
I HAVE IT!!!
I've managed to install a full firmware of XT1965-2 on my XT1965-6, and every thing is working great!!
The short story:
Download
a) XT1965-6_LAKE_RETCN_9.0_PCW29.27-73_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and
b) XT1965-2_LAKE_RETBR_9.0_PPWS29.98-111-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Extracted all the files from (b) to a new folder.
Extract from (a) only bootloader.img & gpt.bin to the same folder.
Make the normal fastboot process to write this mix firmware on the phone.
Reboot and you have a normal G7 plus phone with 128GB storage that costs only $160!!
You can permanently install TWRP in the normal way.
The long story:
I figured out some things:
1) I can hard brick the device if I mess with the bootloader (and even then I can use blankflash to get out of this).
2) TWRP can backup all the partition except for the modem.
3) Someone already managed to install a normal rom on this Chinese phone, so I'm sure I can do it.
4) The name of my modem was "M636_08.23.02.46r lake_chinadsds_cust", and I was affraid that the "cust" stands for custom, but then I found references in the internet for other modems with this "cust", so this helped me to believe that number 2 is not a problem.
5) From the *.info.txt files I found that firmware (a) and (b) have the same modem version, and this version is a bit better than the one shipped with my phone.
so I first fastbooted the full Chinese firmware (a) on the phone. after the long (and nervous) boot I had a full working Chinese phone (it comes with a "ZUI10" text and tons of Bloatwares)
then I used fastboot to load from firmware (b) only: system, system_b, vendor, oem. this gave me the normal system, but the touch screen did not worked
I figured out that you cannot mix vendor (b) with firmware (a)
Next step was a full fastboot process with firmware (a) and system, system_b, oem from (b). this gave a working normal system (with touch screen).
So the next step was to try a full XT1965-2 image, I decided to take the safe way and keep the bootloader.img & gpt.bin from the Chinese firmware (a)
My toughs where:
Use bootloader.img to be away as possible from a hard brick.
Use gpt.bin because my phone as a 128GB ram instead of 64GB in the XT1965-2, and I have no idea how/what this file will do to the partitions.
I did a full fastboot process and the phone is back alive! tested every thing I could think off and everything is working.
The strange thing is that "fastboot getvar all" still have "carrier_sku: XT1965-6" and "version-baseband: M636_09.25.02.49R LAKE_CHINADSDS_CUST" I think these are constants in the bootloader.
What's next:
I will probably try to install Lineage OS 16.0 on the phone.
If any one has more real information about the gpt.bin and bootloader.img I might re-think and make a totally full fastboot of XT1965-2.
Hope this will help others to take this route.
Zohar
Hi Zohar,
Thank you very much for sharing this method with us!
Do you already have managed to do the update to android 10 this way?
As I'm using the XT1965-6 too, this would be very interesting to me.
Best regards Feb
Hi Feb,
Great to know that some one else is using this!
I did the move to 10 last month. this made me do a big leap of faith, but it was worth it!
I could not find an XT1965-6 V10 rom, only for -2 & -3. so after thinking allot about it I just flashed a -3 rom. I did that because I understood that there is a way to unbrick the phone using some low level booting system of Qualcomm (I don't remember the name of the process).
So I installed a full image of XT1965-3, with out using any files from the chines rom. and it booted fine.
Tested it and found that the microphone did not work while on a phone call and the speaker is on.
Then I installed a full image of XT1965-2 (I used XT1965-3_LAKE_RETEU_10_QPWS30.61-25-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip which was the most up to date at the time).
Again it booted fine. this time there was no problems with the microphone.
I then installed the official LineageOS 17.1 and I'm using it since as a daily driver. (It also gets OTA updates every week or two)
The only problem with LineageOS is that the phone speaker is a bit low as they only use the lower speaker and not both of them.
If you need my full install process I can send you the file I made during the install.
Have fun with your leap,
Zohar
zohar_ml said:
Hi Feb,
Great to know that some one else is using this!
I did the move to 10 last month. this made me do a big leap of faith, but it was worth it!
I could not find an XT1965-6 V10 rom, only for -2 & -3. so after thinking allot about it I just flashed a -3 rom. I did that because I understood that there is a way to unbrick the phone using some low level booting system of Qualcomm (I don't remember the name of the process).
So I installed a full image of XT1965-3, with out using any files from the chines rom. and it booted fine.
Tested it and found that the microphone did not work while on a phone call and the speaker is on.
Then I installed a full image of XT1965-2 (I used XT1965-3_LAKE_RETEU_10_QPWS30.61-25-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip which was the most up to date at the time).
Again it booted fine. this time there was no problems with the microphone.
I then installed the official LineageOS 17.1 and I'm using it since as a daily driver. (It also gets OTA updates every week or two)
The only problem with LineageOS is that the phone speaker is a bit low as they only use the lower speaker and not both of them.
If you need my full install process I can send you the file I made during the install.
Have fun with your leap,
Zohar
Click to expand...
Click to collapse
Hi Zohar,
Can you share the file link via Google Drive.
Thank you.
Just google for "XT1965-3_LAKE_RETEU_10_QPWS30.61-25-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
And also LineageOS 17.1 is vary easy to find.
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?
Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot reboot-bootloader
fastboot flashing unlock
fastboot flashing unlock_critical
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Root Key Hash of ABL image: 622D3D5FE38C4198DDFABB264034EFDE58B986B510393A0CF163E803A3FD985E
Proof of concept is attached below, thanks to @singhnsk for testing.
Bro, Nokia x10 please?
HDK.
Where can I get?
Full name please of this app.
mishak750 said:
HDK.
Where can I get?
Full name please of this app.
Click to expand...
Click to collapse
nope, you can't use it, even if you get the full name
hikari_calyx said:
Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot flash frp frp_oemunlock.img
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Proof of concept is attached below, thanks to @singhnsk for testing.
Click to expand...
Click to collapse
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!
AltFantasy said:
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!
Click to expand...
Click to collapse
THAT CAME TRUE, **** YEAH!!!
Posted new topic in X10/ X20 phone section, before reading everything up here...
Seems "up the sh*t creek without a paddle" situation.
Damn Nokia, but if anyone would get it working- I'll subscribe to this topic too.
Cheers!
Visionu said:
Bro, Nokia x10 please?
Click to expand...
Click to collapse
Prototype ABL binaries from Nokia X10 and X100, for bootloader unlock purpose.
If you've followed my prototype ABL image release topics so far, then you should know where it comes from. This topic will be edited later if X20 one is available. WARNING: This is not a guide! Prototype ABL binaries are provided as-is...
forum.xda-developers.com
Here you go
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
Politics+proffits= end user loss
as it comes to coders, it's only so far we get allowed to delve in to, there was time, when I have physically remodded ZTE phone, from non funcioning device in to best phone at the time ALL- during one day on PC using no more that 3 tools and 2 ROM's... now you are constrained to even to get an access to bootloader or the way to extract it without phone started. Silly win for the google (nokia) developers in constraining modifications, with time, (loss of sales) that might change, hence "politics"
Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode
phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)
alegatorul said:
Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode
Click to expand...
Click to collapse
that option is useless. Ignore that.
AltFantasy said:
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)
Click to expand...
Click to collapse
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/
phaleg said:
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/
Click to expand...
Click to collapse
nah, blame HMD for that.
Nokia is trying to distance itself from its past with their legendary phones (like the N95, E95, N97, 3310, and soooo much more!) now, starting from when they redesigned their logo to a more.... minimalistic look, I guess? and their booths in tech events (e.g: CES) now market their IoT tech, routers, and whatnot...
As for HMD, though, they'll keep on using the old logo, because muh homage to le legendary phones and all that, blah blah. (even though their "new" N95 prototype (you can view it in MrMobile's video about the old Nokia N95) is just essentially very uniform (with just a kickstand built into the camera unit, and speakers that slide out from the left side of the phone....))
HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)
Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?
alegatorul said:
Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?
Click to expand...
Click to collapse
I don't know if my guide will also work for your device (though, I suspect it'll still work with the XR20, since all you have to do is flashing the ABL, then do the unlocking commands and all), but here's my guide on how to unlock the bootloader.
Do note, however, that my guide is for a different device (the X10), so it has a few differences here and there, from the XR20 (the unlock commands, and the ABL files). Hikari_Calyx has already given you the commands and files in his post, so just grab that from there.
As for TWRP, you'll have to port the recovery to your phone, which means learning programming and dealing with image layouts and whatnot...
phaleg said:
HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)
Click to expand...
Click to collapse
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux), then claim that they haven't done any modifications to the OS.
AltFantasy said:
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux)
Click to expand...
Click to collapse
Cheers mate.
I'll try with unblocking...
Anyway, the phone is 1 month old under warranty still