Related
thHello all,
This is a known way to root any android phone with an unlocked bootloader. I tested it on my ZR, it just works fine and is easy & fast to follow !
It works for all firmwares and it's a good way to root the latest stock rom (eg .67 / .244 or even KitKat firmwares).
Note: I'm not responsible if something happens to your device ! Just follow the procedure and all'd be fine !
Quick instructions
Unlock bootloader
Flash any CWM-containing kernel
Boot into recovery and flash su-bin-arm-signed.zip (or this one that worked for me on KitKat)
Revert back to stock kernel
Install SuperSU and update su.bin
Enjoy
Instructions for noobies (yes I didn't forget you !)
Unlock your bootloader.
You may want to backup your TA before. In this case you need an already rooted phone. I personnaly downgraded mine to .310 then rooted it with Doom's toolkit to be able to backup my TA.
Download and copy the following file to your phone: su-bin-arm-signed.zip (or this one for 4.3)
Install the firmware you want to be on when the phone gets rooted
Flash a kernel that contains CWM, for example this one which comes from CM 10.1 FXP234a (you can also try to hotboot it, didn't work for me).
You can flash it with a command line or a soft like FlashTool:
In FlashTool select Flash > Fastboot mode
Connect the phone in fastboot mode : when powered off, connect it to your laptop while pressing Volume + key. You can release the key when the LED turns blue
Select the kernel to flash and run the operation
> Now do not try to boot normally the phone because it won't boot, as the kernel's not compatible with the stock rom.
Boot into recovery:
Power on the phone
When the led turns violet at boot for 3", press Volume +
Now you are in recovery. Use Volume buttons to navigate and Power to confirm.
Select Install zip > Choose zip from sdcard or external sdcard (depending where you put the .zip to flash)
Choose su-bin-arm-signed.zip
Confirm
Go to Advanded > Power off
Flash back the stock kernel corresponding to the firmware installed on the phone (.244 -> .244 kernel). You can for example use Flashtool:
Download the .ftf of the build installed on your phone (no matter the location of the firmware)
Run Flashtool
Do Flash > Flashmode and select the .ftf you downloaded
Uncheck anything on the "Wipe" colon
Check everything on the "Exclude" colon except "KERNEL"
You should now only have kernel.sin and loader.sin on the content colon.
Click on Flash
Connect the phone in flash mode : when powered off, connect it to your laptop while pressing Volume - key. You can release the key when the LED turns green
Reboot the phone, install SuperSU, run it and update the su binary
You can relock the bootloader with Backup TA to recover warranty or Bravia Engine 2 without losing root.
May help:
- Stock .310 kernel
- Stock .244 kernel
- Stock .67 kernel
- Stock .569 kernel for C5503 / C5502
- Instructions by gspbeetle
Thanks to:
- Team FXP for the kernel
Sorry for my bad english and I hope I helped
NeoJeo said:
Hello all,
This is a known way to root any android phone with an unlocked bootloader. I tested it on my ZR, it just works fine and is easy & fast to follow !
It works for all firmwares and it's a good way to root the latest stock rom (eg .244).
Note: I'm not responsible if something happens to your device ! Just follow the procedure and all'd be fine !
Quick instructions
Unlock bootloader
Flash any CWM-containing kernel
Boot into recovery and flash su-bin-arm-signed.zip
Revert back to stock kernel
Install SuperSU and update su.bin
Enjoy
Instructions for noobies (yes I didn't forget you !)
Unlock your bootloader.
You may want to backup your TA before. In this case you need an already rooted phone. I personnaly downgraded mine to .310 then rooted it with Doom's toolkit to be able to backup my TA.
Download and copy the following file to your phone: su-bin-arm-signed.zip
Install the firmware you want to be on when the phone gets rooted
Flash a kernel that contains CWM, for example this one which comes from CM 10.1 FXP234a (you can also try to hotboot it, didn't work for me).
You can flash it with a command line or a soft like FlashTool:
In FlashTool select Flash > Fastboot mode
Connect the phone in fastboot mode : when powered off, connect it to your laptop while pressing Volume + key. You can release the key when the LED turns blue
Select the kernel to flash and run the operation
> Now do not try to boot normally the phone because it won't boot, as the kernel's not compatible with the stock rom.
Boot into recovery:
Power on the phone
When the led turns violet at boot for 3", press Volume +
Now you are in recovery. Use Volume buttons to navigate and Power to confirm.
Select Install zip > Choose zip from sdcard or external sdcard (depending where you put the .zip to flash)
Choose su-bin-arm-signed.zip
Confirm
Go to Advanded > Power off
Flash back the stock kernel corresponding to the firmware installed on the phone (.244 -> .244 kernel). You can for example use Flashtool:
Download the .ftf of the build installed on your phone (no matter the location of the firmware)
Run Flashtool
Do Flash > Flashmode and select the .ftf you downloaded
Uncheck anything on the "Wipe" colon
Check everything on the "Exclude" colon except "KERNEL"
You should now only have kernel.sin and loader.sin on the content colon.
Click on Flash
Connect the phone in flash mode : when powered off, connect it to your laptop while pressing Volume - key. You can release the key when the LED turns green
Reboot the phone, install SuperSU, run it and update the su binary
You can relock the bootloader with Backup TA to recover warranty or Bravia Engine 2 without losing root.
May help:
- Stock .310 kernel
- Stock .244 kernel
Thanks to:
- Team FXP for the kernel
Sorry for my bad english and I hope I helped
Click to expand...
Click to collapse
Sounds good. Testing this. Will let you know of the end results
akash4357 said:
Sounds good. Testing this. Will let you know of the end results
Click to expand...
Click to collapse
Thanks ! Did it work as expected ?
NeoJeo said:
Thanks ! Did it work as expected ?
Click to expand...
Click to collapse
Yes! It worked brilliant. Excellent find NeoJeo. Appreciate your help.
akash4357 said:
Yes! It worked brilliant. Excellent find NeoJeo. Appreciate your help.
Click to expand...
Click to collapse
Glad I helped
I wish had nown this before doing it the long way
Backing up with pc companion, downgrading with flashtool, rooting and then wait for OTA update and after that restore the backup with pc companion.
Skickat från min C5503 med Tapatalk 4
Mario.D said:
I wish had nown this before doing it the long way
Backing up with pc companion, downgrading with flashtool, rooting and then wait for OTA update and after that restore the backup with pc companion.
Skickat från min C5503 med Tapatalk 4
Click to expand...
Click to collapse
I also found the long ways to long... mostly with a slow connection. That's why I thought to this one
Regarding backup of TA partition, does it have to revert to original firmware or can I back it up even after flashing 4.2.2 with root?
grim_ripper said:
Regarding backup of TA partition, does it have to revert to original firmware or can I back it up even after flashing 4.2.2 with root?
Click to expand...
Click to collapse
Backing up TA Partition can only be done BEFORE you unlocked bootloader.
Thanks NeoJeo for this awesome rooting method! Flashed the Nordic 4.2.2 ROM on my Xperia ZR and it is working like a charm .
I've backed up my phone's TA partition just in case something goes wrong and I need to re-lock it and give it for servicing .
@ Grim_ripper: Is your bootloader already unlocked ?
@ su1979: You're welcome, glad I helped !
su1979 said:
I've backed up my phone's TA partition just in case something goes wrong and I need to re-lock it and give it for servicing .
Click to expand...
Click to collapse
I did the same ^^
thanks!! I'm testing !
Is it possible to re-lock the BL if I didn't do any TA backup before?
awwer2002 said:
thanks!! I'm testing !
Is it possible to re-lock the BL if I didn't do any TA backup before?
Click to expand...
Click to collapse
Hello,
No, not possible for the moment. For other devices such as the Xperia Z we can relock the bootloader by flashing a .ftf but without recovering the drm.
The backup and restore tool is the better way to reloock but it needs a backup before you unlock the BL.
I cant acces to the recovery mode even i press vol+ when i see the green light
Did i do something wrong？
The device is working good so far by this rooting method.
I just want the recovery mode back:cyclops:
Sorry for my bad english
awwer2002 said:
I cant acces to the recovery mode even i press vol+ when i see the green light
Did i do something wrong？
The device is working good so far by this rooting method.
I just want the recovery mode back:cyclops:
Sorry for my bad english
Click to expand...
Click to collapse
Green light? weird. Do the cyanogenmod logo displays at boot?
awwer2002 said:
I cant acces to the recovery mode even i press vol+ when i see the green light
Did i do something wrong？
The device is working good so far by this rooting method.
I just want the recovery mode back:cyclops:
Sorry for my bad english
Click to expand...
Click to collapse
If "select kernel to flash" says something like
"writing 'boot'...
FAILED (remote: Command not allowed)"
It means your bootloader is not unlocked yet.
NeoJeo said:
Green light? weird. Do the cyanogenmod logo displays at boot?
Click to expand...
Click to collapse
oh, I mean after I flashed back the stock kernel.
sorry I am new to android
---------- Post added at 09:50 PM ---------- Previous post was at 09:47 PM ----------
NeoJeo said:
Green light? weird. Do the cyanogenmod logo displays at boot?
Click to expand...
Click to collapse
gspbeetle said:
If "select kernel to flash" says something like
"writing 'boot'...
FAILED (remote: Command not allowed)"
It means your bootloader is not unlocked yet.
Click to expand...
Click to collapse
I am sure the BL is unlocked already as I flashed CM10.1 before.
anyway, Thanks for your advise
Edit: Use PRFCreated method for lollipop 5.0.2->5.1.1
Edit: For windows 8/10, you need to enable test mode for S1Boot fastboot driver install, you can also sign it with Zadig afterwards and turn off test mode.
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
(reboot)
Thanks NeoJeo for the method!
For some reason, my friend's new machine have to use flashtool to create a ftf backup first after updating the official firmware . Using other kernels will fail and creates a bootloop. (Maybe carrier locked? No idea.)
Bootloop can be solved by re-flashing the stock firmware completely and redo all the steps again, so its quite safe.
Stock roms:
You can always download the latest with firmware with xperifirm.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
HK stock roms seem to be less bloated.
Old roms for research purpose:
C5503_10.1.1.A.1.310 (HK) (4.1.2)
https://docs.google.com/file/d/0B-WWAl17NsavUWJRZldCZVdpNTQ/edit?pli=1
* (Doomlord rooter for this rom:
http://forum.xda-developers.com/showthread.php?t=2327472)
Pre-rooted 10.4.B.0.569 (4.3.0) rom by Sijav:
http://forum.xda-developers.com/showthread.php?t=2590174
C5503_10.5.A.0.230 (HK) (4.4.2)
https://www.dropbox.com/s/phqyx3awwpjr1ab/C5503_10.5.A.0.230_Generic HK.rar
C5503_10.5.A.0.230 (NORDIC) (4.4.2):
http://forum.xda-developers.com/showthread.php?t=2774540
C5503_10.6.A.0.454 (HK) (5.0.2):
https://drive.google.com/file/d/0B7l5nu0bqYuGWUk3WkpQbm9EQm8/view?usp=sharing
Tools:
Flashtool:
http://flashtool.net/download.html
(Remember to install drivers as well from C:\Flashtool\drivers)
Backup TA:
http://forum.xda-developers.com/showthread.php?t=2292598
or https://www.dropbox.com/s/xjm6t08xy946lee/Backup-TA-9.10.zip
SDK Platfom tools:
http://developer.android.com/
or https://www.dropbox.com/s/lgs2m90p1et87hx/platform-tools.7z
Super SU zip install:
http://download.chainfire.eu/supersu
or
https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Boot.img:
http://forum.xda-developers.com/showthread.php?t=2774540
or
https://www.dropbox.com/s/0n62ripm00u4z78/boot_v8.img
UPDATE FOR 5.0.2, new boot.img:
(ref: http://forum.xda-developers.com/xperia-zr/general/c5502-unlock-bootloader-rom-c5502stock5-t3115901)
https://drive.google.com/file/d/0B7l5nu0bqYuGX19QcUl5VWdKOXc/view
Step by step reference for my friends:
1. download & install flashtool http://flashtool.net/download.html
^if doesnt work, then try https://www.dropbox.com/s/xyk493qa8psydrf/flashtool-0.9.13.0-windows.exe
2. install flashmode and fastboot drivers from C:\Flashtool\drivers
3. plugin your phone, make sure settings->security->unknown source and settings->developer options->usb debugging is checked at all times
(if cant find developer options, go to settings->about phone->build number, keep tapping build number to see what happens)
4. - If your already phone upgraded, then:
4.1 If you want to keep your current kernel for later use, see: http://forum.xda-developers.com/showthread.php?t=2334653)
4.2 download 31x kernel (4.1.2) from http://forum.xda-developers.com/showthread.php?t=2384512
4.3 save it to \Flashtool\firmwares
4.4 open FlashTool.exe, click Flash device -> Flashmode
^ to enter flashmode, either plugin usb without battery or plugin usb with Volume - while your phone is OFF
4.5 select the 31x kernel and downgrade
4.6 kill FlashTool.exe
5. download and run doomlord's rooter from http://forum.xda-developers.com/showthread.php?t=2327472
6. use task manager or cmd to kill adb.exe, if it is still running
- Now you have a rooted phone
7. download and run backup ta from http://forum.xda-developers.com/showthread.php?t=2292598 , keep the zip file for later use
- Backup TA only works with rooted rom
- If you want to use the latest andriod continue below:
7 download the latest firmware with xperifirm and bundle it with flashtool.
8. upgrade / flash your system to the latest version (see step 4, but use the latest firmware file instead)
9. get unlock key from http://unlockbootloader.sonymobile.com/unlock/step1
11. download andriod sdk from google and install http://developer.android.com/
12. open SDK manager, scroll down and check Google USB Driver then click install packages
^ if doesnt work, then try: https://www.dropbox.com/s/lgs2m90p1et87hx/platform-tools.7z
^ USB drivers is also avaible under flashtools/drivers
13. go to \sdk\platform-tools
(replace %key% below with the key from sony's email)
run fastboot.exe -i 0x0fce oem unlock 0x%key% in cmd
or create a plain text file and save it as a .bat with
Code:
fastboot.exe -i 0x0fce oem unlock 0x[B][I]%key%[/I][/B] [user=607132]@pause[/user]
^ If stuck at 'waiting for device', you can use flashtool.exe to enter 'fastboot mode via adb' (run Flashtool.exe -> Flash device -> fastbootmode
), then re-try the command above
^ while in fastboot mode, your phone screen is off and led is blue
- Now you bootloader is unlocked.
14. put this zip file into your external sd from http://download.chainfire.eu/supers...om/s/sy1vzzq9ygfvqvb/UPDATE-SuperSU-v2.01.zip
15. run Flashtool.exe -> Flash device -> fastbootmode
16. reboot into fastboot mode (via ADB)
17. after led turns blue, select kernel to flash and choose boot.img from http://www.mediafire.com/download/4bs9zy3z4sl1lvl/boot.img
^ if doesnt work, try: https://www.dropbox.com/s/y5is541wd5lck79/boot.img
18 click reboot device into system while pressing Volume +
- if LED does not turn purple at all, something must be wrong
- press Volume + as long as but NOT before the LED turn purple.
^ return to step 4 if needed, bootloader may be not properly unlocked.
19 select install zip -> choose zip from external sdcard
^ Volume+ - is up and down, Power is select
20 confirm
21 go to advance -> power off
22 remove battery and plugin usb to enter flash mode
^ Flashtool.exe should show the phone is connected in flash mode
^ But there seems to be a time limit where CM 10.1 remount itself automatically with the wired blue thing popping up and then crash
23 return to Flashtool.exe -> Flash device -> Flashmode
24 choose the .ftf either from the one in step 8 or the one you have downloaded
25 Uncheck anything on the "Wipe" colon
26 Check everything on the "Exclude" colon except "KERNEL"
^ You should now only have kernel.sin and loader.sin on the content colon
27 FLASH!
- if bootloop occurs, return to step 4 lol
^ alternatively you can just redo step 24, but this time "Wipe" everything and "Include" everything. If it boots, then jump right to step 14 and retry installing the zip
28 Install super su in google play
^ first boot may need battery in and usb removed
29 (optional) Re-run backup-ta to restore the zip from step 7 for Relocking bootloader (and check for rooted at the same time)
- if backup ta failed because of no su rights, return to step 4 lol
EDIT: do not re-lock bootloader if using the new img
EDIT:
Upgrading should keep your settings and stuff, unless something went wrong that you have to wipe data for a clean install.
Quick check list:
1. Most Important. Make sure you still have your bootloader backups.
Run Backup-TA to backup your current bootlocker if needed (new version here:http://forum.xda-developers.com/showthread.php?t=2292598). Backup-TA only works on rooted.
2. If you somehow lost it, re-obtain your unlock key from http://unlockbootloader.sonymobile.com/unlock/step1
3. Have your Flashtool and SDK ready (https://www.dropbox.com/s/xyk493qa8psydrf/flashtool-0.9.13.0-windows.exe, https://www.dropbox.com/s/lgs2m90p1et87hx/platform-tools.7z)
4. If you need the stock firmware from your carrier, remember to clear contents in something like: C:\ProgramData\Sony Ericsson\Update Engine\db\13740270\blob_fs and/or C:\ProgramData\Sony Mobile\Update Engine\db\13740270\blob_fs (or something similar in %appdata% for windows XP)
5. You can use any ADB backup tool or Sony Companion to backup your settings, best timing is right after OS update but before rooting.
To do:
1. Either upgrade with Sony Companion and use Flashtool -> SEUS Decrypt, or download by XperiFirm to create your own firmware (Will take a while to load depending on the power level of your PC.)
or just use the firmware people uploaded
2. open Flashtool.exe -> Flash device -> fastbootmode
3. reboot into fastboot mode (via ADB)
4. Unlock you bootlocker by running "fastboot.exe -i 0x0fce oem unlock 0x%key%" (%key% is your unlock key from Sony's email)
^ (Last time I checked, some people say they need to update SDK first.)
^ (unlock key may change after new firmware is flashed)
^ you need to enter fastboot mode via ADB first, or it will get stuck at 'waiting for device'
5. select kernel to flash and choose boot.img
6. click reboot device into system while pressing Volume + (press Volume + after the LED turn purple)
7. select install zip -> choose zip from external sdcard -> your-su-zip-file (http://download.chainfire.eu/supersu)
^ 'Volume+' 'Volume-' and 'Power'.
8. go to advance -> power off
^ If you get a boot loop, simply remove battery and plugin usb cable to enter flashmode and re-flash the new firmware again.
^ remember to re-enable "Usb debugging" under "Developer options"
^ tap "About phone" -> "Build number" 10 times to unlock "Developer options"
[/hide]
Thanks this works great but I am unable to successfully install a recovery with this method. Has anyone had the same issues??
Sent from my C5503 using xda app-developers app
Hello,
@awwer2002: After you succeed rooting the device did you install any recovery ? If yes, which one ?
@gmengass: Which recovery are you trying to install ?
Hi,
After updating my phone to Kitkat, i was trying to get a custom recovery and root. I have read few posts and i am confused. I see there are 2 options to keep the stock kernel, but to have a custom recovery. 1. Doom and second is Nut. I am unable to extract the boot file from Doom's kernel so cant flash it and for Nut's method i need a recovery.
So is there a way to get a custom recovery (stock kernel) and root for a unlocked z1 c6902 KK?
Flash doom stock advanced kernel, there is no need to extract anything.
Download it and flash in fastboot.
gregbradley said:
Flash doom stock advanced kernel, there is no need to extract anything.
Download it and flash in fastboot.
Click to expand...
Click to collapse
Are you referring to this one?
ravi_buz said:
Hi,
After updating my phone to Kitkat, i was trying to get a custom recovery and root. I have read few posts and i am confused. I see there are 2 options to keep the stock kernel, but to have a custom recovery. 1. Doom and second is Nut. I am unable to extract the boot file from Doom's kernel so cant flash it and for Nut's method i need a recovery.
So is there a way to get a custom recovery (stock kernel) and root for a unlocked z1 c6902 KK?
Click to expand...
Click to collapse
Just download doomlords latest kernel and install using latest flashtool 9.15 I think. Flash in fastboot mode no need for typing and risking a chance of typing something wrong.
Sent from my C6903 using XDA Premium 4 mobile app
RealiableCandy4 said:
Just download doomlords latest kernel and install using latest flashtool 9.15 I think. Flash in fastboot mode no need for typing and risking a chance of typing something wrong.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As per instrucion in that page, you need to flash his kernel via recovery (i dont have one yet). Or you need to extract the boot.img and flash which i want to do but cant do as i am unable to extract the file.
Edit- Just saw gregbradley's reply in doom's post. it worked.
ravi_buz said:
Are you referring to this one?
Click to expand...
Click to collapse
Hi Ravi
Yes, the file you link is correct.
to install the img,
try this, it worked for me.
If you have flashtool (9.15) recommended. Place the img file inside the folder called Flashtool\x10flasher_lib.
In my case I renamed it to boot.img (not sure if it would work without renaming, didn't want to take that risk)
then, go into command prompt. Change to the folder mentioned above. example: cd "c:\Flashtool\x10flasher_lib"
turn off your phone and disconnect USB.
type the following and press enter.
fastboot flash boot boot.img
which will then say < waiting for device >
at this stage, hold the volume up, and connect the USB cable. This will boot your phone is fastboot mode and will allow fastboot to flash the boot image you indicate above.
when it says finished. you're done. Just disconnect the USB cable and boot your phone.
Hope this helps.
silverfox013 said:
Hi Ravi
Yes, the file you link is correct.
to install the img,
try this, it worked for me.
If you have flashtool (9.15) recommended. Place the img file inside the folder called Flashtool\x10flasher_lib.
In my case I renamed it to boot.img (not sure if it would work without renaming, didn't want to take that risk)
then, go into command prompt. Change to the folder mentioned above. example: cd "c:\Flashtool\x10flasher_lib"
turn off your phone and disconnect USB.
type the following and press enter.
fastboot flash boot boot.img
which will then say < waiting for device >
at this stage, hold the volume up, and connect the USB cable. This will boot your phone is fastboot mode and will allow fastboot to flash the boot image you indicate above.
when it says finished. you're done. Just disconnect the USB cable and boot your phone.
Hope this helps.
Click to expand...
Click to collapse
Yup, this file worked for me, instead of flash tool i used adb. I think the confusion is because the post by doom asks us to flash it using recovery or extract just the boot file. I think he needs to update the post as you just have to flash this via flashtool or adb.
ravi_buz said:
As per instrucion in that page, you need to flash his kernel via recovery (i dont have one yet). Or you need to extract the boot.img and flash which i want to do but cant do as i am unable to extract the file.
Edit- Just saw gregbradley's reply in doom's post. it worked.
Click to expand...
Click to collapse
They are two ways of flashing a the kernal. the latest one can only be installed using flashtool or fastboot unless you replace the boot.img in the zip folder for "Advance Stock Kernel with Recovery v01 (FW:14.2.A.1.136) {RECOVERY FLASHABLE}".
Since you dont have a recovery i recommend you use flashtool(latest one) (fastboot might be a headache since install deals with driver if you habe windows and android sdk).
To do this you need to:
1.Open flashtool
2.Turn phone off then go to fastboot mode (connect usb while phone is off and holding volume up button BLUE LED should show once connected)
3. Click on lightning icon
4.Select "Fastboot mode"
5. click "select kernal to flash"
6. locate the .img image you downloaded (you might have to change the selection thing on the bottom from *.sin to *.img)
7. Click and it will auto install.
ravi_buz said:
Yup, this file worked for me, instead of flash tool i used adb. I think the confusion is because the post by doom asks us to flash it using recovery or extract just the boot file. I think he needs to update the post as you just have to flash this via flashtool or adb.
Click to expand...
Click to collapse
By adb do you mean using the fast boot command... Well that what he means by flashing worth fast boot....
Sent from my C6903 using XDA Premium 4 mobile app
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
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:
So, I have decided on rooting my Xperia Z3 Compact so that I can finally move OBB to SD card, however I have no knowledge of how roots work (not a programmer much), or which one to pick. I have seen quite a few options for different roots, and previously used Kingo root, but seeing the post about it I am avoiding it like a forest fire. Anyone got good suggestions on which one to pick for my Xperia z3 compact?
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
GarrusN7 said:
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
Click to expand...
Click to collapse
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
dev.kasibhatla said:
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
Click to expand...
Click to collapse
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
GarrusN7 said:
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
Click to expand...
Click to collapse
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the mazimum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Thanks. Tho I am sure once I get hands on to it, I will know what to do. Can't wait to move those damned OBB Xd
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
fab_ben said:
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
What he/she says. Sorry, I totally forgot about that method, it's much easier, thank you!
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Well ****....my root doesn't work. I am using SuperSu and TWRP but for some reason a ram disk extraction fails and no install...is it because I have systemless version of my phone or whatever keeps popping up???? And how do I fix that crap???
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
GarrusN7 said:
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
Click to expand...
Click to collapse
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
dev.kasibhatla said:
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
Click to expand...
Click to collapse
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
GarrusN7 said:
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
Click to expand...
Click to collapse
Here's a link from another post. Follow it and check. It should work.
(you've already performed a few of those steps)
link