Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
I was in the process of manually installing CWM Touch via Rashr Flash Tool to replace an old 6.0.1.1 non-touch version i had on it before, 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, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS.
I've tried the following with no success:
Clearing data factory reset
Clearing cache
Clearing Dalvik cache
Full restore to V6 stock
Full restore to Cyanogen (I made a backup when I first got to CWM Touch)
This is the current behavior of my phone:
When powered on, it will display the LG logo, then it will flicker to black and then fade in the LG logo again, 5 seconds later recovery boots. If phone was off and you insert USB cable to charge, the LG logo appears, but the battery mode sort of screen never comes after. Its just stays at the LG logo, and never turns off the display.
It will keep rebooting to recovery no matter if I even tell the recovery to reboot to bootloader.
I don't know exactly how the bootup structure is for androids but the only thing I can think of that may be the issue is the recovery itself if it wasn't the app that caused this. It just doesn't make sense that after a full restore, it would still have an issue, other than the recovery itself, UNLESS there is some secret boot instruction file that's stuck with a "Reboot_to_Recovery = 1" parameter.
Since this thing is stuck in a recovery boot, how would I be able to manually, without OS access, reflash another version of CWM on the device? Or if there's another possible way to fix this, please help me.
Maybe the ROM hasn't flashed on your phone properly .try again with a clean flash. may help
HiT Thank$ If HelPed
I believe this is independent of the ROM. I had noticed in preparing to flash a new ROM that instead of restarting to the OS, it restarted to the recovery. I didn't take much note of this, but it was clear that this problem began when I flashed the new recovery. Also, the fact that I had used 2 seperate, very different restores (full restores) with no success means that it couldn't have been the ROM.
My only probably clue right now is that the recovery is to blame (which is weird since CWM notes 6.0.4.7 as compatible with LG Spectrum. I had 6.0.1.1 before with no issue). I have no idea how to change this recovery however, given that I can't even boot the OS at all, and there doesn't seem to be a "flash recovery' option in recovery (which is kinda annoying).
Related
Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
Okay, so I'm not stuck in some sort of infinite loop here with my Infuse, it will show the Samsung logo, then the Samsung logo with the Cyanogen Mod logo, then CWM Boot Recovery. the thing is, that is all I can do. I have tried rebooting several times, tried to install various ROMs and flavors I have, all installations seem to fail, I have tried wiping and clearing and all that jazz, but I cannot seem to get it to install to anything. Recovery doesn't seem to be working either.
Does anyone know what I should do? I have Odin, but since I still have access to CWM on the device, I thought it might be better to get some more opinions before I totally wipe my everything with a fresh rom.
Maybe help
acidRain burns said:
Okay, so I'm not stuck in some sort of infinite loop here with my Infuse, it will show the Samsung logo, then the Samsung logo with the Cyanogen Mod logo, then CWM Boot Recovery. the thing is, that is all I can do. I have tried rebooting several times, tried to install various ROMs and flavors I have, all installations seem to fail, I have tried wiping and clearing and all that jazz, but I cannot seem to get it to install to anything. Recovery doesn't seem to be working either.
Does anyone know what I should do? I have Odin, but since I still have access to CWM on the device, I thought it might be better to get some more opinions before I totally wipe my everything with a fresh rom.
Click to expand...
Click to collapse
I run into something the last few times. There may be a problem with you losing root. I tried to install the last CM11, and it kept ending in the error 7 thing. Try this. Do the reset thing in cwm, then partition and then dalvic. Take the battery out, and restart it into cwm (hold both volume keys and press power. Then start all over and do the reset, partition, and dalvik thing again, and then try to install rom. Hope it helps.
acidRain burns said:
Okay, so I'm not stuck in some sort of infinite loop here with my Infuse, it will show the Samsung logo, then the Samsung logo with the Cyanogen Mod logo, then CWM Boot Recovery. the thing is, that is all I can do.
Click to expand...
Click to collapse
Can you see Cid on the booting screen or CyanogenMod 4.x.x flashing on the booting screen only without Samsung logo? And can you boot to recovery? Are u on kitkat? I think it's a Gapps problem! Use Paranoid Gapps mini modular!
If so I had a similar problem some time ago. Was about to smack the phone on the wall as it remained on the booting load screen! But I removed battery every time it blocked (about 7 times) and reboot! Took battery out again and left the phone off about 4 hours. Remember to charge if you think necessary. Switched on and after 5 minutes loading (yeah it's long), it finally booted successfully!
If doesn't work, do a dirty flash, i.e, go to recovery, flash same or a newer ROM. back, back, Reboot device. If stuck or error 7 appears on recovery screen, reboot to recovery again and flash ROM again, followed by gapps(I seriously recommend using MINI MODULAR PA paranoid GAPPS), and reboot device. If boot is successful, consider doing a Wipe Dalvik Cache. This should not delete any files!
If nothing works, I guess Odin back to Stock
sorry if this is the wrong section.
My problem is complicated. So i was trying to flash my first rom ever on my lg g2 vs980. The rom was Rashed's unofficial CM 12. So i was on twrp 2.7 but i tried to update to 2.8.5.1 i think it was. After doing this i also flashed the EFS backup final.zip file (i was following a youtube tut). then i flashed my radio.zip and su.zip. I was going make another backup after doing this but then it said backup failed and i think it wiped my phones storage so i decided to just flash cm 12.zip (i didnt wipe or factory reset anything myself). So the phone boots the the cyanogen boot logo and it said "upgrading android" and below it said something like "configuring apps". Then it changed to a blue screen and rebooted. Eventually it booted to "cm 12" and for a split second i can see whats supposed to be to be on the screen, but then it turns black besides the battery, time, and back button. Help?
I searched the forums before posting. 73 results came up and I read through and followed instructions of 7 different posts that seemed similar to mine (including the ones that appear when making a new thread), but nothing has worked or I haven't found a situation like mine.
Hi.
I have a HUGE problem and need help.
I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed the zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that according to someone in Oneplus forums. Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!
Thanks for any advice.
note: I used the signed flashable zip from here.
EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.
EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!
EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready). After that, I got the "Android is starting" "Optimizing app xx of xxx" message again, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!
EDIT 4: I remembered that I did a nandroid backup last February so I restored it with "restore" in TWRP. My phone has been stuck on the "Cyanogen" boot screen for about 40 minutes. I'm lost.
To recap everything:
1. I was trying to manually upgrade from COS 12.1 to COS 13.1
2. My phone was rooted, had TWRP recovery and ADB debugging was enabled in dev options. I can enter fastboot mode using hardware keys. I cannot enter recovery using hardware keys (shows a blank screen), but I can enter recovery using "fastboot boot recovery.img.
3. After I flashed COS 13.1, I was asked (in TWRP) if I wanted to install SU and I said yes and flashed it. This is when I was in a loop of being stuck on COS 13.1 splash screen for about 5-10 minutes and then my phone was "optimizing app xx of xxx" for 15 minutes and then rebooted and did everything all over again.
4. I tried to restored a nandroid backup using "restore" in TWRP, but phone is stuck in "cyanogen" splash screen for more than 40 minutes.
No replies...
Not sure what to do at this point.
I ended up wiping data and performing a factory reset through TWRP. Might try to upgrade again in the future.
I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.