Related
Can someone direct me to a step by step tutorial on how to root my Xperia X.
Thanks!
Just unlock the bootloader and flash a custom kernel. To unlock just use google and it will take you to sony's unlocking webpage with all the instructions you need, then use a kernel found in this very forum.
Where can I get twrp for f5121?? I have searched for a few days now with no luck......
ghuertasw said:
Where can I get twrp for f5121?? I have searched for a few days now with no luck......
Click to expand...
Click to collapse
Did you find it? If yes, how did you root? Please I need help I am very confused..
Here you can find unofficial twrp for xperia x:
http://www.infectedbuilds.net/downloads/suzu/twrp/
Install with fastboot command:
fastboot flash recovery recovery.img
After flashing this twrp you probably cant access data partion in twrp, to fix this boot into twrp(shut down device and turn it on again holding volume down), do a factory whipe and format data partition.
If you want to root flash latest SuperSU: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you want a modded kernel with DM-verity, RIC off, DRM fix, SuperSU & Busybox download this tool and follow instructions: https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
Doesn't unlocking the bootloader degrade the quality of the camera? I am sure it does but just wanted to be sure. If I do decide to unlock, how can I get similar camera functionality back? I may even simply leave it alone, I just want to get rid of the Facebook app. If there was a generic FTF I could download for the F5121, that might not have that app in it. I remember when I had an Xperia Z, I used a generic FTF and didn't have so much bloatware. I also did not have to unlock the bootloader. All it has to be is for the same phone really and it worked for me.
What works for me might not work for you so try at your own risk.
Root xperia X
Hi, Guys...
I have since dec 16 a sony xperia x. And i need a manual to root my xperia x.
Before i had samsungs galaxy IV rooted, it was top.
My question is get i offical updates if the xperia rooted?
Sorry for my english but its a long time ago to write...
Siggi
siggi77 said:
Hi, Guys...
I have since dec 16 a sony xperia x. And i need a manual to root my xperia x.
Before i had samsungs galaxy IV rooted, it was top.
My question is get i offical updates if the xperia rooted?
Sorry for my english but its a long time ago to write...
Siggi
Click to expand...
Click to collapse
Official updates need the original recovery installed on the phone. ( If TWRP is installed it will fail with an error )
You also need a valid DRM (or a DRM fix) that the Sony update tool will notify you about new firmware updates.
That's what I can tell you from my experiences.
Backup your DRM partition if you decide to unlock your phone!
And don't try to relock the phone as the camera won't work on a locked phone without DRM key. (at least it was like this in my case)
I've updated to 311 using lubik1's rom image without any issues today. It has everything included. (root,drm,etc..)
https://forum.xda-developers.com/xperia-x/development/romubxperia-poison-v1-0-xx-f5121-5122-t3525884
Cheers Bru3
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Gdhgeorge1 said:
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Click to expand...
Click to collapse
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Horst the Animal said:
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
Click to expand...
Click to collapse
Thanks for replying! Yeah, I assumed that would be the case. But I found this post that says I can flash a "drmrestore" zip package so I can simulate that the keys are still there: https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
The thing is, in order to flash it, I need TWRP recovery, right? I have been unable to successfully install TWRP. Is there an easy way to install it?
Thanks again!
harry_turtle said:
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Click to expand...
Click to collapse
Thanks a lot for replying! If I find this post where I can create my own kernel, I will have to unlock the bootloader again and flash the new custom firmware using flashtool, right?
Also, will I have to downgrade to Lollipop, since Nougat is pretty new on Sony phones and there's no drm fix for that?
Thanks again!
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Will try!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
Thank you so, so much! I will try this and report back with my results!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
I apologize for replying with my report this late.
It turns out I re-locked my bootloader in the process when I flashed Android Nougat, since I had bricked it temporarily. To do the procedure you mentioned above, I need to have it un-locked, correct?
If that is the case, when I try to unlock the bootloader, I cannot access fastboot because whenever I press VOL UP key with adb, the light flashes blue and then red and then boots into the OS normally. Same with flashmode (the light turns green, and then red, finally booting into the OS).
Does anyone have a solution for this, please?
Thank you very much!
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
Thank you for your reply, Dean F.
OEM unlocking option and USB debugging were already enabled. It should have technically been working by now. Could it have something to do with some drivers I have to re-install?
It worked!!
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Gdhgeorge1 said:
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Click to expand...
Click to collapse
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Dean F said:
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Click to expand...
Click to collapse
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Gdhgeorge1 said:
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Click to expand...
Click to collapse
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Dean F said:
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Click to expand...
Click to collapse
Excellent, I see now, thanks!
Well, what I wanted before starting the entire process was a permanent root solution, one that would allow me to access features like Root Explorer on ES File Explorer, or extra features in Link2SD and such, when the opportunity arose. That is what I did with all my previous smartphones, even a Sony Z1 Compact, but this has been the hardest phone to root I've ever handled.
After all the trial and error I've faced, I will take your good advice and leave it as is for now. In the future, I will flash the rooted kernel when I need to use those functions, and use the androplus kernel you had sent me previously to get it back to normal.
Thank a bunch again for all your help, Dean F. You revived my phone, so to speak!
Cheers!
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
EDIT:
A few extra tips to help get through the process:
- You will need to install Test-point drivers - can be found by running the Potato program and following the web address to the User Manual - link to drivers is there. (Uninstall drivers when finished or else phone won't be recognized properly by PC later!)
- Open up Device Manager to check that you are booting to TP - devices changes from 'USB SER' to 'USB (COM')' - or something like that, I don't exactly remember!. It might take a few goes to boot into TP - disconnect then reconnect battery each attempt.
Thanks for sharing this program. this works for me, after bricking my phone 2 years ago. I finally got to unlock my bootloader. And its working now and doing great.
Hello,
Does this soft FACTORY RESET after bootloader unlock?
Regards
RJ
tested on huawei p10 vtr-l09 with emui 9.1 and works perfectly, does not erase data or do hard reset, excellent tool ?
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
rafjak said:
Hello,
Does this soft FACTORY RESET after bootloader unlock?
Regards
RJ
Click to expand...
Click to collapse
no friend, i did it and it doesn't factory reset
Hey bro, could you please tell me the steps you made?
I am in emui 9.1 too.
Thanks.
josua19 said:
tested on huawei p10 vtr-l09 with emui 9.1 and works perfectly, does not erase data or do hard reset, excellent tool
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
no friend, i did it and it doesn't factory reset
Click to expand...
Click to collapse
itsjhndnllclrg said:
Thanks for sharing this program. this works for me, after bricking my phone 2 years ago. I finally got to unlock my bootloader. And its working now and doing great.
Click to expand...
Click to collapse
Hi, can you help with the steps please, i'm a newbie at using git.
Never mind, thanks.
HOW TO OPEN PotatoNV.exe
New_ said:
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
Click to expand...
Click to collapse
Hi, please please explain how to run the potato project
found it, please ignore the post
Friends could pass the tutorial video of the TP location
New_ said:
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
EDIT:
A few extra tips to help get through the process:
- You will need to install Test-point drivers - can be found by running the Potato program and following the web address to the User Manual - link to drivers is there. (Uninstall drivers when finished or else phone won't be recognized properly by PC later!)
- Open up Device Manager to check that you are booting to TP - devices changes from 'USB SER' to 'USB (COM')' - or something like that, I don't exactly remember!. It might take a few goes to boot into TP - disconnect then reconnect battery each attempt.
Click to expand...
Click to collapse
I DOWNLOADED THE FILE FROM GIT.. BUT IT DOESNT HAVE BOOTLOADER FILES INCLUDED WHERE CAN I GET?
KIRIN 960 HUAWEI P10,
1. DOWNLOADED THE ZIP FROM GITHUB
2. RUN THE PROGRAM USING VISUAL INSTALLER
3. PUT THE P10 TO TESTPOINT METHOD AND ENABLE HUAWEI COM 1.0
4. PROGRAM ERRORS WHEN LOOKING FOR BOOTLOADER FILES.
where can i get bootloader files ? for kirin 960 i can
Please do you add support for newer Kirin CPUs? Kirin 990 etc...
DasXardas said:
Please do you add support for newer Kirin CPUs? Kirin 990 etc...
Click to expand...
Click to collapse
Err, no. Finding bootloader exploit on newer Kirin's would be like finding Holy Grail.
You could always join 'Big Huawei Exploits' group on Telegram and ask them how it's going rolleyes
New_ said:
Err, no. Finding bootloader exploit on newer Kirin's would be like finding Holy Grail.
You could always join 'Big Huawei Exploits' group on Telegram and ask them how it's going rolleyes
Click to expand...
Click to collapse
Thank you. I'll try them.
Is it possible to unlock bootloader & root phone, which was rebranded with "funky huawei" ?
Huawei P10, from VTR-L09 to VTR-L29
[QUOTE = "New_, publicación: 83667321, miembro: 10899731"]
Grandes hazañas de Huawei
[/CITAR]
Please link
Many thanks, it worked flawlessly on my P10 running EMUI 9.1! Test points and disassembly instructions can easily be found on the interwebs. Do not forget to write down the bootloader unlock code PatatoNV generates: I needed it after I bootlooped and downloaded the latest rom with erecovery.
M1chiel said:
Many thanks, it worked flawlessly on my P10 running EMUI 9.1! Test points and disassembly instructions can easily be found on the interwebs. Do not forget to write down the bootloader unlock code PatatoNV generates: I needed it after I bootlooped and downloaded the latest rom with erecovery.
Click to expand...
Click to collapse
Did you lost the unlocked BL after you dl the latest rom and recovery?
Sterben11 said:
Did you lost the unlocked BL after you dl the latest rom and recovery?
Click to expand...
Click to collapse
I downloaded the latest rom twice through erecovery. The first time it locked my bootloader, but the second time it did not. The first time I could easily unlock again with the code generated by the patatoNV tool.
M1chiel said:
I downloaded the latest rom twice through erecovery. The first time it locked my bootloader, but the second time it did not. The first time I could easily unlock again with the code generated by the patatoNV tool.
Click to expand...
Click to collapse
Ah yes I bricked my phone 2 times already and experienced what erecovery is for. It's my first time to mess with my good ol p10 have you tried any working open kirin custom on it? cuz everytime I flash a 9.0/9.1 compatible rom it ends on bootloop I used adb and fastboot btw. This is my last question sorry a noobie here.
(take note I followed every instructions on their support page on how to flash)
Sterben11 said:
Ah yes I bricked my phone 2 times already and experienced what erecovery is for. It's my first time to mess with my good ol p10 have you tried any working open kirin custom on it? cuz everytime I flash a 9.0/9.1 compatible rom it ends on bootloop I used adb and fastboot btw. This is my last question sorry a noobie here.
(take note I followed every instructions on their support page on how to flash)
Click to expand...
Click to collapse
The AEX roms worked for me, the omniroms unfortunately did not boot (emui 9.1). They are supposed to work on emui 9.0. Did you do the factory reset from emui recovery? AEX is very basic android and quite nice, although not as fluent as emui.
Anyone has had luck getting the Pixel Experience ROM working?
Site can be found here:
https://download.pixelexperience.org/j9110
I am on 8170 and would like to test it out.
Really interested in your feedbacks!
How do we flash it without a working twrp?
https://wiki.pixelexperience.org/devices/j9110/install/
Follow these instructions it should work....
chaitanya.krishna said:
Follow these instructions it should work....
Click to expand...
Click to collapse
...
TrustAugustus said:
How do we flash it without a working twrp?
Click to expand...
Click to collapse
Instructions do not Help if there is no way to follow them. Just use GSIs... There is also a Pixel Expierence One around...
joeminati said:
Anyone has had luck getting the Pixel Experience ROM working?
Site can be found here:
https://download.pixelexperience.org/j9110
I am on 8170 and would like to test it out.
Click to expand...
Click to collapse
I tried the June and July builds on my Dual SIM J9110. They are constantly improving so some things that I mention below may have changed. The SODP guys working on it are awesome.
The builds worked well for the most part, performance is not quite as good as stock, there are some stutters and frame drops, but it's still daily driver material.
Some things to keep in mind:
-There is no Dolby Audio. Volume from the speakers is slightly lower than stock.
-The display runs in always 4K mode, it looks great. Doesn't have a huge effect on battery life either.
-The notification LED only displays one colour, which is sort of a bluey-white.
-You have to use Raizen's HyperCam build for photos. A little bit of tweaking within the app and it takes fantastic photos. Supports all 3 cameras as well.
-It will not have any proprietary Sony features like Battery Care.
For flashing you have to use Payload_Dumper on the payload.bin file included within the ROM zip. It will give you dtbo.img, boot.img, system.img, vendor.img and so on.
First make sure you're on the latest Android 10 (55.1.x) firmware on both A and B slots. You can use NewFlasher to flash, and fastboot to switch between slots.
Then flash the latest Sony Open Device Binaries for Kumano (Xperia 1 / Xperia 5) which you can get from here:
https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
Then flash dtbo, boot and vendor. Then boot into AOSP recovery with Power + Vol down. From there you can use adb sideload to install the ROM .zip file and your phone will reboot into PE.
If it bootloops, run fastboot format userdata or boot back into AOSP recovery and do a factory reset.
For updates, it does support OTAs since the device is officially supported by PE and hosted on their servers.
@MeltdownSpectre
Thanks for the info! I'm definitely going to try it.
Would you mind pointing me to the exact hypercam raizen file
TrustAugustus said:
@MeltdownSpectre
Thanks for the info! I'm definitely going to try it.
Would you mind pointing me to the exact hypercam raizen file
Click to expand...
Click to collapse
Here you go:
https://f.celsoazevedo.com/file/cfiles/gcm1/HyperCam-RaizenA-10.apk
MeltdownSpectre said:
Here you go:
https://f.celsoazevedo.com/file/cfiles/gcm1/HyperCam-RaizenA-10.apk
Click to expand...
Click to collapse
Thanks! It doesn't work with stock Sony. Is that normal?
I realized that the ROM is for the DSDS. I have the 802SO version. I wonder if I'll end up borking the phone.
TrustAugustus said:
Thanks! It doesn't work with stock Sony. Is that normal?
I realized that the ROM is for the DSDS. I have the 802SO version. I wonder if I'll end up borking the phone.
Click to expand...
Click to collapse
Not sure if 802SO is supported.
Yes it's normal for it to not work with stock ROM.
MeltdownSpectre said:
I tried the June and July builds on my Dual SIM J9110. They are constantly improving so some things that I mention below may have changed. The SODP guys working on it are awesome.
The builds worked well for the most part, performance is not quite as good as stock, there are some stutters and frame drops, but it's still daily driver material.
Some things to keep in mind:
-There is no Dolby Audio. Volume from the speakers is slightly lower than stock.
-The display runs in always 4K mode, it looks great. Doesn't have a huge effect on battery life either.
-The notification LED only displays one colour, which is sort of a bluey-white.
-You have to use Raizen's HyperCam build for photos. A little bit of tweaking within the app and it takes fantastic photos. Supports all 3 cameras as well.
-It will not have any proprietary Sony features like Battery Care.
For flashing you have to use Payload_Dumper on the payload.bin file included within the ROM zip. It will give you dtbo.img, boot.img, system.img, vendor.img and so on.
First make sure you're on the latest Android 10 (55.1.x) firmware on both A and B slots. You can use NewFlasher to flash, and fastboot to switch between slots.
Then flash the latest Sony Open Device Binaries for Kumano (Xperia 1 / Xperia 5) which you can get from here:
https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
Then flash dtbo, boot and vendor. Then boot into AOSP recovery with Power + Vol down. From there you can use adb sideload to install the ROM .zip file and your phone will reboot into PE.
If it bootloops, run fastboot format userdata or boot back into AOSP recovery and do a factory reset.
For updates, it does support OTAs since the device is officially supported by PE and hosted on their servers.
Click to expand...
Click to collapse
Thanks for Your Post! Is there any reason for flashing the ZIP again after flashing it already via Fastboot? Sounds more Like a Option for coming Updates (I hope update.zip Files Work from the Storage too?). Great to have at least a stable Recovery Base!
Miustone said:
Thanks for Your Post! Is there any reason for flashing the ZIP again after flashing it already via Fastboot? Sounds more Like a Option for coming Updates (I hope update.zip Files Work from the Storage too?). Great to have at least a stable Recovery Base!
Click to expand...
Click to collapse
The developers had given me these flashing instructions. We only flash dtbo, boot and vendor first. Then sideloading the zip flashes them again, as well as flashing system.img which was not flashed through fastboot.
I'm using this build now, everything works fine. But the animation seems not very smooth,a little lag
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40
what variant support by PE rom?
JOKER.SOHA said:
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40
what variant support by PE rom?
Click to expand...
Click to collapse
PE supports J8110 (single SIM) and J9110 (dual SIM).
i have no mobile data.
no SIM detected.
i have no mobile data.
no SIM detected.
the camera is very poor, almost cannot use, even scan a qrcode is difficult
Sketch. said:
I'm using this build now, everything works fine. But the animation seems not very smooth,a little lag
Click to expand...
Click to collapse
camera is not function as better as the stock one
Here was a Guide. Someone said people don't care about Me or My Work so...
Welcome to the Family Xperia 5 Mark II Users <3
Thanks. Looks like it is the same procedure like 1-ii 10-ii.
I know this is obvious, but in case someone forgets, remember to unlock bootloader, you need to unlock "developer options" by tapping the "build number" 10 times in settings>about phone, turn on "OEM unlocking" in system>developer options.
Miustone said:
[*]-Start the NewFlasher.exe, Select: f, n, n, y (fastboot, no, no, yes) in the Prompt Window
Click to expand...
Click to collapse
Not too sure what is this step for?
Unlocking bootloader on these newer Xperia devices doesn't bring the same limitations to the camera as the old days, does it?
Kocane said:
Unlocking bootloader on these newer Xperia devices doesn't bring the same limitations to the camera as the old days, does it?
Click to expand...
Click to collapse
It clearly disables still the Display Enhancement known as Video Optimization, besides that may it mean You can't play 4K HDR anymore over Netflix, limiting it to FHD/HD Playback. Additional will You not being able to use the Xperia Services anymore which shouldn't hurt anyone. With My MARS_SOM can You get even better Display Optimizations combined with 4K HDR Playback on all possible apps. Still searching a Tester on the Xperia 5 II for it actually...
Updated the Guide
Respect for all your effort, thank you very much!
Any way to revert back after this? How to relock bootloader?
Xperia Companion won't repair since the bootloader is unlocked and Xperia Flash Tool (Emma) gives me an error (screenshot) and FlashTool doesn't support Xperia 5 II yet.
Miustone said:
It clearly disables still the Display Enhancement known as Video Optimization, besides that may it mean You can't play 4K HDR anymore over Netflix, limiting it to FHD/HD Playback. Additional will You not being able to use the Xperia Services anymore which shouldn't hurt anyone. With My MARS_SOM can You get even better Display Optimizations combined with 4K HDR Playback on all possible apps. Still searching a Tester on the Xperia 5 II for it actually...
Click to expand...
Click to collapse
Thanks. Does this include creator mode?
vyp54 said:
Any way to revert back after this? How to relock bootloader?
Xperia Companion won't repair since the bootloader is unlocked and Xperia Flash Tool (Emma) gives me an error (screenshot) and FlashTool doesn't support Xperia 5 II yet.
Click to expand...
Click to collapse
"fastboot oem lock" locks the Bootloader again. Just use the Companion to repair after that. Never use Flashtool on newer Devices (2019+), just use NewFlasher and Fastboot. That's the failsafe way...
@Kocane it isn't a DRM Bypass, so No. But it enables 4K Playback and various Pixel 4 XL and Qualcomm configs that enhance the Display on other Ways like Automated Whitebalance, variable vsync and more. The actual GitHub Versions are pretty neat actually in that view...
Miustone said:
"fastboot oem relock" locks the Bootloader again. Just use the Companion to repair after that. Never use Flashtool on newer Devices (2019+), just use NewFlasher and Fastboot. That's the failsafe way...
@Kocane it isn't a DRM Bypass, so No. But it enables 4K Playback and various Pixel 4 XL and Qualcomm configs that enhance the Display on other Ways like Automated Whitebalance, variable vsync and more. The actual GitHub Versions are pretty neat actually in that view...
Click to expand...
Click to collapse
"fastboot oem lock" and 7 seconds of waiting did the charm. Thanks!
!
@Miustone, thanx for your help here.can you tell me what I should choice on Sony Website for unlocking BL ? xperia 5 ii doesn't exist...thanx
Does relocking the bootloader and repairing via companion put the device back to a factory state with the DRM keys etc for 4k playback?
Just want to make sure before I break something I can't fix…
Thanks!
Couldn't make this work, tried several times only got either a boot loop or a message saying that android couldn't boot so I had to either try again or do a full wipe. Any idea?
snikica00 said:
@Miustone, thanx for your help here.can you tell me what I should choice on Sony Website for unlocking BL ? xperia 5 ii doesn't exist...thanx
Click to expand...
Click to collapse
Not Sure, i think other Xperia 5 II User will know how since some are unlocked yet If i'm Not wrong
nanu*1 said:
Does relocking the bootloader and repairing via companion put the device back to a factory state with the DRM keys etc for 4k playback?
Just want to make sure before I break something I can't fix…
Thanks!
Click to expand...
Click to collapse
Yes. That is the Case since the 2019 Xperia Lineup. No worries!
warrip said:
Couldn't make this work, tried several times only got either a boot loop or a message saying that android couldn't boot so I had to either try again or do a full wipe. Any idea?
Click to expand...
Click to collapse
You should reflash the Stock Firmware with newflasher before trying again. Take a look If it boots untouched and Install the Magisk Manager again (to make sure the Firmware is ok)
Have You also did the vbmeta step? You could try to skip that step if You tried it with...
You could also try to Patch the Boot Image with Magisk 21.X. Just Go in the Magisk Manager to the Settings and select the Beta Channel. Go Back to the Main Page for patching and Patch your Image with the 21.X Beta version.
Hope that helps!
Miustone said:
Not Sure, i think other Xperia 5 II User will know how since some are unlocked yet If i'm Not wrong
Yes. That is the Case since the 2019 Xperia Lineup. No worries!
You should reflash the Stock Firmware with newflasher before trying again. Take a look If it boots untouched and Install the Magisk Manager again (to make sure the Firmware is ok)
Have You also did the vbmeta step? You could try to skip that step if You tried it with...
You could also try to Patch the Boot Image with Magisk 21.X. Just Go in the Magisk Manager to the Settings and select the Beta Channel. Go Back to the Main Page for patching and Patch your Image with the 21.X Beta version.
Hope that helps!
Click to expand...
Click to collapse
What does your ROM/Magisk patch include/do?? Thank you for the guide mate!
Miustone said:
Not Sure, i think other Xperia 5 II User will know how since some are unlocked yet If i'm Not wrong
Yes. That is the Case since the 2019 Xperia Lineup. No worries!
You should reflash the Stock Firmware with newflasher before trying again. Take a look If it boots untouched and Install the Magisk Manager again (to make sure the Firmware is ok)
Have You also did the vbmeta step? You could try to skip that step if You tried it with...
You could also try to Patch the Boot Image with Magisk 21.X. Just Go in the Magisk Manager to the Settings and select the Beta Channel. Go Back to the Main Page for patching and Patch your Image with the 21.X Beta version.
Hope that helps!
Click to expand...
Click to collapse
So you don't need to backup the DRM Key like the old models Z3 / Z5 to gain back the functions?
I can't figure out how to unlock this device? '
I've followed the instructions here: https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/
But running: "fastboot oem unlock 0x[unlock code]" results in:
FAILED (Write to device failed (no link))
fastboot: error: Command failed
Any idea what I could be doing wrong?
5 ii dont have 4k res anyway. I think I will keep it unlocked like 10 ii. It will get downsampled anyway.
GnaXi said:
I can't figure out how to unlock this device? '
I've followed the instructions here: https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/
But running: "fastboot oem unlock 0x[unlock code]" results in:
FAILED (Write to device failed (no link))
fastboot: error: Command failed
Any idea what I could be doing wrong?
Click to expand...
Click to collapse
No link can be either not in fastboot (insert usb while holding vol up, have blue led) or no driver or not in Windows 10 test mode.
Also, have you enable "OEM unlocking" in options?
---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------
Miustone said:
[*]-Start the NewFlasher.exe, Select: f, n, n, y (fastboot, no, no, yes) in the Prompt Window
Click to expand...
Click to collapse
Can you tell me a bit more about this step? I am not sure what it is trying to do.
I also tried relock and doing the unlock without newflasher at all and still works.
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
snikica00 said:
@Miustone, thanx for your help here.can you tell me what I should choice on Sony Website for unlocking BL ? xperia 5 ii doesn't exist...thanx
Click to expand...
Click to collapse
The code for 5 ii is the same for 1 ii or 10 ii.
As far as I remember, unlocking bootloader does not wipe the DRM key nowadays, right? Locking back the bootloader everything will become brand-new?