Database Info

[Q] Bricked TF300T - ADB semi ok, no fastboot, some (strange) options left

I made a really stupid mistake...
The Good Part:
...I flashed my bootloader/blob via fastboot with the latest update from ASUS (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), and at that point no problems. Messed around with the thread that mentioned CWM (regular and JB). Found that I couldn't access the SD Cards with CWM JB, so I tried flashing TWRP.
The Bad Part:
I read everything closely, ..... except the darn file name on the TWRP site, so I ended up flashing the TF300TG by accident, instead of the TF300T recovery.
Here's the sum of what I have left:
- no fastboot (Power + VOL DOWN won't work)
- I read about APX mode (Power + VOL UP???) but no dice there if that is supposed to work
- after i realized I lost fastboot I think I panicked and managed to erase the current firmware, so no OS currently on the device
- I think that I may have killed busybox on the device, and any chance of fully using ADB the normal way to restore ROOT/anything else
- I can get into TWRP recovery
- I can use the ADB connection, but none of the commands that would normally use busybox actually work
- under NORMAL circumstances I can't access the internal memory (/SDCard/ mount) nor can I access the external memory
- I CAN select the option to mount SYSTEM, but the contents of SYSTEM are actually my external SD Card (so I can put files on my device)
Through my hours of googling (and searching XDA) i found a thread for another device that mentioned fixing the mount points. I can't seem to find that thread, but again it was for another device, so the commands would probably be different for all the mount points anyways.
So in a nutshell:
- I can use the basic linux commands (like LS and CD), on ADB and in TWRP command line mode, but no mount or push/pull commands
- I can mount "SYSTEM" from TWRP GUI but the contents of SYSTEM are actually my external SD Card, so I can put files on the device
- I can still use TWRP to CHMOD stuff
--->>> Remaining mounts that seem in tact: (all entries are folders unless specified / anything not specified such as ROOT or SDCARD exists but is blank)
- / contains
/default.prop and several other files
- /DEV/
/block
/bus
/graphics
/input
/log
/ts
/snd
/socket
- /ETC/
/fstab (file)
/mke2fs.conf (file)
/mtab (file)
/recovery.fstab (file)
- /LICENSE/
/openaes
- /PROC/
...... lots of folders with numbers for file name
- /RES/
/fonts
/images
- /SBIN/
...lots of files... starting with [, [[, adbd, adjtimex, arp, ash, awk, base64.....
- /SUPERSU/ ... (i tried install from zip with superuser and SuperSU, and TWRP keeps offering to install SU every time I restart)
/99SuperSUDaemon (file)
/install-recovery.sh (file)
/su (file)
/Superuser.apk (file)
- /SYS/
/block
/bus
/class
/dev
/devices
/firmware
/fs
/kernel
/module
/power
/tf_driver
- /SYSTEM/
/bin (but it is empty, when I actually mount SYSTEM, it is then replaced with the contents of my external SD Card)
- /TMP/
/recovery.log (file) ... I think this was an attempt to use TWRP command button to "Copy Log to SD"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I know recovering from this is a major long shot, but the good news is, I have all the data backed up, so nothing is actually lost. Granted I have brick, but it's a brick that I can actually play with, and ADB still partially works. I was wondering about manually installing busybox, fixing mount points, etc, so that I could get back to a state of flashing the proper recovery and/or reflashing the bootloader to an older version.
Of course I'm noob enough to not know exactly where to start, with manually reviving busybox, fixing mount points, and using all this to actually push a bootloader or recovery without fastboot ... and I'm hoping desperately that someone will take a little pity (at least enough to see me squirm???)
I'll appreciate any advice at all to help me recover from my stupidity. I know this is a major long shot. Of course, I'm not above paying ASUS a pretty penny to fix it either, but I'd rather learn and better myself before I shell out money.
I've read a few things about letting the battery completely run out when trying to fix some cases of BRICK ... and supposedly that may get you fastboot back, but I'm holding off on that for the time being while it seems that I may still have a shot since I don't exactly have a 100% brick. My device won't stay on, I can shut it off... (i also read that device staying on all the time = brick??)

Potential Soultion
Quote:
TheArkive said:
I made a really stupid mistake...
The Good Part:
...I flashed my bootloader/blob via fastboot with the latest update from ASUS (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), and at that point no problems. Messed around with the thread that mentioned CWM (regular and JB). Found that I couldn't access the SD Cards with CWM JB, so I tried flashing TWRP.
The Bad Part:
I read everything closely, ..... except the darn file name on the TWRP site, so I ended up flashing the TF300TG by accident, instead of the TF300T recovery.
Here's the sum of what I have left:
- no fastboot (Power + VOL DOWN won't work)
- I read about APX mode (Power + VOL UP???) but no dice there if that is supposed to work
- after i realized I lost fastboot I think I panicked and managed to erase the current firmware, so no OS currently on the device
- I think that I may have killed busybox on the device, and any chance of fully using ADB the normal way to restore ROOT/anything else
- I can get into TWRP recovery
- I can use the ADB connection, but none of the commands that would normally use busybox actually work
- under NORMAL circumstances I can't access the internal memory (/SDCard/ mount) nor can I access the external memory
- I CAN select the option to mount SYSTEM, but the contents of SYSTEM are actually my external SD Card (so I can put files on my device)
Through my hours of googling (and searching XDA) i found a thread for another device that mentioned fixing the mount points. I can't seem to find that thread, but again it was for another device, so the commands would probably be different for all the mount points anyways.
So in a nutshell:
- I can use the basic linux commands (like LS and CD), on ADB and in TWRP command line mode, but no mount or push/pull commands
- I can mount "SYSTEM" from TWRP GUI but the contents of SYSTEM are actually my external SD Card, so I can put files on the device
- I can still use TWRP to CHMOD stuff
--->>> Remaining mounts that seem in tact: (all entries are folders unless specified / anything not specified such as ROOT or SDCARD exists but is blank)
- / contains
/default.prop and several other files
- /DEV/
/block
/bus
/graphics
/input
/log
/ts
/snd
/socket
- /ETC/
/fstab (file)
/mke2fs.conf (file)
/mtab (file)
/recovery.fstab (file)
- /LICENSE/
/openaes
- /PROC/
...... lots of folders with numbers for file name
- /RES/
/fonts
/images
- /SBIN/
...lots of files... starting with [, [[, adbd, adjtimex, arp, ash, awk, base64.....
- /SUPERSU/ ... (i tried install from zip with superuser and SuperSU, and TWRP keeps offering to install SU every time I restart)
/99SuperSUDaemon (file)
/install-recovery.sh (file)
/su (file)
/Superuser.apk (file)
- /SYS/
/block
/bus
/class
/dev
/devices
/firmware
/fs
/kernel
/module
/power
/tf_driver
- /SYSTEM/
/bin (but it is empty, when I actually mount SYSTEM, it is then replaced with the contents of my external SD Card)
- /TMP/
/recovery.log (file) ... I think this was an attempt to use TWRP command button to "Copy Log to SD"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I know recovering from this is a major long shot, but the good news is, I have all the data backed up, so nothing is actually lost. Granted I have brick, but it's a brick that I can actually play with, and ADB still partially works. I was wondering about manually installing busybox, fixing mount points, etc, so that I could get back to a state of flashing the proper recovery and/or reflashing the bootloader to an older version.
Of course I'm noob enough to not know exactly where to start, with manually reviving busybox, fixing mount points, and using all this to actually push a bootloader or recovery without fastboot ... and I'm hoping desperately that someone will take a little pity (at least enough to see me squirm???)
I'll appreciate any advice at all to help me recover from my stupidity. I know this is a major long shot. Of course, I'm not above paying ASUS a pretty penny to fix it either, but I'd rather learn and better myself before I shell out money.
I've read a few things about letting the battery completely run out when trying to fix some cases of BRICK ... and supposedly that may get you fastboot back, but I'm holding off on that for the time being while it seems that I may still have a shot since I don't exactly have a 100% brick. My device won't stay on, I can shut it off... (i also read that device staying on all the time = brick??)
Click to expand...
Click to collapse
Hi there.
Buster99 kind of had the same problem, and he managed to unbrick it.
All credit goes to Buster99.
Here is his post:
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Hope this helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.

Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster

You guys rock! I'll try that as soon as i get home!!
∫εทт ƒя๑๓ ๓γ αทδя๑ïD

Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!

Quote:
TheArkive said:
Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!
Click to expand...
Click to collapse
Glad to have helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.

Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS

hatdrc said:
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS
Click to expand...
Click to collapse
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I went into fastboot and and erase recovery. Did it. Then I tried to flash recovery and again it locks up. Rebooted and it went straight to CM 10.2 Tried flashing recovery with terminal emulator. Said it was copied. Rebooted went back to CM. Rebooted again to recovery but it went back to CM. Booted to fastboot again and selected RCK. now it says
Booting Recovery kernel image
Booting failed
Unrecoverable bootloader error (0x00000000)
It does boot to CM but now I have no recovery. OmniRom was the one I wanted to flash but at this point I'm thinking im going to have to start from square one. I just don't understand why it doesn't want to flash a recovery
Thank you for your help, you are the man

strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was trying to flash the most current blob from the twrp site. I get the following:
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.965s]
finished. total time: 1.965s
fastboot -i 0x0b05 flashe recovery twrp.blob
sending 'recovery' (6448 kb)...
OKAY [ 2.561s]
writing 'recovery'...
OKAY [ 2.394s]
finished. total time: 4.955s
When I erase recovery the green flashing box on the tablet keeps flashing. When I try to flash the recovery the box just stops on what ever shade of green it was on when I hit enter. Also after if I do fastboot devices I get:
???????????? fastboot

hatdrc said:
fastboot -i 0x0b05 flashe recovery twrp.blob
Click to expand...
Click to collapse
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app

Buster99 said:
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry, typo. Should have been flash.
So i unzipped the recovery.img file and placed it in my fastboot folder. I get the same results.
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (6892 KB)...
OKAY [ 2.445s]
writing 'recovery'...
OKAY [ 2.477s]
finished. total time: 4.922s
The green box stops flashing as soon as I hit enter
Could it be that my recovery partition as gotten messed up, would formatting it help you think. Guess there's only one way to find out.
EDIT: Never mind, can't format a 'basic' filesystem

huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Still a no go. The only recover on there was a flashable zip file. That's why I was trying to get anything on it so I could flash that. I'm at the end of my knowledge. I've always had Samsung so I got use to odin. Never had to use fastboot. I really appreciate your help. Guess its going to have to run CM10.2 and hope it doesn't have a problem
Sent from my SGH-T999 using Tapatalk

odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will take a look, and I thank you for the time you have spent with me! If all else fails at least its running and usable for now.
Sent from my SGH-T999 using Tapatalk

Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Hi Buster,
I have a similar problem, but I cant reach the fastboot. I tried to reset and push volume down, connect tablet to PC with volume down pushed, turn off and start the tablet with the volume down pushed, but nothing. My recovery is corrupted, because it doesnt recognize any file in the SD. I tried to type adb reboot bootloader from the pc, but it says "erro: device not found".
Do you have any idea?

Help
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
+needle wont do anything for me cos mine boots to twrp logo and stay there for ever until battery is drained :/ hellp

It's not the exactly the same problem... For me ADB doesnt work.....
ConsoleFreak said:
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
Click to expand...
Click to collapse

[Q] Unable to boot out of TWRP

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.

greymonk said:
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.
Click to expand...
Click to collapse
Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.

cmendonc2 said:
Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.
Click to expand...
Click to collapse
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.

Type adb reboot bootloader
Sent from my GS3 on Carbon KK using Tapatalk 4

ebildude123 said:
Type adb reboot bootloader
Click to expand...
Click to collapse
That worked. I just need to, presumably, rebuild the /data and /cache partitions, I assume?

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.

greymonk said:
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.
Click to expand...
Click to collapse
Shoot me an email at [email protected] we can continue there... Thx lj

lj50036 said:
Shoot me an email at [email protected] we can continue there... Thx lj
Click to expand...
Click to collapse
Dude, thanks again. I really can't thank you enough for resurrecting this thing. :victory:

[Q] TF 700 only boots into TWRP - please advise this NOOB!

Greetings -
I have an unlocked TF700 (twrp v 2.5.0.0) and I was running cromi-x. it began to crash a lot so i tried to flash a new rom and i must've done something wrong because now the tablet will not boot up. I can get into twrp and perform the options listed (install, backup, restore, wipe, mount, settings, advanced, reboot) but nothing seems to help. I haven't played with this in probably 6 months so i'm not sure where to start. Navigating these forums is like reading latin to me. I'm sure there is an explanation for this but I can't find it. Can some one link me to an existing thread if this has been discusses previously or help me out? I can't seem to get anything working on this and it's driving me crazy. I know I need to provide extra information to help identify this issue but i'm not sure what that info that is. Any help would be appreciated!
Also, I've tried a factory reset from twrp as well and it gives me the following messages
E:unable to mount '/external_sdcard
Updating partition details...
E:Mount: Unable to find partition, for path '/'
When I reboot following this, it takes me directly to TWRP.
I'm guessing my tablet can't find my SD card? Maybe that's an easy fix?
Thanks everyone for looking at this and thanks for anyone that takes some time to educate me.

Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.

berndblb said:
Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.
Click to expand...
Click to collapse
Thank you for the reply. My bootloader is "<1.00 e> released by 10.6.1.14.8-20130514"
It also says "key driver not found" immediately before the bootloader data upon turn on

Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?

berndblb said:
Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?
Click to expand...
Click to collapse
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.

Hoggs17 said:
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.
Click to expand...
Click to collapse
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.

berndblb said:
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.
Click to expand...
Click to collapse
When i enter the bootloader, it stays on the screen. If i reboot without entering the bootloader, it goes directly into TWRP. I am not sure if i used the wipe data option or the factory reset (it has been probably 6 months). I will install fastboot on my PC now.

Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.0?

berndblb said:
Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.5?
Click to expand...
Click to collapse
Correct, i don't need any data on this tablet; i can wipe it clean. I think the last thing i flashed was Cromi-X (not sure the number; was back in August probably. My TWRP is 2.5.0.0; i haven't updated that one. I will try to do the fast stuff tomorrow morning; too late tonight. Thanks for all your help.

Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow

berndblb said:
Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow
Click to expand...
Click to collapse
I have installed the fastboot on my PC, ran it figured out my serial number as well. I will wait for your next instruction so that I don't mess anything up (again).

Hoggs17 said:
I have installed the fastboot on my PC. I will wait for your next instruction so that I don't mess anything up (again).
Click to expand...
Click to collapse
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891

das chaos said:
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself

Hoggs17 said:
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself
Click to expand...
Click to collapse
Ok, here's my thinking:
I don't know why the tablet reboots to recovery if you try to boot Android - never seen that before.
That it refuses to boot the rom - seen that plenty
That it only boots to recovery and not even to the bootloader - seen that quite a few times if the user used Wipe Data or factory reset from settings.
You seem to a have a mix of both which makes it unique.
So my advice is:
to clear the misc partition (where a "format data" request may still be lurking) in fastboot
wipe the data partition in fastboot - just general housekeeping
flash a new bootloader and recovery using your current recovery
Use the new recovery to flash the rom of your choice - which one do you have in mind?
So let's start. First make sure you have a fastboot connection:
Code:
fastboot devices
Then erase misc and user data
Code:
fastboot erase misc
fastboot erase userdata
You are still in the bootloader menu, push the Vol Up button on the flashing RCK to enter recovery
Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom
Good luck!

"Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom"
I have successfully completed the steps preceeding the above suggestions; I am not sure how to flash the bootloader. I am trying to follow the guide posted here (http://forum.xda-developers.com/showthread.php?t=2688891) by using the command code
fastboot -i 0x0B05 flash recovery twrp.blob
however, i cannot rename my blob file (contained in the 10.6.1.14.10 bootloader "second zip from the bottom" that you linked me to) to twrp.blob. it is simply called blob. am I doing this wrong? i tried using the above command with just blob and it didn't do anything.
on another thread (http://forum.xda-developers.com/showthread.php?t=2688891) you recommend visiting (http://techerrata.com/browse/twrp2/tf700t) and downloading the latest version of twrp. Should I download this file (openrecovery-twrp-2.8.5.0-tf700t.blob) and rename this to twrp.blob?
Also I am not sure on a new custom rom; i've been out of the game for a while; any suggestions?

No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...

berndblb said:
No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...
Click to expand...
Click to collapse
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...

Hoggs17 said:
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...
Click to expand...
Click to collapse
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external

berndblb said:
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external
Click to expand...
Click to collapse
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.

Hoggs17 said:
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.
Click to expand...
Click to collapse
..... which means the file got corrupted during download or copy to the card.
That's what signature verification is for.
Download it again.

Internal storage 0 mb twrp (Nexus 5 softbricked)?

So I totally messed up my phone. When booting it, CM logo will take forever to disappear. Hopefully I can go to bootloader. I have installed latest version of TWRP. TWRP logo stays up for about 5 minutes then it loads the main menu.
It shows internal storage o mb. If I flash custom rom or firmware, it shows unable to mount /data, /persist, /cache. Even I couldn't unmount the partition through ADB Shell as it shows error "device or resource is busy". What is the solution for this? I badly want my phone back. Even I think I lost all my important data. Please help me to solve this. What could be the actual solution? And I am a noob. So if you instruct me with a solution, be descriptive. Thank you.

Can you get in fastboot mode? If so install the latest factory image.

rdmunn said:
Can you get in fastboot mode? If so install the latest factory image.
Click to expand...
Click to collapse
I tried but device will not mount /data. So flashing fails

hiren43 said:
I tried but device will not mount /data. So flashing fails
Click to expand...
Click to collapse
Try this fastboot command:
Code:
fastboot erase data
fastboot erase cache

Phone does not boot to ROM but only recovery. Must boot bootloader, "Normal Powerup"

Phone does not boot to ROM but only recovery. Must boot bootloader, "Normal Powerup"
My Moto G (2003) has TWRP. When I switch on the phone, it only boots into recovery TWRP 3.0.2.0, no matter what ROM I install.
However, when I boot the phone into bootloader mode and then select to do "Normal Powerup", the phone boots the installed ROM.
It is really strange.
Any hints on how to figure out what is happening? And how to fix?

Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

lost101 said:
Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
Thanks, this solved the problem.
Before, this partition had the strings
Code:
$ adb shell strings /dev/block/mmcblk0p30
boot-recovery
recovery
qe 1/1
Once the partition was cleared up (and stayed zeroed out), the phone would boot to the ROM.

lost101 said:
Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
I have the same problem, but I got the error message:
Code:
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
When I tried to run the suggested soultion.
Any idea how to solve this?

rrd108 said:
I have the same problem, but I got the error message:
Code:
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
When I tried to run the suggested soultion.
Any idea how to solve this?
Click to expand...
Click to collapse
Yes, ignore the error message. The infinite number of zeroes from /dev/zero doesn't fit into the limited space of a partition, but when you get the message the partition is already filled.