[Q] Unable to boot out of TWRP

Search This thread

greymonk

Member
Feb 15, 2014
6
2
I was attempting to install a ROM on my Transformer TF300T and I've apparently done something severe to it.

Right now I have TWRP 2.6.3.0 on it. I've apparently broken the /data, /cache, and internal storage, they're all unable to mount now. I cannot user the PWR and VOL DOWN buttons to get to fastboot anymore, it just ignores the fact that i'm holding those buttons down and only boots into TWRP. I can't choose the ADB Sideload option in TWP, it fails because of the broken partitions. I am able to connect to it in adb from my desktop, and I can push files to it, but I haven't been able to find anything that lets me fix the partitions or fastboot.

I can provide any other info necessary, but I have no idea what further to do with it.
 

cmendonc2

Senior Member
Aug 29, 2011
1,628
896
I was attempting to install a ROM on my Transformer TF300T and I've apparently done something severe to it.

Right now I have TWRP 2.6.3.0 on it. I've apparently broken the /data, /cache, and internal storage, they're all unable to mount now. I cannot user the PWR and VOL DOWN buttons to get to fastboot anymore, it just ignores the fact that i'm holding those buttons down and only boots into TWRP. I can't choose the ADB Sideload option in TWP, it fails because of the broken partitions. I am able to connect to it in adb from my desktop, and I can push files to it, but I haven't been able to find anything that lets me fix the partitions or fastboot.

I can provide any other info necessary, but I have no idea what further to do with it.

Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.
 

greymonk

Member
Feb 15, 2014
6
2
Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.

I tried this, fastboot doesn't seem to see it.

I also tried pushing an earlier blob of TWRP, 2.5, just to see if the if it would do that much. It doesn't seem to work. It still has 2.6.3.0 installed, even though it looked like it was responding properly.

Code:
C:\android_sdk\sdk\platform-tools>adb shell
~ # ←[6ndd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
12896+1 records in
12896+1 records out
6602856 bytes (6.3MB) copied, 0.091592 seconds, 68.8MB/s
~ # ←[6n

It also has the weird ~ # ←[6n as a prompt in the adb shell.
 

greymonk

Member
Feb 15, 2014
6
2
Well, I think I've completely killed it now. I think I had originally put the wrong TWRP onto it. I tried pushing the correct one to it with fastboot, and now it will either 1) do an infinite boot loop, or 2) boot to the fastboot screen but 'fastboot devices' does not see it. I can't see what else I can do with it at this point.
 

lj50036

Senior Member
Feb 14, 2013
3,321
3,297
42
FUXDA
Well, I think I've completely killed it now. I think I had originally put the wrong TWRP onto it. I tried pushing the correct one to it with fastboot, and now it will either 1) do an infinite boot loop, or 2) boot to the fastboot screen but 'fastboot devices' does not see it. I can't see what else I can do with it at this point.


Shoot me an email at jl52741@gmail.com we can continue there... Thx lj
 
  • Like
Reactions: greymonk

Top Liked Posts