Database Info

Official LG G5 H850 Bootloader 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"
}
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

Stuck at fastboot (rooted) - Need help please

Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA

nipun1110 said:
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
Click to expand...
Click to collapse
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!

Gr8man001 said:
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Click to expand...
Click to collapse
Hello, thanks a lot for your prompt response. But it is showing this error.
{
"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"
}

nipun1110 said:
Hello, thanks a lot for your prompt response. But it is showing this error.
Click to expand...
Click to collapse
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.

maigre said:
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
Click to expand...
Click to collapse
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.

nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
That wasn't me. It was Gr8man001 that gave you the advice that worked.

nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
maigre said:
That wasn't me. It was Gr8man001 that gave you the advice that worked.
Click to expand...
Click to collapse
true command : '''' fastboot --set-active=a '''' is it?
For me not work... please help.
https://i.hizliresim.com/pbOkpJ.png

Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.

zulu657 said:
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure

szybki_ben said:
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
Click to expand...
Click to collapse
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.

zulu657 said:
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
Click to expand...
Click to collapse
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked

szybki_ben said:
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
Click to expand...
Click to collapse
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.

zulu657 said:
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
Click to expand...
Click to collapse
If you can boot into recovery then booting a fresh img is a good idea, good luck!

szybki_ben said:
If you can boot into recovery then booting a fresh img is a good idea, good luck!
Click to expand...
Click to collapse
Just tried that one -- No Cigar!!! I followed the instructions for installing recovery on a new install. It said to use the text: fastboot boot recoveryimgrecovery.img I had renamed the Blu-spark img to recovery.img. The result was: no file or directory with this name. I was in the folder with adb, fastboot, recovery.img and all the rest of the files for OP6.
There used to be a way to install twrp with adb if I recall, but I can't find it. I know it was for an earlier phone. I have had OnePlus phones from the first one.
Very frustrating!!! I hate to wipe the phone because this should be a simple thing. Of course those are the ones that really get you....

Hmmmm, evidently the command fastboot set active=a is not a command in adb v1.0.32. When I tried it, I got a list of the commands and that one isn't in it.
Trying to find a later version of adb without success.
There has to be a way to change the active partition without formatting the phone. The phone had the original OS and I upgraded to Experience when I got it and have been using it ever since. Experience should be on another partition, so if I can change partitions, I should be on the original OS.
Would that not be correct???

Android 10 update TWRP not booting

Fastboot Stuck as saying booting with logo. Any Solution?
Sent from my GM1911 using Tapatalk

Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?

I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens ?

equlizer said:
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
Click to expand...
Click to collapse
From 9
Sent from my GM1911 using Tapatalk

Jarek84 said:
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens [emoji29]
Click to expand...
Click to collapse
I got a solution
Twrp 3.3.1.65
Sent from my GM1911 using Tapatalk

Jarek84 said:
Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens
Click to expand...
Click to collapse
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).

First fastboot stucked
Second no partition found
{
"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"
}
Sent from my GM1911 using Tapatalk

You are not supposed to "flash" twrp through windows. Once you "boot" with windows, you install twrp through twrp.

redpoint73 said:
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
Click to expand...
Click to collapse
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.

Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.

links2586 said:
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997

hallo dare said:
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Click to expand...
Click to collapse
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!

hallo dare said:
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Click to expand...
Click to collapse
Can you cite anyone who flashed twrp from fastboot in op7p.
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
whisky_ said:
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
Click to expand...
Click to collapse
. Have you tried patching your own boot.img instead of flashing the one provided on the guide?

Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1

hallo dare said:
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
Click to expand...
Click to collapse
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.

branko.s67 said:
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
Click to expand...
Click to collapse
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash. It's not just a case of saying it cannot be flashed and covered the method in one sweeping statement. There is a method, but as we all know, this is not possible currently with Android 10

hallo dare said:
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash.
Click to expand...
Click to collapse
Once you have booted recovery, you are no longer in fastboot.
Just try a fastboot command while in TWRP, and see how that works for you.

redpoint73 said:
Once you have booted recovery, you are no longer in fastboot. Duh!!!!
Click to expand...
Click to collapse
Hold on a sec. If you are going to act in a childish manner how are we to discuss this properly.
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Your comment said that you couldn't flash twrp via fastboot and never could with this phone. That's half correct. What I'm saying is you can flash the .img file to access twrp before flashing the zip file on Android pie. Unfortunately that's not the case with Android 10.

hallo dare said:
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Click to expand...
Click to collapse
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Once you are booted to TWRP, you can than flash TWRP installer zip (not the TWRP img).
Just look at the post you quoted above in response #14.
This phone does not even have a recovery partition. Recovery resides on boot.img for this device due to A/B partition scheme.
My original statements hold as correct.

redpoint73 said:
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Just look at the post you quoted above in response #14.
This phone does not have a recovery partition. Recovery resides on boot.img for this device.
My original statements hold as correct.
Click to expand...
Click to collapse
O my God, that recognised contributor tag is going to your head.
The command with "boot" boots into TWRP recovery. The command with "flash", flashes the .img file in fastboot mode on Android pie.

stuck on boot loader - no fastboot - linux

Hi,
following the corresponding lineageos guide i executed from my linux machine
Code:
fastboot flash boot twrp.img
.
rebooting got me to the boot loader. i cannot get into fastboot. (nor anywhere else.)
neither via adb reboot fastboot nor volume down + power.
I cannot recall having experienced this before.
Any help to how I can get into fastboot?
Cheers!

inli said:
Hi,
following the corresponding lineageos guide i executed from my linux machine
Code:
fastboot flash boot twrp.img
.
rebooting got me to the boot loader. i cannot get into fastboot. (nor anywhere else.)
neither via adb reboot fastboot nor volume down + power.
I cannot recall having experienced this before.
Any help to how I can get into fastboot?
Cheers!
Click to expand...
Click to collapse
Fastboot boot TWRP.img

AndroidRooterKev said:
Fastboot boot TWRP.img
Click to expand...
Click to collapse
thanks, but unfortunately, I am not in fastboot mode - that's the problem.

inli said:
Hi,
following the corresponding lineageos guide i executed from my linux machine
Code:
fastboot flash boot twrp.img
.
rebooting got me to the boot loader. i cannot get into fastboot. (nor anywhere else.)
neither via adb reboot fastboot nor volume down + power.
I cannot recall having experienced this before.
Any help to how I can get into fastboot?
Cheers!
Click to expand...
Click to collapse
EDL way work try it.

inli said:
unfortunately, I am not in fastboot mode - that's the problem.
Click to expand...
Click to collapse
Bootloader = fastboot. Run fastboot devices. If you're device shows up, run the command I sent previously.

AndroidRooterKev said:
Bootloader = fastboot. Run fastboot devices. If you're device shows up, run the command I sent previously.
Click to expand...
Click to collapse
hm, ok. but. but
Code:
fastboot devices
(with sudo before) does not give me any device list. (as it should be doing)

superac11 said:
EDL way work try it.
Click to expand...
Click to collapse
On EDL I find eg https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
but the solution there presumes windows. I am on a linux machine.

AndroidRooterKev said:
Bootloader = fastboot. Run fastboot devices. If you're device shows up, run the command I sent previously.
Click to expand...
Click to collapse
the screen I get is the one saying "The boot loader is unlocked"...
{
"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"
}

inli said:
the screen I get is the one saying "The boot loader is unlocked"...
Click to expand...
Click to collapse
Ohhh! That's what you meant by "stuck in boot loader". Yeah fastboot won't work there. And you've tried vol down + power multiple times to get to the actual bootloader screen (where you can fastboot)?
Try forcing a shut down (vol up + power) and retry a few times. What were you doing before it got stuck on the boot loader is unlocked screen? You might just need to flash the stock boot.img but you need to try to get to the bootloader screen to run the fastboot command.
If all else fails, you'll have to use the MSM tool (which will wipe everything).
EDIT: Yeah MSM tool requires a windows machine. Not sure how to run it via Linux. Maybe there's a windows emulator out there that can run windows .exe files?

AndroidRooterKev said:
Ohhh! That's what you meant by "stuck in boot loader". Yeah fastboot won't work there. And you've tried vol down + power multiple times to get to the actual bootloader screen (where you can fastboot)?
Click to expand...
Click to collapse
yes, tried multiple times - and, no did not get to the actual bootloader.
AndroidRooterKev said:
What were you doing before it got stuck on the boot loader is unlocked screen? You might just need to flash the stock boot.img but you need to try to get to the bootloader screen to run the fastboot command.
Click to expand...
Click to collapse
i simply executed
Code:
sudo fastboot flash boot 'twrp-3.4.0-0-guacamole.img'
AndroidRooterKev said:
If all else fails, you'll have to use the MSM tool (which will wipe everything).
Click to expand...
Click to collapse
according to https://forum.xda-developers.com/on...to-restore-t4078827/post82210187#post82210187 it seems I need to find a window computer to run this.

inli said:
yes, tried multiple times - and, no did not get to the actual bootloader.
i simply executed
Code:
sudo fastboot flash boot 'twrp-3.4.0-0-guacamole.img'
.
Click to expand...
Click to collapse
That shouldn't have broken the ability to get into the bootloader. Did you have TWRP installed before or was this your first time? Most of the hardware button combos should work regardless of any system/software issues. So vol down + power isn't working, have you tried vol up + power to force a shutdown and retry?

AndroidRooterKev said:
That shouldn't have broken the ability to get into the bootloader. Did you have TWRP installed before or was this your first time? Most of the hardware button combos should work regardless of any system/software issues. So vol down + power isn't working, have you tried vol up + power to force a shutdown and retry?
Click to expand...
Click to collapse
funny, I have been trying now for about 1:30-2h to get into fastboot mode. and 10 sec ago, I got into it. strange. no idea how.
ok, now trying to somehow get into twrp to then perform backup (as originally intended)

oh, no - and now:
I executed
Code:
sudo fastboot boot 'twrp-3.4.0-0-guacamole.img'
Downloading 'boot.img' OKAY [ 0.799s]
booting OKAY [ 0.105s]
Finished. Total time: 0.962s
and then the device rebooted showing me the +1 logo and "fastboot mode". but my computer cannot find it anymore in fasboot mode

inli said:
oh, no - and now:
I executed
Code:
sudo fastboot boot 'twrp-3.4.0-0-guacamole.img'
Downloading 'boot.img' OKAY [ 0.799s]
booting OKAY [ 0.105s]
Finished. Total time: 0.962s
and then the device rebooted showing me the +1 logo and "fastboot mode". but my computer cannot find it anymore in fasboot mode
Click to expand...
Click to collapse
What exact device and software are you running? Have you tried toggling it to "reboot to recovery" on the phone itself? The fastboot command seems to have been successfu so no need to run anymore fastboot commands. Now it's just a matter of getting the phone into recovery. You can even just hold the vol down + power to try and get there.

AndroidRooterKev said:
What exact device and software are you running? Have you tried toggling it to "reboot to recovery" on the phone itself? The fastboot command seems to have been successfu so no need to run anymore fastboot commands. Now it's just a matter of getting the phone into recovery. You can even just hold the vol down + power to try and get there.
Click to expand...
Click to collapse
interesting: when I fastboot boot recovery.img I then get the +1 logo and nothijg works anymore.
if I am in fastboot mode and select "restart bootloader" I get well into fastboot mode. if I select "restart into recovery" I get the "bootloader is unlocked screen".

inli said:
interesting: when I fastboot boot recovery.img I then get the +1 logo and nothijg works anymore.
if I am in fastboot mode and select "restart bootloader" I get well into fastboot mode. if I select "restart into recovery" I get the "bootloader is unlocked screen".
Click to expand...
Click to collapse
Flash the stock boot.img for whatever software you were running.

AndroidRooterKev said:
Flash the stock boot.img for whatever software you were running.
Click to expand...
Click to collapse
yeah, trying this right now. interestingly am now waiting for a few minutes in which lineageos is trying to start - without much success as of yet... i will wait for 10 minutes and then try to reset the whole phone... will keep this thread informed
thank you so far - helped me a lot to note that I am not insane...

aaaah, I figured out
sudo fastboot boot 'twrp-3.3.1-4-guacamole.img' works

hi,
if I may, a brief maybe stupid question: i want to restore
https://oxygenos.oneplus.net/OnePlus7ProOxygen_21.E.26_OTA_026_all_2005192135_8474bf58a0ec4716.zip
websites suggest to run flash all.bat. well, I do not find it anywhere. Do you have an idea where to find it?

inli said:
hi,
if I may, a brief maybe stupid question: i want to restore
https://oxygenos.oneplus.net/OnePlus7ProOxygen_21.E.26_OTA_026_all_2005192135_8474bf58a0ec4716.zip
websites suggest to run flash all.bat. well, I do not find it anywhere. Do you have an idea where to find it?
Click to expand...
Click to collapse
I've never heard of that. But do your research and confirm it works before you do it.
---------- Post added at 01:26 AM ---------- Previous post was at 01:23 AM ----------
inli said:
aaaah, I figured out
sudo fastboot boot 'twrp-3.3.1-4-guacamole.img' works
Click to expand...
Click to collapse
That most likely worked because you're on A9. A10 will not accept that twrp img since it's incompatible.
This is why it's good to mention device/software details of the phone during the creation of an xda post. But glad you got it.

[HELP] POCO M3 system has been destroyed

Hi guys, I need a little help, what happens is that I went to the settings to unlock the bootloader and then proceeded to flash a rom, but after this I got the error "system has been destroyed" Does it mean that to fix it I need to wait for my bootloader to unlock? I forgot that I had to wait a week and I'm not sure what this is because of not waiting or another error, I would also like to know if after time I can fix it since using the MI unlock tool from xiaomi tells me that wait for the time and use the my flash tool to install the stock rom it drops the error "erase is not allowed in lock state"
(EDIT) finish the timer for the unlock bootloader, and after that i just flash a stock rom, thanks for everyone who support me

Re-flash Stock ROM

Tell the problem clearly what issues you are facing??

aaashzz said:
Tell the problem clearly what issues you are facing??
Click to expand...
Click to collapse
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
{
"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"
}

Syxnetrax said:
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
View attachment 5198249
Click to expand...
Click to collapse
Yes tha'ts right you can not flash rom with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi. And the with miflash tool you cannot unlock your phone there is an entirely different tool for unlocking the bootloader "miunlock tool" they are entirely different tools the miflash is only for flash mi rom and for lock your phone. And the other side the miunlock tool is for unlocking the bootloader!

aaashzz said:
Yes tha'ts right you can not flash os with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi.
Click to expand...
Click to collapse
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?

Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?

aaashzz said:
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
Click to expand...
Click to collapse
i can access the fastboot, and the unlock will finish in the time mencioned

Syxnetrax said:
i can access the fastboot, and the unlock will finish in the time mencioned
Click to expand...
Click to collapse
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.

jwoegerbauer said:
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
Click to expand...
Click to collapse
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?

Syxnetrax said:
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Click to expand...
Click to collapse
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>

flashing stock rom does not require bootloader to be unlocked.
just flash the rom using adb or fastboot
i will recommend using fastboot because it's reliable but some time it requires unlocked bootloader so just try fastboot after adb has failed.

jwoegerbauer said:
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
adb reboot sideload starts a bootloop of the same screen "ths system has been destroyed"

bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me

Bhanu8082 said:
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Click to expand...
Click to collapse
this happend, idk if im doing something wrong

Syxnetrax said:
View attachment 5198725
this happend, idk if im doing something wrong
Click to expand...
Click to collapse
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work

jwoegerbauer said:
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
Click to expand...
Click to collapse
after this the same error repeats and start to bootloop with the system has been destroyed screen

bro problem might be your version of adb just use latest version or try version
Android Debug Bridge version 1.0.32
version 1.0.32 is reliable for me as it works

Syxnetrax said:
after this the same error repeats and start to bootloop with the system has been destroyed screen
Click to expand...
Click to collapse
Fix for "The system has been destroyed" Redmi note 8/8T
Fix for "The system has been destroyed" Redmi note 8/8T This will only work for unlocked bootloader...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions...
forum.xda-developers.com

Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Hey did you fixed the phone ??