Related
So I recently rooted my XPERIA Z3v device, and I have decided to unroot it (don't bother trying to convince me to keep the root, I am far beyond your rhetorical questions) and I rooted with the mobile version of kingoapp.com root. When I attempt to unroot my device, neither the computer software nor the app itself are unable to unroot the device. Honestly, I regret ever rooting, and being the rookie I am, I just want to unroot my device so I can go about normal life.
Can someone please help me? I am on the edge of **** right now.
Flash a stock FTF using flashtool or force a software repair using PCCompanion
gregbradley said:
Flash a stock FTF using flashtool or force a software repair using PCCompanion
Click to expand...
Click to collapse
Can you provide links for FTF and such? Sorry for the pestering, it's late at night and I just want to go to bed.
PC Companion refuses to acknowledge that the Z3v exists, Sony lacks support for it.
http://www.flashtool.net/index.php
You can download the FTF using flashtool as well.
I am pretty sure PCCompanion provides support for the Z3v
Trust me, the XPERIA Z3v lacks any support from Sony. It is basically the basterd child of the Sony smartphone division. Pc Companion won't work for this, I have tried many times.
As for the FTF, I don't see any D6708 model firmwares there, is my feeble newbie mind missing something?
On another note again, I will be willing to keep the root access, it's just that I attempt to replace the Kinguser SU app, and superSU can't seem to update it's binary to do so. Any help there?
NeonSuperWalrus said:
Trust me, the XPERIA Z3v lacks any support from Sony. It is basically the basterd child of the Sony smartphone division. Pc Companion won't work for this, I have tried many times.
As for the FTF, I don't see any D6708 model firmwares there, is my feeble newbie mind missing something?
On another note again, I will be willing to keep the root access, it's just that I attempt to replace the Kinguser SU app, and superSU can't seem to update it's binary to do so. Any help there?
Click to expand...
Click to collapse
what firmware version are you looking for? LL or LP
Original KK firmware here: http://firmwaremobile.com/index.php/xperiadownload/file/262-z3-v
I can't find the LP leaked firmware. I believe you can download it using xperifirm and create the ftf using the flash tool.
I am looking for firmware 23.0.E.1.44. I found a supposed compatible firmware on Sony's website, but the boot unlocking and flashing seems to be a bit out of my range when it comes to understanding. (Kitkat 4.4.4)
NeonSuperWalrus said:
I am looking for firmware 23.0.E.1.44. I found a supposed compatible firmware on Sony's website, but the boot unlocking and flashing seems to be a bit out of my range when it comes to understanding. (Kitkat 4.4.4)
Click to expand...
Click to collapse
can't unlock the bootloader on the z3v so don't worry about that. You'll have to use the flashtool to flash the KK firmware I linked above then take the OTA to .44
Hi guys,
Upgraded from a Z3 to a Z5 this week.
Unfortunately the Z5 is from the Vodafone network and therefore has all their crap bloatware installed.
I've got the phone unlocked to use on o2, and was wondering if there was any way to flash a default marshmallow image on to it?? I'm not bothered about root at the moment, but just want a clean ROM on there.
It's a E6653 Z%
Bootloader unlock allowed is NO
Thanks all
waqypaqy said:
Hi guys,
Upgraded from a Z3 to a Z5 this week.
Unfortunately the Z5 is from the Vodafone network and therefore has all their crap bloatware installed.
I've got the phone unlocked to use on o2, and was wondering if there was any way to flash a default marshmallow image on to it?? I'm not bothered about root at the moment, but just want a clean ROM on there.
It's a E6653 Z%
Bootloader unlock allowed is NO
Thanks all
Click to expand...
Click to collapse
Usually you can use flashtool to flash a FTF file (you can also download via flashtool > XF icon)
I like to download the russian FTFs because they have less bloatware unlike the UK versions
If ye need to know more on flashtool either ask or do some googling
Envious_Data said:
Usually you can use flashtool to flash a FTF file (you can also download via flashtool > XF icon)
I like to download the russian FTFs because they have less bloatware unlike the UK versions
If ye need to know more on flashtool either ask or do some googling
Click to expand...
Click to collapse
Thanks for your reply. I already have flashtool and adb all set up from before.
Is there a link you can point me to for the Marshmallow ROM??
waqypaqy said:
Thanks for your reply. I already have flashtool and adb all set up from before.
Is there a link you can point me to for the Marshmallow ROM??
Click to expand...
Click to collapse
Like he said above, use the XF (XperiFirm) icon.
Devo7v said:
Like he said above, use the XF (XperiFirm) icon.
Click to expand...
Click to collapse
My apologies
didn't even know that button existed all this time!
Many thanks for the help, guys :highfive::highfive:
You can perform to install 7.1.1 stock ROM with ftf Russian or Australian files.
Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you
almeister41 said:
Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you
Click to expand...
Click to collapse
Dear are you using latest xperia flashtool which use fsc script. I think you are using old flashtool. Also check drivers are cirrectly installed. Signature verification should be off in window.
faizanfaizan said:
Dear are you using latest xperia flashtool which use fsc script. I think you are using old flashtool. Also check drivers are cirrectly installed. Signature verification should be off in window.
Click to expand...
Click to collapse
Thank you for the quick reply! I'm using Flashtool 0.9.23.1 .. I will try to re-install the drivers see if that works. Thank you again
almeister41 said:
Thank you for the quick reply! I'm using Flashtool 0.9.23.1 .. I will try to re-install the drivers see if that works. Thank you again
Click to expand...
Click to collapse
Welcome dear.
Use 0.9.23.2 if possible. Put off the signature verification in window. Turn off antivirus. Dont plug any other device in usb port.
Installed drivers from driver folder of flashtool.
faizanfaizan said:
Welcome dear.
Use 0.9.23.2 if possible. Put off the signature verification in window. Turn off antivirus. Dont plug any other device in usb port.
Installed drivers from driver folder of flashtool.
Click to expand...
Click to collapse
Tried everything you stated and sadly it doesnt work as well. Maybe there isn't a way to flash SO-01J to a generic rom. :crying:
almeister41 said:
Tried everything you stated and sadly it doesnt work as well. Maybe there isn't a way to flash SO-01J to a generic rom. :crying:
Click to expand...
Click to collapse
Yes it's looking that. I also search for your probpem nut nothing is found. Can your model fall in f8331 aur f8332 category. Otherwise contact with androplus, a great developer in xperia software.
faizanfaizan said:
Yes it's looking that. I also search for your probpem nut nothing is found. Can your model fall in f8331 aur f8332 category. Otherwise contact with androplus, a great developer in xperia software.
Click to expand...
Click to collapse
It's a single sim phone. so It falls under F8331. Thank you @faizanfaizan for all your help!
almeister41 said:
It's a single sim phone. so It falls under F8331. Thank you @faizanfaizan for all your help!
Click to expand...
Click to collapse
If it's f8331 then just install boot image from androplus through fastboot and then install recovery through fastboot and install custom rom.
Responses are still very much appreciated. I still have hope the SO-01J can be flashed with a generic ROM.
almeister41 said:
Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you
Click to expand...
Click to collapse
Hello i were having the same problem xperia xz dual(F8332)
use original cable to connect pc and direct attach to motherboard (from back panel) and try to re install the drivers.
good day
did you manage to fix this?? same prob.. so-01j user here
was anyone able to flash generic firmware ?
so-01j did anyone figure out how to flash f8331 firmware it always fails im tired of the docomo software and I want to stay stock I know theres a way to get generic firmware on this some insight would be great
francisac3 said:
good day
did you manage to fix this?? same prob.. so-01j user here
Click to expand...
Click to collapse
almeister41 said:
Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you
Click to expand...
Click to collapse
Hi!
I am also experiencing the same situation. Who can help me?
Who can help me?
:crying: I m haven the same condition with you. Who can help me? Asking for help.i used all the flashtool,but it still dont ok.
I have the same condition with you.I do it yesterday.you should use 0.9.23.2.Flashtool flash so 01j .ftf. Yesterday i went to japanese NTT'S Home net to download it.
Did you flash the international ROM? Or still use Docomo 6.0.1?
same problem here , i try to flash 41.3.A.2.24 AU on my Sony Xperia XZ SO-01J but it always appear error at all sin files start from partition.sin
anyone have solve this problem?
AFAIK you cannot flash that file to that device.
you can't flash other rom into this phone, it only accept docomo rom. the bootloader is locked and it's not unlockable (as far as I know unless docomo allows it or someone managed to find a way). so I did the next best thing, by removing some of the docomo apps through adb. I also removed some Sony apps like Xperia Tips and Whats New and a few others (facebook etc). battery life has been better since less things running in the background now, free RAM is around 1gb though I don't play games at all.
Hi, i've sony xperia xz premium and i want to flash a generic italian firmware. It's my first time in flashing a sony device and i searched a lot in internet, but i found nothing. I'm on locked bootloader, any help please?
You need flashtool to flash Sony devices. www.flashtool.net
But, it is not yet compatible with XZP.
There is another tool but no one know the safety of it so better wait.
Btw, you don't need to unlock the bootloader to flash official roms from other regions.
ninjy said:
You need flashtool to flash Sony devices. www.flashtool.net
But, it is not yet compatible with XZP.
There is another tool but no one know the safety of it so better wait.
Btw, you don't need to unlock the bootloader to flash official roms from other regions.
Click to expand...
Click to collapse
thank you man. I was reading about a file which is needed to use XZP with flashtool.
And, What about Xperia companion, SEUS and Emma? Are them good to de-brand?
Don't know those 2 other tools.
Personnaly I used on old version of that unsafe tool found on another thread here to unbrand, then to sleep well I did a software recovery using official Xperia companion.
Maybe it is total useless but who knows
ninjy said:
Don't know those 2 other tools.
Personnaly I used on old version of that unsafe tool found on another thread here to unbrand, then to sleep well I did a software recovery using official Xperia companion.
Maybe it is total useless but who knows
Click to expand...
Click to collapse
how to use this unsafe tool?
EDIT: for those who were lookin' for a solution, i used this unsafe tool: i just downloaded custom it firmware from xperiafirm, i pasted all the files (except all .ta files) in the same directory of the tool and i executed it. Now i'm restoring with xperia companion. All good! Thanks
Lorehaze said:
how to use this unsafe tool?
EDIT: for those who were lookin' for a solution, i used this unsafe tool: i just downloaded custom it firmware from xperiafirm, i pasted all the files (except all .ta files) in the same directory of the tool and i executed it. Now i'm restoring with xperia companion. All good! Thanks
Click to expand...
Click to collapse
Would there be any advantage with using a generic firmware for the same region, versus the carrier specific one?
So, does unlocking the bootloader and rooting cause you to stop getting OTA updates like on most phones?
Sent from my G8141 using Tapatalk
I feel your pain. You need newflasher and to follow the tutorial here
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16
- except make sure you put all the *.sin files in the newflasher directory and flash your phone.. Exclude everything else
The newflasher version that worked for me can be found here
https://mega.nz/#!MnhSlD7B!2NR5UVhaZH7D3mPXkXrUG3FfkSiavrSDVfKZ9UgE-Ik
laes443 said:
Would there be any advantage with using a generic firmware for the same region, versus the carrier specific one?
Click to expand...
Click to collapse
You don't have carrier bloatwares, but most of all, usually custom fw are released sooner because they don't need carriers approvals.
Jake_09 said:
So, does unlocking the bootloader and rooting cause you to stop getting OTA updates like on most phones?
Sent from my G8141 using Tapatalk
Click to expand...
Click to collapse
Don't remember about the bootloader but rooting it most probably make it fail to update.
Can't confirm, I usually flash new firm when they are released and don't wait for OTA stuff.
But the most annoying with Xperia phones since Z series, they have a "TA" partition, that contains DRM keys. They are used to unlock features like Bravia engine, special sound processing, ... And it seems also some camera features on XZP.
And when you unlock the bootloader, it wipes this partition and you lose your keys forever.
On Z5 there were two solution for this problem:
- Wait for a security breach that allow rooting Android, and gives you the hability to backup this partition. Then you can restore it after unlocked bootloader.
- Some people modded kernels to fake the presence of DRM keys.
In my opinion, for bootloader unlocking, wait that XZ1 are released (since they probably will have same specs as XZP) and more people getting involved to see what happens. Losing keys = losing Sony specific features you paid for.
By doing this, u won't lose any DRM key: obviously u need to remove all *.ta files (same from boot directory) in which those keys are contained.
I successfully flashed generic firmware over customized carrier firmware and in support app i got the same warranty message. No unlock no drm lost
@Jake_09 yes, carriers are often slowers in releasing firmware (i'm speaking about TIM carrier for Italy), in fact the rom which i found when i bought my phone was updated at april security patches. Now i got the last no brand update. I did the same as @ninjy with xperia companion after newflasher. Hope it helps!
Unlocking bootloader wipe TA partition, not flashing roms
cheetah2k said:
The newflasher version that worked for me can be found here
https://mega.nz/#!MnhSlD7B!2NR5UVhaZH7D3mPXkXrUG3FfkSiavrSDVfKZ9UgE-Ik
Click to expand...
Click to collapse
Heh, thanks for spreading my links :3.
Why we can't use flashtool? Maybe an old flashtool version can be used? I do not trust newflasher since virustotal reports it as a malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/
pawnstar said:
Why we can't use flashtool? Maybe an old flashtool version can be used? I do not trust newflasher since virustotal reports it as a malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/
Click to expand...
Click to collapse
That looks like a false positive since it's only 2-3 different AVs (at most) that are detecting it.
I'm going to flash to an unbranded/generic FW tonight and see how it goes!
Lorehaze said:
how to use this unsafe tool?
EDIT: for those who were lookin' for a solution, i used this unsafe tool: i just downloaded custom it firmware from xperiafirm, i pasted all the files (except all .ta files) in the same directory of the tool and i executed it. Now i'm restoring with xperia companion. All good! Thanks
Click to expand...
Click to collapse
Thanks man. Just a quick question - There's a *.ta file in the BOOT folder of the generic FW I downloaded, I definitely DON'T want to paste this as well correct?
laes443 said:
Thanks man. Just a quick question - There's a *.ta file in the BOOT folder of the generic FW I downloaded, I definitely DON'T want to paste this as well correct?
Click to expand...
Click to collapse
sure man, exclude all *.ta files, do the same for the files in boot folder.
Hope It helps
Lorehaze said:
sure man, exclude all *.ta files, do the same for the files in boot folder.
Hope It helps
Click to expand...
Click to collapse
It all worked out perfectly, just did a restore in Xperia Companion and now it's back using the generic FW, thanks
laes443 said:
It all worked out perfectly, just did a restore in Xperia Companion and now it's back using the generic FW, thanks
Click to expand...
Click to collapse
This doesnt mess with the bootloader or do anything to kill the DRM keys for the bravia engines?
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
Lorehaze said:
By doing this, u won't lose any DRM key: obviously u need to remove all *.ta files (same from boot directory) in which those keys are contained.
I successfully flashed generic firmware over customized carrier firmware and in support app i got the same warranty message. No unlock no drm lost
@Jake_09 yes, carriers are often slowers in releasing firmware (i'm speaking about TIM carrier for Italy), in fact the rom which i found when i bought my phone was updated at april security patches. Now i got the last no brand update. I did the same as @ninjy with xperia companion after newflasher. Hope it helps!
Click to expand...
Click to collapse
Cheers for this. I was worries about losing the features of the sony if I flashed a generic rom over the carrier specific one I have.
Not sure if this will do anything to improve the compatability between my car and the phone via bluetooth but worth a try.
svssolutions said:
This doesnt mess with the bootloader or do anything to kill the DRM keys for the bravia engines?
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
Cheers for this. I was worries about losing the features of the sony if I flashed a generic rom over the carrier specific one I have.
Not sure if this will do anything to improve the compatability between my car and the phone via bluetooth but worth a try.
Click to expand...
Click to collapse
This definitely didn't touch DRM at all. Just make sure you definitely don't use any of the *.TA files at all, even the one in the BOOT folder. I can still adjust my screen colour settings and they definitely work, sound settings, etc. Works great
Whats this talk about excluding .ta files? I just drop newflasher in fw folder and flash, works like a charm everytime.
What benefit do you get for excluding .ta?
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.