[HOW TO]Bring back your X-reality under unlocked BL - Xperia Z2 General

Hey guys!
Some of you maybe experiencing a X-REALITY lose after BL unlock(mostly).I just found a way to fix this problem.I`m not a coder or developer,so I`ll make it easy.
1.Whatever firmware you`re on,first backup all your files from the build-in storage,the next steps will delete all of them.
2.Use flashtool`s BLU function to relock the BL (IMPORTANT!)
3.Flash the official FW17.1.A.2.69 (MUST BE!)
4.After initial boot,you get your X-reality back with locked BL
5.Now use flashtool unlock the BL again (If you boot into the system,you`ll find X-reality still functional)
6.Proceed install the recovery kernel via fastboot,then the roms you like
7.Now you have a fully functional X-reality with a custom rom.
For developers,things to be noticed:
When I flashed official FW17.1.A.2.69 under locked BL via flashtool, at the end of flash log I found an extra rewriting operation
to the TA file comparing to the FW17.1.1.A.0.402 (which there was no logs).The unlock and relock action rewrites
the TA file,so I thought it`s all about the TA file.No matter what rom or kernel you use.
Hope this would help you guys develop sth.
Tested environment:
D6503
Official FW17.1.1.A.0.402 rooted
RomAur v3.1
Official FW17.1.1.A.0.402 kernel
Doomlord kernel V09
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Personally, I don't see the big deal with X-Reality. Wouldn't people want to know what the picture looks like on all devices not just their own? Maybe it's just me.

I also don't get why so many want to have something that makes everything look wrong. I'd prefer if I could use my screen calibration tool and have applied to the system.
Sent from my D6503 using Xparent Red Tapatalk 2

Obviously Sony gives us this function isn`t a waste.It`s a useful stuff viewing pics or videos.
I don`t take much attention about the color "accurate" or "reduction",afterall,it`s just a mobile phone display.
Of course you could disable it if you don`t like those colorish style,but it`s good to have this function rather than not.
No offense mate, it`s just like foods,some of you maybe like sweety things,others like hot things.

Actually, I quite like X-Reality. It gives a very nice colour rendering, not crazy like AMOLED but a nice subtle colour boost and looks amazing, especially when watching YouTube videos.

Bump!!
Well done OP for finally figuring it out!
Tested on two occasions and this method works 100%.
Thanks again.
Sent from my D6503 using Tapatalk

X reality is horrible for video, cause ghosting and make things look grainy, they should just include an option for jpeg only.

I don't know if I can be arsed trying to recovery X-Reality, I've just spent all afternoon configuring my phone again.
What's the easiest way to back up all my settings then so I can do this install method? Is it worth restoring my TA first?

idon't have origina FW 17.1.A.2.69 can i download ?

nbone said:
idon't have origina FW 17.1.A.2.69 can i download ?
Click to expand...
Click to collapse
Download the Taiwan .69 firmware found in the firmware list thread, I've done it now and it works

I may try this, i dont care for bravia but xreality actualy hit me
Edit- it seems you have to use TW global LTE FTF
Sent from my D6503 using XDA Premium 4 mobile app

Yeah,u have to use TW version firmware
Sent from my D6503 using XDA Free mobile app

Bravo!!!
Hello there.. Well this is my first ever post on XDA and to be honest I just made an account to THANK YOU for your marvelous achievement regarding this Bootloader disease. I was on .314 with unlocked bootloader and custom recovery, everything was working fine untill I came to notice after a month that X-Reality is not working since I unlocked the damnloader. I have been nearly searching web for more than 10 hours yet no luck whatsoever to get back the X-Reality function. And then I found your thread and took me 2 more hours to find that Taiwan firmware and download it. Anyways to cut short, the whole process you have described works perfectly and Thankyou sooooo much once again for giving me my X-Reality back :good: :laugh: Now I can see .402 OTA in my notifications and gona try to update from there...

Good, I used this, I installed existenz 3.1.5 with bootloader unlocked and work it. I tried with envi-rom but doesn't work

Can i do this to recover locked bootloader? I unlocked it with no backup.

elchicodelbalcon said:
Can i do this to recover locked bootloader? I unlocked it with no backup.
Click to expand...
Click to collapse
I unlocked it with no backup TA too.. And the answer is no, you can't recover TA DRM keys, I tried recover TA partition (I did backup before, with .55 locked), on 402 and 314 stock, and I can't recovery xreality only on custom roms

sh4d1t0 said:
I unlocked it with no backup TA too.. And the answer is no, you can't recover TA DRM keys, I tried recover TA partition (I did backup before, with .55 locked), on 402 and 314 stock, and I can't recovery xreality only on custom roms
Click to expand...
Click to collapse
ahhh crap...... my current endeavor is a waste of time then....... oh well killed boredom i suppose

NicotineParasite said:
Hello there.. Well this is my first ever post on XDA and to be honest I just made an account to THANK YOU for your marvelous achievement regarding this Bootloader disease. I was on .314 with unlocked bootloader and custom recovery, everything was working fine untill I came to notice after a month that X-Reality is not working since I unlocked the damnloader. I have been nearly searching web for more than 10 hours yet no luck whatsoever to get back the X-Reality function. And then I found your thread and took me 2 more hours to find that Taiwan firmware and download it. Anyways to cut short, the whole process you have described works perfectly and Thankyou sooooo much once again for giving me my X-Reality back :good: :laugh: Now I can see .402 OTA in my notifications and gona try to update from there...
Click to expand...
Click to collapse
Where did you find the taiwan .69 firmware? The link in the firmware thread is dead

HeartUnderBlade said:
Where did you find the taiwan .69 firmware? The link in the firmware thread is dead
Click to expand...
Click to collapse
the second one on the list:
http://www.mrcrab.net/androidfirmware/D6503/Sony-Xperia-Z2-D6503.html
This solution works well however you will loose Xreality again if u flash another stock FW after flashing the Taiwan FW.

nivet5 said:
the second one on the list:
http://www.mrcrab.net/androidfirmware/D6503/Sony-Xperia-Z2-D6503.html
This solution works well however you will loose Xreality again if u flash another stock FW after flashing the Taiwan FW.
Click to expand...
Click to collapse
Ahh, I see. So after flashing the TW firmware, you have to stick to using .69 or use a custom rom?
That sucks as I was hoping I could recover x-reality and flash to 4.4.4..

Related

X-Reality with unlocked bootloader

So far we couldn't use X-Reality after unlocking bootloader,
64yusuf found a way to change it!
His guide was for Xperia Z, but I confirmed it's also working with Z1.
I'm using [monXdifedZ-Honami-136_v04.00-01] (deodexed)
Download Restore Bravia Engine.zip from original thread
1. Enter into recovery and install Restore Bravia Engine.zip
2. Reboot and delete /system/app/CredentialManagerService.apk
3. Reboot again (do not enter into recovery now)
4. After finishing boot, reboot into recovery and install Restore Bravia Engine.zip again
5. Done
Don't forget to check X-Reality for mobile in settings
X-Reality OFF:
http://i.imgur.com/oEXvdLD.jpg
X-Reality ON:
http://i.imgur.com/xutiozl.jpg
WOW that sounds interesting. Once my camera issues with the phone is set, I am planning to have my BL unlocked to gain complete root. This is going to be of good use then. Thanks for posting this info.
Then Bravia and X-reality is back, after Unlock Bootlader, with this method? What about Bionz?
eclyptos said:
Then Bravia and X-reality is back after Unlock Bootlader with this method? What about Bionz?
Click to expand...
Click to collapse
Yes, they're back after unlock bootloader.
I don't know how to check if Bionz is working or not...
(unlocked bootloader and bands)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So does this work on other AOSP based roms?
Or its only for Stock based custom Roms.
we can install the Album app of Sony in Cyanogenmod..so does x-reality work then....if it works...i will switch to Cyanogenmod/Slimkat ROM.
The only factor stopping me is loss of DRM stuff (though i unlocked it long back and relocked it ).
Can anyone confirm this !
Updated : To check for bionz processing...take a photo in dark room with a point source like an LED of a charger or something. Then check for the ISO...if it is anything greater than 3200(possibly 6400) then you have the BIONZ working !!
pranii23 said:
Updated : To check for bionz processing...take a photo in dark room with a point source like an LED of a charger or something. Then check for the ISO...if it is anything greater than 3200(possibly 6400) then you have the BIONZ working !!
Click to expand...
Click to collapse
I took 3DS's LED and it says ISO 6400
http://d-h.st/94S
mmm..I don't know how to test it working or not?
Does anyone have ideas?
pranii23 said:
Updated : To check for bionz processing...take a photo in dark room with a point source like an LED of a charger or something. Then check for the ISO...if it is anything greater than 3200(possibly 6400) then you have the BIONZ working !!
Click to expand...
Click to collapse
I will not be sure about that.
RyokoN said:
I took 3DS's LED and it says ISO 6400
http://d-h.st/94S
Click to expand...
Click to collapse
So if it says 6400.. Then it works!!
Stock Android supports only till 3200...the bionz engine boosts it to 6400!
pranii23 said:
So if it says 6400.. Then it works!!
Stock Android supports only till 3200...the bionz engine boosts it to 6400!
Click to expand...
Click to collapse
That's not true, I just tried using my Z1 with unlocked bootloader (without this patch), and the image is ISO6400. I have attached the image in a zip file so that the forum doesn't remove the EXIF data.
pranii23 said:
So does this work on other AOSP based roms?
Or its only for Stock based custom Roms.
we can install the Album app of Sony in Cyanogenmod..so does x-reality work then....if it works...i will switch to Cyanogenmod/Slimkat ROM.
The only factor stopping me is loss of DRM stuff (though i unlocked it long back and relocked it ).
Can anyone confirm this !
Updated : To check for bionz processing...take a photo in dark room with a point source like an LED of a charger or something. Then check for the ISO...if it is anything greater than 3200(possibly 6400) then you have the BIONZ working !!
Click to expand...
Click to collapse
I wonder the same thing, probably ony on stock based roms tho.
Wait, pick the restore bravia option but not restore x-reality... really??
btw, maybe a rather risky way is to install a stock 4.2 rom on the Z1 then unlock the bootloader
so the camera will now break, and it wont work again without bionz (or is it??)
so restore this thing and check if the camera works
if it works, congrats
if it doesnt, it probably still not working
KWOKSFUNG said:
Wait, pick the restore bravia option but not restore x-reality... really??
btw, maybe a rather risky way is to install a stock 4.2 rom on the Z1 then unlock the bootloader
so the camera will now break, and it wont work again without bionz (or is it??)
so restore this thing and check if the camera works
if it works, congrats
if it doesnt, it probably still not working
Click to expand...
Click to collapse
I already succeeded to take a photo with focus (see above my post) :laugh:
Sony didn't make X-Reality for pictures and they just changed the name.
I read that in Z1 interviews.
RyokoN said:
I already succeeded to take a photo with focus (see above my post) :laugh:
Sony didn't make X-Reality for pictures and they just changed the name.
I read that in Z1 interviews.
Click to expand...
Click to collapse
so u are saying X-reality never exist on Z1 actually??
how come XS and XZ used to got mod for this?? My life's a lie?? :crying:
(i used to flash X-reality on XS on unlock bootloaders and i'm sure it works and make difference, so how come the Z1 dont have it??)
and i think u can still focus with unlocked bootloaders
and that 6400 and 3200 iso stuff, any prove its becoz of the bionz??
I just think u break the camera on 4.2 unlock becoz it kills the bionz and it wont work without bionz back then
so maybe restoring this thing make camera works again on 4.2, thus confirm it brings the bionz back.
logically correct??
For my Z1 the original thread way works not this one
thank you man but your steps didn't work for my Z1 4.3 .136 so I tried the steps on the original thread and it works well for me
http://forum.xda-developers.com/xperia-z/themes-apps/bravia-engine-2-restore-4-1-4-2-4-3-t2610923
I used the following steps, from another thread, on iHackers/DoomKernel and is working perfectly. Though still wonder if Bionz is working or not!
To get Bravia Engine back on deodexed ROM :
- Just flash Restore Bravia Engine (do not flash X-Reality addon)
- Once you rebooted you'll have a "credentialmanager.service crashed" que couple of time.. Go to /system/app with an explorer and delete CredentialManagerService.apk then reboot regular way
- Once you rebooted go back into recovery and flash Restore Bravia Engine again
- Reboot and check if X-Reality/BE is ticked under setting of your phone
Click to expand...
Click to collapse
Files used from the following thread - http://forum.xda-developers.com/xperia-z/themes-apps/bravia-engine-2-restore-4-1-4-2-4-3-t2610923
Hi..i on iHackers v3.0 with unlocked bootloader without ta backup..i have followed ur steps for x reality..now it worls only in album but not in videos...can u Please help me How to make it work in videos too..Thanks in advance
Sent from my C6903 using xda app-developers app
You must add this
ro.service.swiqi2.supported=true
persist.service.swiqi2.enable=1
lines in your build.prop and then it will work.
I have already added those lines in build.prop but even then i see no change
Sent from my C6903 using xda app-developers app
AndroPlus said:
So far we couldn't use X-Reality after unlocking bootloader,
64yusuf found a way to change it!
His guide was for Xperia Z, but I confirmed it's also working with Z1.
I'm using [monXdifedZ-Honami-136_v04.00-01] (deodexed)
Download Restore Bravia Engine.zip from original thread
1. Enter into recovery and install Restore Bravia Engine.zip
2. Reboot and delete /system/app/CredentialManagerService.apk
3. Reboot again (do not enter into recovery now)
4. After finishing boot, reboot into recovery and install Restore Bravia Engine.zip again
5. Done
Don't forget to check X-Reality for mobile in settings
X-Reality OFF:
http://i.imgur.com/oEXvdLD.jpg
X-Reality ON:
http://i.imgur.com/xutiozl.jpg
Click to expand...
Click to collapse
Can you make this work on the latest software update with android 5.1.1 because it only works on the oldest version

Z2 Root Exploit

Hey guys, this is a cross-post of sorts. I just got root execution on my stock Z2 Tablet and it appears that the same method should work for Z2 phone. I have a Z2 phone but just haven't tested it on that one yet.
Here is my Windows, Linux and Mac OSX script to grab the TA partition from Sony devices and deploy full root (superuser + reboot script):
https://mega.co.nz/#!jRB1FBJT!RKIi13TRj__mi7pKIGXP654CBJHi2gc0bIlYONcSfZQ [Update, v11]
Requirements:
1. Be on a firmware earlier than .402
Instructions:
1. Extract exploit.tar.gz and run ./root.sh (Linux) or root.bat (Windows)
2. Follow the instructions and your TA.img will be given and su will be deployed.
Features:
This disables SELinux, takes out sony_ric and then deploys su to /system/xbin/su
This works on ALL Sony Android mobile phones.
This can be run on any operating system.
Survives reboots [thanks to chargemon by DooMLoRD]
can't download the file. MEGA asking me about a decryption key.
Might be onto something here. This is for those that only want root and not an unlocked BL right?
Awesome work if it is working. Unfortunately I'm on .402
Sent from my D6503 using Tapatalk
Really? how about on .55? If it'll work on that I'm rolling back the update. *gets .55 ftf*
Awesome if this in fact works on the Z2!
And who cares if it requires .69 and doesn't run under .402? The only reason I currently don't want to unlock my BL is the loss of my TA partition. So one could simply downgrade to .69, backup TA, upgrade to .402 again and unlock BL (and insert DRM keys again), right?
in_finity said:
Awesome if this in fact works on the Z2!
And who cares if it requires .69 and doesn't run under .402? The only reason I currently don't want to unlock my BL is the loss of my TA partition. So one could simply downgrade to .69, backup TA, upgrade to .402 again and unlock BL (and insert DRM keys again), right?
Click to expand...
Click to collapse
That's exactly what I did.
Technically it should work on 55 too but just not sure because I copy all the vendor libs from 69 tablet.
Someone could easily make a generic firmware that works on all phones with all firmwares but that's not my focus. I just wanted to get this out here and working for Sony because I'm surprised it isn't out already.
xsacha said:
That's exactly what I did.
Technically it should work on 55 too but just not sure because I copy all the vendor libs from 69 tablet.
Someone could easily make a generic firmware that works on all phones with all firmwares but that's not my focus. I just wanted to get this out here and working for Sony because I'm surprised it isn't out already.
Click to expand...
Click to collapse
I'll have a go with it on .55, I've been having some problems with .402 anyway so it gives me an excuse to roll back the update, now I just need to get my hands on a linux live disc. (should have one knocking about).
Awesome I hope this works. I'll have a try tomorrow
Sent from my D6503 using XDA Free mobile app
Can anyone confirm if this works? It would be great!
Sent from my D6503 using Tapatalk
This is great, can someone translate this into a more user friendly method.:good:
Wow none have tried it yet??
Sent from my Xperia Z1 Compact
I tested with D6503 17.1.A.2.69 Orange FR, and successfully crashed service menu,
but TA.img was not backuped.
My bootloader is already unlocked, but it should not affect backing up TA.
Which error did you get? Can you check output in logcat?
xsacha said:
Which error did you get? Can you check output in logcat?
Click to expand...
Click to collapse
Here is the log:
View attachment log.zip
files are in /data/local/tmp but not executed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(don't mind su)
RyokoN said:
I tested with D6503 17.1.A.2.69 Orange FR, and successfully crashed service menu,
but TA.img was not backuped.
My bootloader is already unlocked, but it should not affect backing up TA.
Click to expand...
Click to collapse
RyokoN said:
Here is the log:
View attachment 2795383
files are in /data/local/tmp but not executed.
View attachment 2795394
(don't mind su)
Click to expand...
Click to collapse
Awesome. Looks like everything worked right up to the last vdc which was run by the wrong user. Easy fix. Looks like this definitely works on z2 phone then.
Funnily enough I actually had it right in the first version I made and quickly changed it to run as system a few minutes later.
Try my original script instead: https://mega.co.nz/#!PFoGEBAR!ulKWKy407aYE1vi0F9eZtNVROdG7DbJfFkKLcuIjDko
xsacha said:
Awesome. Looks like everything worked right up to the last vdc which was run by the wrong user. Easy fix. Looks like this definitely works on z2 phone then.
Click to expand...
Click to collapse
Bro, Who are you? You just made my day. I was about to unlock my phone since there's no exploit.
Today is the best day of my life.
Finished the graduation Exam. Received Z2 Tab, Saw that this awesome being found an exploit. I am literally happy right now. :highfive:
chesterr said:
Bro, Who are you? You just made my day. I was about to unlock my phone since there's no exploit.
Today is the best day of my life.
Finished the graduation Exam. Received Z2 Tab, Saw that this awesome being found an exploit. I am literally happy right now. :highfive:
Click to expand...
Click to collapse
Great news. I'm just a happy z2 user that can't live without root. Made a root utility for my last tablet (Blackberry Playbook) too.
I might improve this script to have more checks in it. More logging.
Awesome work xsacha and thanks!
Has anyone tried this on .55 yet??
Sent from my D6503 using Tapatalk
xsacha said:
Awesome. Looks like everything worked right up to the last vdc which was run by the wrong user. Easy fix. Looks like this definitely works on z2 phone then.
Funnily enough I actually had it right in the first version I made and quickly changed it to run as system a few minutes later.
Try my original script instead: https://mega.co.nz/#!PFoGEBAR!ulKWKy407aYE1vi0F9eZtNVROdG7DbJfFkKLcuIjDko
Click to expand...
Click to collapse
I haven't had success yet (running exploit scripts under MacOSX 10.9).
First attempt (from exploit in first post): http://pastebin.com/jwTKWwPu
Second attempt (from exploit "original script"): http://pastebin.com/N7FXRAAw
I'm on a stock standard Telstra Z2 phone (17.1.A.2.55).

[D6653] (5.0.2) Flashable Stock LP Pre-rooted with XZDualRecovery [Updated:05/11/16]

I wanted to share this pre-rooted stock version of Lollipop. Originally I'm on D6653 then I've been to D6603 Lollipop firmware when first released. Now it's time to shift back to D6653.
Update: Added latest firmware update
Overview:
Firmware version: 23.1.A.0.726_CustomizedPH [04/16/15]
- APAC-LTE
- SuperSU 2.46
- XZDualRecovery 2.8.7
- LTE signal icon, not 4G
- NFC icon on statusbar
- Unbranded, no carrier bloatwares
- Close all button
Firmware version: 23.1.A.1.28_CustomizedPH (new) [05/11/15]
- SuperSU 2.46
- XZDualRecovery 2.8.15
-New close all button (much better)
-Fixed message functionality in Ultra stamina mode
Requirements:
Root with working recovery
How to root? Click here
Installation:
1. Download the ZIP file here:
D6653_23.1.A.1.28_R2C_CustomizedPH
D6653_23.1.A.0.726_R2C_CustomizedPH
2. Copy to Internal or External storage
3. Reboot to recovery
4. Wipe cache, dalvik cache, data (optional/recommended)
5. Flash ZIP from recovery
6. Reboot system and wait for a few minutes
Thanks to zxz0O0, G-FACE and [NUT] for tutorials.
I am the Flash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks.
I was just about to try doing it myself after repeated attempts to download the package from another thread. And this localized for my country, too.
Damn it. I still may end up having to do it on my own. Don't know why Mega is always giving me grief.
Hi, flashed D6603 firmware and can't manage to reboot recovery
Any idea how to proceed as i want to flash this one
Sent from my D6653
scribbclubber said:
Hi, flashed D6603 firmware and can't manage to reboot recovery
Any idea how to proceed as i want to flash this one
Sent from my D6653
Click to expand...
Click to collapse
Download this http://forum.xda-developers.com/attachment.php?attachmentid=3243769&d=1428103729, unzip it on your pc and run the .bat file.
Phone will reboot and you should be able to enter recovery by pressing volume down when the phone starts.
Is there any benefit of returning to your original model? I have a D6653 and been using the D6603 lollipop firmmwares since they came out....
dedei said:
Is there any benefit of returning to your original model? I have a D6653 and been using the D6603 lollipop firmmwares since they came out....
Click to expand...
Click to collapse
I would say that if you have no issues with the version you're using right now, it shouldn't be much different if you switch. In fact, if you're happy with the way things are currently, you should be more worried about accidentally breaking something (if it's not broken, don't fix it and all that)). Then again, you can always flash back to your back-up if things go awry.
Anyway, I dirty flashed this over my previous installation and it looks like everything's as it should be, except for the screen off animation. Or is there really not supposed to be one? I was using Gravity Box for CRT off before but it seems like it had fade before that. Now my screen just... winks out.
Why dont u use recovery 2.8.10?
Awestrike said:
Thanks.
I was just about to try doing it myself after repeated attempts to download the package from another thread. And this localized for my country, too.
Damn it. I still may end up having to do it on my own. Don't know why Mega is always giving me grief.
Click to expand...
Click to collapse
We're on the same country, that's why I flashed it right away
dedei said:
Is there any benefit of returning to your original model? I have a D6653 and been using the D6603 lollipop firmmwares since they came out....
Click to expand...
Click to collapse
My firmware now works better than my previous (D6603) and I can tell the changes. With my new D6653 firmware, my issues were resolved:
- 'No Service' on the lock screen
- X-Reality automatically turns off
- Service Menu is crashing
lemonade747 said:
Why dont u use recovery 2.8.10?
Click to expand...
Click to collapse
I was having some issues with the 2.8.10, so I decided to use 2.8.7 instead (which works fine for me). Anyway you can always update the recovery anytime
Arxelance said:
We're on the same country, that's why I flashed it right away
Click to expand...
Click to collapse
Yeah, I thought so. It would have been unusual to just arbitrarily pick this region, haha.
What screen-off animation came with the firmware? Fade or no animation?
Awestrike said:
Yeah, I thought so. It would have been unusual to just arbitrarily pick this region, haha.
What screen-off animation came with the firmware? Fade or no animation?
Click to expand...
Click to collapse
No animation, even when I used D6603 firmware before. There should be a mod for that, I don't know just how, yet
Arxelance said:
No animation, even when I used D6603 firmware before. There should be a mod for that, I don't know just how, yet
Click to expand...
Click to collapse
That's good then. I was worried something that it was a very minor nit in an otherwise perfect flash.
I'll just have to wait until we have Xposed/Gravity Box again for CRT Off/Fade (and quick unlocK).
Hi mates, Currently my version is 23.0.1.A.5.77 (D6653) and under 4.4.4 newly owned z3 2 days ago, just want to ask if safe to root? I have read about the DRM keys issue. If rooted, warranty will be voided?
appreciate anyone response. kabayan Thanks
framework
Can anyone upload fỏr me the framework_res.apk on this rom ?
Hi
An hour ago I flashed the downloaded Customized PH. 726 from XperiFirm. My fault actually that I just visited XDA and checked out your post after I updated my Z3 D6653. How will I be able to install a recovery on this? I know the works and all but what I'm not certain is, is there a way to install recovery and root the device by not downgrading the OS? Because seriously that's a lot of work starting from downloading everything and flashing files afterwards. I'll wait for your response sir. Thanks and God Bless.
vincer0102 said:
Hi mates, Currently my version is 23.0.1.A.5.77 (D6653) and under 4.4.4 newly owned z3 2 days ago, just want to ask if safe to root? I have read about the DRM keys issue. If rooted, warranty will be voided?
appreciate anyone response. kabayan Thanks
Click to expand...
Click to collapse
PM sent bro
dephia said:
Can anyone upload fỏr me the framework_res.apk on this rom ?
Click to expand...
Click to collapse
Here you go I wonder where you might use it?
Hello
I would really appreciate any response on my above-mentioned query
ronniem18 said:
An hour ago I flashed the downloaded Customized PH. 726 from XperiFirm. My fault actually that I just visited XDA and checked out your post after I updated my Z3 D6653. How will I be able to install a recovery on this? I know the works and all but what I'm not certain is, is there a way to install recovery and root the device by not downgrading the OS? Because seriously that's a lot of work starting from downloading everything and flashing files afterwards. I'll wait for your response sir. Thanks and God Bless.
Click to expand...
Click to collapse
The thing is, there is no exploit yet to get root directly on lollipop. The only working exploit for root is by using giefroot, and sad to say, you need to downgrade your firmware for that.
That's so sad. I actually planned to root my Z3 yesterday while still on KitKat but suddenly Lollipop arrived at XperiFirm and I being excited to see what this version offers just jumped on the idea of updating mY device. Is there a link you can direct me to so I could root this thing? Seriously, finding some ways on Google is wearing me down these days.
ronniem18 said:
That's so sad. I actually planned to root my Z3 yesterday while still on KitKat but suddenly Lollipop arrived at XperiFirm and I being excited to see what this version offers just jumped on the idea of updating mY device. Is there a link you can direct me to so I could root this thing? Seriously, finding some ways on Google is wearing me down these days.
Click to expand...
Click to collapse
Yeah it's here
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Thanks
Arxelance said:
Yeah it's here
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Click to expand...
Click to collapse
Thank you for your help. I'll download everything tonight and start working on it tomorrow. Appreciate your help, buddy.

[ROOT] D6503 Flashable Stock 23.1.A.1.28 Customized UK Latest

So i decided to make a new latest version of the Xperia Z2 (D6503) Firmware included's NUT's latest Locked Recovery v2.8.15 and Chain's SuperSU v2.46 that's all thats been added everything else is the same as my previous firmware which i pre rooted. Screenshot and Links below Enjoy. Welcome Back the close all tab buttons :good: Remember to Wipe Dalvik/Cache
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link Download
Will this work on a Locked Bootloader??... i cant even update my damn phone via pc companion due to no usb 2.0 in my pc haha its saying i cant do it with a usb 3.0 port and so my last resort is to either wait for update via air or flash via FlashTool
Does this work for locked bootloaders?
Also, from which FTF did you create this?
H786 said:
Will this work on a Locked Bootloader??... i cant even update my damn phone via pc companion due to no usb 2.0 in my pc haha its saying i cant do it with a usb 3.0 port and so my last resort is to either wait for update via air or flash via FlashTool
Click to expand...
Click to collapse
Yes it will mines a locked bootloader too.
tamasrepus said:
Does this work for locked bootloaders?
Also, from which FTF did you create this?
Click to expand...
Click to collapse
Yes it will and screenshot below of which one i used.
Thanks so much again for another rooted UK ROM! You make my life so easy!
keyz86 said:
Thanks so much again for another rooted UK ROM! You make my life so easy!
Click to expand...
Click to collapse
No problem :good: glad to be of service.
Thanks
Sent from my D6503 using XDA Free mobile app
dk_chaula said:
Thanks
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
You're welcome
Sorry to be a pain but could you point me to the right direction on how to install this?... im used to installing ftf files but not zip so i dont know exactly what to do xD
H786 said:
Sorry to be a pain but could you point me to the right direction on how to install this?... im used to installing ftf files but not zip so i dont know exactly what to do xD
Click to expand...
Click to collapse
Its just like installing a custom rom yet its not a custom rom just stock with pre root access. if you have rooted before and have twmp or philz touch whiz recovery just install it from the recovery option wiping Dalvik and Cache and then installing this zip then reboot system and you're good to go. shouldn't be hard follow some guides on youtube if you don't know.
what if i have never rooted before?? because ive got a locked bootloader with 100% stock rom and havent flashed any custom stuff... all i did was get the phone from vodafone and then i flashed the uk firmware (same as the one you have minus the root)
H786 said:
what if i have never rooted before?? because ive got a locked bootloader with 100% stock rom and havent flashed any custom stuff... all i did was get the phone from vodafone and then i flashed the uk firmware (same as the one you have minus the root)
Click to expand...
Click to collapse
Well i downgraded mine back to kitkat then root you could try root from this post http://forum.xda-developers.com/xperia-z2/general/root-t3108230
i had to flash 17.1.A.2.55 then run the rootkit from doomlord and then flash your rom via recovery and then voilah xD... lets see how it goes as im just starting the process now
EDIT: installed wrong version haha
Nice work with the Flashable zip.
Apart from the inclusion of the 'clear all recents' button what else is improved upon, or not forgotten, in comparison to the earlier Lollipop updates?
My Z2 is still showing V 23.1.A.0.726 ready for downloading but so far I've resisted this so-called upgrade, its too half-baked. I'm still on KitKat until I get more feedback on this being a better attempt at an upgrade.
What are your impressions so far?
rubiicon59 said:
Nice work with the Flashable zip.
Apart from the inclusion of the 'clear all recents' button what else is improved upon, or not forgotten, in comparison to the earlier Lollipop updates?
My Z2 is still showing V 23.1.A.0.726 ready for downloading but so far I've resisted this so-called upgrade, its too half-baked. I'm still on KitKat until I get more feedback on this being a better attempt at an upgrade.
What are your impressions so far?
Click to expand...
Click to collapse
Well since ive been using it daily I found that the battery has been draining fast soon as I take it off charge its down to 98 percent already I have lollipop ? on my moto g doesn't drain this fast. I was getting issues with keyboard on z2. This seems to fix that bug. Haven't noticed any other changes so far just seems to be minor bug fixes.
H786 said:
i had to flash 17.1.A.2.55 then run the rootkit from doomlord and then flash your rom via recovery and then voilah xD... lets see how it goes as im just starting the process now
EDIT: installed wrong version haha
Click to expand...
Click to collapse
:laugh: good luck
thx for the zip
So, as I understand
move the zip to my sd card,
flash from recovery( my Z2 is 17.1.1.a.0.402 root with dual recovery) the zip and that is?????
nothing else?
Do I need flashtool or everything else?
i am asking bcause I saw other guides that said at the end to flash with flashtool the ftf fimware:
like step 11 at following link:
http://forum.xda-developers.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155
"Never exclude = never check (x) kernel. It is the main reason we're flashing this."
nokian70 said:
Well since ive been using it daily I found that the battery has been draining fast soon as I take it off charge its down to 98 percent already I have lollipop on my moto g doesn't drain this fast. I was getting issues with keyboard on z2. This seems to fix that bug. Haven't noticed any other changes so far just seems to be minor bug fixes.
Click to expand...
Click to collapse
I've noticed when i was using the stock rom (1000000% uk stock with no extras) i could get around 3/4 days battery life which includes having the bluetooth on all day connected to my helmet and sbh52 and after i installed this im getting half that xD....
So the increased battery consumption is another reason to stay away from this. I get plenty of usage on KitKat, thats with BT and Wifi on nearly all of the time.
From all the negative aspects I've read about Lollipop on the Z2 it seems like its anything but an upgrade.

[WARNING] IVY/IVY_DSDS POTENTIAL Encrypted Bootloader in OTA

OKay @MotexT have been looking at the ota package 32.1.A.1.185
I will be quoting heavily from hangout
MotexT
Wow, this is really strange. Looks like new algorithm for OTA
Click to expand...
Click to collapse
Hmm, clarify ?
MotexT
We all know how it works - we have updater-script which contain the algorithm of flashing files, right? Here, if I really got it, we don't have a classical scenario for that, which seems like new way to flash OTA updates
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah, i would reject this ota, but some people are stupid and will flash a can of yams if it's in a zip file
and that's not an exaggeration either
MotexT
All this file is almost about S1 boot security
Click to expand...
Click to collapse
someone actually tried to flash one of the defconfigs i zipped and attached to post
MotexT
Yeah, I remember ?
Click to expand...
Click to collapse
yeah there appears to be hashing functions in the kernel commandline as well
tell me this bootloader is encrypted?
MotexT
New one will be - there are certificates for all version and revisions, and looks like it encrypts the new bootloader after flashing
Checked out the files and yes - it will encrypt bootloader with SHA256 keys
Click to expand...
Click to collapse
Can you post that in a thread please?
MotexT
This file is for the first bootloader version
And it flashes some security into it
Click to expand...
Click to collapse
okay so does this really read as encrypted or signed?
This one is encrypted and checks if encryption was successful
It encrypts
Okay yeah let's upgrade that proposed thread to a warning.
i'm going to quote this hangout heavily so can you leave all those screens accessible?
MotexT
Yep, use them. Also highlight the lines where it's written, hope someone will do deeper research of all that stuff. Also I will add boot folder with all that files
Also it's strange at all - looks like this changes will be applied just after OTA - one guy has flashed new TFT an then he installed your kernel and my recovery and for him everything works well
Click to expand...
Click to collapse
So, I have uploaded the whole folder with this files to my Drive. For everyone who flashed the new version via Flashtool, don't flash any OTAs from Sony cause as @moonbutt74 have described in OP, there is some valuable changes. And yeah, they will still popping-up even if you have the newest version on board.
I don't quite understand what this means actually. I installed via flashtool, then kernel also via flashtool, then TWRP and everything seems fine so far. Anything I shouldn't or can't do now? And should others not update or what? What's going on?
Thanks for you work though!
diemadedrei said:
I don't quite understand what this means actually. I installed via flashtool, then kernel also via flashtool, then TWRP and everything seems fine so far. Anything I shouldn't or can't do now? And should others not update or what? What's going on?
Thanks for you work though!
Click to expand...
Click to collapse
In short, don't flash the ota. The ftf seems fine though with flashtool. and then if i have it right , only flash system .?
For anyone who is intersted in picking up development for this device I am attaching the kernel defconfig extracted from the kernel.elf/sin from the aforementioned firmware release. Linux/arm64 3.10.84
What exactly are the consequences when updating with ota?
What can't I do with an encrypted bootloader?
Yeah, i would reject this ota, but some people are stupid and will flash a can of yams if it's in a zip file
and that's not an exaggeration either
Click to expand...
Click to collapse
Hey! hahaha am sorry about flashing that zip file, no need to say that am a noob, I was thinking that defconfigs file was something like a configuration file for the kernel or somthing.... yeah I know... no need to say that I should not touch advanced tweaks but hey! at least my device is working ok! no bricks (luckily think so), no nuclear explosions they say... all good! thanks four your work again and for share your personal chats haha
lilloscar said:
Hey! hahaha am sorry about flashing that zip file, no need to say that am a noob, I was thinking that defconfigs file was something like a configuration file for the kernel or somthing.... yeah I know... no need to say that I should not touch advanced tweaks but hey! at least my device is working ok! no bricks (luckily think so), no nuclear explosions they say... all good! thanks four your work again and for share your personal chats haha
Click to expand...
Click to collapse
Sorry I know that was a little harsh, but the joke was there, I had to go for it. Kudos on having a sense of humor! :good:
I've done some unbelievably stupid things myself! :silly:
The best one/ top of the list was that the first kernel build and resulting boot.img i ever managed to pack right went wrong when
i edited the updater script in the zip package to write to mmcblk0. Instant brick. xD
sorry noobish question, ive purchased my Xperia Z4 E6553 from second hand (used), and its already upgraded to MM fw.163, i did upgrade from flashtool to fw .185 and the chargind time its very slow,
how i can fix that ?
my bootloader says cant be unlocked cant change the kernel and install twrp
wellison said:
sorry noobish question, ive purchased my Xperia Z4 E6553 from second hand (used), and its already upgraded to MM fw.163, i did upgrade from flashtool to fw .185 and the chargind time its very slow,
how i can fix that ?
my bootloader says cant be unlocked cant change the kernel and install twrp
Click to expand...
Click to collapse
Perhaps you have Find My Xperia ON! You need to turn it off in order to unlock bootloader I had the same problem, give it a try after you disable it, restart the phone and the you go to service menu to see if it allow to unlock the bootloader.
tatomolina11 said:
Perhaps you have Find My Xperia ON! You need to turn it off in order to unlock bootloader I had the same problem, give it a try after you disable it, restart the phone and the you go to service menu to see if it allow to unlock the bootloader.
Click to expand...
Click to collapse
Its fixed my bootloader Status, now i can unlock the bootloader, Thank you !!
Now so boring this charging time its too long about 4 hours to complete charge with stock charger come in the bundle, i already test with other sotck charger and cable, i think its a bug with this new fw MM
wellison said:
Its fixed my bootloader Status, now i can unlock the bootloader, Thank you !!
Now so boring this charging time its too long about 4 hours to complete charge with stock charger come in the bundle, i already test with other sotck charger and cable, i think its a bug with this new fw MM
Click to expand...
Click to collapse
Your welcome hope you root your phone!
Sent from my E6533 using XDA-Developers mobile app
fayer3 said:
What exactly are the consequences when updating with ota?
What can't I do with an encrypted bootloader?
Click to expand...
Click to collapse
I can't see a specific reply to this question by fayer3.
Can anyone spell out the consequences and rollback options for anyone flashing the OTA?
Is this likely to affect ALL future versions from Sony? In that case we should find ways to turn off OTA updates, to minimize the risk.
BR.

Categories

Resources