Database Users

[RECOVERY] [Touchpad] TWRP 2.3.2.3 with on-screen keyboard! [2012-12-17]

Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.3:
-Fix to libraries to avoid issues when formatting partitions
CHANGELOG for 2.3.2.1:
-Updates to fix permissions
-Fix USB OTG on GNex
CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
Direct Download
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Awesome job guys
Sent from my EVO 3D using tapatalk

Very well done!

I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey

vWvSTATICvWv said:
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
Click to expand...
Click to collapse
Hmmm, I will look in to this .....

vWvSTATICvWv said:
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
Click to expand...
Click to collapse
Which theme? Maybe someone would want to convert it.
Sent from my Touchpad using xda premium

Awesome work teamwin. This is awesome. Need this on my samsung epic.

Leoisright said:
Hmmm, I will look in to this .....
Click to expand...
Click to collapse
Yea I probably will make a theme when I get the tp in a few days
Sent from my Nexus S 4G using xda premium

I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.
To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.
So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod
This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod
I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.
For the moment I changed the names back so it uses Clockwork for the default and behaves normally.

bobtidey said:
I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.
To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.
So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod
This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod
I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.
For the moment I changed the names back so it uses Clockwork for the default and behaves normally.
Click to expand...
Click to collapse
The bootloader project is here: http://code.google.com/p/moboot/
If you're feeling inclined you can ask how you set the default boot for recovery and whatnot. That would probably be a good start. Maybe someone on my team knows, but it can't hurt to learn anyway.

Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d
I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.
When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.
I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.

anyone flash roms with this yet. In the eco people are stating wipin isn't working and hey flash and get stuck in a boot loop
Sent from my PC36100 using xda premium

I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.

bobtidey said:
Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d
I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.
When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.
I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.
Click to expand...
Click to collapse
All versions of moboot have a README in the moboot_X.X.X.zip file.
From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should
You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.

bluedogtouchpad said:
I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.
Click to expand...
Click to collapse
I had the same problem. I installed CWM first, then install TWRP through CWM.

Installed successfully after running the clean boot zip.
I went to the backup section to try and perform a backup but it gives me options that i can select/unselect and am not sure what should and shouldn't be selected.
Thanks

jcsullins said:
All versions of moboot have a README in the moboot_X.X.X.zip file.
...
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
Click to expand...
Click to collapse
Thanks. I should have checked the readme.
I discovered the home key trick the first time I tried this and was beginning to wonder how to get out of the loop.
Good to hear TWRP will remove it as well as I'm keen to use this as the standard and be able to reboot into recovery from CM7.
Extra refinement would be if CM7 reboot menu listed all the boot options it could find so that it wouldn't be necessary to rename the image to match the Clockwork that will be used when recovery is chosen.

LastQuark said:
I had the same problem. I installed CWM first, then install TWRP through CWM.
Click to expand...
Click to collapse
Did you install CWM by itself? If so how did you do that?
Thanks,

Wow awesome I never thought this would be possible. A revolution in recovery it seems. Wonder why other devices haven't got this already.

jcsullins said:
All versions of moboot have a README in the moboot_X.X.X.zip file.
From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should
You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
Click to expand...
Click to collapse
Thanks, I tested this extensively in an attempt to get my Touchpad into TWRP by default and ran into the same issue with moboot.next, I tried to make it read only after putting Cyanogemnod into it among other things but couldn't get it to work 100%. For now, seems like other folks are running into the same issues and sounds like you guys will take care of it in the next release of moboot. Thanks for all the work.

[BINARY]FlashPak v1.01(A simple binary to flash packages!)[DEV]

Alright, guys, I decided to put a little binary together for you guys. It's called "flashpak", which stands for flash package. The usage is very easy, and I hope developers use this in they're apps.
Works on CWM, TWRP, AMON, and any other recovery ... erm... Let me rephrase that.. it works on all recoveries
Usage:
Code:
flashpak file.zip
^ If the file "file.zip" is in the root of your SDCARD, just type what's above
It will then reboot you into your recovery and begin to flash the package.
Please note:
*Only works on devices that use "reboot recovery".
*Must be ran under su.
*I'm not responsible for anything if any of you mess up... well.. I am, but I won't be available to fix your device right and then.
*Since I used the Android-9 toolchain, I'm assuming that it only for 2.3+... not sure.
*Package must be on your SDCARD!
Changelog:
v1.01 - Fixed errors with confusion of the external storage's.
What to add:
*Able to reboot to recovery on devices that can't do "reboot recovery".
How to install, just extract the "flashpak" binary from the zip provided.. Extract it somewhere and run it
I'll try my best to keep this updated as much as I can. School is gonna start soon, and it's my last year in HS, and I might not update it as often as I will throughout this week :\
Source code: https://github.com/Simran/adbNetScan
Like me on Facebook: https://www.facebook.com/SimranApps
Follow me on Twitter: http://www.twitter.com/SimranDevs
Add me on Google+: https://plus.google.com/114069302448745664287

Good one
Can I use this in my tool over at my signature?
Can you compile it with lower toolchain and add support for 2.1+ devices
There are large number of 2.1 and 2.2 devices.
And this sends the extended commandline to recovery right?

varun.chitre15 said:
Good one
Can I use this in my tool over at my signature?
Can you compile it with lower toolchain and add support for 2.1+ devices
There are large number of 2.1 and 2.2 devices.
And this sends the extended commandline to recovery right?
Click to expand...
Click to collapse
Sure! Just make sure whatever you're going to flash is on the SDcard. If it's in another folder on the sdcard... mm.. say folder "foo" and zip "bar.zip", then simple type in:
Code:
flashpak foo/bar.zip
It doesn't accept a backslash at the beginning, but I'll work on that.

Updated to v1.01. Please give results.. gonna update tomorrow!

[DEV][RECOVERY] TWRP Recovery 2.7.0.0

TWRP Recovery
For Galaxy Ace
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
Me: For compiling it for Galaxy Ace.

CHANGELOG for 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.

DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!

About the current build:
STABLE

Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app

aurisltu said:
Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
I think, I should remind you: Recovery is independent of ROM.
It can flash everything which the new kitkat update-binary allow.
If anything fails to flash, just replace /META-INF/com/google/android/update-binary file inside that zip from cm11 or omni4.4 and it will flash.

well im using this recovery for a while and its responding better than the normal recovery , plus the other features in it , thanks for you great work
keep it up
sent from my kitkat ACE

works great, but if formatting or installing and you accidentaly bump the back button it stops what it is doing, can also corrupt the partition, installs ALL roms from cm9 through to cm11 and all scripts/mods install too,, thanks for this version,, i didnt like the other versions they were a yuck colour, i like the black and gray theme

I just had some look today on your device's development forum and found that @Mardon has already made this recovery for your device (Because, I was confused as I didn't receive a single THANK on any of my posts).
Please note that my TWRP has no relation with @Mardon's TWRP. He has used omniarmv6 sources while I've used official omni sources and the androidarmv6 sources.
I've worked hard enough and researched on everything and have made this recovery. This build is the closest one to an official build unlike little buggy build of @Mardon: Bad colors (not official colors), maybe brightness settings are missing, maybe you can't flash some zips with that recovery, etc.
And...ofcourse, you won't be able to flash stock rom using this recovery because it uses samsung's crappy rfs.

Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.

Thanks Bro for the recovery.
Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse

Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse
Work fine bro.. good job.. :fingers-crossed:

Thanks for this recovery, really works great, with CM9 too!

Bhargav97 said:
DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)

Bhargav97 said:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
not working ... failed with error: -1

GalaxyAce User said:
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)
Click to expand...
Click to collapse
Busybox is needed for flash_image command to work. If you are using any Stock Based ROM, I doubt you have Busybox. If you can't manage to get it done this way (I don't get, why?) then you can replace recovery.img inside any recovery flashable zip file (of recovery, i.e. CWM-x.x.x.x.zip) from the one given in the link of first post. Now flash that zip file using your current recovery.
kjub6 said:
not working ... failed with error: -1
Click to expand...
Click to collapse
What I said above, also applies to you.

Thank you
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.

sdembiske said:
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.
Click to expand...
Click to collapse
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM

Thank you ...
Viper The Ripper said:
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM
Click to expand...
Click to collapse
Yes, found that out - neither this nor Mardon's TWRP version worked on Mardon''s CM11 latest. Took the recovery.image file out of CWM-6.0.5.3-cooper and flashed it using terminal command:
su
flash_image recoveryonly /sdcard/recovery.img
Worked like a charm and all's well now. Would like to know though what settings you recommend on SuperchargerV6 on Mardon's CM 11 with your patch for it installed - have not successfully managed to get it past the Samsung boot screen at 50% Supercharged the two times I have tried.
Thanks again, Steve

Link to dowload
Hi Bhargav97,
I don't found link for to dowload, it's possible that can u send me this link?
Many thaks!

[MOD] No forced encryption on CM12 stock kernel - once and forever

Force-Encrypt Toggler
Disclaimer: I have no experience in Android/ROM development. This is the first time i decided to share something (that i initially made for myself). Flash at your own risk. I am not responsible for boot loops, unexpectedly encrypted partitions, data loses, etc. Make sure you have a backup first!
Click to expand...
Click to collapse
Now that CyanogenMod developers stated that they are going to follow Google's guidelines about forced encryption in their ROM for Nexus 9, those of us who want their tablets unencrypted will have to flash a modified boot image every time they update CM. I hate doing such things manually every time, so i created a patch that disables forced encryption the right way - flash once and forget forever.
force-encrypt-toggler reads and unpacks your boot image, patches the ramdisk, creates a new boot image and flashes it back to the boot partition. And all that is done right on your tablet. Than it uses CM's addon.d framework, so that each time you flash a new CM zip, force-encrypt-toggler is invoked automatically to patch the newly flashed boot image. Thus, you can just upgrade through CM's built-in updater and everything will be patched automatically every time . Also, the script itself can be used on any Linux computer to patch (probably) any boot.img you have.
Thus far i have used it on my Nexus 9 to stay unencrypted starting from 20150216 through 20150224 nightlies. It seems to be quite stable, i believe . See some notes in the second post.
Download
force-encrypt-toggler-1.1-flounder.zip : https://goo.gl/bw7YDq
force-encrypt-toggler-1.1-flounder-dbg.zip : https://goo.gl/95JN34 - this one creates log files in /cache every time
force-encrypt-toggler-1.1-linux.tar.gz : https://goo.gl/3PF6ru - to be used on a desktop to patch arbitrary boot.img
old versions (for CM12): https://goo.gl/125eey
Sorry, it looks like i can not post clickable links yet. Remove space between "https" and colon.
Compatibility
I have tested this script only on my Nexus 9 Wi-Fi with TWRP recovery and CM stock boot image. However, i believe that it should be possible to make it work on other devices (e.g. Nexus 6) by just changing a few constants at the beginning.
Version 1.1 requires TWRP version >= 2.8.7.1 and a CM13 nightly >= 20160110. Version 1.0 will work for CM12.x (but not for recent CM13 nightlies).
Known issues
The addon.d script uses a dirty hack to trick the recovery. While this never happened to me, if you ever encounter a strange recovery behavior regarding installation or backup of boot images after flashing CM zip over CM with this mod, this might be it. Just reboot and it should be ok. See the second post for more info.
If CM changes something in their updater or if something changes in the recovery, this mod may easily break due to the hack mentioned above. Read the disclaimer.
Each time you flash a CM zip over a CM installation with this mod installed, TWRP recovery will hang for 5-10 seconds after reporting successful completion and before showing buttons at the bottom (or before rebooting in case of open recovery script execution). It is possible to fix this easily, but than this mod might be much easier to break.
Installation
First, you should read the disclaimer above and backup your data. Than you just have to flash the zip you downloaded with TWRP recovery. CyanogenMod must be installed first. If your /data is currently encrypted, you will have to do a full factory reset to decrypt it (backup your data first!).
Your current boot image will be patched during installation process (it should not hurt, if it's already patched). In case if something goes wrong, installation script will tell you. In any case you can get force-encrypt-toggler debug output by something like:
Code:
adb pull /tmp/fet.log
Be sure to do this before you reboot, because that file is created in the RAM.
Removal
In order to remove force-encrypt-toggler you have to delete the following files from your /system partition:
Code:
/system/xbin/mkbootimg (v1.1)
/system/xbin/unpackbootimg (v1.1)
/system/bin/force-encrypt-toggler
/system/addon.d/90-force-encrypt-toggler.sh
/system/bin/mkbootimg (v1.0)
/system/bin/unpackbootimg (v1.0)
And than restore your original boot image. You can also just format /system and flash CM again, but that is such an overkill .
Usage
Normally you will not need to run force-encrypt-toggler yourself, but in case you need, you should be able to run it both in Android and in recovery via adb shell. Just run it with --help option to see what it can do. In case you will have to debug some glitches, this command may be useful:
Code:
force-encrypt-toggler --set-not-forced --debug --dry-run --no-cleanup
If you use it on a Linux computer, this is what you will probably need:
Code:
sudo ./force-encrypt-toggler --set-not-forced [ --input path/to/boot.img --output path/to/new/boot.img ]
Note that Android and computer versions are functionally equivalent, so you can theoretically patch boot images for one Android device on another one...
Changelog
Code:
v1.1
+ use toybox instead of busybox because CM now ships only the later
+ mkbootimg and unpackbootimg are now installed to /system/xbin
+ the --help option can now be used without root privileges
v1.0 - initial release
Credits
mkbootimg is built from AOSP source
unpackbootimg is taken from this GitHub page: https://github.com/Dees-Troy/unpackbootimg
update-binary is taken from a CM zip

There is one problem with patching the new boot image from an addon.d script: CM's updater-script flashes boot image after it invokes all addon.d scripts. Therefore at a time, when the script is called, it is possible to patch only the old boot image, and than it will still be overwritten anyway. In order to overcome this, i used a very dirty hack. In short, i replace the device node with a fifo and let the updater write new boot image into it, and than... Ok, so, i think there must be a cleaner solution, so i will appreciate if a more experienced developer takes a look at my code and proposes a better solution.
As for the 5-10 second hang, it is (unexpectedly) caused by that line with "sleep 15" at the end of addon.d script. If it really annoys you, you can comment it out along with the line, where force-encrypt-toggler is called directly (not through the helper script). Updating will be a bit faster than, but if CM devs ever decide to flash boot image prior to calling addon.d scripts, you /data will be silently encrypted.

Download :: For the lazy
force-encrypt-toggler-1.0-flounder.zip : http://goo.gl/N4rZDk
force-encrypt-toggler-1.0-flounder-dbg.zip : http://goo.gl/4nXmkD - this one creates log files in /cache every time
force-encrypt-toggler-1.0-linux.tar.gz : http://goo.gl/hDFNOY - to be used on a desktop to patch arbitrary boot.img

While there was zero discussion in this thread, goo.gl tells me that there was some downloads, so someone might be actually using my small mod. If so, they might notice that it got broken around one month ago. So i decided to share a fixed version. See updated links in the description (links in the USBhost's post above are for the old version, if you wonder).
If you currently have v1.0 installed, you can just flash v1.1 over it. Note however, that if you was flashing recent nightlies while using v1.0, you /data probably have been silently re-encrypted. Also, if you current boot image is patched by v1.0, the initial patching by v1.1 during zip installation will fail, but it should work during system updates afterward. Flash stock boot image and try again if you want to be sure.
The reason for v1.0 malfunction was that around a month ago CM13 stopped shipping busybox in favor of toybox. New version is only compatible with CM nightlies >= 20160110. Also you need TWRP >= 2.8.7.1.

I never took notice to this thread before until your post in the FED thread. I am going to keep an eye on it as I have been issued lately with the FED patch saying that my device is not supported (Nexus 9 Wi-Fi). Hopefully I will have better luck with this. Thank you for sharing your.

[DEV] AoL - Android ON Linux - GM-T810 Edition [CLOSED]

This project is closed due to lack of interest. I'm leaving the files and instructions here for any that want it...
One last present.... See here for a working Arch-AoL MircoSD rootfs.... Just extract it to the ext4 partition of the MicroSD (Step 1) and install the modified kernel (Step 3).
AoL - Android ON Linux - GM-T810 Edition - MicroSD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background
This project was started on the Lenovo Yoga Tab 2 by @ionioni. Over the past couple months he managed to unlock the bootloader and get Linux running natively with Android in the chroot. See his thread here for more details and the real reasons why we would want this. Having Linux in charge makes for a much nicer environment for me. Also having REAL Linux on the go helps with my day to day work.
MicroSD Install of:
AoL - Android ON Linux - GM-T810 Edition
You must be rooted, and have TWRP and Busybox installed
1) Format MicroSD using Linux gparted:
--MAKE SURE IT IS YOUR MICROSD CARD(/dev/mmcblk..) YOU ARE WORKING WITH!!
--Delete all partitions of MicroSD
--Device>>Create partition table - Select ms-dos
--Partition>>New - Select fat32 and the size you want
--Partition>>New - Select ext4 and the rest of the card (suggest ~4-8GB)
--Click the checkmark...
Click to expand...
Click to collapse
2) Install the rootfs on Partition 2 of the MicroSD:
(The following is for an Arch AoL install. Someone else will need to do other Distro's)
**The following is run as root not sudo in a terminal on your Linux PC**
--"su"
--Create and cd into a temp directory
--Download - "wget http://archlinuxarm.org/os/ArchLinuxARM-armv7-latest.tar.gz"
--Download - "wget https://busybox.net/downloads/binaries/latest/busybox-armv7l"
--Download and extract - aol_inits.7z
--Download aol_cold_initramfs.cpio.gz
--cd to root_of_MicroSD_partition2
--"tar -xpvf /path/to/temp_directory/ArchLinuxARM-armv7-latest.tar.gz ."
--"cp /path/to/temp_directory/busybox-armv7l usr/bin/busybox"
--"cp /path/to/temp_directory/aol_inits/init.stage* etc/"
--"chmod a+x usr/bin/busybox etc/init.stage*"
-- "mkdir -p android android/hot android/cold"
--"cd android/cold"
--"gzip -dc /path/to/temp_directory/aol_cold_initramfs.cpio.gz | cpio -idv"
--"cd ../../" (Root of sdcard)
--"rm etc/resolv*"
--"echo "nameserver 8.8.8.8" > resolv.conf"
--"echo "nameserver 8.8.4.4" >> resolv.conf"
--"echo "inet:x:3003:root" >> etc/group"
--"echo "net_raw:x:3004:root" >> etc/group"
--"echo "PermitRootLogin Yes" >> etc/ssh/sshd_config"
--cd out of the MicroSD and do a sync
--Remove MicroSD and place into your tablet
Click to expand...
Click to collapse
3) Installing the aol_kernel:
***YOU MUST DO THIS FIRST***
***Goto SuperSU app and do a "cleanup for reinstall from Playstore"
***Reboot
***DO NOT REINSTALL SuperSU app (or be ready to flash a stock image in ODIN and start all over)
--
--Extract aol_external_sm-t810.7z to /sdcard
--Reboot to TWRP (backup if you wish)
--Install>>Image file
--Select aol_external_sm-t810.img and flash
--Reboot and profit.
Click to expand...
Click to collapse
After AoL boots you will need to log in to ssh localhost, port 22 (Arch install user:alarm pass:alarm) and run the following as root(pass:root):
--"su"
--"gpasswd -a alarm inet"
To go back just need to reflash your old kernel...
If you would like a X11 Desktop (LXDE, XFCE4...) see this thread.... Either use the user alarm or create a new one...
I will be crediting all sources here:
@ionioni - Master Linux/Android chef
@BigBot96 - Rooting tutorial
@ashyx - GTS2 Root, permissive kernel and Recovery Threads, also the permissive custom kernel
Blog @ http://whiteboard.ping.se/Android/Debian - Great hints
@osm0sis - For his AIK
Click to expand...
Click to collapse

Dev Updates
01/17/2016
- Data corruption
At this point the internal installer does its job resizing and creating the needed new partitions. The issue now is the same one I encountered on my first install. The data partition (even if wiped) ends up corrupted. TWRP can't even mount it or fix it. The only solution to fix the error and finish the install process has been to flash the stock recovery. This extra step is not what I want to release to the "public". Until I find a solution I will not be releasing this.
Anyone that "has" to have this installed and doesn't mind the extra 5 minutes of work can PM me and I'll fill you in on the details....
I will release the MicroSD install as it doesn't require any internal partitioning. I will only support Arch at the moment because that is my distro of choice....
12/22/2015
- SUCCESS!!!! AGAIN!!!
After much testing and then a total fail (partitions got corrupted), I now have a working internal AoL install on my tablet. I resized /data (mmcblk0p22) and added 2 new partitions (mmcblk0p23 + 24).
After I work out the kinks in the installer I'll post it. The internal installer will also need a fresh rootfs but I will help with that via a menu driven script similar to my AKBI-TF700 project. It will be better to do the two separately, especially if someone just needs to split their /data partition ( @moonbutt74).
12/16/2015
- SUCCESS!!!!
Apparently AIK was the ticket!!! I also had a bad rootfs (someone somewhere had said to use GPT for the sdcard... GRRR). Arch linux is now in charge and "letting" Android run on my tablet! I have to get the internet working from Linux (systemd issue...) but Android works flawlessly as before. Stay tuned!
EDIT:
- Ok, so I have a working rootfs and a working kernel (thanks to @ashyx (permissive kernel), @moonbutt74 for pointing me to AIK and @osm0sis for making AIK!!!!). I'll be packing up the rootfs as is (simple root and 1 regular user) and anyone who would like to try it shoot me a PM.
I'll run some testing but I'm confident this is a good build. I'll post a rootfs and kernel once at least 2 people PM me and try it... Also eventually my rootfs builder and kernel init's...
My new priority is repartitioning mmcblk0 to add 2 new partitions for Linux to be installed.
EDIT2:
- Posted the install instructions but no files until someone steps up to do a confirming test... Also I decided not to supply any rootfs as it is better (and easy) to build your own fresh.
12/11/2015
- Here is where I am at on the project. I am now setup to compile, pack and unpack successfully the kernel for the SM-T810. Unfortunately (I hate to keep saying that...), any time I modify or replace the ramdisk, it fails to boot. This is what I had thought would be the "easy" way using an externalsd install. All permissions and binaries check out. Grrr.
So, on the advice of my "Master Chef", I'm going to focus on an internal install. This requires taking some space from the /data partition to make 2 new internal partitions. This worked flawlessly on the YT2 and we think that will solve the init issue.
I am going to keep this on hold until @CTXz finishes his port of CM 12.1 to the SM-T710 and he ports CM 12.1 and more importantly CWM-recovery the SM-T810. I need adb access from recovery to do some "safe" initial formatting and the current TWRP does not support adb. Also CM will be a more generic install and will, I think, be more linux friendly...
So to the 350+ observers so far of this project... Stay tuned!
12/8/2015
-I've tried many ways but can't get a kernel to even try to boot. I even tried unpacking ashyx's permissive kernel and repacking it and it won't boot either. I don't have any experience building (or apparently modifying) kernels and no one has stepped up or shown interest. So regretfully this project is on hold. If someone wants to take over feel free to PM me I'll give you everything you need to get an sdcard install running, you just need the "secret" to packing this kernel.
12/7/2015
- So got all my Linux rootfs ducks in a row (binaries and scripts in place). Still can't get the kernel to boot past the first splash... I'm not a kernel man but I guess I'll need to hit the books and see what I can do...

Reserved 2
This one too...

Thank you for your time and effort. I would be happy to test once you get to that in development.
Take care and have a wonderful day.

I went ahead and got an sd install setup. I can't get the kernel to flash in ODIN though. I'm trying to look for information about the kernel build, are they still signed even though the bootloader is unlocked... Probably. I'll have to ask around and find how to sign it...

workdowg said:
I went ahead and got an sd install setup. I can't get the kernel to flash in ODIN though. I'm trying to look for information about the kernel build, are they still signed even though the bootloader is unlocked... Probably. I'll have to ask around and find how to sign it...
Click to expand...
Click to collapse
Unsigned images can be flashed with odin if the bootloader is unlocked.
It's more likely to be something with the way it's been packaged.
How did you repack the boot.img, what is the error in Odin?
Wouldn't it be easier to flash the boot.img with recovery?

ashyx said:
Unsigned images can be flashed with odin if the bootloader is unlocked.
It's more likely to be something with the way it's been packaged.
How did you repack the boot.img, what is the error in Odin?
Wouldn't it be easier to flash the boot.img with recovery?
Click to expand...
Click to collapse
Yes I realize that. There was some there was something wrong with the way I repacked it. It flashed this time but didn't boot. And I do plan on flashing recovery I am just testing and playing around right now. Thank you!
From my LG-G4, Rooted running Stock 5.1

Dev Update
12/7/2015 - So got all my Linux rootfs ducks in a row (binaries and scripts in place). Still can't get the kernel to boot past the first splash... I'm not a kernel man but I guess I'll need to hit the books and see what I can do...
All updates HERE

workdowg said:
12/7/2015 - So got all my Linux rootfs ducks in a row (binaries and scripts in place). Still can't get the kernel to boot past the first splash... I'm not a kernel man but I guess I'll need to hit the books and see what I can do...
All updates HERE
Click to expand...
Click to collapse
@ashyx - Didn't want to bother you with a PM... I tried unpacking and immediately repacking your kernel to test my mod and it doesn't boot either. How is the kernel packed for this device? Thanks.
Edit: I'm thinking it may be the ram base address? Umkbootimg doesn't spit out that on this kernel...
Sent from my SM-T810 using Tapatalk

I've tried many ways but can't get a kernel to even try to boot. I even tried unpacking ashyx's permissive kernel and repacking it and it won't boot either. I don't have any experience building (or apparently modifying) kernels and no one has stepped up or shown interest. So regretfully this project is on hold. If someone wants to take over feel free to PM me I'll give you everything you need to get an sdcard install running, you just need the "secret" to packing this kernel.

Update - 12/11/2015
12/11/2015 - Here is where I am at on the project. I am now setup to compile, pack and unpack successfully the kernel for the SM-T810. Unfortunately (I hate to keep saying that...), any time I modify or replace the ramdisk, it fails to boot. This is what I had thought would be the "easy" way using an externalsd install. All permissions and binaries check out. Grrr.
So, on the advice of my "Master Chef", I'm going to focus on an internal install. This requires taking some space from the /data partition to make 2 new internal partitions. This worked flawlessly on the YT2 and we think that will solve the init issue.
I am going to keep this on hold until @CTXz finishes his port of CM 12.1 to the SM-T710 and he ports CM 12.1 and more importantly CWM-recovery the SM-T810. I need adb access from recovery to do some "safe" initial formatting and the current TWRP does not support adb. Also CM will be a more generic install and will, I think, be more linux friendly...
So to the 350+ observers so far of this project... Stay tuned!

workdowg said:
12/11/2015 - Here is where I am at on the project. I am now setup to compile, pack and unpack successfully the kernel for the SM-T810. Unfortunately (I hate to keep saying that...), any time I modify or replace the ramdisk, it fails to boot. This is what I had thought would be the "easy" way using an externalsd install. All permissions and binaries check out. Grrr.
So, on the advice of my "Master Chef", I'm going to focus on an internal install. This requires taking some space from the /data partition to make 2 new internal partitions. This worked flawlessly on the YT2 and we think that will solve the init issue.
I am going to keep this on hold until @CTXz finishes his port of CM 12.1 to the SM-T710 and he ports CM 12.1 and more importantly CWM-recovery the SM-T810. I need adb access from recovery to do some "safe" initial formatting and the current TWRP does not support adb. Also CM will be a more generic install and will, I think, be more linux friendly...
So to the 350+ observers so far of this project... Stay tuned!
Click to expand...
Click to collapse
How do you repack the boot.img. Usually the kitchen is fault. Try carliv image kitchen. Works almost always.

CTXz said:
How do you repack the boot.img. Usually the kitchen is fault. Try carliv image kitchen. Works almost always.
Click to expand...
Click to collapse
I'll definitely try it...
But I'm almost positive because I'm able to pack and then repack any working kernel it is my changes that aren't being liked... The ramdisk init is actually a shell script and it makes calls for /dev/mmcblk1p2 which may be called something else at boot before Android starts (Android names it /dev/block/mmcblk1p2).

workdowg said:
I'll definitely try it...
But I'm almost positive because I'm able to pack and then repack any working kernel it is my changes that aren't being liked... The ramdisk init is actually a shell script and it makes calls for /dev/mmcblk1p2 which may be called something else at boot before Android starts (Android names it /dev/block/mmcblk1p2).
Click to expand...
Click to collapse
Maybe multirom would be usefull for such cases. If I remember right you can decide what partition to boot from multirom itself. Anyways, i am building CM recovery now to see if I have root access.

Nice utility... He put some work into that... But it still boot loops... Thanks though, it will come in handy.

Hmm CM recovery still saying
33005960dd4672df offline
Guess i'll have to build another recovery then.
I was hoping that selinux was the fault. I will still check the kmsg if it is kernel related.
By the way, realized this right now. I remember getting adb in LPM mode. So while the rom didn't work, instead of reflashing all, I just booted into LPM and from there I had adb. You need to set your default.prop for that.
---------- Post added 12-12-2015 at 12:10 AM ---------- Previous post was 11-12-2015 at 11:52 PM ----------
Ok little update here. I got adb working on the stock recovery. There still no root access tough. I'll replace it with a rooted kernel.

CTXz said:
Hmm CM recovery still saying
33005960dd4672df offline
Guess i'll have to build another recovery then.
I was hoping that selinux was the fault. I will still check the kmsg if it is kernel related.
By the way, realized this right now. I remember getting adb in LPM mode. So while the rom didn't work, instead of reflashing all, I just booted into LPM and from there I had adb. You need to set your default.prop for that.
Click to expand...
Click to collapse
The only info I could fine on LPM mode is for mobile sim cards.... What exactly is this you are refering to...
Ok little update here. I got adb working on the stock recovery. There still no root access tough. I'll replace it with a rooted kernel.
Click to expand...
Click to collapse
Sounds like progress... Not for me... well a little bit. I'm not having any issues modifying the default.prop or any .rc script in the ramdisk and repacking so the kitchen is fine. Although they all boot, none of my changes did anything though.

workdowg said:
The only info I could fine on LPM mode is for mobile sim cards.... What exactly is this you are refering to...Sounds like progress... Not for me... well a little bit. I'm not having any issues modifying the default.prop or any .rc script in the ramdisk and repacking so the kitchen is fine. Although they all boot, none of my changes did anything though.
Click to expand...
Click to collapse
With LPM I mean charging mode, with the big battery. Usually it would gain me full adb access but it would take about a min until adb started.

CTXz said:
Hmm CM recovery still saying
33005960dd4672df offline
Guess i'll have to build another recovery then.
I was hoping that selinux was the fault. I will still check the kmsg if it is kernel related.
Click to expand...
Click to collapse
Well I edited the ramdisk on ashax twrp (based on the nexus 9) and before it couldn't find adb devices at all. Now I get the same error you are:
Code:
3300123a6b6982cd offline
Maybe something in the kernel build stopping it from working???

workdowg said:
Well I edited the ramdisk on ashax twrp (based on the nexus 9) and before it couldn't find adb devices at all. Now I get the same error you are:
Code:
3300123a6b6982cd offline
Maybe something in the kernel build stopping it from working???
Click to expand...
Click to collapse
I thought the same. Strangely enough stock recovery seems to wnter adb fine if the flags are set unsecure in the default prop.