Database Users

[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A)

Hi all,
i've recently bought a Nexus S which is a non-US/UK (GT-i9020) version having a SC-LCD screen (GT-i9023).
Which is not, sadly, the only difference...
MOD EDIT: This tutorial also applies to AT&T/Rogers/Telus variants of the Nexus S with SAMOLED screen (i9020A)
This tutorial is based on AllGamer's [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020 only).
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​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​
Part 2 - Unlock
1 - Open a command prompt go to run & type "CMD" & hit enter
2 - Switch to the directory where you unzipped the Android SDK & go to "tools"
3 - Type "fastboot oem unlock" & hit enter
Then you will get thisfastboot oem unlock
...​Selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
4 - Use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done... OKAY [435.433s]
finished. total time: 435.433s​Now back on this screen you should read
LOCK STATE - UNLOCKED​
Part 3 - Recovery
1 - Download the ClockworkMod recovery image (for i9020A models, use this i9023 recovery image too!) 3024v3-i9023.img from [MOD][RECOVERY]Clockwork 3.0.2.4 New wipe & confirm menus!! i9023 & i9020 versions
2 - Save it to the Android SDK "tools" dir
3 - Open a command prompt go to run & type "CMD" & hit enter
4 - Switch to the directory where you unzipped the Android SDK & go to "tools"
5 - Then type "fastboot flash recovery 3024v3-i9023.img" & hit enter
You should get something like this, if not your image is corrupted, download it again
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s​6 - Then back on the SNS select Power Off (Reboot also works)​
Part 4 - Root
1 - Power ON the SNS
2 - Download su-2.3.6.1-ef-signed.zip from [APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]
3 - Save it to the Android SDK "platform-tools" dir
4 - Open a command prompt go to run & type "CMD" & hit enter
5 - Switch to the directory where you unzipped the Android SDK & go to "platform-tools"
6 - Type "adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip" & hit enter
7 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
8 - Select "Recovery
9 - Then it should boot into this screen, if not then repeat the steps to download the image
10 - Select "Install ZIP from sdcard" (power button to apply)
11 - Select "Choose ZIP from sdcard" (power button to apply)
12 - Select su-2.3.6.1-ef-signed.zip (power button to apply)
13 - Select "Yes - su-2.3.6.1-ef-signed.zip"
Should says
Install from sdcard complete​15 - select go back
16 - select reboot​
You're now free to install the ROM you want.
Have fun, take care !
Credits goes to AllGamer & afilopou

I was heading through this toturial and many others present in the SNS forum. There seems to be some confusion regarding rooting && flash custom roms.
Being rooted does not imply that we can flash new roms. For that we need custom recovery. In several phones, we could only had a custom recovery if the phone was rooted. In SNS, we just need an unlocked bootloader and a compatible recovery. No root is needed IMHO.
Also, in this guide, as in several others, there isn't said anywhere that the custom recovery will be reverted by the system as soon it finishes booting the stock rom. I think it should be clear that we need to remove/rename the script that does that.
Still... Thanks.

Brilliant. Thanks!

this is a very nice, but i'll suggest including the modifications instructions in this topic as well, instead of just linking it to the other topic

DoomFragger said:
I was heading through this toturial and many others present in the SNS forum. There seems to be some confusion regarding rooting && flash custom roms.
Being rooted does not imply that we can flash new roms. For that we need custom recovery. In several phones, we could only had a custom recovery if the phone was rooted. In SNS, we just need an unlocked bootloader and a compatible recovery. No root is needed IMHO.
Click to expand...
Click to collapse
This tutorial is based on AllGamer's one concerning the GT-i9020.
Im very new to Android customisation, i've just followed some toturials i've found trying to make them works, so it may be inconsistent.
As far as i know, i got some problem using the RomManager application that was asking for superuser rights in order to install new rom. This application placed a superuser-xxx-signed.zip at the root of the sdcard, but install on my SNS SCLCD never worked.
Consider using the manual way, not the RomManager application, will be more straiforward.
May be all these steps are not mandatory, but in the end you'll be able to be able to nistall new rom.
Consider it as a global package for customisation.
DoomFragger said:
Also, in this guide, as in several others, there isn't said anywhere that the custom recovery will be reverted by the system as soon it finishes booting the stock rom. I think it should be clear that we need to remove/rename the script that does that.
Still... Thanks.
Click to expand...
Click to collapse
Never noticed that. ClockworkMod recovery has ever stayed in place, even after rebooting the stock rom many times.
Cheers !

AllGamer said:
this is a very nice, but i'll suggest including the modifications instructions in this topic as well, instead of just linking it to the other topic
Click to expand...
Click to collapse
By the way AllGamer, i apologize for the non-agreed use of your tutorial, i was all in the thing at that time, just thinking about to end up with my cyanogen rom.
It works now, thanks to you. MIUI this evening

hi
i also have the 9023 and tried your guide. but im am stuck at #14 because it dont find the android bootloader interface entry, there are just three adb interface driver in this list. i also cleared the driver registry with usbdeview before.
adb driver is installed and i tried to unlock the bootloader but fastboot dont recognice the phone.
and i tried it on 2 different pcs, one with win xp and one with win7, same problem on both systems
ugrubni

When I unlock my bootloader, I've downloaded the "Google USB Driver package" and the "Galaxy Tab by Samsung Electronics".
I haven't edited any .inf file. Those were the instructions I followed from this article.

ok, finally i have bootloader interface installed with edited .inf installed on win7.
i tried to unlock with fastboot but it just does nothing. my nexus says
usb control init
usb control init end
standard_set_configuration
anyone an idea?
ugrubni

Before I root my Nexus S, i got some questions to ask.
Can I "unroot" my nexus s to stock if I do this?
What kind of roms are there available other than CM7 mod?

Hi all,
Followed advice above, had to reinstall SDK as did not have an adpfile. SDK all fine now, but am stuck on fastboot not recognising the phone - stays on waiting for device, did a search on xda but brought up other phones and nothing that could helped me...
updated: adb devices works fine, it sees the phone with adb, but just not with fastboot?
another update:
tried usbdeview to uninstall drivers
re-installed them again, no such luck.. annoyingly adb sees the nexus but fastboot does not..
would appreciate any more ideas?

i finally got it work
fastboot also dont recognized my phone
what i did is:
go to android-sdk/platform-tools folder and copy adbwinapi.dll and adbwinusbapi.dll to /tools folder where fastboot also is located and it worked.
cheerz, ugrubni

kursk said:
This tutorial is based on AllGamer's one concerning the GT-i9020.
Im very new to Android customisation, i've just followed some toturials i've found trying to make them works, so it may be inconsistent.
As far as i know, i got some problem using the RomManager application that was asking for superuser rights in order to install new rom. This application placed a superuser-xxx-signed.zip at the root of the sdcard, but install on my SNS SCLCD never worked.
Consider using the manual way, not the RomManager application, will be more straiforward.
May be all these steps are not mandatory, but in the end you'll be able to be able to nistall new rom.
Consider it as a global package for customisation.
Never noticed that. ClockworkMod recovery has ever stayed in place, even after rebooting the stock rom many times.
Cheers !
Click to expand...
Click to collapse
That's right.The script which removes Cwm recovery after reboot does not exist in i9023(slcd)
Sent from my Desire HD using Tapatalk

hi Guys
sorry about the noob question,
but actually I have a problem installing JDK,
Android SDK always give me back "JDK SE development Kit (JDK) not found."
But I did install several times...,
SDK still not recognise it.
what should I do?
thx
Cheers

Colombus said:
hi Guys
sorry about the noob question,
but actually I have a problem installing JDK,
Android SDK always give me back "JDK SE development Kit (JDK) not found."
But I did install several times...,
SDK still not recognise it.
what should I do?
thx
Cheers
Click to expand...
Click to collapse
Did you try to install eclipse and start sdk from eclipse?
http://www.eclipse.org/downloads/ (download this one Eclipse IDE for Java Developers)
and then read this one
http://developer.android.com/sdk/eclipse-adt.html#installing
Had as well problems, but now i am using eclipse in order to start sdk

thx now it's working, all good, with it, and able to setting up
cheers

thanks ugrubni,
worked like a charm...
now have zeroxs on my nexus sorted!

Hey guys,
Im stuck at part 2 "Unlock", when i run cmd and type fastboot oem unlock i get an error saying fastboot is not recognized as an in or external command, program or batchfile.
I then uninstalled all usb junk with USBDeview 32/64, i didnt quite know what to uninstall, so i just uninstalled everything, maybe a bit to rigorous?
Im in no way a tech wonder and this is the very first phone i tried to root, so if you would be as detailed as possible i would really apreciate that!
hope you guys can help me out?

Fmbl said:
Hey guys,
Im stuck at part 2 "Unlock", when i run cmd and type fastboot oem unlock i get an error saying fastboot is not recognized as an in or external command, program or batchfile.
I then uninstalled all usb junk with USBDeview 32/64, i didnt quite know what to uninstall, so i just uninstalled everything, maybe a bit to rigorous?
Im in no way a tech wonder and this is the very first phone i tried to root, so if you would be as detailed as possible i would really apreciate that!
hope you guys can help me out?
Click to expand...
Click to collapse
Ok lets try to solve it.
First things first, uninstall everything related to sdk and do the part 1 from scratch.Then go to androidsdk/tools folder and check if you have a file named "fastboot".If yes (normally yes because after updating android sdk manager the "fastboot" file must be there.Also make sure you downloaded the google usb driver) then go to androidsdk/platform-tools and find the two files AdbWinApi.dll and AdbWinUsbApi.dll .Copy-paste them to androidsdk/tools .Restart your pc and try the second part.
Hope to help

afilopou said:
Ok lets try to solve it.
First things first, uninstall everything related to sdk and do the part 1 from scratch.Then go to androidsdk/tools folder and check if you have a file named "fastboot".If yes (normally yes because after updating android sdk manager the "fastboot" file must be there.Also make sure you downloaded the google usb driver) then go to androidsdk/platform-tools and find the two files AdbWinApi.dll and AdbWinUsbApi.dll .Copy-paste them to androidsdk/tools .Restart your pc and try the second part.
Hope to help
Click to expand...
Click to collapse
Thnx for your reply,
I followd everything you said, but fastboot is still not recognized, the above error message still aplies!
I do however dont get step 2 of part 2, maybe noobish but how do i get to that directory in CMD?
hmmm what to try next?

[GUIDE] Where's my CPU ID at, why you need adb and whats fastboot!!

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?

[Q] Can't install apks despite my device is NOT adb offline.

Ok I've been following every step some posts follow in order to upgrade every Android SDK component to the last version (adb, sdk manager, avd manager, usb driver, web driver and ALMOST EVERYTHING fetched in the sdk manager). I have my Nexus 4 on stock 4.2.2 (JDQ39) working like a charm with its USB driver with my PC, the debugging is on, also the unknown sources option (if any), the phone is properly linked with the "adb fingerprint protection" thing (can't remember the correct name), and last I can see my Nexus 4 detected on adb devices command AND STILL I can't install a sole apk, in this case I'm using Android Commander 0.7.9.11 and nothing, I've tried with Droid Explorer or even Moborobo and nothing.
However in my cousin's laptop I can successfully install apps.
I thought it must be something wrong or corrupted with my OS, so I reinstalled Windows 8 (x64) and take care about all the drivers and everything mentioned above and still... I get the same, so I'm running desperate here.
Maybe it's something simple, I just need someone to help me.
Sorry if I writed so much... I only did it to avoid Android's ABC related questions.
Thanks in advance for your time.
Best regards.

Does "adb install path/to/app.apk" work?

chromium96 said:
Does "adb install path/to/app.apk" work?
Click to expand...
Click to collapse
When I do it I get this:
Code:
C:\sdk\platform-tools>adb install C:\mxvideoplayer.apk
2752 KB/s (6930955 bytes in 2.458s)
pkg: /data/local/tmp/mxvideoplayer.apk
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]

How to get ADB interface for Lenovo IdeaPad S2110AF

Since I bought the Lenovo IdeaPad S2110AF from NY, I was searching for how to root the device and I found this thread http://forum.xda-developers.com/showthread.php?t=1896899.
But I was unable to get the ADB interface on Windows 7 x64 laptop and I found the same problem is there for most of the users. Finally last night, I could fix this issue and root my tablet. How I did it:
Download the "S2110-Root.zip" file through the above URL. and extract it to a folder.
1. Enable USB debugging under Settings-> Developer options.
2. Connect tab to computer using the provided data cable.
3. The driver for OTP will be installed in Windows. But the ADB interface may not be installed automatically.
4. Go to Device Manager (Right click My Computer and Properties, the click Device Manager).
5. You can see Other Devices-> Android
6. Right click on that and click Update driver software.
7. Click "browse my computer for driver software"
8. Click "Let me pick from a list of device drivers on my computer" rather than browsing and selecting the driver folder.
9. Click Next and then click "Have Disk" .
10. Then choose the drivers folder and the inf file (in extracted files) - \S2110-Root\Drivers\android_winusb.inf
11. Then select the ADB interface and click OK.
12. Ignore any warning message (like not signed)
That is it. Now you got an ADB interface. You will see as Samsung device on the device manager, never mind it.
Now you got the ADB interface and follow instruction to root through the URL.
Note: I am not sure is this a right place, but I just wanted to post this, it may help someone

I had some problems getting root to work.
I found out to use root with adb the display must be on and unlocked.
I started to work on recovery.img, finally I extracted it and took a look on it. Seems not too hard to get it modified and after do some play with custom roms.

Diagnosing USB Driver and ADB issues in Windows

Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit

Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse