Solved!
Please buy hyelton a beer or a damn new phone. He's a hero.
This worked: http://forum.xda-developers.com/showthread.php?t=2432476&highlight=decrypt
Hey guys, but of an emergency here...
I'm stuck at the LG logo after flashing the Pacman ROM with the latest unofficial CWM, and it seems to have failed at Formatting system. All four touch buttons on the bottom were blue, as if they had been pressed and highlighted. No response from anything.
Reboot. Then it got stuck on the LG logo. I can't access CWM anymore, holding power + vol down does nothing, I just go back to the logo. I'm running a D802.
This was a pretty standard flash for me, I have done this many times, so I was confident in it, but now have no way back into a phone I desperately need within hours.
Process went as follows;
Full wipe, format, initialize install, it failed/crashed/whatever, rebooted, now stuck on logo, unable to access CWM, and obviously unable to access ROM.
USB Debugging was on, but as the ROM doesn't exist anymore, not sure how much help that'll be.
I'll gladly go back to either CWM or TWRP, as well as stock ROM or whatever. I can sort all that out later, right now just need things back in running order.
Edit1: I can't even turn it off. It simply boots up again, so now also worried of damaging display or battery.
Edit2: It's not showing after entering "adb devices". List is empty.
ANY help appreciated.
I'm running Windows 8, and no, I will not be able to reinstall to W7 or Ubuntu.
Thank you
Related
I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.
Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?
I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.
Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.
Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.
first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.
I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.
lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT
I've been rooted for quite some time now, was always using axiom, today I decided to try something new, I flashed via twrp ROM and gapps, twrp said no root, installed superuser? I swiped yes, phone booted to Google screen, but now is the stupid part,
Keeps boot looping there, absolutely no boot loader when trying to boot into it, computer won't read device, just says android with a yellow exclamation mark and says the drivers are incorrect or something, I cannot fast boot because of this, when trying to enter boot loader it just gores to Google screen goes black then flashes red light,
Is this fixable? Will JTAG work maybe (last resort), anybody who has the time to help will be my hero haha, I work in a few hours so I won't be back until the afternoon, but please anyone!
Oh and phone isnt unresponsive, still vibrates, still charges and still boots google logo,
Just remeber i cant flash stock img files due to not being abke to use fastboot:/ unless there is a way to get the computer to read my phone
Thanks in advanced to people who reply,
joshracine1 said:
I've been rooted for quite some time now, was always using axiom, today I decided to try something new, I flashed via twrp ROM and gapps, twrp said no root, installed superuser? I swiped yes, phone booted to Google screen, but now is the stupid part,
Keeps boot looping there, absolutely no boot loader when trying to boot into it, computer won't read device, just says android with a yellow exclamation mark and says the drivers are incorrect or something, I cannot fast boot because of this, when trying to enter boot loader it just gores to Google screen goes black then flashes red light,
Is this fixable? Will JTAG work maybe (last resort), anybody who has the time to help will be my hero haha, I work in a few hours so I won't be back until the afternoon, but please anyone!
Oh and phone isnt unresponsive, still vibrates, still charges and still boots google logo,
Just remeber i cant flash stock img files due to not being abke to use fastboot:/ unless there is a way to get the computer to read my phone
Thanks in advanced to people who reply,
Click to expand...
Click to collapse
It happned with me too when its reboot to google logo before that press vol down and power button to get into bootloader
I've been messing around with my phone, trying to flash CWM and CyanogenMod (to no avail), and yesterday something happened. I woke up, my phone was dead so I started charging it. It booted into the Stock OS (the one that ships with the G2--build D20010o I think). Shortly after, a message appeared on the screen about an update the phone was going to install (I'm assuming one that AT&T was pushing to my phone), and shortly after it powered down on its own. I have not been able to get it to boot into the OS since.
Before all of this happened, I rooted the phone with IORoot, tried to flash CWM (I think successfully), but was not able to install CyanogenMod, so I flashed an earlier build of the stock OS (D20010o), rooted it again (I'm not sure that I had to--I think it stated that my phone was already rooted), tried to flash CWM again (unsuccessfully this time), and I gave up. Then this problem occurred.
Every time I try to power on the phone, the LG logo flashes, and the screen stays on, but it's black. If I try to do a factory reset via the hardware buttons, I am able to see that screen, but as soon as I follow the instructions of pressing the power button twice, it says that it's initializing the reset, but then the phone's screen goes black again--not sure if the screen is on or off, though. The LED light is also not on during any of this.
I'm unsure what to do. I've had the phone for about 6 months, but I had not owned an Android before that--iPhone user for 3 years. I obviously did not do enough research or ask enough questions, but I would like my phone to be in a usable state. I would greatly appreciate any help that anyone can give me!
NEVER take an OTA with a recovery.
Use the lg flash tool to go back to stock
http://forum.xda-developers.com/showthread.php?t=2432476
Sorry, should have also mentioned that I can't boot into Download Mode. I'm assuming there's no .kdz file for AT&T, and the other method in that link requires Download Mode. :/
Hello,
I have bricked my LG G2 (D802) and installed the stock image with the LG flash tool. Now, I don't have a recovery anymore (I press volume down and power on boot but it doesn't open a recovery, just tells me in the left corner that I'm in security mode).
Also, the biggest problem here is, that if I boot my LG G2, I can't use it. There is all the time a message popping up that com.android.phone was shut down, I can't do anything.
I want to wipe the phone completely but don't have a clue how. My computer doesn't recognize the booted phone, it's just working in download mode. But I can't install the recovery from download mode.
Could someone please help me?
Flashing kdz makes you loose that. Only way to get it back is by following the procedures mentioned everywhere.
Also note, its likely on your version different combo key opens recovery. Forgot what it was but its been mentioned plenty of times.
Use that combo, do a factory reset and it should be fine
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?
Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!
You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.