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

[dotzip.]

can someone upload their build.prop file as fast as possible? i corrupted mine (somehow) while enabling camera2api so i run into bootloop and i need the phone for tommorow lol

heres mine from XT1922-7
https://drive.google.com/file/d/1f97dNE83S1oh11JhxNx1hhDHd_3IF6__/view?usp=drivesdk

 

[Gleniu]

Send me your stock recovery and I'll check this out. Your model may have gotten an update that made it incompatible with twrp. I've seen the touch thing happen too many times. It's pretty easy to fix. In the mean time try this one and see if it works.

Hi, as I'm in exactly the same situation as Veggo, (the same issues, the same model number and the same firmware version), I'm attaching you a stock recovery.img from said firmware. Unfortunately, the TWRP you attached isn't working as well - the screen doesn't respond to touches.

The touches work fine on Oreo 32GB TWRP, but I can't format data in this TWRP version.

I hope you can help me Thank you.

 

[Spaceminer]

Hi, as I'm in exactly the same situation as Veggo, (the same issues, the same model number and the same firmware version), I'm attaching you a stock recovery.img from said firmware. Unfortunately, the TWRP you attached isn't working as well - the screen doesn't respond to touches.

The touches work fine on Oreo 32GB TWRP, but I can't format data in this TWRP version.

I hope you can help me Thank you.

It looks like your recovery no longer uses a dt.img, which is what holds the touchscreen drivers. I think they're using dtbo, or maybe it's loading the dt.img from boot. Try this and see if it works. It might hang on the twrp splash screen for a few seconds before the menus show up.

 

[Gleniu]

It looks like your recovery no longer uses a dt.img, which is what holds the touchscreen drivers. I think they're using dtbo, or maybe it's loading the dt.img from boot. Try this and see if it works. It might hang on the twrp splash screen for a few seconds before the menus show up.

Thank you very much! Works like a charm. Now I'm trying to root my phone, however I get into bootloop after flashing Magisk. Tried Magisk versions 20.0 and 20.1. After unlocking bootloader, there is a "bad key" info on the top of the screen upon every boot. After flashing DM-verity disabler and Magisk, the "bad key" text switches to some kind of key (the format is XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX) and I get into bootloop - I don't even see Moto logo, just the key on top for about 5 seconds and then reboot.

Any help on that?

EDIT: Nevermind, I solved it by using a fantastic tutorial by tamaringon in post 391

 

[Spaceminer]

Thank you very much! Works like a charm. Now I'm trying to root my phone, however I get into bootloop after flashing Magisk. Tried Magisk versions 20.0 and 20.1. After unlocking bootloader, there is a "bad key" info on the top of the screen upon every boot. After flashing DM-verity disabler and Magisk, the "bad key" text switches to some kind of key (the format is XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX) and I get into bootloop - I don't even see Moto logo, just the key on top for about 5 seconds and then reboot.

Any help on that?

EDIT: Nevermind, I solved it by using a fantastic tutorial by tamaringon in post 391

Magisk 19.4+ will cause a bootloop for us because it signs the boot.img with legitimate keys, which our bootloader refuses. Reflash your stock boot.img, wipe /data, /cache, /davlik. Flash disabler first, then flash magisk 19.3.

---------- Post added at 02:14 PM ---------- Previous post was at 02:09 PM ----------

@Veggo

See post #423 for the fixed twrp.

---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------

@Veggo

See post #423 for the fixed twrp.

 

[carzevedo]

I tried to install the October security patch, I think I was all working perfectly fine with the August security patch.

I get an error reflashing in the following stock roms, my signal is dead:
"XT1922-4_ALJETER_OPENMX_9.0_PPPS29.55-25-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" and
"XT1922-4_ALJETER_AMX_9.0_PPPS29.55-25-2_cid50_subsidy-TELMXLA_regulatory-DEFAULT_CFC.xml"

So, the one that actually boots my phone correctly is:
"XT1922-4_ALJETER_OPENMX_9.0_PPPS29.55-35-12-5_cid50_subsidy-DEFAULT_regulatory-XT1922-4_CFC.xml"

And now I noticed in settings shows up that my software channel was amxmx and changed my stock rom to:
"XT1922-4_ALJETER_AMX_9.0_PPPS29.55-35-12-5_cid50_subsidy-DEFAULT_regulatory-XT1922-4_CFC.xml"

According to https:// mirrors.lolinet.com/firmware/moto/aljeter/official/AMXMX/
this was supposed to be the latest firmware updated for me (I guess...?)

I'm scared to root my device now (cause' I really want to) because I can't stop messing my boot.img or something like that, I can backup my data and personal stuff, but my phone wont accept a good firmware, flashing TWRP correctly and installing Magisk.
Everytime I try to follow the guide with different versions of the elements needed, that bootloop shows up with the "80012A99-867FDA48-4E357816-0E549F..." thing.

What am I missing so I can get a "clean root" process?

1. I'm shutting down my moto G6 play.
2. Entering Fastboot mode by clicking volume down and power keys.
In fastboot I get this captions.

AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-aljeter_retail_b1f322d-190926
Baseband: M8937_31.39.05.93Z JETER_LATAM_CUST
Product/Variant: jeter XT1922-4 32GB P4
(some more info as serial number, cpu, emmc, dram, console, tools mode config)
flashin_unlocked
transfer mode: USB Connected
​

3. Now I boot twrp
fastboot boot twrp.img

TWRP runs and shows
Mount
Decrypt Data (I touch Cancel and then proceed)
**Swipe to allow modifications (I swipe)
4. Try to backup but cmd shows:
"remote object '/dev/block/platform/soc/7824900.sdhci/by-name/boot' not a file or directory
5. Format my data in Wipe Format Data, and typed "yes"
6. Used adb reboot bootloader to reboot.
7. Now I flashed fastboot flash recovery twrp.img and not getting any Decrypt Data screen anymore.
8. I allow modifications.
9. I put my archives in sd card.

Disable_Dm-Verity_ForceEncrypt_05.21.2019
Magisk-v19.1(19100)
​

10. I go to install and install both zips in that same order.
11. Reboot System.
12. Black screen shows up with "Bad key" caption
13. Moto G6 reboots fine, like new.
14. Configuring my device.
15. Checking root with root checker.
16. Root confirmed.

So, I think the solution was to replace the archives in the original guide with:

Disable_Dm-Verity_ForceEncrypt_05.21.2019
Magisk-v19.1(19100)​

Hope this helps everyone else. Or me, in a future :fingers-crossed:

Thank you so much! This sequence and apps works perfectly :good::good::good::good::good:

 

[Gleniu]

Magisk 19.4+ will cause a bootloop for us because it signs the boot.img with legitimate keys, which our bootloader refuses. Reflash your stock boot.img, wipe /data, /cache, /davlik. Flash disabler first, then flash magisk 19.3.

Thank you for the explanation. I successfully rooted with Magisk 19.1 using tutorial in post 391. However, I went for it and tried to update Magisk to latest version (20.1) using Magisk Manager with Direct Flash method. "Bad key" message turned to "XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX", but this time system booted just fine So, it seems that we can use the latest Magisk, but the first flash in TWRP must be done using Magisk version <19.4, and then updated using Magisk Manager.

 

[Veggo]

Magisk 19.4+ will cause a bootloop for us because it signs the boot.img with legitimate keys, which our bootloader refuses. Reflash your stock boot.img, wipe /data, /cache, /davlik. Flash disabler first, then flash magisk 19.3.

---------- Post added at 02:14 PM ---------- Previous post was at 02:09 PM ----------

@Veggo

See post #423 for the fixed twrp.

---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------

@Veggo

See post #423 for the fixed twrp.

Thank you very much. Like Gleniu mentioned TWRP is working fine but I also stuck in bootloop after flashing DM-verity disabler and Magisk
First I tried with Magisk 19.3 but stuck in bootloop so I reflashed stock boot.img, wipe /data, /cache, /davlik. Then repeated the steps from the beginning but with Magisk 19.1. But also stuck in bootloop.
I couldn't find Disable_Dm-Verity_ForceEncrypt_05.21.2019 so I used the latest as in OP (10.20.2019.).
@Gleniu: which version of Dm-Verity did you use?

 

[Gleniu]

Thank you very much. Like Gleniu mentioned TWRP is working fine but I also stuck in bootloop after flashing DM-verity disabler and Magisk
First I tried with Magisk 19.3 but stuck in bootloop so I reflashed stock boot.img, wipe /data, /cache, /davlik. Then repeated the steps from the beginning but with Magisk 19.1. But also stuck in bootloop.
I couldn't find Disable_Dm-Verity_ForceEncrypt_05.21.2019 so I used the latest as in OP (10.20.2019.).

@Gleniu: which version of Dm-Verity did you use?

I used the attached one. I also couldn't find it on the project website, so I just googled it Worked perfectly, so I think it is safe to assume that the disabler is the issue, not the Magisk itself. Hope you'll root your phone as well

 

[Spaceminer]

Thank you very much. Like Gleniu mentioned TWRP is working fine but I also stuck in bootloop after flashing DM-verity disabler and Magisk
First I tried with Magisk 19.3 but stuck in bootloop so I reflashed stock boot.img, wipe /data, /cache, /davlik. Then repeated the steps from the beginning but with Magisk 19.1. But also stuck in bootloop.
I couldn't find Disable_Dm-Verity_ForceEncrypt_05.21.2019 so I used the latest as in OP (10.20.2019.).

@Gleniu: which version of Dm-Verity did you use?

I can give you the one I use. I believe it's the 5/21/19 release.

 

[ninjakira]

Hello everyone, thank you to the people that's been helping on the guide lately, I'm sorry I haven't been posting alot some recent family tragedy has come about so I've had to refocus my attention the last week, our twrp maintainer @Spaceminer is working on updating on TWRP which will fix the issues everyone is having lately, once he is done with TWRP it will uploaded and added to the guide, thank you for your patience and as a reminder, please drive safe

 

[harryspar]

Just for the record

I have an unlocked RETUS 1922-9 on the Pie update.

Everything failed for me except using the 5/21 version of the verity script, and Magisk 19.2, which then worked.

 

[painball]

Just for the record

I have an unlocked RETUS 1922-9 on the Pie update.

Everything failed for me except using the 5/21 version of the verity script, and Magisk 19.2, which then worked.

Honestly you are more stubborn than I am. Can you post this Verity script? Nothing makes my 1922-3 working. When I try to verity and magisk immidiately goes into bootloop with numbers on the top.
@edit: Seems to be working indeed. No numbers on top. Now stuck ant Motorola logo. Well. I will let it think this out for 10 minutes. I flashed plenty of devices. Never had such fight and so many variables between models. Budget phone in 9 versions - what a drama.

 

[brunohrbarros]

You read my post before I had a chance to fix it. I accidentally read what you said backwards. You shouldn't have a long string of numbers. That's Magisk resigning your boot.img. N/A is good and what you want. Try using Magisk 19.1, or 19.3 after flashing the older disabler I posted.

Are you xt1922-7? Also what stock firmware are you running, Pie or Oreo?

Hello Spaceminer! Thank you very much for helping us!
I can confirme the same problem with that "string of numbers"
Coming from android 9 ppps29.55-35-12-5 xt1922-5 retbr
Should I try Magisk 19.3?

I'm new to this, I appreciate if you can explain some things to me, if it won't bother you.
I`ve read all pages, each comment, to understand better what I`m trying to do, but it`s not familiar to me.
What do Disable and Magisk do? (I understood Disable solves the problem with data encrypt and Magisk do the root process)
And when I flash a GSI, do I have root, or I will need to do these steps too?
Another very stupid quest, when I use this command "adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img", what is the .img file location?

Thank you for your patience!

---------- Post added at 10:18 PM ---------- Previous post was at 09:55 PM ----------

Hello everyone, thank you to the people that's been helping on the guide lately, I'm sorry I haven't been posting alot some recent family tragedy has come about so I've had to refocus my attention the last week, our twrp maintainer @Spaceminer is working on updating on TWRP which will fix the issues everyone is having lately, once he is done with TWRP it will uploaded and added to the guide, thank you for your patience and as a reminder, please drive safe

ninjakira you are great! Thanks for all this work! My prayers to you and to your family!

 

[Spaceminer]

Hello Spaceminer! Thank you very much for helping us!
I can confirme the same problem with that "string of numbers"
Coming from android 9 ppps29.55-35-12-5 xt1922-5 retbr
Should I try Magisk 19.3?

I'm new to this, I appreciate if you can explain some things to me, if it won't bother you.
I`ve read all pages, each comment, to understand better what I`m trying to do, but it`s not familiar to me.
What do Disable and Magisk do? (I understood Disable solves the problem with data encrypt and Magisk do the root process)
And when I flash a GSI, do I have root, or I will need to do these steps too?
Another very stupid quest, when I use this command "adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img", what is the .img file location?

Thank you for your patience!

-The disabler prevents encryption, and also removes dm-verity which is a security feature that can prevent you from booting GSIs, or sometimes even the stock OS if it's been modified.

-Yes, Magisk handles all the root stuff.

If you flash a GSI you may or may not have root, it depends. Some GSIs have it included as part of the system and some don't.

If you keep the rooted boot.img from stock and flash a GSI, Magisk will usually show up in your app drawer shortly after booting up. If you open it, it'll prompt you to download some files and finish re-rooting the new system.

If it doesn't show up, you'll have to reflash Magisk in twrp. (use v19.3 by the way)
If you successfully disabled encryption before flashing a GSI, it'll stay disabled on the GSI as well, so no need to reflash the disabler.

-The image file location should be in the same folder you're running adb from.

 

[painball]

-The disabler prevents encryption, and also removes dm-verity which is a security feature that can prevent you from booting GSIs, or sometimes even the stock OS if it's been modified.

-Yes, Magisk handles all the root stuff.

If you flash a GSI you may or may not have root, it depends. Some GSIs have it included as part of the system and some don't.

If you keep the rooted boot.img from stock and flash a GSI, Magisk will usually show up in your app drawer shortly after booting up. If you open it, it'll prompt you to download some files and finish re-rooting the new system.

If it doesn't show up, you'll have to reflash Magisk in twrp. (use v19.3 by the way)
If you successfully disabled encryption before flashing a GSI, it'll stay disabled on the GSI as well, so no need to reflash the disabler.

-The image file location should be in the same folder you're running adb from.

And that's in teory. In practice the devices got different bootloaders. Even if I try to "root" stock 9.0 the device won't boot. With xt1922-3(lucky me) none of mentioned in topic methods pass the bootloop on stock 9.0 or GSI ROMS. Maybe with 8.0? Don't have time for now. Wasted like 3hours yday. For reflashing/booting/searching for archive versions of magisk, disablers etc.

 

[brunohrbarros]

-The disabler prevents encryption, and also removes dm-verity which is a security feature that can prevent you from booting GSIs, or sometimes even the stock OS if it's been modified.

-Yes, Magisk handles all the root stuff.

If you flash a GSI you may or may not have root, it depends. Some GSIs have it included as part of the system and some don't.

If you keep the rooted boot.img from stock and flash a GSI, Magisk will usually show up in your app drawer shortly after booting up. If you open it, it'll prompt you to download some files and finish re-rooting the new system.

If it doesn't show up, you'll have to reflash Magisk in twrp. (use v19.3 by the way)
If you successfully disabled encryption before flashing a GSI, it'll stay disabled on the GSI as well, so no need to reflash the disabler.

-The image file location should be in the same folder you're running adb from.

Just one more question, in case I mess everything, I downloaded the stock rom from lolinet servers (XT1922-5_ALJETER_RETBR_9.0_PPPS29.55-35-12-5_cid50_subsidy-DEFAULT_regulatory-XT1922-5-BRAZIL-MANAUS_CFC.xml).

It shows on info file Modem Version: M8937_31.39.05.93R, but my actual modem version is m8937_31.39.05.93Z. Should I concern about flashing this stock rom from lolinet?

I got a bit confused with these termnologies that Motorola adopted with Moto G6 Play.
When I`m on fastboot mode, it shows on screen:
BL: MBM-2.1-aljeter_retail-b1f322d-190926
Product/Variant: jeter XT1922-5 32 GB p4

There is no jeter rom for XT1922-5 on lolinet

 

[Hannibal Smith]

moto g6 play single sim xt1922-2 32gb ROM
software variant ora
software channel oraeu
android version 8.0.0
patch 1 june 2018
baseband
m8937_19.22.05.62R JETER_EMEA_CUST
kernel
2.18.71-perf-gdd9581c-00001-g0146109
build
OPP27.91-87
I think it's orange branded.

anyone have this stock rom ? I'd like to have it in case i messe up something..

 

[Spaceminer]

Just one more question, in case I mess everything, I downloaded the stock rom from lolinet servers (XT1922-5_ALJETER_RETBR_9.0_PPPS29.55-35-12-5_cid50_subsidy-DEFAULT_regulatory-XT1922-5-BRAZIL-MANAUS_CFC.xml).

It shows on info file Modem Version: M8937_31.39.05.93R, but my actual modem version is m8937_31.39.05.93Z. Should I concern about flashing this stock rom from lolinet?

I got a bit confused with these termnologies that Motorola adopted with Moto G6 Play.
When I`m on fastboot mode, it shows on screen:
BL: MBM-2.1-aljeter_retail-b1f322d-190926
Product/Variant: jeter XT1922-5 32 GB p4

There is no jeter rom for XT1922-5 on lolinet

If you're in Brazil then that should be the correct firmware. I wouldn't worry about the modem, that just looks like a small update. If you're not in Brazil, you'll probably want this firmware. It's retail aljeter: Link

---------- Post added at 06:31 PM ---------- Previous post was at 06:07 PM ----------

anyone have this stock rom ? I'd like to have it in case i messe up something..

Orange? You'll want this one. ORAEU Pie

 

[amedeh123]

If you're in Brazil then that should be the correct firmware. I wouldn't worry about the modem, that just looks like a small update. If you're not in Brazil, you'll probably want this firmware. It's retail aljeter: Link

whats the difference between retail and retbr firmwares?

is it safe to go back and forth between them?