Related
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.
-I can't root my phone after upgrading to 2.2!
use this thread and install the newest .zip extract, and you know the rest. this is done from a PC.
-I can't upgrade my phone to 2.2!
If you have KIES, use KIES MINI, found here scroll down and click download, this is a older version, so the first time you install it, it will take a while to get newest one, and it will install the drivers too.
-Unrecognized device on kies mini!
First, make sure you have ALL the drivers, and just to make sure, uninstall kies, and reinstall it, so it re-downloads the drivers. After it downloads the drivers, unconnect your USB if it is already connected, and reboot your computer, try connecting now, this has fixed most issues so far.
-I'm not getting Froyo through OTA
Tmobile has canceled OTA and made it through Samsung's Kies Mini. there might be a OTA later on, but now there isn't.
-Do i need to unroot first before upgrading?
Most likely, yes, or mini won't recognize your device. Be on the safe side and go to stock using ODIN.
-If none of the solutions on installing froyo work, then wait a few days till the devs make it flashable.
P.S. its not that different from the actual unofficial leaked one btw.
also, if there are more questions, i know i missed a bunch i couldn't think of any, include it to the thread, i'll look for a solution and post it here.
-If none of the solutions on installing froyo work, then wait a few days till the devs make it flashable.
Does this mean the developers plan to release an official ROM that can be flashed to the device using CMR? Would the update simply be copied to the SD card and selected from within the CMR interface?
That would be great.
Many Thanks,
I finally did it. Didn't have to unlock, rollback the firmware, ADB, or anything too drastic. So happy.
I used this method here.
http://forum.xda-developers.com/showthread.php?t=1706588
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers. Can download it here if you're as incompetent as me (Under Utilities). Exit out Asus Sync in your system tray before attempting the method above. And I'm probably not the guy to ask for any help if you got problems or questions.
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
I installed OTA RootKeeper afterwards.
Thanks XDA. Thanks sparkym3.
I think you should give yourself more credit.
GJ
thanks man!
-Bang
supersoulfly said:
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers.
Click to expand...
Click to collapse
This works indeed, but you must stop ASUS sync if it's running. If you don't, the version of ADB packaged with ASUS Sync is different from the one in the zip file and you'll get a whole lot of lines with "adb server is out of date, daemon started successfully" which mess with the script.
Once I stopped the Sync thing from systray and verified in task manager, the script ran like a charm.
So, another TF300 with .29 WW rooted, thanks to the people involved in making this possible
all this confused me way too much but luckily for me i had help (well i say help he did it all via teamviewer lol) from thing o doom he is a star
I used this method too on my 29.WW,thx guys
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
jakelikescake123 said:
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
Click to expand...
Click to collapse
Ummmm.....I think I confirmed it, in the first post.
supersoulfly said:
Ummmm.....I think I confirmed it, in the first post.
Click to expand...
Click to collapse
im the idiot
thanks
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
lightiv said:
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
Click to expand...
Click to collapse
May not be the issue, but it's happened to me several times rooting & ROMing phones - plug the cable into a rear USB port that's on the motherboard. The USB ports on the front of the case don't always work for some reason. The front of my case has 6 ports and I can only get reliable phone connections on 2 of them. Down right squirrely!
ID10T Error on My Part
Turn out to be an ID10T error on my part. I had DroidExplorer running from when I rooted my cellphone. I finally ran across a post that made reference to it and killed the process. It took all of 30 seconds to root once I killed the process.
*** SOLVED ***
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Psychlone said:
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Click to expand...
Click to collapse
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
gears177 said:
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
Click to expand...
Click to collapse
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
if your on the honeycomb bootloader simply flash a honeycomb rom and kernel no need to use afterOTA or anything else if i remember correctly
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
dibb_nz said:
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
Click to expand...
Click to collapse
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
gears177 said:
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
Click to expand...
Click to collapse
Yeh 2nd line of my post hc bootloader ics rom, and u correct use 3.01 buggy update,zip or stock update.zip I shoulda been clearer - thanks gears
Thanks guys, I really do appreciate the help, but I'm still having serious issues reverting back to HC.
I feel like an idiot, but I have to say that even though it seems so, I'm actually the owner of a computer repair business, have 28 years experience in PC/Mac repair, and have rooted and modded every android device I've owned (including some for friends as well) - all the way back to the very beginning with the D1. This, however, has thrown me for a loop. NOTHING with this A500 has been this complicated! Everything up to this point has literally been stupid-proof and I've actually been quite impressed at just how easy modding is on the A500...
Anyway...
Here's what's going on and what I've tried today:
I've tried unsuccessfully several times to get ANYTHING working on my laptop, but to no avail. Same story as last night, no progress whatsoever - however, I did note that with CWM 134, I was able to restore an earlier version of ICS 4.03 (Flexreaper R10 I believe) - but it wasn't easy... I ended up restoring the main image and then using parts and pieces (using Advanced Restore) from other saves to finally even get it to boot.
This clearly wasn't getting me anywhere, so I moved the entire operation to another computer - my main rig (also a Win7 x64 - in fact, I don't own a computer that's not Win7 x64)
Now I've got USB driver issues! I can't even install the standard USB drivers from Acer's website because the installer errors out saying that there's no version of Acer Iconia 3G Driver Install is installed. wtF? That's what I'm TRYING to do!
I did get a different USB driver installed - the USB Driver_Acer_1.06.1500_A30H_A500, but nothing wants to use it and Blackthund3r's APX Flash Util won't see it, AfterOTA won't use it, and it's basically useless anyway. AND I can't install the Acer_1.00.0524_A30H_A31H_A32H_A500_A501 drivers no matter if I've got any others installed or not.
In my device mangler, there is no device with an exclamation, and in fact, sees my Acer Iconia A500 under USB Serial Bus Controllers as "Acer Picasso USB Boot-Recovery Driver", only when it's plugged in. NO other instance shows up at all.
I'm actually at the point of trying to follow through with the EUU (dibb_nz's "last resort"), but vache's website is down and I can't download anything for it. In fact, there's nothing from that guide that has a valid link...
(http://forum.xda-developers.com/showthread.php?t=1632392)
So now where do I go? I understand IT really well, so you don't need to talk to me like a complete noob, but dang if I can't figure this one out!
If I can get valid links to all the downloads from the link above, I'd be more than happy to give it a go and see if that works, but I can't piece together all those things from random places. If either of you (or anyone else for that matter) has valid links for everything needed to follow the EUU guide, I'd be very grateful!
Any other advice would certainly be appreciated as well! I don't have to use either of these computers, but as mentioned, ALL of my computers have Windows 7 x64 on them. I suppose I could try one of my customer's computers for all this, but that's not morally right and probably something that I would prefer not to explore.
I feel as if I could get the USB drivers installed properly on EITHER machine, that I'd likely be in good shape. I think that's what my problem actually is on the laptop as well, even though they're all installed and shows as installed until I boot into any recovery - then I get the MTP Device Driver Fail. There's likely other Acer driver issues there though, since Blackthund3r's utils don't follow through for anything... everything just hangs. AfterOTA just hangs.
Advice please?
And thanks again for your knowledge!
Psychlone
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
dibb_nz said:
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
Click to expand...
Click to collapse
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
EDIT::
OK, so I'm really in bad shape here - now the EUU (PBJ20upgrade) comes back with the error:
Please download the newer image for the upgrade.
Current image version: Acer_AV041_A500_1,054.Acer_AV041_A500
New image version: Acer_A500_1.016.05_Com_GEN1
What now????
Psychlone said:
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
Click to expand...
Click to collapse
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
dibb_nz said:
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
Click to expand...
Click to collapse
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Psychlone said:
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Click to expand...
Click to collapse
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
THANK YOU!
dibb_nz said:
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
Click to expand...
Click to collapse
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Thanks again,
Psychlone
With what I went thru use Civs nvflash and rom and I'd stick with third cement until your safely patched and on ics.do all the wipes and follow instructions to the letter ...I'll check back in shortly
EDIT wtf "third cement" dang auto correct ... should read thors recovery
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
excellent news glad it worked for ya
Psychlone said:
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
Click to expand...
Click to collapse
if its referring to newer image then the data cable is connected!
and it will spit this error at you....
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
Click to expand...
Click to collapse
yup now you're cookin
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Click to expand...
Click to collapse
oh yeahhhhh!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Click to expand...
Click to collapse
nps glad to be of assistance -
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Click to expand...
Click to collapse
becoz then you'd have thousands of posts to look thru and no-one would bother reading it all....i try to keep my cpuid thread updated with things 'unbricking' but its too hard to put 'everything' in one post unfortunately
---------- Post added at 07:01 PM ---------- Previous post was at 06:48 PM ----------
Psychlone said:
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
Click to expand...
Click to collapse
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
dibb_nz said:
excellent news glad it worked for ya
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
Click to expand...
Click to collapse
CM10 is SLICK. Think CM9 on graphics steroids and you're close!
I appreciate your position more than most. I get a lot of enjoyment out of helping others as well - I've written overclocking guides for AMD systems that was written years ago, revised a couple/three years ago and is still used to this day, even though I've long since moved over to Intel's "dark side". I also participate pretty deeply in helping others at a couple PC hardware forums pretty much daily, even though that's my actual job - I own 2 computer repair businesses in my hometown, and with well over 20,000 computers to fix, I'm ALWAYS busy but still always find time to help others in need.
As for adding ***SOLVED*** to the title, I'd love to...but it won't let me. Perhaps it's because I don't have a high enough post count, or because it's reserved for Mods, but I can't do it.
Thanks for everything once again - it's quite refreshing to be on the receiving end!
Psychlone
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
DennisPimps said:
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
Click to expand...
Click to collapse
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Danny2 said:
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Click to expand...
Click to collapse
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
DennisPimps said:
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
Click to expand...
Click to collapse
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Danny2 said:
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Click to expand...
Click to collapse
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
DennisPimps said:
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
Click to expand...
Click to collapse
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Danny2 said:
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Click to expand...
Click to collapse
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
DennisPimps said:
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
Click to expand...
Click to collapse
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Danny2 said:
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Click to expand...
Click to collapse
Yea, it's still bricked. I did finally get the flash tool to recognize it but it kept hanging up. I also tried Timmy Dean's EUU tool and that hangs up too. I did a little more research and found that I may have a faulty emmc. I ran babsector and got 'fatal error code 9 cannot format partition BCT.' I found a thread here that discusses how to write around the bad sectors using Linux. I'm going to give that a go... I've always wanted to learn Linux. Hey, I can't screw it up anymore than it already is, right? Again, thanks for your time and effort in trying to help.
Cheers,
Dennis
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
ericpeacock79 said:
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a go, m8.
Thanks!
-Dennis
DennisPimps said:
I'll give that a go, m8.
Thanks!
-Dennis
Click to expand...
Click to collapse
Just wondering if you ever figured out the errors you were getting during flashing? Currently having the same issues when using babsector.