Related
hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "
im on recovery and when i run adb devices it just blank. any walk through is much appreciated!
Do yo have USB debugging on?
I dont know because i was about to flash a new rom so i did a full wipe already
Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.
i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe
i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.
I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!
Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!
If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.
thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...
still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.
Hi Folks,
I have tried everything...... But I can't get my BRICKED device back to life! Pleae help, the person who will FIX this wil be donated $20,- for his help, because i've tried everything that I know.
The problem is:
I have a TF101 and it's BRICKED
It has ClockworkMod Recovery v6.0.1.3 installed, TWRP is also recognized at last time I was live and kickin in ROM MANAGER, but YES I was stupid and flashed ClockworkMod Recovery v6.0.1.3. Now I can't get /sdcard/ mounted. ADB drivers can not be installed even in APX modus windows 8,7, and XP are all saying UNKNOWN DEVICE.
When I try to format /system the log says:
Formating /system ...
Done.
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
LabeL:
Blocks: 131072
Block groups: 4
Reserved block gorup size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Done.
I:Can't format unknown volume: /sdcard
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
I can't push a rom to anywhere with ADB
Please help me!!!! You'll really earn $ 20,- when I get my device fixed with TWRP running and a good ROM.
I can pay through PAYPAL, normal IBAN account or by donate button if you have one. I wil pay when the system is running again!
I hope someone can help!
:crying::crying::crying::crying::crying::crying::crying::crying:
what sbk is the TF?
scottyf79 said:
what sbk is the TF?
Click to expand...
Click to collapse
Hello Scotty,
I have an B60, so my version should be an SBK-1
Thanks for your reaction on my post!
I also can't push files ADB won't recognize my device.
I think the partion or something is also damaged.
The thing is definitly totally wiped!
I hope someone can help me.
APX should always work, unless there is a hardware defect.
Try these drivers. Try if possible with XP.
Then use easyflasher to install recovery or stock rom again.
Remember:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
AND NEVER USE Rom Manager again on TF101!!
gls9 said:
APX should always work, unless there is a hardware defect.
Try these drivers. Try if possible with XP.
Then use easyflasher to install recovery or stock rom again.
Remember:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
AND NEVER USE Rom Manager again on TF101!!
Click to expand...
Click to collapse
I know the APX modes. So that's one thing i am aware of. The strange thing is that wether i start up in the CWM revoverymodus, or APX, or try to COLD BOOT (hangs) or normal startup. In al was windows 7,8 and XP are telling me UNKNOWN DEVICE.
When I manually try to update drivers, the system won't except the drivers because the shouldn't be compatible?!?!?!?!?
So the naked drivers haven't worked!
If could only get in a working APX mode.... I could manage it from there, but that;s the major issue.
Is it possible that UBUNTU should recognize the tablet?? I could even install DOS or LINUX on a spare machine..... But then I won't have an USB support.
Erik Stroot said:
I know the APX modes. So that's one thing i am aware of. The strange thing is that wether i start up in the CWM revoverymodus, or APX, or try to COLD BOOT (hangs) or normal startup. In al was windows 7,8 and XP are telling me UNKNOWN DEVICE.
When I manually try to update drivers, the system won't except the drivers because the shouldn't be compatible?!?!?!?!?
So the naked drivers haven't worked!
If could only get in a working APX mode.... I could manage it from there, but that;s the major issue.
Is it possible that UBUNTU should recognize the tablet?? I could even install DOS or LINUX on a spare machine..... But then I won't have an USB support.
Click to expand...
Click to collapse
If you see unknown device in device manager, just point to the driver by hand.
Use XP.
A time ago I used Ubuntu ubuntu-11.10-desktop-i386.iso.
Driver was included because I could use nvflash in it. I made a backup with nvflash in Ubuntu. Don't know about later versions of ubuntu.
But first give a try in XP because then you can use easyflasher.
edit: I see you already did by hand.
Which driver you are pointing to ?
I have a nvflash.zip with driver included (usbpcdriver directory). You can also point to universal naked driver.
Have a read through this thread, if your tablet supports NVFlash it should work so long as there are no hardware issues
http://forum.xda-developers.com/showthread.php?t=2270850
I did try to point them by hand, but it's not working.....
I'm using XP on a machine where the tablet was never been used on. So conflicts are also terminated by that.
I did lose my tablet's battery when I was formatting the /data partition. Could that also be the problem? (Dummy
)
This is DUTCH, but the fault is displayed in english.
Erik Stroot said:
I did try to point them by hand, but it's not working.....
I'm using XP on a machine where the tablet was never been used on. So conflicts are also terminated by that.
I did lose my tablet's battery when I was formatting the /data partition. Could that also be the problem? (Dummy
)
Click to expand...
Click to collapse
Not for APX. APX should always work because it is in the hardware.
Did you use a usb 2.0 port on XP ?
Which drivers you are pointing to ?
(where are they are coming from)
You can give Ubuntu a try. You can use the live cd. Installing is not necessary.
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Erik Stroot said:
This is DUTCH, but the fault is displayed in english.
Click to expand...
Click to collapse
Cannot read it. Picture is to small.
Thanks *DETECTION* I'll will read that thread also.
@gls9:I'm pointing to the naked driver as you said to me, it won't work!
DO you know a alternative way???
Erik Stroot said:
Thanks *DETECTION* I'll will read that thread also.
@gls9:I'm pointing to the naked driver as you said to me, it won't work!
DO you know a alternative way???
Click to expand...
Click to collapse
What message you are getting ?
Point to the main directory of the drivers, not to the i386 directory (just to be sure).
gls9 said:
What message you are getting ?
Point to the main directory of the drivers, not to the i386 directory (just to be sure).
Click to expand...
Click to collapse
I am pointing in the directory and i am getting the message:
Can not find newer drivers for hardware
Strange.... because there aren't any drivers.... UNKNOWN DEVICE is "installed" without any drivers!
PS I am know on UBUNTU LIVE DVD, but over there I can't find the device list, but only a view with DISPLAY, MOUSE etc.
IS there an one click flasher for UBUNTU for SBK-machines????
Erik Stroot said:
I am pointing in the directory and i am getting the message:
Can not find newer drivers for hardware
Strange.... because there aren't any drivers.... UNKNOWN DEVICE is "installed" without any drivers!
PS I am know on UBUNTU LIVE DVD, but over there I can't find the device list, but only a view with DISPLAY, MOUSE etc.
IS there an one click flasher for UBUNTU for SBK-machines????
Click to expand...
Click to collapse
First try this on Ubuntu
Then you know apx and nvflash will work.
After this you can try nvflash from here
You have to flash the SOS partition (=recovery). Get it from the easy flasher zip. It is also there.
I don't know if there is a one click flasher for linux. Maybe you can use this
---------- Post added at 09:46 PM ---------- Previous post was at 09:26 PM ----------
Erik Stroot said:
I am pointing in the directory and i am getting the message:
Can not find newer drivers for hardware
Strange.... because there aren't any drivers.... UNKNOWN DEVICE is "installed" without any drivers!
Click to expand...
Click to collapse
Is unknown device gone when disconnect TF101 ?
(to make sure you looking at the right one)
Edit: did you also installed Asus Sync on XP ?
If yes, deinstall and try again with driver.
If not, install Asus sync and try again.
What I also did ( in XP):
- disconnect TF
- start TF in APX mode
- connect cable
(don't know if it is relevant but you can try)
With NVFLASH you must be sure what you are doing. I never restored with it.
I prefer the easyflasher method.
gls9 said:
First try this on Ubuntu
Then you know apx and nvflash will work.
After this you can try nvflash from here
You have to flash the SOS partition (=recovery). Get it from the easy flasher zip. It is also there.
I don't know if there is a one click flasher for linux. Maybe you can use this
---------- Post added at 09:46 PM ---------- Previous post was at 09:26 PM ----------
Is unknown device gone when disconnect TF101 ?
(to make sure you looking at the right one)
Edit: did you also installed Asus Sync on XP ?
If yes, deinstall and try again with driver.
If not, install Asus sync and try again.
What I also did ( in XP):
- disconnect TF
- start TF in APX mode
- connect cable
(don't know if it is relevant but you can try)
With NVFLASH you must be sure what you are doing. I never restored with it.
I prefer the easyflasher method.
Click to expand...
Click to collapse
Hi GLS9,
Yes when I turn of the device, unknown device disapears!
I also did the connecting in your way.
I have also tried installing asus sync.... Also no succes!
I'm trying to connect within Ubuntu, but i can not instal pakages on the normal way as they are descriped in multiple threads.
Tomorrow or Monday i'll Will install Ubuntu in stead of running it from dvd. I will try further! For now i Will have to run! Thanks for your support till now.
Erik to fix unknown device, you have to uninstall it in device manager, then with tab reconnected and on, Windows will try to install the drivers automatically DO NOT ALLOW IT, cancel installation , then head back to device manager and manually install the naked drivers.
Steps
1. Tab is connected and displays unknown device
2. Uninstall unknown device from device manager
3. A reboot of the pc and turn the tablet off and then back on.
4. After reboot reconnect tablet, Windows will try to automatically install drivers " stop immediately " do not allow installation.
5. Go back to device manager and manually install naked driver.
It would be better to do this on Windows 7 if you have it, Windows 8 has driver enforcement which can be extra work to disable.
Sent from my Transformer Prime TF201 using XDA Premium HD
In device manager, try going to VIEW > SHOW HIDDEN DEVICES
That might solve your disappearing issue
But to force a driver install, instead of telling the update driver window to look in a folder, tell it you have the file on your PC and direct it exactly to that driver
Erik Stroot said:
Hi GLS9,
I'm trying to connect within Ubuntu, but i can not instal pakages on the normal way as they are descriped in multiple threads.
Click to expand...
Click to collapse
What packages do you want to install ?
As I remember correctly, nothing is needed.
Would you like me to attempt to walk you through fixing it in windows?
I can use the teamviewer software to either take control of or direct you on where to click (RC or Meeting) and see if I can't help you get the drivers working. I had a tablet in a similar condition that I fixed in this manner for someone.
Pm or quote me if you want, otherwise continue with trying advice in this thread. I don't have much else to add reading through other than making sure the drivers are done right.
Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.
I still haven't had any luck. Does anyone have any ideas?
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2646279
berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so
Whoops, forgot screen shot
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...
berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Hi all first off I'm sorry if this has been posted before but I'm having a problem unbricking an Asus transformer tf101 B60, I'll start with what's going on or not for that matter. lol
1. Boot to recovery is CWM-Based Recovery v5.5.0.4 roach-tf101-r2
2. will not see sd card / backup-restore= -2014-04-05.02.52.56 / no files found
3. Choose a zip = e: can't open /sdcard/update.zip
4.PC windows 7 pro 64 bit will not see the tablet when plugged into usb getting unrecognized device,force driver still getting yellow ding=device cannot start
if I plug in the usb and turn on the tablet windows does not even see that and unit sits on logo screen. and other screen the cold lynx boot that hangs there.
So in short I'm hitting a brick wall, windows won't see it, it won't see the SD card in recovery mode.
I've read in these posts how to fix this problem and have all the software / firmware you name it, but they all say almost the same thing, windows needs to see the device in order for any of these fixes to work, and thus is my wall I'm hitting.
Any help to find a solution to this problem would be oh so thankful to you all and call you Tablet Gods, this was a tablet given to me as a paper weight and I thought if it boots it can be fixed?
Thanks for your time and God like tablet knowledge.
Cheers.
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Driver Not Working
*Detection* said:
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Click to expand...
Click to collapse
I booted the unit into recover mode and windows sees unknown device..Ok
Tried to install new naked driver and getting a splash saying not compatible with windows 64 bit, I tried this on a brand new windows 7 pro 32 bit laptop and got the same results. I do have a brand new usb cable for it thinking that the old one was faulty, tried adb again same thing no device found, are there any commands in terminal emulator that can force the driver on the usb port? I'm thinking that if windows sees an unknown device then at least it sees something there just not whats there? Am i wrong in that somehow it's lost the usb firmware connection? so the driver will not install and if forced does not make the connection to the device? So this is my results.
So I'm ready to put gun in mouth over this, my laptops going to divorce me over driver abuse and the tablet mocks me with the frozen Asus logo.
Again Thanks for all the advice and i'll keep slugging it out.As this unit is in perfect condition outside of the Bricked part
You don't need to boot it into recovery mode to start with, just install the drivers normally first with the TF101 connected and booted normally
It's always going to say it can't find the device if the driver isn't installed
Focus on getting that APX driver installed and working, once you have that installed, Im pretty sure it will see the device fine
Asus TF101 B60 Softbrick? What Now?
Hello all.
I've been searching in vain for an answer to my Bricked Asus tf101? I'm just going to get right to the problem.
I can't get the tablet to be seen by windows 7 pro 64bit, Unknown device and yes I've tried everything, except asking if there's a way to force connection through a terminal like I've seen done with a router and a network switch to force a flash file so as to get at least a response after a reboot instead of just the Asus splash screen, here's a summary.
The Good.
1. I can boot to recovery CWM-based recovery v5.5.0.4 roach-tf101-r2 with menu's
Bad: Does not see sd card only see's internal and there's no file or folder error for backup/restore
2.Boots to screen with 2 icons data wipe and linix cold boot and goes nowhere from there just hangs.
So I'm stuck here, I have all to tools to do the job only if windows would see it, Adb does not see device which means the same thing no driver no fix,
Everywhere I read it says do this and that and it will restore to factory, that would be great if windows saw the thing, so I'm looking for a way to get the tablet to boot to something other than a loop. also tried the put the E101_SDUPDATE.zip in the root of the SD card and restart, does not see the card or file or both so it's not loading the file?
1. windows 7 not seeing device, will not take force drivers, Universal-Nvidia-Asus- MTP
2. recovery does not see sd card, so can't flash new anything?
3. So no communication from SD/USB
4. Is there a terminal command I can use to force a Blob or flash a recovery to the tablet when drivers and USB don't respond?
And to top that off my laptop filed for divorce for driver abuse..lol I'm not giving up.
Thanks to you all,
I want to thank you all for your time and advice it is very much appreciated, and I'll keep slugging away because I know there's a fix out there.
Cheers.
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Thanks
*Detection* said:
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Click to expand...
Click to collapse
Thanks for the Advice, Is there a thread outlining this so I can give it a try? I do have a new laptop I'm building out with windows 7 Pro 32bit as I've had so much trouble with the 64bit version.
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
*Detection* said:
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
Click to expand...
Click to collapse
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Sicknote said:
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Click to expand...
Click to collapse
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
*Detection* said:
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
Click to expand...
Click to collapse
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Sicknote said:
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Click to expand...
Click to collapse
You're not going to be able to put the tablet into APX mode till you get the drivers installed correctly.
With the tablet connected to the computer and the tablet on, download the naked driver package. open up device manager and right click on Other Devices - APX and chose update driver. Chose browse and then go to where you downloaded the naked driver package. If it complains that they aren't signed, click install anyway. If successful, you should now be able to put your tablet in APX mode.
ASUS EEEPAD TRANSFORMER TF101G
EOS JDQ39 Nightly 120
C.W.M. 6.0.1.3
I'm not able to flash any rom or recovery anymore, the only thing i get is: unknown volume for path [/sdcard/] can't mount /sdcard/.
been trying with PERI, 1Click root, and several tools by ADB or by APK, but nothings change.
I would like to flash a linux image, and to change to TWRP recovery, as i've read twpr is the most compatible recovery for tf101g, isn't it?
(the same error is given with any rom zip)
tyvm in advance.
The-Undertaker said:
ASUS EEEPAD TRANSFORMER TF101G
EOS JDQ39 Nightly 120
C.W.M. 6.0.1.3
I'm not able to flash any rom or recovery anymore, the only thing i get is: unknown volume for path [/sdcard/] can't mount /sdcard/.
been trying with PERI, 1Click root, and several tools by ADB or by APK, but nothings change.
I would like to flash a linux image, and to change to TWRP recovery, as i've read twpr is the most compatible recovery for tf101g, isn't it?
(the same error is given with any rom zip)
tyvm in advance.
Click to expand...
Click to collapse
can you go to recovery,
Huntervn said:
can you go to recovery,
Click to expand...
Click to collapse
yes i can, i get the error "unknown volume for path [/sdcard/] can't mount /sdcard/" when i click "choose zip from sdcard" into recovery
The-Undertaker said:
yes i can, i get the error "unknown volume for path [/sdcard/] can't mount /sdcard/" when i click "choose zip from sdcard" into recovery
Click to expand...
Click to collapse
So you can try with this guide
1: Get a working SD card.
2: Download ASUS stock rom.
3: Connect your TF101G to a windows PC.
4: Boot your TF101G into APX mode
5: Install APX drivers.
6: Put the ROM zip inside the asusupdate folder.
7: Launch Easy Flasher and select Flash ASUS stock zip.
8: The app should now open a DOS window and run a script... something like extracting blob and then a bunch of other stuff.
9: Once it runs its course your tablet should say *installation success!* or something to that effect.
10: Reboot.
good luck
Huntervn said:
So you can try with this guide
1: Get a working SD card.
2: Download ASUS stock rom.
3: Connect your TF101G to a windows PC.
4: Boot your TF101G into APX mode
5: Install APX drivers.
6: Put the ROM zip inside the asusupdate folder.
7: Launch Easy Flasher and select Flash ASUS stock zip.
8: The app should now open a DOS window and run a script... something like extracting blob and then a bunch of other stuff.
9: Once it runs its course your tablet should say *installation success!* or something to that effect.
10: Reboot.
good luck
Click to expand...
Click to collapse
done everythings you suggested without any error, but nothings new happened, still the same error when triyng to flash, same with sdcard or ext-sdcard or usb-drive: "unknown volume for path [/sdcard/] can't mount /sdcard/"
the same if i want to flash a new recovery, no errors but no news after reboothing
(the process for flashing the new recovery took only few seconds, even though it didn't get any error)
Huntervn said:
So you can try with this guide
1: Get a working SD card.
2: Download ASUS stock rom.
3: Connect your TF101G to a windows PC.
4: Boot your TF101G into APX mode
5: Install APX drivers.
6: Put the ROM zip inside the asusupdate folder.
7: Launch Easy Flasher and select Flash ASUS stock zip.
8: The app should now open a DOS window and run a script... something like extracting blob and then a bunch of other stuff.
9: Once it runs its course your tablet should say *installation success!* or something to that effect.
10: Reboot.
good luck
Click to expand...
Click to collapse
The-Undertaker said:
the same if i want to flash a new recovery, no errors but no news after reboothing
(the process for flashing the new recovery took only few seconds, even though it didn't get any error)
Click to expand...
Click to collapse
APX mode with NVflash/wheelie won't work on the TF101G unfortunately (we don't have the SBK for the TF101G). So EasyFlasher also won't work!
If you can boot into recovery you could connect to your PC with the cable and use adb shell from your PC. You could then "adb push" the TWRP zip to internal storage (not sure if the CWM version you have installed supports it though). Alternatively you could try mounting the SD from the command line, or try and get a different MicroSD card if your one is faulty. That's about all you can do on the TF101G unfortunately.
jrohwer said:
APX mode with NVflash/wheelie won't work on the TF101G unfortunately (we don't have the SBK for the TF101G). So EasyFlasher also won't work!
If you can boot into recovery you could connect to your PC with the cable and use adb shell from your PC. You could then "adb push" the TWRP zip to internal storage (not sure if the CWM version you have installed supports it though). Alternatively you could try mounting the SD from the command line, or try and get a different MicroSD card if your one is faulty. That's about all you can do on the TF101G unfortunately.
Click to expand...
Click to collapse
could you link one how-to for adb push pls?
The-Undertaker said:
could you link one how-to for adb push pls?
Click to expand...
Click to collapse
Google is your friend
https://www.google.com/search?q=adb+howto
Trying by adb, but the terminal is in waiting mode since a life, after loading adb daemon
The-Undertaker said:
Trying by adb, but the terminal is in waiting mode since a life, after loading adb daemon
Click to expand...
Click to collapse
Does your computer (I assume it's Windows) recognise the TF as a device (in device manager)? Do you have the USB drivers installed?
jrohwer said:
Does your computer (I assume it's Windows) recognise the TF as a device (in device manager)? Do you have the USB drivers installed?
Click to expand...
Click to collapse
windows 7 64bit, recognized and usb drivers installed. i can boot to kubuntu 64, if you think is better to operate under linux OS
The-Undertaker said:
windows 7 64bit, recognized and usb drivers installed. i can boot to kubuntu 64, if you think is better to operate under linux OS
Click to expand...
Click to collapse
You might want to try that although if your tab is recognized under Windows it should be ok. Linux normally does not require installation of special drivers. If you have permission errors, just run adb as root.
BTW, just to be sure, you have to run adb while your tab is in Recovery mode, NOT APX!
jrohwer said:
You might want to try that although if your tab is recognized under Windows it should be ok. Linux normally does not require installation of special drivers. If you have permission errors, just run adb as root.
BTW, just to be sure, you have to run adb while your tab is in Recovery mode, NOT APX!
Click to expand...
Click to collapse
devices management
From what I remember, 64bit Windows requires signed drivers, the drivers you need (Universal Naked Drivers) are not signed
Install 32bit Windows 7 in VMWare or Virtualbox
See my sig links for Easyflasher to use in 32bit Win 7
*Detection* said:
From what I remember, 64bit Windows requires signed drivers, the drivers you need (Universal Naked Drivers) are not signed
Install 32bit Windows 7 in VMWare or Virtualbox
See my sig links for Easyflasher to use in 32bit Win 7
Click to expand...
Click to collapse
one new, i'be been able to flash TWRP by Oneclickrecovery042 (Tab was into recovery mode).
now, having a try with flashing Kubuntu 14.04 With Tegra drivers by @jrohwer, it doesn't see the tarbz2. wrong format?
The-Undertaker said:
one new, i'be been able to flash TWRP by Oneclickrecovery042 (Tab was into recovery mode).
now, having a try with flashing Kubuntu 14.04 With Tegra drivers by @jrohwer, it doesn't see the tarbz2. wrong format?
Click to expand...
Click to collapse
You can't install this with easyflasher. You also cannot install it via a "recovery zip". You have to do it in the command line (either in Android, using Android Terminal Emulator, or in Recovery with adb shell). Detailed instructions are on the threads - please read them!
jrohwer said:
You can't install this with easyflasher. You also cannot install it via a "recovery zip". You have to do it in the command line (either in Android, using Android Terminal Emulator, or in Recovery with adb shell). Detailed instructions are on the threads - please read them!
Click to expand...
Click to collapse
at the kubuntu section of that tread, i don't see many details just as like the other linux images, where can i get instructions pls?