Related
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.
Sent from my Nexus 7 using Tapatalk 2
My N4 is from PlayStore USA, and I live outside of US. A few days ago I did a stupid mistake and flashed a wrong bootloader (please don't ask why - the embarrassment still hurts! ). The N4 is now totally dead - cannot be turned on, and won't boot no matter which sets of buttons I hold down.
I have been searching the net for solutions but have not found any simple enough (for me) solution. I read of several similar cases and the solution has been to send back to Google/LG. As I live outside of US, this isn't much of an option. I have also read about use of Gtag to unbrick devices but this is beyond my capability and this service is also not available in my country. Sending the N4 to my local LG service centre for repairs (there's no International warranty) is a last resort but I am not sure whether they have tbe tools and knowhow to unbrick my N4. They may not even want to get involved!
So I am writing in this forum to ask for help. Any advice will be appreciated. Thanks in advance.
Why the hell would you even flash the bootloader manually?
Anyway, there was a thread recently about Qualcomm's debugging mode. However, you'll need the appropriate drivers and most likely other software for it to work.
I don't know if anyone actually got it working, though
I dont know why I did it too - just following wrong instructions ; out of sheer stupidity!
Sent from my Nexus 7 using Tapatalk 2
download the quacomm usb high speed drivers and install them you might have to do have disk to install them in device manager. then doqnload the QPST qualcomm tool. this will allow you to flash phone images and other files here. It should pick your phone up in download state. Only problem now is that the Qualcomm tool only allows hex image files to be flashed. this is where i was stuck
Thanks for the qualcomm suggestion. I will look through it when I return to my home country in a week`s time. But from what you have described, the procedure seems too complex for me. I am also following the other `bricked Nexus 4` thread in this section which I was not aware of till yesterday. All indications are that my bricked Nexus 4 will be a total loss - LG in my country has told me that they will not touch my unit until Nexus 4 is officially launched in my country (that could be a couple of months away), and returning the unit back to Google USA will be extremely difficult, complex and cumbersome as I just learned that the unit has to be returned by the original purchaser from USA (I bought the N4 from a 3rd party in my country). Its an expensive mistake and I can only blame myself for the stupid mistake I made.
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
chwads2k8 said:
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
Click to expand...
Click to collapse
Not that simple. If you want, read this thread for some good info: http://forum.xda-developers.com/showthread.php?t=1914359
What where you trying to flash?
Anyone tried succesfully?
Hello.
I am having a problem with ADB and Bootloader drivers with my Nexus 4.
I've been sitting here the whole day trying to work it out but no luck (no tutorial helped me from google or xda)
Basically, the problem is ADB isn't working correctly and bootloader drivers are not recognized as well.
When I connect my device to my PC it finds the right driver (Android Composite ADB Interface) but when I try to use "adb devices" it returns "xxxxxxx(device serial number) offline"
When I go to bootloader mode the driver could not be found nor installed manually (when I direct to the directory with the driver it doesn't find it)
I want to downgrade 4.3 to 4.2.2 and cannot do it without the bootloader driver or ADB.
Strange thing is though, I have another Nexus 4 device with 4.2.2 (PAC Rom) and it's working flawlessly from the same computer.
1 more thing is, I've been trying to get to the point where I can approve my pc (RSA) without luck - been trying to delete the .android directory from my PC and also /Android/Misc/ADB directory from the phone, but nothing let me to that stage again.
I've tried 3 PCS, 1 Mac and no luck with anything.
Tried with Pac Rom and PA399 RC2 - AK KERNEL and regular ROM kernel.
No luck with anything.
What can I do that I haven't done yet?
Please Help.
Guy.
well i've been sitting and investigatin the whole day today as well without any luck.
already thinking about a malfunction with ths usb connection on the phone's side as the other nexus 4 device connects just fine with ADB, Fastboot etc.,
Can anyone shad some light?
Thank you!
Well, If anyone is experiencing the same issue I have found a solution.
Flashing a bootloader resolves the issue.
Hope this helps someone.
GuyZapPa said:
Well, If anyone is experiencing the same issue I have found a solution.
Flashing a bootloader resolves the issue.
Hope this helps someone.
Click to expand...
Click to collapse
I'll just point out that while flashing a new bootloader resolved the issue the op was having. What he has done is probably bypassed the problem.
The issue will not have been on his phone but with a driver conflict on his computer.
By flashing a new bootloader, the hardware id's will probably have changed allowing the correct drivers to function this time.
To op
Enabling hidden devices in device manager will probably show a few hidden android devices which was the cause of your initial problems
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
I'll just point out that while flashing a new bootloader resolved the issue the op was having. What he has done is probably bypassed the problem.
The issue will not have been on his phone but with a driver conflict on his computer.
By flashing a new bootloader, the hardware id's will probably have changed allowing the correct drivers to function this time.
To op
Enabling hidden devices in device manager will probably show a few hidden android devices which was the cause of your initial problems
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, I am not sure that flashing the bootloader bypassed the problem, I am pretty sure it solved it.
I am saying that because I have deleted every possible driver, reinstalled, did not help.
Connected the phone to a new virtual machine I've created and was having same problem.
Tried it on a Mac, Same thing.
I've been dealing with this for quite some time, so I'm pretty sure flashing a bootloader solves the problem for people having it (not too many, as I've searched on the subject pretty much everywhere and no one ever said to flash a bootloader.)
I do apologise. I wasn't aware you had tried connecting via different os's
99% of these cannot connect issues are driver related.
Looks like you are the unlucky 1%
Though I am glad you got it sorted.
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
I do apologise. I wasn't aware you had tried connecting via different os's
99% of these cannot connect issues are driver related.
Looks like you are the unlucky 1%
Though I am glad you got it sorted.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I thought just like you, and every tutorial or explanation on the web points to a driver problem.
It's all good, and as I said, hope it'll help others that suffer from the same problem
Good week.
Guy
A while back i hard bricked my N4, and got it replaced, but i kept the broken one, hoping to get it working again. It shows up as "qhsusb_dload" on my computer and says i need the drivers for it. But i cant seem to find the drivers for qhsusb_dload, so if anyone could give me a link for those drivers, it would be a great help.
sinndissension said:
A while back i hard bricked my N4, and got it replaced, but i kept the broken one, hoping to get it working again. It shows up as "qhsusb_dload" on my computer and says i need the drivers for it. But i cant seem to find the drivers for qhsusb_dload, so if anyone could give me a link for those drivers, it would be a great help.
Click to expand...
Click to collapse
There are no drivers. That's what shows up when you're hard bricked.
Sent from my Nexus 5
Try this method http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Tried flashing stock image through fastboot?
No fastboot, no recovery, no anything. /:
I know its a hard brick, but there are drivers for this for other models of android, and ive read of people having success with some phones once they get the drivers for it.
sinndissension said:
I know its a hard brick, but there are drivers for this for other models of android, and ive read of people having success with some phones once they get the drivers for it.
Click to expand...
Click to collapse
Well good luck with that. You're not going to find any drivers
Sent from my Nexus 5
jd1639 said:
Well good luck with that. You're not going to find any drivers
Sent from my Nexus 5
Click to expand...
Click to collapse
Give him a break. The least you can do is not be an asshole.
OP: Linux might help you, you don't need drivers on Linux.
I've tried some Linux recovery tool for my old galaxy player 5.0, however i wasn't successful. I'm not sure is there any recovery tool based on Linux for the Nexus 4
Mashed_Potatoes said:
Give him a break. The least you can do is not be an asshole.
OP: Linux might help you, you don't need drivers on Linux.
I've tried some Linux recovery tool for my old galaxy player 5.0, however i wasn't successful. I'm not sure is there any recovery tool based on Linux for the Nexus 4
Click to expand...
Click to collapse
Dude, jtag is his only option. He's not going to find drivers. I'm not trying to be an a-hole just stating the facts.
Sent from my Nexus 5
qhsusb_dload is what is used to initially load firmware onto the phone. (From what ive read so far) so i cant imagine the company that does this are the ONLY people that the software to do so, unless theres some hardware stuff they do, (which i havent found any proof of this). Still worth a shot to me, and like i said, im just trying to give it a SHOT. Not looking for people to just say, "oh its not possible" unless they have experience with this sort of thing. Thanks.
Well, a few days ago I was using my nexus 7, and it was working fine. I went to go work out and put my nexus 7 down, when I came back it was completely bricked. No charging indicator, won't boot at all - no, not even into fastboot mode.
I have it in APX mode (it shows up in device manager as "APX"), and I'm wondering: is there any way to boot a boot.img so I can get it up and running again, or is my device a lost cause?
To my understanding no, you need a device specific backup made ahead of time.
See this thread
http://forum.xda-developers.com/showthread.php?t=2455927
So unfortunately in your case you are more than likely out of luck, and for everyone else I would suggest make a backup now and store it on PC just in case
Good news is we should see a new nexus tablet in the next month or so...
demkantor said:
To my understanding no, you need a device specific backup made ahead of time.
See this thread
http://forum.xda-developers.com/showthread.php?t=2455927
So unfortunately in your case you are more than likely out of luck, and for everyone else I would suggest make a backup now and store it on PC just in case
Good news is we should see a new nexus tablet in the next month or so...
Click to expand...
Click to collapse
I figured. Thanks
/thread