Hello, everybody.
I would like to ask you my first question on this forum, regarding my LG Optimus G Pro E988. My wife been using it within a year or so, and she didn't find any trouble with it. Until a week ago, she said to me that the phone keep restarting itself, three times. Then I tried to solve it with cable power attached, problem solved. I don't know why. I think it's not the battery, because it's charging normally while attached. But when the cable power is not connected, the phone keep boot-looping.
I tried to factory reset (hard reset) with combination keys, the problem remain unsolved.
I tried to flash the phone to stock ROM with flash tool provided in this site (the OP seems reliable). Note that the device isn't rooted. The result are:
When cable power connected, phone will boot up perfectly, but a few clicks later it turn off (without shutdown animation)
When USB cable connected, sometimes phone will behave exactly same with first condition, but sometime it's enter boot loop
When no cable connected, phone doesn't even finish boot animation, it shutdown in the way of it.
I just wanna know, what problem that i'm facing? Hardware or software?
If the hardware, what is it? Is it worth to replace?
If the software, what should I try to fix?
I'm here waiting answer. Thanks a lot for your help.
Note. I'm already try these:
Hard Reset
Flash with stock KDZ
Wipe partition with a script provided in this forum (in recovery mode)
Related
Dear all,
Desperately need help and deeply appreciate if anyone could shed some light.
I recently upgrade my rom. The rom upgrade without problem, after I installed couple of applications, the phone was hang after restart.
I tried re-flashing the rom couple times and it seems everytime restart, the rom will hang.
After several re-flashing, my phone now stuck at the screen where, it stated, system is being configure and stuck on this screen forever.
I tried reset the rom by Vol-down & back key as well as vol-down & center key, Rom upgrade completed successfully but upon phone restart, my phone keep stuck at the same screen.
I do noticed that, by resetting the phone into bootloader mode (reset with Vol-Down, back key) with USB cable attached to my phone, the bootloader detected USB connection but time out.
Is there any software which I should install on my laptop which allow me to transfer another diamimg.nbh to this phone?
Thank you
decent_devil said:
Dear all,
Desperately need help and deeply appreciate if anyone could shed some light.
I recently upgrade my rom. The rom upgrade without problem, after I installed couple of applications, the phone was hang after restart.
I tried re-flashing the rom couple times and it seems everytime restart, the rom will hang.
After several re-flashing, my phone now stuck at the screen where, it stated, system is being configure and stuck on this screen forever.
I tried reset the rom by Vol-down & back key as well as vol-down & center key, Rom upgrade completed successfully but upon phone restart, my phone keep stuck at the same screen.
I do noticed that, by resetting the phone into bootloader mode (reset with Vol-Down, back key) with USB cable attached to my phone, the bootloader detected USB connection but time out.
Is there any software which I should install on my laptop which allow me to transfer another diamimg.nbh to this phone?
Thank you
Click to expand...
Click to collapse
you should try mtty...it formats your phone and solves all the problem like the yours..a guide to use it is in a sticky thread
or you can try downloading any rom and usually the chef includes a file called customRUU.exe..put your phone in bootloader mode then flash trough customRUU.exe
HELICOPTER88 said:
you should try mtty...it formats your phone and solves all the problem like the yours..a guide to use it is in a sticky thread
or you can try downloading any rom and usually the chef includes a file called customRUU.exe..put your phone in bootloader mode then flash trough customRUU.exe
Click to expand...
Click to collapse
Thanks, Managed to extract one Rom and restore my phone via customRUU.exe.
Hi!
My Xperia (with Cyanogenmod 9.1 ROM) started to behave in an unstable way a week ago, for no apparent reason. The screen would start to freeze and the only way I had to reboot the phone would be to remove the battery and put it back again. Sometimes the screen would show what I presume to be heavy screen corruption, like in the image I attached to this post.
Yesterday, the battery removal trick stopped working. Basically, the phone boots into the FreeXperia Project logo and then nothing shows up. The screen goes black into screen saving mode and if I touch the power button again, an image like the attached one appears.
I tried to reinstall the CyanogenMod ROM following the instructions you can see over wiki.cyanogenmod.org/w/Install_CM_for_zeus.
All goes well up to the point I press the Volume rockers to get into ClockworkMod Recovery mode. Instead of the Recovery Menu, all I get is an image like the one I attached.
Any ideas on how to solve this problem?
Thanks in advance for your help.
Your flex cable is damaged, you will need to change it with a new one, for buying it, go here:
http://www.ebay.es/itm/Replacement-...e_Replacement_Parts_Tools&hash=item27ce40c39b
Thank you for you reply.
I thought it was a software problem, since the screen seemed to work well when the FreeXperia Project logo showed up.
Still have to decide if I have the guts to open my Xperia to fix it or send it for repair. I know there are some tutorials on Youtube showing how to do it, but I am not sure if I have a firm hand to do it without damaging anything else.
Once again thank you for your reply.
I agree that is most likely flex problem, but you try to flash stock firmware and see is software or hardware problem.
If it is the same on stock firmware, then it's flex 100%
Bakisha said:
I agree that is most likely flex problem, but you try to flash stock firmware and see is software or hardware problem.
If it is the same on stock firmware, then it's flex 100%
Click to expand...
Click to collapse
I am going to try to flash the phone with another ROM. If the problem continues I am going to replace the flex cable.
Thanks for the help!
Yup, it's the flex cable
Just an update. I turned on the phone again today, before starting to open it to replace the flex cable and the phone started to boot normally. It was functioning properly until I slid the pad. The screen stopped updating immediatly.
I think this confirms the problem is the flex cable.
Once again, thanks for your help!
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON. The device had never been Rooted or tampered with previously.
So now the phone does not boot at all. I've tried every button combination, but nothing seems to work. If I plug in the phone to charge the orange light flashes, endlessly. Even after I've left the device to charge for 6hours, the orange light still flashes.
When I plug in the phone to my PC, all I get it seems is this new device: QHSUSB_BULK, which shows with an exclamation mark next to it. I've read similar threads for different phones where they've unbricked devices while they were in this mode, is that even possible? I can hear Windows recognizing a device was plugged in, and if I press Power+VolumeUP, it will disconnect the phone and reconnect it, at least based on the sounds Windows is playing. The screen is Black at all times.
How badly have I bricked this device and is there any hope to revive it? Thanks to everyone who chimes in on this.
arrayy said:
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON.
Click to expand...
Click to collapse
Most likely it's a soft break. So you can fix it. First of all get yourself a working usb cable. Your's maybe broken.
Your phone's data partition had been encrypted. It never boots up completely without lux password. You could've format the data partition with a custom recovery such as TWRP. Instead you tried the reflash firmware but obviously it didn't finish and failed. All you need is reflash again but doing it correct way so it can finish. Your old data is gone atm. You will have factory reset phone at the end. Before giving you any instructions, you need to answer a few questions so anyone can help.
Have you ever updated your phone to marshmallow which is android 6? If no: You can recover it with voidzero's wonderful answer titled back to stock. Follow that exactly. If yes you can't flash old versions since they are using different bootloaders. Also you will have to reflash it manually. It's long and difficult for anyone who is new. If you don't know if it was updated. Just boot into bootloader then Fastboot mode, connect usb. Then use htc's Fastboot. Run htc_fastboot getvar all command. Paste output here.
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader using the Power+VolumeUP keys, or any other combination.
Instead of flashing the RUU, or maybe turning to S-OFF(I still don't know if this would've made a difference), I flashed a firmware, one that matched my version. This is the exact filename: 0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed
I've renamed it to 0PKVIMG.zip and booted using the Power+VolumeUP keys. For whatever reason, everything went OK, no errors whatsoever. In the end it told me to press Power to reboot the phone. I've pressed Power and nothing happened since.
If anyone can help me figure this out, I'd be forever grateful.
arrayy said:
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader
Click to expand...
Click to collapse
That is a big problem. I assume you never tried to go S-OFF (which is dangereous). While phone was S-ON. You could always boot into bootloader. That's one of the purpose of staying S-ON.
Combination is Power + Volume down. But if your phone is up & somehow can not continue to boot. eg: stuck at reading system or kernel etc. You can do a hard reset which is pressing Volume up + volume down + power for at least 15 seconds. phone will shut down. then you can try bootlader combination. Make sure it's has power on with light at screen edges you must look at carefully. After trying this if you still can not see bootloader. That's a problem beyond my experiences, so I don't have any idea to fix it.
I have never tried the firmware you have used. Maybe that firmware is not usable, broken or even dangerous.
We need to confirm that here. if anyone else tried and brick their phone with that.
Hi, my 5X got itself into a bootloop state I have no knowledge of and I would really appreciate some pointers.
I searched the forum but I'm still not sure what I'm looking at and more importantly what to do about it. My main concern is not losing my data on the device.
Short summary: unlocked bootloader and rooted, bootloops, difficult to power off, factory images flash successfully but still only bootloader boots. The phone is on the latest stock Android 8.1 and was rooted with Magisk. In the meantime I've reflashed all factory images except userdata with no luck.
Bootloops: the phone started bootlooping by itself overnight. It was on the charger for a top-up and running only a sleep monitoring app like any other night. It boots as far as the Google logo, pauses a bit and repeats.
Power off: if I leave the charger cable connected the phone powers off from the bootloader menu only as far as the charging display and then starts bootlooping. If I first disconnect the charger it does power off, but as soon as I reconnect the charger the phone turns on and starts bootlooping.
Reflashing doesn't help: all factory images reflash successfully but the phone still won't boot into anything other than the bootloader. Booting into either the standard recovery or TWRP goes straight into the same bootloop. FWIW I also obtained the latest cache image and erased and flashed that but no luck.
My main concern is not losing my data so I want to be careful with whatever I try next.
I'd be really grateful for some pointers on what I'm dealing with and what the options are, thanks.
In case some other lost soul with the same problem stumbles across this, the explanation and fix are here:
https://forum.xda-developers.com/nexus-5x/general/tool-bootloop-death-blod-workaround-t3819497