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
Related
I'm about to get the DNA and was doing a lot of reading on S-Off/On, unlock, root and pretty much, I think, know what I need to do. But, not to f-up, would like some validation and corrections from you guys.
So, once I get the phone the very fist thing I will do is unlock as it will cause everything to be deleted, so no point in setting anything up. Correct?
Once unlocked, I can setup and use phone and root later, but I want to remove all the VZ crap, so, I'll probably root right away as well.
From here, how do I remove the bloatware as I want to stay stock and don't want install any 3-rd party kernels that allow system read-write while booted yet. I'm guessing that there are probably "unbloat" zip files that can be flashed via recovery, is that correct?
I haven't research custom recoveries yet, so wont ask but any volunteered information is welcome (which one, any issues to be aware of)
Thanks for your help.
CrazyRussianXDA said:
I'm about to get the DNA and was doing a lot of reading on S-Off/On, unlock, root and pretty much, I think, know what I need to do. But, not to f-up, would like some validation and corrections from you guys.
So, once I get the phone the very fist thing I will do is unlock as it will cause everything to be deleted, so no point in setting anything up. Correct?
Once unlocked, I can setup and use phone and root later, but I want to remove all the VZ crap, so, I'll probably root right away as well.
From here, how do I remove the bloatware as I want to stay stock and don't want install any 3-rd party kernels that allow system read-write while booted yet. I'm guessing that there are probably "unbloat" zip files that can be flashed via recovery, is that correct?
I haven't research custom recoveries yet, so wont ask but any volunteered information is welcome (which one, any issues to be aware of)
Thanks for your help.
Click to expand...
Click to collapse
You can't change any system permissions without being rooted. You will be stuck with anything that resides in system/app. There are some other methods that run an exploit without a permanent root for different phones, but HTC is very strict with what they allow. Alternatively, if you do plan to root and flash then you could use my simple guide for everything else: click here
You will have a lot more fun and better results with performance and battery if you do root and flash. With the simplicity we have now for unlocking this device you would be stupid not to go further
That was my sentiment exactly - root is required to do any modifications/bloatware removal. I might have not been clear when stated that after unlocking the bootloader I can use the phone and root later. I understand that until rooted no changes can be made to system.
Nice Full Gide you have written there, btw, uppon2.
If you delete bloatware while the phone is booted in android the changes won't stick unless you have a writeable kernel. You can use a script that will wipe the bloat in adb instead of flashing a writeable kernel.
I just bought a Z3CT(SGP612) and am a bit confused.
The first big question is about DRM key thing. Why do I care about them if I don't have any other Sony devices (Playstation etc.) and probably won't ever. I read in one thread that these keys may be non-recoverable, but in another thread it was said they could be saved and restored. What are the best practices for doing this?
Second, and I'm stuck here until this thread works, or further research surfaces the answer. I just bought this unit, it's brand new out of box. I'm probably the last man on earth to buy one, but....The device is nagging me to update, but I think that may end in tears. I'm afraid Sony official updates may render the device unrootable, or permanently lock the bootloader forcing me to beg Sony to do whatever I want to my own device. I think on 4.4.4 there is a way to unlock the bootloader without begging Sony to do it. The device is presently 4.4.4, build 23.0.1.A.0.167. The nagging update will take me to 23.0.1.A.3.12. I'm assuming there may be further updates beyond that to get to 23.4.xxxx. Should I accept this, and do any other updates, or proceed directly to one of the pre-rooted stock ftf files (sorry, what is ftf and acronym for?). I'd like to get to the latest 5.11 and have the ability to run adaway, make backups, have proper working SD card and USB OTG, and maybe run a few Xposed apps all of which mean I need root. As it's a virgin device I don't care about if I have to wipe the device in the process.
http://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
http://xperiafirmware.com/8-firmware/77-sony-xperia-z3-tablet-compact
as i´m in the same situation as you i will share my experience / research so far:
1. Rooting works on different firmware with different methods, kingroot being one rather easy but with the drawback of sending personal phone data to uncertain chinese servers. Rooting 4.4 seems easier than 5.x.
2. Research showed that the DRM keys / TA partition is something to be backed up, just in case. But for backing up you need root but no unlocked bootloader (unlocking erases the keys).
3. Recoveries can be installed without unlocking the bootloader but need root(?).
This is where im right now with my progress - rooted, TA/DRM keys backed up and on a custom recovery but bootloader still locked and TA intact .. getting root demanded some patience and several tries though.
4. next step will be installing a prerooted 5.1 firmware i guess and everything has to be running fine
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
francisci said:
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
Click to expand...
Click to collapse
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
madshark2009 said:
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
Click to expand...
Click to collapse
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
francisci said:
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
Click to expand...
Click to collapse
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
madshark2009 said:
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
Click to expand...
Click to collapse
Very helpful ! Thanks v much - I'll let you know if I succeed!
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
--jenana-- said:
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
Click to expand...
Click to collapse
Yah well if the bootloader is unlocked and the system has modification on it , they have every right to refuse fixing it for you because its hard to prove that what bricked the device isnt some modification that you made... Unless they have a really good heart , i had a z2 before and it was rooted but the ftf on it was custom but was on it for like 7 months and all the mods were working properly untill all of the sudden it wont turn on so they told me that what i.did caused it but i didnt do anything wrong i know they lying but can u prove it!? No..
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
francisci said:
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
Click to expand...
Click to collapse
first you gotta download ADB folder
you can find it here if im not wrong : http://forum.xda-developers.com/showthread.php?t=2588979
then place the adb folder in C:\
I think it automatically place it there when installing so no need to do that if so
2. go to cmd (start - type in CMD) and once it launches direct it to where the adb folder is "cd c:\adb" without the quotes of course
3. to flash boot type in "fastboot flash boot boot.img" without quotes and one space step between words only.
4. to flash recovert just type is "fastboot flash recovery "recovery name".img wihtout the quotes and copy recovery name exactly the way it is.
that it
keep in mind that any time you want to flash any thing , that thing must be inside the adb folder for example ,boot.img file must be there in the adb folder with all the other files when installing adb, and also recovery and every other thing you want to flash using fastboot.
hope this is helpful.
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
francisci said:
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
Click to expand...
Click to collapse
well youre new, mistakes like these happen Ive been there, sorry for the late reply XDA isnt giving me notification
any way, make sure after backup TA (which is on lolipop firmware) you gotta get back to original .305 firmware (MM) the process of you getting back to lolipop in the first place is so you can use Ivoyroot tool for temporary root so you can backup your TA partition, once that is done you must get back to .305 because you are flashing a kernel (boot.img) that is for build .305 I guess the guide guy didnt mention this?
second when I said copy recovery name as it is I meant what recovery name you have for example
fastboot flash recovery twrp-3.0.2-0-E5823-20160417.img
thats my recovery name the one that I downloaded, yours might say some thing else its OK I meant copy YOUR recovery name to CMD the way it is exactly in the ADB folder
and now your stuck, if your bootloader is already unlocked, just flash .305 firmware with flashtool the same way you flashed the lolipop firmware, once that is done, do the first boot settings and once device is launched into the software , just flash boot again
make sure you follow instructions to the POINT, so you gotta turn of your phone, press the volume up button keep it pressed while connecting your phone to the PC and flash boot and recovery and thats it
and after youre done with this process , then you turn on your phone connect it to your PC and place the superSU zip file in it and then go to recovery and flash it
adb isnt recognizing your device?
thats weird if you just connect your device nothing will happen, so you turn off your phone and press the volume up button and connect it, (thats how you enter fastboot mode) and if still doesnt recognize then do what I told you to do already and see what happens next
keep me updated and if its urgent just send me a PM because I dont see notification otherwise...
Thanks Madshark for your help, it has finally worked!
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!
Hello, until now I avoided to root my device (SGP612 / Stock Marshmallow), because I did not want to risk to lose the drm-keys or do other damage.
Besides that, there some apps, which will not run on rooted devices as netflix (at least I suppose so).
Now working on Tasker and other tools the demand of root is increasing more and more. But still I want to take it restrained and looking for a way to limit the root via ADB. I'm not sure, if that is possible, but I think, that would be a good compromise. Online I found a huge amount of guides and threads "how to root", but all of them, at least it looks like that, ending with an unlocked bootloader, TPRP, SuperSU and so on. I did not read all of them, because that would take years and these guides may also be outdated or even worse incorrect.
Therefor I'm here to ask you about yours assessment.
My main goal would be to:
- Make a full backup
- Protect the DRM-Keys and other irreversible stuff
- No app should be able to detect that the device has been rooted respectively modified on system-level
- Void a reset of the current setup
- Install some apps to system via adb and grant some permissions, uninstall few oem-apps
- Tweak a few settings via adb
Is that possible? And if so, are there some good and simplified guides, which I should read?
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
temporary2010 said:
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
Click to expand...
Click to collapse
I will ask the moderation to move my thread, thanks for the hint.
That sounds complicated to flash an older ROM, especially if no suitable instructions are known to me.
BTW. I prefer to stay at stock.
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
M1chiel said:
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
Click to expand...
Click to collapse
The thread has been moved by now, so that should be ok.
But still, I do not want any custom-rom. My experience with such on other devices in the past was very frustrating and a waste of time. Had always stability issues on driver-level and other misbehavior. On one samsung device I tested around ten or more roms and all of them was quite ****ty...
And until now it sounds like, I need to install a custom before I even can start to make backups and such. But I want a backup of the status quo, to which I could always rollback, if things gets ugly.
I like the current stock, is a good and stable base, a few tweaks and it would be perfect for me. Of course, I did not test any customs on my current device to be able to make some substantiated conclusion on that but I'm to distrustful to follow this path, especially not when there is no way back.
I miss any imagination what is possible and what is not, or what effect a particular measure entails. Therefor I can't estimate the accuracy of any guide and there are hundreds of them out there, and it looks like the approach is sometimes different. I started reading some of them, but stopped it because I could not retrace the content.
Can you recommend a good guide, which could work out for me and whats the name of the tool to backup the drm-keys? Thanks...
Check here for the TA backup https://forum.xda-developers.com/cr...rsal-dirtycow-based-ta-backup-t3514236/page47
I am very happy with this rom, the developer recently issued a Pie alpha (which I haven't tried yet)
https://forum.xda-developers.com/z3...m-aicp-android-ice-cold-project-o8-1-t3731197
There's a guide for rooting + recovery @ https://forum.xda-developers.com/z3...to-rooted-lollipop-locked-bootloader-t3083980
Be sure you follow the instructions very carefully, since you are flashing (the system partition) with the ROM from a Z3 phone.
The process is similar to the Z3 phones:
- flash to an older ROM
- root
- install custom recovery
- using custom recovery, flash with a prerooted, updated ROM
No need to unlock bootloader and no need for custom ROMs.
Asides from that, I don't know how to do the rest of the stuff in your list.
(I'm debating on getting a used Z3t, which is why I'm researching root possibilities .)