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

Nexus 5 stuck in bootloop with no access to E:

My phone (2nd nexus5, not my daily driver nexus) is stuck in a bootloop (stuck at the booting animation) after updating via the OTA updtes, never rooted or touched any setting in the dev options in the setting menu.
The phone stays like that for hours, doesn't even reboot on its own, just keeps playing the bootanimation for hours and hours until the battery dies.
I have access to the bootloader, and default(stock) recovery.
tried oem unlock, but it doesn't work, and shows no errors.
Tried hard reset from the stock recovery and got numerous E: Failed to mount ..... errors. (check attached photo)
All attempts to wipe or format anypart of the phone fail with the same error,
ADB side load of a custom recovery ( TWRP ) also failed with the same error.
Please help me out, data loss is not an issue as i had no imp data and used it mainly for calls and emails.
{
"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"
}

Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom

pranavmali said:
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
Click to expand...
Click to collapse
It shows an error
FAILED (remote: not supported in locked device)
Like I said, oem unlock doesn't work.
As soon as i give the oem unlock command, it will ask for conformation, after hitting yes,
it will even show LOCK STATE - unlocked.
But as soon as the phone reboots or re-enters bootloader, the phone is back to a locked bootloader.
On unlocking bootloader, flashing TWRP via fastboot, when i enter recovery mode, i am still taken back to the stock recovery.

Try Wug fresh's tool kit! To unlock bootloader

Does the give give an error message when issuing the fastboot oem unlock command?

pranavmali said:
Try Wug fresh's tool kit! To unlock bootloader
Click to expand...
Click to collapse
No effect, still stuck the same way.
below is the live log from the NRT toolkit
Live log initiated [2016-05-19]:
Analyzing factory image; please be patient...
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
Checking ADB/FASTBOOT Connectivity
adb devices
03670030215d290e device
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
fastboot oem unlock
Rebooting your device...
and then suck at bootanimation loop

audit13 said:
Does the give give an error message when issuing the fastboot oem unlock command?
Click to expand...
Click to collapse
when i give the fast boot oem unlock command, it will get executed, my phone will ask for me to manually go to the yes key, hit power button to conform,
I am taken back to the bootloader screen, it shows lock state- unlocked
and the word "erasing..." flashes under it for less than 1 second and thats it...no other change what so ever, as soon as i reboot to bootloader or reboot the phone or do anything, the phone is back to the locked bootloader state.

The emmc is damaged or defective and can only be fixed with a motherboard replacement.

audit13 said:
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
Click to expand...
Click to collapse
is there a sure-shot way of determining that my emmc is damaged ..?
the state that my phone is in now, it would make more sense to just buy a new device rather than replace the motherboard.
or
another option i can consider is the thread - http://forum.xda-developers.com/google-nexus-5/help/nexus-5-64gb-t3350533 for getting a new emmc and replacing, but before i take any actions i would like to know that there is no other option left.

Since you now appear to have nothing to lose, try installing the full N5 OTA image:
https://developers.google.com/android/nexus/ota#hammerhead-for-nexus-5-mobile
The instructions are on the page, or NRT has an OTA option (Advanced utilities/Sideload OTA update).
It may not work if your bootloader is genuinely locked or if the EMMC is really fried, but worst case you can't do any more damage, right?

Tried to unroot, now Pixel won't go past 'Device is corrupt' screen

Hi all,
I tried to unroot and relock the bootloader for my Pixel through SuperSU (settings, unroot, restore stock recovery etc). However, now when I turn the phone on it gets to the 'your device is corrupt' screen (https://lh3.googleusercontent.com/-Avr7yNnXOpY/VjGcdDK9iHI/AAAAAAAGCf0/LLwjhkLX1yk/w666-h2518/15+-+1) and then just switches off. Is there anything I can do? Bootloader is currently locked (EE Pixel)
{
"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"
}

Just want to make sure I understand you, you said you re-locked your bootloader?

kornesque said:
Just want to make sure I understand you, you said you re-locked your bootloader?
Click to expand...
Click to collapse
Yup.
So did the SuperSU thing. Then went into fastboot to relock. That seemed successful so I tried to restart and this happened..
And I can't get into recovery >.<

My ability to post is intermittent, don't know what's up but if this doesn't get through then...well, i guess you won't know.
Did you take any 7.1.1 updates or sideload anything? Do you have a VZW variant? And can you get to the bootloader to issue fastboot/adb commands? Hopefully you're not hosed, we'll see what we can do and hopefully a guru shows up here too.

Try to unlock the bootloader again. If you can. Download the full system image from Google and flash that. Then re-lock it.
Sent from my Pixel using Tapatalk

brpqzme said:
Yup.
So did the SuperSU thing. Then went into fastboot to relock. That seemed successful so I tried to restart and this happened..
And I can't get into recovery >.<
Click to expand...
Click to collapse
What happens when you boot to recovery?

bobby janow said:
What happens when you boot to recovery?
Click to expand...
Click to collapse
It boots into the bootloader. Then I choose the RECOVERY option and the 'YOUR DEVICE IS CORRUPT' screen shows up again. It stays on that for a few seconds then the device turns off, exactly like how it does when I try to boot into the phone normally. So I can't get into recovery either..
kornesque said:
My ability to post is intermittent, don't know what's up but if this doesn't get through then...well, i guess you won't know.
Did you take any 7.1.1 updates or sideload anything? Do you have a VZW variant? And can you get to the bootloader to issue fastboot/adb commands? Hopefully you're not hosed, we'll see what we can do and hopefully a guru shows up here too.
Click to expand...
Click to collapse
So this is an EE variant (similar to the VZW one, but UK-based). I can get into the bootloader (holding down power+ vol down) but ADB DEVICES doesn't list anything. I didn't update it to 7.1.1. I used SuperSU to UNROOT, clicked YES when it asked to restore stock recovery and image. Booted into fastboot and relocked bootloader.
Though if I use the SkipSoft toolkit it does detect it in Fastboot mode

Electroz said:
Try to unlock the bootloader again. If you can. Download the full system image from Google and flash that. Then re-lock it.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Can't unlock without dePixel8, and can't use that unless I boot into Android itself so that I can push the files..

brpqzme said:
Can't unlock without dePixel8, and can't use that unless I boot into Android itself so that I can push the files..
Click to expand...
Click to collapse
Have you tried a regular fastboot unlock?
Sent from my Pixel using Tapatalk

Electroz said:
Have you tried a regular fastboot unlock?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yup, tried that through SkipSoft (because normal ADB doesn't detect my phone so using SkipSoft). It says 'failed' when I tried

No idea what skipsoft is. I mean did you load up a command prompt and run the "fastboot OEM unlock" command. This has nothing to do with ADB. You need to be in fastboot mode to run it. To make sure your device shows, run fastboot devices. Again, adb will not help with the bootloader locked.
Sent from my Pixel using Tapatalk

Electroz said:
No idea what skipsoft is. I mean did you load up a command prompt and run the "fastboot OEM unlock" command. This has nothing to do with ADB. You need to be in fastboot mode to run it. To make sure your device shows, run fastboot devices. Again, adb will not help with the bootloader locked.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Ah I see. OK so yes, 'FASTBOOT DEVICES" shows my device. FASTBOOT OEM UNLOCK fails though. Which I guess I expected, because it's an EE/VZW locked phone..

brpqzme said:
Ah I see. OK so yes, 'FASTBOOT DEVICES" shows my device. FASTBOOT OEM UNLOCK fails though. Which I guess I expected, because it's an EE/VZW locked phone..
Click to expand...
Click to collapse
OK. So even in recovery mode you can't get adb devices to show the phone? It sounds like you're out of luck.
Sent from my Pixel using Tapatalk

Electroz said:
OK. So even in recovery mode you can't get adb devices to show the phone? It sounds like you're out of luck.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!

brpqzme said:
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!
Click to expand...
Click to collapse
If you want to go back to stock and relock the bootloader, flash the entire system image from google first. Don't only do half of it or you'll end up in the same spot. Nice find on the fastboot Continue though!
Sent from my Pixel using Tapatalk

Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Electroz said:
If you want to go back to stock and relock the bootloader, flash the entire system image from google first. Don't only do half of it or you'll end up in the same spot. Nice find on the fastboot Continue though!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse

brpqzme said:
Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Click to expand...
Click to collapse
Yes sir
Sent from my Pixel using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
brpqzme said:
Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Click to expand...
Click to collapse
But go with the 7.1.0 image just in case. So you can depixel8 again if need be.
Sent from my Pixel using Tapatalk

brpqzme said:
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!
Click to expand...
Click to collapse
If you truly are still unlocked, I would use Google's flashall bat file so you reflash both partitions correctly.
And I really wouldn't relock it. You got lucky, it would seem that your attempt to relock failed. If it had worked you would have been out of luck.
Without any mods other than unlocked I am pretty sure Android pay works fine.
Did you change anything else, like root or maybe system mods?
Edit. I'm wrong, unlocked trips safteynet. So you flash a kernel that fixes that. Franco does, I think Elemental does and this one does:
http://forum.xda-developers.com/pix...l-stock-kernel-safetynet-patch-t3516596/page5

Yea I don't get people. What's the point of relocking..

aholeinthewor1d said:
Yea I don't get people. What's the point of relocking..
Click to expand...
Click to collapse
You're assuming everybody stays up all night and day following these forums like you and me. We're the pathetic ones. LOL.

My LG Q Stylo plus bricked, Please help save

Hi All,
Yesterday my LG Q Stylo plus was gone into black screen, and could not soft reset or hard reset. When I put it on charging, it vibrated again and again every few minutes, still with black screen. Then I opened the back cover, unplugged the battery to force it power off. Then I tried to factory reset it, but failed to start. Today I tried to flash it, but the PC could not detect the device even though I already downloaded LG driver. In this case, I can not flash it. And it showed on the screen said " FASTBOOT MODE.........". Please see attached picture. Anyone who know how to fix it please help me. Thanks a lot!
{
"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"
}

Can you get into recovery? If so, reset it in recovery or flash a new stock (or custom) rom onto it. In fastboot mode you may be able to directly boot into a custom recovery or flash a custom recovery if you need to.

I tried to flash a new stock rom on it. But PC could not detect the device, even though I already installed the driver. I tried to hold the power button with volume down key to reset it, it didn't work and the screen showed nothing but black. Only after the battery drained out, I plugged the charger on, the screen will be lit and showed the message like above picture showed. Is there any other way to let PC detect the device so that I can flash it?

If you're using Windows, maybe boot into a Linux Live USB (like linux mint for e.g.) and download adb and fastboot. Linux usually works all the time for me with fastboot, so try that and see if it can detect your phone. If detected you might have to run
Code:
fastboot oem unlock
which WILL erase your data, but you can't flash anything without doing so.

I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?

auroraguy123 said:
I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?
Click to expand...
Click to collapse
No. LOCK STATUS on Fastboot likely means the bootloader is locked to not allow custom images to be loaded. This is purely for security and can be unlocked by running the Fastboot oem unlock command I wrote about above. This wipes your data so that, no thief can steal your phone, unlock the bootloader, and browse your files with a custom recovery, as your data will be wiped. I'm not 100% sure but across the few phones in my life that use Fastboot, it has always meant the oem lock to prevent custom images for security reasons.
Any slowdowns occur either because battery saving scheme, full RAM, many processes running, malware, etc. Its not to do with Fastboot.
You should be able to see the device in Fastboot on Linux. Try and flash a custom recovery first, but it might not work because it's locked. In that case you'll need to unlock the Fastboot (which will erase your user data) and then flash a custom recovery, from which you can flash a new rom. Or flash stock recovery and load your official ROM zip if it's supported
Good luck, let us know if you have any issues.

as
quickishfm
said just connect your phone to computer and type
fastboot devices
if device is connected it will be shown on screen
after it just use command adb oem unlock
to unlock bootloader.
if you dont want to unlock bootloader then you will have to erase data partition by using command fastboot erase data

I downloaded adb and fastboot on Linux. But when I typed adb device, still can not see the device. What should I do?

You must type fastboot devices (or fastboot device, I can't remember ) when your screen is in that FASTBOOT MODE.
Once it's in there you just have to flash a custom recovery, or, unlock the bootloader first as we discussed before. This will wipe user data remember. After unlocking bootloader you can flash a custom recovery or stock recovery, and then a new ROM in recovery.

When the device is power off, after I plug it to pc usb, it will show charging sign on the screen and then go the fastboot mode as showed in the picture above. I checked the device manager it was connected as android bootlock inferface. But if I use adb device, there is no device is found.

Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?

auroraguy123 said:
Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?
Click to expand...
Click to collapse
There's no way to do that. It would not be secure if you could overwrite recovery if data is not deleted - then anyone could steal your phone, put a custom recovery and read data partition if not encrypted.
Maybe you can reflash a stock recovery zip (if you can find and if it let's you to flash) through fastboot, then go into recovery and sideload stock rom to your device. Most likely in this case the data will not be deleted.

Thanks. Why it showed unknowed command when I typed fastboot oem unlock?

Hmm, not sure, might have to look on Google. Does anything come up with
Code:
fastboot oem get_unlock_data
?

same when I typed fastboot oem get_unlock_data showed unknown command. Is there a way to let pc force the device to go to download moade because it stuck in the fastboot mode?

AFAIK the download mode is only a thing for Samsung, most other Android phones use fastboot as the download mode which flashes recovery etc.
Perhaps look online on ways to fix the unknown command issue... How did you install fastboot for the Linux?

Cn you run fastboot oem help, and fastboot --version please
Post the output here, thanks

I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.

auroraguy123 said:
I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.View attachment 5204225View attachment 5204225
Click to expand...
Click to collapse
That's useful, thanks. It seems the syntax has changed. Try
fastboot flashing unlock
to unlock the bootloader, and then you should be able to flash a custom recovery.
There's also update to directly flash an update.zip if you can find one, which might not need unlock boorloader. But this will likely have to be a stock update.zip signed by LG so no custom recovery or anything. I don't know if this will erase data.

I also run fastboot -w, it started wiping, but then failed as shown unknown command.

[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 ??