Database Users

[Q] Acer A500 bricked. Is it fixable?

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.

Rooting nexus 7 is impossible

Well unlocking the boot loader is possible but when rooting the nexus 7 gets stuck in fastboot when its suppose to be rebooting its self oh well I been at it all night so now I realized its impossible
Sent from my Nexus 7 using xda app-developers app

Use the toolkit, worked great for me. I couldnt get the adb right so I tried that. My nexus 4 was easy without the toolkit though..
Sent from my Nexus 4

I get a error saying failed <remote: <>
Sent from my Nexus 7 using xda app-developers app

If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.

How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app

I'll just go to yahoo answers I'll have more help there
Sent from my Nexus 7 using xda app-developers app

Class_of_punk26 said:
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If you unlocked the bootloader and you're having trouble rooting your device then I don't see you being able to relock the device either, which is critical to do before returning it as technically an unlocked device is out of warranty.
And you say no one is helping you, but you haven't provided any information at all. We have no idea what you did to even cause that error, and you were recommended just to use a toolkit if you want, as that is an easy approach, and you haven't responded on whether you have done that either.

Exactly, how is anyone supposed to help if you don't tell us what you did.
How did you unlock fast boot? What did you try to get rooted?........etc

User is informed of multiple posts. So hopefully, with your help, the root issue can get resolved.
User MUST tell people exactly the steps taken to replicate the error. Including PC type and Operating System.
I hope we do not see duplicated posts anymore.
So if some of you more experienced users, can do some "hand holding" and walk him through the steps, then it will be appreciated. As clearly, he has issues on his own.
Do it for XDA...
MD

bftb0 said:
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
Click to expand...
Click to collapse
I agree 100% on Toolkits

That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)

arclight25 said:
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
Click to expand...
Click to collapse
Yeah, this was my problem.. That's the only reason I used the toolkit. It wouldnt install right after downloading USB driver through SDK . got me pissed off and uninstalled every driver, and installed my nexus 4 all over also. Some how that one went easy..
Sent from my Nexus 4

LOL op went to yahoo answer, hilarious!
If he is still reading this, USE THE GOD DAMN TOOLKIT FFS, its pretty much idiot proof.

Yea, toolkit is the only way to go.

I think he is stuck in the same place I am stuck in. Whenever I get to the "Reboot Bootloader" in the Toolkit, it fails to go any further. I've made a thread about it here: http://forum.xda-developers.com/showthread.php?p=37524971
The toolkit isn't for everyone, unless of course I'm doing something wrong.

as long as toolkit detects your device, you can simply flash the google image and have everything reset, i dont see how that isnt for everyone honestly......

I used Wugfresh's toolkit and everything worked easily. I dont know any other way to do it, and the toolkit makes it easy for Gnex or Nexus 7.

HardBricked nexus 7 (i think its HardBricked anyway)

Hi, im kinda new here, but i really need help. i think ive hardbricked my nexus 7 (it wont start and the bootloader is wiped, the computer recognize the device as "APX" or something like that) and in one post they talked about blob files and a blob tool, can anyone help me with that? i have no clue how to compile/decompile the blobtool and what program i should use, can anyone give me a tutorial of any kind? (with what programs to use and in what steps)
thanks ahed

I have a nexus in the same condition. As far as I can see is dead. The blob thing only works if you copied it before it died as it is device specific.
Would be grateful if anyone could help though.
Sent from my D6503 using Tapatalk

I have the same issue. my brother says it bootlooped after updating (this happened a while ago), he then tried to flash the bootloader and then killed it. the device shows in APX mode in windows. I managed to install the Naked drivers and get it to recognize as a Asus Transformer device but I'm not sure where to go next with that. It has been gathering dust since last couple of months. I am hoping some good developer would take interest and solve this thing once and for all.

Stuck in TWRP on LG G2- need a Good Samaritan

First off. I'm pretty much a layman at this. Anyone that can solve my issues, I'll gladly pay via PayPal or whatever...
Two months ago, I bought a used LG G2 . It was rooted and running Lollipop.
Sadly, I was a PokemonGo junkie, so when the M'F'ng Niantic a**holes put a block on rooted phones, I attempted the Magisk workaround and ended up bricking my device.
Fortunately I found a solution via You Tube and was able to restore to the factory KitKat / AT&T.
THE CURRENT problem is that yesterday I re-rooted the device, installed TWRP, but did something wrong to where it will not fully reboot and I'm stuck in TWRP. I've watched and read about 20 "fix it" instructionals, which rely on using a PC. I'm using a laptop running XP and every time I have downloaded, installed, and tried to update the damn LG USB driver, it won't f*ing update. I'm going mad and ready to jump off a bridge.
Supposedly, this is the place to go. for answers, so ...CAN ANYONE HELP?!! Again, I'm a layman. I need VERY simple, step by step solutions, that account for ANYTHING that might go wrong, since so far, it always does.
Thank you, if you read this.

Ok Can you access to twrp ?
(Sorry for my english i'm french)

If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?

Kornelije23 said:
If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?
Click to expand...
Click to collapse
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app

R2MIR2MI said:
Ok Can you access to twrp ?
(Sorry for my english i'm french)
Click to expand...
Click to collapse
Thanks for the reply. Yes, I can access TWRP. I just don't know what to do with it.

Dork6243 said:
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's TWRP 2.7.0. I kind of know in theory what needs to be done, but I don't know how to do it. I thought I backed everything up using Titanium and TWRP, but maybe the KK ROM is gone? I dunno... I was actually hoping to install Lollipop

What model do you have?
If it is d802, then there is an easy-to-flash rom here: http://forum.xda-developers.com/lg-g2/development-d802/rom-pure-stock-lg-google-apps-t3477635/page1
To transfer it to the phone, you can use OTG as Dork said: put the rom on a usb-stick and connect it to the phone with an OTG cable. Most versions of twrp support OTG.
Another way is to get linux for your PC. You're really better off with linux than XP, but you can also just boot with a live-cd. In linux, USB generally just works, though sometimes you have to be root because ordinary users may not have permission.

Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested. I ended up finding a you tube video which walked me through downloading lg flash tool and some .dll file, and on my work computer with windows 7, I was able to install the usb drivers & change the port number which allowed LG flash to work. The crappy XP didn't have that option on the device manager menu and wouldn't install the drivers.
Anyway, I got it restored to ATT stock KitKat. I wanted Lollipop and Magisk, so I tried installing TWRP with AutoRec, then got stuck in TWRP and bricked again. So I did the whole lg flash to KitKat process again. Now Im sick of messing with it and bricking my phone. I cant find any super simple step by step tutorial that makes sense to a layman like me, or that doesn't leave out steps, or provide expired links, or account for anything that could go wrong. I had hoped this was the place to come, but no luck so far. I know its time consuming for someone to make up a truly easy to follow guide for an older device, using layman terms that my grandma could follow, and I work 2 jobs and dont have hours to try to thoroughly learn OS programming, so I guess Ill just leave well enough alone and live with KitKat and without the ability to mask my root.

davizzyus said:
Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested.
Click to expand...
Click to collapse
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4

Jan Philipp said:
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Click to expand...
Click to collapse
I have tried reading a lot of different threads. As I said before, I don't understand the "tech talk" for lack of a better word. When I'm reading "bootload" this, and " sideboot" that, and kernels, and loki, and CM, and mods, and .kdz and ATD,....I don't know what all that means, & there's no OS dictionary to translate. I can't seem to find any threads that explain it for newcomers trying to learn.
Im an accountant. I can prepare corporate tax returns with my eyes closed, but cell phone programming is Greek to me.

Help reviving a Nexus 7 2013 Flo 32G

I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA

Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.

Wish39 said:
Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.
Click to expand...
Click to collapse
Oopsie daisy.
Thanks, I will repost in the proper forum!

drjboulder said:
Oopsie daisy.
Thanks, I will repost in the proper forum!
Click to expand...
Click to collapse
It's fine. People make mistakes sometimes.
Also it looks like something majorly screwed up your Nexus 7. Hope you find a solution to fix it up sooner or later.

drjboulder said:
I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA
Click to expand...
Click to collapse
can you connect through fastboot?