Develop Bugs

Tutorial Htc Bootloader (Complete With the new ruu)

BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
NOTE: If you do not find your ROM version in the table below, and your ROM version is newer, then your device does not require the RUU.
To install the RUU, simply follow these instructions:
1. On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes.
2.If your computer cannot find your phone, you may need to install HTC Sync. You can download HTC Sync http://www.htc.com/www/help/
After your computer has found your phone, double click on the RUU to start the process.
3Follow the on screen instructions to finish flashing the RUU on your phone.
NOTE: If you encounter an error while flashing your phone, it’s possible that the connection to your phone was interrupted. Simply exit the program, disconnect your phone and start over.
Fully exit the RUU to ensure there is no conflict of multiple instances of the program running.
Disconnect the USB cable from both the phone and the computer.
After a few moments, reconnect the USB to the computer and phone. See above if your phone or computer cannot find each other.
Run the RUU.
Disclaimer: You may not be able to get further FOTA updates once the RUU was applied to your device.
Ruu:
Htc Eu http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R.exe
htc Arabic: http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.09.0099_0209_R.exe
Step 1
Remove and reinsert the battery then proceed to step 2. For devices without a removable battery, long press the power key then select restart. Hold down the volume down key while restarting to start the device in Bootloader mode.
Step 2
Press Volume Down and Power to start the device into Bootloader mode.
Step 3
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 4
Connect the device to the computer via a usb cable
Step 5
On your computer create a new folder (For Example: C:\Android) where we will be putting the following 3 files in this new folder:
adb.exe
AdbWinApi.dll
fastboot.exe
Note: for Mac OS X and Linux you will only need adb and fastboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To find these files:
a.
Run the “SDK Manager.exe” which is found in \android-sdk-windows\
.
Wait about 3 minutes. You will see there are many packages you can update. Please install Android SDK Platform Tools and Android SDK Tools (Please update it if your SDK version is r11).
c.
After you have installed this, you will be able to find the files in the following locations.
1.
To find adb.exe, AdbWinApi.dll, look in \android-sdk-windows\platform-tools
2.
To find fastboot.exe look in \android-sdk-windows\tools
Note: fastboot.exe may be unavailable in the latest Windows Android Tools release. You can extract it from a previous release available here: android-sdk_r13-windows.zip
3.
Mac OS X or Linux users can download the fastboot binary using the following links:
https://www.htcdev.com/process/legal_fastboot_mac
Step 6
Open up command prompt. ( Start > Run > Type CMD,). The window that appears is called Command Prompt.
Step 7
Navigate to where you unzipped the ZIP file and go to the folder you just created (For Example: If you created the folder in C:\Android, then you would type in Command Prompt: cd c:\Android).
Step 8
Type in Command Prompt: fastboot oem get_identifier_token.
Step 9
You will see a long block of text. Copy and paste this text into the the token field below (in the command prompt: Right Click > Mark > highlight the block of text > Right click to copy).
You will see one of the following two screens:
Ref. 9a
Ref. 9b
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)
Step 10
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.
Example:
use the link below to make the bootloader unlock correctly
http://www.htcdev.com/
Program to download
Google android sdk
http://developer.android.com/sdk/index.html
Java Runtime
http://java.com/
htc Sync
http://www.htc.com/www/help/
Credit:
Htc Dev For this page
Thehack1
DjOlivier
Me to have the time to paste and write
If some person have a question and i going to help for every thing

[UTILITY|S-OFF] RegawMOD Bootloader Customizer for Verizon HTC One

Description
Verizon HTC One Plug-In for the RegawMOD Bootloader Customizer is now available!
WARNING: YOU MUST BE S-OFF TO USE THIS TOOL AND PLUG-IN
This plug-in will allow you to use the RegawMOD Bootloader Customizer written by regaw_leinad.
With the tool and this plug-in, you can easily create a custom HTC firmware zip for the Verizon HTC One containing a custom bootloader image. You will be able to edit the *** UNLOCKED *** text on the top to whatever you want it to say, change the S-OFF to S-ON, change the bootloader's minor version number, update the bootloader's date and time stamp, and either hide or customize the splash screen disclaimer. Using this tool to change S-OFF to S-ON changes only the text on the screen, it does not change your s-off status of the phone. Same goes for "locked"/"unlocked"/"Relocked" so be careful to remember the correct state of your phone.
Choosing the "Stock" option, the tool automatically sets your banner to say *** LOCKED ***, changes S-OFF to S-ON and hides the HTC Development Splash Screen Disclaimer.
This program will NOT flash the zip for you, but it will create a PN07VZW.ZIP file and save it your computer. From there, you then need to flash it via fastboot.
The process (flashing a new bootloader) is dangerous and may possibly brick your device if done incorrectly. You have been warned
App Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot
This plug-in is based on the stock 1.54.000 hboot (v.10).
How To Flash A firmware zip (Devices without a removable sdcard)
Reboot the phone into the bootloader by either:
Powering off your phone completely, then hold Volume-Down and Power until the phone boots into the bootloader
If you have the android sdk set up, type 'adb reboot-bootloader'
Use the RegawMOD Rebooter
Connect your phone to the computer (if it isn't already) and issue the fastboot command
Code:
fastboot oem rebootRUU
To flash the zip, issue the fastboot command
Code:
fastboot flash zip <[SIZE=2]YourZipName>.zip[/SIZE]
The device's progress bar may not be complete, but when the fastboot command says it's complete, issue the fastboot command below to see your changes
Code:
fastboot reboot-bootloader
To complete the process, issue the fastboot command below to reboot your phone to normal operation
Code:
fastboot reboot
As noted in #4, the progress bar may not reach 100% when flashing this, and the the progress bar will likely look like this:
Just be sure to get the success response from the fastboot flash command and reboot via fastboot. Do not remove your phone from the computer until it has rebooted from the fastboot reboot command.
Download Latest Plug-In Release
Stock hboot 1.54.0000 v.10 Plug-In
MD5s are on the linked page. Be SURE to verify after downloading the plug-in.
This plug in works for the main app version 2.2.3 and newer.
Download Latest Bootloader Customizer App
The main app can be found in regaw_leinad's OP here: http://forum.xda-developers.com/showthread.php?t=1786498
Reminder
WARNING: YOU MUST BE S-OFF TO USE THIS TOOL AND PLUG-IN
USE AT YOUR OWN RISK - YOU COULD BRICK YOUR PHONE
Credits
Main Program and awesome instructions for plug-in: regaw_leinad <-- Be sure give him "Thanks" on his OP
Verizon HTC One Plug-in: Me
Brave Tester & Additional Support: mdmower
Also thanks to mdmower for the outstanding phone screenshots.
Additional thanks to:
cyber_prometheus for offering to be first to test
andybones for the request to make this plugin in the first place.

Reserved

Lol awesome. Gonna use this like a mofo. Chocolate Chip Kick-Ass HTC One here I come.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 05:43 PM ---------- Previous post was at 05:39 PM ----------
Who wants me to change it to F*ck Verizon and then go into a store and have their "tech support" check it out?
Sent from my HTC6500LVW using XDA Premium 4 mobile app

will this v.10 hboot work correctly when I am still on firmware .8?

@junkmail9: In step 4, how about having users do
Code:
fastboot reboot-bootloader
so they can see the results of their mod?

mdmower said:
@junkmail9: In step 4, how about having users do
Code:
fastboot reboot-bootloader
so they can see the results of their mod?
Click to expand...
Click to collapse
Excellent suggestion! I'll update the OP.

andybones said:
will this v.10 hboot work correctly when I am still on firmware .8?
Click to expand...
Click to collapse
The answer is likely yes as long as you stay s-off, assuming only decryption keys were updated between hboots which is likely considering the hboot version number didn't increment between OTAs. Really though, the safest route is to install stock and let the v10 OTA apply. It is mostly just a radio update I believe, and then you're sure to have compatible firmware. You can stay s-off through this whole process.

Awesome you got this tested! Nice work, @junkmail9.

weird double post... oops

I keep getting error loading plugin even though i have it in the same folder as RegawMod. They are the only two files in that folder TBH. IDK what to do from here.

jmotyka said:
I keep getting error loading plugin even though i have it in the same folder as RegawMod. They are the only two files in that folder TBH. IDK what to do from here.
Click to expand...
Click to collapse
Make sure you have the latest main program. You will get an error loading plug in with earlier versions. If your main program is current and you have only one plug in, then the program will automatically load the single plugin in the same directory.
Also double check the md5 signature of the downloaded plugin.
Update: Main program needs to be version 2.2.3, not 2.2.2 as originally stated. Thanks to jmotyka for finding that. OP Updated accordingly.

Just checked the about screen and i have v2.2.3.0 and still the same problem.

jmotyka said:
Just checked the about screen and i have v2.2.3.0 and still the same problem.
Click to expand...
Click to collapse
Hmm...
MD5 of downloaded plugin is b3609caf074e38d854a186d277c77e8b ?
What version of Windows are you running?

Im running windows 7 64bit Home Premium. .NET is installed.

jmotyka said:
Im running windows 7 64bit Home Premium. .NET is installed.
Click to expand...
Click to collapse
That's strange. I have tested this on both 32-bit Windows XP and on Windows 7 64-bit (Professional) without any issues.
For the sake of troubleshooting, try downloading a different plug-in to see if it loads in the main program. Don't actually make a zip with the test plugin if it loads and absolutely do not flash it to your phone if you do make a zip... you'll end up with a brick. Be sure to delete the "other" plug-in after testing.

Error Loading Plugin for both HTC One and Droid INC.
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
Im trying .net 4.5 to see if that will work.
---------- Post added at 05:22 PM ---------- Previous post was at 05:15 PM ----------
Ok so i updated to .net 4.5 and restarted and im still getting the error.

jmotyka said:
Error Loading Plugin for both HTC One and Droid INC.
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
Im trying .net 4.5 to see if that will work.
---------- Post added at 05:22 PM ---------- Previous post was at 05:15 PM ----------
Ok so i updated to .net 4.5 and restarted and im still getting the error.
Click to expand...
Click to collapse
Can you post a screenshot of the error message?
Update: On my XP machine, I have the following .NET installed: 1.1, 2.0sp2, 3.0sp2, 3.5sp1, 4 client profile, 4 extended, and 4 multi-targeting pack. I can not check my Win7 64-bit machine for a while.

Right click on the plugin dll file, and in the General tab, click on "Unblock". You need to do that since the dll was downloaded from the internet. Doesn't the error message tell you to do that?

I will check it out as soon as I get to work. I apologize for any inconvenience this has caused you guys. TTYL. Thank you for your hard work.

jmotyka said:
I will check it out as soon as I get to work. I apologize for any inconvenience this has caused you guys. TTYL. Thank you for your hard work.
Click to expand...
Click to collapse
No inconvenience caused! Getting help is one of the many things this forum is for!

[Q] Widfier S: Can't obtain Identifier Token

MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry

GERJDOY said:
MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry
Click to expand...
Click to collapse
First things first, your problem is not unique..........just less often found
The reason you are not able to get an Identifier token is because of HTC Sync............. HTC Sync usually tends to block any ADB or Fastboot commands
So all you have to do is uninstall HTC Sync, don't worry about it as uninstalling it won't remove the drivers

Thanks very much for replying csoulr666
I promptly uninstalled HTC Sync, leaving:
HTC BMP USB Driver (Ver: 1.0.5375 ) 0.35MB
HTC Driver Installer (4.5..001 ) 2.82MB
and have tried the "get token" process again.
It has not worked.
Do you think that I should also uninstall the HTC Driver Installer?

GERJDOY said:
Thanks very much for replying csoulr666
I promptly uninstalled HTC Sync, leaving:
HTC BMP USB Driver (Ver: 1.0.5375 ) 0.35MB
HTC Driver Installer (4.5..001 ) 2.82MB
and have tried the "get token" process again.
It has not worked.
Do you think that I should also uninstall the HTC Driver Installer?
Click to expand...
Click to collapse
It should work now IMHO, did you see if your device is being recognized using "fastboot devices"???
Plus setting the folder to apply commands("cd"), try using the complete path that comes in the address bar in My Computer/Windows Explorer..........It would be like C................documents and settings......blah blah blah

Hi,
If you can not find a solution for your method of getting the token, you may try another method that worked fine for me.
1) Search for HTC Wildfire S All-In-One Toolkit V2.1 post.
2) Read carefully the whole post.
3) Uninstall everything related to HTC (HTC Sync, USB drivers, everything).
4) Do not use USB hubs or USB 3.0 ports. Enable USB Debugging at the phone settings and plug the phone directly to an USB 2.0 port without the SIM and SD cards (they may be erased while unlocking). Choose the Charge only option in your phone.
5) Proceed with the tool steps (select the step and click on 'go')(in useful links there is a link to a step by step guide):
a) Install the drivers.
b) Register at HTCDev (this is already done).
c) Get the ID (beware, you will see and empty command prompt, close it, and a second command window will appear with the token)
d) Submit the token to HTCDev.
e) Get the Unlock_code.bin file from your e-mail account.
f) Unlock the boot loader.
6) Once you have finished, I recommend to install the clockworkmod recovery with the same tool. Download the right version GSM or CDMA from the Clockworkmod official site. Beware: make sure that you download the right version for your phone. I think yours is GSM, but I am not an expert, sorry. It may be fatal if the wrong version is installed (brick). Choose the option your own recovery in the tool.
7) Create a backup before doing anything else.
8) You are ready to get a permanent root or install a ROM.
I hope this helps you. Feel free to ask any question. Regards.

GERJDOY said:
MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry
Click to expand...
Click to collapse
I think you are doing wrong with the c: android step you should first "cd android" and then enter "fastboot oem get_identifier_token"

csoulr666 said:
It should work now IMHO, did you see if your device is being recognized using "fastboot devices"???
Plus setting the folder to apply commands("cd"), try using the complete path that comes in the address bar in My Computer/Windows Explorer..........It would be like C................documents and settings......blah blah blah
Click to expand...
Click to collapse
Thanks for your continued time and assistance csoulr666. It's taken me a while to reply because after having no sucess having followed your advice, I decided to delete EVERYTHING and IT ALL FRESH, monitoring all downloads as they happened and ensuring I followed all steps and instructions PRECISELY, in case I did something wrong the first time around 3 months ago!
And following your recommendation I retried using the full path when typing both commands and it still didn't work. I'm not sure what you meant by "........your device is being recognized using "fastboot devices"???"
However, as you've mentioned "fastboot", I think I've identified an issue with the fastboot binaries from HTCdev. Please see my new post below.

aWFSuser said:
I think you are doing wrong with the c: android step you should first "cd android" and then enter "fastboot oem get_identifier_token"
Click to expand...
Click to collapse
aWFSuser- thank you for the advice.Yes, I do use the c: cd \Android command first, everytime I try the cmd process, even if it's after somthing silly like removing the sd card from the phone, putting a new one in (to render the "as disk drive" option available in the "USB connection type") on the handset, changing the USB port I'm using to a different one etc.
But thanks.

ukyo_tachibana said:
Hi,
If you can not find a solution for your method of getting the token, you may try another method that worked fine for me.
1) Search for HTC Wildfire S All-In-One Toolkit V2.1 post.
2) Read carefully the whole post.
3) Uninstall everything related to HTC (HTC Sync, USB drivers, everything).
4) Do not use USB hubs or USB 3.0 ports. Enable USB Debugging at the phone settings and plug the phone directly to an USB 2.0 port.
5) Proceed with the tool steps (select the step and click on 'go')(in useful links there is a link to a step by step guide):
a) Install the drivers.
b) Register at HTCDev (this is already done).
c) Get the ID (beware, you will see and empty command prompt, close it, and a second command window will appear with the token)
d) Submit the token to HTCDev.
e) Get the Unlock_code.bin file from your e-mail account.
f) Unlock the boot loader.
6) Once you have finished, I recommend to install the clockworkmod recovery with the same tool. Download the right version GSM or CDMA from the Clockworkmod official site. Beware: make sure that you download the right version for your phone. I think yours is GSM, but I am not an expert, sorry. It may be fatal if the wrong version is installed (brick). Choose the option your own recovery in the tool.
7) Create a backup before doing anything else.
8) You are ready to get a permanent root or install a ROM.
I hope this helps you. Feel free to ask any question. Regards.
Click to expand...
Click to collapse
Thanks so much ukyo_tachibana.
I will try this method, if I have failed to identify the issue correctly.
After having the problem of being unable to obtain my identifier token for so long, (trying now for 3 months!), I've been looking for a way to unlock bootloader & root- that works for the Wildfire S WITHOUT having to use the "get_identifier" process.
THANK YOU for this method!

It's taken me a while because after having no sucess, I decided to delete EVERYTHING and IT ALL FRESH, monitoring all downloads as they happened and ensuring I followed all steps and instructions PRECISELY, in case I did something wrong the first time around 3 months ago!
So, once again:
I created a folder: double click Local Disk C: then \Document&Settings and \administrater >Make a new folder. Called it Android.
Downloaded from HTCdev's links- HTC Sync, Java Runtime Enviroment & Google Android SDK to \Android.
(1) SYNC. Uninstalled Sync, as per csoulr666's advice. Used Control Panel> Add or Remove programs. This left HTC Driver Installer & HTC BMP USB Driver & also setup_3.3.63 (in \Android).
(2) JAVA. Opened chromeinstall-7u51(Runtime) and installed. Checked it installed correctly via Verify Java Version on java.com.
(3) SDK. Unzipped the zipped folder adt-bundle-windows-x86-201... It created a new folder- "adt-bundle-windows-x86-201.." with 2 subfolders & 1 application in it; subfolders (1)"eclipse" & (2)"sdk" along with the application "SDK Manager". NOW, as per instruction following the SDK download, (just in case it was relevant to what I am doing, although I don't think so as Eclipse is a developer tool as I understand it), I opened the eclipse sub-folder & opened (ran) the Eclipse application which set itself up in \workforce. I exited Eclipse in case it interfered with anything else. I did not run, open or do anything else with the adt folder at this stage.
Set up my HTC as per instruction- fastboot off, debugging on & usb to disk drive, (I've also tried it on the charge only setting), downloaded fastboot-win binaries from HTCdev to \Android. Clicked unzip and it generated 1 new folder _MACOSX & an application- fastboot; both in \Android. NOW HTCdev says "open cmd prompt...etc". So I did and retried the process twice. Once typing c: cd \Android. Then the c: \Android> fastboot oem...etc. It didn't work. So I repeated the process using the full path in both the commands- c:\Documents and Settings\administrater\ cd \Android; then c:\Doc...Sett...\admin...\Android> fastboot....Once again nothing. IT DID NOT WORK.
HOWEVER: I did notice 2 things!
(1) Probably nothing but there was a new folder created in \administrater, right beside the Android folder. As I was working from \Android, I didn't notice when happened. I did not do it. It called itself .android; ( "a dot" and a lowrecase "a" for android). I can't recall at what stage of the process this came into being. It contains 1 folder- "avd", which is empty, & 3 files- "adbkey" file, "adbkey.pub" file & "ddms.cfg" file.
(2) Just, following the latest failure of the cmd process working, I thought maybe I was meant to do more than just unzip the fastboot-win, so I went to the fastboot application and tried to open it, It said:
"The application failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem"
So I deleted it, re-downloaded from HTCdev, unzipped. Opened prompt, reran the cmd "get_identifier" process and it still hasn't worked. Again I to run the fastboot.exe in \Android
It still says "...application failed...AdbWinApi was not found. Re-installing the application...".
Does this mean the file download itself on HTCdev,com is corrupt? Could THIS BE the source of my problem????
Thanks.

I'm attaching a zip with the files I use for this stuff............Extract them in a folder, use the "cd" command to it and then try to obtain the token

csoulr666 said:
I'm attaching a zip with the files I use for this stuff............Extract them in a folder, use the "cd" command to it and then try to obtain the token
Click to expand...
Click to collapse
***csoulr666
Yes!! Thank you for the files. HTC's MUST BE corrupt, as your's have worked a treat & also. they behave differently ( "fastboot" application) when <highlight/right click > is used!! No error message! THANK YOU for your files. ***
They worked & after three months and hundreds of hours research, I HAVE MY TOKEN!! You guys are BRILLIANT!
However, there is a new issue, perhaps you can help with this also...
I copied the token exactly as HTC stated on their website. I started at <<<Identifier Token Start>>> & ended with <<<IIdentifier Token End>>>.
There are 18 lines in total- 16 lines of alpha/numeric sandwiched between the above 2 of text.
Both of HTC's examples also have the same line-count (18 in total 16 + 2) & layout as mine.
But when submitted, the website rejects it and the following error is returned:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
I've spent most of last night on this. I've tried logging in and out of HTCdev, copied and pasted multiple attempts (busy web traffic perhaps). I have cleared browser cookies/cache & history in case it's something like that. Counted and recounted my token in comparison with their examples, in case I made a mistake somehow. What am I doing wrong??.
Also, today when I tried the cmd get_token process, I got a different token i.e. a completely different set of 16 lines of alpha/numeric text. Is the token different every time it's requested?
Thank you all for your expert help

GERJDOY said:
***csoulr666
Yes!! Thank you for the files. HTC's MUST BE corrupt, as your's have worked a treat & also. they behave differently ( "fastboot" application) when <highlight/right click > is used!! No error message! THANK YOU for your files. ***
They worked & after three months and hundreds of hours research, I HAVE MY TOKEN!! You guys are BRILLIANT!
However, there is a new issue, perhaps you can help with this also...
I copied the token exactly as HTC stated on their website. I started at <<<Identifier Token Start>>> & ended with <<<IIdentifier Token End>>>.
There are 18 lines in total- 16 lines of alpha/numeric sandwiched between the above 2 of text.
Both of HTC's examples also have the same line-count (18 in total 16 + 2) & layout as mine.
But when submitted, the website rejects it and the following error is returned:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
I've spent most of last night on this. I've tried logging in and out of HTCdev, copied and pasted multiple attempts (busy web traffic perhaps). I have cleared browser cookies/cache & history in case it's something like that. Counted and recounted my token in comparison with their examples, in case I made a mistake somehow. What am I doing wrong??.
Also, today when I tried the cmd get_token process, I got a different token i.e. a completely different set of 16 lines of alpha/numeric text. Is the token different every time it's requested?
Thank you all for your expert help
Click to expand...
Click to collapse
see whether you have copied the code correctly as instructed at HTCdev

Hi,
The token seems to be different every time you retrieve it, I don't know why (maybe someone can enlighten us ).
Regarding the token copy/paste. At the command window: right click, select mark, draw the rectangle enclosing the <<<< Identifier Token Start >>>> and <<<<< Identifier Token End >>>>> (this also includes all the alphanumeric token), right click again to copy. Now, paste it in Notepad, PSPad or any other text editor, and make sure that there are no white spaces, tabs, or any other special character, such as this example:
Code:
<<<< Identifier Token Start >>>>
5C1161E707F362366365EA333A6B51D6
7B52743B74534195B1C0CD07E738AEA3
93A6BD42CFA2C05006C6282B590CEDC3
6593DE3AEF7786B79527C1027E871C3D
9DDD04692D8F653D9BD548D86CB0AC58
01CDF6096D229B7E418BD74E8AC2311C
77D92CE222450E4B233CEC2286DD9CA4
C0871C78B430F4474C74FCE113E95C2D
2134C5495D588B3A580710A226A6675C
3D9F01CB8A8EF628A4EC2BB867E47D3E
2476FE360221DC834197EAECCA4BB09A
243420AEB1CFC713A658FC0A156448A9
6859FF58473B71BDFFFF5FFF292B066B
9CA1B055827C43BFE0F30A656906801E
35FD964354DAA6F83A38FE7D7452B97A
171BDB3A9D280118C638240DEDA452DE
<<<<< Identifier Token End >>>>>
If you select previous lines, there are no unwanted characters, check it. Once you are sure that everything is okay, submit the token to HTC.
I hope this post helps you. Regards.

By the way, two comments:
1) Note that unlocking HBoot is a destructive process, you will loose everything in the phone memory (similar to a factory reset). Besides, the SIM card and the SD card may be also erased, so remove both before starting.
2) If you want to install a custom rom, you don't know which one to install yet and you want some help, I can suggest one that has been working like a charm for more than one year in my Wildfire S. It is based on the last stock rom, but with several tweaks to overcome the limitations of the terminal (amount of RAM, internal storage, etc.). Do not hesitate to ask.
Regards.

ukyo_tachibana said:
Hi,
The token seems to be different every time you retrieve it, I don't know why (maybe someone can enlighten us ).
Regarding the token copy/paste. At the command window: right click, select mark, draw the rectangle enclosing the <<<< Identifier Token Start >>>> and <<<<< Identifier Token End >>>>> (this also includes all the alphanumeric token), right click again to copy. Now, paste it in Notepad, PSPad or any other text editor, and make sure that there are no white spaces, tabs, or any other special character, such as this example:
Code:
<<<< Identifier Token Start >>>>
5C1161E707F362366365EA333A6B51D6
7B52743B74534195B1C0CD07E738AEA3
93A6BD42CFA2C05006C6282B590CEDC3
6593DE3AEF7786B79527C1027E871C3D
9DDD04692D8F653D9BD548D86CB0AC58
01CDF6096D229B7E418BD74E8AC2311C
77D92CE222450E4B233CEC2286DD9CA4
C0871C78B430F4474C74FCE113E95C2D
2134C5495D588B3A580710A226A6675C
3D9F01CB8A8EF628A4EC2BB867E47D3E
2476FE360221DC834197EAECCA4BB09A
243420AEB1CFC713A658FC0A156448A9
6859FF58473B71BDFFFF5FFF292B066B
9CA1B055827C43BFE0F30A656906801E
35FD964354DAA6F83A38FE7D7452B97A
171BDB3A9D280118C638240DEDA452DE
<<<<< Identifier Token End >>>>>
If you select previous lines, there are no unwanted characters, check it. Once you are sure that everything is okay, submit the token to HTC.
I hope this post helps you. Regards.
Click to expand...
Click to collapse
BRILLIANT!!
I followed your recommendation- copy to notepad- there were white spaces:
Note: the <right click/copy> function was not available in cmd prompt.
I had to "mark" and then ctrl & c to copy.
I had spaces at the end of each of the token's lines.
Thanks. Token successfully submitted- just over ten minutes ago. Awaiting an email back from HTCdev with an unlock key and link for Unlock completion!
I assumed I'd have it instantaneously...but I'll be patient; it's taken this long to get this far...what's a few hours? more.
I have not given ANY thought to ROMs etc.
This part of the process baffles me.
This all began three months ago when I got the Wildfire S- my first ANDROID phone- and I noticed there are loads of pre-installed apps on it, many of which I have absolutely no interest in: like Peep, News & Weather, Maps & tons more via: Applications>Running Services>All. TO MY UTTER AMAZMENT I could not delete any of them!
Call me old fashioned but I would like to decide what I put on my phone and have total control over them. On this phone certain apps would start up of their own volition i.e. when the handset was powered off, then on; gather information and data; all without me even using/ activating them e.g. Google services/ Facebook. I could stop them manually, but like I said they would reassert themselves on start-up.
I'm unclear yet exactly what I can safely get rid of without damaging my handset, I need to do research I know, as some processes may be vital to the phone's operation, but I have been consumed with this first basic step- Unlocking the BootLoader.
Ideally, I would love to start with an empty phone- just the basics: calls/messages/phone book/ calender/ alarm facilities with a browser.
A normal, basic phone.
Any extra apps I am then free to decide upon, install, set permissions (where possible) & remove as & if I choose.
Thanks.

Hi,
Did you get the unlock binary file? It should take no longer than a few minutes (or even less) to send it to your e-mail account. Did you successfully unlock the HBoot? Let us know . Regards.

ukyo_tachibana said:
Hi,
Did you get the unlock binary file? It should take no longer than a few minutes (or even less) to send it to your e-mail account. Did you successfully unlock the HBoot? Let us know . Regards.
Click to expand...
Click to collapse
Hi ukyo_tachibana,
Thank you for your ongoing interest. I appreciate it greatly.
I have been checking my email address all night last night, and also today, awaiting my email from HTCdev.
No! As yet (over 24 hours later), I have not yet received my response.
HTCdev's site confirmed that I successfully sent my token when I did. I remained logged in for a hour and a half afterwards, just so the site would notice/ remember me. Sounds daft, but I really want this episode to finish now after all this time. I really thought I had cracked this step!
The web page said to expect and email with my unlock code and a link to directions to help me complete the process.
Now, over 24 hours later, I still have not received any communication from them. I check my email address- the one I used to register with them and, in late December of last year, communicate as to why I the "get_identifier token" process was not working- ever hour or so for the file & link. So I'm sure the site has my correct email address.
I was actually wondering what to do now as I'm unsure as whether I should wait X amount of time, contact them via the "contact us" option on their web site or resend a token to them and risk confusing the process. Basically I'm just playing the waiting/ unsure-of-next-move game.
Thanks.

Hi,
Do not despair . The token should be send to you in question of seconds (but in order to be safe wait a few minutes, no more than 5 minutes). The email sender should be something like [email protected] and the subject should be The key to unlocking your HTC Device (at least, this is what I received).
I would:
1) Search for the email in any other folder than the Inbox, such as spam. Your email provider may have archived the message in a different folder.
If you are not able to find the message:
2) Try to find your email white list and add htc.com and htcdev.com to the list, in order to avoid that emails from HTC or HTC Dev go to the spam folder or are erased.
3) Check that you activated your account. Register at the website is not enough, you also must activate your account clicking on the link that HTC send to confirm your email address. I know that this question is a bit stupid, but it just to cover all the possibilities that I can think about.
4) Get and send again the token.
I hope this helps you. Regards.

I have my email now.
Before I proceed, as I'm a complete techno-novice, I was just looking into how to create a full back up of my stock ROM, in case I decided to pass on the phone later I can return it to it's current out-of-the box condition- with all it's apps etc. Also I need to be clear on the root process files. I don't have the original SD Card. I have two to hand though- a 2GB & 4 GB.
Step 1- Unlock BootLoader.
REALLY, REALLY NOT sure of the rest:
Step 2- download CWM Recovery from (http://www.clockworkmod.com/rommanager/) 5.0.2.8 for the Wiidfire S to my PC.
?Move to SD Card
?Hboot>Recovery>chooseCWM and there should be an option to "Back-Up/ Restore"
?Select this option and "Back-Up". Wait for stoc ROM to be copied onto SD Card. When it has this is the back-up phase complete
As I understand it this will give me a re-installation disk type set up for my current ROM.
Step 3
?Find and download a file to my PC called "Root Zip".
?Transfer it to my SD Card
?Hboot>Recovery>choose file and it roots the phone itself.
Step4
?Find and download a file called "SuperSU"
?Move to SD Card and install.
??This gives me an app called "SuperSU" which allows me now to modify my phone how I like it to be- prevent apps starting at boot/ remove any preinstalled ones that I don't want or do I need to install a custom ROM?
Thanks,

Bootloader Code Generator for Huawei P20 EML-L29

Hello,
I am currently building a python script to generate codes for Huawei P20 (EML-L29) bootloader.
So far, I have to deal with these things in order to make it work:
- the code is a 16 digit number
- the last tried code is stored in a txt file to resume if anything crashes and it goes up incrementally.
- the code usually starts with 15XXXXXXXXXXXXXX
- at 5 failed attempts, the phone will reboot to normal mode. To prevent this, at every 4th failed attempt, It runs "fastboot reboot-bootloader" command to reset the counter.
- each attempt takes 4.5 seconds to complete. No other command will be taken while waiting for response from the phone.
- It tries about 10000 codes per day (which is too slow).
Is there any method to prevent the wait time for every attempt in order to make it run faster?
Here is the code I have used:
Code:
import os, sys, time
start = 1500000000000000
bootloaderGeneratedCode = "bootloaderGeneratedCode.txt"
bootloaderFoundCode = "bootloaderFoundCode.txt"
currentCode = start
lastCode = currentCode
tries = 1
def checkTxtFiles():
if not os.path.isfile(bootloaderGeneratedCode):
with open(bootloaderGeneratedCode, "w+") as bgc:
bgc.seek(0)
bgc.write(str(start))
if not os.path.isfile(bootloaderFoundCode):
with open(bootloaderFoundCode, "w+") as bgc:
bgc.seek(0)
bgc.write(str(""))
def checkFastbootDevices():
res = str(os.popen("fastboot devices").read()).replace("List of devices attached", "").replace("fastboot", "").replace("device", "").replace(" ", "").replace("\n", "").replace("\r", "").replace("\t", "")
# print(res)
if "" == res:
return False
else:
if "not found" in str(res) or "error" in str(res):
return False
else:
return True
def checkAdbDevices():
res = str(os.popen("adb devices").read()).replace("List of devices attached", "").replace("fastboot", "").replace("device", "").replace(" ", "").replace("\n", "").replace("\r", "").replace("\t", "")# print(str(res))
if "" == res:
return False
else:
if "not found" in str(res) or "error" in str(res):
return False
else:
return True
def rebootBootloader():
if checkFastbootDevices():
res = os.popen("fastboot reboot-bootloader").read()
else:
res = os.popen("adb reboot-bootloader").read()
print(str(res))
def tryCode(code):
global bootloaderFoundCode
global tries
res = os.popen("fastboot oem unlock "+str(code)).read()
if "too many links" in str(res):
tries = 1
if "FAILED" in str(res):
#code failed
pass
elif "OKAY" in str(res) or "SUCCESS" in str(res):
#code succeeded
with open(bootloaderFoundCode, "w+") as bgc:
bgc.seek(0)
bgc.write(str(code))
print("FOUND BOOTLOADER CODE: "+str(code))
sys.exit(0)
#print(str(res))
def getLastCode():
with open(bootloaderGeneratedCode, "r") as f:
f.seek(0)
return f.read()
checkTxtFiles()
with open(bootloaderFoundCode, "r") as bgc:
bgc.seek(0)
code = bgc.read()
if 0 < len(code):
print("FOUND BOOTLOADER CODE: "+str(code))
sys.exit(0)
else:
while True:
while checkFastbootDevices():
#has fastboot devices
print("Found fastboot device")
if tries <= 4:
#can try oem unlock
currentCode = int(getLastCode())
print("Trying "+str(tries)+" of 4 with code "+str(currentCode))
tryCode(currentCode)
currentCode += 1
with open(bootloaderGeneratedCode, "w") as f:
f.seek(0)
f.write(str(currentCode))
tries += 1
else:
#need to reboot-bootloader
tries = 1
rebootBootloader()
if not checkFastbootDevices():
#no fastboot device detected
print("Waiting for device..")
while not checkFastbootDevices():
if checkAdbDevices():
print("ADB Device found. Will reboot to bootloader");
rebootBootloader()
tries = 1
else:
time.sleep(1)
tries = 1

sorinbotirla said:
the code usually starts with 15XXXXXXXXXXXXXX
Click to expand...
Click to collapse
Mine starts with Z1A...

oslo83 said:
Mine starts with Z1A...
Click to expand...
Click to collapse
do you mean your bootloader code also has letters for your P20 EML-L29?
this could be a bit overkill. Having the wait times, and now letters.

I believe more than one unlock code may exist for a device. -I was told to be wrong, it's unique.
But bootloader's unlock code is alphanumeric.

Bootloader unlock code
I have a EML-L29
and my bootloader unlock code started with H6S...
Peace

I have no experience with anything like this but it might be possible to use machine learning to try and guess the unlock with enough bootloader unlock codes that have already been generated and IMEI.

TonyCubed said:
I have no experience with anything like this but it might be possible to use machine learning to try and guess the unlock with enough bootloader unlock codes that have already been generated and IMEI.
Click to expand...
Click to collapse
Hi, I have experience with machine learning and I can handle this. But getting pairs of IMEI/unlock codes from others might not be an easy task due to privacy issues involved. AFAIK IMEI posting on this board is forbidden.

sorinbotirla said:
- the code usually starts with 15XXXXXXXXXXXXXX
...
Click to expand...
Click to collapse
Mine doesn't. It starts with C0E

Try no more! Apparently someone has found a way to unlock bootloader without a code(on honor play), but it requires phone disassembly and doing some stuff...

panjaksli said:
Try no more! Apparently someone has found a way to unlock bootloader without a code(on honor play), but it requires phone disassembly and doing some stuff...
Click to expand...
Click to collapse
can you provide more info about this? thank you

sorinbotirla said:
can you provide more info about this? thank you
Click to expand...
Click to collapse
Just look at the honor play thread: https://forum.xda-developers.com/honor-play/how-to/unlock-bootloader-unofficial-free-t3914658
I would definitely try to contact the author, since it has configuration for honor play so far only, maybe the P20 might be very similar.

panjaksli said:
Just look at the honor play thread: https://forum.xda-developers.com/honor-play/how-to/unlock-bootloader-unofficial-free-t3914658
I would definitely try to contact the author, since it has configuration for honor play so far only, maybe the P20 might be very similar.
Click to expand...
Click to collapse
Hi,
I have managed to put the P20 in tespoint mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and tried to flash the twrp using the method described in that post and I got the successful PASS message. The testpoint mode allows temporary bootloader unlock.
however, even if I immediately pressed the volume up button and unplugged the usb to prevent the phone to overwrite the recovery with the default eRecovery at reboot, it still brings me to the default eRecovery (no twrp shown).
I tried to set again the tespoint mode and flashed the twrp img with fastboot using this command
flash recovery_ramdisk twrp.img
tbe flash returned OK on both sending and writing but I couldn't get the twrp shown as it pointed me again to the eRecovery (I rebooted the phone directly in recovery mode)
I tried to flash several images but without success (messages returned are OKAY but I don't think they were really written)
Does the testpoint mode actually allows to write files or just emulates the status messages returned? I think I miss something.

sorinbotirla said:
Hi,
I have managed to put the P20 in tespoint mode
and tried to flash the twrp using the method described in that post and I got the successful PASS message. The tespoint mode allows temporary bootloader unlock.
however, even if I immediately pressed the volume up button and unplugged the usb to prevent the phone to overwrite the recovery with the default eRecovery at reboot, it still brings me to the default eRecovery (no twrp shown).
I tried to set again the tespoint mode and flashed the twrp img with fastboot using this command
flash recovery_ramdisk twrp.img
tbe flash returned OK on both sending and writing but I couldn't get the twrp shown as it pointed me again to the eRecovery (I rebooted the phone directly in recovery mode)
I tried to flash several images but without success (messages returned are OKAY but I don't think they were really written)
Does the tespoint mode actually allows to write files or just emulates the status messages returned? I think I miss something.
Click to expand...
Click to collapse
Did you edit the XML file in the program's folder ? It has the device code name in it(but for honor play) and also paths to the files to be flashed. Also maybe you need specific bootloader and fastboot(recovery) image for the P20 ? I would try it with patched imgs for p20 which should be somewhere here on this xda forum. And btw. you've got some balls to disassemble your phone just for experimenting with bootloader unlock
---------- Post added at 01:46 PM ---------- Previous post was at 01:42 PM ----------
panjaksli said:
Did you edit the XML file in the program's folder ? It has the device code name in it(but for honor play) and also paths to the files to be flashed. Also maybe you need specific bootloader and fastboot(recovery) image for the P20 ? I would try it with patched imgs for p20 which should be somewhere here on this xda forum. And btw. you've got some balls to disassemble your phone just for experimenting with bootloader unlock
Click to expand...
Click to collapse
Wait, that screen says your phone is unlocked ??? Then I would try this https://forum.xda-developers.com/huawei-p20/development/root-huawei-p20-pie-emui-9-t3892601 or https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-finally-root-emui9-t3883295

panjaksli said:
Did you edit the XML file in the program's folder ? It has the device code name in it(but for honor play) and also paths to the files to be flashed. Also maybe you need specific bootloader and fastboot(recovery) image for the P20 ? I would try it with patched imgs for p20 which should be somewhere here on this xda forum. And btw. you've got some balls to disassemble your phone just for experimenting with bootloader unlock
Click to expand...
Click to collapse
no I haven't changed the xml file. Just kept the files in place (with the right paths to ramdisk image). I will give a try to other images. To dissasemble the phone I have bought an ifixit pro set and heated the cover with a heatgun to melt the glue.
Here is a tutorial to disassemble the P20
https://www.youtube.com/watch?v=D4udqBEK0wQ
panjaksli said:
Wait, that screen says your phone is unlocked ??? Then I would try this https://forum.xda-developers.com/huawei-p20/development/root-huawei-p20-pie-emui-9-t3892601 or https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-finally-root-emui9-t3883295
Click to expand...
Click to collapse
After I put my phone in testpoint mode, the fastboot menu shows the Unlocked status for the bootloader (Phone: unlocked). This is just a temporary unlock and it requires putting the phone in testpoint mode again when you need to unlock it.

sorinbotirla said:
no I haven't changed the xml file. Just kept the files in place (with the right paths to ramdisk image). I will give a try to other images. To dissasemble the phone I have bought an ifixit pro set and heated the cover with a heatgun to melt the glue.
Here is a tutorial to disassemble the P20
https://www.youtube.com/watch?v=D4udqBEK0wQ
After I put my phone in testpoint mode, the fastboot menu shows the Unlocked status for the bootloader (Phone: unlocked). This is just a temporary unlock and it requires putting the phone in testpoint mode again when you need to unlock it.
Click to expand...
Click to collapse
Waiiit, if it unlocks phone temporary, if you bridge it, what about soldering those leads together ? Does it still boot normally into system, or just straight up into the bootloader ?

panjaksli said:
Waiiit, if it unlocks phone temporary, if you bridge it, what about soldering those leads together ? Does it still boot normally into system, or just straight up into the bootloader ?
Click to expand...
Click to collapse
LoL that's why I like this board. It comes along with amazing people like you. I haven't yet tried to solder them but the testpoint doesn't automatically boot the phone into fastboot You can boot normally. It is possible that you might just solved one of the biggest issues on the Huawei community.
Yet. I still have to test it to confirm that a temporary bootloader unlock can be simply converted into permanent by just soldering testpoints.
I will keep you updated

panjaksli said:
Waiiit, if it unlocks phone temporary, if you bridge it, what about soldering those leads together ? Does it still boot normally into system, or just straight up into the bootloader ?
Click to expand...
Click to collapse
I have tried to use a wire between the testing points but unfortunately the device doesn't boot while they are connected.

Hi
Hi all ,how to use this code ? Please write me Step by Step

wlosiu30 said:
Hi all ,how to use this code ? Please write me Step by Step
Click to expand...
Click to collapse
hahahahaha

wlosiu30 said:
Hi all ,how to use this code ? Please write me Step by Step
Click to expand...
Click to collapse
1. install Python on your pc
2. install fastboot and adb on your pc
3. enable developer options on your phone
4. enable "allow oem unlock" in developer options
5. connect the phone to your pc with usb and allow usb debugging confirmation (also check the "trust this computer" checkbox)
6. create a file called "unlockBootloader.py" and copy paste the code inside it.
7. open cmd/terminal/powershell and navigate to the file.
8. run python unlockBootloader.py and then leave the room and buy other phone. Also don't forget to live your life. You'll need it later in the next steps.
9. ???????
10. return when you are 120 years old and hope your phone is unlocked (which I doubt)
11. enjoy your unlocked Huawei and die happy few seconds later.
12. profit

12" Chinese Review Mirror Bootloader Unlock/Firmware Update/Theme

Using Ubuntu inside VirtualBox:
Ensure your VirtualBox is setup to see all USB devices, has internet, folder share, and drag & drop enabled.
1. Go to files and create a folder under /home/username/ called “Media”
2. Give permissions to the folder and all subsequent files by right clicking, going to properties, and setting them to allow “create and delete files”.
3. Give permissions for local network share by sharing folder, allowing others to create and delete files in the folder, and allowing guest access.
4. Inside the “Media” folder you will place a modified fastboot zip folder and extract it’s contents into this location. The zip file can be downloaded from here: Modified_fastboot
Now that you have your Computer setup, let’s get started.
--------------------------------------------------------------------------------------------
Prepare Android Mirror: (Plugged into CPU via USB)
1. Power on Android mirror.
2. Go to "Settings".
3. Scroll down and select "System".
4. Scroll down and select "About phone".
5. Scroll all the way down and click on build number until developer mode is unlocked.
6. Click on "Baseband version" 4 times to access EngineerMode.
7. Select "DEBUG&LOG".
A. Enable Never Screen Off.
B. Disable Watch Dog.
C. Enable USB Debug.
D. Allow USB debugging “Always on this computer”, and select “ok”.
8. Click the back arrow far left bottom 2 times until back in System settings.
9. Now you should see “Developer options”. Select it and turn it on.
A. Enable Stay awake.
B. Enable OEM unlocking.
C. Verify USB debugging is enabled.
D. Enable Adb Root Privileges. Pin = 2846
10. Device is now ready.
--------------------------------------------------------------------------------------------
Using Windows with Ubuntu installed within Virtualbox:
To get into fastboot:
1. Ensure you have the latest platform tools for windows. This can be downloaded from here:
Win Platform Tools
2. Extract contents to a folder.
3. Open extracted folder, right click in folder, where you see adb.exe, and select “Open in Windows Terminal”.
**** These next steps I found are to be done in a specific order and time so pay close attention ****
4. Type “./adb devices”. Press enter after the beep sound and the 4G loading screen disappears.
./adb devices
Click to expand...
Click to collapse
If done correctly you will see the following:
List of devices attached
XXXXXXXXXXXXXX device
5. Type “./adb reboot bootloader”.
./adb reboot bootloader
Click to expand...
Click to collapse
6. Press enter. - Must be done before the screen goes black and you hear the next beep. If done correctly you will see on the far left:
fastboot mode
7. You are now in fastboot mode. Try not to take too much time with unlocking the bootloader as this may timeout and take multiple tries.
--------------------------------------------------------------------------------------------
Within Ubuntu:
Unlocking bootloader within Fastboot:
1. Open the modified_fastboot folder, right-click then select Open in Terminal.
2. Setup permissions for user by entering the following one at a time followed by enter.
sudo -i
Click to expand...
Click to collapse
sudo usermod -aG plugdev root
Click to expand...
Click to collapse
cd /home/po/Media/modified_fastboot
Click to expand...
Click to collapse
3. Test device detection using:
./fastboot devices
Click to expand...
Click to collapse
4. Get identifier Token using:
./fastboot oem get_identifier_token
Click to expand...
Click to collapse
5. You should get an output like:
Identifier token:
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
OKAY [0.019s]
finished. Total time: 0.019s
6. Copy the Identifier token.
7. Run this command ; replace XXXXXXXXXXXXXXXXXXXXXXXXXXXX with your Identifier token. Should look like this:
./signidentifier_unlockbootloader.sh XXXXXXXXXXXXXXXXXXXXXXXXXXXX rsa4096_vbmeta.pem signature.bin
Click to expand...
Click to collapse
8. You should have an output like:
Identifier sign script, ver 0.10
1+0 records in
1+0 records out
50 bytes copied, 0.000257562 s, 194kB/s
Identifier sign successfully
9. You should also see a signature.bin file in the modified_fastboot folder.
10. Finally run this command:
./fastboot flashing unlock_bootloader signature.bin
Click to expand...
Click to collapse
11. When it asks to confirm bootloader unlock (volume up/volume down options):
Locate the A/V port on the top of the device, looks like a 3.5mm plug, and use a small ½” long device/toothpick/paperclip to push the button on the inside of the port at the bottom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12. The status should now say:
Begin to erase user data…
This takes >5mins to accomplish
13. Once completed successfully, the status will say:
Info: Unlock bootloader success!
14. Wait 2 minutes and hold the power down to restart the device. The device will restart a few times and will now indicate the bootloader unlocked on the left side of mirror.
--------------------------------------------------------------------------------------------
Update to latest firmware:
1. Go to and read through the Original Post, Original Post in Russian, and ensure your device is the same device or very similar in design. If not you should not update with the mentioned firmware.
2. Download firmware update:
QC_BITE_M5_188_Media_Sleep_2021010619_202101061959_64bit.pac
The tools that will be needed and instructions:
1.Go to this website, https://spdflashtool.com/
2. Download latest version of Research Tool here: Research-tool
3. Follow instructions on how to use the Research Tool here: Instructions
A. Here is the link for the SPD driver you will need: Drivers
B. Stop at step 8 do not connect your mirror to the computer. Make sure your mirror is turned off and follow this video to complete the installation process:
--------------------------------------------------------------------------------------------
If you would rather complete with written tutorial vice watching video, here are the remaining steps.
1. Turn off the mirror if not done already.
2. Ensure firmware loaded into the Research tool and press the Play/start button.
3. With something small like a toothpick/paperclip, press the button inside the AV port at the top of the mirror. Make sure you find the button before proceeding.
4. Once you have found the button, press it and hold it.
5. Then connect the mirror to the computer with your other hand.
6. The firmware will start to download. You can now release the button.
7. Now you wait until complete and reboot(s) complete.
--------------------------------------------------------------------------------------------
Additional/Optional:
Not promoting anything, but kinda am. I get nothing in return for advising to use of any tools. This one here has helped me more than i can explain and was created by an OG of XDA, Koushik Dutta, aka. Koush. He is most famous for his work with Clockwork-mod. Show him some support if you like his work.
Tool to control pretty much any android device from your computer: Vysor
https://www.vysor.io
Here is a video showing you how to use the program. It is done with a Firestick, but once I was setup it just found the mirror itself once I plugged it in as well as my cell phone:
--------------------------------------------------------------------------------------------
Now that your bootloader is unlocked and your system is up to date, you may want to customize things a bit as most on XDA do. This is super new to me, like only 2 days working on this mirror.... I did however find a legit app, through playstore, to customize your home screen to not look like so tacky/boring. The app is called Car Launcher. There is a free version and a paid one. Paid version unlocks so much customization. I recommend installing the free version and testing it out. If all works, then the paid version is the way to go. I know the paid works very well with the above firmware. I have tested it quite extensively and so far found only one hick-up. Here are the links.
Recommended Home replacement: Free
Car Launcher Free
PRO Version is much better: cost $4.99
Car Launcher Pro
Whatever you do, don’t use program brightness settings in the themes or Car Launcher. Use the device’s settings.
Good place for some cool backgrounds I found for my Caddy that has other vehicle designs is: www.el-tony.com
Credit goes to a few places:
Iamrance.asa Bootloader Unlock
Hovatek Bootloader Unlock
Troypoint Vysor Setup
4PDA Threads
SPD Research Tool Guide

Saved for updates and customizations

Mod edit - translated by https://www.deepl.com/translator:
Hi I have a device szkj d 30 10 inch android 8.1 mirror that reboots all the time and goes into recovery on retry!Even if I do the reset it gets stuck in the same position.How do I do the data factory reset if it is stuck and won't turn off!!!!
VNDITORE Amazon says motherboard is broken!!!!
***************************
Ciao io ho un dispositivo szkj d 30 10 pollici android 8.1 mirror che si riavvia in continuazione e va in recovery su riprova!Anche se faccio il reset si blocca nella stessa posizione.Come faccio a fare il data factory reset se è bloccato e non si spegne!!!!
Spoiler
VNDITORE Amazon dice che si è rotta la scheda madre!!!!

Hello @po8pimp. Thank you very much for this tutorial, it is very useful. Hopefully someone can make a custom rom for these mirror.
I have a similar mirror, i think from HGDO brand, 4GB RAM 32Gb ROM with the firmware QC_1126bit_M5_1126_media_sleep_2020112517
Can I use your method and install that firmware?
In other hand I cant logout a google account from the mirror. Do you know how to delete and account from it?
Thank you

cregi said:
Hello @po8pimp. Thank you very much for this tutorial, it is very useful. Hopefully someone can make a custom rom for these mirror.
I have a similar mirror, i think from HGDO brand, 4GB RAM 32Gb ROM with the firmware QC_1126bit_M5_1126_media_sleep_2020112517
Can I use your method and install that firmware?
In other hand I cant logout a google account from the mirror. Do you know how to delete and account from it?
Thank you
Click to expand...
Click to collapse
I will have to check on the firmware ability. As far as the google account logout, you will more than likely have to factory reset the device.

cregi said:
Hello @po8pimp. Thank you very much for this tutorial, it is very useful. Hopefully someone can make a custom rom for these mirror.
I have a similar mirror, i think from HGDO brand, 4GB RAM 32Gb ROM with the firmware QC_1126bit_M5_1126_media_sleep_2020112517
Can I use your method and install that firmware?
In other hand I cant logout a google account from the mirror. Do you know how to delete and account from it?
Thank you
Click to expand...
Click to collapse
Phisung Z66 и клоны - Смарт-зеркало заднего вида - 4PDA
Phisung Z66 и клоны - Смарт-зеркало заднего вида, [Автомобиль][Зеркало][Видеорегистратор][Android]
4pda.to
This is the forum you would want to find your firmware for your device in. I recommend if you don't know Russian to get a browser with add on support to translate the pages for you. I use Firefox and Translate web pages extension which works really well.

hi i have this mirror following the guide, "./adb device" command list the device, but i can't get it to go into fastboot mode with "./adb reboot bootloader" command ...is there another method using combination of buttons?