Develop Bugs

[warning] rom manager t-989 for roms [warning]

Looked urgent huh? That's because it is. I see that most people that have their phones bricked is from using ROM manager to install a rom that they downloaded onto their phone.
LISTEN TO ME WHEN I TELL YOU....
Do not use ROM manager to install a custom ROM that is not listed in the application.
I too have bricked my phone this way and I never made a back up. The quickest solution is to actually re-root your phone again by putting it back into download mode.
Look in the forums for instructions. I'm sure others can explain it better than me.
Only use ROM Manager to install clockwork mod recovery.
From there, do it the manual way. It may be more labor, but it is better than bricking your phone.
There are instructions to do that too. If you can't find it just throw me a PM.

Lol I use it all the time to flash roms never bricked
Sent from my SAMSUNG-SGH-T989 using xda premium

same here. can you elaborate why you think or provide proof that cwm is bricking peoples phones.
I have used cwm on several phones and never had any problems getting to recovery and flashing roms.

you didn't read his post. he is saying not to use Rom manager to get/install roms

Probably because rom manager only wipes data and cache at most. Most of these roms work best with a super wipe

The touch cwm is the worst. Have to toggle signature verification every time, and point it to the internal sd card. Only one brick (soft), though.
That v5 one is notoriously bad on many phones. Just buggy. Not a dealbreaker for me. Is the other touch one better?
Sent from my SAMSUNG-SGH-T989 using xda premium

He's probably referring to the roms listed in ROM manager that are not for our phone.I think there is two of them now

I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.

You guys can stop "trippin" there are 2 roms under the dl section in rom manager for our phone DO NOT IN ANY WAY SHAPE OR FORM FLASH THIS TO YOUR SGH-T989!!! it WILL BRICK YOUR DEVICE!!! Somebody just needs to email koush about it so they can be removed. IMHO dl to your phone or pc and then flash away a superwipe is recommended. I for one am iffy with rom manager because it errors out on restores sometimes.
Sent from MY Juggernaut!!!

zander21510 said:
I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.
Click to expand...
Click to collapse
Holy christ time to flash back to original clockworkmod. Later touch recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium

Still rockin the original CWM, never saw all the fuss about the touch stuff. Manually toggling is much safer and reliable IMO

I see that people have mistaken that I was talking about not using CMW. Let me explain. CMW (Clockwork Mod Recovery) and ROM Manager are two different things. You get CMW from ROM Manager. You use CMW to flash ROMs. Some people use ROM Manager to flash ROMs instead of CMW. That's the way you get bricked. By flashing ROM's that aren't on ROM Manager. I hope this clears it up.

I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall

ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread

the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.

rsfaze said:
the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.
Click to expand...
Click to collapse
There's also soft brick which can be saved. He was most likely referring to that.
Sharpie603 said:
I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall
Click to expand...
Click to collapse
ODIN is really crappy software IMO.. Despite its uses.

Even rom manager has its uses...I wouldn't use it to flash ROMS, because often with our phones you need more wiping than just data & cache, which is all it can do before it flashes a rom. It however it can be used to easily flash CWM and for phones without the option in the shutdown menu, you can use rom manager to reboot straight into CWM.

Guy's, what he is trying to tell you is that there are 2 ROMS that can be dowloaded and installed by ROM MANAGER that WILL BRICK YOUR PHONE. They are listed as T989 roms but they are actually for the International SGS2....

sbell7105 said:
ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread
Click to expand...
Click to collapse
He's accurate about what he described in this thread. I created a similar thread (probably got deleted) yesterday about the same issue. Just because you haven't experienced bricking yours doesn't mean he shouldn't warn others.
I hard-bricked my T989 just simply trying to boot into recovery (non-touch CWM) from the Rom Manager app...and I have read similar issues. The phone goes fcuking dead.
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.

bluepenny65 said:
H
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.
Click to expand...
Click to collapse
There isn't one that fully works with data and audio
Sent from my SAMSUNG-SGH-T989 using Tapatalk

Cwm or twrp???

What are most people using and does it matter that much?? What are the differences?? Cwm or twrp? I'm on twrp because I used qbkings root method and that's what his tutorial had used. I've also seen people say they r using cwm, if I wanted to use that instead, is it OK to use rom manager to flash the recovery? And is rom manager fully functional for the gnexus? I'm sure I could probably test most of this and figure it out with my backup if something goes wrong but sure would b a lot nicer I didn't have to do all that, and maybe this will help someone else too.
Sent from my Galaxy Nexus using Tapatalk 2

i use cwm touch on my gnex, have not tried twrp. i flashed it using fastboot. you can also just try/use it (or other recoveries) without flashing using "fastboot boot [image]". if you flash it be sure to rename/delete recovery-from-boot.p in system as it will otherwise overwrite your custom recovery again once you reboot.

stesmo said:
i use cwm touch on my gnex, have not tried twrp. i flashed it using fastboot. you can also just try/use it (or other recoveries) without flashing using "fastboot boot [image]". if you flash it be sure to rename/delete recovery-from-boot.p in system as it will otherwise overwrite your custom recovery again once you reboot.
Click to expand...
Click to collapse
Where can I find fastboot image for cwm or would it just b easier to rom manager?
Do u know of any differences in the 2, when u say "other recoveries" what else is available for the gnexus??? I've only seen the 2.
Sent from my Galaxy Nexus using Tapatalk 2

justen7723 said:
Where can I find fastboot image for cwm or would it just b easier to rom manager?
Do u know of any differences in the 2, when u say "other recoveries" what else is available for the gnexus??? I've only seen the 2.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
images can be found here: http://clockworkmod.com/rommanager
i have not tried the rom manager, i guess its a little bit easier if you dont want to use the command line.
since i have not tried twrp i cannot say exactly what the differences are. but i would guess both can do about the same things as the job for a recovery is quite well defined.
at least 4 for gnex : stock, cwm, cmw touch and twrp. don't really know if there are others...

Well, in my experience TWRP offers many benefits over CWR e.g. being able to be themed, having scripts, 'flashier' GUI, built-in file explorer but in the end I still swapped back to Touch CWR as it's simple, and it has everything that a recovery should do (flash, wipe, mount etc.). TWRP also has a few small bugs here and there but it's great if you want more options and features. Also that animation of booting into recovery bugs the hell out of me, along with the 'Swipe to continue' thing and touch response isn't that good in file lists (like when you have to choose what you want to flash).
It's all up to personal preference so that easiest way is to just flash both and try it yourself.

Twrp is awesome much quicker than cwm my only complaint right now is I can't find any themes for twrp 2.1.2
Sent from my Galaxy Nexus using xda premium

[RECOVERY] [10/17/12] TWRP 2.3.1.1 - TeamWin Recovery Project

[RECOVERY] [10/17/12] TWRP 2.3.1.1 - TeamWin Recovery Project
dan-htc-touch is proud to present TWRP 2.3.1.1 for the Galaxy Tab 8.9
now with ability to backup/restore/flash from usb dongle
Special credits:
Dees_Troy for a lot of porting help.
braway for helping me to get recovery image to init.
BLOWNCO for helping test
agrabren for writing the initial TWRP GUI code.
AssassinsLament and Dees_Troy for initial TWRP code
Shift and racks for graphics help on default theme
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.1, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
new in 2.2
onscreen keyboard for selecting recovery names
select locations from backup and flash menu's
What's new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.1.0 now features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
In the future we will be working hard to make TWRP easier for other developers to compile. We eventually plan to get a gerrit instance running to let anyone submit patches to the project. We may be looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
Zip files that install more data than free space is available will crash or hang recovery (AOSP issue) - Fixed with flashing zip in place
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
https://github.com/dan-htc-touch/android_device_samsung_SGHI957
DOWNLOAD:
goo.im/devs/damantea/Recoveries
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers

Looks really promising. Maybe now rom zip flashes won't lag like hell. Has this been tested and confirmed working specifically for the i957? It is quite different from the other 8.9s.
Sent from my SAMSUNG-SGH-I727 using xda premium

I have 957r, but built using 957 source. This flashes zips in place, no copy to ram first

Thanks for the work. I'll give this a try when I get some time. Hopefully later tonight. Hopefully my install scripts work with this recovery.

Scarchunk said:
Thanks for the work. I'll give this a try when I get some time. Hopefully later tonight. Hopefully my install scripts work with this recovery.
Click to expand...
Click to collapse
That's what I'm hoping
Sent from my SAMSUNG-SGH-I727 using xda premium

Might help to check the symlink part of your script, and make sure nothing is conflicting with files already there, not sure what else could cause the system lag

Sweet! It does install and come up, taking a backup of the device now.
Anyone else give this a try?
I didn't have any luck with goomanager, it force closed while trying to unsuccessfully download the recovery image. No idea, seemed like a lot of effort to flash a raw image to a partition, so at a root shell I did:
Code:
dd if=openrecovery-twrp-SGH-I957-2.1.4.img of=/dev/block/mmcblk0p22
YMMV might vary there, but it worked for me.
edit to add: adb works in recovery.. pre-OS root shell SCORE!
thanks for this!

twrp v2
Will twrp work with att sgh-i957 as this device is not listed on their website? Can someone give a detail instructions how to install this through GOO manager as someone posted?
I have a stock unit and I've read the forum but not clear on whether to use CWM Recovery or TWRP v2 do a nandroid. I have not installed or flashed anything yet. Just asking for informations before doing anything.
----------------
ATT SGH-I957

nrvate said:
Sweet! It does install and come up, taking a backup of the device now.
Anyone else give this a try?
I didn't have any luck with goomanager, it force closed while trying to unsuccessfully download the recovery image. No idea, seemed like a lot of effort to flash a raw image to a partition, so at a root shell I did:
Code:
dd if=openrecovery-twrp-SGH-I957-2.1.4.img of=/dev/block/mmcblk0p22
YMMV might vary there, but it worked for me.
edit to add: adb works in recovery.. pre-OS root shell SCORE!
thanks for this!
Click to expand...
Click to collapse
spidyman007 said:
Will twrp work with att sgh-i957 as this device is not listed on their website? Can someone give a detail instructions how to install this through GOO manager as someone posted?
I have a stock unit and I've read the forum but not clear on whether to use CWM Recovery or TWRP v2 do a nandroid. I have not installed or flashed anything yet. Just asking for informations before doing anything.
----------------
ATT SGH-I957
Click to expand...
Click to collapse
If goo manager does not work, try the dd method, or Odin flash this
http://db.tt/Tz3MFdDf
CWM and twrp backups only work for the recovery they were created in

I also couldn't figure out how to get Goo Manager to do anything useful. Should I zip up the .IMG file first?

Any problems with a full wipe from recovery? Backup and restore freeze free? Both problems existed in cwm, just making sure.
Sent from my SAMSUNG-SGH-I727 using xda premium

So far so good! Made several backups and restored two of them without issue.
Real encouraging!

nrvate said:
So far so good! Made several backups and restored two of them without issue.
Real encouraging!
Click to expand...
Click to collapse
Have you wiped anything like data system or cache yet?
Sent from my SAMSUNG-SGH-I727 using xda premium

orlandoxpolice said:
Have you wiped anything like data system or cache yet?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes, all three. Worked as expected. Didnt try wiping recovery or boot.y

nrvate said:
Yes, all three. Worked as expected. Didnt try wiping recovery or boot.y
Click to expand...
Click to collapse
Ok last stupid question I promise. Safe to install over cwm I assume?
Sent from my SAMSUNG-SGH-I727 using xda premium

orlandoxpolice said:
Ok last stupid question I promise. Safe to install over cwm I assume?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yep. Installs over cwm and as nrvate said, everything seems to be working as it should. Haven't tried installing any of the stuff I was working on yet. Haven't had the time, but I tossed on dannorom along with the stock kernel and I'm happy.

OK, I'm just dying of curiosity here. How are you guys flashing this .IMG file???
I tried with Goo.im, it won't see it. Renaming to .zip doesn't do anything useful either, it just reboots into recovery.
I couldn't flash the .img or renamed .zip in CWM.
What's the secret? Anybody care to share?
---------- Post added at 05:20 AM ---------- Previous post was at 04:30 AM ----------
orlandoxpolice said:
Ok last stupid question I promise. Safe to install over cwm I assume?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I just flashed TWRP over CWM using ODIN. Worked fine. Still no idea what the .img file is for, but TWRP is so slick I won't be moving back to CWM.

Indeed, no problems installing over CWM.
Digging TWRP alot!

ok, fixed a few things, removed reboot bootloader, added reboot download. as well as added ability to backup/restore to usb dongle, please test before i add to first post
http://db.tt/VxOwWios
usb dongle is called sdcard in mount section

When backing up is it safe to backup and restore boot?
Sent from my SAMSUNG-SGH-I727 using xda premium

Rom Manager with the Photon Q recovery works fine on the Razr M.

So you are Unlocked & Rooted.
Download the apk here
Just choose the setup for The Photon Q let it do its thing.
It is just a "stepping stone" to flash the newest from the same recovery.
It is 6.0.1.3 & works a lot slower than the newest 6.0.4.5 or TWRP from my goodies.
For the doubters I will say that, except the keyboard & digitizer input, the Q & the M are the same phone.
Atrix HD using RM also.
More
See method 4
Love TWRP? RM installs TWRP also. Just flash the zip from cwmr see housekeeping goodies.
The biggest news is that one can go from rooted stock to custom recovery with this. If you want TWRP OR Matt's CWMR just flash it from this recovery -see goodies below. Also the attached flash-able zip is a larger font CWM version from the Atrix HD forum.
This also allows you to take the OTA using 3 (or 4 if you have not unlocked yet ) phone "apps": Rom Manager, VooDoo rootkeeper, and the stockRECOVERY.zip (Motopocalypse.apk).
Get VooDoo on your SDcard from the Developer http://androidvnd.com/download.php?id=org.projectvoodoo.otarootkeeper
Now we have phone maintenance without a PC. More housekeeping goodies here. The bootloader unlock apk is there too http://forum.xda-developers.com/showthread.php?t=2327340
Steps to restore to the newest stock rom: I have a Mac and have to : ( using Parallels desktop & W7)
1. Data wipe from CWMR a must do or WiFi breaks. No more TWRP for me, I lost extSD cause of the box in normal selection.
2. Enter fast boot ...
3. Rsdlite & select the XML from Matts util...Reboots.
4. ByPass SETUP go settings/Dev. settings for USB debug.
5. Root w/ Matts.
6. Say no to logins & syncs.
7. VooDoo protect & unroot.
8. Check for update......yes yes...stock recovery... reboot
9. VooDoo restore root.
10. Login and DL RM.
11. RM with Photon Q recovery.
12. I keep ROM on extSD only... back home
CWMR is way faster and more space efficient than TWRP. Yet the blob folder can lead many to think otherwise.
Never use a space if you rename that date code label.
You never want to use internal SD for backup or anything else as it gets wiped in the often needed data wipe/reset. That is why a SD swap is so needed on our phone.
I keep RomMgr & VooDoo on my SD so I can skip all the logins and syncs If I have to restore w/ RSD.
Now I see why there are no supporters of RM on the Photon Q forum. ROM installations do not work well with the M (read Q also).
Help for general errors & what to do about them:
http://forum.xda-developers.com/showpost.php?p=43043608&postcount=1
The Q and the M are identical hardware and use the same emulated storage0.
But their digitizer screen input is the mirror of each other.
That is why the cwmr hard button version works but their official twrp will work but the screen input is mirrored.

Nobody believes me.
http://www.droidrzr.com/index.php/t...nager-works-on-the-xt907-sleeper-of-the-year/

Famous Dev's opinion.
http://forum.xda-developers.com/showpost.php?p=44055839&postcount=370

Well that's neat and all, but whats the point?

Leraeniesh said:
Well that's neat and all, but whats the point?
Click to expand...
Click to collapse
I never used it before. But it is very handy I think all the features work. I went and bought the premium app when I first got into android with the Dx2. Looking for a bluetooth ready cm based rom to install. Carbon is not yet ready.

while I can agree it "works". The screen resolution is not set-up properly for a Razr M so the text is like a font 8. Let's not forget that one can manually or even automatically install CWM recovery that is not only appropriate for their device, but also up-to-date ie (CWM 6.0.3.2 vs 6.0.1.3) AND can be manaually assigned to be recognized by ROM manager anyway.

tucstwo said:
while I can agree it "works". The screen resolution is not set-up properly for a Razr M so the text is like a font 8.
[I do not see any difference. The Q is also qHD.]
Let's not forget that one can manually or even automatically install CWM recovery that is not only appropriate for their device, but also up-to-date ie (CWM 6.0.3.2 vs 6.0.1.3)
[True, but this allows custom recovery with out a PC. Then one can flash any recovery they want.]
AND can be manaually assigned to be recognized by ROM manager anyway.
[I have found all of the housekeeping features work]
Click to expand...
Click to collapse
Thanks for the feedback.

OP updated.

[RECOVERY][Unofficial][Epic4GTouch] TWRP 2.6.3.0 touch recovery [2014-02-11]

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:
Latest Builds Here
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.[/QUOTE]

Links are up enjoy the light show
Twrp now has haptic feedback.

Wow...first post. I thought this would explode...Lol.
Great job dev.

Like the haptic... Thanx!
Sent from my SPH-D710

Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.

EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.

HighxVoltage said:
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
Click to expand...
Click to collapse
It works to flash jb+ I first built twrp when I was on stock then I flashed jb and went to 4.4
Sent from my SPH-D710 using Tapatalk

This is a repost of the twrp from a while back right?
sent from tumblr
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
I've used an older version of twrp. I install it through Odin then upgrade to this one.
sent from tumblr

@Linux guy this is a new build hint why it has haptic feedback.
Sent from my SPH-D710 using Tapatalk

Working great on my E4GT. Thanks
☞"And on the eight day the Lord made a backup"☜

Any chance for v2.7.0.0 in the near future?

CrimsonKnight13 said:
Any chance for v2.7.0.0 in the near future?
Click to expand...
Click to collapse
This is 2.7 basically I wait for major changes but probably in a week

Unjustified Dev said:
This is 2.7 basically I wait for major changes but probably in a week
Click to expand...
Click to collapse
Thanks! I look forward to your next release.

Any updates regarding 2.7 being compiled & released?

How does one flash this?
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"

os2baba said:
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
Click to expand...
Click to collapse
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk

dirtyhewr said:
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?

os2baba said:
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
Click to expand...
Click to collapse
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk

Surj138 said:
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.

os2baba said:
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
Click to expand...
Click to collapse
This device is different because the recovery comes bundled with the kernel. This particular recovery is only for kk aosp ROMs... It overwrites the recovery those ROMs come with (CWM).
There are custom kernels for stock ROMs that come with a custom recovery. If you're on stock JB I recommend Agats 1.3
Trolling from my SPH-D710 using Tapatalk