[Q] [CM10] [Brick] After CM10 stable Update: Bricked device(?) / HW issues - LG Optimus Black

Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?

Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didnĀ“t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.

Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/

Hardware problem.

That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??

Related

[Q] Won't start unless plugged

It won't start unless plugged it shows empty battery. sometimes when i unplug it stays connected. In usb settings if choose mass storage it seems to get in a loop of connect-disconnect. I have tried flashing different roms but it didn't fix. Any idea of what is happening? Could it be hardware problem?
I've got the same problem, I've tried every kind of wipe, flash with repartition, clearing stats and so on. I'm starting to suspect it's a hardware issue. The Phone seems to always think it's plugged into USB no matter what, it keeps rebooting to the battery icon over and over until I plug it onto a power source and then it boots fine.
After that I can get it back to normalish by rebooting with the power disconnected using the extended power menu in Darkys Rom.
Can anyone help? When I get back from my trip I'll likely flash it back to stock and send it in for repair, or just ***** at bell and get another new phone.
I'm having the same issue, I've searched all over internet and I found other posts with the same problem.. and no one has found a solution for this.
I think is a hardware problem. after having this I've bought a chinese compatible battery, and when I put that battery in, the phone boots up without even pressing the power on button, so weeeird!
With the original one.. there is no way to boot up without plug the phone. I've had the phone working well for more than 5 months
if someone finds a solution please tell!
thanks in advanced!
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
grofudaniel said:
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
Click to expand...
Click to collapse
what did you did? so do you think it's a software problem?
I tried to use a non-original battery and when I put in this new battery, the phone boots up without even press any button. so something it's really wrong. if I try the same with the original battery.. nothing happens, the screen is black unless I plug the phone to the charger.
well, at least I can boot my phone without plugging it this way.
I look forward to know more details about this issue.
thanks!
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
JJEgan said:
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
Click to expand...
Click to collapse
unfortunately I've done the search in this forum and I haven't found any solution for this, I can't believe it!
regards!
This problem is back again. I can`t start the phone unless it is plugged. I am with the nervs down at this moment.
what makes me crazy is to not know if it's a software or hardware failure!
in my case seems to be a hardware problem unless the phone recognize the non original battery and that makes a software change that makes the phone to boot.
I'll wait until the gingerbread update, and if after update it doesn't work, I will bring the phone to samsung repair point.
I see that I'm not alone with this problem.
Maby if i could connect the phone on usb to pc i would do something but that dosent work either for me so god have mercy.
I had that problem for a few weeks. Went away with a firmware change. Flashed back to stock and then docs rom. No idea what it was. Just went away.
Are you sure the battery is charged? I had the exact same problem on cm7, turned out my battery ran flat overnight
Sent from my GT-I9000 using XDA Premium App
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
KeesKaas said:
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
Click to expand...
Click to collapse
OK, I'll do that thanks for the suggestion.
I only have one more doubt left, If I do that, after formating everything in clockworkmod.. What does it happens to the phone? is it going to be able to boot after formating all of this? I'm asking this because I don't know how to download the official rom without using kies and the phone booted up and connected via usb cable.
thanks so much!
I've got the same problem.
I thought it was me trying to flash JVK, but after flashing and reflashing 2.2.1 and 2.3.3 and back with bootloaders the problem stayed. I'll try the format "everything" from CWM, hope this will work.
Still abit strange
(BTW I recently was in sub 15 degrees temperatures, surely this isn't the case??)
I had a problem like this where I was getting USB connected coming up again and again and my phone not starting when it wasn't plugged in.
This sounds dumb and I may just have been lucky but I turned USB debugging off and it stopped, left it off for a day or so, a couple restarts later I thought I'd see if it was still playing up so re-enabled it and nope everything's ok again. That was a couple weeks ago and so far so good, I hadn't seen any reports of anyone else with this.
Might be worth a try
Oh I'm using Darkys 9.5 by the way
My problem got worst! My phone would not charge at all until i reflashed. It now charge and boot normaly without to have it plugged, but my pc don't recognize it, not even in download mode with odin. I quess it has something to do with the hardwhare because both times the problem started when i charged it in the same plug.
i had the same problem,I just cleaned the usb port,plugged in the cable without connecting it to the pc or power source,and it started now it's ok
Me too
Another victim of this issue.
I was running a Darky Rom when I first noticed it... I think I was on Ficeto's 2.3.5 JVT. s
I have tried several steps to rid myself of this issue, with no success:
1. Reflashed ROM CWM
2. Reflashed Kernal CWM
3. Factory Reset, format internal SD, & ODIN flash Stock ROM.
4. Wipe & Flash Juwe ROM.
5. Each time, I also wiped the Dalvik Cache and battery stats.
I have tried leaving the battery out for a lengthy period, I have tried draining the battery all the way down, charging all the way up.
At least with the Launcher I am using now, it has the "Reboot" option instead of just turn off. However, I have to make sure I have a USB cable close by and charger in the car all the time now, just in case it runs out of juice or locks up for some reason and needs a battery pull.
Frustrating... Of course, the warranty expired the end of October.
If anyone has successfully completed the recommendation of formatting boot, system, data and cache and flashing stock Froyo? If you have done it, PLEASE post your detailed steps and the result so we don't waste time repeating something that won't work.
I was eyeing the SGS 2, but with all of the issues the market went through with the SGS, I am thinking maybe I should get away from Samsung...
MM

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

[Q] Cannot Enter Recovery Mode

Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Bump
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
NoDze said:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
Click to expand...
Click to collapse
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
xda_fanboy said:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
Click to expand...
Click to collapse
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.
I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,
EDIT: somehow from the countless attempt it fired up.
Make sure to have the right bootloader before nvflashing unbrick roms....
xda_fanboy said:
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Click to expand...
Click to collapse
Try to flash a new recovery image in apx mode.
And edit the /dev/block/mmcblk0p3 partition your self.
seek=6144 count=75 bs=1 / boot-recovery
Thanks for the added input and encouragement folks.
Just reporting an update:
Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.
Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm
Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!

No input possible at CM11

I installed CM11 last monday from this thread: http://forum.xda-developers.com/showthread.php?t=2658534
Since then I got the issue, that after the phone is in standby for a while, I can't unlock the lockscreen. There is no input possible, just reacts like I'm not touching the screen. If I press the power button again it locks again (screen off), but then it's not possible to even see the lockscreen again, powerbutton not working anymore. The only way to use the phone again is to hold the powerbutton for 10 seconds and reboot then.
I tried to wipe all and flash again, but no change. I tried "cm-11-20140503-UNOFFICIAL-jactiveltexx.zip" from spegelius first, and then "cm-11-20140508-UNOFFICIAL-jactiveltexx.zip" from allram. Wiped everything before flashing, but no luck, still getting that bug.
Sadly I can't post directly into that topic, because I'm new here
:DDDDDDDD said:
I installed CM11 last monday from this thread: http://forum.xda-developers.com/showthread.php?t=2658534
Since then I got the issue, that after the phone is in standby for a while, I can't unlock the lockscreen. There is no input possible, just reacts like I'm not touching the screen. If I press the power button again it locks again (screen off), but then it's not possible to even see the lockscreen again, powerbutton not working anymore. The only way to use the phone again is to hold the powerbutton for 10 seconds and reboot then.
I tried to wipe all and flash again, but no change. I tried "cm-11-20140503-UNOFFICIAL-jactiveltexx.zip" from spegelius first, and then "cm-11-20140508-UNOFFICIAL-jactiveltexx.zip" from allram. Wiped everything before flashing, but no luck, still getting that bug.
Sadly I can't post directly into that topic, because I'm new here
Click to expand...
Click to collapse
I suppose you have Gt-I9295 not US version of the phone?
When you flashed the zip. did u do a factory reset? and format /system /cache?
allram said:
I suppose you have Gt-I9295 not US version of the phone?
When you flashed the zip. did u do a factory reset? and format /system /cache?
Click to expand...
Click to collapse
Yes I got the european version. Before I flashed CM11 I did a "factory reset", wiped cache and dalvik cache. I did that before flashing another rom again. I will try to flash the newest (13th may) version from your gdrive later.
:DDDDDDDD said:
I installed CM11 last monday from this thread: http://forum.xda-developers.com/showthread.php?t=2658534
Since then I got the issue, that after the phone is in standby for a while, I can't unlock the lockscreen. There is no input possible, just reacts like I'm not touching the screen. If I press the power button again it locks again (screen off), but then it's not possible to even see the lockscreen again, powerbutton not working anymore. The only way to use the phone again is to hold the powerbutton for 10 seconds and reboot then.
I tried to wipe all and flash again, but no change. I tried "cm-11-20140503-UNOFFICIAL-jactiveltexx.zip" from spegelius first, and then "cm-11-20140508-UNOFFICIAL-jactiveltexx.zip" from allram. Wiped everything before flashing, but no luck, still getting that bug.
Sadly I can't post directly into that topic, because I'm new here
Click to expand...
Click to collapse
You should also use CWM 6.0.4.7...?

TX shutting down whenever entering system

Hi, this is my first post. I have tried to search and look through the question threads, but nothing seems to be close to the problem I have here, hoping someone can help me.
I have this Xperia TX, recently given by my friend, it can boot up ->sony->ribbon-> entering system->shutting down, it's not like a sudden blackout but more like a command sent telling the phone to shut down, it has the window saying shutting down and vibration at the end, but the shutting down is instant, can't operate yet. I made several approaches trying to fix it, these are what I have been done with it.
-Flashing different stock ROMs using flashtool, the flashing went perfectly without errors, and phone will boot and install new system until the setup wizard (languages, time etc) comes out on screen, and it shuts down right away.
-I used flashtool to unlock BL, succeeded.
-I flashed TWRP, it can boot into TWRP without any problems and working fine.
-I formatted the phone partitions using TWRP, working fine.
-I flashed cm-12.1-20151010, and same thing happened as soon as the system launcher comes out.
-And I flashed stock ROM again, the problem remains.
The phone won't charge the battery, so I tried using a separate charger avoiding 0 battery situation (I do see the battery icon showing 50%+ when it shutting down), and I also tried another lt18i battery (don't want to buy a new one yet in case the phone is dying), and there is no different.
I don't understand the problem, all the operations work fine but can't boot in system, doesn't seem like a hardware thing but what else can it be? I am not hoping to fix it any more at this point, but can anyone tell me what could possibly cause this? Can I read a boot up log somewhere so that I know what happens during booting?
I hope I didn't break any routine or do anything wrong here, if I did, apologies in advance, thank you.

Categories

Resources