Database Info

Back to stock

I rooted, and loaded cm9 rom. I prefer stock rom but when I restored my backup there was no wifi (apparently a common issue). Anyway, I am looking for a way to get back to stock rom. I downloaded firmware from Asus but dont know if that is what I need or what to do with it. I am using the twrp recovery
Thanks for any help

All you have to do is download the full Asus ZIP from my thread and flash in CMW and it will restore your fully stock ROM without recovery
http://forum.xda-developers.com/showthread.php?t=1680570

ok thanks now to figure out how to get cwm into my tablet-- right now trying to install sdk

i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here

this worked
Terminal Emulator Method
Install Android Terminal Emulator on your tablet.
Download the ClockworkMod Recovery image file directly to your tablet, preferably in the root of the /sdcard directory. Take note of where the file is saved. Rename the file to cwm-touch.blob.
Launch Android Terminal Emulator on your tablet.
Enter the commands below. If you did not save/move/copy the image file to the /sdcard directory, you need to replace /sdcardin the second command below with the correct directory where you saved the recovery image file to.
su
dd if=/sdcard/cwm-touch.blob of=/dev/block/mmcblk0p4
Reboot your tablet. The blob file will be automatically installed as your tablet reboots.

voodoo_dr said:
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
Click to expand...
Click to collapse
You can uninstall Eclipse. It has nothing to do with Android or flashing anything. It's an Integrated Development Environment, which is kind of like a word processor for programmers. The only relation it has to Android is that it supports the Java programming language, so a lot of Android developers use it. If you're not going to be writing apps or messing with Android source code, it's probably best if you uninstall Eclipse, just because you won't use it, and it's taking up storage space.
Also, what were you expecting to happen when you put the tablet in fastboot mode? It just opens up a serial connection with a host (in this case, your computer) and allows the host to access the tablet via fastboot (sounds confusing, I know; it's not particularly fast, and doesn't have much to do with booting anything; it's like ADB but for low-level [hardware] flashing) and run commands. The tablet itself does nothing except display the message that it's in fastboot mode. Once the tablet says that, you run fastboot on the computer.

thanks for the reply. Now I have a brick---tried to install stock rom and hangs on asus with the wheel going round and round. It deleted my cwm so now no recovery on tablet. When I go into fastboot, it doesnt seem to recognize my tablet adb devices--nothing comes up

In my device manager I see no adp drivers- the only driver which keeps installing when I plug in the tablet and go to fastmode is the asus bootloader interface so I cant do anything with the tablet--- no recognition of device with adb devices command Help please

If you're in fastboot, ADB won't recognize the tablet. You need to use the fastboot commands with fastboot.
What to do:
-download the CWM blob on your computer
-put the CWM blob in the directory on your computer with the fastboot program
-boot the tablet into fastboot, and flash CWM
-boot into CWM, and restore the nandroid backup you should have made.
Alternately, if you didn't make a nandroid backup, you can boot into recovery, push the Asus stock ROM to /sdcard on your tablet via ADB (I'm assuming ADB works in the stock recovery), then reboot into recovery, and it should flash the update automatically. This will erase ALL your data, including /sdcard.

is cwm blob recovery.img?

I'm not sure if flashing .img files works with this tablet, but you could try. If it doesn't work, go to the place you got the recovery (as long as it's not from ROM Manager, and you're positive it's not the TF201's recovery), and there should be a file that ends in .blob. That's the one you need.

then I just place it in the same directory and click on fastboot? or is there more to it? seems to be having trouble with drivers mtp driver not installing???

I don't use Windows, so I don't know about the drivers. There's a thread in the development section with all the Windows drivers you need, though.
You put the blob in the directory where fastboot is. You open the command line (open Run, and type "cmd" [no quotes]) and run the fastboot command from there.

got it thanks cwm is back

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 HELP HELP Bricked

Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me

Meat6911 said:
Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me
Click to expand...
Click to collapse
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:

When I connect to PC it makes the connection sound but doesn't show as a removable drive so I can't use Easyflash or any program like that also like I said APX mode wont work it makes the sound that it detects the tablet but then makes the remove sound right away. and this happened when I installed the Cyangenmod 9. I found someone who says he may be able to fix it for $50 using Odin but I am worried that he wont be able to and its an hour drive to take it to him... At this point I just want it back to stock ...

erm... ODIN won't work with a transformer, it's only for samsung devices.
Alright, you probably used ROM manager judging by your Recovery version.
You need to just NvFlash the device back to stock:
Download your region's Stock ROM from here: (WW if outside of US, US if inside.) Stock Rom
Download Wheelie NvFlash tool from here: Wheelie
Unzip the stock rom .zip first, into it's own folder. Then unzip the wheelie tar.bz2 into the folder you just made by unzipping the stock rom. Overwrite any files with the wheelie files.
Next find out your Sbk variant, Look at the serial number on the sticker on the bottom of your tablet.
If it says B70, or a higher number like B80 or any C, then you are Sbkv2
If the number is B60 or lower, you are Sbkv1.
Remember this for the next step.
Make sure the tablet is off totally, Then hold the Volume-UP key and Then press power, keep holding volume up. It will enter APX mode.
Plug it into your computer, the screen will stay blank.
It should be detected, if it says unknown device or similar, use the windows device manager to select the 'asus bootloader interface' or 'Unknown device' or similar, with Nvidia ASUS or APX or Bootloader, something along those lines, to update the driver, right click this and navigate to the 'usbpcdriver' folder in the folder you unzipped earlier. It will install and detect.
Then run the .bat file that says Reflash_(Your Sbk version).bat while the tab is connected in apx mode.
It will return to stock, give it time, DO NOT UNPLUG IT.
The screen may flash, and the tablet may/will reboot.
When done you will be on Stock latest from ASUS.
If you want safe root / recovery, download and run my PERI tool, link in signature.
good luck.

ok I am trying that now but I wish I had someone to walk me through everything in real time...

OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you

Meat6911 said:
OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you
Click to expand...
Click to collapse
erm, I guess it worked?
The best thing you can do for someone on xda is hit the 'thanks' or donate buttons, and thanks is free!
Any other questions, I'm guessing it worked alright?

frederuco said:
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:
Click to expand...
Click to collapse
I had similiar problem when I tried to downgrade and go back to stock. After flashing stock from asus, I did it wrong by unzipping (stock_ics_kernel_9.2.1.24US-secure) first then flash the file under the downloaded zip files. Now I am also stuck at Eee Pad, can't get into recovery because it probably wiped out everything. Hopefully this can recover my Eee Pad!!!! I got my fingers cross. This may be my only hope for my asus pad .

Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use

Meat6911 said:
Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use
Click to expand...
Click to collapse
You should be able to with Dolphin HD browser and Flash installed, make sure flash is integrated into the Dolphin. That or the sites should just work..
I use Adaway.

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