[guide] [root] [oreo&pie] [jeter/aljeter] [twrp, decrypt, magisk] [stock firmware]

[madbat99]

Your phone is network unlocked, meaning you can use it on any network. to root you would need to bootloader unlock. Which just opens up the software to modification. And on the g6 play you can still take ota updates with an unlocked bootloader if you haven't modified the software.
And even if you have, all you have to do is reflash the stock firmware to be able to update again. Your phone is very forgiving as far as rooting and unlocking. There are a few exceptions to which brand will let you unlock the bootloader though.
As far as the updates, you don't have to take them. There's an option in developer settings to turn off automatic updates, and you can disable Motorola update services as well to get rid of any annoying update notification

Tell'em killer. LoL

 

[Starkiller2]

Edit: Fixing my rude

 

[Spaceminer]

Is this for real? He's for real?

Yes, absolutely. After Pie everyone needs to use the same twrp. Here's my newer one. I've added the ability to back up and restore the oem partition. I'm working on 64bit, no promises on that. It's a real pain to be honest.

 

[Starkiller2]

Yes, absolutely. After Pie everyone needs to use the same twrp. Here's my newer one. I've added the ability to back up and restore the oem partition. I'm working on 64bit, no promises on that. It's a real pain to be honest.

Sorry, I was referring to the other guy. I just being mildly rude and I apologise
Thank you for the updated twrp though. Something weird is going on lately with everything, gsis, twrp, decryption. I'm having a fun time with all of it. Lol. I'm sure the twrp can only improve things. Bless you

 

[Spaceminer]

Sorry, I was referring to the other guy. I just being mildly rude and I apologise
Thank you for the updated twrp though. Something weird is going on lately with everything, gsis, twrp, decryption. I'm having a fun time with all of it. Lol. I'm sure the twrp can only improve things. Bless you

What weirdness are you experiencing? I'll look into it.

 

[Starkiller2]

What weirdness are you experiencing? I'll look into it.

Every gsi I've tried lately is hanging, and if I try to use gapps they bootloop. Or everything just crashes. I haven't had the time to sit down and test everything. I was gonna do that tonight. I know there were a few other people having issues as well so I was hoping to at least narrow down where the problem is coming from. I'll collect some logs tonight and maybe you can decipher what I'm doing wrong. Lord knows I can't. Everything seems to be fine until I connect to the play store. Even with the modules in place

 

[Spaceminer]

Every gsi I've tried lately is hanging, and if I try to use gapps they bootloop. Or everything just crashes. I haven't had the time to sit down and test everything. I was gonna do that tonight. I know there were a few other people having issues as well so I was hoping to at least narrow down where the problem is coming from. I'll collect some logs tonight and maybe you can decipher what I'm doing wrong. Lord knows I can't. Everything seems to be fine until I connect to the play store. Even with the modules in place

Gapps crashing more than likely isn't a twrp problem, but I'll still check on that if you get a log. GSIs shouldn't be hanging though, and that probably is a twrp problem, unless it's just a simple user error. I personally haven't had any problems. I'd appreciate some logs so I can see what's going on. It might be something stupid, or it could be something much worse. I should definitely check it out in any event.

For the twrp related logs, don't flash gapps or magisk. Just do your wipes, flash the GSI, then see if it boots up. Some GSIs take awhile to boot. Havock OS does. I recently tried that one, and I swear it took like 7min, but it did boot up and work. Definitely give it a good 5-7min, then grab a log if it doesn't go anywhere. Not flashing magisk or gapps will make the log much easier for me to read and help narrow down the GSI specific issue you're having.

Edit: What model is your phone? Also, you should try using the latest twrp I just posted.

 

[Starkiller2]

Gapps crashing more than likely isn't a twrp problem, but I'll still check on that if you get a log. GSIs shouldn't be hanging though, and that probably is a twrp problem, unless it's just a simple user error. I personally haven't had any problems. I'd appreciate some logs so I can see what's going on. It might be something stupid, or it could be something much worse. I should definitely check it out in any event.

For the twrp related logs, don't flash gapps or magisk. Just do your wipes, flash the GSI, then see if it boots up. Some GSIs take awhile to boot. Havock OS does. I recently tried that one, and I swear it took like 7min, but it did boot up and work. Definitely give it a good 5-7min, then grab a log if it doesn't go anywhere. Not flashing magisk or gapps will make the log much easier for me to read and help narrow down the GSI specific issue you're having.

Edit: What model is your phone? Also, you should try using the latest twrp I just posted.

I have the 1922-7 boost Mobile.
See that's the thing. Most of the gsis work great until I flash gapps. And trying one with gapps baked in is useless. I don't think it's twrp related but at least using your new one it can be ruled out.
No worries. I'll get you clean logs. I'm gonna reflash stock and start from scratch

 

[Starkiller2]

Gapps crashing more than likely isn't a twrp problem, but I'll still check on that if you get a log. GSIs shouldn't be hanging though, and that probably is a twrp problem, unless it's just a simple user error. I personally haven't had any problems. I'd appreciate some logs so I can see what's going on. It might be something stupid, or it could be something much worse. I should definitely check it out in any event.

For the twrp related logs, don't flash gapps or magisk. Just do your wipes, flash the GSI, then see if it boots up. Some GSIs take awhile to boot. Havock OS does. I recently tried that one, and I swear it took like 7min, but it did boot up and work. Definitely give it a good 5-7min, then grab a log if it doesn't go anywhere. Not flashing magisk or gapps will make the log much easier for me to read and help narrow down the GSI specific issue you're having.

Edit: What model is your phone? Also, you should try using the latest twrp I just posted.

Apparently it was twrp related. After using the updated one, everything works fine. I'm completely at a loss. But I'll take it

 

[ninjakira]

Yes, absolutely. After Pie everyone needs to use the same twrp. Here's my newer one. I've added the ability to back up and restore the oem partition. I'm working on 64bit, no promises on that. It's a real pain to be honest.

I'll add this in the twrp section Ina seperate "use if on Android 9 (pie)" thing here in the next day

 

[KomitaMKD]

No easier way to root g6 play?

 

[ninjakira]

No easier way to root g6 play?

until we get a twrp that can decrpyt our internal storage this is what you got. Good luck and please remember not to skim ? If you feel you can make a official decrypted twrp or know of someone willing to help then by all means go ahead lol

 

[KomitaMKD]

Unfortunately no

 

[ninjakira]

Unfortunately no

Then this is the best ya get. sorry to sound like a douche it's just what you see is what you get until we get decrypted twrp. Just follow the instructions down to a frickin T and there won't be problems. since it seems people fail to read anything that's also partly why I sound mildly annoyed ?

 

[RodimusConvoy]

I finally bought this phone. It was on sale at a Target for $60 brand new. Couldn't pass that up.

I played around with the settings a bit, seems far snappier than my Huawei Elate. But I wonder if that's because I don't have data constantly streaming through it. See I haven't switched my sim just yet, I want to unlock bootloader and root first.

Jeter and Resus, April 18th Kernal. Going by memory since its in my car (I'm currently on break). After work I'll email Moto about unlocking it then download the necessary files in the first post in the meantime while I wait. I hope to be officially up and running by Wednesday.

 

[ninjakira]

I finally bought this phone. It was on sale at a Target for $60 brand new. Couldn't pass that up.

I played around with the settings a bit, seems far snappier than my Huawei Elate. But I wonder if that's because I don't have data constantly streaming through it. See I haven't switched my sim just yet, I want to unlock bootloader and root first.

Jeter and Resus, April 18th Kernal. Going by memory since its in my car (I'm currently on break). After work I'll email Moto about unlocking it then download the necessary files in the first post in the meantime while I wait. I hope to be officially up and running by Wednesday.

*Ugandan knuckles voice*
Welcome bruddah *begins clicking of tongue* we will show you da wae.

 

[RodimusConvoy]

Ok, having bootloader unlock problems...

I followed the instructions on the Motorola site, even got the unlock key.

In command prompt, this is what happens:

C:\Windows>fastboot oem unlock [unlock key]
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.007s]
Finished. Total time: 0.013s

C:\Windows>fastboot oem unlock [unlock key]
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
Finished. Total time: 0.011s

C:\Windows>

And when I go into settings, the OEM unlock is greyed out. I restart, I don't get the bad key warning. Not sure what I'm doing wrong.

 

[RodimusConvoy]

Well playing a hunch I cut on wifi to my G6 Play (I did this at the library since I don't have wifi at my house). I let it update the Play libraries but I didn't take the security update (should I?). I then went into developer settings and this time OEM unlock wasn't greyed out. I check it, shut off the phone, rebooted into fastboot. Did the fastboot commands for OEM unlock twice like before, but this time on the second go it told me my bootloader was unlocked. I got the bad key! Then it proceeded to encrypt my phone before giving me the "Lets get started" prompts (since this process wipes data).

Wow so I'm ready to go. Bootloader is unlocked now so just gotta read through this a bit so I don't brick my phone. I spent most of the day on this bootloader unlock so I might wait till tomorrow. So, yeah, looks like Wednesday. One last day with the Huawei.

 

[RodimusConvoy]

Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp.

How?

As per the instructions, since I'm copying and pasting here:

Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader

CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.

ROOT PROCESS.

Step 1.) Run the following command from your computer to install the TWRP image to your device.

Code:
fastboot flash recovery twrp.img

Emphasis mine. It says to reboot the bootloader, not go back into TWRP. I did as was written, phone formated (gestating circle), encrypted itself, then "Hello Moto!"

Guess I should be lucky I'm not in a bootloop. But now I have to ask, are these instructions in order? Cause it seems like the dm verity disabler, the part that disables encryption, should come way early.

---------- Post added at 03:34 PM ---------- Previous post was at 03:13 PM ----------

Do it like this.

1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes" to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.

No option to do this part. Its either back or reboot system.

 

[Spaceminer]

How?

As per the instructions, since I'm copying and pasting here:

Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader

CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.

ROOT PROCESS.

Step 1.) Run the following command from your computer to install the TWRP image to your device.

Code:
fastboot flash recovery twrp.img

Emphasis mine. It says to reboot the bootloader, not go back into TWRP. I did as was written, phone formated (gestating circle), encrypted itself, then "Hello Moto!"

Guess I should be lucky I'm not in a bootloop. But now I have to ask, are these instructions in order? Cause it seems like the dm verity disabler, the part that disables encryption, should come way early.

---------- Post added at 03:34 PM ---------- Previous post was at 03:13 PM ----------



No option to do this part. Its either back or reboot system.

Yeah that's normal, select back. Then from TWRPs main menu, select reboot, then select recovery.