When using this recovery i keep getting errors when wiping about not being able to mount system and cache. I tried the tip from sdbags, but that didn't help. Any tips or ideas?
[RECOVERY] KANG TWRP TF701T [email protected] [JULY 5]
- Thread starter sbdags
- Start date
-
- Tags
- development
The only fix is a full format. Clean boot to twrp and format /data
I'm happy about this news about TWRP for the 701T!
However ...
A number of us tried an earlier TWRP for this device, and it seemed to cause the speakers to blow out. There was a discussion about whether this was really due to TWRP, and that was never fully resolved. However, to a number of us, it seemed more than just coincidental that these speaker errors tended to occur right after some of us started using that earlier version of TWRP.
In my case, the speakers were permanenty damaged, and I had to replace my device.
So ... before I dive in and install this new TWRP, can anyone confirm that there are no speaker issues after installing it on the 701T and using that device for a while?
Thank you very much.
However ...
A number of us tried an earlier TWRP for this device, and it seemed to cause the speakers to blow out. There was a discussion about whether this was really due to TWRP, and that was never fully resolved. However, to a number of us, it seemed more than just coincidental that these speaker errors tended to occur right after some of us started using that earlier version of TWRP.
In my case, the speakers were permanenty damaged, and I had to replace my device.
So ... before I dive in and install this new TWRP, can anyone confirm that there are no speaker issues after installing it on the 701T and using that device for a while?
Thank you very much.
.
There is no evidence ever given that would say TWRP had anything to do with speakers blowing out ...
Unless you believe in magic or the tooth fairy .....
Thx Josh
Maybe this will help. The other day, my wife's speakers blew out and hers uses CWM.
On another note, both of ours use Viper4Android. I'm not blaming it. I'm just thinking that some people amp it up too high and have blown their speakers.
Have any of the folks involved installed 3rd party audio?
Again, I'm not blaming that. My wife and I both use it (now just me) at the same settings and my speakers are fine. But I do admit that afterward, I did go into mine and back it down a bit, just to be safe.
Thank you guys. I am really impressed. I can imagine how much work was necessary to make this great project. Thank you again.
That was philz and touch. This one works fine and the touch drivers were rebuilt from source. Do no dangers. I have been running it for weeks with no issues.
Well, I thought it was TWRP, but maybe I got it mixed up in my not-so-great memory with Philz's recovery. In any case, it's good news that this TWRP has been working for you for so long without issues.
Thank you very much. I'll be installing it soon.
.
... and I just tested it with a backup and some other TWRP functions, and it works great!
.
This one does not do the secure erase if you format, does it?
I formatted data in prep for ZOMBi-POP and was all prepared to do something useful for the next hour but next time I looked it was all finished.
BUT with lots of error messages: unable to mount : data, system, cache, etc
Tried to save the recovery log which did not give an error but there's no log in data/media/0 (maybe cause it can't mount /data? doh)
Tried to wipe Dalvik with the same errors.
Rebooted recovery, tried a factory wipe with the same errors.
Then I checked sdcard in TWRP's file browser (yes, it did see externa and internal...) and all my data was wiped. Even data/media - so the format went ok after all?????
Flashed ZOMBi-POP without any problems after all that...
I formatted data in prep for ZOMBi-POP and was all prepared to do something useful for the next hour but next time I looked it was all finished.
BUT with lots of error messages: unable to mount : data, system, cache, etc
Tried to save the recovery log which did not give an error but there's no log in data/media/0 (maybe cause it can't mount /data? doh)
Tried to wipe Dalvik with the same errors.
Rebooted recovery, tried a factory wipe with the same errors.
Then I checked sdcard in TWRP's file browser (yes, it did see externa and internal...) and all my data was wiped. Even data/media - so the format went ok after all?????
Flashed ZOMBi-POP without any problems after all that...
Hmm, that's more or less the inverse of what sbdags reported (he claimed that formatting /data repairs /system and /cache - wtf?)
"adb pull /tmp/recovery.log" would have been the right thing to do here.
I tried unsuccessfully to pull it from /data/media/0, the location TWRP wrote the log to supposedly. Did not know about /tmp/...
I tried to get it for you and ran another format but could not replicate it. This time the format data went without a hitch. Must have been a fluke
I tried to get it for you and ran another format but could not replicate it. This time the format data went without a hitch. Must have been a fluke
Last edited:
I had a couple of odd issues while trying to shoot a Nandroid. And then like a fool I never even thought about trying to retrieve a log, although I doubt it would have been possible.
Just trying a normal backup, it finished /system and generated the md5, went most of the way through /data, and froze. Numbers stopped changing, and it seemed the loading bar animation slowed way down. Stayed that way for 3 or 4 minutes, about what it usually takes to complete the whole task, and I finally hit the cancel button. Cancel button changed color, I guess it was just being polite and acknowledging me, 'cause that was all that happened. Finally had to force-close it with the power key. Booted back into system, deleted the incomplete backup, back into recovery--and had no touch screen. I wasn't using the dock at the time so had no mouse either. I started preparing to re-flash the recovery, decided to try one more reboot--and it worked. And it completed a backup with no issues. Poltergeisten maybe? Incidentally, it usually reports my battery at 70% no matter what. But while the touchscreen was not working, it reported 96%, which would have been about right.
I notice no f2fs support! Is this the price of shrinking TWRP to this tiny recovery partition? Or is there something about the 701 that makes it impractical or impossible? Will the upcoming Zombi support it? Why does this fool keep asking all these dumb questions?
Just trying a normal backup, it finished /system and generated the md5, went most of the way through /data, and froze. Numbers stopped changing, and it seemed the loading bar animation slowed way down. Stayed that way for 3 or 4 minutes, about what it usually takes to complete the whole task, and I finally hit the cancel button. Cancel button changed color, I guess it was just being polite and acknowledging me, 'cause that was all that happened. Finally had to force-close it with the power key. Booted back into system, deleted the incomplete backup, back into recovery--and had no touch screen. I wasn't using the dock at the time so had no mouse either. I started preparing to re-flash the recovery, decided to try one more reboot--and it worked. And it completed a backup with no issues. Poltergeisten maybe? Incidentally, it usually reports my battery at 70% no matter what. But while the touchscreen was not working, it reported 96%, which would have been about right.
I notice no f2fs support! Is this the price of shrinking TWRP to this tiny recovery partition? Or is there something about the 701 that makes it impractical or impossible? Will the upcoming Zombi support it? Why does this fool keep asking all these dumb questions?
Well lj50036 and I spent 3 days building and testing f2fs. It seems the bootloader on the TF701 detects a non ext4 partition (or thinks it is bad) and reformats it back to ext4 in order to boot.
We couldn't get it to stick at all so the TF701 will not have f2fs support.
Well as always thanks for trying. This machine is probably fast enough as it is, but as a teenager I was always trying to shave another 0.2 seconds off a quarter-mile...
I had the same behavior of write errors when trying to wipe, but after a few tries was able to fully clear system, cache and dalvik. Also was able to flash Zombie Pop without issues.
Had to reboot to recovery a few times until it was finally successful.
Tried the export of the recovery log and it was written to my external sd, attached here.
I'll try to replicate it later on since I don't have that much done with the new set up.
Just outstanding. Thank you all *so* much for keeping our TF701s current!
I did another factory wipe in TWRP. It was on the formatting cache step for at least 3 minutes which seems a little long. Then I again got the unable to mount error for /cache, /system (see attached picture). Tried to wipe Dalvik but got the same error. I was unable to connect in adb - tablet was not recognized at all by my Win8 PC (which connected just fine to my TF700).
Rebooted both tablet and PC. All my apps were still there, so the factory wipe didn't happen.
Booted to TWRP and wiped Dalvik only. Again it hung on make_ext4fs for about 3 minutes > failed to mount cache. See recovery.log
Tried a Factory Wipe in the same session and it went through. I flashed the rom. See recovery02.log
The factory wipe worked this time, I'm now on the setup screen
Rebooted both tablet and PC. All my apps were still there, so the factory wipe didn't happen.
Booted to TWRP and wiped Dalvik only. Again it hung on make_ext4fs for about 3 minutes > failed to mount cache. See recovery.log
Tried a Factory Wipe in the same session and it went through. I flashed the rom. See recovery02.log
The factory wipe worked this time, I'm now on the setup screen
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone