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?
Related
I'm noticing in the new Japanese Sony models that you are no longer able to flash International firmwares. Has anyone found a method to do this or even root? Bootloader is unlockable on these as far as I know unless I"m missing that method as well.
someone asked about going from INT'L to JAP, and I told them if they had the voice codecs, everything should still work - just going by the AOSP source.
Have you tried using Flashtool to see if you can flash the international model ftf?
NeoBeum said:
someone asked about going from INT'L to JAP, and I told them if they had the voice codecs, everything should still work - just going by the AOSP source.
Have you tried using Flashtool to see if you can flash the international model ftf?
Click to expand...
Click to collapse
I have. This is generally what I do with these. Currently I'm working with the SO-02H and SO-04H. Both of these fail at system.sin or any other sin for that matter. The SO-04H gets the require script error on some of the FTFs. I've done a lot of these in the past with no issues, but I'm not sure what would keep the FTF from even being flashed.
insanecain said:
I have. This is generally what I do with these. Currently I'm working with the SO-02H and SO-04H. Both of these fail at system.sin or any other sin for that matter. The SO-04H gets the require script error on some of the FTFs. I've done a lot of these in the past with no issues, but I'm not sure what would keep the FTF from even being flashed.
Click to expand...
Click to collapse
I haven't tried this myself - but if that happened to me - I would've experimented with swapping the system.sin when Flashtool finishes the prepare. Maybe some of the Google Core apps are incompatible in the new release.
See if you can find anything here http://files.setool.net/support/SETool2/
I dont think setool supports anything newer. I've actually not thought of swapping, didnt know that was an option lol.
swapping system.sin still fails
Have a look in the update.xml or boot.xml in the prepared folder and see if you can find any matching .sin, and maybe you could cook your own ftf. it's probably getting too complicated and you may as well root.
edit: I was in the middle of shredding a system.sin I mounted in to ubuntu, and that's when I said... screw it, I'll learn gooble repo and make AOSP
NeoBeum said:
Have a look in the update.xml or boot.xml in the prepared folder and see if you can find any matching .sin, and maybe you could cook your own ftf. it's probably getting too complicated and you may as well root.
edit: I was in the middle of shredding a system.sin I mounted in to ubuntu, and that's when I said... screw it, I'll learn gooble repo and make AOSP
Click to expand...
Click to collapse
I would love to root. These damn things have locked bootloaders. I have created my own FTF but still same results (I'm sure I got something off).. definitely not new to the phone game, but very little experience with Sony.
insanecain said:
I would love to root. These damn things have locked bootloaders. I have created my own FTF but still same results (I'm sure I got something off).. definitely not new to the phone game, but very little experience with Sony.
Click to expand...
Click to collapse
Is the 'Bootloader Unlock Allowed' set 'NO' and 'OEM unlocking' greyed out in Dev options? If not - maybe could write a batch file for the cmd prompt to do a brute force
Code:
'fastboot -i 0x0fce oem unlock 0xYOURawesomebatchscript'
NeoBeum said:
Is the 'Bootloader Unlock Allowed' set 'NO' and 'OEM unlocking' greyed out in Dev options? If not - maybe could write a batch file for the cmd prompt to do a brute force
Code:
'fastboot -i 0x0fce oem unlock 0xYOURawesomebatchscript'
Click to expand...
Click to collapse
Bootloader Unlock Allowed is set to No, but weirdly I can set OEM unlocking in Dev options (even though it seems pointless).
insanecain said:
Bootloader Unlock Allowed is set to No, but weirdly I can set OEM unlocking in Dev options (even though it seems pointless).
Click to expand...
Click to collapse
try and brute force then
I have this model. Is there any progress? I'm dying to root this phone
I would take this is a no go for this Japan model.
x.navvvy said:
I have this model. Is there any progress? I'm dying to root this phone
Click to expand...
Click to collapse
SAME DUDE.
I need help to root m sony z5 compact E5823!! Pls
Z5 compact docomo apdate oreo
can anyone help to open frp xperia z5 compact so-02h docomo
vale888 said:
can anyone help to open frp xperia z5 compact so-02h docomo
Click to expand...
Click to collapse
Still no progress?
Any progress rooting so-02h??
Any progress rooting so-02h? ver 32.3.E.0.148 ?
Unlocking the bootloader is possible with the xz1? Because here the xz1 is not listed.
https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
You can do this, but you can't backup the DRM keys before. After opening the bootloader the keys get lost and no solution the restore these after closing the bootloader.
You got me wrong, I wanted to know if there is a way to unlock, there is no support from Sony for it like for other xperias. I don't care for DRM.
Got a point. Cant see any entry naming xz/s/premium/1 eventough its an open device. Im gonna search the "Web"
---------- Post added at 02:16 AM ---------- Previous post was at 02:10 AM ----------
Ive chosen xz and got a code. I did not try to unlock but you can try
Just use xz it's work ! (tested on XZ1c)
pierreem said:
Just use xz it's work ! (tested on XZ1c)
Click to expand...
Click to collapse
And you rooted it?
I've build aosp userdebug from sony repo, so yes, it's rooted. (i did not use it has personal phone)
pierreem said:
Just use xz it's work ! (tested on XZ1c)
Click to expand...
Click to collapse
I used XZ Premium unlock för my XZ1 Dual Sim. All OK
I'm on FW 47.1.A.5.51
I have not rooted it yet, since the only way seems to build yourself, either complete rom or magisk. Maybe I try to fix root though MAGisk one of those days, doen´s seems too hard (see here). My problem is I don't know how to get a stock boot image dump of the 47.1.A.5.51 firmware. In the domnloaded ROM there is only a lot of .sin-files. I do not know how to build a boot.img(.tar) out of it and I don't know how to extract it from my phone without root
Since I lost DRM keys, the camera takes green pictures.
The front camera works in manual mode if HDR is enabled in camera settings.
The back camera does not work and XZ solution with google camera
doesn´t work for back camera (front camera work with google camera version 4.3.016.147548696, but I rather use sony stock with HDR ON)
I have not tested Snap Camera HDR
I found a free camera where everything seems to work, both cameras and both pictures and video. Footej Camera
Apps using camera functionallity does not work. both cameras give green pictures
Status right now.
BL unlocked
No root method known (closes at hand through magisk)
Stock camera works with HDR enabled
Back camera takes green pictures, no known solution
pergoteborg said:
I used XZ Premium unlock för my XZ1 Dual Sim. All OK
I'm on FW 47.1.A.5.51
...
My problem is I don't know how to get a stock boot image dump of the 47.1.A.5.51 firmware. In the domnloaded ROM there is only a lot of .sin-files. I do not know how to build a boot.img(.tar) out of it and I don't know how to extract it from my phone without root
...
Click to expand...
Click to collapse
Look here.
Or here.
pbarrette said:
Look here.
Or here.
Click to expand...
Click to collapse
I've seen this and I suppose I should extract kernel.sin, but whatabout the ramdisk that´s normally in a boot image?
I just haven´t dared yet since I´m scared to brick my phone if I get the boot image wrong
pergoteborg said:
I've seen this and I suppose I should extract kernel.sin, but whatabout the ramdisk that´s normally in a boot image?
I just haven´t dared yet since I´m scared to brick my phone if I get the boot image wrong
Click to expand...
Click to collapse
Once you extract the kernel SIN file, you'll see that it's a standard Android boot image.
You can work with it using the normal tools.
pbarrette said:
Once you extract the kernel SIN file, you'll see that it's a standard Android boot image.
You can work with it using the normal tools.
Click to expand...
Click to collapse
Ok, I got a boot.img extracted from my kernel.sin
I patch in Magisk in it according to this post
I tried both last stable v14.0 and lastest expremental v14.5
When I flash the pached result, the v14.0 version halts on boot at sony logo and the v14.5 bootloops
Fortunately flashing the original boot.img I initially extracted brings my phone back to life.
It seems to me that Magisk simply doesn't work for XZ1 dual.
Hello all I have the Xperia X, it is not my first time that I buy an Xperia and since a i am a guy that in the past has a Nexus devices I like to test ROMs.
To the point before I unlocked the bootloader I see some videos and I read some threads for the DRM keys back up. I do the back up with tool V2 all good the img file is 2mb etc , my problem is that I can't understand the process to restore it, in Nexus devices was more simple they don't have T_A keys.
I read again some threads but I can't understand the exactly command's all the times that I try from some pages the command list the ADB fails!!
Any one that can explain me steep by steep?
B a s i c s
FIRST OF ALL
it was WISE of you to inquire before even touching the bootloader .
xperia is the apple of Android,
literature
first step, understanding the TRICKY world of SONY
https://forum.xda-developers.com/showpost.php?p=76429289&postcount=7 (preface)
what do u need???
https://forum.xda-developers.com/showpost.php?p=76432787&postcount=12
what you should do ?
D-R-I-V-E-R-S
ON WINDOWS X64 PC (ONLY)
1. install xperia companion
2. install flashtool (www.flashtool.net)
3.A after installation flashtool, goto C:\Flashtool\Drivers and there will be one setupfile call DRIVERS, Run it and check all checkboxes ( for you i would say check all) and proceed. The process will take a while and all motherboard drivers will be installed)
3B. IF you are on win10 THEN no3 will fail and you wont able to install drivers! .. hence.. YOU MUST DISABLE DIGITAL SIGNATURE VERIFICATION ( google this, it whole separate method! )
3C, if you are on win7 x64 then you will keep getting this POPUP for digital signature verification warning , INSTALL ANWAYS.
4. install minimal adb and fastboot CLICK HERE
EXTRACTING TA.IMG / DRM KEYS / USING TA_BACKUP AKA DIRTYCOW SCRIPT
1. MAKE sure xperia x is on android 6.0.1 if not then flash it, HOW ? READ HERE
2. EXTRACT TA-BACKUP TOOL ON DESKTOP AND . enable USB debugging in X and run the bat file. download the script from HERE
3. you can run the script multiple times and it will extract same key file timestamped in the same folder on desktop! now you have your TA.IMG
UNLOCKING BOOTLOADER
1. VISIT UNLOCK CODE PAGE ON SONY WEBSITE and select X and give your valid email ID and IMEI number
2. sony will send you an email with your UNLOCK CODE
3. I use flashtool, simply connect your device in FASTBOOT MODE (blue LED) and click "BLU" on flashtool and enter the CODE
4. SONY WILL JERK , restart, ANDROID BOT WILL APPEAR to WIPE your TA PARTITION (DRM KEYS), DATA PARTITION, AND INTERNAL STORAGE PARTITION , so you will LOOSE ALL THE DATA ( i hope you have backup)
5. on every restart, THIS DEVICE CANNOT BE TRUSTED warning will start appearing .
NOW WHAT?
1. its your choice to stay on android 6 or upgrade to 7 or 8
2. you must now use modified kernel in order to mock drm keys and root xperia x
3. you can obtain all that from my post ( CLICK HERE ) PLEASE READ CAREFULLY
----------------------------------------
1. FLASHTOOL comes with XPERIFIRM (last icon xp )
2. Xperifirm offers latest & the very first stockrom on which all sony devices left factory
3. the best tool to download sony stockroms! select 2016 devices, select SUZU and its variant and see the countries v/s builds offered . latest OREO build for X is 34.4.A.2.70. Take the German Customised and download
4. ONCE DOWNLOADED close download window and xperifirm. FLASHTOOL will start compiling the downloaded chunk of data from "C:\Users\<user>\.flashTool\firmwares\Downloads" to ONE .FTF FILE (2.7gb). it will prompt u something about fcs script , click YES or OK (i don't remember which one it is ) and let flashtool create the bundle at "C:\Users\<user>\.flashTool\firmwares"
5. once you have the ftf file , you can DELETE the contents inside "C:\Users\<user>\.flashTool\firmwares\Downloads" to save disk space.
6. NOW YOU ARE READY TO FLASH THIS VERSION OF STOCKROM TO YOU XPERIA X
7. PLEASE GOOGLE THE FLASHING GUIDE , i am bit lazy here to xplain since i has been already done many times
please do let me know in case of any guidance
if you like you may join our whatsapp group too ( click here )
YasuHamed said:
FIRST OF ALL
it was WISE of you to inquire before even touching the bootloader .
xperia is the apple of Android,
literature
first step, understanding the TRICKY world of SONY
https://forum.xda-developers.com/showpost.php?p=76429289&postcount=7 (preface)
what do u need???
https://forum.xda-developers.com/showpost.php?p=76432787&postcount=12
what you should do ?
D-R-I-V-E-R-S
ON WINDOWS X64 PC (ONLY)
1. install xperia companion
2. install flashtool (www.flashtool.net)
3.A after installation flashtool, goto C:\Flashtool\Drivers and there will be one setupfile call DRIVERS, Run it and check all checkboxes ( for you i would say check all) and proceed. The process will take a while and all motherboard drivers will be installed)
3B. IF you are on win10 THEN no3 will fail and you wont able to install drivers! .. hence.. YOU MUST DISABLE DIGITAL SIGNATURE VERIFICATION ( google this, it whole separate method! )
3C, if you are on win7 x64 then you will keep getting this POPUP for digital signature verification warning , INSTALL ANWAYS.
4. install minimal adb and fastboot CLICK HERE
EXTRACTING TA.IMG / DRM KEYS / USING TA_BACKUP AKA DIRTYCOW SCRIPT
1. MAKE sure xperia x is on android 6.0.1 if not then flash it, HOW ? READ HERE
2. EXTRACT TA-BACKUP TOOL ON DESKTOP AND . enable USB debugging in X and run the bat file. download the script from HERE
3. you can run the script multiple times and it will extract same key file timestamped in the same folder on desktop! now you have your TA.IMG
UNLOCKING BOOTLOADER
1. VISIT UNLOCK CODE PAGE ON SONY WEBSITE and select X and give your valid email ID and IMEI number
2. sony will send you an email with your UNLOCK CODE
3. I use flashtool, simply connect your device in FASTBOOT MODE (blue LED) and click "BLU" on flashtool and enter the CODE
4. SONY WILL JERK , restart, ANDROID BOT WILL APPEAR to WIPE your TA PARTITION (DRM KEYS), DATA PARTITION, AND INTERNAL STORAGE PARTITION , so you will LOOSE ALL THE DATA ( i hope you have backup)
5. on every restart, THIS DEVICE CANNOT BE TRUSTED warning will start appearing .
NOW WHAT?
1. its your choice to stay on android 6 or upgrade to 7 or 8
2. you must now use modified kernel in order to mock drm keys and root xperia x
3. you can obtain all that from my post ( CLICK HERE ) PLEASE READ CAREFULLY
----------------------------------------
1. FLASHTOOL comes with XPERIFIRM (last icon xp )
2. Xperifirm offers latest & the very first stockrom on which all sony devices left factory
3. the best tool to download sony stockroms! select 2016 devices, select SUZU and its variant and see the countries v/s builds offered . latest OREO build for X is 34.4.A.2.70. Take the German Customised and download
4. ONCE DOWNLOADED close download window and xperifirm. FLASHTOOL will start compiling the downloaded chunk of data from "C:\Users\<user>\.flashTool\firmwares\Downloads" to ONE .FTF FILE (2.7gb). it will prompt u something about fcs script , click YES or OK (i don't remember which one it is ) and let flashtool create the bundle at "C:\Users\<user>\.flashTool\firmwares"
5. once you have the ftf file , you can DELETE the contents inside "C:\Users\<user>\.flashTool\firmwares\Downloads" to save disk space.
6. NOW YOU ARE READY TO FLASH THIS VERSION OF STOCKROM TO YOU XPERIA X
7. PLEASE GOOGLE THE FLASHING GUIDE , i am bit lazy here to xplain since i has been already done many times
please do let me know in case of any guidance
if you like you may join our whatsapp group too ( click here )
Click to expand...
Click to collapse
1st of all thanks a lot for all this information and for the fast repont!!
2on yea now I see that Sony is the Apple Android, it have many staff to learn before touch the bootloader, but I thought cose of Sony Xperia open source project that was be easier that any other company!! Ok I will check all this information to my home!!
I have downloaded all the Xperia tool's form the 1st place!
. And finally I will report you what happen when I finish!!
bromoxitos said:
1st of all thanks a lot for all this information and for the fast repont!!
2on yea now I see that Sony is the Apple Android, it have many staff to learn before touch the bootloader, but I thought cose of Sony Xperia open source project that was be easier that any other company!! Ok I will check all this information to my home!!
I have downloaded all the Xperia tool's form the 1st place!
. And finally I will report you what happen when I finish!!
Click to expand...
Click to collapse
the devil is in the details where SONY Xperias are concern.
for SONY, Open Project means THE DEVICE IS NO LONGER SONY AND NOW YOU HAVE TO BUILD YOUR OWN OPERATING SYSTEM.
Once BOOT is UNLOCKED , for sony it means DIVORCE
you can always try third party roms , currently we have only 2 or 3 (Omnirom, PanAndroid and XGen) Xgen is prerooted modifed SONY STOCKROM ( I am using XGEN)
Yes sir, there is alot to be be learned just on the are of how to baby sit Xperia , the method of ROOTING, Flashing Twrp and finding right kernels/modes is WHOLE different world. we will come to it once you have your TA.IMG and you unlock your bootloader
YasuHamed said:
the devil is in the details where SONY Xperias are concern.
for SONY, Open Project means THE DEVICE IS NO LONGER SONY AND NOW YOU HAVE TO BUILD YOUR OWN OPERATING SYSTEM.
Once BOOT is UNLOCKED , for sony it means DIVORCE
you can always try third party roms , currently we have only 2 or 3 (Omnirom, PanAndroid and XGen) Xgen is prerooted modifed SONY STOCKROM ( I am using XGEN)
Yes sir, there is alot to be be learned just on the are of how to baby sit Xperia , the method of ROOTING, Flashing Twrp and finding right kernels/modes is WHOLE different world. we will come to it once you have your TA.IMG and you unlock your bootloader
Click to expand...
Click to collapse
Well I see!!
1st I want to say that I use the same room with you because it have DRM restore key's and I am happy with that!! It is a very good stock ROM with nice features.
2on I try custom ROMs but the biggest problem for me is that finger print reader does not work properly!! So now I have the xgen ROM. But I supposed that for now is better to return in-stock locked bootloader until a good aosp ROM works properly!! That's way I need to understand how I can restore my DRM key's!!
bromoxitos said:
Well I see!!
1st I want to say that I use the same room with you because it have DRM restore key's and I am happy with that!! It is a very good stock ROM with nice features.
2on I try custom ROMs but the biggest problem for me is that finger print reader does not work properly!! So now I have the xgen ROM. But I supposed that for now is better to return in-stock locked bootloader until a good aosp ROM works properly!! That's way I need to understand how I can restore my DRM key's!!
Click to expand...
Click to collapse
1. thank you, you are most welcome
2. Xgen is modded Stockrom, working okay for now! but cant be 100% substitute of actual stockrom
3. please see this guide about RESTORING DRMKEYS! the only way is to relock your bootloader!
YasuHamed said:
1. thank you, you are most welcome
2. Xgen is modded Stockrom, working okay for now! but cant be 100% substitute of actual stockrom
3. please see this guide about RESTORING DRMKEYS! the only way is to relock your bootloader!
Click to expand...
Click to collapse
Thanks a lot again for all this informations!!! ???????
after i give the 2on command it says permition denied it is normal or i must do something else!!
(adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA)
bromoxitos said:
after i give the 2on command it says permition denied it is normal or i must do something else!!
(adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72152006&postcount=166
Is that what you are also trying to do! ?
YasuHamed said:
https://forum.xda-developers.com/showpost.php?p=72152006&postcount=166
Is that what you are also trying to do! ?
Click to expand...
Click to collapse
No I find an other thread that is like this.. I will try to reading again and see what i done wrong!!!
YasuHamed said:
https://forum.xda-developers.com/showpost.php?p=72152006&postcount=166
Is that what you are also trying to do! ?
Click to expand...
Click to collapse
I try to go back to stock with lock boot loader, no reason to stay with unlock finally!!
Put I can't understand why it not let me go to flaah it!
bromoxitos said:
I try to go back to stock with lock boot loader, no reason to stay with unlock finally!!
Put I can't understand why it not let me go to flaah it!
Click to expand...
Click to collapse
the RELOCKING is same way thats explained in the post for XZ, i never relocked it so i dont know why its not working for you.
also, please understand that SONY has made sure NO TURNING BACK POLICY from 2018. once unlocked you can never go back
so it was with 2016 device only where bootlock can be toggled! .
meaning?
if you have xzp today! you can never relock it! it will stay unlocked forever!
YasuHamed said:
the RELOCKING is same way thats explained in the post for XZ, i never relocked it so i dont know why its not working for you.
also, please understand that SONY has made sure NO TURNING BACK POLICY from 2018. once unlocked you can never go back
so it was with 2016 device only where bootlock can be toggled! .
meaning?
if you have xzp today! you can never relock it! it will stay unlocked forever!
Click to expand...
Click to collapse
Well yes I see but I have Xperia x, that's I will stay in custom stock ROM!! Thanks a lot for the Replay!!!
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.
The presented files for root in the official firmware f800 * Android 9. Based on the official sources PIE of the LG with minimal changes (fixed static boot ).
Only for F800 * phones with unlocked bootloader.
Small manual
LGup firmware in "partition dl" mode KDZ android 9, remove daws aboot, abootbak, laf ( laf must be left from android 7-8).
In Fastboot mode, run boot-twrp.bat (the kernel and TWRP will be flashed).
Go to TWRP: Cleaning - Selective cleaning - select the "ENCRYPTION" swipe ... be sure to before each DATA format .. (This is a feature of this TWRP only), data format, wipe cache and dalvik cache. Reboot TWRP.
Installing Magisk first, then Lg_rctd_disabler as desired. If you need to disable encryption, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020, otherwise you do not need to flash this file. TWRP supports encryption MTP+ADB+OTG .
For F800S only: Before the first system boot, System / Product / Priv-app remove "Findlostphone".
Next, reboot into the OS.
TWRP 3.4.0 : Enable MTP before connecting to PC! , Use the data backup with the previously disabled password lock, pin code, ....
Config TWRP android 9 (us996.zip)
MTP, second screen...OS no problem F800S version (as in android 7-8).
The "fixed static boot" and "us996.zip" files are the source for developers who wish to build their own kernel or TWRP.
Presented as is. any borrowing, modifications and changes are welcome
I need a more detailed explanation
With LGup what exactly to do
And I say exactly
And in the BAT file I get an answer "waiting for the device
I have drivers and it recognizes it
I'm talking about the device F800L
Awaiting quick reply Thanks in advance
LGup for KDZ firmware, for example (F800L30e_00_1022.kdz) for F800L.
BAT file for Fastboot mode of the phone.
Boot-twrp.bat + TWRP.img + boot1.img must be put in the Fastboot folder before starting.
It's very simple if you have experience unlocking the bootloader.
Den4ik111111 said:
LGup for KDZ firmware, for example (F800L30e_00_1022.kdz) for F800L.
BAT file for Fastboot mode of the phone.
Boot-twrp.bat + TWRP.img + boot1.img must be put in the Fastboot folder before starting.
It's very simple if you have experience unlocking the bootloader.
Click to expand...
Click to collapse
I already have the F800L30e installed
And I have the KDZ file
Where do I get the BAT file from?
And I get waiting for device
When I try to play the file
Yes i have drivers
yes i checked it works
This is just for short answers for you
You mean the BAT file that is in the first message Or another file
Because the same file in the first post I tried several times
And it does not work for me
In which folder to run the file In the fastboot folder
Or from the main folder
In the "download mode" you will not succeed. You need to put the phone in "fastboot mode" to write TWRP + boot.
If you do not have "fastboot mode" then the bootloader is blocked. If I understood you correctly, then this is exactly so.
^^^Only for F800 * phones with unlocked bootloader^^^
Den4ik111111 said:
In the "download mode" you will not succeed. You need to put the phone in "fastboot mode" to write TWRP + boot.
View attachment 5223339
If you do not have "fastboot mode" then the bootloader is blocked. If I understood you correctly, then this is exactly so.
^^^Only for F800 * phones with unlocked bootloader^^^
Click to expand...
Click to collapse
1 Yes I have F800L As you can see in the picture
2 This Write download mode That's what I put it on
3 How do I get to "fastboot mode "
Volume down + cable not working
Yes the cable is connected to the computer
Yes the device is turned off
AVIMPEG said:
3 How do I get to "fastboot mode "
Click to expand...
Click to collapse
You need to make DirtySanta Bootloader unlock!
Den4ik111111 said:
You need to make DirtySanta Bootloader unlock!
Click to expand...
Click to collapse
I left everything alone
hi thank you for your effort
Could you enlighten me about the f800l bootloader unlock
I have applied the dirtysanta method to unlock then I root with magisk now I am under pie and root with magisk but when I check the bootloder status it displays locked under nougat and under pie (when updating)
I wonder if the ditysanta method and to bypass restriction of the bootloader to root the mobile or it is a permanent unlock or imissed sme think?
jeddouu said:
hi thank you for your effort
Could you enlighten me about the f800l bootloader unlock
I have applied the dirtysanta method to unlock then I root with magisk now I am under pie and root with magisk but when I check the bootloder status it displays locked under nougat and under pie (when updating)
I wonder if the ditysanta method and to bypass restriction of the bootloader to root the mobile or it is a permanent unlock or imissed sme think?
Click to expand...
Click to collapse
You can ignore it!
The dirtysanta method does not bypass the bootloader.
The bootloader is overwritten by the engineering unlocked from us996 (aboot.img, abootbackup.img).
With the rule ((LGup firmware in "partition dl" mode KDZ, remove daws aboot, abootbak)), there will never be problems when downgrading or upgrading the android version (repeating the "dirtysanta method" will not be needed).
In short, "permanent unlock" with an unlocked bootloader from us996.
Den4ik111111 said:
You can ignore it!
The dirtysanta method does not bypass the bootloader.
The bootloader is overwritten by the engineering unlocked from us996 (aboot.img, abootbackup.img).
With the rule ((LGup firmware in "partition dl" mode KDZ, remove daws aboot, abootbak)), there will never be problems when downgrading or upgrading the android version (repeating the "dirtysanta method" will not be needed).
In short, "permanent unlock" with an unlocked bootloader from us996.
Click to expand...
Click to collapse
thank you very much... in your small manual you did not explain how to use the fixed static boot file because I have this problem thank you in advance for your patience
jeddouu said:
thank you very much... in your small manual you did not explain how to use the fixed static boot file because I have this problem thank you in advance for your patience
Click to expand...
Click to collapse
Added an explanation of the files.
one thing if you allow
it is about mic the caller does not hear me except in free hand I test the mic with app recording it works well I deactivate voice google I resolved by changing some value to mixer_paths. xml but the recording in somme apps like whatsup is very low and not clear in pie and nougat if you have an idea
jeddouu said:
one thing if you allow
it is about mic the caller does not hear me except in free hand I test the mic with app recording it works well I deactivate voice google I resolved by changing some value to mixer_paths. xml but the recording in somme apps like whatsup is very low and not clear in pie and nougat if you have an idea
Click to expand...
Click to collapse
The F800 dialer has a built-in call recording and records well. Google Voice is not needed for this. WhatsApp, like many other messengers, does not have a built-in recording, attempts to record by third-party applications often lead to poor quality (the compression quality plays a big role as the connection quality). Try every possible application, even outdated ones, and you might find the right one.
I can be wrong somewhere, I don’t use call recording.
Den4ik111111 said:
You need to make DirtySanta Bootloader unlock!
Click to expand...
Click to collapse
Does the DirtySanta Bootloader Unlock work for the F800K model? I should have gotten the F800L, but I ended up with the F800K which seems to have little mention anywhere.
.
DonChino said:
Does the DirtySanta Bootloader Unlock work for the F800K model? I should have gotten the F800L, but I ended up with the F800K which seems to have little mention anywhere.
Click to expand...
Click to collapse
Yes.
Hi im on f800l with pie have you a kernel for software Version 30h? Thanks
TarAntonio said:
Hi im on f800l with pie have you a kernel for software Version 30h? Thanks
Click to expand...
Click to collapse
The official kernel sources for Android 9 (LGF800L_LGF800K_LGF800S_Android_Pie_v20a) were released in a single version, without updates. PIE 30h, 30e must be compatible with the kernel. This kernel was posted by me on another resource more than a year ago, here recently. So far no one has spoken about the incompatibility of the kernel with the "30h" firmware. Otherwise it would have been indicated.
Den4ik111111 said:
The official kernel sources for Android 9 (LGF800L_LGF800K_LGF800S_Android_Pie_v20a) were released in a single version, without updates. PIE 30h, 30e must be compatible with the kernel. This kernel was posted by me on another resource more than a year ago, here recently. So far no one has spoken about the incompatibility of the kernel with the "30h" firmware. Otherwise it would have been indicated.
Click to expand...
Click to collapse
Have you a link for download only the pie kernel?