With the latest version of TWRP (2.8.5.0) I installed that zombi 5.02 rom a few days ago. It was running VERY slow, so I went back into TWRP a few hours ago and figured I would clean up the device and then re-install the rom.
So I used TWRP to wipe the device clean (I selected every partition to wipe, which I suspect is what the problem is). After doing this, I ran the install of the rom which seemed to run fine (although oddly, it seemed to install too fast, as opposed to when I installed it before).
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
I booted into fastboot, and via adb I re-installed the 2.8.5.0 twrp blob file. No errors during the install at all, however after rebooting the device, I am having the exact same issue.
I've tried re-installing twrp 3 times this way, but no matter what I do, I cannot get twrp to get out of this boot cycle.
It is odd that I can install twrp via adb over and over, yet it still has the same problem as before.
Even if i messed up by wiping every partition, why would the TWRP install succeeed, yet the program not run?
Anybody have an idea as to what I can do in order to get twrp back up and running? And if I do, is there something else I need to do to get all the partitions back up, or in theory will installing a rom re-create everything as needed?
Thanks for any help you guys can provide!
gbako said:
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
Click to expand...
Click to collapse
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.
_that said:
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.
Click to expand...
Click to collapse
--
I retrieved the logs as you suggested. I did this twice because after I retrieved the logs, I was looking at the partitions.log file and saw that only 3 partitions appeared. I know there should be more partitions (I don't know what they are called, but I know there should be more). So I was playing around with the fastboot.exe command, and I saw a command (fastboot -w). It said this command "erases userdata and cache". Well, it looked like something good to try, so I ran the command I've attached a file to this post called "fastboot.txt" that shows the output of this command.
Anyways, after doing this (thinking maybe this would do something), I went back into fastbook, and re-installed TWRP once again. Then I rebooted the tablet, and viola! It booted into twrp. Think I was so smart, I figured I would try to install my rom once again, so I started the installer of the rom, but at the very first screen of the installer where it shows device information, I saw what was obviously an issue. System size was showed as -1 MB, and Data Size was also shown as -1 MB. Not looking good, I exited the installer which puts me back into TWRP, and now I see a bunch of error messages about missing partitions.
On a hunch, I rebooted the tablet (back into reovery), and now I am back to the same thing, where TWRP will constantly load the blue curtain backgroud, show the word "teamwin" and then clear the screen, and repeat the process endlessly. So I now re-ran the two commands to retreive the partition info and the recovery log. The recovery log doesn't make much sense to me, but interestingly the partition log now shows a whole bunch more partitions. However, TWRP is once again back to it's boot loop.
So rather than re-trying my silly "fastbook -w" attempt, I will post this message, provide the request log info, and hope one of the experts here have a kind suggestion for me to try
Thanks guys for any help!
P.S. All the logs are in the ZIP file. I also attached a pic I took of the zombi rom installer, showing the partition size being -1 MB
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.
gbako said:
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.
Click to expand...
Click to collapse
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt
That worked! Tablet works once again!
_that said:
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt
Click to expand...
Click to collapse
---
That worked! Shortly after running that "adb shell make_ext4fs /dev/block/mmcblk0p2" command you had suggested, the tablet rebooted it self and the last ROM I had installed in it automatically booted up. It acted as though I had just installed it, so I went thru the standard setup (enter Google ID, etc...). The rom still runs pretty horribly (very slow and sluggish), but that's an issue with the rom hehe I am also able to boot back into TWRP without any problems. It seems that partition was the problem.
Thank you very much for your help; much appreciated!
I had the same problem with my TF700T with an endless loop in the TWRP start screen. I found an unkown device in my device manager called "TRANSFORMER" and i installed the Universal_Naked_Driver. Now i had access with ADB and i could clean the cache with the command here. Now my TF700T is back to life. Thanks a lot !
I seem to have a similar problem. The pad started having random reboots but it managed to fully boot. Since yesterday it is in the reboot loop. When trying to boot into twrp 2.8.7.4 it shows the teamwin screen for a short while and then reboots again.
I pulled the files requested above:
recovery.log
partitions.txt
dmesg.txt
I also tried:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
which shows:
Code:
C:\adb>adb shell make_ext4fs /dev/block/mmcblk0p2
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
However the recommended steps don't seem to help in my case.
I'll attach the log files. (If I can find the attachment icon that is)
Thanks for any help you guys can provide!
Rom and bootloader version please. To attach the logs use your browser to access XDA
Hi berndblb,
thanks for the quick reply.
Rom version is : KatKiss-6.0_TF700T_022.zip
Boot loader taken from the fastboot screen: Android cardhu-user bootloader <1.00e> released by "ww_epad-10.6.1.14.10-20130801" A03
As to attaching the files I think I'm blind as I'm not seeing the option to do so.
Looks like this is only an issue in this threat as I do have the icon in other posts.
Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?
Cathrin said:
Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?
Click to expand...
Click to collapse
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?
berndblb said:
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?
Click to expand...
Click to collapse
I think my very first upgade to 5.1.1. lolli pop has been a Zombi-Pop and a overclocking yes. But since then only the KatKiss versions.
At least everything works fine again now.
So thanks for the help.
Looks like I have this constantly boot to twrp issue. It doesn't stay into twrp long enough to do anything.
adb pull /tmp/recovery.log
Gives me error: Protocol fault (couldnt read status: no error
adb shell cat /proc/partitions > partitions.txt
Gives me the same error above.
adb shell make_ext4fs /dev/block/mmcblk0p2
Gives me filesystem with parameters----created filesystem with 11/27392 inodes and 3534/109568 blocks
fastboot erase misc
Gives me waiting for device
I was on Katkiss 22 before this happened.
Any help would be appreciated.
Hi Isham.padron,
yes that sounds familiar.
I could only get the logs with adb shell or put when I hit return at a very specific moment.
It did fetch the files only when the blue teamwin window has been shown.
Though my recovery.log always looked a bit too short as if the reboot was coming in the way.
for me in the end only fastboot erase userdata did the trick. Everything else failed.
fastboot erase userdata cause it to wait but then nothing happens. ADB seems to be more responsive. IDK, I loved my TF700 and Katkiss gave it new life.
If you get 'waiting for device' your pc does not recognize the tablet. You may have to install fastboot drivers. Check the entry in Device Manager. How does the tablet show up?
In device manager is shows up as ADB. That kind of explains it. I'm using a windows 10 pro machine and I installed ADB/Fast boot with this http://forum.xda-developers.com/showthread.php?t=2588979
Are there issues with Win 10? I dont know how to proceed.
When I do the vol up(left) and power combo and it boots into twrp and then reboots regardless. I don't have the option screen anymore
Did you disable driver verification in Windows before running the tool? Otherwise they probably did not install properly. Windows is a pain with drivers and Win 8 and 10 are very finicky with fastboot...
Although if you have the adb composite interface showing up that's kinda good news. Watch the tablet and Device Manager at the same time and try to get a feeling for when the adb connection is there. Try to hit enter on the already typed 'adb devices' command and see what you get.
This could be tricky and rake many tries but you want to try is to push a small file to the tablet (bootit. ko) and then ins is that file to kick the tablet back into the bootloader. Probably your only chance..
Read this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Good luck!
I am able to do this.
adb push bootit.ko /
results are (27690 bytes in .023s)
When I run "adb shell insmod bootit.ko" I get Error : protocol fault (no status)
I see that on windows it starts installing MTP USB but then it fails when the reboot happens. Tablet continues to reboot.
Any ideas? I miss the TF700
Related
Hi,
I have my TF700 unlocked for a while with good results, but yesterday it was a little bit slow and i did a wipe on the bootloader thinking that it was a good idea... i did not read what dangerous it is....
After, it freezes on the asus logo on the boot.
I tried to go to the recovery and freezes on the teamwin screen....but after like 40 minutes doing nothing it goes into the TWRP 2.5.
I can go to all the options inside but says that internal memory has 0MB, that /data /system is unmount, if I try to mount freezes.
Last time (one more time waiting 40minutes) I tried to reinstall CROMIx 4.7 from the external sdcard using the install option of TWRP. I did it with no issues until the end, but it didn't finishied i think because it was on the same again.
It happened to anyone, about this 40minutes to go to recovery ?
Any solution / idea ?
the best for all.
António
antonio3073 said:
I tried to go to the recovery and freezes on the teamwin screen....but after like 40 minutes doing nothing it goes into the TWRP 2.5.
I can go to all the options inside but says that internal memory has 0MB, that /data /system is unmount, if I try to mount freezes.
Click to expand...
Click to collapse
Connect via adb shell to your recovery and post the output of
Code:
cat /proc/partitions
hexdump -C -n 512 /dev/block/mmcblk0p3
_that said:
Connect via adb shell to your recovery and post the output of
Code:
cat /proc/partitions
hexdump -C -n 512 /dev/block/mmcblk0p3
Click to expand...
Click to collapse
First, thanks a lot
I have adb installed and working, but no connection to TF by USB. I didn't know why because it worked without problems, but now on my PC says that is a driver problem.
I did the same on terminal inside TWRP at TF, that's i think the only way to interact with TF.
i am just waiting more 20minutes.... to go into TRWP to put here the result
antonio3073 said:
I have adb installing and working, but no connection to TF by USB. I didn't know why because it worked without problems, but now on my PC says that is a driver problem
Click to expand...
Click to collapse
Then you need to fix your driver problem first. The recovery reports itself as a different USB device than the regular Android OS (at least the serial number is different), that may confuse your driver.
I can't help you with your driver issues though (Linux doesn't need drivers for adb).
_that said:
Then you need to fix your driver problem first. The recovery reports itself as a different USB device than the regular Android OS (at least the serial number is different), that may confuse your driver.
I can't help you with your driver issues though (Linux doesn't need drivers for adb).
Click to expand...
Click to collapse
Please see the result here
View attachment 2244302
View attachment 2244303
better pictureView attachment 2244309
antonio3073 said:
Please see the result here
Click to expand...
Click to collapse
Partition sizes look OK (but very blurry ), so your recovery can access the eMMC. This is good, because it means you should be able to repair your system.
The output of the hexdump command would be interesting - no idea why it doesn't work for you.
Edit: "I/O error" on the new screenshot looks worrying, also "unable to set emmc bootloader message".
More detailed error messages should be available as the output of the "dmesg" command, but this will be very long, so you'll need adb for this (command: "adb shell dmesg > output.txt").
_that said:
Partition sizes look OK (but very blurry ), so your recovery can access the eMMC. This is good, because it means you should be able to repair your system.
The output of the hexdump command would be interesting - no idea why it doesn't work for you.
Click to expand...
Click to collapse
The last picture is better and has the result of the hexdump
I tried to take out output.txt of the tablet by external sdcard but recovery file manager did not save the file on external.
Than i have to ways:
1- windows usb driver solution. do you know any driver for it ?
2- I have a computer with a version of linux. Where can i learn how to install adb on it ?
Is it not possible to reinstall all from begining starting the bootloader by external sd, because the recovery seems to install ?
antonio3073 said:
I tried to take out output.txt of the tablet by external sdcard but recovery file manager did not save the file on external.
Than i have to ways:
1- windows usb driver solution. do you know any driver for it ?
2- I have a computer with a version of linux. Where can i learn how to install adb on it ?
Is it not possible to reinstall all from begining starting the bootloader by external sd, because the recovery seems to install ?
Click to expand...
Click to collapse
For linux you don't need drivers, just install the AndroidSDK for linux, there are lots of guides wich can help you do it, just search on google or xda.
You can try to install a rom from external memory but imo it will also fail.
Pretoriano80 said:
For linux you don't need drivers, just install the AndroidSDK for linux, there are lots of guides wich can help you do it, just search on google or xda.
You can try to install a rom from external memory but imo it will also fail.
Click to expand...
Click to collapse
Hi, coming again after a while to discover that my daughter's computer has linux. I am starting to be a entusiastic of it...in fact i am on it!!!.
Now i can use adb without problems and i got output.txt
Please I apreciate your suport for the next step.
View attachment output.txt
thanks a lot
<3>[ 8078.194240] mmcblk0: error -110 transferring data, sector 2532352, nr 32, cmd response 0x2000900, card status 0x0
Click to expand...
Click to collapse
Error -110 is timeout, meaning the eMMC did not react in time on the kernel's commands.
I've seen this error at recovery startup when the recovery is incompatible with the bootloader, and I've seen it for external microSD cards because the TF700 has stability problems with the UHS-1 protocol.
Try restarting the tablet (to recovery, because it will do that anyway) and get another dmesg output within the first minute - maybe there are interesting messages in the startup sequence.
_that said:
Error -110 is timeout, meaning the eMMC did not react in time on the kernel's commands.
I've seen this error at recovery startup when the recovery is incompatible with the bootloader, and I've seen it for external microSD cards because the TF700 has stability problems with the UHS-1 protocol.
Try restarting the tablet (to recovery, because it will do that anyway) and get another dmesg output within the first minute - maybe there are interesting messages in the startup sequence.
Click to expand...
Click to collapse
a dmesg after 40minutes of booting to recovery
View attachment output.txt
there is anyway to reinstall bootloader from adb?
antonio3073 said:
a dmesg after 40minutes of booting to recovery
View attachment 2248488
Click to expand...
Click to collapse
You could not get an adb connection any earlier?
_that said:
You could not get an adb connection any earlier?
Click to expand...
Click to collapse
i rebooted, and yes, i have adb just after appear teamwin screen for the next 40minutes
new output
antonio3073 said:
i rebooted, and yes, i have adb just after appear teamwin screen for the next 40minutes
new output
Click to expand...
Click to collapse
OK, the timeouts start almost immediately after the startup, but the recovery kernel does detect the correct partitions. So maybe it just can't write properly but read...
Let's try a "defibrillation":
Download this zip file to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
* Unpack it - you'll get a file named "bootit.ko".
* Push it to your tablet, e.g. with "adb push bootit.ko /".
* Run "adb shell insmod /bootit.ko"
This should reboot immediately to the bootloader menu where you can try to cold-boot Android, or to enter the recovery the "normal" way, or you can try to use fastboot to reinstall a recovery. I would not try to flash the bootloader until it is confirmed your eMMC works properly at least outside the recovery.
Edit: for reference, this is the thread where I developed the "bootit.ko" module to unbrick a TF700: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
OK, the timeouts start almost immediately after the startup, but the recovery kernel does detect the correct partitions. So maybe it just can't write properly but read...
Let's try a "defibrillation":
Download this zip file to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
* Unpack it - you'll get a file named "bootit.ko".
* Push it to your tablet, e.g. with "adb push bootit.ko /".
* Run "adb shell insmod /bootit.ko"
This should reboot immediately to the bootloader menu where you can try to cold-boot Android, or to enter the recovery the "normal" way, or you can try to use fastboot to reinstall a recovery. I would not try to flash the bootloader until it is confirmed your eMMC works properly at least outside the recovery.
Edit: for reference, this is the thread where I developed the "bootit.ko" module to unbrick a TF700: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
it does a shutdown imediate, not a reboot
i have to turn on again, but happen the same
I was looking at output file trying to undestand something. I saw fist error is
lost page write due to I/O error on mmcblk0p8
do you think is a hardware problem on the internal sdcard and nothing to do?
I tried to put a new recovery twrp 2.6 by adb but:
~ # dd if=/twrp.blob of=/dev/block/mmcblk0p4
dd: writing '/dev/block/mmcblk0p4': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 16.133516 seconds, 0B/s
The I/O error is everywhere .....?
antonio3073 said:
do you think is a hardware problem on the internal sdcard and nothing to
do?
Click to expand...
Click to collapse
Hard to say... at least the recovery has severe problems writing to the eMMC - which is strange, because normally it should be compatible with the recent bootloaders. Since you can't boot anything else we don't know if it's only the recovery or a hardware problem. Also strange that my reboot-to-bootloader module just shuts down in your case instead of rebooting.
I'm out of ideas.
If you don't have ideas, imagine myself....
This case for me is a return to my old times on electronics and systems at the time programing assembler on microprocessors intel and texas...good times..
Now more than a destroied tablet (there is a lot more on shops to buy) it's a chanlange for me to understand how android is structured and how it process.ware
Is true that there is 3 parts?:
- bootloader (like bios on PC)
- recovery (like software to change bios on PC)
- firmware (like windows on PC)
all are in diferent mount files, correct ?
In this case the bootloader works normal since power+vol-, can i conclude that bootloader is ok? is function is to stop there?
The recovery that is 40minutes to appear seems to be bad, correct? than i tried to reinstall.
The firmware that no more appear problebly it is not invoked because it stops before.?
It seems that are some problems wirting on internal sdcard as we see on output.
The strange is if i try to reinstall firmware cromix, it goes to the end wiithout any problem, just doesnt start, what seems to doesn't have problems to write..
On the recovery on file manager or on the install says internal space 0MB, not strange ?
can we make something diferent even has risk?
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Long story, short:
For some reasons, seems like the WIPE command from TWRP and CWM recovery screw the partitions.
No partitions or microSD card can be mounted.
The tablet is now booting only in recovery mode or in fastboot mode (the screen with three icons - RTK, Android and WIPE) instead of Android.
IMPORTANT:
If your tablet reboot in fastboot mode DONT WIPE IT AGAIN! Just skip step 4.
First of all, MAKE SURE YOR BATTERY IS CHARGED!
Recharge your tablet for at least two hours.During the flashing process the tablet doesn`t charge.
Use the original Asus USB cable that came with the tablet or a high quality replacement cable. Cheap cables can and will cause problems.
Use a laptop or desktop with known good USB ports. If you have problems, try a diferent computer, some USB chips can cause troubles.
Disable the antivirus or screensaver, sleep etc...
1.Download these files:
from ASUS website: http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300TG/#support
Drivers&Tools, on the OS tab select Android
click on Utilities and download latest version of ASUS PC Sync (you will need this for drivers)
click on Firmware and download the lastest available (you will need this for BLOB file)
Minimal ADB and Fastboot: http://d-h.st/gbx
install ASUS PC Sync and Minimal ADB and Fastboot (on fastboot installer check the box that make a shortcut to desktop)
unzip the firmware file downloaded from ASUS site
you will get a second zip file, unzip this one too
the folder unzipped from the second one contain a file called blob
copy or move the folder to the root of your drive C: or D: or whatever drive letter you have
2.Installing drivers:
connect your tablet to PC
you will get a message about Windows couldnt find driver bla...bla, ignore it and keep your tablet plugged
IMPORTANT: even if you previously installed ASUS PC Sync or other drivers and Windows recognize your tablet, you still need to change the driver.
right-click on My Computer-Properties and click Device Manager
find the Asus Android device - should be with an exclamation mark on it (the driver is not installed sign)
right-click on it and choose:
Update Driver Software..., Browse my computer for driver software, Let me pick from a list of device drivers on my computer, Have disk, Browse
go to C:\Program Files or Program Files (x86), ASUS, ASUS Android USB Drivers, Android and select android_winusb.inf
Asus Android Composite ADB interface will appear in the list of device drivers - don`t hit next yet!
uncheck Show Compatible Hardware and select Asus Android Bootloader Interface from the list, now hit next
3.ADB mode:
open Minimal ADB and Fastboot from desktop - from this point, keep it open
type: adb devices - and you should see some numbers under the List of device attached - thats your tablet
if you can`t see the tablet, try this command: adb start-server
4.Booting to "fastboot":
there are two ways to do this:
a) from adb window type: adb reboot bootloader
or
b) reset and hold vol-down (didn`t work for me, but maybe will work for someone else)
the three icons will appear on screen - NOW YOU ARE IN FASTBOOT MODE
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
the credits for this part goes to buster99. He is the one who figured out the right commands for formatting partitions and flashing back the OS
here is his post: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
here we go, one at the time in adb window:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system x:\your blob folder\blob (here you enter the path to your blob file, must end with blob, to point at the file)
fastboot -i 0x0B05 reboot
THE FLASH SYSTEM COMMAND WILL TAKE SOME TIME
be pacient and wait until the progress bar is 100% full on the tablet and you get the command prompt back in the adb window.
After reboot, the Android is back on.
Cheers and good luck!!
A big thank you alexhosu,
several months ago that my tablet was blocked, but I still kept hope
a solution would be found. I'm really happy for you and thank you again for sharing.
Long live XDA
me too
Thanks from me too; was enjoying 5.0 (timduru) on my TF300 when I went to upgrade and idiotically managed to get into a TWRP bootloop(interrupted a format of \data and then used 'wipe' from the boot screen by mistake...)
Your solution has saved my tablet
Am now carefully reinstalling Katkiss
Thanks
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again
Followed the instructions.. Worked well, but getting error 963 when installing/updating anything in Play Store. Seems to be related to storage permissions. Some users are suggesting using format instead of erase. What's the difference? Could that help.
I did factory reset, reflashed and used fix permissions in TWRP but no luck...
alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Click to expand...
Click to collapse
Big thanks from me.
I killed my tablet with an accidental restore to factory defaults while in cm12, an got stuck in an endless bootloader boot loop.
my tablet came back too life at the end of section 4 after adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3.
although getting adb to talk to the tablet was a fluke.
I just kept trying to send "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" while the tablet was loading (boot looping)
6 months of believing my tablet was dead, after letting CM12 do its own update thing, and now, thanks to the above instructions, I'm back online and its working with the stock rom.
Thank you so much for this. No idea why I couldn't find these instructions before, then I just gave up, back in business now!
Thanks a lot for your guide, this is what helped me fortunately unbrick my device, i was stuck in a boot loop with a broken recovery
Another tablet saved. Know your work is appreciated.
i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.
ajeevlal said:
i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.
Click to expand...
Click to collapse
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.
Act32.97 said:
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.
Click to expand...
Click to collapse
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.
ajeevlal said:
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.
Click to expand...
Click to collapse
I would try moving the blob to the root of the C drive and try the 7th command "fastboot -i 0x0B05 flash system C:\blob" just to make sure sometime of file permission type issue isn't happening on the pc side. Other than that the only kind of issue I think it could be would have to be the connection with the drivers, although if erasing the partition's works fine, I don't really see what could be going on.
I followed all the steps and delete, but when loading the file update.blob I get this error:
C: \ Users \ mikel> C: \ Users \ mikel \ Android \ android-sdk \ platform-tools \ fastboot flash system update.blob
error: can not load 'update.blob'
Can someone help me out?
TF300T KissKat
Theziggy said:
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again
Click to expand...
Click to collapse
Hey, I know that I'm a couple years late on this. But, I was just given a Asus Transformer TF300T, and attempted to install the Kisskat custom rom. I unlocked the device with little issues. Rooted with little issues. But when it came to flashing the rom. I get his error saying that "no MD5 file found" and holds it there for a couple of minutes. Then gives me the failed install. My only option is to boot into recovery and restore the stock JB 4.2. If you could point me in the right direction, I would greatly appreciate it. I've searched the forum for someone with a similar issue, and couldn't find it. I hope that I'm not alone on this one. It would kill me to be stuck with the stock rom.
Hi i made a format data from TWRP recovery, and now i am in a recovery loop and got error of mount partitions, i can access to recovery and the screen with 3 icons, but when i plug to my pc it shows as uknown usb, i install the drivers but dosent reconose as a fastboot device, in minimal adb when i write fastboot devices the result is empty pleace help me.
Muito obrigado!
I know this must seem odd, being such an old thread and all but, after several years adding apps and changing ROMs on my wife's TF300T (my gift!) only these past weeks I had the need to search for help, after installing nougatella 7.1, which I did with success, only to stumble on endless logo loops and loading processes without conclusion. Don't get me wrong, the ROM looks great and it wasn't that hard to install but, after two weeks or so, gave me this problem and after correcting it and installing again the ROM, I got in trouble again...
After some five hours googling and trying different stuff, I finally found this thread and twenty minutes ago (around 2:AM) my ASUS returned to its (Jellybean) life!
Alexhosu, thank you so very much for such a detailed, yet easy to follow guide and, if you happen to come to Portugal on vacation and visit Setúbal, I'll have a bottle of Moscatel waiting for you!
Many thanks to Droidbound (who got me off the hook the first time the tablet went nuts!), and also Kevinthefixer, Gtanner00 and some other very inteligent, patient and thoughtful people, and all the guys who shared their difficulties and in a way helped me find the people with the fix.
For anyone interested in trying this method, I would say that it's paramount that you should stick exactly with what is asked and should pay real atention to what is the correct ROM update to download and use. If anyone needs help with translation to Portuguese, just say so.
Again, thank you so much for this!
JMonteiro
alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
Click to expand...
Click to collapse
Thanks for your help :good: and I'm sorry for my basic English, but here is another tablet saved. Your instructions were clear and my tablet is working.
I hope this information helps, based in the next link (user sszyman): https://forum.xda-developers.com/showthread.php?t=2275035&page=9
in which he recommends using the following commands too:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p2
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p8
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p1
With these commands and "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" I was able to solve my Bootloop problem.
Honestly I don't know which of the commands worked, I used all several times.
I recently installed Linux mint and what not,
and figured out I'd be able to use ADB and fastboot commands off the bat.
So I wanted to try some,
1) adb devices ~ Got a response
2) adb shell ~ worked.
hmm, Lets try fastboot.
1) adb reboot-bootloader
2) fastboot erase cache (A harmless command as I believe)
2) fastboot reboot
Now, I wind up with no signal. APN's are removed and some apps don't function.
So i try and update CyanogenMod, And I'm greeted by an 'error' when trying to download the latest nightly.
At this point , I'm really tired and just leave my phone on and call it a night.
I wake up today and my battery is gone. Charge it for a an hour or so, and squeeze out 24%+ battery.
Try redownloading CM through chrome. No luck, still an error. A weird thought dawns on my that /sdcard0/ wasnt mounted.
So I try to go through in ES File explorer and it isn't able to explore anything except the system.
I boot into my recovery and I see my USB mount option is gone and no "internal sdcard" mount point.
Though i'm not getting any error in the logs.
So im just going to push the latest CM and Gapps and see this fixes it. Ill post my response after.
If anyone has any idea what happened, any response would be great Thank you
Update: 1
Weird, I am still able to access the Sdcard when the screen prompts me to the directory to install the zip.
unfortunately , I pushed CM to the /data/ folder before trying /sdcard0/.
But well see what happens when i re-install.
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??
Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.
I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.
As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.
where can i wirte this codes i dont know , can anyone help me??? i have same problem
i can not connect device also in adb mode pc didnt accept the drivers
y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag
y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file
berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.
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