[RECOVERY] KANG TWRP TF701T [email protected] [JULY 5]

[berndblb]

A couple more

After successful rom flash I booted back into recovery (with buttons) and did not have any touch control, but was able to adb pull the log.

Rebooted with long press of power, entered recovery again through bootloader and this time touch drivers worked. Flashed a gapps, then wiped dalvik and cache. Again hung a while on make_ext4fs, then again unable to mount /cache, /system. Could not pull the log: remote object does not exist...

 

[sbdags]

A couple more

After successful rom flash I booted back into recovery (with buttons) and did not have any touch control, but was able to adb pull the log.

Rebooted with long press of power, entered recovery again through bootloader and this time touch drivers worked. Flashed a gapps, then wiped dalvik and cache. Again hung a while on make_ext4fs, then again unable to mount /cache, /system. Could not pull the log: remote object does not exist...

Yes I have had this error. It seems to be related to corruption on /data for some odd reason. Mine is reproduceable as I have a bad bakcup from CROMi-X that causes the issue.

The only fix I could find was to format mmcblk0p14 from adb.

Try this in twrp:

adb shell
make_ext4fs /dev/block/mmcblk0p14

Restart twrp and you should be good to go again.

 

[berndblb]

Yes I have had this error. It seems to be related to corruption on /data for some odd reason. Mine is reproduceable as I have a bad bakcup from CROMi-X that causes the issue.

The only fix I could find was to format mmcblk0p14 from adb.

Try this in twrp:

adb shell
make_ext4fs /dev/block/mmcblk0p14

Restart twrp and you should be good to go again.

Well, I was able to reboot into the rom just fine after the errors in TWRP, so I don't think /data is corrupted??

 

[sbdags]

Well, I was able to reboot into the rom just fine after the errors in TWRP, so I don't think /data is corrupted??

Mine was. It kept coming back - the rom would boot fine but twrp kept complaining. Eventually other weirdness started to show - things stuck as read only and FCs. Try it if you see anything odd.

 

[berndblb]

Mine was. It kept coming back - the rom would boot fine but twrp kept complaining. Eventually other weirdness started to show - things stuck as read only and FCs. Try it if you see anything odd.

You mean like: Not being able to dl from the store after flashing POP b2??? :laugh:

 

[kevinthefixer]

Well I just had the opposite experience: for the first time ever on this tablet, a flash went just the way it is supposed to. But I did not try to wipe /data, only /cache. But I did a reboot into recovery from shutdown menu, shot a Nandroid with no issues, wiped Dalvic, wiped /cache, dirty-flashed, wiped Dalvic and /cache again, rebooted into /system all with no errors. I am finally beginning to like this tablet!

 

[berndblb]

Yes I have had this error. It seems to be related to corruption on /data for some odd reason. Mine is reproduceable as I have a bad bakcup from CROMi-X that causes the issue.

The only fix I could find was to format mmcblk0p14 from adb.

Try this in twrp:

adb shell
make_ext4fs /dev/block/mmcblk0p14

Restart twrp and you should be good to go again.

Thanks, that seems to have done it. I did a format of /data in TWRP last week, so I'm still wondering...
But after formatting data in adb shell I wiped Dalvik - no error, I flashed a rom - went fine, booted into it. Then I went back and did a factory wipe and that went through without error for the first time. :good::good:

 

[sbdags]

Thanks, that seems to have done it. I did a format of /data in TWRP last week, so I'm still wondering...
But after formatting data in adb shell I wiped Dalvik - no error, I flashed a rom - went fine, booted into it. Then I went back and did a factory wipe and that went through without error for the first time. :good::good:

Yeah we had exactly the same problem. It shouldn't fix it but it does. More evidence for _that! He still won't believe it though. Lol

 

[loner.]

I have installed this recovery and have had no problems at all so far, it mounts correctly backups and does the MDA backup flawlessly so far.

Sent from my K00C

 

[sbdags]

New Lollipop 5.1.1 ROM available here :

http://forum.xda-developers.com/transformer-tf701/orig-development/rom-t3135277

 

[JoshReuben]

No good- tried the adb commands listed above, seemingly successfully, but am still unable to format data, dalvik, cache or system after rebooting recovery. Just hangs until I press Cancel, at which point it returns "E: Another threaded action is already running -- not running 1 actions starting with '%tw_cancel_action%'

 

[_that]

No good- tried the adb commands listed above, seemingly successfully, but am still unable to format data, dalvik, cache or system after rebooting recovery. Just hangs until I press Cancel, at which point it returns "E: Another threaded action is already running -- not running 1 actions starting with '%tw_cancel_action%'

"still unable" is can have many reasons - post a recovery.log. In case of unusual cross-partition effects, also post the result of "adb shell dmesg > dmesg.txt".

The "Cancel" button should not even show up while formatting, as this action can't be canceled. @z31s1g: the condition for the "Cancel" button (tw_has_cancel=1) on the action page seems to be missing.

 

[JoshReuben]

Disaster. Can't reboot to recovery- instead, recovery loads, resumes trying to format cache, fails, and reboots. Prior to this, the last thing I saw when attempting to flash ZOMBi was the size of the data partition at "-1". Looks like I've managed to bork my partitions. Any suggestions?

---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------

OK- whiff of panic there. I can reboot to bootloader. I'm guessing I want to reflash recovery, but I've never had a partition problem before. Any help would be much appreciated.

 

[sbdags]

Disaster. Can't reboot to recovery- instead, recovery loads, resumes trying to format cache, fails, and reboots. Prior to this, the last thing I saw when attempting to flash ZOMBi was the size of the data partition at "-1". Looks like I've managed to bork my partitions. Any suggestions?

---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------

OK- whiff of panic there. I can reboot to bootloader. I'm guessing I want to reflash recovery, but I've never had a partition problem before. Any help would be much appreciated.

adb pull /tmp/recovery.log

 

[JoshReuben]

Attached.

 

[JoshReuben]

Windows doesn't even see the Internal storage/SDCard. Only sees ExtSD at this point.

 

[lj50036]

Attached.

Windows doesn't even see the Internal storage/SDCard. Only sees ExtSD at this point.

What is your bootloader version ?

Thx Josh

 

[JoshReuben]

What is your bootloader version ?

Latest - .30

---------- Post added at 07:58 PM ---------- Previous post was at 07:15 PM ----------

OK - used sdbags instructions from http://forum.xda-developers.com/showthread.php?t=2683787 and upon reboot, ZOMBi's firstboot launched and brought me to the config screen, now all back to normal - except that my sdcard is wiped. What to do with all that space!

Thanks for being there and keeping me off the ledge.

 

[loner.]

Is there any plans to update to twrp 2.8.7.x ?

 

[lj50036]

Is there any plans to update to twrp 2.8.7.x ?

Yes, Should be out within the week ....

Thx Josh