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 ?

[Q] *ClockWork Mod Recovery Issue.

Hi guys I really hope someone can help me with this. I was running CM7 Nightly rom and decided to try and flash eaglesblood 2.3.5 and it flashed ok but the problem is that when I tried restoring my back-up on it I get an clockworkmod recovery error. Any Ideas?

what does the error say?
most likely it was a bad backup and slim chance of restoration
did u do a full wipe before restoring?

Yes I did a full wipe before flashing and also before I tried to restore my black-up thru rom manager.I have flashed plenty of roms and this phone am not a total noob when it comes to this phone. I have never encountered this problem before. Before i tried going into recovery thru rom manager to restore back up thru CWm 4.0 etc, and it says I need CWM 5.0. I updated the rom manager to 5.0 etc and when I reboot and go into recovery (not thru rom Manager) and it says that it is the 4.0 etc version.Also is the 5.0 etc version blue? it jumps from 4.0 to 5.0 back to 4.0. This is a lil weird I went into recovery and did a restore from there and when I try in RM it comes up with error message Cannot restore cuz my CWm is 4.0 etc. thats when it jumps back from 5.0 to 4.0. I know this is confusing and by the way all the etcs you see are because I don't know the exact version. Any helps and thnx to whomever does.

deder21 said:
Yes I did a full wipe before flashing and also before I tried to restore my black-up thru rom manager.I have flashed plenty of roms and this phone am not a total noob when it comes to this phone. I have never encountered this problem before. Before i tried going into recovery thru rom manager to restore back up thru CWm 4.0 etc, and it says I need CWM 5.0. I updated the rom manager to 5.0 etc and when I reboot and go into recovery (not thru rom Manager) and it says that it is the 4.0 etc version.Also is the 5.0 etc version blue? it jumps from 4.0 to 5.0 back to 4.0. This is a lil weird I went into recovery and did a restore from there and when I try in RM it comes up with error message Cannot restore cuz my CWm is 4.0 etc. thats when it jumps back from 5.0 to 4.0. I know this is confusing and by the way all the etcs you see are because I don't know the exact version. Any helps and thnx to whomever does.
Click to expand...
Click to collapse
You need to update thru NVFlash. Here is the link and everything should be fine after that. http://forum.xda-developers.com/showthread.php?t=1054492

Thanks guys u rock. I got the new CWM on there for nvflash. Now I am moving my saved back up zipped file from downloads to CWM on sd card after I zip it, so well see how this goes right now. THanks again

With the G2X don't use rom manager for your backup/restore. Boot directly into the clockworkmod that you installed with nvflash and do the backup/restore from there.

[Q] Can't Flash ANYTHING!!!!

Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0

Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,

bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.

What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.

Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill

[Q] Failed to Use CWM and ICS on phone and now I have a problem

Hi guys, I'm relatively new to this forum.
I've been trying to upgrade my Tmobile LG G2x phone to ICS by using an AOKP ROM that I found online. I followed the instructions on how to use a CWM from this site and all of that worked. However as I was copying the AOKP file to the phone, I realized that I had already extracted that file to my phone instead of leaving it as a zip.
When I booted my phone in CWM I tried to access the install zip from Sd card> choose zip from Sd card> then select the aokp_p999-test2.zip to start flashing the AOKP ROM (ICS). However, all I saw were a bunch of files.
The real problem: I followed these instructions earlier:
Now do a full wipe by selecting Mount and Storage then wipe the following:
Format System
Format Data
Format Cache
Go back to main menu and select advance then wipe dalvik-cache.
Apparently I didn't have a backup, so when I wiped all these formatting files and tried to boot back to my phone to recopy the files, I'm stuck on a blinking screen during boot... I have no way of returning back to my phone and I'm freaking out right now...
Tried using a Flash Stock Recovery option, but I get stuck on the page and can't click on Reboot System now.
HELP ME PLEASE...WHAT DO I DO

AOKP has not been updated for this phone in some time, there are a couple of links to the builds on page 102 of that thread if you insist on trying that out. I'd suggest trying a different ROM from the the development section that has been more recently updated though.
Can you not boot into CWM again hold down the Power & VOL down buttons when you turn your phone on? If not try this: ROM for recovery G2X under the NVFLASH

xBkKx said:
AOKP has not been updated for this phone in some time, there are a couple of links to the builds on page 102 of that thread if you insist on trying that out. I'd suggest trying a different ROM from the the development section that has been more recently updated though.
Can you not boot into CWM again hold down the Power & VOL down buttons when you turn your phone on? If not try this: ROM for recovery G2X under the NVFLASH
Click to expand...
Click to collapse
I can boot into CWM, but apparently I never backed up any files from my phone...
Also, will the new ROM for recovery let me boot into my main screen?
Thanks

Chokachilds said:
I can boot into CWM, but apparently I never backed up any files from my phone...
Also, will the new ROM for recovery let me boot into my main screen?
Thanks
Click to expand...
Click to collapse
The directions in that thread should get your phone to boot back up with the stock ROM installed but since you could still try to just boot into CWM after downloading a different ROM and flash it. There are nandroid backups of the stock ROMs HERE that you can download and unzip the folder into your Clockworkmod/backup folder to have a backup
Sent from my LG-P999

Alright that worked! Now I want to try again to get a ROM for ICS. Since you said that the AOPK one is outdated, do you have any suggestions or links to new ones that work well? I know it's off-topic, but thank you!

Chokachilds said:
Alright that worked! Now I want to try again to get a ROM for ICS. Since you said that the AOPK one is outdated, do you have any suggestions or links to new ones that work well? I know it's off-topic, but thank you!
Click to expand...
Click to collapse
ICS is all.sorts of broken as well as jelly bean. but go look in development section and read and read and read.
than choose!
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel

Moved to proper forum.

[Q] Confused as to what to do next: un-bricked, but recovery is still a garbled mess

So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.

It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.

Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk

I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker

One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium

UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it

MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app

UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info

MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.

UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us