Hi, I apologize for another "bricked A500" thread, but I was unable to find a solution, tried a couple of dozen, none worked. Here is the deal:
I received from a friend an A500 tablet, stuck at the Acer logo. Searched the forum, tried to update.zip all of the listed and uploaded, none of them worked. Got spooked, wanted to get my CPUID, nothing helped my device being recognized by the PC, installed drivers, checked with afterota, which informed me that drivers were fine. Afterota does not see the device, nor does the A500 manager, even when I am in the apx mode and acer picasso usb boot-recovery driver is recognizing the device, but else nothing. The A500 manager says no device connected.
At some point the usbdeview gave me a serial number, but it was an 11 digit number, starting with 1261. On the box (I do have the original box it came in) lists a different serial number, SNID, also 11 digits, starts with 1281. On the box is another number, SN, but starts with XE
At some point, I was pretty frustrated by then, some update.zip went through. I thought "this was it" but next boot showed "Boot verified failed ..." in red. All else does not work, even the try to update.zip with the same (or any other file, for that matter) fails. PC does not see the device, except in the apx mode, acer picasso usb boot-recovery driver. There is no CPUID. Power on/volume - produces only dead androids.
Any help would be greatly appreciated. As far as I know, USB debugging status cannot be determined. Thank you in advance for your time and effort. I will stay put and answer any questions you may have, and also try anything you throw my way. Thanks again.
EDIT: I just managed to switch from picasso driver to the Ader USB Boot-recovery driver and now the A500 manager does see the device in apx mode, unfortunately it does not extract CPUID (stays blank if I try) or does nothing else for that matter.
Hi there,
Am almost in same position... sad owner of a bricked A500 [and now also a n00b and hating myself, duh]
This is how I get my 16-digit number on a Windows PC (Win XP SP3, Win7 or Win8), without any extra tools:
- Plug the tablet into USB port and turn on
Windows should detect it and try to find a driver (which is going to fail)
- Open the Device Manager; ignore any "new device found" popups.
Find there the new device, it should be in "Portable Media devices" category.
- Right click on it, select Properties, then Details
On the details tab, select Device Instance Path
It should be like: USB\VID_XXXX&PID_YYYY&REV_zzzz\NNNNNNNNNNNNNNN
where NNNN... is the 15-digit number.
To that, add a leading 0 and this will be the 16-digit number which you can feed to the SBK generator (acerhacks.com/sbkcalc).
My number is totally different from the Acer's 11-digit "SNID" or other long string printed on their package.
By the way, my VID & PID is 18D1, 3341 and not 0502 & 3325 as in other A500 threads.
Whatever this is worth...
-- dd
Related
Problem was solved by changing the xml file to the language code.
Original Problem:
Hi everyone, just got the kindle today and finished root, then I used the Kindle Utility tool to change to fastboot.
As I finished the fastboot, it ended up stuck on the boot screen. Try serverl methods, but did not work.
According to:
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
"Once rebooted, connect your Kindle again via USB. You'll probably hear 3 tones (which means it recognized a device, but didn't load any drivers). In device manager, you'll see a device just called "kindle" or "unknown" with an exclamation point by it. At this point, you'll need to install drivers for it again. Pick "Browse my computer for driver software" BUT don't browse, just click on "Let me pick from a list...", and select "Android Phone" and then pick the newest "Android Composite ADB Interface" from the list. I think you may have 4.0.0.0 or something similar (you may have only a 2.x version possibly depending on which drivers you loaded to root your phone)."
But the problem here is that it the Windows Manager recgnized the kindle as an "Unkown Device" , and also I did not find "Android Phone" from the list, and cannot install driver manually as well. Does anyone have any suggestions?
just right click the unknown device and update the drivers
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Excellent method! Thanks
Retrieve your CPUID
(1) Use a500Manager Tool (download at bottom of post)
This tool is your first port of call! It will download the drivers, retrieve your CPUID, and flash the unlocked bootloader.
(2) Using Terminal Emulator
Reboot your tab
Code:
dmesg | grep androidboot.serialno
some have reported this did not work for them but that this one did when they tried it:
Code:
dmesg > /mnt/external_sd/dmesg.txt
(3)Using USBDeview
Suggest you extract to the same folder you used for your adb files,
USBDeview will only work when you have previously plugged your tab into the PC WHILE
you were running HC Rom and BL
1 Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2 Click on "VendorID" along the top to sort them
3 Look for the number "0502" under VendorID or 3325 "ProductID"
4 In the serial number column will be a 15-digit number this is your device ID
5 Write the number down and put a 0 in front of it and now you have your CPU ID!!!
(4) From your nandroid backup
In the cwm folder on your ext. sd card - open one of your backup folders and look for "uid.txt" file.
From cwm 1.7.2 on, will dislay your "uid" on the menu screen, and from memory TWRP does too.-
(5) Run command "adb devices" in command prompt HC ONLY
(6) From Custom Recovery
Most of the custom recovery's now have your uid displayed on the main screen of the recovery menu
(7) From a working Tab...
open yr file explorer, esfile explorer is a great one....
navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!!! easy peasy
(8)From a bricked or non-booting Tab
then things become a little more complex. And more involved if you have no backup.
The only way is using Linux. srbeen has a guide to do this using code by eppeP. There are those who being Linux noobs have had success with this method.
Read the whole thread as there are some helpful hints all thru the guide. If you get stuck eppeP is still around and will help out, if you can show an example of
"how and where" something does not seem to be working for you. If your questions go unanswered its because its been answered before so please go thru the thread!!!
here.
srbeens guide here
Cannot boot tab because:
(1) "Write Protected - need to enter password
If you encrypt your data and forget your password - you must do a full data reset wipe to get into your system again
(2) Stuck on the Acer Screen
From user JDGM3NT4L - Want to return to stock? This is for you...
A500 Back to Factory Stock the easy way
- via stock update.zip method
- no cpuid required,
- use with or w/out patched bootloader.
- needs cwm installed
- full data wipe needed
(3) Other things to check
- check data cables, micro-usb cable required
- plug in to another USB Port
- check you have the cable actually connected to both device
Try a different PC. Vista/Win 7/XP usually have no problems, there are issues with Win8 and 64bit systems
Also a heads up for when entering your uid's into the tool generators - a space counts as a character and will produce
an incorrect sbk!!!
You CANNOT use lowercase letters in your cpuid. If you do lowercase it will give you a different result
Vaches new SBK Tool here OR [/B]
DRIVERS
The drivers are not installed properly, I can hear you all already!! I've done that over and over and its not working!!!!
sometimes if you fail to complete a nvflash you need to completely reinstall the Acer Drivers before it seems to want to finish...ssoooooooo, uninstall and reinstall!!!!
Acer Support for Acer APX/Fastboot/Recovery Drivers
Android SDK for the adb/USB drivers - You can d/l a mini zip containing just the adb and fastboot drivers attached to this post "adb_fast.zip"
GUIDES
Civs Guide to flashing the bootloader
walkthrough using apxflash tool at Step 6
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide here
Iconia Root/gingerbreak: For returning to Honeycomb
GETTING ADB SET UP
It's a pain typing "my path" into cmd, can't I just type "adb devices"
Set adb as Environment Variable or call adb direct from command prompt
first, copy the path to your install - in this case:
"Path to adb" = C:\android\
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in this case C:\android\adb
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥
I added a link to this in the V3 guide.
Thanks for this.
civato said:
I added a link to this in the V3 guide.
Thanks for this.
Click to expand...
Click to collapse
Why thank you...all good civ, anything to help really
Stock ICS unable to access any of this...
dibb_nz said:
If you are upgrading/downgrading using APX mode then you need your cpu id.
if you're having problems then keep reading...
Upgrading via an EUU/SBK method is dependant on a "successful communication connection" between your TAB and PC
If you cannot run "adb devices" and have it return your CPU ID then the flashing process will fail.
If you have a custom ICS rom AND on the HC Bootloader this number will be your serial no. please see note below
ok, lets go, you need the correct drivers installed to begin with:
1) go to Acer Support and download the Acer Drivers
2) run the Setup.exe to install them
You must also have the ADB drivers from the android-sdk (see attached zip)
3) Extract the adb files to your desktop
4) Open command prompt as admin
5) In the command prompt window type cd
6) leave a space after it
7) drag and drop the adb folder into the command window (This saves you having to enter the path manually)
8) Now, type adb devices and write your device ID down with a zero in front...done!!!
If you cannot get adb to retrieve your ID then the flashing process will not work as it should.
You need to fix this first....
*****Note: HC Bootloaders on custom ICS builds
adb will report your device ID as your serial number, which of course will not work for APX based flashing - thanks to tehdomil for the heads up
you guys will need your original HC CPU ID which you can get from the back up you made before flashing the ICS rom. For those that didn't - try usbdeview below.
*****How to retrieve your CPU ID from USBDeview
Suggest you extract to the same folder you used for your adb files, just to keep things tidy...you're bound to want these things again
1) If you haven't plugged your tab into this pc before, do so now, before you run the program.
1a) Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2) click on "VendorID" at the top to sort them
3) Look for the number "0502" under VendorID or 3325 "ProductID"
4) In the serial number column will be a 15-digit number this is your device ID
5) Write the number down and put a 0 in front of it and now you have your CPU ID
The adb guide will still apply as far as getting your tab and pc talking on the same wave length
Click to expand...
Click to collapse
Ok, followed all the steps. But cannot get my PC to recognise my tablet completely. MTP:yes, or Camera:yes, yet there is a driver missing which fails to load/install. Any ideas from you bright people?
I would like to access bootloader and flash recovery.
V frustrating.
For example, where do you find mtpfs and mount for Win 7 x64?
Thanks
DrPlumEU said:
Ok, followed all the steps. But cannot get my PC to recognise my tablet completely. MTP:yes, or Camera:yes, yet there is a driver missing which fails to load/install. Any ideas from you bright people?
I would like to access bootloader and flash recovery.
V frustrating.
For example, where do you find mtpfs and mount for Win 7 x64?
Thanks
Click to expand...
Click to collapse
What shows in the command window after typing in adb devices?
dibb_nz
/ adb devices
List of devices
/
In device manager, I have a "Other devices" Acer Iconia A500 no driver installed, yet "Portable Device" Acer Iconia A500 is fine.
I can copy and paste files from tablet while in MTP mode. No difference with SD card mounted or unmounted.
Very frustrating. The last device driver I assume is "USB device" but despite mucking around with Acer USB device drivers 1.00.0524 and 1.06.1500 no luck.
Grr
oops.....
save for later
list of devices shows but no number
DrPlumEU said:
dibb_nz
/ adb devices
List of devices
/
In device manager, I have a "Other devices" Acer Iconia A500 no driver installed, yet "Portable Device" Acer Iconia A500 is fine.
I can copy and paste files from tablet while in MTP mode. No difference with SD card mounted or unmounted.
Very frustrating. The last device driver I assume is "USB device" but despite mucking around with Acer USB device drivers 1.00.0524 and 1.06.1500 no luck.
Grr
Click to expand...
Click to collapse
sorry bit caught up at the moment
things to check first:
...1) That you do have USB debugging enabled:Settings>Applications>Development
...2) Win7/Vista work best; XP can be titchy
...3) You d/l the "Just_adb.zip" to install the adb drivers - you dont mention an entry for them in Device Manager
...4) Switch USB ports on your pc
...5) Try another USB cable
...6) Put the MTP thing aside for now, they have no bearing on this issue
If still no joy then if you can, try another pc
If thats not possible then uninstal and reboot both devices
then reinstall both acer and adb - acer ones mainly
When you connect your tab again WAIT for windows to install them and see how u go
ADB or USBDeview both tell me that my CPUID is 0123456789ABCDEF. Of course, if I get the SKB and use NVFlash to validate it, it fails with a message that says "USB device not found."
I found my CPUID (0x033c20c541a051d7) in an old nandroid backup and tried it but with the same results.
Any ideas?
CPU ID : Dev ID : UID
spoupard said:
ADB or USBDeview both tell me that my CPUID is 0123456789ABCDEF. Of course, if I get the SKB and use NVFlash to validate it, it fails with a message that says "USB device not found."
I found my CPUID (0x033c20c541a051d7) in an old nandroid backup and tried it but with the same results.
Any ideas?
Click to expand...
Click to collapse
Ok i'm amending the guide as we speak, just to be clearer.
The device ID as reported by adb is 15 digits long the (UID)
when we use this no. for an EUU based flash we add a 0 to the front making 16 digits (CPUID)
the one in your nand adds 0x to the basic UID 17 digits
the CPUID from the EUU is for Honeycomb bootloaders
Which I believe is different for ICS bootloaders
and different again for HC b/l on ICS Rom!!!
i tried the SBK generator last nite for the first time and entered only my UID
and had no probs
so give that a go (in the example you gave) 033c20c541a01d7
dibb_nz said:
Ok i'm amending the guide as we speak, just to be clearer.
The device ID as reported by adb is 15 digits long the (UID)
when we use this no. for an EUU based flash we add a 0 to the front making 16 digits (CPUID)
the one in your nand adds 0x to the basic UID 17 digits
the CPUID from the EUU is for Honeycomb bootloaders
Which I believe is different for ICS bootloaders
and different again for HC b/l on ICS Rom!!!
i tried the SBK generator last nite for the first time and entered only my UID
and had no probs
so give that a go (in the example you gave) 033c20c541a01d7
Click to expand...
Click to collapse
Thanks for your help, but no luck. I tried the 033c20c541a01d7 number already in SBK and NVFlash still gives the same error. BTW, SBK generates the same number for both 033c20c541a01d7 and 0x033c20c541a01d7. Apparently, SBK is smart enough to ignore the leading 0x.
Any other suggestions?
spoupard said:
Thanks for your help, but no luck. I tried the 033c20c541a01d7 number already in SBK and NVFlash still gives the same error. BTW, SBK generates the same number for both 033c20c541a01d7 and 0x033c20c541a01d7. Apparently, SBK is smart enough to ignore the leading 0x.
Any other suggestions?
Click to expand...
Click to collapse
that blows that theory
what does dmesg say?
edit: what tool are u using for nv flash, what b/l u on?
and if ADB or USBDeview both tell you CPUID is 0123456789ABCDEF then.....
spoupard said:
....if I get the SKB and use NVFlash to validate it, it fails
Click to expand...
Click to collapse
So, the NV Flash tool invalidates the uid/sbk where usbdeview and adb agree??
with a message that says "USB device not found."
Click to expand...
Click to collapse
i no nothing of the nvflash process "in this instance" but if device is not found then there is no "connection" happening between the 2....have u posted on the thread where you got the tool?? not trying to fob you off at all its just theres alot methods out there at the moment and i'm doing my best to keep up with them all!!!
I found my CPUID (0x033c20c541a051d7) in an old nandroid backup and tried it but with the same results.
Click to expand...
Click to collapse
are you saying cpuid here is different to what the other 2 report???
i'll be out for an hour or so but will stop in when i get back . good luck
dibb_nz said:
So, the NV Flash tool invalidates the uid/sbk where usbdeview and adb agree??
i no nothing of the nvflash process "in this instance" but if device is not found then there is no "connection" happening between the 2....have u posted on the thread where you got the tool?? not trying to fob you off at all its just theres alot methods out there at the moment and i'm doing my best to keep up with them all!!!
are you saying cpuid here is different to what the other 2 report???
i'll be out for an hour or so but will stop in when i get back . good luck
Click to expand...
Click to collapse
I'm using NVFlash from civato's post on how to flash the ICS bootloader. I have a connection because I can launch a shell in ADB and navigate around on my tablet. Also, if I didn't have a connection, "adb devices" would not return any devices. I can also see the device listed in Windows device manager.
I am running the HC bootloader with CM9 ROM. I had been using TeamWin recovery, but found out it is not compatible with the ICS bootloader. I have since replaced that with the ACER Recovery found in the Market. I did another nandroid backup after installing ACER Recovery (thor's recovery) and it gave me a cpuid of 033c20c541a051d7.
- u got adb ones all good bt not apx ones - reinstall acer drvs
spoupard said:
I'm using NVFlash from civato's post on how to flash the ICS bootloader. I have a connection because I can launch a shell in ADB and navigate around on my tablet. Also, if I didn't have a connection, "adb devices" would not return any devices. I can also see the device listed in Windows device manager.
Click to expand...
Click to collapse
yep the usb-adb drivers are all there but you said earlier u have a fail error of device not found from the flash validator, so it sounds like the issue was not the incorrect sbk but the device not found....run the acer driver setup ...windows will install the apx drivers when your tab is ready to enter apx/download mode.
I am running the HC bootloader with CM9 ROM. I had been using TeamWin recovery, but found out it is not compatible with the ICS bootloader. I have since replaced that with the ACER Recovery found in the Market. I did another nandroid backup after installing ACER Recovery (thor's recovery) and it gave me a cpuid of 033c20c541a051d7.
Click to expand...
Click to collapse
I have no idea why you have so many uid's, if any one knows how exactly these are generated from recovery, i'd love to know!!!!
dibb_nz said:
So, the NV Flash tool invalidates the uid/sbk where usbdeview and adb agree??
i no nothing of the nvflash process "in this instance" but if device is not found then there is no "connection" happening between the 2....have u posted on the thread where you got the tool?? not trying to fob you off at all its just theres alot methods out there at the moment and i'm doing my best to keep up with them all!!!
are you saying cpuid here is different to what the other 2 report???
i'll be out for an hour or so but will stop in when i get back . good luck
Click to expand...
Click to collapse
dibb_nz said:
yep the usb-adb drivers are all there but you said earlier u have a fail error of device not found from the flash validator, so it sounds like the issue was not the incorrect sbk but the device not found....run the acer driver setup ...windows will install the apx drivers when your tab is ready to enter apx/download mode.
I have no idea why you have so many uid's, if any one knows how exactly these are generated from recovery, i'd love to know!!!!
Click to expand...
Click to collapse
Well I have to admit that this whole problem was my fault. No matter how many times I read the instructions, I somehow breezed right past the part about entering apx mode. Thank you so much for your help!
I don't have enough numbers
Okay I tried using USBDeview and it came up with a 11 digits - looked where the instructions said.
dawgpoundfan said:
Okay I tried using USBDeview and it came up with a 11 digits - looked where the instructions said.
Click to expand...
Click to collapse
Try to run dmesg from yr tab first, ------ hat tip to jp
If you haven't rebooted your Tab for a while, then in the output of dmesg, the very old entries, the ones just after bootup, which contain the entry/line containing 'androidboot.serialno' are lost/overwritten.
Just reboot your Tab & run dmesg again.
Just use the command ''dmesg | grep androidboot.serialno"
Voila!
Cheers, Jp
Click to expand...
Click to collapse
I can;t seem to find my cpuid. I am running a custom ics rom, with the HC bootloader.
Do not have a nandroid backup to look at.
dmesg does not show androisboot.serialno after a reboot.
osbdeview shows an 11 digit number.
Any ideas?
I am sorry if this topic is covered in other threads. I search around and could only find the developer thread and I am not yet allowed to post there.
--------------------------------------------------------------
I have a new Nexus 7 running Jelly Bean 4.2.1. I have activated developer mode and checked the "USB Debugging" box. Other than that, it is in the default configuration.
I want to root it, so I went to http://forum.xda-developers.com/showthread.php?t=1809195 and downloaded the Google Nexus Toolkit.
After identifying my device (Android 4.2.1 (Build JPP40D) for Wi-Fi Only 32GB), the first option was the install drivers. I did that. The 2nd step was to backup the device and I did that with no problems.
The 3rd step was to Unlock the Bootloader (requires Fastboot Mode). When I try to do this, it says that a Fastboot Device was not found.
I am at a loss here as to what to do?
I have some screencaps. I hope this helps.
Ideas?
http://forum.xda-developers.com/showthread.php?t=1741395
simms22 said:
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
TY, this says I need to be able to use "adb and fastboot". That is the problem. I do NOT know anything about fastboot. I turn off my nexus and then hold the volume up and volume down buttons then turn it on. I get a screen that looks like the image I have attached.
However, I do not know what to do from here. I press the volume up and down keys to change "Start" other options, but Fastboot is not one of the options.
Ideas?
You don't have the right drivers installed. When you see the boot loader screen, you should see 'android fast boot interface' or similar in your device manager.
Sent from my Nexus 7 using xda app-developers app
Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Keep clicking OK a few times, it might find it.
if not, then, press the volume down button until it says reboot bootloader or reboot recovery, sorry i can not remember 100% right now,
press ok a few times more, well keep pressing it and it will find it
adamz2013 said:
Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Click to expand...
Click to collapse
You are replying to a post from December 16th. Doubtful that the OP is still waiting on an answer.
Nice pot shot at people that do try to help, though. Either that or an unmet entitlement issue. No one in here is entitled to an answer for anything. Anything you or others provide in response to an inquiry is a gift, plain and simple. The answers might even be completely wrong or crap; but they are still a gift.
If the OP is still waiting, then they should know that all the detail that they showed (screenshots) are immaterial as they were taken with the device booted into the OS (composite ADB + MTP/PTP showing in Device Manager) instead of the mode that was having communication difficulties - fastboot/bootloader mode.
Immaterial information does not imply that the wrong driver is installed for a different operating mode for which similar information was not provided.
Most of the trouble in these types of post are due to the fact that the posters have no clue how WINDOWS drivers are managed/installed/ etc. That has everything to do with WINDOWS and user skills, and almost nothing to do with the device on the other end of the cable.
Having said that, the principal reason there is confusion is due to the following set of circumstances:
- Casual Windows users are "accustomed to" doing a single install of a driver package when they buy a new device. Even when that device might have many logical endpoints across the USB bus. (Think of a multi-function printer - it might have an SD card slot on it, the printer, a scanner function, etc). When that multifunction behavior exists, usually the OEM provides a "driver installer" package which will actually install multiple drivers, depending on the plurality of USB endpoints in the device.
- Unfortunately, if you carefully inspect any of these three driver bundles:
- Google (SDK) USB Driver
- Asus Nexus 7 USB Driver
- XDA "Universal Naked Driver"
you will find that (as shipped) NONE OF THEM will work for all of the following modes of the Nexus 7:
- Fastboot mode
- ADB Mode, OS (Single or Composite)
- ADB Mode, Custom Recovery
- APX Mode
- PTP Mode*
- MTP Mode*
That's right. As shipped NONE OF THEM will handle all of these cases. The "as shipped" part is a reference to the fact that a trivial edit of the "android_winusb.inf" file for any of them will allow a single driver to handle all fastboot and ADB modes.*
* The MTP/PTP drivers are meant to be handled by MS Windows generic class drivers; in the case of Windows XP you might need to install a Windows Media package to get the MTP driver - I'm not sure that it is part of Vanilla XP SP3
So, anyhow - people get confused because they "install the driver" for one mode (usually ADB), and then are surprised when they boot the device into a different mode (fastboot or ADB running under custom recovery) and surprise, surprise - their PC says "unknown device".
My advice?
Install the Asus Nexus 7 Driver for everything but the Custom Recovery ADB mode, and then install the Universal Naked Driver for that.
Or, prior to installation fix up the android_winusb.inf file that comes with the Asus driver so that it also supports
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
Then a single driver will support everything but APX, MTP, and PTP. The latter two of which are provided by Mister$oftie, and the first of which is currently of unknown value to Nexus 7 rooters.
cheers
That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.
juicejuice said:
That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.
Click to expand...
Click to collapse
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.
bftb0 said:
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.
Click to expand...
Click to collapse
I am a Mac user, and I'm having problems with fastboot. My nexus is unlocked, and I'm trying to flash the lastest 5.1 factory image. I was rooted long ago, but really have no need for root, and lost it during one of the OTA's. I'm not a noob by any means, but none of my terminal commands are working, because fastboot has decided to disappear on me. Any suggestions would be appreciated.
I can't even get TWRP because I don't have root, and I can't get into fastboot.
Edit.....I'm an idiot....I figured it out. On top of it all, my USB cable sucks too so that didn't help any.
Error messages
In device manager, a device named "APX" (within <computer>/Other Devices) with a yellow icon on the lower portion had the following inside its properties box:
-----
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
-----
blackthund3r's A500 Manager reports at the bottom, "A500 Detected in APX Mode. Please install the drivers!"
Circumstances
I am using a Windows 8.1 PC. I have an Acer A500 running an unknown ROM that is bricked. It boots to Acer logo, then continually loops the android text animation.
I am able to boot the device consistently in APX mode. (The trick is to unplug the power cord before starting, so one can see when the power button is lit, to time the release of the power and reset buttons properly. The tricky part is remembering to plug the power back in.)
Attempts so far
I am trying to start over with a clean (EUU?) ROM, but first, I need the CPUID to get the SBK.
After following blackthund3r's guide at http://acerhacks.com/ , I downloaded the A500 Manager executable. I also got "ICONIATABUSBDriverSetup.exe" from a source I do not recall, but I am fairly certain it was a link from forum.xda-developers.com .
I also followed the instructions at http://forum.xda-developers.com/showthread.php?p=48827675#post48827675 to get the folder full of "ini" files. I tried manually updating the driver from within Device Manager using files from this folder. This still did not work. :'-(
My plea
Can anyone help? Should I try a friend's Windows 7 computer? I don't want to install Ubuntu. If I must, will installing it inside VirtualBox work?
alexAG76 said:
My plea
Should I try a friend's Windows 7 computer?
Click to expand...
Click to collapse
Yes!!!
XP, vista or win7 all work fine.
Win8 or any 64bit systems have issues.
Sent from my GT-I9300 using Tapatalk
alexAG76 said:
Error messages
In device manager, a device named "APX" (within <computer>/Other Devices) with a yellow icon on the lower portion had the following inside its properties box:
-----
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
Can anyone help? Should I try a friend's Windows 7 computer? I don't want to install Ubuntu. If I must, will installing it inside VirtualBox work?
Click to expand...
Click to collapse
To get windows to recognize the drivers properly, go into device manager and find the APX driver with yellow triangle. Update the driver for this but chose 'browse my computer for driver software". Direct it to crogram Files (x86)/Acer Inc. This should force it to find the correct driver. I am of course assuming you have the Acer driver installed.
I just bricked and unbricked this device a month ago. What an adventure. APX mode will lead you down the right road. Combined with the toolkits available, you can have it back up in a couple hours.
This link may help you out. http://forum.tegraowners.com/viewtopic.php?f=30&t=388
One thing is getting the uid. If you have an old nandroid off of the device it will be very helpful. There is a file in it that has a number in it that can convert to the UID. if you need more help let me know and I will dig through my history and find the resources I used.
dibb_nz said:
XP, vista or win7 all work fine.
Win8 or any 64bit systems have issues.
Click to expand...
Click to collapse
Using Vista/Win7, I kept hearing the "device connected" noise in APX mode. Device manager refreshed several times, but I could never find the non-functioning device icon in order to update the drivers.
alexAG76 said:
Using Vista/Win7, I kept hearing the "device connected" noise in APX mode. Device manager refreshed several times, but I could never find the non-functioning device icon in order to update the drivers.
Click to expand...
Click to collapse
Does safely remove hardware icon in the system tray show anything???
Sent from my GT-I9300 using Tapatalk
BCSC said:
To get windows to recognize the drivers properly, go into device manager and find the APX driver with yellow triangle. Update the driver for this but chose 'browse my computer for driver software". Direct it to crogram Files (x86)/Acer Inc. This should force it to find the correct driver. I am of course assuming you have the Acer driver installed.
I just bricked and unbricked this device a month ago. What an adventure. APX mode will lead you down the right road. Combined with the toolkits available, you can have it back up in a couple hours.
This link may help you out. (URL omitted due to newbie status.)
One thing is getting the uid. If you have an old nandroid off of the device it will be very helpful. There is a file in it that has a number in it that can convert to the UID. if you need more help let me know and I will dig through my history and find the resources I used.
Click to expand...
Click to collapse
Thanks. I'm about ready to throw in the towel, but I shall look at that URL.
I think my drivers are defective.
dibb_nz said:
Does safely remove hardware icon in the system tray show anything???
Click to expand...
Click to collapse
I will have to check. I've already purchased a replacement, but it would be nice to get this thing going again. Thanks for the responses.
alexAG76 said:
Using Vista/Win7, I kept hearing the "device connected" noise in APX mode. Device manager refreshed several times, but I could never find the non-functioning device icon in order to update the drivers.
Click to expand...
Click to collapse
Open up a couple branches in device manager and plug/unplug it. Do this until you find which branch it is in. Then apply the driver the way I mentioned above. At some stage you will come across the branch that changes. It should only take a couple minutes. Just watch and you will see a new item pop up. You are experiencing the same issues that haunted me and this method will work. Start at the bottom of the device manager list and work up. I'm confident it was towards the end. Hearing that connection sound means that it will be there.
Hi everybody.
I have a problem with my Nexus7 tablet, windows 8 can't see it on Devices and drivers and after I plug off the usb cable this error message appears:
Image like: The last USB device you connected to this computer malfunctioned, and Window does not recognize it.
First thing I opened the developer options and checked USB Debugging, after that a strange icon with 4 vertical white rows appears on the notification tab, It was not the usually USB debugging icon.
Then I went on Device Manager and under Acer Devices (Why Acer ???) I found ACER Composite ADB Interface, so I've decided to install again the drivers following this guide:
-----------------
But at the point 8 I can't see "USB composite device" but only "Acer composite ADB interface".
Since yesterday the tablet worked, and I have not update the tablet neither the pc.
What should I do ?
Thanks for the help, sorry for my bad english
* I have few message so I can't upload images or link, sorry for the inconvenience.
I opened now "Devices and Printers" and I saw Nexus7 (with the correct label) under "unspecified", I cannot interact with it
mmm no one ?
I have the same issue with my 8.1 laptop. I think the Acer driver is something which Microsoft pushed in an update to 8.1 recently. I may go in and see if I can revert it. Not sure I am much help as my only workaround was to grab my Win 7 laptop, which worked as it should. I did not have the time or patience to screw with it.
Pickeroll said:
Hi everybody.
I have a problem with my Nexus7 tablet, windows 8 can't see it on Devices and drivers and after I plug off the usb cable this error message appears:
Image like: The last USB device you connected to this computer malfunctioned, and Window does not recognize it.
First thing I opened the developer options and checked USB Debugging, after that a strange icon with 4 vertical white rows appears on the notification tab, It was not the usually USB debugging icon.
Then I went on Device Manager and under Acer Devices (Why Acer ???) I found ACER Composite ADB Interface, so I've decided to install again the drivers following this guide:
-----------------
But at the point 8 I can't see "USB composite device" but only "Acer composite ADB interface".
Since yesterday the tablet worked, and I have not update the tablet neither the pc.
What should I do ?
Thanks for the help, sorry for my bad english
* I have few message so I can't upload images or link, sorry for the inconvenience.
Click to expand...
Click to collapse
You may wish to go to Storage, on the Nexus 2012, and under the 3 dots, USB computer connection menu, and tick/untick Media Device
Windows 7 and 8, appear to have USB storage driver conflicts, when many different devices have been used repeatedly.
Good Luck!
There are other posts, in the General section, that deal, with this annoying issue.
ROLY5573 said:
You may wish to go to Storage, on the Nexus 2012, and under the 3 dots, USB computer connection menu, and tick/untick Media Device
Windows 7 and 8, appear to have USB storage driver conflicts, when many different devices have been used repeatedly.
Good Luck!
There are other posts, in the General section, that deal, with this annoying issue.
Click to expand...
Click to collapse
Thanks for the hep but it didn't work.
Now the "old" icon came back with "connected as a media device" written with it but the tablet remain invisible.
Same problem here.
Fixed it by disconnecting teh device, going to device manager, showing hidden devices and uninstalling everything related to Nexus 7.
This includes Acer ADB, Android, Nexus7 and unknown devices.
After that I downloaded the Android SDK and installed the Google USB driver from it, connected my Nexus 7 and it werks.
pepo930 said:
Same problem here.
Fixed it by disconnecting teh device, going to device manager, showing hidden devices and uninstalling everything related to Nexus 7.
This includes Acer ADB, Android, Nexus7 and unknown devices.
After that I downloaded the Android SDK and installed the Google USB driver from it, connected my Nexus 7 and it werks.
Click to expand...
Click to collapse
Still nothing, I showed the hidden devices and unistalled all the voices under the "Acer" directory, I haven't found anything related to Android/Nexus 7.
Then i went to http://developer.android.com/sdk/win-usb.html and downloaded the USB driver, but the Nexus7 result again as an unspecified hardware.
Now it works ! I didn't touched it in the last 2 hours and now it works. :good::good: