Develop Bugs

[11.05.2011][CF-Root v3.3] JJ*, JM*, KA*, JQ1 - su+busybox+CWM3/RFS

This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod (CWM3) recovery
(1) THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THIS ENTIRE POST!
(2) THIS IS ONLY FOR GSM TAB. IT MAY WORK ON OTHERS VARIANTS, BUT YOU'RE ON YOUR OWN THERE !
(3) I have moved the description for the old FROYO CF-Root's to the next post, but the downloads for the FROYO CF-Root's are still attached to THIS post. The contents of THIS post however are about the GINGERBREAD CF-Root's
(4) MAKE SURE YOUR PHONE CAN ENTER DOWNLOAD MODE USING THE KEYCOMBINATION WHILE BOOTING BEFORE FLASHING CF-ROOT (or anything, really)
Donate
There have now been over 200.000 downloads of CF-Root for various devices, and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!)
Features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Root
- Superuser 2.3.6.1
- Busybox v1.16.2androidminimal (from CWM)
- Integrated CWM 3.0.0.5 / RFS
Instructions (short)
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
Instructions (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Instructions (alternative if you are already running CF-Root 2.5 or newer)
- Copy the zip file to your SD card
- Stop sharing SD card with computer over USB, unplug the cable, etc
- Applications -> CWM -> Flash kernel. Select the ZIP file on your SD card.
- Done
Other kernels
Replacing CF-Root with other kernels and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while CWM will be lost (unless the other kernel also includes it), but there should not be issues. The CWM Manager and Tweak Manager apps may remain, but they probably won't do anything useful.
CF-Root is made to be applied on a stock kernel. Going from a lagfixed kernel to CF-Root usually does not work. Unlagfix first.
ClockworkMod
CF-Root includes a special version of CWM3, modified to work with RFS. CWM3 by default does not support RFS, koush' versions are all based on ext4. The RFS compatibility is done with heavy scripting. CWM3 is also recompiled from source with some slight modifications to handle key input correctly.
CF-Root/CWM3 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
- Booting into recovery will immediately give you CWM. The standard recovery will only be started if a Samsung package is detected.
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
CWM Manager
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011) and beta. You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to CWM
- Backup firmware
- Restore backups
- Delete backups
- Install APKs
- Flash CWM3 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP)
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility ! At this version of CWM Manager this does not produce errors, it just doesn't do what you expect it to
Tweak Manager
CF-Root includes a number of tweaks that are applied on startup. A "Tweaks" application is included you can use to select which tweaks to apply.
Ext4 Manager
Ext4 is currently NOT supported on Gingerbread for the Galaxy Tab, unlike CF-Root for the Galaxy S.
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed.
Custom boot animations and binaries (note: broken in 3.2, fixed in 3.3)
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
And custom boot binaries:
- /data/local/bootanimation.bin
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Download
LOOK WELL AT THE FILENAMES, MAKE SURE YOU ARE GETTING THE RIGHT VERSION !
CF-Root-TAB-KA1-v2.2.zip
CF-Root-TAB-JME-v2.2.zip
CF-Root-TAB-JJ7-v2.2.zip
CF-Root-TAB-JMG-v2.3.zip
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip

Old FROYO CF-Root's
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THIS ENTIRE POST!
THIS IS ONLY FOR GSM TAB. IT MAY WORK ON OTHERS VARIANTS, BUT YOU'RE ON YOUR OWN THERE !
Features
- Root
- Superuser 2.3.6.1
- Busybox 1.16.2 "androidminimal"
- ClockworkMod 3.0.0.0 (RFS) included as standard recovery
- The same Samsung kernel, just with some added files. The kernel is not recompiled.
Instructions (short)
- Make sure, if you just flashed a ROM, to boot this ROM at least once before flashing CF-Root ! (if you don't do this, ROM-based update scripts may not run)
- Flash CF-Root-.....tar (from the attached zip) as PDA in ODIN 1.7, without repartition. Done.
Instructions (long)
- Make sure, if you just flashed a ROM, to boot this ROM at least once before flashing CF-Root ! (if you don't do this, ROM-based update scripts may not run)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-.....zip (note: it contains a tar file, WinRAR and WinZIP may also extract these... if you end up with a zImage, you extracted twice, instead of once)
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-.....tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Must know
- It is possible you have a protected bootloader, see this thread, and check if you have a protected bootloader. CF-Root does NOT work on protected bootloaders.
- This is an RFS version of CF-Root, if you have used Koush' CWM and your filesystems have been converted to Ext4, CF-Root will NOT work. You need to reflash a full stock ROM with RFS filesystem to use CF-Root.
- If you are using a lagfix, CF-Root will NOT work!
Root
As normal, "su" can be used to get root if your device is fully booted. If not, for example in recovery, you can use the "rootsh" command.
BusyBox
The included busybox version is 1.16.2, this comes from CWM3. It is NOT needed to install or upgrade BusyBox from Market. In fact, I strongly advise against it.
ClockworkMod 3 / RFS
CF-Root for the Galaxy Tab actually includes ClockworkMod v3 (unlike CF-Root for the Galaxy S) as the default recovery. Booting into recovery will give you CWM3.
This is a heavily modified version of Koush' original CWM3 for the Tab, which uses RFS and has been extensively tested. This took a LOT of work!
Main features (differences from Koush' version):
- Uses RFS instead of Ext4 - no filesystem conversion needed
- Nandroid is fully operational without file corruption
- Backups are stored on internal SD-card
- .android-secure (apps on external SD-card) is backed up and restored
Controls:
- Volume up/down to scroll through the list of options
- Power button to select an item
From version 2.3, a "CWM" entry is listed under applications to reboot into CWM, for your convenience
Important note
A full nandroid restore also restores the kernel from the backup. This will overwrite the CF-Root kernel, if you've made the backup using a different ROM or kernel. Use "advanced restore" to restore only pieces.
A trick:
When upgrading between ROMs, I usually make a nandroid backup before the upgrade, then after flashing the ROM, use "advanced restore" in CWM3 and restore only "data". This often just works. It can cause issues, but it's a neat trick to keep your data and settings between ROMs.
ROM Manager
This version of CWM3 is NOT fully compatible with ROM Manager.
Some things work, some things don't. Really I'd advise to just use CWM from recovery manually.
First time installing ROM Manager, it'll tell you to flash CWM, just pick one of the Galaxy Tab versions and don't worry, it won't be used.
To get into CWM, just select the "reboot into recovery" option.
None of the commands that actually do something in recovery work. For example, you can manage your backups (rename, delete), but the backup and restore options don't work. They will just boot into CWM, and you still have to select backup or restore manually.
If you've used CF-Root 1.3 and 1.4
Major difference: backups are now stored on internal SD-card. Simply move the "clockworkmod" folder from external SD-card to internal SD-card to get access to your old backups. Keep in mind that a restore overwrites the kernel (CF-Root) again, as stated above.
Donate
Buy me a beer, click here - I appreciate it! If you're not going to donate, at least use the thanks button!
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. This is a continuation of my CF-Root for SGS.
Downloads
You will find several files listed. There are for different ROM families.
Go to Settings -> About phone -> Build number. It should say something like FROYO.xxyyy. yyy will be something like JJ1 or JMA. This is the part we are interested in, and would be the JJ* and JM* "family" of ROMs. From the downloads, simply pick the latest file that matches this!
The actual file name notes which version the kernel was taken from. Different kernels from the same family usually work fine.
Is your family of ROMs not listed ? Post in this thread, maybe I can make you a version. You'll have to guinea-pig for testing, though!
( pre-2.2 : 666 )

Changelogs
11.05.2011 - v3.3
- Custom bootanimations were broken in 3.2, now fixed
11.05.2011 - v3.2
- Ported all the updates from the latest SGS CF-Root to SGT:
--- Custom CWM 3.0.0.5 modded for dual EXT4/RFS operation
--- Added CWM Manager application (use this instead of ROM Manager, which is NOT compatible)
--- Added Tweak Manager application
--- Custom boot / init scripts support
--- Custom boot animation and binaries support
--- Different busybox versions are now installable
02.01.2011 - v2.3
- A "CWM" entry is listed under applications to reboot into CWM, for your convenience
14.01.2011 - v2.2
- Startup and shutdown sounds now always removed from /system when patching, to make sure there is space to put SuperUser.apk and su
- Patch status now saved in /system instead of /data. Fixes an issue with reflashing the ROM and re-installing CF-Root, which didn't always work before if you didn't wipe /data.
- Patch status from previous CF-Root versions is now removed
11.01.2011 - v2.1
- If /system is full, CF-Root will try removing the startup and shutdown sounds, then try rooting again. This should solve the issue of some people not actually getting root after flashing.
- "rootsh" command now only works in recovery, no longer in fully booted mode. Prevents sneaky programs from gaining root without you confirming.
- "sh" is now busybox shell only in recovery, and normal shell in fully booted mode. Fixes various issues both with normal commands as well as 3rd party programs.
- "reboot" command now works.
- Commands like "am" and "pm" now work, this allows Eclipse to work with the Tab again.
- Reduced size of zImage. May help people who have trouble flashing.
If you are running 2.0 and it is working fine, there is no strict need to upgrade, unless one of the things above is giving you problems.

Dear chainfire,
Thanks a lot for your efforts. I will try this and post result when i find some spare time.
Kind Regards,

Thanks man any chance for P1000JPJK2

on JM6 here failed and gave me the phone error and no boot. Had to run just pit 1 hidden file with repartition to get it to boot correctly again.
I also tried the euro bootlloader, it installs but then reboots to the galaxy tab screen and stays there.
Lordao

I will give this a try and let you know how guys went.
Update : It completely failed.
{
"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"
}
Oh great, now i cant find out how to download heimdall, to push back my old kernel. Great !

sedde said:
I will give this a try and let you know how guys went.
Update : It completely failed.
Click to expand...
Click to collapse
Same error as me
Lordao

Me too
With fresh Flashed JMD also Error.
Have tryed both JMD Versions.
To bad
Hope you bring it to work.

So all if you are having a flashing error ? That's so weird... will see what I can do about it. Has anyone been able to boot it yet ?
EDIT: From a quick look at other threads about this issue, apparently you need to KEEP ODIN OPEN and keep reflashing until it works. Strange I've never ever seen this error before on my SGS or SGT.

Chainfire said:
So all if you are having a flashing error ? That's so weird... will see what I can do about it. Has anyone been able to boot it yet ?
EDIT: From a quick look at other threads about this issue, apparently you need to KEEP ODIN OPEN and keep reflashing until it works. Strange I've never ever seen this error before on my SGS or SGT.
Click to expand...
Click to collapse
After flashing it once, if you try again you are getting stuck in SetupConnection and its doing nothing. I am willing to try it since i just got a backup of my whole thing, but i cant find heimdall to re-install the kernel back so i have to odin it all the time.

Chainfire , you are the man
It works pretty well with JM6 rom
My previous phone was galaxy s ... so I am quiet aware how to flash...
Next step , will be to update the clockwork recovery as ( access to external SD)
But well done for this release .... It will safe my time to manage my custom rom made

Which Busybox version did you use?

its working on JM4?

same fail error as others have received. Tried both JMC and JM6. Thanks for the effort - keep on trying! Glad to continue to test.

doesnt work on my tab (JM6)

Does not work here either with JMD
Tried to flash it with Odin(WinXp) and Heimdall(ubuntu).
Flashing back the original Kernel with heimdall worked fine.
Sent from my GT-P1000 using Tapatalk

Good news everyone! I've finally been able to replicate the issue. Now trying to find a fix (or WHY the problem occurs )

It seems that CWN doesn't flash on devices that has boot.bin of JJM6 or later...

Yeah I just figured the same thing. I wish I hadn't tried to find out, because I had a JM6 _without_ this problem, now I do have it.
The latest JMx ROMs install a new bootloader that uses signature verification. After flashing, it is impossible to flash sbl, boot, or zImage, if they do not have the correct signature.
That is also why many can no longer downgrade either, the old ROMs also don't have these signatures. If future official ROMs do not have them either, well then, we're all in a very big mess, because we will never get away from these JMx ROMs. We'll be stuck.
I've tried all the tricks listed in the various topic to downgrade, but none of them work if you have done full flash. Major bummer.

[DEV][02/May/2015]unOFFICIAL TWRP|v2.8.6.1

Introduction:
---------------------
Team Win Recovery Project 2.X, 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:
---------------------
{
"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"
}
Notice:
---------------------
The attached recovery images were compiled from TWRP's open source.
They were only tested on a European version of the HTC-HD2 powered by cLK bootloader.
The performance on devices powered by MAGLDR bootloader should be considered untested.
Disclaimer:
---------------------
As usual, use at your own risk. TeamWin, arif-ali or kokotas is not responsible for anything bad that may occur from using twrp2.
Nobody appointed me to compile TWRP for HD2. I'm not TeamWin's member. It just happened...
If anyone else is willing to do it and probably do it better I will be glad to step aside,​
Key Features:
---------------------
* Ability to save custom recovery settings
* 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)
* Basic file manager (copy, move, delete, and chmod any file)
* OpenRecoveryScript scripting engine
* On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
* ADB sideload functionality from AOSP
* Pseudo-terminal emulator
* Ability to backup large partitions (size>4GB) by splitting the backup archive.
Mainline TWRP Change-Log:
---------------------
Follow up the changes in mainline project at TeamWin's page : http://www.teamw.in/project/twrp2.
HD2's TWRP Change-Log:
---------------------
Initial TWRP versions
List of changes
TWRP v2.4.0.0.r1 @ 2013.01.17
Compiled version based on mainline code (v2.4.0.0Alpha).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix getting fs-type from a partition created with a label.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.4.4.0 @ 2013.04.03
Compiled version based on mainline code (v2.4.4.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.5.0.0 @ 2013.04.10
Compiled version based on mainline code (v2.5.0.0).
NOTE: Compiled unmodified source code refused to boot! So I had to change a little bit more this time, just to get it to boot up.
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.0.0 @ 2013.07.09
Compiled version based on mainline code (v2.6.0.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.1.0 @ 2013.08.31
Compiled version based on mainline code (v2.6.1.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.3.0 @ 2013.09.14
Compiled version based on mainline code (v2.6.3.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.8.6.0 @ 2015.04.30
Compiled version based on mainline code (v2.8.6.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
Fix some ui bugs in the default theme.
TWRP v2.8.6.1 @ 2015.05.02
It is version 2.8.6 with a quick fix over a bug in the default theme engine that was causing an error during each boot.
Installation:
---------------------
Make sure you have adb and fastboot working. Please don't ask here questions about this - a simple web search will be enough to help you.
Make sure that the size of the 'recovery' partition is enough for the image to fit.
Make sure the name of the recovery *.img file is the one you use in the commands or in flash.cfg
[cLK/MAGLDR]
Flashing the zip file from Recovery
Download zip file to your computer and copy to /sdcard.
Reboot phone into recovery.
Select to install the zip file from your /sdcard.
Reboot Phone into recovery as normal.
[cLK/MAGLDR]
Flashing the *.img file while booted in Android
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Execute the commands:
Code:
adb push recovery-leo.img /sdcard/recovery-leo.img
adb shell erase_image recovery
adb shell flash_image recovery /sdcard/recovery-leo.img
Reboot Phone into recovery as normal.
[cLK]
Flashing the *.img file while in fastboot mode(cLK menu)
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Reboot phone into cLK menu (fastboot mode).
Execute the commands:
Code:
fastboot erase recovery
fastboot flash recovery recovery-leo.img
fastboot oem boot-recovery
[MAGLDR]
Flashing the *.img file while in USB Flasher mode(using DAF.exe)
WARNING!!! This will erase your current Rom on NAND too!
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
Open the folder you have the recovery and place DAF.exe and flash.cfg in that same folder.
Edit flash.cfg according to required recovery partition size:
Make sure the .img file has the name that flash.cfg specifies!!
i.e. If the *.img file is named recovery-leo.img and min-required-size = 6MB then the flash.cfg could be:
Code:
misc ya 1M
[U]recovery rrecov|ro|nospr 6M recovery-leo.img[/U]
boot yboot|ro 5M
system ya 150M
cache ya 2M
userdata ya|asize|hr allsize
Check out the info about flash.cfg.
Connect the device to the computer via usb, enter MAGLDR and select USB Flasher option.
Right click on DAF.exe and select Run as Administrator.
Click [NEXT] when asked and wait to finish.
Download:
---------------------
HD2_TWRP_2.8.6.1.zip
md5: 93972887cfd3e017d16a09a74900496d
Info: You need to have a recovery partition at least 9 MB to fit the img
HD2_SD_TWRP_2.8.6.1.zip
Info: Extract to the root of your SD Card
Old Releases:
---------------------
HD2_TWRP_2.8.6.0.zip
md5: 882aaa25d9ff17613c64efe53c127d3a
HD2_SD_TWRP_2.8.6.0.zip
HD2_TWRP_2.6.3.0.zip
md5: 53c9522dbaa5ab465874258c01758143
HD2_SD_TWRP_2.6.3.0.zip
HD2_TWRP_2.6.1.0.zip
md5: d66519b22d219865d741389013ea034f
HD2_SD_TWRP_2.6.1.0.zip
HD2_TWRP_2.6.0.0.zip
md5: 185e6b34699e4cdb176780695e9e06aa
HD2_SD_TWRP_2.6.0.0.zip
HD2_TWRP_2.5.0.0.zip
md5: 9604cb28b3e91047abdc3a63d5b827df
HD2_SD_TWRP_2.5.0.0.zip
HD2_TWRP_2.4.4.0.zip
md5: b24bdf020b8ea3222c92df0644c88203
HD2_SD_TWRP_2.4.4.0.zip
HD2_TWRP_2.4.0.0_r1.zip
md5: 8bd2b557442c5af73d38f9e7a054b67a
HD2_SD_TWRP_2.4.0.0.r1.zip
HD2_TWRP_2.3.2.3.img
md5: ad8d1909d54c440f9b79eacad31910b9
recovery-twrp-leo-2.0.0RC0.1.img
md5: 6279a726b19a4ff2fccfe592e23b2e48
recovery-twrp-leo-2.0.0RC0.img
md5: e12fc48a863e4a2984d7fcf3b2cad50a
recovery-twrp-leo-1.1.1-3.img
md5: 6198e06b7ca85379e16acde4d9a19752
recovery-twrp-leo-1.1.1-2.img
md5: 52c51eee07c50a928341b22c3e2a60b6
recovery-twrp-leo-1.1.1-1.img
md5: 4801f88e0d2a62b5a1c3d168a4116d0d
recovery-twrp-leo-1.1.1.img
md5: 7fa63b205facf64bd69d805acf34ae8c
recovery-twrp-leo-1.1.0-2.img
md5: 8bd05c6b1e25bd8cf410e308bed23fe5
recovery-twrp-leo-1.1.0.img
md5: 449b06b28f73e996a33e06c047b51b98
Special Thanks to:
---------------------
* Core twrp 2 development team: agrabren, Dees_Troy, ViViDboarder, and AssassinsLament
* Toastcfh – for his underappreciated dedication to the community
* s0up and kevank for their hard work on the web side of things.
* The rest of Team Win: shift, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, and eyeballer
* Amon_RA - for his great Recovery
* Koush - for his dedication to the community and ClockworkMod
* For all the help with devices and testing Akmzero, arif-ali, Evil_DevNull, gus6464, Jesusice, Pyrostic, [R], and Rootzwiki
* As always thank you to the Team's supporters and the Android Community.

[22 Dec 2011][RECOVERY] Team Win Recovery Project (twrp) v2.0.0RC0.1
Original OP

FAQ
FAQ from TWRP team is here
Q: Does Rom Manager work with this
A: No
Q: Will you be providing support for Rom Manager
A: Maybe, when I have time, or if Team View release it before me
Q: Does it work with MAGLDR
A: Yes, use AD recovery
Q: Does this mean we cannot easily install ROMs
A: Yes, but the code for that may be added at later date, this is Work In Porgress
Q: Will reboot to Recovery work as normal
A: Yes
Q: Does Off-mode charging still work
A: Yes, same as CWM on cLK. it will charge when off, but pressing the power button while charging will not turn the phone on
Q: I got "failed with error: -1"
A: make sure the recovery size is 5M, anything below that is not supported, You can check this by running adb cat "/proc/mtd | grep recovery"

Changelog
ChangeLog
---------------------
2011-12-22 - v2.0.0RC0.1
Fix issues with wiping data on MTD devices (thanks Dees_Troy)
2011-12-18 - v2.0.0RC0
Initial release of twrp 2
Full GUI touchscreen with buttons and XML engine
Fixed sdcard free space checking
Fixed bugs with MD5 zip file checking
Now check more places for a serial number
Too many fixes versus twrp 1.1.1 to list
2011-10-11 - v1.1.1-3
Fix sd-ext issues (no longer use auto FS, and use ext3)
2011-10-08 - v1.1.1-2
Fix sd-ext restore issue
Fix issue with SD repartition and the send button again
2011-10-08 - v1.1.1
fixed fix permissions bug
fixed md5 checking for zip install
2011-10-07 - v1.1.0-2
Changed the select key from power to call button
2011-10-07 - v1.1.0-1
Changed buttons so that it works with the HD2
HD2 Initial Release
2011-10-05 - v1.1.0
brand new nandroid process with more error checking and supports ext3/ext4 types of devices
sdcard partitioning is available for devices with a sdcard (courtesy of koush from CWM source)
can choose multiple zips before flashing and they will flash in the order chosen
files & folders are sorted case insensitive
added option to sort zips by file date instead of file name
can apply themes and change time zones without rebooting for instant gratification
saved settings will now persist through version changes
added myn's warm theme with color codes courtesy of myn
added option to wipe system, data, and cache with rm -rf during a nandroid restore to maintain existing file system settings like block size
added options for automatic md5 checking of zips
twrp spam off by default which makes nandroids up to 10x faster
2011-08-05 - v1.0.3
Added timezones that should cover everyone
Added twrp spam feature (twrp settings)
Added fix permissions (advanced menu)
Added wipe cache and dalvik into Flash Zip menu
Added copy recovery.log to /sdcard (advanced menu)
Added output spam/no spam to restores
Added mke2s prebuilt to /sbin
Fixed SD-EXT issues, (no partition SD-EXT features yet)
Fixed EFS partition issues
Changed the way we do backups on mtd devices, which should fix any boot partition issues (we suggest making new backups if you have an mtd device, EVO4G,NS,NS4G,etc)
2011-07-31 - v1.0.2
Fixed SD-EXT issues
Added Format SD-EXT into format menu
Removed GAPPS support, CM7 automatically backsup and restores if you already have GAPPS installed. If you don't, just flash GAPPS zip
Fixed issue where when flashing a rom, rebooting brings you back to recovery. Auto reboot after successful flash should work great now!
Rearranged the format menu
2011-07-30 - v1.0.1
Initial release

Since I had Already started with the ports for the Recovery Themes...
This is the Link to New Thread.
Sory for Any Inconvenience this has caused you Arif...

Please Visit New Thread Here...
If you See any New themes that you would like me to Port please feel free to post on the Thread Linked Above...

tobiascrystal said:
No kidding, you are super fast! In your experience would you say that this has anything over cwm that you have learned getting it to work for us?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
It is customizable and has touchscreen capabilities.

wow very nice new features compared to clockworkmod...
Just installed few minutes ago, as far as I can tell, it seems all is working fine!
I might have a "small" request, is it possible to map the buttons just like in cwm? I didn't like the idea of using the end button that much...
---------- Post added at 01:51 AM ---------- Previous post was at 01:49 AM ----------
Ultimaex said:
It is customizable and has touchscreen capabilities.
Click to expand...
Click to collapse
Not just yet! This is 1.xx version based, the one you're refering with ts capabilities is 2.x based...

Kool... Now users will have a choice for more than one recovery on leo too... Al thanks to you cheers
And button customization would be good... I hate using the end key.. I fearing... My touch screen might get spoilt again ...
Sent from my HTC HD2 using XDA App

Seems to work great. I did a backup and restore and all went well thumbs up
Sent from my HTC Runnymede using XDA App

So right off the bat I'm impressed with the compression....does it allow us to produce our own zips? I'd like to rename my backups based on the rom they backed up instead of just a date/timestamp.

Nice........

Definitely a thing to look in future
Hope all the bugs are resolved soon
EDIT: - Thanked & RATED 5 STAR (All I can do as of now )

i don't understand how can i install this, becouse this is not zip file. Can you help me please

you install through adb. if you dont know what that is, do a search. there are many FAQ's about it. I would recommend doing plenty of research on it before diving right in.

if someone can do some pictures for me that would be great, as I don't have a camera, or a second phone which has a good quality camera
thanks

How's about battery charging, like clk?

huhjun said:
How's about battery charging, like clk?
Click to expand...
Click to collapse
It's the same as CWM
Edit: Added to FAQ

arif-ali said:
if someone can do some pictures for me that would be great, as I don't have a camera, or a second phone which has a good quality camera
thanks
Click to expand...
Click to collapse
Here you go with some phot... Not so high quality though... If you need better.. Tell me I will upload photos taken from my handy cam ... And what vabout changing end call button to call button
http://db.tt/afg0Szat
Sent from my HTC HD2 using XDA App

i got "failed with error: -1"

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Works with HTC Unlock Method (And s-off methods):
Tested after using htcdev.com's bootloader unlock method.
Please see the guides at the bottom of this post!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directoy, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: International HTC One, T-Mobile HTC One, Sprint HTC One, HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Let me know if there are any issues. Feel free to post the encountered issue and a link to the exact file that was flashed. Thanks for the support!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No.
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using the HTC method and gain root access.
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, wipe data as ROM requires and load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including WiFi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Unlock using the HTC method and gain root access.
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate the kernel zip file is contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

Great!!! Was waiting for it to work with the One
Thanks!!!

great!
(bookmark)

buy it and love it! no pc no more!

this looks awesome. Will this work on unrooted phone (i.e stock rom, stock recovery but unlocked and s off)
reason being i need to flash CWM but away from pc and also as on stock rom, no SU of course :good:

exocetdj said:
this looks awesome. Will this work on unrooted phone (i.e stock rom, stock recovery but unlocked and s off)
reason being i need to flash CWM but away from pc and also as on stock rom, no SU of course :good:
Click to expand...
Click to collapse
I do understand the convenience factor of not having to hassle with all the steps, including a computer, drivers, cables, etc.
Yes, to everything except root access is required by Android in order to have security access to write to the kernel or recovery partitions.
Reviewing the Android security model: if any installed application had access to replace the kernel or recovery without root access, this would seem a bit concerning!
Once root access is setup on the device, Flash Image GUI will allow you to flash custom recoveries and kernels without being at a computer!
Hopefully that makes sense and helps! Thanks for the feedback!

joeykrim said:
I do understand the convenience factor of not having to hassle with all the steps, including a computer, drivers, cables, etc.
Yes, to everything except root access is required by Android in order to have security access to write to the kernel or recovery partitions.
Reviewing the Android security model: if any installed application had access to replace the kernel or recovery without root access, this would seem a bit concerning!
Once root access is setup on the device, Flash Image GUI will allow you to flash custom recoveries and kernels without being at a computer!
Hopefully that makes sense and helps! Thanks for the feedback!
Click to expand...
Click to collapse
Thanks for clearing that up!!!! il make a purchase from the market when I can

exocetdj said:
Thanks for clearing that up!!!! il make a purchase from the market when I can
Click to expand...
Click to collapse
Of course. I do like the thread of thought you were on. Feel free to make any other suggestions or ideas for features and improvements as you use the app. I'm always open to improving and making a better experience!

joeykrim said:
Of course. I do like the thread of thought you were on. Feel free to make any other suggestions or ideas for features and improvements as you use the app. I'm always open to improving and making a better experience!
Click to expand...
Click to collapse
that would be f#cking awesome if possible but would be a pain in teh arse to implement im sure hahaha!!!! il have a play and keep you posted
however this would have helped me out in the past a few time in sticky situations had i heard of this lol

bcmon run?? htc one
HTC One cihazımdan Tapatalk ile gönderildi

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
It has LINUX/UNIX and MAC support!
​
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: ​Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
​
Download links: ​Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
​
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​
Known bugs/limitations: ​ - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​
Changelog: ​
Check the changelog for each release here.
​
Tutorials/FAQ: ​
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
Sources: ​The official and original repository can be found here.​
Bug reports/Feature requests: ​If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.​
Licensing: ​Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​
Tech and stuff: ​Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.​
Donations: ​Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
​
Disclaimer:​I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!

I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.

Dodgexander said:
I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.
Click to expand...
Click to collapse
It's a bug of the platform tools used in the package, the latest version of platform-tools should work. I will try to update it today.
Edit: Fixed in 1.3.1

New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu

[TWRP] [CORRECTION] [NORA] 64 bit TWRP for Moto E5

{
"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"
}
Introduction
I'm not a developer. After 4 days of messing with files I made this using AIK (Android Image Kitchen). It include files from different TWRPs. The theme is not mine. I provided all credits below.
As you guys know, our 64 bit TWRP from this thread is usable, but has some major bugs. Specially the touchscreen doesn't work & it's too big to flash. Now, here is a fixed twrp, no need to hassle with OTG & adb anymore!
Installation
Command-
fastboot flash recovery <filename>.img
Booting into TWRP-
- Power off
- Volume down + Power
- Keep pressing volume down until Recovery mode option comes
- Press power
Or,
Command-
adb reboot recovery
Install magisk.zip to avoid twrp being replaced by the stock recovery
Decryption
- Format data
- Install Disable_Dm-Verity_ForceEncrypt.zip
My works
I didn't know these steps from the beginning. I had to discover these. After 30-40 attempts & making 7 versions, the final result came out. To make the thread "To the point" here is what I did for the final one-
Touchscreen Fix :
- Extracted the old TWRP and started modifying it.
- Extracted plus-linux kernel, took "kernel image" & "kernel offset" from there. Inside TWRP, replaced kernel image & kernel offset with these new files. Touchscreen got fixed.
Minimal size :
The TWRP file must be 16 MB or less to be flashable for moto e5. This is because the device has very low recovery partition size. Making a 64 bit TWRP v3.7 under 16 MB was almost an impossible task. Here is how I finally did it-
- Removed txt files.
- Replaced /ramdisk/sbin/ folder with the sbin folder of official TWRP for Asus Nexus 7 2012 3G. This greatly reduced the file size & also made the TWRP v3.7. This happened because that TWRP is 32 bit. Means I used sbin from a 32 bit recovery. But our TWRP didn't become 32 bit because "bit" depends on split_image folder (specially kernel image file inside it)- not sbin folder. After this step, the twrp became 15.1 MB !
- Because of the previous step, a bug came where the cursor was always showing on the middle of the screen even though I was not using mouse via OTG. So I replaced cursor.png with a completely transparent image. So now, the cursor is hidden. And also you won't see cursor while using mouse. But no one need that, as touchscreen is fixed.
- Replaced files inside /ramdisk/twres/ with the files I got by extracting flashable zip of SHADOW"S BLACK THEME. We had a useless font that took almost 4 MB in our old TWRP. After doing the step, got the same font in 100 kb. But the overall file size increased because of new images in /ramdisk/twres/images folder. These images makes the recovery look better. After all, the size became 15.4 mb.
The steps look pretty much easier. But I had to suffer 3 days to discover them. I can briefly say that I ported a 32 bit twrp, used sbin from 8 TWRPs, tried to port 64 bit, removed languages and fonts, removed files from sbin folder, repacked & booted image every time after making every single changes, compressed images using online tools and many more !
I shared all these in case anyone finds them useful.
Bugs
- Adb push / pull (Sideload works though)
- Terminal
NB. Use adb version (boot only) to use adb features like push/pull & inbuilt terminal.
- MTP (Read File Transfer part)
File Transfer
MTP works fine. If you aren't able to use mtp & adb (in adb version), the problem is related to drivers. Here is the fix for windows (Sorry for linux / mac)-
1. Download Drivers.zip.
2. While in twrp, connect it with computer.
3. Go to device manager & uninstall devices related to adb - mtp. Adb device can be under "universal serial bus devices".
4. Disconnect the mobile.
5. In Device Manager, click on view & select "show hidden devices".
6. Again, Uninstall all drivers/devices related to adb - mtp.
7. Re-connect the mobile.
If windows doesn't install the drivers / the installed driver doesn't work, uninstall those and install working drivers manually-
How to install the drivers?
Install automatically- Run the exe file
Install manually (Recommended) - Device manager > Right click on the device > Update driver > Browse my computer >Let me pick > Have disk > Browse > Select the appropiate .inf file provided in each folder.
If you can't see mtp device under portable devices, try running the mtp driver exe file & reconnecting. However, adb fix is guaranteed. Good luck for MTP!
Download
adb version (boot only) - Drive / Mega
v2.1- Drive / Mega
v2.1 (stock)- Drive / Mega
v2- Drive / Mega
v1- Drive / Mega
Drivers.zip- Drive / Mega
Disable dm verity force encrypt
Credits & Links
Theme
Old TWRP
Kernel
Porting Guide
Disable dm verity & force encrypt
TeamWin Official
Android Image Kitchen

Changelog
Version 2.1
- Removed "Install twrp app" screen
Version 2
- Fixed empty area in Advanced options
- Fixed stock theme version error
- Fixed override font error
- Fixed all string resource errors
- Removed all other languages rather than English (Other languages have font problems. And I can't add more fonts because of limited partition size)

Any plans for further updates?
If yes may I suggest the following:
1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)
2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.

kenshinta said:
Any plans for further updates?
If yes may I suggest the following:
1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)
2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.
Click to expand...
Click to collapse
Actually I had to reset my whole computer & lost all my works. I made a list of best working gsi builds for both stock & custom rom. The gsis over stock rom didn't have graphics issues. And I also created other recoveries such as orange fox, Pitch black which were large to flash though. But I lost all of these
I will try to remove that prompt.
And will make a stock theme variant as well. Thanks

Stock theme variant added.

can't boot 64bit lineage 16
https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz/download

basiotte said:
can't boot 64bit lineage 16
https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz/download
Click to expand...
Click to collapse
That's gsi rom bro. They are not guaranteed to work