So we had frankesteined my boyfriend's VS996 back to US998. Played around with root and ROMs. Flashed it back to the latest VS996 Firmware and relocked the bootloader. Did the Verizon software upgrade tool to get to VS99630c now the software status says modified. Is there any fix?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gemini_Lee said:
So we had frankesteined my boyfriend's VS996 back to US998. Played around with root and ROMs. Flashed it back to the latest VS996 Firmware and relocked the bootloader. Did the Verizon software upgrade tool to get to VS99630c now the software status says modified. Is there any fix?
Click to expand...
Click to collapse
Manually flash the KDZ. We have it posted.
https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-vs99630a000704arb00-kdz-t3952254
ChazzMatt said:
Manually flash the KDZ. We have it posted.
https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-vs99630a000704arb00-kdz-t3952254
Click to expand...
Click to collapse
Will using lgup take away the modified software status? He just wants the phone back to normal.
Gemini_Lee said:
Will using lgup take away the modified software status? He just wants the phone back to normal.
Click to expand...
Click to collapse
No but it will give you the latest firmware.
ChazzMatt said:
No but it will give you the latest firmware.
Click to expand...
Click to collapse
We have the latest firmware through the VZW software update tool for windows. It's the exact same KDZ as you uploaded.
Gemini_Lee said:
We have the latest firmware through the VZW software update tool for windows. It's the exact same KDZ as you uploaded.
Click to expand...
Click to collapse
Sorry... I thought the main problem was you couldn't get latest firmware, and you thought it was because of the modified message.
So, your concern is the "modified" status, correct? Was the phone modified in ANY WAY before you re-locked the BL? Locking the BL doesn't undo anything you did to the system partition, and hence the status checker would still see it as "modified". If you want it to be pure stock unmodified, flash the KDZ and it will rewrite the system partition, which will undo any modifications done before.
HOWEVER, also note that if the status checker looks for the bootloader status (ie, that it was EVER unlocked) then it still may show "modified". Though, it shouldn't... my VS996 20k is BL unlocked and rooted, but my status still says Software Status "Official". Probably because I haven't deleted anything in the system partition (but I have disabled some apps, of course).
So flashing the VS99630c KDZ with Lgup and selecting dl partition then clicking select all will rewrite all the partitions?
Gemini_Lee said:
So flashing the VS99630c KDZ with Lgup and selecting dl partition then clicking select all will rewrite all the partitions?
Click to expand...
Click to collapse
Refurbish should do the same.
ChazzMatt said:
Refurbish should do the same.
Click to expand...
Click to collapse
Still says modified. Should I try partition dl
Gemini_Lee said:
Still says modified. Should I try partition dl
Click to expand...
Click to collapse
Yes, try that.
Doesn't modified mean it's been tampered with at some point?
This happened to me as well.
Originally, I started with a stock VS996. Just for fun, I Frankensteined it, then WTF unlocked the bootloader (no issues.) I decided to go back to stock and eventually flashed back to VS99630c kdz. At that point I was getting the modified status in the OS and in Download Mode. I tried reflashing VS99630c using Refurbish and Partition DL but to no avail.
I suspected that the bootloader was still unlocked and that was causing my "modified" status. However, on VS99630c, I couldn't get back to fastboot mode to check or to lock the bootloader again. ("adb reboot bootloader" just rebooted the phone.)
To fix it I did the following:
(!! This is from memory so please make sure everything you're doing makes sense if you try these steps !!)
Used patched LGUP to (Partition DL) flash US99810d. (This is the first step in the Frankenstein method.)
Booted into the phone and enabled USB debugging.
Connected to the phone and used "adb reboot bootloader" to reboot to fastboot mode.
Locked the bootloader using "fastboot oem lock".
Used patched LGUP to (Partition DL) flash VS99630c kdz (tried "refurbish" mode at first but got a cross flash error.)
Used patched LGUP to (Refurbish) flash VS99630c kdz (I'm sure this wasn't necessary but I did it...)
Success! After this I was back to "official" status in the OS and in download mode. To me, this supports my suspicion that having the bootloader unlocked was causing the "modified" error.
Thanks for your help to others. I've annotated your post so people can understand the why behind it.
Superfliege said:
This happened to me as well.
Originally, I started with a stock VS996. Just for fun, I Frankensteined it, then WTF unlocked the bootloader (no issues.)
I decided to go back to stock and eventually flashed back to VS99630c kdz.
[without re-locking the bootloader]
At that point I was getting the modified status in the OS and in Download Mode. I tried reflashing VS99630c using Refurbish and Partition DL but to no avail.
[This freshly installed firmware but still doesn't re-lock bootloader.]
I suspected that the bootloader was still unlocked and that was causing my "modified" status. However, on VS99630c, I couldn't get back to fastboot mode to check or to lock the bootloader again. ("adb reboot bootloader" just rebooted the phone.)
[because there are no fastboot flash commands on any North American variant but US998.]
To fix it I did the following:
(!! This is from memory so please make sure everything you're doing makes sense if you try these steps !!)
Used patched LGUP to (Partition DL) flash US99810d. (This is the first step in the Frankenstein method.)
[This is because to "Frankenstein" convert from one North American variant to another, most need to first go through Nougat to bypass LG's checks. In WTF method, with North American variants, we convert to US998 to get the requisite fastboot flash commands for unlocking and re-locking bootloader. Then for WTF exploit you also need to be on early Oreo to successfully run the commands. But most who need Frankenstein for this have to go through US998 Nougat first before flashing early Oreo US998.]
Booted into the phone and enabled USB debugging.
Connected to the phone and used "adb reboot bootloader" to reboot to fastboot mode.
Locked the bootloader using "fastboot oem lock".
[This finally re-locked the bootloader, using the same type fastboot flash commands which which you first unlocked it.]
Used patched LGUP to (Partition DL) flash VS99630c kdz (tried "refurbish" mode at first but got a cross flash error.)
Used patched LGUP to (Refurbish) flash VS99630c kdz (I'm sure this wasn't necessary but I did it...)
[Most other people who cross flash to other North American variants have to go through that variant's Nougat first. VS996 and US998 have an unusual relationship and for those two only, you don't have to do that. However, if you were converting to H933 instead of VS996 you would need to Partition DL to H933 Nougat, Master Reset, then continue on to newer H933 firmware.]
Success! After this I was back to "official" status in the OS and in download mode. To me, this supports my suspicion that having the bootloader unlocked was causing the "modified" error.
Click to expand...
Click to collapse
Yes, your Bootloader is unlocked until you re-lock it the same way you unlocked it. Just reflashing any stock firmware doesn't lock it.
By flashing to stock VS996 you lost fastboot flash commands. No North American variant except US998 has fastboot flash commands. This is why you have to convert to US998 for WTF exploit in the first place.
And Verizon VS996 firmware doesn't have the annoying bootloader unlock warning -- because Verizon never imagined we would find such an exploit. By flashing back to Verizon stock firmware without re-locking bootloader first, you "hid" the unlocked bootloader but still had it. If you had flashed to stock US998, H933, AS998 or any other North American variant you would have seen the bootloader unlock warning on stock firmware. But still you would have to be on US998 to relock, just like to unlock.
Thanks again for your write up!
@ChazzMatt Thanks for adding the background info. Of course I should also say thanks for all of your efforts with the V30 series and helping everyone on the forums here!
Related
Hello, I have a Sprint lg v30 plus. I'm new to lg devices. Whenever I try to boot into fastboot mode the device just reboots. I tried using adb and reboot bootloader from recovery. I know the device probably locked but lg also removed fastboot? I can get to download mode and recovery. Any ideas?
Seems the Sprint model is locked down... Was hoping it was like the T-Mobile model so I could at least unlock the bootloader
EDIT: Since this thread was dug up, all V30 now have bootloader unlock with TWRP and root possible
________
JWnSC said:
Hello, I have a Sprint lg v30 plus. I'm new to lg devices. Whenever I try to boot into fastboot mode the device just reboots. I tried using adb and reboot bootloader from recovery. I know the device probably locked but lg also removed fastboot? I can get to download mode and recovery. Any ideas?
Seems the Sprint model is locked down... Was hoping it was like the T-Mobile model so I could at least unlock the bootloader
Click to expand...
Click to collapse
No all carrier models have locked bootloader except T-Mobile. And for the T-Mobile variant, they removed most of the fastboot flash commands.
Only the open market variants have (or will have) unlocked bootloader and fastboot flash commands.
Over in the T-Mobile thread, they're very close to finding a workaround to get root.
https://forum.xda-developers.com/showthread.php?t=3690577
Sent from my official carrier unlocked LG V30+ US998
I have an LG-H931 (US AT&T). I cannot reach the fastboot mode in any way. adb reboot bootloader does a regular reboot instead of into the fastboot mode. Power off, hold volume down, plug in USB cable, it boots normally. Power off, press and hold power+vol. down keys, release when logo appears, boots normally. I tried adb reboot recovery. It loaded into recovery, but no options of any kind were available. It's as if fastboot does not exist.
neghvar said:
I have an LG-H931 (US AT&T). I cannot reach the fastboot mode in any way. adb reboot bootloader does a regular reboot instead of into the fastboot mode. Power off, hold volume down, plug in USB cable, it boots normally. Power off, press and hold power+vol. down keys, release when logo appears, boots normally. I tried adb reboot recovery. It loaded into recovery, but no options of any kind were available. It's as if fastboot does not exist.
Click to expand...
Click to collapse
What's the point anyway? H931 will never get bootloader unlocked so fastboot is useless for you even if you could boot into it.
neghvar said:
I have an LG-H931 (US AT&T). I cannot reach the fastboot mode in any way. adb reboot bootloader does a regular reboot instead of into the fastboot mode. Power off, hold volume down, plug in USB cable, it boots normally. Power off, press and hold power+vol. down keys, release when logo appears, boots normally. I tried adb reboot recovery. It loaded into recovery, but no options of any kind were available. It's as if fastboot does not exist.
Click to expand...
Click to collapse
Did you find a solution to this issue? I have the same issue with a Sprint branded LS998. I am trying to unlock the bootloader also.
duck95 said:
Did you find a solution to this issue? I have the same issue with a Sprint branded LS998. I am trying to unlock the bootloader also.
Click to expand...
Click to collapse
look at the wtf posts
basically you activate our ls998
use lgup to flash us998 firmware onto it
unlock bootloader using wtf
root
profit
duck95 said:
Did you find a solution to this issue? I have the same issue with a Sprint branded LS998. I am trying to unlock the bootloader also.
Click to expand...
Click to collapse
You replying to a thread back in February 2018. Try looking at current threads where we discuss all this stuff.
You have to Frankenstein to US998 to get fastboot flash commands to unlock the bootloader for Sprint LS998, Verizon VS996, AT&T H931, Canada H933, "regional" AS998.
If you have Sprint LS998 and want to use Sprint, you need to activate your phone first before doing any of this.
After Frankenstein to US998 you can bootloader unlock root, install TWRP, root. And you can still use the phone on Sprint by flashing back the Sprint modems.
If you are not using Sprint, and don't care, then don't worry about flashing back Sprint modems. I converted two LS998 V30+ to US998 and use them on AT&T.
SEE THE WTF THREAD -- IT HAS ALL THE INSTRUCTIONS.
ChazzMatt said:
You replying to a thread back in February 2018. Try looking at current threads where we discuss all this stuff.
You have to Frankenstein to US998 to get fastboot flash commands to unlock the bootloader for Sprint LS998, Verizon VS996, AT&T H931, Canada H933, "regional" AS998.
If you have Sprint LS998 and want to use Sprint, you need to activate your phone first before doing any of this.
After Frankenstein to US998 you can bootloader unlock root, install TWRP, root. And you can still use the phone on Sprint by flashing back the Sprint modems.
If you are not using Sprint, and don't care, then don't worry about flashing back Sprint modems. I converted two LS998 V30+ to US998 and use them on AT&T.
SEE THE WTF THREAD -- IT HAS ALL THE INSTRUCTIONS.
Click to expand...
Click to collapse
Hi ChazzMatt,
Thanks for your reply and direction. After I posted last night I did some deeper reading into both the Frankenstein
and WTF threads. I figured I needed to flash the different ROM before creating access to the bootloader. I thought I could circumvent the flashing process and access my Sprint bootloader. I now realize the Sprint version does not have access to it.
Regarding the last post being in February, no one ever closed out the question. People forget all the time to follow up with what they found. I googled "no bootloader V30" and came up with this thread. Now anyone else who finds this will know where to go. Thanks for your help.
duck95 said:
Hi ChazzMatt,
Thanks for your reply and direction. After I posted last night I did some deeper reading into both the Frankenstein
and WTF threads. I figured I needed to flash the different ROM before creating access to the bootloader. I thought I could circumvent the flashing process and access my Sprint bootloader. I now realize the Sprint version does not have access to it.
Regarding the last post being in February, no one ever closed out the question. People forget all the time to follow up with what they found. I googled "no bootloader V30" and came up with this thread. Now anyone else who finds this will know where to go. Thanks for your help.
Click to expand...
Click to collapse
Well, back in January/February 2018 we weren't aware of Frankenstein here on XDA (converting to another variant, like US998) -- but online unlockers were doing that with dedicated "Octopus" boxes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And even when we did become aware of Frankenstein (whether by Octopus box or dev patched LGUP), you still couldn't unlock the bootloader by yourself. You needed an OFFICIAL device-specific bootloader unlock code from LG, and those were only distributed to certain models (open market US998 V30, open market H930 V30, and H930G V30+). LS998 is NOT eligible for that "official" bootloader unlock code, even when converted to US998. You had to register with LG website and provided proof your phone was eligible with purchase receipts and not only IMEI but DEVICE-ID.
Simple OEM bootloader unlock in Dev Options (since Lollipop) doesn't do anything unless the carrier/OEM wants it to do something.
So, at first the Frankenstein method (thread created in late April 2018) -- which used dev patched LGUP and replicated an Octopus box -- was mostly used to either SIM card unlock Sprint LS998/AT&T H931 to carrier unlocked US998/H933/AS998 OR sometimes convert the "cheaper" LS998 to more expensive Verizon VS996. Nothing more than that.
At that point in time, with Frankenstein you still could NOT bootloader unlock an LS998, even when converted to US998. You could only convert to one of the carrier unlocked variants to SIM card unlock the LS998.
THEN, in mid-May 2018, EVERYTHING changed. @TxanMoe discovered the WTF LG Oreo bootloader unlock exploit which allows all variants with fastboot flash commands to use a "fake" bootloader unlock code. So, Frankenstein + WTF bootloader unlock exploit allows ALL V30 (except T-mobile H932) to have bootloader unlock and root. H932 only recently joined the V30 root party (mid September 2018) through another method developed by @runningnak3d.
See this quote below? I'm only using it to point out the danger in resurrecting "old" threads.
February 4, 2018
padmanek said:
What's the point anyway? H931 will never get bootloader unlocked so fastboot is useless for you even if you could boot into it.
Click to expand...
Click to collapse
Sounds hopeless, right?
Yet, @padmanek is the person who then gave us dev patched LGUP, which is critical to Frankenstein and WTF bootloader unlock and root. Yes, used on the H931 which now has bootloader unlock. Every place I post dev patched LGUP, I give him credit. I myself said many things months ago that are now totally wrong, with new information and developments.
@JWnSC;75213369, who started this entire thread, later created a thread devoted to HOW to bootloader unlock and root the LS998:
January 2018
JWnSC said:
Hello, I have a Sprint lg v30 plus. I'm new to lg devices. Whenever I try to boot into fastboot mode the device just reboots. I tried using adb and reboot bootloader from recovery. I know the device probably locked but lg also removed fastboot? I can get to download mode and recovery. Any ideas?
Seems the Sprint model is locked down... Was hoping it was like the T-Mobile model so I could at least unlock the bootloader
Click to expand...
Click to collapse
June 2018 - @JWnSC:
US998 to LS998 *Sprint LTE + Root*
I follow the [Frankenstein Phone] Using LGUP for crossflashing and that brick my phone i keep gettng the welcome to fastboot but does not pass from that screen and I was able to get the bootloader unlocked but now I have try using LGUP and flash everything on that post and i still cant pass that screen and when pressing down volume and power does not get me to the screen to wipe or install from sd card, not sure what else to do to get this to work. please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
stuck
Luis2525 said:
I follow the [Frankenstein Phone] Using LGUP for crossflashing and that brick my phone i keep gettng the welcome to fastboot but does not pass from that screen and I was able to get the bootloader unlocked but now I have try using LGUP and flash everything on that post and i still cant pass that screen and when pressing down volume and power does not get me to the screen to wipe or install from sd card, not sure what else to do to get this to work. please help
Click to expand...
Click to collapse
are you stuck on the master reset part? did you format partition etc.etc.
i have done mulitiple times if you flash correct kdz files you should have been fine. If not search other post theres. a zip you can push through adb to twrp and be golden.
Luis2525 said:
I follow the [Frankenstein Phone] Using LGUP for crossflashing and that brick my phone i keep gettng the welcome to fastboot but does not pass from that screen and I was able to get the bootloader unlocked but now I have try using LGUP and flash everything on that post and i still cant pass that screen and when pressing down volume and power does not get me to the screen to wipe or install from sd card, not sure what else to do to get this to work. please help
Click to expand...
Click to collapse
How can Frankenstein have bricked your phone, if you say you then went on to unlock the bootloader? Frankenstein is one step in the process, if you don't have a US998, H930, H930DS phone. What phone DO you have? LS998? I've used Frankenstein to unlock the bootloader to TWO of those.
After Frankenstein, then you have fastboot flash commands to unlock the bootloader. So, if you went on to unlock the bootloader then Frankenstein didn't brick your phone.
You need to start over. There is no "welcome to Fastboot" screen, you are probably talking about the annoying bootloader unlock warning. You will always see that everytime you reboot your phone or even when you boot into TWRP.
Ignore it. It's just a picture LG throws into your face to discourage people from unlocking their bootloaders.
Let the phone finish booting, unless you've messed up the phone somehow trying to avoid that NORMAL bootloader unlock warning?
Did you get to the part where you installed TWRP and rooted?
Do you remember what steps you actually did?
---------- Post added at 08:43 AM ---------- Previous post was at 07:49 AM ----------
travy said:
are you stuck on the master reset part? did you format partition etc.etc.
i have done mulitiple times if you flash correct kdz files you should have been fine. If not search other post theres. a zip you can push through adb to twrp and be golden.
Click to expand...
Click to collapse
If they went on to flash US998 Oreo KDZ AND unlock the bootloader without doing a Master Reset, WOW.
They keep reposting this in various places and we keep giving them the same answers which they are ignoring.
Their screenshot shows unlocked bootloader (in another thread) but they won't tell what they actually did, whether they got as far as installing TWRP or not.
agreed
ChazzMatt said:
How can Frankenstein have bricked your phone, if you say you then went on to unlock the bootloader? Frankenstein is one step in the process, if you don't have a US998, H930, H930DS phone. What phone DO you have? LS998? I've used Frankenstein to unlock the bootloader to TWO of those.
After Frankenstein, then you have fastboot flash commands to unlock the bootloader. So, if you went on to unlock the bootloader then Frankenstein didn't brick your phone.
You need to start over. There is no "welcome to Fastboot" screen, you are probably talking about the annoying bootloader unlock warning. You will always see that everytime you reboot your phone or even when you boot into TWRP.
Ignore it. It's just a picture LG throws into your face to discourage people from unlocking their bootloaders.
Let the phone finish booting, unless you've messed up the phone somehow trying to avoid that NORMAL bootloader unlock warning?
Did you get to the part where you installed TWRP and rooted?
Do you remember what steps you actually did?
---------- Post added at 08:43 AM ---------- Previous post was at 07:49 AM ----------
If they went on to flash US998 Oreo KDZ AND unlock the bootloader without doing a Master Reset, WOW.
They keep reposting this in various places and we keep giving them the same answers which they are ignoring.
Their screenshot shows unlocked bootloader (in another thread) but they won't tell what they actually did, whether they got as far as installing TWRP or not.
Click to expand...
Click to collapse
ChazzMatt i completely agree with you. I have the Sprint ls998 converted to the us998 and I had no issues what so ever following all threads simple easy and directions are perfectly clear. Master reset is sounding like all he needs but who knows. hopefully hell see this and somebody and help him. :laugh::good::good::good::good:
travy said:
ChazzMatt i completely agree with you. I have the Sprint ls998 converted to the us998 and I had no issues what so ever following all threads simple easy and directions are perfectly clear. Master reset is sounding like all he needs but who knows. hopefully hell see this and somebody and help him. :laugh::good::good::good::good:
Click to expand...
Click to collapse
He may have done the steps correctly but I think the "scary" bootloader unlock warning is freaking him out and he's not letting the phone finish booting.
He needs to probably re-trace his steps. Master Reset, then go into download mode manually, connect to dev patched LGUP, flash Oreo 20B US998 KDZ. Let the phone reboot. (YES you will see the scary bootloader unlock warning if you've already unlocked the bootloader. Ignore it! Let the phone finish rebooting.)
IF you see the warning, then phone is bootloader unlocked. At that point, use fastboot commands to install TWRP and boot to TWRP. MAKE SURE YOU HAVE INSTALLED TWRP, BY REBOOTING TO TWRP USING THE FASTBOOT COMMANDS. MAKE TWRP WRITABLE.
Finish flashing the other files and root.
Hello all! I'm on stock H93120d on Cricket
I hope someone can help me with my issues.
1. How can I enable wifi/mobile hotspot?
2. Is there a way of upgrading the fw without att sim card?
3. Can someone share the link of converting H931 to US998? Been trying to find it but failed.
TIA.
Sent from my SM-G930F using Tapatalk
jose makalolot said:
Hello all! I'm on stock H93120d on Cricket
I hope someone can help me with my issues.
1. How can I enable wifi/mobile hotspot?
2. Is there a way of upgrading the fw without att sim card?
3. Can someone share the link of converting H931 to US998? Been trying to find it but failed.
TIA.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
1. How can I enable wifi/mobile hotspot?
Bootloader unlock and root. WTF bootloader unlock and root thread.
2. Is there a way of upgrading the fw without att sim card?
Of course. Use Dev Patched LGUP, once you are converted to US998. You can flash most current KDZ any time you wish.
If you are bootloader unlocked and rooted, you can also install TWRP-flashable zip of latest AT&T H931 firmware provided by devs (basically going back to H931 if you wish) -- or you can stay on US998 and flash that TWRP-flashable zip. (Full KDZ image is what LG provides, the TWRP-flashable zips are based on KDZ but are built like "ROM" so you can flash them in TWRP custom recovery with minimal effort.)
3. Can someone share the link of converting H931 to US998? Been trying to find it but failed.
Frankenstein thread.
If you plan to unlock bootloader to root, when you Frankenstein just don't update Oreo to newest firmware. After bootloader unlock you can do that. For bootloader unlock, for that step you need to be on early Oreo firmware which has the WTF bootloader unlock exploit and you need fastboot flash commands. Thus, you HAVE to convert H931 to US998 (at least temporarily) as US998 is the only North American variant with fastboot flash commands.
It's all in the instructions.
ChazzMatt said:
1. How can I enable wifi/mobile hotspot?
Bootloader unlock and root. WTF bootloader unlock and root thread.
2. Is there a way of upgrading the fw without att sim card?
Of course. Use Dev Patched LGUP, once you are converted to US998. You can flash most current KDZ any time you wish.
If you are bootloader unlocked and rooted, you can also install TWRP-flashable zip of latest AT&T H931 firmware provided by devs (basically going back to H931 if you wish) -- or you can stay on US998 and flash that TWRP-flashable zip. (Full KDZ image is what LG provides, the TWRP-flashable zips are based on KDZ but are built like "ROM" so you can flash them in TWRP custom recovery with minimal effort.)
3. Can someone share the link of converting H931 to US998? Been trying to find it but failed.
Frankenstein thread.
If you plan to unlock bootloader to root, when you Frankenstein just don't update Oreo to newest firmware. After bootloader unlock you can do that. For bootloader unlock, for that step you need to be on early Oreo firmware which has the WTF bootloader unlock exploit and you need fastboot flash commands. Thus, you HAVE to convert H931 to US998 (at least temporarily) as US998 is the only North American variant with fastboot flash commands.
It's all in the instructions.
Click to expand...
Click to collapse
Hi @ChazzMatt I kept getting error flashing magisk and the rest of flashable files. It says file is corrupted.
Sent from my LG-US998 using Tapatalk
jose makalolot said:
Hi @ChazzMatt I kept getting error flashing magisk and the rest of flashable files. It says file is corrupted.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
Well people are using those files every day. In WTF Instructions, the only one I have attached is Magisk 18, while the others are links to download. If you are getting errors on ALL of them, when flashing in TWRP, maybe you should re-install TWRP? Be sure to use the TWRP linked in the WTF thread.
ChazzMatt said:
Well people are using those files every day. In WTF Instructions, the only one I have attached is Magisk 18, while the others are links to download. If you are getting errors on ALL of them, when flashing in TWRP, maybe you should re-install TWRP? Be sure to use the TWRP linked in the WTF thread.
Click to expand...
Click to collapse
I tried it a few times already.
Sent from my LG-US998 using Tapatalk
jose makalolot said:
I tried it a few times already.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
Then you're doing something wrong, or your antivirus is corrupting them. Download them somewhere else using a different computer.
It can't work for ba thousand people before you and work for people after you, but only not work for you.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Then you're doing something wrong, or your antivirus is corrupting them. Download them somewhere else using a different computer.
It can't work for ba thousand people before you and work for people after you, but only not work for you.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I'll retry once I have a new sd card. I'm suspecting it is one of the culprits. Because when I moved files from pc to sdcard within android, it says file is not supported but when it is moved to internal l, it says ok.
By the way, I can still root even if I'm on 20g already right? As long as bootloader is already unlocked?
Sent from my LG-US998 using Tapatalk
jose makalolot said:
I'll retry once I have a new sd card. I'm suspecting it is one of the culprits. Because when I moved files from pc to sdcard within android, it says file is not supported but when it is moved to internal l, it says ok.
By the way, I can still root even if I'm on 20g already right? As long as bootloader is already unlocked?
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
Yes, as long as bootloader is already unlocked.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Yes, as long as bootloader is already unlocked.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-US998 using Tapatalk
Is there a way to relock the VS996 bootloader and get it back on a stock rom? There's no bootloader mode on the VS996 rom, so flashing the stock KDZ and locking isn't going to work. I though I could do it using the US998 rom, but the bootloader warning is still coming up on restart.
EDIT: I got this figured out... I think. I flashed a US996 rooted rom with TWRP, locked the bootloader from fastboot (fastboot oem lock). I was still getting the warning but the status was locked when I checked it from fastboot. I then flashed the current stock KDZ with the DualMode LGUP from the Frankenstein thread (using the REFURBISH option).
ugoff said:
Is there a way to relock the VS996 bootloader and get it back on a stock rom? There's no bootloader mode on the VS996 rom, so flashing the stock KDZ and locking isn't going to work. I though I could do it using the US998 rom, but the bootloader warning is still coming up on restart.
EDIT: I got this figured out... I think. I flashed a US996 rooted rom with TWRP, locked the bootloader from fastboot (fastboot oem lock). I was still getting the warning but the status was locked when I checked it from fastboot. I then flashed the current stock KDZ with the DualMode LGUP from the Frankenstein thread (using the REFURBISH option).
Click to expand...
Click to collapse
Yes, except it's US998 (V30), not US996 (V20) firmware.
You should never lock the bootloader while you still have TWRP custom recovery installed.
You were on the right track however.
You should have flashed us998 KDZ to get back to full stock. Relock the bootloader on us998 full stock.
No more warning.
Then use LGUP to flash to VS996 KDZ.
ChazzMatt said:
Yes, except it's US998 (V30), not US996 (V20) firmware.
You should never lock the bootloader while you still have TWRP custom recovery installed.
You were on the right track however.
You should have flashed us998 KDZ to get back to full stock. Relock the bootloader on us998 full stock.
No more warning.
Then use LGUP to flash to VS996 KDZ.
Click to expand...
Click to collapse
Ha, I definitely would have bricked it if I had got US996 firmware to flash.
Using the US998 KDZ makes sense. I think I had it in my head that it would take less effort to flash a zip via TWRP. It wasn't.
ugoff said:
Ha, I definitely would have bricked it if I had got US996 firmware to flash.
Using the US998 KDZ makes sense. I think I had it in my head that it would take less effort to flash a zip via TWRP. It wasn't.
Click to expand...
Click to collapse
Are you trying to sell the phone or something?
Because there's also VS996 TWRP flashable zip if you just want stock Verizon firmware, while keeping TWRP custom recovery and root.
ChazzMatt said:
Are you trying to sell the phone or something?
Because there's also VS996 TWRP flashable zip if you just want stock Verizon firmware, while keeping TWRP custom recovery and root.
Click to expand...
Click to collapse
Giving it to a family member who I can't trust to use a rooted a phone, so I wanted to get it as stock as possible.
ugoff said:
Giving it to a family member who I can't trust to use a rooted a phone, so I wanted to get it as stock as possible.
Click to expand...
Click to collapse
Makes sense. While I run rooted stock firmware with mods on my own phone, I no longer help family/friends root their phones, run custom ROMs on their phones. Cuts way down on support phone calls to me.
Hello everyone,
In wondering how to root my Moto G power (2021) (Android 10) I've seen other posts on here relating to the rooting of the Moto G power but there's added markups to the the conversations and it kind of confuses the s*** out of me as to what I need to do, and what I don't need to do, it ends up being different than the original guide I've read and I get confused. Please Don't judge. If somebody has the time to walk me through the files needed/ how to root my Moto G power it would be greatly appreciated.
Thanks,
LilaWiya
LilaWiya said:
Hello everyone,
In wondering how to root my Moto G power (2021) (Android 10) I've seen other posts on here relating to the rooting of the Moto G power but there's added markups to the the conversations and it kind of confuses the s*** out of me as to what I need to do, and what I don't need to do, it ends up being different than the original guide I've read and I get confused. Please Don't judge. If somebody has the time to walk me through the files needed/ how to root my Moto G power it would be greatly appreciated.
Thanks,
LilaWiya
Click to expand...
Click to collapse
There is really only one root option, Magisk.
There are two ways to install it, patched boot.img, or Custom recovery (TWRP)
In either method, the bootloader must be UnLocked
In my opinion the patched boot.img is better.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Edit: spelling
sd_shadow said:
There is really only one root option, Magisk.
There are two ways to install it, patched boot.img, or Custom recovery (TWRP)
In either method, the bootloader must be UnLocked
In my option the patched boot.img is better.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
sd_shadow said:
There is really only one root option, Magisk.
There are two ways to install it, patched boot.img, or Custom recovery (TWRP)
In either method, the bootloader must be UnLocked
In my opinion the patched boot.img is better.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Edit: spell
Click to expand...
Click to collapse
sd_shadow said:
There is really only one root option, Magisk.
There are two ways to install it, patched boot.img, or Custom recovery (TWRP)
In either method, the bootloader must be UnLocked
In my opinion the patched boot.img is better.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Edit: spelling
Click to expand...
Click to collapse
Ive unlocked the bootoloader and installed Magisk. i would like to go with the patched boot img. way to root.
Its early in the morning here and I've been thru a hell of a time getting this far. I'm lost as to what to do next. The screenshot below is where I'm at. If you could Point me in the right direction, please? Thank you for your time and I appreciate the help you have been giving me thus far.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LilaWiya said:
Ive unlocked the bootoloader and installed Magisk. i would like to go with the patched boot img. way to root.
Its early in the morning here and I've been thru a hell of a time getting this far. I'm lost as to what to do next. The screenshot below is where I'm at. If you could Point me in the right direction, please? Thank you for your time and I appreciate the help you have been giving me thus far.....
View attachment 5384515
Click to expand...
Click to collapse
Tap Magisk > Install
Then Select and Patch a File
I'll try to make that clearer in my root thread.
I've patched the boot.img file. It all went smoothly.
sd_shadow said:
Tap Magisk > Install
View attachment 5384813
Then Select and Patch a File
View attachment 5384835
I'll try to make that clearer in my root thread.
Click to expand...
Click to collapse
After attempting to flash the patched img. My touch screen stopped responding.......
LilaWiya said:
I've patched the boot.img file. It all went smoothly.
After attempting to flash the patched img. My touch screen stopped responding.......
Click to expand...
Click to collapse
Mostly likely because the boot.img was newer than the one you replaced.
You can find the current software version with LMSA, or
Code:
fastboot getvar ro.build.fingerprint
That name should match the firmware folder you are using.
Usually, with minor updates the boot.img(s) are compatible.
Easiest fix is just you the Rescue option in LMSA and flash the firmware, then the patched_boot.img will work.
Rescue will factory reset the device.
or you can use the Device Model #, Codename, and Software Channel.
and download your current version from https://mirrors.lolinet.com/firmware/moto/
and use that boot.img to fix your device, then patch that one to root.
sd_shadow said:
Mostly likely because the boot.img was newer than the one you replaced.
You can find the current software version with LMSA, or
Code:
fastboot getvar ro.build.fingerprint
That name should match the firmware folder you are using.
Usually, with minor updates the boot.img(s) are compatible.
Easiest fix is just you the Rescue option in LMSA and flash the firmware, then the patched_boot.img will work.
Rescue will factory reset the device.
or you can use the Device Model #, Codename, and Software Channel.
and download your current version from https://mirrors.lolinet.com/firmware/moto/
and use that boot.img to fix your device, then patch that one to root.
Click to expand...
Click to collapse
LMSA seems to hang on my computer, is ODIN an option?
LilaWiya said:
LMSA seems to hang on my computer, is ODIN an option?
Click to expand...
Click to collapse
Odin is only for Samsung devices
LilaWiya said:
LMSA seems to hang on my computer, is ODIN an option?
Click to expand...
Click to collapse
What does getvar all say?
Remove the IMEI before posting?
Code:
fastboot getvar all
My computer and the rescue tool finally cooperated with each other. Touch screen is restored as is everything else minus the bootloader. Ill pick this up again tomorrow. Going Zip Lining....
Does this work on boost mobile version?
I am also looking into a way to root this phone. I have read through the forums, and this one included, and concluded, I do not have a PC. However, If there is a remote root service I could pay for or a senior member who would take a donation in exchange for root access on the Moto G Power 2021 Boost Mobile sprint USA Variant, I'd be ecstatic.
DrRoxxo said:
I am also looking into a way to root this phone. I have read through the forums, and this one included, and concluded, I do not have a PC. However, If there is a remote root service I could pay for or a senior member who would take a donation in exchange for root access on the Moto G Power 2021 Boost Mobile sprint USA Variant, I'd be ecstatic.
Click to expand...
Click to collapse
You would still need to unlock the bootloader, with PC
The OEM unlock option in dev settings is greyed out on this model, says "Contact your provider"
DrRoxxo said:
The OEM unlock option in dev settings is greyed out on this model, says "Contact your provider"
Click to expand...
Click to collapse
Probably because u have a carrier like Verizon
Carriers like Verizon don't allow their bootloader to be unlocked which is why the oem unlock is grayed out
U could try to either remove carrier or switch your carrier to something else like T-Mobile if that doesn't work than their is no way to fix this issue I'm afraid
Austinredstoner said:
Probably because u have a carrier like Verizon
Carriers like Verizon don't allow their bootloader to be unlocked which is why the oem unlock is grayed out
U could try to either remove carrier or switch your carrier to something else like T-Mobile if that doesn't work than their is no way to fix this issue I'm afraid
Click to expand...
Click to collapse
I have sprint, Motorola, Motorola has a unlock page for bootloader. Will try when I have access to PC.
DrRoxxo said:
I have sprint, Motorola, Motorola has a unlock page for bootloader. Will try when I have access to PC.
Click to expand...
Click to collapse
I remember Sprint merged with T-Mobile awhile ago so I don't see reason why oem unlock is grayed out for you
On my moto G7 with T-Mobile I managed to unlock bootloader with no issues at all so if oem unlock was available for me I don't see the reason why it's not available for you
Update: I have rooted the Motorola G Power 2021 Boost Mobile USA variant (Model XT2117-4) successfully with Magisk and the tutorial here https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/ thanks to senior member https://forum.xda-developers.com/members/sd_shadow.4267571 for the tutorial. sd_shadow you are awesome! I saw your tutorial and tried it, works like a charm.
On phone>
Install Magisk app.
Enable developer options.
Use the official Motorola unlock website to unlock the bootloader.
Allow OEM unlocking.
Allow USB debugging
On PC>
Install the stock borneo ROM.
Plug phone into PC
Copy "boot.img" from the borneo ROM on PC to Motorola G Power 2021 storage.
On Phone>
open magisk and click install.
Choose "select and pach a file".
Navigate to the boot.img file.
Flash the file with magisk.
On PC>
navigate to phone's storage and copy the patched magisk boot.img file to the PC.
Put the patched magisk boot.img file in the directory of fastboot and ADB on PC.
Open up fastboot from PC fastboot directory. Hold shift in the Fastboot directory and right click an empty space, choose open powershell/command window here.
Type commands:
fastboot flash boot magisk_patched.img
fastboot reboot
*Make sure magisk_patched.img is the exact name of the magisk patched boot.img file.
Reboot. Check magisk and Root Checker for proper root installation.
Austinredstoner said:
I remember Sprint merged with T-Mobile awhile ago so I don't see reason why oem unlock is grayed out for you
On my moto G7 with T-Mobile I managed to unlock bootloader with no issues at all so if oem unlock was available for me I don't see the reason why it's not available for you
Click to expand...
Click to collapse
Turns out, I had just activated the phone and it takes a week or so for the activation data to register with local cell providers. It took about three, maybe four days but the option for oem locking went from grayed out to available. Using the official Motorola bootloader unlock page I was able to unlock it with ADB/Fastboot on PC.
Triple25 said:
Does this work on boost mobile version?
Click to expand...
Click to collapse
Yes, tried last night. Works splendidly. Safety net tripped for me but using "magisk hide prop" module helped hide root from apps like Google etc. You can get it from the magisk module section.