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

[tdhite]

I have the vibration change as well

Sent from my One using Tapatalk 2

"get prop error" -- that is an issue with the 4.4 builds (all) of Android, on which this recovery is based. Google changed the way getprop works and it's problematic with old updater-binary executables. Can you point me to what you're using? I can try to discern a fix for the general case.

 

[bearw815]

@tdhite

Superwipe script
https://www.dropbox.com/s/73oprshdgjrj7ky/smw6180_Superwipe.zip


sent from my-beanstalk-one

 

[Sloth]

@tdhite

Superwipe script
https://www.dropbox.com/s/73oprshdgjrj7ky/smw6180_Superwipe.zip


sent from my-beanstalk-one

Is this new or the same one posted in the forum?

 

[benny3]

Vibrations are all there -- just to go to "Settings" and "Vibration Duration" -- turn them all down to your liking. If anything is missing, look to your theme -- others had the same issue during early testing.

Cool , i have a theme maybe thats my problem

EDIT: Yes the theme was it, Thank you again!

 

[bearw815]

Same one as in forum.

Is this new or the same one posted in the forum?

sent from my-beanstalk-one

 

[Sloth]

Same one as in forum.





sent from my-beanstalk-one

That's the one I have always used hmmm

---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------

Yes please disable vibration if possible

Update tried Advance wipe/wipe
cache/dalvik cache/system/data
Failed
Tried using superwipe
Failed
Was getting unable to mount cache error.

Flashed back to 2.6.3.0

Should have gotten a recovery log darn it

@tdhite any thought why it's unable to mount cache?

 

[bearw815]

That's why I uploaded it so maybe he can fix it

That's the one I have always used hmmm

---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------



@tdhite any thought why it's unable to mount cache?

 

[tdhite]

Is this new or the same one posted in the forum?

Ok -- two big problems with your superwipe zip:

1) The updater-binary is ancient:

-rw-rw-r-- 1 tdhite tdhite 224260 Aug 31 2011 META-INF/com/google/android/update-binary

That's well over two years old, and it will not work with any 4.4 based recovery (that include PhilZ and CWM as well). Tell the developer to update the updater-binary -- that should have been done long ago, imho.


2) The work taking place in the zip is effectively useless to new recoveries -- they all do the same work automatically for you, so I don't see the need for the flash at all:

$:~/Desktop/unzipped$ cat setup/datawipe.sh
#!/sbin/sh
cd /data; find . -maxdepth 1 ! -name 'media' ! -name '.*' -exec rm -rf {} \;

That command is nothing more than a removal of everything on /data but excludes the internal SD card. TWRP does now, and has for a very long time, taken care of that already.

Edit: adding] The rest of the partitions / directories cleaned are wiping /boot (kernel), /system (standard for recovery wipes), /devlog (/dev/mmcblk0p22), and
/cache (recoveries wipe this). Not sure why anyone would want to dump /devlog, but I can add that to the TWRP if desired. As for wiping /boot, all ROMs writing /boot 'dd' it into place anyway, so wiping it prior is fruitless.

In the end, I'm not sure there's really any value spending much time on arguably superfluous tools like that within the recovery itself, but if I can help, I will talk to the dev and help him update the update-binary for you. That would fix it if you really want it. Regardless, the value is gone, effectively, with new recoveries (that include PhilZ and CWM as well as this one).

One thing I think I can do is prevent any flash from running at all if there's an ancient updater-binary in the zip. I'll look at that.

 

[Sloth]

I got the same error "unable to mount cache" when I wiped manually also
Advance Wipe>Wipe
Chose cache/dalvik cache/data/system
Failed

 

[benny3]

Ok -- two big problems with your superwipe zip:

1) The updater-binary is ancient:

-rw-rw-r-- 1 tdhite tdhite 224260 Aug 31 2011 META-INF/com/google/android/update-binary

That's well over two years old, and it will not work with any 4.4 based recovery (that include PhilZ and CWM as well). Tell the developer to update the updater-binary -- that should have been done long ago, imho.


2) The work taking place in the zip is effectively useless to new recoveries -- they all do the same work automatically for you, so I don't see the need for the flash at all:

$:~/Desktop/unzipped$ cat setup/datawipe.sh
#!/sbin/sh
cd /data; find . -maxdepth 1 ! -name 'media' ! -name '.*' -exec rm -rf {} \;

That command is nothing more than a removal of everything on /data but excludes the internal SD card. TWRP does now, and has for a very long time, taken care of that already.

Edit: adding] The rest of the partitions / directories cleaned are wiping /boot (kernel), /system (standard for recovery wipes), /devlog (/dev/mmcblk0p22), and
/cache (recoveries wipe this). Not sure why anyone would want to dump /devlog, but I can add that to the TWRP if desired. As for wiping /boot, all ROMs writing /boot 'dd' it into place anyway, so wiping it prior is fruitless.

In the end, I'm not sure there's really any value spending much time on arguably superfluous tools like that within the recovery itself, but if I can help, I will talk to the dev and help him update the update-binary for you. That would fix it if you really want it. Regardless, the value is gone, effectively, with new recoveries (that include PhilZ and CWM as well as this one).

One thing I think I can do is prevent any flash from running at all if there's an ancient updater-binary in the zip. I'll look at that.

I ask him a while ago if he would update it and he said he would look into it when he had time.
it would great if you did work him and get us a useful superwipe back for us. Im sure its a placebo effect but its one that i and many of us like...lol

 

[Aldo101t]

I got the same error "unable to mount cache" when I wiped manually also
Advance Wipe>Wipe
Chose cache/dalvik cache/data/system
Failed

BD just for ****s and giggles, did you try wiping one at a time.

 

[Sloth]

BD just for ****s and giggles, did you try wiping one at a time.

Nope got frustrated and re-flashed 2.6.3.0

 

[Riff76]

Nope got frustrated and re-flashed 2.6.3.0

Quitter!

Sent from my GT-N5110 using Tapatalk

 

[tdhite]

I got the same error "unable to mount cache" when I wiped manually also
Advance Wipe>Wipe
Chose cache/dalvik cache/data/system
Failed

Hmmmm -- how'd you set that up? I just did that 'cuz it really concerned me. Worked like a champ. Can I get a log, maybe?

My results:

Cleaned: /data/dalvik-cache
. . .
Formatting Cache using make_ext4fs functionn
. . .
Wiping Dalvid Cache Directories
. . .
Formatting System using make_ext4fs function
. . .
Wiping data without wiping /data/media . . .
Done.

Wipe Complete
Successful.

what gives? Do you have a theme you could send me? I've never seen such an error other than one user who had a theme that broke partition setup.

 

[Aldo101t]

Nope got frustrated and re-flashed 2.6.3.0

well, guess i'll have to get my feet wet here and try it out

 

[Sloth]

Hmmmm -- how'd you set that up? I just did that 'cuz it really concerned me. Worked like a champ. Can I get a log, maybe?

My results:

Cleaned: /data/dalvik-cache
. . .
Formatting Cache using make_ext4fs functionn
. . .
Wiping Dalvid Cache Directories
. . .
Formatting System using make_ext4fs function
. . .
Wiping data without wiping /data/media . . .
Done.

Wipe Complete
Successful.

what gives? Do you have a theme you could send me? I've never seen such an error other than one user who had a theme that broke partition setup.

Give me a few to re-flash

 

[tdhite]

Give me a few to re-flash

thanks -- that you got a mount error is quite concerning to me -- that should *not* happen. not saying the good folks on the TeamWin team get everything right, but the HTC One changes have zero to do with that, so if it fails anywhere, it should fail everywhere. bugs are strange, though, sometime lurking where we least expect.

If we have to drop to PMs -- no problem. I want to know exactly what's up with your scenario.

I'm thinking the user who had the same err quite a while back was @elvisypi -- hopefully he can chime in if it was him.

 

[Aldo101t]

thanks -- that you got a mount error is quite concerning to me -- that should *not* happen. not saying the good folks on the TeamWin team get everything right, but the HTC One changes have zero to do with that, so if it fails anywhere, it should fail everywhere. bugs are strange, though, sometime lurking where we least expect.

If we have to drop to PMs -- no problem. I want to know exactly what's up with your scenario.

I'm thinking the user who had the same err quite a while back was @elvisypi -- hopefully he can chime in if it was him.

advanced wipe option worked fine for me, then i tried to install aokp nightly(which i haven't been able to do)and it still failed.???

restore function works ok though

 

[tdhite]

advanced wipe option worked fine for me, then i tried to install aokp nightly(which i haven't been able to do)and it still failed.???

restore function works ok though

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.

 

[Sloth]

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