Am I stuck in APX mode with no USB connectivity and how do I get out of this? Here is what happened:
A500 with OTA Android Build: Acer_AV041_A500_1.033.00_PA_CUS1
Windows 7x64 with UAC turned off and restarted OS
- Launch Afterota v1.09
- Info tab > Install Driver ... "ACER ICONIA 3G DRIVER INSTALL"
- Boot A500 > ENABLE USB debugging
- Plug USB cable into A500 ... "Acer Iconia Tab A500 ... Your device is ready to use"
- Tablet Information ...
Tablet Serial : 11933073415
Tablet Cpuid : 028841854280E4D7
Tablet Sbk : 0x15290000 0x7FC6C006 0x47E52404 0x302C2103
Android Build : Acer_AV041_A500_1.033.00_PA_CUS1
Bootloader : 0.03.12-ICS
- Save Values to AcerIDs.txt
- Standard tab > Bootloader Ics v3.14.8 + Recovery Thor v1.7.3 > For A50X
- Install sys rw patched kernel (sys rw patch only, no overclocking)?
- Yes > OK
- A500 boots to APX Mode
- Afterota status ... flashing (about 1 minute) ... idle (no further activity ... ever)
A500 screen is BLACK, Power LED is ON, all the Afterota buttons are grayed out except for Unsoftbrick Browse.
Driver: OK - driver installed
Usb: ERROR - connect usb cable and enable usb debugging
I've tried reinstalling the USB driver multiple times and using different USB ports with no luck. I can turn A500 on and off by holding down the Power LED button for 3 seconds, but still a black screen.
Any ideas will be appreciated
May have a possible Fix for you
EDIT: OK May have a possible Fix for you I've just run this myself from apxmode and it worked for me...give it a whirl and see how you go!!!
check this thread here
##############################################################
the 'mode' yr tab is in now - black screen with power lite....
i'm sure its waiting for the apx driver to load this will enable yr tab to enter the next stage where the flash takes place..(this stage is called different things depending on which tool u use...which doesn't help matters at all...) you will know when u enter "the next stage" because yr tab will display some white text "a500 apx mode" or "acer download mode" even "a500 bootloader mode" they're all the same -
so if u do not have the white text displayed the only conclusion one can come to is that the required driver cannot be found....(if I'm wrong on this then please put your 2cents worth in and maybe we can get this problem solved once and for all)
you need to have the "acer usb-boot recovery driver" displayed in your system tray under safely remove h/w or in device manager. Is it there....?
Device manager is yr friend always have it open when trying to troubleshoot flash issues.
connect yr tab to yr pc with yr mini usb data cable - the flash will definietly not happen if you're using a regular sized usb cab le!!!!
is the driver listed under usb controllers?
is there an "APX Device" listed?
if not disconnect and power yr tab off
then enter apx mode manually and reconnect cable and see if the boot-recovery driver installs itself - if it doesn't then reinstall the acer drivers....again!
also if it hangs on the black screen again
always disconnect yr usb cable close the program down and try again.
your other choice is to use civs nvFlash cos it requires yr tab to be in apx mode first - if it fails it will show you an error which will help
There seems to be alot of ppl of late getting stuck in this mode...and there seems to be no real solution to it.....sometimes you just have to keep at it until it works... if all else fails then u may need to downgrade back to HC and try from there!!!
Please let us know how u get on....
cheers
EDIT you need the android drivers too - theres a zip file in my cpuid thread if u need them
I've tried your suggestions, only using AfterOTA so far ... still no success.
These are the steps I've been following:
1) Disable UAC > Restart
2) Run Afterota.exe
3) AfterOTA (Info tab): Install Driver
4) Power on A500 (screen is still black, Power LED is white) ... plug in micro-USB cable from PC ... "driver successfully installed"
5) AfterOTA (Advanced tab): Unsoftbrick ... browse to ... recovery_thor17_403.img
6) AfterOTA (Advanced tab): Unsoftbrick ... browse to ... ics_boot_unlk_V6_500.bin
7) AfterOTA (Advanced tab): Unsoftbrick ... Install
[1/3]loading apx mode bootloader
[2/3]flashing recovery ..
This is where it gets stuck. No vibrating, the screen remains black (no text), nothing even after 5 minutes. I've repeated steps 5-7 trying two different USB cables plugged into the A500 micro-USB (small) port and also connected to different USB ports on my PC. Each time I shut down AfterOTA, unplugged the USB cable, powered off A500 ... then try again. I've also tried uninstalling and reinstalling the USB driver using AfterOTA.
Every time A500 is powered on and connected to USB ...
- "Acer USB Boot-recovery driver" is listed in Device Manager, USB controllers
- "APX" is listed as an Unspecified device in Devices and Printers (not in Device Manager)
- "Usb: ERROR - connect usb cable and enable usb debugging" listed in AfterOTA (Info tab)
It appears AfterOTA can't establish communication over the USB connection.
The very first time I used AfterOTA, A500 was still able to boot to ICS, the USB connection was OK and I was able to retrieve the Acer IDs and save them to a txt file. It was only after flashing "Bootloader Ics v3.14.8 + Recovery Thor v1.7.3" that I got the "Black" screen. It appeared the flashing was successful, as it had completed step [5/5] and then showed status "idle .."
I guess first priority is to find a something (maybe other than AfterOTA) to see if it can communicate with A500. Haven't tried civs nvFlash ... yet.
Thanks for your help.
FCBelser said:
Every time A500 is powered on and connected to USB ...
- "Acer USB Boot-recovery driver" is listed in Device Manager, USB controllers
- "APX" is listed as an Unspecified device in Devices and Printers (not in Device Manager)
Click to expand...
Click to collapse
ok, this is weird:
you are saying device manager reports the boot-recovery driver installed
But there is also an unspecified APX device????
Are u using win7/64 by any chance as there have been some issues reported by those users - are u able to try another pc??
Try manually installing the driver the apx device, by pointing it to the acer folder in program data
what happens there??
- "Usb: ERROR - connect usb cable and enable usb debugging" listed in AfterOTA (Info tab)
It appears AfterOTA can't establish communication over the USB connection.
Click to expand...
Click to collapse
- while yr tab is in apx mode you will have no access to adb or usb b/c apx is using the USB connection -
I guess first priority is to find a something (maybe other than AfterOTA) to see if it can communicate with A500
Click to expand...
Click to collapse
Yeh I wish it were that easy - I've been working on this for a whole week now, as lately there have been a number of "stuck in apx mode" reports - altho yours is the first of it happening using afterOTA - there just doesnt seem to be an easy way out of it,,,its happened twice previously on my tab - i got it working but i cant tell you how....i just kept trying over and over till it worked!!!
If you do give nvFlash a try - edit the .bat file and delete the "cls" commands this will give you a chance to 'see' whats going on...
another tip: after entering your sbk make sure the "system information" window pops up - it will show amongst other things your "chip uid" this is yr cpuid - if you carry on without yr tab being in "bootloader mode" you can end up with a really, truly 'brick' on yr hands - see the walkthru in my sig if you need further guidance
[1/3]loading apx mode bootloader
[2/3]flashing recovery ..
Click to expand...
Click to collapse
once it completes "loading apx mode bootloader" this is when yr tab should vibrate and display the white text "acer a500 apx mode" which is what
leads me to believe that for some reason its waiting for the driver even when it seems to be installed already.....this is where i think the problem lay.
The only other tool that may work is timmydeans v4 it uses apx mode as well but will roll u back to HC, it also repartitions and 'resets' your tabs file system as alot of tabs have got stuck on "formatting partitions" with the flash...hopefully this won't happen to yours but you'll find out after running nvFlash tool...
apxFlash has never been able to pick up the fact my tab is in apx mode, it, like afterOTA relies on adb to gather the required tab info, and of course if it doesnt recognise your tab it doesnt know its connecteD!!! At least afterota recognises this by the fact the "unbrick" menus are not greyed out...
The only other thing i might suggest is putting yr tab in apx mode manually -
Turn tab off
use a paper clip to push and hold the reset button
then press and hold the power button UNTIL the power Lite comes on
count 3 secs and release
then after another second release the reset button
might seem strange thing to try, but you never know it may just 'jog' something into life
Yes ... I'm using Win7 64-bit.
When I plug the USB cable into the A500 ...
1) Acer USB Boot-recovery driver shows up in Device Manager ... listed under USB controllers
2) An APX icon shows up in Devices and Printers (not in Device Manager) ... it's listed under a category call "Unspecified"
When I unplug the USB cable, both 1) and 2) go away.
For manual driver install ... are you referring to:
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\ADB\x64\android_usb.inf
-or-
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\USB_ethernet_rndis\x64\acer_usb_ethernet_rndis.inf
-or- something else?
I have an older laptop running Win7 32-bit, so I'll also try that too.
FCBelser said:
Yes ... I'm using Win7 64-bit.
When I plug the USB cable into the A500 ...
1) Acer USB Boot-recovery driver shows up in Device Manager ... listed under USB controllers
2) An APX icon shows up in Devices and Printers (not in Device Manager) ... it's listed under a category call "Unspecified"
When I unplug the USB cable, both 1) and 2) go away.
For manual driver install ... are you referring to:
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\ADB\x64\android_usb.inf
-or-
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\USB_ethernet_rndis\x64\acer_usb_ethernet_rndis.inf
-or- something else?
I have an older laptop running Win7 32-bit, so I'll also try that too.
Click to expand...
Click to collapse
something else, lol hold on....i'll just go check
I tried the paper clip / power button trick ... and then back to AfterOTA on Win7x64 ... no luck. I also tried AfterOTA on my laptop (Win7 32-bit) ... exact same problem.
ok this is where things get even weirder...and from memory it was a real pain to get this apx device installed....windows kept wanting an inf file but i'm positive that in the end i got it to install from a folder - i just cant remember how????
I cancelled the hardware wizard from doing its thing
then in the next window there are 2 options
let windows choose or let me choose - something like that
i kept trying let me choose and got nowhere
then i think i tried "search my computer" and chose the C drive - i'm sure it found the right ones that way
and i think i uninstalled all acer and android drivers, rebooted and reinstalled them before i could get any joy....i know it took a good 5-6 hours of mucking about - until finally something worked...
and yes def give 32 bit a go before we get too carried away!!!
oh no... i think i've jsut got stuck in apx mode...
---------- Post added at 08:41 AM ---------- Previous post was at 08:17 AM ----------
FCBelser said:
I tried the paper clip / power button trick ... and then back to AfterOTA on Win7x64 ... no luck. I also tried AfterOTA on my laptop (Win7 32-bit) ... exact same problem.
Click to expand...
Click to collapse
then the only other thing to do is a rollback using timmydeansv4. run the tool without yr cable connected and wait for the instructions to put yr tab into manual apx mode - you wont have to worry bout that seeing as you're in it already!!! connect yr cable and click OK - enter cpuid and wait 10mins for it to do its thing...it won't take any longer than this -
let us know how you go!! and good luck m8
Where can I find timmydeansv4? Google search isn't finding it.
Thanks
FCBelser said:
I tried the paper clip / power button trick ... and then back to AfterOTA on Win7x64 ... no luck. I also tried AfterOTA on my laptop (Win7 32-bit) ... exact same problem.
Click to expand...
Click to collapse
i renamed the Acer Folder in Program Files
I then put my tab in manual apx
when the driver went to install
i cancelled "skip searching windows update"
in usb controllers an acer picasso boot recovery is listed
AND in Printers and Hardware the APX device is there - i didnt do anything with it at all
I fired up afterOTA but it couldnt see my tab
So I used civs V8 nvflash pckg
tab went into the proper apx mode with the txt displayed
it flashed and now running v8 and cwm 1.7.3
I did this via HC 3.1 win7 32
That worked !!!
I followed your The Chickens Guide to Flashing the bootloader manually after installing the USB driver from the Acer support website. Now I'm back to ICS without having lost any of my data or settings.
A couple of noob questions:
1) Would an ota update from Acer wipe out the newly installed V8 bootloader & Thor 1.7.3 recovery?
2) What's the most reliable way to root ICS?
Thanks so much for your patience with my problem!
FCBelser said:
That worked !!!
I followed your The Chickens Guide to Flashing the bootloader manually after installing the USB driver from the Acer support website. Now I'm back to ICS without having lost any of my data or settings.
A couple of noob questions:
1) Would an ota update from Acer wipe out the newly installed V8 bootloader & Thor 1.7.3 recovery?
2) What's the most reliable way to root ICS?
Thanks so much for your patience with my problem!
Click to expand...
Click to collapse
Oh m8 thats made my day:laugh::laugh::laugh::laugh: rapt for u!!!
So u think it was the drivers??
1) don't know, we haven't recd an ota to find out - but in my experience nothing wipes unless u do! An EUU may do it or an official updaate.zip.
2) icsroot by blackthund3r google it
3) if u install a custom rom you will need to do a full wipe and format via cwm b4 and after flashing this includes Jr internal storage else all sorts of glitches happen.
Your welcome., as I said its been a problem with no real solution, awesome to know it that in the end it finally worked
I'm not sure it is the drivers. I installed Acer USB Driver v1.00.0524 (2011-10-06) from the Acer website. It appears to be the same version installed by AfterOTA. Maybe it's something else in AfterOTA that just gets hung up on a combination of hardware and software that wasn't anticipated? I'm sure gersma couldn't anticipate or check out every combination.
I'll try ICS Root.
Thanks again for all the help.
FCBelser said:
Where can I find timmydeansv4? Google search isn't finding it.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1307539
i have exactly the same problem, issue is that wen ur in APX mode and win7 has detected ur acer recovery driver and when u start your process of ICS rooting OR apxflashing or bootloading whatever the USB driver disconnects and that's the reason why nothing works and its stuck in partiton format or what ever process your in btwn and when you once again in a hurry power off the device and power u the acer recovery driver, its back there but still its stuck nothing goes on... Also even when acer recovery driver is there and you enter any mode then it says device not connected or found...please help
rondlu said:
i have exactly the same problem, issue is that wen ur in APX mode and win7 has detected ur acer recovery driver and when u start your process of ICS rooting OR apxflashing or bootloading whatever the USB driver disconnects and that's the reason why nothing works and its stuck in partiton format or what ever process your in btwn and when you once again in a hurry power off the device and power u the acer recovery driver, its back there but still its stuck nothing goes on... Also even when acer recovery driver is there and you enter any mode then it says device not connected or found...please help
Click to expand...
Click to collapse
If the usb connection is disconnecting here's a few things you can check.
Both sets of drivers are installed. The Acer ones and the android ones.
Try a different usb cable.
Win 64 bit has issues try xp, ,vista or win 7 machine.
If still no joy try civs manual flash or Ubuntu.
Sounds like a driver issue so check those first.
Dibb
Sent from my GT-I9300 using Tapatalk 4 Beta
Thanks so much for the reply the drive i have is Acer USB boot recovery drive and before that Picasso was visible .. there is just one driver how can i get two drives here? i have read many forum and the links they gaved is Just one two drivers, one was Picasso and the other was simple that i mentioned at first but the Device Manager just shows one (Acer USB boot recovery drive)
Three cables are changed but all it happens that it stuck at partition fomating or flashing recovery
Also like to mention that i Used AFTEROTA which shows the status under
Driver - OK - driver installed
USB - ERROR connect usb cable and enable usb debugging
(how can usb debugging be enabled when tablet is totally dead)
In the cpuid guide in my sig there's a download for adb/fast boot drivers. You must have these installed.
Was yr tab running ok before all this?
Sent from my GT-I9300 using Tapatalk 4 Beta
Sorry but i m new to this android and this forum ,i have followed ur link and im confused that which version (honeycomb or ICs was my tab) yes everything was working fine and suddenly the OS and apps started to held and behave abnormal so then i had to turn it off and after that all this happened
I have followed ur link and this is what i see
DRIVERS
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"
i went to ace support and download the honeycomb first version but the adb_fast.zip doesn't have any driver its a program... Kindly suggest where is the other driver
Sir Kindly reply i am waiting for your suggestion.:crying:
Related
I'm trying to Root my Samsung Tab 10.1 and I'm stuck at a step in this thread:
http://forum.xda-developers.com/showthread.php?t=1130574
Section 2 step 14.
I cant get my computer to install the unsigned USB driver.
When I browse I can see it, chooses it, but it wont install.
Instructions say just bypass the errors but I don't even get those.
It just stops the install and gives me nothing.
Any help would be great.
Thanks
Try running the attached utility and remove any Samsung references or references to any other no longer needed usb devices. Then reinstall the Samsung drivers. That's what worked for me.
I installed it on my PC (win7 64bit) yesterday following the same instructions and it loaded fine.
In your Device manager do you see the device as "APX device" with questionmark.
One more thing, try uninstalling the previos one and then reboot the PC and start again.
I used Samsung Kies and it installed the USB drivers.
katlimaal said:
I installed it on my PC (win7 64bit) yesterday following the same instructions and it loaded fine.
In your Device manager do you see the device as "APX device" with questionmark.
One more thing, try uninstalling the previos one and then reboot the PC and start again.
Click to expand...
Click to collapse
I'm on 32bit. Does this matter?
And...
Do you mean to uninstall APX or the NVIDIA Boot Driver?
BobCobb said:
I'm on 32bit. Does this matter?
And...
Do you mean to uninstall APX or the NVIDIA Boot Driver?
Click to expand...
Click to collapse
I don't think 32/64 bit matters.
Yes, uninstall the APX (Nvidia recovery boot driver) and then press the buttons again on Gtab to enter APX mode and connect to PC and reinstall.
I am trying to unroot my Nexus S and relock the boot loader. I've followed multiple guides and tried them on different computers (mac & windows). Every time I am supposed to type in "fastboot oem lock" and every time the command prompt just says waiting for device and nothing happens
I've installed the usb drivers from the android SDK so I'm lost as to why this is happening
I'm running the I9020T on Wind
Fix: Turns out it was just a driver issue, following these instructions got it working for me
Part 1 - Drivers
1 - Download Android SDK
2 - Unzip & launch "SDK Manager.exe"
3 - Cancel the first popup & go to "Available packages" > "Third party Add-ons" > "Google Inc."
4 - Select "Google USB Driver package" & click "Install Selected"
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
6 - (MOD EDIT: Ignore this step for i9020A models) Open "android_winusb.inf" and add the following lines to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
Click to expand...
Click to collapse
as described here [SOLVED] Google Android USB drivers - Nexus S SCLCD GT-i9023 not recognized
7 - Turn Off your SNS
8 - Make sure the SNS is connected to the PC via the USB cable
9 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
It reads LOCK STATE - LOCKED
Open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
10 - Do a right click and select Update Driver Software
11 - Select Brose my computer for driver software
12 - Point it to your Android SDK installation "extras\google\usb_driver" dir
13 - Make sure to CLICK "Let me pick from a list of device drivers on my computer"
14 - Then from the list 3 choices select Android Bootloader Interface
15 - If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Click to expand...
Click to collapse
Turn on usb debug inside the os.
Then do adb reboot bootloader
Once in bootloader do fastboot oem lock
Hope this helps
Sent from my Nexus S 4G using XDA
Unfortunately i've tried that, nothing happens after I enter fastboot lock
Once you unlocked your bootloader you can not lock it again.
Tom Foolery said:
Unfortunately i've tried that, nothing happens after I enter fastboot lock
Click to expand...
Click to collapse
Do you have a custom recovery installed? Did you try a different usb cable?
1. connect the USB cable directly to USB port on the laptop/desktop; dont connect via monitor USB or extension
2. Open device manager and check if the device is detected as ADB; you need to have the drivers installed
3. perform "fastboot oem lock"
or
Follow the step by step instructions here
zonesan said:
Once you unlocked your bootloader you can not lock it again.
Click to expand...
Click to collapse
Not true, i've done it...as have many others...
gullu101 said:
Not true, i've done it...as have many others...
Click to expand...
Click to collapse
Thanks very much, I always thought we can't lock back the bootloader.
gsrdemon said:
1. connect the USB cable directly to USB port on the laptop/desktop; dont connect via monitor USB or extension
2. Open device manager and check if the device is detected as ADB; you need to have the drivers installed
3. perform "fastboot oem lock"
Click to expand...
Click to collapse
I've tried these steps and I used the guide from nexusshacks but it didn't work.
Do you have a custom recovery installed? Did you try a different usb cable?
Click to expand...
Click to collapse
Although it probably didn't work because before I started the tutorial I installed a ROM which removed Clockwork recovery. I'm going to reroot my phone and try again from the beginning.
Edit: wait that's a lie, I did this a week ago so I'm not 100% sure what I did now, but I'm pretty sure I used the ROM from the guide
I've tried flashing a new recovery but I get the same "waiting for device" message
This makes me think it's a usb issue. I've been having usb issues for a while now, I've tried different cords and different computers. Is there any options I have left.
EDIT: Now I'm almost 100% sure the only thing standing in my way is the USB problems.
Try installing pdanet and using their drivers. Although i doubt this will work as im almost sure that the fastboot drivers arent the same as the adb drivers. Try disconnecting ng and reconnecting your phone on usb once you boot into bootloader.
Sent from my Nexus S 4G using XDA
Greetings all
Apologies in advance for being a total noob, but I have looked all over the place and not seen a solution to the following:
Having recently replaced my Spica with an S II, I thought I'd try rooting/flashing my old phone.
1) With USB debugging enabled, the device is visible in Keis. I'm using 32-bit Win 7 and everything looks correct under Device Manager. When I turn off Keis and try switching to Odin (v4.03), the phone isn't detected and it seemingly fails to install drivers. Device Manager shows unhappy "SAMSUNG Android USB Modem" and "SAMSUNG Android USB Composite Device". I tried using NPS and that basically said go away, I'm too old. I can run a repair in Keis and it's OK until I fire up Odin, which kinda puts me into a faulty driver loop.
2) If I'm understanding this correctly, I need JC3 and above, in order to move to Froyo and above using LeshaK's 2,2 kernel.My current firmware states that it's 2.1 update 1 and the baseband is I570EXXJC1.
Any ideas please on getting the USB talking happily? (Yes, I have tried different ports etc). Also would I need to "flash up" to the later 2.1 and then go from there? The JC3 has me a little confused as the closest thing I see to this is the baseband version.
Many thanks to everyone who may be able to decipher my probs and come back with suggestions.
Doood Bear said:
Any ideas please on getting the USB talking happily?
Click to expand...
Click to collapse
Once you have installed Kies (so Samsung drivers are present on your computer), you need to connect the phone in download mode.
If I'm not wrong, with the the phone powered off and the USB unplugged, press Vol down + Camera + Power, the phone will start on download mode, then you can plug your USB (to both, PC and phone), and you should see it deteceted in ODIN (a COM port is assigned to it).
Once you flash Leshak's 2.2, you can apply other updates (even gingerbread alphas) from recovery menu (Vol down + Hung up + Power).
Hope this helps.
Do not hesitate to ask further questions if needed.
Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!
Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program
Thanks for the info!
I am away until tomorrow evening. I will try it then.
Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!
it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver
Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.
Ok so I figured this is my MAIN problem not being able to flash my Acer A500 and not being able to put a custom bootloader and recovery on it. My computer all together cant recognize my Acer ONLY when its in APX mode! My Acer IS ROOTED as well. My computer will recognize it normaly when its on and plugged i and i can transfer files and what not bewteen my computer and the Acer. But once I put it in APX mode thats when things go down hill! My computer installed a driver called "Acer Bootloader-Recovery" driver the first time i put it in APX mode. But still wont seem to recognize it! BUT!! I can go into my "Devices and Printers" and their it shows i have an "APX" device connected and its under "Unspificed" devices. So no matter WHAT program I use to flash it or install a custom recovery/bootloader, it can NEVER find my Acer! Even when i try to do an EUU to fully wipe the thing back to HC it STILL wont recognize my Tablet!!!! Its SO FRUSTRATING.... since to do anything with my tablet it needs to be in APX mode....I have ALL drivers installed. I got em off the website and downloaded the "HC 3.0.2" drivers (since they dont have any drivers for my ICS 4.0.3v).... So can anyone help me on this? Ive tried almost EVERYTHING i can in the book to get this thing to flash and recognize my Acer, but just wont.....heres ALL my tablet info if this helps at all:
Tablet Serial : 12713752215
Tablet Cpuid : 037C61C9408103D7
Tablet Sbk : 0xE4531F00 0x18070000 0xF74EE402 0x11DE2003
Android Build : Acer_AV041_A500_1.033.00_PA_CUS1
Bootloader : 0.03.12-ICS
Not even the Babsector.rar file will recognize it! If anyone could help in anyway possible please do so! Im at my last resort and i really cant think of anything else to do to it....