Guide: Returning to stock firmware + re-lock bootloader.
NOTE: following this guide will factory reset your phone so back up your data before hand.
Hi all, after having to do a fair bit of digging around last night in order to return my G7 to stock firmware i
figured i would make a all in one guide to make it a bit easier for people to follow!
First half of this guide is how to re-flash stock firmware:
1. Download LGUP here:Link
1.1 Download additional file we will need later: Link
1.2 Download stock KDZ file: Link
2. Install LGUP, after it has been installed extract the file from step 1.2 and place it here:
"C:\Program Files (x86)\LG Electronics\LGUP\model\common"
You will most likely have to create the common folder first and then place the file "LGUP_Common.dll" inside, this allows the LGUP software to recognise the device.
3. Next power down your device, once it is fully powered off hold the volume up key and insert the USB cable into your device
while continuing to hold volume up, continue to hold until your device enters download mode.
4. Open the LGUP software and drag the KDZ file into the file path section within the software, if your device is not showing
it means you dont have the correct drivers installed or haven't placed the .dll file from step 2 in the correct place.
5. Once the KDZ file is showing in LGUP simply click start and wait for the stock firmware to flash! Once it has completed
your device will reboot!
6. (Optional) download and install LG Bridge and check for any software updates after the flash has completed, OTA updates
can also be checked but in my experience it didnt show any updates where as LG Bridge did.
Second half of this guide will be how to re-lock the bootloader:
1. Download and install Android ADB + Fastboot drivers. The best guide I've found for this can be seen here:Link
2.Navigate to the folder where you have ADB and fastboot installed, usually this folder will be called platform tools.
hold shift and right click inside the folder then select "open powershell window here". Next make sure USB debugging is
enabled in developer settings and then head back to your powershell window and enter the following commands in order:
"adb reboot bootloader"
"fastboot oem lock"
"fastboot reboot"
3. Your phone will reboot and go through the usual first time start up, make sure to enable developer options again and
un-checking "OEM unlock". Your bootloader is now locked again!
If you followed the above steps you should now be back to complete stock! Enjoy
I think it's better to flash stock firmware first to avoid problems when relocking the bootloader, because locking the bootloader just erases /data and /cache, and if you have some modifications like root or twrp it could cause a bootloop.
What I do is first flash stock and then relock the bootloader, with that order you will prevent any problems after relocking.
mprovi_15 said:
I think it's better to flash stock firmware first to avoid problems when relocking the bootloader, because locking the bootloader just erases /data and /cache, and if you have some modifications like root or twrp it could cause a bootloop.
What I do is first flash stock and then relock the bootloader, with that order you will prevent any problems after relocking.
Click to expand...
Click to collapse
Thanks for the advice mate, I've updated the post and switched the order
Can you use this guide to flash different carrier firmware on device?
mrpickem said:
Can you use this guide to flash different carrier firmware on device?
Click to expand...
Click to collapse
You can always try! I would probably recommend sticking to the firmware from your carrier though just to be on the safe side. If worst comes to worst you can always use this guide again to re-flash your carrier specific firmware if you find you are having issues! Let me know how you get on if you do try or need any help
camy25695 said:
You can always try! I would probably recommend sticking to the firmware from your carrier though just to be on the safe side. If worst comes to worst you can always use this guide again to re-flash your carrier specific firmware if you find you are having issues! Let me know how you get on if you do try or need any help
Click to expand...
Click to collapse
Thanks
I have been reading a bit and apparently there are different modems used between carriers. I currently have an unlocked Tmobile device and was wanting to flash the unlocked firmware...just dont want to risk bricking the phone. The phone works ok with tmobile fw, just wanted to get rid of bloat since I am now using it on ATT prepaid. Can find no info where anyone has done this. I 've flashed several Galaxy phones (to diff f/w)recently and Moto G's a few years back and it worked great.
mrpickem said:
Thanks
I have been reading a bit and apparently there are different modems used between carriers. I currently have an unlocked Tmobile device and was wanting to flash the unlocked firmware...just dont want to risk bricking the phone. The phone works ok with tmobile fw, just wanted to get rid of bloat since I am now using it on ATT prepaid. Can find no info where anyone has done this. I 've flashed several Galaxy phones (to diff f/w)recently and Moto G's a few years back and it worked great.
Click to expand...
Click to collapse
I know it's possible to flash the boot.img seperate, as I've done that already myself but I'm unsure about flashing a different modem. I imagine the process will be very similar to flashing the boot but I'd need to do some digging and find out exactly! Even if you could there's no guarantee that it would work. I'll do some digging and see what I can find and get back to you!
mrpickem said:
I have been reading a bit and apparently there are different modems used between carriers. I currently have an unlocked Tmobile device and was wanting to flash the unlocked firmware...just dont want to risk bricking the phone.
The phone works ok with tmobile fw, just wanted to get rid of bloat since I am now using it on ATT prepaid. Can find no info where anyone has done this. I 've flashed several Galaxy phones (to diff f/w)recently and Moto G's a few years back and it worked great.
Click to expand...
Click to collapse
Assuming LG has made the same decisions for the G7 as they did for the V30, the answer is no.
At least on the V30 series, T-mobile variant can NOT be flashed to anything else because it has different RSA encryption keys from any other V30 phone. This is why back in May when we found the wonderful LG Oreo bootloader unlock exploit, every V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Someone with a G7 came in to the V30 Frankenstein thread to ask if it works on G7, but that seems like something that should be discussed in this forum.
ChazzMatt said:
Assuming LG has made the same decisions for the G7 as they did for the V30, the answer is no.
At least on the V30 series, T-mobile variant can NOT be flashed to anything else because it has different RSA encryption keys from any other V30 phone. This is why back in May when we found the wonderful LG Oreo bootloader unlock exploit, every V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Someone with a G7 came in to the V30 Frankenstein thread to ask if it works on G7, but that seems like something that should be discussed in this forum.
Click to expand...
Click to collapse
Thanks for the reply and that's kinda what what I been reading, just not as much detail. Thanks for detailed explanation
ChazzMatt said:
Assuming LG has made the same decisions for the G7 as they did for the V30, the answer is no.
At least on the V30 series, T-mobile variant can NOT be flashed to anything else because it has different RSA encryption keys from any other V30 phone. This is why back in May when we found the wonderful LG Oreo bootloader unlock exploit, every V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Someone with a G7 came in to the V30 Frankenstein thread to ask if it works on G7, but that seems like something that should be discussed in this forum.
Click to expand...
Click to collapse
Ok what about flashing the European LMG710EM firmware onto the Sprint G7? Would i risk bricking my device? Im trying to find a solution to unlocking my sprint phone
mastervideogamer79 said:
Ok what about flashing the European LMG710EM firmware onto the Sprint G7? Would i risk bricking my device? Im trying to find a solution to unlocking my sprint phone
Click to expand...
Click to collapse
did you try flashing G710EM firmware in the sprint g7? i also have a sprint variant and want to unlock it.
UPDATE: just tried to flash it but lg up doesnt even start flashing the kdz file, it gives "LAF WRITE PROTECTION" and "Cross flash is not supported" messages
luckily phone is working just fine with the original software, i mean it didnt bricked the phone since it didnt even started to flash.
in other post i saw a user that tried flashing tmobile firmware with lg v20 dll and bricked his sprint g7
elmy24 said:
did you try flashing G710EM firmware in the sprint g7? i also have a sprint variant and want to unlock it.
UPDATE: just tried to flash it but lg up doesnt even start flashing the kdz file, it gives "LAF WRITE PROTECTION" and "Cross flash is not supported" messages
luckily phone is working just fine with the original software, i mean it didnt bricked the phone since it didnt even started to flash.
in other post i saw a user that tried flashing tmobile firmware with lg v20 dll and bricked his sprint g7
Click to expand...
Click to collapse
Oh man thats why I didnt want to risk it but thanks for trying. Haven't found a way to unlock it, phones just sitting there
Hi everyone,No-one haven't successful crossflash the lg g7,I have the verizon g7 variant I would like to flash it to a different carrier.,
elmy24 said:
did you try flashing G710EM firmware in the sprint g7? i also have a sprint variant and want to unlock it.
UPDATE: just tried to flash it but lg up doesnt even start flashing the kdz file, it gives "LAF WRITE PROTECTION" and "Cross flash is not supported" messages
luckily phone is working just fine with the original software, i mean it didnt bricked the phone since it didnt even started to flash.
in other post i saw a user that tried flashing tmobile firmware with lg v20 dll and bricked his sprint g7
Click to expand...
Click to collapse
I am getting same error. I have sprint LG g7. Trying to flash canadian AWM rom.
I followed this tutorial in my LG G7 variant model LM-G710EMW and works. Now, I'm downloading the specific firmware in lg-firmwares.com to install with this method.
I bought my LG G7 in Brazil, with CLARO mobile operator and now I have a LG G7 without bond. Thanks for this tutorial!
With this guide warranty come back?
mastervideogamer79 said:
Oh man thats why I didnt want to risk it but thanks for trying. Haven't found a way to unlock it, phones just sitting there
Click to expand...
Click to collapse
akyl001 said:
I am getting same error. I have sprint LG g7. Trying to flash canadian AWM rom.
Click to expand...
Click to collapse
just found a way to unlock the sprint variant by flashing european rom
elmy24 said:
just found a way to unlock the sprint variant by flashing european rom
Click to expand...
Click to collapse
You should make a post verifying the way you did it and giving proof of this happening. If you do it you will help a lot of people, and maybe it will help other variants to reach root.
How can I solve the "unsecure flashing image to secure flashing device" problem?
Eltoniz said:
How can I solve the "unsecure flashing image to secure flashing device" problem?
Click to expand...
Click to collapse
model number?
software version?
is it KDZ or TOT firmware?
Related
This is an unlocked T-Mobile G5, but why have a special ROM for unlocked phone? I wonder if I flash other ROMs, I could lose the unlock. Anyone have any problem rooting and install twrp?
Conclusion after a month long discussion:
G5 with H83020i_un ROM is NOT factory unlock. Upgrading or downgrading will result in SIM lock to T-Mobile, period.
Once locked, it can only be unlocked by T-Mobile customers via T-Mobile unlocked app. Some has to go thru T-Mobile customer service and request SIM unlock by adding IMEI to their database.
I bought 6 (New to New other) unlocked H830 and 2 has the hacked ROM H83020i_un and 4 were completely locked to T-Mobile. Yes, those stupid sellers on ebay just keep sending lock phones as unlocked phone! Good luck getting a unlocked one.
No, you cannot install TWRP or root this version.
I ended up returning mine.
You shouldn't lose the unlock by flashing another ROM.
A ROM isn't just about 'locked or unlocked'. The ROM is the operating system. While it will still be Android no matter what you do, different ROMs are modified differently to provide additional features, or more control over the settings or just a slightly different user interface.
This has NOTHING to do with the phone being unlocked for use on any GSM network.
For example some people want to be able to control the CPU processor speed on the phone more. Some ROM's give you that control built into the settings and use customer kernels that allow the CPU to run faster than it does running stock. Other people just like a more simple UI that you get on base Android ROM's (rather than some of the overlays LG puts on)
Skipjacks said:
You shouldn't lose the unlock by flashing another ROM.
A ROM isn't just about 'locked or unlocked'. The ROM is the operating system. While it will still be Android no matter what you do, different ROMs are modified differently to provide additional features, or more control over the settings or just a slightly different user interface.
This has NOTHING to do with the phone being unlocked for use on any GSM network.
For example some people want to be able to control the CPU processor speed on the phone more. Some ROM's give you that control built into the settings and use customer kernels that allow the CPU to run faster than it does running stock. Other people just like a more simple UI that you get on base Android ROM's (rather than some of the overlays LG puts on)
Click to expand...
Click to collapse
I can't confirm this personally, but @autoprime mentioned on IRC that everyone who tried flashing other KDZs over this specific firmware lost the SIM unlock.
BehindTheMath said:
I can't confirm this personally, but @autoprime mentioned on IRC that everyone who tried flashing other KDZs over this specific firmware lost the SIM unlock.
Click to expand...
Click to collapse
So we can't flash this device?
dkyu said:
So we can't flash this device?
Click to expand...
Click to collapse
Well, technically you can, but as of now it sounds like you'd lose the SIM unlock.
BehindTheMath said:
Well, technically you can, but as of now it sounds like you'd lose the SIM unlock.
Click to expand...
Click to collapse
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
It seems that this is not a regular unlock. When I open the T-Mobile app, it says the phone is still locked, but it works anyway.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
I just tried downgrading to 20A and lost the SIM unlock.
BehindTheMath said:
I just tried downgrading to 20A and lost the SIM unlock.
Click to expand...
Click to collapse
Did you confirm that by trying the phone with a non T Mobile SIM on a different network? Or did you just let the T Mobile unlocker app tell you it's still locked?
The app isn't the most reliable thing in the world. It's known to say it's not unlocked when it is or that it can't be unlocked when it already is. Etc etc...
Unlocking it manually (through codes, ADB, root, etc....) messes with the unlocker app. But the unlock itself should still be valid.
Skipjacks said:
Did you confirm that by trying the phone with a non T Mobile SIM on a different network? Or did you just let the T Mobile unlocker app tell you it's still locked?
The app isn't the most reliable thing in the world. It's known to say it's not unlocked when it is or that it can't be unlocked when it already is. Etc etc...
Unlocking it manually (through codes, ADB, root, etc....) messes with the unlocker app. But the unlock itself should still be valid.
Click to expand...
Click to collapse
I took the active H2o (At&t MVNO) SIM from my current device and tried it in this one. I could not make phone calls or access data, both in stock 20A and Resurrection Remix.
BehindTheMath said:
I took the active H2o (At&t MVNO) SIM from my current device and tried it in this one. I could not make phone calls or access data, both in stock 20A and Resurrection Remix.
Click to expand...
Click to collapse
that's sucks.
I wonder if you can actually get an unlock code to unlock the phone now.
dkyu said:
that's sucks.
I wonder if you can actually get an unlock code to unlock the phone now.
Click to expand...
Click to collapse
If I'm not mistaken, you can't unlock this phone with an unlock code.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
Maybe it is something to the specific phones people are getting from the ebay seller. They are being sold as new yet are not factory sealed and missing the Tmo sim card. People are claiming Android pay doesn't work and the phone isn't rooted. A new out of the box phone shouldn't have that issue. So something isn't necessarily kosher.
Guys, I have the same version (H83020i_un) and it has April security update and T-Mobile has different version #s on their website. I have checked for update, but nothing came up. So I can't get T-Mobile updates?
The software version H83020i_un is apparently not an official ROM released by T Mobile or LG.
There is a lot of speculation on Slickdeals (a website for coupons and stuff where this eBay deal has been discussed quite a bit) that the unlock was done by flashing a modified ROM. If so that would explain why flashing a new ROM loses the unlock.
Additionally people are saying that Android Pay doesn't work on this phone with that software update, presumably because it's not official firmware. I've never used Android Pay so I have no idea if it works or not.
All in all if you have the H83020i_un software and bought the phone 'new' I think you got conned. It's not new and that seems to be unofficial software.
I spent a lot of time, with help from @autoprime, trying to figure out where the unlock is stored. I was able to dump the partitions from 20i_un using the method here. After I downgraded to 20A and flashed TWRP, I flashed back all the 20i_un partitions (besides recovery, cache, and userdata), and it still wasn't unlocked. So I'm baffled as to how the unlock works.
Skipjacks said:
The software version H83020i_un is apparently not an official ROM released by T Mobile or LG.
There is a lot of speculation on Slickdeals (a website for coupons and stuff where this eBay deal has been discussed quite a bit) that the unlock was done by flashing a modified ROM. If so that would explain why flashing a new ROM loses the unlock.
Additionally people are saying that Android Pay doesn't work on this phone with that software update, presumably because it's not official firmware. I've never used Android Pay so I have no idea if it works or not.
All in all if you have the H83020i_un software and bought the phone 'new' I think you got conned. It's not new and that seems to be unofficial software.
Click to expand...
Click to collapse
I see. It will be used as a second device, so it is fine. I flashed the phone with stock T-Mobile H83020a, then got few OTA updates. Now my phone has H83020i, but T-Mobile's page(below) shows an "f" version as the latest. So is the H83020i, the latest update or not? Also would be good if anyone with real T-Mobile unit could chime in.
https://support.t-mobile.com/docs/DOC-30673
BehindTheMath said:
I spent a lot of time, with help from @autoprime, trying to figure out where the unlock is stored. I was able to dump the partitions from 20i_un using the method here. After I downgraded to 20A and flashed TWRP, I flashed back all the 20i_un partitions (besides recovery, cache, and userdata), and it still wasn't unlocked. So I'm baffled as to how the unlock works.
Click to expand...
Click to collapse
And there is no way to root the phone without downgrading to 20A right?
Charkatak said:
I see. It will be used as a second device, so it is fine. I flashed the phone with stock T-Mobile H83020a, then got few OTA updates. Now my phone has H83020i, but T-Mobile's page(below) shows an "f" version as the latest. So is the H83020i, the latest update or not? Also would be good if anyone with real T-Mobile unit could chime in.
https://support.t-mobile.com/docs/DOC-30673
Click to expand...
Click to collapse
Looks like 20i is the latest.
https://forum.xda-developers.com/tm...ock-h830-20i-rom-flashable-zips-imgs-t3609735
dkyu said:
And there is no way to root the phone without downgrading to 20A right?
Click to expand...
Click to collapse
Correct.
BehindTheMath said:
Looks like 20i is the latest.
https://forum.xda-developers.com/tm...ock-h830-20i-rom-flashable-zips-imgs-t3609735
Correct.
Click to expand...
Click to collapse
So if 20i is the latest, then it is possible that T-Mobile's variant of the phone could have a different model # than H830...
So my s7 930u is here. I've found hundreds of methods on here and youtube and odin just fails..
Who has rooted their s7 930u android 7.0 phone. And what exact method did you use. This is getting ridiculous
tried this https://www.youtube.com/watch?v=KawiIZ4bAV8
annnnnnnd now my phone is bootlooped
im flashing 7.0 stock firmware (latest update) with odin 3.12.10
seemed to be the only odin that flashed bl + ap + cp + csc correctly for me
if anyone has the latest method used to root this phone id greatly appreciate a link or tut
removed
removed
Since the US models have a locked bootloader, it's much harder to root than international. I think they'll reject anything from Odin that isn't official firmware.
You might have more luck in the US/Snapdragon specific sections of the forums, near the bottom: https://forum.xda-developers.com/galaxy-s7
Beanvee7 said:
Since the US models have a locked bootloader, it's much harder to root than international. I think they'll reject anything from Odin that isn't official firmware.
You might have more luck in the US/Snapdragon specific sections of the forums, near the bottom: https://forum.xda-developers.com/galaxy-s7
Click to expand...
Click to collapse
I thought oem unlock was unlocking the bootloader? I can simply do that in developer options.
OEM unlock as in the developer settings menu? That toggle only works on Exynos (930F/FD/W8) devices, on Snapdragon (930U/V/T/P/A) it doesn't actually do anything. SD bootloader has and likely will always be hard locked.
Beanvee7 said:
Since the US models have a locked bootloader, it's much harder to root than international. I think they'll reject anything from Odin that isn't official firmware.
You might have more luck in the US/Snapdragon specific sections of the forums, near the bottom: https://forum.xda-developers.com/galaxy-s7
Click to expand...
Click to collapse
Beanvee7 said:
OEM unlock as in the developer settings menu? That toggle only works on Exynos (930F/FD/W8) devices, on Snapdragon (930U/V/T/P/A) it doesn't actually do anything. SD bootloader has and likely will always be hard locked.
Click to expand...
Click to collapse
So why all the tutorials and YouTube videos on all the different methods of rooting snapdragon s7 if the bootloader doesn't unlock for root. Wtf
I've never watched them so I can't say, but I would assume they would use round about methods to do it? For example Exynos is simply flash TWRP on with Odin, then flash a SU zip.
Do the youtube videos tell you to do that with the snapdragon models, or is it some arbitrary multi step process? The only way I can imagine rooting Snapdragon is exploiting security flaws. I've also seen mentions of flashfire but I don't know what it does.
Like I said you'd have better luck going to the AT&T/T-mobile/Verizon etc sections. This area of the forum is mostly for Exynos.
I don't even know what this phone classifies under.
It was a Verizon phone, with Verizon logo on back.
Unlocked.
Now it's on TMobile Network.
aarongotgame said:
I don't even know what this phone classifies under.
It was a Verizon phone, with Verizon logo on back.
Unlocked.
Now it's on TMobile Network.
Click to expand...
Click to collapse
Isn't there a method to unlock a bootloader?
Carrier unlocked just means you can use it on any carrier network, which is you've got.
But bootloader lock is at a firmware level, and can't be done for any US model S7.
Since all the US models are basically the same, any guide in any of their sections should work for any other model. Yours is a G930V but you can use any guide or firmware from any other US model S7.
You need to root using an engineering bootloader. Not sure if there's a version compatible with the latest update.
You will have problems, as eng BL is not stable, and your battery will not charge past 80%.
So basically is really difficult/impossible Root a 930u? and more difficult flash with a custom firm?
Investigating because just buy a Samsung S7 gm-930u and want to debloat it.
How can i know if is a snapdragon? I am on new zealand not US.
Rooting is difficult, flashing custom firmware, as in a ROM is basically impossible on snapdragon SoC's. With a locked bootloader you can't modify the boot image which is needed for ROMs.
To check your model boot into download mode by turning it off, then pressing and holding vol down + home + power. In there it will tell you your model, being in new zealand you should be on a SM-G930F or FD unless you grey imported.
Same button combo for ~10 secs gets you out of download mode.
Yes is the grey and is 930U pitifully.
So I should sell it and buy another one haha
Thanks for the advice.
Come on you good guys and let's root and custom rom this device.
What I'd really love is for someone to work out how we can use root to insert the settings needed for VoLTE and VoWoFi on UK networks (seeing as LG refuse to enable it for the UK)
Sent from my LM-G710 using Tapatalk
stuclark said:
What I'd really love is for someone to work out how we can use root to insert the settings needed for VoLTE and VoWoFi on UK networks (seeing as LG refuse to enable it for the UK)
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
Why they refuse to enable it for UK? That is the reason why I can't find it in settings...
Boot-loader Unlock Available for TMG710TM
I still am waiting for being bale to unlock my T-mobile variant
Tetraguy said:
I still am waiting for being bale to unlock my T-mobile variant
Click to expand...
Click to collapse
Right I hope LG would let us but to be honest I highly doubt they will
Joe199799 said:
Right I hope LG would let us but to be honest I highly doubt they will
Click to expand...
Click to collapse
Things like that honestly makes me want to have gotten the Oneplus 6 instead because I love custom roms and building my own using AOSP, and to me it doesn't make sense how you can allow the same exact phone to be unlocked but not in all places, is annoying.
Tetraguy said:
Things like that honestly makes me want to have gotten the Oneplus 6 instead because I love custom roms and building my own using AOSP, and to me it doesn't make sense how you can allow the same exact phone to be unlocked but not in all places, is annoying.
Click to expand...
Click to collapse
I feel you homie it sucks, but that's how it is just gotta hope the lovely people here can figure something out, other than the lack of root I'm really enjoying this phone
Tetraguy said:
I still am waiting for being bale to unlock my T-mobile variant
Click to expand...
Click to collapse
Joe199799 said:
Right I hope LG would let us but to be honest I highly doubt they will
Click to expand...
Click to collapse
Won't happen the T-mobile variant G7. For the LG V30 H932, T-mobile not only stripped out the fastboot flash commands they also have different RSA encryption keys so you can't convert to another model (even temporarily) which has fastboot flash commands. They also did this for the LG G6 T-mobile, so I can't see them reversing course to help people who want to unlock bootloader and root.
Since back in May when we found the wonderful LG Oreo bootloader unlock exploit, every LG V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because they don't have fastboot flash commands and you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
ChazzMatt said:
Won't happen the T-mobile variant G7. For the LG V30 H932, T-mobile not only stripped out the fastboot flash commands they also have different RSA encryption keys so you can't convert to another model (even temporarily) which has fastboot flash commands. They also did this for the LG G6 T-mobile, so I can't see them reversing course to help people who want to unlock bootloader and root.
Since back in May when we found the wonderful LG Oreo bootloader unlock exploit, every LG V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because they don't have fastboot flash commands and you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Click to expand...
Click to collapse
That blows I literally don't have any other answer but that, I remember back in the day when Verizon was no go and T-Mobile were the easy phones to root. my my how the turntables. Fu**ing John Legere I thought he was all for unlocking bootloader's and was trying to talk to Samsung to not lock it down on the S6 or S7 a couple of years ago. Just F*** dude. Welp I'll live I honestly just miss viper4android and adaway, I've been doing fine with eqfy mixed with the stock EQ and Blokada but I wish it were root apps instead.
the 710TM does have Fastboot commands, I've already played around with them, such as "fastboot getvar device-id", "fastboot oem unlocked" give the bootloader locked status, you can even flash with fastboot to unlock the bootloader with "unlock.bin". Once LG gives 710TM owners the green light, they will give us the unlock.bin
Scotsman828 said:
the 710TM does have Fastboot commands, I've already played around with them, such as "fastboot getvar device-id", "fastboot oem unlocked" give the bootloader locked status, you can even flash with fastboot to unlock the bootloader with "unlock.bin". Once LG gives 710TM owners the green light, they will give us the unlock.bin
Click to expand...
Click to collapse
I really don't think LG will ever give us that green light, don't get me wrong I hope I'm wrong but I just don't see it happening
ChazzMatt said:
Won't happen the T-mobile variant G7. For the LG V30 H932, T-mobile not only stripped out the fastboot flash commands they also have different RSA encryption keys so you can't convert to another model (even temporarily) which has fastboot flash commands. They also did this for the LG G6 T-mobile, so I can't see them reversing course to help people who want to unlock bootloader and root.
Since back in May when we found the wonderful LG Oreo bootloader unlock exploit, every LG V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because they don't have fastboot flash commands and you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Click to expand...
Click to collapse
T-mo didnt demand this, If this was the case then all their devices would be the same way, I had the HTC10, None of the fastboot commands are stripped, everything is there.. you can even S/off and cross install.
and rebrand the phone........ If T-mo was at fault for the LG devices, then all would be the same way.. its only LG and LG only.. LG started doing that with the MM update on the V10 which screwed over everyone.
the only reason none of the other American devices outside the US unlocked version didnt do that.. because they didnt think anyone would be able to unlock it..
T-mo has always allowed you to unlock bootloader if OEM allows it...... This isnt T-mo its LG that has done it.. They dont want any US variant to have fastboot commands..
and since you found that Oreo Bug, you can be sure that futures devices and so on by LG will have that fixed...
This has always been LG that has done this to the American Market not US Carriers, Even the MOTO from T-mo is unlockable with full fastboot commands..................
Scotsman828 said:
the 710TM does have Fastboot commands, I've already played around with them, such as "fastboot getvar device-id", "fastboot oem unlocked" give the bootloader locked status, you can even flash with fastboot to unlock the bootloader with "unlock.bin". Once LG gives 710TM owners the green light, they will give us the unlock.bin
Click to expand...
Click to collapse
Fastboot commands are not fastboot flash commands.
All fastboot flash commands are stripped out. And T-Mobile has different RSA encryption, apparently per demand of T-Mobile.
T-Mobile LG G6, V30 and now G7.
---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------
Eliminater74 said:
T-mo didnt demand this, If this was the case then all their devices would be the same way,
I had the HTC10, None of the fastboot commands are stripped, everything is there.. you can even S/off and cross install.
and rebrand the phone........
T-mo has always allowed you to unlock bootloader if OEM allows it...... This isnt T-mo its LG that has done it.. They dont want any US variant to have fastboot commands..
and since you found that Oreo Bug, you can be sure that futures devices and so on by LG will have that fixed...
Click to expand...
Click to collapse
HTC 10 is 2016 phone. Things have changed since then. T-MOBILE is no longer dev friendly. You are living in the past.
T-Mobile even tweeted for the LG V30 you would NOT be able to unlock the bootloader. Yeah you can "fake" unlock it, but without fastboot flash commands you can't do anything with the "unlocked" bootloader. It's like having the keys to the car -- but there's no car.
We went through all this with the 2017 LG G6 and LG V30. Sorry you haven't kept up?
T-Mobile users who want root with V30 have to buy another North America variant and root it, and use on T-Mobile.
Yes, T-Mobile did demand the different RSA encryption or LG wouldn't have done it JUST for T-Mobile models.
Yes, LG stripped fastboot flash commands out of most of the North America carrier variants, but you can convert ALL those -- EXCEPT for the T-Mobile H932 -- to carrier unlocked model US998. The reason you can't do that with the T-Mobile H932 is because ONLY that model has different encryption keys than other North America variants. Why would LG do that for ONLY T-Mobile H932?
I used an unlock.bin from a V30 just to see if it would attempt to flash with "fastboot flash unlock unlock.bin", it attempted to flash but errored out because of wrong unlock.bin.
I've had this phone since launch with the hopes of rooting and being able to use other roms etc. but I've not attempted any of the guides posted on the g7 as almost all of them either exclude the verizon model or dont specifically detail the necessary changes to the guides for the verizon model. And yet other guides state the verizon model can indeed be unlocked and rooted however broken download links and multiple issues noted by users riddle the posts. Point in the right direction? Is there a clear step by step guide on going from a stock us verizon lg g7 to having an unlocked bootloader with root access? Or is this still impossible on this model?
The issue with Verizon model is that the fastboot is disabled by default, AFAIK. So try crossflashing another location's firmware or simply ULM (Unlocked). After that you will be able to get to fastboot but, again rooting phones isn't as easy as it used to be before. If you want I can write a dummy guide that explains every step of the procedure but I think most guides are mediocre and you can use them to unlock your phone/root if you have previous experience with newer devices. So try this first : https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303 to cross flash your phone. Then follow the guide here : https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-unlock-bootloader-root-g7s-t-mo-t4077105 . Feel free to ask me questions. Beware that you will lose all data so do your backup first. I can NOT help you if you brick your device, since I haven't bricked mine yet, but supposedly crossflash method should save your device in that case. Also make sure that your phone is unlocked by Verizon before attempting any of this since you may lose network connectivity. Cheers.
Root T-mobile lgg7
Thank you for your explanation on root for the Verizon model. Can I root my T-MOBILE LG-G7 without erasing everything? I have about 6 GB of photos and videos on my internal memory I wish to recover!
marstonpear said:
The issue with Verizon model is that the fastboot is disabled by default, AFAIK. So try crossflashing another location's firmware or simply ULM (Unlocked). After that you will be able to get to fastboot but, again rooting phones isn't as easy as it used to be before. If you want I can write a dummy guide that explains every step of the procedure but I think most guides are mediocre and you can use them to unlock your phone/root if you have previous experience with newer devices. So try this first : https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303 to cross flash your phone. Then follow the guide here : https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-unlock-bootloader-root-g7s-t-mo-t4077105 . Feel free to ask me questions. Beware that you will lose all data so do your backup first. I can NOT help you if you brick your device, since I haven't bricked mine yet, but supposedly crossflash method should save your device in that case. Also make sure that your phone is unlocked by Verizon before attempting any of this since you may lose network connectivity. Cheers.
Click to expand...
Click to collapse
It gives an error download fail:firehose fail......
As said befor... Wooting will wipe everyting. Just make a backup... Upload it to Google drive or somting
Artaid said:
Thank you for your explanation on root for the Verizon model. Can I root my T-MOBILE LG-G7 without erasing everything? I have about 6 GB of photos and videos on my internal memory I wish to recover!
Click to expand...
Click to collapse
As Mr.mayb2 requested...here a rooted boot.img from the US Verizon LG Velvet.
Pulled the original boot.img directly from the kdz that was provided to me via
http://lgegdmswdl.s.llnwi.net/dn/do...5CAIKAED3DRMO/G900VM10e_00_VZW_US_OP_1009.kdz
Then did un'kdz and un'dz.
loaded it into magisk and patched the file.
Please note that LG Velvet has 2 bootloader partitions. so be sure that you patch it to a/b.
How to unlock bootloader
29y6145 said:
How to unlock bootloader
Click to expand...
Click to collapse
Thats the thing where everything will stand and fall.
To unlock the bootloader you need an unlock-code from the vendor.
For the EU-Version i got that via mail from LG.
But i've no clue if LG does this for US too.
Does that come down to LG or to the carriers (Verizon, ATT, etc)?
WELCOMETOOCEANIA said:
Does that come down to LG or to the carriers (Verizon, ATT, etc)?
Click to expand...
Click to collapse
Got it this way.
LG Developer
The official developer resources for LG products and platforms.
developer.lge.com
MikGx said:
Got it this way.
LG Developer
The official developer resources for LG products and platforms.
developer.lge.com
Click to expand...
Click to collapse
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
WELCOMETOOCEANIA said:
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
Click to expand...
Click to collapse
Sry.
Dont know about lg´s politics concerning this.
Just reacted on the request to produce an rooted boot.img.
Maybe plead lg via mail to the bones givin other regions possibility to root...?
WELCOMETOOCEANIA said:
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
Click to expand...
Click to collapse
Maybe try getting into fastbootd by rebooting in fastboot to fastbootd
Fastboot reboot fastbootd
Worth a shot.
you cant root without a bootloader unlock and you arent getting it with the verizon version. the velvet is down to $120 and although its tempting, i wouldnt do it without the unlock.
Anyone with unlocked abl or eng abl for Velvet G900EM, EMW or Wing F100EM, EMW I can unlock bootloader and root device, just have unlocked abl or eng abl
Mr.PvT said:
Anyone with unlocked abl or eng abl for Velvet G900EM, EMW or Wing F100EM, EMW I can unlock bootloader and root device, just have unlocked abl or eng abl
Click to expand...
Click to collapse
Hava you been able to unlock yours? Im on Korea version and if you can unlock yours with exploit then I can also do the same with LG token
I can't unlock bootloader for my lg velvet LM-G900VM
Please suggest how to root?