Hi! I've decided that I'm going to upgrade my rooted Z3 (D6603) to Lollipop. I currently have a locked bootloader and I'm running Android 4.4.4 (23.0.A.2.93) which I rooted using Giefroot.
Now if I follow this tutorial, I can upgrade without unlocking. However, I'd prefer Stock Xperia at 5.1.1 (since its built for my specific hardware) over Generic. The problem is, there's no US T-Mobile 5.1.1 build for the D6603. The closest two builds are 5.1.1 Generic and 5.0.2 T-Mobile UK. I'm torn between these two options, as I can't seem to find any good list of pros/cons concerning Xperia vs. Generic and 5.0 vs. 5.1.
However, there is a third option I am considering. If I were to unlock my bootloader I could run CM12, which would be much better than both Stock Xperia and Generic IMO. The only issue with that is that I'm confused as to what I would end up loosing. I've backed up my DRM keys, but I don't know what good any of that is going to do for me. I've also seen that I may be able to restore functionality using this, but I'm worried I'd screw everything up, since I fully grasp what I'm doing. I also don't know if I could turn back and re-lock if anything were to go wrong.
So my question is: Which firmware do I flash? And what will I end up having to lose? My three options are as follows:
CyanogenMod 12 (After Unlocking the Bootloader)
Generic, Unbranded Android 5.1.1
Branded (T-Mobile UK) Android 5.0.2
There are NO differences between branded and un-branded Sony stock software. you can flash the "generic" variant (please be sure to match you phone model... d6603 and so on)
you can also update you phone with a flashable zip made of:
a stock sony FTF
Xzdr recovery
Supersu package
To do this you need: PRF creator ; Xperifirm (to download FTF's) ; Flashtool (to make FTF's) ; Xzdr Recovery Flashable package ; Supersu Package.
My experience with CM12 is terrible because you won't get any benefit over stock software, because stock is the most optimized / featured Rom for Z3. with CM12 be prepared to forget the "power on and play"
the "this" mod is a package to restore the features (the magic behind the DRM keys of stock roms only when you have lost your DRM keys. this mod cannot be used on non-Sony based software. DRM keys are lost forever if you do not backup them before bootloader unlock.
Just to verify before I go on with this: I won't need a unlocked bootloader, correct? All the links for Xzdr Recovery I can find state that they will brick a locked bootloader.
Not sure if this is the right place to ask this, if not just move it. TY
I have an Xperia Z3 SO-01G from Japan.
I updated it with the latest firmware from xperifirm, however, the lollipop version is only 5.02 and they don't have 5.1.1 from Docomo
When I use the generic firmware NFC doesn't work.
My question is, is it possible to use the generic firmware and just extract the NFC drivers from the docomo firmware?
I want to use the generic firmware with the latest version of lollipop with no issues regarding the drivers.
I will highly appreciate if someone could help.
Thanks a lot
Id also love to hear if this is possible. Same phone and same issue
First, to clarify, there is no 100% working method to port NFC firmware from Japanese variants to Global firmware. Sony Japan uses different method to encrypt the drivers of all Japanese model, and it can be only used by using the required firmware.
Secondly, if you want to use NFC badly, STAY WITH STOCK. There is NO USE updating the software to 5.1.1 since the stock software from those network providers is fully compatible with the devices.
If you just want to use NFC for devices to devices connection, you can port the whole NFC packages and firmware from the stock rom and flash it to the Global one (I don't have SO-01G but the SOL26 from KDDI AU, and the package is call NFC Osafu/Keitai).
And if you are not using NFC really much, you can just disable the package from root.
Note: I used to obsessed with new OSes and try to do as much as I can to port every apks from Japanese firmware to Global, but after then I realized: Tons of bugs shown in catlogs, unstable system, apps crashed a lot, overheating even when not using (with NFC-Wifi-Bluetooth disabled too, no background apps), etc...
Now I'm sticking with the stock from providers and happy with it.
Thanks N0K0m3
I'm not so much obsessed with having the latest latest software as I am about root. I'd go back to 5.0.2 (or whatever the current global) firmware if NFC still worked. I don't suppose I could flash the previous kernel on top of this ROM and everything would be honky dory.
Any more advice you have is welcomed. I'm sure I'm not the only person curious.
Thanks again
this is my work long time ago for firmware (23.1.A.62), can not guarantee 100% working with NFC driver, because I don't have condition to test.
If you like, you can flash it as flashing prerooted zip.
https://drive.google.com/open?id=0B0EOZK8Eg5HBYjdGVVlsclNadm8
if wifi get problem, after flashing rom, flash this fix
https://drive.google.com/open?id=0B0EOZK8Eg5HBYjdGVVlsclNadm8
Hi there!
Apologies if there is an existing thread that covers this topic but I was unable to find anything so I decided to create one.
I'm based in Australia and currently using an Xperia XZ F8331 that is branded by my telco, Telstra.
What I would like to know is the following:
1. Where can I find official Sony ROMs? I would like to remove all traces of the Telstra branding, software, etc. and install the same ROM as would ship on the handset if purchased directly from Sony.
2. If there is such a ROM resource available and I successfully flash my handset, will I receive future software updates via OTA notifications as soon as Sony pushes them out into the world or will I still be waiting for my carrier to test and release their own update?
3. Are there any potential downsides from removing all traces of my carrier on my handset?
Essentially, I want my handset to be identical to one purchased directly from Sony with future updates still downloadable automatically and as quickly as Sony releases them.
Many thanks in advance for the help!
mouzii said:
Hi there!
Apologies if there is an existing thread that covers this topic but I was unable to find anything so I decided to create one.
I'm based in Australia and currently using an Xperia XZ F8331 that is branded by my telco, Telstra.
What I would like to know is the following:
1. Where can I find official Sony ROMs? I would like to remove all traces of the Telstra branding, software, etc. and install the same ROM as would ship on the handset if purchased directly from Sony.
2. If there is such a ROM resource available and I successfully flash my handset, will I receive future software updates via OTA notifications as soon as Sony pushes them out into the world or will I still be waiting for my carrier to test and release their own update?
3. Are there any potential downsides from removing all traces of my carrier on my handset?
Essentially, I want my handset to be identical to one purchased directly from Sony with future updates still downloadable automatically and as quickly as Sony releases them.
Many thanks in advance for the help!
Click to expand...
Click to collapse
1. You can download them in "XperiFirm" software. However, to my experience, it's best to use XperiFirm that's inside Flashtool's latest version. It will only work on latest version (0.9.23.2). You can find it at flashtool's website (here) and then you need to update to latest by replacing x10flasher.jar
2. Short answer: No. In order to flash another ROM you need to unlock your device. It's better to backup your unique DRM keys before unlocking. You will always be able to update your ROM, however OTA will never work again, unless you go back to everything stock.
3. Absolutely not. In fact it's even healthy
quera said:
2. Short answer: No. In order to flash another ROM you need to unlock your device. It's better to backup your unique DRM keys before unlocking. You will always be able to update your ROM, however OTA will never work again, unless you go back to everything stock.
Click to expand...
Click to collapse
Not true for stock ROMs flashed with flashtool. You only need to unlock if you are flashing a custom ROM, or one based on stock that has been modified in some way. Flashtool can only flash completely stock ROMs in flashmode using files downloaded direct from Sony servers that are completely unmodified. Flashtool does NOT require you to unlock the device in order to do this.
Once you have flashed a FTF on flashtool you WILL still receive OTA updates.
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.
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