I own an M2 D2303. I've rooted it with Towelroot, so I'm stuck with Jellybean for now and am thinking of upgrading to Lollipop. I rooted mainly to delete bloatware and some stock Sony apps that I thought were useless. I haven't done any modification other than that (e.g. flashing custom ROMs).
I've found an FTF file for update 18.6.A.0.175. My main concern right now is if this will be safe to flash with Flashtool. I've seen some tutorials for flashing that warn me to backup IMEI information before flashing, but those are usually for if people want to flash custom ROMs rather than stock ROMs. So, are there any extra precautions I really have to take (besides backing up the data on my phone...also, would the stock Backup & Restore app suffice?), or will this generally be a safe process?
Flashing you need an unlocked bootloader too not just root,
Make sure you have 50+% battery and the USB connection on your phone and pc is good also do not use your phone or pc especially the USB ports during this period also it's good to get an exact backup of every thing
You do not need unlocked bootloader to use flashtool or be rooted for that matter. Flashtool will work on totally stock devices. totally the wrong information for sonys EMMA software you need unlocked bootloader which is totally different to flashtool
[email protected] said:
You do not need unlocked bootloader to use flashtool or be rooted for that matter. Flashtool will work on totally stock devices. totally the wrong information for sonys EMMA software you need unlocked bootloader which is totally different to flashtool
Click to expand...
Click to collapse
Thank you very much for the response
Just clarifying that I am indeed not talking about Sony's EMMA but Androxyde's Flashtool. So will this be safe for my phone then? Would it really be necessary to still back up IMEI or take any other precautions?
Sorry, I'm just really clueless right now and I'm worried I might do something wrong.
Do us T-Mobile D6616 Xperia Z3 owners have any options to install a different Sony ROM from another variant that has a newer Android version (Marshmallow)? Our bootloader is locked but it's my understanding that the bootloader doesn't need to be unlocked to install another Sony Xperia ROM from the same variant. The question is: although it might be expected/understandable, what is the root cause as to why our D6616 soft bricks when trying to installing the ROM from another Z3 variant (eg. D6653)? Is there a certain piece of the ROM such as the baseband that causes the soft brick, in which case wouldn't it be possible to just remove the baseband from the ROM/FTF and it would work?
Are there any Devs willing to explore this or already know? I just want to know if us T-Mobile Xperia Z3 owners are completely screwed with no options?
By the way, Des from the product team at T-Mobile said that Sony dropped Dev support for the T-Mobile Xperia Z3... How lovely...
s1dest3pnate said:
Do us T-Mobile D6616 Xperia Z3 owners have any options to install a different Sony ROM from another variant that has a newer Android version (Marshmallow)? Our bootloader is locked but it's my understanding that the bootloader doesn't need to be unlocked to install another Sony Xperia ROM from the same variant. The question is: although it might be expected/understandable, what is the root cause as to why our D6616 soft bricks when trying to installing the ROM from another Z3 variant (eg. D6653)? Is there a certain piece of the ROM such as the baseband that causes the soft brick, in which case wouldn't it be possible to just remove the baseband from the ROM/FTF and it would work?
Are there any Devs willing to explore this or already know? I just want to know if us T-Mobile Xperia Z3 owners are completely screwed with no options?
By the way, Des from the product team at T-Mobile said that Sony dropped Dev support for the T-Mobile Xperia Z3... How lovely...
Click to expand...
Click to collapse
Without an unlocked bootloader, there's not really much to be done. You're at T-Mobile's mercy for updates. You cannot install a ROM for any other variant than the D6616. There is a check that happens in the bootloader when you turn the device on. If a non-D6616 firmware is detected, it will refuse to boot until it detects the correct one. This is easily bypassed with an unlocked bootloader, which is not available for the T-Mobile variant.
In short, yes, D6616 owners are indeed screwed. Don't buy carrier models whenever possible.
There are unlocked versions now available. I unlocked my version and tried to flash another room but didn't work.
I would love to know more specifics on how to bypass the check. Is part of it replacing the phone ID?
---------- Post added at 06:52 PM ---------- Previous post was at 06:06 PM ----------
Here is the partition files if that helps
https://docs.google.com/document/d/1Nl5Egwt4ubXDRpLNOEzVQRu0gNk2lxO2ad7nUkNTkD0/edit?usp=sharing
A quick note from the battlefront. Both Sony and TMO are pointing at eachother. The one constant is not owning up to orphaning the TMO variant less than a year into its product cycle. It's actually quite amusing to see the non-statements from both parties. A simple "It ain't happening" statement would shut the door.
Here's hoping someone with a lot of time on his/her hands can jailbreak the D6616 variant.
The partition layout is the same. If every partition was pulled from a D6603 with adb or fastboot. I theoretically should be possible to flash them one by one to a D6616 if done in the correct order. A jtag cable may be necessary.
So you are saying the only way to do it is getting a copy of someones phone partions and installing them individually?
/u/cajunflavoredbob @cajunflavoredbob Any further suggestion from your end?
odunke01 said:
So you are saying the only way to do it is getting a copy of someones phone partions and installing them individually?
/u/cajunflavoredbob @cajunflavoredbob Any further suggestion from your end?
Click to expand...
Click to collapse
The bootloader for the D6616 is not the same as on the other unlocked models. You can bypass the bootloader lock and write directly to the partitions using a jtag box or similar hardware, but there's a very real chance that it will still not boot up, since the bootloader checks for firmware verity on boot. As I mentioned before, take this as a lesson not to buy carrier branded models in the future, or at least those without a bootloader unlock method. I know the temptation is there to get the device cheaper through the carrier, but you're getting what you pay for.
@cajunflavoredbob the device I have is unlocked. It is not from tmobile directly.
When I purchased it the phone was branded as a D6603.
So with the knowledge that this phone does have an unlocked bootloader. Is there a non hardware related method?
odunke01 said:
@cajunflavoredbob the device I have is unlocked. It is not from tmobile directly.
When I purchased it the phone was branded as a D6603.
So with the knowledge that this phone does have an unlocked bootloader. Is there a non hardware related method?
Click to expand...
Click to collapse
You're in the wrong forum then. This is for the T-Mobile version (D6616). With an unlocked bootloader, you can pretty much flash whatever you want.
I am annoyed as when I purchased the phone it was branded as a D6603 (packaging and advertising) but is truly a D6616 as stated in the phones internals.
When I originally got the phone I upgraded it using xperia companion and it installed D6616 firmware, that was the first time i realised something was different with it.
The IMEI numbers match and sony recognises it as a proper IMEI.
I checked the bootloader status using *#*#7378423#*#* and it stated "Bootloader unlock allowed: yes"
I then proceeded to Sonys website to unlock the bootloader and it changed to "Bootloader unlocked: yes"
Flashing a normal d6603 firmware (rom or ftf) doesn't work, only d6616
There are also others who have stated that they have unlockable versions of the d6616, it isnt just me.
So repeating my question, is there something that can be done?
I think we need to try the Non-T-Mobile US Model (D6646) ROM. It's the closest to our T-Mo model.
Ok, so I tried again.
Checked my bootloader staus again, it still says unlocked:yes
Tried flashing niabocs existenz rom - > softbrick (blackscreen, no logo)
Reflashed the stock 4.4.4 FTF
Rooted, recovery etc.
rechecked bootloader, still unlocked: yes
Tried Slimm rom from Wajk - factory reset etc
- > softbrick (blackscreen, no logo)
What step am I missing?
Do i need to flash the D6603 FTF first?
---------- Post added at 09:44 AM ---------- Previous post was at 09:34 AM ----------
Ok, so that didn't work
03/041/2016 11:41:47 - INFO - Opening TA partition 2
03/041/2016 11:41:47 - INFO - Writing TA unit 00002774. Value : 01
03/041/2016 11:41:47 - INFO - Closing TA partition
03/041/2016 11:41:48 - INFO - Processing partition-image.sin
03/041/2016 11:41:48 - INFO - Checking header
03/041/2016 11:41:48 - ERROR - Processing of partition-image.sin finished with errors.
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
Do I need to extract the files and create a PRF, leaving the bootloader from D6616 in it?
Screenshots to show it is a D6616 with an unlocked bootloader
@cajunflavoredbob Hate to bother you still, but you mentioned it was easy to bypass the check on boot.
I haven't been able to find that searching on XDA or google.
How would I got about it.
As you can see above, I DO have a D6616 and it has an unlocked bootloader.
As I mentioned, you can bypass the bootloader by writing directly to the partitions through a jtag box or similar. However, you would still likely have an issue when you reboot due to the bootloader verifying the system on each boot.
It seems like your device took the wrong firmware update, though. I have not come across any D6616 devices with an unlockable bootloader. If you say that the packaging labeled it a D6603, and it later turned into a D6616 with an unlockable bootloader, this backs up my theory.
You could try unlocking the bootloader and flashing whatever you want, but the issue now is that you have a D6616 bootloader looking for the same system image.
Long story short, it is easy to bypass the bootloader, but only if you have the hardware to do so. Honestly, I would argue that it's better to just pick up a new device at this point. The G4 can be had for under $200, for example, and that's about what a jtag box is going to cost you.
Unless someone creates a tool to unlock the D6616 bootloader or to replace it with one of another model, there's really nothing you can do. Carrier branded devices suck.
Ok, thanks mate. Thought you meant there was a software coded way of bypassing.
That sucks.
Oh well, no idea why it changed to a D6616 firmware, but i'm stuck with it now. Its still a good phone and I can do enough manually, it was just easier to use someone elses hardwork through an already modded rom.
Thanks for the reply.
@odunke01: I have D6616 with Bootloader unlock allowed: yes, same as yours. I think that like me, you purchase your phone from non-authorized distributor. I found that DRM Key has [Unknown error]. Though I do think that the phone originating US T-Mobile D6616 and has been modified (may be illegally). This modification is to unlock SIM card that allow the phone working with free SIM.
well if ur package labels as d6603 then u need to recover it to this version somehow else this mobile will be no fun for ya. miht an mod cn be done for an recovery to cheat on the kernel and insall the right kernel above it and sin error can apear when ur download have problems. ps if uinstall an costumrom then install one wich is ful and before that delete everything on ur phne except the fota partition. mch easier to avoid darkness of death. it should work.
Hey there!
I'm a new owner of Z5 and in the past I owned X8,xperia mini,xperia L,and Z3+(with LB),so I'm kind unfamiliar with Z5 rooting,backing up DRM keys,etc.My question is:Flashing a kernel or unlocking the BL can be done only via ADB or can I use Flashtool as well?
I used flashtool to do both.
I have not received the 32.2.A.0.305 update for my Z5 yet, so I went to XperiFirm to check which region my device's firmware is from. It turns out the firmware is CDA 1298-2996 (South Africa).
I live in Australia and wish to flash the Customized AU firmware with CDA 1298-7277. I want to do this so that my device will be updated and will be using the Australian firmware.
My bootloader is locked; is flashing possible without unlocking the bootloader?
Will flashing a different firmware potentially cause damage (my device is not network locked, and single sim E6653).
Will this affect my warranty / DRM keys?
Thank you in advance, I appreciate any help :angel:
You are safe to flash almost any E6653 Firmware onto your E6653
Obviously dont flash test firmwares or ones that May lock your sim
Sent from my E6653 using XDA-Developers mobile app
Envious_Data said:
You are safe to flash almost any E6653 Firmware onto your E6653
Obviously dont flash test firmwares or ones that May lock your sim
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you And the DRM keys should not be affected? I have read that unlocking the bootloader only affects the keys.
csfrank271 said:
Thank you And the DRM keys should not be affected? I have read that unlocking the bootloader only affects the keys.
Click to expand...
Click to collapse
Flashing a FTF shouldent touch DRM At all.
Envious_Data said:
Flashing a FTF shouldent touch DRM At all.
Click to expand...
Click to collapse
Thanks again, I appreciate the knowledge!
csfrank271 said:
I have not received the 32.2.A.0.305 update for my Z5 yet, so I went to XperiFirm to check which region my device's firmware is from. It turns out the firmware is CDA 1298-2996 (South Africa).
I live in Australia and wish to flash the Customized AU firmware with CDA 1298-7277. I want to do this so that my device will be updated and will be using the Australian firmware.
My bootloader is locked; is flashing possible without unlocking the bootloader?
Will flashing a different firmware potentially cause damage (my device is not network locked, and single sim E6653).
Will this affect my warranty / DRM keys?
Thank you in advance, I appreciate any help :angel:
Click to expand...
Click to collapse
you can flash and what ever with your device, DRM keys are safe!
when u ulock bootloader, the device WIPE user Data and sony partitions (TA (trimArea) partitions) and DRM keys and FIDO keys will be lost!
this $h!t is with sony only!!
i rooted my fone and having modified kernel having DRM stimulation installed. its working fine now.
- at any given day, to a thirsty user who wants to CONTROL his Xperia to the most. i would say, ignore drm keys and make a deal with devil to have root access
- however since Xperia Z5 (unlike latest xperia Xseries) came out on LP kernel. so u can FLASH LP kernel and root it with app like kingroot and extract your DRM keys to windows pc and back it up. now u can flash the LASTED Android back on you Xperiaz5 and unlock your boot loader to have root access.
check this
http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
YasuHamed said:
you can flash and what ever with your device, DRM keys are safe!
when u ulock bootloader, the device WIPE user Data and sony partitions (TA (trimArea) partitions) and DRM keys and FIDO keys will be lost!
this $h!t is with sony only!!
i rooted my fone and having modified kernel having DRM stimulation installed. its working fine now.
- at any given day, to a thirsty user who wants to CONTROL his Xperia to the most. i would say, ignore drm keys and make a deal with devil to have root access
- however since Xperia Z5 (unlike latest xperia Xseries) came out on LP kernel. so u can FLASH LP kernel and root it with app like kingroot and extract your DRM keys to windows pc and back it up. now u can flash the LASTED Android back on you Xperiaz5 and unlock your boot loader to have root access.
check this
http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
Click to expand...
Click to collapse
Thanks for the advice, I will look into it in the future when CyanogenMod improves and I need to unlock the bootloader to install it. My main incentive for this would be to greatly improve the camera, which we all know takes very washed-out photos.
I have just gone through the firmware flashing process. Thankfully there are many guides available and it all worked just fine, so I am using the current, correct firmware now
The worst part was just the waiting and suspense (feels like a lot could go wrong).
Thanks again Envious_Data and YasuHamed!
csfrank271 said:
Thanks for the advice, I will look into it in the future when CyanogenMod improves and I need to unlock the bootloader to install it. My main incentive for this would be to greatly improve the camera, which we all know takes very washed-out photos.
I have just gone through the firmware flashing process. Thankfully there are many guides available and it all worked just fine, so I am using the current, correct firmware now
The worst part was just the waiting and suspense (feels like a lot could go wrong).
Thanks again Envious_Data and YasuHamed!
Click to expand...
Click to collapse
i had flashed Cm13 on XperiaZ and inbuilt camera app of CM13 was worse than xperia! and if you think you z5 camera isn't working properly then God Help you when you won't have DRM keys in place! because the DRM keys actually enables feature of camera which wont be activated if DRM keys are lost
nothing will go wrong! be confident! sony devices are Hardcore stallions! once you nail them! they will be your pet!
So I got a Xperia XZ F8332, it have bootloader status is Yes and I'm going to run a custom ROM, i have some question before follow a guide to root 1st :
1.I need to downgrade to MM in order to backup TA partition, i know this contain drm key for some technology, so i only just keep a backup and everytime i use a new ROM, i only need to flash it back?
2.I've heard some people say when downgrade to MM the Bootloader will change to No if you flash wrong way, so which .sin i should tick to avoid that problem?
3.which ROM is stable and bring the best Performance for this Phone?
Thanks alot to anyone who spend some time to answers my questions