[TOOL/UTILITY][TWRP][3.2][RECOVERY] TWRP 3.2.1-0 TeamWin Recovery Project

[00bofh]

Indeed - please let me know that either:

1 - I'm all alone and probably have a broken tablet
-or-
2 - That I'm not delusional and this really does happen...

 

[bigbiff]

Indeed - please let me know that either:

1 - I'm all alone and probably have a broken tablet
-or-
2 - That I'm not delusional and this really does happen...

Exynos seems to have heartburn in omni-5.0, please try http://techerrata.com/bigbiff/openrecovery-twrp-2.8.4.0-v1awifi.img.tar

 

[00bofh]

New recovery.log posted to: http://pastebin.com/AVupY3mF.

Error 13 still present on ext-sdcard access, new issue noted (though to be honest, I didn't try with the public release of 2.8.4.0):

Install of "fresh" ROM fails with bootup proclaiming that "Data partition is corrupt", rebooting to recovery, "wiping" Data and then rebooting again to ROM. This continues to cycle (lather-rinse-repeat).

Complete format of both DATA and SYSTEM partitions was done (changed to exfat, then to ext_2, then to ext_4), same result for all three ROMs I tried (CM 12 0104, which is my current daily ROM; Gatsrom debloated stock BNK1 and, HyperDrive 1.1).

Returning to 2.8.1.1, formatting DATA and SYSTEM and restoring my last backup worked as expected. Full wipe and fresh install of all three worked as expected.

 

[bigbiff]

New recovery.log posted to: http://pastebin.com/AVupY3mF.

Error 13 still present on ext-sdcard access, new issue noted (though to be honest, I didn't try with the public release of 2.8.4.0):

Install of "fresh" ROM fails with bootup proclaiming that "Data partition is corrupt", rebooting to recovery, "wiping" Data and then rebooting again to ROM. This continues to cycle (lather-rinse-repeat).

Complete format of both DATA and SYSTEM partitions was done (changed to exfat, then to ext_2, then to ext_4), same result for all three ROMs I tried (CM 12 0104, which is my current daily ROM; Gatsrom debloated stock BNK1 and, HyperDrive 1.1).

Returning to 2.8.1.1, formatting DATA and SYSTEM and restoring my last backup worked as expected. Full wipe and fresh install of all three worked as expected.

If you do a setenforce permissive in twrp terminal, does backups work to external sdcard?

 

[00bofh]

My apologies for the lengthy delay - RL and work strike again...

Indeed, setting permissive in TWRP allowed the external_sd backup to complete. I tested backup, wipe, restore and install from scratch. All clean.

Thank you!

 

[bigbiff]

My apologies for the lengthy delay - RL and work strike again...

Indeed, setting permissive in TWRP allowed the external_sd backup to complete. I tested backup, wipe, restore and install from scratch. All clean.

Thank you!

Please see if this turns off selinux for backing up to external sd: http://techerrata.com/bigbiff/openrecovery-twrp-2.8.4.1-v1awifi.img.tar

 

[00bofh]

No such luck. Error 13 and requires Terminal command to set permissive.

Once set, it works as expected, backup, recovery, etc., so it's moving in the right direction!

Update: I was attempting to install the latest CM12 build from Valera1978 and on opening the Terminal to set permissive, I noticed an error.

Recovery logfile uploaded to http://pastebin.com/93igkf65 - looks like something weird in CACHE?

Didn't impact wipe or load, but backup failed during MD5 creation for DATA and forced a reboot back into TWRP.

ROM seems to be functioning as expected, so it's more a worry /annoyance, and doesn't seem to be a funtionality impacting glitch.

 

[bigbiff]

No such luck. Error 13 and requires Terminal command to set permissive.

Once set, it works as expected, backup, recovery, etc., so it's moving in the right direction!

Update: I was attempting to install the latest CM12 build from Valera1978 and on opening the Terminal to set permissive, I noticed an error.

Recovery logfile uploaded to http://pastebin.com/93igkf65 - looks like something weird in CACHE?

Didn't impact wipe or load, but backup failed during MD5 creation for DATA and forced a reboot back into TWRP.

ROM seems to be functioning as expected, so it's more a worry /annoyance, and doesn't seem to be a funtionality impacting glitch.

The discard error is fine. Just can't figure out why setenforce isn't running on start yet.

Can you run http://techerrata.com/bigbiff/openrecovery-twrp-2.8.4.1-v1awifi.img.tar and let me know if /tmp/test gets created in recovery?

 

[00bofh]

Nope, nothing in /tmp except the recovery.log file.

I updated the pastebin with the most recent output - I'm not sure if there's a way to turn on an "extra debug" mode, but if there is, let me know...

 

[bigbiff]

Nope, nothing in /tmp except the recovery.log file.

I updated the pastebin with the most recent output - I'm not sure if there's a way to turn on an "extra debug" mode, but if there is, let me know...

Do me a favor, in adb shell or TWRP terminal, execute: getprop ro.hardware and paste the results.

 

[00bofh]

From ADB Shell:

[email protected]:/ # getprop ro.hardware
getprop ro.hardware
universal5420

 

[bigbiff]

From ADB Shell:

[email protected]:/ # getprop ro.hardware
getprop ro.hardware
universal5420

Hi, can you get the output of dmesg > /sdcard/dmesg.txt after booting TWRP?

 

[00bofh]

No problem - uploaded to http://pastebin.com/keLmragR

I really appreciate all the time you're taking to tweak and tune! It's a Good Thing (tm) when a developer is willing to work with an end-user!

 

[bigbiff]

No problem - uploaded to http://pastebin.com/keLmragR

I really appreciate all the time you're taking to tweak and tune! It's a Good Thing (tm) when a developer is willing to work with an end-user!

Please test http://techerrata.com/bigbiff/openrecovery-twrp-2.8.4.1-v1awifi.img.tar

If it still doesn't work get me a new output of dmesg please.

 

[00bofh]

Success!!

Backup, wipe and full restore tested - no issues noted.

The only niggle left is the CACHE error, I know it doesn't impact function, but for a complete beginner (granted, I'm not far past that, but still...) it could generate some concern when they see the bold red lettering.

Thank you again and I greatly appreciate your hard work!

 

[bigbiff]

Success!!

Backup, wipe and full restore tested - no issues noted.

The only niggle left is the CACHE error, I know it doesn't impact function, but for a complete beginner (granted, I'm not far past that, but still...) it could generate some concern when they see the bold red lettering.

Thank you again and I greatly appreciate your hard work!

It's not really an error. Guess google has to help with that in education because we don't control how that error gets printed since it's from an external project for make_ext4fs.

I think we might release 2.8.5 soon. I will be looking at releasing all the fixes then. If not I will do 2.8.4.1.

 

[jimbob_sf]

Here we go again. New version and IMPOSSIBLE to find. Why is this the only app in the Android world that nearly everyone uses and the devs don't provide direct links?

ex. It takes 3 to 4 tries to figure out what search text to use to get the device to show in the pick list. Once you find it, the download game begins. Another classic example: as of this morning, goo.im doesn't have 2.8.5.0.What the hell, click the mirror (I think the meaning of mirror isn't lost on this crowd) and the techerrata site has everything.

 

[francesco totti]

Hi @bigbiff . today i wanted to download TWRP 2.8.5.0 for my SM-P901 from techerrata but downloading stucks at 99.99 % !! is it a bad upload?!? would you please reupload it ? Thanks.

 

[bigbiff]

Hi @bigbiff . today i wanted to download TWRP 2.8.5.0 for my SM-P901 from techerrata but downloading stucks at 99.99 % !! is it a bad upload?!? would you please reupload it ? Thanks.

Try a different browser.

 

[nsiti]

The latest TWRP worked seamlessly on my P900, thanks for all your hard work bigbiff. I'll try to donate soon, perhaps enough for a couple of beers.