Hi!
Somebody in a different forum suggested that it might be possible to root the latest firmware (23.0.1.A.0.167) by downgrading the kernel (http://forum.xda-developers.com/showpost.php?p=56590546&postcount=1224).
Can anybody confirm this method to work?
I purchased my Z2 tablet yesterday and was foolish enough to believe that I can upgrade to the latest firmware and still root my device (with a locked bootloader).
Greetings
MJFox
MJFox78 said:
Hi!
Somebody in a different forum suggested that it might be possible to root the latest firmware (23.0.1.A.0.167) by downgrading the kernel (http://forum.xda-developers.com/showpost.php?p=56590546&postcount=1224).
Can anybody confirm this method to work?
I purchased my Z2 tablet yesterday and was foolish enough to believe that I can upgrade to the latest firmware and still root my device (with a locked bootloader).
Greetings
MJFox
Click to expand...
Click to collapse
It doesn't work. You end up to bootloop. However you can flash prerooted firmware in custom recovery and have fully rooted device.
kulvertti said:
It doesn't work. You end up to bootloop. However you can flash prerooted firmware in custom recovery and have fully rooted device.
Click to expand...
Click to collapse
In order to do so I have to unlock my bootloader and with that I'm going to lose my drm keys, right?
MJFox78 said:
In order to do so I have to unlock my bootloader and with that I'm going to lose my drm keys, right?
Click to expand...
Click to collapse
No. If you easy root and install the dual recovery beforehand you flash from that.
But easy root doesn't seem to work with the latest firmware, they closed the vulnerability that easy root is using
MJFox78 said:
But easy root doesn't seem to work with the latest firmware, they closed the vulnerability that easy root is using
Click to expand...
Click to collapse
Easy Root Tool works just fine with .314 firmware. So if you are now on latest .167 firmware, downgrade to .314, root it, install custom recovery and flash prerooted flashable.zip in custom recovery. Done.
kulvertti said:
Easy Root Tool works just fine with .314 firmware. So if you are now on latest .167 firmware, downgrade to .314, root it, install custom recovery and flash prerooted flashable.zip in custom recovery. Done.
Click to expand...
Click to collapse
Ah, I didn't know it's possible to downgrade the firmware
So I need the firmware flash tool and a ftf file of the 167 firmware, right?
And it can be done without root and a locked bootloader?
Sorry for all the newbie questions, I'm coming from HTC devices and it's a little different there
Greetings
MJFox
MJFox78 said:
Ah, I didn't know it's possible to downgrade the firmware
So I need the firmware flash tool and a ftf file of the 167 firmware, right?
And it can be done without root and a locked bootloader?
Sorry for all the newbie questions, I'm coming from HTC devices and it's a little different there
Greetings
MJFox
Click to expand...
Click to collapse
You need:
- latest Flashtool with drivers installed correctly for your device
- some working custom recovery
- Easy root tool
- ftf file you need is 314 firmware of you device where you have to downgrade to easily root it
- prerooted zip file included you device 167 firmware, SuperSu install files and latest dualrecovery install files.
You don´t need unlocked bootloader for this. Point of downgrading is to achieve root easily that you can have root with 167 firmware? Or do you mean that can you achieve root on 314 firmware without having it before? If so, yes you can with Easy root tool.
kulvertti said:
You need:
- latest Flashtool with drivers installed correctly for your device
- some working custom recovery
- Easy root tool
- ftf file you need is 314 firmware of you device where you have to downgrade to easily root it
- prerooted zip file included you device 167 firmware, SuperSu install files and latest dualrecovery install files.
You don´t need unlocked bootloader for this. Point of downgrading is to achieve root easily that you can have root with 167 firmware? Or do you mean that can you achieve root on 314 firmware without having it before? If so, yes you can with Easy root tool.
Click to expand...
Click to collapse
thanks for your efforts!
in the meantime I managed to downgrade the firmware to 314, successfully root and backup TA
I installed superSU from the play store and it is telling me that I need to update the binaries and I can choose between "normal" (which doesn't work) or through "twrp/cwm"
I didn't install any custom recovery yet, so I'm not sure how to move on from now
should I install dual recovery (from here: http://forum.xda-developers.com/showthread.php?t=2785598), after flash the latest supersu from recovery and finally flash prerooted zip file?
do I need custom recovery to flash the prerooted 167 firmware?
or should I just run the OTA to get 167 firmware (will the device still be rooted after the update)?
please advice
MJFox
MJFox78 said:
thanks for your efforts!
in the meantime I managed to downgrade the firmware to 314, successfully root and backup TA
superSU is telling me that I need to update the binaries and I can choose between "normal" (which doesn't work) or through "twrp/cwm"
I didn't install any custom recovery yet, so I'm not sure how to move on from now
should I install dual recovery (from here: http://forum.xda-developers.com/showthread.php?t=2785598), after flash the latest supersu from recovery and finally flash prerooted zip file?
or should I just run the OTA to get 167?
please advice
MJFox
Click to expand...
Click to collapse
Good to here you achievment. If you can´t update SuperSu binaries by "normal" way easiest might be to flash SuperSu latest update from custom recovery. I recommend dual recovery from your link and when installed use TWRP.
So install dualrecovery, flash latest SuperSu and then prerooted zip. If you end up without write permissions to system here might be solution for that.
http://forum.xda-developers.com/showpost.php?p=56616135&postcount=52
kulvertti said:
Good to here you achievment. If you can´t update SuperSu binaries by "normal" way easiest might be to flash SuperSu latest update from custom recovery. I recommend dual recovery from your link and when installed use TWRP.
So install dualrecovery, flash latest SuperSu and then prerooted zip. If you end up without write permissions to system here might be solution for that.
http://forum.xda-developers.com/showpost.php?p=56616135&postcount=52
Click to expand...
Click to collapse
I installed dual recovery and flashed your prerooted zip from the other thread - everything works perfect, thanks a lot for your efforts! :good:
greetings
MJFox
Does downgrading to 4.4.2 (and unbranding) will wipe TA partition (DRM)?
And I need do unlock my bootloader to downgrade firmware with flashtool?
andorid1 said:
Does downgrading to 4.4.2 (and unbranding) will wipe TA partition (DRM)?
And I need do unlock my bootloader to downgrade firmware with flashtool?
Click to expand...
Click to collapse
Unlocking your bootloader wipes your TA permanently
Not required to flash a new firmware using flashtool
Hi,
i upgraded to the latest Build 23.0.1.A.0.167 and lost root. I have done a TA partition backup on Version EURO-LTE_17.1.A.2.36.
My question is: If i flash a rootable ftf file with flashtool now, how is the TA partition affected? Could i proceed without losing the TA partions DRM information? Or should i restore the TA partition backup afterwards?
My plan is to downgrade via flashtool and a rootable ftf file. Apply root and upgrade to the latest firmware via recovery.
Thx in advance.
Solved. I didn`t know that as long as your bootloader is locked, the TA partition isn't affected.
Hi guys,
a workmate has a htc one m8 and i flashed his device, but i had to read a lot of sh*t to understand how htc Roms for example work.
You need to flash the correct firmware to the ROM. (When you want a LP Rom, you need a LP Firmware from HTC).
Why is this not needed on sony devices? Is the firmware inside the ROM? I can freely flash from 4.4.2 to 5.0.1 to 5.1 and back to 4.4.4 without any problems.
Also we don't have any "radio roms" or "modems" i think?
How is this working at sony devices? Thanks for your answeres
1. xperias have something called drm keys which have some xperia functions work and also state your warrenty, unlocking your bootloader will wipe your drm keys (which are in your TA partition) and this will void your warrenty
2. xperias are quite easy
-unlock bootloader
-flash recovery
-flash kernel (thats supports fota (= recovery)
use that to flash any rom you want
or if you want to keep drm keys and all, downgrade, root, backup TA and upgrade and rooting just before
or if you want to keep it stock then downgrade, root and recovery then upgrade and flash root before upgrating recovery
So, I had my bootloader unlocked back when I was in kitkat (unsure whether I had version 4.4.2 or 4.4.4), but I had backed up my ta partition in case I wanted to relock the bootloader.
Fast forward to today, I am on lollipop (version 5.1.1) and I want to relock my bootloader. Note that I am on stock kernel.
Obviously enough, I have to restore my ta backup.
But I have some questions.
1)Do I have to downgrade to the android version the phone had when I took the ta backup, or I can simply flash the ta backup on my current android version?
2)During this procedure, does anything (such as data) get wiped?
3) Will I lose recovery during this procedure?
Mokiwipeout said:
So, I had my bootloader unlocked back when I was in kitkat (unsure whether I had version 4.4.2 or 4.4.4), but I had backed up my ta partition in case I wanted to relock the bootloader.
Fast forward to today, I am on lollipop (version 5.1.1) and I want to relock my bootloader. Note that I am on stock kernel.
Obviously enough, I have to restore my ta backup.
But I have some questions.
1)Do I have to downgrade to the android version the phone had when I took the ta backup, or I can simply flash the ta backup on my current android version?
2)During this procedure, does anything (such as data) get wiped?
3) Will I lose recovery during this procedure?
Click to expand...
Click to collapse
1. no
2. shouldent be
3. if you are using recovery for locked bootloader then no