Database Info

[Q] Phone force boots into recovery [Solved]

So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?

Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.

Handalaan said:
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Click to expand...
Click to collapse
Let me guess, you didn't convert back to RFS before flashing??
Try Factory reset. And don't use the backup you have for Cognition, Flash a fresh full ROM. Your backup could be messed up.
EDIT: Studa beat me to it.. Grrrr

studacris said:
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Click to expand...
Click to collapse
This is exactly what I needed to do. Apparently, (after finding a link I somehow overlooked before posting this) it had something to do with the format of the partition so upgrading the Stock to Cognition forced the RFS to EXT3 change allowing -all- of my backups to work. Thanks guys for getting me in the right direction.

Perhaps Im a little Slow
So Im suffering the same issue. Running Serendipity 7 update 2
I looked down at my phone one day and it was in clockwork recovery v2.5.1.2
I figured I had loaded it by an errant button press. So I selected reboot system now. It goes back into Clockwork right after the serendipity 7 splash screen.
Tried Factory Reset
Tried doing a restore
Tried doing a serendipity 7 re install Original and update.
I can install zips from sd card including the external one.
Any Recommendations ?

Stuck at splash screen after CWM nandroid restore

I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.

CZ Eddie said:
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
Click to expand...
Click to collapse
I dont know what ALOT of investment is.......but what i think happened here is this<<
You were on Gingerbread right, Infused v2.x.x and you made a Nandroid(thats fine)
u installed miUi and didnt have the luck you wanted...Thats fine
You went back to stock, and rooted and modded the Recovery so you could restore your nandroid....Thats fine
But if you went back to stock(Froyo Right) and try to load up a Gringerbread Nandroid on top it shouldnt work. Nandroids only back up the ROM not the Kernel......so you were in a sense trying to run a Gingerbread Rom on a Stock Froyo Kernel......
Go into CWM flash your Kernel, or use odin and flash a Ginger Kernel then go into CWM and RESTORE.
Happy FLashing

Didn't know that! That may explain a lot of my ROM frustrations.
I'll try this and report back.
Off to go find a suitable kernel....

I really should get my post count up so I can get past this horrible 10 post restriction.

Did you try initiating the flash through CWM or through ROM Manager? Honestly I don't prefer to do any work via ROM Manager, I always have more luck going through CWM and starting a flash from there. Kernel is the first place I'd start but you should also Factory Wipe and Cache Wipe each time you move between ROMs, sometimes you get very lucky and don't need to, most times you bork your phone, and if you're nandroiding back from a backup wiping before you restore is good practice just to make sure you don't leave anything behind from your old ROM.

I installed a gingerbread kernel:
http://forum.xda-developers.com/showthread.php?t=1212485
Version 1.1.
But it didn't work out.
So now I'm fighting with trying to get a stock Infused V2 ROM on there.
No luck yet. Once I do, I'll try the recovery again.

Btw, I'm using CWM for everything.

Go to mounts and storage in clockwork recovery then select format system then do your nand restore ...
Sent from my Samsung Infuse 4G - 1.6ghz

Wow, I was totally making some rookie (which I am) Android mistakes today.
Every time I tried to restore the backup image, I was doing it in CWM by selecting "install .zip from SD card". When I SHOULD have been using the "backup/restore" function.
I'm up & running again. All original apps/settings are restored. Great!
Now to start breaking things again, since I know how to restore from backup now.

[Q] Stuck on splash screen

ok i have another inspire and everything rooted fine flashed eva miui awhile back and havnt touched it sense. so yesterday i decided to update it to a working ICS build and i cant seen to get any of them to work. i have tried the recovery included with the ace kit and the 4ext touch recovery and talons recovery. all of them make it to the flashy boot screen and just sits there. i let it sit for almost an hour so obviously i did something wrong. now i cant flash any new rom. luckily i made a nandroid before doing all this so im still able to use eva miui but i cant flash a new rom. what am i doing wrong???
yes i wiped 3 times, factory, data, cache, dalvik
tried flashing rom twice before reboot to test.
switched to the 4ext recovery to convert everything to 4ext but still nothing.
all these roms say they have the kernel included so im guessing i shouldnt have to flash a different kernel

nevermind got the collective ics rom to flash. just not the aospX rom.

tsdeaton said:
ok i have another inspire and everything rooted fine flashed eva miui awhile back and havnt touched it sense. so yesterday i decided to update it to a working ICS build and i cant seen to get any of them to work. i have tried the recovery included with the ace kit and the 4ext touch recovery and talons recovery. all of them make it to the flashy boot screen and just sits there. i let it sit for almost an hour so obviously i did something wrong. now i cant flash any new rom. luckily i made a nandroid before doing all this so im still able to use eva miui but i cant flash a new rom. what am i doing wrong???
yes i wiped 3 times, factory, data, cache, dalvik
tried flashing rom twice before reboot to test.
switched to the 4ext recovery to convert everything to 4ext but still nothing.
all these roms say they have the kernel included so im guessing i shouldnt have to flash a different kernel
Click to expand...
Click to collapse
Deleted...didn´t see the second post

Sounds like a bad flash. Mine did that the one time I didn't verify md5 sum.
Zombies ate my Inspire

tsdeaton said:
ok i have another inspire and everything rooted fine flashed eva miui awhile back and havnt touched it sense. so yesterday i decided to update it to a working ICS build and i cant seen to get any of them to work. i have tried the recovery included with the ace kit and the 4ext touch recovery and talons recovery. all of them make it to the flashy boot screen and just sits there. i let it sit for almost an hour so obviously i did something wrong. now i cant flash any new rom. luckily i made a nandroid before doing all this so im still able to use eva miui but i cant flash a new rom. what am i doing wrong???
yes i wiped 3 times, factory, data, cache, dalvik
tried flashing rom twice before reboot to test.
switched to the 4ext recovery to convert everything to 4ext but still nothing.
all these roms say they have the kernel included so im guessing i shouldnt have to flash a different kernel
Click to expand...
Click to collapse
I'd get the same problem once, i flashed official rom, and then i used AAHK and everything was fine, hope it will helps.

Help with flashing ROMs

I've crawled through the development. I've flashed a ROM before, but went back to a rooted stock version because of the bugs in the builds I was using. But now, basically any time I flash something new, it bricks at the Galaxy Tab 2 7.0 screen.
I've done:
Flashed back to non-root stock firmware (newer)
Then flashed the CF Autoroot, installed Mobile Odin, flashed CWM official 6.0.2.3 for the 3113. When I install CM9, brick.
PA doesn't brick immediately but sticks at the splash with the shark.
So, I flashed back to non-root stock, CF Autoroot, installed CWM 6.0.1.1 and tried again. All ROMS besides PA hang at boot screen (like before), PA hanging at the shark.
I figured it was a kernel issue? So, I've tried both Dhollmen and AGNI. No change.
I can get it to rooted stock JB, but I don't *want* that, I want something that isn't so freaking bloated and buggy.
Ideas?
*edit*
So, after installing TWRP 2.5 on top of stock, I downloaded Rom Manager, installed CWM and CM9 through that. Got past the initial boot screen, but seem to be stuck on CM Splash. Would flashing older stock image and trying from there help?

This might seem like a dumb question since you say you have flashed ROMs before: are you doing a "clean" install? I also will wipe cache and dalvic cache AFTER each install. I only have "bricked" a device one time and that is when I tried short cuts. I also ALWAYS follow the developers instructions to the letter.
Sent from my GT-3113 running DF-2

Clockworkmod not working anymore.

Well I have been a CWM(and sometimes also TWRP) user for years. But I am stumped. I recently started having issues staying connected to AIO/Cricket(voice not even staying connected). As I am running a custom ROM I decided to try Stock and see if the problem persists, thus it may be a hardware issue with the radio or something. So I did a current backup, and restored one from a few weeks back. It's the same ROM but I thought it was worth a shot. It restored fine but the problem persisted. Then I decided to restore my new backup from the hour before. It failed. Gave me an MD5 Mismatch error(I think I have that right). So I made another new backup, same thing. I am unable to restore any backups made right now. I can still restore the one from a few weeks ago. I am running the very latest CWM touch. I tried flashing TWRP to see if that might help(using Rom Manager to do so). This has always worked before. It said that it works, and even tells me it's rebooting into TWRP when I reboot to Recovery. But the broken version of CWM is still what is loading. I am at a loss here.

your issue here is that you are using rom manager. rom manager doesnt fully work, it is broken, stop using it. you can flash a new recovery the right way, via fastboot. you can also flash twrp using the flashify app(yes, it works).

simms22 said:
your issue here is that you are using rom manager. rom manager doesnt fully work, it is broken, stop using it. you can flash a new recovery the right way, via fastboot. you can also flash twrp using the flashify app(yes, it works).
Click to expand...
Click to collapse
Thank you! Gonna try flashing TWRP that way now!

Landara said:
Thank you! Gonna try flashing TWRP that way now!
Click to expand...
Click to collapse
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.

simms22 said:
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.
Click to expand...
Click to collapse
First thing I did. I was able to backup with TWRP. Since I am currently running the restore from that NANDROID from a few weeks ago, it's all good! I am restoring the TWRP i just made, just to be sure. Seems to be restoring fine though. With my NANDRIOD problem solved, I can work on getting this radio issue fixed. I am really hoping it's just ROM related and I can salve it by flashing something else. I'm going to flash STOCK and see if it persists now.

simms22 said:
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.
Click to expand...
Click to collapse
Actually one fast question, if I may. Would it be at all risky to flash the stock radio onto a custom ROM? That seems the easiest fix, if it is a fix at all. I downloaded the correct stock radio for my 820 from here:
http://forum.xda-developers.com/goo...-android-4-4-2-kot49h-rooted-busybox-t2557523
If I just flash it over Nikxus would there be a problem?

Landara said:
Actually one fast question, if I may. Would it be at all risky to flash the stock radio onto a custom ROM? That seems the easiest fix, if it is a fix at all. I downloaded the correct stock radio for my 820 from here:
http://forum.xda-developers.com/goo...-android-4-4-2-kot49h-rooted-busybox-t2557523
If I just flash it over Nikxus would there be a problem?
Click to expand...
Click to collapse
no problem, in stock or custom roms the radios are the same

simms22 said:
no problem, in stock or custom roms the radios are the same
Click to expand...
Click to collapse
Thanks!