Develop Bugs

Rooting updates?

Any updates on if the g5 is rootable yet?
Sent from my LGAS992 using Tapatalk

nope... just sitting with an unlocked bootloader and waiting for someone to root it.. im a noob and i've experimented with many root tools but none of em worked cos of the forced encryption of data partition. i couldn't wipe it with twrp.. there's a guide for LG G5 on how to disable forced encryption, but it doesn't work for our phone.. "http://www.droidorigin.com/root-lg-g5/". i hope someone can adapt it for our phone and finally somehow root it..

salaigeethan666 said:
nope... just sitting with an unlocked bootloader and waiting for someone to root it.. im a noob and i've experimented with many root tools but none of em worked cos of the forced encryption of data partition. i couldn't wipe it with twrp.. there's a guide for LG G5 on how to disable forced encryption, but it doesn't work for our phone.. "http://www.droidorigin.com/root-lg-g5/". i hope someone can adapt it for our phone and finally somehow root it..
Click to expand...
Click to collapse
I posted a rooting guide for LG K10 420DS. Try that!
How did you get your bootloader unlocked?

Surely root for the LGAS992 cannot be that hard...just need someone with knowledge to take the time.

pvineeth97 said:
I posted a rooting guide for LG K10 420DS. Try that!
How did you get your bootloader unlocked?
Click to expand...
Click to collapse
Enable developer options and enable usb debugging. Then make sure the oem unlock option is enabled.
connect pc to phone.
//*Backup your data first. It resets your phone*//
# adb reboot bootloader
# fastboot oem unlock
//*Follow instructions on your mobile phone*//
Done. Now its unlocked and your phone will say, "your phone is corrupted and may have been tampered" everytime you reboot

:silly:

salaigeethan666 said:
Enable developer options and enable usb debugging. Then make sure the oem unlock option is enabled.
connect pc to phone.
//*Backup your data first. It resets your phone*//
# adb reboot bootloader
# fastboot oem unlock
//*Follow instructions on your mobile phone*//
Done. Now its unlocked and your phone will say, "your phone is corrupted and may have been tampered" everytime you reboot
Click to expand...
Click to collapse
You are from Chennai. How did you get K430 lol?

pvineeth97 said:
You are from Chennai. How did you get K430 lol?
Click to expand...
Click to collapse
i bought it in hong kong

fastboot unlock vs fastboot unlock critical

When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...

Az Biker said:
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Click to expand...
Click to collapse
Only if you want to update the bootloader. That's the only thing I can see that critical does.
Sent from my Pixel 2 XL using Tapatalk

I believe unlock_critical is necessary if you want to be able to flash updates manually..

"For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock "
Above quote is from Google Factory Image page.

thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!

Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:

Badger50 said:
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Click to expand...
Click to collapse
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel

Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:

Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck

Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?

Wickidmasshole said:
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Click to expand...
Click to collapse
This is why I asked the question. I wasn't sure if doing the basic unlock prior to the critical unlock would be an issue.
I'm running the critical unlock when I get home tonight (I want to be able to update the bootlader in the future), I'll let you know what I run into, if anything.

Az Biker said:
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Click to expand...
Click to collapse
Didn't use any toolkits, just these 2 guides....
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176 https://forum.xda-developers.com/pixel-2-xl/how-to/guide-magisk-root-snoke-kernel-t3701930
....and didn't run into any problems at all. My P2XL is just humming right along. The battery on this thing is phenomenal! Takes me a good 2 days to knock it down to 10% :good:
Now we just need some TWRP to get Beans up and running :good::good:

Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.

iamjimmy said:
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
Click to expand...
Click to collapse
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:

Badger50 said:
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Click to expand...
Click to collapse
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Sent from my [device_name] using XDA-Developers Legacy app

slaydog said:
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Click to expand...
Click to collapse
This one :good:

Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!

marbertshere said:
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
Click to expand...
Click to collapse
I've unlocked the ordinary bootloader first, then the bootloader_critical without any problems :good:

I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?

jaybird779 said:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
Click to expand...
Click to collapse
The bootloader_critical unlock has to be performed only if you want to flash the bootloader (e.g. when you flash a factory image), but, if you want to perform all the other operations, such as rooting, kernel flashing, etc., you have to unlock the ordinary bootloader, too.
So, these are the two Fastboot commands:
fastboot flashing unlock_critical (for bootloader flashing, you've already performed this)
fastboot flashing unlock (for all the other operations)
The request which appears on your phone, when you enter these two commands, is the same, and you have to allow the bootloader unlock in both cases :good:

Root/Bootloader unlock

Hey guys, I'm super excited to get my new LG G8 tonight, with all of the incentives Sprint is offering me it'll cost just over $300!
However, the previous LG phones that I've had (G4 and G5) were absolute trainwrecks when it came to software, and the G8 doesn't seem to be too different. I'm hoping that eventually we will be able to root it, if not install a Project Treble AOSP build.
How likely is this? Can we get a bootloader bounty going? Heck, I'd be happy with just root and Magisk

2390 said:
Hey guys, I'm super excited to get my new LG G8 tonight, with all of the incentives Sprint is offering me it'll cost just over $300!
However, the previous LG phones that I've had (G4 and G5) were absolute trainwrecks when it came to software, and the G8 doesn't seem to be too different. I'm hoping that eventually we will be able to root it, if not install a Project Treble AOSP build.
How likely is this? Can we get a bootloader bounty going? Heck, I'd be happy with just root and Magisk
Click to expand...
Click to collapse
Unless something like this will work on G8, there is no reason to believe your G8 will be able to be rooted anytime soon.

mr3p said:
Unless something like this will work on G8, there is no reason to believe your G8 will be able to be rooted anytime soon.
Click to expand...
Click to collapse
let me know when u can unlock bootloaders , happy to help out with twrp or so
Cheers

The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.

Dumb question but did you try the adb reboot bootloader command?

BoredKender said:
Dumb question but did you try the adb reboot bootloader command?
Click to expand...
Click to collapse
Yes and it simply reboots the phone. Does not go to the bootloader at all. Not a dumb question by the way. Pretty good to ask.

AngryManMLS said:
The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.
Click to expand...
Click to collapse
some variants doesnt have fastboot if im not wrong

J0SH1X said:
some variants doesnt have fastboot if im not wrong
Click to expand...
Click to collapse
I suspect that's the case with the T-Mobile variant. I wouldn't be shocked if there's a backdoor method found to getting fastboot to work on such variants as I can still get into download mode easily along with recovery. So I'm sure there's a way to use either one of these to getting fastboot to work.

AngryManMLS said:
I suspect that's the case with the T-Mobile variant. I wouldn't be shocked if there's a backdoor method found to getting fastboot to work on such variants as I can still get into download mode easily along with recovery. So I'm sure there's a way to use either one of these to getting fastboot to work.
Click to expand...
Click to collapse
the problem is i think ur phones abl partition doesnt contain fastbootd , and since T-Mobile variant has different RSA keys then other variants you cant crossflash it with some variant that includes twrp

J0SH1X said:
the problem is i think ur phones abl partition doesnt contain fastbootd , and since T-Mobile variant has different RSA keys then other variants you cant crossflash it with some variant that includes twrp
Click to expand...
Click to collapse
Fudge... I figured that someone who knows way more than I do would prove my idea would not work.
No method to add fastboot to the abl partition I'm assuming? Just throwing ideas out there.

AngryManMLS said:
Fudge... I figured that someone who knows way more than I do would prove my idea would not work.
No method to add fastboot to the abl partition I'm assuming? Just throwing ideas out there.
Click to expand...
Click to collapse
i have no idea just sharing what ive learnt from my g6 and g7, as on g7 the TMO is the only one not unlockable , bcs of its rsa keys

J0SH1X said:
i have no idea just sharing what ive learnt from my g6 and g7, as on g7 the TMO is the only one not unlockable , bcs of its rsa keys
Click to expand...
Click to collapse
A shame really. :crying:

AngryManMLS said:
A shame really. :crying:
Click to expand...
Click to collapse
yeah if u buy lg always watch out , i always wait till i buy a new phone to see if it can be unlocked i probably buy g8 at some time and i need unlock bl i cant stand the lg rom

J0SH1X said:
yeah if u buy lg always watch out , i always wait till i buy a new phone to see if it can be unlocked i probably buy g8 at some time and i need unlock bl i cant stand the lg rom
Click to expand...
Click to collapse
Someone has a engineering bootloader that allows you to unlock bootloader working on the g7 andv40 and v35 mabye works on g8 you need to use jtag from octoplus though.

Any other info yet?
Verizon
LM-G820UM

I'm pretty sure they'll update their Bootloader Unlock Key page in the next few weeks and add the G8(S) to the list of supported devices.
The unlocked G8S at least boots into Fastboot and also explicitly describes and explains how to unlock the bootloader. So there's that.

AngryManMLS said:
The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.
Click to expand...
Click to collapse
AngryMan, I have an unlocked G8 that I got from Amazon. I tried your "Up then plugging in" method and got to the download mode and a screen that said "Firmware Update" But from there, I couldn't get into anywhere else - no Recovery, and no broken Android logo. How did you get into the recovery mode. I would like to try that on my unlocked version of the G8

Robin M said:
AngryMan, I have an unlocked G8 that I got from Amazon. I tried your "Up then plugging in" method and got to the download mode and a screen that said "Firmware Update" But from there, I couldn't get into anywhere else - no Recovery, and no broken Android logo. How did you get into the recovery mode. I would like to try that on my unlocked version of the G8
Click to expand...
Click to collapse
It's volume down and plugging in the cable. What @AngryManMLS edited in as well.
If your device is unlockable it should lead you to fastboot mode with (more or less) detailed instructions on how to unlock the bootloader.
I "only" own a G8s but it should be the same for the other variants.
{
"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"
}

Frau Son said:
It's volume down and plugging in the cable. What @AngryManMLS edited in as well.
If your device is unlockable it should lead you to fastboot mode with (more or less) detailed instructions on how to unlock the bootloader.
I "only" own a G8s but it should be the same for the other variants.
Click to expand...
Click to collapse
Thanks. It didn't work on mine. I have a carrier unlocked version that I got from Amazon - $350 discount on Prime Day. (It's an LM-G820QM model with no digital assistant key and the Alexa apps added.) All I get when when using the volume down key (even with plugging in the cable afterwards) is the attached Factory Reset screen... I cannot get to the screens AngryMan saw.

I have an LM-G820QM unlocked I got from a bestbuy a couple weeks after launch. I can use adb reboot bootloader to get into fastboot. I followed the instructions on the LG bootloader unlock page. I got the device ID and IMEI put in and it told me my device doesn't support bootloader unlocking or some nonsense. I was pretty disappointed because I thought buying the unlocked variant it would be unlockable by LG. I seem to be the only person with this vairant here so if I can help the effort in any way, please let me know.

Moto G7 Power Root with Magisk NOT TWRP

My intent is to prevent crying and gnashing-of-teeth
Thanks to my retailer's very forgiving return policy I am up and happily running fully ROOTed (But after bricking two phones)
1. Get a copy of the Factory ROM (others have posted online - so hard work done.)
https://mirrors.lolinet.com/firmware/moto/ocean/official/CC/
I used XT1955-5_OCEAN_CCAWS_9.0_PPO29.114-30_cid50_subsidy-CCAWS_regulatory-DEFAULT_CFC.xml.zip
You can check which your phone is using Settings->System->About then Build Number at the bottom
2. Open the zip and copy the boot.img to the phone
3. Install "Magisk Manager" from Play Store
4. Use Magisk Mangers to create a "magisk_patched.img" from the boot.img and move the magisk_patched.img to your adb fastboot folder on the PC
5. Use fastboot to flash the magisk_patched.img
fastboot flash boot_a magisk_patched.img
the _a is important
If phone acts weird after, used bootloader to factory restore and believe it or not the magisk_patched stays flashed
See Restore Below
Install adb fastboot see
https://forum.xda-developers.com/android/software/windows-adb-fastboot-installer-sdk-t3516898
UNLOCK the Bootloader
(Motorola Mobility helps you with this but VOIDS the Factory Warranty)
1. Boot into bootloader –
(i). turn phone off,
(ii). hold volume-down and power together boots to bootloader
2. Plug phone into computer via USB-C
3. Open command prompt window
(i). In “type here to search” just type cmd
(ii). Right-Click Command Prompt in pop-up and select “Run as Administrator”
4. Test Fastboot
(i). Type “fastboot devices” (plural) in Command Prompt Window
(ii). It will return you phone’s ID. If it doesn’t return your device ID - your adb fastboot installation need attention, probably drivers
5. Now type the fastboot instruction
(i). fastboot oem get_unlock_data
6. The Phone will return 4 values
7. Combine all 4 values into a SINGLE string and go to
https://support.motorola.com/us/en/bootloader
HINT: After signing up and logging in click on SKIP this for now
these unlock bootloader instructions with more detail are on this site
8. Input the SINGLE string on the website (input box found below the instructions) it will email you your UNIQUE UNLOCK CODE
You have to click Send Code and OK on the Warranty pop-up box TWICE
9. Unlock using the fastboot command
fastboot oem unlock UNIQUEUNLOCKCODE
fastboot to flash
1. Boot into bootloader – see steps #1 thru #4 above
(i). fastboot devices
2. Now type your fastboot instruction
fastboot flash boot_a magisk_patched.img
Restore
If selecting Recovery Mode from within Bootloader (volume keys to move between, power button to select) returns
No Command
You have to press and hold the power button. Now press and release the volume up button but continue to hold power button
After this, you can see a list with option of Wipe data/ factory reset
SEE ALSO & Credit given to diversenerd
https://forum.xda-developers.com/g7-power/how-to/versions-moto-g7-power-supra-magisk-t3923857

Attached is a boot logo for unlocked bootloader's that will hide the code that is displayed after installing a magisk patched bootloader.
Unzip and install via fastboot:
Nothing fancy, but gives bootups a cleaner look.
{
"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"
}
View attachment BootLogo_mg7p.zip
Sent from my moto g(7) power using Tapatalk

I keep seeing guides on rooting the G7 Power XT1955-5
I have Verizon's G7 Power XT199-6
Will this work with my model?

Kinobody said:
I keep seeing guides on rooting the G7 Power XT1955-5
I have Verizon's G7 Power XT199-6
Will this work with my model?
Click to expand...
Click to collapse
Does your device have a switch in developer options that says something about unlock bootloader? Can that switch be moved or is it greyed out?
Most Verizon devices have encrypted bootloader's and cannot have their bootloader's unlocked because Verizon encrypts them and has for quite some time now.

flash713 said:
Does your device have a switch in developer options that says something about unlock bootloader? Can that switch be moved or is it greyed out?
Most Verizon devices have encrypted bootloader's and cannot have their bootloader's unlocked because Verizon encrypts them and has for quite some time now.
Click to expand...
Click to collapse
Yeah it has a switch it says " allow bootloader to be unlocked" it's it greyed out. I switched it to on.

Kinobody said:
Yeah it has a switch it says " allow bootloader to be unlocked" it's it greyed out. I switched it to on.
Click to expand...
Click to collapse
So see if Motorola will give you an unlock code. There is a guide for all of this...
https://forum.xda-developers.com/g7-power/how-to/versions-moto-g7-power-supra-magisk-t3923857

Vortell said:
So see if Motorola will give you an unlock code. There is a guide for all of this...
https://forum.xda-developers.com/g7-power/how-to/versions-moto-g7-power-supra-magisk-t3923857
Click to expand...
Click to collapse
Okay, but do you know if it matters if I have the model number XT1955-6? This thread tutorial says it works for all models and variants but it only has download links for XT1955-5, does the model number really matter?

Kinobody said:
Okay, but do you know if it matters if I have the model number XT1955-6? This thread tutorial says it works for all models and variants but it only has download links for XT1955-5, does the model number really matter?
Click to expand...
Click to collapse
As i stated the first step is get the unlock code. Then you can unlock the bootloader. Which means you can root it. Since it says all i assume it will work either way you can post in that thread. First i suggest you search it for your model or carrier.

Kinobody said:
Yeah it has a switch it says " allow bootloader to be unlocked" it's it greyed out. I switched it to on.
Click to expand...
Click to collapse
If the switch doesn't allow you to move slider then it is probably encrypted by Verizon like all Verizon devices, well about 99% of their devices are nowadays. If the bootloader is indeed encrypted then there's nothing that can be done as far as I know because Verizon holds the keys to it and I've never read anything that said they have given that info up to anyone for anything. I may be wrong about this but greyed out "allow bootloader to be unlocked" is a red flag that to me mean it's encrypted and being a Verizon sold model device they're the ones who encrypted it.. Id do more research on it and if it is what I believe it may be maybe ask Verizon if they'll allow you to activate an unlocked Moto g7 power and if they say yes get an unlocked model and see about hooking it up through them but idk their policy about that they're pretty strict from what I've heard.. Worth a shot though. But if you do decide to go that route make sure lte bands and all match up to what Verizon uses , you know ... I search a bit later today and see if I can locate any more info on this model... If I do I'll send you a message with links.
Edit added:
***Just reread your replies ..
If you switched it to allow bootloader unlocking then I'd proceed with unlocking it and see what happens. I thought you meant it didn't allow to move the switch. If I was in your shoes I'd proceed with the unlocking bootloader. It will either work or it won't. Just remember it does delete all your data ..

I too have the 1955-6 My OEM unlock toggle works, I can enable it but Motorolas thing said it couldn't be unlocked. I stayed on the phone with Verizon for over an hour getting moved up to different people and thought I was getting somewhere until they said they said it was on Motorolas end..lol

GarrettVW67 said:
I too have the 1955-6 My OEM unlock toggle works, I can enable it but Motorolas thing said it couldn't be unlocked. I stayed on the phone with Verizon for over an hour getting moved up to different people and thought I was getting somewhere until they said they said it was on Motorolas end..lol
Click to expand...
Click to collapse
U need to get that conversation recorded or if done in chat a copy of the chat and precedent it to the Moto techs on the bootloader stuff

Well I also stayed on the phone with Motorola for an hour and explained everything. They said that phone cant be unlocked and they dont have the power to create me a code because Verizon having them come locked. They kinda each blamed each other. I should have 3 wayed them I guess lol

Kinobody said:
I keep seeing guides on rooting the G7 Power XT1955-5
I have Verizon's G7 Power XT199-6
Will this work with my model?
Click to expand...
Click to collapse
You'll want to go here:
https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/
Then check your phone's Build Number to verify that you download the correct file. Mine was this one:
XT1955-6_OCEAN_VZW_9.0_PDOS29.114-134-12_cid2_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip
I hope this helps.

MrHallows said:
You'll want to go here:
https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/
Then check your phone's Build Number to verify that you download the correct file. Mine was this one:
XT1955-6_OCEAN_VZW_9.0_PDOS29.114-134-12_cid2_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
How will that help us to unlock the bootloader or obtain root? I was wondering if it was possible to flash the XT-1955-5 firmware and it allow the bootloader to be unlocked. Im sure it wouldn't work though.

GarrettVW67 said:
How will that help us to unlock the bootloader or obtain root? I was wondering if it was possible to flash the XT-1955-5 firmware and it allow the bootloader to be unlocked. Im sure it wouldn't work though.
Click to expand...
Click to collapse
If u use the 1955-5 and can find an program to flash it then u be able to root

roadkill42 said:
If u use the 1955-5 and can find an program to flash it then u be able to root
Click to expand...
Click to collapse
Thats the thing. What program would I use to flash it? I just feel like something is bound to go wrong lol. So if I were to flash the 1955-5 firmware, its going to give me a new code to use on Motorola's website? My OEM unlock switch does toggle on and off, which I assume doesnt mean much of anything lol

GarrettVW67 said:
Thats the thing. What program would I use to flash it? I just feel like something is bound to go wrong lol. So if I were to flash the 1955-5 firmware, its going to give me a new code to use on Motorola's website? My OEM unlock switch does toggle on and off, which I assume doesnt mean much of anything lol
Click to expand...
Click to collapse
It don't really on Verizon devices
---------- Post added at 10:20 PM ---------- Previous post was at 09:49 PM ----------
GarrettVW67 said:
Thats the thing. What program would I use to flash it? I just feel like something is bound to go wrong lol. So if I were to flash the 1955-5 firmware, its going to give me a new code to use on Motorola's website? My OEM unlock switch does toggle on and off, which I assume doesnt mean much of anything lol
Click to expand...
Click to collapse
It don't really on Verizon devices u can try rsd light it might do it for u check I to it

I'm sorry but what does the above mean, "It don't really on Verizon devices". I understand the English but I don't understand the answer in the context of the discussion. Thank you.

zapjb said:
I'm sorry but what does the above mean, "It don't really on Verizon devices". I understand the English but I don't understand the answer in the context of the discussion. Thank you.
Click to expand...
Click to collapse
Most Verizon phones can't be rooted . This software the rsd light might b able to root the Verizon phone try at ur own risk

I followed Op's steps and it worked, rooted.
I read somewhere that for A/B partition, we may need this additional step:
fastboot flash boot_b magisk_patched.img
Question is, do we really need _b flashed also? Thanks,

Question Is there a noob guide for rooting the Motorola G10?

So I bought myself the Motorola G10 phone just today and I'm interested in getting it rooted.
Is there a guide pasted somewhere for this phone? So I don't mess up my phone. There's Guides on Google but I don't trust any of them. Would prefer to get it from this forum.

jake7901 said:
So I bought myself the Motorola G10 phone just today and I'm interested in getting it rooted.
Is there a guide pasted somewhere for this phone? So I don't mess up my phone. There's Guides on Google but I don't trust any of them. Would prefer to get it from this forum.
Click to expand...
Click to collapse
[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

sd_shadow said:
[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
Thanks.
You wouldn't happen to know a way to get the OEM part unlocked? I hear from google results and a couple of XDA threads that it's some sort of security feature and that it'll be unlocked within a couple of days but I'm kind of impatient. It's been about a day now and I really want to get this phone Rooted as soon as possible.
The oem part being grayed out is putting a halt on everything. I've already gone through the process on the motorola website to attempt to unlock the bootloader with the access key and my phone can be unlocked... but can't tick the oem box...

jake7901 said:
Thanks.
You wouldn't happen to know a way to get the OEM part unlocked? I hear from google results and a couple of XDA threads that it's some sort of security feature and that it'll be unlocked within a couple of days but I'm kind of impatient. It's been about a day now and I really want to get this phone Rooted as soon as possible.
The oem part being grayed out is putting a halt on everything. I've already gone through the process on the motorola website to attempt to unlock the bootloader with the access key and my phone can be unlocked... but can't tick the oem box...
Click to expand...
Click to collapse
Connect the device to internet, it will be available in 3-14 days.

sd_shadow said:
Connect the device to internet, it will be available in 3-14 days.
Click to expand...
Click to collapse
... I did. Damn 3-14? I should not have bought this phone...

jake7901 said:
... I did. Damn 3-14? I should not have bought this phone...
Click to expand...
Click to collapse
In bootloader mode you can try
Code:
fastboot flashing unlock
Some have report this as working.

sd_shadow said:
In bootloader mode you can try
Code:
fastboot flashing unlock
Some have report this as working.
Click to expand...
Click to collapse
{
"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"
}
Tried. I don't think it worked or I did something wrong.
Then I tried this
I put adb.exe and fastboot.exe into the system32 folder. I tested it earlier with the unlock code tutorial found on the motorola website and that worked but for some reason I can't get this command to work.

jake7901 said:
Tried. I don't think it worked or I did something wrong.
Then I tried this
Click to expand...
Click to collapse
You have the code use it
Code:
fastboot flashing unlock code

sd_shadow said:
You have the code use it
Code:
fastboot flashing unlock code
Click to expand...
Click to collapse
No luck
I think my adb files broke or something I don't know what's going on. Was working yesterday.

jake7901 said:
No luck
I think my adb files broke or something I don't know what's going on. Was working yesterday.
Click to expand...
Click to collapse
No
Code:
fastboot flashing unlock "code"

sd_shadow said:
No
Code:
fastboot flashing unlock "code"
Click to expand...
Click to collapse
Daemon wasn't started hence why the commands wasn't working so I restarted that and went back into my fastboot and adb is not detecting my device
When my phone is on tho normally adb can detect it
You wouldn't happen to know why this is happening?
It doesn't detect it when I'm in fastboot.
EDIT: Nevermind I did "fastboot devices" and it pops up
Still can't get the above command to work tho.
If I try and unlock the bootloader the normal way I can't because oem is not enabled because it's grayed out and won't let me enable it
So I guess I'm screwed...

jake7901 said:
Daemon wasn't started hence why the commands wasn't working so I restarted that and went back into my fastboot and adb is not detecting my device
When my phone is on tho normally adb can detect it
You wouldn't happen to know why this is happening?
It doesn't detect it when I'm in fastboot.
EDIT: Nevermind I did "fastboot devices" and it pops up
Still can't get the above command to work tho.
If I try and unlock the bootloader the normal way I can't because oem is not enabled because it's grayed out and won't let me enable it
So I guess I'm screwed...
Click to expand...
Click to collapse
You have to wait something like 48/72 hours and OEM unlock option will "unlock", then you can proceed with fastboot oem unlock *code*. It was driving me crazy too, then I found out some people on Lenovo forums saying that it magically un-greyed out after some days, so I just waited 3 days and it was actually true. Unfortunately chinese phones have their own "particularities" when it comes to unlocking bootloader.

obrobrio2000 said:
You have to wait something like 48/72 hours and OEM unlock option will "unlock", then you can proceed with fastboot oem unlock *code*. It was driving me crazy too, then I found out some people on Lenovo forums saying that it magically un-greyed out after some days, so I just waited 3 days and it was actually true. Unfortunately chinese phones have their own "particularities" when it comes to unlocking bootloader.
Click to expand...
Click to collapse
Did yours say "Connect to the internet or contact your operator"? Cause I'm worried mine is not gonna get unlocked.
It's connected to Wifi.

It's now been 3 days... still grayed out

It's now unlocked but I'm having issues.
I can't get the firmware to download through rescue and smart assistant.
So I have to use an external link. Which one do I download from this?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

jake7901 said:
It's now unlocked but I'm having issues.
I can't get the firmware to download through rescue and smart assistant.
So I have to use an external link. Which one do I download from this?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
You need to know these 4 things
Device Model #, Codename, and Software Channel.
Build number

sd_shadow said:
You need to know these 4 things
Device Model #, Codename, and Software Channel.
Build number
Click to expand...
Click to collapse
It's all good I got it.
I just downloaded a random build off that lolinet website from the RETEU folder > put the boot.img file onto my phone > ran magisk to patch it > then used adb to flash the magisk rom and that was it.
Ran root checker and it says I'm rooted so I did it!
Thanks for your help man.
It took me over an hour to figure out that tutorial of yours since it wasn't that clear but got it figured out at the end.