THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
and
https://forum.xda-developers.com/xperia-x/development/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
F5122 IS AT https://mega.nz/#F!7RRWEJjZ!qbotcsuXiKfXs2gwpVoBAw
F5121 .. https://mega.nz/#F!qUwV3R5Q!zpi18kKSNuS7vAHH9jOoQA (THANKs @velemas )
both f5121/5122 folders have two kernel images, if you flash the WITH SU image, the device will wakeup rooted. However if you flash the CLEAN kernel, you must flash TWRP3.1.1 (use adb fastboot commands) and from twrp you must flash SUPERSU or Magisk (whichever) -
PLEASE PROVIDE ME WORKING MAGISK (some friends have had been using) i will update my repository.
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
F5122 IS AT https://mega.nz/#F!GFo1EArZ!ngb5WsZJtbmFwXk_ImN-TA
F5121 .. https://mega.nz/#F!2EQniYoZ!0Rhj15GN7nSRmrTFMC8smg (THANKs @Mikolaj612 and @velemas )
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
.
Click to expand...
Click to collapse
ROOT DIRECTORY (ON MEGA)
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
F5122 IS AT https://mega.nz/#F!iUB00abB!N7sDP1pv33ZCEC76j3RkYQ
F5121 .. AT https://mega.nz/#F!2FI0BI4B!f-wrWGTOzhgYX-_aLEBhBg ( THANK YOU @Mikolaj612 )
Code:
[SIZE="5"]
-if you don't have th 34.3 fsc script , i have included in the folder
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
- :)
[/SIZE]
base directory
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________________________
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
UPDATED KERNELS
F5121 IS AT https://mega.nz/#F!HcZmTIhR!0oCiMfh9uT-AdHp-bdSqZw (THANKS TO @velemas)
F5122 IS AT https://mega.nz/#F!fRBEVS5C!QjT-TgxZc9FYwAbh-F5IgA
during past 3 days; I had to flash my X, 3 times for build 34.3.A.0.238 ,
why?
here are my findings and i want your contribution
1.
after CLEAN FLASHING OF STOCK via FLASHTOOL ... I BOOT MY DEVICE, SETUP THE GOOGLE ACCOUNT(S) sync data etc AND then i switched off the device and FLASHED KERNEL without twrp and without SuperSU, i had to FLASH TWRP3.1.1 via ADB. when I boot my device held power+volumeDOWN key and went in to recovery. I FOUND twrp3.1.1 cannot access internal storage, asked password
SO
2.
after CLEAN FLASHING OF STOCKROM VIA FLASHTOOL, I NEVER BOOT MY DEVICE AND DIRECTLY flashed KERNEL ( version which doesn't have twrp orsupersu) LATER I flashed TWRP3.1.1 via ADB. I went in to recovery and this time twrp was able to access my internel storage. So I flashed KCAL (which later i found doesn't work for this kernel) and I FLASHED SUPERSU 2.82.zip.
I switched off my device and later boot it up, I setup all the accounts in android and sync data.
LATER I FOUND that my internal storage has only 10gb left, I got surprised and I found that my SYSTEM STORAGE is TAKING 50GB out of 64GB. I never found any such folder in the /system having files worth 40gb after android itself (10gb).
3.
again third time, after CLEAN FLASHING OF STOCKROM VIA FLASHTOOL. I FLASHED KERNEL having no TWRP but having SUPERSU. and boot my device and went thru sony setup. I found out that found out that only 15GB out of 64GB is used.
and now i am using device normally
the only explanation i can give is that when i flashed superSU via twrp3.1.1, it made partitions incorrectly, but when supersu is flashed by script, it works just fine.
any comments? who can try all above with his device?
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
kloroform said:
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
Click to expand...
Click to collapse
Fotakernel is the option you are looking for
Doesn't your phone distort at that high gain(I.e 92)?? Mine starts to crackle at 86 or 88 on headphones..
With 7.1. Update Sony made our x more quite but clearer, before it was more loud but harsh too..
Nice work :good:
I was going to ask if I can flash your older kernel to newer one, but I guess I don't have too. By the way, do you know what's the difference between .238 and .224 kernels? Didn't sony just released security update? Sorry, I'm new to Xperia Phones. :silly:
you wrote include wrongly(probably typo)
kloroform said:
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
Click to expand...
Click to collapse
You may skip FotaKernel.
however you can always flash latest recovery twrp3.1.1 is out,
gaurav_15 said:
Doesn't your phone distort at that high gain(I.e 92)?? Mine starts to crackle at 86 or 88 on headphones..
With 7.1. Update Sony made our x more quite but clearer, before it was more loud but harsh too..
Click to expand...
Click to collapse
at 96, it does, I felt 86 (even 88) pretty low , special if the mobile is in bag and i am driving.
but at 92, its just fine.
also when u use the noise cancellation option ON, you get perfect quality sound on sony headphones
btw, i am using samsung earbuds, and works amazingly well!
Dominykas Only One said:
Nice work :good:
I was going to ask if I can flash your older kernel to newer one, but I guess I don't have too. By the way, do you know what's the difference between .238 and .224 kernels? Didn't sony just released security update? Sorry, I'm new to Xperia Phones. :silly:
you wrote include wrongly(probably typo)
Click to expand...
Click to collapse
welcome to Sony's complex world of kernels builds and LOST DRM KEYS
1. KERNEL USUALLY GETS UPDATE AS AND WHEN GOOGLE UPGRADES ANDROID ( for example from marshmellow to nougat )
2. on Nougat (android 7) the Linux kernel is 3.1.x.x , on this kernel sony has been releasing various builds with minor chances in security patch and/or some bug fixes in volume rockers / bluetooth / NFC connectivity etc
so technically, you CAN use android N kernel came with initial build by sony over latest BUILDS by sony.
on the booting level it will not affect your device
however I am not sure what will happen once android is loaded and it may show u older security patches or may crash
hey, thanks a lot for the update!
I am on .228 rooted, I got notification for system update, so after I update + flash your .238 with SU and I am good to go?
Prerooted Magisk Manager compatible kernel
You can flash from TWRP, just select Install then click Image File, select the kernel img file and selectBoot and flash
https://www.mediafire.com/file/40v6g55eluw7k70/patched_boot.img
Intsall Magisk Manager from here
https://github.com/topjohnwu/MagiskManager/releases/download/v5.3.0/MagiskManager-v5.3.0.apk
JukiCro said:
hey, thanks a lot for the update!
I am on .228 rooted, I got notification for system update, so after I update + flash your .238 with SU and I am good to go?
Click to expand...
Click to collapse
on unlocked bootloader, OTA fails. but you can try!
but if anyhow you upgrade to .238 via OTA, you will lose you rooting and twrp. so yes you will have to FLASH the kernel only.
kloroform said:
Prerooted Magisk Manager compatible kernel
You can flash from TWRP, just select Install then click Image File, select the kernel img file and selectBoot and flash
https://www.mediafire.com/file/40v6g55eluw7k70/patched_boot.img
Intsall Magisk Manager from here
https://github.com/topjohnwu/MagiskManager/releases/download/v5.3.0/MagiskManager-v5.3.0.apk
Click to expand...
Click to collapse
thank you! i found magisk interesting option since its system , Open source and let you install modules (including xposed) (if supported)
Does the 238 kernel include drmfix? I am still on Android 6.0.1 and am looking to jump straight to the latest 7.1.1fw note i don't have drm key's they are long gone.
sucker for sony's said:
Does the 238 kernel include drmfix? I am still on Android 6.0.1 and am looking to jump straight to the latest 7.1.1fw note i don't have drm key's they are long gone.
Click to expand...
Click to collapse
you and update directly to 7.1.1
the kernel has drm fix
where can i download the 34.3.a.0238 tft rom ?
nova001 said:
where can i download the 34.3.a.0238 tft rom ?
Click to expand...
Click to collapse
Using xperifirm software or directly from xpericheck.com
hhjadeja007 said:
Using xperifirm software or directly from xpericheck.com
Click to expand...
Click to collapse
yee a saw, but i dont have alfa file account :S
flashtool (xperifirm ): error invalid upda information...
if i flash this kernel do i lose my drm key's? what is better version to use with SU or without? Best Regards.
Doesn't work for me. Root works just half a way. I can use root apps like adaway etc. but i can't uninstall any apps, mount /system as rw and even install busybox. Something is broken out there. 34.3.A.0.238
Related
XZ Dual Recovery is not yet compatible with Marshmallow and because of this I was forced to unlock the BL. Are there any recovery that we can use as of this moment? It seems that the development section for this is not so active.
infinitylook said:
XZ Dual Recovery is not yet compatible with Marshmallow and because of this I was forced to unlock the BL. Are there any recovery that we can use as of this moment? It seems that the development section for this is not so active.
Click to expand...
Click to collapse
I saw that there is a prerooted 6.0.1 with only TWRP recovery installed, not dualrecovery. Can you guide me on steps to get from official 6.0.1 to root status on an unlocked bootloader? I can't do anything to go back to previous firmwares and it seems I have to unlock as the only way to get anywhere.
GigaSPX said:
I saw that there is a prerooted 6.0.1 with only TWRP recovery installed, not dualrecovery. Can you guide me on steps to get from official 6.0.1 to root status on an unlocked bootloader? I can't do anything to go back to previous firmwares and it seems I have to unlock as the only way to get anywhere.
Click to expand...
Click to collapse
I tried flashing the TWRP from the site of TWRP but it results in blank screen. Also XZDR is not compatible with Marshmallow.
Did you already backup your TA? You can only do this by obtaining root so it is a must to flash previous FW (KK or LP) then root and backup your TA partion unless you don't care for your DRM keys.
1. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and follow instructions to unlock your bootloader. Alternatively you can use flashtool (just search here in the forums).
2. Download a TWRP image of Scorpion Windy (Z3 Tablet Wifi) https://twrp.me/devices/sonyxperiaz3tabetcompact.html
3. Download older versions of SuperSU. Systemless root doesn't seem to work with Xperia Stock so you go the system way, older versions are preferred. Will attach the zip I used.
3. Flash MM FW by Flashtool, do initial setup.
4. Boot into fastboot, fastboot the TWRP image you downloaded. Reboot and you should be in recovery
5. Flash the SuperSU. Flash also the RIC defeat zip. Reboot and you'll notice your just in TWRP.
6. Force shutdown.
7. Open flashtool flash the mM FW but only kernel and the FotaKernel, dont wipe anything. Reboot. It should start.
That worked for me.
After you, need to install busybox from playstore and the SELinux Changer app
P.s I can't attach any file however you can find everything i mentioned (Zips) here at XDA and TWRP. I still need to enable init.d but I guess that's difficult with stock rom stock kernel. Oh, and you can install flashfire in substitute of your recovery. Be careful with flashing Zips after you have a stable system since you don't have recovery and therefore no Nandroid backup
infinitylook said:
I tried flashing the TWRP from the site of TWRP but it results in blank screen. Also XZDR is not compatible with Marshmallow.
Did you already backup your TA? You can only do this by obtaining root so it is a must to flash previous FW (KK or LP) then root and backup your TA partion unless you don't care for your DRM keys.
1. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and follow instructions to unlock your bootloader. Alternatively you can use flashtool (just search here in the forums).
2. Download a TWRP image of Scorpion Windy (Z3 Tablet Wifi) https://twrp.me/devices/sonyxperiaz3tabetcompact.html
3. Download older versions of SuperSU. Systemless root doesn't seem to work with Xperia Stock so you go the system way, older versions are preferred. Will attach the zip I used.
3. Flash MM FW by Flashtool, do initial setup.
4. Boot into fastboot, fastboot the TWRP image you downloaded. Reboot and you should be in recovery
5. Flash the SuperSU. Flash also the RIC defeat zip. Reboot and you'll notice your just in TWRP.
6. Force shutdown.
7. Open flashtool flash the mM FW but only kernel and the FotaKernel, dont wipe anything. Reboot. It should start.
That worked for me.
After you, need to install busybox from playstore and the SELinux Changer app
P.s I can't attach any file however you can find everything i mentioned (Zips) here at XDA and TWRP. I still need to enable init.d but I guess that's difficult with stock rom stock kernel. Oh, and you can install flashfire in substitute of your recovery. Be careful with flashing Zips after you have a stable system since you don't have recovery and therefore no Nandroid backup
Click to expand...
Click to collapse
Well then, I knew what I should have done before I lost root. In any case, what certain DRM keys would I be losing on the tablet? I know the biggest commotion on the phones were the camera algorithms.
GigaSPX said:
Well then, I knew what I should have done before I lost root. In any case, what certain DRM keys would I be losing on the tablet? I know the biggest commotion on the phones were the camera algorithms.
Click to expand...
Click to collapse
You would lose camera algorithm (I don't care for that, it's a tablet and its pictures are bad from the start).
X-reality and display enhancements, sound and noise cancellation (This is i don't want to lose since i use mine mainly for graphic projects) and remote play. That's only what I remember, i don't know if I missed out something.
NO NEED TO UNLOCK THE BT, flash a MM prerooted zip you can make it yourself with prf you need the FTF, recroot and superSu.
Anyway if you still want unlock the bt backup the drm keys with backupta
dnnz said:
NO NEED TO UNLOCK THE BT, flash a MM prerooted zip you can make it yourself with prf you need the FTF, recroot and superSu.
Anyway if you still want unlock the bt backup the drm keys with backupta
Click to expand...
Click to collapse
That won't work and would cause bootloop. tried the latest supersu. anyway, i found the workaround and it's been working good now.
infinitylook said:
You would lose camera algorithm (I don't care for that, it's a tablet and its pictures are bad from the start).
X-reality and display enhancements, sound and noise cancellation (This is i don't want to lose since i use mine mainly for graphic projects) and remote play. That's only what I remember, i don't know if I missed out something.
Click to expand...
Click to collapse
Wow, yeah that's too dire for me to go forward to. I should've just stayed on lollipop since it was already what was best for me.
infinitylook said:
That won't work and would cause bootloop. tried the latest supersu. anyway, i found the workaround and it's been working good now.
Click to expand...
Click to collapse
But but but if many did that without problem including me, check the th "when is mm out"
dnnz said:
But but but if many did that without problem including me, check the th "when is mm out"
Click to expand...
Click to collapse
i willread on that. last timme i checked it out mostly devices are with sgp 612 (wifi) anyway thanks for the tip.
Can you give me the link on that thread? i checked the threads here on this device forum and they are for sgp 612 and 611 (wifi versions)
Hi,
I will release here my updated "boot.img" files for all Xperia XA Ultra.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Releases for Nougat:
2017/07/26: From 36.1.A.0.182 kernel sources and Ramdisk from 36.1.A.0.182 FR firmware.
https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
THANKS!!!
Little shook that no one has replied to this awesome work! Thanks Man I have been waiting! Sent a thanks
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for all Xperia XA Ultra.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
Releases for Nougat:
2017/07/26: From 36.1.A.0.182 kernel sources and Ramdisk from 36.1.A.0.182 FR firmware.
https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
Click to expand...
Click to collapse
For f3212
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
I don´t understand quite well (sorry for my ignorance, i´m new to this stuff), so i flash supersu from twrp ¨just after flashed new boot¨ to avoid boot loop.....does that mean flash supersu after flashed twrp right away? how do i avoid bootloop? my build number is 36.0.A.1.100, should i worry about it?
my model is f3213
Thanks a lot
Jazinto93 said:
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
I don´t understand quite well (sorry for my ignorance, i´m new to this stuff), so i flash supersu from twrp ¨just after flashed new boot¨ to avoid boot loop.....does that mean flash supersu after flashed twrp right away? how do i avoid bootloop? my build number is 36.0.A.1.100, should i worry about it?
my model is f3213
Thanks a lot
Click to expand...
Click to collapse
All boot released here are for Nougat only. You have Marshmallow so you are not on the right place
Why don't you update your phone to a recent MM firmware? .100 is very old and only useful for making TA backup.
can you guys work on kernel? cause charging speed is cancer and maybe you can set max cpu clocks a bit higher?
Hi @rrvuhpg
looking forward the update of your work?
Is there anyway to install or switch to magisk after flash this boot image?
I've tried but error 1 i love magisk simplicity
This kernel gives me, NVRAM Warn. error on Wifi, please fix it
NVRAM warning error on Wifi. F3213
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for all Xperia XA Ultra.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
Releases for Nougat:
2017/07/26: From 36.1.A.0.182 kernel sources and Ramdisk from 36.1.A.0.182 FR firmware.
https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
Click to expand...
Click to collapse
I have an Xperia XA Ultra single sim, I am root right now with this kernel, but I get an error on mi Wifi settings, it says "NVRAM warning error" I'm on nougat "36.1.A.1.86", I think the error is caused because of the dual kernel you made for both versions of XA Ultra (Single and dual Sim), can you please make individual kernels for individual versions?. thanx in advance.
kiukirimas said:
I have an Xperia XA Ultra single sim, I am root right now with this kernel, but I get an error on mi Wifi settings, it says "NVRAM warning error" I'm on nougat "36.1.A.1.86", I think the error is caused because of the dual kernel you made for both versions of XA Ultra (Single and dual Sim), can you please make individual kernels for individual versions?. thanx in advance.
Click to expand...
Click to collapse
Hi, kernel sources are unified for single and dual Sim models so I can't build individual kernel. I think that your problem is because you are on a newer firmware than my kernel. I will not update my work, maybe an other user can do it for you.
36.1.A.0.182 is still with error
rrvuhpg said:
Hi, kernel sources are unified for single and dual Sim models so I can't build individual kernel. I think that your problem is because you are on a newer firmware than my kernel. I will not update my work, maybe an other user can do it for you.
Click to expand...
Click to collapse
Hi, thanks for your answer, I just followed your advice, and now I can see is not the firmware, is the kernel who causes the problem. I just installed the 36.1.A.0.182 firmware version from flashtool, and installed the kernel, following your tutorial for root, but I'm still having the same problem. I must say that I successfully did root my previous phones in Nougat and marshmallow (Xa-E5-L1) and marshmallow in the Xa ultra too, but is only the Nougat version of XA ultra who gives me this problem, can you check it please?. I wanted to use another kernel from XDA, but I can't see any other, so please you are the only one person who can fix this. thanx in advance.
Hi, great work! Can you share the build script?
Hi all https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
is this working in my device please let me know before ill try it my device is F3212 running Nougat
ill try to root mine...someone can respond to me if its working or not.....?????????????
william.alovera said:
Hi all https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
is this working in my device please let me know before ill try it my device is F3212 running Nougat
ill try to root mine...someone can respond to me if its working or not.....?????????????
Click to expand...
Click to collapse
There are threads here that supports f3212, Be sure to read them all mate and be reminded of it's requirements like unlocked bootloader etc
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
and
https://forum.xda-developers.com/xperia-x/development/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
F5122 IS AT https://mega.nz/#F!GFo1EArZ!ngb5WsZJtbmFwXk_ImN-TA
F5121 .. https://mega.nz/#F!2EQniYoZ!0Rhj15GN7nSRmrTFMC8smg (THANKs @Mikolaj612 and @velemas )
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
.
Click to expand...
Click to collapse
ROOT DIRECTORY (ON MEGA)
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
F5122 IS AT https://mega.nz/#F!iUB00abB!N7sDP1pv33ZCEC76j3RkYQ
F5121 .. AT https://mega.nz/#F!2FI0BI4B!f-wrWGTOzhgYX-_aLEBhBg ( THANK YOU @Mikolaj612 )
Code:
[SIZE="5"]
-if you don't have th 34.3 fsc script , i have included in the folder
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
- :)
[/SIZE]
base directory
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________________________
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
UPDATED KERNELS
F5121 IS AT https://mega.nz/#F!HcZmTIhR!0oCiMfh9uT-AdHp-bdSqZw (THANKS TO @velemas)
F5122 IS AT https://mega.nz/#F!fRBEVS5C!QjT-TgxZc9FYwAbh-F5IgA
F5121 here:
Code:
http://www100.zippyshare.com/v/gcX0M8iD/file.html
Mikolaj612 said:
F5121 here:
Code:
http://www100.zippyshare.com/v/gcX0M8iD/file.html
Click to expand...
Click to collapse
thank you,
link updated in the OT
have a great day!
I am using the same kernel which i have put on the cloud, f5122
however updatin to .224 via flashtool via win7pro took LONGER than usual time! , TA Partition Headers weren't closing! and eventually froze!
softBricked device twice! , then flashed via Windows 10 / 64bit from different machine!
however! please note!
the kernels are already rooted!
after FLASHING xperia X, if you DONT boot, and FLASH RECOVERY twrp3.1, via adb, adn boot X by pressing power+volumeDOWN key until PINK LED, you can FLASH kcal module! (which should be in your sd card, or use otg cable)
with Kcal you can use your device in gray scale - and it will extend your battery life to amazing level! since X has poor battery!
remember! if you have booted your X into system , the twrp will give PASSWORD error while accessing internal storage! because SONY encrypts storage on its VERY FIRST BOOT when you CLEAN FLASH STOCK ROM using FLASHTOOL!
YasuHamed said:
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
and
https://forum.xda-developers.com/xperia-x/development/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
F5122 IS AT https://mega.nz/#F!GFo1EArZ!ngb5WsZJtbmFwXk_ImN-TA
F5121 .. https://mega.nz/#F!2EQniYoZ!0Rhj15GN7nSRmrTFMC8smg (THANKs @Mikolaj612 and @velemas )
ROOT DIRECTORY (ON MEGA)
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
F5122 IS AT https://mega.nz/#F!iUB00abB!N7sDP1pv33ZCEC76j3RkYQ
F5121 .. AT https://mega.nz/#F!2FI0BI4B!f-wrWGTOzhgYX-_aLEBhBg ( THANK YOU @Mikolaj612 )
Code:
[SIZE="5"]
-if you don't have th 34.3 fsc script , i have included in the folder
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
- :)
[/SIZE]
base directory
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________________________
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
UPDATED KERNELS
F5121 IS AT https://mega.nz/#F!HcZmTIhR!0oCiMfh9uT-AdHp-bdSqZw (THANKS TO @velemas)
F5122 IS AT https://mega.nz/#F!fRBEVS5C!QjT-TgxZc9FYwAbh-F5IgA
Click to expand...
Click to collapse
Nice, Work on F5122
Where clean kernel for F5122?
Can't use the kcal
ReddFreedom said:
Where clean kernel for F5122?
Click to expand...
Click to collapse
updated, please check now
FuLiterary said:
Can't use the kcal
Click to expand...
Click to collapse
put supersu and kcal in sd card ( https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw) ( 7.x__417__Kcal_For-X_XZ_by_venkat-kamesh_SIGNED.zip)
AFTER FRESH FLASHING OF STOCK ROM, DON"T BOOT YOURDEVICE AND
1. flash twrp3.1 via adb (fastboot mode)
2. flash the clean kernel (with no supersu) via flash tool
3. boot in to recovery / twrp ,
4. flash kcal
5.flash supersu or magisk (whatever)
reboot NOW
the device will wakeup
1. rooted
2. having color modular in the app dock
YasuHamed said:
put supersu and kcal in sd card ( https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw) ( 7.x__417__Kcal_For-X_XZ_by_venkat-kamesh_SIGNED.zip)
AFTER FRESH FLASHING OF STOCK ROM, DON"T BOOT YOURDEVICE AND
1. flash twrp3.1 via adb (fastboot mode)
2. flash the clean kernel (with no supersu) via flash tool
3. boot in to recovery / twrp ,
4. flash kcal
5.flash supersu or magisk (whatever)
reboot NOW
the device will wakeup
1. rooted
2. having color modular in the app dock
Click to expand...
Click to collapse
i will try it.thanks
YasuHamed said:
updated, please check now
Click to expand...
Click to collapse
Thank you.
YasuHamed said:
put supersu and kcal in sd card ( https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw) ( 7.x__417__Kcal_For-X_XZ_by_venkat-kamesh_SIGNED.zip)
AFTER FRESH FLASHING OF STOCK ROM, DON"T BOOT YOURDEVICE AND
1. flash twrp3.1 via adb (fastboot mode)
2. flash the clean kernel (with no supersu) via flash tool
3. boot in to recovery / twrp ,
4. flash kcal
5.flash supersu or magisk (whatever)
reboot NOW
the device will wakeup
1. rooted
2. having color modular in the app dock
Click to expand...
Click to collapse
Have test it and can't use the kcal
(5. flash Magisk v.14)
BiaBertK said:
Have test it and can't use the kcal
(5. flash Magisk v.14)
Click to expand...
Click to collapse
now i am surprised!
how did you flash it? did u just install apk or flashed via twrp. its signed for X and XZ, and its working fine :s
YasuHamed said:
now i am surprised!
how did you flash it? did u just install apk or flashed via twrp. its signed for X and XZ, and its working fine :s
Click to expand...
Click to collapse
flashed via twrp!
This is how I proceeded:
(flashed via Windows 10 pro / 64bit ; Flashtool v.0.9.23.2 ; Minimal ADB and Fastboot v.1.4.2)
1. flash "F5121_34.3.A.0.228_1303-2543_R5D.ftf" via FlashTool
2. flash "twrp-3.1.1-suzu-2017.07.16.img" via adb
3. flash clean kernel "F5121_34.3.A.0.224_CLEAN_noTWRP_NOsuperSU" via FlashTool
4. boot to twrp
5. flash kcal "7.x__417__Kcal_For-X_XZ_by_venkat-kamesh_SIGNED.zip" in twrp
6. flash Magisk "Magisk-v14.0.zip" in twrp
7. Wipe Cache/Dalvik
8. reboot to System
Now I have the app "Color Control"
When I start the app I get the error
Do I make a mistake somewhere?
BiaBertK said:
flashed via twrp!
This is how I proceeded:
(flashed via Windows 10 pro / 64bit ; Flashtool v.0.9.23.2 ; Minimal ADB and Fastboot v.1.4.2)
1. flash "F5121_34.3.A.0.228_1303-2543_R5D.ftf" via FlashTool
2. flash "twrp-3.1.1-suzu-2017.07.16.img" via adb
3. flash clean kernel "F5121_34.3.A.0.224_CLEAN_noTWRP_NOsuperSU" via FlashTool
4. boot to twrp
5. flash kcal "7.x__417__Kcal_For-X_XZ_by_venkat-kamesh_SIGNED.zip" in twrp
6. flash Magisk "Magisk-v14.0.zip" in twrp
7. Wipe Cache/Dalvik
8. reboot to System
Now I have the app "Color Control"
When I start the app I get the error
Do I make a mistake somewhere?
Click to expand...
Click to collapse
it should work
Thank you!!!...it works
I tried with the 34.3.A.0.228 and works perfectly!!! :good:
I finally could ROOT my Xperia F5121 with this rooted kernel. Thank you for assistant!:laugh:
I'm on 34.3.A.0.217 rooted, how do i go about updating to this version?
Just use the system setting option to update then flash the rooted kernel? or just flash the rooted 224 kernel via recovery?
Does it work with OmniRom
this one: [ROM][Xperia X][SUZU][N][7.1.2][WEEKLY]OmniROM
Why even after a week I don't get this update??
gaurav_15 said:
Why even after a week I don't get this update??
Click to expand...
Click to collapse
It's late in India this time
[oreo]XZ1-drmfix-root-ricoff
Available for any version of the official 8.0 oreo
First you have twrp https://forum.xda-developers.com/xperia-xz1/development/twrp-t3716488
Be sure to use the zip I provided,Make sure your rom is clean.If you want wipe data,cache and dalvik, please execute it first.
1，flash drmpatch.zip
2，flash SuperSU.zip
3，flash RicOff.zip
4，reboot
Perfect, please enjoy.
download
https://mega.nz/#F!s8QlGD7S!cSlNJcZArwwdvZGGE5sVdA
drmfix.so/drm****.so thank @sToRm// :good:
The secd of 47.1.A.12.34 is the same as 47.1.A.8.49.
secd original file（G8441_47.1.A.8.49_CE） https://mega.nz/#!IpYg1Q4Q!ONXXqHoP6JkrFQ9jGUHMMXlzHcPAfog3ISrMgogO8go
modify
E803003206000014E8031F3204000014E807003202000014E8031E32
for
08008052060000140800805204000014080080520200001408008052
drmpatch.zip
Install XperiFIX
In C:\XperiFIX\DATA\XZP\G8142\Oreo2
Modify the update binary
ui_print "******************************"
ui_print "Sony XZ Premium *OREO* DRM restore by //sToRm"
ui_print "******************************"
change
ui_print "******************************"
ui_print "Sony XZ1/XZ1C *OREO* DRM restore by //sToRm"
ui_print "******************************"
/ system
change
/vendor
And replace secd
Click to expand...
Click to collapse
SuperSU.zip
Modify init.supersu.rc.24 and init.supersu.rc.24.bindsbin
on post-fs
exec u:r:supersu:s0 root root -- /sbin/fbe_bypass.sh
export LD_PRELOAD drmfix.so:drm****.so
#RIC disable
mount securityfs securityfs /sys/kernel/security nosuid nodev noexec
write /sys/kernel/security/sony_ric/enable 0
Click to expand...
Click to collapse
RicOff.zip
The status of SELinux changes to permissive
Click to expand...
Click to collapse
The original machao44 account is lost
I do not know how to misunderstand me
前來支持個~~
謝馬大
How do I get root and Kernel to xperia xz1 g8342 ?
How do I get root and Kernel to xperia xz1 g8342 ?
sofyanpall said:
How do I get root and Kernel to xperia xz1 g8342 ?
Click to expand...
Click to collapse
Unlocked bootloader and as it says here gives you root on stock kernel.
Use [RECOVERY] TWRP 3.2.1 twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img from just that post if you´re at FW 47.1.A.8.49 due to EXT4 File Based Encryption (FBE)
If you´re on older FW use twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
or simply upgrade to 47.1.A.8.49 before proceeding
thank you for your reply Senior Member
pergoteborg said:
Unlocked bootloader and as it says here gives you root on stock kernel.
Use [RECOVERY] TWRP 3.2.1 twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img from just that post if you´re at FW 47.1.A.8.49 due to EXT4 File Based Encryption (FBE)
If you´re on older FW use twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
or simply upgrade to 47.1.A.8.49 before proceeding
Click to expand...
Click to collapse
I opened bootloader , my phone 47.1.A.2.374 I tried to flash 47.1.A.8.49 flashtool does not work in xperia g8342
At the start of the show the message glows ( your device hes been unlocked and can"t be trusted - your device will boot in 5 Seconds ) Currently I can not access developer options and the camera picks up green images
What should I do؟
all Respect and appreciation for you Senior Member
sofyanpall said:
I opened bootloader , my phone 47.1.A.2.374 I tried to flash 47.1.A.8.49 flashtool does not work in xperia g8342
At the start of the show the message glows ( your device hes been unlocked and can"t be trusted - your device will boot in 5 Seconds ) Currently I can not access developer options and the camera picks up green images
What should I do؟
all Respect and appreciation for you Senior Member
Click to expand...
Click to collapse
.
Green pictures are because you unlocked bootloader. Will be fixed by DRMFix.
your device hes been unlocked and can"t be trusted-message will allways be there on unlocked BL
Download G8342_MY_47.1.A.8.49 .rar according to this post, it contains latest ROM and newflasher
You need to install drivers for flashtool. It may be a little tricky and it was soooo long ago I set it up myself I simply do not remember. Google it. Maybe This or http://www.**********.com/setup-androxyde-flashtool-sony-xperia-devices-windows/may help.
With drivers installed:
Turn off phone. Hold Vol down while connecting USB to computer (Green light on phone). Open commandprompt on computer and cd to unpacked G8342_MY_47.1.A.8.49 .rar directory. Run
Code:
newflasher.exe
.
This installs lastest stock kernel and firmware.
When finished reboot phone
Download DRMPatck package , unpack it and move the three zip files to phone
Turn off phone
Download twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img and move the file to the same directory on computer where flashtool is installed
Commect the phone to computer USB while holding Vol UP (Blue light on phone)
Open commandprompt on computer and cd to flashtool directory (where also twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img exists)
Run command
Code:
fastboot flash recovery twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img
Disconnect phone.
Hold Vol Down while starting the phone which brings you to TWRP.
Flash DRMFix according to OP.
DONE
Next maybe custom rom?
Wysłane z mojego G8342 przy użyciu Tapatalka
Hopefully
Any chance to backup TA Partition?
root xperia xz1 g8342
pergoteborg said:
.
Green pictures are because you unlocked bootloader. Will be fixed by DRMFix.
your device hes been unlocked and can"t be trusted-message will allways be there on unlocked BL
Download G8342_MY_47.1.A.8.49 .rar according to this post, it contains latest ROM and newflasher
You need to install drivers for flashtool. It may be a little tricky and it was soooo long ago I set it up myself I simply do not remember. Google it. Maybe This or http://www.**********.com/setup-androxyde-flashtool-sony-xperia-devices-windows/may help.
With drivers installed:
Turn off phone. Hold Vol down while connecting USB to computer (Green light on phone). Open commandprompt on computer and cd to unpacked G8342_MY_47.1.A.8.49 .rar directory. Run
Code:
newflasher.exe
.
This installs lastest stock kernel and firmware.
When finished reboot phone
Download DRMPatck package , unpack it and move the three zip files to phone
Turn off phone
Download twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img and move the file to the same directory on computer where flashtool is installed
Commect the phone to computer USB while holding Vol UP (Blue light on phone)
Open commandprompt on computer and cd to flashtool directory (where also twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img exists)
Run command
Code:
fastboot flash recovery twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img
Disconnect phone.
Hold Vol Down while starting the phone which brings you to TWRP.
Flash DRMFix according to OP.
DONE
Click to expand...
Click to collapse
Thank you so much pergoteborg
I followed the instructions and my phone works well and the camera works without problems
Before the operation you have repaired the phone system on a program ( emma )
:good::good::good:
The only remaining problem is developer options and not a necessity
sofyanpall said:
Thank you so much pergoteborg
I followed the instructions and my phone works well and the camera works without problems
Before the operation you have repaired the phone system on a program ( emma )
:good::good::good:
The only remaining problem is developer options and not a necessity
Click to expand...
Click to collapse
Go into settings -> system -> about phone and click repeatibly on version at the bottom to open up developer options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk
root xperia xz1 g8342 47.1A.2.374
pergoteborg said:
Go into settings -> system -> about phone and click repeatibly on version at the bottom to open up developer options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk
Click to expand...
Click to collapse
I changed the phone language from Arabic to English and the developer options worked well
I can confirm that the method of M-Rom works perfectly fine for my G8341 Xperia XZ1 with Android 8.0.0.
Additionally I wanted to add: For those who did not already solve the Google USB driver phenomenon for fastboot to detect Sony devices: See here: https://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114. This is the guide I followed to do it. You can get the file needed for that guide here, as the link provided there is no longer active: https://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Thanks a bunch M-Rom and sToRm// for saving my phones life (and mine, too :good: )
Hello guys, can someone explain me how to install TWRP?
unlock bootloader from developed options?
after flashing twrp via fastboot? like fastboot flash recovery (recovery name.img)??
and what the features of drmfix ricoff?
does google camera HDR+ works?
Thanks!
georgesalo said:
Hello guys, can someone explain me how to install TWRP?
unlock bootloader from developed options?
after flashing twrp via fastboot? like fastboot flash recovery (recovery name.img)??
and what the features of drmfix ricoff?
does google camera HDR+ works?
Thanks!
Click to expand...
Click to collapse
Yes, you're exactly right. Boot into the unlocked bootloader:
Adb reboot bootloader
(Next command)
Fastboot flash recovery name/and/location/of/recovery/image.img
Not sure if hdr+ works as I believe it uses api2 (I could be way wrong on that name) but I believe it uses something that this device doesn't support but I could be wrong.
DRM ricoff reactivates the Sony features and the Sony camera to full functionality. Basically once you've flashed TWRP then you can flash the root and DRM fix and you have root and fully working camera and features even though you've lost the DRM keys. The only difference between this method and the method created by Storm for the XZP is that on the XZP you can backup the TA partition whereas we haven't figured out how to do that yet but the result is still exactly the same.
Hey, can i flash Magisk instead of SuperSU, or does the DRM Fix need SuperSU to work?
Unfortunately the DRM fix needs SuperSU to work, the package comes with a special version of SuperSU to make it work. Hopefully if @aledoom gets some time he can try build a new version of the Andro+ kernel for our phone running the latest 8.49 firmware that will support Magisk and the DRM fix. He doesn't own an xz1 himself so testing isn't easy butt I'm sure one of us will be happy to help with that. I know I will for sure.
If he gets a working kernel built then we can have the DRM fix with Magisk instead of SuperSU, which I think we all would love.
The problem is that Magisk doesn't work on the stock kennel. In fact it causes a bootloop so don't try flashing it.
M-Rom said:
[oreo]XZ1-drmfix-root-ricoff
Available for any version of the official 8.0 oreo
First you have twrp https://forum.xda-developers.com/xperia-xz1/development/twrp-t3716488
Be sure to use the zip I provided,Make sure your rom is clean.If you want wipe data,cache and dalvik, please execute it first.
1，flash drmpatch.zip
2，flash SuperSU.zip
3，flash RicOff.zip
4，reboot
Perfect, please enjoy.
download
https://mega.nz/#F!s8QlGD7S!cSlNJcZArwwdvZGGE5sVdA
drmfix.so/drm****.so thank @sToRm// :good:
Click to expand...
Click to collapse
Is this DRM-fix/patch working on the latest XZ1 firmware?
xFirefly93 said:
Is this DRM-fix/patch working on the latest XZ1 firmware?
Click to expand...
Click to collapse
Yes, it is working. Tested it with my G8341 XZ1 with latest firmware on 8.0.0.
Camera works again and you can set the X-Reality display saturation again.
CoinsClassic said:
I can confirm that the method of M-Rom works perfectly fine for my G8341 Xperia XZ1 with Android 8.0.0.
Additionally I wanted to add: For those who did not already solve the Google USB driver phenomenon for fastboot to detect Sony devices: See here: https://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114. This is the guide I followed to do it. You can get the file needed for that guide here, as the link provided there is no longer active: https://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Thanks a bunch M-Rom and sToRm// for saving my phones life (and mine, too :good: )
Click to expand...
Click to collapse
If you're having trouble installing the fastboot / flashmode drivers from Sony because of driver signing issues, the answer should never be to disable driver signing altogether.
Instead you should look at the answer here and use the open-source tool it describes to install the driver with a self-signed certificate.
Of course, Sony should be doing a better job and releasing signed drivers so we wouldn't be in this situation to begin with.
rooted kernel hiding bootloader unlock
with working sony stock fw fota updates
for Sony Xperia XZ1
Firmware Over the Air system updates have been disabled/not working with sony xperia phones with unlocked bootloader.
Also many sony drm functions are disabled if fw detects unlocked bootloader even if device master key was recovered.
I've implemented a kernel patch for xperia XZ1 Compact / XZ1 / XZ Premium phones that properly masks bootloader unlock status so it appears as still locked for sony stock firmwares.
This allows FOTA updates to be installed if running completely unmodified stock firmware. This is possible if this kernel is just booted from usb via fastboot instead of flashing it.
The kernel is pre-rooted, so you can have root as usual with magisk when running this kernel (you can use magisk system less patching to make changes to system/vendor partitions without actually modifying them).
For oreo fw the boot process is patched to hide magisk from sony ric daemon that stops the boot in case it thinks the bootloader is still locked. This special patch allows to pass safetynet including cts while having properly working magisk.
This kernel may be used (flashed) just to properly enable sony drm features, like video image enhancements, if device master key was recovered via locked state TA restore.
The bellow described way to install FOTA system update works with both - phone with TA restored and phone with drm keys lost. Both variants have been tested with xz1c.
How to use this kernel while planning to do FOTA system update eventually
Update: please see here for the latest usage instructions for kernels in flashable zip archive.
Please see screenshots bellow for this kernel in action (with xz1c) doing fota system update from oreo to pie and from pie to next pie version. There is also a video documenting this here. Few longer waiting parts have been cut out to fit the video under 15 minutes of youtube limit for not verified accounts.
if your bootloader is still locked
Use renoroot exploit to backup your TA, unlock your bootloader and restore TA-locked to recover device master key as described in
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented thread.
select one of the prepared kernels and download it
make sure you are running unmodified stock firmware
You need the version corresponding to the selected kernel - reflash the firmware to make sure it is unmodified.
Please note: any mount of /system or /vendor partitions in write mode would result with modifications even if nothing is copied there.
Be aware that some zip packages flashed from twrp may mount the partitions for write access even when that is not needed.
reboot the phone to fastboot mode
Use either "adb reboot bootloader" or
enter fastboot by holding powered off phone's volume up key while connecting it to PC via usb cable and use 'fastboot reboot bootloader' command.
boot the downloaded kernel via fastboot
For example (xz1c):
Code:
fastboot boot boot-G8441-47.1.A.16.20-hideunlock-rooted.img
enjoy your rooted phone which thinks it is still locked
Sony apps will be offered to install/update. System FOTA update may come.
Magisk will provide your root when magisk manager app is installed (offered on the first boot).
if you need to use a custom recovery, like TWRP
Do not flash it. If you do, FOTA update verification will fail.
Instead use 'fastboot boot' the same way as with the kernel above, but instead of the kernel, boot the twrp image without flashing it.
to install a FOTA system update
just start the update as usual
let it run until it finishes the installation
try to catch the restart then and hold volume up that time to enter fastboot
you need to use following command to make next boot working
Code:
fastboot reboot bootloader
use 'fastboot boot' to boot kernel for fw to which fota updating to,
for example (xz1c):
Code:
fastboot boot boot-G8441-47.2.A.4.45-hideunlock-rooted.img
if you miss the restart (or do not have the right kernel version),
it does not matter, the installation will finish even when bootloader unlock is detected with the last reboot to updated system,
so just 'fastboot boot' the corresponding 'hideunlock-rooted' kernel then
Alternative use of this kernel
If you do not like booting from usb via fastboot to startup your phone, you can flash the kernel and boot normally.
But if you like to install FOTA system update then, you would need to flash the stock kernel first in order to make the fw untouched again (assuming no other changes to the fw, like system or vendor partitions, have been done) and boot the patched kernel via 'fastboot boot' as described above.
You can backup stock kernel (and recovery) to avoid need to download full stock fw when you need to restore stock kernel & recovery when you decide to install fota system update - see here and following post for more details please.
If you do not care about FOTA, just do not install it.
And use this kernel just to enable all sony drm features that are available on a locked phone (assuming locked state TA has been restored).
In case you like to make some modifications to system or vendor partitions (as you do not care about fota), you would need to disable verity in the kernel - please see post#3 for noverity variants of oreo kernels and linked post describing howto switch verity off via magisk in all pie kernels.
Downloads
See the post#2 please.
Source code
patched kernel sources to hide bootloader unlock (my-bluhide/* branches)
https://github.com/j4nn/sonyxperiadev-kernel-copyleft
patched magisk sources to hide magisk from sony ric daemon on early boot phase (v19.1-manager-v7.1.2-ric branch)
https://github.com/j4nn/Magisk/tree/v19.1-manager-v7.1.2-ric
The patches are provided under GPL (that means you may include them in your builds, but you need to provide buildable source of released binaries /true for any kernel change btw/).
Credits
Thanks to @tonsofquestions for lot of initial testing of this concept when I did not have a phone with unlocked bootloader and for discovering the need to reboot to fastboot by a command to make the 'fastboot boot' command properly boot the supplied kernel image.
Thanks to @topjohnwu for his excelent magisk tool.
If you find my work useful, consider donating here please:
https://j4nn.github.io/donate/
Thank you.
XDA:DevDB Information
kernel_bluhide_poplar, Kernel for the Sony Xperia XZ1
Contributors
j4nn
Source Code: https://github.com/j4nn/sonyxperiadev-kernel-copyleft
Kernel Special Features: proper hiding of bootloader unlock, sony ric with magisk hack
Version Information
Status: Stable
Stable Release Date: 2019-02-10
Created 2019-02-10
Last Updated 2019-08-07
Downloads
- hideunlock kernel pre-rooted boot images:
Xperia XZ1 (G8341/G8343)
boot-G8341-47.1.A.16.20-hideunlock-magisk-19.1.img
boot-G8341-47.2.A.4.45-hideunlock-rooted.img
boot-G8341-47.2.A.6.30-hideunlock-rooted.img
boot-G8341-47.2.A.8.24-hideunlock-rooted.img
boot-G8341-47.2.A.10.28-hideunlock-rooted.img
boot-G8341-47.2.A.10.45-hideunlock-rooted.img
boot-G8341-47.2.A.10.62-hideunlock-magisk-19.3.img
Xperia XZ1 Dual (G8342)
boot-G8342-47.1.A.16.20-hideunlock-magisk-19.1.img
boot-G8342-47.2.A.4.45-hideunlock-rooted.img
boot-G8342-47.2.A.6.30-hideunlock-rooted.img
boot-G8342-47.2.A.8.24-hideunlock-rooted.img
boot-G8342-47.2.A.10.28-hideunlock-rooted.img
boot-G8342-47.2.A.10.45-hideunlock-rooted.img
boot-G8342-47.2.A.10.62-hideunlock-magisk-19.3.img
- hideunlock kernels flashable to multi fw versions (see here for usage howto):
Xperia XZ1 (G8341/G8343)
kernel-G8341-47.1.A.16.20-hideunlock.zip
kernel-G8341-47.2.A.10.62-hideunlock.zip
kernel-G8341-47.2.A.10.80-hideunlock.zip
kernel-G8341-47.2.A.10.107-hideunlock.zip
kernel-G8341-47.2.A.11.228-hideunlock.zip
Xperia XZ1 Dual (G8342)
kernel-G8342-47.1.A.16.20-hideunlock.zip
kernel-G8342-47.2.A.10.62-hideunlock.zip
kernel-G8342-47.2.A.10.80-hideunlock.zip
kernel-G8342-47.2.A.10.107-hideunlock.zip
kernel-G8142-47.2.A.11.228-hideunlock.zip
Screenshots of XZ1c FOTA system update from oreo 47.1.A.16.20 to pie 47.2.A.4.45
(video available here)
Downloads
This is for alternative use only - please see post#10 for more details.
boot-G8341-47.1.A.16.20-hideunlock-magisk-19.1-noverity.img
boot-G8342-47.1.A.16.20-hideunlock-magisk-19.1-noverity.img
Screenshots of XZ1c FOTA system update from pie 47.2.A.4.45 to pie 47.2.A.6.30 version
(video available here since 08:10 time)
This should be the first paragraph!
j4nn said:
[...] use this kernel just to enable all sony drm features that are available on a locked phone (assuming locked state TA has been restored).
Click to expand...
Click to collapse
Since I do not care about OTA updates, because we can download every firmware via XperiFirm and flash it via newflasher, I will use your modded kernel in the 'alternative' way! :good:
j4nn said:
Alternative use of this kernel
If you do not like booting from usb via fastboot to startup your phone, you can flash the kernel and boot normally.
Click to expand...
Click to collapse
@j4nn - I flashed "boot-G8341-47.2.A.6.30-hideunlock-rooted.img" on my G8341 which has the latest Pie firmware (G8341_47.2.A.6.30_Customized DE_1310-4290_R6C) installed, but the device did not boot into Android after that! :crying: I flashed the latest official Magisk before your kernel. Do I need to use your patched Magisk instead?
Did you forgot to add the patched magisk flashable img file? "hide magisk from sony ric daemon on early boot phase (v18.1-manager-v7.0.0-ric branch)"
j4nn said:
Downloads
Click to expand...
Click to collapse
Maybe the firmware version is not compatible with the one you took the kernel from? The firmware folder includes:
kernel_X-FLASH-ALL-C93B.sin
boot/bootloader_X_BOOT_MSM8998_LA2_0_P_107_X-FLASH-ALL-C93B.sin
...
Click to expand...
Click to collapse
@SGH-i200, I just compared the stock kernel boot image extracted from G8341_Customized DE_1310-4290_47.2.A.6.30_R6C (which I have used to create it) and it seems all good to me:
- os version and patch level match
- device tree blobs are the same
- kernel command line is the same
- extracted kernel config is (except few comments as it is usual) the same, with poplar target (i.e. single sim XZ1)
- ramdisk is the same except changes that are expected (integrated magisk in order to provide root when booted from usb having unmodified stock fw)
Did it result with an infinite hang during boot (which phase of the boot splash animation)?
Or did it reboot during boot (a boot-loop) - which phase?
I am sorry I forgot to mention the kernels for other targets than xz1c have not been tested (I have only xz1c for testing).
But it should be safe to test the above howto as described. Even if the kernel was flashed (instead of just fastboot booted), recovering from this should be as simple flashing stock kernel back.
Anybody else tested this with XZ1?
j4nn said:
Did it result with an infinite hang during boot (which phase of the boot splash animation)?
Or did it reboot during boot (a boot-loop) - which phase?
Click to expand...
Click to collapse
The SONY white splash screen appeared (with only black SONY text) and then it hang forever.
j4nn said:
Even if the kernel was flashed (instead of just fastboot booted), recovering from this should be as simple flashing stock kernel back.
Click to expand...
Click to collapse
I flashed the kernel_X-FLASH-ALL-C93B.sin (and everything else as I did to upgrade to latest Pie) from the stock fw to recover.
After the XZ1 was booting again, I executed the fastboot booting, without problems!
adb reboot bootloader
fastboot boot boot-G8341-47.2.A.6.30-hideunlock-rooted.img
Click to expand...
Click to collapse
@SGH-i200, that sounds good. Now just flash it:
Code:
adb reboot bootloader
fastboot flash boot boot-G8341-47.2.A.6.30-hideunlock-rooted.img
disconnect from usb and power on.
If it booted from usb, I believe it should boot just fine if flashed as above too.
j4nn said:
If it booted from usb, I believe it should boot just fine if flashed as above too.
Click to expand...
Click to collapse
I flashed your patched kernel again and got into a bootloop: Bootloader unlocked warning and white SONY splash screen in an endless loop.
Since my XZ1 was connected to my Windows workstation already, I simply long pressed the volume up button till the notification light went blue, and booted into twrp to restore the stock kernel (rooted by Magisk to remove the dmverity stuff).
@SGH-i200, you are right, it is the verity thing.
I've assumed that verity is ignored when kernel detects unlocked bootloader, because the dm-android-verity kernel component used that is_unlocked() call to:
/* Allow invalid metadata when the device is unlocked */
- that comment is in the dm-android-verity.c source code.
But it looks like that is only a corner case and if verity metadata is valid, verity is active (if not disabled in device tree) even with unlocked bootloader.
Now I am wondering: for OTA updates we need untouched system, so having verity enabled in the kernel is good for this purpose - when you flash something that writes to system or vendor, you may detect it soon enough to be able to tell what it was. The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions.
From this point of view it should be all good then.
But I understand that the "alternative" use of this kernel, i.e. not planning to do FOTA at all, just using only the unlock hide feature restoring drm functionality and using root the old way (with real writes to system) may be liked.
For this, just use magisk manager main screen, in "Advanced Settings" unselect the "Preserve AVB 2.0/dm-verity" option and then use the "Magisk INSTALL" button, confirm install of Magisk-v*.zip, select "Patch Boot Image File", browse to sdcard where you put my kernel image and select it.
Magisk will repack the boot image disabling dm-verity in device tree blobs, noting where you can find patched_boot.img.
Flash that and you should be good to go.
This procedure is valid for all my pie kernel builds.
I will repack the oreo 16.20 build as using magisk manager gui would not keep the magisk patch for sony ric daemon.
-- edit --
Updated post#3 with downloads of oreo kernels noverity repacks.
Thanks for the kernel but after flashing the kernel the phone don't go into doze (deep sleep). Any suggestions on this?
j4nn said:
Now I am wondering: for OTA updates we need untouched system, so having verity enabled in the kernel is good for this purpose - when you flash something that writes to system or vendor, you may detect it soon enough to be able to tell what it was. The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions. From this point of view it should be all good then.
Click to expand...
Click to collapse
I use AdAway and activated NightLight by copying a apk to /vendor/overlay .
Thanks for creating the noverity Oreo kernel versions! :good:
---------- Post added at 09:04 AM ---------- Previous post was at 08:57 AM ----------
j4nn said:
The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions.
But I understand that the "alternative" use of this kernel, i.e. not planning to do FOTA at all, just using only the unlock hide feature restoring drm functionality and using root the old way (with real writes to system) may be liked.
For this, just use magisk manager main screen, in "Advanced Settings" unselect the "Preserve AVB 2.0/dm-verity" option and then use the "Magisk INSTALL" button, confirm install of Magisk-v*.zip, select "Patch Boot Image File", browse to sdcard where you put my kernel image and select it.
Magisk will repack the boot image disabling dm-verity in device tree blobs, noting where you can find patched_boot.img. Flash that and you should be good to go. This procedure is valid for all my pie kernel builds.
Click to expand...
Click to collapse
If I flash your patched Pie kernel via TWRP and flash Magisk right after, this should have the same effect as patching your kernel via the Magisk app, right?
@j4nn - "using root the old way (with real writes to system)" - will flashing Magisk via TWRP change this to system-less root?
sinkoo1979 said:
Thanks for the kernel but after flashing the kernel the phone don't go into doze (deep sleep). Any suggestions on this?
Click to expand...
Click to collapse
I have no idea. In my opinion, if you get such behaviour with my kernel, you will get exactly the same behaviour with stock kernel of the same version.
My kernel is compiled from sony's open source kernel package, with kernel config that's identical (except few comment lines) to the one compiled in stock kernel.
My kernel patch only fixes kernel command line that comes from bootloader and hijacks trust zone api to mask the bootloader status to appear as still locked to firmware's userspace.
These changes hardly could have any influence on power saving behaviour.
Please flash the same version stock kernel and test again for deep sleep.
Could not be that caused by some app you've installed?
SGH-i200 said:
If I flash your patched Pie kernel via TWRP and flash Magisk right after, this should have the same effect as patching your kernel via the Magisk app, right?
@j4nn - "using root the old way (with real writes to system)" - will flashing Magisk via TWRP change this to system-less root?
Click to expand...
Click to collapse
Most likely flashing magisk via twrp after flashing the patched pie kernel would disable verity too.
Using the image file - you have it under your control.
Flashing from twrp - some magisk scripting tries to detect if verity should be disabled or not.
Also a kernel image already containing magisk contains the setting of verity and encryption - not sure how that is used when flashing magisk again over it.
I tried it with my xz1c and verity was flipped from enabled to disabled - so the same effect (this time).
But as described, some detection is used, so the results might not always be the same.
j4nn said:
I have no idea. In my opinion, if you get such behaviour with my kernel, you will get exactly the same behaviour with stock kernel of the same version.
My kernel is compiled from sony's open source kernel package, with kernel config that's identical (except few comment lines) to the one compiled in stock kernel.
My kernel patch only fixes kernel command line that comes from bootloader and hijacks trust zone api to mask the bootloader status to appear as still locked to firmware's userspace.
These changes hardly could have any influence on power saving behaviour.
Please flash the same version stock kernel and test again for deep sleep.
Could not be that caused by some app you've installed?
reflashed stock firmware and everything is fine. Thanks for the kernel.
Click to expand...
Click to collapse
j4nn said:
Downloads
This is for alternative use only - please see post#10 for more details.
boot-G8341-47.1.A.16.20-hideunlock-rooted-noverity.img
boot-G8342-47.1.A.16.20-hideunlock-rooted-noverity.img
Screenshots of XZ1c FOTA system update from pie 47.2.A.4.45 to pie 47.2.A.6.30 version
(video available here since 08:10 time)
Click to expand...
Click to collapse
Hi j4nn
I unlocked my bootloader on 47.1.A.16.20 and lost my drm keys. I upgraded via newflasher_v13 to 47.2.A.4.45 Customised SG as that is where i am based and where my phone is from. Unfortunately when I flash boot-G8342-47.2.A.4.45-hideunlock-rooted.img my phone still boots up showing the device has been unlocked and the Backup and Restore feature of Xperia devices does not work. Am I correct to say if I lost my drm keys that I am unable to use this kernel to hide my bootloader unlock?
Thank you for answering me.
Working fine on xz1 pie 47.2.A.6.30 with blx firmware, Kernel flashed with twrp, widevine is L1 now, and Bravia engine working
@leonaheidern, the kernel would hide the unlocked bootloader regardless you lost drm keys or restored locked TA.
Please check you kernel build date when you boot your phone in about menu.
@j4nn, I have a quick question and a bit off topic, I'm still tinkering a bit but I did manage to backup my ta. and I flashed janjan's so things may seem a bit off, (see pic).. but I did restore my ta. before flashing Jan's kernel, any idea what may happen if I flashed yours on top?
oh and everything is working..
@lilbrat, I guess that the result would be the same if you flashed my kernel without flashing janjan's before it.
Just note please, my kernels as they are have verity enabled, so you need to have unmodified stock fw.
Or disable verity as hinted for alternative use.
With my kernel and restored TA your security screen would look perfect as with a still locked phone.
j4nn said:
@lilbrat, I guess that the result would be the same if you flashed my kernel without flashing janjan's before it.
Just note please, my kernels as they are have verity enabled, so you need to have unmodified stock fw.
Or disable verity as hinted for alternative use.
With my kernel and restored TA your security screen would look perfect as with a still locked phone.
Click to expand...
Click to collapse
OK.. thanks for the info... now I have another question, now that xz1 has a new update out and granted it will take you a bit to catch up if you need to redo all your kernels you have going... (great work by the way) Will I need to reflash my ta. backup for the new firmware and or just your kernel?