Related
Okay - I can't seem to find a single thread that has a working solution to this.
Had Gingerale 2.0 on the Droid X. Was acting funny so decided to go up to CM7.1 now that it's supported. Had trouble getting into Clockwork via ROM Manager then via Bootstrap. Was about to try re-rooting (even though it is definitely rooted) but then ran into this problem..
First, when in standard recovery, I could not install the CM ROM because it failed to match the md5 sum (I'm presuming it's an md5). Not sure if that's normal, though, since it's the standard recovery and not clockwork.
After a system reset, which I did read somewhere, now the phone is stuck in a loop. Gets to the "DROID" noise, then the red-eye circle thing, then back to "DROID."
I cannot get the phone to show up on a computer - Win 7 in VM, Win 7 on laptop, Win 7 on desktop - so that I can try doing an SBF on it (which I have never done, but I think I have all the parts).
Thoughts on how I can get it to show up? Or other options?
thanks.
You may need to install drivers if you haven't already.
Try the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App
Drivers are installed. The "new device found" pop up never shows. Just acting as if it's not there.atnall.
kaiyen said:
Drivers are installed. The "new device found" pop up never shows. Just acting as if it's not there.atnall.
Click to expand...
Click to collapse
Try setting the connection type to either 'charge only' or 'PC mode'. Also try cycling through the different options.
I also would definitely recommend going the Linux route via 1kds's bootable SBF distribution.
Sent from my DROIDX using XDA App
The phone doesn't see the computer (any of them) either. The most it does is randomly start doing the boot loop again. If it's looping, by definition I can't get to the "charge only" or "PC mode" screen.
I will consider the linux distribution.
kaiyen said:
The phone doesn't see the computer (any of them) either. The most it does is randomly start doing the boot loop again. If it's looping, by definition I can't get to the "charge only" or "PC mode" screen.
I will consider the linux distribution.
Click to expand...
Click to collapse
Sorry for bad information lol.
The phone will enter bootloader mode successfully though?
Sent from my DROIDX using XDA App
No problem - the hardest thing is that I can't quite find the exact problems I'm having when doing searches. So the "usual" answers dont' seem to apply.
Bootloader mode - not 100% sure what that is. It starts up, I get the "M" and then the "DROID" sound. Then I get the spinning robotic eye thing, then it goes back to DROID. Over and over.
I can go into the standard recovery but not bootstrap nor clockwork (both of which I have installed in the past) and I know it's been rooted successfully.
I have wiped the entire phone while in the standard recovery several times but no luck.
thanks for any help. Worst case, I'm going to Verizon tomorrow and just going to show them it not working over and over, and try to get all my data off of it. Get a new phone. But I'd like to figure out what's up and/or get CM on here eventually.
allan
There's your issue.
Your phone must be in bootloader mode to SBF.
Hold both volume buttons and press the power button (press, NOT hold) and your phone will boot into bootloader mode.
The bootloader screen should show your bootloader version and say 'OK to program'.
From there, simply use RSD Lite or the Linux method to SBF.
After you SBF your device you must boot into stock recovery and format data and cache.
Sent from my DROIDX using XDA App
I haven't tried doing the SBF yet but THANK YOU. Ever reference I got to getting the phone into any kind of mode was just recovery. I had not found this bootloader mode option until now. Just missed it or whatever in other posts!
Ok, Im new to android and this account is new also because I cant remember the password of the old account...
So i was in 6.2, supposedly I rooted it, because I was able to run the Android marketplace. So Today I decided to give CM7 a try, so I follow a "tutorial" on
liliputing dot com, it is using "KindleFireUtility"
So when I hit "7" on KindleFire Utility , it downloaded twrp and the it said it has to check if the device was rooted or something, so it did all that, then it stay for like 10 minutes on "restarting device" or "waiting for device", and the kindle was doing nothing at all, it didnt turn off or do anything, so I got tired of waiting and hit the "Disconnect" button on the kindle screen, unplug the USB, the Kindle turned off and back on and it stays on the very first screen with the KinleFire Logo, it doesnt even shows the little animation. Now the computer doesnt detects the kindle at all...
I try to follow the steps in the topic : [HOW TO] Unbricking/Restoring your Kindle Fire 9 Attachment(s)
But it says "error: device not found"
What now?
I dont know is this has any relevance at all, but Im using a MacBook running Windows7 on "WMware Fusion"
Throwing a guess out there, you're probably still in fastboot.
//KindleFire.Tapatalk//
You're definitely on fastboot mode.
I just answered a similar problem here http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
Hope it helps you too.
ch0mch0m said:
You're definitely on fastboot mode.
I just answered a similar problem here http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
Hope it helps you too.
Click to expand...
Click to collapse
nope, either I cant seem to undestand exactly what i have to do and im doing it wrong, or it doesnt work on mine...
at one moment the computer recognize the kindle as a "unrecognize device" but still didnt work, or maybe I dont know how to do it, and now it doesnt recognize it anymore, just like it was yesterday, I connect it and nothing happens...
:/
You need to reinstall drivers to get your machine to see the kindle properly.
Sent from my PC36100 using xda premium
When The computer detects ir as a "unrecognize device" if I click update drivers I point it to where the drivers are and it tells me the drivers are up to date.
Kindlefiteutility shows "error: device not found" or something like that...
I'm still stuck /:
Shadow-of-Death said:
When The computer detects ir as a "unrecognize device" if I click update drivers I point it to where the drivers are and it tells me the drivers are up to date.
Kindlefiteutility shows "error: device not found" or something like that...
I'm still stuck /:
Click to expand...
Click to collapse
The instructions from this link fixed it for me the other day. I would do a complete shutdown of your Mac/PC instead of a reboot as a simple reboot didn't work for me the first time.
Ramer84015 said:
The instructions from this link fixed it for me the other day. I would do a complete shutdown of your Mac/PC instead of a reboot as a simple reboot didn't work for me the first time.
Click to expand...
Click to collapse
the thing is that I cant get the computer to recognize it as a kindle, or even a android phone!...
-_________________-
If I direct it to the folder with the drivers it doesnt do anything, and if I click pick from list, like the guy say on that post theres no "android" on the list.
So It seems I will just have to enjoy my Brick Fire how it is, I guess I can use it as a pretty expensive door stoper or paper weight....
Okay I had post before about my tab and I had great help but I couldn't get it to work now it's stuck in apx mode because of a theme for v8 bootloader that I had mistakenly flashed instead of a rom. So every time I turn on my device it shows the new image for the bootlader but gives the message "flashing bootloader....update failed" then goes into apx mode. So with some research and trying out a few things I figure that my partitions are messed .
MODFAST said:
Okay I had post before about my tab and I had great help but I couldn't get it to work now it's stuck in apx mode because of a theme for v8 bootloader that I had mistakenly flashed instead of a rom. So every time I turn on my device it shows the new image for the bootlader but gives the message "flashing bootloader....update failed" then goes into apx mode. So with some research and trying out a few things I figure that my partitions are messed .
Click to expand...
Click to collapse
use tdv4 to reset partitions links in cpuid guide in my sig
btw, is fastboot available??
which method did u use to flash originally, have u tried it again?
does yr pc recognise the tab in apx mode - is an apx device listed???
dibb_nz said:
use tdv4 to reset partitions links in cpuid guide in my sig
btw, is fastboot available??
which method did u use to flash originally, have u tried it again?
does yr pc recognise the tab in apx mode - is an apx device listed???
Click to expand...
Click to collapse
Fastboot not available used to be no is not
My device has been fastboot clean wiped completely like 50 time and I had boot loader but it wouldn't go past the bootlader after I flashed this v8 custom bootloader image zombie rock from civato it had issue when I had restarted it and the rest is in the top.
Pc recognize it as a apx device but not apxflash manger or a500 manger it don't show up but before the download it did
MODFAST said:
Fastboot not available used to be no is not
My device has been fastboot clean wiped completely like 50 time and I had boot loader but it wouldn't go past the bootlader after I flashed this v8 custom bootloader image zombie rock from civato it had issue when I had restarted it and the rest is in the top.
Pc recognize it as a apx device but not apxflash manger or a500 manger it don't show up but before the download it did
Click to expand...
Click to collapse
did u run tdv4??
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
did u run tdv4??
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I had downloaded that already and I don't really understand how to use it
I used tdv.4 it took longer than it said in the post ,5 mins, (16 mins) to run the detecting current image part but it got there and now its working great.
If you like i could walk you through it. Just pm me
I have use tdv4 but my tab keep showing as undetected and I follow the directions over and over but once the update starts my tab goes into "entering acer download mode" so It keeps going undetected after I just unplug the USB then plug it back in then it goes to the next screen.But after that on the update screen the most the green bar goes to is till the end of the word upgrade and stays there for a long period.
If necessary I can make a video showing step by step what I did ? but I don't see tdv4 working for this.
MODFAST said:
I have use tdv4 but my tab keep showing as undetected
Click to expand...
Click to collapse
do u mean the window that pops up saying ."cannot detect iconia tab"??
this is correct, at this point u put yr tab in manual apx mode THEN you connect yr micro USB cable up to yr PC and continue the flash
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
do u mean the window that pops up saying ."cannot detect iconia tab"??
this is correct, at this point u put yr tab in manual apx mode THEN you connect yr micro USB cable up to yr PC and continue the flash
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I did that and it keeps giving me errors so instead of turning off device because at this point it says acer on it with entering acer download mode in the top left corner I just unplug it then plug it in again then after that no error and the green bar moves but the bar for hour don't go passed the word update.
Originally Posted by dibb_nz<br />
do u mean the window that pops up saying ."cannot detect iconia tab"??<br />
this is correct, at this point u put yr tab in manual apx mode THEN you connect yr micro USB cable up to yr PC and continue the flash<br />
<br />
<br />
<br />
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
<br />
<br />
I did that and it keeps giving me errors so instead of turning off device because at this point it says acer on it with entering acer download mode in the top left corner I just unplug it then plug it in again then after that no error and the green bar moves but the bar for hour don't go passed the word update.
Click to expand...
Click to collapse
I'm a wee bit confused here....
does it give u an error or does it just get stuck on the green status bar?
i think that with u unplugging usb WHILE the tab is in download mode maybe disrupting the flash....
being stuck in apx mode isn't easy to repair, u just have to keepmtrying, good luck
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
I'm a wee bit confused here....
does it give u an error or does it just get stuck on the green status bar?
i think that with u unplugging usb WHILE the tab is in download mode maybe disrupting the flash....
being stuck in apx mode isn't easy to repair, u just have to keepmtrying, good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Ok every time I connect to the program it at the screen before the update where u put cpuid after I click next you see update screen then it goes back to say that they cant recognize the tab and then I have to unplug the tab then re plug it instead for putting it in apx mode again beacuse it just kees me doing th same process over I just take out the usb then re plug it then update starts the bar goes 20 percent then stops for hours .[IIIIII______________] and that's all that happens.
Today my Nexus 7 shut off because the battery died. So I plugged it in and left. When I returned it was on the Nexus X logo boot screen.
I now can't do anything. If I try to turn it off by hitting the power button nothing happens.
If I hold the power button for 20 seconds it just reboots back to the X logo.
If I hold the power button and volume up for 20 seconds it just reboots back to the X logo.
If I hold the power button and both volume buttons for 20 seconds it just reboots back to the X logo.
If I hold the power button and volume down for 20 seconds it boots into Bootloader.
From bootloader I have 4 options:
-Start: This just reboots back to the X logo.
-Restart Bootloader: This just refreshes the Bootloader but leaves me where I am.
-Power Off: This is the only way I can even turn my Nexus 7 off. But when I turn it back on it just boots back to the X logo.
-Recovery Mode: This just shows a android with his chest open with a red exclamation mark and it says "No Command". At that point I can only hold power for 20 seconds to get it to reboot to the X logo.
My Nexus 7 is completely stock.
What can I try? Any advice or ideas? TIA.
Chillin said:
Today my Nexus 7 shut off because the battery died. So I plugged it in and left. When I returned it was on the Nexus X logo boot screen.
I now can't do anything. If I try to turn it off by hitting the power button nothing happens.
If I hold the power button for 20 seconds it just reboots back to the X logo.
If I hold the power button and volume up for 20 seconds it just reboots back to the X logo.
If I hold the power button and both volume buttons for 20 seconds it just reboots back to the X logo.
If I hold the power button and volume down for 20 seconds it boots into Bootloader.
From bootloader I have 4 options:
-Start: This just reboots back to the X logo.
-Restart Bootloader: This just refreshes the Bootloader but leaves me where I am.
-Power Off: This is the only way I can even turn my Nexus 7 off. But when I turn it back on it just boots back to the X logo.
-Recovery Mode: This just shows a android with his chest open with a red exclamation mark and it says "No Command". At that point I can only hold power for 20 seconds to get it to reboot to the X logo.
My Nexus 7 is completely stock.
What can I try? Any advice or ideas? TIA.
Click to expand...
Click to collapse
I had this EXACT same problem, what I did was use the process I found on theunlockr.com website, I would post the direct link but since I'm a new member it won't allow me to, hope this helps.
P.S. I googled "reset nexus 7 through fastboot" and it's the first option
khalum777 said:
I had this EXACT same problem, what I did was use the process I found on theunlockr.com website, I would post the direct link but since I'm a new member it won't allow me to, hope this helps.
P.S. I googled "reset nexus 7 through fastboot" and it's the first option
Click to expand...
Click to collapse
If you just put a space in the link you can post it. Like so:
http: //theunlockr.com/2012/09/21/how-to-hard-reset-a-bricked-nexus-7-with-your-pc/
Thanks for the help. is there no easier way to do a wipe or restore? That seems unnecessarily complicated.
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Chillin said:
http://theunlockr.com/2012/09/21/how-to-hard-reset-a-bricked-nexus-7-with-your-pc/
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda premium
esema1o said:
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Sorry but what exactly does that do for me?
It allows me to install a recovery, which I don't want to do.
It allows me to boot into recovery, which I can already do.
It allows me to install a custom ROM, which I don't want to do.
What am I missing?
Gizmoe said:
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm?
Chillin said:
Thanks for the help. is there no easier way to do a wipe or restore? That seems unnecessarily complicated.
Click to expand...
Click to collapse
Its really not as complicated as it looks. You could even copy and paste each command. But if its something more simple you are looking for then look in the development stickies. There are tools there to do the same stuff.
Sent from my Nexus 7 using xda premium
---------- Post added at 11:19 PM ---------- Previous post was at 11:11 PM ----------
Chillin said:
Hmmm?
Click to expand...
Click to collapse
Just making it an actual link for other readers who want to click it.
Sent from my Nexus 7 using xda premium
Gizmoe said:
Its really not as complicated as it looks. You could even copy and paste each command. But if its something more simple you are looking for then look in the development stickies. There are tools there to do the same stuff.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Well you actually can't paste into a command prompt, so I can't cut and paste.
But it wasn't so much that it was complicated (certainly much easier than the rooting, unlocking, and flashing ROMs and basebands I've done on many devices), it was more so that it seems there should be an official proper way to restore your device like there is with many others.
Anyways I'm downloading the factory image and whatnot now.
Chillin said:
Well you actually can't paste into a command prompt, so I can't cut and paste.
But it wasn't so much that it was complicated (certainly much easier than the rooting, unlocking, and flashing ROMs and basebands I've done on many devices), it was more so that it seems there should be an official proper way to restore your device like there is with many others.
Anyways I'm downloading the factory image and whatnot now.
Click to expand...
Click to collapse
Ctrl v will paste into prompt on linux. On windows 7 you just right click and paste. Check out wugs tool as well. May be worth checking out.
Sent from my Nexus 7 using xda premium
Chillin said:
Well you actually can't paste into a command prompt, so I can't cut and paste.
But it wasn't so much that it was complicated (certainly much easier than the rooting, unlocking, and flashing ROMs and basebands I've done on many devices), it was more so that it seems there should be an official proper way to restore your device like there is with many others.
Anyways I'm downloading the factory image and whatnot now.
Click to expand...
Click to collapse
Windows? You sure can paste into a command prompt. While ctrl+v won't work, you can still right click.
Gizmoe said:
Ctrl v will paste into prompt. Check out wugs tool as well. May be worth checking out.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Actually no Ctrl-V just gives you "^v", but I just discovered that right-click Paste works. I never use right-click so I never saw that, so turns out you were right after all.
Anyways I was just kidding about the cut and paste, obviously that wasn't what was holding me back from doing it.
Thanks for trying to help suggesting something else, but I've already downloaded the necessary tools for this one, and like I said it wasn't that I wanted another tool it was that I wanted an Official way to do it.
najaboy said:
Windows? You sure can paste into a command prompt. While ctrl+v won't work, you can still right click.
Click to expand...
Click to collapse
lol, ya windows. Like I just said in another post I just noticed that. I didn't notice before because I never use right-click.
And regardless I would never use it to copy 2 word prompts anyways. More trouble than it's worth.
Chillin said:
Actually no Ctrl-V just gives you "^v", but I just discovered that right-click Paste works. I never use right-click so I never saw that, so turns out you were right after all.
Anyways I was just kidding about the cut and paste, obviously that wasn't what was holding me back from doing it.
Thanks for trying to help suggesting something else, but I've already downloaded the necessary tools for this one, and like I said it wasn't that I wanted another tool it was that I wanted an Official way to do it.
Click to expand...
Click to collapse
I edited my post to say what I meant more clearly. Linux is Ctrl v and windows is just right click and paste. I assumed you where using Linux and couldn't right click and paste. Hope it works out for you. I agree there should be like an ruu or Odin method. I've only been on the nexus for a couple of days and it is much different.
Sent from my Nexus 7 using xda premium
Gizmoe said:
I edited my post to say what I meant more clearly. Linux is Ctrl v and windows is just right click and paste. I assumed you where using Linux and couldn't right click and paste. Hope it works out for you. I agree there should be like an ruu or Odin method. I've only been on the nexus for a couple of days and it is much different.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh I see, gotcha. Never ever used Linux.
I have the Nexus 4, Nexus 7, and Nexus 10 and all have been quite good to me, this is my first real issue.
OK, no luck, none of the methods suggested here worked.
The method on theunlokr doesn't just says waiting for device.
The JROMFlasher says no device is detected.
Wugs tool says Fastboot device was not found.
Any other ideas or anything else I can try?
Chillin said:
OK, no luck, none of the methods suggested here worked.
The method on theunlokr doesn't just says waiting for device.
The JROMFlasher says no device is detected.
Wugs tool says Fastboot device was not found.
Any other ideas or anything else I can try?
Click to expand...
Click to collapse
There are a few different drivers for the nexus. Sounds like you don't have the correct drivers. Download the android sdk and install the Google drivers from the
SDK manager. When in fastboot type fastboot devices and it should list your device. If not then its a driver issue. The other two drivers are "USB driver r06 windows" from Asus website and "universal naked driver 072" which I found on Google. One of those should work but the one in sdk should work.
Sent from my Inspire 4G using xda premium
Chillin said:
Well you actually can't paste into a command prompt, so I can't cut and paste.
But it wasn't so much that it was complicated (certainly much easier than the rooting, unlocking, and flashing ROMs and basebands I've done on many devices), it was more so that it seems there should be an official proper way to restore your device like there is with many others.
Anyways I'm downloading the factory image and whatnot now.
Click to expand...
Click to collapse
I am very new to this but I might be able to help if you have USB debugging enabled on your nexus 7. I saved mine from a soft brick the other day, very frustrating, but I got it.
I am guessing your boot loader is unlocked and you are running a custom recovery?
Again hopefully USB debugging is enabled.
I recommend mskips nexus toolkit.
1. Remove the back cover of the nexus 7 and disconnect the battery. It's easy. Just follow the wires coming off the battery to the little black plastic connector. Once you locate it, use something small and plastic to push on the edge near where the wires go in. Push toward the power and volume buttons. Let it sit for an hour or so.
2. Very, very ,very ,important!!! Get into your device manager on your PC and uninstall all drivers on the PC that say android, Google or nexus. I mean all of them! Check USB drivers for this also. To many of these cause to many paths for the toolkit and PC to try and follow. Get them all off!
3.after the nexus sits unplugged for at least 1 hour. Reconnect the battery.
4. Get into fast boot mode-power/volume/up/down and plug the nexus into the PC. Let the drivers install. These need to be the only ones on the PC at this time!
5. Open mskips toolkit and check for serial number. Refresh toolkit and or switch USB ports on PC if serial number does not show. It will.
6. On the toolkit try option 5 first. Rename recovery.
7. Then option 6. Reflash custom recovery.( I had to do this three times).
8. Download and flash factory image.
9. Root using the toolkit.
10. Start flashing again.
When the toolkit gave me an error I went back and started over, this happened a few times.
This saved my nexus 7 from being smashed by a sledge hammer and thrown in the garbage. This was very frustrating for me but I got it.
Thanks to mskip
Sent from my Nexus 7 using XDA Premium HD app
tnt0303 said:
I am very new to this but I might be able to help if you have USB debugging enabled on your nexus 7. I saved mine from a soft brick the other day, very frustrating, but I got it.
I am guessing your boot loader is unlocked and you are running a custom recovery?
Again hopefully USB debugging is enabled.
I recommend mskips nexus toolkit.
1. Remove the back cover of the nexus 7 and disconnect the battery. It's easy. Just follow the wires coming off the battery to the little black plastic connector. Once you locate it, use something small and plastic to push on the edge near where the wires go in. Push toward the power and volume buttons. Let it sit for an hour or so.
2. Very, very ,very ,important!!! Get into your device manager on your PC and uninstall all drivers on the PC that say android, Google or nexus. I mean all of them! Check USB drivers for this also. To many of these cause to many paths for the toolkit and PC to try and follow. Get them all off!
3.after the nexus sits unplugged for at least 1 hour. Reconnect the battery.
4. Get into fast boot mode-power/volume/up/down and plug the nexus into the PC. Let the drivers install. These need to be the only ones on the PC at this time!
5. Open mskips toolkit and check for serial number. Refresh toolkit and or switch USB ports on PC if serial number does not show. It will.
6. On the toolkit try option 5 first. Rename recovery.
7. Then option 6. Reflash custom recovery.( I had to do this three times).
8. Download and flash factory image.
9. Root using the toolkit.
10. Start flashing again.
When the toolkit gave me an error I went back and started over, this happened a few times.
This saved my nexus 7 from being smashed by a sledge hammer and thrown in the garbage. This was very frustrating for me but I got it.
Thanks to mskip
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for trying to help but like I mentioned it was completely stock so I couldn't have done that. Regardless taking my device apart to fix a software issue seems rather extreme.
Gizmoe said:
There are a few different drivers for the nexus. Sounds like you don't have the correct drivers. Download the android sdk and install the Google drivers from the
SDK manager. When in fastboot type fastboot devices and it should list your device. If not then its a driver issue. The other two drivers are "USB driver r06 windows" from Asus website and "universal naked driver 072" which I found on Google. One of those should work but the one in sdk should work.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I had the correct drivers according to Wugs, but I removed all of them (and dozens of other old ones from other phones and tablets) and then reinstalled.
Wugs still failed to do a wipe so I used it to unlock my bootloader instead (in hopes of re-trying to do a wipe afterwards) and then it finally booted up.
So it is now fixed. Yay!
Thanks.
hi,
Recently I wanted to install a custom rom onto my Acer A501 tablet. I looked up a bunch of guides in this forum and found a very common flash guide made by blackthund3r, so I went and followed the proper guidelines given here: http://forum.xda-developers.com/showthread.php?t=1622425. Everything worked fine until I got to the part where the A500 APX Flash Utility was suppose to detect my tablet in APX mode but it can't.
I've installed the Acer Composite ADB driver found here: http://downloads.rurouniserver.com/...driver-download-v1000524-android-32-honeycomb. (Version 1.0.10.0).
Someone else on the forum suggested here (http://forum.xda-developers.com/showthread.php?t=1660313) that we must install the google adb driver instead but I can't seem to get it to work either.
I desperately need help or advice on how to get the A500 APX Flash utlity to detect my tablet.
Sometimes it just hangs, also only runs with ics roms. if both sets of drivers are correctly installed u should see an apx device listed in device manager on ur pc. What os r u using...if all else fails just use the manual nvflash method instead
Sent from my GT-I9300 using Tapatalk 4
when I set my tablet into apx mode the screen is dark but the power button is on. I don't see any apx devices listed in my device manager and the composite adb driver disappears after setting into apx mode.
I'm running windows 7 ultimate x64 on as my OS.
Run the manual method instead but in saying that, if an apx device isn't listed. ..uninstall and reinstall the drivers
Sent from my GT-I9300 using Tapatalk 4
night8388 said:
when I set my tablet into apx mode the screen is dark but the power button is on. I don't see any apx devices listed in my device manager and the composite adb driver disappears after setting into apx mode.
I'm running windows 7 ultimate x64 on as my OS.
Click to expand...
Click to collapse
Hi
I thought I got the same situation like you.
I use blackthund3r's apx flsh 0.41. Everything goes well:
.........................extracting resources
.........................Starting ADB Server
.........................Enter APX Mode
.........................Wait 5 Seconds.....
.........................Killing ADB Server
and then, no matter how many times I press the "Done! Press to run again", I CANNOT go into the APX mode again.
at this time, the a500 screen is black.
I run another adb screen on PC, and found no device list.
But when I re-open the a500, I can detect the device.
Now my a500 cannot go into the recovery node, but it can work normally.
Anyone can help me to figure out what happened?:crying:
uzni said:
Hi
I thought I got the same situation like you.
I use blackthund3r's apx flsh 0.41. Everything goes well:
.........................extracting resources
.........................Starting ADB Server
.........................Enter APX Mode
.........................Wait 5 Seconds.....
.........................Killing ADB Server
and then, no matter how many times I press the "Done! Press to run again", I CANNOT go into the APX mode again.
at this time, the a500 screen is black.
Click to expand...
Click to collapse
apx mode is black screen and power lite is on - carry on with the flash!
I run another adb screen on PC, and found no device list.
Click to expand...
Click to collapse
When you are in apx mode - adb is not available -
Check the drivers are correctly installed correctly.
..put yr tab in apx mode,
(sometimes its easier to do this via the buttons, theres plenty of posts on how to do it, do quick search)
you should hear the new hardware detected sound in windows...
then go todevice manager or the safely remove hardware icon in your system tray and look to see if an "apx device" is listed there...
if it is, then carry on and flash the bootloader and recovery.
See the apxFlash pictorial in my sig for a step by step if you still have troubles
But when I re-open the a500, I can detect the device.
Click to expand...
Click to collapse
Do you mean you can view your tabs files from windows???
This is why you need both sets of drivers! acers and androids (you need the android-sdk installed too, but if you have used the mini-sdk zip from my guide then you don't need the full sdk kit)
Remember, if you can view files you cannot be in apx mode and vice versa...its one or the other
There can be driver issues with 64bit win 7/8 PC's. XP or Win 7 work best.
Reinstalling Acer drivers can help too.
Now my a500 cannot go into the recovery node,
Click to expand...
Click to collapse
No it won't if you have not completed the flash!
dibb_nz said:
apx mode is black screen and power lite is on - carry on with the flash!
When you are in apx mode - adb is not available -
Check the drivers are correctly installed correctly.
..put yr tab in apx mode,
(sometimes its easier to do this via the buttons, theres plenty of posts on how to do it, do quick search)
.........
Click to expand...
Click to collapse
OK, I upload 2 pictures for better explain.
01.jpg:
A500 power led light = on
U see, apx flash tool CANNOT go into the APX mode.
My notebook can see APX device
I set another window for adb devices, and found nothing.
02.jpg:
Set A500 power off and on. (manually)
do not touch apx flash tool window.
My notebook can not see APX device (while off).
My notebook can see "MTP" device (while on).
I set another window for adb devices, and found device code.
Now I can run A500 normally.
==================
Then, I click "Done! Press to run again" on the apx flash tool window,
It will become the "01.jpg"
Like an endless loop.:crying:
Could you help me?
Yup sometimes the tool does that.
Try again , when Windows detects the apx device just click the blue arrow anyway, let's see wot happens
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Yup sometimes the tool does that.
Try again , when Windows detects the apx device just click the blue arrow anyway, let's see wot happens
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Many thanks for your suggestion, and I will try your plan tonight.
dibb_nz said:
Yup sometimes the tool does that.
Try again , when Windows detects the apx device just click the blue arrow anyway, let's see wot happens
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Sorry for my late response. Please check the attached pics for reference.
I ignore the wrong message and go forward. and then, I stuck on the 03.jpg over 1 hour...
and I open another adb screen, please see 04.jpg.
Does this help you recognize my problem? what should I do now? Please give me some advise.
It doesn't look good
Pls download the babsector.rar file. It's in post 2 of the root guide in my Sig along with the instructions. Run the bat file and post the output pls
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
It doesn't look good
Pls download the babsector.rar file. It's in post 2 of the root guide in my Sig along with the instructions. Run the bat file and post the output pls
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
many thanks for your suggestion, and I will try it later.
dibb_nz said:
It doesn't look good
Pls download the babsector.rar file. It's in post 2 of the root guide in my Sig along with the instructions. Run the bat file and post the output pls
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Ya! I finally install your bootloader successfully!
Your "babsector.rar " is wonderful.
I had install a new rom for my old A500. Thanks very much.
uzni said:
Ya! I finally install your bootloader successfully!
Your "babsector.rar " is wonderful.
I had install a new rom for my old A500. Thanks very much.
Click to expand...
Click to collapse
Yes babsector is a tabsaver!!! I can't take the credit for it as it came from someone in the Russian forums but it does a very good job. Pleased u got up n running again
Sent from my HTC_PN071 using Tapatalk
I think I am in a similar predicament here. My a500 has an SOS checksum error, and is not detected by windows as an APX device. None of the tools listed see my tab. ANy advice?
sharkguy said:
I think I am in a similar predicament here. My a500 has an SOS checksum error, and is not detected by windows as an APX device. None of the tools listed see my tab. ANy advice?
Click to expand...
Click to collapse
Yr tab must be have drivers correctly installed and be in apx mode for Windows to detect it. use XP, Vista, win7 32bit. Issues on 64bit and win8
Run babsector.rar file as above.
Sent from my HTC_PN071 using Tapatalk
Oh, Thanks dibb, will give that a try! Only have a VM win XP so I hope that works...
sharkguy said:
Oh, Thanks dibb, will give that a try! Only have a VM win XP so I hope that works...
Click to expand...
Click to collapse
Yerrrr...ok.good luck with that..try manual nvflash I.e. babsector(not the manual option in the tool) Will work when the tool won't.
Sent from my HTC_One using Tapatalk
Scratch that. I guess what I will be using is a VM version of WIN7 32bit. not that it makes all that much of a difference. Just thought I would keep you informed, lol.
Gave up for the night. Can't seem to get the USB devices to show in my VM. will attempt a fresh install of lower OS in the morning. thanks again.
Sent from my SGH-I317M using xda app-developers app