Related
Just rebuilt CM from the source, with JIT enabled (and fixed the code to compile)
* With "plain" CyanogenMod 5.0.x ROM it appears to be at least partly functional (people reporting Linpack jump from 7 to 17 Mflops) but I expect instabilities so JIT is definitely still far from the "prime time"
* It appears that HTC Desire ROM and JIT do not mix well. You will get reboots as soon as you try to unlock via. slider. I am trying to figure out what is causing this
For people that want to experiment - I am providing the precompiled Dalvik libraries with JIT enabled. DO NOT TRY THIS IF YOU ARE INEXPERIENCED!!! I assume no liabilities for any problems. Please read the readme first!
Code:
JIT Support for Nexus One CyanogenMod 5.0.x / Kernel 2.6.33.1 (Eclair)
By Ivan Dimkovic (psyq321)
--------------------------
NOTE: JIT is totally unsupported and known to be NOT stable!!! There is no guarantee your system will boot at all!!! ALWAYS BACK UP YOUR SYSTEM WITH NANDROID FIRST!!! This package is provided for TESTING PURPOSES ONLY. Author assumes NO LIABILITY WHATSOEVER if you brick your phone!!!
1. What is this?
This package contains several Android system files that enable JIT ("Just in Time") feature in the Dalvik VM. JIT is very unstable and it is not built-in the AOSP or Cyanogen's ROMs. This package contains system files built with JIT feature ON and it could be useful for testing for people that do not wish to recompile the entire ROM
extra_tuning directory contains Dalvik JIT library compiled with WITH_JIT_TUNING option. This option presumably enables even more optimizations for the JIT, but it appears to be totally unstable (I get endless reboot cycle)
2. How to make JIT enabled?
Follow these steps:
- BACK UP YOUR SYSTEM WITH NANDROID (IMPORTANT!!!)
- Connect your phone to the PC
- Copy the Dalvik files to the system directories:
adb remount
adb push libdvm.so /system/lib/libdvm.so
adb push libnativehelper.so /system/lib/libnativehelper.so
adb push dalvikvm /system/bin/dalvikvm
- Go to the shell (e.g. via adb shell, or via ssh) and change the permissions:
chmod 755 /system/bin/dalvikvm
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
- Add this line at the end of your system's build.prop
dalvik.vm.execution-mode=int:jit
- Reboot into RECOVERY and wipe Dalvik cache!
- Reboot
3. It does not work? My system keeps rebooting / My system crashes randomly?
Unfortunately, this can happen and this is known issue with JIT. This is the reason why it is not enabled. You are free to look in the AOSP code and try to fix it by yourself, but I suggest to wait until original developers make it stable
Enjoy!
Try JIT with a none sense rom like Cyanogen.
Gimpeh said:
Try JIT with a none sense rom like Cyanogen.
Click to expand...
Click to collapse
Bah! What nonsense..... sorry.
[email protected] said:
Bah! What nonsense..... sorry.
Click to expand...
Click to collapse
Don't be so senseless!
it seems people were running it on the g1 for at least a little while what do you think is the difference
I am not really sure, maybe HTC Sense components are much more intensive and force the JIT bugs to appear earlier.
Just tried everything (replaced libdvb.so, libnativehelper.so and dalvikvm - and cleaned up the dalvik cache) - and it is a no-go
If JIT is ON, SIM card is not accessed at all, I just get the lock screen, which triggers the system reboot if I slide it.
This is all on the HTC Desire a19 ROM... I guess JIT is a bit more stable on a stock ROM.
Gimpeh said:
Don't be so senseless!
Click to expand...
Click to collapse
that makes no sense whatsoever.
I thought the last time JIT was in CyanogenMod was in cm-5.0 beta 3. I'm pretty sure it wont work on any ROM except that. I would use it but the multi-touch included in it is still the hacked together version.
I miss JIT ;/
JIT is just not compiled-in by default in CyanogenMod but it is definitely in the code.
You can still enable it manually, but you need to rebuild the ROM from the source.
If you wish to try it - put this line in the buildspec.mk:
Code:
WITH_JIT:=true
Then rebuild everything - and the Dalvik VM will have JIT features inside. Then you need to enable JIT in the build.prop (or by adb manually on runtime)
Doh...
Just fetched the latest source from Cyanogen's github...
Looks like CM+JIT compilation is broken now There are some asserts in the code (Jit.c, line 48 for example) that are referencing missing structure members (looks like they reorganized structure layouts and moved JIT-specific stuff to another one) so the JIT-enabled code won't compile.
Ivan Dimkovic said:
Doh...
Just fetched the latest source from Cyanogen's github...
Looks like CM+JIT compilation is broken now There are some asserts in the code (Jit.c, line 48 for example) that are referencing missing structure members (looks like they reorganized structure layouts and moved JIT-specific stuff to another one) so the JIT-enabled code won't compile.
Click to expand...
Click to collapse
I saw a bunch of JIT related activity on GITHUB today from Cyan. Perhaps hes testing it again for a new experimental build.
This is one official upgrade I'm really looking forward to. Sadly, I bet it wont be released for another year.
yeah. A stable JIT would be a gamechanger.
I thought i was the only one that was interested in on JIT. Either that or Dalvik-Turbo
Looks like JIT breakage is coming from the AOSP itself.
What is going on is, in Jit.c (/dalvik/vm/interp/Jit.c) there are places that expect JIT stuff to be in the DvmGlobals structure - however, those elements are in the DvmJitGlobals structure.
For example, line 48 of Jit.c
Code:
assert([b][u]gDvm.jitTableSize[/u][/b] &&
!([b][u]gDvm.jitTableSize[/b][/u] & (gDvmJit.jitTableSize - 1))); // Power of 2?
gDvm (which is of DvmGlobals type) has no jitTableSize entry - it is part of gDvmJit
I'll try manually fixing these errors (there are few, and mostly confined to asserts fortunately) tonight but this smells like more things are broken.
I had JIT running on my Magic. It was 99% stable... I am actually hoping that Cyanogen fixes all of the bugs in the Java V8 script engine first. It made a big difference in the Browser.
Ivan Dimkovic said:
Doh...
Just fetched the latest source from Cyanogen's github...
Looks like CM+JIT compilation is broken now There are some asserts in the code (Jit.c, line 48 for example) that are referencing missing structure members (looks like they reorganized structure layouts and moved JIT-specific stuff to another one) so the JIT-enabled code won't compile.
Click to expand...
Click to collapse
IIRC, Cy removed Jit due to stability issues. I think there was a stability concern by just having the code in there, even if it wasn't enabled. You might want to dig through his thread a bit.
Hmm
JIT is definitely still in CM's repository... and just by quickly looking at it, it looks exactly the same as in the current AOSP
But it is broken in both. I don't know when exactly it got broken - as the last CM snapshot I had on my Linux VM was from few weeks ago, and the JIT definitely compiled.
Perhaps the breakage is result of some AOSP checkin by Google.
Ok, I fixed compilation errors.. rebuilding everything now.
Will test and upload JIT libraries here.
Ivan Dimkovic said:
Ok, I fixed compilation errors.. rebuilding everything now.
Will test and upload JIT libraries here.
Click to expand...
Click to collapse
Thanks that would be pretty cool.
[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Galaxy Note (ATT)!
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.
quincyatt Device Config: https://github.com/TeamWin/android_device_samsung_quincyatt
Kernel: https://github.com/bigbiff/i717-GB-Kernel
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.
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.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.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.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
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 showing data 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.0
Fixed Device Configs for booting TWRP
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.1
Fix screen timeout by adding correct brightness config file to BoardConfig.mk
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.3.3.0
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
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
10/18/12
Fixed keyboard segfault
Handle single LUN file for USB Storage
Handle mounting of slow sdcards
Update USB Mount Code to be more Efficient
10/13/2012
Many, many updates. See https://github.com/TeamWin/Team-Win-Recovery-Project/commits/jb-wip/ for detailed commits.
8/25/2012
Device ID Sanitization - doesn't affect the note
1920x1200 theme - not for note
320x480 theme - not for note
/data/media issues for other devices fixed - not for note
Fix keyboard issues for 800x1280 and small ui tweaks
Fix some mount error messages
SD-EXT Improvements
Unmount before formatting (if mounted)
Fix Umask for JB builds (this version is still built in CM9/ICS)
Change initial logging fo TWRP startup (include version field)
Kinetic Scrolling improvements
7/17/2012
Fixed backup duplicate name checking
Added checking to see if boot is 0 size and remove from backup menu
Fixed a bug with android secure backup using ORS
Fixed a bug with backup naming when using ORS and backup name is
Slight tweaks to 800x1280 layout
7/12/2012
New release 2.2. See OP for details on changelog. Please leave any feedback in the thread.
6/14/2012
Added the ability to backup /efs when backing up and restoring. It will tar the files instead of using dd so the filesystem isn't formatted.
6/11/2012
Fixed dual mount for USB. You will now see your internal and external sdcards as Windows drives in recovery!
Fixed md5 checking parsing filenames with apostrophes.
Added reboot to download mode in Reboot page
New support for updater-binary included in TWRP. (Don't currently implement this for the SGH-I717
If no OS installed, reboot buttons won't show. Fixes bricking in some devices but doesn't seem to affect SGH-I717.
Added support for partitions greater than 2 GBs.
5/23/2012
Updated ui.xml to make bigger console space
Worked with Dees_Troy to get flash zip in place working. Are ROMs were getting to big and were being copied to /tmp. With the ROMs and RADIOs we overwhelmed recovery. Now your ROM should flash with no issues because we are extracting from storage now.
Dees_Troy fixed a graphics bug which the recovery was still doing work but the GUI said successful.
Update is at teamw.in or goo manager.
5/11/2012
Fixed ui.xml to fix Mount Page for external and internal sdcards
Updated filename on TWRP device page to have proper version in filename
Updated img for GooManager to have proper version in filename
FAQ
Q. How do I see/use/change between internal and external SDCARD?
A. Please use the Mount page to change between using internal and external. Click Using internal sdcard will allow you to use your internal sdcard to install ROMs. Click Using external sdcard will allow you to use your external sdcard to install ROMs. Please dont use the file browser to find the mounts as this is done for you automatically when you change options and navigate back to the Install page.
To be clear this works as follows:
1. internal emmc sdcard mounted on /emmc
2. external sdcard mounted on /sdcard
3. You can choose what storage you want to use on most screens by selecting "Use external SD" or "Use internal storage"
4. Otherwise you can browse to the appropriate directories
Q. Are TWRP backups compatible with CWM and vice versa?
A. You cannot flash a CWM backup in TWRP and vice versa. Please flash appropriate recovery to restore your backup. You can restore the backup, flash back to your wanted recovery, then make a backup in that recovery for later use.
Q. Can I have TWRP and CWM installed at the same time?
A. There is only one recovery partition that can hold a specific version of recovery. CWM, TWRP2, and Samsung 3e are able to be flashed to recovery, but none can coexist.
Q. Does USB mounting work in recovery?
A. Sorry haven't updated this. It works with internal and external sdcard.
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. Installing Roms
A.All ROMs should be able to be installed.
Please post in this thread if you have any issues flashing.
Q. How does MD5 checking work?
A.To create a md5 for a rom perform the following steps:
1. Open a terminal emulator or use adb and cd to the directory your file is located.
2. Execute busybox md5sum rom.zip > rom.zip.md5 where rom.zip is the file you want to create a md5 for. Make sure that the md5 file has the same prefix as your original file with md5 appended with a period.
3. Check force checking of md5 in Settings in TWRP or after the Install file selector page to check the md5.
Q. I can't name my backups.
A. Make sure to hit enter on the keyboard and not the back button to accept the name.
Q. What's next?
A. Fixing bugs.
flashing now!
flashed
Works well, only issue does not mount to pc in recovery, not sure if that is recovery issue or "leaked" ICS issue.
Works Great!!!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
bigbiff said:
Default [RECOVERY] [5/9/12] TWRP 2.1.2 - TeamWin Recovery Project
TeamWin is proud to present TWRP 2.1.2 for the Galaxy ATT Note!
Special credits:
Dees_Troy for a lot of porting help.
braway for helping me to get recovery image to init.
BLOWNCO for helping test
agrabren for writing the initial TWRP GUI code.
AssassinsLament and Dees_Troy for initial TWRP code
Shift and racks for graphics help on default theme
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.1, 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)
What's new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.1.0 now 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.
In the future we will be working hard to make TWRP easier for other developers to compile. We eventually plan to get a gerrit instance running to let anyone submit patches to the project. We may be looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
Zip files that install more data than free space is available will crash or hang recovery (AOSP issue)
No reboot to recovery
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
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.
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Just choose the device in the dropdown.
http://teamw.in/project/twrp2
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Click to expand...
Click to collapse
heard great things about this recovery
Sent from my SAMSUNG-SGH-I717 using xda premium
external sd not working?
how to install from external sd and backup to external sd?
assaace said:
external sd not working?
how to install from external sd and backup to external sd?
Click to expand...
Click to collapse
You can change that option in the mount page to use external sd on the install page. This recovery can also be installed by goomanager from the market.
do we have to remove cwm to install this?
does it become your default recovery when you install it?
thanks
wase4711 said:
do we have to remove cwm to install this?
does it become your default recovery when you install it?
thanks
Click to expand...
Click to collapse
Yes you cannot have more than one recovery installed. You can always reflash cwm if you need to with TWRP.
so, what is the recommended procedure to uninstall CWM, and install TWRP?
when you flash twrp, does it ask you if you want to uninstall CWM?
thanks
Looking good man. Installed from goo.im with no issues. Except even after mounting sd/ext, the external is blank?
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope this is a sign of other things to come
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Actually I discovered when selecting internal vs external, they are reversed
Sent from my SAMSUNG-SGH-I717 using xda premium
Backup rom with cmw it takes more than 5minutes.
When i use this twrp2 it only takes few seconds, is it normal?
Sent from my SAMSUNG-SGH-I717 using xda premium
wase4711 said:
so, what is the recommended procedure to uninstall CWM, and install TWRP?
when you flash twrp, does it ask you if you want to uninstall CWM?
thanks
Click to expand...
Click to collapse
Flashing the zip through CWM overwrites the recovery partition with TWRP2. It's like installing a ROM that overwrites /system.
dsmitty166 said:
Looking good man. Installed from goo.im with no issues. Except even after mounting sd/ext, the external is blank?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Try going in and out of the Install page. I noticed a refresh bug sometimes happens after changing from internal sd to external sd and vice versa.
EDIT:
Just read your next post. You are saying that the internal and external cards are reversed? Can you verify this for me? I didn't have this issue.
bigbiff said:
Try going in and out of the Install page. I noticed a refresh bug sometimes happens after changing from internal sd to external sd and vice versa.
EDIT:
Just read your next post. You are saying that the internal and external cards are reversed? Can you verify this for me? I didn't have this issue.
Click to expand...
Click to collapse
Yeah man, just looked again
select use internal...and only see external
select use external...and only see internal
Sent from my SAMSUNG-SGH-I717 using xda premium
bigbiff said:
Try going in and out of the Install page. I noticed a refresh bug sometimes happens after changing from internal sd to external sd and vice versa.
EDIT:
Just read your next post. You are saying that the internal and external cards are reversed? Can you verify this for me? I didn't have this issue.
Click to expand...
Click to collapse
assaace said:
Backup rom with cmw it takes more than 5minutes.
When i use this twrp2 it only takes few seconds, is it normal?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
There is a GUI bug that sometimes shows successful but the console will still show that its running. We are looking into this issue. Make sure to pay attention to the console if this bug happens and please send me a copy of /tmp/recovery.log. You can used the Advanced Page to copy the logfile to sdcard.
Icy Fusion ROM
Final: v2.3
~~The best ICS experience..on Gingerbread!~~ Fast and smooth! Crazy battery life!
klin1344 said:
Hi everyone,
I am sorry to say that I will be retiring this ROM. I will be receiving my HTC One S next week, and most of my development efforts will be focused over in those forums. I won't abandon the 4.0 completely, but this will be my last ROM for it, with no more future updates. I also feel that this ROM is pretty complete and definitely usable for a stable daily driver.
I want to thank the community who supported my development, and my ROMs have been a good learning experience for me. But too bad the galaxy players were never very popular with developers...
Anyways, hope you enjoyed my work here. Links will always be available.
Click to expand...
Click to collapse
As you probably all know, I have ditched Klassic and letting hanthesolo continue it. I was going to make a SGS2-styled ROM, but instead I chose a total ICS-styled ROM instead due to the popularity of Android 4.0. I will be maintaining this ROM in two builds--one based on G1UEKI8 (USA) and another based on XXKPQ (INTL). Using an INTL ROM on a US player, and a US ROM on an INTL player caused too many issues (bluetooth, home button, toggles, etc), so I have decided to do it this way for better integration and the best possible experience. As of now it is not very different from Klassic (or Stratus), but as I make new releases it will have more and more features. Also it will be flashable with CWM. Enjoy
Features:
v1 (6/18/12)
- complete ICS theme (even better themed than Klassic, just look at the screenshots)
- swapped internal USB storage and external SD card (see 3rd post on how to revert)
- Holo Launcher installed
- ICS transitions + Roboto Fonts
- ICS clock widget
- deodexed
- zipaligned
- smooth scrolling mod (a.k.a. disabled scrolling cache in framework)
- smooth spinners mod
- CRT screen off animation
- 14 statusbar toggles
- "Device ID" hack ~now apps like XDA, Whatsapp, Tap Tap Revenge, and any app that needs a unique device id will run and not force close~ (XXKPQ uses Meticulus' hack, G1UEKI8 uses a slightly different method, but still same result)
- advanced powermenu with reboot, recovery, and download
- Supercharged with V6 Supercharger
- my own init.d scripts (you can look at the notes in the "55tweaks" file to see what I put in there)
- improved battery life
- I/O performance enhancements
- better performance
- TerraSilent as the default CPU governor
- plus more
- fixed performance and freezing issues from Klassic R5 (note: this ROM is completely made from scratch from stock, not based on Klassic or another ROM)
- fixed bluetooth issues from Klassic R5
- loads of build.prop tweaks
- debloated (I will attach the apps that I removed if you still want them)
- latest SU Binary 3.0.3.2
- BusyBox 1.20.1
- RFS filesystem ---> /system doesn't need to be on EXT4 because you are not constantly writing data on it
Click to expand...
Click to collapse
v1.1 (6/19/12)
- more init.d scripts for unbeatable battery life and performance
- loopy smoothness script
- sysctl tweaks for speed
- added SuperSU
- fixed the busybox symlink problems in v1
- released the INTL build
- busybox 1.19.3
- updated theme (look at screenshots)
Click to expand...
Click to collapse
v2.0 (6/21/12)
- disabled zCache by default --> to enable, go in 55tweaks and delete the '#' in front of "insmod /lib/modules/zcache.ko"
- implemented swipe to remove notifications
- added CRT screen ON animation
- improved touch responsiveness
- disabled start up sounds
- set an ICS wallpaper as default
- added 5 new ICS wallpapers in Wallpaper Gallery
- Galaxy Nexus bootanimation
- improved the implementation of the device id hack
Click to expand...
Click to collapse
v2.1 (6/23/12)
- FIXED BLUETOOTH!! and still Supercharged
- more battery life tweaks
- more performance and responsiveness tweaks
- fixed powermenu "Reboot Download"
- added TouchWiz 4.0 modified by me
- GT-I9000 Settings.apk (more options)
- completely re-designed Settings.apk
- ICS themed + added HoloLauncher Settings (see screenshots)
- "IcyFusion ROM" selection in Settings is a shortcut to device status
- succesfully smali'ed out (removed) "Call Settings" from the Settings.apk
- updated Holo Launcher to v1.0.5
- updated SuperSU to v0.92
- now /system is on EXT4
- ODIN package until CWM /data issues are sorted out
Click to expand...
Click to collapse
v2.2 (6/24/12)
- used stock Settings.apk, but still designed the same as v2.1
- fixed the setup wizard loop
- cleaned up init.d scripts
- added a lot more init.d speed tweaks
- added DSP Manager apk + libs
- added Zeam Launcher
Click to expand...
Click to collapse
v2.3 (6/26/12)
- optimized EXT4 mounts in init.d scripts (fast i/o performance; I got 2300 in Quadrant with only stock 1Ghz)
- added transparent background theme --> see post 3 on how to change the background picture
- optimized auto brightness levels for battery life
- stock sd card and internal storage mounts
- improved ICS theme
- Youtube HD apk
- fixed DSP Manager, and now every feature works
Click to expand...
Click to collapse
Downloads
*Simply flash in CWM*
*v2.1 & up flash with ODIN*
wipe data if you are have issues
USA/INTL:
v1: http://d-h.st/wWE
v1.1: http://d-h.st/jyP
v2.0: http://d-h.st/jGF
v2.1: http://d-h.st/W0I
v2.2: http://d-h.st/WYB
v2.3: http://d-h.st/mPa
INTL
v1: none; look for v1.1
v1.1: http://d-h.st/ILv
v2.0: none
INTL users please try the US version and post here if there are issues
Sorry, I will have to drop support for INTL players because it is too difficult to keep flashing, modding, and testing both builds of the ROM. I understand that 2.3.5 caused a reboot issue on INTL players when the headphones are plugged in. If somebody could please post a logcat, and I will try and see what I can do to fix the issue. Thanks.
Special thanks to:
Dark_Balor for improving the kernel for our device
zeppelinrox for his V6 SuperCharger
Meticulus for his Device ID hack for 2.3.6
Vertumus for some parts of his ICS Domination Theme
dsixda for his kitchen
And many others I probably forgot to mention
ScreenShots
Extras and add-ons
Extras and Add-ons
Here I will attach some miscellaneous add-ons for my ROM.
How to manually wipe and format data into EXT4
1. Boot into CWM recovery. Make sure you are using the latest TerraSilent kernel.
2. Type 'adb shell' in command prompt or Terminal.
3. Type the following code:
Code:
umount /data
umount /dbdata
umount /cache
Then:
Code:
mke2fs -f ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p2
mke2fs -f ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/stl10
mke2fs -f ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/stl11
4. Reboot. Or you can follow below on how to disable EXT4 journaling (don't reboot), which GREATLY improves i/o performance. Note that every time you boot into recovery, /data get wiped into RFS again due to a CWM bug. I suggest that you do not boot into recovery again after rebooting unless you really need to.
To disable EXT4 journaling
1. Make sure you have flashed my ROM, as it includes some tools for this procedure.
2. Unmount the partitions if they aren't already:
Code:
umount /data
umount /cache
umount /dbdata
4. Follow:
Code:
tune2fs -O ^has_journal /dev/block/mmcblk0p2
tune2fs -O ^has_journal /dev/block/stl10
tune2fs -O ^has_journal /dev/block/stl11
5. You're done! Now you can reboot, and see the massive jump in Quadrant, especially if you're using ROM v2.3 and up.
How to change the background wallpaper theme
For v2.3, I've enabled the use of a custom wallpaper theme, which will show up in many apps. If you don't like the picture I used, you can replace it yourself with these very simple instructions.
1. Copy the /system/framework/framework-res.apk from your player.
2. Using an archiver, like winzip or 7zip, open the apk.
3. Find any 480x800 png image that you like, and name it screen_background_dark_transparent.png
4. Drag it into the res/drawable-hdpi/ folder of the apk. It will replace the original one in there.
5. Copy framework-res.apk back, and make sure to set permissions rw-r--r--. Reboot.
Extras
- Stock vold.fstab (for stock usb storage and sd card mounts): http://d-h.st/FKL
This is how to install
Code:
cd [B]*directory of the file*[/B]
adb remount
adb push vold.fstab /system/etc
Or simply just copy/paste with root explorer and reboot.
reserved again
It looks nice. I have 1 suggestion. It is possible to put the SGSII lockscreen into it? It would be perfect! (for me though I don't know for the others)
zaclimon said:
It looks nice. I have 1 suggestion. Is it possible to put the SGSII lockscreen into it. It would be perfect! (for me though I don't know for the others)
Click to expand...
Click to collapse
I could try, and maybe upload a framework-res specifically for people who want an SGS2 lockscreen.
I am trying to get INTL support for this ROM, but unfortunately I noticed that with XXKPQ if I use dsixda's kitchen I get this error when trying to use busybox:
Any busybox applet will result in the same...
It doesn't happen on 2.3.5 G1UEKI8 though.. I have tried unrooting and rerooting, using the install busybox option with kitchen, reinstalling busybox, but nothing seems to work.
So..for now I will only be supporting US devices until someone can either help me get rid of this error or at least help me find another INTL ROM that I can base my work off of.
Nice! It seems we are branching off, you to theming and features, I to raw performance . Just from one dev to another, did you fix bluetooth by unullifying? Also, how did you get framework-res to successfuly recompile without FC's? I tried doing it, and it basically blew up my Gplayer. Maybe using a apk decompiler is not the way to go...Argh, I hate windows, I never have these issues in Ubuntu...
Finally, where did you find his deviceid hack? when I got to his thread he had nuked all of his work...sad that someone would try and rip off his hundreds of hours of work.
hanthesolo said:
Nice! It seems we are branching off, you to theming and features, I to raw performance . Just from one dev to another, did you fix bluetooth by unullifying? Also, how did you get framework-res to successfuly recompile without FC's? I tried doing it, and it basically blew up my Gplayer. Maybe using a apk decompiler is not the way to go...Argh, I hate windows, I never have these issues in Ubuntu...
Finally, where did you find his deviceid hack? when I got to his thread he had nuked all of his work...sad that someone would try and rip off his hundreds of hours of work.
Click to expand...
Click to collapse
I use apkmanager to modify my apks if I'm on windows, but if I just happen to be using Linux and I'm too lazy to reboot I use apktool (which requires more work though). For the device id hack, it was a method in framework.jar. Copying and pasting that method from Meticulus's worked for 2.3.6, but would cause a bootloop on 2.3.5 US. So I looked at the logcat and used a modified version of this: http://forum.xda-developers.com/showthread.php?t=955847 for my deviceid hack.
I hate editing smali though...it's so difficult to understand.
klin1344 said:
I use apkmanager to modify my apks if I'm on windows, but if I just happen to be using Linux and I'm too lazy to reboot I use apktool (which requires more work though). For the device id hack, it was a method in framework.jar. Copying and pasting that method from Meticulus's worked for 2.3.6, but would cause a bootloop on 2.3.5 US. So I looked at the logcat and used a modified version of this: http://forum.xda-developers.com/showthread.php?t=955847 for my deviceid hack.
I hate editing smali though...it's so difficult to understand.
Click to expand...
Click to collapse
Thanks! I used apk manager, but it still did not work without fc....maybe i will try a different tool (for some reason it will not recognize adb or aapt in ubuntu even though I can run the commands from the terminal.
It seems we have competing roms now...may the best dev win.
Sent from my Galaxy Player Running my Stratusrom.
hanthesolo said:
Thanks! I used apk manager, but it still did not work without fc....maybe i will try a different tool (for some reason it will not recognize adb or aapt in ubuntu even though I can run the commands from the terminal.
It seems we have competing roms now...may the best dev win.
Sent from my Galaxy Player Running my Stratusrom.
Click to expand...
Click to collapse
Ummm...don't forget that your work is still based off of my work
Editing smali and the framework for new features (powermenu, toggles, etc) is the real ROM work...hehe
Besides, I'm not here to compete; I just want to share my work.
Point taken, I just wanted some friendly competition, it helps to make work go faster.
But, I would like to see you spend 3 hours fixing init.d scripts, and tweaking sysctl for best ram usage.
My point is, we are both skilled in completely different areas. I am better at some things, and You blow past me in others. It just comes down to the users preference.
klin1344 said:
I am trying to get INTL support for this ROM, but unfortunately I noticed that with XXKPQ if I use dsixda's kitchen I get this error when trying to use busybox:
Any busybox applet will result in the same...
It doesn't happen on 2.3.5 G1UEKI8 though.. I have tried unrooting and rerooting, using the install busybox option with kitchen, reinstalling busybox, but nothing seems to work.
So..for now I will only be supporting US devices until someone can either help me get rid of this error or at least help me find another INTL ROM that I can base my work off of.
Click to expand...
Click to collapse
Ugh..I just found out that it is the same with G1UEKI8 as well.
I flashed my factoryfs.rfs version and busybox worked, so I will upload the factoryfs in an Odin package tomorrow. From now on the roms will have to be flashed through Odin until I can find a fix.
Sent using Tapatalk
klin1344 said:
I am trying to get INTL support for this ROM, but unfortunately I noticed that with XXKPQ if I use dsixda's kitchen I get this error when trying to use busybox:
Any busybox applet will result in the same...
It doesn't happen on 2.3.5 G1UEKI8 though.. I have tried unrooting and rerooting, using the install busybox option with kitchen, reinstalling busybox, but nothing seems to work.
Click to expand...
Click to collapse
I have that same issue on my device (different rom). Busybox works fine; the issue is that somehow the symlinks got corrupted (hence the not found and weird characters). I fixed it (post-install) by deleting the broken files and recreating the symlinks in /system/xbin. You might want to check your updater-script or the 'install-busybox.sh' file the kitchen creates.
Sent from my 5.0 USA GenGin + ICS theme
Flash Tool for this ROM
Which flashing utility/method do you recommend for this ROM?
Thanks!
Mevordel said:
I have that same issue on my device (different rom). Busybox works fine; the issue is that somehow the symlinks got corrupted (hence the not found and weird characters). I fixed it (post-install) by deleting the broken files and recreating the symlinks in /system/xbin. You might want to check your updater-script or the 'install-busybox.sh' file the kitchen creates.
Sent from my 5.0 USA GenGin + ICS theme
Click to expand...
Click to collapse
Thank you. So all I have to do is just recreate the symlinks in /system/xbin? I didn't think it would be that easy
Sent using Tapatalk
If we did all that ext4 foo foo should we go back to stock before flashing?
rozelle25 said:
If we did all that ext4 foo foo should we go back to stock before flashing?
Click to expand...
Click to collapse
No need to. It will still work fine with ext4 partitions.
Sent using Tapatalk
What you need to do is make a list of all of the files in /system/xbin that are there after flashing but aren't in your working folder's system/xbin. Those are the (broken) symlinks created by the installbusybox.sh script at the root of your zip. You need to put a symlink command in your updater-script for each of those (referring to the lines already there), and then you can delete the installbusybox.sh script and the updater-script lines referring to it.
Sent from my 5.0 USA GenGin + ICS theme
Everytime I try to turn on Wifi it says error and bluetooth still doesnt work... besides that everything seems to be working fine is there a reason why my wifi wont start?
[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
Agnostic-kernel - filesystem independent kernel flasher
WARNING!
Please, make a backup or be prepared to roll back to a working state somehow. You are using this tool on your own responsibility. You have been warned!
If anything goes wrong, flashing another kernel that was working for you before should return your device to a working state.
Repository on GitHub
This is a recovery tool primarily made for kernel/ROM developers, but anyone is welcome to use it, provided he knows what to do. It was made to enable kernel developers to have a single .zip with the kernel which will work on all partition layouts like All-F2FS, Data-F2FS and All-EXT4 (the standard layout).
It takes a boot.img, unpacks it during the installation, finds out what partition layout is used on the device, changes the fstab in the ramdisk accordingly, repacks the boot.img and flashes it.
Instructions for kernel/ROM developers/flashaholics who wish to incorporate this tool:
Make sure your kernel is compiled with F2FS drivers.
Download agnostic-kernel-template.zip
Replace the boot.img-placeholder in the .zip with your boot.img.
OPTIONAL: change the fstab in fstab/ folder to specify any mount options you wish to use. Make sure you include a line for each partition and filesystem combination you want to use.
OPTIONAL: change the updater-script to print any additional messages or make modifications to the kernel after flashing.
Instructions for users who wish to try this tool:
Choose one of the prepacked kernels you wish to install and download it.
Install it via recovery.
Instructions for people who wish to port it to other devices:
Change the asserts in updater-script to check for your device name.
Change the fstab in the fstab/ folder. Make sure you include a line for each partition and filesystem combination you want to use.
Change the FSTAB variable in tools/repack-and-flash.sh to contain the name of your fstab file.
Change the BOOT_PARTITION variable to contain the path to your /boot partition device.
Currently supported partition layouts:
/system on EXT4 or F2FS
/cache on EXT4 or F2FS
/data on EXT4 or F2FS
Filesystem changes are supported only on these partitions because the Nexus 7 doesn't have any other EXT4 partitions by default.
If you want to add support for some other device specific layout (F2FS formatted SD card comes to mind, for example), feel free to do so or contact me, but it may require some changes to your recovery too.
Tested on:
Kernels
3.2.5-XPerience by @TeamMex
LegoKernel / SlimKernel by @legolas93
franco.Kernel by @franciscofranco and modified by @HTCDreamOn
linux-tegra-nv-3.1-grouper by @HTCDreamOn
M-Kernel by @Metallice
Recoveries
CWM Recovery 6.0.4.3 by ClockworkMod
TWRP by @legolas93[/MENTION]
MultiROM recovery by @@Tasssadar
ROMs
ROM shouldn't matter, I tested on various 4.4 / 5.0 ROMs and even without a ROM and it always worked.
Downloads
Pre-packed kernels:
Kernel from SlimROM by @legolas93
3.2.5-XPerience-19 by @TeamMex
Empty template for devs:
agnostic-kernel-template.zipYou can download other kernels using agnostic-kernel in their respective threads.
Credits:
Android Image Kitchen - @osm0sis - this wouldn't be possible without him
F2FS Recovery - @legolas93
Kernels on which I tested - @TeamMex & @legolas93 & @franciscofranco & @HTCDreamOn & @Metallice
Recovery magic - @Chainfire & @_that
Answers to a lot of my problems - forum.xda-developers.com community
Some nice ideas - @Metallice
Partition layout checking, scripting - @frantisek.nesveda
If you wish to incorporate or modify this tool, please, mention me somewhere, thanks
Changelog:
13th November 2014
This is a highly recommended update for all developers using agnostic-kernel.
Now completely ROM independent
Updated Android Kitchen to version 1.6 - thanks, @osm0sis!
Fixed an issue with Android Kitchen binaries using /system/bin/linker which was not always available.
First I did an ugly hack to solve the issue...
and then I found out that the updated Android Kitchen binaries are statically linked now and the ugly hack was not needed anymore.
Changes to the way fstab is generated - now it uses only one file and deletes unneeded lines from it - inspired by @Metallice
Added more error-checking
Some other small fixes and improvements
Tested on a lot of recoveries and partition layouts.
13th May 2014
Fixed an issue with the zip which could arise when /system was not mounted before the install.
Tested on a lot of recoveries and partition layouts.
12th May 2014
Initial release.
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
aosp said:
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
Click to expand...
Click to collapse
If I'm not mistaken, this is a code in a custom recovery that enables the user to select if he wants to format his partitions as F2FS or EXT4, similar to what the MultiROM recovery does after yesterday's update?
If so, I don't see the connection that your code has with my tool... My tool is a template for a recovery zip, in which kernel devs can place their boot.img, and when the user installs that zip with the boot.img, the script in that zip will check for which partitions does the user have formatted as F2FS and modify the fstab in the boot.img accordingly.
Updated all the zips with a bugfix. The Android Image Kitchen would not start on CWM when /system was not mounted, because it tried to use sh in /system/bin instead of /sbin.
Also, I tested the zips on more partition layouts and recoveries, and verified that it works right both on CWM and TWRP and on ALL-F2FS, Data-F2FS and ALL-EXT4.
awesome work
How do we convert if we only have a zimage and no boot.img
Sent from my Nexus 7 using Tapatalk
chaostrodamis said:
How do we convert if we only have a zimage and no boot.img
Click to expand...
Click to collapse
The changes are all done to the ramdisk, so you can't do them without one, at least not with this method.
But, if you look how @sgt. meow does it in his Oxydo kernel, perhaps that is the way you could use. He unpacks the ramdisk from the currently installed kernel and then packs it with his zImage to a boot.img which he then flashes. This requires that the user first flashes another kernel with f2fs working, and then flashes your kernel.
Perhaps it would be easier if you packed your kernel with some ramdisk and then used it.
An updated version of agnostic-kernel is available in the OP. See post #2 for changelog.
Both the template zip and the two prepacked kernels are updated.
This is a highly reccomended update for all kernel developers, as it fixes compatibility issues with some ROMs (AOSP Lollipop, for example).
I've also published sources to my working folder on GitHub, if anyone is interested. There's nothing really important there, though.
Thanks for the post in my thread. I've been trying to figure out how to edit the line in the file and kept running into roadblocks. I'll definitely take a peek. The other thing I am planning to do is pull the boot image from the phone instead of having it in the zip file.
RoryB said:
Thanks for the post in my thread. I've been trying to figure out how to edit the line in the file and kept running into roadblocks. I'll definitely take a peek. The other thing I am planning to do is pull the boot image from the phone instead of having it in the zip file.
Click to expand...
Click to collapse
You're welcome. And you could perhaps try pulling the boot.img with dd, something like this:
Code:
dd if=$BOOT_PARTITION of=/tmp/agnostic-kernel/boot.img