A couple weeks ago, I upgraded the ClockworkMod Recovery on my Thrill. A few hours ago, I attempted booting into recovery mode. My phone is now stuck attempting to boot into recovery. It's stuck at the LG boot logo and will not progress to recovery or even into the boot animation for a normal boot. I have tried holding the VolDown+3D to manually boot into recovery, I have tried turning it off and back on, I have tried removing the battery for a few minutes, I've tried removing the battery and SIM card for several minutes and there is no change in status.
I'm using an LG Thrill on a stock GB ROM and the latest ClockworkMod Recovery, installed by latest version of ROM Manager (play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en)
If any more info is needed, let me know. The computer I'm using is a Macbook Pro.
Schuetrumpf2 said:
A couple weeks ago, I upgraded the ClockworkMod Recovery on my Thrill. A few hours ago, I attempted booting into recovery mode. My phone is now stuck attempting to boot into recovery. It's stuck at the LG boot logo and will not progress to recovery or even into the boot animation for a normal boot. I have tried holding the VolDown+3D to manually boot into recovery, I have tried turning it off and back on, I have tried removing the battery for a few minutes, I've tried removing the battery and SIM card for several minutes and there is no change in status.
I'm using an LG Thrill on a stock GB ROM and the latest ClockworkMod Recovery, installed by latest version of ROM Manager (play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en)
If any more info is needed, let me know. The computer I'm using is a Macbook Pro.
Click to expand...
Click to collapse
Try this. Take out the battery, while the battery is out hold down the 3d button, the volume down button and power button. "While" these 3 buttons are pressed insert the battery. You should see the lg logo flash on for a second or two than off. From this point leave the battery in and try to boot into recovery with the three buttons. (It may boot into recovery right away after you reinsert the battery)
Sent from my LG-P925 using xda premium
Schuetrumpf2 said:
A couple weeks ago, I upgraded the ClockworkMod Recovery on my Thrill. A few hours ago, I attempted booting into recovery mode. My phone is now stuck attempting to boot into recovery. It's stuck at the LG boot logo and will not progress to recovery or even into the boot animation for a normal boot. I have tried holding the VolDown+3D to manually boot into recovery, I have tried turning it off and back on, I have tried removing the battery for a few minutes, I've tried removing the battery and SIM card for several minutes and there is no change in status.
I'm using an LG Thrill on a stock GB ROM and the latest ClockworkMod Recovery, installed by latest version of ROM Manager (play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en)
If any more info is needed, let me know. The computer I'm using is a Macbook Pro.
Click to expand...
Click to collapse
And one more thing, do not use the latest recovery! Only 5.0.2.7. I also had problems with the latest. lol
Sent from my LG-P925 using xda premium
Instal from lg flash tool v21e
Sent from my LG-SU760 using xda app-developers app
bigfoot.kom said:
Try this. Take out the battery, while the battery is out hold down the 3d button, the volume down button and power button. "While" these 3 buttons are pressed insert the battery. You should see the lg logo flash on for a second or two than off. From this point leave the battery in and try to boot into recovery with the three buttons. (It may boot into recovery right away after you reinsert the battery)
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
I tried this several times to no avail. No change. The LG logo flashed on and off, but when I tried to boot back into recovery, it didn't boot into recovery. I tried doing it again, then booting normally and still no change.
You may want to try and use the lg flash tool. I had a lot of trouble with the new recovery. Had to revert to on older version.
Sent from my LG-P925 using xda premium
Sorry never mind i see now u can not get it to boot. You may just have to use the lg flash tool and go back to stock gb. http://forum.xda-developers.com/showthread.php?t=1540163
I had this issue one time also. Go to terminal emulator and type su. See if super user ask to grant permission. If no you may have lost your root. Try and re-root the thing with the Megatron root and reinstall cwm from ROM manger.
Sent from my LG-P920 using xda app-developers app
*Deleted*
billy8362 said:
Sorry never mind i see now u can not get it to boot. You may just have to use the lg flash tool and go back to stock gb. http://forum.xda-developers.com/showthread.php?t=1540163
I had this issue one time also. Go to terminal emulator and type su. See if super user ask to grant permission. If no you may have lost your root. Try and re-root the thing with the Megatron root and reinstall cwm from ROM manger.
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Finally got my phone working again. I had to borrow someone else's computer to do it, but hey, at least I have my phone back. I'd rather not reinstall CWM from ROM Manager, because it installs only the latest version which is exactly what bricked my phone to begin with.
Long story short, all's good, everything works. Thanks.
i have the same problem
Schuetrumpf2 said:
Finally got my phone working again. I had to borrow someone else's computer to do it, but hey, at least I have my phone back. I'd rather not reinstall CWM from ROM Manager, because it installs only the latest version which is exactly what bricked my phone to begin with.
Long story short, all's good, everything works. Thanks.
Click to expand...
Click to collapse
which kdz is best for my p925 mine originally had froyo v20 something, i only glanced at it the other day before it crashed. thank you in advance
Related
I flashed the bugless beast v0.4 rom earlier. But for a couple days now have had trouble getting device to stay in recovery which I'm using clockworkmod. It reboots after a couple seconds of entering recovery by its self. Now I can't get it to stay at all. I'm trying to install the black glass theme. Any ideas?
Sent from my Droid using XDA App
I have a similar problem with Milestone, i flashed the Got sbd and used their mod of Open recovery, i used it (put Got theme, root, busybox and maybe one or two more things) I got back in Got's Open recovery 1 or 2 more times but since i can't i've got the Warning but never the recovery itself, i put a new one (new version) but same thing. The Got sbf works well but get back again in recovery stay a mistery, i search for a clue in google but i feel like i'm the only one with that problem
Yeah I know, the problem with Droid is it doesn't mount the sdcard when I enter recovery so it aborts and reboots. I've reflashed but when I pull the battery after it fails recovery then put it back in and try again it works some times but I may have to do it a couple times to work. Can't seem to figure it out. Also I've tried sprecovery and I think its the same thing but it doesn't reboot it just wont let me do some things in sprecovery like make a backup or flash a rom. Scratching my head here.
Sent from my Droid using XDA App
Ok, so you've got the recovey list then? I don't. It's stay on the warning screen. I think the last thing i've done before i can't get it back is to use app2sd (the choise witch make the app2sd partition (I put 2 Go i think) maybe that's the my problem.
Maybe you might have to try rrflashing recovery. I'm not sure other wise like the Droid there might be a couple buttons to hit to enter recovery. I know before I rooted when I want to enter recovery, I have to hold power and the x button on power up and when on warning screen I hold volume up and camera button. I don't know if the same appliese to you after rooting where you don't need second set of buttons. But I do know recovery.img. isn't flashed or stored on sdcard. So when it's flash recovery your flashing the file on the phones internal storage. You probably know this but that being said unless you have a bad recovery flash or recovery.img isn't present on phone hard drive. It should work. or atleast I think it should. Some devices have trouble mounting the sdcard when entering recovery, I don't know if that's what happens if your doesn't. All I can suggest is trying to flash an alternative recovery system and if it work try reflashing the one you use now. When mine wont work I flash sprecovery and flash back to clockworkmod and it work some times. Other wise I pull the battery for 2 minutes and try again. Usually have luck with one of those. Sorry if this don't help you if you've tried.
Sent from my Droid using XDA App
Thanks for the help i manage to enter recovery this way : after the warning screen : i let all buttons then i hold Volume UP and then push camera button
Next step : enter GOT's Openrecovery instead ^^
No problem. Glad to help. Just surprised because usually after installing custom recovery you don't need second set of buttons to hold down. I learn something new every day.
Sent from my Droid using XDA App
Of course still having trouble with mine but realized after flashing alternate recovery from terminal emulator and then going back to clockworkmod. It seems easier. Just wish I could figure out why sdcard doesn't mount in recovery.
Sent from my Droid using XDA App
I'm on a Sprint Hero. I used the universal one-click to root. Titanium Backup to restore my apps after flash. Clockwork's ROM manager for the rest.
Two days ago I decided to flash my first ROM, CM6. When I flashed I got a little carried away, flashed the ROM, gaaps, sprints vvm, the mms fix, and a stable uncapped kernel all at once. Bottom line, it wasn't running quite like I had hoped and I was running out of spare time. Flashed my nandroid backup and was good to go. Everything restored like it was before I started.
Yesterday I found some time and decided to try flasing CM6 again. This time starting slower, with just the cm6 and gapps. Then everything else as needed.
Here's the problem; I can't get to recovery mode. I've tried the "Reboot into Recovery" from the ROM manager. I've tried the power down, power up w/ home key held down. I've tried power up with volume down key then choose recovery mode. I've tried installing rom from sd (this gets me to the point that says it is sending me to recovery to finish installing).
I get three different results, and they seem to apply themselves randomly to my reboots. First, I get hung on the white HTC screen. Second, I get the white HTC screen, the phone gives a vibrate and the screen goes off. Third, I get the white HTC screen, the phone gives a vibrate, it reboots back through the HTC screen and starts up like nothing happened. For the first two, the only way to get the phone back is a battery pull.
I have rerooted with the one-click. Still no luck.
I can restore my original nandroid backup through ROM manager.
I can flash clockworkmod recovery. It is current at 2.5.0.1
Could someone please help me find my recovery mode.
Thank you.
Peace.
Have u just tried holding down power and home it takes like 20 seconds just keep holding them it should pop up and if you hold power down and volume down wen the screen pops up just hit home button and wait it should popup hope this helps good luck
Root-Hack-Mod-Always™
I have tried both. I have also tried getting to recovery through Clockwork's ROM manager.
Every time my phone tries to get into recovery mode it gets stuck. When I say it gets stuck, I mean one of three things happen. First, the phone hangs on the white HTC screen. Two, the phone gets past the HTC screen, the screen shuts off, and the phone becomes completely unresponsive (when this happens I need to pull the battery to get it back on). Three, the phone gets past the HTC screen, reboots itself and boots right up to the stock sprint ROM(it ignores my request to get to recovery mode).
This morning I tried something new, but still failed. I uninstalled Clockwork's ROM manager. Erased the clockwork folder from my SD card. Reinstalled the ROM manager. Flashed the ClockworkMod recovery. Was successful with getting a recovery, 2.5.0.1 Tried to backup my current ROM. The phone rebooted, gave me the HTC screen, then shutdown and I need to battery pull. After that I tried the Home Key recovery reboot and got the same shutdown.
Does anybody see anything that I have done wrong here? Anywhere. I just want to find my recovery mode. Is there another way to get there?
Please help.
Thanks.
Peace.
Try flashing a different recovery I recommend Darch Star RA 1.7 If you search XDA /hero cdma/ android development you will find a thread called Darch Droid 2.8 go there and on the first page u will find it along with instructions on flashing the recovery if you need help with that just respond here and if I can help I will but hopefully that helps good luck
Root-Hack-Mod-Always™
Open Rom Manager, scroll down to flash alternate recovery and click on that. When finished scroll back up and select flash clockwork recovery. Hope it helps
Sent from my HERO200 using XDA App
I guess he bricked it
Sent from my HERO200 using XDA App
I'm thinking so as well hope not though I bricked my first hero back in feb and man it sucks so hopefully he didn't a if you reading this dude I'm rooting for ya
Root-Hack-Mod-Always™
laie1472 said:
I'm thinking so as well hope not though I bricked my first hero back in feb and man it sucks so hopefully he didn't a if you reading this dude I'm rooting for ya
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Same here my silent brother.
Sent from my HERO200 using XDA App
trip187 said:
Open Rom Manager, scroll down to flash alternate recovery and click on that. When finished scroll back up and select flash clockwork recovery. Hope it helps
Click to expand...
Click to collapse
Trip, I think I love you!
This got me back to where I need to be. I've got my recovery mode back! I'm running a nandroid as I type and I'm on my back to CM6!
Thank you for suggesting something that hadn't been suggested yet.
Peace.
PhntmParadox said:
Trip, I think I love you!
This got me back to where I need to be. I've got my recovery mode back! I'm running a nandroid as I type and I'm on my back to CM6!
Thank you for suggesting something that hadn't been suggested yet.
Peace.
Click to expand...
Click to collapse
Happy I could help.
Sent from my HERO200 using XDA App
After trying the update(made cwm backups btw) the phone is in a reboot loop cycle. However, I can't get back into CWM in order to restore the backup i made or even the revo_stock or the stockrooted zip. I can get into the OS to the point where it wants me to select a language then it tries to find the SIM and fails completely and reboots. If i pull the battery and try to boot from the power on the USB it will reboot to the LG logo then instantly reboot again... Ideas anyone?
cliffs:
-backed up in cwm
-tried to install gingervolt
-stuck in reboot mode
-cannot access cwm to restore
Did you wipe data both times MT said? Maybe try wiping again?
Did you try flashing from a froyo ROM?
Wiped date both before and after the flash of gingervolt. I was using the decrapped rom 1.1
I would happily go back and try to clear the data again, however i cannot access CWM in order to do so after the gingervolt flash... Even using the power button+volume down i get no access...
SomeFknGuy said:
After trying the update(made cwm backups btw) the phone is in a reboot loop cycle. However, I can't get back into CWM in order to restore the backup i made or even the revo_stock or the stockrooted zip. I can get into the OS to the point where it wants me to select a language then it tries to find the SIM and fails completely and reboots. If i pull the battery and try to boot from the power on the USB it will reboot to the LG logo then instantly reboot again... Ideas anyone?
cliffs:
-backed up in cwm
-tried to install gingervolt
-stuck in reboot mode
-cannot access cwm to restore
Click to expand...
Click to collapse
I had the same thing happen to me. Although once it rebooted i was able to bypass the setup process and just manually do it from the home screen.
If you can't even get past the LG logo without it rebooting, I also had that happen to me on my last phone a few months ago. I called Verizon and they said that they had reports of other phones doing that too. Unfortunately I never figured out how to fix it. The problem was that it never stayed on long enough for the computer to recognize it.
Flashing Gringerbread ROMS from froyo breaks this phone. I did that same thing
restoring a back up is what you need how to get there idk
I haven't had much luck getting the phone to do anything, it will stay turned on for ~2-3 minutes then instantly reboot...
SomeFknGuy said:
I haven't had much luck getting the phone to do anything, it will stay turned on for ~2-3 minutes then instantly reboot...
Click to expand...
Click to collapse
Hope on IRC I'll see if I can help
Ok this is how i fixed this i pulled the battery then holding power and volume down button at the same time turn your phone on hold it until you get a black screen asking to wipe hit the power button to.confirm now it will reboot back to cwm and go to back up and restore then go to restore and restore one of your backups deck stock back up does not work it must be one you made.
Sent from my VS910 4G using xda premium
CWM reboot loop
Use this zip from thecubed it works wonders.
My phone would not go past reboot option in CWM
Search fast boot loop thread for further instructions on how to use it.
I pulled the SD card from my Revo and used it in my old win mobile Omnia so it would mount on my PC then I copied the zip onto the stuck Revo card.
Well after a few hours of tinkering i got her working... CWM never wanted to register but finally after about 100 tries of power on+vol it actually caught and booted into cwm. from there it was a cake walk until i got into gingervolt and it refused to allow the phone to come out of airplane mode(why this was even on is beyond me). after about 4 reboots the phone is working flawlessly...
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
mhelm23 said:
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
That's the stock Droid 3 recovery. Using a reboot recovery will lead to that, and will not allow Safestrap's bootloader to intercept the boot and activate Safestrap recovery.
I haven't tried running Safestrap 3.05 myself, since it's still not official, but I do know that you cannot reboot recovery as you describe to to get into Safestrap for any version of Safestrap.
mhelm23 said:
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
thats the stock recovery
now. do you still get the boot menu splash page where it asks you to input the menu key or continue?
if so hit the menu many times or hit on the screen the hit menu for recovery image section, as it shoulod also work.
maybe my next question is silly or already tried, but have you tried to try it with the charger disconnected?
some times when my droid 3 is connected, the touch screen gets un responsive o registers more than input
hope this helps
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
DoubleYouPee said:
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
Click to expand...
Click to collapse
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
mhelm23 said:
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Skreelink said:
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Click to expand...
Click to collapse
Yea - I tried that too. I am really at a loss.
Sent from my DROID3 using xda premium
I am sittin in the same spot. Can't boot into recovery...
Sent from my DROID3 using xda app-developers app
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
Had this problem today after creating a rom slot and flashing a new rom, this worked for me however I had to try it a few times. Once I got into recovery I wiped the rom and rom slot and ss3 is working properly now. Not sure if this was a rom issue or ss3.
Sent from my DROID3 using XDA
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
dabayer said:
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
Click to expand...
Click to collapse
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
doogald said:
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
Click to expand...
Click to collapse
i dont like the word "should"
ok i try to save the files in safetrap and try an OTA. yesterday the ota didn't run but i think i have to wait longer thar it starts the installation than the 10 minutes...
The slots are all stored on the internal storage (the mount point /sdcard) on the phone, so as long as you don't format internal storage, they should stay there.
I should note that I have never tried installing the OTA with safestrap 3.05 installed - I did it with 1.08. Actually, you may want to activate the stock slot, go into the safestrap app and uninstall recovery, and then try running the OTA. It's possible that the OTA will balk with a custom recovery installed - I don't remember, and, like I said, I never tried with Safestrap 3.05 installed.
You can also download the OTA, copy it to an external SD card, and manually run the update from stock recovery. See this thread: http://forum.xda-developers.com/showthread.php?t=1643521
[edit] Sorry - that link is for an update from 890 to 906. I forgot that you were not on 890. Sorry about that...
I had almost the same problem with my phone, the diference is that mine got stuck on non safe system (Stock ROM). Initializing the phone with th Android Recovery (Turning on with the key "m" pressed down) and choosing BP Tools doesn't worked.
- Phone: Milestone 3 XT860 (Brazilian Droid 3)
- Carrier: Vivo
- Current ROM: Stock 2.3.5 - 5.2.440
So i got a new lg g2 for verizon last week. ive had good experiences with cyanomod and other roms so i figured off the bat that i would install one of these. turns out they were alot more problems than it was worth. so i went back to stock rom and rooted. for some reason i took OTA. now phone is stuck in fastboot. so i went through this thread http://forum.xda-developers.com/showthread.php?t=2582142. so i got everything done and figured out (running live ubuntu so getting automount to stop was a challenge and then figuring out the new file paths). so now i reboot phone and try to get into twrp (from complete power off hold power button and volume down, release when logo shows and press again). so i get the "do you want factory reset" screen and i click yes, yes then it just goes into fast boot again. problem is now not even linux is reconizing the device. device doesnt go into twrp. cant get into download mode to reflash. all i got is "[16370]fastboot mode started [16420]udc_start() [16590]-reset- [1660]-portcharge- [16640] fastboot: processing commands.
do i have any hope? the phone is new from a third party so i dont think i have a chance to return to the seller, and im not sure if lg will take it either
added info
also, just read and possibly part of problem, twrp was 2.7.1.0, either way though im still stuck with it at this point
ok, so just a bit more info. now when the phone is plugged into windows 7 computer it automatically installed a driver "USB Movem Phone ADB port". so i figured id try to run adb devices and see if it showed, no luck. dont know if this puts me in a different situation or not...
Did you try via terminal $ reboot-bootloader you may be able to force into bootloader for adb sideload twrp 2.7.0.0
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
Adb and fastboot are two different programs. If your in fastboot mode computer won't recognize adb devices. While in fastboot mode, reboot-bootloader then see if you can get adb through toggling vol + or -
Sent from my VS980 4G using XDA Premium 4 mobile app
actually i just got a step farther.... now i have twrp installed and working (turns out version 2.7.1.0 and 2.7.0.0 both didnt work with my phone even though i specifically got the versions for my phone. now im using 2.6.3.2 in case anyone else is having issues).
so twrp is on the phone. by random luck i apparently had all the rom zips left on the SD card. so i was able to flash a known working rom (at least it was working well enough to get by...). so i flashed the rom and rebooted the phone. unfortunatly it went straight back into twrp. i dont know if there is a flag i havent set or what. i thought i saw a walkthrough about what to do at this point, so im still working on it and i will update if i can fix it... but as i stated right now have twrp 2.6.3.2 working, still no download mode apparently(ill mess with this more because originally this is how i was flashing back to stock when things went wrong), and even though twrp installed a known working rom its still booting straight into twrp (without the whole power and volume down seqeunce...)
Some ROMs won't work on 2.6.3.2
Sent from my VS980 4G using XDA Premium 4 mobile app
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
If recovery doesn't detect a compatible ROM it bootloops. That or corrupt download itself, make sure to verify md5s whenever possible.
Sent from my VS980 4G using XDA Premium 4 mobile app
YAY, got it mostly back kinda sorta. so i followed this http://forum.xda-developers.com/showthread.php?t=2451696 after getting back into twrp. i dont know what this did or if it helped. then i flashed a new rom (which i also by chance had on the SD already) i believe it was malladus 1.2.9 and it worked (except i didnt put gapps or anything so it was having a fit about play... now its restarted and i have download mode back so ill just flash the whole thing with the regular rom (the rom on this website might even be older than the phone, but for me it worked well...). here is that website i case anyone needs it http://www.lg-phones.org/guide-to-flash-restore-unbirck-verizon-lg-g2.html i will reflash and post results, hopefully a bone stock phone to start over with...
glenn3451 said:
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
Click to expand...
Click to collapse
As far as a straight to recovery, I haven't had that problem on my g2. On my tablet,I run multi ROM recovery and it will go straight to recovery if a ROM is not installed. I would think it would do the same on vs980 twrp.
Sent from my VS980 4G using XDA Premium 4 mobile app
btw thankyou for suggesting a different rom, wouldve probably been stuck for awhile without that advice. so flashed verizon stock firmware(which also deletes everything) and its 100% running with the exception of the activation (switched back to old phone while working on getting this guy running again). i feel like ive learned alot more than i ever wanted so ill stay subscribed to this thread and if anyone has similar issues when you post hopefully ill be able to help alittle... no promises though