yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mhaha:
The thing you want to take extra precaution with is your DRM keys. Once you've unlocked your bootloader, there's no way to get them back without a prior backup.

I believe many of the replies above assume you have already unlocked your bootloader. To the best of my knowledge, it's impossible to run custom software (anything not signed by Sony) with a locked bootloader. To date, there's no way to root with a locked bootloader.

Therefore you can conclude that you have to unlock your bootloader before you can progress, but then you'd face the first problem I warned about.

So, what you'd want to do is first and foremost is downgrade your firmware to an older version that is exploitable to backup your TA partition, which contains your DRM keys.

To perform a downgrade, you must use a third party tool. Flashtool is the de facto flashing tool for Xperia devices.

To obtain an older version of stock firmware, you can download it straight from Sony's servers using a tool called XperiFirm, then use Flashtool to convert the package to FTF format, which is the file type Flashtool uses for flashing firmware.

However, Sony's servers usually only serve the latest firmwares, so you might not find the version you want. The next best option is to find and download a FTF file from a trustworthy source. Unfortunately, I don't think anyone has attempted to make a repository of FTF files for Z5C, so you'll have to search the forums and cross your fingers.

How old the version should be depends on what solution you pick to backup the TA partition. I recently made a rooting guide that provides instructions on one of the solutions which uses the dirtycow exploit. I think any MM or earlier version would work, since the last MM firmware Sony released is 32.2.A.5.11, which is vulnerable to dirtycow.

Once you've backed up your TA partition, then you can safely unlock your bootloader, then decide for yourself how you want to get root.

If you prefer a "stock" kernel and firmware, see the rootkernel thread, or you can see the guide I linked to above. If you do follow my guide, in step 6 don't include xposed, and use superuser instead of SuperSU for root management (see the first post in the rootkernel thread for more info). You'll need to download phh's superuser app from the Play Store after you're done. The rootkernel tool packs TWRP into the boot.img automatically, so there's no need to install it separately. It also integrates DRM fix.

Or, you can try any of the replies above.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] brokich:
Thank you very much for the post - it's very informative! This is basically what I have gathered (also through your dirycow exploit threat, which is awesome), but I was under the impression that it is not so easy to flash older firmware, or that even that requires an unlocked bootloader? Well, actually you answered that - ROMs that are officially signed by sony can be flashed without unlocking bootloader, it seems. And is there any risk of bricking the device by doing this?

Is it really that simple? Get a MM build and use flashtool to flash it, and you are done? If that is the case, then I might as well try the whole process, using your guide and rolling back to MM before that. It is very annoying to see what kind of insane battery drain we get (even 3 days of usage is ridiculous, less than half of what we should be getting) and to be fair it's just not pleasurable to use a device that you do not really "own".
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mhaha:
Using Flashtool to flash stock firmware is relatively safe, but I don't think anyone can guarantee no risk. In the unlikely event that something goes wrong, you can always try to reflash or use Sony's official tools like PC Companion (or whatever they call it these days) and attempt to repair. In any case, the TA partition is not touched, so your DRM keys will be safe and you have a greater chance of not voiding your warranty. As long as you don't tick the wrong checkbox in Flashtool that is, since it does have the ability to wipe the TA partition.

The basic idea really is that simple, but as you can see from the long guide, the actual steps to get there isn't exactly 1-2-3. The point of the downgrade is to backup the DRM keys, but if you'd like to stay on MM instead of going back to 32.3.A.0.376 that's also an option. I'm not sure if you're aware, but Xposed currently only supports up to MM.

The battery drain you mentioned is slightly curious, although personally I'm still on MM, I've read through the Nougat thread and thought people generally reported improved battery compared to MM. And 3 days of usage is ridiculous indeed... ridiculously long that is. Which phone can do more than double that time? I thought the Z5C maxed at 2-ish days of moderate to light usage.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Bobzee:
I might ultimately roll back to MM and stay there until Xposed is done for Nougat (if it is done at all). But really, what I need from Xposed is baked into some of these Kernels already, so I won't be missing much.

The problems are bugs and stability... your long post is concerning as it reveals quite a few issues along the way.

And about battery, to respond to mhaha - yes, 2-3 days would be a lot with very heavy usage (10 hours of screen time in 2-3 days). But idle, full standby, should be about 25-30 days with LTE on on almost any phone with a battery that has 2700-3000mAh. This is not some kind of voodoo magic, these devices should drain about 0% per hour when not used. Of course, under usage it will drain much more, but not in idle. And now I get 0.6-1% of idle drain. How can that be compared to 0.0% drain?

https://drive.google.com/file/d/0B5vc7tjpQrnkdlFmRi0wWTVjMDg/view

This was from jenana, in your dirtycow exploit thread, on android 7, with some modifications in the rom and kernel.

That's what I am after. There is also another topic about battery life in the Xperia cross-device forums. You can see screenshots there with 10 hours of screen time during 100% - 6% battery. I get 2h 40mins after 3 days of almost no usage, just casual net browsing and chatting. That is completely ridiculous to me and seems very abnormal.

Even factory reset is scary to me, because I won't be able to use Debloater again on 7.0. So, I might try rolling back to 6.0.1 to back-up DRM keys and then even possibly doing the battery guide. With my casual usage of the phone I would be charging it once/twice per week.

But the whole idea is to not brick the device, while using it to the full extend, optimized as you want it, and not as Google want it.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
That's nifty, is that an app producing that log?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Bobzee:
I believe it is produced by the app "Better Battery Stats", which requires root for full functionality and is a paid app. But it seems to be very well-done and worth the money. I plan to purchase it if I ever end up reaching a rooted and stable state with this phone.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] divansantana:
Silly Q but why does one need the DRM keys?

Secondly how can one do a full backup to include the DRM keys et. Running stock 7.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
I'm still getting Recovery Loops when I do a restore from TWRP... everything is good until I try to restore

so you can get your free movies in lounge and use the special camera filters and touch things, and have a easier time claiming any warranty faults
[Xperia Z5 Compact Q&A, Help & Troubleshooting] --jenana--:
That's Better Battery Stats, indeed...

I had to check if it was paid or not, but apparently I paid €2,- for it in 2014. For me, it's most useful to dive into my idle logs, because it gives a lot of details about what happens with your phone in idle time (especially the partial wakelocks, they get your phone out of deep sleep without turning the screen on; also CPU and network use and other stuff.

[MENTION=4491364]divansantana[/MENTION]
[MENTION=5722545]mhaha[/MENTION] explained it a few message above your and also in another thread on top of "XDA - Sony Xperia Compact Z5 Compact".

Those keys are useful when you want to re-lock your bootloader and/or can be used as an alternative to the DRM-fix.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
I got a bit mad trying to get TWRP working with root and having restore functions working - but the last build for rootkernel (EDIT: I should say: rootkernel is fine, it's adding TWRP with rootkernel that causes the issue: rootkernel is what currently gave me root with SU)I have downloaded broke the partitioning of the OS so I think that's what's causing the loops - unless it was actually something to do with that DRM fix which locked everyting again... but everything worked fine in Marshmallow, that's what I don't understand (if it was DRM/TA or Verity)

Good news is - (because I rage quit, I decided to go old school and currently my compact is running non-recovery Root for now with Titanium handling my userdata) - I think I may be able to rebuild TWRP, and integrate it to Rootkernel, because I took some time to read what was happening, and during my firstboot set up and getting my phone back to some usable state - I took down some notes to where I think the TWRP was not binding correctly and to where the Z5C .376 build needed to put the internal folder.

I took some snaps for Bobzee asking about my battery in another thread. Here was my 'optimized' non-root-setup again, except this time, I only had installed ES and SuperSU/Pro as the old versions had my keys, and then I decided to redownload all(most) my apps again. I managed to keep my data low until I actually started the downloading, which was part of the idea of my first-boot setup because I was and am studying when Android first started their sync with adding photos and drive - and needed to keep my data allowance in check because of my Prepaid Mobile service. I found this out the hard way years ago when photos was added to my apps and decided to upload my albums to drive. Yay. No mobile credit suddenly.... anyway... here's the results of the battery life (Mobile data was at 40MB with WiFi at 6MB before I did the market download:

Roughly 4 hours of hard downloading/with scanning the phone/checking folders/uninstalling/usb-otg + micro-sd transfers/titanium/setup etc....

Then I went to sleep.

So, part of the good news is - while I'm on break for studying - because I can actually understand and am familiar with C++/C from school - the rest of this Linux/Unix stuff I just started reading about at Christmas last year, I'm going to try to rebuild TWRP with Rootkernel and have something specifically for the Z5C on Nougat, so I can remove all the other junk that's related to other devices that may be causing problems.

EDIT: I might even go in and change/ or add the labels to TWRP that will match Flashtool64 to make it easier for newer users to see what exactly needs flashing and what actually gets backed up in TWRP.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
Found what TWRP is doing... It's not wiping or formatting correctly after a factory reset, and the internal partitioning gets marked as ROOTFS and it's not mounted as fused
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Bobzee:
Thank you very much for your work and reporting in this thread, NeoBeum, it looks very useful. I have still not started doing any kind of re-flashing or even unlocking the bootloader. But my unit is acting strangely, sometimes slower than it used to be in MM (very snappy) and in the beginning of Nougat (again, very snappy). It's like Greenify did something I still can't fix, or the phone just somehow got bugged in some specific way. Actually, this rom has been through a lot, and it was even debloated in MM before the update and has not been reset.

So, ultimately I might even wait to see if things get better for the 7.0 rooting process, especially with TWRP. That's probably what scares me most as different users report so many different results, boot loops and stuck situations.

Unfortunately I have basic linux skills, but nothing on the level of a developer, so at this stage I can't be of any real help. But I am grateful to anyone who is helping in their free time, it's well appreciated. :highfive:
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
the TWRP git has been updated with some terminal fixes about some bugs i posted that limited my ability to work in the terminal inside TWRP, so I might contact Team Win and see what needs to be done to get the base recovery repo and then have me submit a working build for the e5823 to get it officially supported
[Xperia Z5 Compact Q&A, Help & Troubleshooting] brokich:
That would be really great! I am hoping to see official z5c support for TWRP any day now.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
I'm still a noob at this
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mhaha:
Doesn't matter if you're super haxx0r elite or complete noob, what matters is you're contributing. Props!
[Xperia Z5 Compact Q&A, Help & Troubleshooting] brokich:
Absolutely! You have my thanks as well. May your ROMs always be stable and your cache triple-wiped!
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
Thanks

I thought I'd give an update - but while I was working on the Bootable recovery, I thought I'd load up Xperia Companion... it connected... to my rooted phone... success - part one!

[IMG="XC"]http://i.imgur.com/hXiqge0.png[/IMG]

I might get the new ROM available, so I might work on the Android bootable recovery for 32.3.A.0.376 & 32.3.A.2.33

You know you're on the right track when this happens too...

[IMG="Telstra"]http://i.imgur.com/gobdAKul.png[/IMG]
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
I've got TWRP going on 32.3.A.2.33, but I was in a rush to get out of the house... Going to test restore. If I don't post back in 15 minutes... Then I broke some thing
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
I think I figured it out... Last bit of testing ... just want to make sure

Because I more than broke something yesterday... I lost my IMEI... all good though...

If it's going to work like I think it is, I should be back in 15 minutes this time

edit: There's a problem with mounting sdcard
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
I'm restored.

I'll write up a debug report and some process for people that might be having problems with TWRP/ABRecovery and Nougat.

I'm just heading to a birthday, but I'll be taking a tablet with me so I can work on my Z5C.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
Try this on 32.3.A.2.33, you'll need your DK.ftf as well for the DRM

I'm still working on the latest TWRP for Rootkernel, but I got this one going:

If you need to restore - you only restore the "Data" partition. Don't restore anything else... this is the problem I'm looking at, to get the System partitions restoring as well.

It may have something to do with the Locking and Relocking of the Bootloader messing with the TA and things not being able to read ro.hardware

[IMG="Dev Options OEM Unlocking Toggle"]http://i.imgur.com/a/YsnrL.png[/IMG] - attached image

In 32.2.A.0.253 & 32.2.A.0.305, the OEM Unlocking switch can get set to Off if Developers Options gets turned off, you won't notice, and it won't affect anything because of the DRM fix in rootkernel, but it does make a difference when you try to "restore" in TWRP.

I reset everything, got my IMEI back, closed my Bootloader, and went back to 32.0.A.6.200, unlocked the bootloader, Flashed 32.3.A.2.33, fastboot flashed the rootkernel image.

Everything you need, except the Kernel ELF is in that ZIP, you can use all the versions that Sony released up to 32.3.A.2.33 with TWRP, except the Lollipop version - that zip will get TWRP going on 32.3.A.2.33 for users that are currently having trouble with "Restore" on TWRP.

Remember - Only restore the Data partition.

SHA-1: 2BDDAF2000549B33CBB9363E9C74E0B253A6C6ED
[Xperia Z5 Compact Q&A, Help & Troubleshooting] bofis:
Thank you, I have 32.3.A.2.33 up and running with this version of TWRP:

https://mega.nz/#!kxgzQAwK!04Nrn98vxChFRoyN8y0JvD9VRTf-0CrM6qx_9WldDVw

(flashed in fastboot mode with 'fastboot flash recovery twrp.img' or whatever you rename your TWRP .img file)

Then I also flashed this customized Kernel:

https://xdaforums.com/showpost.php?p=71651795&postcount=9

And then in TWRP flashed superuser-r310-beta.zip from here to get root:

https://superuser.phh.me/

(after rooting you'll have to install PHH's SuperUser and BusyBox off the Play Store)

Now I have 32.3.A.2.33 with TWRP, BusyBox, DRM Fix,RIC disabled, and dm-verity disabled with ROOT!
[Xperia Z5 Compact Q&A, Help & Troubleshooting] NeoBeum:
PSA: Android Bootable Recovery (TWRP 3.1)

Just wanted to give an update... We might have a device tree for the Suzuran soon... I have to get in contact with the Team Win developers and find out what I need to do, because I screwed up so many times, just trying to get my repos right... only took about 100GB of download... not bad for a first project.... considering the 7.0 branches are broken for the e5823 on the omnirom/android_bootable_recovery

I might ask my teacher if I can use this as an assignment... hurrrr

If I did it right, I should have encryption working for the data partition, and targeting android 7.0+, but after having looked over everything, I can get trees going down to 5.1, I just want to get 7.0 done first

I'll work on it more this week.
[Elephone S7 Questions & Answers] Oajj:
Hello. As many of you might know I'm porting cm 13 to our device. Long story but I deleted my /system folder by accident(long story) so I thought why not to make another port and try it. Anyway the rom doesn't continue from Elephone logo and I get this weird error. Could anyone please help?

02-20 17:17:32.819 18280 18280 W hwcomposer: [JOB] (0) SET/bypass/nulljob
02-20 17:17:32.852 18280 18280 E SurfaceFlinger: rejecting buffer: bufWidth=1, bufHeight=1, front.active.{w=312, h=0}
02-20 17:17:32.853 18280 18280 W hwcomposer: [HWC] (0) PRE/bypass/boot=0.1
02-20 17:17:32.855 18280 18280 W hwcomposer: [JOB] (0) SET/bypass/nulljob
02-20 17:17:32.963 18280 18280 E SurfaceFlinger: rejecting buffer: bufWidth=1, bufHeight=1, front.active.{w=312, h=0}

Thanks in advance!
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Swapnil Soni:
Closed
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] YazumiWuHung:
This is MI MIX not MI MAX .
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Swapnil Soni:
Oops my bad .. moving..
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Swapnil Soni:
Moved here

https://xdaforums.com/mi-max/develo...ootloader-unlock-method-t3560387#post71124949
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] YazumiWuHung:
It´s ok don't worry. It´s a common mistake on this forum hehe . Thanks for moving.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Swapnil Soni:
Hehe thankyou for knowing .. i did huge mistake xD
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] malybru:
Mod Edit

Thread closed at the request of the [OP]

malybru

Senior Moderator
[T-Mobile Samsung Galaxy Note 3] O's:
I've seen several N7 ROMs for N900T, but they all seem to have bugs and/or stability problems.

Which N7 ROM works best for everyone?

Darklord? AryaMOD? Mag-Ma-NX? Phronesis? Other? Thanks for all replies and especially any detailed experiences!
[T-Mobile Samsung Galaxy Note 3] Beesvee:
It depends on your preferences really. AryaMod and Phronesis are customizable, where Mag-Ma-Nx is a pure Note 7 ROM. For me personally I use Mag-Ma-NX because to me it's the most stable and complete Note 7 experience. I could never get mobile data to work with DarkLord so I never got to experience it to provide feedback. NFC doesn't work on any of them as we have a different baseband. Also the other ROMs do not have Flipboard Breifing. There are a few fix zips you need for Bluetooth and smart stay as well as Ultradata savings amd smart manager. I am also using DarkLord kernel as it is one of the only kernels that allow you to enable greyscale. But don't use DarkLord Kernal if you like to overclock or tweak because DarkLord isn't tweakable. Mag-Ma still has Dev support the others haven't seen updates for months. Hope that helps. :D
[T-Mobile Samsung Galaxy Note 3] O's:
Thank you! I guess Darklord Kernel plays well with MagMa? That's the ROM I ended up with. Couple issues (camera keeps FC'ing, something keeps waking the screen, couple other small gripes) but I'm new to it so there might be fixes.

Does DarkLord Kernel have solid performance and battery on MagMa? Thanks!
[T-Mobile Samsung Galaxy Note 3] Beesvee:
Dark Lord Kernel does well for my use. The kernel that comes with MagMa would do better for you if you have knowledge of over clocking and tweaking for performance and better battery life. I'm not a gamer so I have no need for that. The camera issue seems to be more stable when selecting the S7edge version from aroma installer. The Note 7 camera is sketchy. I haven't experienced the screen waking issue but I do know there is a Smart Stay zip fix floating around in that thread that could help with that. There is also a setting, Keep Screen Turned Off, that you could activate under the Dispay setting that may help too. Good luck to you bro.
[T-Mobile Samsung Galaxy Note 3] O's:
Great to know. i don't game either, just want stable performance and battery. I'll try Dark Lord Kernel. Yeah, the N7 or S7E cameras gave me nothing but problems in MagMa. I listed them out there, but basically they crashed too much and didn't give real benefit over N4 camera. NXTeam vastly improved the N7 camera in the latest MagMa release (UX), but it still has a delay on tap focus. That ruins it for me. Only the N4 camera does instant tap focus. Also, MagMa has an issue right now with resizing videos for text. Can't do it unless you record the video in text quality directly from Messages. Surprised at that, but hopefully it'll get fixed in a future release.

I'll try the kernel. Thanks!
[T-Mobile Samsung Galaxy Note 3] CajunDreDog:
Seems everyone I try, I get a bootloop once the SIM is in. I'm on att with n900t phone. Any ideas?
[T-Mobile Samsung Galaxy Note 3] hapa8o8:
Probably flash the respective ROM from this subforum. :silly:
[General Topics] howejustin:
Not sure where this fits, but does anybody know of an iPhone skin that is completely compatible with WM6? All that I've seen are WM5 ones that require re-linking in the text file to be compatible with new app names and whatnot of WM6.

I know that's a simple thing to do, but I'd prefer a turnkey solution, if one is available.

Thanks in advance,
[Moto Maxx Q&A, Help & Troubleshooting] filipecoimbra222:
Hi guys, how you're doing? Hope you're fine.

I'm having some weird issues with my Maxx battery. My phone was showing 80% the last time I charged, when I rebooted it showed something around 74. The most weird part was when I rebooted to recovery right after, and TWRP showed 70%. All I could think by that time was that my battery is either dying or miscalibrated. I did all the battery calibration procedure but the problem persists.

Do you guys know any method to solve my problem?

Also, sorry for my bad English.
[Moto Maxx Q&A, Help & Troubleshooting] Septfox:
I'm not sure I understand the problem. What you're describing is normal behavior...rebooting places a high load on the CPU, which uses a considerable amount of power; you might have noticed that the phone gets pretty hot if booting up takes a long time. It's not uncommon or unreasonable to drop several % doing so.

If you're worried about miscalibration, run the phone until it shuts off, and then recharge it fully. But really, I wouldn't worry too much about it unless your phone starts doing very odd things (such as turning itself off anywhere above 5%).