Develop Bugs

A few qiestions about rooting

Hello everyone, im really mew to rooting.
I have the T Mob M8 with 5.0.1, i was planning on rooting but will I be able to update nprmally wjen 5.1 comes out? If so how?
Also whats tje easiest method to root this phone? Ive seen apks like framaroot that root the phone extremely quick and easy...is there something similar for this phone?
Thanks in advance
Sent from my HTC One_M8 using XDA Free mobile app

Root by unlocking the bootloader via HTCDev.com and then just install custom recovery and flash current (2.56) SuperSU zip.
One click root solutions won't work with a locked bootloader. Unlocking the bootloader is really the key.
Once rooted, you can OTA. But you need to have stock ROM (nothing altered in /system partition) and you need to re-install stock recovery. Root is okay (although you will likely lose root) and unlocked bootloader is okay to OTA. To root again after an OTA, just install custom recovery and flash SuperSU again.

Thanks a lot. I will unlock the bootloader and can you link me to a good tutorial or guide on how to install custom recovery and supersu?
Thanks again
Sent from my HTC One_M8 using XDA Free mobile app

Red_Gh0st said:
Thanks a lot. I will unlock the bootloader and can you link me to a good tutorial or guide on how to install custom recovery and supersu?
Click to expand...
Click to collapse
The following guide is a pretty good one: http://forum.xda-developers.com/showthread.php?t=2799796
Although some links are outdated:
1) Installing HTCSync should be fine to get the HTC drivers on your computer; or you can search XDA for more recent HTC drivers. The HTC drivers linked in the guide are really old.
2) Get the latest SuperSU zip here: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3) And if you need an easy adb/fastboot installer, just use the XDA seach function with the phrase "simple adb" and you will get a few results for beginner adb guides and installers.
4) Get the latest version of TWRP here: http://techerrata.com/browse/twrp2/m8

redpoint73 said:
The following guide is a pretty good one: http://forum.xda-developers.com/showthread.php?t=2799796
Although some links are outdated:
1) Installing HTCSync should be fine to get the HTC drivers on your computer; or you can search XDA for more recent HTC drivers. The HTC drivers linked in the guide are really old.
2) Get the latest SuperSU zip here: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3) And if you need an easy adb/fastboot installer, just use the XDA seach function with the phrase "simple adb" and you will get a few results for beginner adb guides and installers.
4) Get the latest version of TWRP here: http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
hello I saw your post Im planning also to root my m8 but I dont want to flash the custom recovery someone told me it is possible
just download the custom recovery
then type "fastboot boot recovery.img" = this will boot my m8 to custom recovery but not flash so I can flash the supersu in that custom recovery then reboot after that stock recovery is still intact

imfuzzyyy said:
hello I saw your post Im planning also to root my m8 but I dont want to flash the custom recovery someone told me it is possible
just download the custom recovery
then type "fastboot boot recovery.img" = this will boot my m8 to custom recovery but not flash so I can flash the supersu in that custom recovery then reboot after that stock recovery is still intact
Click to expand...
Click to collapse
That's true, you can boot TWRP remotely with fastboot, without actually flashing it (installing to the phone).
Although its slightly irrelevant; you can always flash back to stock recovery back to the phone (over-write TWRP). You can either find your stock recovery posted in the collection; or back it up your self using the fastboot TWRP trick (fastboot boot TWRP, and use TWRP to backup stock recovery). In that instance, the fastboot boot TWRP trick is very useful.
Having TWRP installed after root is very useful. Reason being, it gives you a lot more recovery options if things go south. And also, for a lot of mods done under root, you will want to backup your stock setup anyway (just in case the mod goes wrong, and you need to revert). Stock recovery is close to useless for anything but installing OTA updates.

redpoint73 said:
That's true, you can boot TWRP remotely with fastboot, without actually flashing it (installing to the phone).
Although its slightly irrelevant; you can always flash back to stock recovery back to the phone (over-write TWRP). You can either find your stock recovery posted in the collection; or back it up your self using the fastboot TWRP trick (fastboot boot TWRP, and use TWRP to backup stock recovery). In that instance, the fastboot boot TWRP trick is very useful.
Having TWRP installed after root is very useful. Reason being, it gives you a lot more recovery options if things go south. And also, for a lot of mods done under root, you will want to backup your stock setup anyway (just in case the mod goes wrong, and you need to revert). Stock recovery is close to useless for anything but installing OTA updates.
Click to expand...
Click to collapse
woah didnt know that I can back up the stock recovery by fastboot boot in TWRP BTW if I'm using this phone I will probably use a TWRP but its my gf who uses it so she just need the root access for xmod app because she is an coc adik haha and she doesnt know about modding its system, thanks for this wonderful information
---------- Post added at 01:33 AM ---------- Previous post was at 01:13 AM ----------
hello I need your help this m8 is previously rooted have supersu installed then take OTA before now it is not rooted but the supersu still intact on my apps, I fastboot boot twrp.img then went smoothly flash the supersu.zip but Im still unrooted any suggestion? it say on root checker the root access is not properly installed
update: sorry got root now I flashed the 1.94.zip which is very outdated didnt notice it flashed the latest 2.46.zip now its rooted thank you so much!

Hello I finally started downloading everything to get started. I start the process to unlock the bootloader but when i get to the part i need to type "fastoboom oem....." On cmd I get an error saying Adbwinapi.dll is missing try reinstalling the program.
What can I do to fix this?
Sent from my HTC One_M8 using XDA Free mobile app

Red_Gh0st said:
On cmd I get an error saying Adbwinapi.dll is missing try reinstalling the program.
Click to expand...
Click to collapse
Is HTC Sync installed? If so, re-install it.

Reinstalled but it still says tht file is missing from my conputer
Sent from my HTC One_M8 using XDA Free mobile app

Red_Gh0st said:
Reinstalled but it still says tht file is missing from my conputer
Click to expand...
Click to collapse
Try a different adb installer.

Thanks a lot I unlocked my bootloader and rooted my phone

How Autorec works

Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.

Simone98RC said:
Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.
Click to expand...
Click to collapse
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have

RapHaeL_4_4_4_ said:
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have
Click to expand...
Click to collapse
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?

Simone98RC said:
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?
Click to expand...
Click to collapse
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.

If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone

ypsmav said:
If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone
Click to expand...
Click to collapse
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
RapHaeL_4_4_4_ said:
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.
Click to expand...
Click to collapse
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?

Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone

ypsmav said:
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone
Click to expand...
Click to collapse
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
RapHaeL_4_4_4_ said:
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Click to expand...
Click to collapse
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.

Simone98RC said:
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.
Click to expand...
Click to collapse
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.

NatusVincere said:
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.
Click to expand...
Click to collapse
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid who won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).

Simone98RC said:
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid which won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).
Click to expand...
Click to collapse
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one

bender_007 said:
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one
Click to expand...
Click to collapse
Thanks much for the specification: since I want to flash a firmware newer than 20H, I need latest Autorec to work with that [emoji106]
https://www.androidfilehost.com/?fid=24052804347817962
After all you are the official Autorec developer

^ yap, flash safely, after that flash fulmics
That's how I was using it
Plus thx to all people involved in here for answering and helping out
Poslano sa mog LG-H815 koristeći Tapatalk

Recovery after 6.0

Hey all,
Trying to get my TWRP recovery back after upgrading to M.
Flashed recovery a number of different ways but always end up back at the stock recovery after flashing. I've tried going straight into it before rebooting etc with no luck.
Any ideas?
Thanks

Basttrax said:
Hey all,
Trying to get my TWRP recovery back after upgrading to M.
Flashed recovery a number of different ways but always end up back at the stock recovery after flashing. I've tried going straight into it before rebooting etc with no luck.
Any ideas?
Thanks
Click to expand...
Click to collapse
if your trying to flash recovery from your LP to get back to old back-ups in LP - you have to downgrade to LP first
There is only a recovery for flashing a patched SU / boot to give you root in MM.

Thanks for the reply.
Not trying to get back to LP backups. Just trying to get TWRP back on the phone again.

Basttrax said:
Thanks for the reply.
Not trying to get back to LP backups. Just trying to get TWRP back on the phone again.
Click to expand...
Click to collapse
To flash twrp recovery, your bootloader needs to be unlocked. For now, there's no way to unlock the bootloader on MM. The only option is to downgrade to LP if you need twrp or customs roms.
I hope you understand my explanations.

Basttrax said:
Thanks for the reply.
Not trying to get back to LP backups. Just trying to get TWRP back on the phone again.
Click to expand...
Click to collapse
this will work as a temporary recovery and you will be able to install SU and Xposed.
Here:
http://forum.xda-developers.com/showthread.php?t=3404321
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. Do it at your risk and I won't be able to answer your questions.
3. There is no unlock for Android 6.0 atm. Device will be locked once you upgrade to 6.0.
4. Good thing is you can always downgrade to Lollipop to unlock your device following the instructions in this thread.
5. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0. If you upgrade to 6.0 from locked Lollipop, you have to downgrade to unlock it, then upgrade to 6.0.
2. Once you are in Android 6.0, fire the following command to boot twrp. is the twrp recovery file. This TWRP is recommended.
adb reboot-bootloader
fastboot boot
Click to expand...
Click to collapse
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade:
Refer to Asus Zentalk Forum and grab the required files from there.
**Note that the first commnad line has been revised by @shakalaca and it should work without bricking the device.
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Then you can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!
Sent from my ASUS_Z00AD using XDA-Developers mobile app

Can I install CWM via the fastboot command?

I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.

Fiksdal said:
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Click to expand...
Click to collapse
Worth checking general section
http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748
http://forum.xda-developers.com/zenfone2/development/z00az008-zenfone-2-t3265236

Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works

Fiksdal said:
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Click to expand...
Click to collapse
Tip
It is always worth googling
and put an XDA on the end

timbernot said:
Tip
It is always worth googling
and put an XDA on the end
Click to expand...
Click to collapse
Haha, you know, I had been struggling with this problem for like 2 days. So many hours on the computer and Google trying to figure it out. I was trying to get the scripts to work, then CWM, then TWRP. I was just really confused and didn't know how to do it since most guides on Google said I had to use the scripts for Windows. Then finally I realized that it was as simple as using fastboot from OS X Anyway, sorry to bother you guys. But Everything is working now, root, Xposed and permanent TWRP. Awesome

Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip

timbernot said:
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
Click to expand...
Click to collapse
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again

Fiksdal said:
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Click to expand...
Click to collapse
You are doing great now :victory:

Best way to root,unlock BL and install custom recovery

I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one

bolcna said:
I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6

levone1 said:
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6
Click to expand...
Click to collapse
Do i have to be rooted to backup TA partition

bolcna said:
Do i have to be rooted to backup TA partition
Click to expand...
Click to collapse
I don't think so. Just need adb...

I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
You don't have to downgrade to flash NUT. It's been a while since I did it, but I'm pretty sure that flashing supersu won't totally remove Kingroot. Best thing to do once you're rooted, if you don't want to unlock bl, is probably to install recovery, then in recovery flash a prf, which will wipe your system and install new system with supersu instead of Kingroot.

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
bolcna said:
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps
Click to expand...
Click to collapse
I would go with unlock bl method. You can restore TA after rooting so you done lose drm, and it's easy to root with unlocked bl - https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6