Related
TWRP v2.8.6.0 (fota) with F2FS for: Z1, Z1c, Z2, Z3, Z3c, TabZ3c(LTE&WIFI)
Thanks to funiewski who inspired me/ teached me how to repack Z2 twrp to work with z1 and z1c.
This ain't my work! I've just been cooking with projects made by others. Thank TeamWin, [NUT], creator of Android Image Kitchen, and others
Use at your own risk!
Seems like fota TWRP for sirius (Z2) will boot on all these phones: Z1, Z1c, Z2 (offcourse), Z3, Z3c and TabletZ3c (both LTE and WIFI version)!
When repacked with res/ and default.prop from NUTs dual recovery, we got TWRP for each specific device.
Download folder:
Edit 25. september 2021: Please consider using newer recoveries than these old ones.
Officially supported Sony devices: https://twrp.me/Devices/Sony/
Includes Z1 (honami), Z2 (sirius), Z3 Compact (z3c), Z3 Tablet Compact Wi-Fi (scorpion_windy)
Unofficial
Z1 Compact (amami), by 115ek: https://forum.xda-developers.com/t/3960699/
Z1 (honami), by daviid99: https://forum.xda-developers.com/t/4316409/
If you are still interested in my old frankenstein builds:
MEGA.co.nz
https://mega.co.nz/#F!fh5hhL5L!xso7GESQ9AR556_nswFfTw
Google Drive
https://drive.google.com/drive/fold...ourcekey=0-0_o2xNplFlKcnt4IaxrUdg&usp=sharing
What is this?
This is a repacked TWRP from Z2 sirius, where I have:
- Added f2fs support by adding mkfs.f2fs and fsck.f2fs from blastagators TWRP.
- Shrinked images in twres/images folder. It wouldn't boot on my Z1c otherwise.
- Switched res folder and default.prop from respective ones from [NUT]s XZDualRecovery
More info? See recepy down below
Works for?
ONLY: Unlocked bootloader, AOSP based ROMs with support for booting a recovery from the FOTA partition.
Stock ROM, locked or unlocked bootloader: See [NUT]s project: http://nut.xperia-files.com/
How to install?
There are many ways in doing so. Fastboot: "fastboot flash recovery nameofrecovery.img" is the easiest IMO
Bugs?
Me and others have tested it, only bug atm seems to be:
- Can't adjust screen brightness in TWRP
Report if you find anything
Can you fix bugs?
Most probably not. If you find bugs regarding layout, images and stuff like that: Maybe.
This is not compiled, this is just repacked using Android Image Kitchen.
Bugs in this recovery will most probably be bugs that all TWRP builds share.
f2fs does not work!!
Yes it does. The recovery will format any partition to f2fs for you. But you need a compitable kernel to use it. Don't ask me for compitable kernels, google it.
Migrate to f2fs: http://forum.xda-developers.com/showthread.php?t=3004755
How to use f2fs on Sony Devices: http://forum.xda-developers.com/showthread.php?t=3056740
Recepy
Just repacking the Z2 recovery with f2fs-files will make a un-bootable IMG. I believe this is due to some limitations regarding size or something.
In order to get the file size down I made a new, simple "curtain.jpg". Plain black with the text "TWRP". Kind of clean and simplistic when I think about it And I found out that these PNGs can be compressed without getting grapchical glitches:
Code:
- file.png
- folder.png
- keyboard (all)
- medium-button.png
- menu-button.png
- slideout.png
- slider-touch.png
- slider.png
- unlock.png
How I did it:
- DL TWRP for Z2 (sirius), Android Image Kitchen, [NUT]s XZDualRecovery flashable for your device, and blastagators TWRP for LG G2
- Unpack blastergator TWRP with Android Image Kitchen. (drag'n'drop .IMG on to the "unpack.bat")
- In ramdisk/sbin "steal" these two files: mkfs.f2fs and fsck.f2fs. Store them some place safe.
- Cleanup Android Image Kitchen folder. (cleanup.bat)
- Open XZDualRecovery with 7zip. Go to system/bin. Open the twrp file. "Steal" the res/ folder and the default.prop file. Store it somewhere safe.
- Unpack TWRP for Z2 with Android Image Kitchen
- Change images in ramdisk/twres/images with these (they are compressed. Unless you use them the img won't boot: https://mega.co.nz/#!e9g1TRCI!vmGsPqVdqSnpcW6G8PC_saLLyyfqTL-1FhjQmggVvxA)
- Add mkfs.f2fs and fsck.f2fs to ramdisk/sbin.
- Replace res folder and default.prop with the ones from XZDualRecovery
- Repack with "Android Image Kitchen". (Double click on "repack.bat")
Links:
Z1 (Honami): Official TWRP - http://forum.xda-developers.com/showthread.php?t=3234877 | http://teamw.in/devices/sonyxperiaz1.html
Z1 (Amami) : Compiled TWRP with f2fs by hawkeyexp - http://forum.xda-developers.com/showthread.php?t=3173411
Z2 (Sirius): Official TWRP - http://forum.xda-developers.com/showthread.php?t=2772879 | http://teamw.in/devices/sonyxperiaz2.html
Z3c: Official TWRP - http://teamw.in/devices/sonyxperiaz3compact.html
Z3 Tablet (Scorpion_Windy): Official TWRP: http://teamw.in/devices/sonyxperiaz3tabetcompact.html
Do it Compiling by yourself and all will works like a charm.
You guys so funy use only ONE repacked images for all other devices which have different resolutions and different kernel base
UPDATE: Packed a individual recovery for each device, with /res folder and default.prop taken from [NUT]s XZDualRecovery. Installing amami CM with sirius recovery gets aborted..
Does this work with the Z3 tablet (scorpion-windy)?
Thanks
belrik said:
Does this work with the Z3 tablet (scorpion-windy)?
Thanks
Click to expand...
Click to collapse
It would probably boot, but installs of ROMs and similar would be aborted because device id on flashable zips would not match device id of recovery.
If you modify build.prop to fit your device, I bet it would work
EDIT: Made a img for tablet z3c. I believe both 4g and WIFI-version can use the same recovery (CM uses same device ID in their build.prop)
EDIT: Separate recovery.img is up for scorpion and scorpion_windy.
o-l-a-v said:
It would probably boot, but installs of ROMs and similar would be aborted because device id on flashable zips would not match device id of recovery.
If you modify build.prop to fit your device, I bet it would work
EDIT: Made a img for tablet z3c. I believe both 4g and WIFI-version can use the same recovery (CM uses same device ID in their build.prop)
EDIT: Separate recovery.img is up for scorpion and scorpion_windy.
Click to expand...
Click to collapse
could you build a second one for tabz3c with "scorpion_windy" device ID? the scorpion one does not flash cm12.1 on my SGP611.
2 Bugs I found:
-Inability to shut off the screen. Even happens when device displays the power (full screen picture of battery). This bug doesn't affect [NUT]'s recovery.
-TWRP crashes whenever you try booting to recovery via charging cable without the system attempting to boot to Android (in other words, turning on the phone with the power cable rather than the power button). The only way out is to hard reset.
Using Xperia Z1 (honami)
kentexcitebot said:
2 Bugs I found:
-Inability to shut off the screen. Even happens when device displays the power (full screen picture of battery). This bug doesn't affect [NUT]'s recovery.
-TWRP crashes whenever you try booting to recovery via charging cable without the system attempting to boot to Android (in other words, turning on the phone with the power cable rather than the power button). The only way out is to hard reset.
Using Xperia Z1 (honami)
Click to expand...
Click to collapse
Yep. Asked in the Z2 TWRP thread, Z2 owners don't have these bugs. Might be because we use z2 related stuff (kernel base) for other phones. If I learn to compile in future this should be fixed afaik. But as far as i know, there is nothing I can do (in regards of repack with other stuff) to fix these bugs.
o-l-a-v said:
Yep. Asked in the Z2 TWRP thread, Z2 owners don't have these bugs. Might be because we use z2 related stuff (kernel base) for other phones. If I learn to compile in future this should be fixed afaik. But as far as i know, there is nothing I can do (in regards of repack with other stuff) to fix these bugs.
Click to expand...
Click to collapse
I lack knowledge with TWRP+Recoveries+Pretty much a lot of things, but couldn't you repack NUT's recovery and try porting it to Lollipop? Maybe exclude Philz's version if it conflicts...?
Hi,
is it possible, to make also a Version for the Xperia ZL?
thanks for the scorpion_windy build! :good:
unlock with material theme has some troubles. i need to get the right line on the screen for wipe to work and also then it takes several tries.
TWRP 2.8.6.1 supposedly brings support for encryption (on bacon at least) [1]. Has anyone played with that on a sony device yet? Maybe created a first package to test?
[1] https://github.com/TeamWin/Team-Win-Recovery-Project/issues/333#issuecomment-105152622
can make a version for zr/zl/z? thx!
hi anyone : )
nostupidthing said:
can make a version for zr/zl/z? thx!
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z/orig-development/recovery-teamwin-recovery-project-t2982889
Z already has TWRP with f2fs and stuff.
If you need it for zr or zl simply repack it with res/ and default.prop from the correct phone. Guide in 1st post.
Hi, does it work for scorpion_windy with lollipop? Thx.
v2.8.7.0 is up! I'm on stock ROM now, so please check if it works
http://forum.xda-developers.com/showthread.php?t=3098573
2.8.7.0 on sony z1 (honami) with cm-12.1 is botting, gui is ok, but internal storage and sdcard not present.
hawkeyexp said:
2.8.7.0 on sony z1 (honami) with cm-12.1 is botting, gui is ok, but internal storage and sdcard not present.
Click to expand...
Click to collapse
same on amami.
EDIT: fixed in yesterday build with z1c res and default prop! :good:
rzlatic said:
same on amami.
EDIT: fixed in yesterday build with z1c res and default prop! :good:
Click to expand...
Click to collapse
still not working on honami...
This is TWRP 2.8.7, i.e. ramdisk-recovery..cpio built from source including the latest commit fixing failure to back to external SD. See here.: https://github.com/omnirom/android_bootable_recovery/commit/85161af11117431ff3a1d6b845e8faf35ef07b2c . I have also reduced annoyingly loud default vibration values...
This is not FOTA image, but rather a pre-built cpio ready to be included in your boot.img. It is built specifically for Xperia Z1 with all the appropriate flags.
Instructions:
1. Unzip the attached image, if you don't, you'll have a bootloop
2. Use Archi Kitchen to unpack your boot.img. Download from here: http://forum.xda-developers.com/showthread.php?t=2597220
3. Unpack kitchen, open terminal in that directory and do chmod a+x archi; then execute ./archi
4. Follow script directions and create a new project
5. Put your boot.img where the script tells you to
6. Execute ku to unpack kernel: you will have kernel directory in your project;
7. Go to /kernel/boot.img-ramdisk/sbin: you will see ramdisk-recovery.cpio file; just replace it with the attached one and execute kr to re-pack kernel.
8. You will have the new boot.img in project directory ready to be fastboot flashed.
9. If you touch anything else in unpacked kernel, your phone won't boot
10. From now and on, when you open archi kitchen, just pick (e) option for existing project and you can use any other boot.img to do the same.
optimumpro said:
This is TWRP 2.8.7, i.e. ramdisk-recovery..cpio built from source including the latest commit fixing failure to back to external SD. See here.: https://github.com/omnirom/android_bootable_recovery/commit/85161af11117431ff3a1d6b845e8faf35ef07b2c . I have also reduced annoyingly loud default vibration values...
This is not FOTA image, but rather a pre-built cpio ready to be included in your boot.img. It is built specifically for Xperia Z1 with all the appropriate flags.
Thanks. That is what I'm searching for for 2 days.
But it would be much better, if i could get totally rid of build in recovery.(TWRP will probabliy update.)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Introduction & Notes
Hello, I have created flashable zips containing the stock things for use with our Xperia SP. I used @MrSteve555's antique tutorial on how to package an ftf file into flashable zips.
I also made other might be useful zips that have each of their own purposes for those who wants it. Those zips are listed in the Addons Zip post.
As usual, I am not responsible for any damages caused on your SP. Flashing these are completely your choice and did I even forced you to do so? If you need help, just reply in the thread. :angel: As much as this might scare you, don't worry, it should work fine on your device
All zips are taken from FTFs that are not carrier-locked (thus the name Customised). Since the C5306 is a quite rare variant, the only version I can find that is not carrier-locked is the .205.
Steps
What you should do is choose the respective components that you want to flash to your phone. This will ultimately replaces the old one. Say for example, if you want to have the stock fotakernel, all you need to do is to flash the "fotakernel" zip. This will override any previous modifications that you have made on that partition such as custom recoveries.
Done.
Notes & Warnings
Warning!
The files are exclusive for its Xperia SP model. Do not attempt to take the risk in flashing other version for your Xperia SP model.
The stock kernel is not to be flashed if you are running a custom ROM! (yes, you can still safely flash FOTAKernel and RIL components without any harm)
Note!
Flashing the zips via Cyanogen Recovery is now possible. The zips are signed.
Requirements
Knows how to flash ZIPs via recovery
Knows what to flash
Acknowledged the disclaimer above
Components
These are the partitions that I have extracted:
boot
fotakernel
elabel *
modemst1 *
modemst2 *
fsg *
I didn't include the "system.img" of the stock ROM. If you intent to use Stock ROM, please consider FlashTool method instead.
* I have combined these 4 components in a single zip as they serve the same purpose: RIL (network)
Purpose of each zip files
c530x-stock-fota.zip - This will replace your current fotakernel partition with the stock one. Any custom recoveries that you have flashed using Rashr will ultimately gone.
c530x-stock-kernel.zip - This will replace your current boot partition and the kernel with the stock one. Any custom kernel that you hace flashed will be replaced.
c530x-stock-ril.zip - This will flash the stock RIL components.
Choose your Xperia SP model
This will bring you to the respective posts that contains respective files for your respective model of your Xperia SP.
C5303
C5302
C5306
Alternative install method for terminal enthusiasts
You can extract the zip and "dd" the img to the respective directories in /dev. This section is for terminal enthusiasts so I assume that you guys know where is this located and also knows what the hell is "dd". I suggest for the "dd" to use read block of 4096 for faster flashing process.
Example terminal command:
Code:
dd if='Kernel.elf' of='/dev/block/platform/msm_sdcc.1/by-name/Kernel' bs=4096
Here is the list for reference:
Kernel.elf ----> /dev/block/platform/msm_sdcc.1/by-name/Kernel
FOTAKernel.elf ----> /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
LTALabel.ext4 ----> /dev/block/platform/msm_sdcc.1/by-name/LTALabel
modemst1.img ----> /dev/block/platform/msm_sdcc.1/by-name/modemst1
modemst2.img ----> /dev/block/platform/msm_sdcc.1/by-name/modemst2
fsg.img ----> /dev/block/platform/msm_sdcc.1/by-name/fsg
Click to expand...
Click to collapse
One small request from me
If this in some ways helped you, consider thanking this main post Your thank can hugely motivates me in contributing more!
C5303
This section is for the the C5303 model only
NOTES
Please read the main post if you haven't read them!
For this model, I have used Customised Singapore 12.1.A.1.207 / R2B CDA 1272-4881
Whole Folder [Google Drive]
FOTAKernel c5303-stock-fota [Download]
Kernel c5303-stock-kernel [Download]
elabel, modemst1, modemst2, fsg combined c5303-stock-ril [Download]
C5302
This section is for the the C5302 model only
NOTES
Please read the main post if you haven't read them!
For this model, I have used Customised Singapore 12.1.A.1.207 / R2B CDA 1272-3116
Whole Folder [Google Drive]
FOTAKernel c5302-stock-fota [Download]
Kernel c5302-stock-kernel [Download]
elabel, modemst1, modemst2, fsg combined c5302-stock-ril [Download]
C5306
This section is for the the C5306 model only
Please read the main post if you haven't read them!
NOTES
Please read the main post if you haven't read them!
For this model, I have used Customised US 12.1.A.1.205 / R3B CDA 1272-4529
Whole Folder [Google Drive]
FOTAKernel c5306-stock-fota [Download]
Kernel c5306-stock-kernel [Download]
elabel, modemst1, modemst2, fsg combined c5306-stock-ril [Download]
Addons Zip
Unrelated flashable zips that might be useful
Folder for Downloads
AdAway Generated Hosts [4.1+] *
[ Download ] Replaces the standard hosts file in /system/etc/hosts with the one generated by AdAway. Could ease your life and save yourself a reboot if you flash this after flashing an update to your ROM. This zip file will get updated when there is a new hosts file update by AdAway. You can check by looking at the text file's name from within the zip file).
ViPER4Android [5.0+] *
[ Download ] This will flash ViPER4Android as a system app. It doesn't end there, it will also push an supolicy that enables you to use V4A with an Enforcing SELinux, it will install the drivers automatically for you, it will remove AudioFX, and all of these will persist on a ROM update (aka dirty flash)! Thanks to the help of @Tomoms, @Arvind7352, @shavendum, @Zenith and @akashsaini7 . Without their help this wouldn't probably happen at all
Android N Emojis [5.0+] *
[ Download ] This will flash the Android N emoji support to your current Andorid version. Note, you can only display the new unicode 9 emojis on the device (no more squares), to actually write them, you will need a keyboard that can already write the new emojis (which most still aren't). Should be compatible with Lollipop and newer, and not for KitKat and below. Tested on Marshmallow.
Remove AudioFX [5.0+] *
[ Download ] Removes AudioFX from your CM-based custom ROM to make way for your preferred sound mod. No more hassle to freeze AudioFX using TiB (or any other freezing tool)
Persisting Walkman [5.0 - 5.1] *
[ Download ] This will flash a file into addon.d folder to make sure that your Walkman and sound effects stays on the ROM when you dirty flash an update. This flashable zip however only compatible with [port][LP] Xperia Sound enhancement by @ankurjn364. Note that this port is only for Lollipop ROMs.
Xperia SP Boot Animation [4.1+] *
[ Download ] Get yourself the original Xperia SP Boot Animation!
Xperia Z5 Boot Animation [4.1+] *
[ Download ] Get yourself an Xperia Z5 Boot Animation! Thanks to @xkeita for porting the Xperia Z5 Boot Animation, especially for creating it for the 720p screen! Please leave a thank to xkeita on the original thread: Xperia Z5 bootanimation for Xperias!
Xperia X Boot Animation [4.1+] *
[ Download ] Get yourself an Xperia X Boot Animation! Thanks to @chitshiv for porting the Xperia X Boot Animation, especially for creating it for the 720p screen! Please leave a thank to chitshiv on the original thread: [MOD] Xperia X Series Bootanimation
* Note
The addons with the star means that the zips will push a backup script into the addon.d folder. This means the files flashed onto the system will survive a dirty flash, granting your modifications to the system persisting.
This will not work if you wiped your /system partition. If you did that, you will need to flash the zips again.
If you dislike this, you can simply delete the scripts that starts with "ts-" located in "/system/addon.d/".
Cool! I added a link to this thread in Tangerine's 1st post. It might be useful for those seeking for a stock FOTAKernel
Tomoms said:
Cool! I added a link to this thread in Tangerine's 1st post. It might be useful for those seeking for a stock FOTAKernel
Click to expand...
Click to collapse
Thank you so much for that! :highfive: :victory:
Update!
All models' respective files are now available
Update!
Now all zips can be flashed on CyanogenRecovery! Thank you so much for @Tomoms in helping me to sign the zips
Update!
All stock components updated with a new supposedly "output design"
Nothing is changed in the original files, it is just that I have changed the log output of the flashable zips so it looks pleasing to the eyes. Also I am now able to make use of the TWRP progress bar thanks to my brain for finally understanding the "set_progress()" Edify syntax
Two new zips added in the Addons zip section
adaway.zip
stock-rom-bootanimation.zip
[ Head on directly to the #5 post ]
Update!
New file name prefix for the Addon zips
Some zips now have the "ts-" prefix in their names
Two new zips added in the Addon zips section
Persisting Walkman
Persisting Xperia Keyboard
[ Head on directly to the #5 post ]
Backup scripts for persistence on ROM update!
AdAway Generated Hosts
Remove AudioFX
Persisting Walkman
Persisting Xperia Keyboard
These flashable zips now have a backup script included with them. This will make the modification on your system stays when you dirty flash a ROM update. Really useful if you prefer having a shorter time on flashing a new update for your current ROM
Update!
New zip added in the Addon zips section!
Xperia Z5 Boot Animation
[ Head on directly to the #5 post ]
New console output design
Well, when you flash a zip, there will be output texts on the screen. I changed the design a bit lol
No more pause
ZIPs will flash instantaneously as "sleep()" functions has been removed in all ZIP's updater-script. This is not really a new change, as I have silently removed it weeks ago. But I think it would be good to write it here
Updated hosts file for AdAway Generated Hosts
Also for those who uses this zip, I always update this zip whenever there is an update from the AdAway app.
Announcement
Currently the files are unaccessible due to CubeServer went off from the face of the Internet. I will upload to another cloud storage soon after collecting all the FTFs and extract them all.
Still can't download, can you solve please?
VladHD said:
Still can't download, can you solve please?
Click to expand...
Click to collapse
I am currently dealing with this. Expect them files available soon. I will edit this post when it is done
EDIT: Now all are updated
Update!
New Xperia Keyboard!
Also included is the Xperia X boot animation.
Updated all mirrors, now on Google Drive
I am very sorry for being very late in updating those mirrors. A few days or so before CubeServer went down, I also did something very irreversible on my HDD, thus making me lost all of the files. Since I only have a local backup of those stock components, this render me unable to mirror it instantly. And about those other remaining lost time, I think everyone can guess that lel. Anyway enjoy, for those who needs them
I'm using CM13 ROM, does these stocks give better performance?
Can anyone explain the benefits of using them? especially ' stock RIL components ' I don't know what is this.
parkavenu said:
I'm using CM13 ROM, does these stocks give better performance?
Can anyone explain the benefits of using them? especially ' stock RIL components ' I don't know what is this.
Click to expand...
Click to collapse
Hmm i should update the OP soon to explain more about using the zips while being on a custom ROM.
This thread is made to cater all my other personal flashable zips that I share, while also focusing on stock components as a main objective of the thread. These so called "stock components" are only for stock ROM with the exception of the RIL components.
Now to answer to your question
The FOTA is useful if you have a some sort of "ritual" and prefer stock FOTA partition when you want to wipe your TWRP recovery. Adrian provided a FOTA eraser that fundametally write zeros to the FOTA partition. That's the difference between this stock FOTA and Adrian's FOTA cleaner. This does not improve or make your experience on CM worse.
The stock Kernel is strictly for stock ROMs. Flashing on another ROM that doesn't depend on stock ROM will make the ROM unbootable. This makes your experience on CM worse.
The RIL components will flash the network-related things to your system. This might be useful for someone who requires baseband (elabel) without needing to use the FlashTool. This may improve your network experience, as it really did for me.
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
Carliv Touch Recovery
- version 5.7.2 is for Lollipop (cm 12.1, aicp lp or resurrection remix lp) and version 6.6 is for Marshmallow (cm 13, aicp-mm or resurrection remix mm).
The version starting number is related to android version.
This is a CWM based recovery and I did put up some work to update it to lollipop (cm 12.1) and marshmallow (cm-13) after official cwm development stopped at kitkat. It works with LOLLIPOP and MARSHMALLOW kernels and it builds with cm 12.1, aicp lp or resurrection remix lp (version 5.7) and with cm 13, aicp-mm or resurrection remix mm (version 6.5).
This is for those who want a lighter and simpler recovery or they just liked CWM before. It's not as good or complex as twrp, but it will do the job just fine.
For gui I ported PhilZ Recovery full touch module.
Because the vold in cm 12.1 and 13 doesn't support cwm anymore I had to use the old fstab1 type for functionality, although for building reason a valid recovery.fstab should be provided in device tree. In the third post there are some building hints to make it clear for those who want to try building it.
Features:
- EXT4 and F2FS support (for f2fs use the BoardConfig flag).
- full touch menu ported by me from PhilZ touch Recovery. The old Napstar-xda touch module was good but it's quite old and to update that was too much work. Actually There is a version 4 with that touch module, all working, but the touch doesn't work with some input drivers and I had to give up on it for the new and improved version from PhilZ.
- all cwm functionalities are up and working (adb, sideload, backup, restore, install, mass storage...). There is no mtp and if your phone doesn't have an external sdcard you can't connect it to PC while is in recovery mode. But there is usb-otg support, of course if your phone was shipped with that.
- added new menu for backup and restore advanced, to use it for backing or restoring only a specific partition and I also ported from PhilZ the multizip flashing function.
- in Carliv menu there is now a new section for flashing boot and recovery images. It is a feature that I needed during many recovery builds testing. I wanted an easier way to flash other image without booting to android and using an app like RashR. You can browse your storage locations for any image and after choose you will have to select on wich partition should that be flashed. I added multiple confirmations check to avoid flashing on wrong partition. This feature works only with boot and recovery images. I won't add other partitions to this because for other things there are multiple backup restore functions.
- for MTK phones (if the flag is used in Boardconfig) there is a new menu to backup and restore some important partitions like uboot, nvram an secro because they are involved in restoring a lost IMEI, and also the logo partition which may often get broken by bad ported ROMs.
- besides these all my old specific menus (aroma, rainbow...) are still in place.
- added support for dencrypting and mounting data partition using the builtin minivold from cyanogenmod with vdc commands (the ideea came from this post of Lekensteyn). Tested and working well with text ar hex passwords, and maybe will work with pin too but I don't think it will work with pattern .
- added support for dencrypting and mounting adopted storage in marshmallow. The solution is based on this article of nelenkov.
- there is no included root solution. I choose to do it this way because there is no universal root solution now and someone may end up messing things with a non-working root option. You can flash a zip installer from Chainfire's SuperSu or other solution that may work for your phone.
All screenshots are made with my old tool from here (still working well).
CREDITS:
The biggest thanks go to AP756 and DerTeufel1980, two friends from Germany, who sent me a new phone each, with lollipop OS and that helped me a lot to do this.
- Phil3759 for the touch code and many other things from his recovery;
- TWRP developers. I learned a lot from their work;
- Clockworkmod Team starting with Koushik Dutta and ending with all developers that made the CWM recovery what it was;
- Cyanogenmod Developers;
- Nikolay Elenkov;
In next post there are some links for built recoveries. I'll add more soon as I get a valid link (on a reliable webhost) from people who build it for other phones.
I worked alone on this, there is no team here, not because I don't want to , but probably because there was no one interested in this, and so there may be some unspotted bugs. If you find any please do tell me to help on fixing it.
XDA:DevDB Information
Carliv Touch Recovery, Tool/Utility for all devices (see above for details)
Contributors
carliv
Version Information
Status: Stable
Current Stable Version: 5.7.3 & 6.6.1
Stable Release Date: 2016-07-19
Created 2016-05-30
Last Updated 2016-07-19
Changelog and working builds
CHANGELOG 19-07-2016:
- fix backup for old mtk phones.
Lollipop
1. Jiayu S3+
2. Zopo Speed 7+
3. Zopo Speed 7
4. Mlais Mx Base
5. Alcatel Pop C2/C3
6. ZTE Blade L3 / Digicel DL910
7. Nous NS5511
Marshmallow
1. Zopo Speed 7+
2. Zopo Speed 7+ with adopted storage
3. Zopo Speed 7
4. Zopo Speed 7 with adopted storage
* NOTE: sadly the kernel source for zopo marshmallow isn't published so these two don't have touch in recovery, but you can use them as in CWM with phone buttons.
[*] QCOMM devices:
1. Huawei Honor 5x (kiwi)
2. Samsung Galaxy A5 (SM-A500FU)
Building Guide
To build you need a local repo of cm-12.1 or cm-13 and a proper device tree. To see how a buildable device tree looks check this one from my github.
It builds out of the box with aicp lp-5.1 and aicp mm-6.0 too, but like in cm you need a proper device tree.
Some things to be considered:
For BoardConfig:
- the most common thing in all BoardConfig I saw (you need this to use power button to select if you use physical buttons in some situations)
Code:
- BOARD_HAS_NO_SELECT_BUTTON
- for the graphical interface
Code:
- TARGET_RECOVERY_PIXEL_FORMAT
- for mass storage if your phone has an external sdcard, to connect it to PC (this one can be specified in fstab too) - and it has to be without any quotes or slashes
Code:
- TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/devices/platform/mt_usb/musb-hdrc.0.auto/gadget/lun%d/file
- for LCD backlight lights - and it has to be without any quotes or slashes
Code:
- TARGET_RECOVERY_LCD_BACKLIGHT_PATH := /sys/class/leds/lcd-backlight/brightness
- for vibrator feature - and it has to be without any quotes or slashes
Code:
- VIBRATOR_TIMEOUT_FILE := /sys/devices/virtual/timed_output/vibrator/enable
- with link to a valid recovery.fstab version 2 (it may work without it but it is better to be here)
Code:
- TARGET_RECOVERY_FSTAB
- for a better readability adapted to your screen (check the minui folder for more fonts)
Code:
- BOARD_USE_CUSTOM_RECOVERY_FONT
Carliv Touch Recovery specific flags:
- if you have the recovery on recovery-carliv folder under bootable directory in cm-12.1 source use this next flag.
Code:
- RECOVERY_VARIANT := carliv
NOTE: in cm 13, and other android 6 sources too, you can't build with this flag out of the box and so you have some things to do - the easy one is to rename recovery folder in [recovery-stock] and to place my recovery next to that with the name [recovery]. Other option is to open Android.mk from /sytem/core/healthd and find line 58 where you need to replace [LOCAL_C_INCLUDES := bootable/recovery] with [LOCAL_C_INCLUDES := $(call project-path-for,recovery)].
- with your phone resolution like this width x height
Code:
- DEVICE_RESOLUTION := 720x1280
- if you want to use it with encrypted phone (it work with a non encrypted phone too but it will be smaller if you don't need decrypting function)
Code:
- BOARD_INCLUDE_CRYPTO := true
- if your phone is MTK powered you need this for the MTK menu (it is not mandatory though with the mtk phones shipped with lollipop or marshmallow)
Code:
- BOARD_HAS_MTK_CPU := true
- for touch menu, if your phone has an input driver with PROTOCOL_TYPE_B (synaptic is an example, or many samsung devices); if you have access to, check your kernel input driver for something like this [#define PROTOCOL_TYPE_B] - google it if you want to know more about this
Code:
- BOARD_USE_PROTOCOL_TYPE_B := true
- to block an input device use
Code:
- TOUCH_INPUT_BLACKLIST := "devicename"
- if you use Adopted Storage
Code:
- BOARD_USE_ADOPTED_STORAGE := true
For system.prop from device tree:
Code:
#
# system.prop for mx
#
ro.ctr.crypto.passwd="64656661756c745f70617373776f7264"
ro.ctr.forbid_format=/frp,/persistent,/lk,/uboot,/logo,/metadata,/nvdata,/nvram,/secro
ro.ctr.forbid_mount=/frp,/persistent,/lk,/uboot,/logo,/metadata,/nvdata,/nvram,/secro
ro.ctr.touch_accuracy=7
- to use decrypt data specify here your password (ro.ctr.crypto.passwd); I forgot to mention that if the phone uses encryption, the recovery will start with few seconds delay, because of the decrypting and mounting data process. If the message will tell you that couldn't be decrypted it is possible that your password was wrong or it uses an unsuported type of password. To be sure just restart the recovery from Power menu and if you still get the same message then you need to check your provided password from system.prop or to find a different solution (other recovery like twrp). If you want to decrypt your phone for good you need to format data and data media from Mount/Storage menu but you will loose your data (settings, preferences).
- ro.ctr.forbid_format and ro.ctr.forbid_mount are for partitions from fstab that you don't want to be shown in Mount/ Storage menu with mount and format option (coma separated, no spaces and with leading slash), like in my example above.
- ro.ctr.touch_accuracy to improve the touch handling (bigger lcd_density = bigger accuracy); the initial value is 7, just like in PhilZ Recovery, and I reccomend you to try different numbers to see what is right for you, but don't go over 19.
All these system.prop lines are not mandatory.
Carliv Touch Recovery uses a fstab version 1 named [ctr.fstab] and you have to create a folder recovery in your device tree, in that recovery folder create a new folder named root, in root folder another folder named etc and in that one place the ctr.fstab. Like this:
Code:
recovery/root/etc/ctr.fstab
That will be enough since the compiler will add it in recovery ramdisk and the recovery module will find it in etc folder.
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# mount point fstype device [device2] fs_options [fs_options2] lun
/boot emmc /dev/block/platform/mtk-msdc.0/by-name/boot
/cache ext4 /dev/block/platform/mtk-msdc.0/by-name/cache
/recovery emmc /dev/block/platform/mtk-msdc.0/by-name/recovery
/system ext4 /dev/block/platform/mtk-msdc.0/by-name/system fs_options=rw
/data ext4 /dev/block/platform/mtk-msdc.0/by-name/userdata fs_options=rw
/internal_sd datamedia /dev/null
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 lun=sys/class/android_usb/android0/f_mass_storage/lun/file
Important here is how you define internal storage which is data media
Code:
/internal_sd [COLOR="Red"]datamedia[/COLOR] [COLOR="Magenta"]/dev/null[/COLOR]
You can see It's used the old way with "datamedia" fstype and /dev/null device.
Important thing: if you have only internal storage define it as
Code:
/sdcard datamedia /dev/null
If you have also an external sdcard, use either way:
Code:
/internal_sd datamedia /dev/null
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
or
Code:
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
If you are using the adopted storage feature for external sd card, define this
Code:
/data_sd ext4 /dev/block/mmcblk1p2 fs_options=adopted
and remove or comment out the line for external sd card.
You can see the internal storage can be sdcard or internal_sd and external sdcard can be sdcard or external_sd, but internal storage can't be external_sd or external sdcard internal_sd.
If your phone has OTG support you can use that too defining it like this
Code:
/usb-otg vfat /dev/block/sda1 /dev/block/sda
or this
Code:
/usbdisk vfat /dev/block/sda1 /dev/block/sda
-check with your phone booted up in Android and a OTG USB mounted to see in [/sys/class/block] or [dev/block] how to set device for this (the dev/block/sdx part).
The recovery has fat32, exfat and ntfs support builtin (also f2fs for file system). You can define your usb-otg and/or external sdcard as "auto" instead of "vfat" and it will work with any of these formats. I tested a portable HDD self powered and it works (120 GB) as usb-otg. Anyway that is available only for zip and image flashing. Maybe I'll make it to work for backup and restore too.
@carliv is back!!! Thanks a lot for this.
Should I port or should I build?
kirito9 said:
@carliv is back!!! Thanks a lot for this.
Should I port or should I build?
Click to expand...
Click to collapse
You should build it of course. I won't make porting recoveries anymore.
Actually wait for a day or two because I'm working on some improvements and I'll push them to github soon.
Also I have a working version for cm13 too. That also need some more tests before release.
carliv said:
You should build it of course. I won't make porting recoveries anymore.
Actually wait for a day or two because I'm working on some improvements and I'll push them to github soon.
Also I have a working version for cm13 too. That also need some more tests before release.
Click to expand...
Click to collapse
I will wait for cm13 support
Anyway this recovery support arm64?
Sure. Look at the phones already supported
Gesendet von meinem HERO1 mit Tapatalk
carliv said:
You should build it of course. I won't make porting recoveries anymore.
Actually wait for a day or two because I'm working on some improvements and I'll push them to github soon.
Also I have a working version for cm13 too. That also need some more tests before release.
Click to expand...
Click to collapse
Goood xD. No more complaints from users who "brick" their devices and blame you :laugh:
All things are mostly done.
Just a little heads up: Added usb-otg support for install zip menu - should work with ntfs, fat, exfat and fat32 usb flash drives (I tested only with fat32). Other improvements too for both versions (lollipop and marshmallow).
I'll push the source tomorrow.
Attached a screenshot of the recovery for marshmallow (cm13).
Thanks to Master [emoji322]
Sent from my Lenovo A7010a48 using XDA-Developers mobile app
Thread updated with instruction and links for the new version for cm-13 and the version for lollipop is upgraded to 5.2.
If some of you build a working recovery and want to share here the link, just post a replay and I'll add it in post #2.
If you have a buildable device tree public on github and want a recovery built for it ask here and maybe I or someone else will do it in some free time.
@carliv do you interested to build this recovery for kenzo (redmi note 3 pro) ?
here's kernel source for it: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/kenzo-l-oss
exodius48 said:
@carliv do you interested to build this recovery for kenzo (redmi note 3 pro) ?
here's kernel source for it: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/kenzo-l-oss
Click to expand...
Click to collapse
The kernel alone is useful only if builds out of the box, but you still need a proper device tree to build, even with a prebuilt kernel. For building a recovery or a ROM that is what you need. I can't build a recovery only with that. Maybe someone else have the phone and manage to create the device tree and it will build the recovery.
Cheers
Look forward to Flash system Image In Carliv Menu
Thank You
Finally CTR for LP & MM! Amazing @carliv, I love this recovery.
Update to version 5.3 for lollipop and 6.2 for marshmallow
CHANGELOG 12-06-2016:
- activated working support for ntfs, exfat and f2fs;
- rewritten the flash image menu for better functionality and more protection to avoid mistakes;
- change the local busybox libs and modules names to avoid conflicting with existing external folder;
- some other small fixes and improvements (you can check the github commits).
@carliv
Hi, I have a device tree that I used for TWRP https://github.com/kirito96/device_Alcatel_4032 recovery and I would like to know if this is enough for building CTR or do I need a "complete" device tree? Thanks.
kirito9 said:
@carliv
Hi, I have a device tree that I used for TWRP https://github.com/kirito96/device_Alcatel_4032 recovery and I would like to know if this is enough for building CTR or do I need a "complete" device tree? Thanks.
Click to expand...
Click to collapse
Not really complete like in building ROMs, but you have to do some changes:
- convert it to cm building or, better and easier for you since it's for omni, to aicp.
- then you need to add in boardconfig partitions sizes (twrp doesn't need that because it checks the size from dumchar_info or partinfo).
- add that recovery/root/etc folder with ctr.fstab in it.
- add specific flags in boardconfig, but if your device has a small recovery partition let the crypto flag out (don't use it at all) and you will gain almost 2 Mb.
- add resolution and desired font if you want to not use the default which is for 540x960 dpi.
and that's it ...
Take a look at my mlais device tree (link in OP)-sorry, in post #3 to see these things - I have a branch for aicp too.
And I see your device use mtk header. You can check in my github for the lenovo p780 device tree where I implemented the mkbootimg part from my kitchen.
Cheers!
PS: if you can send me your phone dumchar_info file and a stock boot image I'll try to convert your device folder to use it as an example for other people about how to do it.
@carliv
Thanks for informing me, but for now I think I'll opt for a device tree that you made and I'll use that as a base for other devices that I'll work on in the future.
I've attached the dumchar_info.txt file below along with the stock boot.img. Funny thing is, I have 2 stock boot.img. I have for which my phone came with (4.2.2) and an AOSP upgrade with 3.10.xx kernel (5.1.1). I uploaded both because this recovery is for LP right? Which should be 3.10.xx kernel. In any case, I'll use what you made as a base. Thanks again.
carliv said:
CHANGELOG 12-06-2016:
- activated working support for ntfs, exfat and f2fs;
- rewritten the flash image menu for better functionality and more protection to avoid mistakes;
- change the local busybox libs and modules names to avoid conflicting with existing external folder;
- some other small fixes and improvements (you can check the github commits).
[/B]
Click to expand...
Click to collapse
You did it!!! :victory:
Good thing I was checking up on you or I might of missed it.
Thanks carliv I realize this project must of been a huge effort on your part and I for one am very grateful :highfive:
I DID NOT CREATE THIS ROM OR THE RECOVERIES OR FLASH TOOLS LINKED, I ONLY MODIFIED THE SYSTEM UI AND SETTINGS AND BUILD PROP ZIPS BELOW.
I am not responsible for any damage (if any) to your device, data, life, job or anything else you'd care to think of.
ANY QUESTIONS, PLEASE ASK IN THE THREAD AS EVERYONE BENEFITS, PM'S WILL MOSTLY BE IGNORED.
IF YOU DON'T HAVE AN UNLOCKED BOOTLOADER YOU MUST FIRST UNLOCK IT.
Download all files you want/need to your PC/External SD before starting...just saying.
[/CENTER]
Step One
Flash stock firmware for your device that the rom is based off. Readily available from Xperifirm (attached to flashtool - Bonus!), or XDA. Flash via Flashtool or Newflasher. Again, there's plenty of guides on using flashtool and newflasher, i'm not covering that here.
Step Two
Once flashing has completed, turn the device on and allow it to fully boot. Complete the setup process, and log in to your google account. Move the ROM file you already (hopefully) downloaded to internal storage (IMPORTANT STEP: I had symlink errors flashing the ROM from the External SD Card). I normally disable auto-updates in the Play Store/Whats New apps and then let it rest for 5 minutes.
Step Three
Turn your device off, boot into FASTBOOT MODE, and flash TWRP (fastboot flash recovery TWRP/ATWRP.img). If you don't know how to fastboot, see above re: XDA/Google. Unplug your device, wait 10 seconds, then boot into recovery (Hold power and volume down together, release both at at the vibration). Tick the checkbox then swipe right, and the first thing you SHOULD do is go to settings and turn the damn vibration off. :laugh:
Step Four
DON'T WIPE ANYTHING!!! You are installing on top of an already clean installation, its pointless. Press Install, select the XPERIA_PIE_XZP_1.0.zip file you downloaded earlier, and swipe right to install that sucker. Don't freak out when it takes 5 to 8 minutes for the recovery screen to change, its doing its thing, trust me. Once you get the all clear and the button down the bottom says reboot, that's pretty much all that's left to do.
Step Five
Once the phone reboots, let it settle again for a while, and deny all the requests the Chinese apps throw at you. After a few minutes, go into the root explorer app, allow root permissions when it requests it, then go to system/priv-app and delete any app starting with TG. Unless you really like Chinese bloat, in that case, proceed to set up your phone as usual.
The ROM is pretty basic at the moment but given time and based off the Oreo series, more System UI mods will become available with later versions.
CREDITS: @machao44 @uditrawat @Myself5 @Androxyde @munjeni @Ticklefish @Pandemic
@fOmey[/SIZE]
DOWNLOAD LINKS
M-ROM P v1: BASED ON 306 FIRMWARE https://drive.google.com/file/d/1eOWzREBPehv8QoCFYQfPdF4yqKH2NdB1/view
M-ROM P v1.1: BASED ON .33 FIRMWARE
https://mega.nz/#F!MNYGhKhR!OtCS6j-YBXaxcDI1sa7FlQ
Thanks to @sam.foro for uploading.
M-ROM P v1.2: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=1ZX...ixVN09Ry_vVhDf
Thanks to @Yanun
https://drive.google.com/file/d/14K-...ew?usp=sharing
Thanks to @karrouma
M-ROM P v1.3: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=10l...uGinaYCEzy-vt_
Thanks to @Yanun
TWRP: https://dl.twrp.me/maple/
Aroma TWRP: https://mega.nz/#!TdxmiaLb!FYBet5eRYHGqiLT0niRH9F90Ts_QeRdfkOfPWOAgQCM
Flashtool: www.flashtool.net/
Newflasher: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
M-Rom P v1.6 - BASED ON 10.28 FIRMWARE - Thanks to @karrouma for uploading and sharing
https://drive.google.com/file/d/1pNsIaGR2_r74INyH8p053bQStiruPEWd/view?usp=sharing
M-Rom v1.6 - English Translated
https://mega.nz/#!6ExSGYQZ!HD0YM_Sypeu5h-6K4vhKT9NkiQn_63PZG0ZPwf_kRmY
M-ROM 1.6 aroma add-on.
M-ROM v1.6 aroma add-on - contains .25 animation mod, font picker and fonts, xperia 10 boot animation, double tap to wake kernel selection (g8141/g8142), and magisk 18.1/19.0 selection.
Enjoy.
https://mega.nz/#!nZpihCqK!TvB0_-w0cdTWFBKylPUk5Da3YdLAJCc_vk5d8XNDySc
Beetle84 said:
ADD-ONS
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch (COMING SOON - UPLOADING) for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch:
Enjoy
Click to expand...
Click to collapse
Thank you my friend
Great job
Nice
Thanks for this
Nice bro
Keep it up ^^
Added Patched Services.jar Magisk Module to Post 3.
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
hasaan6545 said:
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
Click to expand...
Click to collapse
Its not a new upload so I wonder what is happening. It is the same link available from the Oreo M-ROM thread, just copied and pasted.
Are you downloading from your device or from a PC?
Removed
link opened fine. and the file is fine opened normally . no problem
Beetle84 said:
ADD-ONS
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch: https://mega.nz/#!mdhmnKwS!POI9MLzZRH9g4isgy0XCZLIhYmu6pUAnZwlXcgaM2xM
And a Patched Services.jar Magisk Module. Flash in Magisk and reboot.
306 Patched Services.jar.zip: https://mega.nz/#!LYpyHQyD!Ka21OVx-yWIM1WUb-WQLoLoJEGOZItz7V_BQMz6fbsk
Enjoy
Click to expand...
Click to collapse
can you explain the step how to deodex the pie ??
rizky_zulfikar said:
can you explain the step how to deodex the pie ?
Click to expand...
Click to collapse
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Beetle84 said:
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Click to expand...
Click to collapse
i've tried that tool, but my priv-app and framework fail to deodex there still odex and vdex file, only my app ?
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
stipi69 said:
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
Click to expand...
Click to collapse
Its a slightly modified stock rom, based on .306 dual sim Pie firmware. The rom is odexed.
I have it flashed root working, looks nice, refreshing and snappy, i guess xzp does not have hardware side sensors but you can still tap on edge of screen and bring side menu out , nice!!!
I love new camera look, huge icons in pull down menu.... not so much, haha , it is a matter of gettin use to it i guess
Great work, thanks
If you cannot flash 47.2.A.0.306 via flashtool and get same error as i did below download and copy next file:
downloaded "47.2.fsc" file to: username/.flashtool/device/G81XX, delete 47.1.fsc
https://drive.google.com/file/d/1hZR...w?usp=drivesdk (not my work in this link, credits to xda user xrenoix)
Hi, i get error in flashtool, somoene else same error?
28/048/2018 13:48:07 - INFO - Start Flashing
28/048/2018 13:48:07 - INFO - Parsing boot delivery
28/048/2018 13:48:07 - INFO - Found a boot delivery
28/048/2018 13:48:07 - ERROR - No flash script found. Flash script is mandatory
28/048/2018 13:48:08 - INFO - Sending Sync
28/048/2018 13:48:09 - INFO - Sync status : OKAY
28/048/2018 13:48:09 - INFO - Sending powerdown
28/048/2018 13:48:09 - INFO - powerdown status : OKAY
28/048/2018 13:48:11 - INFO - Device disconnected
old .270 rom flashes with no problem
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Indashio said:
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Click to expand...
Click to collapse
Does it work for XZ1?
Thanks
unless we get gravitybox (from xposed) features, like in Resurrection Remix, i'm not moving to Pie.