Related
So i decided to unlock my h815sea bootloader, every thing went fine. I was able to flash twrp, flash android 6.0 with root and boot into system. I wanted to install xposed, i downloaded v78-sdk23-arm64.zip. I flash the zip and reboot into system. Now i cant go past lg boot screen. Could someone tell me how i can go into twrp? I am able to go into download mode, but LGUP application shows phone as unknown, can I use lg flashtool to flash android 6.0 kdz? OR am i able to flash android 5.1 kdz since i am able to go into download mode. I backed up everything using twrp and have all the files on my desktop.
nvm. I was able to go into recovery and flash genisys rom for xposed framework. For some reason when i try to flash xposed on a stock mm file, phone goes stuck on lg logo.
blackburry said:
nvm. I was able to go into recovery and flash genisys rom for xposed framework. For some reason when i try to flash xposed on a stock mm file, phone goes stuck on lg logo.
Click to expand...
Click to collapse
When did you unlock your bootloader?
I would love to know the answer to that as well.
reiko09 said:
When did you unlock your bootloader?
Click to expand...
Click to collapse
I was able to get the unlock key when lg accidentally enabled bootloader unlocking for SEA variant on their website. Didn't it use the unlock key until yesterday. Loving MM, so smooth.
blackburry said:
I was able to get the unlock key when lg accidentally enabled bootloader unlocking for SEA variant on their website. Didn't it use the unlock key until yesterday. Loving MM, so smooth.
Click to expand...
Click to collapse
There's a guy (shiboby) that is looking for the unlock.bin files to examine to see if he can figure anything out for them. Doubtful anything will come of it, but you may want to send him yours to see if it would help
hyperfriend said:
There's a guy (shiboby) that is looking for the unlock.bin files to examine to see if he can figure anything out for them. Doubtful anything will come of it, but you may want to send him yours to see if it would help
Click to expand...
Click to collapse
As an owner of a locked H815 SEA, I would greatly appreciate him being sent this file haha. Or perhaps post it in this thread: [Bounty] [allready $2400+] Unofficial bootloader unlock
hyperfriend said:
There's a guy (shiboby) that is looking for the unlock.bin files to examine to see if he can figure anything out for them. Doubtful anything will come of it, but you may want to send him yours to see if it would help
Click to expand...
Click to collapse
Done & Done. Posted the zip on bootloader bounty thread.
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?
Seriously nobody? I thought this phone has good community and support...
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock
ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.
I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU
samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk
SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I do have a computer, a Windows 10 Pro
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
sliding_billy said:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
Click to expand...
Click to collapse
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
coolhandz said:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
Click to expand...
Click to collapse
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
sliding_billy said:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
Click to expand...
Click to collapse
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
sliding_billy said:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
Click to expand...
Click to collapse
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.
eec007 said:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Click to expand...
Click to collapse
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
bobby janow said:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
Click to expand...
Click to collapse
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
eec007 said:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
Click to expand...
Click to collapse
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.
eec007 said:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
Click to expand...
Click to collapse
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
eec007 said:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Click to expand...
Click to collapse
They're right to mention that relocking a modified device can result in a brick.
Your best bet is to go to https://developers.google.com/android/images#taimen
Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.
Would suggest to do this anyway, no matter future unlock status.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...
Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said.
turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.
I entered my device info (European G8s) on the LG bootloader unlock page and they actually sent me a key
I flashed it and the bootloader is now unlocked.
Are there any custom recoveries for the G8 so I can root it?
Confirmation SS: https://i.gyazo.com/c462abdb50c9b9b4f985a72d4c17c3cc.png
Flashing: https://i.gyazo.com/a35d0baebc4e1fcfa6ab2d2697e0709c.png
Confirming flash: https://i.gyazo.com/cbc958227bbdf75496f8b78ca0601086.png
Yup, I unlocked mine as well. Hope someone develops custom recovery and rom.
hej2010 said:
I entered my device info (European G8s) on the LG bootloader unlock page and they actually sent me a key
I flashed it and the bootloader is now unlocked.
Are there any custom recoveries for the G8 so I can root it?
Confirmation SS: https://i.gyazo.com/c462abdb50c9b9b4f985a72d4c17c3cc.png
Flashing: https://i.gyazo.com/a35d0baebc4e1fcfa6ab2d2697e0709c.png
Confirming flash: https://i.gyazo.com/cbc958227bbdf75496f8b78ca0601086.png
Click to expand...
Click to collapse
You can root without twrp in fastboot. No custom ROMs because most people can't unlock bl...
Just tried with my LMG820QM. Does not work. I was hoping it would because the G8s isn't on the list either.
Thank you.
If anyone has the stock boot.img of the EAUW (I think? the one with W) variant, please upload it
I can't manage to unpack the KDZ and get to the img but I would really love to get root already
Frau Son said:
Thank you.
If anyone has the stock boot.img of the EAUW (I think? the one with W) variant, please upload it
I can't manage to unpack the KDZ and get to the img but I would really love to get root already
Click to expand...
Click to collapse
How did you get the KDZ? Can you send/upload it?
Edit: I downloaded a KDZ and got it extracted using https://github.com/steadfasterX/kdztools.
Will try to patch the boot image with magisk
hej2010
Thank you best news this year wait since last year,i no longer believed in it :laugh: . I love the LG 8s today more :victory:
I have the "DEC" LMG810EAW is working ,i hope beginning developer make custom roms ,kernel,TWRP and camera mods :highfive: :victory:
Root is working!!!
I patched the boot image with magisk and it works
Edit: wrote a small guide here: https://forum.xda-developers.com/lg-g8/how-to/rooting-g8s-guide-t4044193
hej2010 said:
Root is working!!!
I patched the boot image with magisk and it works
Edit: wrote a small guide here: https://forum.xda-developers.com/lg-g8/how-to/rooting-g8s-guide-t4044193
Click to expand...
Click to collapse
You are an ANGEL!
Thank you so, so much, you made my evening!
:fingers-crossed:
I was able to unlock my G8s LM-G810EAW aswell
Let's hope there will be a custom recovery soon!
Anybody with unlocked bootloader already tried to flash a gsi?
According to the G8, v50 telegram group gsi are fully working on the g8 without any special adaptions.
Anyone know how to unlock the LM-G850QM version?
Can't seem to find a way yet.
How do you lock the bootloader?
I bought an unlocked LG G8 ThinQ US Cellular version here in HK. Works perfectly fine but I receive the bootloader is unlocked message when loading up. As a result (or at least I think it's linked), when I try and install any banking app for Citibank on my phone, it insists my phone is rooted and I cannot use it. I have checked with as many different apps as possible and they all insist that the phone is not rooted. I don't need/want the phone to be rooted and I want the banking app to work on my phone, so I am trying to lock the bootloader. Apparently, this is doable using ADB and loading in fastboot, unfortunately, I cannot load the phone into fastboot mode. Any ideas on how I can lock the bootloader as it's not clear how it was unlocked in the first place? The version I have is LMT600US.
Also, if anyone knows whether locking the bootloader will somehow render my phone unusable - that would also be helpful as I clearly don't want to do that? :good:
djoseph852 said:
I bought an unlocked LG G8 ThinQ US Cellular version here in HK. Works perfectly fine but I receive the bootloader is unlocked message when loading up. As a result (or at least I think it's linked), when I try and install any banking app for Citibank on my phone, it insists my phone is rooted and I cannot use it. I have checked with as many different apps as possible and they all insist that the phone is not rooted. I don't need/want the phone to be rooted and I want the banking app to work on my phone, so I am trying to lock the bootloader. Apparently, this is doable using ADB and loading in fastboot, unfortunately, I cannot load the phone into fastboot mode. Any ideas on how I can lock the bootloader as it's not clear how it was unlocked in the first place? The version I have is LMT600US.
Also, if anyone knows whether locking the bootloader will somehow render my phone unusable - that would also be helpful as I clearly don't want to do that? :good:
Click to expand...
Click to collapse
Well, you can first try to install magisk manager and try to enable magisk hide (the default settings for play services and for your banking apps). If it says you don't have magisk, make sure you try and backup your boot img first and then click direct install. You can also hide magisk manager in settings. If you still don't pass safety net, clear data for Google apps and look up the pxl4xlprops module
I have an LM-G810EAW with Android 10 (V20a-EEA-XX) and tried to unlock the bootloader. Got unlock.bin from LG and tried to flash it, but got the message:
Code:
> fastboot flash unlock ./unlock.bin
Sending 'unlock' (1 KB) OKAY [ 0.009s]
Writing 'unlock' FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Have I missed something?
EDIT:
YES, I missed to enable OEM Unlock!
hej2010 said:
I entered my device info (European G8s) on the LG bootloader unlock page and they actually sent me a key
I flashed it and the bootloader is now unlocked.
Are there any custom recoveries for the G8 so I can root it?
Confirmation SS: https://i.gyazo.com/c462abdb50c9b9b4f985a72d4c17c3cc.png
Flashing: https://i.gyazo.com/a35d0baebc4e1fcfa6ab2d2697e0709c.png
Confirming flash: https://i.gyazo.com/cbc958227bbdf75496f8b78ca0601086.png
Click to expand...
Click to collapse
I need Lg up & Dll for my lg g8 s LM-G820N
Hello XDA-Developer-Forum!
I think I have messed up my new phone XQ-BT52.
I followed the instructions on this thread https://forum.xda-developers.com/t/how-to-root-and-pass-safetynet-on-xq-bt52-62-0-a-3-163.4408851/ and all worked fine.
But then I wanted to have R/W on System and started there. https://forum.xda-developers.com/t/...-superrw-featuring-makerw-read-write.4247311/
I wanted to flash the image with fastboot, but had problems with the drivers.
Somehow I had the bad idea to issue fastboot oem lock
Now my device is locked again. I managed to get into recovery and made a wipe data / factory reset.
I cannot flash with fastboot, because the device seems to be locked.
The same happens with adb sideload.
Can I unlock the bootloader again?
Or can I flash the version of stock android 12 with adb sideload (I read that this would work with locked bootloader too)?
But adb sideload works only with zip-files. How to create a signed zip from XQ-BT52_Customized EEA_62.1.A.0.533?
Any help is really appreciate!
Thankx in advance!
It sounds like maybe your system partitions got messed up? Go into flashboot mode and try using newflasher with just the super.sin file from the downloaded firmware.
Make sure you use a super.sin from the same firmware you had on the phone when this happened.
Flashing official images should work even if the device is locked, because they're signed by Sony.
Thank you for your reply wirespot!
I guess flashing would not be not be possible, because the phone is locked.
However, I managed to repair the phone with Xperia Companion.
Selected "Device not detected" and connected with volume up or down pressed (cannot remember).
And it worked!
I removed unneeded apps with adb shell and pm uninstall -k --user 0 NameOfPackage.
Glad to have my new phone back.
Thankx again.
Please, did you find an answer to your question about unlocking again?
I am going through some issues with my 10III too and I want to try locking the bootloader, and going the Companion way as you did. But, once everything is repaired, I will need an unlocked bootloader again.
marbalf said:
Please, did you find an answer to your question about unlocking again?
I am going through some issues with my 10III too and I want to try locking the bootloader, and going the Companion way as you did. But, once everything is repaired, I will need an unlocked bootloader again.
Click to expand...
Click to collapse
Yes you can unlock BL after
King081 said:
Yes you can unlock BL after
Click to expand...
Click to collapse
Thank you!