Hi,
Right, my A100 kept failing on auto update to new ICS with update failed. No ideas why so I manually updated using the update.zip method to ver 1.012. All working fine on ICS.
My two questions are :-
1) Is there a very easy way to update to ver 1.014 without losing anything on the tablet?
2) rooting. well, i'm following the method by zeronull (full root for a100 ics simple method) and it keeps failing at waiting for device. (the daemon method).
The tablet is accesible from windows fine so cables/drivers fine. The driver version is ver 1.000 as from acer website. I've followed all of the tips on the thread in developers forum. so.......
My tab details are :
Android - 4.0.3
Kernel - 2.6.39.4+
Image Version - Acer_AV041_A100_RV01RC01_WW_GEN1
Build number - Acer_AV041_A100_1.012.00_WW_GEN1
Image P/N - FM.S18A0.00D
Thanks
Download the stock ROM 1.014 from development section.
The method is the same (just put update.zip on the external_sd card), if you don't make factory data reset you will not loose your information.
For the rooting ... do you have 'check' on USB debugging?
yes, usb debugging is checked. (it sets it to that automatically tho)
ok, updated to version 1.014 all fine.
Now when I run 'runit-win' for ICS rooting i get :-
waiting for connect device
*daemon not running. starting it now on port 5037 *
*daemon started successfully*
Thats it..... now nothing.....
filking said:
Thats it..... now nothing.....
Click to expand...
Click to collapse
It's nothing because,the adb still waiting for device.Go through cmd to the ICS_rooting folder (from where you execute install-win.bat) and type : adb devices - You must see some number,if not you don't have the correct drivers or don't have USB debugging selected in settings.
Send from my A100
went thru cmd, the adb shows no devices at all.
debugging is def on. The drivers I am using are the ones from the uk and us acer site. redownloaded them and checked update drivers and the comp says the current driver is the latest.
But looking at the device when plugged in it says under driver details :-
Driver Provider - microsoft
driver date - 21/06/2006
Driver Version - 6.1.7600.16385
Now, assuming this is the wrong driver (it's the microsoft windows one), when i try to update driver it says the one i'm using is the best. Tried uninstall tablet, plug it back in, it automatically picks the windows one. grrr
I'm on Win 7 but also tried on vista.
Sorry for being a pain
Manually reload the acer USB driver
I had the same problem until I manually loaded the acer provided USB driver by running the acer driver setup
Sorry, but have you got a link for that Acer driver setup?
got it, thanks
thanks all, I now have up to date ICS and rooted. Thanks for all your help.
Related
Hi guys, hopefully someone can help.
I rooted the phone using unrevoked and now have clockworkmod recovery on the phone. Tonight I tried to connect the phone to the android SDK with no success.
Windows device manager only shows it as an Android Phone. Everytime I try to manually install the SDK usb drivers, it comes up with a message saying drivers aren't available. I have deleted and reinstalled the SDK usb drivers and have also deleted the android phone from the device manager as well as USBDView. Have had no success whatsoever.
How can I get ADB commands working again on the phone?
EDIT - SOLVED - Apparently I had to reinstall HTC Sync and it worked! strange how these things work!
1. I have an SGN2 International version GT-N7100 (bought in HK) from Samsung.
2. I rooted the device using the latest root kit from your site. It worked like a charm!
3. I flash romed to Jellybean 4.2 (N7100XXDLL5_N7100OJVDLL2_N7100XXDLK7_HOME.tar.md5) on Win 7 (again, worked like a charm).
But,the device became "un-rooted." Which - I guess is kinda logical, I suppose.
4. Now, when I send/receive phone calls and messages, the name(s) associated with my contact list do not appear - only the cell number.
This is a MAJOR, MAJOR problem for me.
There are several other minor issues like not automatically connecting to my home wi-fi network; the device would automatically find and connect before. And I would guess that there are other issues that I haven't come across yet.
5a. When I try to "re-root", the root kit stops when it looks for "USB debugging".
5b. When I try to flash the GT-N7100 stock rom (N7100ZSALJ7_N7100OZSALJ7_TGY) using Odin (3-v1.838), Odin cannot see my device (usb driver issue). In Odin there is no yellow, green or blue color that signifies Odin can see my device.
6a. Windows Kies can no longer detect my device (and it seems the latest version of Kies does not allow installing drivers).
So, I uninstalled Kies and downloaded the latest SGN2 usb drivers from XDA. When I install, I get the following error message:
"The MSS InstallWizard cannot install samsung usb driver V1.5.16.0."
6b. It also says the Samsung drivers already exist, but I can't find them.
And even so, shouldn't the installation just replace the existing one(s)?
7. When I connect the phone to Windows I get the following message: "Device driver software was not successfully installed." And then, I see the following list:
USB Composite Device - ready to use
GT-N7100 - ready to use
SAMSUNG_Android - No driver found
CDC Serial - No driver found
8. When I put the phone in "Odin" or download mode (press vol+on-off+home) and plug the phone in it searches for a "Gadget Serial" driver and finds - nothing.
After doing several searches, I found that the Gadget Serial driver is the same as the Samsung mobile usb drivers - which do not work.
… Please, please, please - help a Brutha out. I'm dying ovaheeya!
Try switching on your internet for Windows to look your drivers in the net..
Sent from my GT-N7100 using xda app-developers app
Download and install http://forum.xda-developers.com/showthread.php?t=1923956
gabamoner said:
Try switching on your internet for Windows to look your drivers in the net..
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
… Naaaah, no good, but thanks.
yerebakan said:
Download and install http://forum.xda-developers.com/showthread.php?t=1923956
Click to expand...
Click to collapse
Already done.
1. When I install the drivers via the tool kit, I keep getting the following message:
"The MSS InstallWizard cannot install samsung usb driver V1.5.16.0."
2a.When I look at device manager I see Other devices->Gadget Serial (with an exclamation point "!"). I did all kinds of searches and just come up with with the same usb driver as the toolkit -which doesn't work.
2b.The usb driver installation does say that samsung usb driver already exists, but I can't find it.
… I'm dying here, but thanks for taking time to help.
yerebakan said:
Download and install http://forum.xda-developers.com/showthread.php?t=1923956
Click to expand...
Click to collapse
Already done.
1. When I install the drivers via the tool kit, I keep getting the following message:
"The MSS InstallWizard cannot install samsung usb driver V1.5.16.0."
2a.When I look at device manager I see Other devices->Gadget Serial (with an exclamation point "!"). I did all kinds of searches and just come up with with the same usb driver as the toolkit - which doesn't work.
2b.The usb driver installation does say that samsung usb driver already exists, but I can't find it.
… I'm dying here, but thanks for taking time to help.
same problem
I have exactly the same problem.. I hope we can get some help
You could try to install the drivers with PDAnet : read http://forum.xda-developers.com/showthread.php?t=1983470
or you could try on another PC / another windows session (another user logged in)...
then come back and let us know how it worked
Okay, so the latest Cyanogenmod update went wrong and after a couple of tries I remembered power on and then volume up got me in recovery mode. I needed to flash anyway and wanted to try the android 4.2.2 and choose the OpenSEMC. When I installed it, I noticed that is was poluted with half apps from my previous state, so I made a backup of my SD storage and formatted the whole thing with TeamWin recovery projects 2.4.4. I than found out that this ROM software doesn't support USB mounting as CWM does. I'm now trying to get my rom to my device using ADB sideload, but in W8 as well as Windows XP I can't get my Xperia S driver installed. I've installed PC companion and tried a couple of loose drivers I've found, but in device manager I have an "unknown device" Xperia S, but no way to install the driver. The consequence is that in a command prompt using the command "adb sideload OpenSEMC-OTA-RC0.zip" the results are:
* daemon not running. startng it now on port 5037 *
* daemon started successfullt *
error: device not found.
Stupid me, realised later on that my backup's gone now as well. The drivers I've found all had a name according to the android version, but my problem is that there's absolutely no software on the thing.
Can someone please lend me a hand?
itsMuppet said:
Okay, so the latest Cyanogenmod update went wrong and after a couple of tries I remembered power on and then volume up got me in recovery mode. I needed to flash anyway and wanted to try the android 4.2.2 and choose the OpenSEMC. When I installed it, I noticed that is was poluted with half apps from my previous state, so I made a backup of my SD storage and formatted the whole thing with TeamWin recovery projects 2.4.4. I than found out that this ROM software doesn't support USB mounting as CWM does. I'm now trying to get my rom to my device using ADB sideload, but in W8 as well as Windows XP I can't get my Xperia S driver installed. I've installed PC companion and tried a couple of loose drivers I've found, but in device manager I have an "unknown device" Xperia S, but no way to install the driver. The consequence is that in a command prompt using the command "adb sideload OpenSEMC-OTA-RC0.zip" the results are:
* daemon not running. startng it now on port 5037 *
* daemon started successfullt *
error: device not found.
Stupid me, realised later on that my backup's gone now as well. The drivers I've found all had a name according to the android version, but my problem is that there's absolutely no software on the thing.
Can someone please lend me a hand?
Click to expand...
Click to collapse
Did you try using the driver package that comes with flash tool?
v0ids0ul said:
Did you try using the driver package that comes with flash tool?
Click to expand...
Click to collapse
Yes, the driverpackage contains 3 sets of drivers for an Xperia S:
1. driver for ICS
2. regular driver
3. driver for GB
All drivers contains 2 inf. files: an ADB driver, which can be installed and a rndis driver which fails on Windows 8.
On Windows XP however, all drivers can be installed, but I still get an unknown device Xperia S, that surprises me a bit, because if it's unknown, how come it does know the name.
I had the same problem, and I found a site and solved it. But now, I can't find it! I just found this, Here:
forum.xda-developers.com/showthread.php?t=1583801
Sent from my LT26ii using Tapatalk 4 Beta
This might sound odd but have you tried uninstalling the "unknown device Xperia S" and then reinstalling the drivers?
itsMuppet said:
Okay, so the latest Cyanogenmod update went wrong and after a couple of tries I remembered power on and then volume up got me in recovery mode. I needed to flash anyway and wanted to try the android 4.2.2 and choose the OpenSEMC. When I installed it, I noticed that is was poluted with half apps from my previous state, so I made a backup of my SD storage and formatted the whole thing with TeamWin recovery projects 2.4.4. I than found out that this ROM software doesn't support USB mounting as CWM does. I'm now trying to get my rom to my device using ADB sideload, but in W8 as well as Windows XP I can't get my Xperia S driver installed. I've installed PC companion and tried a couple of loose drivers I've found, but in device manager I have an "unknown device" Xperia S, but no way to install the driver. The consequence is that in a command prompt using the command "adb sideload OpenSEMC-OTA-RC0.zip" the results are:
* daemon not running. startng it now on port 5037 *
* daemon started successfullt *
error: device not found.
Stupid me, realised later on that my backup's gone now as well. The drivers I've found all had a name according to the android version, but my problem is that there's absolutely no software on the thing.
Can someone please lend me a hand?
Click to expand...
Click to collapse
HI,
go to adbdriver.com and install the adb driver while the device is still connected.
Have a good day
i m facing the same problem whenever i connect my Xperia S with PC its Says Unknown Device USB not Recognised till now my Xperia S not connected to PC..
mkarande786 said:
i m facing the same problem whenever i connect my Xperia S with PC its Says Unknown Device USB not Recognised till now my Xperia S not connected to PC..
Click to expand...
Click to collapse
Uninstall the pre installed drivers from the device manager. Then try installing drivers again from flashtool.
Mirhawk said:
Uninstall the pre installed drivers from the device manager. Then try installing drivers again from flashtool.
Click to expand...
Click to collapse
plz read my threat -->> http://forum.xda-developers.com/xperia-s/help/help-help-xperia-s-t2867998
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Silent Assasin said:
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Click to expand...
Click to collapse
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
wizardknight said:
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
Click to expand...
Click to collapse
Thanks for replying. That's the guide I was using. I can't get into fastboot. ADB commands work. I tried to manually install the drivers (On the computer). Windows 7 says my drivers are up to date. I can't move forward out of mini pooploader (funny name by the way). Any ideas would be appreciated...
I meant to say that I found that thread after being stuck in mini poop mode.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
Click to expand...
Click to collapse
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
plrusek said:
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
Click to expand...
Click to collapse
I followed your advice. I let mini pooploader run the blue screen with white letters. Once finished, I removed the battery, placed the battery back in and then plugged usb into computer. I then powered the phone up with the same results. I performed this task 11 times with the same results. No black screen and no win 7 driver install. The computer says unknown device. I have tried to install drivers and computers states the drivers are up to date. I have tried different USB ports. I have attempted to install HTC drivers someone posed in this forum as well as the drivers that come with SDK with negative results. I have tried to uninstall the drivers in hopes that windows would install upon recognizing device with no luck.
Any ideas? I really need to get this working. i have not had a phone for a week now
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Try these steps:
-uninstall previous version of SDK tools from PC
-download latest SDK Tools from HERE
-have a USB 2.0 cable available
-follow these steps to verify connectivity
see if these things help
Unless there is a specific reason you're still on Sept 8.0, I'd take this chance and upgrade to lasts 8.1 factory image.
evanxalmighty said:
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Click to expand...
Click to collapse
I'm just spitballing here but....
With phone plugged in, on your pc, under device manage. When you open it up do you see unknown android device? That driver may need to be updated. Also, USB debugging is on, and the option to transfer files? Is your SDK platform-tools up to date?
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
I haven't seen it with this phone yet, but try changing the USB mode on your phone from the notification; I've had a few phones that refuse to work in specific modes.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
Have you tried a different USB-C-A cable just for the heck of it. May have to factory reset and see if that solves it.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
So your driver is messed up. Did you use the driver below?
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Sent from my taimen using XDA Labs
It won't let me install the driver I get some kind of error when selecting it. I was able to get it to work after plugging it in and out. Now that I updated to 8.1 everything was fine untill I got home. Now it's doing it again. I tried 2 different cables restarted my computer and laptop and can't figure out why it was working fine before without doing anything different.
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
JimSmith94 said:
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
This definitely worked for me -- Thanks for posting!
I am having sort of the same problem. I was on Android 11 on my 2xl, rooted with fast boot boot twrp.Img and installed magisk and super super, all latest. I could not get gaps so I used Android flash tool to attempt to go back stock and it downloaded and flashed it but it is now stuck in loop, I reboot to recovery and it’s stock now and it will not be recognized by adb or fast boot,!0plesase help