Database Develop

Rooting from .101 walkthrough

This is the first time I root/flash my Xperia ZR from .101. This post is to document how I rooted my phone and the problems I encountered.
Tools I used:
Helium - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
Flashtool (Windows Installer)
http://www.flashtool.net/index.php
Backup TA
http://forum.xda-developers.com/showthread.php?t=2292598
DooMLoRD Easy-Rooting-Toolkit v17
http://forum.xda-developers.com/showthread.php?t=2327472
XZDualRecovery
http://forum.xda-developers.com/showthread.php?t=2261606
ROM/files used:
[Stock ROM][LB&UB][4.3] Rooted, Deodexed & Zipaligned Stock 10.4.1.B.0.101
by IJskonijn22
http://forum.xda-developers.com/showthread.php?t=2713073
C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf: which can be downloaded from the above thread
C5503_10.4.1.B.0.101_Generic NL.ftf: which can be downloaded from the above thread
Idea:
1. Downgrade to .310
2. Root it
3. Install Recovery
4. Flash rooted .101 ROM
Steps:
1. Backup all the data in the Internal Storage
2. Backup apps data using Helium - App Sync and Backup
3. Install all Flashtool and driver
Flashtool comes with drivers installer. I checked "Flashmode Drivers", "Fastboot Drivers", and "Common drivers Lagan, Fusion3 board"
4. Enable USB Debugging
5. Use Flashtool and Flashmode to downgrade to .310
When asked to hold "back buttom" and connect the USB cable, hold volumn down instead.
6. After booting into .310, enable USB Debugging Mode and UNKNOWN SOURCES
7. Make sure you close Flashtool in your PC
8. Run runme_win.bat in DooMLoRD Easy-Rooting-Toolkit v17 and root the device
9. (Optional) After rooting, backup the TA in case you need to unlock the device in the future.
10. Run install.bat and install XZDualRecovery
11. Copy the ROM zip file to the SD card and flash it using Recovery
12. Swith Off the device
13. Use Flashtool to flash C5503_10.4.1.B.0.101_Generic NL.ftf, CHECK exclude system
14. Boot and after 1-2 minutes, reboot the phone
15. Restore apps data
16. DONE
Advice:
1. Take some screenshots for the homescreen before everthing, so you can put the apps icons back to where they were after rooting the phone
2. Check MD5 checksum of the files downloaded
3. Make sure the battery of the PC and phone are enough
4. Download everything before you start
5. Have fun
Some problems I encountered:
Problem with MTP/MSC USB Mode:
MTP mode seems cannot be used with Flashtool. For .101, you can find them in Setting->Xperia->USB Connection.
Using DooMLoRD Easy-Rooting-Toolkit v17, got stuck at *daemon started successfully*:
1. Make sure ADB driver is installed
2. Make sure no other adb.exe process is on
3. Make sure USB Debugging Mode and UNKNOWN SOURCES are enabled
4. Try Restart PC
5. Try uninstall drivers and install again

Hello,
for all fellow ZR users: you do not need to downgrade your ROM version to root it.
here is a simple way, you will only need Flashtool, Cyanogenmod kernel, SuperSu zip and original .230 ROM kernel
1 Backup TA, link provided in first post (this is optional but highly RECOMMENDED)
2 Unlock Bootloader, you will need flashtool and code from Sony
3 Download SuperSu and place it somewhere on your device
4 Flash boot.img from CyanogenMod 10.2.1 (unzip and flash only boot.img using fastboot mode - USB in holding vol+ while device is powered off)
5 Boot into recovery (power on, hold Vol+), choose "install zip from SD card", find where u placed SuperSu zip, install it and power off the device, do not do anything more
6 Connect device in flashmode (USB in holding vol- while device powered off) and flash the kernel form your 10.5.A.0.230 ROM (or any .230 ftf for that matter, for ex. this). Flash ONLY kernel, uncheck everything else.
Original instructions for previous versions of ZR firmware are here courtesy of NeoJeo

drZeT said:
Hello,
for all fellow ZR users: you do not need to downgrade your ROM version to root it.
here is a simple way, you will only need Flashtool, Cyanogenmod kernel, SuperSu zip and original .230 ROM kernel
1 Backup TA, link provided in first post (this is optional but highly RECOMMENDED)
2 Unlock Bootloader, you will need flashtool and code from Sony
3 Download SuperSu and place it somewhere on your device
4 Flash boot.img from CyanogenMod 10.2.1 (unzip and flash only boot.img using fastboot mode - USB in holding vol+ while device is powered off)
5 Boot into recovery (power on, hold Vol+), choose "install zip from SD card", find where u placed SuperSu zip, install it and power off the device, do not do anything more
6 Connect device in flashmode (USB in holding vol- while device powered off) and flash the kernel form your 10.5.A.0.230 ROM (or any .230 ftf for that matter, for ex. this). Flash ONLY kernel, uncheck everything else.
Original instructions for previous versions of ZR firmware are here courtesy of NeoJeo
Click to expand...
Click to collapse
And if you dont have a ta backup you still need to downgrade to gain root.
If you dont you will lose the drm keys and bravia.
Skickat från min C5503 via Tapatalk

Mario.D said:
And if you dont have a ta backup you still need to downgrade to gain root.
If you dont you will lose the drm keys and bravia.
Skickat från min C5503 via Tapatalk
Click to expand...
Click to collapse
This is a way to root a ZR which includes unlocking the bootloader, it is clearly stated. Unlocking your bootloader is supported by manufacturer since it is Sony who provides you with a key. So I suppose it is no more unsafe than any other operation with the device, although yes it voids your warranty. That's why making TA backup is recommended, one can relock the bootloader easily with it.
If one's priority is safe play, do not proceed with flashing and rooting in the first place.

sijav said:
well that's interesting that you had restored your TA without downgrade. I couldn't.
alright I just translated with google, did you mean: derogate = void? cumbersome = bloated? and lengthy = too many steps? please correct me if I'm wrong my English is not good.
Click to expand...
Click to collapse
Derogate means belittle, make something appear less than it is. This is what you've done on Thibou's thread and here. It also means not being able to discuss thing in civilized manner, swearing and insults.
Cumbersome means inconvenient or too complex.
Lengthy means taking more time than one would expect
sijav said:
oh and I don't give a **** for your thinking too if you don't like it, you're free to report me to moderators.
Click to expand...
Click to collapse
This is exactly what I have done.

drZeT said:
Derogate means belittle, make something appear less than it is. This is what you've done on Thibou's thread and here. It also means not being able to discuss thing in civilized manner, swearing and insults.
Cumbersome means inconvenient or too complex.
Lengthy means taking more time than one would expect
This is exactly what I have done.
Click to expand...
Click to collapse
thanks for full translation of those words

This method works with prerooted 4.4 too.
If you want to backup your TA, root is required. And if you are in 4.3/4.4 already, you need to downgrade to root your device tho.

Hi , Everyone is saying one different method. Please give one method. That we will follow. I am really confused by seeing different methods. Don't understand a bit

Just a little would be great

Hello,
To start i'm familiar with android, rooting, custom roms etc. But now I have this very nice new phone this Z3 Compact. A really nice phone but i want more. I just can't get my phone downgraded to .93 firmware to root it without unlocking the bootloader. But i some way it just won't boot properly after flashing one of those. Know i've tried .264 firmware and that one just worked fine.
Mayby you guys could help me out.
I've already managed to update te latest drivers with an unsigned drivers with windows 10 so they are fine...

Hi there
I have had success with doing what you are trying to do.
Search for the file: D5803_23.0.A.2.93_Customized CE1.ftf - it came as a zip but I can't find the link now, it's on here somewhere in the development or original development part of the z3c forum.
And flash it using flashtool64, being sure to check boxes for wiping APPS_LOG AND USERDATA and when it asks if you want to use script, click no.
After you have successfully booted into that firmware, carefully follow instructions for giefroot to gain root access via USB and your computer.
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Somebody else will have to help you from there because I could not work out how to upgrade out of that old firmware without losing root. I ended up unlocking the bootloader and flashing viper-x which is pre-rooted marshmallow rom by Jenkins. I then applied DRM restore and it appears to have worked...I got the phone as a hand-me-down so I don't really care about losing warranty. It already had a smashed back.
Good luck.
You'll end up unlocking that son of a ***** some time ;p

I already had that file, that you recommend, it didn't work, but i'll try it again. Mayby it's a corrupt file.
Hope it is!
EDIT
Thanks m8 don't know what i was doing wrong but hey it worked! Guess a corrupt file mayby.

Ok,
I know want to backup my DRM files, but it says it can't start ADB server and offcourse the check for SU binary FAILED and also the request for root permission. But my phone is rooted, tested with root checker!
Any stepps i missed mayby?

Problem solved, I had to restart my Pc in order to start ADB deamon normal!

From this guide
40 Flash the pre-rooted fw (flashable.zip) from the recovery (touch "install zip", select /storage/sdcard1/flashable.zip then confirm install) on the phone, then power off the phone (DO NOT REBOOT)
41 To power off, go into the "power options" and hit "power off" (dont do "reboot in flashmode" DO power off)
42 Unplug USB (yes this is required, DO IT)
43 Open Flashtool and select the non-pre-rooted fw (this is 23.1.A.0.690), but DESELECT system: in "EXCLUDE" make sure you check the checkbox next to "SYSTEM", flash it.
44 press volume DOWN and plug USB cable while keeping volume DOWN pressed, when flashing starts, stop pressing the volume button
45 After flash is done and when flashtool tells you to, remove USB cable and start the phone
46 Congrats and enjoy, you made it to the end! you now have latest + recovery + root and backups of your DRM keys! (and of course all DRM functions enabled)
Click to expand...
Click to collapse
I'm currently on firmware 23.0.A.2.93 and rooted but this is android 4.4.4 and i want 5.1.1 as mentioned below.
I've downloaded a pre rooted firmware and put it on my sdcard [Rom][5.1.1][D5803]Pre-Rooted+++XZDR+2.8.21+[23.4.A.1.264]+-+BAL.zip.
I took a pre rooted firmware Newer then the guid listen to...
Is it now possible to just take this stock firmware D5803_23.4.A.1.264_1289-4696_R8C.ftf
How do i need to setup flashtool is this ok?
https://onedrive.live.com/redir?resid=AC16F01210B5FE5C!119&authkey=!ADFqguAuL4wnEps&v=3&ithint=photo%2cJPG
And why do we need to flash a stock firmware again without the system? Isn't this pre rooted firmware not enough ?
It would be great for some little help!!

I can guess why you don't want to unlock your bootloader, if its because you don't want to lose Sony's camera functionality and post image processing along with X-Reality
--------------------------------------
>Backup your DRM Keys using backup-ta get it here
>Unlock your bootloader via Sony's Website
>Flash any custom kernel with recovery pre-installed
>Flash SuperSU latest zip
>Flash this zip file to restore DRM Functions ( credits to @jimRnor )
>And you have a perfectly rooted phone with busybox installed
------------------------------------------
If you are still on kitkat ( Firmware .93 ) its very easy to get 5.1.1, just download a .246 (5.1.1) custom rom found in the Android Development Section, most custom roms are pre-rooted meaning you can flash them and still have root access on your device.
All you need to do is achieve root by using GIEFroot, and afterwards install NUTs Lockeddualrecovery so you can flash the rom. ( Take Note this only works for the .93 firmware [KK] )
If you plan to you use flashtool you cannot gain root on lollipop unless you have unlocked bootloader. Flashtool's main purpose is for locked bootloader devices to recover faster from bootloops and the like.

How to install MAGISC without TWRP and locked bootloader?

Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk

Not to hijack your thread, so consider this a free bump, but I am also curious. Galaxy S7 G920T here and looking for the same options.

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Sent from my Redmi 2 using Tapatalk

fake2die said:
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Click to expand...
Click to collapse
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.

veez21 said:
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
Click to expand...
Click to collapse
Right! So you can accomplish a Magisk install without a custom recovery for example using the Magisk Manager or Flashfire but as stated above, in order to boot a modified boot.img the bootloader needs to be unlocked or otherwise it will refuse to boot it.

There should be an option to install magisc like a systeme update with the stock recovery.
Gesendet von meinem XT1650 mit Tapatalk

JRapsky said:
There should be an option to install magisc like a systeme update with the stock recovery.
Click to expand...
Click to collapse
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.

Sytis said:
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Click to expand...
Click to collapse
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?

COOLPLAY6FAN said:
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
Click to expand...
Click to collapse
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Actually you can boot into twrp rather than install/flash twrp which means u must use cmd to boot twrp everytime for flashing something~ As for locked bootloader, just like others said, you must unlock it.

Didgeridoohan said:
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
Click to expand...
Click to collapse
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance

COOLPLAY6FAN said:
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
Click to expand...
Click to collapse
There are installation instructions on how to create the patched boot image with the Magisk Manager in the release thread.
When you have the patched_boot.img file, you'll need to flash it to your device. On most normal devices you can do this with fastboot. Check out your device's forums/DuckDuckGo/Google/Whatever-search-engine-you-use for instructions on that.

I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
* Unlocked bootloader is needed. Period.
* A custom recovery is needed to flash Magisk. TWRP for instance.
* That custom recovery prevent the built-in OTA update to work
* But TWRP can flash OTA updates that can be downloader from XDA for example
Am I correct?
Also,
* Magisk needs a patched boot image
* This image has no impact on the OTA process at all
* There are encryption matters to take care of (I don't understand them yet though).
Is everything correct?
Thanks.

Krystanos said:
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
Click to expand...
Click to collapse
Let's see about answering those statements/questions.
* Unlocked bootloader is needed. Period.
Click to expand...
Click to collapse
Yes.
* A custom recovery is needed to flash Magisk. TWRP for instance.
Click to expand...
Click to collapse
Not necessarily. You can let the Magisk Manager patch your device's stock boot image and then flash it to your device with fastboot. See the installation instructions in the release thread.
* That custom recovery prevent the built-in OTA update to work
Click to expand...
Click to collapse
Yes.
* But TWRP can flash OTA updates that can be downloader from XDA for example
Click to expand...
Click to collapse
No. And yes. Official OTA files can (most of the time) not be flashed in TWRP. ROM zips and flashable firmware packages can.
* Magisk needs a patched boot image
Click to expand...
Click to collapse
Yes, that's all Magisk is about.
* This image has no impact on the OTA process at all
Click to expand...
Click to collapse
It definitely does. See the official docs
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips for more info on how to keep OTA capabilities for your device.
* There are encryption matters to take care of (I don't understand them yet though).
Click to expand...
Click to collapse
Possibly. Depends on what you're talking about.

Great answers. It's more clear for me now. Many thanks sir!

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Hi!
There are good news for you, rooting with magisk is very easy that way . No bootloader unlocking, custom recovery,
adb and fastboot command, no sdk no mtk tool . NOTHING but Sp flashtool - our best friend. This method really works with mtk phones android 5.0+ .
What U only need is
Sp flashtool and its drivers /scatter file with the ROM/ -I think not mtk devices with their own flashtool will work too
the ROM of your device
Magisc manager app on the phone
First of all you need clear up the device / after backup somewhere if needed/with sp flashtool - flash the whole ROM in format+download mode.
Install Magisc manager app , it will load for U a zip file in the map of the app
Put the boot img file of your rom in that map too
Run install option - it will create a patched boot img file within the app s map
Run again sp flashtool with download mode , mark only the boot section , and flash that patched boot img in phone
After reboot phone it is rooted
best regards

Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it? 
 @Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)

lefteriskmail said:
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
Click to expand...
Click to collapse
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device.
Done.
All of this is covered in the installation instructions...
The folder being mentioned above is MagiskManager on your internal storage (where the patched boot image is also stored).

Magisc
Hi!
Magisc works fine for me from the first time. Excuse me I won't do installation again to see how it goes. Really it causes some hesitation but in the end it's clear.
I use Total commander, and magisc folder is on the external SD card after installing magisc manager app. Factory reset later will not clear the root. After installing manager it says "not installed" till the end of the rooting process. Opening the app it begins to look after the downloadable zip file, you have to wait and download it. This zip and the stock boot img must be in the same place in a folder, and the app itself makes the patched boot img but I don't remember what was the name of the option. This is the flashable img file. In the end after flashing with flashtool and rebooting, magisc manager says "installed". Good luck

Hi, I am trying to centralise this sort of information and am compiling it in another topic for Magisk and android-based media centres too.
Trying to properly document things (full sentences with references, links, and examples) rather than just writing some brief summarised steps that most people will not understand - not just for myself but to share should it assist others learn and understand the preparation and steps involved, plus consequences and ramifications of their actions (which never seem to be stressed enough).
Here is what I have compiled. Hopefully it will help and prevent you going loopy!? :silly:
- - - - - - - - - - - - - - - - - - - -
*** EXTREMELY CLEAR MAGISK ROOT INSTRUCTIONS ***
(Work In Progress! To Be Verified & Critiqued By Others)​
Connect your WiFi so that all auxillary files can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free disk space. Allow for 1-2 hours to perform these steps. Do not rush!
Bootloaders come with every Android device, and give it all the instructions on how to boot and what to execute. If your Bootloader is locked, then you have not flashed anything like TWRP previously, or, you have re-flashed a stock Bootloader and Recovery, etc. The process is much easier when you have previously rooted the device using another method, and the Bootloader already unlocked.
To preserve your System partition, Magisk only modifies the unlocked Bootloader boot partition, which can easily* be restored and 'locked' later.
0. Before starting anything, always perform a FULL Backup (ADB) of your device, using a good quality USB cable and ADB FastBoot toolkit. Or on some devices you can use a Micro SD card with a TWRP recovery.img to boot into TWRP to perform a backup of partitions. Do both if you want! Make sure you search for the appropriate commands and usage of ADB FastBoot backup so that all data is backed up and included.
> ADB FastBoot: https://developer.android.com/studio/releases/platform-tools.html
> TWRP: https://dl.twrp.me/twrpapp/ \\ https://twrp.me/FAQ/
> Plus various other solutions...
1. Identify your device's firmware, build number, Bootloader, full unique model number, etc. Download any two of these apps:
a) AIDA64 ("System", "CPU" & "Android" tabs.)
b) Device Info HW ("General" & "System" tabs.)
c) DevCheck ("Hardware" & "System" tabs.)
2. Download the stock Bootloader, Recovery and Firmware (___.tar.md5) for your device model, variant and OS. (e.g. match your firmware, build number, bootloader, full unique module number, etc). Some sites will force you to pay to download - search around and you can get free download links, or sometimes from the manufacturer's site. From this firmware, we need to either extract or download the stock Bootloader.img image separately.
3. Install Magisk Manager v5.3-v5.6 as of 2017.02.22 ("Magisc" is typo by guy above).
4. Open Magisk and go to settings, adjust theme, change the language, enable notify for updates, change prompt timeout, etc.
5. On the home screen of the Magisk Manager app, click "Install" then in the pop-up select "Install" again.
a) If you have root access already, choose "Direct Method" - Select, wait, reboot and done (very easy!);
b) If you have stock recovery & locked bootloader, choose "Patch Boot Image File" - in the pop-up explorer, browse for the downloaded Bootloader Image.
c) ... I don't know about "Download ZIP Only" - I assume for flashing with Odin or ADB FastBoot from PC or existing root/unlocked user....?
NOTE: If you are being asked to browse and select a file, be aware that there is no confirmation! As soon as you click, that JPG or RAR archive will be used for patching (and result in an error if cannot be extracted!!!)
6. A file will likely be downloaded in the background (flashable ZIP), a black screen will pop-up processing etc. Wait.....
The processed Boot image will be processed and output to the /MagiskManager/ directory.
If you do NOT have root, or custom recovery, you will need to:
a) grab a PC, install the USB drivers for your device and confirm your device is fully recognised
b) then flash the "patched" Boot image from the Magisk Manager directory with ODIN for Windows or FastBoot on Windows via a good-quality USB cable.
7. ...
8. ...
I think that is it... I may have forgotten something. Please advise if something needs to be fixed or corrected. My Media Centre was already unlocked, so I did not have to unlock and flash the Bootloader.
9. Install free TWRP on your device, and choose to backup any partitions, should you wish to restore them later. Set an alarm to backup your device every few months! What are you prepared to lose if your device was lost/squashed/washed/crunched et al.???
Say thank you and donate to the amazing and all powerful Magisk developer 'TopJohnWu' and team!
Sweet! :fingers-crossed:

Question Root or twrp recovery

Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version

There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.

kouzelnik3 said:
There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.
Click to expand...
Click to collapse
Thank you so much... Can you link a tutorial or something to show how to root my phone? I wanna use substratum and I read Andromeda no longer works I've been on iPhone too long I forgot all the cool things android can do

s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
OnePlus 10 Pro NE2215 ***ROOTED*** (EX01 Update! READ BEFORE UPDATING)
This is for the NE2215 Rom. Step 1: Unlock your bootloader. Step 2: Download and install Magisk Stable or Canary. Your choice, but I used Canary. https://github.com/topjohnwu/Magisk Step 3: You can use either patch the stock boot or use my...
forum.xda-developers.com

s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help

s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help

Your first step will be to quickly set up the phone so your ready to handle the bootloader. Get past all set up, it doesn't matter what you do as your wipe the device anyway.
Second is going about the tackling the bootloader (oem unlocking) Plenty of guides however please use below Make sure your sat on the home screen (unlocked)
Bootloader link bro
(Once you have done this leave the terminal open, you need this again.)
Afterwards, do a quick setup, nothing major to this as your be wiping again anyway
g96818 was kind enough to post a quide here : Rooting​
I will refer to his links shared from now however in such a way you can stay here.
Assuming bootloader unlocked, device setup, now download and install the apk :Magisk root
You will also want his stock boot file being this here : Boot.img
With magisk open go to 'install' and select the boot image to patch it. Once it is patched up, connect back to the PC and copy the file to the same folder as the bootloader/ADB files . (rename the file to "patched_boot")
*terminal used before*
\To Reboot to bootloader - this also checks connection indirectly ( Copy from here and right click in CMD/terminal to paste it in)
Code in terminal:
adb reboot bootloader
(after a minute for two)Followed by:
fastboot boot patched_boot.img
After, reboot the phone so it powers up, maybe takes a tad longer but it should actually be very quick. (This is known as a temporary boot)
Then simply, "Open Magisk and perform a direct install". Afterwards i personally would reset the phone and set it up again properly (accounts, email, porn ect). The files you need remain.
Once set up, just be sure to reactivate developer options (OEM will now remain unlocked however re-enable USB debugging (if you have any issues this will save you!!!!!!!)) you cannot perm brick this phone unless you miss this one critical step up.
Reinstall magisk (I found my phone kept it however i also have it naturally on my play account so i may have missed it installing) Just check its there, any concerns you can now just directly flash again with no need for the PC now. Otherwise use a root checker off the play store however just get magisk anyway.
I then updated to A12 from the settings update and afterwards just for peace of mind, i redid a direct install via magisk incase the boot.img differed. I booted up perfectly fine after my update but for peace of mind i would recommend it.

Question Magisk support

I'm thinking of getting a 30 Ultra the next week, as I'm very disappointed with my OnePlus 10 Pro and the way OnePlus is heading.
I've been an OnePlus user since the 6 and never had a Motorola before, but the 30 Ultra really fascinates me.
Before I buy it I only wanted to ask how the modding community for motorola is.
Is Magisk easily installable with Motorola devices? Anything I should keep in mind with unlocking the bootloader / rooting of a motorola?
Thank's in advance

I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.

You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.

Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Yes, it's true.
But i big problem in poland, because customer write to unlock bootlader code = warranty is out.
I this method broken my Moto G82

Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?

No, you can unroot at any time if you uninstall magisk and flash the stock boot.img. But you can't / shouldn't relock the bootloader. I think times are over when a lot of people developed kernels / Roms / TWRP for specific phones. We need more people to take matters into their own hands, the market is flooded with too many different models.

@Killuminati91 any news on twrp for this phone yet?

_Hinnie_ said:
I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.
Click to expand...
Click to collapse
I'd be very thankful if you could share a guide for this

memocatcher said:
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?
Click to expand...
Click to collapse
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
memocatcher said:
I'd be very thankful if you could share a guide for this
Click to expand...
Click to collapse
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot

_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
Thanks a lot!!

TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
No success yet and I currently don't have the time to try, sadly. Device tree can be generated with helpers but the whole Linux compiling part is still gibberish to me.

TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.

arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.

logandavid said:
sorry for an off-topic question: What did you hate about Oneplus 10 Pro in particular?
Click to expand...
Click to collapse
I just don't like the way OnePlus is heading, like many users with the 10 Pro. It feels like using an Oppo device honestly and they made it impossible to unbrick your device by encrypting the popular MSM Tool.
After 5 years with OnePlus it's time for me to try something different

_Hinnie_ said:
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.
Click to expand...
Click to collapse
Yes it didn't work for me either

Nope !! , stay where you are, I had One Plus 9 Pro before, the Edge 30 Pro is much better in all aspects, One plus = Oppo, very bad phone.

A few questions;
Do you need to have a sim card installed in the phone during the 7 day wait period until the oem unlock button is available? Can I just connect the phone to wifi and let it sit for a week?,
Do you need some sort of unlock code from Motorola? I read the unlock directions, but to go any further it's asking for an email address and the need to register and account.,
Also what is the main difference between the pro and the ultra? Is it only the 200MP camera?

_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?

solsolhh said:
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?
Click to expand...
Click to collapse
This but for me dosn't work if write something there is 0 bytes, if you make it work let us know
Tools:
- Universal Mount System RW (Guide)
-> Fix for Android 12

arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
Kernel Sources now available, if you got the time:
Release MMI-S3SQ32.16-16-28 · MotorolaMobilityLLC/kernel-msm
eqs-g push for android 12
github.com