[Q] Prime 1a Bricked, but can't adb - Asus Eee Pad Transformer Prime

I'm sorry if this is a bad post, I'm new to these forums. I used the viperMod tool to install CWM, rebooted, and I now get the 1a brick error described the the developers section. However when I try to fix it using adb (which I have installed correctly), it doesn't work.
To be specific, my computer (running windows) doesn't recognize that I've hooked it up in devices. I do an adb devices and get "List of devices attached" and nothing shows up. Each time I plug in the prime, I get the usual beep that windows recognizes it is attached, however it does 3 real quick beeps and then nothing happens. I think if I could get it hooked up properly the fix described in the developers section would work, but for some reason my computer doesn't like it.
Any suggestions and/or help would be greatly appreciated!

This might sound a little silly but have you installed the drivers?
If you have the drivers installed windows should detect the device correctly and you'll be able to use adb. There is a link to universal drivers in the dev section, or you can get ASUS' from their support website.

I had the drivers installed properly prior to the CWM installation. However, the 3-tone beep does indicate that the drivers are not installed. Unfortunately the prime isn't showing up in device manager at all, so I need to figure out how to re-install the drivers and see what happens from there. Is it possible to install drivers for a device that doesn't show up in device manager?

Ok, so I can't install the drivers for the device. The only thing device that pops up in device manager is "Full Android on Emulator" in "Other devices". I try to install drivers for it, and it does not like either the universal drivers or the drivers from ASUS.
Why would windows not recognize it as an android device like before? I haven't touched the drivers which I had installed and previously worked. I feel like the only thing stopping me from unbricking the device is a connection issue. Any suggestions?

Well, here was my fix in case someone else had this problem:
In device manager under "Other Devices", I selected "Full Android on Emulator". I selected to install drivers, and browse to drivers. Now where the stock ASUS drivers would not work, the universal driver posted in the dev section worked, although it thought the device was some samsung phone.
It turns out that was OK. I followed the unbrick instructions from 1a in the dev section and all is well.
I appreciate the geniuses who post all these fixes and mods. Great work!

Related

[Q] Kies working fine, but Windows still lists "Unknown device"

I installed latest version of Kies in my Windows 7 Professional 64bits (UAC disabled, install was "ran as admin")
In the end of the installation process, Windows shows a balloon saying it is installing the driver for the device (note that there is no phone connected to the computer at that moment), but it fails saying that it could not find the driver for the device.
After installation finishes, I can connect the phone, open and use Kies normally, but if I go to Windows device manager, in the "Other devices" branch, it still lists an "Unknown device".
Any idea about how to solve this? I already searched the forum, but could not find anything that worked for me.
Thanks!
PS: I'm using the original USB cable from Samsung.
As long as you are able to connect and work via Kies just leave it. Just check how many people are having problem with Kies, you should consider yourself lucky that you don't have a connection problem
Regards.
Leave your phone plugged in and do a windows update. It should find the missing drivers.
You can find the drivers inside the dir where kies was installed, alternatively a copy is stored on my 4shared, link in my sig.
You can try installing the drivers and see if that helps.
Kies is a huge PITA, you may need to swap USB port and uninstall/reinstal for it to get its act together.
Thanks all who answered.
Unfortunately, Windows Update can't find any driver (already had tried that), and also asking to update the driver and setting it to search in the Kies driver directory has no effect either.

[Q] Driver Wont Run?? Revolutionary Can't Identify Device

I'm trying to run Revolutionary to gain root, but running into some driver issues. I've never had a problem connecting as a disk drive and transferring files from PC to TB or vis versa, so I haven't encountered this yet. But when I run Revolutionary I get stuck at "Identifying Device" (or finding, or whatever it says first). Uninstalled HTC Sync, uninstalled and reinstalled drivers. Installation process says everything goes along fine, but when I look in Device Manager I have an /!\ with this error message:
"Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 37."
Tried 2 different cables, 3 different ports (could they all suck?) Shows up in "My Computer" as CD Drive (K Verizon Wireless.
Running Windows Vista
Searched around a bit and saw some similar problems but under different circumstances and with solutions that didn't seem to apply. Anybody seen this? Know how to get it going?
Also, I'll run into the same problems trying to root through ADB, correct?
May have some corruption issue.
From the command prompt (on your PC), try running this:
sfc /scannow
Let it run then reboot and see if it fixes anything.
Good Luck
Nope....
Tried that, said there were some errors that were fixed (surprisingly vague about what), rebooted, but same problem. Any other ideas?
Unplug device.
Uninstall all drivers related to the device and reboot the computer.
Install the newest driver package from the HTC website (sync not required). *Optionally, you can just update your current driver using the inf located in step 12 here instead of the driver package from HTC.*
Reboot if prompted.
Turn on USB Debugging in settings->applications->development.
Plug phone in.
Try again.

Unable to Install Universal Naked Drivers

So I have a TF201 with AndroWook HairyBean v1.0 on it. I did my initial install on a different computer so I have never plugged in my transformer prime to this computer (I no longer have access to the other computer). I have tried installing the Universal Naked Drivers 0.7 in several different methods and none work.
When I plug in my tablet I get an "Unknown Device" prompt. I have tried everything to resolve this, including uninstalling and reinstalling all USB drivers, restarting, etc. and nothing has worked.
I have tried navigating to the drivers themselves to right click install and I get the message "The INF file you selected does not support this method of installation."
I have tired navigating to the "Unknown Device" in device manager and trying to force the installation of the drivers but I get the "The folder you specified doesn't contain a compatible driver for your device. If the folder contains a driver, make sure it is designed to work with Windows x64-based systems."
This is on a Windows 7 64-bit Ult. All USB drivers are up to date. Any other suggestions before I throw my tablet at the wall?
USB Cable
Dilhrnhydramine said:
So I have a TF201 with AndroWook HairyBean v1.0 on it. I did my initial install on a different computer so I have never plugged in my transformer prime to this computer (I no longer have access to the other computer). I have tried installing the Universal Naked Drivers 0.7 in several different methods and none work.
When I plug in my tablet I get an "Unknown Device" prompt. I have tried everything to resolve this, including uninstalling and reinstalling all USB drivers, restarting, etc. and nothing has worked.
I have tried navigating to the drivers themselves to right click install and I get the message "The INF file you selected does not support this method of installation."
I have tired navigating to the "Unknown Device" in device manager and trying to force the installation of the drivers but I get the "The folder you specified doesn't contain a compatible driver for your device. If the folder contains a driver, make sure it is designed to work with Windows x64-based systems."
This is on a Windows 7 64-bit Ult. All USB drivers are up to date. Any other suggestions before I throw my tablet at the wall?
Click to expand...
Click to collapse
I had this problem, turned out to be a faulty USB cable, try another one, maybe you could take your tablet to a sotre and ask if they can borrow you another cable and test it. Hope this helps.
sj010489 said:
I had this problem, turned out to be a faulty USB cable, try another one, maybe you could take your tablet to a sotre and ask if they can borrow you another cable and test it. Hope this helps.
Click to expand...
Click to collapse
Thanks. That is what I am hoping. I ordered one online (mine is starting to fall apart at the standard USB end anyways). I was getting desperate yesterday and tried flashing up to AndroWood HairyBean 1.2. It didn't help. I am now stuck without a recovery but access to fastboot so if it is just a cable problem I should be able to get it up and running, otherwise I may have just bricked my tablet.
So it was a faulty cable. Got a new one, can now see my device and was able to fastboot and push the AndroWood Hairybean update to it and we're all good now!
Glad to help.
Dilhrnhydramine said:
So it was a faulty cable. Got a new one, can now see my device and was able to fastboot and push the AndroWood Hairybean update to it and we're all good now!
Click to expand...
Click to collapse
I'm glad it worked! So do you have Hairybean 1.2? If so, could you tell if it has wifi ad-hoc support? Cause thats the only thing that's keeping me on ICS. Thanks.

Can't find correct Windows 8 64-bit drivers.

Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.

[Q] Help restoring my rooted, S-OFF, moonshine DNA to stock

Hey!
This is my first time posting, but I have read tons of threads on here over the last year or so with my Droid DNA.
A while ago, I rooted my DNA, and unlocked the Bootloader, and used moonshine for S-OFF. I now want to undo all that I have done. Wiping data is no issue, I backed up all my info. I plan to get a new phone soon. Basically, I can't get adb drivers to work. So I deleted my drivers, and installed the ones mentioned in the thread linked below, and I can't find how to get these drivers to work.
My plan is to follow this thread, using step 3 (for moonshine). I have TWRP installed, and flashed the lock_bootlader.zip file provided there. I cannot get adb to work, however, for the next step. For example, "adb devices" returns no devices. And thus i cannot use adb commands. When I run "adb devices", it shows this. What do I do??
Thanks
Some more clarification:
I might also add that Device manager shows my phone as "HTC6435LVW", under "Portable Devices". It seems to recognize it as an MTP Device when I try to update the drivers, and won't let me update the drivers, because "The best driver software for your device is already installed".
In addition, HTC Sync Manager does not recognize my phone either. I should mention that I already chose "Reset Phone" from the Settings menu, and then also did a Factory Reset from TWRP.
I'm so confused by all this - Why can't I get ADB to recognize it?? I have been and will continue to be searching for solutions to this problem here on XDA and also on Google. And do I even need to do all this to give my phone back to Verizon?
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
RLGL said:
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
Click to expand...
Click to collapse
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
av ed said:
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
Click to expand...
Click to collapse
Ok thanks I will try this when I get home. Glad to see I'm not the only one with the problem!
EDIT: Thats the thread I am following, as I stated in the OP.
[/URL]
antrom1818 said:
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
Click to expand...
Click to collapse
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
RLGL said:
[/URL]
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
Click to expand...
Click to collapse
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
antrom1818 said:
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
Click to expand...
Click to collapse
Try a different cable.
RLGL said:
Try a different cable.
Click to expand...
Click to collapse
Thanks for the suggestion, I will try it when I get home and report back with an edit to this post!
EDIT: Nope, didn't work. Momentarily, I got it to install drivers. During that time, adb worked but not fastboot. So then I deleted the drivers to try to reinstall for fastboot, and now neither of them works.

Categories

Resources