Database Info

Need help restoring device, big problem, read inside

Could someone please help me with this? I have posted a thread over on Android Forums with all the problems.
http://androidforums.com/asus-eee-p...restoring-device-big-problem-read-inside.html
Also, I have posted on here in the past about this, but I honestly am a giant noob at android and did not know what they were telling me to do.
Any help would be really great, thanks!

Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you. I will report back with what happens.
Edit: Also congratulations on 100 thanks.

format your micro SD and only put the ROM you want in it. Now install twrp as other guy said and reboot into twrp recovery in go to wipe and wipe (dalvik, cache, internal memory, system and everything else expect micro SD). Then do a clean installation of ROM and you should be good to go.. if that doesn't work then try easy flash
Sent from my Transformer using xda app-developers app

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
This did not work, I still boot into cwm when the device restarts after downloading it.

Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes

frederuco said:
Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=/TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
Click to expand...
Click to collapse
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.

BloodyRory said:
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.
Click to expand...
Click to collapse
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.

frederuco said:
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.
Click to expand...
Click to collapse
Ah, sorry, long time since I've done this. Alright, well I've gotten into terminal emulator and I've typed that exactly, switching over my directory to my microsd though and changing the file name to the exact one. I'm getting a "cannot open for read: No such file or directory" error when I do this. I have also tried moving the file to /sdcard/ and I have named the file twrp.blob, and neither of these have helped.

Did you issue the su command and get a popup for root access?

frederuco said:
Did you issue the su command and get a popup for root access?
Click to expand...
Click to collapse
Yes, that was the first thing I did. I did exactly as you said. I've tried changing file names, changing directories and everything but for some odd reason I'm getting the same error.
Edit: and yes, I'm changing those when I enter them in terminal as well.

Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.

frederuco said:
Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.
Click to expand...
Click to collapse
Thank you. Here is an image of what I have typed in case it is an error on my part.
http://i.imgur.com/lyJU8MR.jpg

Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.

frederuco said:
Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.
Click to expand...
Click to collapse
And it appears that I am still in clockworkmod when the device boots up.

BloodyRory said:
And it appears that I am still in clockworkmod when the device boots up.
Click to expand...
Click to collapse
Try a normal reboot at the end instead of reboot recovery and see if that works.
If not, run through this and download one of the flashable .zip files (it is version 2.2.X.X) and see if that works. If so, then run through GooManager to get the 2.3.2.3.

[Q] HELP, i think is almost a brick

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?

Guide to fix TWRP or CWM bootloop

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.

possible bricked Tf300t

Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !

_shakabra_ said:
Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !
Click to expand...
Click to collapse
Does it connect to fastboot using the universal naked drivers? If so, try this: http://forum.xda-developers.com/showthread.php?t=2425581

Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!

i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.

Help
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883

_shakabra_ said:
Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!
Click to expand...
Click to collapse
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
norm883 said:
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883
Click to expand...
Click to collapse
Have you seen this:
http://forum.xda-developers.com/showthread.php?t=2403674
---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------
olster said:
i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.
Click to expand...
Click to collapse
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?

Follow-up
cmendonc2 said:
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Have you seen this:
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?
Click to expand...
Click to collapse
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
That is very doable, just google it.

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.

Have done that, "partial brick"
Graiden05 said:
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.
Click to expand...
Click to collapse
That does work, but the problem is it does not stay. You need to do each time you want to use the table (shut down / reboot etc.). But it does allow me to boot into Android 4.3 but it is only a partial load since GAPPS was never loaded. I can push via ADB but nothing seems to stick! I believe all except /system has a no write or no permission granted. In the Android part (4.3) with Root Explorer I have granted the permissions? It appears that TWRP is both the bootloader (fastboot) and recovery. So any fastboot commands are futile, (waiting for device. I did see somewhere there is an administrative function for fastboot but have not been able to locate in all my readings. Except one persons mention of it to eliminate the waiting for device.
norm883

Partial Brick
If this helps anyone I found in a post:
I used it in Terminal Emulator while in Android 4.3 from (adb reload bootloader)
• # dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
• # dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
• # reboot
This now stops when I reboot or turn off the tablet from going directly to TWRP which basically allows me to do nothing, except pretend to do ADB then on a reboot nothing happened.
norm883

Terminal Emulator in Android 4.3
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883

norm883 said:
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883
Click to expand...
Click to collapse
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.

BAHHH Hummbug
Graiden05 said:
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.
Click to expand...
Click to collapse
All seem to be different say directory does not exists etc Crazy program.
Is it possible that from a corrupt there could be 2 layers here? Because in the recovery mode it tells me that there is not OS installed?
Yet I know I can boot to CM Android 4.3.
Wish I could think of a way to clear and start fresh, but without fastboot I am up the creek.
Thanks,
norm883

teamwin flashing, device can't connect to fastboot

So I screwed up. I was trying to flash Zombi-Pop and I wasn't careful to say the least. I was trying to format /data to f2fs so I could do ROM2SD. When I did this I wasn't thinking straight and all my data got deleted (duh). I had already formatted my sdcard properly so all of my data on there got deleted as well (idiot!).
After booting the device it got stuck at crombi-kk as if it was trying to boot. It never did. I was then able to get into recovery by entering fastboot. I tried flashing Zombi-pop from my sdcard but it failed even though it said it was a success. I think the problem was after thinking about it was the fact that I also forgot to flash Kang's TWRP and was still using the one I flashed Crombi-kk. I have the log for successful installation of Zombi-pop, if anyone wants to take a look, which was suspiciously fast which made me think it wasn't successful at all.
Now when I boot, it flashes teamwin and nothing happens. I can still enter fastboot on the tablet, but I can't get a connection. It says key driver not found.. booting os. Android cardhu_user bootloader <1.00 e> released by "US_epad-10.6.14.10-20130801" A03. Starting Fastboot USB download protocol. RCK flashes and when I enter recovery this way teamwin continues to flash.
The idea is to get zombi-pop up and running. If that means I need to reflash crombi-kk and do it all over again I am willing. If anyone could help out, it would be greatly appreciated.
Thanks in advance.

What do you mean: You cannot get a fastboot connection? What is the return for 'fastboot devices'?
Reboot your PC, try a different USB port. You need to establish fastboot or your tablet is a brick.
And then slow down. From your description up there ^^ I cannot tell what you are doing wrong, but you are doing something screwy....
Flash the latest Kang TWRP then read the script when booting. It should tell you in which file format you have on data and cache.
Do not use the rom2sd partitioned microSD! That is a level of complexity you don't need right now.... Use a plain vanilla micoSD to flash ZOMBi-POP from.
Zombi is better flashed internally with data on f2fs anyway....
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
What do you mean: You cannot get a fastboot connection? What is the return for 'fastboot devices'?
Reboot your PC, try a different USB port. You need to establish fastboot or your tablet is a brick.
And then slow down. From your description up there ^^ I cannot tell what you are doing wrong, but you are doing something screwy....
Flash the latest Kang TWRP then read the script when booting. It should tell you in which file format you have on data and cache.
Do not use the rom2sd partitioned microSD! That is a level of complexity you don't need right now.... Use a plain vanilla micoSD to flash ZOMBi-POP from.
Zombi is better flashed internally with data on f2fs anyway....
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Hi! Thanks for the reply. When I type in 'fastboot devices' it returns 'no permissions fastboot'. Just to make sure, I type this in while my tablet has the three options for RCK, Android, and Wipe Data, correct? Otherwise there isn't another place I could do it unless I do it while teamwin is flashling. Also, I'm not sure if this matters but I'm running Ubuntu.

10 seconds on Google gave me this: http://ubuntuforums.org/showthread.php?t=1890861
You gotta learn how to do research before you do stuff...

berndblb said:
10 seconds on Google gave me this: http://ubuntuforums.org/showthread.php?t=1890861
You gotta learn how to do research before you do stuff...
Click to expand...
Click to collapse
Yea, you're right. I got caught up in browsing the xda forums that I forgot about Google! Well anyway your post reminded me about permissions and everything I did and I was able to figure out how to get my computer to recognize my device. Now when I type in fastboot devices it returns a serial number which is my device. Now when I try to flash TWRP it says "error: cannot load 'twrp_tf700t_kang_2.8.7.2.img': No such file or directory"
I've been searching forums (not just xda this time) and I can't seem to figure out where to put TWRP. I've followed these directions where they say put it with the fastboot.exe and binaries but, and I'm embarrassed to say, I don't know where that is. I've tried putting it with the SDK and that doesn't work. I've tried putting it my sdcard and putting it into my tablet and that doesn't work either. I'm not sure what to do next here. Should I try to find a way to move where fastboot is located on my computer and place twrp with it? Or is there something else going on here?
Thanks in advance.

Okum4 said:
Yea, you're right. I got caught up in browsing the xda forums that I forgot about Google! Well anyway your post reminded me about permissions and everything I did and I was able to figure out how to get my computer to recognize my device. Now when I type in fastboot devices it returns a serial number which is my device. Now when I try to flash TWRP it says "error: cannot load 'twrp_tf700t_kang_2.8.7.2.img': No such file or directory"
I've been searching forums (not just xda this time) and I can't seem to figure out where to put TWRP. I've followed these directions where they say put it with the fastboot.exe and binaries but, and I'm embarrassed to say, I don't know where that is. I've tried putting it with the SDK and that doesn't work. I've tried putting it my sdcard and putting it into my tablet and that doesn't work either. I'm not sure what to do next here. Should I try to find a way to move where fastboot is located on my computer and place twrp with it? Or is there something else going on here?
Thanks in advance.
Click to expand...
Click to collapse
If I remember correctly you should have the file in your Home directory.
The command is
Code:
fastboot flash recovery twrp_tf700t_kang_2.8.7.2.img

berndblb said:
If I remember correctly you should have the file in your Home directory.
The command is
Code:
fastboot flash recovery twrp_tf700t_kang_2.8.7.2.img
Click to expand...
Click to collapse
Awesome! It works! Thanks a bunch!
Now. I feel that the last thing I need to do is format /data since it cannot be mounted. I check my internal storage and it is at 0. I found this and I wanted to hear your thoughts on it.
I want to format the /data since it can't be mounted. First of all I want to make sure this is the step I need to take. Secondly, I am confused to whether I need to follow this command,
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Or this command.
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
I am assuming I should follow the first one first to see if that works, then try the second one, but I thought I might as well make sure from someone who is knowledgeable. I also realize this TWRP is probably newer than the one that was used in this thread, therefore there may be a different way in doing things.
Thanks again!

Or should I just go to Wipe, advanced wipe, check data, then press repair or change file system, then resize file system? It says there is 0MB for size. It says it is present, and that it is ext4.

Okum4 said:
Awesome! It works! Thanks a bunch!
Now. I feel that the last thing I need to do is format /data since it cannot be mounted. I check my internal storage and it is at 0. I found this and I wanted to here your thoughts on it.
I want to format the /data since it can't be mounted. First of all I want to make sure this is the step I need to take. Secondly, I am confused to whether I need to follow this command,
Or this command.
I am assuming I should follow the first one first to see if that works, then try the second one, but I thought I might as well make sure from someone who is knowledgeable. I also realize this TWRP is probably newer than the one that was used in this thread, therefore there may be a different way in doing things.
Thanks again!
Click to expand...
Click to collapse
Okum4 said:
Or should I just go to Wipe, advanced wipe, check data, then press repair or change file system, then resize file system? It says there is 0MB for size. It says it is present, and that it is ext4.
Click to expand...
Click to collapse
You need to format data and there are several ways to go about it.
Have you tried doing it in TWRP? Wipe > Format data > type yes
This will take upwards of an hour. Do NOT interrupt it. Make sure the battery has sufficient charge!
The mke2fs command is the same thing just issued from TWRP's build in terminal.
If both don't work try the last one from your computer, while in recovery, in an adb shell.
The killall -19 recovery just suspends the recovery so that it does not interfere with the formatting. I don't think that's your problem, but it won't hurt either.
Oh, and once you got it going your data partition will be ext4 again. If you want to run ZOMBi-POP use TWRP to convert data (and only data) to f2fs before you flash.
Good luck!

berndblb said:
You need to format data and there are several ways to go about it.
Have you tried doing it in TWRP? Wipe > Format data > type yes
This will take upwards of an hour. Do NOT interrupt it. Make sure the battery has sufficient charge!
The mke2fs command is the same thing just issued from TWRP's build in terminal.
If both don't work try the last one from your computer, while in recovery, in an adb shell.
The killall -19 recovery just suspends the recovery so that it does not interfere with the formatting. I don't think that's your problem, but it won't hurt either.
Oh, and once you got it going your data partition will be ext4 again. If you want to run ZOMBi-POP use TWRP to convert data (and only data) to f2fs before you flash.
Good luck!
Click to expand...
Click to collapse
Alright! It seemed to have worked! It's up and running and it's so snappy that it seems as if it's running in turbo mode! Many many thanks.
Also I don't close the thread right? That's a moderator?

Okum4 said:
Alright! It seemed to have worked! It's up and running and it's so snappy that it seems as if it's running in turbo mode! Many many thanks.
Also I don't close the thread right? That's a moderator?
Click to expand...
Click to collapse
Yep, you're all good. Glad to see you back in business!