[08/03/2019] AMlogic Tools [7.1.0][A new milestone][Donate Version Available] - Android Stick & Console AMLogic based Computers

So, AMlogic have a horrible way of dropping support for their tools.
Decided to make a few of my own. More stable, more efficient and (no longer opensource)!
Also, with the versions of the tools, i decided to base it on the latest version of the amlogic tool and increment it by 1.
ALL DOWNLOADS ARE HERE IN A SINGLE PACKAGE(32.6mb)
BE SURE WINDOWS DEFENDER AND ANTIVIRUS DO NOT INTERFERE WITH THE PROGRAMS AND ALL ITS CONTENT!!!
The only thing i request is that my software is not mirrored or uploaded anywhere else
Wanna create your own ROM? Check out my Android guides on Youtube right Here
And there is also a guide on making a custom firmware with V6.0.0 Here
Feel free to check out my website RD Engineering​
A donate version is now available so donate HERE and email [email protected] after you have donated to acquire the donate version​
Click to expand...
Click to collapse
Donate version is now free - Visit my website for download link - http://rickydivjakovski.com/
Customization Tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixes/Features-
-Removed obsolete functions
-Better tool management
-More information displayed
-Fixed changing bootanimation
-Fixed bootanimation orientation
-Added bootanimation dimensions + FPS are now shown
-Fixed displaying wallpaper
-Fixed ability to change wallpaper
-Fixed ability to display bootlogo
-Apps tab now literally shows all apps.
-Added kernel/recovery tab
-Shortcuts to open certain kernel files added
-Shortcuts to open certain recovery files added
-Ability to convert recovery to TWRP recovery
-Option to open Generic.kl(keymap) file
-Ability to add init.d support(system hook)
-Abillity to compile into TWRP flashable zip
-Added option to choose wipe /data
-Added options to choose what files to write
-Faster EXT4 decompression
-Faster way of splitting update package
-Partition verification added
-Ability to save as project
-Repack to USB burn img
-Change bootvideo
-Enable boot video
-DTB editing
-Add/remove required keys for firmware flashing
-Enable adblocking(Donate version only)
-Full vendor partition support(Donate version only)
-Abillity to modify the internal partition table(Donate version only)
-Unpack/Repack the bootlogo
Much more i have forgot..
Bootloader Console​Fixes/Features-
-Communicate with UBOOT
Burn Card Maker
Fixes/Features-
Formatting happens in the background(no P/Invoke)
Formatting done on seperate thread
Quicker extraction of aml_sdc_burn.UBOOT
Faster file processing
AMLogic Flash Tool
Fixes/Features-
Flash kernel
Flash recovery
Port recovery from device recovery
Port recovery from recovery.img
Port recovery from Upgrade package
Flash after completing port
Backup kernel/recovery to folder
Backup kernel/recovery to flashable.zip
Reboot
Reboot into recovery
Flash zip(coming soon)
Upgrade Info Tool
Fixes/Features-
Basically displaying all needed info about an AMLogic upgrade package
CHANGELOG
Code:
---------------------------->> v6.0.0 <<----------------------------
Built newest make_ext4fs from source
Built newest sparse utillities(simg2img, img2simg etc) from source
Built newest unpackbootimg from source
Built newest mkbootimg from source
Built newest mkbootfs from source
Built newest dtc from source
Newest cygwin libs
Removed the need for multiple copies of the same library
Automater program build system
Better backwards compatibillity support for microsoft windows
Full 5.x.x > 8.1 support(Soon 9.0 aswell)
Code has been cleaned
---[Customization Tool]---
Optimized gathering file contexts
Added support for unpacking/repacking vendor
Fixed 8.x compatibillity issues
Faster repacking
Removed DTB editing(still unpacks/repacks, just makes the tool too slow)
Fixed booting issues with vendor
Support for more launchers
Removed recovery converting
Partition lengths now read from DTB
Added automated debloating(Donate version)
Added abillity to block ads(Donate version)
Quick Unpacker(Donate version)
Added partition table modification(Donate version)
Appended full vendor support(Donate version)
---[Quick Unpacker]---
Initial release(serves the purpose of standard level2 unpack/repack)
---[Unpacker Class]---
Added vendor support
Fixed contexts issue
Fixed 8.x compatibillity issues
Added true timestamp
---[XML Decipher]---
Initial released
Abillity to split files by tags
Abillity to patch files by tags
---[AML Partition]---
Initial release
Abillity to generate simple partition table
---[AMLogger]---
Added more detailed logging
---------------------------->> v5.5.0 <<----------------------------
---[Customization Tool]---
Optimizations to the unpacking process
Fixed typo in packing tab
Fixed simg2img crash
Fixed not booting bug
Fixed SizeInflater creating 1bit bigger bug
Added abillity to repack logo
Fixed disabling tabs while packing
Added option to change bootlogo
---[Unpacker Class]---
Added repacking logo support
Redesigned Unpack logo class
All streams optimized and closed before disposed(freeing resources)
Added ResInjector class(Inject resources to a specific index) - never used in tools..
---[ResPack]---
Added support for unpacking AMLogic resource files
Added support for repacking AMLogic resource files
---[AMLSerialConsole]---
Communicate with the device via serial(UART)
---------------------------->> v5.3.1 <<----------------------------
---[Unpacker Class]---
Fixed contexts typo causing crash
---------------------------->> v5.3.0 <<----------------------------
Added AMLogic driver installer
---[Customization Tool]---
Fixed removal of old DTB combo box items
Removed logging of keys
Fixed double unpacking of bootlogo
Tool now checks for currupt bootlogo(bitmap)
Tool now checks if bootanimation exists
More launcher support(Minix)
---[Unpacker Class]---
Added logging of keys
Fixed detection of null raw image
Quicker EXT4 partition unpacking
Updated file context tool
---[AMLogic driver installer]---
Added worldcup driver to the installer
Added PL2303 driver to the installer
---[Bootloader console]---
Added icon for bootloader console
---------------------------->> v5.2.0 <<----------------------------
Fixed simg2img binary issue
Fixed simg2img binary incompatibillity issues(cygz.dll)
Added missing binary and libraries for bootloader console
---[Customization Tool]---
System is now converted to a raw ext4 img before unpack - longer process but more stable
---[Amlogic Bootloader Console]---
Fixed startup crash
---------------------------->> v5.1.5 <<----------------------------
---[Customization Tool]---
Fixed repack issue with platform configuration
Fixed key check on unpack
Added logging for required firmware keys
---------------------------->> v5.1.2 <<----------------------------
Added platform configuration as a resources
---[Customization Tool]---
Abillity to add platform configuration
Fixeed unpacking level3(logo) when only selected level2
---------------------------->> v5.0.9 <<----------------------------
Fixed startup issue
---------------------------->> v5.0.8 <<----------------------------
Updated context decompiler
---[Customization Tool]---
-Adjustments to logging
-Repaired recovery porting feature
-Fixed kernel replacement issue
-Fixed recovery replacement issue
---[Unpacker Class]---
-Dynamic link libraries are reset on start
-Resolved kernel output directory issue
---[Recovery Converter Module]---
-Preserves file context from previously converted recovery
---------------------------->> v5.0.0 <<----------------------------
Added bootloader console tool
Added Amlogic USB Api
Added AMLogger(My Amlogic tool logging class)
Added AMLUnpacker V2
Added RecoveryConverterModule
Updated CoolADB client
Tools now run COMPLETELY native
The source code is no longer released to the public
Included EOLUtil(my utillity to convert EOL chars between formats)
---[AMLogic Flash Tool]---
-Fixed ADB connectivity issues
-Fixed recovery porting issues
-Updated recovery converter
-Added recovery porting for S905W devices
---[Unpacker Class]---
-Splitting is now done with official binary
-Now includes kernel unpacking/repacking
-Now includes converting file_contexts
-Much quicker in operation
-Quicker method of checking CRC checksums
-Added abillity to split/append the DTB partition
-Added abillity to convert dtb files to and from text
---[Customization Tool]---
-Fixed clearing tmp folder crash
-Updated recovery converter
-Removed the need for JRE
-Fixed issues of unpacking kernel on some computers
-Cleaned up keernel unpacking/repacking
-Added background support for Tanix3
-Added background support for H96 Pro H3
-Fixed replacing recovery/kernel bug(not valid ramdisk)
-Fixed Saving/exporting/loading level 1 unpacks
-Support added for 5.x.x - 7.x.x
-Fixed system length(file size) issue
-Removed add init.d support(problematic for some Android versions)
-Removed port recovery from only this tool, flash tool still has it
-Fixed permissions issue
-Internal checks for successful kernel unpacking/packing added
-Internal checks for successful recovery unpacking/packing added
-Internal checks for successful system unpacking/packing added
-Internal checks for successful dtb unpacking/packing added
-Option to edit remote.conf
-Added support for unpacking meson1.dtb
-Added DTB tab
-Added DTB editor
-Auto DTB line conversion
-DTB editor with search capabillities
-DTB editor with Obsidian theme/syntax highlighting
-Tool now searched for suppoted preinstall directories
-Fixed replace recovery/kernel issue
-Fixed "No changes applied" issue with system
-Full windows 7 support now added
-Added oem partition unpacking support
-Added vendor partition unpacking support
-Updated way of repacking to zip file
-Fixed wallpaper apk still in use
-Added partial packing for upgrade package
-Added partial packing for upgrade zips
-Stronger compression method(avg pack time 1-3 - 4min, 5-7 - 10min, 8-9 - 20min+)
---------------------------->> v4.0.0 <<----------------------------
---[AMLogic Flash Tool]---
Fixed connection errors
Fixed the out of index bug
Adb now included
Custom CoolADB client added
---[Customization Tool]---
Added detection of bootvideo
Added abillity to repack to upgrade package
Added abillity to choose unpack level
Fixed error of not finding launcher
Added abillity to change bootvideo
Added abillity to enable bootvideo
Fixed FC/Error of unpacking
True permissios detected from file_contexts
---[Unpacker Class]---
Now generates image.cfg
Optimizations added to unpacking
Second method of unpacking being implemented
---------------------------->> v3.5.6 <<----------------------------
---[Customization Tool]---
Fixed flash bug preventing rom from being flashed
---------------------------->> v3.1.5 <<----------------------------
Added UpgradePackageInfo tool
Contributions added by Akwhite(jasonnimwegen)
---[AMLogic Flash Tool]---
Fixed connection force close tool bug
Fixed block backup typo
Tool now operates while disconnected
Some functions are now blocked if not connected
Added connection status bar
Fixed shows connected while not connected bug
Added abillity to allow flashing custom block paths
---[Customization Tool]---
Added wallpaper changing for other AML devices with different launchers
Fixed displaying of current file open
---[UpgradePackageInfo]---
Added abillity to show partition layout
Checks Upgrade package size compared to hex size
Abillity to see file sizes
Abillity to show file type
Abillity to show file names
Abillity to show start hex address
Abillity to show end hex address
Shows file count
Shows partition count
---------------------------->> v3.1.0 <<----------------------------
Added AMLogic flash tool
---[Unpacker Class]---
Removed support for commandline unpacking[EXE]
Perfected unpacking of all firmware
Completely unpacked via recognised hex algorithm
Completely generated head via hex algorithm
Option to list upgrade content added
Option to get partition information added
Option to unpack single partition added
Corrected logo unpacking
Extended to support unpacking of kernels/recoveries
Option to split Upgrade Package head(Input package, Output file)
Option to generate partition info(Input package, output txt)
---[Customization Tool]---
Updated TWRP recovery resources to 3.2.1-0
Removed inbuilt unpacking class
Removed inbuild kernel unpacking class
Tool now uses Unpacker Class
Tool now uses Kernel Unpacker class
Fixed SHA1 checking
Added Importing/Exporting project
Drag and drop on icon functionallity
Fixed bug copying update-binary
---[Burn Card Maker]---
Updated icon
---[AMLogic Flash Tool]---
Updated icon
Based on original AMLogic flash tool
Updated recovery resources
Fixes with connectivity
Added option to flash flash kernel or recovery zip(experimental)
Added option to port from upgrade package
Added option to port from recovery.img
Added option to pull recovery from device
Operations are handled on seperate thread
Includes Unpacker Class
Option added to backup kernel/recovery
Option to flash after porting
Rebased UI
Based on .net 4.5 to allow windows 7 compatibillity
Includes CoolADB Class library(also made by me)
---------------------------->> v3.0.2 <<----------------------------
---[Unpacker Class]---
Faster unpacking
SHA1sum verification added(VERIFY file, PARTITION file)
Abillity to unpack VERIFY files(SHA1 sum)
Near perfection of unpacking
---[Customization Tool]---
Fixed not including recovery or kernel while packing
Fixed file context error
Partition verification added
---------------------------->> v3.0.0 <<----------------------------
---[Unpacker Class]---
Used source from my old AML unpacker
Improved functionality and stability
Unpacked by algorithm rather than assuming struction
---[Customization Tool]---
Removed obsolete functions
Better tool management
More information displayed
Fixed changing bootanimation
Fixed bootanimation orientation
Added bootanimation dimensions + FPS are now shown
Fixed displaying wallpaper
Fixed ability to change wallpaper
Fixed ability to display bootlogo
Apps tab now literally shows all apps.
Added kernel/recovery tab
Shortcuts to open certain kernel files added
Shortcuts to open certain recovery files added
Ability to convert recovery to TWRP recovery
Option to open Generic.kl(keymap) file
Ability to add init.d support(system hook)
Abillity to compile into TWRP flashable zip
Added option to choose wipe /data
Added options to choose what files to write
Faster EXT4 decompression
Faster way of splitting update package
---[Burn Card Maker]---
Formatting happens in the background(no P/Invoke)
Formatting done on seperate thread
Quicker extraction of aml_sdc_burn.UBOOT
Faster file processing
XDA:DevDB Information
AMlogic tools, Tool/Utility for the Android Stick & Console Computers
Contributors
Ricky Divjakovski
Version Information
Status: Stable
Created 2018-05-07
Last Updated 2020-09-26

Waw thnnnnnnks

algdu83 said:
Waw thnnnnnnks
Click to expand...
Click to collapse
Ive basically got the Customization Tool finished,will be uploaded in a few hours with fixed functions
Current changelog(V3.0.0)
-playing/changing bootanimation, changing wallpaper, unpacking(Level 1, Level 2 and Level 3 - used for storing raw bootanimation, wallpaper and logo),
-fixed splitting logo.PARTITION
-Bootanimation playback now shows dimensions + FPS,
-More info is shown in the info tab
-unpacking is significately faster
-added pack to flashable .zip
I still havent decided
-if im gonna allow the tool to repack to an AMLogic upgrade package
-if im going to implement the option to convery the recovery.img to a TWRP ported recovery.img

Thnks for your work
possible to add the option for convert rom img to zip

algdu83 said:
Thnks for your work
possible to add the option for convert rom img to zip
Click to expand...
Click to collapse
Yes that is implemented already, just adding the repack kernel and recovery and the advanced tab and done

Super cool thnks

Customization Tool going up

Thread updated, CustomizationTool has been uploaded

And source code is available

Me again!!! Glad to subscribe to your second thread mate!
I dunno if I am happier about actually using the Poison ROM...... Or in fact, these tools here that let me get rid of amlogics cheap nasty undeveloped Asian $h!t ! ....I honestly don't know how THEY flash millions of units efficiently using their tool, i have always thought they must have there own tool at HQ or flash direct to chip before making there boxes!?
Anyways.... I no longer worry about that now! as I no longer dread plugging my amlogics into my PC anymore! (Usually a nervous time for ANYONE dealing with this software!) Thanks to this project!
I have been purely playing around now for last few hours since release..... My Verdict???
Sorry Ricky mate.... It ain't good...
Its f*%king GREAT!!!! WOW!!
I have been patiently waiting on the ROMS progress and thinking that's what I want!..."Hurry up with that bloody PC tool!" BUT... In fact, this has made me a lot happier! And I realise exactly how much this will shape the future for all amlogic users and how important this is to poison ROMs future!
This has twice the features I ever expected! I have realised how much work has gone into this project! I can only imagine! So when I get paid I will post a small donation for all this you give us, thank you!
*if only another 2 or 3 people would follow suit then Ricky can get another s912 unit sorted and help this guy develop the ROM we all enjoy* OH! AND actually let the poor guy use his own ROM!! Lol!
As I said on my first post on the other thread... I am a junior developer that discovered you and your work through googling ROM features I wanted/had planned to make, so I just wanted you to know that I hope to be the first ROM released using this software! (I have some great ideas!) (I'll have to PM the details over!)
And finally if there is ANYTHING I can do to help you or your projects move forward towards greatness...PLEASE let me know! Happy to test for you whilst you get the TV box sorted, I'm sure whiteteaks hands must be pretty full too!
THANK YOU!!!
P.S Im about to delete all amlogic programmes off of my PC!

ErbDroid said:
Me again!!! Glad to subscribe to your second thread mate!
I dunno if I am happier about actually using the Poison ROM...... Or in fact, these tools here that let me get rid of amlogics cheap nasty undeveloped Asian $h!t ! ....I honestly don't know how THEY flash millions of units efficiently using their tool, i have always thought they must have there own tool at HQ or flash direct to chip before making there boxes!?
Anyways.... I no longer worry about that now! as I no longer dread plugging my amlogics into my PC anymore! (Usually a nervous time for ANYONE dealing with this software!) Thanks to this project!
I have been purely playing around now for last few hours since release..... My Verdict???
Sorry Ricky mate.... It ain't good...
Its f*%king GREAT!!!! WOW!!
I have been patiently waiting on the ROMS progress and thinking that's what I want!..."Hurry up with that bloody PC tool!" BUT... In fact, this has made me a lot happier! And I realise exactly how much this will shape the future for all amlogic users and how important this is to poison ROMs future!
This has twice the features I ever expected! I have realised how much work has gone into this project! I can only imagine! So when I get paid I will post a small donation for all this you give us, thank you!
*if only another 2 or 3 people would follow suit then Ricky can get another s912 unit sorted and help this guy develop the ROM we all enjoy* OH! AND actually let the poor guy use his own ROM!! Lol!
As I said on my first post on the other thread... I am a junior developer that discovered you and your work through googling ROM features I wanted/had planned to make, so I just wanted you to know that I hope to be the first ROM released using this software! (I have some great ideas!) (I'll have to PM the details over!)
And finally if there is ANYTHING I can do to help you or your projects move forward towards greatness...PLEASE let me know! Happy to test for you whilst you get the TV box sorted, I'm sure whiteteaks hands must be pretty full too!
THANK YOU!!!
P.S Im about to delete all amlogic programmes off of my PC!
Click to expand...
Click to collapse
Happy to hear the great feedback, this is a big learning curve for me aswell, prior to this i had no idea on assuming programatically generated algorithms, programatically copying byte by byte from hex address to hex address..
but all i can say is what a turn out!
My next mission is to create USB Burning tool with a much better/safer way of flashing, and unlike AMLogics USB burning tool, you will be able to select what partitions to flash
But first i wanna release PoisonRom V3.0 as im more then likely going to brick my device(possibly to an unrecoverable state)..
But this will be a stepping stone towards innovating AMLogic devices
EDIT: as i still dont have a working TV, i havent tested the flashing process of the compiled ROM, so if you could, within custom recovery just flash the ROM(ofcoarse taking a backup prior) and let me know the result, also prior to compiling into a flashable zip, try the change wallpaper option and see if everything goes sweet

EDIT: everything works..

Ricky Divjakovski said:
Happy to hear the great feedback, this is a big learning curve for me aswell, prior to this i had no idea on assuming programatically generated algorithms, programatically copying byte by byte from hex address to hex address..
but all i can say is what a turn out!
My next mission is to create USB Burning tool with a much better/safer way of flashing, and unlike AMLogics USB burning tool, you will be able to select what partitions to flash
But first i wanna release PoisonRom V3.0 as im more then likely going to brick my device(possibly to an unrecoverable state)..
But this will be a stepping stone towards innovating AMLogic devices
EDIT: as i still dont have a working TV, i havent tested the flashing process of the compiled ROM, so if you could, within custom recovery just flash the ROM(ofcoarse taking a backup prior) and let me know the result, also prior to compiling into a flashable zip, try the change wallpaper option and see if everything goes sweet
Click to expand...
Click to collapse
Hello again Ricky,
Sorry for the seemingly late reply, timezones! UK to OZ!!!
Well done!
No problem at all mate, I'm all backed up as per usual and ready to test V3 using your tools whenever your ROM is ready!!
Before it rolls out i could record the flash process so you can see it!! And I'll log it too and send over.
Now... First flash, to test it, you reckon I should flash stock firmware for my device quickly as it came with (previously) incompatible build?:
* 2GB/16GB-7.1.2 * ?
If not I can try with newer stock firmware, the newer build is actually version 7.1.1 for the device I have in mind (AlfaWise H96 Pro dongle) that is how I got on PoisonRom.
Oh! And congrats on Aroma!! Yeahhhhbuddyyyy!

ErbDroid said:
Hello again Ricky,
Sorry for the seemingly late reply, timezones! UK to OZ!!!
Well done!
No problem at all mate, I'm all backed up as per usual and ready to test V3 using your tools whenever your ROM is ready!!
Before it rolls out i could record the flash process so you can see it!! And I'll log it too and send over.
Now... First flash, to test it, you reckon I should flash stock firmware for my device quickly as it came with (previously) incompatible build?:
* 2GB/16GB-7.1.2 * ?
If not I can try with newer stock firmware, the newer build is actually version 7.1.1 for the device I have in mind (AlfaWise H96 Pro dongle) that is how I got on PoisonRom.
Oh! And congrats on Aroma!! Yeahhhhbuddyyyy!
Click to expand...
Click to collapse
if your changing android version(eg. going from android 7.1.1 to 7.1.2) you must flash stock firmware with USB Burning tool or sd boot card maker, until i can find a way to bypass AMLogics ****ty security implemention(still unsure if bootloader or UBOOT or DTB)
I tested the flash option last night at my sisters house, seems like im getting the gist of this blind coding lol
it worked flawlessly
So in theory its as simple as using my customization tool to make your own custom ROM from stock firmware
Id still like to improve EXT4 FS handling a little better, i seen a good bunch of opensource tools for handling EXT4 FS in C#, only problem may be is that it has no documentation on if it supports compressed FS

not possibility to open zip rom?
i dont find it

algdu83 said:
not possibility to open zip rom?
i dont find it
Click to expand...
Click to collapse
will add it next update

Ricky Divjakovski said:
will add it next update
Click to expand...
Click to collapse
Thnkssss

Seems like my tools do it better, ill be updating CustomizationTool soon with big changes to the unpacker + the feature to verify if sha1 sums are correct on unpack
As you can see, my generates wayyyyy more files then standard customization tool
Im also gonna add re-pack to USB burn image and unpack update.zip(packed for recovery)

Updating in within the next hour
Changes
-Customization tool performs partition verification checks on unpack
-Much faster and unpacking in customization tool
-Optimized code for customization tool
-Added new opensource tool - AMLUnpacker(executable and C# class)
Im not adding the abillity to repack as im unable to see how the first 4 bytes of the file generate the .img files CRC32 hash

thanks good job for this tool :good:
zip please

Related

[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

[TOOL/UTILITY][TWRP][3.3][RECOVERY] TWRP 3.3.1-0 TeamWin Recovery Project 5/22
[RECOVERY] [5/22/19] TWRP 3.3.1-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.3.1-0 for the Samsung Galaxy Note 2 (International)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
t03g Device Config: https://github.com/TeamWin/android_device_samsung_t03g
Kernel: https://github.com/bigbiff/android_kernel_samsung_smdk4412
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
Please see https://twrp.me for changelog details.
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.
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
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
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)
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.
2.8.6.0
- Allow mulitple overlays for popup boxes (Dees_Troy)
- Add pattern style password entry for decrypt (Tassadar)
- Keyboard improvements (_that)
- Update AOSP base to 5.1 (Dees_Troy)
- Reduce theme count to 5 and rely on scaling (Dees_Troy)
- Various scaling improvements (Dees_Troy)
- Improved handling of resources in the GUI (_that)
- Make scroll bar size proportional to list size (_that)
- Allow scoll lists to render without a header (_that)
- Make console scroll per pixel with kinetic scrolling (_that)
- Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
- Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.3.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- 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
2.8.1.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.1
t03g
fix contexts, external storage backing up
t0lte
fix assert
Please note the file name is now t0ltetwrp for now.
2.8.0.0
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
2.7.2.1
t0lte
- fix exfat
2.7.2.0
All thanks to @Dees_Troy
- fix crash in setting contexts on datamedia
- fix restoring data partition as f2fs after formatting f2fs
- mount data after being formatted
2.7.2.0
All thanks to @Dees_Troy
- fix crash in setting contexts on datamedia
- fix restoring data partition as f2fs after formatting f2fs
- mount data after being formatted
2.7.1.0
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
2.7.0.2
t0lte and t03g
fix OTG
2.7.0.1
t0lte
fix external_sd backup
fix splitting system
2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
2.6.3.2
Add f2fs support
Fix data wiping crash when formatting data
Other surprise stuff that will be in twrp 2.7
2.6.3.1
Update t03g to 2.6.3.1 to support SELINUX kernel and setting contexts properly
Working on t0lte as well.
2.6.3.0
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
Change to GPL exfat kernel module to work around exfat-fuse bugs
2.6.1.0
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
2.6.0.1
Fix Data being listed twice in advanced wipe
2.6.0.0
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
2.5.0.2
Rename device to t03g from n7100 at goo.im, techerrata.com and build scripts. This is to support ROMs using the t03g product name which is the correct name to use.
2.5.0.1
Fixed encryption
2.5.0.0
Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
Fixed a problem with directory permissions on split archive backups
Fixed a problem with md5 verification of backups
Added a search function to libtar (thanks to kokotas)
Improve handling of XML errors (fix permissions)
Fixed handling of subpartitions
Improvements to recovery.fstab flags
Fixed a problem with decryption not being able to locate the decryption key in some situations
2.4.4.0
Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
More fixes for the file selector
Switched from using busybox md5sum to a direct C function call
Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
Update exFAT to latest commits
Added a build flag to disable using the ioctl for screen blanking
2.4.3.0
Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
Added a scroll bar to file selectors and listboxes courtesy of Tassadar
Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
Added a screen dim effect 2 seconds before screen off on some devices
Finally fixed file selector crash (one of the joys of working with multi-threaded software)
Fixed loading of screen timeout setting during startup
Improvements and bugfixes to screen timeout code
Fix Military Time setting persisting
2.4.2.0
Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
Add a brightness setting (requires device specific setup and only some devices have been added)
Add a root checker and offer to install SuperSU if the device isn't already rooted
Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
Check and offer to fix root permissions if broken
Add an option for a 24 hour clock display instead of AM/PM (aka military time)
Move stock recovery reflash check to occur during the reboot cycle
Add support for some MTK6xxx devices
Change libtar to vfork to help prevent memory problems
Add a "clicked" effect to most buttons, file selector, and listbox
Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
Other minor bugfixes and improvements
2.4.1.0
Fix detection of exfat and vfat
Fix formatting vfat past 2GB
2.4.0.1
Revert to using kernel modules for exFAT for performance
2.3.3.2
Uploaded with the following debrick fix courtesy of AndreiLux: https://github.com/AndreiLux/Perseus-S3/commit/54ddcbe7aff1c19c07f76a05ab45f37bcbae2951
2.3.3.1
Updated Kernel due to this recommendation from AndreiLux: http://forum.xda-developers.com/showthread.php?t=2057364
2.3.3.0
Increased Brightness
Added better handling of wiping on /data/media devices with Android 4.2 to help prevent multiple upgrades of the file system for multiple users
NOTE: It is not recommended to jump back and forth between 4.1 and 4.2 ROMs. If you do, this may trigger additional upgrades and you will have to manually move your files back to the "single user" layout when going back to 4.1.
Fixed renaming of backups when a space is present
Added decrypt button to mount page if you cancel decryption during boot
Added ignore blkid flag support
Fixed handling of MTD partitions during mount
Fixed some keyboard mapping issues on 800x1280 layout
2.3.2.3
Added ability to backup modem
Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see http://teamw.in/androidmultiuser)
Fixed a bug with deleting a backup with a space in the name
Added highlights on keyboard key presses
Updates to Fix Permissions
2.3.1.3
Added external SDCARD exfat mounting
2.3.1.2
Added large font
Added code to speed up boot thanks to AndreiLux
2.3.1.1
Fixed keyboard segfault
Handle single LUN file for USB Storage
Handle mounting of slow sdcards
Update USB Mount Code to be more Efficient
FAQ
Q. Are there any themes I can use?
pctv007 has ported some themes for the Note2: http://www.mediafire.com/?34sulxbjxzb34
Q. Can I use Goo Manager to install TWRP if I am not rooted?
A. No, you will not have permissions to access the recovery paritition without a rooted system installed. This gives you the ability to have su installed as SUID root and with Superuser or SuperSu, you can give Android applications root access to use su to access the system as the root user.
Q. Where is the "Delete battery stats opton?"
A. We removed this option in 2.1. Please see https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT as reference.
Q. What happens if I wipe /data?
Good description also here: http://teamw.in/DataMedia
The Galaxy Note 2 is using the fuse filesystem to pretend /data/media is its own filesystem to external computers when you plug the phone into the computer. /data is one partition formatted as ext4. There is a subdirectory for media under /data which is presented as its own block device using fuse. Then mtp responder uses this directory to present the directory to a host computer when plugging in via USB.
Never allow your computer to format this directory in case there is a problem with mtp responder. Also NEVER wipe data under the Wipe menu unless absolutely necessary. This will remove all your files in /data/media.
On the original note, internal SDCARD was a separate file system formatted with the fat32 filesystem but exported directly through UMS.
First !
Envoyé depuis mon GT-N7100 avec Tapatalk
I flash it through CWM Recovery, reboot, but Recovery still the same, what's wrong?
Great! Now we aren't stuck with cwm anymore!
Thanks!
Edit. Btw, does backup and restore work now?
Sent from my GT-N7100 using Tapatalk 2
""No recoveries were found for your device" - say me GooManager...
xaoc747 said:
I flash it through CWM Recovery, reboot, but Recovery still the same, what's wrong?
Click to expand...
Click to collapse
I get the same result, also tried the odin method > mobile odin complains that the image is missing. I try PC odin and it blows up when it goes to flash.
Go to the TWRP web site, choose the GT-N7100. Download the Odin flashable .tar file and flash via Mobile Odin.
For themes the HTC Evo themes are the same size 720x1280, but make sure they 2.3 compatible as 2.2 themes dont have some of the options available in 2.3.
Sent from my GT-N7100 using XDA Premium HD app
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
kest874 said:
I get the same result, also tried the odin method > mobile odin complains that the image is missing. I try PC odin and it blows up when it goes to flash.
Click to expand...
Click to collapse
Change the file name to recovery.tar or use the .img file and name it just recovery.img, Mobile Odin will flash then.
Sent from my GT-N7100 using XDA Premium HD app
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
Reb0rn said:
Great! Now we aren't stuck with cwm anymore!
Thanks!
Edit. Btw, does backup and restore work now?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Backups work 100%, just never tested the restore.
Sent from my GT-N7100 using XDA Premium HD app
Backups and restore work fine for me.
Sent from my GT-N7100 using Tapatalk 2
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
xaoc747 said:
I flash it through CWM Recovery, reboot, but Recovery still the same, what's wrong?
Click to expand...
Click to collapse
kest874 said:
I get the same result, also tried the odin method > mobile odin complains that the image is missing. I try PC odin and it blows up when it goes to flash.
Click to expand...
Click to collapse
Download the image (.img) file here:
http://goo.im/devs/OpenRecovery/n7100/openrecovery-twrp-2.3.1.0-n7100.img
Rename it to recovery.img then you'll be able to flash through mobile odin.
Sent from my GT-N7100 using Tapatalk 2
CRudner said:
Change the file name to recovery.tar or use the .img file and name it just recovery.img, Mobile Odin will flash then.
Click to expand...
Click to collapse
Partition could not be found on file - say me Mobile Odin!
recovery.img flashed through mobile odin and I have touch recovery!!! great!!!
Sorry guys I need to fix the zip. Don't use it for now.
Also make sure you guys backup all your partitions just in case.
Luckily the zip is harmless and non damaging. I still recommend using dd to backup your phone but otherwise your fine if you flashed the zip.
Thanks alot!
Strange, TWRP wont mount my external sd
So does this mean that the Note 2 actually uses the recovery partition, instead of using an initramfs image in the kernel?
bigbiff said:
Sorry guys I need to fix the zip. Don't use it for now.
Also make sure you guys backup all your partitions just in case.
Luckily the zip is harmless and non damaging. I still recommend using dd to backup your phone but otherwise your fine if you flashed the zip.
Click to expand...
Click to collapse
When will be ready?
mprziv said:
Strange, TWRP wont mount my external sd
Click to expand...
Click to collapse
If you could provide me /tmp/recovery.log I can take a look.
bigbiff said:
Sorry guys I need to fix the zip. Don't use it for now.
Also make sure you guys backup all your partitions just in case.
Luckily the zip is harmless and non damaging. I still recommend using dd to backup your phone but otherwise your fine if you flashed the zip.
Click to expand...
Click to collapse
Flashed it just now.
Works fine 4 me.
What should I be affraid of?
Set backup name, click on the virtual keyboard the program crashes.
Chenglu said:
Set backup name, click on the virtual keyboard the program crashes.
Click to expand...
Click to collapse
I can confirm this issue.
@bigbiff I have attached a link to my log, hopefully it recorded it as it restarts TWRP.http://dl.dropbox.com/u/24188397/recovery.zip
Sent from my GT-N7100 using XDA Premium HD app

[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Samsung Galaxy Note 3 (Sprint)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
hltespr Device Config: https://github.com/TeamWin/android_device_samsung_hltespr
Kernel: https://github.com/bigbiff/android_kernel_samsung_smn900p
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
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.
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
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
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)
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.
2.8.6.1
- Fix writing backups to external sdcard
2.8.6.0
- Allow mulitple overlays for popup boxes (Dees_Troy)
- Add pattern style password entry for decrypt (Tassadar)
- Keyboard improvements (_that)
- Update AOSP base to 5.1 (Dees_Troy)
- Reduce theme count to 5 and rely on scaling (Dees_Troy)
- Various scaling improvements (Dees_Troy)
- Improved handling of resources in the GUI (_that)
- Make scroll bar size proportional to list size (_that)
- Allow scoll lists to render without a header (_that)
- Make console scroll per pixel with kinetic scrolling (_that)
- Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
- Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.3.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- 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
2.8.1.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.0
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
2.7.1.0
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
2.7.0.1
Fix splitting system and free space calculation
2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
2.6.3.8-4.3-BL
4.3 Bootloader Only
Fix time
2.6.3.7
Fix EFS Backup and Restore
2.6.3.6
Fix USB Storage flags again by adding storage flag
2.6.3.5
Fix USB Storage flags
2.6.3.4
Fix storing SELINUX contexts in backups and restoring them properly
Add fix /data/data SELINUX contexts in Fix Permissions (under Advanced) for applications restoring data without setting contexts correctly
Add EXFAT to kernel
FAQ
How do I fix bootloops?
This has worked for me multiple times to restore from bootloops:
1. Load Odin
2. Download FW for the phone from Sammobile
3. Extract files using 7zip
4. Open Odin
5. Deselect Reboot and Reset Time in Odin
6. Flash the following images one at a time: cache.img, boot.img, system.img
7. Pull the battery and replace
8. Hold home, volume up and then power to boot stock recovery
9. Update.zip will flash
10. Pull the battery and replace
11. Hold home, volume up and then power to boot stock recovery
12. Factory Reset
13. Boot into android and hopefully everything is fixed
Data will be still untouched. Also you have blown the knox fuse and get more knox notifications about applications accessing system.
Very NICE!!
Sent from my SM-N900P using XDA Premium 4 mobile app
---------- Post added at 08:36 PM ---------- Previous post was at 08:26 PM ----------
If choosing to flash in odin, is it the Img.tar file? Do we check the PDA box in odin?
Sent from my SM-N900P using XDA Premium 4 mobile app
Has this been tested to have successful backup Restores? I remember reading something about the SE LINUX needing to be worked out or something to that effect. I'm using twerp 2.6 .3 on the note 2 and everything is Great
Goo manager tells me no recovery found for my device...
Sent from my SM-N900P using XDA Premium 4 mobile app
mrcrptguy said:
Goo manager tells me no recovery found for my device...
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same here
Yeah, goo manager a no go. Has anyone flashed this with success?
The Lawngenie said:
Yeah, goo manager a no go. Has anyone flashed this with success?
Click to expand...
Click to collapse
You have to install via Odin for now. I'm waiting until everything is settled before adding to goo manager.
asacado said:
Has this been tested to have successful backup Restores? I remember reading something about the SE LINUX needing to be worked out or something to that effect. I'm using twerp 2.6 .3 on the note 2 and everything is Great
Click to expand...
Click to collapse
We can restore selinux contexts thanks to Tassadar.
bigbiff said:
We can restore selinux contexts thanks to Tassadar.
Click to expand...
Click to collapse
I quite literally got this phone yesterday so I'm not used to the development phase
bigbiff said:
You have to install via Odin for now. I'm waiting until everything is settled before adding to goo manager.
Click to expand...
Click to collapse
I tried via odin but it didnt see file witj pda checked...do i extract recovery.img? Can u explain?
asacado said:
I quite literally got this phone yesterday so I'm not used to the development phase
Click to expand...
Click to collapse
It's kind of like Christmas. All developers and testers get in a huge circle and bang heads together to come up with wonderful presents. Analogy of course lol but this will probably get real interesting real fast. Me as a noon figured out boot animations already but that's a small feat to building a recovery or room lol
---------- Post added at 03:11 AM ---------- Previous post was at 03:10 AM ----------
The Lawngenie said:
I tried via odin but it didnt see file witj pda checked...do i extract recovery.img? Can u explain?
Click to expand...
Click to collapse
U have the tar file. Choose pad and select the tar. Make sure to have the drivers installed and be rooted.
Can we use mobile Odin to flash?
Edit: never mind, device is not supported yet.
Sent from my SM-N900P using XDA Premium 4
Naddict said:
I have made a zip flashable, just to test only as I do not yet have the device.
http://d-h.st/s5z
Not meant to thread hijack, but someone please let me know if it works, if not, the goo manager method certainly will.
Thanks all, and thanks for the latest Note 3 Build to Team Win!
Click to expand...
Click to collapse
I tried the zip and it did not work.
Sent from my SM-N900P using XDA Premium 4 mobile app
smark72 said:
I tried the zip and it did not work.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just use ODIN.. 10 seconds.. Done. But dont use ODIN with the zip he provided. Go to TWRP website.
tandxcstar1 said:
Just use ODIN.. 10 seconds.. Done. But dont use ODIN with the zip he provided. Go to TWRP website.
Click to expand...
Click to collapse
I am just currently without a pc til tomorrow. Thought I might be able to get it done another way.
Sent from my SM-N900P using XDA Premium 4 mobile app
smark72 said:
I am just currently without a pc til tomorrow. Thought I might be able to get it done another way.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am sorry I dont know of any other way.. Maybe re-try downloading zip file he provided and try again.
---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------
The Lawngenie said:
I tried via odin but it didnt see file witj pda checked...do i extract recovery.img? Can u explain?
Click to expand...
Click to collapse
What version of ODIN did you use? I used ver 3.04. I think the previous version 1.85 I couldnt find it. Let me know what version your running. Also no I didnt have to extract IMG file. Just found zip with ODIN ver 3.04 and selected PDA slot. I am sure its safe to extract and use on older version of ODIN.
tandxcstar1 said:
I am sorry I dont know of any other way.. Maybe re-try downloading zip file he provided and try again.
---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------
What version of ODIN did you use? I used ver 3.04. I think the previous version 1.85 I couldnt find it. Let me know what version your running. Also no I didnt have to extract IMG file. Just found zip with ODIN ver 3.04 and selected PDA slot. I am sure its safe to extract and use on older version of ODIN.
Click to expand...
Click to collapse
I figured it out, thanks for all the help
Just flash with Odin 3.07 running a first backup now.
Thank you all for your hard work.
~Bizack
edit: Did a full backup on a extreme 32gb sd card it 4.29gb in 410 sec @ 29mb a sec... Damn this phone flies...

[RECOVERY][ms013g] TWRP 3.0.0 Touch recovery[with EFS/Modem backup][F2FS support]

Team Win Recovery Project 3.0.0.x​
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.
Phone look:
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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.
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.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
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.
DOWNLOAD:
ON post #3
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
Team Work Recovery Project, Tool/Utility for the Samsung Galaxy Grand 2
Contributors
aapav01
Version Information
Status: Stable
Current Stable Version: 3.0.0
Stable Release Date: 2016-02-05
Created 2015-05-13
Last Updated 2016-02-07
Change LOG & Difference
Main Difference From Other TWRP recovery available for ms013g
Changes of 7 feb 2016
Updated to 3.0.0
Changes of 21 September 2015
Updated to 2.8.7.0
Added F2FS support
Changes of 13th May 2015
Updated to 2.8.6.0
MTP support
ADB sideload fixed
EFS backup
Modem backup
DOWNLOADS
Method 1:
Odinmod edit - links removed
1) Install whatever drivers make you happy and make your device connect (i would suggest samsung ones).
2) Reboot your device in download mode you can use adb reboot download or the hardware key combo for your device.
3) Load up Odin and uncheck auto-reboot.
4) Click PDA and select the TWRP tar you downloaded.
5) Connect your device in download mode.
6) Click start.
7) When its finished disconnect your device, pull the battery out.
8) Reinsert the battery and use the hardware keys for your device to power directly into recovery mode (this will bypass install-recovery.sh if you are stock).
9) Enjoy having a custom recovery.
Method 2: IF you are already on anyother recovery
1)Reboot your device in recovery mode you can use adb reboot recovery or the hardware key combo for your device.
2)Now just flash the flashable zip from sdcard or extsdcard you have downloaded
3)Now REboot into recovery and Enjoy ur new TWRP recovery
Downloads
TWRP 3.0.0
mod edit - links removed
TWRP 2.8.7.0 (OLD VERSION)
mod edit - links removed
TWRP 2.8.6.0 (OLD VERSION)
ODIN (Tar file)- mod edit - links removed
Recovery flashable zip -mod edit - links removed
Recovery image - mod edit - links removed
Good work
You are good mr @aapav01 , thz for your hard work!! Your are my best developer!! And waiting your new rom!! I'm a big fan of you!!��������������
But why i can't download your recovery flashable zip(everytime i click on download now it just reload page not download), i can only download only recovery image?
G.NO_BOYz said:
You are good mr @aapav01 , thz for your hard work!! Your are my best developer!! And waiting your new rom!! I'm a big fan of you!!��������������
But why i can't download your recovery flashable zip(everytime i click on download now it just reload page not download), i can only download only recovery image?
Click to expand...
Click to collapse
mod edit - links removed
it working.. try to open in a new tab
aapav01 said:
twrp_2860.zip - 8.72 MB
it working.. try to open in a new tab
Click to expand...
Click to collapse
Thz alot now it working!!
thanks aapav for the new recovery
it works flawlessly
best dev!!
thanks alot:good::good::good::good:
@aapav01 Can I install the themes from this thread? forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
5 Golden Stars for this smart project.
Regards ?
rv5750 said:
@aapav01 Can I install the themes from this thread? forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
Yeah it should Work
aapav01 said:
Yeah it should Work
Click to expand...
Click to collapse
it work, i already tried it and it look very cool!!!
installation on cyanogen 12.1
Hey aapav I'm currently using cyanogen 12.1 that is android 5.1.1 And i have cwm recovery installed. Can i install this recovery through cwm if i'm on cyanogen? Or this is only flashable on kitkat?
pradhyumn1998 said:
Hey aapav I'm currently using cyanogen 12.1 that is android 5.1.1 And i have cwm recovery installed. Can i install this recovery through cwm if i'm on cyanogen? Or this is only flashable on kitkat?
Click to expand...
Click to collapse
yes, u can i already do this!!
hit thank if i helped!!
does not work in mine dunnoe y
i am on kitkat 4.4.2 .....was using a custom rom s6styled s5 port by singhking83 .....when i tried installing v3...it stuck on the boot logo of samsung......but then i installed cwm.,..then the rom was installed successfully.....what must be the problem? i relly like the interface of twrp.....
Why does the title say "kitkat only" ? Does that mean I can't use this recovery to flash CM 12.1 ?
Oscuras said:
Why does the title say "kitkat only" ? Does that mean I can't use this recovery to flash CM 12.1 ?
Click to expand...
Click to collapse
No, u can flash it in cm 12.1 , i already did it!!
Click thank if i helped!!
thanks
thk for great rom
I recently flashed this recovery and now while flashing a theme it gives error could not load data/media/0/twrp/theme/ui.zip ...
Sent from my SM-G7102 using XDA Free mobile app
xubairsarwar said:
I recently flashed this recovery and now while flashing a theme it gives error could not load data/media/0/twrp/theme/ui.zip ...
Sent from my SM-G7102 using XDA Free mobile app
Click to expand...
Click to collapse
You don't need to flash theme, u just change (theme name.zip) to ui.zip and copy it in sd card/TWRP/theme if you can't fine theme folder you can make new folder and copy ui.zip in there. After you just go to recovery mode and done!!
Good luck guy!!
Click thank if helped!!

[TOOL] [Windows] [GUI] ClassyKitchen For Android ROMs Development

I don't take responsibility for any damage may happen to your device because of using this tool, USE AT YOUR OWN RISK​A new generation of Android ROMs development...The ClassyKitchen​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About:
A new C++ Windows application that based on ASSAYYED KITCHEN to deal with the most of android ROMs (stock images, stock updates, running device ..... etc)
In addition to built-in apktool to easily decompile & recompile apk in the PROJECT
And with a friendly user interface with full mouse control just one click.
With static build feature and a new built-in windows tools feature (hex dump) that makes the whole working environment into one exe file only.
ROM editor features:
1 - Supported ROMs type for extract:
Any stock system[lz4] & boot[lz4] [cache | odm] images
All Samsung stock firmwares (TAR[.MD5]) with support for LZ4 compress
All Google stock firmwares (ZIP)
All Lineage stock ROMs (system.new.dat[br] & vendor - payload.bin)
Any other images dumped from other stock ROMs (Huawei - HTC.....etc)
Rooted device OR custom recovery (*With technology to dump boot & system & vendor images without need a space on device*)
2 - Supported ROM edits:
Pre-remove for Samsung RMM security
DeOdex for android [4.x.x] till [9.x.x]
ZipAlign for all APKs & JARs
Heavy DeBloat ROM with Re-Bloat
Full DeKnox ROM
Clean ROM from all CSC apks (in Samsung ROMs)
Support safe and powerful Build.prop tweaks
Support change Build Number text
Support add busybox into the ROM itself with all available symlinks in image
3 - Supported ROM build:
ZIP ROM contains sparse system [vendor & odm] dat
ZIP ROM for custom recovery flashing
ZIP images ROM for fastboot flashing
TAR images ROM for Samsung devices
Support compress Samsung images with original LZ4 format
4 - Supported boot image edits:
Support all boot images partitions names other than boot.img
Remove dm-verity with AVB & ForceEncryption
Enable ADB
Patch sepolicy (supports CIL) to supported deodexed Oreo
Add / Remove Magisk Root to boot image directly in windows
Support patch boot image to run scripts during boot that placed in /system/smart_scripts
5 - Supported Apktool:
Decompile single apk
Recompile single apk
Sign single apk
Support option to specify [New | Original] apk signature
Support use custom apktool.jar selected by user
Support Decompile - Recompile multi APKs in the same time
Support Decompile - Recompile JAR files (Support multi classes files)
6 - Supported On Device Features:
Support dump full device memory using (adb root) - supported (EMMC & UFS) Without need any space on device
Support dump specified partitions from device using (adb root) - (List to user and pick needed partitions)
General Features:
Quite simple user interface
Very safe when working with images ROM for files [modes, gid, uid, contexts, capabilities]
Read the exact EXT4 [symbolic links, full permissions] and re-apply them when building
Write full permissions for [fs_config, contexts, capabilities] when building an EXT4 image or in [updater-script]
Support fix the case sensitive problems with ROMs like (Samsung S8 / S8+)
Support save project and restore it when needing
Support [Added edits log] to allow the user to see all edits he made
Support add custom text during flash in recovery
Support save the system image and [odm] image sizes to rebuild them using the exact original size
Support allow user to change the build configs (size, sparse header, images ext)
Support custom debloat list
Support more that one connected ADB device and list them to user to pick one to pull ROM from
Pro Version:
The kitchen has two versions Free & Pro
And the Pro version requiring a small donation (20$) and it needs an authenticating code to run it on a specified PC,
If anyone need to use it just download and run then send to me the output code with a transaction ID to send the activation code that match the given code.
NOTE: The Pro version is to supporting my work only, and the Free version is enough to create a full modded flashable ROM
- The following features are only available in Pro version:
All On Device Features
Pull ROM from Rooted device or custom recovery
Change Build Number text
Build TAR images ROM for Samsung devices
Build ZIP images ROM for fastboot flashing
Add Magisk Root to boot image directly in Windows
Patch boot image to run script during boot
Decompile - Recompile multi APKs in the same time
Manual DeBloat as user wants
Download link:
- Latest Free Version: http://www.mediafire.com/file/7uch95enkpc7q2p/ClassyKitchen_Free_Beta_1.0.4.7z/file
- Latest Pro Version: http://www.mediafire.com/file/l62q85rj8d8lqu0/ClassyKitchen_Pro_Beta_1.0.4.7z/file
Changelog:
- Version: 1.0.4 - BETA:
Added support to build sparse dat images
Improved some props read in OnePlus devices
Added new tab On Device Features: Support dump Full device memory without need space on device & dump selected partitions without need space too (Pro Version)
Updated flash_kernel.sh script
Updated Magisk to version 18.0
- Version: 1.0.3 - BETA: Free Version - Pro Version
Added support to Decompile - Recompile multi apks in the same time (Pro Version)
Added support to manual DeBloat (list all ROM apks to user to pick one and remove) (Pro Version)
Updated DeKnox list
Improved dump ROM from device (skip search for ODM - VENDOR partitions if the device doesn't have them)
Added support to decompile & recompile JAR files
Added support to deal with boot images that have names other than boot.img
Added support to build ODM image in fastboot build option
ReCoded all Deodex codes to support ROMs that have symlinked 64 oat files like Huawei devices
Updated Magisk Root files and Magisk sources to v18
- Version: 1.0.2 - BETA: Free Version - Pro Version
Added support to ReCompress Samsung images to LZ4 during TAR building
Updated packing original APK signature during APK compiling
Updated Magisk to 17.3 (2018-11-22)
Added SmartScripts feature to easy run scripts as Root during system boot (Pro Version)
- Version: 1.0.1 - BETA: Free Version - Pro Version
Fixed bug happened when switch from system_root to system type ROM
Added support to vendor (build zip - build images - extract)
Updated building images codes (better size printing)
Added support to (vendor.new.dat[br])
Added support to pull vendor image from Rooted devices
- Version: 1.0.0 - BETA: Free Version - Pro Version
Initial release
Reports & Request features:
To report any issue Please provide a pic for the Error happened in the Kitchen and A link for the ROM used (Without them I can not provide any help) (Posting here not via PM please).
To request any features to add or any notes about exists features just post about them on this thread (Or via PM).
Credits:
- Cygwin Project: For base tools to deal with Linux symbolic links in Windows
- 7zip: For 7z binary to deal with EXT4 filesystem
- AOPS Platform Tools: For ADB tools
- And_pda: For ImgExtractor tool
- LZ4 Project: For sources to deal with lz4 compressed images
- AOSP Sources: For all android sources (sparse converting, simg2img, aapt, zipalign, brotli, cdex_convert_sources, readelf......etc)
- Cubinator: For his EXT4 images analyzing python sources
- testwhat: For oat2dex tool
- anestisb: For vdexExtractor tool
- Linus Yang: For compact_dex_converter tool
@topjohnwu: For Magiskboot tool sources
@JesusFreke: For his Smali & Baksmali
@xpirt: For sdat2img python tool
@iuss: For payload_dumper python tool
@iBotPeaches: For apktool tool
WoW , that was mind blowing . I Just got my Pro version, and i build my first tar rom and it was flashed successfully . Thank you sir.
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
arvs47 said:
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
Click to expand...
Click to collapse
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
AndroDef said:
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
Click to expand...
Click to collapse
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
arvs47 said:
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
Click to expand...
Click to collapse
No, Porting feature is not supported now
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
dr460nf1r3 said:
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
Click to expand...
Click to collapse
Create a (txt) file and write in it all items you want to remove (Names with extensions only without paths)
Then press on Debloat and select custom debloat list and select your txt file (File browser)
At samsung ruins, it would not be possible to include vendor.img.lz4 among the unpacked and repackaged
You also have to change things to get the better rom done
Thanks in advance
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
dr460nf1r3 said:
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
Click to expand...
Click to collapse
Thanks for the prompt answer. I didnt have a clue about that. Good to know.
Any idea why my SIM and radios got screwed up. No cellphone signal, didnt even ask for the SIM pin as if it didnt see it. The wifi didnt connect the usual network. Bluetooth kept asking me many times to confirm the connection code of my WearOs watch.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
AndroDef said:
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
Click to expand...
Click to collapse
Do you mean flashing the full stock on Odin? That would make me lose TWRP. And the idea for me of using your very nice ROM creating tool was to remain official, rooted, without having to install custom recovery again.
It worked perfectly on my tablet.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Sapiens said:
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
I finished add support for vendor partition and will release the update soon.
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
vendor.new.dat missed
Sapiens said:
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
After debloat process you can navigate to (PROJECT_FILES/DEBLOAT) and delete what you want then restore the needed items by the kitchen, However I will add manual debloat feature and currently I attached the debloat list of the kitchen.
daxiaamu said:
vendor.new.dat missed
Click to expand...
Click to collapse
Send to me a link for a firmware contents that file.

Development [KERNEL] CleanSlate T 2.4.0/S 1.4.2 |AdBlock|SafetyNet|BatterySaver [Oct 28]

tbalden's
CleanSlate kernel
for Asus ZenFone 9
The User Experience Kernel leaning towards Stock Stability plus UX features.
Rock stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As always tbalden is here to bring you authentic new features first in line, this year Asus ZF9.
No root elevation (magisk) needed for all functions and preference switches through CS Config App
​
Release Calendar
Version 2.4.0 - 13 of Dec 2022
Version 1.4.2 - 28 of Oct 2022
Version 1.0.0 - 29 of Aug 2022
Should work on official ROM bases 32.2050.2050.x+.
Features:
- Flashlight Notification/Call blinking (see video below)
- Vibrating Notification Reminder (DETAILS)
- Notification In-Pocket Booster boost notifications vibrations while phone is in pocket
- Haptic Type Tweak change haptic feedback waveform types
- K.AdAway adblocking built-in kernel only, All browsers, Apps web-ads, except YouTube / streaming / Facebook ads
- SafetyNet pass passes if using without Magisk/Rooting, flashing the boot img only, Google Pay should work
- Sweep to Sleep gestures - highly customizable
- DoubleTap & LongTap on corner area gestures - new way to pull down android Notification Area or screen off
- Sweep/Tap gesture to force close foreground app - DETAILS HERE
- Battery Saver cut back max CPU freqs, 3 levels + touch boost limiter options
- Face down screen off - put phone face down to turn screen off
- Kernel Log / Crash dump to internal storage/sdcard - no root/magisk needed, from Companion App use Kernel Log button
- CleanSlate Companion / Config - rootless app to configure
Facts:
- no root required, use /sdcard/uci_user.cfg file to configure 99% of the features without rooting. If you need tweak apps (e.g. EXKM / FK) you'll need rooting!
- built on top of kernel sources released by ASUS, 5.10.x
- built with standard toolchain for stability and efficiency
- built with Control Flow Integrity sec hardening from Android S versions onwards
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Requirements
- Unlocked ZF 9, stock or with magisk root
- BACKUP: make sure you have a stock image (boot img) from asus before installing this!
Installation Guide
Firstly install CleanSlate configuration and CleanSlate companion apps on your phone (both found down below in Download section). (On play store version: with Android 12 you need to join the Beta program for the correct app versions.) Set them up initially.
- Non-rooted method: 0. download the non-rooted boot img.zip, UNZIP it first!
Reboot to bootloader, and flash the images with these commands:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
.. reboot, enjoy
- Rooted method: 0. download the rooted installer zip
1. install magisk
2. use a Kernel Flasher to flash the installer zip
- For SafetyNet, Adblocking, after flashing you might need to restart the phone after the first boot, otherwise it might not work.
- For adblocking KAdaway switching on and off, you will need to Force Close browser app like Chrome to let it work in the given browser.
- For Play Integrity (with SafetyNet passing) you might need to Clean App Data in Google Play Store app to make it reevaluate Integrity
--- If you have magisk installed Play Integrity might be tripped. I only tested without Magisk, flashing CleanSlate 1.0.0 bootimage.
- If using Companion App for notification / gesture etc features, there's a setting in the app to Switch off Proximity sensor while Screen is on. This will prevent the flickering, but Face down screen off feature won't work
Known bugs
- None, please tell
- please disable magisk modules before reporting issues, and please provide logs if possible
Download
Android 13
Non rooted, Android 13 images
ZF9 non rooted installer images zipped - 33.2060.2060.65 WW - CS 1.4.2: https://forum.xda-developers.com/attachments/fastboot_cleanslate_s_zf9_240_imgs-zip.5784177/
Rooted installer zip, Android 13 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 2.4.0: https://forum.xda-developers.com/attachments/cleanslate_s_zf9_240-zip.5784179/
Android 12
Non rooted, Android 12 images
ZF9 non rooted installer images zipped - 32.2050.2050.29 WW - CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Rooted installer zip, Android 12 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android 12 image
ZF9 boot image zipped - 32.2030.2030.26 WW - CS 1.0.0: https://www.androidfilehost.com/?fid=14871746926876840958
Config Applications
Companion App 3.3.x-- Donation premium on PlayStore:
You need to join the BETA program to get the working version for the kernel!
https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 3.2.x -- Donation premium on playstore:
You need to join the Beta program to get the working version for the kernel!
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
How to join beta program: https://forum.xda-developers.com/t/...ashlight-s2s-vib-dec-22.4281807/post-86171493
Android 12:
Companion App 3.3.9 -- Normal free download:
https://www.androidfilehost.com/?fid=15664248565197208875
Configuration App 3.2.11 -- Normal free download:
https://www.androidfilehost.com/?fid=14871746926876820727
Donation:
If you appreciate this, don't forget to hit the Thanks button, Vote 5 stars on Thread, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@MarcoG:
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
@knopie
Special thanks to AnyKernel installer developer: osm0sis
To @Freak07 for all his work on XDA and help
To @Captain_Throwback
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.
Source Code: https://github.com/tbalden/android_kernel_asus_zf9_common-kernel
Readme's and howtos
Changelogs come here later
Be aware that in Battery Saver feature, there's CURRENTLY NO CAMERA APP FOREGROUND DETECTION! Please disable this feature when you use Camera apps (otherwise slow camera, video recording)!
Hopefully camera detection can come later, as still working on more features.
nice work!
great to see you here
Great develop
Thanks for sharing! If I have the patience to get the C version when it eventually releases, I'll give this kernel a try!
- Update Android 12 Stable - 1.4.0 -
Major CleanSlate feature update
​
- Build and repack to QGKI2 kernel format (boot, vendor_boot, vendor_dlkm, dtbo images) with new scripts
--- Thanks go to @Freak07 for the teamwork of many hours in getting to the bottom of this crooked path to build Qualcomm's new modular kernel format and make it work on the ZenFone 9
--- Thanks go to ASUS for providing the most complete sources zip for Qualcomm based QGKI kernels up to date by ANY vendor/OEM.
--- Thanks go to @osm0sis for his AK3 installer and @capntrips for his excellent tooling in AK3 and the tips help he lended in the process of getting things rolling
- Now all features possible to implement added to drivers
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
-- Updates
-- Hosts file for KAdaway
-- Safetynet + Play integrity still passes without Magisk
-- All features work with or without Magisk (tho flashing magisk will break safetynet until you use SafetyNet fix magisk modules)
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.0 Downloads:
Rooted installer zip:
CleanSlate S 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820728
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2030.2030.26)
fastboot image zip CS 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820729
Cleanslate config app version 3.2.11 needed for new features:
Free version download: https://www.androidfilehost.com/?fid=14871746926876820727
Premium version: https://play.google.com/store/apps/details?id=org.cleanslate.csconfig&hl=hu&gl=US
- rolled out to playstore Beta program
Read first post in thread for installation details.
Will it run with the latest fw update?
NisseGurra said:
Will it run with the latest fw update?
Click to expand...
Click to collapse
It actually runs, but new sources are up, and I'm updating the installers soon.
- Update Android 12 Stable - 1.4.1 -​
CleanSlate asus sources update
-- sources updated to 2040.23
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.1 Downloads:
Rooted installer zip:
CleanSlate S 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834460
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2040.2040.23)
fastboot image zip CS 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834462
Read first post in thread for installation details.
Installed, seems flawless
2040.28 update is up, with sources. The new sources has no changes, tested, I'm using the .23 based cs kernel without issues.
- Update Android 12 Stable - 1.4.2 -​
CleanSlate asus sources update
-- sources updated to 2050.29
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.2 Downloads:
Rooted installer zip:
CleanSlate S 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2050.2050.29)
fastboot image zip CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Read first post in thread for installation details.
Is there any way to add vowifi or volte without rooting with a kernel like this?
Hello,
I recently buy this phone and wanted to increase the battery life of this phone.
This seem to be an good option, but have you information about battery life with this kernel ?
Thanks you.
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
dragonii said:
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
Click to expand...
Click to collapse
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
tbalden said:
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
Click to expand...
Click to collapse
So, according to you, I should just take the latest zip file and run the commands in fastboot mode even if I flashed already the cleanstate img file in the first post?
EDIT: did it already and no more error messages with version 1.4.2. Thanks !
Hi again,
How can I access these features? There are not showing up in the CleanSlate Configuration tool.
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
Thanks in advance,

Categories

Resources