Hello fellow G2 owners! First post here and sad enough its a question/problem, just moved from an LG Optimus G so Im sad I had to leave the other forum ): Anyhoo, my G2 since before I rooted it and installed a custom recovery would never jump into its own stock recovery. I turned the power off, held both the power button and the volume down button, waited for the LG logo, unheld the buttons then reheld them to only see the logo go away and come back. Now that I am rooted with TWRP, the only way to boot in is through a an app while in the phone. Can anyone let me know how to fix this?
I had the same issue for the longest time. Could never get into recovery while turning on the phone. Finally realized that I need to hold the power button and the volume down and keep them held down until my recovery opens (never release them and push them again). Hopefully your phone is goofy like mine and that's all it takes.
Related
Hello,
I recently got a brand new DHD from T Mobile UK. Naturally, I wanted to get rid of the bloatware that came with it. To cut the long story short, I tried to install the cyanogenmod software and ended up bricking my phone. At first it would not get past the cyanogenmod start up screen (spinning smoke thing). Now it will not boot past the T Mobile logo.
I am desperate and any solution to give me back ANY funstionality of the phone would e great.
Kind Regards.
Sena.
Can you get into the bootloader? Try turning it off, then holding the power button and volume down - I think the easiest method is to hold volume down, press the power button for a few seconds (still holding volume), then let the power button go and after that the volume button. Seems to get me into the bootloader reliably.
If you can get into the bootloader, you should be able to flash back to the stock rom by placing a file on the SD card - not certain of the exact method there but someone will know
I wouldn't worry too much unless you were flashing the bootloader (hboot) to get s-off - as I understand it, the only real way to brick these devices is if you corrupt the bootloader.
What exactly did you do? I agree with the previous poster that you probably did not brick your phone you just need to get into the bootloader and flash a backup, if you made one. Also what ClockworkMod Recovery are you using. I know that if you flashed with 3.xxx you will need to flash an older version of CWM something like 2.xxx
If you give us more info we could prob help more
jords12 said:
Can you get into the bootloader? Try turning it off, then holding the power button and volume down - I think the easiest method is to hold volume down, press the power button for a few seconds (still holding volume), then let the power button go ...
Click to expand...
Click to collapse
Also try taking the battery out first.
senakiro said:
Hello,
I recently got a brand new DHD from T Mobile UK. Naturally, I wanted to get rid of the bloatware that came with it. To cut the long story short, I tried to install the cyanogenmod software and ended up bricking my phone. At first it would not get past the cyanogenmod start up screen (spinning smoke thing). Now it will not boot past the T Mobile logo.
I am desperate and any solution to give me back ANY funstionality of the phone would e great.
Kind Regards.
Sena.
Click to expand...
Click to collapse
If you have cwm / rom manager install to your phone just turn off your phone and charge it now you are in recovery state you can flash rom again or restore backups
Sent from my Desire HD using XDA App
So I'm running CM 10.2 android version 4.3 and I started to notice that when I pressed the power button, it brought up the reboot menu instead putting my screen to sleep so I downloaded the newest nightly and figured it was probably just a bug and went to flash the latest nightly. Upon reboot, my phone got in an infinite bootloop so I pulled the battery, let it sit for a minute and then held the power, volume up and menu button to enter recovery. I got the blue words in corner that you will normally see when booting into recovery, then saw the S3 screen that you'll see right before entering recovery, however, my phone started rebooting again constantly vibrating etc. So then I decided to try and get into download and flash back to stock with Odin. So I entered download mode, pressed volume up on the confirm screen and then it entered download mode and then immediately rebooted and wouldn't stop. Is my phone bricked? I'm wondering if the power button is broken since when in download mode, it reboots which normally occurs when you hold the power button in download mode. Sorry for the long description but just wanted you guys to know what I've done so far and am experiencing. Any help is appreciated. I've been rooting phones from all manufacturers for years now and I'm out of ideas at this point. Thanks!
Definition of a bricked phone: A completely unresponsive device which doesn't turn on at all. Doesn't vibrate upon start up and doesn't have any signs of life.
You most likely have a jammed power button as that has been the issue with the GS3. Not a brick.
Clearly not bricked as the first reply explained. And for the love of god, please use some white space (paragraphs) next time.
If you think that a button is jammed, see if you can physically unjam it without causing damage. If you believe that the flash may be messed up, the mskip's Samsung Toolkit may be able to reflash a known good ROM even with a stuck button. And look into some of the button remapping apps like the aptly titled Fix Broken Power Button app.
Good luck.
Hello everyone first let me say thank you for taking the time to read my post any help would be fantastic
I747m rooted
was stuck in reboot loop
Removed the power button completely
Fixed the issue and phone worked fine had button savior installed
Was happy see
Than noticed my camera wasn't working so opened my phone again days later to see if the camera was connected properly
Put my phone back together and now it won't boot its stuck at the s3 logo
Please help loli need my phone and have a baby on the way and cannot afford a new one
Report your own post and ask a moderator to move it for you, this forum is for the i9300 only.
Sent from my GT-I9300 using Tapatalk
OK thank reported myself. I really hope I can gain some insight into this matter xda-devs are the best I'm told so fingers crossed
XxDAxXBLITZ said:
Hello everyone first let me say thank you for taking the time to read my post any help would be fantastic
I747m rooted
was stuck in reboot loop
Removed the power button completely
Fixed the issue and phone worked fine had button savior installed
Was happy see
Than noticed my camera wasn't working so opened my phone again days later to see if the camera was connected properly
Put my phone back together and now it won't boot its stuck at the s3 logo
Please help loli need my phone and have a baby on the way and cannot afford a new one
Click to expand...
Click to collapse
You might have to factory reset in recovery (vol up + home + power). I read you removed the power button, that's so not useful lol.
Maybe you'll be able to use ADB to boot in recovery or a jig to boot in download mode (if it gets to that point).
no luck
BWolf56 said:
You might have to factory reset in recovery (vol up + home + power). I read you removed the power button, that's so not useful lol.
Maybe you'll be able to use ADB to boot in recovery or a jig to boot in download mode (if it gets to that point).
Click to expand...
Click to collapse
On no luck when I try to boot into recovery it just vibrates and stays black vibrates every few seconds till I release the button than stays there
Only thing I have access too it the is downloaded vol down and home
What could I have messed up while opening my phone to cause this?
XxDAxXBLITZ said:
On no luck when I try to boot into recovery it just vibrates and stays black vibrates every few seconds till I release the button than stays there
Only thing I have access too it the is downloaded vol down and home
What could I have messed up while opening my phone to cause this?
Click to expand...
Click to collapse
Hold all 3 buttons until he boots up (vibrate), then release the power, while still holding home+vol up. It should boot in recovery.
Depending on your carrier, you may be able to flash a stock ROM via Odin.
If you have the 4.3 bootloader, only flash a stock 4.3 ROM. If you have a 4.1.1 or 4.1.2 bootloader, you can flash either a stock 4.1.1 or 4.1.2 ROM via Odin.
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
(PS: I posted this in XDA assist originally but figured it would be better being posted here.)
UPDATE: my power button will now lock my phone but not unlock it.
hi all! I've certainly royally screwed myself over this time around.
I installed sling v3.2 and restored my apps, after restoration I tried to unlock bootloader with freegee (since it was pre-rooted) and freegee showed it was already unlocked, so I tried to flash a custom kernel and viola! this happened!
Problem is, my power button is close to broken and no amount of pressing down will turn the device off. is there anyway I can turn it off or save my Optimus G? thanks in advance!
UPDATE:
I've tried to get into download mode but to no avail (tried pressing volume up + down while ramming the power button on my PC desk). I tried Vol Down + Power and I got into factory reset mode, so i pressed vol down because I didn't want that.
It restarted to LG screen which showed that dreaded secure boot error message. This time around I tried Volume Up + power button and it restarted but with the message "something unLock!! restart boot!!" something like that, didn't really see what it was, it flashed too quickly for me to see what it said. Anyways it then rebooted into CWM and now I've cleared cache/dalvik/system/data and re-installed Sling v3.2!!
Hopefully this will work out so I'll update this when it finally boots back to life! (hopefully!)
BTW, my device is an LG F180K the Korean Variant, it's color Maroon with an Olleh logo at the back, just in case anyone was wondering.