{
"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"
}
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Link Download Rom Fastboot Images : Huawei2_NXG46W_Global_4G.zip
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press.
Step 1: Unlock the Bootloader
1.) On command prompt mode, type this command:
Code:
fastboot oem unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 2 : Flashing
While on Fastboot mode, type this on lenh.bat prompt one at a time:
Code:
fastboot flash bootloader bootloader.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
• If you want to Lock Bootloader to enable the logo when you see the annoying warning when unlocking bootloader, then typing:
Code:
fastboot oem lock
• Restart the machine
Code:
fastboot reboot
--- > and then go to recovery and do a wipe data / factory reset.
Congrats! Your done! :highfive:
Link tinhte.vn : https://tinhte.vn/threads/huong-dan-up-rom-quoc-te-cho-huawei-watch-2-noi-dia.2695788/
Group Facebook Hội SmartWatch Việt Nam : https://www.facebook.com/groups/smartwachvietnam/
CadBuRy.VN said:
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Link Download Rom Fastboot Images : Huawei2_NXG46W_Global_4G.zip
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press.
Step 1: Unlock the Bootloader
1.) On command prompt mode, type this command:
Code:
fastboot oem unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 2 : Flashing
While on Fastboot mode, type this on lenh.bat prompt one at a time:
Code:
fastboot flash bootloader bootloader.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
• If you want to Lock Bootloader to enable the logo when you see the annoying warning when unlocking bootloader, then typing:
Code:
fastboot oem lock
• Restart the machine
Code:
fastboot reboot
--- > and then go to recovery and do a wipe data / factory reset.
Congrats! Your done! :highfive:
Link tinhte.vn : https://tinhte.vn/threads/huong-dan-up-rom-quoc-te-cho-huawei-watch-2-noi-dia.2695788/
Group Facebook Hội SmartWatch Việt Nam : https://www.facebook.com/groups/smartwachvietnam/
Click to expand...
Click to collapse
hello,
that is exactly the same process I already posted, except probably for firmware number.
do you have link for Huawei Watch 2 Sport Non 4G ??? can you find it and post it?
thanks and regards
I wonder have you backup your chinese version system dump?
I just finding for PinYin intpu method which include in chinese version.
giangishanghai said:
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Link Download Rom Fastboot Images : Huawei2_NXG46W_Global_4G.zip
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press.
Step 1: Unlock the Bootloader
1.) On command prompt mode, type this command:
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 2 : Flashing
While on Fastboot mode, type this on lenh.bat prompt one at a time:
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata.img
• If you want to Lock Bootloader to enable the logo when you see the annoying warning when unlocking bootloader, then typing:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
• If you want to Lock Bootloader to enable the logo when you see the annoying warning when unlocking bootloader, then typing:
fastboot oem lock
• Restart the machine
hello,
that is exactly the same process I already posted, except probably for firmware number.
do you have link for Huawei Watch 2 Sport Non 4G ??? can you find it and post it?
thanks and regards
Click to expand...
Click to collapse
what is the difference between the chinses rom and the international rom? I've got a chinese rom watch, and I use it in Austria. Thank you.
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
wzhy said:
I wonder have you backup your chinese version system dump?
I just finding for PinYin intpu method which include in chinese version.
Click to expand...
Click to collapse
Is that possible to install a Pinyin input when installing the international rom?
DaNiEl4W said:
what is the difference between the chinses rom and the international rom? I've got a chinese rom watch, and I use it in Austria. Thank you.
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
Is that possible to install a Pinyin input when installing the international rom?
Click to expand...
Click to collapse
main differences are leanguage (of course) and google packages.
about pinyin I have never tried, maybe possible, you have to have an apk able to add pinyin into phones and see of you can install it into watch via adb command.
regards
DaNiEl4W said:
what is the difference between the chinses rom and the international rom? I've got a chinese rom watch, and I use it in Austria. Thank you.
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
Is that possible to install a Pinyin input when installing the international rom?
Click to expand...
Click to collapse
Yes, use adb install sideload the adb to watch and it will work.
I have install a pinyin input method from AW2.0 DP5 china edition. But I dont know if this app is upgraded when aw2.0 china edition is released.
Version number in DP5 china edition is: 1.0.1 100528. Find this by Settings-Personalization-Input methods-Google PinYin.
Version info is in the bottom, just swip down.
About China vrision
Thanks for the global ROM sharing! But I found that its difficulty using global vrision in China. Could you post a China ROM? Thank you again!
Eason C said:
Thanks for the global ROM sharing! But I found that its difficulty using global vrision in China. Could you post a China ROM? Thank you again!
Click to expand...
Click to collapse
hello,
why you find difficult to use HW global rom in China? I have global firmware in my HW 1st generation and except ok google it works perfectly + for example the help of watchmaker about faces that is impossible with chineese rom.
by the way, you can ask about chineese rom in another treath, this is for Global (more spec about 4G variant), better do not mix or it ill become a mess.
thanks a lot and regards
Thanks for the global ROM sharing,but my watch is the bluetooth version ,can you post the global bluetooth version?Thank you
DaNiEl4W said:
what is the difference between the chinses rom and the international rom? I've got a chinese rom watch, and I use it in Austria. Thank you.
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
Is that possible to install a Pinyin input when installing the international rom?
Click to expand...
Click to collapse
可以安装拼音输入法，当手机上安装了谷
Need a h China Version rom？ NLG47F
Need a h China Version rom？ NLG47F
Thank you for your amazing tuto ! worked perfectly for me
wrong message...
ak6102 said:
Need a h China Version rom？ NLG47F
Click to expand...
Click to collapse
Hello, could you please share your chinese rom? I want to flash back, thanks.
ak6102 said:
Need a h China Version rom？ NLG47F
Click to expand...
Click to collapse
PM me with your phone model 4G/BT and current ROM I can help you getting China version back
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Bricked my watch ><
I accidentally flashed these images on my Huawei Watch 2 BT LEO-B09/LEO-BX9 Chinese version instead of the ones from the other thread and now my whole watch won't even boot. I think it's called hard bricked, I try to press the power button but the screen remains black and when I plug in the watch to a computer I get an error saying that Windows does not recognize that device. I know I did a stupid thing but is there anyway to fix this?
sorayahya said:
I accidentally flashed these images on my Huawei Watch 2 BT LEO-B09/LEO-BX9 Chinese version instead of the ones from the other thread and now my whole watch won't even boot. I think it's called hard bricked, I try to press the power button but the screen remains black and when I plug in the watch to a computer I get an error saying that Windows does not recognize that device. I know I did a stupid thing but is there anyway to fix this?
Click to expand...
Click to collapse
hello,
it is not "big" stupid thing.... time ago was stated 4G and BT versions firmware was the same....... in fact not.
btw, there is nothing to do, you have to send back to HW service for replacement, it happened to me.
If you are in China this will take one week, other places I dont know.
regards
sorayahya said:
I accidentally flashed these images on my Huawei Watch 2 BT LEO-B09/LEO-BX9 Chinese version instead of the ones from the other thread and now my whole watch won't even boot. I think it's called hard bricked, I try to press the power button but the screen remains black and when I plug in the watch to a computer I get an error saying that Windows does not recognize that device. I know I did a stupid thing but is there anyway to fix this?
Click to expand...
Click to collapse
A member Acberry tried the same and was able to boot the BX9 normally (with prompt of no SIM). Did you tried removing the watch from the charging dock and press and hold the power button? It does not bring up anything on screen?
mcdull said:
A member Acberry tried the same and was able to boot the BX9 normally (with prompt of no SIM). Did you tried removing the watch from the charging dock and press and hold the power button? It does not bring up anything on screen?
Click to expand...
Click to collapse
I tried everything, I tried turning it on with and without the charging, I tried holding the power buttom for 30 second, I tried to plug it in with the PC and run fastboot, but the screen doesn't even turn on. nothing.
sorayahya said:
I tried everything, I tried turning it on with and without the charging, I tried holding the power buttom for 30 second, I tried to plug it in with the PC and run fastboot, but the screen doesn't even turn on. nothing.
Click to expand...
Click to collapse
See if @dr_chch can get you the full rom recovery software. The extracted image for BX9 is provided from him. In the example of B09s, the executable file is actually used by Huawei to recover the watch, although it cannot be run successfully (with error). BX9 could be another story. I guess it should be used together with another low level qualcomm driver to sideload the image including the bootloader.
Related
{
"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
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
Hello !
Just acquired an HTC U12+ in replacement for my brave Oneplus One, that i kept updated to Android Pie. Compare to my old One, HTC didn't make it easy to make mod...
As I hate all these stupid UI, i want AOSP without the google app as much as i can, so i wanted to try the Android Pie GSI "FLOSS", hoping it works great.
Anyway since yesterday i spend a lot of time trying to install TWRP on my U12, and fastboot and adb make me crazy. First i unlock the bootloader with the describe procedure, it works fine, i use fastboot from offical repo of ubuntu 18.10. I red all the thread and understand that i must boot first twrp and then flash it with the installer. The problem is fastboot and adb are not working after unlocking the bootloader. I am using the USB type C to type A cable from HTC.
My phone was with firmware 1.25 with june patch when i bought it. So i download the right version of TWRP. Fastboot is not working anymore and i get an error of "protocol". Then i see in the FAQ that you need to use the last version from google. This fastboot didn't worked much more, "too many links" error or similar. I tried different usb port of my pc, it seems the usb 3.0 and 3.1 do this, with usb 2.0 error is different, it said "downloading boot.img" and nothing happens. Then i tried to update to 1.30, but fastboot is not working more. I tried in windows, i install the htc driver and use the latest fastboot, same errors. Also tried another pc running ubuntu 18.04 without success.
Right now "fastboot devices" find the U12 properly but all command show error, and "adb devices" shows nothing in download mode.
I guess the problem come from the usb cable ? I live in a small town in the middle of nowhere and have no type c cable, so i ordered two new cable among other accessories, i hope they works but i won't have them before two week probably more (revolution in coming in France ).
But what i don't understand, if it's a problem with the cable, why fastboot was working when i do the "fastboot flash unlocktoken Unlock_code.bin" to unlock the bootloader, and then it refuse to work ?
Regards !
When you do fastboot devices and U12 shows up then you should be alright.
To boot TWRP you must be in boot loader, NOT download mode.
fastboot boot twp.img
It has worked for me just fine on windows, macOS, and Ubuntu
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Use
fastboot --version
To see what fastboot version you have. Latest should be 28.0.1
Hello,
Thank you for your answer. I know the difference between the fastboot and download mode, i try everything but the problem is always the same. My fastboot is the latest from the xda topic :
./fastboot --version
fastboot version 28.0.1-4986621
For example i just try again, it's connected to the usb 2.0 port of my pc, i'm in fastboot (recovery) and not download mode :
./fastboot devices
FA8731F01429 fastboot
./fastboot boot twrp-3.2.3-2-ime.img
Downloading 'boot.img' ... and nothing happens
If it's connected to usb 3.0 or 3.1, get the "too many links" error.
Edit : another exemple, if i use the fastboot from kubuntu 18.10 repo :
[email protected]:~$ fastboot devices
FA8731F01429 fastboot
[email protected]:~$ fastboot boot twrp-3.2.3-2-ime.img
< waiting for any device >
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
That is a strange issue.
Several users on the Pixel 2 forum had the same issue and a different cable worked. I don't know how a cable only works with certain commands.
Looks like you're doing it right however. Unfortunately it might simply be a cable.
Maybe try flashing a boot.img that already has twrp in it so you can just use the bootloader recovery option?
---------- Post added at 08:35 AM ---------- Previous post was at 08:27 AM ----------
k_l_o said:
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
Click to expand...
Click to collapse
You should be on this screen.
BOOTLOADER
{
"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"
}
Yes i am to this screen when i use fastboot. Not have the same info in the screen though. I cannot make a photo now so i will just write what i see :
press volume key etc...
Fastboot Mode (in red)
PRODUCT_NAME - HTC_Phone
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - FA8731F01429
SECURE BOOT - PRODUCTION
SECURE STATE - S-ON
DEVICE STATE - UNLOCKED (U) (in red)
KEY STATE - NONE
*** Software status: Modified *** (in red)
Guess i will try again when i'll get the other cable, but it's very strange indeed.
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
k_l_o said:
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
Click to expand...
Click to collapse
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
ghstmm said:
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
Click to expand...
Click to collapse
I brought up the HTC Sync Manager only for the purpose of installing the drivers. I uninstall the Sync Manager portion of the package afterwards. Anyway, try this link for the latest HTC Driver:
http://www.mediafire.com/file/g4r62oz2v9b1x0q/HTC-Mobile-Driver-v4.17.0.001.zip
I was already in v4.17.0.001. Guess i have to wait now for the new cable, hope it solve the problem...
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Alan-B said:
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Click to expand...
Click to collapse
I don't have any problem with adb, it works always without issues. Yeah sometimes it's difficult to boot into bootloader, but I use adb for that also
Sent from my HTC U12+ using XDA Labs
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
master66 said:
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
Click to expand...
Click to collapse
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
ghstmm said:
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
Click to expand...
Click to collapse
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
DeeZZ_NuuZZ said:
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
ghstmm said:
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
Click to expand...
Click to collapse
No not bricked, but you can't sideload an img. Just get it back to sdcard and flash it from there, also for GSI it is better to wipe from stock recovery
Sent from my HTC U12+ using XDA Labs
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
ghstmm said:
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
Click to expand...
Click to collapse
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
mauiblue said:
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Ok i get it Short timing indeed.
Edit : I finally install the latest android 9 pie gsi. It's working great and i love the floss version, but their is a few bugs : no brightness adjustment, localisation not working and few screen bugs (icon mostly).
Anyway thanks you all for your help
Hello,
My OnePlus is stuck in a bootloop. I can turn it off but if I turn it on, it displays the first screen with the logo "+1" then the second screen with the circles that turn and there they freeze. The circles do not move any more then it restarts and it starts again until the battery runs out.
I tried this awesome tuto called "How to unroot OnePlus 6 in bootloop / hard-brick" but i'm stuck in thé step 5. The phone restarts, I first screen "1+" then the screen with the H2OS logo and then it remains frozen on the logo and the phone restarts and so on. I have tried to retake everything from step 1 but I am still stuck in step 5.
Do you have any idea ?
Thanks,
Don't know that tutorial, but i think it's only a softbrick, have you tried to format data from recovery? Stock one or TWRP doesn't matter, and what you was doing before the phone goes bricked?
Hi !
Sorry I can't post URL of this tuto because i'm new here and there is a restriction. It's this one :
{
"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"
}
Before this bug I was just playing with a stupid filter in Snapchat then white screen and bootloop.
I've already tried the followings things (without success) :
Wipe data and cache
- reset system setting
- wipe cache => aucun effet
- erase everything (music, pics, etc)
Advanced
- Reboot to fastboot
- Reboot to recovery
I'm lost...
Oli78 said:
Hi !
Sorry I can't post URL of this tuto because i'm new here and there is a restriction. It's this one :
Before this bug I was just playing with a stupid filter in Snapchat then white screen and bootloop.
I've already tried the followings things (without success) :
Wipe data and cache
- reset system setting
- wipe cache => aucun effet
- erase everything (music, pics, etc)
Advanced
- Reboot to fastboot
- Reboot to recovery
I'm lost...
Click to expand...
Click to collapse
Are you encrypted/decrypted twrp/root unlocked bootloader? One or all of them? Tell me more
Sent from my OnePlus7T using XDA Labs
have u try to flash the stock oxygenos firmware zip ? u can use both stock and twrp recovery. what's ur bootloader state ? locked or unlocked ?
Hitman478™ said:
Are you encrypted/decrypted twrp/root unlocked bootloader? One or all of them? Tell me more
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
I'm sorry I don't know what is "TWRP". But i saw there is wrote : "bootlocker : device state locked". Is it helpful for you ?
Azhar_Fahry said:
have u try to flash the stock oxygenos firmware zip ? u can use both stock and twrp recovery. what's ur bootloader state ? locked or unlocked ?
Click to expand...
Click to collapse
I just follow this tutorial https://www.youtube.com/watch?v=yKfT7UsWQAk and i'm stuck in the step 5 like you can see here https://www.youtube.com/watch?v=4gMUUZ2CVDM
My bootloader state is locked.
You need to try a format from stock recovery but you'll lose your data
Hitman478™ said:
You need to try a format from stock recovery but you'll lose your data
Click to expand...
Click to collapse
Luckily I made a backup a week before so it's not a problem to lose my data. How can I format from stock recovery ?
Is there a tutorial?
I tried to unlock my bootloader.
Download & Update OnePlus 6 Drivers => ok
Download & Update Fastboot and ADB Binaries/Drivers => ok
Open a command prompt window
fastboot devices => ok
fastboot oem unlock => flashing unlock is not allowed
Try the MSM unbrick tool, i don't think you can unlock the bootloader in this state since you didn't enable it in the dev options
Oli78 said:
Hello,
My OnePlus is stuck in a bootloop. I can turn it off but if I turn it on, it displays the first screen with the logo "+1" then the second screen with the circles that turn and there they freeze. The circles do not move any more then it restarts and it starts again until the battery runs out.
Thanks,
Click to expand...
Click to collapse
With the phone turned off. Hold the volume down button and then push the power button for 10-15 seconds and see if phone reboots to recovery or fastboot. If you can get the phone boot to fastboot, follow the simple guide at the link below. Be patient and follow the steps. This process will erase all the data but you said you already have a copy of the back up data. Download on your PC/laptop the correct version, most current stable OS is 9.0.9. Download will be in the zip format. Unzip the file. While phone in the fastboot mode, connect to your PC. In the unzipped folder, click on FlashAll.bat file and wait. You may get some failure messages, just igore them. Eventually the phone will reboot as a brand new phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Goodluck.
Chinaroad said:
Try the MSM unbrick tool, i don't think you can unlock the bootloader in this state since you didn't enable it in the dev options
Click to expand...
Click to collapse
I already try this solution but i'm still in bootloop.
Gr8man001 said:
With the phone turned off. Hold the volume down button and then push the power button for 10-15 seconds and see if phone reboots to recovery or fastboot. If you can get the phone boot to fastboot, follow the simple guide at the link below. Be patient and follow the steps. This process will erase all the data but you said you already have a copy of the back up data. Download on your PC/laptop the correct version, most current stable OS is 9.0.9. Download will be in the zip format. Unzip the file. While phone in the fastboot mode, connect to your PC. In the unzipped folder, click on FlashAll.bat file and wait. You may get some failure messages, just igore them. Eventually the phone will reboot as a brand new phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Goodluck.
Click to expand...
Click to collapse
Thanks, I try that but there is a failure message "FAILED (remote: Flashing is not allowed in Lock State)" and the phone dit not reboot.
Turn off the phone.. Den press both volume up and power button for few sec.. It will boot into Fastboot.. Now connect to pc and then use Fastboot command to unlock your bootloader. Then use msmtool to install fresh stock rom.
HatRiGt said:
Turn off the phone.. Den press both volume up and power button for few sec.. It will boot into Fastboot.. Now connect to pc and then use Fastboot command to unlock your bootloader. Then use msmtool to install fresh stock rom.
Click to expand...
Click to collapse
I already did that and with this command (fastboot oem unlock) I get this error : flashing unlock is not allowed.
I guess I've to unlock my bootloader first but I don't know how to do that in hardbrick...
I am assuming that you have appropriate ONEplus driver installed?
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
Also are you using the command mentioned in my previous email from the downloaded zipped file. don't try to unlock. Simply try flashall.bat file in the fastboot mode.
Oli78 said:
Luckily I made a backup a week before so it's not a problem to lose my data. How can I format from stock recovery ?
Is there a tutorial?
Click to expand...
Click to collapse
boot into ur recovery, wipe data and flash this firmware. https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232 . i hope it works.
try this
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Gr8man001 said:
I am assuming that you have appropriate ONEplus driver installed?
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
Also are you using the command mentioned in my previous email from the downloaded zipped file. don't try to unlock. Simply try flashall.bat file in the fastboot mode.
Click to expand...
Click to collapse
Yes, i dit that :
reboot the phone in fastboot mode
download the OS 9.0.9
connect the phone to the PC (in USB)
in the previous zip folder, click on flash-all.bat
and see the capture below...
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