So I have the LG Optimus V and was running a custom Stock ROM. I was going to give it to a friend to use so decided to use the factory reset in the phone...whoops.
I'm using ClockworkMod Recovery v3.2.0.0 and every time I try to install a ROM from the zip file on it it just goes back to Clockwork after a reboot.
I've tried using the ROMs listed here: http://forum.xda-developers.com/wiki/LG_Optimus_V/ROMs (besides MIUIv4 and LeWa Port) to no avail. I just keep rebooting back into recovery after it says it was a successful install.
I've also tried getting into a workaround using fastboot but I believe the condition my phone is in right now won't allow it. I can't boot up to the fastboot recovery and other issues have arised.
So is there anything I can do or am I boned?
Thanks for reading and any feedback
Cantee said:
So I have the LG Optimus V and was running a custom Stock ROM. I was going to give it to a friend to use so decided to use the factory reset in the phone...whoops.
I'm using ClockworkMod Recovery v3.2.0.0 and every time I try to install a ROM from the zip file on it it just goes back to Clockwork after a reboot.
I've tried using the ROMs listed here: http://forum.xda-developers.com/wiki/LG_Optimus_V/ROMs (besides MIUIv4 and LeWa Port) to no avail. I just keep rebooting back into recovery after it says it was a successful install.
I've also tried getting into a workaround using fastboot but I believe the condition my phone is in right now won't allow it. I can't boot up to the fastboot recovery and other issues have arised.
So is there anything I can do or am I boned?
Thanks for reading and any feedback
Click to expand...
Click to collapse
Are there any other recoveries for your phone
AFAIK new ROMs don't support Clockwork Mod 3.2
Try updating the recovery to the latest one available i.e maybe 4.x for your Optimus V
This problem happened to me some months ago
I reflashed the recovery using terminal emulator
Sent from my GT-I9082 using xda premium
Related
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Tried flashing another version of the recovery?
The K-Zoo Kid said:
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Click to expand...
Click to collapse
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
+1
I also made the experience that flashing recovery through rom manager doesn't always work...had the same problem, also using brainmaster's MIUI rom.
simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
How would i go about doing this?
Check the rooting guides for the directions.
Sent from my Nexus S 4G using xda premium
I tried looking for directions on how to do it and for some reason I can't seem to find them.
Sent from my Nexus S
You obviously didn't try very hard
http://forum.xda-developers.com/showthread.php?t=1067813
[REF] Complete List of Roms | Kernels | Rooting/Other Guides for Nexus S (GSM)
I am not linking you to the direct directions, but I hope you will find your answer by finding a root guide from the first post.................
Sent from my Nexus S 4G using xda premium
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
zenithz said:
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
Click to expand...
Click to collapse
You should make sure you are erasing the old recovery before flashing a new one. This can be done as a fastboot command or through the advanced options in rom manager.
Sent from my Nexus S 4G using xda premium
Just rooted and s-off a replacement one S. Everything went fine until i got to the point i was going to flash a rom. Ive been using the viper rom. after starting the installer it seemed out that all it did was format the memory. After it finished it rebooted and stayed on the HTC splash screen for probably twenty minutes before i did a hard boot. after getting back into recovery and trying again it did the same thing. i decided to just start over and do reboot from recovery but it is saying there is no OS. so i went back to view my card from recovery and everything on it was erased. Now im trying to copy the viper rom back over via recovery but the transfer speed is down to about 50kbps and keeps saying its timing out. any ideas
What recovery are u using? I read several times, that ViperRom and the latest twrp don't fit. In case of using twrp u should try an older version.
Sent from my HTC One S using xda app-developers app
customromfan said:
What recovery are u using? I read several times, that ViperRom and the latest twrp don't fit. In case of using twrp u should try an older version.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I guess i was using the twrp with that all in one toolkit i would switch to cwm but i cant get my computer now to reconigze the phone. i keep getting the htc mtp driver issue and haven't been able to figure it out. I figured if i can get the other recovery installed i should be able to flash a os
Jayster06 said:
I guess i was using the twrp with that all in one toolkit i would switch to cwm but i cant get my computer now to reconigze the phone. i keep getting the htc mtp driver issue and haven't been able to figure it out. I figured if i can get the other recovery installed i should be able to flash a os
Click to expand...
Click to collapse
go into bootloader, then fastboot usb mode.
the flash the new recovery via fastboot command, or with the all in one toolkit (chose custom, then locate your file)
i switched over to cwm and tried copying a viper rom to my phone but it keeps erroring out during the transfer. I tried a smaller rom and it copied over but all its doing with i click install is going to a black screen then back to cwm
i also tried several other roms that were smaller in size and it was doing the same thing
Background: I am still on ICS 4.0.4 rooted and unlocked (atleast ez unlock says im unlocked and i have superuser and voodoo says im still rooted) .
However, when I try to flash a custom recovery , ROM manager gets stuck at 100 % and closes. I have also tried installing a custom recovery via EZ recovery, and it says its flashed. However, when I boot into recovery mode, all i see is the stock recovery. So I am not sure what is going on. Do you guys have any idea?
If your still on ICS try selecting an older recovery? Some newer versions are not meant for ICS anymore I believe ...
Sent from my SCH-I535 using xda premium
I recall a similar issue I had due to the bootchain...not sure if that would apply here or not though
I was reading somewhere that samsung devices auto -overwrite a flashed recovery and change it back to stock. I am not sure how to combat this issue , or whether this affects anyone else?
You could try flashing a recovery through odin, that might give a different result. I think when you boot straight into recovery mode from download mode after flashing it might ask you to disable the phone from auto restoring the stock recovery.
I could be wrong though, it seems that's a common thing that happens when rooting a 4.1.1 or 4.1.2 base. However, flashing only the recovery file should still work for an ics base too. Just make sure it's a tar file, not an img file for the custom recovery for use in odin.
Sent from my SCH-I535 using Tapatalk 2
I have an HTC One S and recently tried putting a newer rom on my phone. That process has made my phone a paperweight.
I was using a really old ROM from my rooted HTC One and decided it was time to update as I was having a lot of issues with outdated software. Since i've tried installing several versions of TrickDroid onto my phone and all them failed me. I'm currently running S-off HTC One S with TWRP and I'm stuck in a vicious cycle of bootcycling from either the recovery, bootloader, or the logo. Whenever I leave TWRP it says that I don't have an OS installed, which is most likely why I hang at the logo and cycle through restarts. However, I'm adb pushing roms onto the phone and using the recovery install from zip to run the installers. I've followed that up with variations of flashing the boot in the bootloader with Fastboot flash boot boot.img or just trying to restart straight into my OS, but I can't.
I'm not really sure where to go from here.
khaele said:
I have an HTC One S and recently tried putting a newer rom on my phone. That process has made my phone a paperweight.
I was using a really old ROM from my rooted HTC One and decided it was time to update as I was having a lot of issues with outdated software. Since i've tried installing several versions of TrickDroid onto my phone and all them failed me. I'm currently running S-off HTC One S with TWRP and I'm stuck in a vicious cycle of bootcycling from either the recovery, bootloader, or the logo. Whenever I leave TWRP it says that I don't have an OS installed, which is most likely why I hang at the logo and cycle through restarts. However, I'm adb pushing roms onto the phone and using the recovery install from zip to run the installers. I've followed that up with variations of flashing the boot in the bootloader with Fastboot flash boot boot.img or just trying to restart straight into my OS, but I can't.
I'm not really sure where to go from here.
Click to expand...
Click to collapse
So what happens when you try to install an OS via recovery?
Also what TWRP version do you use?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
So what happens when you try to install an OS via recovery?
Also what TWRP version do you use?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I use TWRP 2.6.0.0
When I try to use TWRP to recovery install I can successfully complete the installation, but once I leave recovery to restart I'm stuck in bootcycles.
khaele said:
I use TWRP 2.6.0.0
When I try to use TWRP to recovery install I can successfully complete the installation, but once I leave recovery to restart I'm stuck in bootcycles.
Click to expand...
Click to collapse
Wipe data/factory reset, cache, dalvik and flashing boot.img before flashing ROM all good??
I see no other reason why it shouldn't boot up.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Wipe data/factory reset, cache, dalvik and flashing boot.img before flashing ROM all good??
I see no other reason why it shouldn't boot up.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I can do all of those things. I eventually got back to an OS by using an RUU from my carrier. It could just be the trickydroid rom I'm trying to use or ALORA. I have no idea.
Ok, Ive unlocked my bootloader, installed CWM, rooted my device and checked that it worked, and when I go to the boot loader and select recovery it takes me to CWM. Ive made backups from it and and they restore fine. I even installed a custom kernel and it worked because noFrills let me OC/choose a different governor. Yet from the three ROMs Ive tried so far, they install fine, no errors from CWM, but when I boot up it just gets stuck booting forever. Ive tried wiping everything, Ive tried wiping some things, heck I even tried wiping nothing but I still get the same issue. Id really like to try a new ROM now that I went through the trouble of voiding my warranty, so please try to help me. Thanks in advance, alexbenh
Same here
Gonna try out this guy's method real quick except with CWM
http://forum.xda-developers.com/showpost.php?p=49668571&postcount=5
I know this seems obvious, but are the ROMs you are flashing specific for your device?
Sent from my ST18i using xda app-developers app
yes, I have the Moto G XT1034 and have flashed ROMs before on my old galaxy exhibit and never had any trouble with that
Join the club, same here, done everything right but no custom rom joy for me
Sent from my XT1032 using XDA Premium 4 mobile app
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
WOOOHOOO, I reinstalled the stock 4.4 firmware and everything, I couldnt root it with superboot so I just skipped the rooting step. Then I flashed CWM through the bootloader although I decided to take a risk and instead of "fastboot flash recovery recovery.img", I did "mfastboot flash recovery recovery.img" just to see if it would change anything. Not sure if thats why it works for me now, but its worth a try. Good luck to the rest of you who have this problem.
lowrider262 said:
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Yes, I was already running the stock 4.4 ROM the only differences was that I had a custom kernel which could possibly be an issue, but I wouldnt think so
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
BBOXPT said:
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
Click to expand...
Click to collapse
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
alexbenh said:
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
Click to expand...
Click to collapse
My experience. I tried CWM then loaded a Rom, the first one I tried being CM11 = Bootloop, Then I tried several other Rom's and always the same result, spinning on Bootloop
I then put the phone back to stock firmware 4.4.2 and tried TWRP version TWRP2630, no joy even the bootloader wouldn't work right.
Finally put the phone back to stock AGAIN (now getting frustrated!) and tried installing TWRP2631 using fastboot. That did the trick, now all ROM's load and run fine. This version of TWRP appears to be working well. Backup/restore works, and no problems at all.
Other's report CWM works well, but not for me unfortunately.