{
"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"
}
The European H850 can now be officially unlocked through LG's developer unlock program page.
Yes, only the European version. Your H850 is from the Middle East? Won't work. You have an AT&T G5? That's not an H850, move along.
LG Developer Unlock Site Here
Prerequisites:
1. European LG G5 H850
2. Computer w/ADB & Fastboot. ADB/Fastboot for Windows here. ADB/Fastboot for Linux/OS X here.
3. Basic knowledge of ADB, Fastboot and Windows command prompt or Linux/OS X terminal.
4. Device IMEI. This 15-digit code can be found on your box, the back of the phone or by dialing *#06#
5. LG developer account (free, click here then click sign in at the top of the page to make an account.)
Directions:
LG's official bootloader unlock directions can be found in the big link at the top of the page..
but I've still rewritten the steps out below while adding some for root and TWRP.
1. 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.
2. 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.
3. Open CommandPrompt or Terminal and enter the following ADB command to reboot into the bootloader:
Code:
adb reboot bootloader
If ADB is not detecting your device try switching your phone's USB mode from Charging to MTP or PTP.
4. Once in the bootloader, use the following fastboot command to obtain Device ID:
Code:
fastboot oem device-id
Fastboot command will return a string. This is the Device ID which is needed to generate your unique unlock key.
Example :
Code:
$ fastboot oem device-id
(bootloader)-----------------------------------------------------------------
(bootloader) Device-ID
(bootloader) CD58B679A38D6B613ED518F37A05E013
(bootloader) F93190BD558261DBBC5584E8EF8789B1
(bootloader)-----------------------------------------------------------------
To generate your unlock key, you will need to paste together the 2 lines of output into one continuous string without "(bootloader)" or white spaces. In the example above, the Device ID would be:
CD58B679A38D6B613ED518F37A05E013F93190BD558261DBBC5584E8EF8789B1
5. Copy Device ID and IMEI into the LG developers unlock site and hit the confirm button. In a few moments the unlock.bin will be emailed to you. Download unlock.bin to computer.
6. While the phone is still in fastboot enter the following command to unlock the bootloader:
This will unlock your phone AND factory reset your device wiping all data!
Code:
fastboot flash unlock unlock.bin
7. You can now reboot the phone and boot into your unlocked device! Enter:
Code:
fastboot reboot
8. Want root or TWRP? Before moving forward I suggest getting a microSD card and putting the SuperSu 2.65 zip on there. Do not set the external SD up as adoptive storage. Download this TWRP image too.
Reboot back into the bootloader (you'll have to first re-enable USB debugging):
Code:
adb reboot bootloader
9. Flash TWRP:
Code:
fastboot flash recovery twrp-3.0.2-0-h850.img
For TWRP to "stick" you must first boot directly into TWRP and not back into Android, until after flashing the SuperSU zip.
After flashing TWRP unplug the USB cable and pull the battery. Plug battery back in then boot into recovery which should hopefully load TWRP.
To boot into recovery:
a. Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.
b. As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
c. Keep holding until you see the Factory Reset screen. Click thru the factory reset screens.. Yes.. Yes...
10. You will not be able to decrypt your internal data while in TWRP (unless performing a full /data wipe in TWRP and you will lose encryption!) but you can manually mount your external SD card to view the SuperSu zip. Feel free to back up first.. but otherwise.. time to install SuperSu. Click the Install button and navigate to the external_sd, select the SuperSu zip then swipe to install. Now you're rooted and TWRP'd! Reboot into system...
Have fun and be careful.
FAQ:
Q: I have an H850Q from Israel.. can I unlock the bootloader?
A: No, this official unlock program is ONLY for the H850 model for countries in Europe just like LG did for the LG G4.
But... for about a 10 day span last year G4 devices from SE Asia worked with the official site and users received unlock.bin files. :good:
Q: Will more devices be added?
A: While there is no "official" word.. most likely no. Unless another mistake happens where another region's H850's are allowed for a week.
Other than then EU H850 and possibly the T-Mobile H830... no other variants have a shot at being bootloader unlocked officially.
Q: I can't get my phone to show up with ADB or Fastboot, watdo?
A: Make sure USB debugging is enabled and try changing the phones USB modes.. from maybe charging to MTP.. or MTP to PTP.
Make sure drivers are installed if using Windows. Learn2Computer.
Q: Where can I get drivers and things?
A: A good start is my G5 Info thread found here. Google and this very website are good places to search as well.
Q: What happens to warranty if I unlock or root?
A: YMMV I suppose. The official LG site claims that warranty is void if damage is caused by the unlock. Not sure how they could prove such things. I thought there was some EU law that gave everyone warranty coverage even if unlocking the phone. Not sure if that is enforced or even still valid at this time... maybe someone knows for sure?
Q: Can I re-lock the bootloader?
LG does not support re-locking the bootloader... so once unlocked you remain unlocked.
Thanks to @Loggsie for the heads up... the previous statement above is confirmed not true.
It IS possible to re-lock the bootloader with the the command: fastboot oem lock
I wrote a bit more about it in this post HERE... and in the post under that.. @wolfgart shows off some examples.
DO NOT re-lock the bootloader if you have a modified boot/system img... restore them to stock first or you will not be able to boot into android after the lock and need to flash a KDZ in download mode.
Q: So many words... yudodat?
A: Here is a video on how to unlock the G4... up until the 6minute mark it is step-by-step 100% the same as G5. Only slight difference is when you get to the TWRP/root steps. https://www.youtube.com/watch?v=O64GfQORCaE
Click to expand...
Click to collapse
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Feel free to contribute to my LG G5 fund...
click my name at the top of any post and hit donate or click here.
Awesome!
This is Fire Baby ! ??
Can't wait to get my Hands on my H850... My first LG Device ?
Thanks for sharing Prime!
As for G4, will this void the warranty?
Envoyé de mon SM-G925F en utilisant Tapatalk
@misteurz
Once your phone is unlocked, it will no longer be covered by LG warranty.
Thanks for your tutorial!
I'm having a problem with the last step "fastboot boot twrp-3.0.2-0-h850.img"
downloading 'boot.img'...
OKAY [ 0.412s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.454s
Click to expand...
Click to collapse
Any ideas?
kerniger said:
Thanks for your tutorial!
I'm having a problem with the last step "fastboot boot twrp-3.0.2-0-h850.img"
Any ideas?
Click to expand...
Click to collapse
odd.. not sure where it's getting "boot.img" from.
try: fastboot flash recovery twrp-3.0.2-0-h850.img
if flash and boot dont work then sounds like fastboot is broken and LG is really screwing with all of us. :laugh:
Tried that, but entering Recovery shows red triange error...
Sent from my LG-H850 using XDA-Developers mobile app
kerniger said:
Tried that, but entering Recovery shows red triange error...
Sent from my LG-H850 using XDA-Developers mobile app
Click to expand...
Click to collapse
are you booting back into system first after flashing it by any chance? because if so, booting into system runs a patch to restore stock recovery. so after flashing twrp while in the bootloader/fastboot it'd be easiest to unplug the usb cable... pull the battery then put it back in... then boot into recovery. hopefully TWRP works like that. if so, then you'd just need to flash the supersu zip for root.
autoprime said:
are you booting back into system first after flashing it by any chance? because if so, booting into system runs a patch to restore stock recovery. so after flashing twrp while in the bootloader/fastboot it'd be easiest to unplug the usb cable... pull the battery then put it back in... then boot into recovery. hopefully TWRP works like that. if so, then you'd just need to flash the supersu zip for root.
Click to expand...
Click to collapse
did work like a charm! Thanks!
kerniger said:
it doesn't boot into recovery with power+vol down, any other suggestion?
Thanks again for your help
Click to expand...
Click to collapse
check step #9 in the OP.. I have edited the TWRP/root steps to now use fastboot flash instead of fastboot boot.
After flashing and booting its stuck at loading as u can see at the picture
D:\android\sdk\platform-tools>fastboot flash revovery twrp-3.0.2-0-h850.zip
target reported max download size of 536870912 bytes
sending 'revovery' (16377 KB)...
OKAY [ 0.530s]
writing 'revovery'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.569s
What did i wrong?
STUPID me. i should use img not zip.....
ok still same error....
doncompadre said:
D:\android\sdk\platform-tools>fastboot flash revovery twrp-3.0.2-0-h850.zip
target reported max download size of 536870912 bytes
sending 'revovery' (16377 KB)...
OKAY [ 0.530s]
writing 'revovery'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.569s
What did i wrong?
STUPID me. i should use img not zip.....
ok still same error....
Click to expand...
Click to collapse
Check the command, maybe is because you wrote "revovery" again instead of "recovery"
What is the easiest way to backup and restore the apps&data before rooting?
Never had the situation that I used a phone before root was available
Helium backup is not working
Killua96 said:
Check the command, maybe is because you wrote "revovery" again instead of "recovery"
Click to expand...
Click to collapse
thanks man thats it... to blind to see
but now after flash twrp i cant come into it. after the step with 2 yes it reboots normal...
aehm2k5 said:
After flashing and booting its stuck at loading as u can see at the picture
Click to expand...
Click to collapse
i got the same now... how easy things goes on my old HTCs
aehm2k5 said:
After flashing and booting its stuck at loading as u can see at the picture
Click to expand...
Click to collapse
I have the same problem - recovery hangs on its splash screen
Horgul123 said:
What is the easiest way to backup and restore the apps&data before rooting?
Never had the situation that I used a phone before root was available
Helium backup is not working
Click to expand...
Click to collapse
Helium backup seemed to work fine for me. You could try LG Backup but i'm unsure if it backs up app data.
duckysempai said:
Helium backup seemed to work fine for me. You could try LG Backup but i'm unsure if it backs up app data.
Click to expand...
Click to collapse
Thanks for the hint. Will check it
okgnew said:
I have the same problem - recovery hangs on its splash screen
Click to expand...
Click to collapse
Same, knew it go smoothly :laugh:
aehm2k5 said:
After flashing and booting its stuck at loading as u can see at the picture
Click to expand...
Click to collapse
LBensley said:
Same, knew it go smoothly :laugh:
Click to expand...
Click to collapse
u mean now it goes ??? tell us what u did please
Related
Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.
Anybody?
{
"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"
}
I get this when I hit Apply Update and then use storage as option.
moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?
geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb
geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.
https://dl.twrp.me/cheryl
Razer Phone Install Instructions
Read these instructions and follow them carefully. Failure to do so may result in not being able to update the device in the future and there are no factory images available.
The Razer Phone uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. Unlike the Pixel devices, Razer has disabled fastboot boot so there is no way to temporarily boot TWRP to perform an installation.
Getting into fastboot mode or recovery on the Razer Phone requires plugging the device into a USB cable. I would recommend against flashing or performing recovery-related actions unless you have access to a USB cable and port so that you can get back into recovery should something go wrong. Power off the device. Hold volume up to get into recovery or volume down to get into fastboot mode. Plug the device in while holding the appropriate button and the device should boot to the mode you selected. If it boots up to the charging screen, try a different USB cable or port. Make sure you are able to boot the device to fastboot via USB cable before flashing anything.
We are going to use the other boot slot to flash the initial copy of TWRP and boot TWRP. To do this you will need to turn on developer options and enable USB debugging. You will also need to enable OEM unlocking and unlock the bootloader. I am not going to discuss how to get the proper drivers installed or assist you with doing these basic steps. There's tons of guides elsewhere for these items if you need it. I will say that unlocking the bootloader requires using fastboot flashing unlock instead of fastboot oem unlock. Once you have adb working, run this command:
adb shell getprop ro.boot.slot_suffix
It should say:
[ro.boot.slot_suffix]: [_a]
Or:
[ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this:
fastboot --set-active=_b
Or on slot B type this:
fastboot --set-active=_a
You should see something like this:
Setting current slot to 'a'...
OKAY [ 0.042s]
finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Your device should now boot into TWRP. From here, decrypt your device if needed at the password prompt. DO NOT swipe to allow modifications until after you make your initial backup; instead tap on the read-only button. Go to the reboot page and tap on the button at the bottom to switch back to the slot you were originally using. Go to the backup page in TWRP and back up Boot and System Image. It is HIGHLY recommended that you save this backup in a safe spot on your computer because you may need to restore it to take official OTA updates from Razer. Once you have finished making your backup, run this command:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
In TWRP, tap on Install and browse to the zip and install it. TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal, though with TWRP installed, you won't be able to take OTA updates without restoring the stock boot image.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel. ADB also does not work with the stock kernel which makes transferring files between your PC and the device when using the stock kernel a bit of a challenge. The TWRP bootable image does have working ADB though and you can copy files to a SD card or USB stick if needed.
Reserved!
Thanks you so much @Dees_Troy
Let development begin
Awesome work! :highfive:
Awesome! Now we just need to let the dev fun begin! BTW You Rox!
Edit: Im trying to do a full backup of the current state of my phone. went into TWRP and selected every partition and hit backup. Was flying along till it got to Data and it just stopped. No movement @ 40% for about 5 minutes so far Is it working for anyone else? does it just take insanely long with no percentage increase, or am I just being paranoid cause its my new phone lol
Edit 2: I just cancelled it and backed up everything but Data and it went fine, I'm now attempting to backup JUST Data.. Ill have to restore 2 backups seperately, but it appears to be working
Final Edit: All good.. not sure what happened the first backup but doing them seperately worked. Rooted with Magisk 15.1 and running beautifully! Gonna try out some root stuff like Xposed.. Thanks for all your hard work devs & testers!
@Dees_Troy Thanks for your work. Broken link https://github.com/TeamWin/android_device_razer_cheryl
Please update when you have time
Another thing in your instruction consider that on european razer phone the right command is this (I've found problem only for slot b in slot a work without -i 0x1532)
ffastboot -i 0x1532 flashing unlock
{
"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"
}
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
RicardoSal24 said:
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
Click to expand...
Click to collapse
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device work add -i 0x1532
raimondomartire said:
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device word add -i 0x1532
Click to expand...
Click to collapse
I would still get the message saying <waiting for any device>
RicardoSal24 said:
I would still get the message saying <waiting for any device>
Click to expand...
Click to collapse
Verify your driver in setting. You must add google driver
raimondomartire said:
Verify your driver in setting. You must add google driver
Click to expand...
Click to collapse
link please
RicardoSal24 said:
link please
Click to expand...
Click to collapse
https://developer.android.com/studio/run/win-usb.html
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
RicardoSal24 said:
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
Click to expand...
Click to collapse
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
raimondomartire said:
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
Click to expand...
Click to collapse
My problem is getting the drivers to work. I've tried Robin. That succeeded. But updating drivers in Device Manager doesn't work. It says there are no compatible drivers for the phone. And if I can't update drivers I can't get the phone to be recognized in Device Manager so adb can work
edit
DarkestSpawn said:
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
Click to expand...
Click to collapse
Try switching slots in Twrp then restart.
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Xshooter726 said:
Try switching slots in Twrp then restart.
Click to expand...
Click to collapse
No problem also for me. I can share my slot b image
---------- Post added at 02:59 PM ---------- Previous post was at 02:44 PM ----------
Firebuster said:
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Click to expand...
Click to collapse
Try to boot in bootloader mode from twrp and after write fastboot reboot
This May Work With Other Devices As Well.
Prerequisites:
Starting from Bootloader Locked Stock Verizon.
CrossFlash to G710ULM11g.kdz: LG G710U | LG G7 ThinQ | Version: G710ULM11g_01_NAO_US_OP_1112 | Firmware for Region: BPT from UNITED STATES - Lg-firmwares.com (lg-firmwares.com)
Fastboot works on the G710ULM11g.kdz no need to erase laf.imgs.
See the 2 links below for crossflashing threads.
(There are 2 ways to crossflash).
1. Use LGUP, Partition DL and Refurbish is you want the kdz on both a and b slots: https://mega.nz/#!kCpHBaia!xZmico6MYL1T07ffuc8z6cCbs5oU4pKEz5VG-AwfvV0
2. Power Shell Command line Crossflashing thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Files required to unlock bootloader while crossflashed to the ULM11g.kdz V35eng file and firehose file for Qfil. https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Zip contains Stock G710VM21b stock boot_a and boot_b img and Magisk patched boot_a and boot_b imgs. https://www.androidfilehost.com/?w=files&flid=322268
Latest Verizon kdz LG G710VM | LG G7 ThinQ | Version: G710VM21b_04_0812 | Firmware for Region: VRZ from UNITED STATES - Lg-firmwares.com (lg-firmwares.com)
NOTE: Some links are from other helpful threads so thank whoever wrote them.
To successfully unlock the bootloader while on the crossflashed 11g,
Setup Device then go into Developer options and Enable the OEM Unlock toggle and enable usb debugging in the phone.
Now Let's Begin:
1. Switching the phone to EDL modeopen device manager):
Turn off the phone, then hold the vol- and power buttons together and repeatedly press the vol+ button until you see device in device manager as "Qualcomm HS-USB QDLoader 9008". then release buttons. If you don't succeed at first keep trying.
2. Using QFIL:
Install the QPST package, launch Qfil, in the program window select:
(1) Select port to which the device is connected
(2) Storage type UFS
(3) select build type: Flat
(4) Select programmer: prog_ufs_firehose_Sdm845_lge.elf
Click to expand...
Click to collapse
{
"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"
}
3. Load v35eng.img to abl_a partition:
in the upper left menu, select Tools, then partition manager , look for abl_a in the window that opens , Right click abl_a, select manage partition data, then use the V35eng.img overwrite the abl_a with load image.
4. Reboot into Fastboot to Unlock the bootloader:
Leave EDL mode by holding the volume down and power for about 10 seconds. Phone will restart. Turn off phone disconnect usb and hold vol- and plug in usb. (phone should boot into fastboot like the picture).
Now we need platform tools unpacked to any folder convenient for you, launch the shell by pressing the shift + right mouse button and choosing to open the power shell window here .
Use the command : "fastboot oem unlock" without quotes
Use the command: "fastboot reboot" without quotes
That's Everything the bootloader is unlocked.
Crossflash back to Stock G710VM21b.kdz and root or crossflash to android 10 kdz to install custom roms.
To Root stock 21b use EDL mode for Qfil to load the magisk patched 21b boot.imgs to boot_a and boot_b reboot and install magisk.apk then it should update to latest magisk zip.
***NOTE***
Only use this part of the guide if you are relocking bootloader. This locking bootloader procedure may work for other devices use at your own risk.
***Do not uninstall magisk with the magisk uninstall button. Just go into download mode and crossflash to ULM11g. If you use the uninstall button in magisk manager you will brick your device.**
To relock bootloader:
Cross Flash back to ULM11G, setup phone, enable Developer options, enable USB debugging. (Enable OEM unlock) should be greyed out don't worry).
Platform-tools and issue powershell commands:
1. PS C:\Program Files\platform-tools> adb devices
List of devices attached
LMG710ULM******** device
2. PS C:\Program Files\platform-tools> adb reboot bootloader
3. PS C:\Program Files\platform-tools> fastboot oem lock
(bootloader) Erasing userdata and cache OKAY [ 0.492s]
Finished. Total time: 0.592s
4. PS C:\Program Files\platform-tools> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
To confirm locked bootloader:
Enable developer options again and you will see (Enable OEM Unlock) Unchecked.
***Profit Bootloader is locked***[/QUOTE]
I just cross flashed and rooted the G710ULM20d for my LG710VM Verizon. This method should work on any phone that is cross flashed. I only used Qfil no twrp.
Can someone write this up in a more noob friendly way?
Is 'adb debugging in ULM11g', the same as 'USB debugging' under developer options?
My phone currently has Oreo (8.1) installed and is model no. LMG710ULM
Dishe said:
Can someone write this up in a more noob friendly way?
Click to expand...
Click to collapse
Yeah, totally lost me at
When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away (if it don't work just let the phone boot up and go into adb and command prompt and type fastboot reboot bootloader.
2. When you've entered fastboot, execute this command:
Click to expand...
Click to collapse
I guess we're supposed to have ADB cmd window open on the PC, similar to 3:30 of the following video:
/watch?v=wp4Rb0INxvU
OP then mentions the following
Once bootloader is unlocked you can cross flash back to Verizon Pie kdz. Make the backup for whatever slot your using a or b.
Click to expand...
Click to collapse
This doesn't make any sense, since he didn't revert to Oreo, to install the v35eng.img
Edit: It seems he's referring to the original abl_a/abl_b files, this post talks about distinguishing the 2
3. Installed magisk manager and patched boot_a.
Click to expand...
Click to collapse
It seems Magisk apk needs to be executed directly on the phone, then it'll do it's thing from there
/watch?v=m4f21ZCGJuk
Edit: here are my images of the steps to patch boot_a and boot_b
imgur.com/a/E4Abu4t
You must manually navigate to the directory with your LG, press and hold then select 'share' file, so it can appear in Windows explorer; filenames will be the same so you have to do this twice.
File size of each file went from 64 MB to 23.1 MB
After patching boot_a and boot_b with QFIL, the red question mark will change into a green check mark, when you boot up again.
But yeah, none of this makes any sense without some sort of image or video. Thank you for the guide though.
There are 5 main files that should be backed up 'just in case'
i.imgur.com/uqk2Cwb.png
Edit: consider backing up abl_b as well.
The phone's on a GSM network. I as able to uninstall facebook directly from the phone, and then use ADB shell to remove the app manager/system facebook files as well.
paxar331 said:
Is 'adb debugging in ULM11g', the same as 'USB debugging' under developer options?
My phone currently has Oreo (8.1) installed and is model no. LMG710ULM
Click to expand...
Click to collapse
Yes you need it enabled to use adb.
Just to let everyone know, once you upgrade to Pie, QFIL can not be used to place files onto the partition, but to read or erase.
paxar331 said:
Just to let everyone know, once you upgrade to Pie, QFIL can not be used to place files onto the partition, but to read or erase.
Click to expand...
Click to collapse
Sorry to disagree with you but you are incorrect. Qfil can load any file you want as well as restore a backup file. Boot_a, abl_a, laf_a, and so on.
ik this phone is so cool
---------- Post added at 04:57 AM ---------- Previous post was at 04:52 AM ----------
netookska05 said:
Sorry to disagree with you but you are incorrect. Qfil can load any file you want as well as restore a backup file. Boot_a, abl_a, laf_a, and so on.
Click to expand...
Click to collapse
I am so lost on this....
(Don't mean to rude as I understand a lot of work put into the community is voluntary and kindness, but I got to this thread from a comment on the previous one and still not understanding).
Unlocking the Verizon LG G710VM bootloader with QFIL may work with other devices
edit
nik322 said:
(Don't mean to rude as I understand a lot of work put into the community is voluntary and kindness, but I got to this thread from a comment on the previous one and still not understanding).
Click to expand...
Click to collapse
What's going on?
It doesn't work to lock the bootloader, I get red case
HimikoMw said:
It doesn't work to lock the bootloader, I get red case
Click to expand...
Click to collapse
What version of phone do you have? (Dual SIM what?)
Did you flash the Android 8 ulm11g.kdz and boot into fastboot and enter the fasboot OEM lock command and fastboot reboot?
netookska05 said:
What version of phone do you have? (Dual SIM what?)
Did you flash the Android 8 ulm11g.kdz and boot into fastboot and enter the fasboot OEM lock command and fastboot reboot?
Click to expand...
Click to collapse
It's the G710EM Latin American version, flash the kdz G70ULM11g and reboot to fastboot with the command (adb reboot bootloader), from there once in fastboot mode, execute the command (fastboot oem lock), and then (fastboot reboot), and it showed me red case
HimikoMw said:
It's the G710EM Latin American version, flash the kdz G70ULM11g and reboot to fastboot with the command (adb reboot bootloader), from there once in fastboot mode, execute the command (fastboot oem lock), and then (fastboot reboot), and it showed me red case
Click to expand...
Click to collapse
How did you unlock bootloader?
Was it with the official way generating your unlock key?
netookska05 said:
How did you unlock bootloader?
Was it with the official way generating your unlock key?
Click to expand...
Click to collapse
for that model there is no official unlocking, so I unlocked it by the unlock they published first.
flashing the G71011g and installing the v35 abl(https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568), that was the method I used that time, it was the only way there was.
HimikoMw said:
for that model there is no official unlocking, so I unlocked it by the unlock they published first.
flashing the G71011g and installing the v35 abl(https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568), that was the method I used that time, it was the only way there was.
Click to expand...
Click to collapse
Then flashing back to the 11g and enabling debugging should have worked. Once you issued all commands it should have rebooted minus the bootloader unlock screen you get booting up and then went back into phone into developer options and turned off OEM unlock switch.
netookska05 said:
Then flashing back to the 11g and enabling debugging should have worked. Once you issued all commands it should have rebooted minus the bootloader unlock screen you get booting up and then went back into phone into developer options and turned off OEM unlock switch.
Click to expand...
Click to collapse
yes but after executing all the commands, it doesn't start me and only remains in red case.
My theory is that in some G7 when flashing a kdz the safetynet passes both in (ctsProfile, as in basicIntegrity), which allows the bootloader to lock again, in my case when flashing either any KDZ, only passes me (basicIntegryty), which causes the bootloader does not lock properly, and causes the red case, that's what I think, I've tried several ways to lock the bootloader but always leads me to red case.
HimikoMw said:
yes but after executing all the commands, it doesn't start me and only remains in red case.
My theory is that in some G7 when flashing a kdz the safetynet passes both in (ctsProfile, as in basicIntegrity), which allows the bootloader to lock again, in my case when flashing either any KDZ, only passes me (basicIntegryty), which causes the bootloader does not lock properly, and causes the red case, that's what I think, I've tried several ways to lock the bootloader but always leads me to red case.
Click to expand...
Click to collapse
When you crossflaahed to 11g did you use command line or lgup partition do? Are you stuck at the red case now?
netookska05 said:
When you crossflaahed to 11g did you use command line or lgup partition do? Are you stuck at the red case now?
Click to expand...
Click to collapse
Try this guide for your red case problem. https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
HOW TO FLASH IN EMUI10 VIA SOFTWARE TESTPOINT
1. Enter USB Update Mode
On older EMUI versions you would use vol up + vol down + power. This has changed now.
On EMUI 10, enter eRecovery by holding volume up and power until you see the Huawei logo appear. Then let go and press volume up again and wait for eRecovery screen. Then press USB Update and it should show an update screen at 5% complete.
2. Enable Software Testpoint
Using the update.app of the same firmware that you are currently on, turn factory mode on via whichever app you happen to be using. Personally I am using Octoplus Huawei Tool (paid), but you could also use Chimera (paid), Sigmakey (paid) and many others. There are free methods too by manual flashing in Linux but it is too involved to discuss here.
Output from Octoplus looks like:
Code:
Starting ON/OFF Factory Mode
Selected phone model: CLT-L29
To Enable Factory mode put the phone in Upgrade mode and connect USB cable!
To Disable Factory mode connect the phone in Factory mode or Factory Fastboot mode!
Checking the existence of the auto firmware file...
Selected firmware file file: C:/Users/srefs/Documents/HiSuite/ROM/Charlotte-L29C10.0.0.171_Firmware_EMUI10.0.0_05015AMH/Software/dload/UPDATE_BASE.APP
Performing ON Factory Mode operation...
Checking firmware package type
Searching device in Upgrade mode...
Connecting to phone..
Phone connect successfully!
Writing firmware partitions...
Writing SHA256RSA partition...
Writing CRC partition...
Writing BASE_VERLIST partition...
Writing BASE_VER partition...
Writing PACKAGE_TYPE partition...
Writing HISIUFS_GPT partition...
Writing XLOADER partition...
ON/OFF Factory Mode done.
Performed by 1.2.3 Software version.
You should now see this in Device Manager on Windows, which means you successfully entered testpoint mode without disassembling your hardware. You can now literally do anything to your hardware.
{
"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"
}
3. Write factory fastboot.
If you are using Octoplus, you just go to the Update backup tab, make sure 'Update OEMInfo' is NOT ticked and click Update. As soon as you see fastboot is flashed, you can cancel. For free method, see: Downgrade/Unbrick Huawei device (if other methods doesn't work) | XDA Developers Forums (xda-developers.com)
4. Flash whatever you want
Now you can flash whatever the heck you want over EMUI 10, such as a kernel. You will also need to disable verified boot so you can load unsigned images without getting the dreaded "your device has failed verification". Have fun!
Code:
PS C:\adb> .\fastboot flash kernel .\KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.183s]
writing 'kernel'...
OKAY [ 0.275s]
finished. total time: 0.462s
PS C:\adb> .\fastboot flash kernel .\image-new.img
target reported max download size of 471859200 bytes
sending 'kernel' (20664 KB)...
OKAY [ 0.155s]
writing 'kernel'...
OKAY [ 0.081s]
finished. total time: 0.241s
PS C:\adb> .\fastboot oem get-build-number
...
(bootloader) :CLT-L29 10.0.0.171(C432E3R1P3)
OKAY [ 0.008s]
finished. total time: 0.011s
PS C:\adb> .\fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
5. Turn off Software Testpoint
Turn factory mode off in same software you used in step 2.
Code:
Performing OFF Factory Mode operation...
Searching Fastboot devices...
Found a fastboot device:
Device Model: CLT-L29
System: CLT-L29 10.0.0.171(C432E3R1P3)
...
Writing secure data...
Rebooting device...
ON/OFF Factory Mode done.
Performed by 1.2.3 Software version.
Now either you did the right thing by this stage and it boots up nicely... or you screwed up something and it doesn't boot up. As long as you can get to eRecovery again, you can let Huawei automatically recover. Note: If recovery fails the first time complaining about 'authorization', just run recover again and it will work.
Could that mean Possible Custom Roms in the Future?
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Me i
xsacha said:
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Click to expand...
Click to collapse
I Wonder myself aswell. The P20 Pro would be even better with Custom Firmware.
The Development should be there in my Opinion.
Good Phone, lag of Development.
By the way, you should be able to flash an older bootloader (but keep EMUI 10) using this method and then your bootloader will be unlocked again. Or, if not already unlocked, you can unlock with a key as per old way.
Advantages of bootloader unlock:
Flash kernels/roms without third-party software.
Disadvantages:
Have to root and use magisk hide for Google Pay to work again.
So, with this method, you can literally flash treble roms? Also, can we just the usb cable provided instead of a dongle for the paid programs?
xsacha said:
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Click to expand...
Click to collapse
Because without a bootloader unlock method, nobody bothered to keep maintaning the phone
AnotyClaws said:
So, with this method, you can literally flash treble roms? Also, can we just the usb cable provided instead of a dongle for the paid programs?
Click to expand...
Click to collapse
Dongle? I'm using the digital licence and it's just a key you paste in. No dongles required.
Is the same possible for honor 9 lite, lld-l31, EMUI 9.1 too? And how to make this free in linux?
sergeyzap said:
Is the same possible for honor 9 lite, lld-l31, EMUI 9.1 too? And how to make this free in linux?
Click to expand...
Click to collapse
Linux method requires you to open up your device, from what i see above. Shame that i don't have cash to buy the software required to root my phone.
Awesome there's some roms we can flash already?
Hi, does anyone know how to retrieve saved notes from the Huawei phone’s in-built note after a factory reset, without having it backed up in huawei’s cloud? Please help! Much appreciated
Nwl295 said:
Hi, does anyone know how to retrieve saved notes from the Huawei phone’s in-built note after a factory reset, without having it backed up in huawei’s cloud? Please help! Much appreciated
Click to expand...
Click to collapse
You can't. I'm sorry
I actually wonder, by "Flash anything" you mean i can just flash TWRP and, from there, do everything i want?
AnotyClaws said:
I actually wonder, by "Flash anything" you mean i can just flash TWRP and, from there, do everything i want?
Click to expand...
Click to collapse
@xsacha tell us more
Sorry to budge in, but Octoplus does not detect my phone at all, regardless of HiSuite version installed, reboots.
One weird thing I noticed is that even though I have USB debugging turned on and accept/approve the connection, HiSuite prompts me to approve the connection to my PC again while in USB update mode.
Any help is highly appreciated.
Edit: This is what it sees attached.
Found COM ports:
1: COM12 HUAWEI Mobile Connect - Fake Acm Interface
2: COM13 DBAdapter Reserved Interface
3: COM14 Android Adapter PCUI
this is great !
please can you share a simple how-to document when you have a valid ROM [e.g. TWRP]
i would like to flash my own p20 pro and dont have the skilset yet :-/
my p20pro is now wide open after battery change, and I wonder if it is possible to unlock bootloader by grounding test pin? Are there any good instructions?
xsacha said:
HOW TO FLASH IN EMUI10 VIA SOFTWARE TESTPOINT
[...]
4. Flash whatever you want
Now you can flash whatever the heck you want over EMUI 10, such as a kernel. You will also need to disable verified boot so you can load unsigned images without getting the dreaded "your device has failed verification". Have fun!
[...]
Click to expand...
Click to collapse
Hello dear xsache. I'm playing around with my P20 Pro since yesterday morning and I fked up.
I used DC Phoenix which can also set phone into Software TestPoint mode which is a great thing.
But... I'm now stuck exactly on that Device Verification, and I cant flash new Firmware because CURVER can't be flashed. I'm now wondering how I can deactivate Device Verification.
I can get into TestPoint Mode + Fastboot (with temp. unlocked bootloader), and I can get into Regular Fastboot (with locked bootloader).
I would like to run TWRP and install LineAgeOS, but I cant start TWRP out of TestPoint Mode.
I already ordered OctoPlus licence, but maybe you can give me a hint on how to deactivate verification.
Thx.
Update: With OctoPlus I managed to fully flash EMUI 8. Verification Message is gone.
But still no TWRP
I can get into Testpoint mode and Flash to recovery_ramdisk. Then get out of Testpoint Mode and phone reboots normally. Then shutdown. If I try Vol Down + Power I get into Fastboot, if I try Vol UP + Power I get into Huawei eRecovery...
If I go to fastboot mode and type "fastboot reboot recovery" it gets me into Huawei eRecovery too.
Do I need to flash another Partition? Or are changes reverted after I get out of Testpoint Mode?
UPDATE2:
FKIN HELL! FK HUAWEI!
I managed to boot into TWRP.
In DC Phoenix I went into Testpoint mode, temporarily unlocked bootloader, then:
fastboot flash erecovery_ramdisk twrp-3.5.0_9-0-charlotte.img (make sure its *e*recovery)
Then.... started holding Vol UP + Power, in DC Phoenix Disables TestPointed and holded the buttons all the time.
It then went into fastboot and then into ... TWRP!
Unfortunately, TWRP was not able to provide mounted partitions to windows and fastboot commands didnt work. But I was able to adb push the zip to /storage.
When I tried to install, I got following error:
huawei.verify_vendor_build_id() failed to read
current vendor build id: -2
updater process ended with ERROR: 7
Fking Huawei all over the place....
Update3:
Changed updater-script in LineAge Zip. remove first 3 assert lines... hehe xd
Successfully flashed.
It could have been so nice.... tried to reboot but it always went to TWRP. Not able to boot System.... :/
Gonna Flash EMUI 9 and Try again.
And then EMUI10 and Try again.
And then Give up and burn that fking phone.
Final(?) Update:
Phone Dead. Looks like I flashed a Bad FW.
(1) Verification failed msg back.
(2) eRecovery destroyed (recovery image load failed)
(3) Bootloader Locked
(4) FRP Locked, so no bootloader unlock
I then have thrown the phone out of the window.
OK, unfortunately that was just in my imagination.
I opened up the phone and used hardwaretestpoint, got into fastboot with DC Phoenix and was able to flash another firmware...
I think LineAge OS like it is (Install Script) wont work with termporary unlocked bootloader.
It looks like TWRP does some stuff it needs an unlocked bootloader for.
So we will have to wait until there is a working method.
BTW, Ministry of Solutions really offers CLT-L29 Bootloader unlock codes now. But it seems to doesnt work with every model. He was on my PC yesterday for hours trying to do so but the found Code didnt work. It was the second phone (P20 Pro) that didnt work for him. With some others he was successful. So there might be some hope for some people out there. He refunded my $15 same day even after I told him he could keep it.
To be continued...
Is it possible on Emui10 to just flash Magisk to get root and not go through all the hell posted above?
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it.
Currently with many trial and error I got LiR-ROM to boot.
The first step is to unlock the Bootloader so I thought I will share the process here.
Your data will be deleted while unlocking, try it at your own risk.
Unlock Bootloader manually
Requirement: PC with ADB Fastboot
1. Go to Settings -> System -> About Phone, tab on it until developer settings are enabled.
2. Go to Developer Settings and enable "USB Debugging" and "OEM Unlocking".
3. Open Console and enter "adb devices". Allow USB-Debugging if tablets asks.
4. Enter command "adb reboot bootloader".
5. Write down the serial number shown on the bootloader screen
You can either get the unlock image via this link "http://cdn.zui.lenovomm.com/developer/tabletboot/[your sn number]/sn.img" or via the webseite
5. Go to the ZUI Unlock Website and request the unlock image
{
"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"
}
6. You should get a mail where you can download a file called "sn.img".
7. Flash the image with fastboot "fastboot flash unlock sn.img"
8. Enter command "fastboot oem unlock-go", bootloader will unlock now.
9. Restart with "fastboot reboot".
Done, your bootloader should be unlocked now.
Lock and Unlock Bootloader with Batchscript
I recently found a batch script for lenovo devices in an chinese forum and translated it.
It's easy and convenient to use. For unlocking you still need the sn.img from the ZUI Unlock Website.
Download BatchScript
Thanks a lot for your contribution! Mine was unlocked when I received it but it's good to see some guides here.
What is the opposite process, to close the bootloader? Does Widevine L1 recover after closing the bootloader? In the case of doing so, can the bootloader be opened again?
@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.
Tropaion said:
@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.
Click to expand...
Click to collapse
Thank you very much, I hope you can install a custom rom and this tablet will not be forgotten, since it is one of the most powerful compact tablets.
@sakun-ice I got LineageOS to run on it today, but it still has 2-3 bugs.
Helloi received one unlocked with a globaoe fw without ota's and i flashed the cn one and took the boot.ipg and patched it with pagisk for root and when flashing it via fastboot the device reboots to fastboot everytipe 1nd had to reflash the fw via edl , i did flashed vbmeta img with the known command o disable verification but no success same thing again. Can anyone plz tell me how to root that crap , it was intended to root use only and took over xiaomi pad pro just because the xiaomi needs 7 days of waiting before unlocking , plz help guys .thx so much i can buy a couple beers for the helper
I'm able to flash back to China stock rom but i can't lock the bootloader.
i have placed the sn.img in both the batchscript folder and platform tools
Tried the batch script :
"
Please select your device status:
1. Fully booted
2. Fastboot mode
Status: 2
Start locking bootloader, don't disconnect device from PC!
FAILED (remote: Command not supported in default implementation)
Finished. Total time: 0.016s
FAILED (remote: Unrecognized command flashing lock)
Finished. Total time: -0.000s
If prompt says "OKAY", locking was successfull.
Use the volume keys to select "LOCK BOOTLOADER", press power key to confirm.
Done!
Press any key to continue . . .
"
Powershell :
"
PS C:\Users\weeteck\Downloads\platform-tools_r31.0.3-windows\platform-tools> ./fastboot flash lock sn.img
Sending 'lock' (5 KB) OKAY [ 0.000s]
Writing 'lock' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
"
@zeroflame15 Did install the driver correctly? For locking you don't need the sn.img, only for unlocking. And did you use the LockBootloader Script?
hmm..i'm not sure if i install the driver correctly. what should be shown in device manager? i did follow PHRS guide and installed the ADB driver but there is this !Android under Other Devices.
Any other driver that i need to install?
And should i be in bootloader mode or fastboot mode to run the command? I run the command at fastboot moder i will get the error above. If i run at bootloader mode will stuckedd at <waiting for device>
@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.
Tropaion said:
@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.
Click to expand...
Click to collapse
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Try to connecting in another usb port with other usb cable.
zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Check out this post:
Post in thread '[Solved] Re-locking bootloader - no fastboot commands working' https://forum.xda-developers.com/t/...stboot-commands-working.4330019/post-85755663
It can be a bit tricky to get the commands working because it's not always clear if you need to be in fastboot or bootloader.
This worked for me:
Reboot to bootloader by entering "adb reboot bootloader"
After that try "fastboot flashing lock"
Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~
zeroflame15 said:
Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~
Click to expand...
Click to collapse
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks
fazioso said:
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks
Click to expand...
Click to collapse
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Saw some chinese video for those who wanted the rooted status and also to perform OTA updates, they are using magdisk to hide the root.
zeroflame15 said:
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Click to expand...
Click to collapse
thanks!
its seems most difficult to lock/unlock bootloader that flash rom.....
but you need ZUI Unlock Website also for lock? cause seems need only for unlock...right?
No need for lock. Like what others have mentioned. Just a single line command and it works as long you got the right drivers installed.
Tropaion said:
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
5. Go to the ZUI Unlock Website and request the unlock image
View attachment 5432885
6. You should get a mail where you can download a file called "sn.img".
Click to expand...
Click to collapse
my friend ....i have a unlocked bootloader ,cause for now i have the fake global....want to change in china stock....
but i ask anyway to the zui unlock website the sn.img in case i need in future.....
just a question.... after many hours or days i will receive the sn.img file? pass 10 minutes and nothing yet