Hello
I have managed to extract the boot.img from the kdz file and patched it with Magisk.
I now have an rooted working LG V60.
The latest V600EA20c is now also available and patched
Regards,
Olavbson
boot_V600EA10o_00_1118_magisk.img
drive.google.com
boot_V600EA20c_magisk.img
drive.google.com
Can it be done in the AT&T variant? LMV600AM
PesSarmiento said:
Can it be done in the AT&T variant? LMV600AM
Click to expand...
Click to collapse
Only EA variant, other variant for now is not possible or maybe never
olavbson said:
Hello
I have managed to extract the boot.img from the kdz file and patched it with Magisk.
I now have an rooted working LG V60.
Regards,
Olavbson
boot_V600EA10o_00_1118_magisk.img
drive.google.com
Click to expand...
Click to collapse
Can you back up partitions like abl_a, abl_b, xbl_a, xbl_b, xbl_a_config, xbl_b_config and post the link here, I will be able to root other models
Mr.PvT said:
Can you back up partitions like abl_a, abl_b, xbl_a, xbl_b, xbl_a_config, xbl_b_config and post the link here, I will be able to root other models
Click to expand...
Click to collapse
I am waiting one day when other models will be rooted
Mr.PvT said:
Can you back up partitions like abl_a, abl_b, xbl_a, xbl_b, xbl_a_config, xbl_b_config and post the link here, I will be able to root other models
Click to expand...
Click to collapse
Hello
You will find all the extracted files from the dz files under the post LG V60 LMV600EA extracted dz files
olavbson said:
Hello
You will find all the extracted files from the dz files under the post LG V60 LMV600EA extracted dz files
Click to expand...
Click to collapse
I need the file from the device with successfully unlocked the bootloader, not the word kdz, if the word kdz it is too simple, I have had it for a long time
JigsawMobile said:
I am waiting one day when other models will be rooted
Click to expand...
Click to collapse
yes i am testing that, but i need files from unlocked device bootloader, not extract from kdz
Mr.PvT said:
yes i am testing that, but i need files from unlocked device bootloader, not extract from kdz
Click to expand...
Click to collapse
Check on reddit lg v60 thread and ask them, there are people with EA models, ask to unlock bootloader if not unlocked
Just replying to say that's awesome!
Hey man is there any way i can contact you. I also have an ea version and would like to root it aswell.
now that LG mobile is no more, maybe we can petition for them to help us unlock our phones!
I've been thinking of writing something like that up. The issue is there are so many closed source components in the OS that disentangling it is far more work than LG has ever shown an interest in doing.
Hey guys, for all of you who rooted the LMV600EA, does your VoLTE still work? or is that a A11 issue?
Also is that a thing on the V60 that if you unlock BL, the Fingerprint sensor won't work at all? My unlocked G8s worked fine.
Edit: Fingerprint sensor just randomly started working lol
olavbson said:
Hello
I have managed to extract the boot.img from the kdz file and patched it with Magisk.
I now have an rooted working LG V60.
The latest V600EA20c is now also available and patched
Regards,
Olavbson
boot_V600EA10o_00_1118_magisk.img
drive.google.com
boot_V600EA20c_magisk.img
drive.google.com
Click to expand...
Click to collapse
Hello everyone, I am from Vietnam. I am buying a variant of LG V60 ThinQ in the Taiwan market with its model number: LMV600EA.ATWNCB
Everyone can refer to it from the following link: https://www.lg.com/tw/support/product/lg-LMV600EA.ATWNCB
As far as I know, the list of supported bootloader unlocked devices includes LG V60 but it is in the European market in supported devices tab at the following link: https://developer.lge.com/resource/mobile/RetrieveBootloader. dev
I asked myself that: Assuming, if it can't be unlocked bootloader then will it be able to be unlocked by flashing Europe firmware as the following V600EA20c? https://lg-firmwares.com/downloads-file/24767/V600EA20c_00_COM1_EU_OP_0219
Nguyễn Đức Hiếu said:
Hello everyone, I am from Vietnam. I am buying a variant of LG V60 ThinQ in the Taiwan market with its model number: LMV600EA.ATWNCB
Everyone can refer to it from the following link: https://www.lg.com/tw/support/product/lg-LMV600EA.ATWNCB
As far as I know, the list of supported bootloader unlocked devices includes LG V60 but it is in the European market in supported devices tab at the following link: https://developer.lge.com/resource/mobile/RetrieveBootloader. dev
I asked myself that: Assuming, if it can't be unlocked bootloader then will it be able to be unlocked by flashing Europe firmware as the following V600EA20c? https://lg-firmwares.com/downloads-file/24767/V600EA20c_00_COM1_EU_OP_0219
Click to expand...
Click to collapse
can be unlocked
Mr.PvT said:
can be unlocked
Click to expand...
Click to collapse
Are u sure 100%? because I have only one chance
Nguyễn Đức Hiếu said:
Hello everyone, I am from Vietnam. I am buying a variant of LG V60 ThinQ in the Taiwan market with its model number: LMV600EA.ATWNCB
Everyone can refer to it from the following link: https://www.lg.com/tw/support/product/lg-LMV600EA.ATWNCB
As far as I know, the list of supported bootloader unlocked devices includes LG V60 but it is in the European market in supported devices tab at the following link: https://developer.lge.com/resource/mobile/RetrieveBootloader. dev
I asked myself that: Assuming, if it can't be unlocked bootloader then will it be able to be unlocked by flashing Europe firmware as the following V600EA20c? https://lg-firmwares.com/downloads-file/24767/V600EA20c_00_COM1_EU_OP_0219
Click to expand...
Click to collapse
Hey, I've got the Taiwan model and the bootloader cannot be unlocked and no other variant can be flashed.
hegezolee said:
Hey, I've got the Taiwan model and the bootloader cannot be unlocked and no other variant can be flashed.
Click to expand...
Click to collapse
Lol. I yet didnt buy it, V600EA Taiwan market. Okay, thks so much for your information, i will stop buying it now.
Hi,
I'm having trouble flashing the patched boot.img to my phone, I hope someone can help.
I have an LM-V600EA (European SWC variant) and I've done the bootloader unlock process via LGs website, and flashed the unlock.bin. fastboot getvar unlocked tells me the phone is unlocked.
When I adb reboot fastboot and then fastboot flash boot boot_V600EA10o_00_1118_magisk.img I get the following error:
sending 'boot' (98304 KB)...
OKAY [ 2.259s]
writing 'boot'...
FAILED (remote: Cannot flash this partition in unlocked state)
Anyone able to shed some light what I am doing wrong?
Thanking you in advance.
Related
https://threatpost.com/another-linux...access/137800/
Would be awesome if that works
I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9
S8ntsHaz3 said:
I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9
Click to expand...
Click to collapse
Unlock critical is allowed and already known thing but this is for flashing bootloader and stuff. It doesn't help us at all for now.
There are already many rooted tmobile g7 sold in China.
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
anyone tried it yet?
kasuma_asuma said:
anyone tried it yet?
Click to expand...
Click to collapse
So it's a fake post for one (actually not exactly fake I would say more clickbait then anything) two I believe the T-Mobile version is the G710TM, three we have a gimped fastboot as in it doesn't work at all. And four I think our only option is something to do with LAF
---------- Post added at 11:22 AM ---------- Previous post was at 11:21 AM ----------
curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
No it's not the case see my previous answer
We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.
alecthenice said:
We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.
Click to expand...
Click to collapse
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
So for dm-verify I know how to manually get around that and the patch thats floating around via flashable.zip. What do we need to extract from the .up or .kdz? Im pretty sure there is a full kdz dump for the 710EM in a thread I read through just last night? I really believe the only obstacle we have is making the bootloader unlock through a command line independent of the official unlock code. This should be able to be acheived by editing that in a way to where it doesnt check much like dm-verity. Then you can flash your (patched by deletion) boot.img run fastboot oem unlock ( btw did you know that "fastboot oem flashing unlock critical works) **could run that then flash an unlock.bin, then fastboot oem unlock unlock.bin** I am working with a 710pm varient. And am speaking from experience rooting the v30 ls version currently using G7 as daily driver
This leaves me thinking that we have lots of wiggle room here (also leaves me thinking how weird LG is for having a lot of variation within G7)
LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
View attachment 4667707
GROOVYJOSHCLARK said:
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
Click to expand...
Click to collapse
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.
LameMonster82 said:
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.
Click to expand...
Click to collapse
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.
GROOVYJOSHCLARK said:
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.
Click to expand...
Click to collapse
So, do you want to cross flash or just the Sprint firmware
LameMonster82 said:
So, do you want to cross flash or just the Sprint firmware
Click to expand...
Click to collapse
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian
runningnak3d said:
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian
Click to expand...
Click to collapse
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.
GROOVYJOSHCLARK said:
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.
Click to expand...
Click to collapse
Awesome! But octoplus will not allow you to cross flashing, right?
any news on this ? would love to change my T-mobile software. and get the fingerprint to work for that matter
I really need TWRP, but it needs a custom version right ?
Also has somebody got root with magisk yet ?
I have managed to get root on G7, and the way to get root on G7 Power is similar (read my posts on G7 section)
Unfortunately, I don't know how to build TWRP or I can make custom recovery for all three variations
Unfortunately it seems like we currently lack stock ROM images for the European Retail version (RETEU2), which makes using Magisk to root that variant currently not safely possible.
AforAnonymous said:
Unfortunately it seems like we currently lack stock ROM images for the European Retail version (RETEU2), which makes using Magisk to root that variant currently not safely possible.
Click to expand...
Click to collapse
Are you able to get the full ROM?
You should look up your model number to find matching ROM
The best bet is to get "RETAIL" , but you should get ROM of your version just in case you want to revert it back
Many thanks to Mingkee. I just got root access following his directions on the G7 forum. The different step was that I had to download a previous version of stock ROM, once the current version has not leaked. :good:
Do you have the American version?
I have the Brazilian stock firmware (xt1955-1 version PPO29.80-27). Sorry.
---------- Post added at 10:09 AM ---------- Previous post was at 09:30 AM ----------
drive.google.com/file/d/1VFkPzuTuFJInLrbqTbKm4mzHQa6KgYnr/view
It seems this one is the us retail stock firmware. The link above was obtained from kfhost.net/artigo/firmware-motorola-moto-g7-power-xt1955-1-android-9-pie
I just got root on my g7 power using mingkee's instructions for the g7. It says bad key on startup, but still works just fine!
I have root as well from mingkee's guide in the g7 forum.
Crystawth said:
I just got root on my g7 power using mingkee's instructions for the g7. It says bad key on startup, but still works just fine!
Click to expand...
Click to collapse
Please take a link on dm
tommytomson said:
Please take a link on dm
Click to expand...
Click to collapse
Friend what I gather it is just indicating that bootloader is unlocked.
Crystawth said:
I just got root on my g7 power using mingkee's instructions for the g7. It says bad key on startup, but still works just fine!
Click to expand...
Click to collapse
It's rather strange issue because I see same error even I flashed bone stock boot.img when doing manual update G6 to Pie.
The bad key message appeared to me after I had the bootloader unlocked. To unlock it I just followed this: techdroidtips.com/unlock-bootloader-moto-g7/
Download Links
Best place to look for your stock rom is here:
https://mirrors.lolinet.com/firmware/moto/ocean/official/
if somebody has the "RETEU2" moto g7 power and rooted it, see if you can change your wifi region using root so that 5Ghz Wifi can be supported. I read somewhere about it, that the current Wifi region doesnt support 5Ghz and i really need it for my moto
Eutono said:
The bad key message appeared to me after I had the bootloader unlocked. To unlock it I just followed this: techdroidtips.com/unlock-bootloader-moto-g7/
Click to expand...
Click to collapse
Didn't see this before, but yes the "bad key" note pops up on all Moto phones that have bootloader unlocked. I have had 4 different Moto phones and each one has had the "bad key" message before booting.
Is anyone working on a TWRP for this? I'm happy to buy and ship a phone to a reputable forum member if there is a need for the physical hardware.
Alternatively if there is an easy way to get xposed and xprivacy lua installed on this device without TWRP, that's all I need. I don't care about passing safetynet checks.
I've got a root guide over in the discussion threads.
eth01- said:
Is anyone working on a TWRP for this? I'm happy to buy and ship a phone to a reputable forum member if there is a need for the physical hardware.
Alternatively if there is an easy way to get xposed and xprivacy lua installed on this device without TWRP, that's all I need. I don't care about passing safetynet checks.
Click to expand...
Click to collapse
I havent heard anything about anyone working on a twrp and xposed hasnt supported my -2 yet
Eutono said:
I have the Brazilian stock firmware (xt1955-1 version PPO29.80-27). Sorry.
---------- Post added at 10:09 AM ---------- Previous post was at 09:30 AM ----------
drive.google.com/file/d/1VFkPzuTuFJInLrbqTbKm4mzHQa6KgYnr/view
It seems this one is the us retail stock firmware. The link above was obtained from kfhost.net/artigo/firmware-motorola-moto-g7-power-xt1955-1-android-9-pie
Click to expand...
Click to collapse
No, that is not the USA Retail Stock that one, that one is the Brazil version. The USA Retail Stock Verison is XT1955-5. and you can get it from here: Official RETUS XT1955-5 Firmware Download
Just in case here is a list of all variants model numbers
Code:
Moto G7 Power Model Numbers and Regions it belongs to.
XT1955-1 Brazil
XT1955-2 Latin America, Argentina
XT1955-3 Mexico
XT1955-4 Europe
XT1955-5 USA
XT1955-7 Europe, Various (International)
Hi!
I have LGV450PM and I'd like to know if I can try to flash the firmware for example for Hungary on it? Will it brick my phone?
Btw LGUP 1.16 succesfully see my phone.
MindfreakDenny said:
Hi!
I have LGV450PM and I'd like to know if I can try to flash the firmware for example for Hungary on it? Will it brick my phone?
Btw LGUP 1.16 succesfully see my phone.
Click to expand...
Click to collapse
You cannot cross flash it will just give you an error. There's no chance of brick because it just won't flash
But why LG doesn't allow crossflash?
MindfreakDenny said:
But why LG doesn't allow crossflash?
Click to expand...
Click to collapse
Because carriers don't want you to use another firmware... LG has never "allowed" cross flash in the past
But it was possible with LG G7 for example.
MindfreakDenny said:
But it was possible with LG G7 for example.
Click to expand...
Click to collapse
But not because LG allowed it
Hey all, has there been any discussion or progress regarding an EDL firmware for the 2020U variant of the Axon 10 Pro yet? I see we have some Chinese and G EDL firmwares released, but not any for the 2020U. I've yet to unlock my bootloader or install TWRP because of no EDL firmware available to fall back on if anything goes wrong. Just curious if there's one available floating somewhere. Thanks!
brian117 said:
Hey all, has there been any discussion or progress regarding an EDL firmware for the 2020U variant of the Axon 10 Pro yet? I see we have some Chinese and G EDL firmwares released, but not any for the 2020U. I've yet to unlock my bootloader or install TWRP because of no EDL firmware available to fall back on if anything goes wrong. Just curious if there's one available floating somewhere. Thanks!
Click to expand...
Click to collapse
It's available on easy-firmware
Unjustified Dev said:
It's available on easy-firmware
Click to expand...
Click to collapse
Thanks for the response UD, however I cannot seem to locate the specific one needed for the 2020U. Half of them are SD Firmwares, and it doesn't specify the region for them. Any help would be appreciated if you can link the correct one. Thanks again.
brian117 said:
Thanks for the response UD, however I cannot seem to locate the specific one needed for the 2020U. Half of them are SD Firmwares, and it doesn't specify the region for them. Any help would be appreciated if you can link the correct one. Thanks again.
Click to expand...
Click to collapse
https://easy-firmware.com/index.php?a=downloads&b=file&id=165761it doesn't specify region because they all have different model numbers. A2020U is the only US model. Link not working, but it's the ones the correlate with your build number for instance b10 or b04 not the PV that's preproduction firmware used for testing
Sent from my ZTE A2020U Pro using Tapatalk
Unjustified Dev said:
https://easy-firmware.com/index.php?a=downloads&b=file&id=165761it doesn't specify region because they all have different model numbers. A2020U is the only US model. Link not working, but it's the ones the correlate with your build number for instance b10 or b04 not the PV that's preproduction firmware used for testing
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
How do I create an EDL version out of one of those files?
MlM1c said:
I really did a number on my phone and basically now its on EU 1.8. I can't find the U firmware anywhere so please if you have or know where I can obtain it please share.
Thanks a ton!.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=313083
MlM1c said:
Thanks soo much!. One thing though is I'm trying to get it to flash with MiFlash but ends in an error. The EU firmware worked with MiFlash so I'm wondering what I need to do with these files in order to get it to flash. Thanks once again.
Click to expand...
Click to collapse
Did you add the firehose programmer?
Bricked Axon 10 pro
I bricked my Axon 10 pro Us version by trying to unlock the bootloader via the EDL tool, All my phone does is boot into fastboot or just a boot loop and the bootloader did not unlock. I'm new to rooting and stupidly tried this on my daily driver phone. Any help would be greatly appreciated.
I have done some research on this and it turns out i didn't do oem unlocking when i turned on usb debugging, so the issue is that the phone will not boot to the os to enable oem unlocking and the bootloader is still locked so i can't even install a stock rom to it. Anyone have any ideas how i can get an OS on the device or enable oem unlocking through fastboot or any other solution that might help
?
Kay, backstory. I bricked my phone, and MSM for the Global didn't work. I used the op9 pro indian MSM, and that worked, so now I'm with the incorrect firmware. OTA won't work, for whatever reason, so what should I do? No bootloader unlocking, not doing that stuff again
You can try fastboot image. You can find one around here. Otherwise, root, download full zip via OOS Updater and do a local update.
Twrp is also working for our device now, at least mostly.
gorilla p said:
You can try fastboot image. You can find one around here. Otherwise, root, download full zip via OOS Updater and do a local update.
Twrp is also working for our device now, at least mostly.
Click to expand...
Click to collapse
I would, but I don't wanna unlock bootloader
winterfoxx said:
I would, but I don't wanna unlock bootloader
Click to expand...
Click to collapse
I don't think there is a way to get back to global without
XxBigBuckxX said:
I don't think there is a way to get back to global without
Click to expand...
Click to collapse
I pulled it off, and am working on a comprehensive unbricking guide. Thanks!
winterfoxx said:
I pulled it off, and am working on a comprehensive unbricking guide. Thanks!
Click to expand...
Click to collapse
is it ready im in the same boat and curious on how you did it?
YourLocalDund33 said:
is it ready im in the same boat and curious on how you did it?
Click to expand...
Click to collapse
Yes, sorry about the late reply, here:
Global/US unbricking guide.
Global/US OnePlus 9 Unbricking Guide Tested and used on a LE2115 variant device. YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST...
forum.xda-developers.com
Okay so I was finally able to flash back to the tmobile firmware using msm tool
I'm testing everything out now but it seems fine still had to trick it into thinking it was the IN variant.
XxBigBuckxX said:
I'm testing everything out now but it seems fine still had to trick it into thinking it was the IN variant.
Click to expand...
Click to collapse
How exactly did you trick it?
JimmyJurner said:
How exactly did you trick it?
Click to expand...
Click to collapse
You download the msm tool you need and oppo_decrypt to extract the .ops file. Then there will be a file created called settings.xml and you just need to edit that file and add one line to the bottom in-between <SupportMultiTarget> , run oppo tool again to put it one big .ops file, So more so not trick it but just add support to for the IN model. Until I can figure out how to make it change on the actually device this is the best I can come up with. This is only if you are having trouble using your original msm tool and having to use the Indian Pro version. Its solved all my issues.
XML:
<Target ID="3" Desc="India" />