mod please remove

[Starkiller2]

Heck yes that's awesome to know. And I planned on it lol mirrors.lolinet should have it up in couple weeks if anything

Good to know. Makes me nervous not having the fallback, I panicked so hard when my service went out, having turned my e5 play into a WiFi only device awhile back. I prayed so hard taking that update. Freaked the whole house out yelling when I got it back

---------- Post added at 11:39 AM ---------- Previous post was at 11:32 AM ----------

Thanks again, you and kwiksi1ver(?) Everybody learns differently. And some people learn the hard way, like me. I gotta touch the wet paint. Gotta see how everything works so both guides are helpful. Thanks for all the hard work

 

[Dauntix]

I'm currently rooted on stock rom. If I updated my phone, will it still be rooted? If not, do I take the same exact steps to root it again (on the latest update)?

 

[drgsrbad81]

At risk of sounding dumb

First off, I want to kudos to ninjakira for making this post and for helping everyone with a problem in this and the original G6 forum.. that being said, I read both posts in there entirety and I want to make sure I got this crystal clear, before I end up here asking ninjakira for help with a bootloop lol.. Now I have the boost Mobile g6 play and it already has the October 1st security update... As long as I follow the instructions to the letter, I should have no issues obtaining root... Is this true and accurate? It's been a while since I have been able to root a phone because I kept buying phones that I couldn't unlock the bootloader..

 

[ninjakira]

First off, I want to kudos to ninjakira for making this post and for helping everyone with a problem in this and the original G6 forum.. that being said, I read both posts in there entirety and I want to make sure I got this crystal clear, before I end up here asking ninjakira for help with a bootloop lol.. Now I have the boost Mobile g6 play and it already has the October 1st security update... As long as I follow the instructions to the letter, I should have no issues obtaining root... Is this true and accurate? It's been a while since I have been able to root a phone because I kept buying phones that I couldn't unlock the bootloader..

Hey sorry for not responding or being on the forum lately been work moved me from 3rd shift to 1st shift so my sleep has been way out of wack. Yes if you follow the instructions you will be able to obtain root. The latest magisk beta is 17.3. word of caution. There is no stock firmware uploaded for the October update yet so if you do get a bootloop you will be stuck until it gets uploaded

 

[krltz2]

works with this patch??? OPP 27.91-140

 

[ninjakira]

works with this patch??? OPP 27.91-140

Yes it should work. But be warned there is no stock firmware uploaded with that security patch so if you get Ina bootloop you will be stuck until it does get uploaded. Just follow the instructions and you should still be able to get root status.

 

[krltz2]

Yes it should work. But be warned there is no stock firmware uploaded with that security patch so if you get Ina bootloop you will be stuck until it does get uploaded. Just follow the instructions and you should still be able to get root status.

Doesnt Work :I

 

[madbat99]

Doesnt Work :I

What exactly doesn't work? You can't unlock the bootloader? Magisk? Because it works for others on 27.91 150 you should provide details.

 

[krltz2]

What exactly doesn't work? You can't unlock the bootloader? Magisk? Because it works for others on 27.91 150 you should provide details.

At the moment of installing the twrp after following all the steps it remains in N / A

 

[madbat99]

At the moment of installing the twrp after following all the steps it remains in N / A

Saying na is normal. It sounds like you have missed some steps. So you have wipe data and Flash magisk in TWRP? Or are you just trying to boot the system without doing any of the other steps?

 

[krltz2]

Saying na is normal. It sounds like you have missed some steps. So you have wipe data and Flash magisk in TWRP? Or are you just trying to boot the system without doing any of the other steps?

It stays stuck in N / A does not start anything, before installing the magisk I made wipe then install the Magisk I think it stays in N / A since my rom.es OPP 27.91-140 ..... you have the same rom Did you run the root and the twrp ??

 

[ninjakira]

It stays stuck in N / A does not start anything, before installing the magisk I made wipe then install the Magisk I think it stays in N / A since my rom.es OPP 27.91-140 ..... you have the same rom Did you run the root and the twrp ??

It sounds like you have put yourself into a bootloop somehow which I honestly don't see how. But There is currently no firmware uploaded for the security patch that your on yet. Until one gets uploaded your stuck with a bricked device

 

[madbat99]

It stays stuck in N / A does not start anything, before installing the magisk I made wipe then install the Magisk I think it stays in N / A since my rom.es OPP 27.91-140 ..... you have the same rom Did you run the root and the twrp ??

Restore the backup you made of boot.img wipe data and then try again

 

[Swift2603]

My phone (XT1922-3) offers an update to OPP27.91-143, but it doesn't install. The update process just doesn't start, when I click on install.

I reverted back to stock boot.img (OPP21.91-87) and stock recovery beforehand, but when I try to update via sideload the process gets canceled at some point with Error in sideload/package status:0

Any idea how to solve this?

 

[madbat99]

My phone (XT1922-3) offers an update to OPP27.91-143, but it doesn't install. The update process just doesn't start, when I click on install.

I reverted back to stock boot.img (OPP21.91-87) and stock recovery beforehand, but when I try to update via sideload the process gets canceled at some point with Error in sideload/package status:0

Any idea how to solve this?

You're not going to be able to sideload it without adb. As for the failure when trying to install it normally did you make any changes to your system while you had root?just like everyone else you're going to have to reflash the full stock firmware to apply the update most likely

 

[ninjakira]

My phone (XT1922-3) offers an update to OPP27.91-143, but it doesn't install. The update process just doesn't start, when I click on install.

I reverted back to stock boot.img (OPP21.91-87) and stock recovery beforehand, but when I try to update via sideload the process gets canceled at some point with Error in sideload/package status:0

Any idea how to solve this?

Gonna have to reflash the firmware your currently on reboot the phone then take the update.

 

[krltz2]

Restore the backup you made of boot.img wipe data and then try again

IS IT ALL GOOD TO HERE?

PS C:\Users\Usuario\Desktop\platform-tools> cmd
Microsoft Windows [Versión 10.0.17134.345]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.

C:\Users\Usuario\Desktop\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully


C:\Users\Usuario\Desktop\platform-tools>fastboot boot moto-g6-play-jeter-patched-twrp.img
Downloading 'boot.img' OKAY [ 0.527s]
booting OKAY [ 0.078s]
Finished. Total time: 0.655s

C:\Users\Usuario\Desktop\platform-tools>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
/dev/block/platform/soc/7824900.sdhci/by-name/boot: 1 file pulled. 17.7 MB/s (16777216 bytes in 0.904s)

C:\Users\Usuario\Desktop\platform-tools>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
/dev/block/platform/soc/7824900.sdhci/by-name/recovery: 1 file pulled. 19.1 MB/s (16879616 bytes in 0.842s)

C:\Users\Usuario\Desktop\platform-tools>adb reboot bootloader

C:\Users\Usuario\Desktop\platform-tools>fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Sending 'recovery' (16228 KB) OKAY [ 0.539s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.174s]
Finished. Total time: 0.720s

C:\Users\Usuario\Desktop\platform-tools>adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor

C:\Users\Usuario\Desktop\platform-tools>adb push Magisk-v16.4.zip /tmp
Magisk-v16.4.zip: 1 file pushed. 18.4 MB/s (4500886 bytes in 0.233s)

WHAT IS THE ERROR ?? IT KILLED ME IN N / A AGAIN HEL PLEASE

 

[ninjakira]

IS IT ALL GOOD TO HERE?

PS C:\Users\Usuario\Desktop\platform-tools> cmd
Microsoft Windows [Versión 10.0.17134.345]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.

C:\Users\Usuario\Desktop\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully


C:\Users\Usuario\Desktop\platform-tools>fastboot boot moto-g6-play-jeter-patched-twrp.img
Downloading 'boot.img' OKAY [ 0.527s]
booting OKAY [ 0.078s]
Finished. Total time: 0.655s

C:\Users\Usuario\Desktop\platform-tools>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
/dev/block/platform/soc/7824900.sdhci/by-name/boot: 1 file pulled. 17.7 MB/s (16777216 bytes in 0.904s)

C:\Users\Usuario\Desktop\platform-tools>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
/dev/block/platform/soc/7824900.sdhci/by-name/recovery: 1 file pulled. 19.1 MB/s (16879616 bytes in 0.842s)

C:\Users\Usuario\Desktop\platform-tools>adb reboot bootloader

C:\Users\Usuario\Desktop\platform-tools>fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Sending 'recovery' (16228 KB) OKAY [ 0.539s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.174s]
Finished. Total time: 0.720s

C:\Users\Usuario\Desktop\platform-tools>adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor

C:\Users\Usuario\Desktop\platform-tools>adb push Magisk-v16.4.zip /tmp
Magisk-v16.4.zip: 1 file pushed. 18.4 MB/s (4500886 bytes in 0.233s)

WHAT IS THE ERROR ?? IT KILLED ME IN N / A AGAIN HEL PLEASE

You not using the right files......don't use magisk 16.4. have you even read my guide dude because in this very guide your commenting on Everything is updated....READ THE GUIDE AND FOLLOW IT

 

[ninjakira]

IS IT ALL GOOD TO HERE?

PS C:\Users\Usuario\Desktop\platform-tools> cmd
Microsoft Windows [Versión 10.0.17134.345]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.

C:\Users\Usuario\Desktop\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully


C:\Users\Usuario\Desktop\platform-tools>fastboot boot moto-g6-play-jeter-patched-twrp.img
Downloading 'boot.img' OKAY [ 0.527s]
booting OKAY [ 0.078s]
Finished. Total time: 0.655s

C:\Users\Usuario\Desktop\platform-tools>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
/dev/block/platform/soc/7824900.sdhci/by-name/boot: 1 file pulled. 17.7 MB/s (16777216 bytes in 0.904s)

C:\Users\Usuario\Desktop\platform-tools>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
/dev/block/platform/soc/7824900.sdhci/by-name/recovery: 1 file pulled. 19.1 MB/s (16879616 bytes in 0.842s)

C:\Users\Usuario\Desktop\platform-tools>adb reboot bootloader

C:\Users\Usuario\Desktop\platform-tools>fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Sending 'recovery' (16228 KB) OKAY [ 0.539s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.174s]
Finished. Total time: 0.720s

C:\Users\Usuario\Desktop\platform-tools>adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor

C:\Users\Usuario\Desktop\platform-tools>adb push Magisk-v16.4.zip /tmp
Magisk-v16.4.zip: 1 file pushed. 18.4 MB/s (4500886 bytes in 0.233s)

WHAT IS THE ERROR ?? IT KILLED ME IN N / A AGAIN HEL PLEASE

Your just not doing anything right it's like your not following the guide. AFTER flashing twrp you have to go to the recovery option in the bootloader and go into twrp and do everything else you have to go to your /tmp folder in twrp and install magisk....

 

[madbat99]

You not using the right files......don't use magisk 16.4. have you even read my guide dude because in this very guide your commenting on Everything is updated....READ THE GUIDE AND FOLLOW IT

I had a feeling he was using the wrong version of magisk