Hello,
this is a kernel tuned on battery life. It is supposed for stock M4 Aqua Android 5.0 version. Should work on all stock based rom, on all 23xx devices if bootloader is unlocked.
Please be careful and make a backup.
Tested devices
- Sony Xperia M4 Aqua E2306 OS: Sony Stock 5.0 26.1.A.3.111 :good:
- Sony Xperia M4 Aqua E2306 OS: Sony Stock 5.0 26.1.A.3.120 :good:
- Sony Xperia M4 Aqua E2333 OS: Sony Stock 5.0 26.1.B.3.109 :good:
Install instructions:
- boot into recovery
- backup full system (boot and system to restore previous version; data to avoid data loss)
- flash the zip file (see second post attachment)
Revert instructions
- restore boot, system
Additional instructions:
- for low power mode (only use little cluster, long battery life, but poor performance, ok for browsing, etc. to survive a desert holiday):
-- echo 1 > /sys/module/cluster_plug/parameters/low_power_mode
- for normal mode:
-- echo 0 > /sys/module/cluster_plug/parameters/low_power_mode
- reboot will restore normal mode (you can use script tools from market to make buttons to switch easily)
- the following script can be used with $cripter app (run as root) so you can make a toggle icon to change between modes:
Code:
#!/system/bin/sh
echo 1 > /sys/module/cluster_plug/parameters/active
STATE=$(cat /sys/module/cluster_plug/parameters/low_power_mode)
if [ $STATE -eq 1 ]
then
echo 0 > /sys/module/cluster_plug/parameters/low_power_mode
else
echo 1 > /sys/module/cluster_plug/parameters/low_power_mode
fi
echo "low power consumption"
cat /sys/module/cluster_plug/parameters/low_power_mode
init.d support:
- this kernel brings you init.d support, so no need to use other scripts to enable it
-- busybox needs to be installed in /system/xbin
Code:
mkdir /system/etc/init.d
chmod 755 /system/etc/init.d
(put a script there)
chmod 755 /system/etc/init.d/00_myscript
Please report back if it works or not with your device info.
Credits:
@kaiiori: thanks for your "xperia M4 high temperature Decrease"; i based my scripts on your idea (but took them from another device)
@vinay: thanks for help with kernel assembly
for cluster_plug: all guys which worked on it in CM development
Kernel sources:
https://github.com/cyclon1978/m4aqua
Greetings,
Andreas
Changelog:
1.001 [Attachment ckp-1.001.zip]
- undervolt to reduce heat
1.000 [Attachment ckp-1.000.zip]
- added cluster_plug
- msm_performance.c updated to avoid problems with cluster cache
- modified system scripts to make ondemand work (as default), enable cluster cache (also as default)
Let me see if i understand: this kernel works on locked bootloader too?? I've just flash it with recovery??
romeo_charly said:
Let me see if i understand: this kernel works on locked bootloader too?? I've just flash it with recovery??
Click to expand...
Click to collapse
I don't know... locked bootloader checks kernel signature on some xperia devices. You have to try it
The recovery image is definitely not checked, so why should they check the kernel partition... please report back if it works.
To revert if you get bootloop just enter recovery and restore kernel (plus system to revert all changes).
Thanks for testing!
Working on E2306 version with 26.1.A.3.120 firmware!
wich are the features of this kernel?? cluster_plug works turning off and on little cluster automatically?
Works on E2306 on 3.111!
donalberto17 said:
wich are the features of this kernel?? cluster_plug works turning off and on little cluster automatically?
Click to expand...
Click to collapse
Exactly. The little cluster is turned off if not required so the device can last longer. Performance should not be affected.
It didn't work for me on E2306 on .311 My device doesn't turn on 8|
I tried installing it on E2303 and now my phone it doesn't start anymore...it keep restarting after xperia logo...
What can i do? i have bootloader locked and No at allow unlock status...
Is my phone dead?
Try to flash the fw with flashtool... It should work
Sent from my E2303 using Tapatalk
donalberto17 said:
It didn't work for me on E2306 on .311 My device doesn't turn on 8|
Click to expand...
Click to collapse
Your bootloader is locked?
vic604 said:
Try to flash the fw with flashtool... It should work
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
or just enter recovery and restore kernel / boot from the backup you made.
cyclon1978 said:
or just enter recovery and restore kernel / boot from the backup you made.
Click to expand...
Click to collapse
I can't enter recovery, the phone restarts before led turn on ...
What i did not mention, is that when i have made my backup and flash the kernel, i have received some messages with red text, something about "firmware..."
And after flashing, i made a cache and dalvik cache clean... should be something related to this?
vyrussu said:
I can't enter recovery, the phone restarts before led turn on ...
What i did not mention, is that when i have made my backup and flash the kernel, i have received some messages with red text, something about "firmware..."
And after flashing, i made a cache and dalvik cache clean... should be something related to this?
Click to expand...
Click to collapse
If bootloader is locked you can use sony software to repair it. After that you can install recovery and restore your backup / data.
The cache/dalvik cache clean is not required, but wont break anything. The red text... i dont know...
I'll try later to reinstal original software with Sony Companion or by flashtool and let you know if i succeeded, now i'm at work...
The message in red was something like: cannot access firmware partition ... maybe because i have locked BL
using with rooted, bl unlocked version of e2303 (26.1.A.3.111). i don't have any problems right now. overall performance seems to be improved, so thank you sir.
what i want to ask is this, i am a link2sd user and i want to improve app opening speeds, how can i do this with this kernel installed?
(i am using a korean company's micro sd with r/w speeds of 95/90 by the way)
lazarusxd said:
using with rooted, bl unlocked version of e2303 (26.1.A.3.111). i don't have any problems right now. overall performance seems to be improved, so thank you sir.
what i want to ask is this, i am a link2sd user and i want to improve app opening speeds, how can i do this with this kernel installed?
(i am using a korean company's micro sd with r/w speeds of 95/90 by the way)
Click to expand...
Click to collapse
sdcard speed tweaks are possible, it's a question of time and priorities...
Ok, so i managed to flash my phone with Sony Companion and now everything is ok... so it seems that this kernel is not compatible with phones who have locked boot-loader... unlucky me...
Anyway, keep the good job!
Off:
Anybody knows a way to unlock boot-loader if it has status: Unlock bootloader allowed: No ??
Only the carrier from witch the phone is bought can unlock this?
It worked for me e2333 unlocked bootloader
I have a question, could you add wake gestures to kernel?
Related
-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***
Welcome to the Xperia Z Ultra Questions & Answers thread!
I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones!
If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.
Currently supported XPERIA models:
These are also links to the device specific Q&A threads.
Xperia Z: SO-02E, C6602, C6603, C6606, C6616
Xperia ZL: C6502, C6503, C6506
Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351
Xperia Z Ultra: C6802, C6806, C6833, C6843
Xperia Z1: C6902, C6903, C6906, C6943, C6916
Xperia Z1 Compact: D5502, D5503, D5506
Xperia Z2: D6502, D6503, D6506, D6543, D6563
Xperia Tablet Z2: SGP511, SGP512, SGP521, SGP551, SGP561
Xperia ZR: C5602, C5603, C5606
Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
Xperia S: LT26i
Xperia SP: C5302, C5303
Xperia T2 Ultra: D5303, D5322
Xperia Z3: D6603, D6633, D6643, D6653, D6616
Xperia Z3 Compact: D5803, D5833
Xperia Tablet Z3 Compact: SGP621, SGP641, SGP651
To follow development, be sure to check the DevDB thread!
INSTALLER: How to install using the installer:
Make sure you have USB debugging turned ON.
download ZU-lockeddualrecovery[VERSION]-BETA.installer.zip from http://nut.xperia-files.com
Windows:
unpack at C: or somewhere you will remember!
navigate to the resulting directory and look for install.bat, double click it to run;
Linux:
unpack in your home folder with 'unzip ZU-lockeddualrecovery[VERSION]-BETA.installer.zip'
navigate to the resulting directory and 'chmod +x install.sh', then execute it, follow instructions.
Your phone WILL reboot when installation has completed and it will go into the default recovery for the first boot.
Reboot to system from recovery to allow the installer to clean up after installation (it is safe to skip this step).
Enjoy DUAL RECOVERY!
How to install or update using a previously installed (XZDualRecovery) recovery:
Create a backup of /system/bin/chargemon and keep it somewhere safe, then just flash ZU-lockeddualrecovery[VERSION]-BETA.flashable.zip from http://nut.xperia-files.com using CWM or TWRP.
How to remove:
Delete the following files:
/system/bin/recovery.twrp.cpio.lzma (or .tar)
/system/bin/recovery.cwm.cpio.lzma (or .tar)
/system/bin/recovery.philz.cpio.lzma
/system/bin/charger
/system/bin/dualrecovery.sh
/system/bin/mr
Rename /system/bin/mr.stock to /system/bin/mr to restore stock functionality, then inside /system/bin/ rename chargemon.stock to chargemon check its permissions (should be 755 or otherwise visible as -rwxr-x-r-x). Done!
When installing custom ROMs:
Be sure to flash ZU-lockeddualrecovery[VERSION]-BETA.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!
How to use:
At boot, once you feel the phone vibrate and while you see the green led burn:
- press VOL-UP for PhilZ Touch;
- press VOL-DOWN for TWRP.
To enter Vanilla CWM, you will need to use the (free) NDRUtils app from the Play store
2.x Features:
When you have a SDCard1 and the XZDualRecovery is able to use it, you can put a file called 'donotrun' inside the XZDualRecovery log folder to make XZDualRecovery escape following boot attempts.
If you find yourself in a bootloop situation, take out your SDCard1 and put that file in the directory if it exists using a PC. Reboot your phone with Power+Vol-UP and you will be able to boot your phone as if there was no recovery there!
XZDualRecovery will signal the escape or any reason why it would not be able to continue normal operation with a 2 second burn of your LED in the color RED. A reason would be a broken /cache and no SDCard1 or a busybox in /system/xbin which does not support the lzcat command. If you see that, check /tmp/XZDualRecovery for a logfile there, it will tell you why.
XZDualRecovery will try to use your SDCard1 for logging and functionality, if it has been formatted with ext2/4, FAT16/32 or exFAT. NTFS is currently unsupported.
XZDualRecovery now prevents the RIC service from starting up, this means when running XZDualRecovery the Remount-Reboot fix is no longer needed.
Defaults:
The default on first boot with the boot-to-recovery flag set by any recovery is PhilZ Touch Recovery.
Init.d support is disabled by default, set dr.initd.active to true to enable it.
Insecure ramdisk support is disabled by default, set dr.insecure.ramdisk to true to enable it, set to 'power' to boot it by pressing the power button at boot.
Error reporting:
Please, when reporting errors or problems:
Put up a notice in this thread providing the package name you used to install or update;
Include ROM name and/or FW version numbers;
Include what SU apk you are using (SuperUser or SuperSU)
Send me the contents of all the log files from right after a failed boot attempt or a link to an archive containing these logs by PM (that's including the .old rotation logs!). If you have no website or online location to store the logs, PM me for an email address to send them to.
Logs can be found inside:
/cache/recovery
/tmp/XZDualRecovery
/storage/sdcard1/XZDualRecovery
/cache/XZDualRecovery (if the previous exists, this one will not!)
NOTE: I need them ALL!
I really need them to troubleshoot what failed and what worked OK. Thank you!
Special Thanks:
@DooMLoRD for all his excellent work on our much loved Sony phones!
The Team Win developers for TWRP
The ClockWorkMod developers for CWM
@alexocean for his awesome job testing almost all FW releases and the discovery of SuperSU causing problems for the installation of this recovery!
@RoberM for testing
@surdu_petru for testing and handy pointers
@Androxyde for allowing to use his linux and mac adb binaries.
@lancebukkake for finding the TWRP 'fix' to use exFAT formatted sdcards!
@delewer for the final fix for TWRP and its use of exFAT formatted sdcards
@DevShaft for some code help on the windows installer (the menu!)
@Androxyde again, but now for his bash code/script suggestions... oh boy this guy is a genius! :highfive:
@Tamirwig and @shoey63 for their excellent job at testing early BETA's (Xperia Z)
@gregbradley for his extensive testing on the Xperia Z1
Well, enjoy! :fingers-crossed:
The origins of this XZDualRecovery package are in the packages done by:
Krabappel2548, Cpasjuste and DooMLoRD
Thank you for your excellent work guys! :victory:
[Locked Bootloader]CWM recovery 6.0.2.8 for locked bootloaders v4[25-03] by Krabappel2548
[APP/RECOVERY] TWRP 2.4.3.0 for lockled bootloaders installer by Cpasjuste
[KERNEL][Z] DooMKernel {JB}(v06)[20130414] by DooMLoRD
Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:
Awesome, and thank you! I can't see a reason why i should flash this if i already have recovery/TWRP installed? Or? Would you recommend me to install this one, or isn't it that big of a deal?
LordManhattan said:
Awesome, and thank you! I can't see a reason why i should flash this if i already have recovery/TWRP installed? Or? Would you recommend me to install this one, or isn't it that big of a deal?
Click to expand...
Click to collapse
No, it's a personal preference really
XZDualRecovery has been created with choice in mind. It's feature rich and more are coming but if you can do without the features...
Hi guys, can someone tell me what i am doin wrong??
1. Hes not asking about choice from menu.
and also
2. hes going forward saying theres no choice64 and cannot push any files...
http://feb.imghost.us/FUDj.png
//okay, i am stupid i suppose to navigate there through cmd, not explorer. Sorry for bothering.
downloaded ZU-lockeddualrecovery2.7.92-BETA.installer
(model 6802; Clean non-root .136)
what is this:
ro.build.product=C6802
ro.build.id=14.2.A.1.136
setsockopt() failed: Bad address.
this device is not supported.
kallsyms_addresses search failed.
Any help ?
avetny said:
downloaded ZU-lockeddualrecovery2.7.92-BETA.installer
(model 6802; Clean non-root .136)
what is this:
ro.build.product=C6802
ro.build.id=14.2.A.1.136
setsockopt() failed: Bad address.
this device is not supported.
kallsyms_addresses search failed.
Any help ?
Click to expand...
Click to collapse
Check the 3rd post on the development topic... It clearly states not all rom versions can be rooted like this.
You need the 534 JB4.2 release for this to work.
I didn't check cuz I thought it for developers
Thanks for help
Dual recovery was working fine, now it stopped and I'm getting the red LED burn.
I was reading the OP again and it mentioned Busybox. If I installed a busy box pro apk I had, could that have broken the dual recovery? Should I just reinstall?
I didn't flash anything or reinstall ROMs prior to it breaking.
Poi25 said:
Dual recovery was working fine, now it stopped and I'm getting the red LED burn.
I was reading the OP again and it mentioned Busybox. If I installed a busy box pro apk I had, could that have broken the dual recovery? Should I just reinstall?
I didn't flash anything or reinstall ROMs prior to it breaking.
Click to expand...
Click to collapse
That depends on the version of XZDR you installed really... If you had the latest it should fix busybox by itself.
Check the logs inside the XZDualRecovery folder, it will probably tell you what's wrong.
[NUT] said:
That depends on the version of XZDR you installed really... If you had the latest it should fix busybox by itself.
Check the logs inside the XZDualRecovery folder, it will probably tell you what's wrong.
Click to expand...
Click to collapse
I had .95 beta. Busybox messed it up, uninstalling busybox did nothing. I just restored the phone and fixed it real quick, no big deal.
Hi all,
If I am already on TWRP, can I simply flash the zip file then reboot recovery? Just curious
thanks!
kipue said:
Hi all,
If I am already on TWRP, can I simply flash the zip file then reboot recovery? Just curious
thanks!
Click to expand...
Click to collapse
As long as you are using a stock based rom, yes.
[NUT] said:
As long as you are using a stock based rom, yes.
Click to expand...
Click to collapse
Can I use it for a KitKat ZU?
Sent from my C6802 using Tapatalk
quachhanthanh said:
Can I use it for a KitKat ZU?
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
As long as it is already rooted, yes. Otherwise you will have to downgrade to the last rootable version (.532) to root and upgrade to KK.
[NUT] said:
As long as it is already rooted, yes. Otherwise you will have to downgrade to the last rootable version (.532) to root and upgrade to KK.
Click to expand...
Click to collapse
I am on rooted (.136) with ur dual recovery. So I can download a KitKat zip flashable and install it through recovery?
Sent from my C6802 using Tapatalk
Never Mind..
I'm running Monx and I've been using TWRP for a while, but I want to try PhilZ, and I can't get this thing to work. Is being on Monx messing me up? When I install this and tell it to boot PhilZ, the phone just turns off. Then if I hold Vol-Up and Power, the phone stays off. I can still boot TWRP just fine, but it seems like everything else is getting blocked off. Any advice?
installation says device is not supported for me
i have c6833 running 4.4.2
Required:
- Flashtool in the latest version from: http://flashtool.net
- DualRecovery by NUT as installer.zip: http://nut.xperia-files.com (Download the correct one for your device and at least version 2.8.1+!)
- Root on 23.0.A.2.93 (Download) for example with this method: http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Featurelist:
- SuperSU integrated
- DualRecovery by NUT integrated (2.8.1)
Can be used on locked and unlocked bootloader.
Firmware Files:
D5803 and D5833
- Flashable.zip's and FTF files in folders - sorted by devices
The Flashable.zip i've created with the mighty tool PRFCreator by zxz0O0.
Installation/Update (short) guide:
0. Downgrade to the firmware 23.0.A.2.93 and root it (with giefroot)
0.1. Install the LockedDualRecovery by NUT with the installer.zip (install.bat)
1. Put the downloaded update file (ROM.zip) on your device. I recommend you to put it directly on the device.
2. Boot into the recovery (While rebooting -> when the info LED flashs -> press shortly the VOL button for the Recovery you prefer)
(On Recovery you may create a twrp/cwm backup of your device if you get any issues on updating process!)
3. Flash the ROM update file (.zip) with "install zip".
4. Wipe cache and dalvik cache (perhaps under advanced).
5. Reboot to system.
You may have to wait some minutes on the first boot because of initializing system for first time (optimizing apps etc.).
What to do if you get permission errors? (While installing for example the Recovery)
Untill NUT updates his DualRecovery you should fix permissions with ADB with the following commands:
(tested with command line from the giefroot_V...\files\ directory -> shift + right mouse -> open cmd "here")
Either you could try the modified DualRecovery (installer) by NUT (modified by monx): http://d-h.st/iM9p
Code:
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
Special Thanks to:
[NUT] (DualRecovery and his efforts!)
zxz0O0 (giefroot rooting tool, PRFCreator and his efforts!)
XDA: DevDB Information
[STOCK][D58XX][4.4.4] Firmware 23.0.1.A.5.77 Generic [ROOT/XZDR/SuperSU], Stock Firmware Xperia Z3 Compact
Contributors
meetdaleet
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: Stock - 23.0.A.2.93
Version Information
Status: Stable
Release Date: 2015-01-25
Created 2015-01-25
What about d5833 ftf
@muzab a
I'm currently creating the firmware files and will upload them further.
I think they will be available at the evening
Kind Regards
meet
Which ftf to use for d5833?
Great , thanks! In case we can go back to totally stock? (For any case) And for lollipop I imagine will have to flash a rom, right?
Matteo Mazzu said:
Great , thanks! In case we can go back to totally stock? (For any case) And for lollipop I imagine will have to flash a rom, right?
Click to expand...
Click to collapse
You may delete some specific folders on internal SD (sdcard0) and flash a ftf without changing anything (like wipes etc.).
abj2aqua said:
Which ftf to use for d5833?
Click to expand...
Click to collapse
I've just added the D5833 files to the OP.
Kind Regards
meet
The firmware file is D6603, not D5803
Sorry i've just put the wrong link on the OP.
Corrected it right now
Thanks for yozr help!
You can find all my files under:
http://mega.leetbox.net
Kind regards
Meet
Thanks a lot!
i read in the op that this can be flashe don locked bootloaders aswell as unlocked but i also heard that if we want to flash any rom so we must unlock bootloader , so im a bit confused now? can i just flash it on locked bootloader?
pw1nce said:
i read in the op that this can be flashe don locked bootloaders aswell as unlocked but i also heard that if we want to flash any rom so we must unlock bootloader , so im a bit confused now? can i just flash it on locked bootloader?
Click to expand...
Click to collapse
The "ROM" i've opened to you on this thread is a stock rom (just with SuperSU and DualRecovery integrated).
There is the stock kernel inside why it runs on both. Locked and unlocked bootloader!
meetdaleet said:
The "ROM" i've opened to you on this thread is a stock rom (just with SuperSU and DualRecovery integrated).
There is the stock kernel inside why it runs on both. Locked and unlocked bootloader!
Click to expand...
Click to collapse
ok thnx broo , do we need to wipe system , data and then flash or dirty flash ? thanks
edit : i just did as mentioned in op , after flashing i downloaded the recovery and ran install.bat , it installed the new recovery mentioned in op , it rebooted into that recovery , the icons are too damn big , i can only see ''install'' , wipe , backup option on all the screen , now i have no idea how to get out of here , power buttonn evn if i hold wont work , any suggestion?
pw1nce said:
ok thnx broo , do we need to wipe system , data and then flash or dirty flash ? thanks
edit : i just did as mentioned in op , after flashing i downloaded the recovery and ran install.bat , it installed the new recovery mentioned in op , it rebooted into that recovery , the icons are too damn big , i can only see ''install'' , wipe , backup option on all the screen , now i have no idea how to get out of here , power buttonn evn if i hold wont work , any suggestion?
Click to expand...
Click to collapse
Press on Power + high Volume
Two questions, the .93 fw was country specific, this update doesn't require a specific version?
I feel kind of clumsy asking this but i haven't found the meaning of "XZDR", what does it mean?
Thanks!
My root seems to have broke after flashing.Can't mount in root explorer
@pikeylfc,
Did you read the OP?
pikeylfc said:
My root seems to have broke after flashing.Can't mount in root explorer
Click to expand...
Click to collapse
meetdaleet said:
@pikeylfc,
Did you read the OP?
Click to expand...
Click to collapse
There's a problem with RIC on .5.77, making it impossible to mount system r/w. Nothing to do with root, as you can do other root actions just fine.
You just need to update XZDR, [NUT] just uploaded 2.8.1, which has been fixed for Z3C on .77. Also TWRP has been updated.
Edit: Sorry, see that you already updated OP for XZDR 2.8.1.
Sydrox said:
I feel kind of clumsy asking this but i haven't found the meaning of "XZDR", what does it mean?
Thanks!
Click to expand...
Click to collapse
Same question here what is XZDR?
Sydrox said:
I feel kind of clumsy asking this but i haven't found the meaning of "XZDR", what does it mean?
Click to expand...
Click to collapse
ovizii said:
Same question here what is XZDR?
Click to expand...
Click to collapse
XZDualRecovery
What is XZDR? There are two versions one with that and other one without...
Another question: after done all the steps in the op, if we flash another kernel (with locked boot) it will boot?
Thanks
Sent from my D5803 using XDA Free mobile app
Simply put, this is (as of now) the latest TWRP (with F2FS, without multirom - sorry).
https://www.mediafire.com/?mj5885q1x5lamzv
Either install it normally or by using fastboot:
Code:
fastboot flash recovery fota.img
If you head over to AndroPlus' thread and download his latest kernel (as of writing, that is Z3_AndroPlusKernel_F2FS_v26a.zip) you could format /system and /cache as F2FS and it will boot and run fine, /data will however, sadly, not format or work as F2FS. But so far, /system and /cache does.
* Goal: get /data to work with F2FS as well
Thanks for contributing ! Will Multirom ever get integrated by any chance ?
Sent from my Xperia Z3 using XDA Free mobile app
I didn't think anybody was interested.
But sure, I'll see what I can do!
You do need to wait a few days though.
Sure I think there would be a good amount of interest considering it would mean that no matter what happened to the Kernel/recovery we would still be able to fall back on Fota for Multirom.
Sure take your time, would be great if possible.
Sent from my Xperia Z3 using XDA Free mobile app
I don't suppose we are any closer to having MultiRom integrated into this ?
Thanks bud
Sent from my Xperia Z3 using XDA Free mobile app
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
so you mean i can just flash this into fota and boot into it? Thanks.
kjames2001 said:
so you mean i can just flash this into fota and boot into it? Thanks.
Click to expand...
Click to collapse
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
kjames2001 said:
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
Click to expand...
Click to collapse
Lol, just Remembered, you need Cm to use it.
来自我的 D6603 上的 Tapatalk
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
You need something that, in the init, at boot, waits to check and see if you hit a set key.
"If set key is pushed - load "kernel" (or really ramdisk) from FOTA-partition"
Or more correctly, as @AndroPlus has coded it:
Code:
if [ -n "$POWRKEYCHECK" ]
then
#load FOTA ramdisk
busybox mknod -m 600 ${BOOTREC_FOTA_NODE}
busybox mount -o remount,rw /
busybox ln -sf /sbin/busybox /sbin/sh
extract_elf_ramdisk -i ${BOOTREC_FOTA} -o /sbin/ramdisk-recovery-fota.cpio -t / -c
busybox rm /sbin/sh
load_image=/sbin/ramdisk-recovery-fota.cpio
busybox echo 'Selected FOTA recovery' >>boot.txt
fi
If you want to do that yourself I can attach the original Sony LP kernel, dt.img and ramdisk for you.
Stock ROM
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
da900 said:
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
Click to expand...
Click to collapse
Well, to put it easy:
On boot the phone has a script that tells it to look for certain keys to be pushed.
1. If volume up is pushed then go to CM Recovery
2. If volume down is pushed then go to TWRP Recovery
3. If camera button is pushed then go to...
And so on. If there is no script telling the phone to do so (original Sony kernel/ramdisk) then the phone will just simply boot in to android. Nothing tells it to do otherwise.
If there is a script that only tells the phone to boot in to CM recovery or what ever, then that's the only options the phone has.
The kernel (or rather, the ramdisk with the kernel) you use has to have support for booting from the FOTAKernel-partition. If there is no support for it in the kernel then the installed FOTAKernel will just exist there. Not hurting anything, but not doing any good either.
TL;DR - ask the creator/developer of your kernel to add booting from the FOTAKernel as a feature.
Is there any automated or hassle-free way of replacing the nightly CM12 installer script with the script required for this recovery? Or do I have to download the zip manually, unzip, replace the sript manually, rezip, transfer the zip to my Z3, and then flash - every day?
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
Wrong. On Sony devices, once the bootloader is locked, the device will NOT boot the contents of the FOTAKernel partition.
This is similar to older Samsung devices.
The problem with this, of course, is that you normally can't change recovery without changing the kernel.
The workaround developed (IIRC by Dees_Troy of TWRP) was to have the boot kernel extract its recovery ramdisk from the FOTAKernel partition if present, allowing a person to switch recoveries without switching kernels - but they still need a kernel that will read the ramdisk. Also, the recovery ramdisk present needs to "play nice" with the kernel itself, which can lead to problems when Qualcomm or Sony do things that break display compatibility. For example, I'm fairly certain most current Z3 FOTAKernel builds use RGBX_8888, which Qualcomm dropped support for in vanilla framebuffers (like what recovery uses) in newer kernels. So any FOTAKernel ramdisk that tries to use RGBX_8888 will fail, for example, with Sony AOSP (due to it using a newer 3.10 kernel)
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
[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.