So it looks like XperiFix is pretty far behind in terms of device support, XZ2 is in experimental status since August with no sources for recovery, and it's likely that XZ3 will take a long time. We can unlock the boot loader but at huge risk to our camera functionality (green photos or nothing at all depending on how badly Sony has shafted us this time).
Prior to any further action or research a reliable way to backup the TA partition to enable a full BL relock in case of trouble seems prudent.
The XZ3 ships with the August patch level in .220. As of writing there is a system update available and I'm guessing it will update the ROM to the September patch level. Google Project Zero has published an exploit that is fixed with the September patch level: OATmeal on the Universal Cereal Bus: Exploiting Android phones over USB. The article is vague about the attack surface of Android Pie but it seems that on Oreo and earlier the patch can be executed on a locked phone, and that while there is some mitigation present in Pie, it should still be possible to execute the patch on an unlocked phone running Pie.
Of course this wouldn't give us root on a locked BL because of the boot signature verification (just a bricked phone if we attempt to modify boot.img), but it should be possible to at least dump the TA partition, allowing the bootloader to be safely unlocked and relocked with DRM keys intact.
Hopefully some developers and security researchers will show some interest in Sony's new flagship so ROM development can flourish here on XDA.
Hey @mufunyo
I created TWRP for the XZ2, XZ2C and XZ2P.
It took a long time, because the bootloader was locked until the September Firmware Update, which prevents modified bootimages to boot.
Because the Sony AOSP Project did need the time to integrate the TAMA Plattform with its new 4.9 Kernel.
The XZ2 Tamaline is the first Sony Device who as the 4.9 Kernel, instead of the 4.4 Kernel.
Of course this took time.
They are working hardly to migrate the older device to Kernel 4.9, too.
I am in contact with @sToRm// to get the DRMFix fully working. I use my own device for his testing purposes.
Everything is fine, except a little bug in the bootimage patcher routine, which is preventing the system to load the already finished DRMFix.
Btw. WIth the "manual" loaded DRMFIX (yes, hacky, to test it) we achieve to activate every feature which would need a locked bootloader (DRM).
SInce the XA2 and XZ2 we also still can shot pictures with the stock app, only the preview is black.
And the video playback will still work.
https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597
PS:
Since the XZ3 is part of the TAMALine, too, I could create a TWRP too.
Of course I would need a person which wants to test it with me and will unlock his bootloader.
And the bootloader need to be capable booting modified bootimages.
MartinX3 said:
Since the XZ3 is part of the TAMALine, too, I could create a TWRP too.
Of course I would need a person which wants to test it with me and will unlock his bootloader.
And the bootloader need to be capable booting modified bootimages.
Click to expand...
Click to collapse
Of course I would be willing to test with my own XZ3. However I would want to wait for the XZ2 DRM fix to be fully working before committing to it, if you can understand. I've had dust between the sensor and lens of my Z2 and Z5 (loose back cover and cracked screen respectively), so this is the first time in years I actually have a fully working phone camera, haha.
mufunyo said:
Of course I would be willing to test with my own XZ3. However I would want to wait for the XZ2 DRM fix to be fully working before committing to it, if you can understand. I've had dust between the sensor and lens of my Z2 and Z5 (loose back cover and cracked screen respectively), so this is the first time in years I actually have a fully working phone camera, haha.
Click to expand...
Click to collapse
Of course, follow the twrp xz2 thread
I will make a status update after storms DRMfix installation routine works
The fix itself is working, I tested it in the XZ2 XZ2C and XZ2P
You can write me a PM, after you wants to test
But we first make sure that there is no Sony bootloader upgrade needed to boot modified bootimages
The XZ2 and XZ2c is sharing now the same firmware as the XZ3 (all are Tama platform)
After I adapt twrp on pie and someone helps me, I could start tryjng to create twrp for the XZ3.
if u haven't already created twrp for xz3, im willing to help!!! want to root my xz3 badly...
MartinX3 said:
The XZ2 and XZ2c is sharing now the same firmware as the XZ3 (all are Tama platform)
After I adapt twrp on pie and someone helps me, I could start tryjng to create twrp for the XZ3.
Click to expand...
Click to collapse
clyde112 said:
if u haven't already created twrp for xz3, im willing to help!!! want to root my xz3 badly...
Click to expand...
Click to collapse
The single problem was the missing tester.
No one asked me :silly:
But let's wait for the next monthly patch or I would need to patch the twrp again. :silly:
Send me a message after you receives it
But be aware that I only have limited free time to work on it
ok sounds great, I understand/appreciate your limited free time.
looking forward to this, will pm u after monthly patch!
MartinX3 said:
The single problem was the missing tester.
No one asked me :silly:
But let's wait for the next monthly patch or I would need to patch the twrp again. :silly:
Send me a message after you receives it
But be aware that I only have limited free time to work on it
Click to expand...
Click to collapse
MartinX3 said:
The single problem was the missing tester.
No one asked me :silly:
Click to expand...
Click to collapse
I got in contact with @sToRm// already but he says he doesn't have a DRM fix for Pie yet, so I'm holding off for that.
How to enable oem unlocking in XZ3 H9493
MartinX3 said:
Hey @mufunyo
I created TWRP for the XZ2, XZ2C and XZ2P.
It took a long time, because the bootloader was locked until the September Firmware Update, which prevents modified bootimages to boot.
Because the Sony AOSP Project did need the time to integrate the TAMA Plattform with its new 4.9 Kernel.
The XZ2 Tamaline is the first Sony Device who as the 4.9 Kernel, instead of the 4.4 Kernel.
Of course this took time.
They are working hardly to migrate the older device to Kernel 4.9, too.
I am in contact with @sToRm// to get the DRMFix fully working. I use my own device for his testing purposes.
Everything is fine, except a little bug in the bootimage patcher routine, which is preventing the system to load the already finished DRMFix.
Btw. WIth the "manual" loaded DRMFIX (yes, hacky, to test it) we achieve to activate every feature which would need a locked bootloader (DRM).
SInce the XA2 and XZ2 we also still can shot pictures with the stock app, only the preview is black.
And the video playback will still work.
https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597
PS:
Since the XZ3 is part of the TAMALine, too, I could create a TWRP too.
Of course I would need a person which wants to test it with me and will unlock his bootloader.
And the bootloader need to be capable booting modified bootimages.
Click to expand...
Click to collapse
My H9493 (HONGKONG) couldn't enable oem unlocking in developer options. I have tried Pattern+VPN+Google account, no luck.
I think no official unlock is available currently for XZ3.
Since you cannot find the device name on the Sony dev page.
jamesys said:
My H9493 (HONGKONG) couldn't enable oem unlocking in developer options. I have tried Pattern+VPN+Google account, no luck.
Click to expand...
Click to collapse
It's a bug.
They will fix it.
Maybe with next monthly update.
Bootloader unlock bug got fixed und may be released with the December update.
https://github.com/sonyxperiadev/bug_tracker/issues/211#issuecomment-440851984
MartinX3 said:
Bootloader unlock bug got fixed und may be released with the December update.
https://github.com/sonyxperiadev/bug_tracker/issues/211#issuecomment-440851984
Click to expand...
Click to collapse
That mean, we become custom ROMs for this phone?
GreyFox777 said:
That mean, we become custom ROMs for this phone?
Click to expand...
Click to collapse
The XZ2c, XZ2 and XZ3 are very similar.
I wouldn't wonder, if someone would maintain these devices at once.
Maybe the XZ2P, too.
But at first we need to be patient.
We XZ2 owners for our first Custom Stock Room yesterday.
You may loose your camera after unlocking.
On the XZ2/compact/premium the december patch broke the camera for unlocked devices. It shoot green pictures.
Downgrading to the november patch fixed it.
But we only have a working camera on the XZ2 devices, because we used a drmfix on oreo before.
I don't know if the same problem will happen on the XZ3, but if you really need the camera, i would wait for one to test the unlocking first.
At the moment, there is no PIE DRMfix.
PS:
Of course, AOSP will have a working camera, but the camera is not fully implemented at the moment.
But it will.
Is it possible to enable RAW Support on rooted AOSP-Roms on Xperia Phones? Maybe GCam works then? This phone really needs it!
Last hope before selling this beautiful phone.
madphone said:
Is it possible to enable RAW Support on rooted AOSP-Roms on Xperia Phones? Maybe GCam works then? This phone really needs it!
Last hope before selling this beautiful phone.
Click to expand...
Click to collapse
No, because RAW is not disabled there. :silly:
The entire camera2api is available. But please look into the bugtracker of my aosp rom in the xz2 ROM thread to know at which time the camera got fully implemented.
MartinX3 said:
You may loose your camera after unlocking.
On the XZ2/compact/premium the december patch broke the camera for unlocked devices. It shoot green pictures.
Downgrading to the november patch fixed it.
But we only have a working camera on the XZ2 devices, because we used a drmfix on oreo before.
I don't know if the same problem will happen on the XZ3, but if you really need the camera, i would wait for one to test the unlocking first.
At the moment, there is no PIE DRMfix.
PS:
Of course, AOSP will have a working camera, but the camera is not fully implemented at the moment.
But it will.
Click to expand...
Click to collapse
Wait, so unlocking the bootloader only affects the camera on the stock ROM, while a custom one is a totally different story? Did I get that right?
TunerCP said:
Wait, so unlocking the bootloader only affects the camera on the stock ROM, while a custom one is a totally different story? Did I get that right?
Click to expand...
Click to collapse
Unlock the bootloader on latest PIE.
The preview and photos will be fine.
Except the low light anti noise feature.
The aosp has its own hardware drivers, independent from stock.
But there are many partitions in the phone from the stock used by aosp except the big ones you flash.
Related
This has already discussed in other posts here BUT I continue to see A LOT of people waiting for Nougat OTA like Santa Claus should bring to them... (or, even worse, trying to push it in their phones... )
So, I make this post just to give more visibility to all...
I'll try to write it clear...
Don't update your Z to Nougat by OTA!
Is it clear enough? :laugh:
Now some explainations...
Over the the common generic motivations (difficulties when not in full stock conditions, risk to brick it during process, OTAs that are the Evil... ), there is a strong one in this case: Nougat OTA for Moto Z (silently...) upgrades your bootloader too, from v. 90.xx to v. 91.xx...
This isn't really needed (Nougat runs flawlessly on v.90.xx too... ) BUT it introduces some tighter rules on what you can and what you can't anymore boot on it, limiting hacking and upgrading (to developed third part ROMs...) possibilities...
One of this rules is that with v. 91.xx bootloader you can't anymore boot to MM ROM!
Considering that as of today it seems that bootloader can't be donwgraded (some have soft/hard bricked their Z trying to downgrade it...), Nougat upgrade by OTA is a one way process.
If you consider that stock Nougat seems to have some bugs and issues (and, as of today, no Xposed available...!) and that some (all?) third part Nougat ROMs requires "MM" (v. 90.xx) bootloader to work, it seems not to be a great idea leave that Motorola upgrades silently your bootloader...
So?
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
Considering we on the Moto Z droid don't have an unlockable bootloader and/or ability to root I don't see it effecting you negatively, other than an exploit that may be discovered for marshmallow that would allow for root. We are at the mercy of a kind developer taking on the task. I really miss my hotspot without a fee... But I can go back to my Moto X if it is necessary.
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
I agree with dap... proposed solution can't be used since of unlocked bootloader, BUT if I had a Droid I would have remained sticky to first SW release as long as possible because of the higher probabilities of a flaw to hack and root it...
With Nougat and newer (even more "locked"...) bootloader it will be harder...
those are a lot of steps... is there a way to just hide the nag/update screen that pops up? it keeps wanting to update or ask for a time to update or reminds me to update etc
enetec said:
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
Click to expand...
Click to collapse
Does the method you linked to even work with the VZW variant? It looks like it used to, but the Verizon stuff is all marked through and I'm not clear on the process.
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
aatjitra said:
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
Click to expand...
Click to collapse
Hello did you try to get down to MM? Thank you
regards
iron maiden said:
Hello did you try to get down to MM? Thank you
regards
Click to expand...
Click to collapse
No. I didn't.
I read in other thread that bootloader v91 won't work with MM.
Moto Z ( UAE ) no OTA yet
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
yanniclord said:
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
Click to expand...
Click to collapse
You can't. The only thing you *can* do is tap the "Later" and then "Done" buttons. That will defer it for another 24 hours since it automatically fills in the phone's current time for the next check.
It's annoying, but it's only once a day.
EDIT: I thought you were referring to the VZW variant. If you're not and your phone is rooted, you might be able to disable or remove "Motorola Update Services". To do so, go to Settings > Apps > select "Show system" from menu (3 dots at top right) > scroll down and tap "Motorola Update Services"
I can't disable it on my VZW unit, but you might be able to. Or maybe you can remove the app via root (though I have no idea if that will cause further problems).
I too can confirm thr disabling motoservice in settings method. But you have to do it everytime you reboot your phone, it does t hurt me doing that.
I found a simple fix, get Titanium Backup and freeze that crap app, done.
yanniclord said:
I found a simple fix, get Titanium Backup and freeze that crap app, done.
Click to expand...
Click to collapse
There is another way for users with root eventually...
saif_khans said:
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
Click to expand...
Click to collapse
Simply use the method linked in OP. It uses retmx sw.
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
sam564 said:
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
Click to expand...
Click to collapse
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Variants doesn't matter all moto z is using same kernel source (I have Chinese moto z)
Let me explain, I'm trying to port farm-root for moto z
Here's the source : https://github.com/freddierice/farm-root
If anyone knows how to deal with ndk and other Stuffs, can install TWRP with this version of farm-root
But I'm trying to make it easier and here's big barrier called SELinux
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Hope it happens. The phone (accidentally?) Downloaded the update and is now asking to install. I'm afraid one day it'll just automatically update on it's own.. I can't seem to find where the system update got downloaded to, otherwise I'd delete it
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Mike3009 said:
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Click to expand...
Click to collapse
How did you relock bootloader? with TA backup?
Try to use patched kernel.
Thanks for the reply. I actually just was about to report back that I fixed the issue. I flashed over the drm workaround with twrp.
I found it here:
https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Happy to say everything is working perfectly now.
Will this work for 7 nougat on a z5?
I'm not sure. I flashed back to marshmallow to get it working. Then upgraded to the latest official firmware after.
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
smiley.raver said:
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
Click to expand...
Click to collapse
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Mike3009 said:
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Click to expand...
Click to collapse
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
smiley.raver said:
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
Click to expand...
Click to collapse
Try this drm fix. http://www.theandroidsoul.com/restore-drm-xperia-z5/
As for my marshmallow firmware, I'm in Taiwan so I used the only one listed on xperiafirm for Taiwan. Sorry I'm not able to use a Pc now to confirm.
are you on android 7.1.1?
Oops double post...sorry. Look below.
Yes. I didn't know to back up my drm keys before unlocking my bootloader and thought I was screwed. Now I'm on the latest 7.1.1, all drm functions working and I have root access. This drm fix works perfectly on the z5 premium e6853.(other models too but I can't personally verify)
I've been trying to root my Xperia Z5 Dual, and was able to get it working. However, I was unable to receive any updates from Sony (as they don't support rooted devices) so am looking into some custom ROMs (such as LineageOS, and CarbonROM), since I still want security updates (especially since the device is still vulnerable to the BlueBorne exploit). From what I've seen, these ROMs work on the single SIM variant, so I was wondering if there's any way to get them working on the dual SIM variant? I've been at this for the past few days but I've only found stock ROMs which work, none of the custom ROMs I've tried seem to work at all.
What's happened so far when I try to get them working is I end up on the Sony logo and nothing ever loads. I'm fairly new to this still so I don't understand everything about it yet.
EDIT:
I was also wondering if there's any other way to protect against the BlueBorne exploit? I'm assuming there isn't however (other than to keep Bluetooth off but I'd rather not do that).
EDIT 2:
You can delete this, based on the research I've done it doesn't seem possible to get a custom ROM for the Xperia Z5 Dual, nor does it seem possible to get the BlueBorne security patch from any source but Sony itself (as such I've relocked the bootloader and am using the Xperia Companion program to repair the device; I hope to look into rooting it once I've gotten the security patches however but I'll be going about it a different way; no trying different ROMs unless I find a custom ROM which will work).
A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Pomaraczowy said:
A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Sent from my Honor 9 using XDA Labs
hujialun2002 said:
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Click to expand...
Click to collapse
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?
Pomaraczowy said:
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?
Click to expand...
Click to collapse
We have already had a taste of Pie now,so for anyone who dont care EMUI 9 they can simply do with Treble Pie GSIs.Who cares about the ugly UI of Huawei?PE 9.0 and OpenKirin Pie AOSP are both doing quite great.
Sent from my Honor 9 using XDA Labs
Pomaraczowy said:
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?
streetu said:
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?
Click to expand...
Click to collapse
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0
Pomaraczowy said:
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0
Click to expand...
Click to collapse
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.
streetu said:
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.
Click to expand...
Click to collapse
Probably gonna do it soon.
Thanks for help.
For now, I'm up to B372, and still able to do whatever I want, fyi.
Keep on updating... and supporting the Apple wannabees of the Android world. They learned and stole the ideas they wanted from the community and now will completely lock out the devices, bootloaders, root methods, anti-rollback measures, etc.
Oh, and as for that "spying" part? Just search for "Huawei D.U.B.A.I.". Every single aspect, action, usage and telemetry of your device is logged and sent to Huawei's Big Data Analytics servers, and it's embedded on kernel and can't be disabled. Most i could do on my kernel was disabling it on GPU framework, but the rest remains. If i turn it off on kernel or eliminate it, the mobile comms framework is killed and sim card doesn't even get activated, turning your device into a small tablet at most... so you either accept it or get yourself another phone.
Since using Treble Roms gets rid of the "system" part of EMUI, like their store, services, etc, it's possible that the Analytics part is somewhat suppressed but i can't be sure of that.
My advice is, stop updating EMUI and go Treble. Or just sell your device and get another. Or just resign to the new Huawei's reality and forget this community.
Hey guys,
after all these good messages (like DRM Backup/fix etc.) i consider to root my device finally, like i did with my old Z1. but im also interested in the new pie update to test it out. So im asking myself for some weeks now:
Should i finally root or wait till the update? i heard about the problem of downgrading that, once u get the update you couldn't downgrade to the exploitable fw. What's more, I want to keep my warranty (i know that drm backup is working but the message, that my device cannot be trusted is still there at every boot). i use several banking apps that checks for root and my experience with magisk and root hiding weren't so good at all.
Thats my current situation. Should i root or not?
Irrespective of the Android Version, Rooting on XZP requires you to UNLOCK the bootloader and loosing your DRM KEYS.
so the solution is either xperifix or posts in XDA offering kernels of specific builds for you to flash.
1. lets say you are on OREO and unlock your bootloader, if you wana root that oreo version, you must find the post on XDA offering modded kernels W.R.T that buildnumber for you to flash and flash drmfix.zip & finally flash Magisk.
2. let say you are on PIE, again you will do the same, but I am not sure they already have modded kernels available on xda or not. so make sure!!!
the third option is always (disputed tool on xda known as) xperifix.
YasuHamed said:
Irrespective of the Android Version, Rooting on XZP requires you to UNLOCK the bootloader and loosing your DRM KEYS.
so the solution is either xperifix or posts in XDA offering kernels of specific builds for you to flash.
1. lets say you are on OREO and unlock your bootloader, if you wana root that oreo version, you must find the post on XDA offering modded kernels W.R.T that buildnumber for you to flash and flash drmfix.zip & finally flash Magisk.
2. let say you are on PIE, again you will do the same, but I am not sure they already have modded kernels available on xda or not. so make sure!!!
the third option is always (disputed tool on xda known as) xperifix.
Click to expand...
Click to collapse
Im aware that i have to unlock the BL and all that stuff that i have to flash, thats not the problem at all. im just not sure if i should wait for the update (since some people experience some problems and they said they couldn't downgrade) and root or not. im currently waiting for the OTA update since my provider is vodafone and they take their time before releasing the fw. the benefits of the new updates, that i heard, are just some fixes for Android, new design for the camera ui, full hd ultra slow mo and some ui changes on xperia home. or did i miss some new functions?
If you unlook the BL, OTA didn't work anymore : so you must upgrade the phone by yourself. Via newflasher or (if you've a ftf file flash tool) you can up and downgrade when ever you want. I didn't know exactly in this this moment, how to hold the user data.... you lost in this moment only the feature video enhanced (something with X-....) if you unlook the BL and upgrade to Pie