Database Users

Help!! messed up updating cyanogenmod! Bricked??

I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.

Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492

Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??

What!
can you get in the recovery?

Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.

Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!

Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?

Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow

Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?

icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map

OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!

icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window

Using the RUU Issues

Hero had a hardware fault w/ the SD slot(good thing too! I dropped it last week and had a bit of rub on the top left that was bothering the hell out of me)
Was going to go get it replaced tonight, but for some damn reason the RUU won't work.
I have the latest RUU(1.56?)
Tried with phone w/ and without USB debugging
Went into fastboot mode(which made W7 install drivers for Android 1.0?) yet the RUU still won't recognize the phone.
I'm not computer illiterate, I'm just having problems with this damn RUU.
Halp?

What's the error you're getting?

The RUU basically says like
"Finding your Android Device" for about 30 seconds then says it cannot find it.

error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"

thedudejdog said:
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
Click to expand...
Click to collapse
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.

intx said:
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
Click to expand...
Click to collapse
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.

thedudejdog said:
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
Click to expand...
Click to collapse
Why wouldn't I want help?

ok try this.
type "adb devices"
if that sees your phone type reboot into fastboot then type "fastboot devices"
if that sees your phone then run the ruu

adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<

intx said:
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
Click to expand...
Click to collapse
have you tried this?
realmrealm said:
For some of the people running into problems with Windows 7 you may want to try:
1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"
2. I believe there is a tab called "Compatibility" or something, click on it.
3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there
4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)
5. near the bottom should be a place to check "run as administrator" check that.
6. click "ok" and then try running the program again.
I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.
I also don't even know if this will work, but it's definitely worth a shot.
-AndyS-
Click to expand...
Click to collapse

or this?
10 char...
flipzmode said:
Possible resolutions would be:
1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.
2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command
3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
Click to expand...
Click to collapse
or this?
crunchybutternut said:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
Click to expand...
Click to collapse

Tried the first two things, neither helped
I figured out part of the problem though. I had to dig up some 64 bit drivers.
I got the RUU to recognize my phone and it sends it to the bootloader and gets stuck on Waiting for bootloader then errors 170 out.
I'll try copying the files over now.

Replacing those 3 files did the trick!
Thanks

intx said:
Replacing those 3 files did the trick!
Thanks
Click to expand...
Click to collapse
no problem, when i did it i tried all of those steps at once, so i wasn't sure which one fixed it for me. so now (in theory) it should work for you on that machine every time.

wont run and get "ARUGlobal.dll can not be found" even tho im looking right at it....

fastboot help?

in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...

Try this
shug24 said:
in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...
Click to expand...
Click to collapse
Try resetting your phone and your computer then try again

like a reboot? that hasn't helped yet...

yeah exactly- hmmm try re-installing the drivers

where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.

shug24 said:
where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.
Click to expand...
Click to collapse
you have to get the drivers through android sdk
(with phone usb connected)
device manager
Android Device
right click
update drivers
click browse my computer then next and then click install
if it doesnt give you that option let me know

okay I am having problems there. First, it doesn't recognize an android device, it says unknown device and it won't take any drivers I have followed the pdanet steps, and I have tried the galaxy s drivers with no luck...

okay there is your problem now we are getting somewhere,
do you have android sdk
if yes do you know how to install packages

I have tried this on two 64bit machines and one x86 the one I am on now.. and can't get it to work. I feel like a total newb but this is not a new thing to me ( rooting/unlocking etc) I have had a g1 since the release, then a nexus one since release and just got the nexus s yesterday and have struggled with this one..

what do you mean by install packages, and I appreciate your help

okay no problem it took me a bit to figure it out too.....there arent samsung drivers for this phone they come straight from google through android sdk. im assuming you have it and im going to assume its in this directory if you did eveything right with your n1
c:/androidsdk
in the directory there is a file called SDK setup.exe open it
once it opens do yourself a favor and click cancel dont ask why just do it
now thats out of the way there is 5 options on the left pane of the android sdk window click settings.
then at the bottom of that window is a box under misc. by force http..make sure its checked
then on the left pane goto then available packages
click them all to save yourself trouble and then on the bottom right install packages
let me know when thats done

doing it now - not sure if this helps or not but I had done this last night on a different pc - unfortunately that is at home and I am on my work laptop right now.
and... done.

okay now go back into the device manager and right click on unknown device
update/re-install/install whichever it says then when it asks search or browse
BROWSE
c:/androidsdk/googleusb driver
and watch the magic happen

okay a few things: first it says e: now for the phone under portable devices second, there is no google usb drivers, so I tried it just under the AndroidSDK folder and all the following and it said:
The best driver software for your device is already installed. WPD Filesystem Volume Driver
thoughts?

go back to the sdk setup.exe expand the boxes under available packages and read me what you see

is this where you are asking me to display from? http://www.twitpic.com/3gwnus
OR here: http://www.twitpic.com/3gwo9i

let me save you the trouble
unzip cut and paste to your androidsdk folder
http://www.multiupload.com/Y3T61793BP

yes and paste the file i sent you into that folder

now it still says the best driver is already installed...

uninstall your phone

[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] Help rooting N7

Hello..I am a complete n00bie here
I am trying to root and unlock the bootloader of my N7 and I am having a problem:
http://forum.xda-developers.com/showpost.php?p=42745327&postcount=377
As per the method..I downloaded the files on my desktop and now trying to move those over to /sdcard..but having device not found error..
some help here pls..

rockstar283 said:
Hello..I am a complete n00bie here
I am trying to root and unlock the bootloader of my N7 and I am having a problem:
http://forum.xda-developers.com/showpost.php?p=42745327&postcount=377
As per the method..I downloaded the files on my desktop and now trying to move those over to /sdcard..but having device not found error..
some help here pls..
Click to expand...
Click to collapse
I responded in the other thread let me know if that helps otherwise we can take this to pms and I will try to help you that way.

While following this tutorial..
LINK
I reach successfully till 'adb push supersu.zip /sdcard/'
but when I try to install zip from sdcard..device errors out saying 'Can't mount sdcard'
I tried 'adb push supersu.zip /sdcard/0/' but I get same error
any idea what the problem might be??

underwaterjr said:
Sorry I got tied up. If it doesn't list any devices you don't have adb set up yet. First go into settings on your device, you have to enable developer options by going into about tablet and scroll down to bottom and tap build number about seven times, it will tell you when your getting close. Then go into developer options and enable android debugging. Now plug your tablet into computer and you should get a pop up asking you if this computer is ok for debugging or something like that so enable it or say yes what ever the option is. Sorry doing this from memory so can't tell you exactly verbatim what those popup prompts say. Now for debugging on the computer end. I don't know how long you've had the sdk on your computer so just make sure its up to date by opening the sdk manager and check for any updates. In order for adb to work with 4.2.2 you need the latest tools. Ok so with all that done now open a cmd window and navigate to your platform-tools folder and try adb devices again. you should get a read out of some numbers after that. Let me know if that works and we can proceed. Good luck!
Click to expand...
Click to collapse
This helped me..Thank you underwaterjr:laugh: