Related
i registered on htc dev website and followed all the instructions up to the point of getting the bootloader code from fastboot cmd, i then pasted the code in the box and hit submit then i got this error:
Unlocking Bootloader Failed!
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 122.
Error Reason: Email cannot be sent.
Do 1 thing.....
Copy that code and first paste it into notepad without any spaces....
Once done copy the same code from notepad and paste it into the required field of htc dev. Com
Hope this will work 4 u
Sent from my HTC Wildfire S A510e using xda premium
Don't copy any of the "INFO" Bits... just the code.
Hi !
You installed EMUI 9 beta from @a1Pha wonderful guide, but you are not happy of the result ?
Then this guide is for you !
Disclaimer: I am not responsible for your bricked devices. This has only been tested by a few people with Windows 10 and EML-L29 C432. Other models may or may not work. Please don't use that method if you don't know how to recover your phone from a bricked or semi-bricked state.
Before starting, you need to ensure 3 things.
Your phone's bootloader needs to be unlocked
Your phone's should also be FRP unlocked
You need to remove any type of password, fingerprint or pin from your phone. (TWRP data decryption only works when the phone has no lockscreen security)
If all is OK, then we are good to go !
Steps:
- Download the DOWNGRADE TOOL v0.4.
- Download the matching firmware bundle for your device. (Under EMUI 8 you need 3 files: update.zip, update_full_XXX_hw_eu.zip, and update_data_full_public.zip)
- Extract the DOWNGRADE TOOL somewhere on your PC.
- Put your firmware bundle in the ZIPS-HERE folder (don't forget to rename them, the script will tell you how to do so).
- Plug your phone, enable ADB (Android Debug Mode) and launch the FLASH.bat script.
- Follow all the steps carefully ! Everything should be OK if you do so.
- YOU WILL NEED TO FACTORY RESET !
Compatibility:
I can guarantee this script is working under Huawei P20 and P20 Pro (thanks to @MrDanMak for testing it) . I don't know about other devices.
Massive thanks to:
- @a1Pha
- @Atarii
- @ante0
- @dkionline
- @frantorresm5434
- laststandingdroid
- @mankindtw for the original NoCheck recovery
- @MrDanMak for testing this on his P20 Pro.
- @Pretoriano80
- @shimp208 for the bundled minimal ADB + Fastboot
Getting the following errors when running the script:
adb: error: failed to copy 'ZIPS-HERE/update.zip' to '/data/update/HWOTA/': remote couldn't create file: Is a directory
ZIPS-HERE/update.zip: 0 files pushed. 20.9 MB/s (131056 bytes in 0.006s)
adb: error: failed to copy 'ZIPS-HERE/update_all_hw.zip' to '/data/update/HWOTA/': remote couldn't create file: Is a directory
ZIPS-HERE/update_all_hw.zip: 0 files pushed. 49.9 MB/s (262112 bytes in 0.005s)
adb: error: failed to copy 'ZIPS-HERE/update_data_public.zip' to '/data/update/HWOTA/': remote couldn't create file: Is a directory
ZIPS-HERE/update_data_public.zip: 0 files pushed. 49.9 MB/s (262112 bytes in 0.005s)
images/nocheck.img: 1 file pushed. 20.5 MB/s (26284032 bytes in 1.223s)
Any idea why I could be having this problem?
MrDanMak said:
Getting the following errors when running the script:
adb: error: failed to copy 'ZIPS-HERE/update.zip' to '/data/update/HWOTA/': remote couldn't create file: Is a directory
ZIPS-HERE/update.zip: 0 files pushed. 20.9 MB/s (131056 bytes in 0.006s)
adb: error: failed to copy 'ZIPS-HERE/update_all_hw.zip' to '/data/update/HWOTA/': remote couldn't create file: Is a directory
ZIPS-HERE/update_all_hw.zip: 0 files pushed. 49.9 MB/s (262112 bytes in 0.005s)
adb: error: failed to copy 'ZIPS-HERE/update_data_public.zip' to '/data/update/HWOTA/': remote couldn't create file: Is a directory
ZIPS-HERE/update_data_public.zip: 0 files pushed. 49.9 MB/s (262112 bytes in 0.005s)
images/nocheck.img: 1 file pushed. 20.5 MB/s (26284032 bytes in 1.223s)
Any idea why I could be having this problem?
Click to expand...
Click to collapse
Hello, I just updated my tool, please download it and try again, tell me if it fixes your issue.
Androlark said:
Hello, I just updated my tool, please download it and try again, tell me if it fixes your issue.
Click to expand...
Click to collapse
Issue is fixed but when I reboot to nocheck recovery it fails to install the update package unfortunately.
Will keep trying though just in case.
MrDanMak said:
Issue is fixed but when I reboot to nocheck recovery it fails to install the update package unfortunately.
Will keep trying though just in case.
Click to expand...
Click to collapse
My error ! I putted a letter in a file name which is not required here ! Sorry about that..
You can download again or just edit the 98th line of the FLASH.bat script (update_all_how.zip -> should be update_all_hw.zip)
Androlark said:
My error ! I putted a letter in a file name which is not required here ! Sorry about that..
You can download again or just edit the 98th line of the FLASH.bat script (update_all_how.zip -> should be update_all_hw.zip)
Click to expand...
Click to collapse
Script worked perfectly after the edit and my device is now back to stock 8.1
Just to confirm my device was a P20 Pro (L29-C432). So if anyone wants to know if it works on a P20 Pro as well the answer is yes.
Thanks for all your help!!
Do i need a root or umlocked bootloader?
and do you think I can use this method to upgrade my UK C782 branded phone from .120 to .152?
g_oral said:
Do i need a root or umlocked bootloader?
and do you think I can use this method to upgrade my UK C782 branded phone from .120 to .152?
Click to expand...
Click to collapse
You don't need root, because EMUI 9 was not supporting any root method. But yes, you need a unlocked bootloader. (It is written on the top of the post btw..)
Yes, you can use this method to upgrade your phone, it is planned to help downgrading your phone, but you can also us it to upgrade... (You need to upgrade from a EMUI 8 FW to another EMUI 8 FW)
Androlark said:
You don't need root, because EMUI 9 was not supporting any root method. But yes, you need a unlocked bootloader. (It is written on the top of the post btw..)
Yes, you can use this method to upgrade your phone, it is planned to help downgrading your phone, but you can also us it to upgrade... (You need to upgrade from a EMUI 8 FW to another EMUI 8 FW)
Click to expand...
Click to collapse
Just to confirm, unlocking FRP is as simple as selecting OEM unlock in the developer settings??
burgess_boy said:
Just to confirm, unlocking FRP is as simple as selecting OEM unlock in the developer settings??
Click to expand...
Click to collapse
Yep!
ante0 said:
Yep!
Click to expand...
Click to collapse
Sorry, but it is not for me.
You can't lock or unlock in developer settings.
You need an unlock code.
But this does not even work for me.
Everytime I unlock FRP in bootloader mode and phone resets in beta 9 it is locked again.
Orlando.Rodriguez said:
Sorry, but it is not for me.
You can't lock or unlock in developer settings.
You need an unlock code.
But this does not even work for me.
Everytime I unlock FRP in bootloader mode and phone resets in beta 9 it is locked again.
Click to expand...
Click to collapse
Oem unlock is required (Frp unlock in fastboot) to unlock the phone.
You will of course need the unlock code as well when unlocking in fastboot mode.
ante0 said:
Oem unlock is required (Frp unlock in fastboot) to unlock the phone.
You will of course need the unlock code as well when unlocking in fastboot mode.
Click to expand...
Click to collapse
I have the unlock code and yes, bootloader is unlocked.
But it reverses after every factory reset.
Orlando.Rodriguez said:
I have the unlock code and yes, bootloader is unlocked.
But it reverses after every factory reset.
Click to expand...
Click to collapse
Why are you using that?
Just tick the Oem unlock option in Settings > Developer options.
If OEM unlock is disabled in settings, and you unlock using frp-unlock command I would assume it's only temporary
I can't do anything
Orlando.Rodriguez said:
I can't do anything
Click to expand...
Click to collapse
Try connecting WiFi, wait 10 mins, then reboot and check if it can be enabled.
It says right there under it "connect to the Internet or contact your carrier.".
Maybe even try taking out SIM, reboot, put in, reboot, then check if it can be enabled.
ante0 said:
Try connecting WiFi, wait 10 mins, then reboot and check if it can be enabled.
It says right there under it "connect to the Internet or contact your carrier.".
Maybe even try taking out SIM, reboot, put in, reboot, then check if it can be enabled.
Click to expand...
Click to collapse
I'll try ?
---------- Post added at 06:32 PM ---------- Previous post was at 05:35 PM ----------
Nothing works for me. I guess it's because I upgraded to beta through funkyhuawei
Hi, as for the install script, I created a linux/mac version.
It works, as I've used it myself to downgrade my P20 pro.
So the bootloader relocks after rollback?
RazOne said:
So the bootloader relocks after rollback?
Click to expand...
Click to collapse
No
As it's Android One device, it probably uses Google OTA service. If you would be able to provide me with system fingerprint, there's a chance for me to get full OTA link to start up the development for this and possibly other devices.
How to do it?
Install Terminal Emulator from Google Play, type:
Code:
getprop | grep fingerprint
and click enter.
if you want to provide more of usable data, use just
Code:
getprop
Thread will be updated with links once somebody helps. Or will be closed in case of no solution.
pastebin.com/wWpYHPHd
WmcB said:
pastebin.com/wWpYHPHd
Click to expand...
Click to collapse
No update available yet, so I can't check currently if there will be full OTA zips. If you still have the access to this device, try getting kdz download link or file itself (via the official LG tool). Or post/*pm* the IMEI (it may be without last three numbers, because I don't need your own, but just any of them to simulate LG Bridge request). Basically, the only way to get fw now is to get the kdz. Aand last question: is G7 One bootloader unlockable? From what I saw in getprop, there was a prop suggesting that OEM unlock switch is blocked.
j1505243 said:
No update available yet, so I can't check currently if there will be full OTA zips. If you still have the access to this device, try getting kdz download link or file itself (via the official LG tool). Or post/*pm* the IMEI (it may be without last three numbers, because I don't need your own, but just any of them to simulate LG Bridge request). Basically, the only way to get fw now is to get the kdz. Aand last question: is G7 One bootloader unlockable? From what I saw in getprop, there was a prop suggesting that OEM unlock switch is blocked.
Click to expand...
Click to collapse
After enabling developer mode, I am given the option of unlocking the bootloader from the developer menu. I am able to enable it but I didn't test it.
The config [sys.oem_unlock_allowed]: [1] is now set
I tried using LG Mobile Support tool. Software is up to date, so I went into Upgrade Recovery menu option. It did a few checks and failed after "analyzing software version."
The error was "problem with communication between cell phone and PC." Maybe LG's support tool isnt updated to handle the phone yet.
I'll PM you an IMEI
WmcB said:
After enabling developer mode, I am given the option of unlocking the bootloader from the developer menu. I am able to enable it but I didn't test it.
The config [sys.oem_unlock_allowed]: [1] is now set
I tried using LG Mobile Support tool. Software is up to date, so I went into Upgrade Recovery menu option. It did a few checks and failed after "analyzing software version."
The error was "problem with communication between cell phone and PC." Maybe LG's support tool isnt updated to handle the phone yet.
I'll PM you an IMEI
Click to expand...
Click to collapse
Ok, managed to decrypt LGMST thingies. So, it seems that LG just didn't push any kdz yet. But the good news is that we should be able to fetch them as soon as they do it. In the free time, see if you can extract the Camera app from the device. Through Solid Explorer, for example.
j1505243 said:
Ok, managed to decrypt LGMST thingies. So, it seems that LG just didn't push any kdz yet. But the good news is that we should be able to fetch them as soon as they do it. In the free time, see if you can extract the Camera app from the device. Through Solid Explorer, for example.
Click to expand...
Click to collapse
Camera apk extracted
drive.google.com/drive/folders/1aRgQAUxq_aqtU7kOeXd3A1OD_dR6oUDo
WmcB said:
After enabling developer mode, I am given the option of unlocking the bootloader from the developer menu. I am able to enable it but I didn't test it.
The config [sys.oem_unlock_allowed]: [1] is now set
Click to expand...
Click to collapse
Did you end up unlocking the bootloader? I am considering getting this phone tomorrow but only if the bootloader can be unlocked.
jfd3220 said:
Did you end up unlocking the bootloader? I am considering getting this phone tomorrow but only if the bootloader can be unlocked.
Click to expand...
Click to collapse
I may not be savvy enough to test if it is unlocked. I ran "adb reboot bootloader" but it rebooted normally. Is there another way I can check?
WmcB said:
I may not be savvy enough to test if it is unlocked. I ran "adb reboot bootloader" but it rebooted normally. Is there another way I can check?
Click to expand...
Click to collapse
Maybe try
Code:
fastboot oem device-info
Bootloader unlocked from dev options.
I recall seeing other phones with that option that did not actually have unlockable bootloaders.
Pr0l1f1k said:
Bootloader unlocked from dev options.
Click to expand...
Click to collapse
Thanks but that's just a setting that you have to change to enable the unlocking. You also have to enable USB Debugging in Developer Options, then reboot into fastboot as instructed here.
Enable USB-Debugging on your phone. USB-Debugging is required for the commands “adb” and “fastboot” to work. To enable USB-Debugging, go to Settings > About phone > Software info and tap Build number 7 times. Return to the previous screen, select Developer options and enable USB-Debugging.
Enable OEM unlock on your phone. Activating the "Enable OEM unlock" is necessary for the bootloader unlock. To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock.
You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window. Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window.
Are you able to retrieve the Device ID?
EDIT: Never mind. I just got this from LG Support Chat: "As per our MC Specialists, unlocking the bootloader on G7 One is not possible anymore."
jfd3220 said:
EDIT: Never mind. I just got this from LG Support Chat: "As per our MC Specialists, unlocking the bootloader on G7 One is not possible anymore."
Click to expand...
Click to collapse
I can confirm that this phone will not enter fastboot with the "adb reboot bootloader" command. It just reboots to system like normal.
snardos said:
I can confirm that this phone will not enter fastboot with the "adb reboot bootloader" command. It just reboots to system like normal.
Click to expand...
Click to collapse
So is that it? Will we ever be able to unlock the bootloader.
j1505243 said:
As it's Android One device, it probably uses Google OTA service. If you would be able to provide me with system fingerprint, there's a chance for me to get full OTA link to start up the development for this and possibly other devices.
How to do it?
Install Terminal Emulator from Google Play, type:
Code:
getprop | grep fingerprint
and click enter.
if you want to provide more of usable data, use just
Code:
getprop
Thread will be updated with links once somebody helps. Or will be closed in case of no solution.
Click to expand...
Click to collapse
Hi ! I will receive my LG G7 One this week and I'm fully commited to help you get the files / test things on my device.
Please let me know, if can be any help !
Simshady97 said:
As it's Android One device, it probably uses Google OTA service. If you would be able to provide me with system fingerprint, there's a chance for me to get full OTA link to start up the development for this and possibly other devices.
How to do it?
Install Terminal Emulator from Google Play, type: and click enter.
if you want to provide more of usable data, use just
Hi ! I will receive my LG G7 One this week and I'm fully commited to help you get the files / test things on my device.
Please let me know, if can be any help !
Click to expand...
Click to collapse
Nah, we are seemingly clogged, until kdz start to distribute. For now, you may just capture the OTA link in adb.
Heads up for anyone interested in this phone: it is available on ebay. I've looked a few times over the last week, and there have been several of them up for grabs for a reasonable price. It's also available on Canadian Amazon (amazon.ca).
If anyone is wondering what frequency bands the phone will use, let me know and I can call around and ask some place that sells this phone.
Ok
Sent from my LGE LG-Q710AL using XDA Labs
fingerprint
O:/ $ getprop | grep fingerprint
[ro.boot.vendor.lge.fingerprint_sensor]: [1]
[ro.bootimage.build.fingerprint]: [lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/191471306ed81:user/release-keys]
[ro.build.fingerprint]: [lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/191471306ed81:user/release-keys]
[ro.vendor.build.fingerprint]: [lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/191471306ed81:user/release-keys]
:/ $
Can someone please share the stock camera APK of this phone?
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
Can we unlock the bootloader using bugjager app or do we really need a pc?
You can Use Bugjaegar App. It is simple to use
Mod edit - translated by https://translate.google.com/:
Couldn't unlock bootloader with bugjaeger!
*****************
Bootloader kilidi açamadım bugjaeger ile!
[email protected] said:
Mod edit - translated by https://translate.google.com/:
Couldn't unlock bootloader with bugjaeger!
*****************
Bootloader kilidi açamadım bugjaeger ile!
Click to expand...
Click to collapse
Mod edit - translated by https://translate.google.com/:
how to do?
*****************
nasıl yapılır?
[email protected] said:
Mod edit - translated by https://translate.google.com/:
Couldn't unlock bootloader with bugjaeger!
*****************
Bootloader kilidi açamadım bugjaeger ile!
Click to expand...
Click to collapse
[email protected] said:
Mod edit - translated by https://translate.google.com/:
how to do?
*****************
nasıl yapılır?
Click to expand...
Click to collapse
Please use the English language! [Lütfen İngilizce dilini kullanın!]
XDA Forum Rules (excerpt):
...
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
...
Click to expand...
Click to collapse
yametekudasai said:
Can we unlock the bootloader using bugjager app or do we really need a pc?
Click to expand...
Click to collapse
I used the app to unlock my Motorola oem unlock it works
Absolutely yes you can use bugjaeger instead of a PC to unlock and run adb and fast boot commands. I highly recommending spending the money for the premium bugjaeger app
Sativa33 said:
I used the app to unlock my Motorola oem unlock it works
Click to expand...
Click to collapse
I think it's work for auther phone .but what about xaiome phones
Pls reply
yametekudasai said:
Can we unlock the bootloader using bugjager app or do we really need a pc?
Click to expand...
Click to collapse
Install in depth test app for your realme device
1.Turn on OEM unlocking your
phone(target device)
2.Then turn on USB debugging(target device)
3.Enable OTG connection (bugjaeger device)
4.power off device(by using in depth test app)
6.check if device is connected or not(Make sure the OTG side is on bugjaeger device)
7.enter command "fastboot devices" (it will show all the devices connected)
8.enter command "fastboot flashing unlock" (this will unlock your phone's bootloaded ofc)
9.check your phone screen and do what it's asking for confirmation...mostly it's pressing volume up button
10.when it's done....enter the command "fastboot reboot" this will reboot your phone
11.voilah! you unlocked your device's bootloader without a pc
Not work
Reaper7531 said:
Install in depth test app for your realme device
1.Turn on OEM unlocking your
phone(target device)
2.Then turn on USB debugging(target device)
3.Enable OTG connection (bugjaeger device)
4.power off device(by using in depth test app)
6.check if device is connected or not(Make sure the OTG side is on bugjaeger device)
7.enter command "fastboot devices" (it will show all the devices connected)
8.enter command "fastboot flashing unlock" (this will unlock your phone's bootloaded ofc)
9.check your phone screen and do what it's asking for confirmation...mostly it's pressing volume up button
10.when it's done....enter the command "fastboot reboot" this will reboot your phone
11.voilah! you unlocked your device's bootloader without a pc
Click to expand...
Click to collapse