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
Many people has reported that, serial number changed to CTA4A0000000 after flashing in QPST, fastboot rom.
Here is the solution for you.
Caution::
This method is only to re-fix own device's serial no.
I am not responsible for illegal use/bricked device.
Use it on your own risk.
Do step wise,
U need a windows PC
1. Download the zip, unzip it.
2.there is a file named persist_MaxM2.img, you need to edit it.
3. to edit the persist image file you need hex editor, if u have it pre-installed go to next step or install it given hw_680.exe
4. Open hex editor, open that persist_MaxM2.img file in hex editor.
5. Click on edit tab in hex editor-->goto-->hex address 00E02020, your cursor will be taken to that address. see image
6. In the erxisting file serial no ""123456789ABCDEF0"" is given which is an arbitrary common number, replace this with your own serial no provided in your product package/shipping details.
7. save the file in hex editor, close hex editor.
8. Now its time to flash it in phone.
9. you need to have fastboot driver installed in your pc, google it, your device need to be detected as fastboot devices in PC during flash.
10. put the phone in fastboot mode, connect it to PC.
11. Run the Fl;ash_To_Rectify_Serial.cmd file (simply double click on it. it will take 6 sec to complete then window will wait for 10 more sec before it vanish).
11. your device will get rebooted, Need not to be worried, data will NOT be erased.
12. If you were using custom ROM, then you need to unlock the boot-loader before you start to android.
13. Connect device in fastboot again, Simply run unlock.cmd in the same folder, data will NOT be erased again.
14 wait for device to restart in android.
Voila...you got your new serial no.
download file here
https://www.androidfilehost.com/?fid=1899786940962588576
THANK YOU BRO, VERY HELPFUL
Thanks bro. Its working fine.
Confirmed it works
I like to confirm that it works.
After bringing my phone back from the dead, serial was 111111111, not good.
Your method put my official serial back.
Thanks so much!
Now I only have to get rid of encryption, so I can use twrp for backups.
Greetings,
Mike
Serial number
Please, I need help with this case. My Zenfone ZE554KL phone has the serial number CTA4A0000000 in status. When I use the adb devices or fastboot devices commands, the number that appears is 111111111. This happened after I made a recovery using QFIL. I used the hex editor indicated but I didn't find the serial number in the persist.img file.
tiagopraz said:
Please, I need help with this case. My Zenfone ZE554KL phone has the serial number CTA4A0000000 in status. When I use the adb devices or fastboot devices commands, the number that appears is 111111111. This happened after I made a recovery using QFIL. I used the hex editor indicated but I didn't find the serial number in the persist.img file.
Click to expand...
Click to collapse
Your device model is different... So the address will be different. You have to find it out.
Hi i have an asus rog phone zs600kl i have the same problem i was flash with qfil the stock rom of this phone afther flash me serial has chanced to c4atas000000 and i also cant find that serial on hxd editor i need help i cant also not unlock bootloader do i need unlocked bootloader voor this files to restore me serial back with persist.img file or not unlocked bootloader how i can find the serial of c4atas000000 with hxd editor need help bro
murasio3 said:
Hi i have an asus rog phone zs600kl i have the same problem i was flash with qfil the stock rom of this phone afther flash me serial has chanced to c4atas000000 and i also cant find that serial on hxd editor i need help i cant also not unlock bootloader do i need unlocked bootloader voor this files to restore me serial back with persist.img file or not unlocked bootloader how i can find the serial of c4atas000000 with hxd editor need help bro
Click to expand...
Click to collapse
Unlock bootloader will b required to change persist.img
If you want more help.. PM me
I have exactly the same case, but in different model, mine is zenfone max pro m2 (X01BDA).
I need your help, since the SN changed it does have mobile connection issue and can't connect wifi in long range.
Thanks before.
banggaryo said:
I have exactly the same case, but in different model, mine is zenfone max pro m2 (X01BDA).
I need your help, since the SN changed it does have mobile connection issue and can't connect wifi in long range.
Thanks before.
Click to expand...
Click to collapse
Send me your present persist.img and tell your present serial no.
i cant unlock bootloader the asus unlock tool application doenst not works more voor me shows an error networks becouse me serial has be chanced to c4atas000000
murasio3 said:
i cant unlock bootloader the asus unlock tool application doenst not works more voor me shows an error networks becouse me serial has be chanced to c4atas000000
Click to expand...
Click to collapse
Unlock tool available for max m2 unofficial.
[email protected] said:
Send me your present persist.img and tell your present serial no.
Click to expand...
Click to collapse
My recent SN is C4ATAS000000.
About the presist file, i found no presist folder or presist.img in my root explorer. How can i find that file?
redmi 4x serial no. change to orignal
[email protected] said:
Send me your present persist.img and tell your present serial no.
Click to expand...
Click to collapse
sir how to edit persist.img for orignal serial number.
didnt recognize from persist.img in hex editor.
please help
can you please tell me how can i use this method in asus zenfone max pro m1
My Device's Bootloader Is Unlocked If I Flash Through Qpst Then It Will Going To Relock Or not ???
My asus z010d SD615 has same problem serial no. changed to CTA4A0000000. how can i recover it please help someone
##Help
Dear sir i am unable to flash modded presis_MAXM2.img in my asus zenfone Max M2 via fastboot.
Problem -
After reboot to fastboot mode adb commands are not Working for example i use "adb devices" in result no devices are found means by device not detected.
But in power on at homescreen adb interface are fully Working expamle "adb devices" in result shows me serial no (which is wrong)
But i am unable to flash img file
Pls Find
Hello XDA Developers
I have been running for two days through Internet (including XDA) and try to find any valuable solution how to root my phone Alcatel 1S 2019 (5024D) on Windows 10.
I did:
- unlock developer mode and activated "OEM unlocking" and "USB debugging"
- installed "Minimal ADB and Fastboot" and when i connect the phone and run "adb devices" i can see my device on the list
- found, that in "Device manager" after connecting the phone i get a lot of: "Spreadtrum Phone" devices under "Other Devices" - those not workin properly, sice there is yellow exclamation mark next to the icon
- tried to install the drivers for the case from above - no luck. Keep getting errors while installing the drivers.
- tried: Framaroot https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276 without luck.
I found:
- https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713, but there is no clear information how to get to the fastboot, and the PWR and VOL+ wont work as stated in the post
- https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, but here I need to unlock bootloader, but when I am trying to do that by using "Minimal ADB and Fastboot" tool, i receive error:
FAILED (remote: Not implemet.)
finished. total time: 0.000s
I suspect that i should start from the drivers. But now i cannot find any clear information how to do that.
Obviously I tried to install some drivers, but without luck. I found dozens of step by step solutions how to properly implement drivers, but always get the same error (above) and can see in device manager, that after connecting the phone still not all devices has been installed properly.
Is someone from here have an experience in rooting that exact phone and will help me?
Hi there, have the same issue, is no driver problem. Seems at present this particular phone CANT be rooted Spent days on it too. Hope someone can help. Regards A.
Sorfeus said:
Hi there, have the same issue, is no driver problem. Seems at present this particular phone CANT be rooted Spent days on it too. Hope someone can help. Regards A.
Click to expand...
Click to collapse
Hello @Sorfeus. I am still fighting with that phone, but I am 80% sure, that there is no need anything else than normal Android USB drivers and ADB/fastboot. What I have noticed is when I have used original Alcatel USB cable and install above drivers still all commands you are able to run. I believe, that there is other problem though. Even when you unlock Developer options in Android and then switch on ability to unlock the bootloader actually you are not able to do this from the fastboot sight. The message I receive is that the option not exist. So you cannot even unlock bootloader not mention about running root ROM.
But again. I am not an expert but I think, that you do not need any spreadtrum drivers.
If only I had the boot image for my device Alcatel 1S (2020) 5028D.. then maybe I could have had root with magisk right now. Since no flashable firmware for my device is out there anywhere to be found and backing up boot partition on device requires root or a custom recovery in the first place, I seem unable to root it for now.
I was able to unlock bootloader with simple "fastboot flashing unlock" command though.
If you wanna do that, do the following: (and I assume you know how to type in the commands)
With "OEM unlocking" and "USB debugging" settings activated, connect phone to pc and type in command "adb reboot bootloader".
Next you type "fastboot flashing unlock" and "fastboot flashing unlock_critical".
Press volume up button on phone to confirm.
Now you type in command "fastboot reboot" and thats all.
My device is with Mediatek SoC and I had Mediatek drivers installed by Windows Update but I dunno if it is a driver issue you're having since you at least are able to run "adb devices" and you do see your device being listed there.
If you are able to unlock bootloader however you could proceed to try doing how this article describes on how to do (getdroidtips.com).
I have to also warn about that stock rom getdroidtips links to is for model 5024J not 5024D, flash a boot.img for wrong device model and you'll most certainly brick your device.
I managed to find stock roms 5024D while searching around the web but none that are free download or they require a password to unpack... could be scams, I dont know. Feels sketchy AF...
Anyways here is some of them I found and I guess these are good ones but needs a premium account:
Alcatel 1S 5024D EEA [needrom.com]
Alcatel 1S 5024D TMST [needrom.com]
Alcatel 1S 5024D ALAP [needrom.com]
Alcatel 1S 5024D ALRU [needrom.com]
[Update] found out this rom and is free download so I'll add it in here too:
Alcatel 1S 5024D ALRU
This might also be of interest if you want to know about how to extract and get the boot.img:
https://androidmtk.com/extract-spreadtrum-pac-file
Hello @RavZ75
Thank you for the clear information regarding unlocking. I didn't knew this command until you stated it in the above post.
Unfortunately I cannot check it, since I sold the phone.
Anyway, I believe that it is a good Idea to keep sharing rooting information in this thread since the question has been already asked.
Maybe someone else will use your knowledge to root it's phone.
Here's how I rooted mine: https://forum.hovatek.com/thread-32678.html
It's a long and complicated process, but it works.
FrescoLibra said:
Hi guys,
This is how I unlocked my bootloader and thats all I can do with this phone without Factory Firmware. I can not Root my device in any way. If anyone has a Scatter File for the Alcatel 1s 5024D 2019, please post so we can help each other out with this nasty phone's security
Bootloader Unlock: You need Linux, (eg) Parrot OS or Ubuntu!
Spreadtrum SC9863A - postmarketOS
wiki.postmarketos.org
Click to expand...
Click to collapse
That's only part of the process, but then you need to sign a modified boot/recovery image, edit the vbmeta image and flash both. It's all in the guide I linked above.
Hi all! I'm almost blown it. I don't know English I write through an interpreter. ROOT obtained in Russia.
Alcatel OneTouch 5024D 1S - Обсуждение - 4PDA
Alcatel OneTouch 5024D 1S - Обсуждение, Смартфон, 5.5"
4pda.to
This is a link to the bootloader unlock and firmware instructions with root 01003.
Alcatel OneTouch 5024D 1S - Обсуждение - 4PDA
Alcatel OneTouch 5024D 1S - Обсуждение, Смартфон, 5.5"
4pda.to
This is the forum itself in the header of which there is a lot of useful things. TWRP and Magisk update.
With an automatic translator, everything will be clear.
Good luck with root rights.
Hello Developers!
I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have entered
IMPORTANT: MAKE SURE THE PHONE IS CONNECTED TO ADB OR THIS TOOL WILL NOT WORK AS IT WILL RESTART INTO FASTBOOT AND TRY ALL THE CODES IT GENERATED!!!!!!!.
THIS TOOL WORKS FOR Linux and Windows. the guide is for windows but the script would work for linux completely fine.
REQUIREMENTS
Download The Tool from the thread
Install Python From Microsoft Store Or The Python Website
Run Powershell as Admin
Run the Command:- python unlock.py
Enter Your IMEI Number
MAKE SURE YOUR PHONE IS CONNECTED TO ADB!!!!!
Wait for the code to be found
If your phone reboot into EMUI reboot back into bootloader mode and the tool will start the bootloader unlocking process
The Phone May Reboot Several Times.
If you get an warning about unlocking the bootloader you have succeeded to unlock the bootloader
Special Thanks To KASHIFALIKHAN For the tool . the download will be down below
Hello does unlocking bootloader resets my data? As in will it factory reset?
Yes it would reset your data. It happens on all phones for security reason
deleted
Hello..could you please explain more about the process and what should we do about attached file?
you have to extract the ZIP and run the unlock script and enter your imei number make sure you have python installed on your PC
TMHAKIM said:
you have to extract the ZIP and run the unlock script and enter your imei number make sure you have python installed on your PC
Click to expand...
Click to collapse
Thank you for your answer..
So ,unlocking bootloader resets my data..
My phone is nova 3i android 9 LX2..
Is this procedure safe for my phone?
Have you tried it on this model?
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
honorable9x said:
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
Click to expand...
Click to collapse
Have you installed Hisuite drivers? And check device manager when you boot into fastboot if it shows Android bootloader interface then you're good to go if not then try installing Hisuite drivers
honorable9x said:
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
Click to expand...
Click to collapse
Since you could enter the bootloader when you first trying, I'm guess it might be the Harmony OS. You can try use Hisuite to roll back your HarmonyOS to EMUI, then try to unlock the bootloader. Most of modified Android OS removed the OEM mode to make you have a hard time on unlock bootloader. These will be really easy if you use some phones like Google's Pixel.
I have an old Huawei Nova 3i and it's updated into the Harmony OS, which is not what I want, I'd like to have a more cleaner OS that not with so much preinstalled apps. Then I roll back to EMUI as the first step to install other ROM, and that script it's working now. It's still trying get the password so I can't say it worked or some thing else.
And alter is that, if you just want install some google-apps, you may just roll back to EMUI, it should worked fine. And I'm not really suggest you have any phone from Huawei now since they really push their Harmony OS as a thing (at least, in China) and not really friendly towards people not in China (since lots of popular apps' depended G-apps). I'm annoyed even I'm Chinese though.