Database Users

Nubia Z9 Mini SuperSU root tutorial

There is already a tutorial on how to root the Z9 mini but it uses Kinguser as the root method.
I rooted my phone using the Kinguser method but was unable to use titanium backup or lucky patcher for that matter.. (Whats the use when it doesn't work with two of my favorite apps. lol).
This tutorial takes it one step further and changes the root from Kinguser to SuperSU !!
This tutorial doesnt need you to Install a custom recovery. Installing SuperSU only requires flashing a custom recovery first, this bypasses that need to flash one.
Bonus: Tutorial for any Soft Brick Involving the Z9 mini​
STEP 1 : ROOT using Kinguser
Download: http://www50.zippyshare.com/v/5Tn8Cp1f/file.html​
After downloading the above files, extract them.
Open that folder and run the file named as “r-o-o-t.bat”. A command window will appear in your PC screen.
Now connect your device to PC using USB data cable.
Enter the number "1" in command window and wait for the program to process your entry.
Once you see the message “Waiting for devices” in the command window, switch off your smartphone,
press the Volume down button and Power button until you see the Boot Menu.
Once you see the Boot Menu in your device, press Reboot to begin the rooting process.
Congrats!! Your ZTE Nubia Z9 Mini is rooted now but unfortunately with Kinguser.
STEP 2 : Change Kinguser to SuperSU.
This is where the fun begins. As I am not sure on which Custom recovery to use.. I just went ahead with using terminal to install SuperSU and replace Kinguser.
Download :
Terminal emulator app LINK
Replace_Kingroot_With_SuperSU.zip LINK​
Steps :
Send the extracted folder "mrw" to the root of SD card and make sure that this folder contains 6 files
Open Terminal emulator and type :
Su
Click to expand...
Click to collapse
This grants root permission to terminal emulator.
Next type
sh /sdcard/mrw/root.sh
Click to expand...
Click to collapse
and press enter.
It might display some error, at the end it will launch SuperSU. (open SuperSU manually if it doesn't)
Update su binary using normal method, then reboot.
Now All apps that require root will work without issues..!!:laugh:

Hi, the folder you mention contains only 4 files. What is the problem with that?

FULL Disk ENCRYPTION + ROOT Easy steps >>> HOW TO root & encrypt entire device

FULL Disk ENCRYPTION + ROOT Easy steps >>> HOW TO root & encrypt entire device
How to encrypt your rooted device. I wrote these instructions based on my Note 4 (T-Mobile branded N910T3 ) BUT they will work for ANY device!
THE SHORT OF IT:
YOU SIMPLY NEED TO ECRYPT YOUR DEVICE FIRST PRIOR TO ROOTING. YOU CAN ROOT IT AFTER IT IS ENCRYPTED, NOT BEFORE.
tested on Android 4, 5, & 6.
Once you root or install various roms you lose the ability to encrypt your device. This issue manifests itself in the form of either hanging, rebooting, or the animation just sitting there but not actually doing anything when you try to use the full disk encryption feature built into all modern versions of android. Below are the steps on how to get this native encryption feature working while still maintaining your root & favorite rom.
Credit goes to chatty kathy, i mean bruzzy who graciously and verbosely provided instructions on how to encrypt my rooted 12.2" Samsung Galaxy Note Pro (AT&T branded SM-P907A) here: http://forum.xda-developers.com/showthread.php?t=2791587
McFood on androidforums.com also reiterated much of the same here: http://androidforums.com/threads/how-to-encrypt-a-rooted-device.866968/
As usual: Use this guide at your own risk!
Quick Overview:
Unroot if rooted. Encrypt. Reroot. The only thing special is that you have to manually kick start SuperSU when rooting after the encryption is in affect. See steps 12 & 13.
INSTRUCTIONS:
-------------------
0. Make a backup to your external SD card of your entire system FIRST such as a nandroid backup via a custom recovery (Philz Touch, TWRP, etc). I even do modem, etc. just in case you ever need.
1. Ensure your device is not rooted and also not encrypted (if already rooted, skip to step 3; if already encrypted, decrypt or do a factory-reset - don't try CF-Auto-Root on an encrypted device, it'll soft-brick)
2. Root the device (I used this sticky: http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 )
3. Temporarily un-root the device (when using SuperSU: go to Settings and remove the tick at the option "Activate Superuser")
4. Reboot
5. Activate the device encryption (the battery must be at least at 80% and the device must be plugged in the wall charger)
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
7. After the encryption is finished the device will reboot and ask for the password, just log in
8. If not yet done, flash a custom recovery where you have console access or can use ADB as root (I used TWRP)
9. Boot into recovery. (POWER + VOLUME UP + HOME button together at the same time)
10. Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
11. Open a console or ADB shell to run the basic linux commands in red in the next two steps on the phone ((In TWRP it is under Advanced & then Terminal Command and start the console in any directory, it doesn't matter, i would choose the root directory / ))
11-continued: Laymans terms: go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in the commands in red in steps 12 & 13.
12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )
14. Reboot
15. Send the NSA a message and tell them to lick your balls. Oh wait nevermind they have a backdoor in AES... FTP = Fukt The Police :cyclops:

OP space
The real trick here is disabling (step 3) and then manually re-enabling (steps 12 and 13) root which you manually re-enable after the encryption is complete. The order is key. You cannot encrypt the device while rooted.
go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.

? on steps 12 + 13
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?

?
Bueller?

V3racious said:
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
Click to expand...
Click to collapse
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.

livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Exactly. I tried this before and got the same results.

jrkart99 said:
Exactly. I tried this before and got the same results.
Click to expand...
Click to collapse
I just gave up on root for now.

Breakdown of steps 12 & 13
jrkart99 said:
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?
Click to expand...
Click to collapse
For steps 12 and 13 you go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.
To answer your other question: YES you need to choose your ROM first, otherwise you have to do this all over again. Install your ROM first, root it next if your rom doesn't come pre-rooted, manually disable root, and lastly encrypt the device.

livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Can you verify that you have in fact disabled root first? You cannot encrypt a rooted device. Also what is the model number of your device? What version of Android are you using?

Try this method after SuperSU is installed.
http://forum.xda-developers.com/showthread.php?p=56037508
Good luck
Sent from my Nexus 7 using Tapatalk

Hello,
I have sprint note 4.. I have installed HybridX Android 5.1.1 on it.. which have root and everything ready.
I go to system apps, from there disable SuperSu and then reboot in safe mode and start encryption.. These are the steps I read on another page..
However, my phone gets stuck on the sprint spark yellow screen as soon as I say ok to encrypt.. it will restart and gets stuck on there.
I have tried without restarting in safe mode.. but the same result.
What can I do to encrypt my Sprint Note 4.
Thanks

Hello,
I am on Galaxy Note 3 with N7 Darklord ROM and both methods don't work.
Root is disabled, but when I run encryption, the phone restarts in 2-3 minutes
and nothing is encrypted
Please advise how to encrypt the device! Thanks!

5.0.1 Should be fine to root + encrypt
Hi all,
Just to confirm that the only version I managed to root and encrypt is 5.0.1.
I have a Note 4 910F and this worked;
- Flash stock via odin
- Root (chainfire via odin)
- Install Busybox
- Install Terminal Emulator, then run su -> pkill -KILL daemonsu (same as other instructions on this forum)
- Encrypt the phone
Again, this only worked on 5.0.1 (N910FXXU1BOC5_N910FBTU1BOB2_N910FXXU1BOC4_HOME.tar)
All other versions got stuck on encryption screen.

In short, all you have to do is ENCRYPT the device FIRST then ROOT it AFTERWARDS. It will not work once the device is rooted. I have not had a chance to try unrooting through SuperSU or disabling the daemonsu through a terminal emulator as mentioned so I am not sure if this works but it definitely works if you encrypt PRIOR to rooting. I can confirm it works on Marshmallow as I just did so on a Note 4.

Now has anyone had any luck making backup images of their encrypted devices? If so what custom recovery software and version are you running on your device?

[GUIDE]How to Root and Custom Recovery with a broken USB Port!

A Comprehensive guide to Rooting And Custom Recovery with a Non-Functioning USB Port​
This is for those of us who have a broken USB port on our Xperia devices and still want to flash! If it is too difficult/expensive to get your device repaired, this method may still get you root and custom recovery.
Requirements:
As we always say with suggestions from XDA, DO THIS AT YOUR OWN RISK. I take no responsibility for you or your device.
This procedure was carried out on a Z3 Compact with stock firmware 23.4.A.1.264.
1. Xperia device with stock firmware - what I had: 23.4.A.1.264
2. KingRoot - what I had: 4.8.1
3. [NUT]'s XZDualRecovery - what I had: Z3C-lockeddualrecovery2.8.26-RELEASE.combined.zip
4. Android file exporer with root capcibility - what I had: ES File Explorer File Manager
5. Android terminal with root capability - what I had: Terminal Emulator for Android
6. Root Checker - what I had: Root Checker
STEP 1:
Use Kingroot to root the device. The version I had at the time said that there was no root method specifically available but there was a generic method which worked. If this doesnt work - try rebooting and try it. It worked for me on my second attempt.
STEP 2:
Use Root Checker to make sure the device is rooted - a dialog box should open from Kingroot asking if you want to grant it root access, press yes!
STEP 3:
Download XZDualRecovery twice - one for flashing and one for extracting (I found this easier on a PC).
STEP 4:
In the extracted version, open the install.bat in a text editor so you can read the code
STEP 5:
Search for the bit where the bat file makes the directory and transfers the necessary files
Code:
echo =============================================
echo Step2 : Sending the recovery files.
echo =============================================
adb shell "mkdir /data/local/tmp/recovery"
adb push ..\tmp\dr.prop /data/local/tmp/recovery/dr.prop
adb push ..\system\bin\chargemon /data/local/tmp/recovery/chargemon
adb push ..\system\bin\mr /data/local/tmp/recovery/mr
adb push ..\system\.XZDualRecovery\xbin\dualrecovery.sh /data/local/tmp/recovery/dualrecovery.sh
adb push ..\tmp\NDRUtils.apk /data/local/tmp/recovery/NDRUtils.apk
adb push ..\system\.XZDualRecovery\xbin\rickiller.sh /data/local/tmp/recovery/rickiller.sh
adb push ..\tmp\byeselinux.ko /data/local/tmp/recovery/byeselinux.ko
adb push byeselinux\byeselinux.sh /data/local/tmp/recovery/byeselinux.sh
adb push ..\tmp\wp_mod.ko /data/local/tmp/recovery/wp_mod.ko
adb push byeselinux\sysrw.sh /data/local/tmp/recovery/sysrw.sh
adb push ..\tmp\modulecrcpatch /data/local/tmp/recovery/modulecrcpatch
adb push ..\system\.XZDualRecovery\xbin\busybox /data/local/tmp/recovery/busybox
adb push ..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma /data/local/tmp/recovery/recovery.twrp.cpio.lzma
adb push ..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma /data/local/tmp/recovery/recovery.philz.cpio.lzma
if exist {..\system\.XZDualRecovery\xbin\ramdisk.stock.cpio.lzma} (
adb push ..\system\.XZDualRecovery\xbin\ramdisk.stock.cpio.lzma /data/local/tmp/recovery/ramdisk.stock.cpio.lzma
)
adb push ..\tmp\installrecovery.sh /data/local/tmp/recovery/install.sh
STEP 6:
Make the corresponding directory /data/local/tmp/recovery with your file explorer
STEP 7:
Copy the files mentioned in the bat from the extracted version to the folder location. All the files go into one folder with the same file name apart from the last one which is renamed installrecovery.sh to install.sh.
STEP 8:
Double check everything that it mentioned in the bat file is in the correct directory on the device.
STEP 9:
Open terminal emulator and type "su" - a dialog box should open from Kingroot asking if you want to grant it root access, press yes!
STEP 10:
Use "pwd" and "cd" to see where you are and to change directory. You are trying to get to /data/local/tmp/recovery.
STEP 11:
Once your there type in "./install.sh" to start [NUT]'s recovery installer. A whole bunch of stuff should come up in the window explaining the status of the installer.
STEP 12:
If all went well - your device should reboot and go straight into TWRP. MAKE A BACKUP!!!
STEP 13:
From here I directly wiped the device and installed a new ROM. Click the thanks button if this worked for you - Happy Flashing!
Credits
@[NUT] for his custom recovery and support.
@istux for his research, suggestions and perseverance.

Finally you get it
Great work!

istux said:
Finally you get it
Great work!
Click to expand...
Click to collapse
thanks - lets hope it is useful for someone

Awsome! Very useful guide

MAKING SYSTEM WRITABLE - [Z5] [Nougat] AFTER ROOT

after ROOTING Nougat 32.3.A.0.376 (E6833 E6853 E6883) (E6633 E6653 E6683 ), we will still face ERROR while removing system apps, because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in #terminal
Code:
su
mount -o rw,remount /system
ORRR
Code:
su
busybox mount -o rw,remount,rw /system
-----------

What???

Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that

chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
Mee too unable to write on system

download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry
Credits: https://forum.xda-developers.com/showpost.php?p=70677335&postcount=92

I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!

Can any of you share here your perfectly rooted working kernel for Z5 E6683 DSDS ????

chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
i found a workaround and it goes
installing busybox
installing terminal
and writing following codes
Code:
su
'to give terminal root access
busybox mount -o rw,remount /system
later using ROOT APP REMOVER i manage to remove all bloatware!

toncheee said:
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Click to expand...
Click to collapse
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!

YasuHamed said:
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
Click to expand...
Click to collapse
I also think the issue is not the RIC but something to do with the Nougat filesystem itself.
I can delete all the files and folders with any file managers I like but like after 1 sec they all reappear as nothing ever happened to them !!!
How strange is that ??
It shows file sizes when I delete them and take times to delete the folders with , say for 500MB
but they still reappear after just 1 refresh or 1 sec.
I cant figure it out at all for the sake of my sanity --- why the hell this is happening ????

https://www.dropbox.com/sh/2kf8wg3g13pv869/AACB3l8iPJHJnBlpnGorRqrha?dl=0
@bungadudu @chinmoy32
I followed bungadudu-s steps and it worked i can change permissions and prove it with link i provided.
And chenges, yes they stick after reboot and i can rename files allso, but:
after reboot i have to repeat this steps if i want to change something elsewhere, old changes do stick aroind though
I deletet phone to 0 mb in twrp, flashed AU nougat .372 with flashtool, rebooted into twrp, flashed zip file provided in link, then flashed supersu in link and rebooted, no custom kernel used
Next i will try to copy modified thermal files now and see if they stick after reboot and if kernel aduitor uses them, see you later
Observations:
-i changed permissions from file /system/build.prop and changed lcd density to 320 and i have bootloop
working on how to boot it up...

YasuHamed said:
after ROOTING Nougat 32.3.A.0.372 (e6833 e6853 e6883) (E6633 E6653 E6683 ), we will still face ERROR because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in terminal
Code:
su
busybox mount -o rw,remount /system
-----------
Click to expand...
Click to collapse
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links

https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse

chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
I install both of them via play.google.com
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
&
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
later i opened terminal and ran those commands
later i installed System App remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
granted it SU rights and removed HANGOUTS and GOOGLE MOVIES etc

It seems to work to some extend but if you want to go tweak it up, kablaaam
i did not managed to boot it up after bootloop sadly, i need my phone so this is it for me this week

stipi69 said:
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
Click to expand...
Click to collapse
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before

I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "cd /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse

stipi69 said:
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "md /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
Click to expand...
Click to collapse
I just managed to restart my phone successfully after changing the LCD density to 320 [I also use this value since always ]
But then I carefully just deleted 1 single app and booom--- boot loop
PS. i used root explorer to just click mount as R/W and then do anything to system partition --

Great you magaged it, and yes 320 seems so right.
And i asume there is no way to break bootloop?...other than reflashing?
I had trouble afterwards on downgrading to.253, 3x times error on start, even after reseting " power & + " and couple of full wipes in twrp.
I had to flash lineage from twrp and boot it up and only then flashtool succeeded pushing. 253.
This nougat will be fun i see
If there is something to try tell me i will flash it once more tonight, otherways i can do it on weekends
Oh i did not tell, i managed to copy modified thermal files with no error and then changed lcd density so i can not 100% tell which caused bootlop, since i did not reboot in between...

chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
there is another way which i did not try because the busybox commands worked for me
its about flashsing updater script
delete_recursive(
"/system/app/GoogleAnalyticsProxy",
"/system/priv-app/GoogleBackupTransport",
"/system/priv-app/textinput-chn-xxhdpi",
);
https://forum.xda-developers.com/showpost.php?p=70920831&postcount=2015

[GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and Magisk installation OLD guide

The guide below is depreceatred and should NOT be used.
Please use the guide in this thread instead. - https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you could not call in.
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
This has been confirmed to work on:
XT1922-3 Model
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile variant of this device with the code name JETER with Android 8.0.0 Build OCP27.91-23
XT1922-9 Model
Links to all boot images have been removed at the request of Motorola.
If you have done an OTA for your Device these boot.img's may not work for your device. We will need a newer boot.img to patch.
Please make backups using TWRP. Right now there is no ROM from moto for these devices that I've found. So proceed with caution.
Just make sure to download the correct boot.img for your device.
If you have another model please follow the first few steps to grab the stock boot.img and post it here and I can patch it.
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio/releases/platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Step 1.) Download _ this TWRP image to the ADB/Fastboot folder on your computer.
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding power and both volume buttons at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel):
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you to revert to stock later.
Step 5.) Now type:
Code:
adb reboot bootloader
Step 6.) Download either XT1922-9_no_dm-verity_boot.img or XT1922-7_no_dm-verity_boot.img or XT1922-5_no_dm-verity_boot.img or XT1922-4_no_dm-verity_boot.img or XT1922-3_no_dm-verity_boot.img patched dm-verity boot image depending on which device you have and download it into the ADB/Fastboot folder on your computer.
Step 7.) Run the following command from your computer to install the relevant boot image to your device.
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-7_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-5_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-4_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-3_no_dm-verity_boot.img
Step 8.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Step 9.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. When it prompts for a decryption password select cancel again.
Step 10.) From your computer type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
Step 11.) Download this patched fstab.qcom boot image into the ADB/Fastboot folder on your PC.
Step 12.) Run the following command from command prompt/terminal on your computer:
Code:
adb push fstab.qcom /vendor/etc/fstab.qcom
Step 13.) Next click the "Wipe" button in TWRP and slide "Swipe to Factory Reset" THIS WILL WIPE YOUR DATA ON YOUR PHONE. Ensure you have backup.
Step 14.) Download the Magisk zip file https://github.com/topjohnwu/Magisk/releases/ to your ADB/Fastboot folder.
Step 15.) Run the following command to push the boot image to your device
Code:
adb push Magisk-vXXX.zip /tmp
This will push the Magisk-vXXX.zip to your /tmp folder
Step 16.) Flash Magisk-v16.4.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 17.) Reboot your device
Step 18.) It will say N/A in the top corner of your device for a few seconds. Then it will boot the the Motorola boot screen and you can setup your device as a new phone.
Step 19.) Verify Magisk Manager is installed and the root functionality works.
Step 20.) ???
Step 21.) Profit
Credits:
CodyF86 and his Moto E5 thread for clues as to what it would take to turn off DM-Verity

Reserved

1st....
Thanks for your guide!

i can confirm this works perfectly on my boost model if you do everything exactly as the tutorial say. will be posting screenshots once i re download xda labs on phone. using computer as i type this
---------- Post added at 01:40 AM ---------- Previous post was at 01:00 AM ----------
alright so until this thread is able to work on the app i cant post screenshots but magisk safety net protection works. my kernel adiutor settings stuck on boot. the only things thats not working is being able to uninstall some bloatware and useless system apps. o theres no device encryption on boot anymore which is nice.

Hi @kwiksi1ver,
Thank you for your guide! :highfive:
However, I recomend to do one of these two things:
- Option 1: Add to your guide a link for download the original "boot.img" and "recovery.img". This is required for restoring the original state of the device in case of some error.
- Option 2: Instead of directly "flash" the "recovery.img" in the step 3, you can recommend to use a simple "boot". This doesn't replace the recovery and it's more safe. Then you can instruct to the user to make a backup of his stock boot & recovery partitions. See my guide about G6+: https://forum.xda-developers.com/moto-g6/how-to/moto-g6-root-guide-start-pro-users-t3795197
If you do it, then some users can rollback when some trouble appear. For example, someone here: https://forum.xda-developers.com/showpost.php?p=76789160&postcount=27 needs your help (I have a G6+, so I can't help him).
Regards. :angel:

Sweat
So here is confirming. This works 100% alas i can only confirm the boost version as well.
THANK YOU

I Can confirm this works on the boost mobile variant of the jeter if you follow every step exactly. Magisk works, and safety net is good, and magisk hide works tried Pokemon go and it was successful. Modules I used on my Moto g4 play work on my g6 play. Only thing I've noticed is the bloatware and certain system apps ( like Facebook) refuse to be uninstalled. Screenshots provided. Kernel aduitor settings also stayed when I used the apply on boot option

manos78 said:
Hi @kwiksi1ver,
Thank you for your guide! :highfive:
However, I recomend to do one of these two things:
- Option 1: Add to your guide a link for download the original "boot.img" and "recovery.img". This is required for restoring the original state of the device in case of some error.
- Option 2: Instead of directly "flash" the "recovery.img" in the step 3, you can recommend to use a simple "boot". This doesn't replace the recovery and it's more safe. Then you can instruct to the user to make a backup of his stock boot & recovery partitions. See my guide about G6+: https://forum.xda-developers.com/moto-g6/how-to/moto-g6-root-guide-start-pro-users-t3795197
If you do it, then some users can rollback when some trouble appear. For example, someone here: https://forum.xda-developers.com/showpost.php?p=76789160&postcount=27 needs your help (I have a G6+, so I can't help him).
Regards. :angel:
Click to expand...
Click to collapse
Cheers. I've added the stock files to the second post in the thread and I'll see what I can do about updating with the fastboot boot twrp.img steps and have the user backup their stuff first.
I wish I could help the user your referenced too, but they have different device. They have a G6, I have a G6 Play, and you have a G6+.
ninjakira said:
Only thing I've noticed is the bloatware and certain system apps ( like Facebook) refuse to be uninstalled.
Click to expand...
Click to collapse
You can run "adb shell" then "su" then type "pm disable com.facebook.system", "pm disable com.facebook.katana", "pm disable com.facebook.appmanager", "pm disable com.ironsource.appcloud.oobe", "pm disable com.lookout" etc which will disable the apps.
Alternatively you could use a file manager with root access and delete the various files and reboot. Make sure to keep a backup just in case you need them:
/oem/app/FcbkAppManagerSprint/FcbkAppManagerSprint.apk
/oem/app/FacebookStubSprint/FacebookStubSprint.apk
/oem/priv-app/FcbkInstallerSprint/FcbkInstallerSprint.apk
/oem/priv-app/LookoutSprint/LookoutSprint.apk
/data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==/base.apk

kwiksi1ver said:
Cheers. I've added the stock files to the second post in the thread and I'll see what I can do about updating with the fastboot boot twrp.img steps and have the user backup their stuff first.
I wish I could help the user your referenced too, but they have different device. They have a G6, I have a G6 Play, and you have a G6+.
You can run "adb shell" then "su" then type "pm disable com.facebook.system", "pm disable com.facebook.katana", "pm disable com.facebook.appmanager", "pm disable com.ironsource.appcloud.oobe", "pm disable com.lookout" etc which will disable the apps.
Alternatively you could use a file manager with root access and delete the various files and reboot. Make sure to keep a backup just in case you need them:
/oem/app/FcbkAppManagerSprint/FcbkAppManagerSprint.apk
/oem/app/FacebookStubSprint/FacebookStubSprint.apk
/oem/priv-app/FcbkInstallerSprint/FcbkInstallerSprint.apk
/oem/priv-app/LookoutSprint/LookoutSprint.apk
/data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==/base.apk
Click to expand...
Click to collapse
I just mainly want to remove Facebook as a system app and remove it's automatic updates and just reinstall it on play store as a regular app lol. I did try a couple root uninstallers and the failed to remove anything from the system. Also used a file manager with root and the results were the samr. The phone automatically resets when there's an attempt at removing system apps. I'll try to get a logcat for ya

I removed it all without any tools except for adb and it doesn't come back. Here is the code I used.
Code:
adb shell
su
cp -r /oem/app/FcbkAppManagerSprint /sdcard
cp -r /oem/app/FacebookStubSprint /sdcard
cp -r /oem/priv-app/FcbkInstallerSprint /sdcard
cp -r /oem/priv-app/LookoutSprint /sdcard
cp -r /data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==/base.apk /sdcard
mount -o rw,remount /oem
mount -o rw,remount /data
mount -o rw,remount /system
rm -rf /oem/app/FcbkAppManagerSprint
rm -rf /oem/app/FacebookStubSprint
rm -rf /oem/priv-app/FcbkInstallerSprint
rm -rf /oem/priv-app/LookoutSprint
rm -rf /data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==
reboot
If you run all of those command it will backup your annoying APK's to the /sdcard folder if you need them later and then delete the originals and then it reboots your device.
The ironsource appcloud apk is the thing that reinstalls the Sprint bloatware apps over and over again, so removing or disabling that is key to keeping the crap gone.

Will rooting Boost mobile variant unlock the phone ?

piesladowy said:
Will rooting Boost mobile variant unlock the phone ?
Click to expand...
Click to collapse
No it does not sim unlock the phone. Sprint/boost will unlock your sim provided you are with them for a year with the same device

XT1922-5
Hi Guys. I've tried use this procedure on XT1922-5 (Brazilian varianty) however, how I imaginated, it did not work. After the Step 18 my phone stay freez on Motorola boot screen (freezed in M). After that I did a full restore to stock and now phone is ok.
Some one her that have this same Moto g 6 Play variant (XT1922-5) could help me to create a recovery + root process too?
Best regards, GESATEC

Stock Firmware file?
Does any one have a stock frimware file for the
JETER??
I have a 100% stock JETER
If some one can help me I'll post the frimware file ones I get it

FizzyAps said:
Does any one have a stock frimware file for the
JETER??
I have a 100% stock JETER
If some one can help me I'll post the frimware file ones I get it
Click to expand...
Click to collapse
Hi,I believe that there is another Topic with JETER rom:
https://forum.xda-developers.com/moto-g6/development/firmware-stock-moto-g6-play-aljeter-t3792868
Please, check If your stock file os different before post

GESATEC said:
Hi,I believe that there is another Topic with JETER rom:
https://forum.xda-developers.com/moto-g6/development/firmware-stock-moto-g6-play-aljeter-t3792868
Please, check If your stock file os different before post
Click to expand...
Click to collapse
that's got the unlocked model not sprint/boost

JETER
FizzyAps said:
that's got the unlocked model not sprint/boost
Click to expand...
Click to collapse
Ok, I understood . I would lik JETER rom too.
Can u put files on Google Drive?

GESATEC said:
Hi Guys. I've tried use this procedure on XT1922-5 (Brazilian varianty) however, how I imaginated, it did not work. After the Step 18 my phone stay freez on Motorola boot screen (freezed in M). After that I did a full restore to stock and now phone is ok.
Some one her that have this same Moto g 6 Play variant (XT1922-5) could help me to create a recovery + root process too?
Best regards, GESATEC
Click to expand...
Click to collapse
Hi, can you post your stockboot.img file that you backed up during step 4? I can modify that and then I see if we can make it work for the XT1922-5 as well.

kwiksi1ver said:
Hi, can you post your stockboot.img file that you backed up during step 4? I can modify that and then I see if we can make it work for the XT1922-5 as well.
Click to expand...
Click to collapse
Manu thanks. Let me arrive at my home and I'll post it

ninjakira said:
No it does not sim unlock the phone. Sprint/boost will unlock your sim provided you are with them for a year with the same device
Click to expand...
Click to collapse
If you managed to get the boost version onto sprint, in theory it should be eligible for a sim unlock w/50 days of service.