Alright.
So yesterday i was just cassualy using my phone, when suddenly my volume down button started to act weird.
It kept pushing itself and raise or lower the volume. Since i didnt update my phone in a while, i figured it might be a software issue.
So i installed the latest update, and suddenly my phone booted in safe mode. Tried to reboot, no luck. Now my volume down key is unresponsive... I opened the phone up and cleaned the ports, but still no luck...
Looks like the key is dead. Now i am rooted and have twrp installed.
What are my options here?
Can i install an android 9 rom, maybe they wont boot into safe mode, i'm not sure?
I do still have warranty, so i could try my luck with relocking the phone and sending it back, but i also already opened it to look at the volume keys.
Do you guys have any ideas on how to handle this?
Related
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
The same thing just happened to me! Someone please help us! IS there a solution to this?
dsljk2009 said:
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
Click to expand...
Click to collapse
colbyrainey said:
The same thing just happened to me! Someone please help us! IS there a solution to this?
Click to expand...
Click to collapse
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
colbyrainey said:
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
Click to expand...
Click to collapse
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
jocyrus said:
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
Click to expand...
Click to collapse
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
audit13 said:
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
Click to expand...
Click to collapse
It didn't work. Any other suggestions? :|
jocyrus said:
It didn't work. Any other suggestions? :|
Click to expand...
Click to collapse
Don't know of any other methods because holding down the power button got the phone to turn off and allow me to get into download mode. From download mode, I was able to restore a stock 5.01 ROM to my phone via LG Mobile Support Tools.
LG G2 Bluescreen then no boot after disconnecting battery
Found my LG G2 with a completely blue screen. It would not turn off. Took it apart and disconnected the battery. Reconnected the battery and there was only a blank black screen and the phone would not boot. Zilch. Even with pressing the power button with the volume down to boot into recovery.....still zilch.
I sucessfully got my phone to work again using a hair dryer trick on an LG G3, which I found here.
1. I took the back off the phone, disconnected the battery, and removed the SIM card.
2. I then used a hairdryer on high heat and blew the heat over the uncovered areas for 10 minutes.
3. I let the phone from hot to warm, reconnected the battery and put it all back together with the SIM card replaced.
4. I booted into recovery and restored a TWRP backup, and my LG G2 is working like a champ again.
So basically my phone was stock but rooted and modded slightly with volume boost, camera mod, and the multi window mod as well. Other than that its all stock and never flashed a Rom on it. The phone ran smooth about 90% of the time but there were little quirks here and there that kind of bugged me. For example, every once in a while the screen wouldnt wake up after being locked via button or double tap. Wifi wouldnt respond randomly unless I reset my phone. Things of that nature, but anyhow I decided maybe hard reseting my phone might clear up some of these issues. I got into TWRP from AutoRec, and checked off everything except internal storage. I believe they were Davlik, Cache, System and obviously it didnt work out for me. I feel like me checking off the system is what did it because it wasnt considered a basic swipe at that point. Anyhow I cant get to recovery, download mode or anything of that sort. Everytime I hold down the power button it just resets and brings me back to the LG logo and just sits there while the led lights keeps rotating colors. Is my phone done for?
edit: Oh yea one last thing, I remember when I went to reboot it I somehow ended up being asked if I wanted to install SuperSU and I said yes. And than at that point it went to restart my phone and got stuck.
fjgotgame24 said:
So basically my phone was stock but rooted and modded slightly with volume boost, camera mod, and the multi window mod as well. Other than that its all stock and never flashed a Rom on it. The phone ran smooth about 90% of the time but there were little quirks here and there that kind of bugged me. For example, every once in a while the screen wouldnt wake up after being locked via button or double tap. Wifi wouldnt respond randomly unless I reset my phone. Things of that nature, but anyhow I decided maybe hard reseting my phone might clear up some of these issues. I got into TWRP from AutoRec, and checked off everything except internal storage. I believe they were Davlik, Cache, System and obviously it didnt work out for me. I feel like me checking off the system is what did it because it wasnt considered a basic swipe at that point. Anyhow I cant get to recovery, download mode or anything of that sort. Everytime I hold down the power button it just resets and brings me back to the LG logo and just sits there while the led lights keeps rotating colors. Is my phone done for?
edit: Oh yea one last thing, I remember when I went to reboot it I somehow ended up being asked if I wanted to install SuperSU and I said yes. And than at that point it went to restart my phone and got stuck.
Click to expand...
Click to collapse
You wiped system. That's your rom. Don't wipe system unless you plan on flashing a rom. You should still be able to get back to recovery. From phone powered off state ( hold power and volume up when lg logo is on). Hold power and volume down, when lg comes on, release both, then hold both again. You should now be at the factory reset screen. Press power three times (it's not going to factory reset). You should be in recovery. From here, restore your backup. If you don't have a backup, you just found out the reason why you should always have a backup. If you don't have a backup, you're going to need to install a rom via adb or otg (assuming your recovery is up to date). You can also tot or kdz back to stock (wipes sdcard though).
Return to stock thread: http://forum.xda-developers.com/showthread.php?t=2448960
nexus 7 4.4.4 f2fs
I was uninstalling some apps to get ready to back up and flash my phone because my microphone volume was stuck at minimum and no one could hear me. After rebooting my back and multitask (menu) button won't light up or respond. This has happened to me before occasionally. I could fix it by powering the screen off and back on. I believe I read somewhere it had something to do with xposed.
I tried flashing using MOP and my buttons didn't come back so I loaded a TWRP, wiped all partitions, rebooted in download mode and flashed with regular ODIN. Still can't get the buttons to function. Home button works just fine, though.
I tried finding a solution to this but I can't seem to find one. I had the same issue intermittently on my Galaxy S4 but I fixed it by wiping the partitions and reflashing. G900R4 USC variant.
So I went into stock recovery and did a factory reset. It was already as wiped as it could possibly get afaik but I thought I'd try just to see. My buttons lit up in stock recovery so I knew they were getting power. I did a factory reset and low and behold upon reboot my buttons came back.
Did I fix it or is there a circuit starting to fail on my phone and it was just luck? I'm curious.
Hello All,
I received an OTA update last night, which I accepted and installed. The phone rebooted, and began installing the update. After a while, "Error" was displayed underneath the android alien.
I rebooted my phone, and received a message similar to 'There’s an internal problem with your device. Contact your manufacturer for details.'. It still prompted me to enter my password, like normal when I power on my phone, which I did. The screen then went black, and I have been unable to power it on since.
The phone was stock, not rooted, no custom bootloader/rom/anything.
I have tried every combination I can think of, power, power+vol down, power+vol up, power + vol up + vol down. Charger plugged in, charger unplugged. Nothing seems to work.
The phone was running perfectly with no issues before this OTA update. Is there any way I can get my phone working again without RMA'ing it?
Thanks
Tey getting into the stock recovery and wiping your cache partition.
If that doesnt help then you should repair your cache partition as it might have gotten corrupt.
amusingduck said:
Hello All,
I received an OTA update last night, which I accepted and installed. The phone rebooted, and began installing the update. After a while, "Error" was displayed underneath the android alien.
I rebooted my phone, and received a message similar to 'There’s an internal problem with your device. Contact your manufacturer for details.'. It still prompted me to enter my password, like normal when I power on my phone, which I did. The screen then went black, and I have been unable to power it on since.
The phone was stock, not rooted, no custom bootloader/rom/anything.
I have tried every combination I can think of, power, power+vol down, power+vol up, power + vol up + vol down. Charger plugged in, charger unplugged. Nothing seems to work.
The phone was running perfectly with no issues before this OTA update. Is there any way I can get my phone working again without RMA'ing it?
Thanks
Click to expand...
Click to collapse
I think your only option is to RMA the device, even if you could get into the bootloader you wouldn't be able to flash anything because you never unlocked it, plus you can't unlock it without enabling the OEM unlock setting in Developer Options.
Sent from my Nexus 6P
If you get a RMA be sure to unlock the bootloader so you at least have a means of potentially saving it if the issue occurs again.
Please help me. I have a Huawei Y625 (a bit more than a year old), it is NOT rooted. I have never attempted to customize it/tinker around with it. I don't even know the exact terminology so I'm sorry if I get something wrong.
Yesterday it suddenly went into a bootloop, it kept saying "DataBackupStart" with a bunch of processes failing.
I held volume down + power button, which opened a menu entirely in Chinese.
I clicked everything on that menu, but those were just some tests, like camera and sound test.
Then I powered it off, held volume down+volume up+power button this time, and it finally got me to recovery mode I think.
I wiped cache, and I wiped all data, which did a factory reset. It was OK with me because I just want it to work.
Then I tried to reboot it, but then it started behaving even worse. It will not turn on until I remove and put back the battery, and then it will vibrate, show the Huawei logo for a few seconds and then turn off again. It never got past that logo, except if I turn on recovery mode.
I found its official stock files, put the 'update.app' in the dload folder on sdcard, then tried to activate that rom in the recovery mode. It says 'error, status 7, installation aborted'. I googled it but I do not understand a thing, I really don't get these tutorials and I don't know what to do about that.
I tried downloading Marshmallow 6.0 version, because I thought maybe upgrading Android would help, but I cannot find any download links that work.
I am out of my mind, I need my phone and nothing I found on the Internet has been helpful. I don't even know how it came to this since I have never even attempted to root my phone! Please help me, thank you. :crying::crying::crying: