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:
-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
-TF101: Ignore blkid when mounting /data
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!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also 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 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.
We also now back up and restore boot! Yay!
Want to compile yourself?
I'm using this config: https://github.com/ViViDboarder/android_device_asus_tf101
And this kernel: https://github.com/ViViDboarder/android_kernel_TF101
And compiling against CM9 source tree
Further device specific announcements will go here
A few thanks for this specific build:
Roach2010 for helping be me test and find the mystery kernel
RaymanFX for finding a config that worked. Still not sure where he found it yet exactly
And... Dees_Troy and eyeballer for their relentless nagging
first ...
well second lol
So, third ......thanks guys, that's awesome !
thanks, been waiting for this.
great work, i've been waiting forever and finally have this on all my devices and those that I support.
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
gdeeble said:
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
Click to expand...
Click to collapse
Good note. That's a theme issue then. I can build a new theme zip or something later. Working on releasing the much delayed Nexus One build.
EDIT: I've been informed by Dees_Troy that we have build flags to do just this. So I'm adding them to my configs so the next build should have them removified.
It's worth pointing out that this build of TWRP has a recompiled kernel with boot and recovery exposed. You can finally back up boot and restore it.
GooManager keeps hanging at Looking for recoveries after trying to install OpenRecoveryScript. Unable to retrieve files...
Finally recovery on a touch screen device the way it should be! Thanks guys!
Sent from my SGH-I747 using Tapatalk 2
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
MassStash said:
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
Click to expand...
Click to collapse
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
sidneyk said:
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
Click to expand...
Click to collapse
Weird. It didn't wipe my data. Just installed nicely as per instructions.
running great with no issues I used goo manager app but i flashed it through the flash roms selection on the main menu not the 3-dot menu install open recovery script selection.
sidneyk said:
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Click to expand...
Click to collapse
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
ViViDboarder said:
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No, I was using RaymanFX's TWRP build prior to this and before that Team Rogue Touch and before that Roach's CWM build, all flashed from within recovery. I only did the GooManager thing because that was the recommended method. Subsequent boots to recovery did not reproduce the data wipe and after reflashing my ROM and restoring my apps, I went into recovery without a hitch. It was only after installing this one through GooManager per the instructions. It downloaded, rebooted and flashed and rebooted back to Android (Team EOS3 JB #57). After a few minutes I rebooted to recovery from the Power menu in EOS3 and as soon as the blue curtain raised it was wiping my data partition - /data/media. Of course, I didn't expect that and didn't get any chance to stop it. I know I read somewhere before that open recovery wasn't working on the TF101, but since this was new and it was recommended to use open recovery, I just assumed that meant it was now working. Oh well, all is well now.
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
cbrox said:
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
Click to expand...
Click to collapse
I had already flashed EOS3-N58, but had changed some files experimenting with getting Polaris Office to work and gave up. So, I followed your suggestion and moved a few other files that I normally flash along with the ROM and it worked like a charm. Pretty nifty. I setup the order to flash for EOS3-N58, gapps, Guevor kernel, nVidia codecs, iobusy, and DSP Manager along with the preliminary cache and Dalvik cache wipes and it just worked like you say. Thanks. I hadn't tried that feature yet, mostly because until now I thought it might break something since I had read that open scripting wasn't working yet for TF101 somewhere. I can say now, with this recovery and your change to the download folder, that it is working and working well. You just have to have whatever files you want to flash in that folder (or maybe just somewhere in /data/media) and you're good to go.
Related
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:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
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!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Changelog: See our website!
FAQ:
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG06IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG06IMG.zip) after booting
Enjoy
How to install with Fastboot:
Download the fastboot binary for your computer from HTC
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-speedy-1.1.0.img
Does this back up Wimax partition?
That is an option if you chose. Recommended to make at least one backup of just wimax and store that somewhere safe.
The screen went black after doing [insert random function]. What is the issue?
When testing the recovery early on we noticed fastboot wasnt a stable way to flash the recovery. Random issues would arise after using the method. As a result and a solution, flashing the recovery via the PG06IMG.zip is recommended to avoid such issues. Please try this as a solution.
I found a bug! What do I do?
Well you're probably going to want to post here and see if other people are having the same issue. We're also going to start tracking bugs on Github along with our project. This will let you see what issues we are aware of. You can submit a bug here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues Be sure to include how you came about the issue as well as list your device and how you installed twrp.
Have a great new feature idea for TWRP?
Submit it on our Github page! It'll help us track it and notify you of the progress. https://github.com/TeamWin/Team-Win-Recovery-Project/issues
Why should I use this over ClockworkMod?
While all three recoveries offer roughly the same abilities (backup, restore, flash) we feel like ours adds a bit more in addition to the basics as well as blend some of the more useful features. A few differences to hightlight:
USB Mass Storage mode (Not in CWM)
Re-organized menus with most commonly used features on top
Saveable settings for all preferences selected
Date and battery display (configurable timezones)
Ability to auto-reboot after flashing
Color themes
Capacitive button support
Go a head and give it a try! You've got nothing to lose. If you don't like it you can always roll back to whatever recovery you want. Of course, shift might go all Emo Pony on us, but he'll get over it.
Sweet! First post! Time to get rid of rom manager!
Teleported from my Shifty Speedy using Tapatalk
Nice! Congrats on the release on the evo shift!
Thank you for this amazing recovery teamwin! Way way better then anyone ever expected! CWM will prolly never be used again lol
Supremely Shifted
ZOMFG!!
yeah, i'm pretty sure this is wood i'm sporting
Yeah, been using this since last night, it is awesome. And clockwork did have USB storage mode, its in the advanced settings, not that it matters anymore.
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Same thing here.. Had to do a battery pull.
Sent from my PG06100 using Tapatalk
Haha... You can still use RM to reboot to TWRP recovery and when I tried to backup my ROM (through RM) (just to see what would happen) it just sends me to TWRP recovery as well...
from the "CRACKED" Speedy EVO Engine...
thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
good job man. . .thank you
jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
Not doubting you! But with CWM it took barely a minute.
Teleported from my Shifty Speedy using Tapatalk
jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
I waited a good 5 minutes after the "end" of the progress bar and finally did a battery pull. I was able to fix permissions through terminal, just didn't work through recovery.
Sent from my PG06100 using Tapatalk
noob question but will this also restore backups made from cwm?
hoesnaps said:
noob question but will this also restore backups made from cwm?
Click to expand...
Click to collapse
No. You'll need to make fresh backups
Sent from my PG06100 using Tapatalk
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
sparksco said:
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It has the option to partition but I haven't tried it yet... anyone?
Sent from my PG06100 using Tapatalk
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
Because of the way the recovery is packed into boot, this will not work with all kernels / ROMs. It is known to work with CM7.2 and CM9.1.0. It will probably work with most other MTD-based ROMs and kernels but will not work with any BML ROM or kernel. Use at your own risk! Installing a new ROM or kernel may end up replacing your install of TWRP. Also note that TWRP is *not* compatible with CWM backups. We are not based on CWM, we wrote our own recovery based on AOSP. With that said, I hope that you will get a chance to at least see how fast and easy-to-use TWRP is.
In addition to the on-screen keyboard, TWRP now supports using the hardware keyboard on the Epic 4G. Unfortunately the screen doesn't rotate, but hey, the hardware keyboard does work.
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:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
First. Thanks.
×Marcusant
Sick!!!"
Sent from my SPH-D700 using xda premium
Wow, this looks great, can't wait to try it out. Thanks TeamWin
Sent from my SPH-D700 using XDA
This will probably work on all mtd roms afaik.
×Marcusant
Niiiice
Part of the trick with this build of TWRP is the inclusion of a new utility that I've started working on called injecttwrp. It's a work in progress. I'll be building upon this to inject our recovery ramdisk into existing Samsung boot images so that you can choose to keep TWRP installed as you install new ROMs or kernels regardless of what recovery is included with the kernel or ROM that you are installing.
https://github.com/TeamWin/Team-Win-Recovery-Project/blob/master/injecttwrp/injecttwrp.c
Note that this utility is not restricted to just working with TWRP. It could be used to inject any recovery that you wanted.
Awesome, I use this for my Kindle Fire and love it. It also is the only current recovery that works with the new 3.0 kernel, but I think that is mainly a fire issue. I will try it when I get some time!
anyone confirm it works on ics (aokp particularly)?
This looks awesome
Just a thought.. marcusant.. could you build this recovery into nyan for sayyy cm7?
Sent from my SPH-D700 using XDA
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium
Of course on the day I'm busiest is when this is released lmao. Thanks for the hard work guys, I'll be playing with this tomorrow for sure!
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
The failure was an oddity with the formatting of our flash_image on ics as far as I can tell
×Marcusant
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
Dees_Troy said:
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
Click to expand...
Click to collapse
I mean it goes through everything but then stops towards the end... write_flash_image has an error and it shows E: /sdcard/goomanager/twrp.zip ... and aborts.. so what marcus said about the flash image.
Sent from my SPH-D700 using xda premium
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!
pvtjoker42 said:
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!
Click to expand...
Click to collapse
........interface similar to Epic CM Team's test touch recovery; will await sign from Dees_Troy + flash again.
.........sent from today's android = 4.0.4
I believe that the zip install should now be working!
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I couldn't get it to install on cm7 says error installing blah blah (bad).. tried to download it twice.. both times errors
Sent from my SPH-D700 using XDA
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:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
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!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the HTC One S
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-16
Created 2013-09-16
Last Updated 2013-09-16
You guys are doing an amazing job, ROM will come these days!
Well, this is version 2.2.1 but wheres the changelog for it ?
I installed it anyway, but I like to see what changed :-3
EDIT:
Nevermind, this is for S3 >.<
Love it! Glad to see s3 getting some love too!
Sent from my HTC VLE_U using Tapatalk 2
Yeaaaaaaaaaah! Yes! Yes! Yesssss! Yeeees! Thank you million times!
Fantastic!
@Dees_ Troy
I seemed to find a little bug. The battery in recovery always shows 66%.
Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium
dsellers2 said:
Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Yeah I've learned that yesterday that this is a well known issue with some of the htc. There is two waya,one you have described to flash it manually in fastboot and the other is a workaround that twrp supports. It is called HTC dumlock,just search on their official page how to use it.
Sent from my HTC One S using xda app-developers app
Thank dev. For S3 development.
Sent from my HTC One S using xda app-developers app
I got my Villec2 Unlocked with htcdev.com site
but i can't flash any recovery, Why?
I found that this recovery works on my hts one s (my i mean villec2)
i tried to do it couple of times with cmd and fastboot, and then with HTS ONE S AIO KIT
every time it says that sending is ok, and writing i ok... but can't go into recovery got only htc sentence...
Do you guys got any solution? whey on that threat above some people with s3 says that they flashed recovery and i can't do it?
Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP
Wyall said:
Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP
Click to expand...
Click to collapse
I tired that method also without any progress,
GooManager downloaded img then i saw little box that recovery installed successfully, But unfortunately still cant use recovery
Do you have root? And did you use the Reboot to Recovery Option in GooManager?
Wyall said:
Do you have root? And did you use the Reboot to Recovery Option in GooManager?
Click to expand...
Click to collapse
I just got unlocked Phone with htcdev, i thought that i need to Flash Recovery before i can Flash superSu like i saw in torxx guide. Can i Flash superSu like i try to Flash Recovery? Which one shall i choose?
With GooManager i restart to Recovery, the result was the same....
And still i count on your help in flashing Recovery on my HTC
Regards in advance
First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/
Wyall said:
First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/
Click to expand...
Click to collapse
So now i got root (method from link above) and i got custom recovery installed with gooManager method. Sweet. i for other users it's very important to got root first
Updated to 2.2.2.0!
Dees_Troy said:
Updated to 2.2.2.0!
Click to expand...
Click to collapse
Hi!! Has full wipe partitions in this recovery?
Thanks?
Do it work with S4 or just only S3? Thanks
Team Win Recovery Project 2.2, 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.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
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!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
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.
thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)
Going to flash this now and give it a try. Hopefully it works out good.
whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!
thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks
I flashed this a week or two ago and been working awesome! I love it.
i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this
they are in different folders on the SDCARD, im not even sure they are compatible.
ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder
alsp cani get the twrp 2220 in a zip format?
will this recovery work with firerats? on heroc?
dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
thanks im trying it now, love the use of touch
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.
Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?
* DELETE *
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app
Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.