Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
corpsegrinder62 said:
Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
Click to expand...
Click to collapse
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
antintin said:
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
Click to expand...
Click to collapse
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
corpsegrinder62 said:
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
antintin said:
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
Click to expand...
Click to collapse
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
corpsegrinder62 said:
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
Click to expand...
Click to collapse
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
antintin said:
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
Click to expand...
Click to collapse
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
corpsegrinder62 said:
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
Click to expand...
Click to collapse
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
antintin said:
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
Click to expand...
Click to collapse
Thats great! When you say flash though. You mean dd flash with terminal with su to flash boot_b using said root access right? Then using fastboot to switch to boot_b and use that to unlock, correct?
But no abl yet for G8s as far as im aware, so i take it we need to wait on firehose for it or would cross flashing abl from another device work? Also android 10 update is around the corner, im still on pie 10i for now.
Thanks alot for your patience to help
Related
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
Guys look what i found
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Happy flashing
daca0 said:
Guys look what i found
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Happy flashing
Click to expand...
Click to collapse
are you tried this method before? the thread for Kenzo
It could work with devices with unlocked bootloader but in this case we couldn´t need it; devices with unlocked bootloader can be flashed using MiFlash Tool/fastboot and eventually TWRP.
It doesn´t work in devices with locked bootloader.
Technically script sends device to EDL but like the bootloader it´s locked it refuses to boot in EDL mode and restarts in the system finally.
SubwayChamp said:
It could work with devices with unlocked bootloader but in this case we couldn´t need it; devices with unlocked bootloader can be flashed using MiFlash Tool/fastboot and eventually TWRP.
It doesn´t work in devices with locked bootloader.
Technically script sends device to EDL but like the bootloader it´s locked it refuses to boot in EDL mode and restarts in the system finally.
Click to expand...
Click to collapse
is it true EDL flashing more 'clean' than fasboot flashing method?
EriecTan said:
is it true EDL flashing more 'clean' than fasboot flashing method?
Click to expand...
Click to collapse
Sorry, What do you mean?
If you ask if through EDL it's a cleanest method, no, there's no difference with fastboot method that you can use using MiFlash Tool or using fastboot commands to flash partitions
SubwayChamp said:
Sorry, What do you mean?
If you ask if through EDL it's a cleanest method, no, there's no difference with fastboot method that you can use using MiFlash Tool or using fastboot commands to flash partitions
Click to expand...
Click to collapse
thanks mate for the answer!
Do not worked
Hi.
This treatment does not work for redmi note 6 pro.
In my opinion Google should make EDL mandatory on any and every phone. If I remember correctly EDL makes Snapdragon phones unbrickable. Though Xiaomi has been locking it off and using proprietory code to put authorization locks on it.
I'm guessing because it's a major vulnerability (on Kenzo, I think EDL meant you could throw any file at the phone) but the easy fix there is simply enforcing a hardcoded checksum for any incoming recovery file.
But really Google needs to make sure phones can be easily recovered by consumers from even the dodgiest bootloader flashes, botched flash memory situations, modem edits, mismatched firmware somehow flashing to the wrong phone and whatever other ways a phone can be messed up.
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:
It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying
Are you able to flash one of these Fastboot ROMs?
Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images
I cannot flash anything. Because my OEM state is locked.
Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?
Volume down plus power button takes me to "Your device is corrupt and will not boot"
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.
Don't know if it's too late but I believe there's a working MSM tool now
Anyone know how to lock the bootloader successfully? Clarification - I can lock the bootloader successfully but then can't boot normally.
I have a Frankenstein LG G7 emw from Aliexpress.
I have crossflashed it with an open EUR 10 Q kdz (G710EM)
After flashing the V35 onto abl_a and using "fastboot oem lock" the command is successful.
If I then restore my backed up original abl_a I then get a red triangle bootloop. I also sometimes get an unpatched fastboot screen with correct model type (G710EMW instead of the V35 one)
However I am unable to boot normally and then have to restore the V35, unlock the bootloader again, restore original abl, get into download mode and then reflash kdz using LGUP.
What do I need to lock the the bootloader and then boot normally? I want to be able to use Google pay and banking apps
Any help, ideas, tips or clues appreciated
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
sourabh7625 said:
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
Click to expand...
Click to collapse
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
gridmuncher said:
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
Click to expand...
Click to collapse
It was running on competely stock just booted into fastboot from using "adb reboot bootloader" and entered "fastboot oem lock" and everything worked fine.
What's state your phone currently in ? And what is your desired state ?
I have cross flashed the phone with an Android 10 kdz (european 30f). The bootloader is unlocked, but I cannot relock the bootloader. I have erased the laf_a partition to enable fastboot, but then "fastboot oem lock" doens't work. If I flash the v35 to abl_a then th command works but then the phone is in a red triangle bootloop.
I have tried extensively to google it but I have no idea how to make it work. I backed up numerous partitions using QFIL and tried to restore them once bootloader was locked but nothing seemed to help. The only way out of the bootloop was to return to download mode a reflash a kdz using LGUP
I’ve unlocked my bootloader and rooted previously on the stock A10 ATT rom. I’ve then cross flashed to the A11 CAN version. Bootloader is still obviously unlocked but root is gone. I understand how to root again but I can’t get into bootloader mode to see if I have an active boot_a or boot_b. Does anyone know how to do this or any other way to see which is active? I’ve tried button combinations and ADB reboot bootloader command with no luck. It was working fine previously but I can no longer get into it after crossflashing.
BWA_Dallas said:
I’ve unlocked my bootloader and rooted previously on the stock A10 ATT rom. I’ve then cross flashed to the A11 CAN version. Bootloader is still obviously unlocked but root is gone. I understand how to root again but I can’t get into bootloader mode to see if I have an active boot_a or boot_b. Does anyone know how to do this or any other way to see which is active? I’ve tried button combinations and ADB reboot bootloader command with no luck. It was working fine previously but I can no longer get into it after crossflashing.
Click to expand...
Click to collapse
You probably don't have the engineering abl flashed to the appropriate abl slot. Using that abl is what gives you fastboot. But once you've used it, you have to flash the original back, so that the phone will boot. The engineering abl is based on an earlier version of android.
This is exactly what I needed. Thank you!