Database Users

[Q] Looks like I hard bricked it...

My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.

hayatohuseman said:
My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.
Click to expand...
Click to collapse
That definetly doesn't sound like a hard brick. Use romracers recovery and try to flash a fruitcake http://forum.xda-developers.com/showthread.php?t=1163009 which are much safer then sbfs.
By the way theres no need to apologize when posting in the "correct" forum .General or QandA is where this thread belongs. if this were development though then you'd be in a world of ****! LOL

if you are on big M (without any "failed to boot" ) you're soft bricked,
try to power on button+ volume down button...
if says "fastboot" then just volume up,
download the .img files in the fruitcakes section and follow the fastboot mode instructions...
you'll get back your phone.
read carefully the instruction where to put the files in your windows 7 user directory etc etc, 90% of the problem is because people don't understand where to place executables and run them
hope it helps

Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!

hayatohuseman said:
Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!
Click to expand...
Click to collapse
Kudos for doing some research and figuring out how to resolve the problem. Not enough of that going on. Doesn't it feel like more of an accomplishment?!

KeRmiT80 said:
follow the fastboot mode instructions...
you'll get back your phone.
Click to expand...
Click to collapse
hayatohuseman said:
all I had to do was flash to 2.3.4 with moto-fastboot
Click to expand...
Click to collapse
* 10chars

Unresponsive Device

So, I had been using my A500 for the last few days with no problems. Well, yesterday, I got home from work and powered it on. The lockscreen came up, but the screen was unresponsive. I turned it off and then back on, but screen still didn't work. Then I did a hard reset, which still didn't fix the problem. I put it into recovery, then did a wipe that still didn't fix the issue. I flashed the ROM again. Then a different ROM. All it does is is boot up and go to the lock screen, but the screen does not respond.
If I can avoid it, I don't really want to go through the hassle of returning it since I got it online. Hopefully it can be fixed without having to take it back. Thanks in advance for everyone's help.

Boot back into recovery.
Wipe your 3 things,
User Data
Cache
Dalvik
Then go to Mounts
Format the same 3 (user data, cache partition and Dalvak.
And Flexrom
Then flash your rom. Try and flash a basic rooted rom. No kernels, no gapps.zip
See what happens.
If you have a file called update.zip, on your sd, I would delete it. And anything else there except for the rom.

sounds like hardware failure. Has the tablet been dropped or banged around. The connector on the digitizer could have came loose.That would mean void warranty and take it apart ..
Send it back is likely your. Best option

Thanks for the quick responses! I'm gonna try these things, hopefully I don't have to take it back.

Guess it is a massive hardware failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.

sikkboy626 said:
Guess it is a massive software failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
Click to expand...
Click to collapse
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.

Moscow Desire said:
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Click to expand...
Click to collapse
Thanks for all your help. I was able to get it back to stock. The return should go fine. You're awesome and I did not forget to use the thank you button.

have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure

You can use normal usb mouse with this tablet, you will get mouse pointer on the screen when you connect mouse...

erica_renee said:
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
Click to expand...
Click to collapse
I was able to flash using the physical buttons. I got it all back to factory specs so I can return it. you were correct I believe, it does seem to be a screen hardware failure. Everything else works but the touch response.

Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo

erica_renee said:
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
Click to expand...
Click to collapse
Guess I had to take one for the team

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!

Semi-bricked DHD

Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James

This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.

Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James

There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.

Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James

Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice

Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James

[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.