Database Info

HELP! Soft-bricked Transformer tf300 - sdcard mounting issue

Hi everyone,
First post (brilliant video!).
My tablet:
Asus Transformer Pad TF300 (rooted)
CWM 5.8.2
My problem:
- We decided to give our Transformer to my gf's dad for his birthday. I tried to backup using a later version of CWM (6 something) but it didn't work. I downgraded to 5.8.2 and it worked fine. I then did a factory reset (which I realise now was not the way to go).
- CMW bootloop : restored my backup, successful - still bootloop.
- Have spent the last 4 hours figuring out ADB and managed to push both a new recovery (rogue) and the latest ASUS firmware to the SDCARD. Despite it confirming the transfer from the cmd line I could not see the zip files in the directories. I tried several times to several different directories. On the last try before the SD card decided to go on vacation I did see one of the files in the root directory.
- Now, no matter what I do, I get a "can't mount /SDCARD" error. Trying to erase/format/factory reset the pad results in errors when trying to access DATA and SDCARD.
- I've located and tried several different scripts from different threads that supposedly create a fake SDCARD directory but nothing has worked
http://forum.xda-developers.com/showthread.php?t=1679274&highlight=encrypted&page=3
- I've also tried to run the install package remotely from ADB but the mounting problem reoccurs
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
It appears that many people have encountered similar problems but none of the recommendations have been successful for me so far.
There also seems to be a strange anomaly with the adb shell timing out before I can finish the command. Is this a cable issue?
I'd be super grateful to anyone that can help me sort this out.
Cheers
Sam

Anyone?
I should mention that I had installed Super SU / Super User on the tablet... if that makes any difference.
I woke up this morning and booted the tablet to get this:
E:can't mount /cache/recover/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
Error mounting /cache!
In addition to all the previous problems.
Super!

Nobody? Anybody?! Please help!

Hi,
If you have fastboot mode, try to inject twrp (the last 2.2.x.x or something like that) ...
--> read the way to do that on the http://teamw.in/project/twrp2/97
With last TWRP you can mount sd card (first download & extract stock rom .zip and put it on root of your sdcard)
After that, flash stock rom with TWRP ...
Choose fastboot method...be careful (there is 2 versions : JB or ICS)

SOFT BRICK fixable!!! although root repair not yet covered...
I seemed to have a simular problem on my tf300t.
tried to install a CM 9.1.0 (stable)
Stuck at asus cold boot screen.
Solution i found+
*download Fastboot and an adb.shell brigde if you dont already have it.
*place the downloaded systemware (AVALIBLE ON THE ASUS SUPPORT WEBSITE) you wish to install in the same folder you have fastboot. (example-US_epad_10.4.3.13.blob)[432.3MB]
*Boot tablet into CWM [NOTE: I used CWM-Touch. 6.0.3.1 or something along those lines] (TWRP- im unsure if the process is the same).
-from advanced settings at the bottom, wipe dalvik cache.
-no need to wipe your user data cache, but wipe other data cache.
-reboot to bootloader and select fastboot option. (3rd one with pic of usb) DO NOT PLUG IT IN YET.
*Back on your WIN pc open your windows explorer, find the folder containing the Fastboot.exe and hold shift and right click at the same time for an admin operations menu. You should see an option "Open Command Prompt Here". Click it to begin a Fastboot session.
*NOW CONNECT YOUR TABLET!!!
*TYPE THE FOLLOWING AS SHOWN! DO NOT DIVERT OR YOU SCREW UP-
fastboot -i 0x0B05 flash system blob
***NOTE THAT THIS METHOD WILL TAKE QUITE SOME TIME AND YOUR COMPUTER MAY EVEN LOOK LIKE ITS FROZEN...STOP! JUST LET IT DO WHAT YOU ASKED IT TO...THIS IS QUITE A LARGE TASK AND WILL TAKE TIME. MY PC IS AN OLD DELL E300 dem. I KICK THE PROCESS ATLEAST A DOZEN TIMES BEFORE I JUST LEFT IT ALOOOOONNNE and it worked...although i cant seem to figure out how to delete the old su binary i install so i could re-root it....ANYONE GOT ANSWER? PLEASE HELP. EMAIL IS ALWAYS UP.
IF THESE INSTRUCTIONS ARE UNCLEAR, OR YOU DONT UNDERSTAND SOMETHING, MESSAGE ME...
AND IF THIS HELPED YOU...SHARE THE LOVE-GIMME A THANKS!

Encryption unsuccessful help

Hello,
I turned on my Xoom to see "Encryption Unsuccessful" tonight. If i boot into stock recovery and try to factory reset, it cannot mount Cache. If I plug the device into my computer, fastboot can find it but ADB cannot. I have the proper drivers installed. I can't get into my tablet to turn on USB debugging. I just bought an OTG cable to try to fix it, but cannot find the update.zip file that I need. If i try to fastboot oem unlock, it fails. I've tried everything I can find, I've done hours worth of playing/trial and error to no avail. Any help would be fantastic. Truly at a stand still. Please ask with any specifics needed to assist me.
Is it possible to flash to CWM recovery without being able to boot/find it in ADB?
Thank you,
Bradon

>.<
Nearly to the point of offering some sort of payment for assisting me. I'd rather not ship it out, but more than glad to work something out paypal or giftcard wise. This tablet is the only thing keeping my wife entertained, and another tablet is not in the budget.

But u can connect with fastboot to device ?
if yes this should help you
http://forum.xda-developers.com/showthread.php?t=1451655&page=7
http://forum.xda-developers.com/showthread.php?t=1049485
Probably you will lose all data on it ... Why u wanted to encrypt u device ...
I did it too but it was missunderstanding specialy when flashing a lot .

Alright so...
I've used fast boot flash user data, system, recovery and boot. Those are all successful, but if I reboot.. Nothing changes.
I've loaded many zips onto a flash drive with an otg cable, boot into the stock recovery and try to update, unable to verify signature.
Adv will not find the device, reinstalled drivers many times
Rsd will not find the device
Factory reset fails, cannot mount cache and about 10 other cache/recovery errors
Fast boot OEM unlock fails, unable to write a certain 3 letter file
I'm at work right now, so I can post specifics/pics later.
I didn't try to encrypt it, it seemed like a virus that my wife got. She clicks on advertisements, downloads sketchy files/apps.
It is unrooted, stock recovery.
20+ hours of research and trial.. No success.

Can u use this ?
http://forum.xda-developers.com/showthread.php?t=1074979
Use 2 method.
Write response what happend and it does flash recovery .
You have to unlock bootloader
look here simillar problem :
http://forum.xda-developers.com/showthread.php?t=1571827
http://forum.xda-developers.com/showthread.php?t=1952628
And u do not need any special otg cabel - use stock xoom from package. OTG is for host-usb.
Anyway u will have to do it with fastboot , probably /cache partialy encrypted.

Alright, I just followed the CWM recovery guide.
First off, ADB does not find my device, meaning I cannot reboot into the bootloader. I can flash the recovery only after flashing userdata for some reason. After flashing, it says complete though when I reboot nothing changes. The other 2 links, first one I can't use because adb doesn't find my device, and the 2nd one.. I don't think xoom has a "download mode".
Thanks

Ok, so when u push down button in booting u have only recovery ?
U should have fastboot too ... try to press up vol 1 s after booting, then connect to pc, and check in device manager rmb on "My pc"
And ? .... This must working ... Use fastboot.exe in cmd ( in windows 7 ) on Administrator User.

Also, when I first boot up recovery I get
E: failed to mount /cache (invalid argument.)
E: Can't mount /cache/recovery/command
E: Failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E: Failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E: Failed to mount /cache (invalid argument)
If i try to factory reset or clear the cache, I get the same message.

U do not understand what u reading, u cant do this from recovery ...
U have partialy crypted storage ... its normal!
1. download fastboot on windows
2. install drivers from
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
Click to expand...
Click to collapse
3. run fastboot protocol on xoom press down vol "find fastboot" if not press top vol in booting - should fastboot protocol ... in output
4. Use fastboot.exe from android sdk - run in in cmd ( Run ad Administrator , right click on cmd)
4. unlock bootloader
5. flash rom boot recovery in *.img format!
This must working...

When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"

bcwest said:
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
Click to expand...
Click to collapse
Is it bad ? - now when u show up "fastboot protocol ... " on xoom run fastboot from android sdk .

Fastboot ran from cmd with admin privileges.
fastboot oem unlock
used volume controls to select yes/i accept
Device unlock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:324 NvStorMgrFileOpen("UDA"):196624
ERROR: Failed to format UDA.
Error while unlocking device.

unplug mmc card from xoom and try again, where did u get files ... system.img ,recovery.img,boot.img ?

I've tried with both the mSD card in, and out. I got the boot/system/recovery/userdata from the stock image post from XDA.

ok, I didnt tryed this with stock rom, try to change recovery with http://forum.xda-developers.com/showthread.php?t=1074979
reboot and try to get to new recovery.
do this:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img <- from http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )

mx600 is the model that I have.
All of the flashing goes through fine
fastboot erase cache fails instantly (Failed to format PDB)
fastboot erase userdata fails instantly (Failed to format PDB)
fastboot reboot
volume down for recovery to see if CWM changes went through
stock android recovery

If I put my mSD card back into the unit, and try to do it all over again..
Flashes go through fine
Cache fails instantly, same error
Erase userdata causes my cmd to hang up, and the xoom sits at "StorMgr Formatting UDA STATUS: | | |"
5 minutes later, still sitting at that message.

Mx600, I restarted the device after flashing everything, If I let it go past the Dual Core Technology big red M, it boots into android but all that I get is the Encryption Unsuccessful screen. It says push restart, but it does nothing.
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )[/QUOTE]

Damn, that mean bootloader is locked or he have problem with gpt ?
ok... I'm not sure what will hapend but u can try to lock it again
fastboot oem lock
then reboot
fastboot oem unlock
output ?

Device Lock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:350 NvStorMgrFileWrite(ff, 0x00004000:00000000):196608
ERROR: Failed to format UDA
Device lock operation FAILED.

[Q] Bootloop, Rom Manager, no restore possible

Can be closed!
Oh man, I read the warning too late.
I had a few issues installing Rayman's 4.2 on my TF101 with clockworkrecovery v5.x (Error was not able to open /cache/recovery/** or so. Shouldn' t matter anymore).
Call it stupidness, I thought using the actual cwm version would solve my problem.
As you can see, it did not.
I flashed v.8, the addons and the gapps. No errormessage (did not get any with the older version either).
But it is stuck in a bootloop.
Not too stupid, I did a backup before - sad but true I can't use it. (E:unknown volume for path[/sdcard/]\\E:Can`t mount /sdcard)
Of course I am not able to flash any other rom from internal sdcard. (not even think about external sd!)
I can push a rom to sdcard via adb push, but can`t use it (>choose zip from sdcard \\ E:unknown volume for path[/sdcard/]\\E: Can`t mount /sdcard/) and after reboot the rom dissapears.
Pushing to /data/media is not possible, as media does not exist.
Fastboot seems not to be a possibility, as I can`t boot in bootloader mode... (but tell me, if I am wrong!)
So if anybody knows a solution - I would be so happy!
Update 1:
I followed these instructions:
www tabletroms.com /forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
I installed Nvflash on my linux pc.
APX mode works, I just had to do what people told me to. (Press Vol UP(!) and Power Button)
Connect via USB.
Then run sudo ./download.sh
Everything looks fine, but then again: An error occurs:
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Update 2:
I tried another version. For some reason, my TF is not WW, as I thought than US...
Everything is fine, I am happy again. Maybe it helps anybody? And if not - I had my xda rubberduck.

[Q] Galaxy S3 Soft Bricked? & no access to E: or Internal or extSD cards

My phone is a Samsung galaxy S3 SCH-S968c, Verizon Networked for Straight Talk. I ran into having my phone stall after the Samsung logos boot up and then the tracfone logo appears and stalls there. The issue started after i tried installing multiple tweeks using a popular app for rooted devices (i cant think of the apps name at the moment). I have a version of CWM on it. After reading threads here in XDA i found that my CWM will not work correctly on this phone. Retired Forum Moderator "edfunkycold" said "It's not really a bug with the recoveries which where modded. It's part of whatever Samsung has done to keep people from rooting and flashing roms." so i downloaded both CWM_mod2.img and TWRP_mod2.img.
So between the soft bricking and the usless cwm i cannot flash anything or access the internal or external sd cards. I tried using ADB and these commands:
adb push .img /sdcard/.img
adb shell
su
dd if=/sdcard/.img of=/dev/block/mmcblk0p18
I just get the Android Debugging Bridge version...............
I also tried other methods found in XDA using ADB.
I tried Samsung Kies, 4 versions of Odin, SkipSoft Android Toolkit and some other java executable program that didnt work.
I can boot into both recovery mode and download mode.
Recovery mode does nothing....
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /sdcard
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
.....etc. etc.
In Download mode, Odin recognizes that the phone is connected but when i try loading anything it wont connect. example: trying to load a bootchain file it says:
checking MD5 finished successfully..
Leave CS..
All threads completed. (succeed 0 / fail 0)
Other attempts show the RED FAIL square.
Im having trouble finding the correct Files to Flash. Im guessing the SCH-I535 is the non-straight talk equivalent to my straight talk phone so i have downloaded file: Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip
and Rom: Sons Of Android - cm-10.2-20130928-UNOFFICIAL-jewel.zip
Bottom line is I DONT CARE what version of android (stock or ROM) as long as it's compatible and need the correct flash files necessary. I THINK it originally has jellybean 4.2.2??? PLEASE help. ive been messing with this for 3 weeks now :crying:
Thanks

try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.

jbaker22 said:
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
Click to expand...
Click to collapse
ADB is not recognizing my phone. Odin still is. I tried to flash recovery with Odin last night. The process completed with success but when i restarted the phone i was not able to gain access back to the recovery. Now I can only get into download mode. Is this why ADB is not working, cuz it has to be in recovery mode?
Also I am confused on how the file structure should be when i put a rom on the sd card. I know they go in the root..... do i just extract them from the ZIP straight over to the SD? Is there a way to convert ZIP files to an Odin flashable file?

FIXED!!!! w/ Straight Talk Stock Firmware SCH-S968C
I FINALLY found a working download link for the correct firmware!!! Thanks to an old post by Kenny1974 who posted the name of the file. I googled it and found only one available!
https://www.dropbox.com/s/j2uc1hkm4...8CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
I Flashed with Odin and Presto!
If this link becomes invalid, p.m. me and i will send you a link or the file.

Asus TF700T boot loop

Some time ago I successfully unlocked my TF700 and installed one of the Cromi-X roms. The machine wasn't improved that much and was still very slow with frequent messages asking if I wanted to wait for apps to respond or to close the app. I thought I would try the "Revisited CROMi-X-ET_v3.0-RC2" rom as that allowed the f2fs file system and I wondered if that would be faster. I installed TWRP version twrp-3.0.0-0-tf700t and did the install of the above rom using TWRP and choosing all the default options which reformatted some of the partitions to f2fs.
On reboot I got the start screen and then after a while a reboot again repeatedly. I tried booting to recovery and just got the Teamwin screen.
I then reinstalled TWRP using fastboot and a USB connection. I have tried twrp-2.8.7.0-tf700t, twrp_tf700t_kang_2.8.7.4, and twrp-3.0.0-0-tf700t and all give error messages when I do a wipe, try to restore a previous backup or try to install a new ROM.
On 2.8.7.0 the log I get from a wipe is:-
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/staging'
Erimary block device '/dev/block/mmcbblk0p8' for mount point '/data' is not present!
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Kernel does not have support for reading SELinux contents.
E:Unable to mount '/cache'
E:Unable to set bootloader message
E:Unable to mount '/cache'
E:Unable to mount '/data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
E:Unable to mount '/data'
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
E:Unable to mount storage.
The twrp_tf700t_kang_2.8.7.4 version gives similar messages except it says failed to unmount system cache and data. The log from twrp-3.0.0-0-tf700t is the same as the kang version except this one says failed to mount the three partitions.
After reading another thread with similar symptom, I tried to format a partition using adb with the shell command:
make_ext4fs /dev/block/mmcblk0p8
this returns Need size of filesystem.
I would be grateful if anyone could help (or is my tablet irretrevably bricked).

What's the version of your bootloader?
Boot to TWRP and run "adb shell dmesg > dmesg.txt" and post the resulting file.

_that said:
What's the version of your bootloader?
Boot to TWRP and run "adb shell dmesg > dmesg.txt" and post the resulting file.
Click to expand...
Click to collapse
I did this some time last week but got no text file for some reason. Repeated it without the redirect to file and copied from the cmd window. It's a very long file however. Do I paste it in here or is there some way of attaching it so you can see it (I'm new to posting in forums)
How do I get the boot loader version?
Thanks for trying to help.

kenhanley said:
Do I paste it in here or is there some way of attaching it so you can see it (I'm new to posting in forums)
Click to expand...
Click to collapse
This forum has a feature to attach files (use the paper clip icon). I'm not sure if new users are allowed to attach files - if not, put your log on pastebin and add the relevant part of the URL to your answer.
kenhanley said:
How do I get the boot loader version?
Click to expand...
Click to collapse
Boot to the bootloader (Power+Volume down), read the small text in the upper left corner.

_that said:
This forum has a feature to attach files (use the paper clip icon). I'm not sure if new users are allowed to attach files - if not, put your log on pastebin and add the relevant part of the URL to your answer.
Boot to the bootloader (Power+Volume down), read the small text in the upper left corner.
Click to expand...
Click to collapse
As far as I can tell with two pairs of reading glasses on (its an age thing), the second line reads
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
I don't see the paperclip and - sorry to be so ignorant but - how do I logon to pastebin
Regards
Ken

kenhanley said:
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Click to expand...
Click to collapse
OK, that's the correct version.
kenhanley said:
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
Click to expand...
Click to collapse
You need to fully reboot after installing TWRP via fastboot (however you can go directly to the bootloader menu and select RCK, no need to start Android), otherwise it can't access your partitions.

kenhanley said:
As far as I can tell with two pairs of reading glasses on (its an age thing), the second line reads
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
I don't see the paperclip and - sorry to be so ignorant but - how do I logon to pastebin
Regards
Ken
Click to expand...
Click to collapse
I think I manage to paste into pastebin under title KenHanley demsg. Not sure how you get to see it.
Regards
Ken

Not sure I understand about the reboot after TWRP install. When I install TWR the tablet is sitting with the three icons RCK Android and Wipe Data. After install completes if I press Vol up with the RCK flashing TWRP works. If I reboot straight away TWRP hangs on the start screen or tries to reboot after a time depending on which version I installed. Same thing happens after powering down from running TWRP without the reboot.
Regards
Ken

just realised youasked for pastebin url. It's
pastebin/4Bh8zdXa
regards
Ken

kenhanley said:
Not sure I understand about the reboot after TWRP install. When I install TWR the tablet is sitting with the three icons RCK Android and Wipe Data. After install completes if I press Vol up with the RCK flashing TWRP works. If I reboot straight away TWRP hangs on the start screen or tries to reboot after a time depending on which version I installed. Same thing happens after powering down from running TWRP without the reboot.
Regards
Ken
Click to expand...
Click to collapse
There's your problem, as _that said: You need to reboot after flashing TWRP before you can use it:
Flash TWRP
Reboot into bootloader
Enter TWRP by selecting the RCK icon.
I know you said TWRP hung if you reboot straight away, but that is strange. Describe step by step how you flash TWRP.

OK.
I boot TF700 with vol down pressed. Connect USB to computer running windows 10. Open cmd window. (copy from cmd window below):
C:\adb>fastboot flash recovery twrp-2.8.7.0-tf700t.img
sending 'recovery' (7372 KB)...
OKAY [ 3.418s]
writing 'recovery'...
OKAY [ 6.528s]
finished. total time: 9.951s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb>
Holding vol down when typing fastboot reboot. Press Vol up when RCK is flashing. Teamwin screen comes on then briefly flashes off and comes on again and that is as far as it gets.
Same thing happens if instead of typing fastboot reboot I press and hold the TF700 power button to reboot.
If I skip the reboot and press Vol up after the flash has finished TWRP starts up and after a delay I get all the various buttons to Install, Backup, Restore etc.. Then I get the storage not mounted problems

Do not touch any button on the tablet after the recovery flash. Just type fastboot reboot, then hit enter.
After you've seen the Asus logo with a blue bar underneath filling up you can reboot into the bootloader and enter recovery.

Just done that. I get a blue bar when I flash.
After fastboot reboot the screen blanks then the Asus Logo comes up but no bluebar. Eventually after displaying the Asus screen for about 35 seconds the tablet reboots itself in the bootloop I originally mentioned. Booting to recovery gives me the teamwin screen hangup I described above.
I repeated and this time instead of waiting on the Asus screen I rebooted from the Asus screen by pressing and holding power and vol down. Same happens TWRP hangs on Teamwin screen
Sorry I'm causing all this trouble.
Regards
Ken

Never seen that before and I don't have an explanation for it either....
What kind of wipes did you do before flashing the new rom?
Don't know.. maybe @_that has a better idea, but at this point I would flash the Asus firmware in fastboot and start from scratch.....
Hang in there for word from @_that, otherwise I can hook you up with instructions for the fastboot firmware flash
Sent from my ASUS Transformer Pad TF700T using Tapatalk

kenhanley said:
C:\adb>fastboot flash recovery twrp-2.8.7.0-tf700t.img
sending 'recovery' (7372 KB)...
OKAY [ 3.418s]
writing 'recovery'...
OKAY [ 6.528s]
finished. total time: 9.951s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb>
Holding vol down when typing fastboot reboot. Press Vol up when RCK is flashing. Teamwin screen comes on then briefly flashes off and comes on again and that is as far as it gets.
Click to expand...
Click to collapse
I think it's crashing due to a corrupted filesystem. Reboot to TWRP, and with the splash screen flashing, run this:
Code:
adb pull /tmp/recovery.log
Post the resulting file.
To reformat /data as f2fs (be careful with this command and press Enter only after double-checking that you got the "p8" right):
Code:
adb shell mkfs.f2fs /dev/block/mmcblk0p8

_that
I posted the recovery log http://pastebin.com/PdZVbEsC title KenHanleyrecoverylog.
Just did the format of /data then installed TWRP again. Reboot still didn't give a blue bar but Yipee The bootloop is gone and I'm into the setup screens for the ROM I flashed that caused all the bother. Thank You
berndblb
I looked on the Asus site for firmware but they don't list the TF700T anymore. I would be grateful if you can point me to the files and instructions for the Asus firmware in case I do need to do a restore to original.
Thanks again to you all for the help

It's not the rom that did it - I'm running it without trouble for months! It was what you did.
http://www.transformerforums.com/fo...e-firmware-tf101-tf201-tf300-tf700-tf701.html
Check out post 2 and download a copy. Who knows when Asus takes it down entirely....

I didn't mean to imply it was the ROM. It seems to be running OK now. I think somehow the formatting of \data went wrong during the install but I can't identify anything I did that could have caused it. Anyway I'm just grateful to you guys for digging me out of the hole I dug for myself. Thanks for the link, I got to the firmware download page OK from that. I'll grab everything I can now while the going is good.

I realize this is an old post, but hopefully ....
I have the same problem except that it will only boot to the splash screen of TWRP3.1.x.
I had KatKiss 7.1 on it and rebooted it and into a loop. I re-flashed TWRP V3 via fastboot and the much discussed blue line was there, a "fastboot reboot" just sent me into the boot loop again. Pwr/Voldn gave me the 3 flashing icons, but selecting recovery just gives me the TWRP loading screen for about 10 seconds or so, then reboots.
I'm assuming I have to start from scratch as well but am a bit confused as to which firmware from asus' site and how to do this.

Strange - I wonder what it is that prevents TWRP from booting....
Did you try the command from above to reformat data to f2fs?
If nothing resolves this you can always flash the stock blob in fastboot.
The firmware is here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Download the SKU for your region (most likely WW or US).
Unzip it twice and copy only the blob into your fastboot folder.
Then try this:
Code:
fastboot erase userdata
Now try to boot into TWRP via the buttons
If that did not do it, continue with:
Code:
fastboot erase misc
fastboot erase cache
Again boot into TWRP and see if that did it.
If not continue with this:
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot flash system blob
fastboot reboot
The commands will finish fairly quickly except for erasing data and flashing the blob. Be patient.
If you're not the inquisitive type who wants to find out what the problem is and more the roundhouse-punch-radical type you can also run all the above commands one after the other in one go to get you back to stock. The order is not important as long as you flash the blob last. Before rebooting that is.
That should return you to a stock JB 4.2 system.
Then flash TWRP, format data, convert it to f2fs and finally flash the rom or restore your last nandroid.
Good luck