Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
I've been added on to this post as a contributor, so now you can direct blame my way. (Oh yeah, I'm @Hachamacha on this board.) All credits to Phil3759 and the guys the made CM11 happen.
Just added the 6.58.7 build (see main thread) and has a number of enhancements and is likely the final build for months: You can download from the usual spot in either .img or .zip format. Keep in mind that on this device I'm just a builder and don't have any of the "moto g" devices myself so all testing is in your hands.
Click to expand...
Click to collapse
6.58.7
- Source Update and Fixes
Click to expand...
Click to collapse
Update v6.57.8 / CWM 6.0.5.1 / libtouch_gui 1.41
- fix for ROM OTA updates generating two install scripts (openrecovery + extendedcommands)
- merge CWM updates to selinux permissions for init services
- fix adb for 3.10 kernel
Click to expand...
Click to collapse
6.57.5
- Update SuperSU
- merge a few SR/CWM changes and bug fixes
- fix aroma file manager issue with some slow mount/unmount devices
Click to expand...
Click to collapse
6.55.0
-add option to disable md5 from edify restore_rom command line
- this fixes restore of custom roms
Click to expand...
Click to collapse
6.54.9 - libtouch_gui 1.40
- support faster transfers through USB storage for voldmanaged devices
- fix compiling for devices with custom recovery key or ui files
-- This version adds many enhancements in the code to better support storage volumes
-- USB mount should have now good transfer speeds for vold volumes if you add needed entries in extra.fstab
Click to expand...
Click to collapse
Notes regarding 6.50.6:
- fix potential failure for TWRP backups (cause scan_mouned_volumes() not called)
- loki_recovery code clean up
- fix potential failure to reboot when checking config file
- never confirm wipe in ors scripts
- always show text in sideload mode
- support wipe_cache and clear_display edify script commands
Click to expand...
Click to collapse
Notes regarding 6.41.6:
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
Click to expand...
Click to collapse
6.41.5 - Stable
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
Click to expand...
Click to collapse
Download links
Last version can be found here:
Moto G (falcon)
- Unified device for xt1028, xt1031, xt1032, xt1033, xt1034, Google Play Edition: falcon
Build Links:6.58.7: Img: http://d-h.st/DEw : Zip: http://d-h.st/Dbh
Build links: 6.57.9 : Img : http://d-h.st/kgN : Zip : http://d-h.st/Unh
Build links: 6.57.8 : Img : http://d-h.st/FLK : Zip : http://d-h.st/vzql
Build links: 6.57.5 : Img : http://d-h.st/lTD : Zip : http://d-h.st/D8y
Build links: 6.55.0 : Img : http://d-h.st/ljR : Zip : http://d-h.st/Seu
Build links: 6.54.9 : Img : http://d-h.st/3GH : Zip : http://d-h.st/N6G
Build links: 6.50.6 : Img : http://d-h.st/Lwx : Zip : http://d-h.st/F8Y
Build links: 6.41.6 : Img : http://d-h.st/LmY : Zip : http://d-h.st/KUS
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
XDA:DevDB Information
[falcon][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Moto G
Contributors
Phil3759, hachamacha
Version Information
Status: Stable
Created 2014-05-11
Last Updated 2014-10-21
FIRST TO REPLY! NICE!! whats the ETA for the upload to the goo.im?
At last we got a fully stable recovery.
Hey wait wait. wait.. wait... wait....
Brought to you by my own mmmmuuuuffffffffiiiinnnn
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt1032
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt1033
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt1034
Thx phil really appreciated
done uploading xt1032, xt1033 and xt1034
Let me know about any bug
Very nice. Not fully usable for GPE devices though, cannot mount /data partition supposedly because it is fomatted to ext4 not f2fs.
Seemed to backup as expected going todo a restore now ill let you know how it goes.
I did a full cleanup before i was going to restore the rom it seems to have deleted the backup.
drfr said:
Very nice. Not fully usable for GPE devices though, cannot mount /data partition supposedly because it is fomatted to ext4 not f2fs.
Click to expand...
Click to collapse
What is GPE ?
If you need ext4 vs f2fs, let me know which devices should be fixed
Phil3759 said:
What is GPE ?
If you need ext4 vs f2fs, let me know which devices should be fixed
Click to expand...
Click to collapse
Google Play Edition
Enviado desde mi XT1032 mediante Tapatalk
GPe Moto G uses ext4 instead of f2fs. Working fine on XT1032 running 4.4.2.
Does anybody know if this also works with 4.4 on XT1033?
lost101 said:
GPe Moto G uses ext4 instead of f2fs.
Click to expand...
Click to collapse
They have same code (xt1032...) ?
Phil3759 said:
They have same code (xt1032...) ?
Click to expand...
Click to collapse
I believe so.
http://forum.xda-developers.com/showthread.php?t=2622323
One other thing, the date in CWM is wrong; backup today was labeled: 1970-02-14.11.06.59_KLB20.9-1.10-1.9
i get the 'can't mount backup path' error... what do i need to do to get rid?
lost101 said:
I believe so.
http://forum.xda-developers.com/showthread.php?t=2622323
One other thing, the date in CWM is wrong; backup today was labeled: 1970-02-14.11.06.59_KLB20.9-1.10-1.9
Click to expand...
Click to collapse
You can go into the settings and manually change the date.
Will this recovery be able to install OTA updates for stock rooted ROM?
jamesro1208 said:
You can go into the settings and manually change the date.
Click to expand...
Click to collapse
Where can i find those settings? For me is showing '2024-02-13....' after backup.
Sent from my Nexus 7 2013 using xda app-developers app
jamesro1208 said:
You can go into the settings and manually change the date.
Click to expand...
Click to collapse
Settings where?
rapunzel11 said:
Where can i find those settings? For me is showing '2024-02-13....' after backup.
Sent from my Nexus 7 2013 using xda app-developers app
Click to expand...
Click to collapse
michalurban said:
Settings where?
Click to expand...
Click to collapse
PhilZ Settings - GUI Preferences - Time Setup
Related
IRC on freenode: #sk8erwitskil
NEW: I have created a script to easily update to the latest version of my recovery.
- Download this file ----> updater.sh (updated to fix typo)
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh skyrocket
- it will reboot you into recovery
- starting in v14.2.1 it will automatically start installing and reboot when its done
Note: If your sdcard is not mounted on /mnt/sdcard then open the script and change the line that says path=/mnt/sdcard/sk8sUpdater to match your mount point. i.e. ICS users may have to change it to say path=/mnt/emmc/sk8sUpdater
Click to expand...
Click to collapse
I have ported touch recovery to Clockworkmod 6. I will be making updates to this just like my other touch recovery. I have added a few menu items and tweaks to make it like my CWM5 recovery.
Looking through the cwm code more in depth i have noticed MANY flaws with the code for new(er) phones that use /emmc instead of /sdcard as the main storage. i have now fixed those flaws in v9+.
Here is a video of how it works: --------> YOUTUBE LINK
Flashable zip:
cwm6027touch_v14.4.6_skyrocket.zip: ---------> DOWNLOAD
Click to expand...
Click to collapse
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
[/CODE]
Current Version:
v14.4.6
- added exFAT support
- some under the hood optimizations
Click to expand...
Click to collapse
Major update to how touch works now:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Whats in the extras menu?
- change bootanimation (this lets you select a bootanimation form your internal sdcard. it backs up your current bootanimation to /{internal sdcard}/clockworkmod/ba_backup/. it only backs up the original bootanimation so if you keep changing your bootanimation you will still only have your original one in ba_backup.)
- enable/disable one confirm (this makes it so you only have to scroll through one confirm selection when installing something instead of having to go through 10 of them to click yes)
- hide/show backup & restore progress (this makes it so the progress bar when you backup/restore doesnt show up and makes backups/restores a bit faster since it doesnt have to show you the progress and files its backing up)
- select android_secure on internal/external (use this to select where you have .android_secure. default is internal, so if you have it on external make sure to choose this once to set it up)
- aroma file manager (file explorer)
- create custom zip (this will create a custom rom from the currently installed files you have on your phone. it takes your /system partition and /boot partition and makes them into a zip file ready to be flashed. the end product will be in clockworkmod/custom_rom/. this has recently been fixed to work on all phones/roms
- choose custom openrecoveryscript (read THIS)
- recovery info (shows the version of recovery and the build date)
- Special Backup & Restore (backup and restore your kernel/boot and /misc partitions)
- Misc Nandroid Settings (change time zone, turn preload support on/off (default is off), enable md5 checking)
I used the odin install and now I cant boot into recovery at all. just goes to a black screen.
its fixed now
BaconStep said:
I used the odin install and now I cant boot into recovery at all. just goes to a black screen.
Click to expand...
Click to collapse
let me take a look.
sk8erwitskil said:
let me take a look.
Click to expand...
Click to collapse
almost fixed. uploading now
watching this
Hope to check this out soon! Gotta wait for a more stable release though.
Slightly off topic but what are the benefits in upgrading CWM? I'm on 5.5.0.4 touch and have always disregarded upgrading with each phone I root as they all seem to function the same.
Sent from my SGH-I727 using Tapatalk 2
lnfound said:
Slightly off topic but what are the benefits in upgrading CWM? I'm on 5.5.0.4 touch and have always disregarded upgrading with each phone I root as they all seem to function the same.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Mostly bug fixes and compatibility issues.
This should be ready soon! Gweedo and utkanos are working on it as well so something good is coming
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
augh yes! i fixed it and its running smooth as buttah!!! ill add recovery.img and recovery.tar.md5 later but there is a flashable zip in the OP. just flash in recovery.
When wiping davlk, it throws like it was on CWM 5
E:unknown volume for path [/sd-ext]
Dismal Shadow said:
When wiping davlk, it throws like it was on CWM 5
E:unknown volume for path [/sd-ext]
Click to expand...
Click to collapse
yes thats expected. i dont know how many times this has been talked about. /sd-ext is a legacy option in cwm that was used for apps2sd. if you can find a cwm that doesnt show that error i would be shocked. the only reason it doesnt do it on my 5.5.0.4 touch recovery is because i took out the part where it prints it to the screen so people would stop asking about it. lol.
You are awesome, we need you over on the gsiii side...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Will this work for the t989?
Gotroot said:
Will this work for the t989?
Click to expand...
Click to collapse
Yea it should i flashed the first one put up and it wrked on my t989
Sent from my SAMSUNG-SGH-T989 using xda premium
Gotroot said:
Will this work for the t989?
Click to expand...
Click to collapse
yes it will work. but the fix permissions might not work. i have to make one specifically for the hercules. thats my project tomorrow.
So just to clarify. Download zip. Flash in current cwm touch and that's it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
garydv2002 said:
So just to clarify. Download zip. Flash in current cwm touch and that's it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yessir
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
RiNo808 said:
You are awesome, we need you over on the gsiii side...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
no poaching our devs!
deezhemi said:
no poaching our devs!
Click to expand...
Click to collapse
Heh.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
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.
CHANGELOGS :
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.
TWRP 3.0.0.0_2 (All Variants support)
twrp-3.0.0.0_2-falcon.img #CHANGELOG
Old downloads :
OLD TWRP 3.0.0.0
twrp-3.0.0-falcon_gpe.imgtwrp-3.0.0-falcon.img
Latest TWRP 2.8.7.0
twrp-2.8.7.0.-falcon_M_GPE.img
twrp-2.8.7.0.-falcon_M_GPE_NOTHEME.img
twrp-2.8.7.0.-falcon_M_STOCK.img
twrp-2.8.7.0.-falcon_M_STOCK_NOTHEME.img
TWRP 2.8.7.0
twrp-2.8.7.0.-falcon_GPE.img - 9.8 Mo (AFH Mirror)
twrp-2.8.7.0.-falcon_GPE_NOTHEME.img - 9.2 Mo (AFH Mirror)
twrp-2.8.7.0.-falcon_STOCK.img - 9.8 Mo (AFH Mirror)
twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img - 9.2 Mo (AFH Mirror)
TWRP 2.8.6.0 - OLD
twrp-2.8.6.0-falcon.img - 9.0 Mo
twrp-2.8.6.0-falcon_GPE.img - 9.0 Mo
*Later
twrp-2.8.6.0-falcon_GPE.img - 10.0 Mo
twrp-2.8.6.0-falcon.img - 9.9 Mo
* Later later 2.8.6.0.1
twrp-2.8.6.0.1-falcon_GPE.img - 8.9 Mo
twrp-2.8.6.0.1-falcon_STOCK.img - 8.9 Mo
* Later later later
twrp-2.8.6.0.-falcon_GPE_NOTHEME.img - 9.2 Mo
twrp-2.8.6.0.-falcon_GPE.img - 9.8 Mo
twrp-2.8.6.0.-falcon_MULTI_NOTHEME.img - 9.2 Mo (Might be able to run GPE and STOCK. This need to be tested !)
twrp-2.8.6.0.-falcon_STOCK_NOTHEME.img - 9.2 Mo
twrp-2.8.6.0.-falcon_STOCK.img - 9.8 Mo
twrp-2.8.6.0.-falcon_MULTI.img - 9.8 Mo (Might be able to run GPE and STOCK. This need to be tested !)
TWRP 2.8.5.0
twrp-2.8.5.0-falcon.img - 10.0 Mo
twrp-2.8.5.0-falcon_GPE.img - 10.0 Mo
TWRP 2.8.4.0
openrecovery-twrp-2.8.4.0-falcon_GPE.img is for GPE ONLY (ext4 userdata)
openrecovery-twrp-2.8.4.0-falcon_STOCK.img is for STOCK ONLY (f2fs userdata)
openrecovery-twrp-2.8.4.0-falcon_GPE_LP.img is for GPE ONLY (ext4 userdata & lollipop bootloader)
openrecovery-twrp-2.8.4.0-falcon_STOCK_LP.img is for STOCK ONLY (f2fs userdata & lollipop bootloader)
TWRP 2.8.3.0
twrp-2.8.3.0_falcon-GPE_sub77.img
twrp-2.8.3.0_falcon-STOCK_sub77.img
TWRP 2.8.2.0 :
twrp-2.8.2.0_falcon-GPE.img is for GPE ONLY (ext4 userdata)
twrp-2.8.2.0_falcon-STOCK.img is for STOCK ONLY (f2fs userdata)
How to install ? :
Do
Code:
sudo fastboot flash recovery twrp-3.0.0-falcon_gpe.img
or
Code:
sudo fastboot flash recovery twrp-3.0.0-falcon_gpe.img
Sources
- android_device_motorola_falcon
Bugs ?
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Support
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][falcon] TWRP 3.0.0-0 touch recovery [2016-03-06], Tool/Utility for the Moto G
Contributors
h2o64
Version Information
Status: Stable
Created 2014-12-22
Last Updated 2016-03-06
is it normal if I can see some line running from top to bottom of my screen?
and I can do backup but can not restore it.
and can not boot after this.
it's really alpha
gpe 5.0.1
S0bes said:
is it normal if I can see some line running from top to bottom of my screen?
and I can do backup but can not restore it.
and can not boot after this.
it's really alpha
gpe 5.0.1
Click to expand...
Click to collapse
I know fixes.
New release in a minute.
h2o64 said:
I know fixes.
New release in a minute.
Click to expand...
Click to collapse
it is gpe related. i have just checked with xt1032.
Is dis multirom recovery and btw how much you approached in multirom ..
sub77 said:
it is gpe related. i have just checked with xt1032.
Click to expand...
Click to collapse
Yes yes.
I'm uploading the two new files :
twrp.fstab is the fstab for backup.
BUT the actual one backup userdata f2fs only.
SO we needed to make 2 different ones
Bhavy123 said:
Is dis multirom recovery and btw how much you approached in multirom ..
Click to expand...
Click to collapse
@sub77 and me are doing this in order to get a proper Multirom v30 (TWRP 2.8.2.0 based)
h2o64 said:
Yes yes.
I'm uploading the two new files :
twrp.fstab is the fstab for backup.
BUT the actual one backup userdata f2fs only.
SO we needed to make 2 different ones
@sub77 and me are doing this in order to get a proper Multirom v30 (TWRP 2.8.2.0 based)
Click to expand...
Click to collapse
Wish you all d best and really wish that you sussessfully port one to our device.Thanks for d hardwork btw how much time will it take more to port multirom ?
Bhavy123 said:
Wish you all d best and really wish that you sussessfully port one to our device.Thanks for d hardwork btw how much time will it take more to port multirom ?
Click to expand...
Click to collapse
I don't know
NEW BUILD :
- graphic issue fixed
- add differents recoveries for GPE or STOCK
@sub77 , MTP issue is due to the lollipop encrytion.
Maybe "twrp set tw_mtp_enabled 0" will solved it ?
Backup/ Restore works without any issues on XT1032 Retail EU, first version of TWRP2.8.2.0. :good:
Cant download new version from Mega (shows me only blank screen), Mirror would be nice :fingers-crossed:
Kai Obey said:
Backup/ Restore works without any issues on XT1032 Retail EU, first version of TWRP2.8.2.0. :good:
Cant download new version from Mega (shows me only blank screen), Mirror would be nice :fingers-crossed:
Click to expand...
Click to collapse
I'm mirroring.
Thanks a lot for this, specially for fixing the graphical glitch. I'll be trying it on GPE 5.0.1 ASAP. By the way, can you hangouts me? Thanks
Edit: After flashing, the screen flickering is still there
mount usb storage doesn't work - stock version.
xpirt said:
mount usb storage doesn't work - stock version.
Click to expand...
Click to collapse
Sure ?
EDIT :
MTP doesn't work
@h2o64 I flashed gpe version!!
Graphical glitch is there and i cant even factory reset!!
The recovery restarts when i do factory reset!!
Sent from my Moto G using XDA Free mobile app
your mirror is broken
also i cannot get into recovery at all
i see teamwin logo for a moment and then my phone reboots into lollipop
calusari said:
your mirror is broken
also i cannot get into recovery at all
i see teamwin logo for a moment and then my phone reboots into lollipop
Click to expand...
Click to collapse
Just reboot again and it should work.
Else, provide logs please
Flashhhh said:
@h2o64 I flashed gpe version!!
Graphical glitch is there and i cant even factory reset!!
The recovery restarts when i do factory reset!!
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
The factory reset make the device reboot because there is a wierd thing with the userdata partiotion (encryption issues ... again ...) BUT the partition is wiped.
Could you describe the graphical glitch ?
Flashed the stock image on a german xt1032
Usb-otg, wiping cache/dalvik, flashing supersu zip (on 4.4.4 stock) all working :good:
Edit: Flashed update to 2.8.3 and now recovery is unusable because of massive screen issues..
With techerrata's build screen is fine..
Added TWRP 2.8.3.0 Version
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
@h2o64 what is the difference between this build and official build
Edit : OK I got the answer
reversegear said:
@h2o64 what is the difference between this build and official build
Edit : OK I got the answer
Click to expand...
Click to collapse
And here, we know who built it, we know the trees,...
And we can upgrade faster.
I made this recovery because I'm working on multirom and I wanted to share this piece of work
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
20160214: Upstream merge till 34741d9cefd5981d23330eb6f6130d7d30ddf206
20160328: Upstream merge till a915ec4215386949ab0a92d2c401c004864cba6a
DOWNLOAD:
at least u already use TWRP 2.8.7.0 by @dh.harald
1) Download Folder
2) Reboot to TWRP
3) Hit Install and tap the "Images..." 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
Device: https://github.com/fire855/android_device_xiaomi_ferrari
Kernel: https://github.com/fire855/android_kernel_xiaomi_ferrari
Vendor: https://github.com/fire855/android_vendor_xiaomi_ferrari
Credits:
@dh.harald
@omerjerk
@fire855
@k2wl
Altaf-Mahdi
rohanpurohit
Thanks for sharing. Is it working just update recovery while i use custom rom??
Sent from my MI 4i using Tapatalk
dkasmara said:
Thanks for sharing. Is it working just update recovery while i use custom rom??
Sent from my MI 4i using Tapatalk
Click to expand...
Click to collapse
yes, just flash it via some apps like flashify or rashr
dkasmara said:
Thanks for sharing. Is it working just update recovery while i use custom rom??
Sent from my MI 4i using Tapatalk
Click to expand...
Click to collapse
D4rkCyb3r said:
yes, just flash it via some apps like flashify or rashr
Click to expand...
Click to collapse
Already mentioned above
And the step
I've fleshed it over the old version, it's really cool, and the bug with duplicating storage was fixed.
Thanks a lot.
Thanks for the latest version!
why in this version wipe process too long?
just me?
old twrp by magdag
fumakila said:
why in this version wipe process too long?
just me?
old twrp by magdag
Click to expand...
Click to collapse
It's same like dh.harald
Use rm rf instead of format
Rm rf it's linux command to remove entire directory
faizauthar12 said:
It's same like dh.harald
Use rm rf instead of format
Rm rf it's linux command to remove entire directory
Click to expand...
Click to collapse
How to change it?
blackagent said:
How to change it?
Click to expand...
Click to collapse
Please check setting section(TWRP Setting ..... ,u can see the setting button)
Hi, I got this while use format data.
Sorry for my bad English.
rhotha said:
Hi, I got this while use format data.
Sorry for my bad English.
Click to expand...
Click to collapse
Hmm ,i never use format data feature..
I used wipe
I will find out why
And wait for next commit from TWRP repo
Anyway ,can u tell me which firmware and which rom u used ?
How can I do merge the partitions?
In the 1st version of this new TWRP 3, he doubled the partitions.
So I updated to the 2nd version but also have duplicate partitions.
How can I fix this?
It's just a display bug nothing to worry about just use it as normal
nice job brother.. :good:
but it takes a long time when the wipe cache and Dalvik
sorry for bad english
-Rhoby|™-Bugs said:
nice job brother.. :good:
but it takes a long time when the wipe cache and Dalvik
sorry for bad english
Click to expand...
Click to collapse
Firmware?
Rom ?
-Rhoby|™-Bugs said:
nice job brother.. :good:
but it takes a long time when the wipe cache and Dalvik
sorry for bad english
Click to expand...
Click to collapse
Go to TWRP settings -> use rm rf instead of format
Gesendet von meinem Mi 4i mit Tapatalk
faizauthar12 said:
Hmm ,i never use format data feature..
I used wipe
I will find out why
And wait for next commit from TWRP repo
Anyway ,can u tell me which firmware and which rom u used ?
Click to expand...
Click to collapse
I use global v6 6.6.6.0
Edit: the case is same with twrp 2.8.7.0 by dh.harald
Could you please advise why do I can't see USB OTG at this TWRP?
ROMs used are CM13 by fire 865 and RR since 3/23.
RiD91 said:
Could you please advise why do I can't see USB OTG at this TWRP?
ROMs used are CM13 by fire 865 and RR since 3/23.
Click to expand...
Click to collapse
Try change file format type of this usb.
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.
Features :
- f2fs formatable support (/data and /cache)
- Lattest kernel from @dev_harsh1998
DOWNLOAD :
3.0.2:
Lenovo-A6000-TWRP-3.0.2
3.0.3 (thanks to @TingyiChen) :
Lenovo-A6000-TWRP-3.0.3
3.1.0 (big thanks to @dev_harsh1998) :
Lenovo-A6000-TWRP-3.1.0
Installation Instruction :
Make sure you are on latest firmware
Fastboot :
- Turn off your phone, combine power + vol (-) to enter fastboot
- type " fastboot device " to check devices
- type " fastboot flash recovery TWRP-3.0.2-Lenovo-A6000x32.img "
- type " fastboot reboot "
TWRP :
- reboot into recovery (TWRP)
- select install image
- select TWRP-3.0.2-Lenovo-A6000x32.img
- swipe to install
- and reboot
Convert to f2fs :
Backup all your data off the Internal Storage because it will get wiped!!
- Enter TWRP, choose Wipe > Advanced Wipe
- Make a full wipe except External SD Card
- Check the box for "data" (for data) / Check the box for "cache" (for cache)
- Tap "Change or repair file system"
- Tap "Change file system"
- Tap "F2FS"
- Swipe the button
- Flash Kernel & ROM with F2FS support[/QUOTE]
Device tree-3.0.3:
Lenovo-A6000-TWRP-3.0.3
Credit :
@dev_harsh1998
@TingyiChen
XDA:DevDB Information
TWRP-3.0.2, Tool/Utility for the Lenovo A6000/Plus
Contributors
bugerxXx
Version Information
Status: Testing
Created 2017-01-23
Last Updated 2017-01-23
XDA:DevDB Information
TWRP-3.1.0-Lenovo-A6000, Tool/Utility for the Lenovo A6000/Plus
Contributors
bugerxXx
Version Information
Status: Stable
Created 2017-01-23
Last Updated 2017-05-05
Screenshot :
Update :
- Remove cursor (thanks to @TingyiChen)
- Add missing partition for backup
Update link:
https://www.androidfilehost.com/?fid=673368273298926090
Finally here!!!! Could you also include the steps get f2fs on our device with lineage 14.1 source built ROM? Would be really useful
Woohoo finally f2fs support now we need more f2fs rom
Working fine so far :good: I'll report if I find any bugs.
Vignesh_K said:
Working fine so far :good: I'll report if I find any bugs.
Click to expand...
Click to collapse
Thanks
Good I will push 32bit tree to twrp official gerrit
nice work man
but i don't understand what is f2fs ? can you tell me
Thanks
Iqbal Now thats what i call community support Hatts off to you .., Man you made my works easier
Islam Mu said:
nice work man
but i don't understand what is f2fs ? can you tell me
Thanks
Click to expand...
Click to collapse
F2fs is a filesystem developed by Samsung which provides better performance for devices that use flash memory such as smartphones.
Vignesh_K said:
Finally here!!!! Could you also include the steps get f2fs on our device with lineage 14.1 source built ROM? Would be really useful
Click to expand...
Click to collapse
it is already mentioned in OP, but still:
- Enter TWRP, choose Wipe > Advanced Wipe
- Make a full wipe except External SD Card
- Check the box for "data" (for data) / Check the box for "cache" (for cache)
- Tap "Change or repair file system"
- Tap "Change file system"
- Tap "F2FS"
- Swipe the button
- Flash Kernel with F2FS and N support
Vignesh_K said:
F2fs is a filesystem developed by Samsung which provides better performance for devices that use flash memory such as smartphones.
Click to expand...
Click to collapse
this is good i make change to f2fs
but while i flashing a rom i found 2 file system
1- f2fs
2- ext4!!
this is normal ?
screenshot for more details
Islam Mu said:
this is good i make change to f2fs
but while i flashing a rom i found 2 file system
1- f2fs
2- ext4!!
this is normal ?
screenshot for more details
Click to expand...
Click to collapse
did you change system to f2fs ?
Islam Mu said:
this is good i make change to f2fs
but while i flashing a rom i found 2 file system
1- f2fs
2- ext4!!
this is normal ?
screenshot for more details
Click to expand...
Click to collapse
You changed system to f2fs change it back
dev_harsh1998 said:
Iqbal Now thats what i call community support Hatts off to you .., Man you made my works easier
Click to expand...
Click to collapse
bugerxXx said:
did you change system to f2fs ?
Click to expand...
Click to collapse
i wiped every thing then i check system
change and repair
change system
f2fs
swipe button
then i flash lineage 14.1 rom
anything wrong ?
i tried check data and cahe and click change and repair system so i got error
Islam Mu said:
i wiped every thing then i check system
change and repair
change system
f2fs
swipe button
then i flash lineage 14.1 rom
anything wrong ?
i tried check data and cahe and click change and repair system so i got error
Click to expand...
Click to collapse
You should change it one by one. I also got error
---------- Post added at 05:10 PM ---------- Previous post was at 05:09 PM ----------
Don't change system to f2fs it should be ext4
Vignesh_K said:
You should change it one by one. I also got error
---------- Post added at 05:10 PM ---------- Previous post was at 05:09 PM ----------
Don't change system to f2fs it should be ext4
Click to expand...
Click to collapse
right, i tried it right now
thanks bro i will try and give my feedback with new SS
why recovery deceted 2 filesystem or this is the same file ?
Mod Edit: Content Removed
XDA:DevDB Information
Dead Toolkit {Infos} Xtrem/Assault, Tool/Utility for the Xiaomi Mi A2
Contributors
Matteo
Version Information
Status: Abandoned
Current Stable Version: DEAD
Stable Release Date: -0001-11-30
Created 2018-12-16
Last Updated 2019-02-04
Latest
-----------------------------------------------------
Version 5.4
Changelog:
- donation engine
- russian fix
- update & fix ota scripts
- fix's & improvements
-----------------------------------------------------
Version 5.3
Changelog:
- russian language & support
- fix github repos
- fix git engine
- update language engine
- update & fix ota scripts
- fix's & improvements
-----------------------------------------------------
Version 5.0
Changelog:
- move repos to github
- new git engine (now download repos, ota etc using git clone)
- update language engine
- english only
- better file locations & file optimizations
- new ota scripts
- fix's & improvements
- delete offline version, soon back again
- soon a version with an option to disable auto-update verification, so user can do it manually
-----------------------------------------------------
Old Changelog
-----------------------------------------------------
Version 4.2
Changelog:
- new language engine
- english, spanish, indonesian
- better file locations & file optimizations
- new ota scripts
- fix's & improvements
-----------------------------------------------------
Version Offline 4.2
Changelog:
- first release
- same changelog as version 4.2, but without ota scripts and without the update engine
-----------------------------------------------------
Version 2.0
Changelog:
- new engine
- some UI fix's and improvements
- auto update engine
- ota notification engine
- better scripts
- better edits & scripts for the twrp part
- same for teh rom part
-----------------------------------------------------
Version 1.3
Changelog:
-delete release engine
-create release & download engine
-ui fix's & improvements
-engine fix's & improvements
-update updater scripts
-fix extract scripts
-update credits
-create version rules
-easter egg
Woo nice man, i have usb debugging enabled on stock pie when i enter adb toolkit and select flash rom i get could not detect the active partition used, please ensure your phone is plugged in and in fastboot mode.
Press any key to retry..
when i whant to flash a ROM
boot into TWRP failed.
what can I do?
Thanks
Thanks
If I install twrp permanently, will I lose the OTA updates?
bavmouse said:
when i whant to flash a ROM
boot into TWRP failed.
what can I do?
Thanks
Click to expand...
Click to collapse
try to change the usb port
BassB said:
try to change the usb port
Click to expand...
Click to collapse
thanks! after changing the usb-port the toolkit works fine. everything was flashed, rom, twrp, hex, magisk. but after reboot in system i hang now in bootloop, after few minutes device powers off and wenn i start again it stocks on androd one logo for a few minutes, until device power off again. what went wrong? thank you.
EDIT
without hex it works fine-
awesome!
will try later
Hi,, does it work on the V10.0.2.0 ???
Can i temp root and go back to unroot??
Thks
royaltartufo said:
Hi,, does it work on the V10.0.2.0 ???
Thks
Click to expand...
Click to collapse
It works on V10.0.2.0 for me.
Can u add update ROM also
Matteo said:
Hey ! Today i will share you my new project, the "Mi A2 Xtrem Toolkit" !
Click to expand...
Click to collapse
I think you should update the HEX kernel that is included with this tool. The previous version causes bootloops. Use the latest one from telegram.
Edit - Sorry, I didn't see that you haven't included files of your own. The user needs to add them.
The provided TWRP isn't decrypting user data on V10.0.2.0 :/
Is it possible to used it for enabling camera2 API?
xdxita said:
The provided TWRP isn't decrypting user data on V10.0.2.0 :/
Click to expand...
Click to collapse
That's why we use sideload... Read everything next time.
Matteo
GK_NL said:
Is it possible to used it for enabling camera2 API?
Click to expand...
Click to collapse
Maybe in the next alpha build.
Matteo
The Toolkit linked in the thread is outdated. I will update it in some hours.
Changelog :
- new engine
- now stable
- auto update ( don't need to download a specific file or something like that. The Toolkit will does everything )
- some fix's and improvements
sakiyo said:
Can u add update ROM also
Click to expand...
Click to collapse
I will check that. Thank you for your support. When the new build will be pushed you will be able to contact me using the toolkit. It will allows user to have better support than on XDA.
Matteo
Matteo said:
That's why we use sideload... Read everything next time.
Matteo
Click to expand...
Click to collapse
Matteo, problem is that I need to access /data to remove a faulty magisk module that is causing bootloop. So far my only 2 options are wait for a fully working recovery or format /data.