Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.
CartoonmanPDC said:
Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.
Click to expand...
Click to collapse
Yes, restoring the last working nandroid backup would be an option.
Alternatively you may have to flash another recovery.
I found this guide to flash CWM recovery on a similar device: How to flash cwm recovery on the lg spectrum 2.
But I am not sure if it wil work for your device too.
So better ask in the General discussion > Questions and Answers forum.
Thread closed and thank you.
Related
Hi to all! I did a big mistake and now don't know what to do. I had cyanogen mod 7 RC1 installed, but wanted to go back to my original froyo. I did all these steps
Install ClockworkMod recovery (using fastboot is the easiest way).
Boot into recovery using the 3-button combo
Do a backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from the SD card using ClockworkMod Recovery
Optionally install the Google Addon
Click to expand...
Click to collapse
, but when I tried to install the old os, my ohone showed something like "bad" and didn't want to install it. Now I'm stuck with no solutions. When I try to boot into recovery it just shows "update failed" and cannot proceed. Now what?
Thanks in advance!
Well, I was able to boot normal finally. I think I'm going to repair it now!
I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.
Parrot mac said:
I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.
Click to expand...
Click to collapse
Whatever happened to people just rebooting into recovery and flashing something else?
Sent from my SCH-I535 using xda app-developers app
Parrot mac said:
I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.
Click to expand...
Click to collapse
You're special indeed. You are not following the directions put forth by the ROM developers in flashing their ROMs. Also some ROMs don't require you to flash Gapps as it is already part of the ROM. There is also a chance that you are flashing the wrong gapps. Give me a list of ROMs that you failed to flash that way I know for sure how to help.
prerequisites
which Cyanogenmod are you flashing? and by soft bricking, what were the symptoms? like could you get back to CWM? or TWRP?
Parrot mac said:
I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.
Click to expand...
Click to collapse
jwattt said:
which Cyanogenmod are you flashing? and by soft bricking, what were the symptoms? like could you get back to CWM? or TWRP?
Click to expand...
Click to collapse
I have the same problem like OP does. Plus mine does not accept Jellybean OTA at all. I flashed liquid smooth and the phone shows samsung logo for half a second and shuts off.
ajrty33 said:
Whatever happened to people just rebooting into recovery and flashing something else?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
i feel u on that i seen cwm then rom manager....
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
dmccrack said:
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
Click to expand...
Click to collapse
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
SlimSnoopOS said:
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Click to expand...
Click to collapse
The ROM was downloaded via Goo.im app
dmccrack said:
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
Click to expand...
Click to collapse
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
dmccrack said:
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
Click to expand...
Click to collapse
dmccrack said:
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
Click to expand...
Click to collapse
No problem. As for your issue, its fairly simple actually. What you need to do is a clean flash which is either of the two steps I listed earlier. You're trying to go from TW to AOSP but what you did was only wipe the cache then flashed the rom. Wiping cache and dalvik cache is regarded as a dirty flash, something you only do when flashing a newer version of the rom you're on. You never fully removed the TW rom before flashing Liquid which is why it did not boot. Basically, when you want to flash a new rom, by a different developer, you need to do 1 or 2 in order to have a successful flash.
For AOSP roms, you should also be flashing the recommended GApps (Google Apps) as well so that you have your Play Store and a few other Google Apps. The latest "generic" gapps zip is listed here at the top, its "20120301" which is March 1st. Liquid may have their own, that's for you to find out via their thread. Google apps are included in TW roms so this is not necessary.
Cannot reboot system from Clockworkmod Recovery
Hello, my phone detected that there is an update then i click the update after that it told me to confirm for reboot my phone enter CWM recovery then I clicked on reboot system now. It showed the Samsung Logo and the Splashscreen, but then enters the CWM recovery. I also tried pulling out the battery and then pushing the power button, but it still boots into CWM recovery. Any help? It looks like my phone got messed up and I can only use it in CWM recovery. Help is much appreciated. for everyone information i did root my phone a year ago.
So no problem at all.Wipe the data there and enter into mobile.It should work..
well the thing is i already tried that. i dont remember how many time i wipe it clean. then tried to reboot but still comeback to CWM recovery.
If there are any roms for ur device then fladh it .Of restore the nandroid backup...:thumbup:
wipe dalvik cache
I've got a T-Mobile phone with stock updated to the last version, with TWRP 2.6.3.0 and root. Everything worked fine for a couple of months.
A month ago the phone started to boot loop with no apparent reason. I've wiped everything, re installed stock, rooted and used the phone again. I've thought it might be an app updated that screwed something.
Anyway, I've only got the basic apps on the phone and today it happened again. I've read that I need to boot into bootloader and selecr "CLEAR STORAGE", I've tried that but it goes into recovery and there I can only wipe the data. I've did that and rebooted and it didn't help.
Any other ways to fix this without re installing the rom?
I think that if you use the clear storage option, you will have to reinstall the rom. I believe it wipes the system partition as well.
If you want to do this, you should flash the stock recovery (get it here)
Go into the bootloader and select the clear storage option.
Then you can flash CWM or TWRP recovery again and install the ROM.