Related
Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)
So today I managed to root my Z2
Following advice from o0 Matt 0o in another thread, I downgraded from 4.4.4 to 4.42 using flashtool, then using the rootkitXperia_20140719 install.bat the phone is now rooted (for some reason it would not find adb even though running adb from a cmd prompt worked!)
Anyway, now I am on 4.4.2 with root, if I upgrade back to stock 4.4.4 rom will I lose the root?
EDIT: I have installed dual recovery, is there a pre packaged rooted rom for:
Android 4.4.4
23.0.1.A.0.167
United Kingdom - 3 - 1281-2574
Click to expand...
Click to collapse
Dont really want to create a rooted package myself, the steps can be confusing
Thanks!
Since you have dual recovery on 4.4.2 you can use the pre-rooted package by niaboc79 (can be found in the Android Development section) or any pre-rooted stock based ROM based on 4.4.4. It is all down to your preference.
I doubt there will be a 3 branded pre-rooted package either.
Actually you're right I should just get one of those roms which is not branded which would look better anyway
One last thing what is the steps to backup ta partition? At some point I will unlock bootloader but don't want to lose the dry keys
Cheers
Ned_Flanders said:
Actually you're right I should just get one of those roms which is not branded which would look better anyway
One last thing what is the steps to backup ta partition? At some point I will unlock bootloader but don't want to lose the dry keys
Cheers
Click to expand...
Click to collapse
In the Sony cross device development section there is the backup TA tool, simply use that. Also, make sure to upload your backup to a cloud service or something like that, in case your hard drive goes kaput and you need it to relock your bootloader.
Please remember that unlocking the bootloader wipes the internal SD card (not the user one). Also, restoring the TA backup relocks the bootloader so make sure you are on a stock ROM and kernel when you restore the backup.
gamer649 said:
In the Sony cross device development section there is the backup TA tool, simply use that. Also, make sure to upload your backup to a cloud service or something like that, in case your hard drive goes kaput and you need it to relock your bootloader.
Please remember that unlocking the bootloader wipes the internal SD card (not the user one). Also, restoring the TA backup relocks the bootloader so make sure you are on a stock ROM and kernel when you restore the backup.
Click to expand...
Click to collapse
Cool thanks for the tips :good:
So I've been reading these forums for the last 3 or 4 hours and I seem to be in an endless loop. I'm hoping people can help me untangle this mess, and perhaps I can write this up for others to enjoy.
I just picked up a HDX 7" with 13.3.0.5 on it. I dont care about the stock software, my ultimate goal is to get CM12.1 running on it.
So I see this ROM is available...
http://forum.xda-developers.com/kin...ent/rom-cm-12-unofficial-apollo-thor-t3050199
So from previous ROMing I know I need to get TWRP installed to get that running. So I find this post...
http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
However, first step is to unlock the bootloader... so I find this...
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
That says the first step is to install the "vulnerable" 13.3.2.3 firmware. Ok great...
http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
That first step there is to install TWRP :/ Seems we have an infinite loop here. Can anyone explain the proper procedure for going from stock 13.3.0.5 to CM12.1 using these procedures?
TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.
derpadoodle said:
TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.
Click to expand...
Click to collapse
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).
Davey126 said:
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).
Click to expand...
Click to collapse
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image
insodus said:
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
Click to expand...
Click to collapse
The 13.3.2.3 bootloader update is quick and easy. This code remains on your device even with other roms. So yeah, you should apply the update.
insodus said:
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image
Click to expand...
Click to collapse
My preference is HDX toolkit as it avoids wifi, installs SuperSU and has other handy options. However, it is a tethered solution which can be a PiTA. Towelroot should work fine too; I have used both.
Although it involves little risk bootloader unlocking is not for the faint of heart. You can always flash CM11 after step #3 and play with that while researching the bootloader unlock procedure. A recent tutorial by travanx captures most of the steps in one post. You'll want to start about halfway down.
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
rajdude said:
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
Click to expand...
Click to collapse
The only reason to use that guide is to backup ta keys for whatever reason you'd want to do that.
If you're after root on stock ROM the single easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. Solid marshmallow with root goodies. Xpower has everything and is deodexed and ready for xposed framework.
just a little more clarification please?
civicsr2cool said:
.....easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. ......
Click to expand...
Click to collapse
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
rajdude said:
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
Click to expand...
Click to collapse
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
still a little confused
civicsr2cool said:
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
Click to expand...
Click to collapse
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my day job). In Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
rajdude said:
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my d Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
Click to expand...
Click to collapse
Android is Linux, to gain root in the ROM you have on your phone currently all you need is an unlocked bootloader to run SU, but then you'll be left with a phone that still needs a customized kernel to keep root and a DRM fix for the camera. Xpower 3.0 is that package.
You could really benefit from reading more. Google up on dm-verity and Sony Ric, and fastboot/adb for a little better understanding of what you're getting into without a pre compiled ROM. Messing around with any Android you'll have the majority of the same steps, unlock bootloader with fastboot, flash Supersu, customized kernel.. Etc
Why use a stable compiled ROM?
Let me list down and explain to you why it's best to use a stable compiled ROM. But first you need to understand these few things before you decide to unlock your bootloader and root.
Before Sony Z models kicked in, every rooted Sony device are still able to retain all the features that came together with the phone before it was rooted. When Sony introduce the first Z model, they start to create these things called DRM keys. DRM keys are unique algorithm (i guess i should put it that way) which is attached to every phone the same way an IMEI number is attached to every phone. In short, my DRM keys cannot be used on your phone and vice versa.
DRM key: It's a unique algorithm that holds all the unique features that an unrooted Sony phone boast such as camera quality, X-reality, High Res Audio etc etc.
The moment you unlock your bootloader, that's the moment your DRM keys will be lost. But don't panic, the wonderful devs on XDA have prepared a tool to backup your TA partition (a partition that contains your DRM key) for your own convenience if you want to relock your bootloader.
Then recently Sony/Android come up with new features called Sony RIC and dm-verity. (You may Google what these are all about but to my understanding it is placing limitations to people who root their phones to meddle around with the system settings of thier phone)
With all these "hurdles", it have taken some time for devs here to find a work around and like every fairytale ending, they manage to find a way.
Now you're wondering if you can actually root without flashing another rom. Good news for you: you can! There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting.
.. But ask yourself what's the point of going through the hassle of rooting and your phone is not tweaked for performance or for theming purposes?
That's when people flash roms and in Z5 compact's case, XPower is the best rom there is. It gives you all the performance tweak you need to make your phone lag free, it has a lite version that removes all the unnecessary system apps you can't delete without root, it gives you an option to add themes and framework from Xperia X with all those work around in place.
For your second question: why is there a need to install TWRP?
TWRP is a recovery tool which is a need for all rooted phone. It's also a tool for you to backup and restore your current rom so that you can rollback to the last working configuration if your phone went into a bootloop etc. Plus i believe all these guides require you to actually use TWRP to flash the SuperSU to successfully root your phone.
I hope this explains your doubts.
Thanks a lot but...
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
I think this is a pretty great thread rajdude. It's getting people to spell out a lot of information to noobs like us that it seems most posters have taken for granted over time.
I'm a complete novice at all of this. Sort of gleaning information as I go along, but I used this guide: http://twigstechtips.blogspot.hk/2016/04/sony-z5-compact-root-without-losing-ta.html?m=0
Along with this guide: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
The first guide is pretty basic step-by-step instructions. It unfortunately occasionally kind of skips over a couple very small things (that will be clear as you go along), or occasionally words things in such a way that might not be completely intuitive, but maybe that's cause I need things explained to me like I'm five sometimes. Any time I might have had a question about something in the the first guide, I went to the other and found the answer. It didn't take me long to get the gist of the whole thing though, and overall, it wasn't as scary as I thought it was going to be. It'd be fantastic if someone created a video walkthrough, but so far as I know, no one has done that yet.
The guide will help you back up your TA Partition where your DRM keys are stored, unlock your bootloader, root your device, and then restore your DRM keys. In order to do this you need to downgrade to Lollipop (if you're not already on it), and then upgrade back up to Marshmallow. It will also install TWRP (which I had no clue was installed until I went into "recovery mode" by pressing UP when I saw the LED flash yellow during boot). There may be an easier way to go about this whole process, but this is the process I used.
Before jumping into anything, I'd hold off until you heard more from firdyRAY or someone more experienced. They may look at the guide I linked and be horrified.
And yeah, I haven't installed xpower yet for the same reasons you haven't. Sounds like there's even an xpower 4.0 that was released recently, but still seems kinda buggy. Being rooted with stock I've been able to give Greenify access to root. Install Adaway (which was worth getting root to begin with). Install sound/music mods like DiVA-X, Viper4Android and Dolby Atmos. Install Titanium Backup. And make a few other minor tweaks (that I've since reversed). I still don't know much about custom ROMs and all that jazz, so I'm holding off until I get more understanding. I'd love to install the xpower ROM (when the bugs are worked out), and maybe some sort of sound ROM. I also need to get more understanding on some of the other vernacular like what exactly a "dirty flash" is.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
Click to expand...
Click to collapse
sony ric is a layer of security for sony roms so that they can protect nfc and fingerprint stuff. samsung and htc have there own variants as well.
yes lol the big red lettering is there to make you read, although hes not far off on the melting your phone part, the s810 is ridiculously hot.
the xpower thread doesnt not include the drm backup instructions because: 1) you need bootloader unlocked to flash it. and 2) because it includes the drm fix in it so you dont have to backup your ta keys.
the fingerprint sensor bug is on any bootloader unlocked phone, the hardware fails after x amount of hours and requires a reboot to work again. xpower is a stock rom, the only thing different is its pre-rooted, de-bloated, and deodexed for xposed to work. we have a separate thread for the fingerprint sensor bug and its been solved.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
Click to expand...
Click to collapse
Sony RIC main function is to disable /system write even you got root permission(you still able to do /system write but after a reboot will restore to original). There is a workaround but very trouble, TWRP recovery file manager can bypass Sony RIC(it works in the old day for me, not sure about now). BTW, all 3rd kernel should be disabled RIC nowadays. For any regular computer, there is no hardware or software lock to prevent you gain root access in linux but there are many such trouble stuffs in the android world... lol
I'm running XPower 3.0 Full as a daily driver since June and been very happy. Battery life, stability and speed is good.
Please note, that you MAY lose your warranty when you lose your DRM keys. That's why I didn't unlocked my phone before there was a way to backup TA partition. Now I'm after warranty repair, and before it I was able to fully restore stock ROM with DRM and all features fully functional. In my country, there is only one Sony approved repair center and they check DRM keys before repairing anything - even if it's mechanical fault.
When I had Z1c in KitKat days, it didn't had dm-verity and Sony RIC. It was possible to gain permanent root with bootloader locked, so I was happily using stock ROM and kernel. In Z5c case, first thing I tried was to do the same and it was possible (just backup TA, unlock bootloader, and flash TWRP with patched kernel (dm-verity and Sony RIC disabled) to begin with), but going XPower way was much more confident - I didn't had to think about removing every bloat app. I just flashed lite version in June and I'm using it till this day without any problems at all
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
michuroztocz said:
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
Click to expand...
Click to collapse
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
flopower1996 said:
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
Click to expand...
Click to collapse
That's just what I wrote - just put it in another words
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Gdhgeorge1 said:
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Click to expand...
Click to collapse
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Horst the Animal said:
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
Click to expand...
Click to collapse
Thanks for replying! Yeah, I assumed that would be the case. But I found this post that says I can flash a "drmrestore" zip package so I can simulate that the keys are still there: https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
The thing is, in order to flash it, I need TWRP recovery, right? I have been unable to successfully install TWRP. Is there an easy way to install it?
Thanks again!
harry_turtle said:
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Click to expand...
Click to collapse
Thanks a lot for replying! If I find this post where I can create my own kernel, I will have to unlock the bootloader again and flash the new custom firmware using flashtool, right?
Also, will I have to downgrade to Lollipop, since Nougat is pretty new on Sony phones and there's no drm fix for that?
Thanks again!
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Will try!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
Thank you so, so much! I will try this and report back with my results!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
I apologize for replying with my report this late.
It turns out I re-locked my bootloader in the process when I flashed Android Nougat, since I had bricked it temporarily. To do the procedure you mentioned above, I need to have it un-locked, correct?
If that is the case, when I try to unlock the bootloader, I cannot access fastboot because whenever I press VOL UP key with adb, the light flashes blue and then red and then boots into the OS normally. Same with flashmode (the light turns green, and then red, finally booting into the OS).
Does anyone have a solution for this, please?
Thank you very much!
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
Thank you for your reply, Dean F.
OEM unlocking option and USB debugging were already enabled. It should have technically been working by now. Could it have something to do with some drivers I have to re-install?
It worked!!
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Gdhgeorge1 said:
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Click to expand...
Click to collapse
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Dean F said:
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Click to expand...
Click to collapse
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Gdhgeorge1 said:
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Click to expand...
Click to collapse
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Dean F said:
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Click to expand...
Click to collapse
Excellent, I see now, thanks!
Well, what I wanted before starting the entire process was a permanent root solution, one that would allow me to access features like Root Explorer on ES File Explorer, or extra features in Link2SD and such, when the opportunity arose. That is what I did with all my previous smartphones, even a Sony Z1 Compact, but this has been the hardest phone to root I've ever handled.
After all the trial and error I've faced, I will take your good advice and leave it as is for now. In the future, I will flash the rooted kernel when I need to use those functions, and use the androplus kernel you had sent me previously to get it back to normal.
Thank a bunch again for all your help, Dean F. You revived my phone, so to speak!
Cheers!