Just got a brand new LG G2. I've already rooted and flashed TWRP, but after I flashed CM 10.2 RC1, I couldn't boot. I got stuck on a screen that says:
Code:
fastboot mode started
udc_start()
After messing around with it a bit, I was able to get back to recovery. I double checked the MD5's of the ROM and Gapps but they were both correct, so I tried flashing again and got the same problem. I tried looking for a solution online, but I wasn't able to find anything.
I'm new to TWRP, and somewhat new to custom ROMs in general, so I'm really not sure what to do.
Has anybody encountered the same problem? Am I doing anything wrong?
gollum999 said:
Just got a brand new LG G2. I've already rooted and flashed TWRP, but after I flashed CM 10.2 RC1, I couldn't boot. I got stuck on a screen that says:
Code:
fastboot mode started
udc_start()
After messing around with it a bit, I was able to get back to recovery. I double checked the MD5's of the ROM and Gapps but they were both correct, so I tried flashing again and got the same problem. I tried looking for a solution online, but I wasn't able to find anything.
I'm new to TWRP, and somewhat new to custom ROMs in general, so I'm really not sure what to do.
Has anybody encountered the same problem? Am I doing anything wrong?
Click to expand...
Click to collapse
Never mind, turns out I am just a dumbass. The Cyanogenmod wiki gives you the download for d802 by default. I have the d800, so I was trying to flash the wrong ROM. :silly: That really should not have taken me that long to figure out.
In case anyone encounters the same problem in the future: If you are stuck on the screen I mentioned above, you should still be able to get back to recovery the normal way. (Hold down the power button until the phone turns off, then hold power + volume down until the LG logo appears. Release the buttons and hold them again until a screen appears asking you if you want to reset. Hit power twice to boot to recovery. From there you should be able to restore and/or fix your mistakes.) Make sure you downloaded the right ROM.
Did u download the correct Rom for your model, d800,d801 etc?
Sent from my LG-D800 using Xparent BlueTapatalk 2
Related
I recently attempted to flash the Virtuous S-Series ROM to my Nexus 7, and something went wrong. When I attempt to boot normally, I get the correct boot screen, followed by something that looks like light static interference, and then nothing. It won't respond in any way after that until I hold the power button for about 20-30 seconds to shut it off manually. If I attempt to boot into CWM Recover (Using Vol- + PWR) It freezes as soon as the CWM menu appears. I'm really not sure what else to try....it just doesn't seem to respond to anything I know how to do. I don't have a lot of experience with Android, mostly just messing around with custom ROMs every now and again. Any help is appreciated!
this toolkit will help you mate, everything you can find there, from rooting, installing CWM to re-installing the default stock image to escaping from bootloop to everything basically
Follow this to get it back to stock. http://forum.xda-developers.com/showthread.php?t=1907796
It is not that hard at all and you will be glad you did.
You guys rock! I'll give it a try right away. =)
I've tried to find a way to use both solutions, but I can't get my tablet into recovery or the normal android interface, so there's no way for me to install the necessary drivers, as far as I can tell? What can I do to restore my device if I can't make it respond to anything?
Guys,
I installed CM10 (official) onto my Nexus 7. The ROM was running perfectly, no problems whatsoever. I then decided to flash the Elite kernel. I made a back up via Clockwordmod before hand, just in case anything went wrong.
I then installed the kernel and now all I get is the CM10 spinning green boot screen. That's it! I've installed Wug's tool, to try try and boot into recovery, but I can't even get the drivers to install to even use the tool... which is massively annoying.
Spent an hour last night searching for a solution and trying to get this thing to boot into recovery.
I've tried the obvious by holding down the volume rockers and then holding power, I get to the screen (I can't remember it's name) where you can toggle through different selections via the volume rockers, I select Recovery but it doesn't work.
Any ideas?
Make sure your Nexus is plugged into your PC, then you'll be able to get into recovery from the bootloader. This is the well known workaround for the problem with the original bootloaders.
Also, upgrade your bootloader to 4.13 as that version fixed the problem of getting into recovery.
Sent from my Nexus 7
Thanks.
Daft question, I'm not 100% on upgrading the boot loader. Can this be done on the device itself? If so, how?
Yes. There's a flashable zip file that you can install using recovery. Search the Development section.
Sent from my HTC Desire S
Hey all, I figured it was time to make a post and see if anyone could help figure out what I'm missing.
So I recently got my G2 and rooted it, then I installed Team Win Recovery Mod (on accident, actually. Was intending to install Clockwork, but figured it wouldn't hurt anything and it was working fine). Anyway, moved on to install Cyanogen Mod and gapps following the usual factory reset -> flash from /sdcard/ approach. Unfortunately on reboot, it went into fastboot mode.
Since then I've read a ton of stuff about fastboot, and I've reflashed recovery, boot, and system a dozen times, but I'm still stuck in fastboot mode. I've grabbed the CWM for LG G2 (AT&T) from http://www.clockworkmod.com/rommanager and the latest stable Cyanogen Mod from http://wiki.cyanogenmod.org/w/D802_Info. Sadly everything I've seen just tells me to do what I did - reflash recovery and tell it to reboot. I've also tried the "volume down + power until logo, then release and re-hit" method of getting into recovery mode, but the logo is present for literally less than a second, so I just end up back in fastboot.
Perhaps I need to find an flash a stock OS first? The thread on returning to stock firmware scares me :/ http://forum.xda-developers.com/showthread.php?t=2432476 Edit: I gave in and tried playing with this anyway. No good, I can't get the phone to enter "download mode", no matter what I do, it reboots into fastboot.
Any ideas?
Edit: The flash method I used for TWRM: http://forum.xda-developers.com/showthread.php?t=2449670
Edit2: This seems possibly relevant. When I do "fastboot devices", I get "? fastboot". So something is wonky in terms of its detection. But all the commands seem to be getting executed fine...
Edit3: Finally a potentially useful piece of info: If I flash the boot image extracted from the Cyanogen mod zip, then run "fastboot continue" I get "ERROR: Getting device tree address failed". Which is the same message I get when trying to remotely run a boot image without flashing it. Possibly related to the "?" in the "fastboot devices" listing above? I switched to Koush's Universal Adb Drivers, but no change.
Pretty please?
I find it hard to believe I could manage to brick a 2 week old phone just by following the guides posted here
Well, I still have no clue what went wrong, but I was finally able to make use of the reset to stock thread. It was strange and scary and at no point did I really have any idea I was hitting the right buttons, and at the end it said it failed... BUT it rebooted me into a fresh install, apparently even unrooted! My problems along the way appear to have entirely been related to actually getting the phone *into* download mode since I couldn't get it to actually turn off. Once it ran itself out of battery and turned off, I was able to enter download mode while reconnecting it to power.
No to decide if I want to try installing a custom ROM again, or take this as a sign...
Who am I kidding. *re-roots phone and pulls up the mod threads*
Short version: Phone is boot looping at LG logo and when I try to volDown+power into recovery it gets to the factory reset prompt and I press power twice but nothing ever loads and the backlight just stays on. I'm guessing I no longer have a functioning download mode either because of the way these flashable bootstack zips we've been using on the VS980 ROMs mention that they disable download mode, so I probably can't use LG Flash Tool either. Bricked?
I had been on CloudyRom 1.3. I switched back to xdabbeb's VS980 ROM, the newest version with the 25B bootstack. As many people ran in to, for some reason after coming off of Cloudy, KnockOn doesn't work on other ROMs. I had tried to do this hidden menu trick to update the touch screen firmware which some people reported got the KnockOn working again. Long story short I was having trouble getting the hidden menu trick working while on the xdabbeb ROM, I went back to Cloudy ROM and tried to do it but that didn't fix it either. I saw people having success by going back to a purely stock ROM and doing the hidden menu trick from there.
Here is where I probably messed up, I had a backup from April of this year that I didn't have labelled/named well but I was certain it matched up with the last time I had probably been on a purely stock ROM when the VS980 finally got KK earlier this year, a backup I had made for the convenience of ever having to return to stock. I tried to restore this and that's where the trouble happened. At the time I figured worst case scenario would be that the baseband wouldn't match up and I wouldn't get a signal, but in hindsight I'm guessing it wasn't safe to try to restore this after updating to different bootstacks. Original KitKat rom was 24a I believe but I had just recently updated to 25B to use the newest xdabbeb ROM.
I saw a small ray of hope when I calmed down enough to remember the voldown+power sequence to get into recovery, but after reaching the factory reset prompt and pressing power twice to continue, nothing ever loads and the backlight just stays on, like my recovery is gone now too I guess.
And in a comedy of errors I'm guessing I no longer have a download mode that would allow me to use the LG Flash Tool through PC because these flashable bootstack files always mention that they disable download mode and I never worried about restoring it.
So, bootloop, can't get into recovery, probably can't get into download mode to work with LG Flash Tool.
Screwed? :crying: :crying: :crying:
Yeah, volUP + plug into PC just gets me fastboot mode.
Don't really understand why my recovery is gone, thought the button sequence to get back into recovery was the safety net to this entire thing and why I wasn't too worried. Was running TWRP.
I'm at the mercy of checking the internet when I have access to another computer because my phone was also my internet access on my home PC. Hoping someone can help. : (
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.