Database Users

Bricked?

A good friend of mine supposedly shut off his A500 during a upgrade/update. The unit still powers on but all I can get it to show is "boot verified failed..." in the upper-left corner of the Acer screen. I've downloaded several ROMs and tried reflashing from the SD card but no luck in reviving this. All I get is the Android triangle. I've reformatted the SD card. I've tried the Vol + power + screen lock stuff, too. I can't get to any other screen to change any settings... period. Many of the ROMs that I would like to try are dead links now that the government has shut them down. This is a US unit. Would someone be kind enough to direct me to where I can get the right stock ROM so I can at least get this thing running for him?

Hi ..
Not sure what he done.But it sounds like this will fix this issue for you..
Just follow this link good luck
http://forum.xda-developers.com/showthread.php?t=1307539#

erica_renee said:
Hi ..
Not sure what he done.But it sounds like this will fix this issue for you..
Just follow this link good luck
http://forum.xda-developers.com/showthread.php?t=1307539#
Click to expand...
Click to collapse
Thanks for your response and it DOES look like it would work... IF I could access anything on the tablet - like enabling USB Debugging, etc. I can't get to it. What I need is something I can flash or boot right from the SD card as that's the only thing I have access to.

with this you do not need to have access to nothing. Download the file From the thread above to your windows pc. OPEN THE Zip file. it will have all the tools and A VERY DETAILED set of instructions. Find the instruction file and fallow it.
Many people have used this with ease. If you want help just flashing another.zip file. post the rom that was on the tablet . the recovery installed as well.

erica_renee said:
with this you do not need to have access to nothing. Download the file From the thread above to your windows pc. OPEN THE Zip file. it will have all the tools and A VERY DETAILED set of instructions. Find the instruction file and fallow it.
Many people have used this with ease. If you want help just flashing another.zip file. post the rom that was on the tablet . the recovery installed as well.
Click to expand...
Click to collapse
OK, I tried it out and it doesn't pick up the tablet as I don't think USB debugging is enabled and I have no way to enable it. That's why I'm asking for a method to flash it from the SD card.
BTW, I found the S/N inside the SD card door.

You could try decrypting one of the update roms;
http://forum.xda-developers.com/showthread.php?t=1113878
Note that some are encrypted, and you have to de-crypt with the tool listed there.
Extract and copy the update.zip. Copy to SD.
Boot by vol- or vol+, and see if it will install.
There are a couple of other tips in the threads, like toggling the button for Portrait lock, to force the tab to start formatting.

Moscow Desire said:
You could try decrypting one of the update roms;
http://forum.xda-developers.com/showthread.php?t=1113878
Note that some are encrypted, and you have to de-crypt with the tool listed there.
Extract and copy the update.zip. Copy to SD.
Boot by vol- or vol+, and see if it will install.
There are a couple of other tips in the threads, like toggling the button for Portrait lock, to force the tab to start formatting.
Click to expand...
Click to collapse
Thanks VERY much! I swear I must have tried these before and they didn't work. However, I missed one important step - unzipping the update.zip from the file! DOH! I feel really stupid but the tablet is running 100% perfectly.
Again, my most sincere thanks!

gjtoth said:
Thanks VERY much! I swear I must have tried these before and they didn't work. However, I missed one important step - unzipping the update.zip from the file! DOH! I feel really stupid but the tablet is running 100% perfectly.
Again, my most sincere thanks!
Click to expand...
Click to collapse
Hey, really, it's no problem. Glad we all could help get you up and running.
No, I haven't used that method, since my HTC desire. Same principle though.
I'd tell you the principle behind it, but it's rather long.
Glad you got it going.
My pals and I, are launching a new site. Hopefully it will be for people not so technically PHD'd with android. Not quite so technical as XDA. You're more than welcome to place some info, when we launch. It's more community orientated, so a different venue.
XDA, is, and always will be the place to come for the really technical stuff. As you see, there are users here, which will give you what they know. May not always be the fix, but, some people here "do" care.

Moscow Desire said:
Hey, really, it's no problem. Glad we all could help get you up and running.
No, I haven't used that method, since my HTC desire. Same principle though.
I'd tell you the principle behind it, but it's rather long.
Glad you got it going.
My pals and I, are launching a new site. Hopefully it will be for people not so technically PHD'd with android. Not quite so technical as XDA. You're more than welcome to place some info, when we launch. It's more community orientated, so a different venue.
XDA, is, and always will be the place to come for the really technical stuff. As you see, there are users here, which will give you what they know. May not always be the fix, but, some people here "do" care.
Click to expand...
Click to collapse
Be happy to check it out. While I don't have a lot of tech savvy in Android, XDA has been my "go to" for almost all things Android for MY A500. While I can't contribute much (if anything ), I have sure picked up a wealth of help/tips here.

gjtoth said:
Be happy to check it out. While I don't have a lot of tech savvy in Android, XDA has been my "go to" for almost all things Android for MY A500. While I can't contribute much (if anything ), I have sure picked up a wealth of help/tips here.
Click to expand...
Click to collapse
Hey, we all start "somewhere".
Androidtabletgeeks.com And remind you, it is not competition. Just an alternative.
Officially, it has not launched. Still working on tutorial videos and such. Like I said, it's a different venue.
We all start somewhere......

Moscow Desire said:
Hey, we all start "somewhere".
Androidtabletgeeks.com And remind you, it is not competition. Just an alternative.
Officially, it has not launched. Still working on tutorial videos and such. Like I said, it's a different venue.
We all start somewhere......
Click to expand...
Click to collapse
I peaked very nice.hope you don't mind.
Did not reg.

erica_renee said:
I peaked very nice.hope you don't mind.
Did not reg.
Click to expand...
Click to collapse
No problem. Still have tons of video tutorials to make.

Moscow Desire said:
You could try decrypting one of the update roms;
http://forum.xda-developers.com/showthread.php?t=1113878
Note that some are encrypted, and you have to de-crypt with the tool listed there.
Extract and copy the update.zip. Copy to SD.
Boot by vol- or vol+, and see if it will install.
There are a couple of other tips in the threads, like toggling the button for Portrait lock, to force the tab to start formatting.
Click to expand...
Click to collapse
MD, i was unable to download any of the 3.0.1 update files. When i click on the link it takes me to some xml tree. is there any other place where i could download?

Bricked??
Hello All,
I was running ICS ota on my a500, I am trying to boot with recovery, and it gives me an icon of android with gears and reboots, with the following error:
Not legal! Abort
The blob package is not official ~Abort!
After which it just shows the word android and blinks every few seconds.
My a500 was not rooted.
I tried afew things posted on the forums, civato method, downloading a previous OTA and running it. nothing works.
Please help....

When i start up normally the screen shows the word ANDROID and stay`s on that.
volume down and power android puppet with exclamation mark.
Volume up and power give`s me the menus skrilax bootloader V6 reboot- fastboot mode – Boot recovery – Set Boot secondary Kernel image – Set Debug mode on – Wipe cache.
I have tried all options.
Finally holding reset and power button down and after 3 sec release power and 1 sec after that the reset
When I use Blackthund3r`s flashtool v0.4 I get the message no APX mode devices are connected.
Can you help me out? Preferably whit a Dutch recover.
Many thanks in advance

Lost all hope...

It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD

shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.

Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD

cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.

Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.

Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.

im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire

lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!

chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!

Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse

tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!

[Q] How (im)possible is it to brick the N4?

As long as you can get into fastboot mode, you haven't bricked your device
Click to expand...
Click to collapse
Is this statement true?
I know it isn't impossible to brick your device to the point of no return. I've actually done it myself (huray!) with my Nexus S. It was declared dead even by AdamOutler himself, the maker of the Unbrickable Resurrector. After trying to unbrick it myself, I sent it to him. Apparently I screwed up the radio, a mistake which is impossible to recover from. Don't ask me how I did it... I did flash something before, but my phone worked fine for a while. Only then the battery drained really quickly. When it was dead and I plugged in the charger, it booted up fine, but the moment I started the browser my Nexus S died. Forever. RIP.
I guess it's no different with the N4. If you screw up the radio, you have a problem. Can somebody confirm this? And are there other ways to brick your phone to the point of no return?
I think it's kind of stupid that you are able to brick your phone. You can't brick a PC, can you? That's just impossible. You can ALWAYS completely reset everything. Well, not with Android apparently. I think it's weird that even with Nexus devices, there's still a way to brick it. I guess you need to be stupid like me to brick a Nexus device, but still... it shouldn't be possible.

Yes as long as bootloader mode is able to be started! You cannot brick. Just flash google stock factory images.
Sent from my Nexus 4 using xda premium

Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.

Hah, I've bricked PC's with BIOS flash fails.
But as for the phone, as long as you can enter fastboot, you are able to recover.

Harry GT-S5830 said:
Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.
Click to expand...
Click to collapse
You can? Ah, then I rest my case.
I did screw up the radio though, and not the bootloader. I was able to get into download mode using the resurrector tool, only the screen stayed black.\
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.

You could think of it as the bootloader = the BIOS and Android = Windows

Androyed said:
[snip]
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.
Click to expand...
Click to collapse
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.

You could always delete your bootloader, thall brick your device pretty fast

efrant said:
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.
Click to expand...
Click to collapse
Very true. For an example, Check out the HD2 phone and the various bootloaders available for it. I have booted Windows Mobile 6 and 7, Ubuntu, oh.. and Android on it. It was originally a WM6 phone. It also has the ability to change partition sizes, and has an sBoot partition so it can do a true dual boot. One from Nand memory and one from SD card with just a reboot.
I waiting to see if we get a way to flash unsigned bootloaders on Nexus 4 (or get a key).

I seem to recall a few devices being bricked in the few days after release. There was a problem with the faux kernel that caused the device to totally and irreparably brick if one overclocked (to 1.8Ghz I think) and then ran an antutu benchmark.
The few could not recover from the brick despite a lot of suggestions thrown around and some even from the dev of the kernel. Ultimately, they RMA'd.

Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2011328
Many users seen to have bricked their devices by overclocking their CPUs and running benchmarks.
Heck, I even see people talking about the red LED problem daily. Something's clearly not right...
Sent from my Nexus 4 using Tapatalk 2

The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.

Lownita said:
The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.
Click to expand...
Click to collapse
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.

Nuu~ said:
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.
Click to expand...
Click to collapse
There is the point.
Bricking by software alone will be almost impossible. I have seen a few flashing bricks recovered already.
Bricking by damaging the hardware, well, that is probably unrecoverable. Over Clocking or O/C + Over-Heat is causing what seems to be permanent damage in some phones.

fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?

I don't think anyone has the QCOM_USB_DLD mode figure out yet and I don't think anyone knows what secure boot does either, I know originally people blamed it for custom recoveries being reverted, but that's just a script that's called on bootup.

molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
I've seen that on my Nexus S... after I had bricked it completely ;p. I don't think it had anything to do with the brick though. It's something from HTC devices: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/. At least I think so.
When I tried to repair my bricked Nexus S, I asked if it had something to do with secure: on. They didn't know what it was exactly, so maybe it isn't the same as s-on on HTC devices.

molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
Click to expand...
Click to collapse
Pure speculation on my part: I think that the "secure boot: on" relates to the boot chain of the Snapdragon SoC. When it's on, I think that it will not boot an unsigned bootloader, and hence you cannot boot the device. Similar to, but not quite the same as, S-ON for HTC devices as was mentioned above.
molesarecoming said:
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
More speculation: I haven't had much time to look into it yet, but I'm guessing that you should be able to flash a .tot file (an LG "factory image" I think like the ones found here) while you are in download mode. I think it requires something like the LGNPST tool with the right .dll. This is my first LG device (and my first Snapdragon SoC), so I'm still in the reading/learning stages.

[Q] Another bricked A501

Noob, here. I have a small computer repair business and offered to take a look at a friend's A501. I am quite embarrassed to admit it, but I have searched through these (and other) forums and I am clueless. Due to my complete ignorance, I fear I may have made matters worse by becoming flash happy. Would anyone be able to give me *very* remedial instructions for what to try? I have no idea what the CUID is or how to obtain it, and I know nothing more about the machine than what I am able to extract by looking at it. Humbly, Anne
Let me add that I have searched and tried to follow the instructions on many other posts on this subject, I believe that haven't been successful because it seems that there is a prior knowlege/familiarity required with the OS/device that I don't have. Thanks again.

annenap said:
Noob, here. I have a small computer repair business and offered to take a look at a friend's A501. I am quite embarrassed to admit it, but I have searched through these (and other) forums and I am clueless. Due to my complete ignorance, I fear I may have made matters worse by becoming flash happy. Would anyone be able to give me *very* remedial instructions for what to try? I have no idea what the CUID is or how to obtain it, and I know nothing more about the machine than what I am able to extract by looking at it. Humbly, Anne
Let me add that I have searched and tried to follow the instructions on many other posts on this subject, I believe that haven't been successful because it seems that there is a prior knowlege/familiarity required with the OS/device that I don't have. Thanks again.
Click to expand...
Click to collapse
hehehe 'flash happy' welcome to the club!!! Yes the acer is a strange beast, luckily though its fairly 'unbrickable' unless your tab suffers from the hardware fault prob.
There are a couple of guides in my sig you should look at before attempting a fix.
The cpuid guide for a start, there are quite a few different ways of retrieving this - its all explained in the OP.
The root guide is a500 based, but everything will work for the 501 and has links to all the tools you will need
You don't say whats actually wrong with the tab - does it boot still, is there a custom recovery (power vol down buttons) on there and can you boot to that?
The more info you can give the easier it will be to provide the best solution
rgds donna

dibb_nz said:
hehehe 'flash happy' welcome to the club!!! Yes the acer is a strange beast, luckily though its fairly 'unbrickable' unless your tab suffers from the hardware fault prob.
There are a couple of guides in my sig you should look at before attempting a fix.
The cpuid guide for a start, there are quite a few different ways of retrieving this - its all explained in the OP.
The root guide is a500 based, but everything will work for the 501 and has links to all the tools you will need
You don't say whats actually wrong with the tab - does it boot still, is there a custom recovery (power vol down buttons) on there and can you boot to that?
The more info you can give the easier it will be to provide the best solution
rgds donna
Click to expand...
Click to collapse
Hi Donna-
Yeah, I guess explaining what it's doing might be helpful. Right now, if I just power it up, the acer logo is in the center and in top left corner is "boot verified failed" in red.
Power + vol up, displays in the top left corner:
erasing cache before sd update
sd update cmd: recovery
update package=sd card update.zip
booting recovery kernel image
then it shows the android guy working then the android guy dead
I'll take a stab at determining the CPUID tomorrow.
Thanks again.

annenap said:
Hi Donna-
Yeah, I guess explaining what it's doing might be helpful. Right now, if I just power it up, the acer logo is in the center and in top left corner is "boot verified failed" in red.
Power + vol up, displays in the top left corner:
erasing cache before sd update
sd update cmd: recovery
update package=sd card update.zip
booting recovery kernel image
then it shows the android guy working then the android guy dead
I'll take a stab at determining the CPUID tomorrow.
Thanks again.
Click to expand...
Click to collapse
EDIT: I'm just uploading a 501 update.zip - the 500 will work ok you just won't have 3G
I'll post a link when its done
ok you might be able to get fixed by heading to the root guide in my sig.
download the 3.1 FULL update.zip - rename it to update.zip and make sure it doesn't end up as update.zip.zip
Copy it to your external sd card
Start the update by Pwr and vol up
If it works your tab will be back on HC 3.1
Grab your CPUID - its the easiest way
From there you can get system updates all the way to ICS OR
Install the v8 bootloader to flash any ICS/JB roms
If it doesn' work you will need that CPUID
Good Luck m8!!
rgds donna

[Q] Seeks Expert Help on Bricked ATT LG G2 using Straight Talk Sim

Elite thanks in advance. No, seriously, thanks. I'm a broke single parent of 2 kids and I realized my phone is about my only guilty pleasure after giving my kids 200% of my time and money. Any help would be appreciated.
I have an LG G2 that I apparently bricked by using an app to "freeze" the latest OTA software update that was pushed to my ATT LG G2 about a month + ago if not slightly longer. I unfroze the process and the update suddenly appeared and said it would reboot the phone and or apply the update it in 30 seconds. I panicked and held the power button in to turn the phone off.
Once the phone was turned back on I was greeted with tiny white text that said "error: Boot certification verify" From here I was unable to get into down load mode, do a hard reset. I was able to see fast boot mode but wasn't sure what to do with it. I was able to see the phone in Windows 7 Pro Sp1 device manager but it was listed as QHSUSB_BULK
After initially freaking out which lasted about 20 mins, I was able to compose myself and start researching my new seemingly serious problem. After a few hours of reading a dozen or so treads / hundreds of replies it seemed I would have to load into Ubuntu and push some files to my LG G2.
I followed this guide - http://forum.xda-developers.com/showthread.php?t=2582142
I was very careful to follow this guide to the letter and everything went as expected the first, 2nd and 3rd time only the results were worse and worse and worse.
The first time I lost fast boot, the 2nd time I lost the boot certification verify error, After the 3rd attempt I get a split second LG Logo and that's it. What did I do during those 3 attempts? The first time, the 4 files and the recovery as directed. The 2nd time, the same files, plus the boot.img and a different recovery. The 3rd time, all the files and yet a different recovery. All the files were pulled from here - http://downloads.codefi.re/autoprime/LG/LG_G2/D800
The other recovery.imgs were for the correct model, just older, newer variants. I was very careful to push the right files to the right partitions.
I can still see the phone via Ubuntu. I'm scared to do anything else along the lines of what I've been doing. In fact I'm lost as to what to do next.
Can anyone here help me push more / different files via Ubuntu that would help bring my phone back to life? I'm completely dead in the water. Or perhaps an exe package / program that can fix my problem? If I sound stupid, it's because this is all new to me.
Thanks in advance, Tom

@rthefley Go back to the autoprime downloads and get the boot, aboot and laf image. Follow the ubuntu guide and flash those images only.

@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.

rthefley said:
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
Click to expand...
Click to collapse
In that case, you should try to push a recovery image, too!

Raymonf said:
In that case, you should try to push a recovery image, too!
Click to expand...
Click to collapse
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.

rthefley said:
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
Click to expand...
Click to collapse
Did you lokify them?

Raymonf said:
Did you lokify them?
Click to expand...
Click to collapse
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom

rthefley said:
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
Click to expand...
Click to collapse
Okay, are you now able to go into download mode?

1127
Art Vanderlay said:
Okay, are you now able to go into download mode?
Click to expand...
Click to collapse
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu

rthefley said:
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
Click to expand...
Click to collapse
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.

Art Vanderlay said:
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Click to expand...
Click to collapse
Yes I'm pretty sure it's completely powered off. I will try again but I've held the power button in for several several seconds and saw the screen go solid black. I've flashed those 3 files just as instructed. Nothing is working sadly. Maybe I am missing some key procedure others take for granted that I just personally do not know about
Is there anything else I could try doing? I'm going in circles here.

Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk

LilDemon124 said:
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
No they are different, I actually gdisked all of the different letters but I have an sda,c,b and e, I even have have an sde1. All the numbers follow sde however up to 42 or 43. So when I gdisk -l /dev/sde that's when I see all the files.
I've tried to gdisk sdb but I get a mbr / gpt or something error saying something is corrupted so I just leave it alone.
Should I be looking at a different letter then? If so, I can't seem to get into any of them other than the one I mentioned, sde

Guys, I'm now offering a $40 paypal bounty directly to your pocket or a donation to this web site for help allowing me to get back into my phone.

I will try my best to help you. Im at work, but will be home soon so that I can do some snooping.. From what your saying you MIGHT have a corrupt storage OR you might have a corrupt file.
Sent from my LG-LS980 using Tapatalk

Im going to have to work on this a bit later. Worked all day. I'm still here and around just need to get a little sleep before I even think of trying to dive into this again. Thanks.