Related
Now I know your first thought “I bet this tool didn’t even use Search like the rest of the shlubs on here”. Well you are mistaken. I have not only searched xda but even tried Google and Yahoo (just in case) as well. I have found numerous posts (like HERE and HERE and many others) with similar situations but haven’t seen a resolution. Here is the rundown:
Running JF’s 1.5 CRB21 ROM
Hard SPL (HSPL10.95.3000)
JF’s 1.43 Recovery Image
SDK 1.5_r1
Fastboot.exe placed in System32
Haykuro’s Updated Drivers placed in System32
Windows XP 2002 SP3
I have been able to flash nandroid backups without issue in the past but adb started intermittently not recognizing my phone when I flashed from JF’s RC33 to JF’s 1.5. I was able to restore a backup once but now adb will not recognize my phone at ALL. Tried different USB plugs and cables with no result. If I mount the phone to view the SD card via Windows Explorer it shows as “HTC Dream Composite ADB Interface” in Device Manager. However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order. I have deleted my SDK and drivers and re-downloaded/installed them and STILL cannot get adb to connect. It has to be something simple I am missing here right? Any idea why this would have worked without issue in the past and now not at all? Could it have been a Windows Security update? (That's about the only thing I can thing that has changed other than the newer ROM)
Thank you for your help.
Did you update you USB Drivers or try reloading them?
Also.... Settings > Applications > Development > USB debugging has to be checked....
and stop being a tool.
nah im jk.
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
gPhunk said:
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Click to expand...
Click to collapse
Repent .. Repent..
Did reloading the USB Driver work?.. Did for me =)
billc.cn said:
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
Click to expand...
Click to collapse
How do I know which one to install? (I am running Vista Home Premium 32bit)
Thank you for your help
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
ubernicholi said:
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
Click to expand...
Click to collapse
Thanks man - I was able to install the drivers but am still unable to view my device. It shows as "HTC Dream" in Device Manager but when I run "adb devices" in the command line, it yields a blank list. Further commands (I.e. adb shell) say "cannot find device. Running fastboot commands result in "waiting on device". This happens on both my laptop and my home pc so I am beginning to think it's the phone. Should I have something loaded on the phone? I have USB Debugging checked so that's not it. Any ideas?
possibly the problem is that ADB does not work in Bootloader mode, it is designed to work while the phone is running.
However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order.
Click to expand...
Click to collapse
Yuo are obviously trying this in bootloader mode, underline for emphasis.
try >fastboot devices
see if that shows you your phone
Otherwise try ADB while in the OS already.
Hi guys.
Sorry for this noobish post, but i cannot remember for the life of me on how to install things by using 'adb' - i know there is an option on the phone, but where bouce is it? I used it when rooting, but i just cant find it.
I'm trying to install a new boot image, but when i go into cmd i type "adb remount" and the reply is "device not found"... AndroidSDK is in my C directory.
Another EDIT; I just rebooted my device into the recoverymode, and i didn't see ndroid back up thing, does that mean my phone hasn't actually been rooted... - But my phone is deffently debranded.
Thanks if anyone can help my noobish style.
Slim.
When in recovery mode you must have the driver installed. If you enter 'adb devices' it should give you the serial number of your device, if the driver is installed correctly.
To enter the recovery menu you must run the recovery-windows.bat from modaco if using windows or a similiar file (recovery-linux.sh, recovery-mac.sh) according to your operating system. The file should be run when in recovery-mode or else it returns a whole bunch of errors.
Awesome, thanks mate. Just what i needed! Could i have advice what driver i need to be able to acsess the adb?
I just use the driver supplied in the newest version of ADB.
You can get it here. usb_driver.rar
Or else just install HTC Sync from htc.com. It also has the driver files needed.
Remember to have USB Debuging enabled from the Programs/Development menu.
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!
Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.
You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G
ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
tried your directions again
I have tried them again and they do not work.
Try the usb cable for the droid x. Its a really good one.
if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.
mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G
thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.
I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk
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?
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.