Related
Hi,
I have been messing with this for a few weeks now.
I have a magic 32B, spl 0004
I don't know how but i got cyanogenmod 4.2.5 on my phone.
But then i tried to use the update app and it fails.
It seems that there are 2 problems.
1. my recovery is still the stock one
2. i just cant seem to get a good connection with my computer.
Every time i try something its waiting for device.
Or with adb devices its an empty list.
i used a windows vista machine and a windows 7 machine
Is there someone who is willing to help me get this done?
I checked threads about, usb drivers, installing adb, installing recovery.img, installing cyanogen.
But there is always a step that just doesn't go according to the manuals.
i was about to give up, but i just really want this to work.
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
justbenjp said:
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
Click to expand...
Click to collapse
I have tried to install a custom recovery, but when i follow the steps i cant seem to connect to my phone via CMD.
When i check the drivers.. i'm not sure its 100% correct.
I have installed the once before.
and now he doesn't ask me for the drivers anymore.
but neither do i see it in the devicemanager, the way its being described in the manuals.
just something else involving android, but not ADB
i have tried to follow the manual, and threats about how to get the driver right..
but with this, i also have had problems with the steps..
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
justbenjp said:
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
Click to expand...
Click to collapse
I have done this..
I will try again on a vista machine which i havent used for this yet
anheuer said:
I have done this..
I will try again on a vista machine which i havent used for this yet
Click to expand...
Click to collapse
Great.. it would not install the SDK..
So back on my windows 7 machine..
still getting device not found in CMD - adb devices
connected with usb debugging on..
cant see anything in device manager, but the system also doesnt ask for drivers...
I went into fastboot and then it asked me for drivers..
Now i do have
Android phone - Android Bootloader interface
but in any other situation, it does not show anything or ask anything.
I just keep getting device not found...
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
To all devs out there ,im been trying to root the hero for a week now ,ive tried every guide going also the gold card with 10 different sd cards with no luck.the rom what ive got is the release 2.73.405.66 rom.it has the new nboot is thats why i cant flash.is there any way i can wipe all date and software so i will have nothing on the phone and then install an earlier rom, its just an idea as im starting to lose it with this fone.i hope someone can help me or do i have to wait for the official update from htc
with this rom version you need to create a goldcard and downgrade your rom before you can install a custom rom. if you have problems with the goldcard you should be more specific.
waiting for the update doesn't seem like the best idea, because it might take some until a security flaw is found that allows to root the rom when already installed on the phone. if you have the custom recovery image you will be able to install the (pre-rooted) update short time after it was released.
You should be able to use fastboot for this issue.
Search around the forums, (also http://hero.modaco.com) and read about it.
All you need is the fasboot tool, a usb cable and the "debugging mode" switched on at ur phone...
everytime i create the gold card and try to downgrade the rom it states boot error 140.i follow the guides very indepth i get the serial number from the sdcard than i reverse the string and then replace the first two numbers or letters with 2 zeros how can you tell when the goldcard is on the sdcard.when i replace the sdcard back in sdcard reader it states that the folder is empty.im quite clued up on winmo but android is giving me a headache
wouldn't the fastboot give you the "remote: not allowed" error?
anyway, you can try:
start your phone by holding back and pushing power, you should see three skating androids. put recovery image in the folder where your fastboot.exe is, open terminal and go to that folder and type:
Code:
fastboot boot recovery-RA-hero-v1.5.3.1.img
if that works report back.
for the goldcard i can't help, never did it.
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
rednose30 said:
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
Click to expand...
Click to collapse
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
mjames_84 said:
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
Click to expand...
Click to collapse
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
TastyBurger said:
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
Click to expand...
Click to collapse
Hi
I have tried making a goldcard, and installed via. the RUU shown here.. 405.5 .. but then I tried using Flashrec to get another recovery image, it failed making the first step...
So is my phone rooted or did something go wrong ?
the phone is still unfortunately not rooted. I would've tried the fastboot method
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
nicknyhk said:
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
Click to expand...
Click to collapse
Very similar story. I did make a goldcard but hadn't got as far as finding out how to extract the update.zip out of the RUU exe, in order to use it. I tried running the RUU to see what would happen & my Hero downgraded.
Sorry to be a hassle, but I just can't figure this out!!
I've rooted my phone with the "new clarified method" thread, gotten to the clockwork mod and everything, but once I've done that I just cannot get the Unrevoked 2 to work. I've tried it on Windows 7, xp, and osx, and nothing seems to work! The main issue I'm getting is that it'll do the whole process, and then I think it says "reboot to recovery" and then I just get that old phone with a red triangle error. What could I possibly be doing wrong??? It can't be driver issues, because doesn't OSX do that automatically?
I had a similar issue on windows 7 and a simple pc reboot seemed to work for me.
Nope, still no luck. Am I supposed to put these Reflash files on the phone somewhere? I just feel like I'm missing some big step or something. Why is there no good tutorial on this process yet?
Oh my god I think I'm going to go insane! Please someone, point me in the right direction! I have done this hundreds of times now, I'm gonna die. All I can get is "Done!" and then my phone is showing me a big dumb red exclamation point triangle thingy. What am I doing wrong??????
Was I supposed to do something once I first reached the clockwork on my initial root? Cuz all I did was reboot to OS. I don't know if anybody can tell, but I'm kinda desperate. hah
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
larry996 said:
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
Click to expand...
Click to collapse
I was having the same problem also until I ran reflash.exe and the command prompt both as admin. I also reran Android SDK installing all of the updates. After plugging in the phone, the SDK picked up two more updates, one of which was USB drivers. Once I did that, things seemed to have worked.
Use attn1's method. The clarified method didnt work for me properly.
I assume you never flashed a rooted rom after reaching clockwork mod. If not the phone is not yet rooted. You have to get back to clockwork recovery and flash a rooted rom (either attn1's liberated one or his stock rooted rom). Both found in his liberated thread. Then set up all the drivers for unrevoked and run it. It should work then.
When my phone is just sitting in bootloader, it is not recognized by adb devices.
You have to go through the whole loop process again booting your phone into recovery and connecting the usb cable.
gdeadfan said:
When my phone is just sitting in bootloader, it is not recognized by adb devices.
Click to expand...
Click to collapse
Thats not good, try reformatting your sd card on your pc with an external reader not with your phone and try again. I'm almost certain it needs to be recognized by adb devices when in bootloader.
Just managed to install the Liberated beta ROM, but now unrevoked can't even get past superuser privelages. it's not popping up anymore
Nevermind, it gets past superuser now, but now it just says "waiting for reboot" and completely reboots the phone to the point at which i can use it regularly
Have you installed the hboot drivers?
Re-ran unrevoked?
Edit: Does it reach "done!"?
Yes, yes, and yes. And my phone just keeps getting to the red triangle. doesn't make any sense to me! And at this point, I'm positive I have no drivers getting in the way like Sync etc., and I'm sure HBoot is installed correctly.
Go to the android market and download titanium backup. It requires root so if it installs we know that you are at least rooted.
Try this, because I had the same problem. Go into device manager with Revoked2 says waiting for reboot. Look under devices above my computer or below cant remember and right click uninstall and remove the android device. reboot your computer then see if it installs are does it automatically, if not don't do anything just plug the phone in and get to hboot/ red triangle screen, then try revoked2 again. This finally got loop to read my device then when I got to clockwork I loaded "liberated rom"
Screw revoked2, just get to clockwork recovery and have liberated rom on your SD card ready to go. Then after install I ran revoked2 for clockwork mod.
Good Luck
Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
ssvNormandy said:
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
Click to expand...
Click to collapse
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
9918
Moscow Desire said:
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
Click to expand...
Click to collapse
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
ssvNormandy said:
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
Click to expand...
Click to collapse
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Moscow Desire said:
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Click to expand...
Click to collapse
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
ssvNormandy said:
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
Click to expand...
Click to collapse
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Moscow Desire said:
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Click to expand...
Click to collapse
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
ssvNormandy said:
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
Click to expand...
Click to collapse
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Moscow Desire said:
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Click to expand...
Click to collapse
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
ssvNormandy said:
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
Click to expand...
Click to collapse
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Moscow Desire said:
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Click to expand...
Click to collapse
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
ssvNormandy said:
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
Click to expand...
Click to collapse
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Moscow Desire said:
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Click to expand...
Click to collapse
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
ssvNormandy said:
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
Click to expand...
Click to collapse
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Moscow Desire said:
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Click to expand...
Click to collapse
blackthunder's tool just WILL NOT RUN on the tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
ssvNormandy said:
blackthunder's tool just WILL NOT RUN on my tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
Click to expand...
Click to collapse
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Moscow Desire said:
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Click to expand...
Click to collapse
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
ssvNormandy said:
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
Click to expand...
Click to collapse
Yep, same issue with me. I'm stuck on 3.2 HC
Well, it's a secondary tablet anyhow.
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
ssvNormandy said:
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
Click to expand...
Click to collapse
Yeah, and a little bit of knowledge :laugh::laugh::laugh: (maybe too much)
Am glad I could help out!! :good: