Related
Question in topic. I'd like to get the V30+ if there aren't any differences as so far I'm not finding any modification discussions on the V30+.
Hiyoto said:
I'd like to get the V30+ if there aren't any differences as so far I'm not finding any modification discussions on the V30+.
Click to expand...
Click to collapse
There's no functional differences (software) between any of the V30 and V30+, except for extra 64GB internal memory (which is hardware). Some carriers are offering free premium earbuds in the V30+ box, but that's nothing to do with the phones themselves.
As for mods, unless you mean simple debloating there's nothing you can can do to "mod" without bootloader unlock and root.
No carrier branded versions will qualify for LG's bootloader unlock list and root. Only the North American and European carrier unlocked versions ("open market" versions) will get guaranteed bootloader unlock and root.
* European H930 was released in early November.
* North America US998 will be released in early December. (THAT is the official carrier unlocked V30 version, NOT the U.S. Cellular carrier-branded model. Carrier-branded versions will not be eligible for LG Bootloader Unlock List.)
Neither of these models have yet been added to the LG Developer Bootloader Unlock list, but should be in the coming weeks. Took six weeks for the LG G6 carrier unlocked models to be added to the bootloader unlock list. When they are you'll start seeing Development threads.
So far, none of the official carrier unlocked versions are V30+. EDIT: The LG V30 H930G (which is V30+) was added to the bootloader unlock list today.
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0703
I haven't had a LG phone since the LG G3 and was wondering how unlocking the bootloader would potentially affect the warranty. With the G3, it was unofficial for my device and wasn't traceable if I had to send it in for warranty claims / service as long as I did a hard factory reset. Prior to owning the G3 I owned exclusively HTC devices that had the bootloader modified check showing "S-Off" or "S-On" depending on whether the bootloader is or was tampered with. Thankfully there were simple exploits to restore this prior to sending it in for service. I know Samsung's KNOX is also a pain in the ass. I guess my question is since I will purchase the US unlocked model regardless, will there be any way of protecting my warranty if I unlock the bootloader? For example, could the official unlock software be reverse engineered to create an unofficial unlock method that would circumvent tripping these potential flags? Or could an exploit be found after the fact to erase signs that the bootloader has been previously unlocked &/ or tampered with?
*Edit*
I probably should have started a thread about this...
I haven't had a LG phone since the LG G3 and was wondering how unlocking the bootloader would potentially affect the warranty. With the G3, it was unofficial for my device and wasn't traceable if I had to send it in for warranty claims / service as long as I did a hard factory reset. Prior to owning the G3 I owned exclusively HTC devices that had the bootloader modified check showing "S-Off" or "S-On" depending on whether the bootloader is or was tampered with. Thankfully there were simple exploits to restore this prior to sending it in for service. I know Samsung's KNOX is also a pain in the ass. I guess my question is since I will purchase the US unlocked model regardless, will there be any way of protecting my warranty if I unlock the bootloader? For example, could the official unlock software be reverse engineered to create an unofficial unlock method that would circumvent tripping these potential flags? Or could an exploit be found after the fact to erase signs that the bootloader has been previously unlocked &/ or tampered with?
*Edit*
I probably should have started a thread about this...
Click to expand...
Click to collapse
Feel free to start a thread but do NOT do it in this Q&A format. Start a REAL thread. You have to use a web browser to answer these Q&A format questions and you can't easily quote, etc.
Unlocking the bootloader will void your warranty if you do it officially through LG. LG3 was a long time ago in software years. It's harder to crack bootloaders and LG removed most of the ADB flash commands even if you do so. Only the "open market" versions have LG sanctioned bootloader unlock and full ADB flash commands.
See posts #6, #7, #9 of this thread, which was written back in early September. Yes, it seems to discuss T-mobile a lot, but that's only because T-mobile bootloader is easily unlocked. Still doesn't do any good. The answer is REALLY for all carrier-branded models.
https://forum.xda-developers.com/lg-v30/help/unlock-bootloader-root-t3665927
Cant believe it was that easy! I just went into fastboot and unlocked it via the prompts! I get the warning when i reboot my phone saying the bootloader is unlocked! How do I get twrp on here and root this sucker!
stu5797 said:
Cant believe it was that easy! I just went into fastboot and unlocked it via the prompts! I get the warning when i reboot my phone saying the bootloader is unlocked! How do I get twrp on here and root this sucker!
Click to expand...
Click to collapse
And it doesn't do any good (right now).
T-Mobile H932 has crippled ADB.
There's a T-Mobile H932 specific thread where they're trying to get root and stuff:
T-Mobile LG V30 H932 | Progress Towards Root/TWRP/ROMs (not achieved yet)
https://forum.xda-developers.com/showthread.php?t=3690577
Then, when you finish that, go read this:
https://forum.xda-developers.com/showthread.php?t=3665927
That last thread was started back in early September -- and even then on the first page, we detailed the issue T-Mobile LG V30 would have, based on the T-Mobile LG G6.
Both the LG carrier unlocked versions have official bootloader unlock and root, while the T-Mobile model has a bootloader unlock but most of the ADB flash commands are removed. The T-Mobile LG G6 STILL doesn't have root.
stu5797 said:
Cant believe it was that easy! I just went into fastboot and unlocked it via the prompts! I get the warning when i reboot my phone saying the bootloader is unlocked! How do I get twrp on here and root this sucker!
Click to expand...
Click to collapse
yes as always for LG TMO's , but probably you still don't have write commands enabled on Fastboot.
You should only be able to send "read" commands from there
wolfgart said:
yes as always for LG TMO's , but probably you still don't have write commands enabled on Fastboot.
You should only be able to send "read" commands from there
Click to expand...
Click to collapse
Question
If i will try to unlock the H930G Israel model (no carrier) using this method (fastboot) - will i theoretically have write commands?
the H930G italy model is the only one to get the bootloader unlock for now.
Orof said:
Question
If i will try to unlock the H930G Israel model (no carrier) using this method (fastboot) - will i theoretically have write commands?
the H930G italy model is the only one to get the bootloader unlock for now.
Click to expand...
Click to collapse
You can try on the LG Developer Bootloader Unlock list website, but when you put in your IMEI or serial number or whatever they go buy, they'll probably say the phone isn't eligible. Same way U.S.Cellular version is not eligible...
But wouldn't hurt to try. LG system could have a snafu and you might very lucky.
Goodbye warranty for no benefit. you have no fastboot commands, so it is useless to unlock on your phone model.
and the phone keeps track of if the bootloader has been unlocked, even if you re-lock it.
That might be a big deal for some but the way I go through phones I'm not too concerned.
stu5797 said:
Cant believe it was that easy! I just went into fastboot and unlocked it via the prompts! I get the warning when i reboot my phone saying the bootloader is unlocked! How do I get twrp on here and root this sucker!
Click to expand...
Click to collapse
Yup.. Didn't need unlock.bin.. Just like you said.. Strange.. Has anyone tried using write commands or is everything I'm reading assumptions? I can't find proof of What was tried anywhere.. What if twrp recovery worked? No one can confirm really unless it exists.. What if writing recovery is one of few commands that might work.. Any information would be appreciated..
lowkeyst4tus said:
Yup.. Didn't need unlock.bin.. Just like you said.. Strange.. Has anyone tried using write commands or is everything I'm reading assumptions? I can't find proof of What was tried anywhere.. What if twrp recovery worked? No one can confirm really unless it exists.. What if writing recovery is one of few commands that might work.. Any information would be appreciated..
Click to expand...
Click to collapse
What you did is useless. Been discussed for a hundred pages elsewhere. Notice you've dug up an old thread from December 2017?
Right now (September 2018), every V30/V30+/V30S on the planet can be bootloader unlocked and rooted ----except for T-Mobile H932. Been that way since mid-May 2018, when we discovered the WTF Oreo bootloader unlock expoit.
H932 does not have any fastboot flash commands, so cannot be rooted. Also, since it has different RSA encryption it cannot be converted (Frankenstein) to carrier unlocked US998 which does have fastboot flash commands, like all the other North American variants.
See post #2 of this thread you are in for more information. I notice you quoted post #1 but didn't quote post #2? There were only 7 posts in this thread before it died off! If you can't find proof it's because you haven't actually looked... Here's post #2, from December 1, 2017:
ChazzMatt said:
And it doesn't do any good (right now).
T-Mobile H932 has crippled ADB.
There's a T-Mobile H932 specific thread where they're trying to get root and stuff:
T-Mobile LG V30 H932 | Progress Towards Root/TWRP/ROMs (not achieved yet)
https://forum.xda-developers.com/showthread.php?t=3690577
Click to expand...
Click to collapse
Go read THAT referenced thread, which is current, and is up to 148 pages now. H932 may get root eventually, but right now still impossible.
Also, you could have bought a carrier unlocked V30 and use it on T-Mobile and have root. Or you could buy a mint LS998 for just over $300 off eBay, convert it to carrier unlocked US998 and have root.
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
I've just bought V30 and would like to root it. Preferably with Magisk.
Every guide I found requires to unlock bootloader. This is one step too far for me. Is there a way to root V30 without unlocking it's bootloader?
przemhb said:
I've just bought V30 and would like to root it. Preferably with Magisk.
Every guide I found requires to unlock bootloader. This is one step too far for me. Is there a way to root V30 without unlocking it's bootloader?
Click to expand...
Click to collapse
NO.
Which variant did you buy?
With some, it's simply flashing a simple code via fastboot flash commands. On others you first have to convert to a variant which has fastboot flash commands, so you can flash that code. If you tell us which variant you bought, you will know if you have extra steps or not...
For all V30/V30+/V30S (except T-mobile H932) for bootloader unlock and root, you need to:
have fastboot flash commands
be on specific Oreo firmware
use the "fake" bootloader unlock code
install TWRP and flash Magisk (OK technically there is a way to root without installing TWRP, but it's easier with TWRP)
WTF V30/V30+/V30S Bootloader Unlock and Root
Thank you for your reply. I've bought European H930. Unbranded.
Android 8.0.0. Build: OPR1.170623.026. SW: V20d-EUR-XX. Security patch: 1.03.2018.
I don't want to loose my warranty, DRM protected stuff playback capability, etc.
These warnings from LG bootloader unlock website worry me and make me extra cautious. I have to be 100% sure none of the things will happen:
"When unlocking the bootloader, applications which require a trusted execution environment (TEE) to operate will not work properly because after unlocking the bootloader the device will no longer be trusted.
Unlocking the bootloader will also affect the DRM protection of your device, therefore some applications which require DRM protection may not work anymore or block certain functions due to this untrusted state.
Common examples for affected applications are services which offer download/streaming of paid multimedia content like music and movies or services offering mobile payment."
Is there at least reliable app+data migration utility to move my apps with data from an old (Marshmallow) phone to this new one? LG Mobile Switch didn't manage to migrate apps' data.
przemhb said:
Thank you for your reply. I've bought European H930. Unbranded.
Android 8.0.0. Build: OPR1.170623.026. SW: V20d-EUR-XX. Security patch: 1.03.2018.
I don't want to loose my warranty, DRM protected stuff playback capability, etc.
These warnings from LG bootloader unlock website worry me and make me extra cautious. I have to be 100% sure none of the things will happen:
"When unlocking the bootloader, applications which require a trusted execution environment (TEE) to operate will not work properly because after unlocking the bootloader the device will no longer be trusted.
Unlocking the bootloader will also affect the DRM protection of your device, therefore some applications which require DRM protection may not work anymore or block certain functions due to this untrusted state.
Common examples for affected applications are services which offer download/streaming of paid multimedia content like music and movies or services offering mobile payment."
Is there at least reliable app+data migration utility to move my apps with data from an old (Marshmallow) phone to this new one? LG Mobile Switch didn't manage to migrate apps' data.
Click to expand...
Click to collapse
LG also throws a scary bootloader unlock warning in your face.
LG's "warning" is to keep you from rooting your phone. If you've rooted phones before, its no different.
Magisk hides root, so all apps work.
Anyone who's rooted their V30 can tell you how it is. The threads here are very active!
But it's your decision.
Is it possible to lock back the bootloader at the end of the process?
przemhb said:
Is it possible to lock back the bootloader at the end of the process?
Click to expand...
Click to collapse
At the end of what process? Rooting? You don't seem to understand, you have to unlock the bootloader to install TWRP. You have to install TWRP to flash Magisk. OK, technically there is a way to root without TWRP (by installing a rooted kernel), but you still need bootloader unlock.
You seem hung up on bootloader unlock when it's REALLY root that LG is trying to prevent. They really couldn't care less about bootloader unlock, they are focusing on that to prevent you from rooting your phone. Because once you unlock your bootloader you are one step away from root...
Yeah, you can lock the bootloader back if you no longer want root.
Most phones require bootloader unlock to root -- Motorola, Pixel, LG, ZTE, OnePlus.
---------- Post added at 11:59 PM ---------- Previous post was at 11:51 PM ----------
przemhb said:
Thank you for your reply. I've bought European H930. Unbranded.
Android 8.0.0. Build: OPR1.170623.026. SW: V20d-EUR-XX. Security patch: 1.03.2018.
Click to expand...
Click to collapse
I'm sorry, what is the DATE of the security patch? May, July, September? If pre-July, you are good to go. You just flash a simple code with fastboot. If July or later, you would need to temporarily downloader to pre-July 2018 firmware.
Thank you for your detailed answers! I really appreciate them.
ChazzMatt said:
At the end of what process? Rooting?
Click to expand...
Click to collapse
Yes. I was wondering if it is possible to lock back the bootloader once the phone is rooted, TWRP, Magisk are there. The question behind it is if having unlocked bootloader doesn't unnecessarily increase security risk (of course the main risk is to have rooted phone, and I accept it).
ChazzMatt said:
Yeah, you can lock the bootloader back if you no longer want root.
Click to expand...
Click to collapse
Good news. Suppose I would unroot and lock back the bootloader, then send the phone to warranty service. Is it possible for the service to discover the phone was rooted and reject my warranty claim?
ChazzMatt said:
Most phones require bootloader unlock to root -- Motorola, Pixel, LG, ZTE, OnePlus.
Click to expand...
Click to collapse
So far I've rooted every phone without unlocking bootloader. It was harder, but in some cases possible (Xperia Z2, Xperia V, Motorola Defy).
ChazzMatt said:
I'm sorry, what is the DATE of the security patch? May, July, September? If pre-July, you are good to go. You just flash a simple code with fastboot. If July or later, you would need to temporarily downloader to pre-July 2018 firmware.
Click to expand...
Click to collapse
It's March.
I am not familiar with Magisk. Is it safer from the security point of view than classic roots with SuperSu+BusyBox?
Correct me if I am wrong, but unlocking bootloader means gaining write access to boot partition. TWRP needs to be stored on it. Kernel is also there. And where is Magisk stored?
I will be unlocking my phone in about a month and moving to TMobile.
I'm just curious, has anyone moved their v30 plus from sprint to tmo and it work fine? (After unlocking it off course)
I do know there is one band that will not work, 600 or something like that, and I'm ok with that, as long as the rest will work ok.
easyrider77 said:
I will be unlocking my phone in about a month and moving to TMobile.
Click to expand...
Click to collapse
Are you talking about carrier unlock or also bootloader unlock/root?
easyrider77 said:
I'm just curious, has anyone moved their v30 plus from sprint to tmo and it work fine? (After unlocking it off course)
I do know there is one band that will not work, 600 or something like that, and I'm ok with that, as long as the rest will work ok.
Click to expand...
Click to collapse
Yes, many use on U.S. T-Mobile. Because the easiest way to carrier unlock LS998 is to flash US998 firmware. Convert LS998 V30+ to US99 V30+.
See the Frankenstein instructions.
At the end of the process you will have carrier unlocked US998 with these bands:
US998
CDMA: 800 MHz CDMA
2G GSM: 850/900/1800/1900 MHz
3G UMTS (HSPA):850/900/1900/2100 MHz
4G LTE Bands: 1/2/3/4/5/7/12(17)/13/20/25/66
LTE band 71 is the only U.S. T-Mobile LTE band the US998 not any other V30 have except the T-Mobile H932.
ChazzMatt said:
Are you talking about carrier unlock or also bootloader unlock/root?
Click to expand...
Click to collapse
Just carrier unlock.
Not wanting to root although I have rooted multiple other phones before, so I am comfortable with doing so if and when I decide to.
So that brings me to a couple other questions. I have looked over the Frankenstein thread on how to flash from ls998 to us998 and even have the files for lgup downloaded, but I was curious about a few things.
1: say if I flash and get on TMobile fine and everything works then for whatever reason I want to go back to sprint, will the us998 work on sprint or will I have to flash back to ls998 for it to work?
2: if it's needed to flash back to ls998, the only way I am reading on forums is to unlock the bootloader and root, unless there is another way without rooting that I missed? If there is a rootless way could anyone direct me to that, I'd appreciate it greatly.
Don't get me wrong, I'm in no way anti-root, it's just not for me with this phone, so I'm trying to do all this without rooting (if possible)
easyrider77 said:
Just carrier unlock.
Not wanting to root although I have rooted multiple other phones before, so I am comfortable with doing so if and when I decide to.
So that brings me to a couple other questions. I have looked over the Frankenstein thread on how to flash from ls998 to us998 and even have the files for lgup downloaded, but I was curious about a few things.
1: say if I flash and get on TMobile fine and everything works then for whatever reason I want to go back to sprint, will the us998 work on sprint or will I have to flash back to ls998 for it to work?
2: if it's needed to flash back to ls998, the only way I am reading on forums is to unlock the bootloader and root, unless there is another way without rooting that I missed? If there is a rootless way could anyone direct me to that, I'd appreciate it greatly.
Don't get me wrong, I'm in no way anti-root, it's just not for me with this phone, so I'm trying to do all this without rooting (if possible)
Click to expand...
Click to collapse
Both Sprint and AT&T do not release public KDZ (firmware images). For LS998, to carrier unlock it and get most compatibility with other North American carriers the method is to convert it (Frankenstein) to a native carrier unlocked firmware -- like Open Market US998 or even Canada H931. US998 is more popular because it also has fastboot flash commands.
While it's not entirely a one-way street, it's a lot harder to go back -- because Sprint doesn't release public KDZ images. Our talented devs have created their own TWRP flashable zips (basically ROMs) to flash back to Sprint firmware via TWRP. One dev even created a TWRP flashable zip for warranty return purposes that would flash back stock recovery, erasing TWRP custom recovery.
To use those, yes you have to be bootloader unlocked and have TWRP custom recovery.
While you can use US998 on Sprint, there are two caveats which may apply to you. Three Sprint LTE bands are missing on US998 and in the past Sprint wouldn't activate a US998 phone, even though IMEI shows it was a former LS998. However, someone recently said they were able to activate a NATIVE US998 phone on Sprint, so maybe their policies have changed? Still, in the past, the method for Sprint customers was to activate Sprint service while still on LS998 firmware, then temporarily convert to US998 for bootloader unlock and root, then flash back to Sprint firmware (to get those three LTE bands back) using TWRP flashable zip -- while keeping TWRP and root. If you wanted to go back to Sprint, you would probably have to bootloader unlock, install TWRP and flash one of those dev crafted Sprint stock ROMs.
I hope I haven't confused you. There is no need for you to bootloader unlock and root just to convert to US998 to go to T-mobile. "Frankenstein" existed long before our WTF bootloader unlock and root method, to carrier unlock the Sprint LS998 and AT&T H931. Merely convert to US998 and you are carrier unlocked, have bands compatible with most other carriers, and have access to publicly released KDZ.
The LS998 was the main reason Frankenstein was created. It's a V30+ and is available very inexpensively and can be carrier unlocked very easily. Most people using it are NOT Sprint customers. Like me, they bought to convert to US998. I wrote the Frankenstein instructions and the screenshot images are from my own LS998 I bought off eBay.
ChazzMatt said:
Both Sprint and AT&T do not release public KDZ (firmware images). For LS998, to carrier unlock it and get most compatibility with other North American carriers the method is to convert it (Frankenstein) to a native carrier unlocked firmware -- like Open Market US998 or even Canada H931. US998 is more popular because it also has fastboot flash commands.
While it's not entirely a one-way street, it's a lot harder to go back -- because Sprint doesn't release public KDZ images. Our talented devs have created their own TWRP flashable zips (basically ROMs) to flash back to Sprint firmware via TWRP. One dev even created a TWRP flashable zip for warranty return purposes that would flash back stock recovery, erasing TWRP custom recovery.
To use those, yes you have to be bootloader unlocked and have TWRP custom recovery.
While you can use US998 on Sprint, there are two caveats which may apply to you. Three Sprint LTE bands are missing on US998 and in the past Sprint wouldn't activate a US998 phone, even though IMEI shows it was a former LS998. However, someone recently said they were able to activate a NATIVE US998 phone on Sprint, so maybe their policies have changed? Still, in the past, the method for Sprint customers was to activate Sprint service while still on LS998 firmware, then temporarily convert to US998 for bootloader unlock and root, then flash back to Sprint firmware (to get those three LTE bands back) using TWRP flashable zip -- while keeping TWRP and root. If you wanted to go back to Sprint, you would probably have to bootloader unlock, install TWRP and flash one of those dev crafted Sprint stock ROMs.
I hope I haven't confused you. There is no need for you to bootloader unlock and root just to convert to US998 to go to T-mobile. "Frankenstein" existed long before our WTF bootloader unlock and root method, to carrier unlock the Sprint LS998 and AT&T H931. Merely convert to US998 and you are carrier unlocked, have bands compatible with most other carriers, and have access to publicly released KDZ.
The LS998 was the main reason Frankenstein was created. It's a V30+ and is available very inexpensively and can be carrier unlocked very easily. Most people using it are NOT Sprint customers. Like me, they bought to convert to US998. I wrote the Frankenstein instructions and the screenshot images are from my own LS998 I bought off eBay.
Click to expand...
Click to collapse
Awesome, thanks for the info, and no it didn't confuse me at all, I completely understand all of it.
On a side note I might add, that sprint and vz both detect the bootloader unlocked and will not currectly register with thier networks as long as the bootloader is unlocked.
I know this from experience, because I had a g5s plus that was rooted and worked fine on tmo, cricket, simple mobile, yet would not currectly setup and work right on sprint or on vz.
I tried flashing a stock rom and still did not work. Only when I locked the bl again did it then work fine on both networks. I got data but no calls or texts.
Since I had a very very very bad time locking the bl on that phone, and no one had a solution, it took me upwards of near 3 months to find a way to lock the bl.
Once I got the stock rom and locked the bl it works just fine with no issues at all.
I did find out from a friend that the way to have root on those networks is register it in the network THEN root it, although I was too lazy to do that so I just left it un-rooted.
That given, I just was wondering if there a simple way to relock the bootloader in case this may happen again in the future? Perhaps via fastboot commands??
As a side note, fastboot command did not work on my g5s plus sadly. It said it worked but when I rebooted nothing happened and bootloader was still unlocked. Not sure exactly why but as you can imagine it made me a bit gun shy on rooting. I've rooted a dozen or more phones in my span of phones, from the s2 and up, and the g5s plus is and was the only phone I had issues with and had a horrible time locking the bootloader.
easyrider77 said:
That given, I just was wondering if there a simple way to relock the bootloader in case this may happen again in the future? Perhaps via fastboot commands??
Click to expand...
Click to collapse
Yes, bootloader is easily re-locked on US998 firmware.
Very good. Thanks so very much for all the info.
Hopefully it will just unlock via sprint and work on TMobile and I won't have to mess with anything but either way I'm ready.
Just FYI, thank you for your hard work and efforts on the tutorial on converting to us998. I greatly appreciate you and the devs and others that make it easier for us.
So I've read some on the Frankenstein thread, and I decide to go that route I'll follow that thread.
I have not switched carriers as of yet so I am on sprint still.
I know if I am going to say tmo it's recommend to kdz flash the us988.
As I understand it, you can go to us988 fine without issues (normally) but to go back to sprint you need to reflash to ls988 and to do that, root is needed, which also requires bl unlock.
I tried a moto g5s plus with an unlocked bl on both sprint and vz, but in both cases I got data to work but no voice at all. After some research and trial and errors, I found out it was because the bl was unlocked, because I was flashed to stock rom. Once I locked the bl, everything worked fine. Some how sprint network detects the bl bring unlocked or the bl being unlocked makes it so the system doesn't work right with the phone, not sure. I also found out you can be root and use an unlocked bl once you are on the network, but not before.
So, that brings me to my question.
In order to use ls988, again you need root and unlocked bl, so that being the case, how would I go about using the ls988 without the bl being unlocked? Because with the bl unlocked, as stated above, calls won't work.
Is it possible to use the us988 abd bl locked, then get registered on the network, then flash the ls988?
Sorry for any confusion, I sometimes have a hard time explaining in words what's in my head.
easyrider77 said:
So I've read some on the Frankenstein thread, and I decide to go that route I'll follow that thread.
I have not switched carriers as of yet so I am on sprint still.
I know if I am going to say tmo it's recommend to kdz flash the us988.
As I understand it, you can go to us988 fine without issues (normally) but to go back to sprint you need to reflash to ls988 and to do that, root is needed, which also requires bl unlock.
I tried a moto g5s plus with an unlocked bl on both sprint and vz, but in both cases I got data to work but no voice at all. After some research and trial and errors, I found out it was because the bl was unlocked, because I was flashed to stock rom. Once I locked the bl, everything worked fine. Some how sprint network detects the bl bring unlocked or the bl being unlocked makes it so the system doesn't work right with the phone, not sure. I also found out you can be root and use an unlocked bl once you are on the network, but not before.
So, that brings me to my question.
In order to use ls988, again you need root and unlocked bl, so that being the case, how would I go about using the ls988 without the bl being unlocked? Because with the bl unlocked, as stated above, calls won't work.
Is it possible to use the us988 abd bl locked, then get registered on the network, then flash the ls988?
Sorry for any confusion, I sometimes have a hard time explaining in words what's in my head.
Click to expand...
Click to collapse
Yes, it's best to activate the phone on Sprint FIRST before you temporarily convert to US998, then flash back to Sprint. So that part of your question is valid.
But the rest is a little silly considering we've been rooting this phone for over 2 years now.
Of course calls/data work with a Unlocked Bootloader on all variants.
Everyone who unlocked a boot loader on the LS998 have calls and data working just fine on Sprint. And Verizon and AT&T and T-Mobile and every other carrier and the world.
Lots of Sprint people who have temporarily converted to US998, unlocked bootoader, then flash back to Sprint firmware -- keeping TWRP and root. One of our main DEVs is a Sprint customer. So your worries are totally baseless.
Why do you think we have TWRP flashable zips Sprint firmware to flash back to, if the phone couldn't be used?
By the way this is an LG not a Motorola. It's also not a Sony, which is another common question -- do to boot loader unlock issues with Sonys.
However, if you're thinking about moving to T-Mobile, then stay on US998 and go to T-Mobile. Why mess with Sprint?
Us998 on T-Mobile has VoLTE, Wi-Fi calling, etc. Us998 has more compatible T-Mobile bands than LS998 firmware.
I've rooted almost a dozen different phones from back to the s2 days, but the moto phone threw me. I've never once had an issue with bl unlocked and being able to switch to another carrier until the moto phone, so I wasn't sure if that was a network thing or a phone thing.
With the moto it was obviously a phone thing.
Why switch to sprint instead of just staying on tmo? I guess simply put, it gives choices. Like everything in life, it's good to have choices and even if you never choose to use said choice, the fact that it's there is good, because it doesn't limit things to just a small selection. This is why we have multiple phones, and cell services to choose from, it gives a variety of things to choose from, to suit each person's needs.
I've seen people who live in a specific area and can only get one carrier because nothing else works in that area so they have to change carriers.
As for being baseless I am confused how it is baseless from a question. I never said anything about lg not working with our without the bl locked or unlocked, I simply referred to the Motorola phone and was curious if the lg phone would have the same issue I had with the moto phone.
If for some reason there is an implied statement that I am lying about the moto phone not working with the bl unlocked before it was registered on the network and the only thing I did was lock the bl, I am willing to hear why exactly it would not receive or make calls on both vz and sprint, both the exact same issue, until I locked the bl.
Nowhere in my thread did I say the lg would not work with an unlocked bl, twrp or anything else..... I was simply asking a question based on the experience I had with the moto phone (not lg or any other phone) so I am confused how that is baseless, considering I was baseing it off of the phone that did give me issues which was the moto phone, and not the lg phone.
easyrider77 said:
So I've read some on the Frankenstein thread, and I decide to go that route I'll follow that thread.
I have not switched carriers as of yet so I am on sprint still.
Click to expand...
Click to collapse
easyrider77 said:
Why switch to sprint instead of just staying on tmo? I guess simply put, it gives choices.
Click to expand...
Click to collapse
Can you make up your mind what carrier you're on right now?
easyrider77 said:
I've rooted almost a dozen different phones from back to the s2 days, but the moto phone threw me. I've never once had an issue with bl unlocked and being able to switch to another carrier until the moto phone, so I wasn't sure if that was a network thing or a phone thing.
With the moto it was obviously a phone thing.
As for being baseless I am confused how it is baseless from a question. I never said anything about lg not working with our without the bl locked or unlocked, I simply referred to the Motorola phone and was curious if the lg phone would have the same issue I had with the moto phone.
Nowhere in my thread did I say the lg would not work with an unlocked bl, twrp or anything else..... I was simply asking a question based on the experience I had with the moto phone (not lg or any other phone) so I am confused how that is baseless, considering I was baseing it off of the phone that did give me issues which was the moto phone, and not the lg phone.
Click to expand...
Click to collapse
We've been bootloader unlocking and rooting these V30 phones for two years and using across all carriers. That's why I said your assumptions were baseless. This forum would not be as active as it is if we have any of the problems you were asking about. Bootloader Unlock and Root only improves V30 phones. For instance you will never have the LG DTS Surround Sound stereo framework enabled unless you bootloader unlock and root the phone. Yes, in latter Oreo LG gave use DTS libs, but then didn't enable them. But you can root and enable DTS 3D Surround stereo.
Have you even read the WTF Bootloader Unlock instructions yet? ALL the way through? Read in web browser, not an app. App seems to truncate entire sections. Section 9 talks about flashing back to your own carrier firmware -- like Sprint.
Most everybody who buys an LS998 are NOT Sprint customers and convert them to something better -- like US998 V30+ to use on AT&T, T-Mobile, Cricket, etc. or create a VS996 V30+ to use on Verizon (make sure you have an already activated Verizon SIM card). And most also Bootloader Unlock and Root their LS998 and use on other carriers. I bought a few LS998 I either converted myself or were already converted to US998. Some of these converted LS998-to-US998 I bought are being used on AT&T. My sister and brother-in-law use their converted LS998-to-US998 on Verizon.
I wrote the Frankenstein instructions and the screenshots in those instructions are from my LS998 being converted to US998.
I also wrote the WTF INSTRUCTIONS on bootloader unlock, TWRP Installation and Root. Both threads have current, up to date procedures.
Any North American variant -- EXCEPT for T-mobile H932 -- has to be on US998 firmware (at least TEMPORARILY) to bootloader unlock and root, because of the North American variants only US998 has the requisite fastboot flash commands. After bootloader unlock, TWRP installation and root, users can choose to stay on US998 firmware or use DEV-created TWRP flashable zips to flash back to their carrier firmware. Sprint users choose to flash back Sprint firmware because there are 3 LTE bands Sprint uses (for now) which US998 modems do not have. I use AT&T, but I choose to remain on Open Market US998 firmware instead of flashing back to AT&T firmware.
____
Please don't bother mentioning other brands of phones in this forum. They have nothing to do with LG phones. Now, if you said you had a certain problem with Bootloader Unlock of a previous LG phone, then that would be valid concern.
You're acting like this is something people haven't done a thousand times already with V30. Even people in other countries are buying North American V30 variants and using them on their own carriers -- AFTER Bootloader Unlock and Root.
Even your thread title is somewhat confusing. Says going from US998 to LS998, don't you mean the reverse? You have LS998. You would be going from LS998 to US998 (at least temporarily).
____
But to reiterate -- for Sprint customers only -- yes you should activate the native LS998 on Sprint first BEFORE doing anything else to the phone. AFTER activation on Sprint, then TEMPORARILY convert to US998 for Bootloader Unlock, TWRP and root. Follow the Frankenstein and WTF Instructions.
Then flash back Sprint firmware via TWRP flashable zip to get back Sprint LTE bands.
JohnFawkes is one of our main DEVs. He created the Sprint TWRP flashable zip. He's a Sprint customer himself.
If you fail to follow that simple guideline, yes there is also a full firmware Sprint stock zip -- which wipes out TWRP custom recovery, replacing with stock recovery. You can flash that to go back to "original" Sprint firmware. It's use for warranty exchanges, but can also be use to your phone activated on Sprint if you failed to do it prior to unlocking bootloader. After flashing this special zip, your bootloader is STILL unlocked but the phone can be activated on Sprint. THEN even though your Bootloader is unlocked, after Sprint activation you have to TEMPORARILY CONVERT back to US998 yet again (for fastboot flash commands) to reinstall TWRP... So you're wasting a lot of time and effort doing all that, when you can just activate the LS998 FIRST on Sprint before bootloader unlock and root.
HOWEVER if you are on Sprint already with your LS998 -- as your OTHER thread seems to indicate -- then your LS998 phone is already activated on Sprint. So, I'm not sure why you're asking about all that.