Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
ryn.ste said:
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
Click to expand...
Click to collapse
Can u share the link I wanna try it also
ryn.ste said:
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
Click to expand...
Click to collapse
Is it a 8.0 kdz to update to 9.0 or directly a 9.0 kdz?
Did it work?
MishaalRahman said:
Did it work?
Click to expand...
Click to collapse
Lack of response, I'm gonna guess no? LoL
dah brick dah bricks.
???
The suspense is killing me. Personally I'm waiting for the official, but it would be nice to know...
i guess i would be able to flash it on my g7 , but i only have a .up file instead of a kdz and that doesnt work
Warning!
From what I read recently; LG has started to use unique RSA keys for each device (within a group, i.e G7) starting with V35 (I think), thus flashing a KDZ from another G7 would definitively cause hardbrick.
Edit: Apparently this was (mostly?) wrong. At least some confirmed models can be cross-flashed.
askermk2000 said:
Warning!
From what I read recently; LG has started to use unique RSA keys for each device (within a group, i.e G7) starting with V35 (I think), thus flashing a KDZ from another G7 would definitively cause hardbrick.
Click to expand...
Click to collapse
I thought that was only for TMoile but not the rest of variants?
GROOVYJOSHCLARK said:
I thought that was only for TMoile but not the rest of variants?
Click to expand...
Click to collapse
Well, like I said, not anymore.
IIRC, this is what @runningnak3d said in a tread somewhere (I don't recall exactly, maybe V30 forums).
He is the current resident expert on LG root, and bootloader matters. At least the most active one, and he's provided root for many previous LG devices.
askermk2000 said:
Well, like I said, not anymore.
IIRC, this is what @runningnak3d said in a tread somewhere (I don't recall exactly, maybe V30 forums).
He is the current resident expert on LG root, and bootloader matters. At least the most active one, and he's provided root for many previous LG devices.
Click to expand...
Click to collapse
I am definitely not arguing as I dont know the answer 100% myself.
What I DO know for sure is that I can, (and I have) flashed other LG G7's firmware on my G7 (Sprint) through my Octoplus box. This is using the Octoplus box, not LGUP, but if the RSA keys were an issue, I would expect it to not work (flashing another variant .KDZ), or I would expect the device not to work (boot) afterwards. It boots and works just fine. I also know of numerous others who have converted their LG G7's (except TMobile) to the unlocked model (ULM). My understanding was that only the TMobile ones were using a custom RSA key coming FROM TMobile themselves (I could be wrong but this is what I read) and since I dont own a TMobile flavor, I cant test myself to confirm.
In that case maybe I remember wrong, or runningnak3d statement was not accurate (maybe doesn't apply to G7 specifically).
askermk2000 said:
In that case maybe I remember wrong, or runningnak3d statement was not accurate (maybe doesn't apply to G7 specifically).
Click to expand...
Click to collapse
All good, I dont know for sure myself so I cant confirm nor deny anything except for my personal Octoplus flashing. I just want ROOT, thats what I am pressing through to figure out how to achieve. I HATE that LG locks the bootloaders, if I had known prior, I would NEVER have switched from HTC!
LG mobile will go out of business soon enough if they dont cut the crap.
Yeah, not to mention that we don't have a way to fix ourselves bricked devices. It would be a trivial matter with a simple qualcomm type firehose-file.
Instead now it's basically dead weight. They seem to think it's ok to produce lots of electronic garbage, and not make efforts to reduce this.
askermk2000 said:
Yeah, not to mention that we don't have a way to fix ourselves bricked devices. It would be a trivial matter with a simple qualcomm type firehose-file.
Instead now it's basically dead weight. They seem to think it's ok to produce lots of electronic garbage, and not make efforts to reduce this.
Click to expand...
Click to collapse
Exactly, hopefully the drop in sales will be enough to kick their butt's in gear BEFORE they become the next Blackberry! If they would simply give us a restore KDZ, we would love LG, instead, they lock us out, and make it damn near impossible to restore or recover our devices from normal things, such as a bad OTA updates. BUT NO, for some dumb A$$ reasons, they dont so it WILL be their demise. Its almost like being able to see the future. If they took notice of all the predecessors before them, all their mistakes, made changes then history wouldn't have to repeat itself. If not, LG will be another forgotten company no one gives a crap about.
GROOVYJOSHCLARK said:
I am definitely not arguing as I dont know the answer 100% myself.
What I DO know for sure is that I can, (and I have) flashed other LG G7's firmware on my G7 (Sprint) through my Octoplus box. This is using the Octoplus box, not LGUP, but if the RSA keys were an issue, I would expect it to not work (flashing another variant .KDZ), or I would expect the device not to work (boot) afterwards. It boots and works just fine. I also know of numerous others who have converted their LG G7's (except TMobile) to the unlocked model (ULM). My understanding was that only the TMobile ones were using a custom RSA key coming FROM TMobile themselves (I could be wrong but this is what I read) and since I dont own a TMobile flavor, I cant test myself to confirm.
Click to expand...
Click to collapse
What partitions did you flash?
All of the KDZs I have been able to pull down have different RSA certs (granted it is only a couple) but it is not just the TMO that was different.
If you don't mind, link to the exact KDZ for your model, and the KDZ that you flashed -- I would love to compare the certs.
-- Brian
runningnak3d said:
What partitions did you flash?
All of the KDZs I have been able to pull down have different RSA certs (granted it is only a couple) but it is not just the TMO that was different.
If you don't mind, link to the exact KDZ for your model, and the KDZ that you flashed -- I would love to compare the certs.
-- Brian
Click to expand...
Click to collapse
There is no KDZ for the PM (Sprint model) yet so I cannot go back to Sprint or link to one (until one is released) but I wish there was one for others who are in a loop or brick situation, here are the 2 I used:
EM (European Model - bootload unlockable approved by LG):
G710EM10b_00_0521.kdz
https://drive.google.com/file/d/1W14Y-jbvnwDt4UOfitni8hDGfwYsXesV/view?usp=sharing
ULM (US Unlocked Model):
G710ULM10g_00_NAO_US_OP_0913.kdz
http://pkg02.lime.gdms.lge.com/dn/d...XADM55F9FR80/G710ULM10g_00_NAO_US_OP_0913.kdz
I flash ALL partitions through Octoplus EXCEPT the modems (MODEM1/2), I left those from Sprint (stock), not sure if it helps or not, but I have service so I like to think it did. There are lots of users who have also used the LGUP (somehow) to cross flash the KDZ's to the ULM (unlocked) model but I haven't personally used this LGUP method so I cant comment if its valid or not. Octoplus, most definitely works though (and I have the logs to show the partitions if one was interested).
GROOVYJOSHCLARK said:
There is no KDZ for the PM (Sprint model) yet so I cannot go back to Sprint or link to one (until one is released) but I wish there was one for others who are in a loop or brick situation, here are the 2 I used:
<snip>
Click to expand...
Click to collapse
There will never be a Sprint KDZ -- neither Sprint or AT&T release KDZs (I don't think they even use them internally).
I am downloading them now, and I will pull the certs / post the results as soon as they are done.
Thanks!
-- Brian
Related
I had to make an insurance claim on my AT&T G3 recently and they sent me a G4 Android 6.0 / h81020n, build MRA58k. From what I understand, there's no way to root it and many don't expect there will be for a while...is that right? If so, what are my best options to downgrade and then root it? It's my only phone, and though I'm extremely competent with this stuff, I need to be sure it's a surefire method of downgrading. Thanks
noamo48 said:
I had to make an insurance claim on my AT&T G3 recently and they sent me a G4 Android 6.0 / h81020n, build MRA58k. From what I understand, there's no way to root it and many don't expect there will be for a while...is that right? If so, what are my best options to downgrade and then root it? It's my only phone, and though I'm extremely competent with this stuff, I need to be sure it's a surefire method of downgrading. Thanks
Click to expand...
Click to collapse
As of now, I'm going to be bold with my statement about the G4: The AT&T cannot and will not ever have an unlocked bootloader. I would also assert the likelihood of root on Marshmallow is slim to none. I'd say "none", except there's always a remote chance that someone with the time/money/know-how will decide not to give up until they've figured it out.
When you say "downgrading", I presume you mean going back to a previous build? If so, it is not possible. It would require the level of access that only an unlocked bootloader could provide, from what I understand. I think there was mention of some sort of bypass option that works on other devices, but it doesn't work with this one.
Long story short: get comfortable with your current experience, because it isn't likely to ever change with this device. I too had to replace my device under warranty (for the 2nd time), and was bummed when the replacement arrived having Marshmallow on it.
noamo48 said:
I had to make an insurance claim on my AT&T G3 recently and they sent me a G4 Android 6.0 / h81020n, build MRA58k. From what I understand, there's no way to root it and many don't expect there will be for a while...is that right? If so, what are my best options to downgrade and then root it? It's my only phone, and though I'm extremely competent with this stuff, I need to be sure it's a surefire method of downgrading. Thanks
Click to expand...
Click to collapse
I have not been able to downgrade H81020n since I got a replacement phone due to the infamous bootloop issue. I'm starting to wonder if somehow AT&T with or without support of LGE figured out which phones were rooted and injected some network packets to stress the radios in this device causing failures.
What's really unfortunate is the replacement devices all come with Marshmallow 6.0 on the H81020n ROM. That locked-down image, with the locked bootloader have made this device much less fun.
I've tried several downgrade paths with no success; the low-effort Root method, TOT downgrades with the LG flash utility, and good old fashioned send_commands.exe for image restoration to stock.
You need to use LGUP
http://forum.xda-developers.com/showpost.php?p=66316842&postcount=113
smknutson said:
You need to use LGUP
http://forum.xda-developers.com/showpost.php?p=66316842&postcount=113
Click to expand...
Click to collapse
I have LGUP and the .tot file. LGUP just won't allow me to flash it for some reason ?....
Sent from my LG-H810 using XDA-Developers mobile app
BTMoneyGang said:
I have LGUP and the .tot file. LGUP just won't allow me to flash it for some reason ?....
Sent from my LG-H810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you load the.tot, close the LGUP program then reopen it and attempt the flash?
Did you change the Port # in Device Manager?
Can the same downgrade be done on 21y for h810 I miss root
This is a thread for the progress of MM root on the AT&T variant of the LG V10. I am working to find a way to root it, even if it is not through a TOT, but a exploit.
I know some of you were wondering about my donate info, and so I decided to go and set up a Paypal if you felt so obliged haha. (Its in my info in my profile)
Right now I am examining a TOT that someone sent me and I will determine if it is corrupted too, or if we have a shred of hope. Wish me luck! Will update later if it is found that it is bad, which I expect.
Ok, so I just compared this TOT to the one that iBowToAndroid sent me, the 2nd time. They are practically identical, regardless of them having different MD5s. Although if anyone feels like actually testing it before they go to better phone, feel free. ha
If it will be possible (and when you will find a way), please, make possible for H960a too.
Well, i am happy to see someone is making progress on the root development on MM, at least, make the community alive.
However, MM needs systemless root and the old way by injecting su binary to the TOT will not work at all.
I am not going to discourage you, unlocking bootloader should be the only way to root MM.
ivangundampc said:
Well, i am happy to see someone is making progress on the root development on MM, at least, make the community alive.
However, MM needs systemless root and the old way by injecting su binary to the TOT will not work at all.
I am not going to discourage you, unlocking bootloader should be the only way to root MM.
Click to expand...
Click to collapse
Unlocking bootloader is something else I currently working on, if the su binary inject does not. Right now I am planning to pull the entire systems contents by soldering off the storage chip and reading it using some hardware of mine. Once I copy all of the partitions over, then the fun begins
ZVNexus said:
Unlocking bootloader is something else I currently working on, if the su binary inject does not. Right now I am planning to pull the entire systems contents by soldering off the storage chip and reading it using some hardware of mine. Once I copy all of the partitions over, then the fun begins
Click to expand...
Click to collapse
The KDZ files used by LGUP include an image of most of the flash used by the system. A few portions are missing, but not very many, notably the "misc" portion is absent. I believe the missing portions are ones that would be unaffected by rooting, so you could get most of the data out of a KDZ file and then root to get the rest of the data.
Aside from the key for the bootloader potentially being in the "misc" area, I also noticed there is noticeable amount of space reserved by the GPT, but unused. There is also a noticeable amount of unallocated space between the GPT and first slice (the "modem" area; this could be for alignment purposes, but it could have other uses as well).
Hopefully LG will be persuaded to unlock the bootloader of all V10 models, but I'm a bit on the pessimistic side at this point. I also hope the unlock mechanism will be shared by all V10s, so we don't need to reproduce it for each device. I haven't done cracking before, but I hope to target the H962 and be able to install full mods in the future...
How goes the progress ZVNexus? Thanks so much for embarking on such a journey for the sake of us all. I loved the flexibility of my Nexus 6, but it was so much weaker than the V10 in so many areas...especially the camera functionality and the ridiculous amount of sluggishness during normal tasks. I went through around 10 of these phones due to QC issues. I'm happy with my V10 (at&t gave me a replacement since I warranty returned the nexus so many times). But, it's just not the same without root and unlocked bootloader. Thank you again!
I found this today..I am sure you have seen it but I figured I would put it here anyway. I downloaded it but figured someone smarter should look before I tried to flash it. I cannot post it. Someone posted it on the original mm tot download thread..it was posted by radical.
In Theory...
In theory...
Are stock MM KDZ files available for the AT&T V10? I haven't seen them in the KDZ thread, but they may be posted in the AT&T area. If so, it should be possible to use my KDZ tools to unpack the KDZ, then install Superuser in the image and then repack the KDZ and tell LGUP to install the modified KDZ.
At the moment I'm cautiously optimistic about the KDZ tools. I've got all of the fields inside the files identified, but there some hazardously big ones in the DZ header that are unknown. My tools simply copy those, but I worry. Also SEEK_DATA/SEEK_HOLE are available on Linux, but likely not on Windows. (hack: replacing SEEK_HOLE with io.SEEK_END at the top of image2chunks.py should work around errors)
any update on this project?
I follow the V20 threads and all the V20s have root now. From what I read they used a debug boot.img from a Developer V20 and extracted the boot.img and used an exploit from the DirtyCow Root method to flash it. You have to really be involved to root it.
Just seeing where this can take the V10.
Any Update?
Sir is there any update on the root for at&t LG v10? Waiting anxiously!!
SH4DOW ASSASSIN said:
Sir is there any update on the root for at&t LG v10? Waiting anxiously!!
Click to expand...
Click to collapse
Nope. The hope of root for this phone was crushed long ago. Almost time for everyone to get new ones.
I am going to upgrade my phone from lg v10 to v20. Can you confirm me that is every lg v20 mobile carrier version ROOTABLE or i should buy a specific version?
SH4DOW ASSASSIN said:
I am going to upgrade my phone from lg v10 to v20. Can you confirm me that is every lg v20 mobile carrier version ROOTABLE or i should buy a specific version?
Click to expand...
Click to collapse
Don't do it. I'm done with LG. But a pixel or something, they are much better.
Hi guyzz I think I've found a solution to the following problems:
1. VS990 board with H900 or H901 software.
2. Settings app crashes, Fingerprint sensor doesn't work, uninstalling an app causes soft boot
But I need help. So anyone willing please comment below.
P.S. as usual this is an experimental solution, so please try at your own risk.
Step 1: I need someone to put their phone in [Qualcomm HS-USB QDLoader 9008], because to my understanding this is the lowest level hardware control for the emmc in qualcomm evices.
Step 2: Once in this mode we need to follow the qfil solution to recover from the hardbrick and install the VS990 software.
But as I'm new to this, I've only found one way of entering the mode. (can't add the image due to xda restrictions -_- please help me with posting the image link )
If there is a software way to do this too, please comment below.
I have the same problem.
I tried many solutions but nothing better.
What is your solution ?
lukskajwoker said:
I have the same problem.
I tried many solutions but nothing better.
What is your solution ?
Click to expand...
Click to collapse
Hi, sorry for the late reply. But my solution is very very risky. It involves willingly hard bricking your phone and just flashing the device with VS990 software using the Q-fil method. But I need testers to actually prove that it works in general and not just on my phone.
But as I mentioned it is very very dangerous. So, unless you have the phone just lying around; I wouldn't suggest it.
OK,
I would try. Now phone is usless.
Mouldydroid said:
Hi, sorry for the late reply. But my solution is very very risky. It involves willingly hard bricking your phone and just flashing the device with VS990 software using the Q-fil method. But I need testers to actually prove that it works in general and not just on my phone.
But as I mentioned it is very very dangerous. So, unless you have the phone just lying around; I wouldn't suggest it.
Click to expand...
Click to collapse
Ok, what is it?
I'm more than willing to try.
I also have to mention that the ARB is not just in the system, it's also somehow modifying the hardware. I have 2 H900 (both are VS990) boards. One of them is 5.1 rooted, the other is H90021w. I put the 5.1's emmc on the other board and not working. Then I flash the H90021w on the former 5.1's emmc, the phone is working. I won't put the H90021w emmc to the other board as it will ruin the board.
Note: I have a medusa pro box, so I can flash the 90021w anytime if it's bricking.
Mouldydroid said:
Hi, sorry for the late reply. But my solution is very very risky. It involves willingly hard bricking your phone and just flashing the device with VS990 software using the Q-fil method. But I need testers to actually prove that it works in general and not just on my phone.
But as I mentioned it is very very dangerous. So, unless you have the phone just lying around; I wouldn't suggest it.
Click to expand...
Click to collapse
I think some of us are ready.
I am ready to do this, translate in 9008 if still relevant,
skype:zlocontrol
lg v10 h900&901
Hey, I'm really interested on how this turns out.
So from what I'm understanding, the idea is to get the LG V10 AT&T software flashed (with verizon motherboard) into usb qloader mode, and then to flash the verizon software or the original LG V10 H900 unto it?
I'd say its worth a go, but I don't have a medusa box in case it goes wrong ^^
Theamerix said:
Hey, I'm really interested on how this turns out.
So from what I'm understanding, the idea is to get the LG V10 AT&T software flashed (with verizon motherboard) into usb qloader mode, and then to flash the verizon software or the original LG V10 H900 unto it?
I'd say its worth a go, but I don't have a medusa box in case it goes wrong ^^
Click to expand...
Click to collapse
I've try the very possible way I can think of.
I've take out the EMMC and put a H900 lollipop inside it, not working. Not even any other FW will working, whether VS990 or H901, not after we put H90021w on it. And if I put that EMMC with android 5.1 on another VS990 board, which H90021w is never run on it, it's working fine.
I really suspect the ARB of H90021w is making physical changes on the board, and then only H90021w will working and probably newer FW too. I think that's our only chance. If we can find someone with newer FW willing to help, we can try it. Please check https://forum.xda-developers.com/att-lg-v10/general/calling-help-h90021z-h90022b-firmware-t3881691
Hi and thanks for the support. But due to utter desperation I got rid of the phone about 3 months ago. Now here is all of my research.
1. Get into HS USB mode by holding down both vol up+down....
2. Get QFIL to flash and it should work... P.S. flash proper ones... also dont flash versions below the one that it got messed up with
P.S. I did have a guy try out the board pinching method to get into HS USB... and somehow he got into fastboot and then I got out of contact with him
Mouldydroid said:
Hi and thanks for the support. But due to utter desperation I got rid of the phone about 3 months ago. Now here is all of my research.
1. Get into HS USB mode by holding down both vol up+down....
2. Get QFIL to flash and it should work... P.S. flash proper ones... also dont flash versions below the one that it got messed up with
P.S. I did have a guy try out the board pinching method to get into HS USB... and somehow he got into fastboot and then I got out of contact with him
Click to expand...
Click to collapse
Thanks..
But the problem is, there's no newer KDZ than H90021w around.
ardian1899 said:
Thanks..
But the problem is, there's no newer KDZ than H90021w around.
Click to expand...
Click to collapse
I know.... but my solution was... as you get into EDL mode all security goes to hell (theoretically) so theoretically you should be able top flash the original ROM that was meant for that specific motherboard, and not the one that was eventually installed during refurbish process
Now technically this should get rid of the unable to uninstall apps and the fingerprint bug....
Mouldydroid said:
I know.... but my solution was... as you get into EDL mode all security goes to hell (theoretically) so theoretically you should be able top flash the original ROM that was meant for that specific motherboard, and not the one that was eventually installed during refurbish process
Now technically this should get rid of the unable to uninstall apps and the fingerprint bug....
Click to expand...
Click to collapse
Maybe.. but the option is very limited on H900. And if we flash the H90021w firmware, there;s no way back.
Basically I really suggest anybody outside US to avoid buying an AT&T phones.
I need to add. Contrary to many believe here, motherboard with VS990 code may not only for verizon, but Tmo and AT&T as well. I've open many V10's board, not once I found H901 or H900 printed on the motherboard (many VS990 and a few F600). Even those H901 which working normally and able to run on the latest official nougat KDZ, are on VS990 boards too.
ardian1899 said:
I need to add. Contrary to many believe here, motherboard with VS990 code may not only for verizon, but Tmo and AT&T as well. I've open many V10's board, not once I found H901 or H900 printed on the motherboard (many VS990 and a few F600). Even those H901 which working normally and able to run on the latest official nougat KDZ, are on VS990 boards too.
Click to expand...
Click to collapse
Is there a way to identify for what deviceversion the version of VS990 board one might have really is.
i just ordered an lg v20 at&t model, and would like to know how to either update it or convert it to the unbranded version, as I am from the UK. Is it also possible it can be done without root, and by just using the software flashing tool?
thanks
sol.j146 said:
i just ordered an lg v20 at&t model, and would like to know how to either update it or convert it to the unbranded version, as I am from the UK. Is it also possible it can be done without root, and by just using the software flashing tool?
thanks
Click to expand...
Click to collapse
Yeah, grab yourself the modded version of LGUP, download the KDZ (Most likely US996) and flash it. No root involved.
I'm in the same boat as the OP, in the UK.
I broke my International version HD990DS which I've had for a couple of years, and scored a replacement H910 on ebay (£115, sealed in box, 2019 date on battery). I received it this morning.
I wasn't aware when I bought it that it was an AT&T brand (unlocked), on Android 7, and un-updateable OTA here in the UK.
The kdz I'm downloading is 'US99620f_00_1120.kdz' from here: https://www.mylgphones.com/unlocked-lg-v20-us996-received-oreo-update-us99620f.html
Should this be good to go? I'm not aware what bands this enables. The bands EE use here are 1,3,7 & 20.
Is there a 'better' kdz I should be downloading?
TIA.
[edit] further to the above, for any UK EE users, the page here gives EE APN details which will need inputting if your phone isn't going to be a wifi only paperweight. Other operators and phones are listed in the site:
https://apn-uk.gishan.net/en/apn/ee/lg-v20
In this page you'll note EE does not support the H915 for 4G at all.
The H910 isn't listed, but it is supported for 4G by EE.[/edit]
Excudent said:
Yeah, grab yourself the modded version of LGUP, download the KDZ (Most likely US996) and flash it. No root involved.
Click to expand...
Click to collapse
Modded LGUP says : "Error:KDZ file is invalid' H910->US996"
I wish it had been that simple....
Anyone any pointers?
stateit said:
Modded LGUP says : "Error:KDZ file is invalid' H910->US996"
I wish it had been that simple....
Anyone any pointers?
Click to expand...
Click to collapse
to flash cross model use partition dl mode, select all partitions. iirc
(not applicable to you specifically, but as a reminder to anyone else who reads this)
Remember, never ever flash (T-mobile) H918 firmware on anything but an H918, and if you have an H918 never ever flash another model's firmware. Instant permanent brick.
Thanks for your input. I'll give it a go tonight.
With LGUP does "DUMP" fo a restorable backup?
I've not used LGUP before a couple of days ago. I used to use Odin a lot, but that was years ago (see my forum join date...)
[edit] OK, I've found what I need to know about LGUP here: https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/ [/edit]
stateit said:
Thanks for your input. I'll give it a go tonight.
With LGUP does "DUMP" fo a restorable backup?
I've not used LGUP before a couple of days ago. I used to use Odin a lot, but that was years ago (see my forum join date...)
[edit] OK, I've found what I need to know about LGUP here: https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/ [/edit]
Click to expand...
Click to collapse
Did you manage to get oreo on H910? My mother has a H910 stuck in Nougat, but I'd like her to get the oreo update without having to mess with root or anything hard for her to use.
Not yet... I'm waiting until I've had the crap annoyed out of me enough before I invest the few hours time to put everything back on this phone that I want.
As all partitions have to be rewritten then its a case of starting from a totally fresh phone. Which is a chore that I'll do sometime, but not until this week at least is of the way....
Salvaparalyzer said:
Did you manage to get oreo on H910? My mother has a H910 stuck in Nougat, but I'd like her to get the oreo update without having to mess with root or anything hard for her to use.
Click to expand...
Click to collapse
Lgup patched linked above using partial download you can load Oreo from us996 or h915. H915 = H910 only Canadian version with respective network software.
Salvaparalyzer said:
Did you manage to get oreo on H910? My mother has a H910 stuck in Nougat, but I'd like her to get the oreo update without having to mess with root or anything hard for her to use.
Click to expand...
Click to collapse
I'm using H91520a_00_RGS_CA_OP_0717.kdz
Downloaded from LG-Firmwares here: https://lg-firmwares.com/downloads-file/...
IIRC it was the world's slowest download, reminiscent of using a dial-up modem (well, almost).
The H915 is the canadian version of the US H910, so no worries about hardware incompatibilities
Update in patched LGUP (using 'partitions.dl' option) took about 5 minutes and was painless (one warning screen popped up at start of f/w update process in LGUP saying USB was disconnected, but I ignored this throughout the update and left it showing) .
APN numbers need to be added
I backed up data (phone logs, messages etc) first in LG Mobile Switch app first, saving to SD Card. Which I took out of the phone first before the update 'just in case'.
No more AT&T crap, and Android 8.0.0, which is back to how my last V20 990DS was before I broke it (water damage).
It's a bargain phone for £120 on eBay. Good luck!
There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Dishe said:
There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Click to expand...
Click to collapse
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
loonycgb2 said:
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Click to expand...
Click to collapse
Wow, that's some good info right there, thank you for sharing!
Hmm- messing with nvdata though? So you're saying the SN missing is some sort of accident or goof? That doesn't sound so cool. Should I be concerned anything else is messed up? There's a ton of these in the wild now and it seems the SN is the only weird side effect that has been noticed.
As far as I know the IMEI is fine (looking it up reveals it is a PM imei, which is correct, and it does work with voice over Wifi and VOLTE, which I think wouldn't work if the IMEI was messed up). In fact, it's interesting because when that screen loads in Settings>About, etc, it shows "checking" under S/N, then checking goes away and it comes back blank. None of the other fields seem to need any sort of checking first. There's something fishy about how the S/N is stored that it has to check it first and then error out.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Click to expand...
Click to collapse
Hmm. It came with Oreo, and I used 1.15 to flash to Pie. So you're saying I should flash another Oreo kdz with my LGUP and it will magically fix any corrupt NVdata?
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
Click to expand...
Click to collapse
Oh, that is unfortunate. And that value stays with it forever, even if you go back to it's native firmware? I'm assuming that value can't be manipulated with any of the tools we have available.
Thank you so much for sharing this knowledge. Any insight on how the bands work? Is that from nvdata as well, and completely independent of firmware? So essentially, I have whatever band support a G710pm has? Or perhaps was it manipulated by the seller/refurbisher, who possibly used some nvram voodoo tricks which killed the S/N as a result?
Even tho the s/n is blank and at time if you try to show the imei it might also be blank, it is still stored internally and not lost forever.
There is multiple oreo's which for ulm is 10g and 11g, but i would have said flash to the original firmware but you cannot as sprint kdz is not available and the people who have an Original firmware still on device cannot or will not back it up for us.
The value for certified device returns to normal when flashed to the original firmware as lgup has an internal database used for identifying models.
As far as the basebands, all g7 thinq's come with the same bands no matter the firmware or region. The difference is the kdz gives band priority to the ones prefered by the carrier.
All of that can be changed by getting into the lg data secret menu or the dialer code menu
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
netookska05 said:
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
Click to expand...
Click to collapse
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
netookska05 said:
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
Click to expand...
Click to collapse
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
loonycgb2 said:
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
Click to expand...
Click to collapse
Can you please elaborate for those unfamiliar with this?
Dishe said:
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
Can you please elaborate for those unfamiliar with this?
Click to expand...
Click to collapse
Using TWRP to create a backup of efs. Sometimes the restore is faulty.
EFS partition holds up the unique IMEI number of the device, also other identifying numbers like MAC address, MEID, and ESN are stored up in this partition.
Check you IMEI with this.
https://imeipro.info/check_lg.html
To get your sn.
Oh ok.
So I don't actually need to know my SN but I'd like it to not be blank if flashing back to a previous version would restore it... Especially if there are possibly other parts of nvram that may be corrupt that I'm unaware of?
Thanks for the info. The one I got said it can't work on Sprint or Verizon networks, and is missing the serial #, as you said.
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
vishal198900 said:
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
Click to expand...
Click to collapse
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
I just got a 710pm off ebay. I unlocked the bootloader, crossflashed to ulm pie, and rooted. It works just fine. [emoji106]
Sent from my LM-G710 using Tapatalk
netookska05 said:
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Click to expand...
Click to collapse
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
netookska05 said:
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
Click to expand...
Click to collapse
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
vishal198900 said:
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
Click to expand...
Click to collapse
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
netookska05 said:
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
Click to expand...
Click to collapse
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
vishal198900 said:
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
Click to expand...
Click to collapse
Yes it will work.
I'd also like to add that Google Pay will not work, at retail brick and mortar stores.
A pop up says device may be rooted or modified.
I have magisk installed and it seems to trick Schwab banking app.
Edit:
Edit: I followed the instruction from the following video, and was able to get GPay to accept the card. Also Gpay needs to be manually hidden in magisk, be sure to select 'display system apps' to find it.
https://www.youtube.com/watch?v=wKYC0r-m0Mo
Click to expand...
Click to collapse
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
captain barbosa said:
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
Click to expand...
Click to collapse
If you're on Pie, I doubt you have one of these Sprint phones. Check if you pass SafetyNet and if so, you have a native ULM model. Most G7 variants receive very few updates (including the ULM).