Rooting Help for a Complete Beginner - Sony Xperia XZ2 Compact Questions & Answers

PLEASE DO NOT FOLLOW MY INSTRUCTIONS. I DO NOT KNOW WHAT I AM DOING.
Basically, I am a complete noob wanting to root my device - using Sony Xperia XZ2 Compact Dual (H8324, build 52.0.A.8.107, so that's Android 9)[1]. I'm hoping someone can check if what I'm doing is correct and answer a few questions, as I am much confused. I appreciate your help. Hopefully, this can help other people like me who want to get into rooting.
I've been reading a lot on this website and other websites, and I think I have a basic idea of what I am supposed to do, but I've been reading some info and I do not know what is outdated and am being overwhelmed.
Before all else, I should have adb and fastboot from the 'android-tools' package (installed from pamac-manager on Linux, but there are other ways to get it for other OS's)[2]. Also, connect device to PC.
First, I need to unlock the bootloader, which can be done using two methods[3]:
1. Using adb/fastboot by running these commands:
Code:
adb reboot bootloader
fastboot oem unlock-go
OR
2. Following Sony's guide on https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Then, I need TWRP, which, officially, does not support the XZ2C, so I need a custom one, like MartinX3's (https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597)[4], for example:
Download 'Sony Xperia XZ2 Compact/android_9/twrp/custom_rom/2019-07-12_12-15-30_twrp_sodp_xz2c.tar.gz'[4] (which is the latest version as of me writing this).
Extract the archive
Open a terminal in the same directory[5]:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
In TWRP menu on the device, open Advanced Menu, "Install recovery ramdisk" using twrp.img
Finally, I need to install a root manager, Magisk, for example (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
Download 'Latest Stable' (*.zip)
Download MagistManager from the GitHub link (*.apk)
Place the files somewhere on the device through the PC (Downloads folder, for example)
Boot into recovery (which will open TWRP(?))
Install the *.zip
Boot normally and install the *.apk
At this point, I should have a rooted Sony Xperia XZ2 Compact Dual?
Process related questions:
[1] Does build number matter when rooting? Or is it just the Android version?
[2] Are there any specific Sony drivers I need to install on my Linux PC, or is 'android-tools' enough?
[3] Does the method of unlocking the bootloader matter? Which is best for a beginner? Also, when doing the adb/fastboot method, should the device be connected in recovery mode before-hand?
[4] So, over here I am downloading the TWRP for the normal Sony Xperia XZ2 Compact, not the Dual SIM one. Does that matter? I do use the two SIM slots.
[5] Again, when doing these commands, should I be in recovery mode before-hand?
Other questions:
I've been reading a lot about the DRM thing and breaking some functionality, including the camera. Is that still a problem on Android 9? I heard it's mostly not. What am I loosing from unlocking the bootloader on Android 9?
I like to keep my device updated for the security patches. I read that I cannot do that through the device with root, but I have to flash it from my PC each time. Does anyone have a guide for Linux users? Do I loose root? Where do I even download the updates from?
Also, should I keep TWRP and Magisk updated for security and stability? How do I do that?
Thank you for reading this relatively long post, and I appreciate your help.

About the rooting, follow my twrp thread after unlocking in the newest PIE firmware.
With PIE you loose sony backup&restore, OTA, maybe Bluetooth ps4 controller, the login into the Sony club (I think) and maybe low light night antinoise algorithms (I think).
You can also switch to one of the custom ROMs. Existenze is stock and gives you at least an OTA notification.
Or omnirom and sonyaosp, based on SODP, a rewrite of the hardware drivers in an aosp compatible way. (Camera is work in progress).
For stock upgrades you need xperifirm, newflasher and removing the userdata.sin (if you don't want a full wipe)

MartinX3 said:
About the rooting, follow my twrp thread after unlocking in the newest PIE firmware.
With PIE you loose sony backup&restore, OTA, maybe Bluetooth ps4 controller, the login into the Sony club (I think) and maybe low light night antinoise algorithms (I think).
You can also switch to one of the custom ROMs. Existenze is stock and gives you at least an OTA notification.
Or omnirom and sonyaosp, based on SODP, a rewrite of the hardware drivers in an aosp compatible way. (Camera is work in progress).
For stock upgrades you need xperifirm, newflasher and removing the userdata.sin (if you don't want a full wipe)
Click to expand...
Click to collapse
Ok. I think I get.
First I unlock bootloader.
Flash latest stock firmware (which I can download from XperiFirm).
Flash TWRP and Magsik.
Finally, use the eXistenZ Pie patch.
Thank you very much.
But before I go ahead and follow through, I have a few more questions:
Does re-flashing the latest stock firmware mean I will lose personal data stored on the device (like call/chat history for example)?
Also, in the eXistenZ Pie patch, it says it is based on 52.0.A.8.83, but latest firmware is 52.0.A.8.107. Does that matter?
Finally, I will only get the OTA notification, but I will need to follow the process again to update (flash latest firmware from XperiFirm, --> flash TWRP and Magisk, --> eXistenZ patch)?
Again, thank you.
Edit: I almost forgot. Installing TWRP for H8314 on H8324 (Dual SIM) is ok, right? I won't lose that functionality?

orapyt said:
Ok. I think I get.
First I unlock bootloader.
Flash latest stock firmware (which I can download from XperiFirm).
Flash TWRP and Magsik.
Finally, use the eXistenZ Pie patch.
Thank you very much.
But before I go ahead and follow through, I have a few more questions:
Does re-flashing the latest stock firmware mean I will lose personal data stored on the device (like call/chat history for example)?
Also, in the eXistenZ Pie patch, it says it is based on 52.0.A.8.83, but latest firmware is 52.0.A.8.107. Does that matter?
Finally, I will only get the OTA notification, but I will need to follow the process again to update (flash latest firmware from XperiFirm, --> flash TWRP and Magisk, --> eXistenZ patch)?
Again, thank you.
Edit: I almost forgot. Installing TWRP for H8314 on H8324 (Dual SIM) is ok, right? I won't lose that functionality?
Click to expand...
Click to collapse
First flash newest firmware and boot it once, then unlock please
And yes, dual/single is the same twrp.
Existence V9 for 107 comes soon. Yes, sou should wait

MartinX3 said:
First flash newest firmware and boot it once, then unlock please
And yes, dual/single is the same twrp.
Existence V9 for 107 comes soon. Yes, sou should wait
Click to expand...
Click to collapse
I think I understand the process completely now. Thank you for your help.
About the OTA notification: I will get the notification for update from Sony but I will have to wait for the eXistenZ Pie patch to update first, right?

orapyt said:
I think I understand the process completely now. Thank you for your help.
About the OTA notification: I will get the notification for update from Sony but I will have to wait for the eXistenZ Pie patch to update first, right?
Click to expand...
Click to collapse
Yes. Just update to 107, wait for v9 and with existence you'll get the august notification

MartinX3 said:
Yes. Just update to 107, wait for v9 and with existence you'll get the august notification
Click to expand...
Click to collapse
Oh, sorry. My question was not clear enough. I feel bad for wasting your time.
I mean like each time I update I have to re-flash latest stock firmware and start from beginning, losing all data? I cannot update from the UI in the device?
Also, while I wait for v9 (I am on 52.0.A.8.107), can I unlock bootloader now, flash TWRP and Magisk in order to make a backup using Titanium Backup?

orapyt said:
Oh, sorry. My question was not clear enough. I feel bad for wasting your time.
I mean like each time I update I have to re-flash latest stock firmware and start from beginning, losing all data? I cannot update from the UI in the device?
Also, while I wait for v9 (I am on 52.0.A.8.107), can I unlock bootloader now, flash TWRP and Magisk in order to make a backup using Titanium Backup?
Click to expand...
Click to collapse
No problemo, I'm a recognized XDA slave hihi
Oh, just remove userdata.sin all the time before using newflasher and no userdata will be lost
As backup tool I can recommend migrate and titanium backup
Titanium backup makes a backup of each app and can restore it
Migrate makes a big flashable twrp zip.
(Make sure removing the app cache to reduce the backups size)

MartinX3 said:
No problemo, I'm a recognized XDA slave hihi
Oh, just remove userdata.sin all the time before using newflasher and no userdata will be lost
As backup tool I can recommend migrate and titanium backup
Titanium backup makes a backup of each app and can restore it
Migrate makes a big flashable twrp zip.
(Make sure removing the app cache to reduce the backups size)
Click to expand...
Click to collapse
lol
'userdata_X-FLASH-CUST-B6B5.sin' from the firmware folder?

orapyt said:
lol
'userdata_X-FLASH-CUST-B6B5.sin' from the firmware folder?
Click to expand...
Click to collapse
Correct

MartinX3 said:
Correct
Click to expand...
Click to collapse
Thank you. :good:
Is there a way for people like me to contribute to this amazing community?

orapyt said:
Thank you. :good:
Is there a way for people like me to contribute to this amazing community?
Click to expand...
Click to collapse
Yeah, provide ROMs for the xperia Rama devices or be a developer/tester.
Andjoin our Sony slack
And follow the big SODP link I put in all my project pages

Just to give closure to this: I did get eXistenZ on my Sony XZ2C Dual on build 52.0.A.8.107, and here is what I did exactly (could act as a guide, but please read completely before doing anything and I'm not responsible for any losses before, during, or after the process).
Prerequisites:
adb/fastboot (through package manager for Linux ('android-tools') or here for Windows)
mono (required only for Linux, through package manager)
Drivers (only required for Windows--install them from device manager when you have device turned on normally, and then again after you reboot into bootloader, as Windows detects it as a different device)
XperiaFirm
Newflasher
Steps:
I. Flashing the latest firmware:
Use XperiaFirm to get latest stock firmware with your customization (run with mono on Linux)
Delete userdata{somethingsomething}.sin from the firmware folder created by XperiaFirm
Place Newflasher into the folder
Shut-off phone
Hold volume-down button and plug in phone to computer to enter recovery mode
Run Newflasher and enter 'n' when prompted
Just wait until everything finishes (no data should be deleted).
II. Unlocking the bootloader:
Before you do, understand that you are voiding your warranty. Also it has some side-effects:
MartinX3 said:
With PIE you loose sony backup&restore, OTA, maybe Bluetooth ps4 controller, the login into the Sony club (I think) and maybe low light night antinoise algorithms (I think).
Click to expand...
Click to collapse
Get the unlock code for your device here.
Enable USB debugging from developer menu
Plug in phone to computer
Connect to fastboot:
Code:
adb reboot bootloader
Enter unlock code:
Code:
fastboot oem unlock 0x<insert your unlock code>
Wait for device to boot again (For me data was deleted. Also, don't mind the "can't check for corruption"; it's a side-effect of unlocking the bootloader)
III. Installing TWRP:
Get TWRP for XZ2
From the "Download," navigate to "Xperia XZ2 Compact/android_9/twrp/stock/" and download latest one
Extract, and open terminal in the extracted folder as a working directory
Plug in phone
Copy twrp{sometingsomething}.img to phone somewhere
Boot into TWRP:
Code:
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp{somethingsomething}.img
Enter pin if prompted
Go to Advanced, Install recovery ramdisk, and pick the copied twrp image (this will install twrp to recovery mode, so you just shutdown phone, hold volume-down button and power, wait for vibration, and let go to enter TWRP)
IV. Flashing other stuff (Magisk, permissive):
Copy Magisk .apk and .zip, and permissive .zip from the twrp .tar.gz downloaded above to your phone somewhere
Enter installed TWRP by going into recovery mode (shutdown phone, hold volume-down button and power, wait for vibration, and let go)
Go to install, pick the Magisk .zip, and slide to install
Reboot into system and install the Magisk .apk to make sure it's working (do not update Magisk as it may be unsupported; only use the version provided in the twrp .tar.gz)
Boot back into TWRP and install permissive the same way Magisk .zip was installed
Reboot into system and launch Magisk manager, go to modules to check if permissive is working
V. Installing eXistenZ:
Download the version for your firmware version
Place the .zip somewhere on your phone
Boot into TWRP (shutdown phone, hold volume-down button and power, wait for vibration, and let go)
Got to wipe, advanced, and selected only Data and Dalvik/ART Cache
Now install eXistenZ .zip like installing the Magisk .zip
Reboot into system
??? (takes a long time)
Profit!! (for me data was deleted, so I had to reinstall Magisk and permissive)
Notes:
You probably want to backup your data.
Personally, I used UK customization firmware because that is what my phone shipped with.
Some guides say remove the *.ta files from the firmware folder, but I did not and it worked fine??
For some reason, all fastboot commands return "FAILED (command write failed (Success))" on Linux (fastboot version 9.0.0_r41) for me, but worked on Windows??
If you get 'error getting bootctrl module,' in TWRP you might need to mount something... forgot what exactly (might be OEM)??
Edit 1: Added drivers for Windows

Related

[Q] z1 comact stuck

i try to root me z1 compact (i have unlocked the bootloader) but i forget to save th superuser zip into sd card....i wwant in fastboot mode and i didn t innstall the zip.........and now i am stuck on fastboot mode...and i haven t do backup..what can i do ?plz help
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.
how?
mkhairym said:
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.[/QUOTE
man i copy the supersu in the sd card but when i choose zip i press update superSU and it writes ......done
and when i prees reboot system now it gets me into recovery mode again
Click to expand...
Click to collapse
thanos kary said:
mkhairym said:
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.[/QUOTE
man i copy the supersu in the sd card but when i choose zip i press update superSU and it writes ......done
and when i prees reboot system now it gets me into recovery mode again
Click to expand...
Click to collapse
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
listen
darkmystel said:
thanos kary said:
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
listen ...i haven t done buckup and i haven t flash my rom......my phone can get in to the recovery mode ONLY....can i get out from the recovery mode ?:crying:
Click to expand...
Click to collapse
Well if you have access to your recovery you should be able to mount your SD card there and then connect it to your PC. From there you can transfer a zip file to your phone and flash it.
I don't see anything mentioned about which custom recovery he flashed.
Could this be a stock recovery that he is in? (that may not allow mounting etc.)
.....
LaZiODROID said:
I don't see anything mentioned about which custom recovery he flashed.
Could this be a stock recovery that he is in? (that may not allow mounting etc.)[/QUOTE
i have done this....... and then what? i have 4.4.4 android
This is a CWM-Based Recovery 6.0.4.6 Touch Recovery for Xperia Z1 Compact!
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
[ info ]
This Recovery is built from CWM 6.0.4.6 sources!
I dont have this device with me and I dont intend to buy one... my friend wanted root on his phone so I created this to help him out...
all the testing was done remotely on users devices...
[ PROOF ]
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
CyanogenMod and FreeXperia Team (especially jerpelea) for too many things *
special thanks to @swedan for helping out with testing and risking his devices for the sake of development!!! and NO, his phone was NOT damaged during testing
ME for creating this for u guys!
[ Requirements ]
Bootloader unlocked
working fastboot
STOCK ROM FW:
4.4.2
14.3.A.0.757 - v04
14.3.A.0.681 - v03
4.3
14.2.A.1.142 - v02
14.2.A.1.114 - v01
or ROMS BASED ON THAT FIRMWARE
[ features ]
standard CWM recovery 6.0.4.6 - TOUCH RECOVERY!
kernel is insecure (ro.secure=0)
adb debugging is enabled by default in OS
TIP: if u are experiencing very slow backup in CWM do this
[ WARNING ]
for flashing this kernel you WILL NEED TO UNLOCK BOOTLOADER! Check this thread for more info (same steps as Xperia Z1 are used for Xperia Z1 Compact)
UNLOCKING BOOTLOADER WITHOUT TA BACKUP WILL LEAD TO IRREVERSIBLE LOSS OF DRM KEYS!!!
AND YES CAMERA STILL WORKS AFTER UNLOCKING BOOTLOADER!!!
[ known issues ]
adb is not working in recovery (can be fixed later)
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the boot.img to the folder containing fastboot binary
flash the boot.img using fastboot:
Code:
fastboot flash boot boot.img
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
Click to expand...
Click to collapse
....
darkmystel said:
thanos kary said:
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
yes i get into recovery and then what i must do?
Click to expand...
Click to collapse
thanos kary said:
darkmystel said:
yes i get into recovery and then what i must do?
Click to expand...
Click to collapse
I think a little more studying should have been done before flashing things. Now that we know you can get into CWM Recovery, you can flash a custom ROM. Note that doing so will involve wiping your data/cache/system - so whatever apps you were using on your phone will be gone (along with the data for each app, like your preferences etc.)
And since your bootloader is unlocked, you can flash pretty much any ROM you like because the unlocked bootloader allows custom kernels to be flashed.
As an example, you can flash SlimKat. It is a custom ROM with a custom kernel. The page is here: http://forum.xda-developers.com/showthread.php?t=2700456. You can find the download links in post #3. There will be a ZIP file for the ROM, and then optionally, another ZIP for the Google Apps (aka GAPPS), which would allow you to sign in to your Google account, use Play Store, etc. SlimKat offers 3 gapps (which I will link here because the GAPPS link on that thread seems to take me to a login page): They have mini, normal, and full. Take your pick..
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
Once you've downloaded them, copy the Slimkat ZIP to your external SD card. Also copy the GAPPS zip that you chose (if you wanted that).
Put the external card back into the phone and power it up, and get back into recovery like you did earlier. In recovery, before flashing the zips, you should do your wipes (this is where it wipes your apps/data/system). But as a precaution, maybe go into "install zip from sdcard", navigate through your external card to make sure the ZIP files are available to you.
I think that most ROM install zips take care of these wipes for you, but it's a good habit to get into when flashing custom ROMs.
You're going to:
1) Wipe data/factory reset (this will wipe the data and cache)
2) Go into Advanced and wipe Dalvik cache
3) Go into Mounts and Storage and format /system
Once that's done, you're going to go to "install zip from sdcard", choose your external card, and choose the SlimKat ZIP. That will flash the ROM and kernel. Once that's done, you're going to do one more flash - which is the GAPPS zip (if you decided that you wanted it).
Once that flash is done, you should be able to just reboot and the phone will start to boot into the new ROM. Note that on first boot, it will take some time - so you may be staring at the boot animation for a few minutes.
Click to expand...
Click to collapse
root?
LaZiODROID said:
thanos kary said:
I think a little more studying should have been done before flashing things. Now that we know you can get into CWM Recovery, you can flash a custom ROM. Note that doing so will involve wiping your data/cache/system - so whatever apps you were using on your phone will be gone (along with the data for each app, like your preferences etc.)
And since your bootloader is unlocked, you can flash pretty much any ROM you like because the unlocked bootloader allows custom kernels to be flashed.
As an example, you can flash SlimKat. It is a custom ROM with a custom kernel. The page is here: http://forum.xda-developers.com/showthread.php?t=2700456. You can find the download links in post #3. There will be a ZIP file for the ROM, and then optionally, another ZIP for the Google Apps (aka GAPPS), which would allow you to sign in to your Google account, use Play Store, etc. SlimKat offers 3 gapps (which I will link here because the GAPPS link on that thread seems to take me to a login page): They have mini, normal, and full. Take your pick..
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
Once you've downloaded them, copy the Slimkat ZIP to your external SD card. Also copy the GAPPS zip that you chose (if you wanted that).
Put the external card back into the phone and power it up, and get back into recovery like you did earlier. In recovery, before flashing the zips, you should do your wipes (this is where it wipes your apps/data/system). But as a precaution, maybe go into "install zip from sdcard", navigate through your external card to make sure the ZIP files are available to you.
I think that most ROM install zips take care of these wipes for you, but it's a good habit to get into when flashing custom ROMs.
You're going to:
1) Wipe data/factory reset (this will wipe the data and cache)
2) Go into Advanced and wipe Dalvik cache
3) Go into Mounts and Storage and format /system
Once that's done, you're going to go to "install zip from sdcard", choose your external card, and choose the SlimKat ZIP. That will flash the ROM and kernel. Once that's done, you're going to do one more flash - which is the GAPPS zip (if you decided that you wanted it).
Once that flash is done, you should be able to just reboot and the phone will start to boot into the new ROM. Note that on first boot, it will take some time - so you may be staring at the boot animation for a few minutes.
Click to expand...
Click to collapse
man i haven t done root yet.....i have 4.4.4 android can you give instructios? and slimkat it is not support my z1 compact
Click to expand...
Click to collapse
thanos kary said:
man i haven t done root yet.....i have 4.4.4 android can you give instructios? and slimkat it is not support my z1 compact
Click to expand...
Click to collapse
When you say you want to root, it means that you want to root the current system that you are on. But from what you have described in this thread, you are currently having a problem with your phone, where it does not boot normally into the system/ROM. You boot straight into Clockworkmod Recovery, every time. Correct? If this is correct, then rooting your current ROM probably won't help your situation (because you are not able to boot normally into the system).
Slimkat is a ROM that has root access included. I believe that pretty much any custom rom has root included. I'm not sure what you mean when you say that slimkat does not support your Z1 compact. You should be able to flash Slimkat to your Z1 Compact. The link from my previous post points to the Slimkat thread, which is in the Z1 Compact Original Android Development forum, so it is made for Z1 Compact.
That said, you don't need to choose Slimkat - I provided that just as an example of a custom rom that has a custom kernel included. Look through the Xperia Z1 Compact Original Android Development forum for custom roms that use custom kernels. Most of those roms have the custom kernel included in their ZIP. Whichever custom rom you choose, make sure to READ the original post (and other posts if necessary) to get the information you need on how to install it, or to find out what files you will need for that ROM (as some roms have add-ons and stuff you may find interesting).
There are also ROMs that are stock-based. Those can be found in the Xperia Z1 Compact Android Development forum. These roms also have root included, and are built to run on the standard stock Sony kernel. Some of them may be based on a specific stock Sony kernel version, so pay attention to that.
If you want to start over, and flash a pure stock Sony ROM to your phone (also known as an FTF), you can do that at any time by downloading an appropriate FTF for your phone, and flashing it by loading the FTF with FlashTool. It will then ask you to put your phone into FlashMode (which is done by making sure the phone is OFF, then holding the VolDown button, and connecting the USB cable while still holding the VolDown button. Once the flash begins, you can let go of the VolDown button) But !! Please note that if you haven't used FlashTool before, you will need to install some drivers. They are included with FlashTool, in a folder called Drivers. You would choose the driver specific to your phone, plus the FlashMode driver, plus the Fastboot driver. If you are using Windows8, you will have to do some extra work to get those drivers to install correctly. It involves booting Win8 into a mode where Driver Signature Enforcement is disabled, then installing the drivers found in the drivers folder of FlashTool. You can easily find out how to do that by searching online.
Hope this helps... don't make any risky flashing moves if you aren't certain about them - just keep reading and searching and you will eventually find the answers you need.
zoom out
LaZiODROID said:
When you say you want to root, it means that you want to root the current system that you are on. But from what you have described in this thread, you are currently having a problem with your phone, where it does not boot normally into the system/ROM. You boot straight into Clockworkmod Recovery, every time. Correct? If this is correct, then rooting your current ROM probably won't help your situation (because you are not able to boot normally into the system).
Slimkat is a ROM that has root access included. I believe that pretty much any custom rom has root included. I'm not sure what you mean when you say that slimkat does not support your Z1 compact. You should be able to flash Slimkat to your Z1 Compact. The link from my previous post points to the Slimkat thread, which is in the Z1 Compact Original Android Development forum, so it is made for Z1 Compact.
That said, you don't need to choose Slimkat - I provided that just as an example of a custom rom that has a custom kernel included. Look through the Xperia Z1 Compact Original Android Development forum for custom roms that use custom kernels. Most of those roms have the custom kernel included in their ZIP. Whichever custom rom you choose, make sure to READ the original post (and other posts if necessary) to get the information you need on how to install it, or to find out what files you will need for that ROM (as some roms have add-ons and stuff you may find interesting).
There are also ROMs that are stock-based. Those can be found in the Xperia Z1 Compact Android Development forum. These roms also have root included, and are built to run on the standard stock Sony kernel. Some of them may be based on a specific stock Sony kernel version, so pay attention to that.
If you want to start over, and flash a pure stock Sony ROM to your phone (also known as an FTF), you can do that at any time by downloading an appropriate FTF for your phone, and flashing it by loading the FTF with FlashTool. It will then ask you to put your phone into FlashMode (which is done by making sure the phone is OFF, then holding the VolDown button, and connecting the USB cable while still holding the VolDown button. Once the flash begins, you can let go of the VolDown button) But !! Please note that if you haven't used FlashTool before, you will need to install some drivers. They are included with FlashTool, in a folder called Drivers. You would choose the driver specific to your phone, plus the FlashMode driver, plus the Fastboot driver. If you are using Windows8, you will have to do some extra work to get those drivers to install correctly. It involves booting Win8 into a mode where Driver Signature Enforcement is disabled, then installing the drivers found in the drivers folder of FlashTool. You can easily find out how to do that by searching online.
Hope this helps... don't make any risky flashing moves if you aren't certain about them - just keep reading and searching and you will eventually find the answers you need.
Click to expand...
Click to collapse
ooooohhh man i love you ,....it works with slimkat....thank you ...thank you...but i don t like this rom ..tell me if you know......how to get back to the officil from sony?
and if you can give a guide to root 4.4 android z1c
thanos kary said:
ooooohhh man i love you ,....it works with slimkat....thank you ...thank you...but i don t like this rom ..tell me if you know......how to get back to the officil from sony?
and if you can give a guide to root 4.4 android z1c
Click to expand...
Click to collapse
You could try to flash Kitslim (http://forum.xda-developers.com/showthread.php?t=2743177)
It is a slightly optimized rom based on the original Sony stock rom.
I use it and ist awesome. You have the stock feeling with this.
.....
Schlengge said:
You could try to flash Kitslim (http://forum.xda-developers.com/showthread.php?t=2743177)
It is a slightly optimized rom based on the original Sony stock rom.
I use it and ist awesome. You have the stock feeling with this.
Click to expand...
Click to collapse
i will flash this rom...but first i want to go in official rom and then i will root the rom
how to root?
thanos kary said:
i will flash this rom...but first i want to go in official rom and then i will root the rom
Click to expand...
Click to collapse
can anyone tell me how to root....i can not root with easy towel root

[HOW-TO] How to SuperSU the Moto G5 Plus (Rooting Guide)

Hey guys,
Thanks to @vanche for the modified kernel and twrp recovery and @fayiaz for the guide on how to root and @Johny Cipel for the original guide and everyone else like
@topjohnwu
@santhosh
@abdyasar
For the original twrp, root and other stuff.
Now thats out of the way
Requirements:
-Unlocked Bootloader (Moto G5 Plus with offers from Amazon won't have unlockable bootloaders but if you buy the standard model from them then you'll be fine)
-Vanche's Modified TWRP from here (http://cloud.vache-android.com/Moto/potter/TWRP/twrp-3.1.0-0-potter.img)
- Vanche's Modified Boot Kernel from here (http://cloud.vache-android.com/Moto/potter/root/potter_boot_test7.img)
- Vanche's Wifi Patch because wifi will stop working after flashing the modified boot kernel (http://cloud.vache-android.com/Moto/potter/root/wlan_custom.zip)
- Chainfires Root http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
--- If you already have TWRP on your phone, the one by Santosh, you must flash the one made by Vanche or it wont work and you can just download the recovery image and flash it via twrp by toggling the flash zip button on the twrp recovery install menu.
1.. Download all the three files then boot your phone into bootloader mode by holding Volume Down + Power
2. Connect your phone to your PC and then open the adb terminal wherever adb is located open command prompt at that folder
3. Place the recovery image and boot image where the adb terminal folder is located
4. Fastboot flash recovery first and then boot into recovery at least once then reboot into bootloader fastboot flash boot the modified boot image.
5. Boot into the system (May take a while for the first time after flashing the boot image).
6. Place the wlan_custom.zip into your phones internal storage
7. Boot back into recovery and then flash the zip this time
8. Then download and flash the SR3 Super Su from above using recovery and you should have root!!
Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.
wiping?
do we need to wipe storage in this process?
yourtitan said:
do we need to wipe storage in this process?
Click to expand...
Click to collapse
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once
Awesomeslayerg said:
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once
Click to expand...
Click to collapse
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.
wifi not working after supersu root
wifi not working mate.. Flashed custom zip .. No use..
Dhan... said:
wifi not working mate.. Flashed custom zip .. No use..
Click to expand...
Click to collapse
Did you correctly flash vanche TWRP and boot image? Because you're supposed to do that first and then flash the wifi zip..
yourtitan said:
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.
Click to expand...
Click to collapse
The phone will wipe as soon as you unlock the bootloader so best to back up first.
Sorry but what's the differences beetwen this method and magisk?
Awesomeslayerg said:
Requirements:
-Unlocked Bootloader (Amazon bought Moto G5 Plus dont have unlockable bootloaders so your out of luck)
Click to expand...
Click to collapse
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.
Dahenjo said:
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.
Click to expand...
Click to collapse
Will do thanks
The "Magisk method" didn't give me privileges on /system, there are some things I can do and others do not, this method gave me full root access like in the other MotoG devices? And the safetynet check fails too?
Anyway thank you very much!!
What's going to be different than magisk root?
Videon Tutorial [SuperSu]
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE
gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to
gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to reflash above said recovery?
will it wipe my current data on both storage?
Pls guide..........How is Moto app working with super su?
Shamith08 said:
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE
Click to expand...
Click to collapse
Thank you so much! This worked! Why would WiFi stop working with this boot image?
I'm
donjuro said:
Thank you so much! This worked! Why would WiFi stop working with this boot image?
Click to expand...
Click to collapse
I don't know why but you have to flash WLAN in order to get it to work
Twrp backup can't worked
I successfully rooted my moto g5 plus mobile. And TWRP INSTALL Latest supersu via. But sdcard card backup can't worked. Why can't work sdcard in twrp? I think this twrp unofficial so not supported sdcard process. Please help me. How to work sdcard backup twrp. I try mount sdcard. But can't mount sdcard. Totally I'm very tired. Please help me.
Does someone have the img file for G5/Cedric?
Awesomeslayerg said:
...Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.
Click to expand...
Click to collapse
Do you think that will be fixed soon with a newer version of SuperSU, or some "root hider" apps? The idea of running a phone without root is absurd/offensive/rediculous IMO, but I don't want to be denied the ability to run certain apps because the developers have the rediculous idea that running without root should be "OK" to ordinary users? This idea is extremely offensive to me!!!
Guys, I wonder why the OP is "Account currently disabled"? I hate running without root, but, it seems a bit early and not all the problems have been worked out yet, such as TWRP not accessing SDCARD yet - I think I was a little premature buying my Moto G5 Plus as we don't really have "stable" release custom ROMs or fully functioniong TWRP and to even root we have to rely on some not well known sources for kluged files to make SU work?

Unofficial TWRP based on v4.88B - WiFi working, Magisk Rootable

*IT IS FOR UNLOCKED BOOTLOADERS ONLY*
Voila ..
Alas TWRP is working on Nokia 8 NB1 based on v4.88B kernel. Wifi and Magisk root both are working on my mobile. Please and report if it is working for you as well.
Download:
https://mega.nz/#!nRgVWKqB!fWx4zO1f19Shs_I8Thkw4ycsZMMMmSYP24cK0MHIBlM
Flash:
adb reboot bootloader
fastboot flash boot_a TWRP_NB1_boot_v2.img
fastboot reboot
Click to expand...
Click to collapse
If working well, also flash boot_a partition as well.
Then following below thread to root it using MagiskManager
https://forum.xda-developers.com/nokia-8/development/pre-rooted-boot-image-nokia-nb1-v4-88b-t3798063
Check Following Post for Update:
https://forum.xda-developers.com/showpost.php?p=77307135&postcount=74
WARNING: Don't change boot slot using TWRP . I am not responsible if you brick your phone.
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
head66 said:
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Click to expand...
Click to collapse
Didn't checked by flashing it. But, logically yes. Though system partition is still encrypted. That may cause an issue. But for custom ROM developers - it can be a start. Provided - your bootloader is unlocked.
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Hey,
maybe that can help u.
Fastboot need Admin permissions on windows open a CMD as Admininstator.
On Linux just login into user root.
WORKING
Image is working! Thanks a lot!
Magisk is also working after patch. (With WiFi)
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Did you checked if USB debugging is on in the developer settings?
Powered by View 10
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
I have it problem on Windows 10 too. If you want very strong, download any Linux-based LiveCD, flash it on USB and load. After this install adb and fastboot from LineageOS site (delete space after "https://" https:// wiki.lineageos.org/devices/bacon/build) and run commands.
P.S.: I am sorry for my bad English, but I hope help you
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
corpsegrinder62 said:
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
Click to expand...
Click to collapse
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
bidhata said:
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
Click to expand...
Click to collapse
Thanks bro. You are making tremindous progress on this phone though. Hopefully you inspire other devs to jump the train on our N8
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
iKillua said:
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
Click to expand...
Click to collapse
You need an unlocked bootloader. Else fastboot not let you overwrite /boot partition. No OST LA required.
trandafirmd said:
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
Click to expand...
Click to collapse
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
bidhata said:
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
Click to expand...
Click to collapse
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
trandafirmd said:
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
Click to expand...
Click to collapse
It is the same image for TA 1004 / TA-1012 . Taken from v4.88B update.
I realized that after the download finished. I apologize for jumping the gun. Since I'll have to unlock my bootloader, is there a way to do a full system backup through adb or otherwise? Most likely, I have a locked bootloader and before I can figure out a way to unlock it, I will have to backup as much data as possible since unlocking it will most likely wipe all my data and do a factory reset.
You can not make a backup unfortunately.
could you and other people making useless threads put it in the thread title and OP so that 99.9% of nokia 8 owners that dont have a way of unlocking the bootloader dont waste our time by having the salt rubbed in, thanks

[GUIDE] How to Root OnePlus 7T without TWRP

So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi
Flashed and working flawless.
Really thanks for this.
Awesome work bro.
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder
Working, thanks a lot @mauronofrio
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it
Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.
Thanks, rooted successfully
?
To be honest need video tutorial asap?
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.

Rooting with Android 10

My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
buddy the best bet for not hard/soft bricking is to downgrade to android 9 and install preloader and then root/install recovery.
if you want you can search "konah begonia guardian" on YouTube. he has quite nice guides.
regards
david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse
FYI this device is really easy to brick that one single misstep can brick your phone and mostly the only way to restore it is via service center. So you must really pay attention to each instruction on the guides. Most root guide need to flash custom recovery first so I guess its inevitable. In order to flash custom recovery, you need to downgrade to Android 9 or Pie, more higher version than that will brick your phone.
In order to root this phone, you first need to unlock the bootloader, refer to here for the guide. (Warning, just follow the unlock bootloader guide since the flashing twrp and rooting guide from there are kinda outdated and not recommended to follow)
Then you need to flash factory firmware (preloader and lk) so you can unbrick your phone in case you brick it, refer to Megathread for guide how to do it. After that you can flash custom recovery, then you can flash magisk via custom recovery to root your phone.
This guy does a ice job explaining a simple root method for Android 10 on youtube
thanks :good:
one more thing , in all methods , after flashing twrp recovery and booting into it the guides say to delere a file called "recovery-from-boot.p".
i saw on telegram channel describing the same mathod but it also said that if i skip the deletion of that file the original recovery will remain , the phone will be rooted
and be able to OTA update.
does anyone know if its ok to do that?
I rooted from Android 10, and same with you, I only need to root to remove ads and install a few apps only.
I used this guide
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Make sure that the twrp is the one that compatible with android 10, otherwise it won't boot to recovery.
Have mi flash app and android stock rom ready on your PC so that if you find problem you can always flash the stock ROM.
david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse
gaban05 said:
I rooted from Android 10, and same with you, I only need to root to remove ads and install a few apps only.
I used this guide
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Make sure that the twrp is the one that compatible with android 10, otherwise it won't boot to recovery.
Have mi flash app and android stock rom ready on your PC so that if you find problem you can always flash the stock ROM.
Click to expand...
Click to collapse
after reading a bit i think the right recovery version to root with android 10 is in the following thread:
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
and this is the procedure:
1. Download recovery file from this message
2. Open CMD from the dir where you store twrp.img (it's important because you don't need to type whole path of the twrp.img
3. Turn off the device, hold Power button & Vol- to enter fast boot and connect device to USB
4. In CMD type first fastboot devices to ensure that device is in fastboot, this is not important but recommended. Output should be something like this 4l6lsctgskpj4swc fastboot
5. Then it's time to flash recovery file. Type fastboot flash recovery twrp.img
6. This is the most important step now, on the device screen it should write USB Transmission ok if that is there you are ready to go. Remove device from the USB and hold Power button & Vol+, When the device turn off the screen keep holding Vol+ it'll keep screen off for about 5-10 seconds, then it'll show a recovery, still holding vol+ because it will get restarted again, and again still holding vol+ and recovery will show up. Simple words (Keep holding vol+ till recovery not appear for second time)
7. If it asks for a password, it's a password you use on the device it self(one for unlocking the screen or unlock the device after reboot), enter password and wait for Data decrypt.
At the moment there is no root and recovery will be replaced after you try to boot next time. To prevent it from replacing recovery do next (my opinion is skipping step 8. and 9. and having stock recovery because of MIUI updates):
8. Go to mount and tick the /system
9. Go back, tap on advanced, then to File Manager search for system_root dir open it, then find system and on the bottom is file called recovery-from-boot.p Remove that file and recovery wont be replaced
Now how we root it:
10. Go to advanced and tap on Close AVB2.0 and swipe to confirm
11. Go back and tap to Install ROOT, swipe to install and Reboot system
This will install Magisk v19.4, after boot you can update it from the Magisk Manager, my suggestion is to first update the manager then Magisk binary.
can anyone confirm that?
Thisnameisepic said:
This guy does a ice job explaining a simple root method for Android 10 on youtube
Click to expand...
Click to collapse
Yes it was his video I used to flash twrp to my phone,his explanation is amazing
david_z said:
after reading a bit i think the right recovery version to root with android 10 is in the following thread:
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
and this is the procedure:...
can anyone confirm that?
Click to expand...
Click to collapse
Yup, that worked for me on Android 10, global 11.0.5.0 QGGMIXM. The LR Team TWRP is the only one that worked for me, and I tried several.
Do make sure you download the v1210 for Android 10...
- in step 5, the 'twrp.img' you write in the command must match the actual filename you downloaded. Either change the name of the file, or enter the full filename in the command line.
- step 6 is kinda tricky. you might not get it right the first time. before installing twrp, i actually made sure i got the key combination right by going into stock recovery a few times.
When you do get TWRP up and running, the very first step is to set the language to English (unless you want Chinese). It will be the lower right buttton on the very first screen you are presented with (where you are asked for your password, if there is one).
I did not do steps 8 or 9, and TWRP has held. I did, however, reboot right back to recovery immediately after my first successful TWRP load-up. That may have stuck it.
The LR Team TWRP installed Magisk 20.3 for me. 20.4 is the latest, but I'm a little timid about letting it update. I had softbrick issues with trying to install Magisk manually thru this TWRP (instead of using the 'Install Root' button). Let me know if you update yours.
HTH
david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse
You can go follow guide from telegram group
i tried twrp avb2.0 but it gave me bootloop after power off and on again , it's better to get the avbmeta image file from fastboot rom(same miui rom you use) and disable it from fastboot mode.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Categories

Resources