Develop Bugs

[DEV][OTA] OmniROM Galaxy 551/Callisto Port [OmniARMv6]

OmniROM Galaxy 551/Callisto port [OmniARMv6]
Current port status: beta - may not be suitable for daily use. For experienced users only.
Latest Google Apps package: not yet available
Pre-requisites:
ClockworkMod or TWRP recovery
Initial install:
Download the latest build that supports OTA updates from: http://dl.androidarmv6.org/callisto
Reboot to recovery, wipe data and install the update package normally.
How to perform OTA (over the air) update:
Go to Settings -> About phone -> System updates. The latest diff between your current ROM and the latest build will be downloaded, which will be used to create a new update zip in the /sdcard/OpenDelta folder.
If you are using OmniARMv6 TWRP recovery, it can flash the new update automatically [not yet tested].
If you are using CWM recovery, you can flash the patched package (/sdcard/OpenDelta/omni-*.zip) manually.
Source:
Complete project: https://github.com/omniarmv6
Device (note: relies on shared device configuration): https://github.com/omniarmv6/android_device_samsung_callisto
Kernel: https://github.com/androidarmv6/android_kernel_samsung_msm

Reserved #1

Reserved #2

I have tested and found camera is not working , document (file manager) unable to open apk file and need some work on lock screen except that rom is smooth.
Thank for creating thread.

thanks

ROM is very smooth and fast. Works much faster than CM11.
Very thanks

@psyke83 omni rom will be used kernel 3.×.× as per source given above.

@psyke83 omni project has been abanded ? after bunch of ota failed ota disappeared from Jenkins. This rom is smooth and fast except few problems like camera,keyboard back light and lock screen resize.

Last builds (also for other devices) are dated June 15. And the last Android version was 4.4.3. Is it just a build process that got stuck, or is it more serious?

Links are down!
Hey man,
Thank you and others in armv6 team for their incredible work. You guys brought CM11 to a number of devices and that's a BIG DEAL.
Since our device is quite old now, I can see why the project died.
Now, the only thing we want is the links of the latest stable (RC) builds of the devices hosted somewhere. I can (at-least) host (CM11 and OMNI) stable builds of callisto in my GDrive.

Anyone knows what the license for ready-built ROMs is? That is, if the original source goes down, would anyone be allowed to upload a copy?
I'm not thinking about modified images yet - but it'd be easy to make people download something that isn't identical to the original thing, and the md5sum files have also gone - would archive.org be able to help? https://web.archive.org/web/*/http://download.androidarmv6.org/_builds/callisto/* seems to return something at least

Can Someone reupload this?

[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL

New version Slimkat 8.10 compiled today . New kernel with Tomoyo security enabled (as opposed to Apparmor). Enjoy.
See Download section
________________________________________________________________________________________
Here is the famous Slimkat 4-4-4 rom built from sources a few hours ago. Changes made to kernel only and they are the following:
Hardened Kernel with the following features:
a. Selinux disabled (don't trust them) and APPARMOR enabled as main security
b. All crypto core features enabled
c. All authenticated encryption modes enabled - CCM, GCM and SEQIV
d. All blocks enabled - CBC, CTR, CTS, ESB, LRW, PCBC and XTS
e. All hash modes enabled including SHA512 and others
f. All ciphers enabled including CAMELIA, TWOFISH, ANUBIS, SALSA20 and others
g. Compression - DEFLATE, ZLIB and LZO
h. Random number generation all options enabled to result in a better generation without CPU wakeups
Credit: Slimroms Team
WARNINGS:
I am not responsible for your device becoming a paperweight. I am also not responsible for death and destruction caused by your flashing this rom on your device. You are at your own perill. Complain to Putin - he will surely help.
INSTRUCTIONS
1. Unlocked Bootloader
2. If you have CWM, go to mounts and storage and wipe System/Cache/Data
3. If you have TWRP, go to advanced wipe and wipe System/Cache/Data
4. Flash the rom and reboot.
5. I recommend that you delete Cyanogenmod original boot animation as it slows down the boot significantly: without it your boot should take about 25 seconds. Once you remove bootanimation.zip in /system/media, you will have a nice vanilla android bootanimation.
6. Enjoy the rom and hit Thank You or perhaps Donate?
P.S. Rom is in Download Section above
XDA:DevDB Information
[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Beta
Stable Release Date: 2014-11-11
Beta Release Date: 2014-10-21
Created 2014-10-21
Last Updated 2014-11-11

Thanks Man.. Please keep up the good work

OP, it must be terrible to be asked over and over again but I'd be very glad if you could tell what those changes in the kernel that you have introduced mean for the end user. So to speak, what can we expect after installing this? is this more security oriented or would the random number generation is related to entropy stuff and is supposed to speed up the system?
I saw your other thread too, wanted to give it a try but couldn't understand what these changes to the kernel actually mean for a layman.
Thanks man for your work!

srqrox said:
OP, it must be terrible to be asked over and over again but I'd be very glad if you could tell what those changes in the kernel that you have introduced mean for the end user. So to speak, what can we expect after installing this? is this more security oriented or would the random number generation is related to entropy stuff and is supposed to speed up the system?
I saw your other thread too, wanted to give it a try but couldn't understand what these changes to the kernel actually mean for a layman.
Thanks man for your work!
Click to expand...
Click to collapse
It is actually both security oriented and system speed based on better random number generation.
First of all, I don't trust Selinux, especially in light of the recent Snowden's revelations. So, selinux is out of this kernel. Instead, you have trusted Apparmor, which has been used in Linux for years. In addition, many newer ciphers, which are in this kernel, were disabled by default -- again think of several 3-letter-agencies that are known for deliberately weakening kernels and operating systems to make it easiers for themselves to break. So, I have enabled those ciphers. Hashes, especially SHA512, which is the strongest, were disabled by default. I have enabled them all. Random number generation: the same.
So, as result, you have a more secure system that is faster, because of better and more random seeding.. If you remember, there is an app on XDA, which the author says, provides better random number generation, but it drains battery, because CPU constantly checks if the pool (of random numbers) is large enough. Here, it is different, because the changes (better and more random seeding ) are on the kernel level. So, CPU does not have to constantly wake up and check...

optimumpro said:
It is actually both security oriented and system speed based on better random number generation.
First of all, I don't trust Selinux, especially in light of the recent Snowden's revelations. So, selinux is out of this kernel. Instead, you have trusted Apparmor, which has been used in Linux for years. In addition, many newer ciphers, which are in this kernel, were disabled by default -- again think of several 3-letter-agencoes that are known for deliberately weakening kernels and operating systems to make it easiers for themselves to break. So, I have enabled those ciphers. Hashes, especially SHA512, which is the strongest, were disabled by default. I have enabled them all. Random number generation: the same.
So, as result, you have a more secure system that is faster, because better and more random seeding.. If you remember, there is an app on XDA, which the author says, provides better random number generation, but it drains battery, because CPU constantly checks if the pool (of random numbers) is large enough. Here, it is different, because the changes (better and more random seeding ) are on the kernel level. So, CPU does not have to constantly wake up and check...
Click to expand...
Click to collapse
Got it, thanks for the great explanation bro.
I totally get it now, would be trying Aragon one today would definitely come and report how that works!

Great work buddy,
Can you share your kernel sources?
I might include some of your changes in official slimkat
also out of curiosity, if the change is only on the kernel, wouldn't it be easier to share the kernel only!
Regards,
Omar.

OmarEinea said:
Great work buddy,
Can you share your kernel sources?
I might include some of your changes in official slimkat
also out of curiosity, if the change is only on the kernel, wouldn't it be easier to share the kernel only!
Regards,
Omar.
Click to expand...
Click to collapse
Of course it is easier to do the kernel only, but I haven't found the way to do that outside of building the whole rom. Plus, in CM roms, I know where to put those changes: row rhine honam_def.conf and if you look at my sources for Black Argon rom, you will find the changes there.. But Slimroms guys use some other file, so I put my .config file in during the build. Plus, for the new kernel to work, you need modules from the rom you will be using it in and roms differ from one to another. So, for now, it is easier for me to build the whole rom.

very good
each person who comes to their work
it is a hope to be in a rom kk
if this rom has the same problem that all
3g signal loss that is very unpleasant truth
You could solve this drawback

It's good to see you here. A couple of months ago in the ion forums you were patient and answered a lot of questions I had when I switched from HTC to Sony. Armed with a little knowledge, I was able to find a good used Z1 with an unlockable bootloader.
Thanks again.

New Version Slimkat 8.10 posted: see Download section
New version posted. See Download...

auto rotate not working
Auto rotate not working anywhere

Yes. For some reason autorotate does not work. I even recompiled the 8.12 version and it still does not work. The Slim original 8.12 is fine. It is also not my kernel, because I am using my kernel with Slimkat original weekly without any problem. I am puzzled as to why it is happening...
The only change in build.prop I made was to add 3 entries regarding rild. You can try to open build.prop and delete those three entries (search for "rild" and delete them). But I don't think rild has anything to do with the sensors.

thanks !
optimumpro said:
New version Slimkat 8.10 compiled today . New kernel with Tomoyo security enabled (as opposed to Apparmor). Enjoy.
See Download section
________________________________________________________________________________________
Here is the famous Slimkat 4-4-4 rom built from sources a few hours ago. Changes made to kernel only and they are the following:
Hardened Kernel with the following features:
a. Selinux disabled (don't trust them) and APPARMOR enabled as main security
b. All crypto core features enabled
c. All authenticated encryption modes enabled - CCM, GCM and SEQIV
d. All blocks enabled - CBC, CTR, CTS, ESB, LRW, PCBC and XTS
e. All hash modes enabled including SHA512 and others
f. All ciphers enabled including CAMELIA, TWOFISH, ANUBIS, SALSA20 and others
g. Compression - DEFLATE, ZLIB and LZO
h. Random number generation all options enabled to result in a better generation without CPU wakeups
Credit: Slimroms Team
WARNINGS:
I am not responsible for your device becoming a paperweight. I am also not responsible for death and destruction caused by your flashing this rom on your device. You are at your own perill. Complain to Putin - he will surely help.
INSTRUCTIONS
1. Unlocked Bootloader
2. If you have CWM, go to mounts and storage and wipe System/Cache/Data
3. If you have TWRP, go to advanced wipe and wipe System/Cache/Data
4. Flash the rom and reboot.
5. I recommend that you delete Cyanogenmod original boot animation as it slows down the boot significantly: without it your boot should take about 25 seconds. Once you remove bootanimation.zip in /system/media, you will have a nice vanilla android bootanimation.
6. Enjoy the rom and hit Thank You or perhaps Donate?
P.S. Rom is in Download Section above
XDA:DevDB Information
[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Beta
Stable Release Date: 2014-11-11
Beta Release Date: 2014-10-21
Created 2014-10-21
Last Updated 2014-11-11
Click to expand...
Click to collapse

Installed this 4.4.4 version and it works gr8.. but my recovery is gone
Tried : Z1-lockeddualrecovery2.8.15-RELEASE.installer and Fota.. both states that it works but my recovery never "boots" just stands there with a another light on the phone..
Suggestions anyone ?
Now i have a working 4.4.4 Rom but no working recovery (light changes but recovery never boots, when i press volume)

hakd said:
Installed this 4.4.4 version and it works gr8.. but my recovery is gone
Tried : Z1-lockeddualrecovery2.8.15-RELEASE.installer and Fota.. both states that it works but my recovery never "boots" just stands there with a another light on the phone..
Suggestions anyone ?
Now i have a working 4.4.4 Rom but no working recovery (light changes but recovery never boots, when i press volume)
Click to expand...
Click to collapse
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.

optimumpro said:
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
Click to expand...
Click to collapse
LOG:
C:\Megasync\Android\ADB + Recovery>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
C:\Megasync\Android\ADB + Recovery>fastboot reboot
rebooting...
finished. total time: 0.002s
Thanks alot for taking the time to help me, now i got an awesome 4.4.4 With a custom recovery when i change my mind (5.x.x was not stable enough)

optimumpro said:
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
Click to expand...
Click to collapse
this helped me a lot

[RECOVERY][TWRP][dragon]

April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !
https://twrp.me/google/googlepixelc.html
I would like to continue this thread for publishing test builds and other troubleshooting.
Once the changes are stable and tested I will merge them into TeamWin github for the next official build.
Known issues:
- FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.
fwtool
The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
Installation:
Please install the new version from your current TWRP.
Pls make a "reboot to recovery" once you have installed the new version.
Of course you can install it via fastboot too.
Sources:
https://github.com/TeamWin/android_device_google_dragon
https://github.com/omnirom/android_bootable_recovery
DOWNLOAD:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
Have fun!
XDA:DevDB Information
[TWRP][dragon], Tool/Utility for the Google Pixel C
Contributors
followmsi
Version Information
Status: Stable
Current Stable Version: 3.3.1-2
Stable Release Date: 2017-04-01
Created 2016-06-17
Last Updated 2023-01-11

Changes:
Official 3.7.0_9-1 (2023-03-25)
- Exclude MTP
- Restore stock values for init.recovery.dragon.rc
- Enable Screen Timeout
https://dl.twrp.me/dragon/twrp-3.7.0_9-1-dragon.img.html
Official 3.7.0 (2022-10-10)
- New official version -> https://twrp.me/site/update/2022/10/10/3.7.0-released.html
Official 3.6.2 (2022-06-01)
- New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
Official 3.6.1 (2022-03-10)
- New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
Official 3.6.0 (2021-11-28)
- New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
Official 3.5.2 (2021-04-07)
- New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html
Official 3.5.1 (2021-03-17)
- New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Official 3.5.0 (2020-12-31)
- New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html
Official 3.4.0-0 (2020-06-22)
- New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Official 3.3.1-2 (2020-03-01)
- Script updates to improve encryption -> Thanks to updateing from Team Mokee !
Official 3.3.1-1 (2020-01-27)
- Script updates for Android 10
- Added more languages
- Fixed build issues
- New Kernel
Official 3.3.1-0 (2019-05-19)
- New official version
Official 3.3.0-0 (2019-04-10)
- New official version
Official 3.2.3-0 (2018-07-29)
- New official version
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Official 3.2.2-0 (2018-06-30)
- New official version
* DRM changes
Official 3.2.1-0 (2017-12-18)
- New official version
Official 3.2.0-0 (2017-11-29)
- New official version
Official 3.1.1-1 (2017-09-15)
- Including all changes for Oreo and for better en/decryption from unofficial V1 and V2
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
- New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
- Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)
Official 3.1.1-0 (2017-05-17)
- Upgrade to 3.1.1-0
Unofficial 3.1.1-0 (2017-05-14)
- Latest TWRP changes (3.1.1)
- Latest kernel sources (2017-05-12)
- Latest LineageOS changes (Android 7.1.2)
Official 3.1.0-0 (2017-04-01)
- Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.
3.1.0-2
- Custom installer script problems should be fixed now.
3.1.0-1
- Removed all the FBE changes - will take longer to get it running on dragon
- Added NTFS-3G support for NTFS R/W -> USB-OTG
- Used new kernel binary with changed F2FS config
3.1.0-0
- @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
- Added some more config changes for FBE.
3.0.3-4
- Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.
3.0.3-3
- Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
- fstab modification (usb-otg -> auto)
3.0.3-2
- F2FS enabled
- tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)
3.0.3-1
- Based on Android 7.1.1 AOSP -> android-7.1.1_r14
- Based on TWRP branch for Android 7.1
- tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)
v23
- Based on Android 7 AOSP -> android-7.0.0_r3
- Based on TWRP branch for Android 7
- tegra-3.18 kernel -> v160907
v22
- Based on Android 7 AOSP -> android-7.0.0_r1
- Based on TWRP branch for Android 7
- chromeos-3.18 kernel -> v160823
- Maybe not fully working as v21 due to new sources.
v21
- Added BRIGHTNESS PATH ... Thx to @ggow
v20
- Added Battery PATH ... Thx to @ggow
v19
- "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now
- New versioning
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
v17
- "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
- chromeos-3.18 kernel -> v160618
v16
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617

Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app

DarthDestroyeis said:
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the feedback ..
Did you install something before .. maybe still mounted from before ?
Or you just made the backup only ?
Which partitions did you backup ? .. system as well .. or just data ?
Pls post recovery.log on pastebin.com .. helps a lot !
Thanks

http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk

DarthDestroyeis said:
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It´s always system which is complaining .. no other partitions, correct ?
Thanks ... will have a look.

Yup... just the system partition.

Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?

N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again

ilpolpi65 said:
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
Click to expand...
Click to collapse
You did flash system-vendor update.zip via fastboot ?
No good idea.
The kernel and the TWRP are fine to flash via fastboot, but not the system.img and vendor.img.
Like written on first page of the updatr.zip thread.
Pls install the package via TWRP.
Or use unmodified stock image from Google for fastboot.
For recovery bootloop I know only "fastboot reboot".
I had the bootloop once myself, as I still was on M, but the command did help me.

YevOmega said:
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
Click to expand...
Click to collapse
I am not the OTA User
As I know, the tool "flashfire" from Chainfire should handle the whole OTA process smoothly.
The Update.zip packages I do anyway, because I am used to it .. over the years.
Did this for Nexus Flo ... Nexus 10 as well.
For Pixel C I just publish them, because nobody as else is doing it.
Look in Flo and manta xda .. They have these packages too, done by others.
Because of all the problems with OTA .. in the past ..and still today.
Today we have systemless root and regular OTA...times are changing.
Maybe it's time for something like flashfire in the next time ..

sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)

ilpolpi65 said:
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
Click to expand...
Click to collapse
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..

followmsi said:
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
Click to expand...
Click to collapse
True... It's really strange..but..pixel c too is a strange device...
anyway thanks for your help !

DarthDestroyeis said:
Yup... just the system partition.
Click to expand...
Click to collapse
v17
- "Failed to unmount `/system `(Device or resource busy)" - fixed now
- chromeos-3.18 kernel -> v160618
Please have a try with v17.
My problems are gone .. no more warning messages while doing backup or restore.
"Failed to unmount `/system `(Device or resource busy)"
Pls test as well !
Thanks

sorry for all this quick releases today .. this is the last one for now !
but when something new is working .. I would like to share it with you ...
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
Enjoy !

Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work

redukt said:
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
Click to expand...
Click to collapse
Today I have made 3 backups and restores
No problems or messages so far ..
But pls test on your device as well .... On Pixel C you never know
Cheers

Ok, will test it now without wipes

redukt said:
Ok, will test it now without wipes
Click to expand...
Click to collapse
Hopefully

[RECOVERY] Unofficial TWRP for Elephone P9000 3.0.2-8

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Unofficial TWRP 3.0.2-8 for Elephone P9000
Mirror 1
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
XDA:DevDB Information
[RECOVERY] Unofficial TWRP for Elephone P9000, Tool/Utility for the Elephone P9000
Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_elephone_p9000/tree/Omni
Version Information
Status: Stable
Current Stable Version: 3.0.2-8
Stable Release Date: 2016-08-24
Created 2016-07-26
Last Updated 2016-09-11

FAQ:
Attention ROM Devs - You need to update your ROM's updater-script to use the correct by-name parts for this recovery, the old M2 ported one had this:
Code:
/dev/block/platform/mtk-msdc.0/by-name
The correct by-name parts for the Elephone P9000 are:
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
DEVICE-SPECIFIC CHANGELOGS:
3.0.2-8:
-Updated Kernel to an early version of my DarkSense kernel
-Possible fix for F2FS support (if it doesn't work we have a few theories as to why)
3.0.2-7:
-Updated Kernel to Deepflex's flexy kernel for now (compatible with new preloader and lk images)
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
3.0.2-5:
-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files
3.0.2-4:
-Fix USB-OTG Mounting
3.0.2-3:
-Use Toybox mount and grep
3.0.2-2:
-Fully built from source for Elephone P9000 - unlike the other one which was ported (repacked recovery.img) from the Elephone M2
Current TWRP "bugs" for Elephone P9000:
NONE

Jonny said:
Current TWRP "bugs" for Elephone P9000:
NONE
Click to expand...
Click to collapse
:good:
---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------
Pease upload in a different more android browser friendly host.

andy radical said:
:good:
---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------
Pease upload in a different more android browser friendly host.
Click to expand...
Click to collapse
Done, the Mega link has been renamed to Mirror 1.

installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..

andy radical said:
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
Click to expand...
Click to collapse
Thanks, I'll look into it.

3.0.2-4:
-Fix USB-OTG Mounting

andy radical said:
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
Click to expand...
Click to collapse
Further info on the battery meter issue. I spoke to some of the guys over on the twrp freenode IRC channel and after a bit of experimentation it turns out that this is an issue with the way the kernel links to the battery level, some proprietary lib or bin is needed to help link them, at this moment in time I haven't a clue which one but I'll keep looking.

Does this work on P9000 Lite?

Jtig said:
Does this work on P9000 Lite?
Click to expand...
Click to collapse
No, once I'm happy with this I'll maybe look into making one for P9000 lite, but I'm vary wary of developing things for devices I do not own, as I can't test things.

3.0.2-5:
-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files

Jonny said:
No, once I'm happy with this I'll maybe look into making one for P9000 lite, but I'm vary wary of developing things for devices I do not own, as I can't test things.
Click to expand...
Click to collapse
What's so different about P9000L? You can even run P9000 ROMs on P9000L with fixed buildprop

Jtig said:
What's so different about P9000L? You can even run P9000 ROMs on P9000L with fixed buildprop
Click to expand...
Click to collapse
I just don't particularly like doing blind builds, never have done.

Hi....can I update from TWRP 3.0.0.0 by Marsapa?
I have installed this one......
Thanks

fatalhh said:
Hi....can I update from TWRP 3.0.0.0 by Marsapa?
I have installed this one......
Thanks
Click to expand...
Click to collapse
If you have installed this one then you have updated the recovery, unless you're asking something else?
Sent from my Elephone P9000 using XDA Labs

Jonny said:
If you have installed this one then you have updated the recovery, unless you're asking something else?
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks

fatalhh said:
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks
Click to expand...
Click to collapse
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.
Sent from my Elephone P9000 using XDA Labs

Jonny said:
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
Really confusing my friend.....I am newbie in the side of rooting....flashing....etc.....and reading a lot to learn.....everytime I flash something my stomach get butterflys.....like when you are in love:laugh::silly:
Thanks mate

3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue

Jonny said:
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
Click to expand...
Click to collapse
Hi @Jonny, when I backup with twrp i must choose every voice or i must untick system image? Thank you
Inviato dal mio P9000 utilizzando Tapatalk

[RECOVERY][X00T] KudProject's Unofficial TWRP 3.5.2_9-1 (k4.4/k4.14) [16-05-2021]

This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Disclaimer​
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements​
ASUS ZenFone Max Pro (M1) ZB601/2KL (of course)
Unlocked bootloader, in either ways (official, unofficial)
Some knowledge on how to deal with your device... and patience.
Flashing Instructions​I assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Up button until ASUS logo with "FASTBOOT MODE" message appears.
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x_9-<kernel>-y-KudProject-X00T.img
Where:
x and y are version of TWRP you're going to flash.
kernel: k4.4 - stock firmware or custom ROMs with FDE encryption; and k4.14 - FBE for custom ROMs with FBE encryption.
IMPORTANT: After flashing, immediately press and hold Power + Volume Down for about 10 seconds button to reboot to recovery.
Swipe the option to allow modifications. This way, you'll trip Android Verified Boot (AVB) and it's required to flash no verity zip in order to be able to boot stock ROM.
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues​
k4.4: Due to QTI keymaster's behavior, only specific stock firmware as well as custom ROMs with same platform security patch level that can only be decrypted by TWRP. Applicable versions will be indicated explicitly in the changelog.
k4.14: Recovery may start with very low vibration level. You can adjust vibration intensity in settings later.
k4.14: Recovery can only decrypt userdata partition encrypted using AES-256-XTS algorithm. Only ROMs using Qualcomm's Inline Crypto Engine (ICE) with 4.14 kernel may also be decrypted by the recovery as well. This can be assumed an intended behavior since implementation of fscrypt_ice on msm-4.14 and msm-4.19 kernels are completely different. Tell ROM maintainers wanting to switch to FBE to use AES-256-XTS instead.
Special Thanks​
Dees_Troy and everyone behind TWRP
shakalaca - base device tree used for older releases
Ankit Gourav - his work on whyred
Shivam Kumar Jha - person who kickstarted ZenFone Max Pro (M1) development
Everyone involved in testing numbers of test builds.
Sources​
TWRP repository fork
Device tree
Kernel source: k4.4 - k4.14

Some stuffs...​Another TWRP thread? Why?
I like to keep discussions about my builds separate. Moreover, the existing TWRP that already available on XDA before doesn't seem to be maintained anymore.
I flashed via fastboot but it always fails.
Check or change your cable, use other USB slot (especially 2.0 one if 3.0+ doesn't work), or if needed try to flash recovery with USB connected to a hub.
Changelogs​twrp-3.5.2_9-1-KudProject-X00T
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Builds are now splitted for devices running FDE (targetting stock, running 4.4 kernel) and FBE encryption (targetting custom ROMs, running 4.14 kernel, only works with ROMs using AES-256-XTS encryption)
FDE: Can decrypt 16.2017.2009.087 stock firmware and any custom ROM with 5 September 2020 security patch
Restored ability to backup system and vendor partition (images backup for these partitions are recommended)
Switched to build system libraries from source
Added persist partition backup support
Added support for NFC availability check in recovery
Added support for formatting asusfw partition in GUI
Updated set_version script to match up Android 10's system-as-root behavior
FBE: Updated crypto blobs from 17.2017.2012.438 stock firmware
twrp-3.4.0-0-KudProject-X00T
Merged TWRP source changes up to 11 June 2020 (UTC+8)
Can decrypt 16.2017.2005.082 stock firmware and any custom ROM with 5 May 2020 security patch
Switched f2fs-tools to latest AOSP master
Only allow user to backup system and vendor images
set_version script doesn't longer touch persist partition; script now has hardcoded SKU and version instead in case ASUS props can't be found
Updated prebuilt kernel based on S082 source drop
F2FS kernel driver updated to 5.3-rc1 with backports up to 5.7-rc1 from 4.9
Switched to arter97's fork of exFAT
Switched from NTFS kernel driver to FUSE ntfs-3g due to incomplete write support
twrp-3.3.1-0-X00T-20190526
Fixed stock ROM flashing due to missing prop
Fixed FDE decryption
twrp-3.3.1-0-X00T-20190525
Updated F2FS on kernel to 5.2-rc1
TWRP 3.3.1 + upstream changes
twrp-3.3.0-0-X00T-20190513
Updated base to android-9.0
Updated blobs from 16.2017.1903.050
Support for flashing unmodified stock firmware (please read notes!)
Rebased kernel to S050 source drop
Updated F2FS on kernel to 5.1-rc1
TWRP 3.3.0 + upstream changes
twrp-3.2.3-0-X00T-20190217
Now based on whyred official TWRP tree
Reverted kernel to stock-based as-released (S339) with F2FS upstream and sdFAT included
(this should fix USB-OTG support while retaining support with latest f2fs-tools)
TWRP upstream changes
twrp-3.2.3-0-X00T-20190118
Pick more patches from LineageTWRP project
Updated f2fs-tools to latest development branch
Slight cleanup
TWRP upstream changes
twrp-3.2.3-0-X00T-20190115
ADB sideload fixed for everyone
f2fs-tools v1.12.0
Disabled Synaptics' firmware update driver entirely
Removed qcacld-3.0 from kernel
TWRP upstream changes
twrp-3.2.3-0-X00T-20190108
Removed ntfs-3g from recovery
Included several extra recovery keys
Updated kernel to S338-based
Disabled Synaptics' startup firmware update
TWRP upstream changes
twrp-3.2.3-0-X00T-20181231
Updated platform security patch override to 2018-11-01 (matches 338 firmware)
twrp-3.2.3-0-X00T-20181226
Imported more proprietary blobs from stock 337 firmware
TWRP upstream changes
twrp-3.2.3-0-X00T-20181224
Allow wiping vendor partition
2nd CPU target set to Cortex-A73
Initial import of proprietary blobs from stock 337 firmware
Updated kernel to S337-based
TWRP upstream changes
twrp-3.2.3-0-X00T-20181215
Removed texfat and tntfs stock modules
Enabled DT2W
twrp-3.2.3-0-X00T-20181214
Rebased to shakalaca's tree
CPU target set to kryo
Updated platform security patch override to 2018-10-01 (matches 337 firmware)
Switched to my rebased kernel
TWRP upstream changes (android-9.0 branch)
twrp-3.2.3-0-X00TD-20181024
Initial build, based on ASUS-X00TD tree

Notes​
"fastboot boot" command isn't supported by our bootloader. Don't ever try that. (blame ASUS/Huaqin)
I'll try to always keep this recovery updated especially when ASUS releases firmware update that also updates AOSP security patch. Security patch set in TWRP needs to match stock firmware used so TWRP can decrypt data partition. This isn't possible with current state as the bump is useless.
Unmodified Stock Firmware Support​With introduction of unmodified stock firmware support, I need to clear up some confusions you've if any. Notes below are copy-pasta from my post elsewhere:
Code:
Starting this build, recovery supports flashing stock firmware without modifying the updater-script. In order for it to be possible, ro.product.device has to be set to ASUS_X00TD.
This, however, breaks flashing of custom ROMs that check for either X00TD or X00T.
Simply supporting it doesn't mean that you can flash stock firmware directly; you need to be at least on stock when you flash the recovery, so required properties can be exported to /persist which then will be set on every recovery boot up.
Still not sure though, as some ROMs check for ro.product.device and then fallback to ro.build.product for matching devices.
Flashing incremental OTAs are supported but not recommended, since you'll most likely flash verity disabler at the minimum and get the flashing failed upon patching boot.
In plain text:
The recovery has ro.product.device set to ASUS_X00TD that may break custom ROM flashing.
You need to be on stock before booting the recovery for the first time, then afterwards you can flash any stock firmware. 21 June 2020 UPDATE: Now not required, as it's now hardcoded in the script itself and since touching persist is never a good idea to begin with.
If you modify your system in any ways and don't have any system backup to restore, don't flash incremental OTAs. This also includes TWRP tampering system to prevent stock recovery from overwriting TWRP.
Verifying released builds​This was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.
Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.
You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.
To import on Linux:
Code:
gpg --import krascgq.gpg
To verify builds on Linux:
Code:
gpg --verify <build-name>.sig <build-name>
Windows users will need to search for compatible tools.

size is almost half from official recovery ?

I have been using official TWRP 3.2.3.0 since last 2-3 FW updates and haven't faced any problem. However, it's good to have a specific updated TWRP for 601KL.

theraaj said:
size is almost half from official recovery ?
Click to expand...
Click to collapse
And that almost half size comes from unwanted and unused SDM630, SDM636, and SDM660 DTBs concatenated inside kernel image used.
Sent from my ASUS_X00TD using XDA Labs

First of all thank you for updating the twrp. Could you make something clear.
Is it synaptic only twrp if not can it be flashed over the older twrp?
Will it be supporting encryption?

Ak-64 said:
First of all thank you for updating the twrp. Could you make something clear.
Is it synaptic only twrp if not can it be flashed over the older twrp?
Will it be supporting encryption?
Click to expand...
Click to collapse
1. It's not a Synaptics' exclusive version, and well you can override any installed TWRP versions.
2. Not tested on my side since my data isn't encrypted, but I try to keep the platform patch inline with latest firmware so feel free to test.
Sent from my ASUS_X00TD using XDA Labs

Thank you very much for your amazing work.... hope this TWRP will get the official tag soon??

Can this decrypt encrypted data partition yet?

Thank you for your excellent work, @krasCGQ

@krasCGQ Have you been able to fix the adb sideload function that doesn't work in the older twrp builds? Thanks. Otherwise, this is good as official. Thanks for your hardwork!

I couldn't able to touch anything after booting in to recovery
I need to press power button twice to use it
Any solution

krasCGQ said:
2. Not tested on my side since my data isn't encrypted, but I try to keep the platform patch inline with latest firmware so feel free to test.
Click to expand...
Click to collapse
Hi,
you have to overwrite init.recovery.vold_decrypt.keymaster-3-0.rc in /recovery/root/ (like in shakalaca version), because the name of ven_keymaster-3-0 service is [email protected] with "-qti" at the end. Than encrypted data will work. I already test it.

vladlp said:
Hi,
you have to overwrite init.recovery.vold_decrypt.keymaster-3-0.rc in /recovery/root/ (like in shakalaca version), because the name of ven_keymaster-3-0 service is [email protected] with "-qti" at the end. Than encrypted data will work. I already test it.
Click to expand...
Click to collapse
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Sent from my ASUS_X00TD using XDA Labs

krasCGQ said:
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Click to expand...
Click to collapse
Any planning to official sir ?
Sorry if asking.

gusbalaa said:
Any planning to official sir ?
Sorry if asking.
Click to expand...
Click to collapse
Nope.
Sent from my ASUS_X00TD using XDA Labs

sorry for noob question, if i flash this new twrp it wipe my current OS or replacing twrp only? tyvm

SlamDec said:
sorry for noob question, if i flash this new twrp it wipe my current OS or replacing twrp only? tyvm
Click to expand...
Click to collapse
The latter if you flash it on the right partition; if not... :silly:
Sent from my ASUS_X00TD using XDA Labs

krasCGQ said:
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Click to expand...
Click to collapse
And... ~24 hours late from expectations, lol.
It's up for public now.
Sent from my ASUS_X00TD using XDA Labs