So here's the deal, I tried to format the cache partition of a stock, non-rooted and non-unlocked bootloader Zenfone 2 (Z00A) through recovery, and it somehow failed/got stuck. After about 1h, I shut down the phone via long-pressing the power button and now it won't boot.
Booting it just leads to an "error!' message and stay there. Trying to go back to recovery does the same thing, I can get to the initial fastboot screen, but selecting recovery mode and pressing power+vol up after the reboot doesn't lead to recovery at all. Instead, every 5 or 10 seconds, the screen clears to black for 1 sec and the same error message shows up.
I tried to get access to it through ADB, but it won't show up in the device list under either the fastboot screen or the Error! message screen on which it stays stuck. Also, the phone was setup so that it didn't allow USB debugging, but I doubt that matters, given that it can't even load Android at all.
Is there something I can do about it? Any tip is greatly appreciated, I looked around XDA and Reddit but didn't find anything that really helped.
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
ultramag69 said:
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
Click to expand...
Click to collapse
Thanks, I had tried various variations of that approach but the issue was a bit more complex than that. In the bootloader, the phone was detected by Windows and drivers from Asus installed properly. ADB wouldn't list the phone, but fastboot did. However, any operation by fastboot was denied access because USB debugging was not enabled prior to the phone going down. Otherwise, as you mentioned, fastboot erase cache would have worked fine.
In the end, I found another post on XDA by Theja which linked to a post in Spanish. The modified ADB and fastboot packet there contains a batch file that manages to bypass this issue and installs CWR, from which clearing the cache is possible. Upon reboot, Asus replaces CWR with the original recovery and things look back to normal.
Sweet, as long as you got it back up and running...
ultramag69 said:
Sweet, as long as you got it back up and running...
Click to expand...
Click to collapse
Hehe, thanks. I'm pretty happy indeed, was already considering the need for a new phone.
However, I must say that finding this toolset worries me a little bit. I thought the whole point of disabling USB debugging was to ensure that people can't perform low-level operations on the phone via fastboot/adb. In this case, this protection is somehow bypassed. I didn't have time to read through the entire batch file, nor am I proficient-enough in Android to make sense of it all, but I wonder how it was done...
In any case, I now have USB debugging left on. It increases convenience and the ability to recover things if problems occur, and it seems like the security benefits are not that strong anyways.
Related
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.
[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.
anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state
hard reset ?
hard reset always works for me. 20 seconds
krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Is your device rooted? If not that is just rediculous on asus's part
slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.
I would return it..I'm sorry to hear that I have had troubles myself with two devices so far
krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?
I have no way to enable usb debugging since I cant tun on the device, right?
krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.
Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you
Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)
JunkTardis said:
Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)
Click to expand...
Click to collapse
best thing is go to recovery factory reset and flash viper again
get to recovery by power vol down just in case you dont know
JunkTardis said:
Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)
Click to expand...
Click to collapse
there is 2 flashable zips in nexus 5 forum to swap between dalvik and art cant see why they shouldnt work can all ways ask and just side load them and flash them in recovery
jaythenut said:
best thing is go to recovery factory reset and flash viper again
get to recovery by power vol down just in case you dont know
Click to expand...
Click to collapse
That did not work at all, the entire phone was completely frozen on the Venom bootscreen. I did manage with some fiddling to get into Recovery. I did Power+VolUp to force reboot the device, then when the screen went black very quickly switched and did Power+VolDown to enter HBOOT and go to TWRP from there. Painstaking, and took a few goes. Luckily I still had my VenomRom on the USB Stick and after trying multiple different options in TWRP I made sure I had a backup of my data, and reinstalled Venom fresh with a full wipe. I tried doing just an install over it, as that's worked in the past - but the issue persisted. A full wipe was required.
For future until this bug is resolved, if you want to try ART on the One M8 with Venom, make sure to have a nandroid backup to hand as always. Mine was 2 days out of date, but no real loss to me
Thanks for your help!
Do an adb pull you should still have adb access at the boot screen.
/data/property/persist.sys.dalvik.vm.lib is a textfile containing one of two values: 'libart.so' or 'libdvm.so'. You can change from ART to Dalvik simply by editing this file.
Ex: adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'
It's because deodexed roms can't use art
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
Do an adb pull you should still have adb access at the boot screen.
/data/property/persist.sys.dalvik.vm.lib is a textfile containing one of two values: 'libart.so' or 'libdvm.so'. You can change from ART to Dalvik simply by editing this file.
Ex: adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'
It's because deodexed roms can't use art
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
That has actually helped me, and I appreciate it. I'm relatively experienced and comfortable in doing a lot of Android things such as bootloader unlocking and editing system files but I had no clue that deodexed roms can't use ART. I should submit a warning to the VenomDevs to grey out or hide the option in Developer Options or at least provide a warning
I can't boot up my device it's have blink sleeping android error. (my device is ze551ml running WW_2.19.40.22 firmware and never ever ROOT!!! )
I tried hold power button and press volume up button but its doesn't work.
I also can't access to recovery mode too.
It's have the same blink error message and can't pass by hold power button and press volume up button.
Oh but i can access to fastboot page.
and my computer don't recognize my phone at all(i already install driver)
Before this problem happen I get in to recovery mode try to wipe cache but i miss press and i selected "apply update from adb"
and that time my phone doesn't connected with PC. I don't know what to do so I turn off my phone.
then I open recovery mode again and select wipe cache then I go out to take a bath.
I came back and see my phone is off so I boot it.
It's booting about 2-3 mins and nothing happen so i go to recovery mode again but this time they have problem like i explain before(blink error message that can't pass by hold power button and press volume up button)
So anyone have a solution for my problem. please I really need your help!
Sorry for my bad english
Hi,
I had this when I went to wipe my system cache and it failed. Your best bet, especially if you can't get into recovery is to fastboot flash the recovery again if you have an unlocked bootloader.
If you don't you'll want to unlcok the bootloader and follow the instructions for using ADB if you're new to it: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
How can I unlock my boot loader when i can't even open up my phone.
stultus136 said:
How can I unlock my boot loader when i can't even open up my phone.
Click to expand...
Click to collapse
If you hold volume down and power, it should go to bootloader first, then you have your choices for recovery....Get it to the bootloader screen, then run the commands to unlock it...
Could you please tell me everything step by step on how to cure my phone?
I'm very noob.
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
stultus136 said:
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
Click to expand...
Click to collapse
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Same Problem
smokinjoe2122 said:
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Click to expand...
Click to collapse
Hey I'm having the same problem, how'd you get the computer to recognize that the phone was plugged in? My computer does not recognize that the phone is on when I have the flashing error screen, so ADB doesn't recognize that there is a device connected.
Hi,
I had the exact same problem, and I managed to boot up again thanks to you!
What I did :
Install ADB and Drivers
Boot my phone into Fastboot (Power+Volume Up at boot, keeping VolumeUp button pressed while booting). Don't go into any menu (do not select recovery or so). At this point your computer should recognize your Android phone when you plug it in through USB.
Open up a cmd with admin rights, navigate to adb install path by typing : cd C:\adb
Then type : fastboot erase cache
It should trigger an action on your device, and the prompt should display sth like "Cache successfully erased" (I don't remember exactly)
Finally type : fastboot reboot, press volume up while booting again, and access Recovery like usual!
Now you can try wiping your partition cache again.
Worked like a charm for me! Thanks a lot
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED <remote: flash write failure>
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
Cheers
Mattia
Did you update to the latest sdk tools? I think fastboot has been updated. Also, make sure you are using a good cable in a good port. I had trouble flashing with a USB 3.0 cable in a USB 3.0 port. It worked in a USB 2.0 port just fine.
I suspect your device is in a dirty state- it wants to wipe data to unlock the bootloader, but it didn't complete, so it is unwiped, but still considered encrypted. Maybe try flashing the stock system using fastboot -w update some-update.zip. The update zip is inside the factory image- you'll need to untar it. This is a destructive flash and will erase your data! If it works, let the system boot up since it will take a while to encrypt so that it is in a sane state.
I think download mode is for factory programming. I've been there a few too many times already, and I think it is vol up and power. It'll tell you not to disconnect the cable and the percentage bar will be stuck at 1%. I'll let you guess on how to get out of it.
Make sure you update android sdk like ^ he said, I spent 3 hours trying to get back to stock and trying to figure why fastboot system image wasn't workking -_-
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
addisontodd said:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
Click to expand...
Click to collapse
it's seems like me , it's been a month i can't boot it up .
sfhub said:
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
Click to expand...
Click to collapse
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
addisontodd said:
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
Click to expand...
Click to collapse
what if you try
fastboot boot twrp.img
I've bootlooped so many times I don't know where to start.
So you flashed the factory IMG from your bootloader correct.
Fastboot -w will wipe without wiping system.
Then reflash your whole system. I would redownload from the Google site through Skipsoft...the easiest way. When it asks to keep or flash new recovery you want to flash the stock recovery.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
You'll have to reroot afterwards which you can also do through skipsoft.
Profit... Thank me if I helped.
It's a Hardware issue. Installing system again will not fix it. Send it to LG for a repair. My phone had the same issue.