[RECOVERY][09-18-2014] TWRP2 Touch Recovery 2.8.0.3

[Aldo101t]

Not quite sure what you mean by: "aokp nightly(which i haven't been able to do)and it still failed.???"

I'm not certain how to support you on a nightly that doesn't work. I can try -- but what failed? The ROM itself? Or some script error in the installer?

I'm not worried much about advanced wipe -- it works, but possibly there's an upgrade issue for some folks.

Here's a thing to try:

1) Boot into your DD ROM;
2) Rename the TWRP directory (in /data/media) to, say, TWRP.BAK
3) Reboot into recovery;
4) Flash your nightly again;
5) Let me know what happens.

Like I said, not sure I can fix broken ROMs, but we might learn something in the process.

i've tried to install aokp numerous times and it fails inrecovery with symlink errors it's no big deal they say you need 2.6.3.4 to install it. i don't think anyone on sprint can, although the rom is for sprint, go figure.i wouldn't worry about that at this point just solve your other problems, i just figured i'd give a whirl to see what happens

it still fails.

 

[tdhite]

i've tried to install aokp numerous times and it fails inrecovery with symlink errors it's no big deal they say you need 2.6.3.4 to install it. i don't think anyone on sprint can, although the rom is for sprint, go figure.i wouldn't worry about that at this point just solve your other problems, i just figured i'd give a whirl to see what happens

it still fails.

LOL -- so far there's no actual problems . @BD619 I figured out, but will have to work with him to solve his phone (I believe).

With the said -- point me at the ROM and let me take a look at the installer -- I'll see what's up.

 

[Sloth]

LOL -- so far there's no actual problems . @BD619 I figured out, but will have to work with him to solve his phone (I believe).

With the said -- point me at the ROM and let me take a look at the installer -- I'll see what's up.

Add me on hangouts if need be

 

[Aldo101t]

LOL -- so far there's no actual problems . @BD619 I figured out, but will have to work with him to solve his phone (I believe).

With the said -- point me at the ROM and let me take a look at the installer -- I'll see what's up.

the latest nightly from AOKP 02-08-2014(They all fail) aokp.co

yeah everything i've tried so far except for that rom works ok.

 

[tdhite]

Update:
I made a backup with 2.6.3.0
Restored with 2.6.3.4...stuck on splash screen
Re-flashed 2.6.3.0
Screenies and recovery log attached

Ok, brother -- we have work to do. It's not TWRP2 (at least not the build), but there's definitely a problem on your phone. From the boot process:

/cache | /dev/block/mmcblk0p38 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p38
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

The /cache partition *cannot* be 0MB, by definition. That's easy to fix, though. The question is -- why do you have an invalid /cache partition??? We need to solve that -- forget this new recovery.

I'm sharing a proper boot sequence (attached) for the partitions. The key is notice the correct /cache partition block device:

/cache | /dev/block/mmcblk0p38 | Size: 629MB Used: 24MB Free: 605MB Backup Size: 24MB
. . .

wft, man -- what's with your cache partition?

[Edit]: the problem with the phone was the use of "fastboot erase cache" as opposed to using "fastboot format cache" for 'hand' clearing the cache partition before booting the recovery. The former remove the file system from the partition, therefore there's nothing to mount (thus the errors). The latter does create a file system on /cache. Do the latter in all cases if you really feel the need to clear /cache manually. I updated the OP for this as well in the event others do the same.

 

[Sloth]

Ok here is an update @tdhite and I got a few things figured out.
I was always told to type fastboot erase cache after flashing a recovery, that seems to be an issue with this recovery so don't do it lol.
The other thing I had a problem with is, that I made a backup using TWRP 2.6.3.0 and tried to restore using TWRP 2.6.3.4 and it said successful but never made it past the splash screen. I had to hard reset and re-flash TWRP 2.6.3.0 in order for the backup to work.
@tdhite is gonna do some more digging around with that issue he will keep us posted.
I have not tried doing a backup using TWRP 2.6.3.4 and restoring with 2.6.3.4 so not sure if that will work either.

Update #2
Re-flashed TWRP 2.6.3.4
Made a backup using TWRP 2.3.6.4
Flashed rom...flashed fine
Restored my backup using TWRP 2.3.6.4 was successful, booted just fine.
So it seems backups made with 2.6.3.0 are not compatible with 2.6.3.4
I'm sure @tdhite will get it sorted out shortly

 

[Aldo101t]

Ok here is an update @tdhite and I got a few things figured out.
I was always told to type fastboot erase cache after flashing a recovery, that seems to be an issue with this recovery so don't do it lol.
The other thing I had a problem with is, that I made a backup using TWRP 2.6.3.0 and tried to restore using TWRP 2.6.3.4 and it said successful but never made it past the splash screen. I had to hard reset and re-flash TWRP 2.6.3.0 in order for the backup to work.
@tdhite is gonna do some more digging around with that issue he will keep us posted.
I have not tried doing a backup using TWRP 2.6.3.4 and restoring with 2.6.3.4 so not sure if that will work either.

Update #2
Re-flashed TWRP 2.6.3.4
Made a backup using TWRP 2.3.6.4
Flashed rom...flashed fine
Restored my backup using TWRP 2.3.6.4 was successful, booted just fine.
So it seems backups made with 2.6.3.0 are not compatible with 2.6.3.4
I'm sure @tdhite will get it sorted out shortly

BD i restored a backup from 2.6.3.0 with 2.6.3.4 and it was fine??(this was after the failed rom and a complete wipe, then i restored the backup made on 2.6.3.0)

 

[Sloth]

BD i restored a backup from 2.6.3.0 with 2.6.3.4 and it was fine??

IDK bro I tried 3 times once while I was on hangouts with tdhite
Gets stuck at the splash screen

 

[Aldo101t]

IDK bro I tried 3 times once while I was on hangouts with tdhite
Gets stuck at the splash screen

crazy, man

 

[elvisypi]

Ok here is an update @tdhite and I got a few things figured out.
I was always told to type fastboot erase cache after flashing a recovery, that seems to be an issue with this recovery so don't do it lol.
The other thing I had a problem with is, that I made a backup using TWRP 2.6.3.0 and tried to restore using TWRP 2.6.3.4 and it said successful but never made it past the splash screen. I had to hard reset and re-flash TWRP 2.6.3.0 in order for the backup to work.
@tdhite is gonna do some more digging around with that issue he will keep us posted.
I have not tried doing a backup using TWRP 2.6.3.4 and restoring with 2.6.3.4 so not sure if that will work either.

Update #2
Re-flashed TWRP 2.6.3.4
Made a backup using TWRP 2.3.6.4
Flashed rom...flashed fine
Restored my backup using TWRP 2.3.6.4 was successful, booted just fine.
So it seems backups made with 2.6.3.0 are not compatible with 2.6.3.4
I'm sure @tdhite will get it sorted out shortly

Yes it's a problem with the fastboot erase cache I believe. But even if you do it, you should boot the phone first, than afterwards go to recovery, not directly. I am sure it's not a problem with this recovery, I have had it with previous version aswell.

Sent from my HTC One using Tapatalk

 

[Sloth]

Yes it's a problem with the fastboot erase cache I believe. But even if you do it, you should boot the phone first, than afterwards go to recovery, not directly. I am sure it's not a problem with this recovery, I have had it with previous version aswell.

Sent from my HTC One using Tapatalk

This is the first time I have ever had a problem with fastboot erase cache
I'll just stop using it lol

 

[elvisypi]

This is the first time I have ever had a problem with fastboot erase cache
I'll just stop using it lol

Probably the other times you didn't boot direcly to recovery to wipe. I just tried to restore an old backup with the old recovery, stuck at boot.

Sent from my HTC One using Tapatalk

 

[avwheeler]

IDK bro I tried 3 times once while I was on hangouts with tdhite
Gets stuck at the splash screen

On earlier revisions I experienced similar restoring, I knew better, but kept on using the theme I really liked. So I would usually have something to flash after restoring, so I would wipe cashes, however due to theme it would wipe cache and system. Anyway was not recovery just my stubbornness to get rid of theme. Also wiping caches is now 1st and 3rd vs 1st and 2nd so have to get used to newer layout.

Sent from my HTC One on some Awesome Rom..

 

[elvisypi]

On earlier revisions I experienced similar restoring, I knew better, but kept on using the theme I really liked. So I would usually have something to flash after restoring, so I would wipe cashes, however due to theme it would wipe cache and system. Anyway was not recovery just my stubbornness to get rid of theme. Also wiping caches is now 1st and 3rd vs 1st and 2nd so have to get used to newer layout.

Sent from my HTC One on some Awesome Rom..

Restoring 2.6.3 backups doesn't work. Backups made with the new recovery work though

Sent from my HTC One using Tapatalk

 

[rootlinux]

Restoring 2.6.3 backups doesn't work. Backups made with the new recovery work though

Sent from my HTC One using Tapatalk

I found this out last night.
Made 2.6.3.4 into a flashable zip so I can easily switch between the 2.6.3.0 and 2.6.3.4 to access old backups.
Will probably just make new backups of my old roms though.

 

[tdhite]

Restoring 2.6.3 backups doesn't work. Backups made with the new recovery work thoughk

So the gist is: inconvenient that backups are not (currently) backward compatible. Worst case for folks (at the moment) is restore any desired backups with old TWRP, backup with new TWRP, good to go). Painful? Possibly. Critital? not so sure. With all the other fixes, it's hard to imagine (to me, anyway) foregoing those for a bit of backup transfer work. No matter -- a fix I'll find.

With all that said, recent commits on TWRP source (and in this recovery) changed the tar archiver -- likely culprit (see commit). I'll find a fix over time -- nothing yet has stopped me from squashing bugs once noted .

 

[elvisypi]

I found this out last night.
Made 2.6.3.4 into a flashable zip so I can easily switch between the 2.6.3.0 and 2.6.3.4 to access old backups.
Will probably just make new backups of my old roms though.

If you just wanna switch recoveries, install recovery tools from play store, it installs them pretty easily no need for pc or anything

Sent from my HTC One using Tapatalk

---------- Post added at 01:55 PM ---------- Previous post was at 01:44 PM ----------

So the gist is: inconvenient that backups are not (currently) backward compatible. Worst case for folks (at the moment) is restore any desired backups with old TWRP, backup with new TWRP, good to go). Painful? Possibly. Critital? not so sure. With all the other fixes, it's hard to imagine (to me, anyway) foregoing those for a bit of backup transfer work. No matter -- a fix I'll find.

With all that said, recent commits on TWRP source (and in this recovery) changed the tar archiver -- likely culprit (see commit). I'll find a fix over time -- nothing yet has stopped me from squashing bugs once noted .

It's really no problem at all. Just write it in the OP so that people don't mess things up.

Sent from my HTC One using Tapatalk

 

[rootlinux]

If you just wanna switch recoveries, install recovery tools from play store, it installs them pretty easily no need for pc or anything

Sent from my HTC One using Tapatalk

---------- Post added at 01:55 PM ---------- Previous post was at 01:44 PM ----------



It's really no problem at all. Just write it in the OP so that people don't mess things up.

Sent from my HTC One using Tapatalk

I can flash easily within Android but there could be a time when you become locked out of Android and with the wrong recovery flashed.
That is why I made the flashable.
Covering all bases to save any headaches in the future.

In case anyone wants to test this or use it.
If OP wants it removed I will take this link down.
http://d-h.st/PRL

Much thanks for this recovery as ViperONE had to have it to backup.

 

[tdhite]

I can flash easily within Android but there could be a time when you become locked out of Android and with the wrong recovery flashed.
That is why I made the flashable.
Covering all bases to save any headaches in the future.

In case anyone wants to test this or use it.
If OP wants it removed I will take this link down.
http://d-h.st/PRL

Much thanks for this recovery as ViperONE had to have it to backup.

Hmmm -- realistically I can't stop anyone from making new distribution models -- it is, after all, open source. With that said -- so long as you're willing to deal with any support requests from folks trying out your flashable, and you updated it all the time with new builds that I produce, then it seems fine and I can post that on the 'custom builds' area. Frankly I'm a believer in community additions (@elvisypi gave me some cool graphics for battery animations while charging off-line -- I plan to repack the recovery with those and post that soon as well).

Let me know how you want to handle the flashable. My visceral reaction is we need to either: 1) keep things supported and open in the first posts; or 2) nix them before all sorts of madness ensues. Recoveries are really important. On the flip side -- my ego is so big I could care less about download counts, if that's what you were thinking I might worry about.

 

[rootlinux]

I am willing to keep up with packaging the recoveries to make flashable.
That is no problem at all my friend.
I don't have a big ego but on the flip side I do love giving back to the community so it all works out.