Database Info

Root for MetroPCS/T-Mobile LG Stylo 2 Plus Android 7.0 Nougat ( LGMS550 & LGK550 )

Root for MetroPCS/T-Mobile LG Stylo 2 Plus Android 7.0 Nougat ( LGMS550 & LGK550 )
Everything you need to root your LG Stylo 2 Plus running on Android 7.0 is packed into Stylo2.zip for convenience
If the link ever goes down send me a private message, I'll have a few backups of this laying around.
This method works on MetroPCS (LGMS550) and T-Mobile (LGK550) phone models.
Stylo2.zip​(35.6mb)
VirusTotal Scan
Click to read the guide​
Before doing anything, on your computer you need to extract Stylo2.zip to your Desktop, and install:
minimal_adb_fastboot_v1.4.1_setup.exe (Install this into the Stylo2 folder)
PhoneDrivers.exe
1. Enable Developer Options on your phone, and navigate to the Developer Options page.
Enable OEM unlock
Enable USB debugging
Enable File Transfer
Place no-verify-opt-encrypt-5.1.zip and SuperSU.zip onto your external sd card.
2. After placing the two zip files into the root of your sd card
Enable Charging mode
Authorize your computer for USB debugging
3. Launch MAF32.exe from the Stylo2 folder
(This is Minimal ADB and Fastboot)
4. In the window that pops up type:
adb devices
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2>
5.Boot into the bootloader by typing
adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2>
6. Next you will be unlocking the bootloader
(This will erase everything on the Internal Storage)
In the PowerShell window you will need to type:
fastboot oem unlock
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2> fastboot oem unlock
...
(bootloader) Erasing userdata and cache
OKAY [ 12.386s]
finished. total time: 12.389s
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2>
Your data should now begin to wipe.
7. Once finished with the data wipe, you will need to flash the recovery.img to your device.
In the PowerShell window you will need to type:
fastboot flash recovery recovery.img
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> fastboot flash recovery recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (15588 KB)...
OKAY [ 0.508s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.918s
PS C:\Users\Hyperion\Desktop\Stylo2>
This is where it can get tricky.
8. Turn your phone off.
Unplug your USB cable
Take out your battery
Put your battery back in
Read next step before turning your phone back on
9. You will now need to boot into TWRP, which isn't the most fun thing to do.
(This process begins after the screen prompt that says your phone can't be authorized has already came up.[if it pops up at all])
Get comfortable with this process before attempting it.
Hold Vol Down + Power (Don't let go)
Once you see the LG Logo let go of the power button briefly
Press the power button while still holding Vol Down
Don't let go until a white Factory Reset screen comes up.
Select Yes, then on the next screen select Yes again
(This should boot you into the flashed TWRP Recovery Image)
If you do not boot into TWRP, repeat Process 1-8 until success
(excluding unlocking your bootloader, once unlocked it does not need to be unlocked again.)
10. Assuming you are in the TWRP menu, you will need to wipe the device again.
Navigate to WIPE in the top right
Follow on screen instructions to wipe the device
Click Reboot, and choose Recovery
It wouldn't be a bad idea to make a Backup at this point
11. Once back at the TWRP menu again, you will need to start flashing .zip files.
Click Install
Click Select Storage in the bottom left
Select no-very-opt-encrypt-5.2.zip
Swype to confirm Flash
Press back until at the TWRP main menu again
Click Install
Select SuperSu.zip
Swype to confirm Flash
Some people have had better luck flashing no-very-opt-encrypt after flashing supersu. (I can not confirm this)
12. Reboot to system, let the thing boot loop a couple times at the MetroPCS screen
Cross your fingers until your phone boots up
Download a Root Checker
Check your root access.
If all went well your MS550/K550 running Android 7.0 Nougat should be rooted
I hope it went well xD
-Mike​
Thanks to:
Danielhammons1/Reemitch (For notifying me about a missing step between steps 4 and 5)

I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).

i am stuck at fastboot oem unlock it doesnt do anything will you please contact me at [email protected]

wellsweb said:
I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).
Click to expand...
Click to collapse
I believe between number 4 and 5, so at 4.5 you must enter the command "adb reboot bootloader" in order to enter fastboot mode.

some help please, stuck on step 4
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks

cruba001 said:
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks
Click to expand...
Click to collapse
That was completely my bad! I forgot I had setup adb and fastboot differently than in this guide, I updated the above post to reflect what you should actually be doing xD Thanks for catching that!~

Can i do this even though im an update behind?

Th3Joker2496 said:
Can i do this even though im an update behind?
Click to expand...
Click to collapse
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.

Dark Bulbasaur said:
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.
Click to expand...
Click to collapse
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'

Please help me lower fw lg stylo 2 plus ms550. thank you
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
Please help me unlock my bootload. ms550

Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.

Dark Bulbasaur said:
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.
Click to expand...
Click to collapse
im so lost bro you have skype?

I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?

Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE

BlackGTNinja said:
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE
Click to expand...
Click to collapse
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase

Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
Reflash TWRP on CMD and remove the battery and run twrp like in the instructions. Afterwards go to wipe, select format in TWRP and type "yes" (after you type "yes" the storage will be wiped. Nothing in internal storage.) and reboot to TWRP (make sure you got a sd card or computer to install rom). After the format, install rom. I don't know how to root on stock. Running LOS 64bit 7.1.2 on my Stylo 2 Plus.

Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
It was the Android Fastboot drivers was not configured right,I had to go to Device Mangager and Manually update drivers to Bootloader interface
http://visualgdb.com/KB/usbdebug-manual/

I hv searched for many websites and they said you should unlock bootloader to go further.
But on lg stylo 2 plus bootloader can't be unlocked it is not available on website .
Can anyone suggest me what i should do to forcefully unlock my bootloader.

xpurge1 said:
I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?
Click to expand...
Click to collapse
no you're not. just go into twrp, format data, mount the device, move the folders, and try flashing SuperSU BEFORE no verity.

I can't seem to flash the recovery. OEM is unlocked and everything else is correct but when i go to the step to flash, it tells me it cant be flashed.

softbricked pixel

Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !

luigigigi said:
Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !
Click to expand...
Click to collapse
Did you try turning the phone off and then using the power-on + volume down key to get to the bootloader menu? from there press the volume up key until you get to recovery and the press the power button. In recovery do a factory reset. That should take care of stuff. In future, don't use kingroot as it's a malware ridden app (that is if you care about your personal data). If you need root then use Magisk instead. Gives you root and also a root manager. If you are planning to tamper with root then make sure to have your bootloader unlocked. Let me know if factory reset worked.

yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.

luigigigi said:
yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.
Click to expand...
Click to collapse
I have one more idea you could try. Download latest OTA update from here: https://developers.google.com/android/ota
go into recovery and follow the instructions given on the link I just gave you and apply the update using adb sideload in recovery. (You have to manually get into recovery as you did before but follow the instructions from the point where you're inside the recovery.) This should work. Seems that kingroot/supersu corrupted your system somehow. Let me know if it worked.

i already came across that site because i was on android p, i didn't like it so i went back to nougat...anyway to say that i have the nougat image .zip , so do i have to download the latest firmware ?

ok ok, that's not the same...SORRY ?? !!

luigigigi said:
ok ok, that's not the same...SORRY ?? !!
Click to expand...
Click to collapse
yeah, it's not the same and you'll find the 8.1.0 update there and the updates from the past. Give it a go and tell me the results when you're done

i tried that, everything went as intended, when i power it up there's animations of 8.1 but still wont boot.
i tried to wipe data and boot again, nothing.
is there a way to flash stock rom with adb (just like we did with that update) ?

now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!

---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
luigigigi said:
now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!
Click to expand...
Click to collapse
It's the newer setup screen. Have you managed to boot into system. Is everything working?

Arju said:
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
It's the newer setup screen. Have you managed to boot into system. Is everything working?
Click to expand...
Click to collapse
no since i did a wipe ( i guess i shouldn't have done that) , now when it boots it is locked, it is asking for a pattern, wjch i don't know because i didn't set a pettern previously.
i guess i'm stuck here for ever ? ??

is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !

((((Update))))
I didn't notice that there was a connect to Google option, so I finally set up the phone with my Google account and I'm back in.
I'm very thankful to you man you saved my phone, thank you a lot.
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )

luigigigi said:
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )
Click to expand...
Click to collapse
I'm glad it worked itself out.
I'm from Norway. Married a swede so living in Sweden now. My parents are from Sri Lanka (the island below India) but moved to Norway before I was born. I've been to Sri Lanka once. Would like to travel to India sometime too :silly:
Algeria seems nice. Must be hot there. I've never been to Africa. Would like to travel there too some day

Yes totally, Algeria is really safe and people here won't bother you (like if you're wondering how u would be seen or received as a foreigner) there's foreigner all year round but especially in summer time, just have something planned in advance because it's Algeria not USA or another well developed country ? but still there's a lot to see here, definitely worth the visit.
When it comes to whether, well it's a Mediterranean weather so expect nice warm days, that being said, there's some time when it goes rainy with thunders and cold, for example now it is very pleasant outside, but yesterday the weather gone crazy... I guess that's because of the global warming.

luigigigi said:
is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !
Click to expand...
Click to collapse
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps

MpandAUS said:
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps
Click to expand...
Click to collapse
I'm sure this gonna help me in the future, as i'm planing to try some custom Rom's and i'm probably gonna brick it again so ? ... Thanks you ? !

[Recovery][cv1] TWRP 3.2.3.0 For LM-X210 Devices

Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled​
OEM Unlock Enabled​
ADB/Fastboot Device Drivers​
Your Phone/Brain​
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754​Latest USB Drivers --> https://www.lg.com/us/support/software-firmware-drivers​
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
Code:
adb devices
Code:
adb reboot bootloader
4. It should boot into fastboot mode. From there type:
Code:
fasboot devices
Code:
fastboot flashing unlock
5. To prevent fastboot from encrypting cache and data type:
Code:
fastboot erase userdata
Code:
fastboot erase cache
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
Code:
fastboot flash recovery rec.img
7. Now that you've flashed TWRP test it:
Code:
fastboot reboot recovery
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!

Downgrade?
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...

tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
Yah, it's still like that unfortunately. But you can downgrade to Nougat with LG Uppercut. You should just flash the TWRP on Nougat firmware because it's not locked. So when you downgrade just follow these steps to get Oreo. Also don't install Tec's version of Oreo Firmware. Just jump to my other thread for my Custom Stock ROM. Tec's flashes Oreo Firmware with Oreo Stock Rooted. But mine just flashes the nesassary Oreo Boot and System. The links on my signature.
By the way for anyone wondering the LG Phoenix 4 can be Rooted this way to.

NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled
OEM Unlock Enabled
ADB/Fastboot Device Drivers
Your Phone/Brain
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754
Latest USB Drivers --> http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
4. It should boot into fastboot mode. From there type:
5. To prevent fastboot from encrypting cache and data type:
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
7. Now that you've flashed TWRP test it:
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!
Click to expand...
Click to collapse
If fastboot flashing unlock fails try fastboot oem unlock

tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
As long as your bootloader is unlocked it won't be a problem at least on the LG Phoenix 4 it can have TWRP with Oreo

hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal tengop a lg k9 x210em I do not understand the truth any suggestion excuse my English

hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion

tazlooney89 said:
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion
Click to expand...
Click to collapse
on my device is the same

Problem!!!
I do what you write in tutorial but my phone dont run on fastboot mode Please HELP!!!

Do we know anything about unbricking these phones? I've got a US Cellular K8+ (LG-X210ULM) that my wife accidentally bricked a while back while trying to flash TWRP (not this particular build, obviously). I think she said everything seemed fine and then on reboot...well, it just never turned on again. PC doesn't pick it up at all, no Qualcomm mode or anything. Based on that, I had assumed it was a lost cause that would take JTAG to bring back, and it may well be...
...but then I noticed something unusual the other day. For the hell of it, I decided to plug it into a charger and let it sit for a while. I got what I expected, which was nothing at all. Oh well. Anyway, I happened to be working with another X210 at the time but only had one battery handy, so I just popped the one out of the "dead" phone without unplugging it and went about with what I was doing. After about 5-10 minutes, something caught my eye - sure enough, the dead phone's screen was now on, displaying the "?" battery screen. I put the battery back into the phone and got unceremoniously dumped straight back to black nothingness. Oh well.
So yeah, the phone still doesn't seem to respond to anything when connected to the PC with no battery, so it's probably a no-go, but the fact that it still shows the no-battery screen tells me it's not quite *as* bricked as I thought it was at least. Any ideas? Are we lucky enough to do a boot-from-SD trick on this phone?

Lmx210cm twrp
Do you happen to have anything for the lmx210cm?

Ausboz said:
Do you happen to have anything for the lmx210cm?
Click to expand...
Click to collapse
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
I tested oreo and it works file

AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Hi would mind telling how to flash that firmware amd whats the prog_+++++++ddr.mbn to flash i have aristo 2 android 8.1 metro and i cant do any flash in fastboot or root it anything you know about it will be appreciated so much...

@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM

tazlooney89 said:
@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM
Click to expand...
Click to collapse
Have you tried installing the Aristo 2 firmware on your phone? In theory these phones have the same build and processors. Also in theory, but proven to work on some other cv1 devices (LG Phoenix 4), you should be able to flash Aristo 2 firmware and unlock your phone that way. I would also check your system.img to see if anything such as a security patch is in place to keep your phone from rebooting to the bootloader. You can backup the system.img manually and send me the img and I will look for anything that different from the Aristo 2 system.img.
Also by backing up the system.img and sending it to me, I can retrieve any "extra" carrier settings and add them to the cv1 img. I'm working on a full stock cv1 firmware img that will work on all the cv1 devices as a root strategy.

I have Lg K9 ( lmx210em ) and it's IMPOSSIBLE enter in fastboot mode, either with key combinations, either with adb command... The phone always boot in normalk mode !!!
Download mode and recowery mode work properly, but fastboot mode DID NOT !!!

urgent
i need the firmware the phoenix 4 please

NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
..............
[/COLOR][/SIZE]
Click to expand...
Click to collapse
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.

i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?

jdthomas4181 said:
i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?
Click to expand...
Click to collapse
The issue you describe appears to be caused by kernel incompatibilities between certain partitions of the phone.
The fact that TWRP does not have the screen glitching issue implies that the kernel embedded in the TWRP image you flashed IS compatible, but perhaps the kernel within your boot image is NOT.
My first question would be:
You mention that you rooted your phone from fastboot.
Did you:
1. patch the stock boot image on your phone or
2. flash a pre-rooted boot image to your boot partition or
3. Flash a pre rooted ROM to your phone
If you answered #2 or #3, then my secondary question would be:
Specifically which boot image or ROM did you flash to your phone ?
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
noidodroid said:
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.
Click to expand...
Click to collapse
I did not get the edl package, but I really want it and of course his account is suspended.
Anybody have it ?
Also this method should be capable of working on your phone, as it is a cv1 device.
You may have to downgrade the firmware to Nougat before proceeding if the device is currently running Oreo.
If the device is currently running Oreo or later, you can downgrade the phone to Nougat using the LGUP utility

[BOOTLOADER UNLOCK] [NE1] [NOKIA 3] Guide To Unlock The Bootloader Of Nokia 3 [TA-1020,TA-1028,TA-1032,TA-1038]

This Guide is used to Unlock the Bootloader of Nokia 3 [NE1] for all the "TA" variants & also applicable on Android 7.X Nougat, Android 8.1 Oreo, Android 9.0 Pie.
Please follow the below steps carefully to unlock the handset succesfully.
First of all we need to convert our phone SN (Serial Number) to MD5 hash
For checking the SN dial *#06# OR Go to the settings > About Phone
MD5 HASH CHECKSUM
The output will be looks like
8AE2A2B4F0D939819F762798F14A4D34​
Code:
fastboot oem alive
After executing this command connect the USB cable, your device will boot into Fastboot mode/Download mode.​
Code:
fastboot devices
To Check wheather your devices connected or not, if connected you will find the device SN
Example: NE1GAMXXXXXXXXXX​
Code:
fastboot oem key <Your MD5 hash checksum>
​
Input your MD5 hash checksum that you've generated by device SN​
Code:
fastboot oem key 8AE2A2B4F0D939819F762798F14A4D34
​
Just taking as an example (How you need to put the MD5 key see above command)​
Code:
fastboot flashing unlock
After executing this command you will see the warning message on the screen
Now press Volume + button to continue the unlocking process.​
Code:
fastboot reboot
All Done!!
Device Bootloader Unlocked Succesfully.​Required files:
Platform Tools by Google (Make sure your device got installed with adb/fastboot driver)​
Nokia Driver (Required before executing the fastboot commands, otherwise the output will be NIL.​
​Please like the thread if its helpfull to you​- CRUECY​

Comment down if you've any queries regarding this.

Serial number (?
WORKED! Thanks brou

Bro it's not working please help me out
It is showing failed
---------- Post added at 09:25 AM ---------- Previous post was at 09:19 AM ----------
I have tried all the methods to root my nokia 3 given here but it's not working Every time i try to unlock Bootloader Using Command Fastboot oem unlock it doesn't work then I used Fastboot flashing unlock then new window comes in my phone saying press Volume up to unlock Bootloader when I press volume up button it shows failed and a msg comes in my command window that unlock not allowed then I tried with MD5 hash key still not working
My Oem unlock is on
My usb debugging is on
But still not working plzz help me out

Vishwas_shaji said:
Bro it's not working please help me out
It is showing failed
---------- Post added at 09:25 AM ---------- Previous post was at 09:19 AM ----------
I have tried all the methods to root my nokia 3 given here but it's not working Every time i try to unlock Bootloader Using Command Fastboot oem unlock it doesn't work then I used Fastboot flashing unlock then new window comes in my phone saying press Volume up to unlock Bootloader when I press volume up button it shows failed and a msg comes in my command window that unlock not allowed then I tried with MD5 hash key still not working
My Oem unlock is on
My usb debugging is on
But still not working plzz help me out
Click to expand...
Click to collapse
Hi, bro. I tried yesterday this method and worked for me.
Boot your phone to bootloader.
In adb/fastboot type this command: fastboot devices
Then it will show you the serial number of the device.
Copy it and go to the generator page, paste it there and now you have the key.
Now you just have to type the command: fastboot oem key "Here your MD5 hash key"
Now go further.

Now My nokia 3 Bootloader is unlocked and is showing orange state your device is unlocked and cannot be trusted and will boot in 5 sec
After that I tried to install twrp recovery it shows finished in my cmd window but when I try to boot to twrp recovery using command fastboot boot twrp.img my system doesn't boots into twrp recovery after that I tried to poweroff and boot to twrp recovery using volume and power buttons then also it doesn't boot to twrp recovery
Please give me a solution for this

Hello, your post is for TA-1032 for Android 9, I have TA-1020 Android 8.1.0, but I tried this and nothing changed, it just fails the unlock, even after I put the oem key.
You seem like you're good and you know what you're doing, can you please help me? https://forum.xda-developers.com/nokia-3/help/rooting-nokia-3-ta-1020-android-8-1-0-t4077501
Thank you so much.

It worked!
Thanks for the help. Still works in april. To clarify for others - the number that you need to put in the hash generator is the number that you get when you type *fastboot devices*.

Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?

quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
I haven't tried it yet in fear of bricking my device. What do you mean you got it installed? Can you boot into it at least once before it gets replaced with the stock recovery? Cus if you want twrp to be permanent, you need to flash root on your device. Also if you can't get it working on pie try downgrading as there are many threads for previous versions.

Not working, adb device in fastboot shows blank. nokia 3 drivers are installed, oem unlock enabled. Nokia 3 - 1032, Android 9.

quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
I have unlocked bootloader, TWRP, Magisk & removed encryption on Android 9.0 April security patch succesufuly. I tried to flash TWRP with SP Flash Tools but it just reverts back to stock recovery with No Command screen like you said. To install TWRP, use fastboot instead with fastboot command "fastboot flash recovery twrp.img". It works. To remove encryption, first format data than flash this in TWRP: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 This also solves issue with TWRP when TWRP can't read Internal storage. After that flash Magisk. That's it.

quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
You need to patch the boot.img by magisk then flash the twrp.img it will work...
In the version of Android 8.1 Oreo and 9.0 Pie boot.img patched required to boot Custom recovery TWRP....

Константинос said:
I haven't tried it yet in fear of bricking my device. What do you mean you got it installed? Can you boot into it at least once before it gets replaced with the stock recovery? Cus if you want twrp to be permanent, you need to flash root on your device. Also if you can't get it working on pie try downgrading as there are many threads for previous versions.
Click to expand...
Click to collapse
To install twrp in Nokia 3 Android 9 pie you must patch the boot.img by rooting with Magisk... after that twrp will successfully flash in your phone...
Thanks

blubbbb said:
Not working, adb device in fastboot shows blank. nokia 3 drivers are installed, oem unlock enabled. Nokia 3 - 1032, Android 9.
Click to expand...
Click to collapse
use Platform Tool by Google
Thanks

quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
My man if u get the no command screen press the power button and volume up key simultaneously

Hey there,
You think it'll work in a Nokia 3 TA-1028 with android 9ie?

caterham1888 said:
Hey there,
You think it'll work in a Nokia 3 TA-1028 with android 9ie?
Click to expand...
Click to collapse
Yes This method is applicable for TA-1020, TA-1028, TA-1032, TA-1038

What is MD5
Bro actually I am new in bootloader unlocking and root so I wanted to know what is MD5 key

My Nokia 3 TA-1032 failed to unlock with "fastboot flashing unlock" & "fastboot oem unlock". Anybody have some tipp about how to then? Thank you very much

Re-lock bootloader without OEM unlocking

It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"

Hyoretsu said:
It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"
Click to expand...
Click to collapse
What does getvar all say are the codename and software channel?
Sent from my perry_f using XDA Labs

sd_shadow said:
What does getvar all say are the codename and software channel?
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to
Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though
Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"

Hyoretsu said:
I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to
Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though
Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"
Click to expand...
Click to collapse
Did you check the flashfile.xml
For the official flash commands?
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Did you check the flashfile.xml
For the official flash commands?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
https://pastebin.com/X5TD77YS As far as I remember (just downloaded firmware file on phone) they're the same from the eraseandupdate.bat I was using
EDIT: Yeah, aside from it erasing modemst1 and modemst2 after flashing everything as opposed to after flashing FSG and reflashing FSG after that it's the same commands

Hyoretsu said:
OEM unlocking is still greyed out.
Click to expand...
Click to collapse
OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.

WoKoschekk said:
OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.
Click to expand...
Click to collapse
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)

Hyoretsu said:
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Click to expand...
Click to collapse
Usually that error is caused from using the wrong relocking commands
Are you using
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock

And mine is greyed out too

Hyoretsu said:
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Click to expand...
Click to collapse
Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.
I red that it's necessary to run the oem lock command a few times to make it work.

sd_shadow said:
Usually that error is caused from using the wrong relocking commands
Are you using
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)
WoKoschekk said:
Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.
Click to expand...
Click to collapse
Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.

Hyoretsu said:
I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)
Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.
Click to expand...
Click to collapse
Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.
I loose my IMEI on my Moto g6 plus, too. You won't be able to overwrite it because it is linked with your device and encrypted by Motorola. The location of these files is /persist/rfs.
If your IMEI is broken or corrupt you won't be able to restore it. Except you have a backup of your persist partition.
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
Try to relock your bootloader with the command provided in the screenshot (source: https://source.android.com/setup/build/running)
Screenshot
https://ibb.co/f2LzMzS

WoKoschekk said:
Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.
Click to expand...
Click to collapse
I get a bootloop when I install TWRP alone and when I install Magisk from bootable TWRP, been using the official one from twrp.me this whole time since the screen is bugged on unofficial one. I only ever installed both (in that order) when I was still trying to install Custom ROMs, but I kept getting bootloops for other reasons.

Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.
So install Magisk Manager
Copy the boot image from the firmware that you installed to your phone.
Run Magisk Manager, click update Magisk and Select patch boot.img
Navigate to the folder on you phone that you copied the boot image to
Wait until Magisk Manager patches it
Copy Patched_boot.img to your adb folder on your PC
From your PC command prompt:
adb reboot bootloader
Then
fastboot devices
If your phone serial # shows, then:
fastboot flash boot patched_boot.img
fastboot reboot
You should now have root and the unlock bootloader option in developer settings will not be greyed out.
There is another thread with these same instructions. That is what allowed me to relock my bootloader.
Sent from my moto g(7) power using Tapatalk

Also,
Now that you are able to relock your bootloader, you could hold off until 10 is out.
If you don't like the unlocked bootloader message on startup, flash the attached logo.img fileView attachment BootLogo_mg7p.zip
Sent from my moto g(7) power using Tapatalk

MrCamby said:
Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.
So install Magisk Manager
Copy the boot image from the firmware that you installed to your phone.
Run Magisk Manager, click update Magisk and Select patch boot.img
Navigate to the folder on you phone that you copied the boot image to
Wait until Magisk Manager patches it
Copy Patched_boot.img to your adb folder on your PC
From your PC command prompt:
adb reboot bootloader
Then
fastboot devices
If your phone serial # shows, then:
fastboot flash boot patched_boot.img
fastboot reboot
You should now have root and the unlock bootloader option in developer settings will not be greyed out.
There is another thread with these same instructions. That is what allowed me to relock my bootloader.
Sent from my moto g(7) power using Tapatalk
Click to expand...
Click to collapse
Ty, this was the only way in which I could get root in stock. Although the Allow OEM Unlock is still greyed out it now has the same message as before I unlocked the bootloader for the first time, though if it acts the same way it'll be available in a few days. IMEIs and SIMs still aren't working though, but eh. At least I can try testing the locking bootloader theory to get them working again (IMEI not working = can't even see any of them in settings)
MrCamby said:
Also, now that you are able to relock your bootloader, you could hold off until 10 is out.
Click to expand...
Click to collapse
Also Motorola still allows unlocked users to receive OTA for some reason, my device updated and it's still working

To repair your IMEI on a G7 power, this is what worked for me:
Remove your sim card.
Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.
Startup in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.
Sent from my moto g(7) power using Tapatalk

MrCamby said:
To repair your IMEI on a G7 power, this is what worked for me:
Remove your sim card.
Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.
Startup in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.
Click to expand...
Click to collapse
No luck unfortunately, still don't have IMEI/SIM. Once I can I'll try relocking bootloader and maybe sending it to warranty, since apparently using a tool to re-write IMEI won't work on this phone. (Followed to the T, unless unlocking it after flashing and waiting for microSD messes it up)

Did you try the LMSA software to try and fix it. There are two options: update and repair.
Sent from my moto g(7) power using Tapatalk

MrCamby said:
Did you try the LMSA software to try and fix it. There are two options: update and repair.
Click to expand...
Click to collapse
I tried using it back when I was trying to go back to stock "the right way" (to try and solve the lost IMEI, go back stock and re-lock bootloader) but it couldn't even recognize my phone so that I could download anything