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
Related
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
infinitybiff said:
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
Click to expand...
Click to collapse
Twenty seconds doesn't sound bad. I think it's the normal time for Nexus S to boot into recovery. Try checking some videos on YouTube of nexus a booting into bootloader. That should give you an idea.
Yea checked all that and asked other nexus s users. No one has this problem. going to try an older recovery.
Update on this:
Flashed back to an earlier recovery from fastboot. Its a 2.x version and reboot recovery is instant (or at least the speed it should be) When flashing the latest recovery from rom manager, the problem returns.
So I'm stuck. Obviously its an annoyance more than anything but the first time it happened I thought I bricked my $500 new toy
infinitybiff said:
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
Click to expand...
Click to collapse
The lag time was introduced with the 3.0.2.4 recovery, if it really bothers you flash back down to 3.0.0.5.
But i have it as well, im sure Koush will fix it soon
bringonblink said:
The lag time was introduced with the 3.0.2.4 recovery, if it really bothers you flash back down to 3.0.0.5.
But i have it as well, im sure Koush will fix it soon
Click to expand...
Click to collapse
glad to know i'm not crazy. thanks
Hello, I'm new to the forums and I feel bad I'm already screwing things up :/
Anyway on to the problem... I've had CM9 running on my phone for about two weeks now but I wanted to get rid of the rainbows in CWM and at boot. Today I downloaded Rom Manager from the market place, and when I ran it, it prompted me to install CWM recovery to my SD card, although I already had it installed I thought I'd give it a try. Bad idea, now I can't leave recovery mode, my phone will continually reboot into recovery, I've tried wiping all data and clean installing CM9 again and still nothing. I've even tried the exitrecovery.zip script to no avail
Any suggestions or ideas on how to fix it and boot into my ROM again?
Thanks!!
I would venture to say you might have to reflash...or start over from stock...
i would reload stock....then reload ics or the rom of your choice...
Thanks a lot! Worked like a charm, I used Odin and flashed factory stock 2.2.1, now I'm off to getting ICS back.
Thanks again!
Does anyone know why this happens? I've noticed that anytime I open CWM and choose the boot to recovery option is when I get stuck with CWM Recovery looping. I then have to go back to stock and start over again.
I'm not entirely sure why it happens, my guess was that it puts up a bad flag not compatible with ICS that keeps it from booting that, that was why I tired the exitrecovery script, I looked through it and it appeared to me to change a flag for booting. I'm not sure why it happens but I'd say just use the reboot to recovery option that the ROM provides in the shutdown menu, I know that always works.
So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.
Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..
Are you able to get into bootloader?
Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?
same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.
I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.
You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader
So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.
When I flash merely anything, my tablet gets stuck on the Samsung boot logo (I have waited, and waited, and waited, until the battery dies). Sometimes even installing ClockWorkMod Recovery (official) will do this. But I managed to get the latest official CWM flashed. But I can't get ANY other rom to work. Even roms I have successfully flashed before.
Note: If it flashes it gets stuck at the Samsung boot logo. But I have also had it not flash sometimes too, giving me error code 7 in CWM which is an authentication/permission/certificate problem.
I am going to try right now using Odin to flash to stock, and work from there, maybe it will completely clean out any crap in the memory.
My tablet is the P3113 model.
Ok! So after flashing stock rom, then cleaning all the cache stuff, then attempting to install CM it fails with CWM Error code 7. And when I just reboot system, it gets stuck at the boot logo. Damn, I get stuck there without even flashing!!
Well, I may have figured it out..... ummm i guess *cough! cough!* I somehow changed kernels *cough! cough!* dang, my allergies! Hahaha, anyways, I flashed a kernel compatible with stock rom and cm10.1 and it has gotten past the flash of cm10.1 and seems to be booting up right now.
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).