LG G3 Will Not Reboot - G3 Q&A, Help & Troubleshooting

Today I tried updating my Verizon LG G3 to a new nightly CyanogenMod 12.1. I cleared the cache, delvak cache, and then installed the new nightly over an older nightly. Then, my screen went black (after a successful install). Now, every time I boot my phone up i get to the LG logo screen, and then the screen goes black. I have to remove and reinsert the battery in order to turn the phone on again. My phone will not stay on long enough to enter twrp or settings.
Is a factory reset/wipe on my pc the only option?
Thanks

Hi, you can't enter twrp recovery by buttons power + Vol- ?
If you can, flash again the rom without wipe cache and dalvik

I can not even boot into TWRP

SquirtingLlama said:
Today I tried updating my Verizon LG G3 to a new nightly CyanogenMod 12.1. I cleared the cache, delvak cache, and then installed the new nightly over an older nightly. Then, my screen went black (after a successful install). Now, every time I boot my phone up i get to the LG logo screen, and then the screen goes black. I have to remove and reinsert the battery in order to turn the phone on again. My phone will not stay on long enough to enter twrp or settings.
Is a factory reset/wipe on my pc the only option?
Thanks
Click to expand...
Click to collapse
can't recover thru adb ?

Well no recovery mode and not normal boot.
We can't use adb commands.
If you can go to download mode , apply a kdz firmware .

Related

[Q] HTC Desire HD boots but black screen afterwards

So I have a rooted HTC desire HD with Jellytime on it. All was working great till recently when it would shut down by itself. Today after I wanted to test a new boot screen from Rom toolkit I restarted it and while the boot screen worked great after it finished I see a black screen (backlit so I know its on). I tried going to the bootloader but after I try to go to wipe cache for example it restarts by itself and it gets stuck after the boot screen... Any ideas?
ok an update seems that if I go to the recovery via down button and power it lets me do actions. All this time I went to recovery mode when phone was shut down and plugged into a power source. I did a wipe cache and now it says android is upgrading and now it finished saying starting apps. Hope it didnt get stuck there because it keeps doin the cycle animation but doesn't do anything else.. I ll leave it be for a bit like this... :/ Had to restart it by removing the battery after 20 minutes... same problem as before still...
another update... just before it goes to a black screen when the boot screen finishes an orange light appears just briefly (where the green light appears when it charges)
Wipe everything (system data cache) and install a stock-ish ROM. What happens?
bananagranola said:
Wipe everything (system data cache) and install a stock-ish ROM. What happens?
Click to expand...
Click to collapse
I flashed the rom again and wiped data and all seem to be ok now. I ll update this because I saw many people have similar problems... thanks in advance for any help!
Have the same problem.
I bought this with the problem that it keeps rebooting all the time.
I unlock the bootloader with htcdev,root with Easy Ace Tool,flashed the new cyanogenmod 11,
but did the same .
At least 3-4 rebooting before open normally.
I said that it must be ROM issue and flashed the KK-LegacyCarbon-4.4.
Did the things should be...flash the ROM and then the boo.img separately.
Now i have black screen and the only screen i am able to get is bootloader and the recovery 4EXT.
I reflased cyanogenmod back but nothing happened,any thoughts???

Help! Stuck on loading after flashing mahdi 2.5 20140326

I got LG GPad v500 earlier today, rooted and installed CWM. Then I flashed the latest Mahdi and GAPPS, cleared cache and dalvik cache, and on reboot it stuck on google logo animation (four colored circles moving). When I press and hold Power it just reboots. When it reboots it shows this error for a few sec:
------------------------------
Secure booting Error
Cause: Device ulnock. Success!
------------------------------
and proceeds to the google logo. I can't even get it to recovery mode because it doesnt shut down (catch 22!).
Any help please!
Ok, after 20 attempts I managed to boot into recovery. I reflashed both rom and gapps, reset to factory defaults, and it boots now!
Keeping it here in case someone else gets into the same situation

Soft bricked after CM12 nightly install

Hi there,
After successfully rooting and unlocking bootloader of my Z1C I installed TWRP/philz double recovery. From there I transfered latest CM12 nightly, slim zero gapps and double recovery zip.
Recovery at first worked just fine, could factory wipe my phone and installation seemed OK. But after first boot of CM12, Google Play services kept crashing down, could not even pass first screen.
Ufter booting CM recovery I wiped factory again with cache (no dalvik option) and reinstalled CM12 but WITHOUT gapps this time. Same result, google play services kept crashing.
Now I rebooted to bootloader and only have a black screen with blue light on top.
How can I bring my phone back from the land of the dead ? Any help is appreciated

HTC One M8 won't boot after downgrading CM 13 to 12.1

Hello,
after experiencing some problems with crashing Galery-app on Stock ROM Android 6.0.1 I decided to do a factory reset.
After factory reset, I got constant android.process.acore and HTC Sense crashed and could not use ANY app nor even see my starting-screen.
I managed to get into the settings and enable USB Debugging. But most of the time, my device did not boot up properly and just showing the HTC-bootscreen. When I pressed volume-up + Power I could reset the phone but was not able to manually power on again. Aso Volume-Down+ Power (To access recovery mode) did not worked anymore.
After getting on low batterie my device turned off and then I was able to access recovery mode again.
I started installing CWM Recovery (Philz touch) which ran fine.
After some unsuccessfull factory resets (same problem as above) I decided to install a custom rom. I choose cm-13.0-20160329-NIGHTLY-m8.zip (Android 6)
The installation process ran fine and I was able to boot normally. Only thing that was wierd: The phone did not recognize my sim-card and I was not able to play any sound. So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop). Naturally, there was the animated CM-Bootlogo showing and not the stock HTC Boot screen.
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power, instead I have to wait till my phone powers up on its own (Which will lead to a bootloop again)
Is there any way to get the device working again?
Thank you!
EDIT: Also it is running really hot while in bootloop.
EDIT2: my battery ran out of energy and I managed to get into recovery mode again. installing latest nightly (20160330) now
EDIT3: "Setup Assistent" crashes while startup. Can't get into recoverymode either. dont know why. phone just starts up normally...
Vendaar said:
Hello,
after experiencing some problems with crashing Galery-app on Stock ROM Android 6.0.1 I decided to do a factory reset.
After factory reset, I got constant android.process.acore and HTC Sense crashed and could not use ANY app nor even see my starting-screen.
I managed to get into the settings and enable USB Debugging. But most of the time, my device did not boot up properly and just showing the HTC-bootscreen. When I pressed volume-up + Power I could reset the phone but was not able to manually power on again. Aso Volume-Down+ Power (To access recovery mode) did not worked anymore.
After getting on low batterie my device turned off and then I was able to access recovery mode again.
I started installing CWM Recovery (Philz touch) which ran fine.
After some unsuccessfull factory resets (same problem as above) I decided to install a custom rom. I choose cm-13.0-20160329-NIGHTLY-m8.zip (Android 6)
The installation process ran fine and I was able to boot normally. Only thing that was wierd: The phone did not recognize my sim-card and I was not able to play any sound. So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop). Naturally, there was the animated CM-Bootlogo showing and not the stock HTC Boot screen.
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power, instead I have to wait till my phone powers up on its own (Which will lead to a bootloop again)
Is there any way to get the device working again?
Thank you!
EDIT: Also it is running really hot while in bootloop.
EDIT2: my battery ran out of energy and I managed to get into recovery mode again. installing latest nightly (20160330) now
EDIT3: "Setup Assistent" crashes while startup. Can't get into recoverymode either. dont know why. phone just starts up normally...
Click to expand...
Click to collapse
Yout could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Vendaar said:
EDIT: Also it is running really hot while in bootloop.
Click to expand...
Click to collapse
That's going to happen. The CPU is working hard during boot, and if its caught in a bootloop, the CPU is getting constantly worked, and heat is the inevitable result.
---------- Post added at 09:38 AM ---------- Previous post was at 09:34 AM ----------
Vendaar said:
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power,
Click to expand...
Click to collapse
Is the phone powering off with Power+vol up; or is it rebooting? It should be rebooting. If its rebooting, the moment the screen goes dark, and before any boot splash screen shows; hold only vol down to access bootloader (don't let go of vol down until you see bootloader).
Failure to get into bootloader this way is usually user error (often the result of not pressing vol down soon enough, or letting go of it too early)
---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------
jkolner said:
Yout could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Click to expand...
Click to collapse
I agree to try TWRP. Philz hasn't been updated in a very long time, and is known to cause some issues due to that.
---------- Post added at 09:43 AM ---------- Previous post was at 09:40 AM ----------
Vendaar said:
So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop).
Click to expand...
Click to collapse
Are you doing full wipe (data, Dalvik, cache) when installing new ROMs? This is recommended, and failure to do so will often lead to boot problems on the ROM.
Also, are you installing gapps (Google apps) with the CM ROMs? Failure to do so will also lead to boot issues, or setup assistant crashing (and a lot of other errors during startup). And the CM ROMs can be finicky with some gapps packages.
Thanks for your replies!
redpoint73 said:
Failure to get into bootloader this way is usually user error (often the result of not pressing vol down soon enough, or letting go of it too early)
Click to expand...
Click to collapse
I pressed both about 10+ seconds. Guess it was my error then.
redpoint73 said:
Are you doing full wipe (data, Dalvik, cache) when installing new ROMs? This is recommended, and failure to do so will often lead to boot problems on the ROM.
Click to expand...
Click to collapse
I did not do a full wipe then . Thought deleting cache will also delete dalvik cache. I did only delete data+cache
redpoint73 said:
Also, are you installing gapps (Google apps) with the CM ROMs? .
Click to expand...
Click to collapse
Yes, I booted to recovery, and used sideload to first push CM and afterwards gapps to the phone.
jkolner said:
Your could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Click to expand...
Click to collapse
Okay. I will now install TWRP 3.0, do a full reset (data, dalvik, cache) and flash the latest CM. Thank you very much!
Android is now booting well. Thank you
Next problem i'm running into: can't play any audiofile. Ringtones dont work either. My phone isn't doing any beep. videos do not work and Gallery-app is crashing instantly. Also my equalizer AudioFX.
Errors, I get are:
Music-App
[CRASH] com.cyanogenmod.eleven threw java.lang.IllegalStateException
Gallery crash:
[CRASH] com.android.gallery3d threw java.lang.RuntimeException
Audiofx:
[CRASH] org.cyanogenmod.audiofx threw java.lang.IndexOutOfBoundsException
I researched some time but did not found anything useful here
EDIT: New problem:: SIM is not recognized by phone anymore. It worked on first boot..
Edit2: cant even hear sound over headphones.
updated to latest nightly. Did not resolve anything.
Bump.
Updated to latest nightly and cleared cache + dalvik before. didn't solve my problem either
Bump
Sent from my m8 using XDA-Developers mobile app

GT-I9195 LTE Cannot access recovery or download mode

Good day all,
I have a GT-I9195 LTE and have just flashed the Bliss-v6.0-serranoltexx-UNOFFICIAL-20160131-2157.zip using twrp-3.7.0_9-0-serranoltexx.img.tar. I did a complete clean install (wiped system / data / cache / dalvik) then first flashed the blissos then open_gapps-arm-6.0-nano-20220215.zip, then wipe cache/dalvik again and rebooted. All went fine, I set the phone up and all seemed to be working fine. I did a reboot to fix the small font on the lock screen as suggested on another thread and now I am stuck. the phone keeps booting, going into "Bliss is starting.. Optimizing app" then says Bliss is starting.. starting apps" then immediately goes back to the Bliss splash screen, over and over. So then I tried with volume-down/home/power to get to TWRP recovery mode, but no luck, it just boots normally. Then I tried volume-up/home/power to get to download mode, also no luck, it also just boots normally. Can anyone please advise how I can get into download mode at the very least so I can reflash TWRP using Odin and try to flash a different ROM? Thanking you.
Update to above post: Ok, after many tries I managed to get into download mode and reflash TWRP. So far so good.

Categories

Resources