Database Users

[Q] fastboot - no boot or img file

hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.

you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.

when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.

unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery

[Q] TF101 Stuck in CWM, adb access, no ICS

I seriously searched EVERYWHERE.
My TF101 is now stuck in CWM. The only way to turn it off is a weird way I found out by holding POWER + VOL UP...
If I try to turn it off, it just turns back on. I have full adb access, and I wiped data/factory reset because I was trying to revert back to the original Asus ICS rom, but now I can only get into CWM and if I try booting into Android it just sits there forever. I tried downloading the "US_epaduser9_2_1_17.zip" and tried "adb install" onto the tablet, but it says there is no Manifest.xml
How do I reinstall ICS (stock) back on the tablet AND remove CWM? (Basically completely unroot it)

rthmn3021 said:
I seriously searched EVERYWHERE.
My TF101 is now stuck in CWM. The only way to turn it off is a weird way I found out by holding POWER + VOL UP...
If I try to turn it off, it just turns back on. I have full adb access, and I wiped data/factory reset because I was trying to revert back to the original Asus ICS rom, but now I can only get into CWM and if I try booting into Android it just sits there forever. I tried downloading the "US_epaduser9_2_1_17.zip" and tried "adb install" onto the tablet, but it says there is no Manifest.xml
How do I reinstall ICS (stock) back on the tablet AND remove CWM? (Basically completely unroot it)
Click to expand...
Click to collapse
If you're holding Power + Vol up it's not turning OFF but is simply in APX mode.
What version of CWM?
With ADB you have to ADB push NOT ADB install

I have version v5.5.0.4
I tried adb push but doesn't that just send the file to the tablet?
I can't access anything on the tablet, just cwm. If i try to "install from sdcard" it will say cannot mount "sdcard"
Also more info: I rooted with viper and then unrooted with it.

Try to reboot into system ,then when the screen goes off to do it hold power and volume-. Hopefully a screen will come up with some small print in the upper left hand corner . Let go of the power and volume and let it chill, should cold reboot after 10 sec
Sent from my Transformer TF101 using Tapatalk

Now it doesnt' even cold reboot..
I think I wiped the entire Android system away.
Because when I cold boot it from that menu with the 2 icons, it just stays there when I push ok.
Also, I have a microSD and it won't detect it. I tried formatting with the sd card formatter from the sd assosiation website with no luck. The only thing i can use right now is adb and cwm.

rthmn3021 said:
Now it doesnt' even cold reboot..
I think I wiped the entire Android system away.
Because when I cold boot it from that menu with the 2 icons, it just stays there when I push ok.
Also, I have a microSD and it won't detect it. I tried formatting with the sd card formatter from the sd assosiation website with no luck. The only thing i can use right now is adb and cwm.
Click to expand...
Click to collapse
With 5.5.0.4 it only read from the internal sd card.
Did you flash CWM via ROM Manager? If you did go here
http://forum.xda-developers.com/showthread.php?t=1530337
That thread will also show you how to use ADB to push files to the internal storage for flashing

Then you'll have to ad push. The problem is that recovery is ****ed. I don't have a whole lot of experience with adb, for some reason adb won't recognize my tf. I wish that I could help you more
Sent from my Transformer TF101 using Tapatalk

baseballfanz said:
With 5.5.0.4 it only read from the internal sd card.
Did you flash CWM via ROM Manager? If you did go here
http://forum.xda-developers.com/showthread.php?t=1530337
That thread will also show you how to use ADB to push files to the internal storage for flashing
Click to expand...
Click to collapse
Thank you for that! But, I don't really get the instructions. (I'M SUPER SORRY I'M TOTALLY NEW TO THIS D
while booted into CWM 5.5.0.4 ...
step 1: use adb to push a good recovery [I used Rogue XM v1.3.0 (CWM-based v5.0.2.7)]***
step 2: flash the zip
step 3: use the adb shell to execute the following command
What does it mean by good recovery and flash what zip?
Edit: When I try to push files to the tablet, how do I view them on there? I can't install from sdcard as it says it cannot mount it.

Please help? :/

I SOLVED IT!
I just used nvflash and reflashed the entire Asus ICS rom back on!
Thank you to everyone who tried to help!
(I don't know how to mark the thread as solved.)

rthmn3021 said:
I SOLVED IT!
I just used nvflash and reflashed the entire Asus ICS rom back on!
Thank you to everyone who tried to help!
(I don't know how to mark the thread as solved.)
Click to expand...
Click to collapse
Good to hear. Yeah it's good to have SBKv1.
Edit your original post and change the title

i have the same problem..
I only can access to recovery (5.8.x.x) or adb...
How can i flash new recovery for external sd card usage?
thanks

Check my recent posts for how I got help to solve the same problem.

Updated TWRP and now not booting

I updated TWRP today to 2.3.0.0 from within GooManager then rebooted into recovery and fixed my permission. It was done unusually fast and when I rebooted, it would get stuck on the booting screen. When I tried to boot into recovery by pressing power and both volume buttons, it would get stuck on the google logo.
Please advise.
Any other way I can fix this or somehow restore from a backup?

A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium

Gigabitex2 said:
A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you very much!
I'm sorry but I'm not too much of an expert on Android. AFAIK Recovery mode is the only way I know to do some low system stuff. If I can't boot into recovery, how else can I do anything to fix this?
How can I revert back to old version?
I know you linked the other thread but there are 33 pages I was hoping you would have a short answer hehe thanks.

Is it constantly rebooting at the google screen or just stuck?

goofball2k said:
Is it constantly rebooting at the google screen or just stuck?
Click to expand...
Click to collapse
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.

I see that you posted over on the twrp thread, hopefully those guys can help you. I am assuming that you have updated to 4.1.2? If you're really stuck maybe try a tool kit like wugs or n7 toolkit? Sorry but SDK isn't one of my strong points either
Sent from my Nexus 7 using xda premium

woshiweili said:
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2

comminus said:
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol

woshiweili said:
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol
Click to expand...
Click to collapse
Hey, glad to hear you're in. In an earlier post you described
woshiweili said:
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
which sounds like you were able to get to fastboot mode (power + vol buttons) - your N7 should look like this. From there you can issue fastboot commands to the device to flash recovery. kerne, and bootloader to name a few.

Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.

woshiweili said:
Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.
Click to expand...
Click to collapse
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.

comminus said:
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.
Click to expand...
Click to collapse
Thanks for all your help comminus!
Fortunately I was able to wipe everything while I was in recovery and restore from my most recent backup and now it's working fine. At the very least it's allowing me to boot into system
OK I'm really not rebooting for a while lol

I installed twrp a few weeks ago through GooManager and made a backup. When the 4.1.2 update came out, I downloaded it manually with the intent on flashing it via cu custom recovery, but low and behold twrp wasn't working at all. Even with my device plugged into my Win 7 pc... nothing but the exclamation point droid.
I was able to install an updated version of twrp and get everything sorted out, but now I don't have a lot of faith in it, and am booting into recovery at least once a day to make sure it's still working. I never had any problems with cwm.

Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium

I'm using twrp version 2.3.0.0, and have no plans on updating it because it's stable and working great now

Gigabitex2 said:
Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Updated to 2.3.1.0 but still having booting issues

[Q] HELP!!!!!!! I may have brick my nexus 7

I'm not new to clockwork recovery, and I have flashed many Roms on my Nexus 7........ today I did a full back up of my latest ROM and I downloaded the latest version of the bug less beast .....I let rom manager do the back up and flash......then there was an error flashing the new rom and an abort and a reboot.......no im stuck on the google screen with the little un-locked lock at the bottom of the screen......if I reboot and go into recovery it just goes back to the google screen and stays there.....any clue as what I should do ??

Search around the forums for solutions.
Use the Wugs toolkit to make your work easier.

It's not bricked its standard procedure you just need to plug it in
Sent from my ADR6425LVW using xda premium

download .zip from google and restore it to your tablet (this is full wipe)

a1exus said:
download .zip from google and restore it to your tablet (this is full wipe)
Click to expand...
Click to collapse
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.

CharliesTheMan said:
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
Click to expand...
Click to collapse
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen

GCSM said:
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
Click to expand...
Click to collapse
dude, i'm told you what you need to do, i had erased manually my bootloader,recover,system,data and i was able to restore w/ what i told you it worked w/out any issues

Get fastboot. plug into your computer and do these:
fastboot flash recovery recovery.img (recovery.img is whatever file you have for recovery. IMO, get the newest touch recovery from CWM and have it in the same directory as fastboot)
fastboot reboot-bootloader
From there, leave it PLUGGED IN and get back into recovery. Worked for me.

Bricked....Need help

Well, I have finally done it......bricked my Transformer
Any assistance to fix my problem would be greatly appreciated.
Here is my situation:
I have a tf101 - model b90
I was running ICS rom with rogues recovery
I have been trying to fix the GPS problem for a while now and went back to stock rom unrooted to see if that would work.....it did not
In my effort to re-root my device i STUPIDLY flashed recovery with ROM Manager (and then read AFTERWARDS that was BAD, BAD, BAD)
I am now stuck in a recovery bootloop......HERE IS THE GOOD PART
I tried to flash an older ROM - Revolution 3.2
So now i have a combination of the recovery loop and when i try a cold boot it gets stuck on the Linux cold boot / android screen
i have tried to get ADB running with no success.....my computer (WIndows XP) makes the chime when i connect my transformer......i even get the message in the taskbar showing the device is trying to install drivers but it never shows up in my computer
My device does not show up when i run adb
Can get into ADX mode but my model is too new at B90 to run NFLASH
I have downloaded drivers but cant get the transformer to install them
I have tried PERI to unloop to no success - i get an adb error
What can i do to unbrick my transformer?!?!?!
Thanks in advance

salukis93 said:
Well, I have finally done it......bricked my Transformer
Any assistance to fix my problem would be greatly appreciated.
Here is my situation:
I have a tf101 - model b90
I was running ICS rom with rogues recovery
I have been trying to fix the GPS problem for a while now and went back to stock rom unrooted to see if that would work.....it did not
In my effort to re-root my device i STUPIDLY flashed recovery with ROM Manager (and then read AFTERWARDS that was BAD, BAD, BAD)
I am now stuck in a recovery bootloop......HERE IS THE GOOD PART
I tried to flash an older ROM - Revolution 3.2
So now i have a combination of the recovery loop and when i try a cold boot it gets stuck on the Linux cold boot / android screen
i have tried to get ADB running with no success.....my computer (WIndows XP) makes the chime when i connect my transformer......i even get the message in the taskbar showing the device is trying to install drivers but it never shows up in my computer
My device does not show up when i run adb
Can get into ADX mode but my model is too new at B90 to run NFLASH
I have downloaded drivers but cant get the transformer to install them
I have tried PERI to unloop to no success - i get an adb error
What can i do to unbrick my transformer?!?!?!
Thanks in advance
Click to expand...
Click to collapse
good news is you didn't really brick the device.
edit:
try this first
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
try using easy flasher
and restore the partitions.
if you have a problem installing the drivers try using [Win32/64][Dual Boot] Tubuntu - Dual boot 1 click installer SBK2 Only! my drivers or try using [ADB/FB/APX Driver] Universal Naked Driver 0.7
hope this helps. let me know how your turn out

x3maniac said:
good news is you didn't really brick the device.
edit:
try this first
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
try using easy flasher
and restore the partitions.
if you have a problem installing the drivers try using [Win32/64][Dual Boot] Tubuntu - Dual boot 1 click installer SBK2 Only! my drivers or try using [ADB/FB/APX Driver] Universal Naked Driver 0.7
hope this helps. let me know how your turn out
Click to expand...
Click to collapse
clockwork recovery is not reading my sd card - i took it out to download the twrp recovery - clockwork is not showing the file on the sd card....even when i reboot recovery
ezflasher does nothing for me - i go in to apx mode and try to flash twrp and nothing
the ubuntu does not detect my tablet in apx mode
i dont know what else to try - looks like i am running out of options

salukis93 said:
clockwork recovery is not reading my sd card - i took it out to download the twrp recovery - clockwork is not showing the file on the sd card....even when i reboot recovery
ezflasher does nothing for me - i go in to apx mode and try to flash twrp and nothing
the ubuntu does not detect my tablet in apx mode
i dont know what else to try - looks like i am running out of options
Click to expand...
Click to collapse
Try pushing the new recovery zip to internal storage with ADB.

baseballfanz said:
Try pushing the new recovery zip to internal storage with ADB.
Click to expand...
Click to collapse
the recovery i am in does not give the option to flash zip from internal sd card

salukis93 said:
clockwork recovery is not reading my sd card - i took it out to download the twrp recovery - clockwork is not showing the file on the sd card....even when i reboot recovery
ezflasher does nothing for me - i go in to apx mode and try to flash twrp and nothing
the ubuntu does not detect my tablet in apx mode
i dont know what else to try - looks like i am running out of options
Click to expand...
Click to collapse
When using Easy Flasher are you choosing SBK2?

baseballfanz said:
When using Easy Flasher are you choosing SBK2?
Click to expand...
Click to collapse
yes

Instead of just trying to flash recovery with Easy Flasher, try restoring to stock ROM with EF per instructions and start over with rooting.

baseballfanz said:
Instead of just trying to flash recovery with Easy Flasher, try restoring to stock ROM with EF per instructions and start over with rooting.
Click to expand...
Click to collapse
no luck
a command prompt comes up and tells me that file ..\temp\META-INF\MANIFEST.MF already exists. Overwrite with same file name.
options:
yes
no
always
skip all
auto rename all
quit
Same message with several other files
no matter what i choose it looks like ef is going through the process but the tablet does nothing

salukis93 said:
no luck
a command prompt comes up and tells me that file ..\temp\META-INF\MANIFEST.MF already exists. Overwrite with same file name.
options:
yes
no
always
skip all
auto rename all
quit
Same message with several other files
no matter what i choose it looks like ef is going through the process but the tablet does nothing
Click to expand...
Click to collapse
Silly but start with Skip all, then no, then auto rename all, then yes, see what those do. Ensure that you have the correct zip rom from ASUS from their site, instead of trying to install a DEV ROM.
LET IT SETTLE. Often times these errors are caused by impatience. set the tab down for a while, an hour, maybe 2 when you start this whole reflash.
CWM has an issue with the TF101, if at all possible install TWRP, and work from within there.

I agree with MasterDecker, use TWRP. I had some issues with CWM. TWRP is a nicer interface anyway.
I find wheelie (from linux PC) to get me back from any situation. The steps are not easy at first. I had to download the stock blob, unpack the blob and then use reflash_sbkv1.sh to flash it through USB cable in APX mode.
Even if you don't linux, you could download a free Ubuntu livecd from ubuntu.com, boot off the cd and use wheelie without installing ubuntu linux. Or just about any other linux distro fro that matter.

ethoms said:
I agree with MasterDecker, use TWRP. I had some issues with CWM. TWRP is a nicer interface anyway.
I find wheelie (from linux PC) to get me back from any situation. The steps are not easy at first. I had to download the stock blob, unpack the blob and then use reflash_sbkv1.sh to flash it through USB cable in APX mode.
Even if you don't linux, you could download a free Ubuntu livecd from ubuntu.com, boot off the cd and use wheelie without installing ubuntu linux. Or just about any other linux distro fro that matter.
Click to expand...
Click to collapse
Using my app tubuntu you can flash either twrp or cwm(by roach) via one click. I also have the windows version of wheelie in the bin folder
Sent from my SGH-T999 using xda app-developers app

Asus eee pad 101t dont reponse
I don't think my TF has ADB enabled, and i have a non working power button. No access to internal or external storage, and pc doesn't want to detect my TF. Is there a way around this?
Asus eee pad transformer TF101; CaynogenMode 10; I click reflash_sbkv1 on wheelie folder in APX mode. Going lines in cmd and TF restart, apear EEE logo and stop. I click Power button and nothing. Black screen, i cant induce APX mode, Buttons not working, APX mode Off, controled on 2 computers on windows 8, windows 7, Ubuntu. No responding.
Cable work
Buttons not broken

this worked for me when i bricked mine
google and download "asus_ics_tf101_winnix_nvflash"
connect to computer put it in APX mode then run "download" untill it boots itself

kudiska said:
this worked for me when i bricked mine
google and download "asus_ics_tf101_winnix_nvflash"
connect to computer put it in APX mode then run "download" untill it boots itself
Click to expand...
Click to collapse
no luck for me on any front
adb still wont recognize
apx mode recognizes but when i run any fixes the tablet does nothing
might have to sell it as bricked if i cannot find a solution