Database Develop

[Q] Stuck on SPRecovery; can't flash Clockworkmod recovery

Is there an sbf to flash clockworkmod recovery similar to the SPRecovery file used in the "how to root any droid regardless..." method? I've tried flash_image from terminal but get a not found error even though i know the clockwork.img file is right there at /sdcard. RomManager reports that it's flashed clockworkmod but when i reboot into recovery there's SirPsycho's green droid. Some alternate method to change my recovery back to clockworkmod would be greatly appreciated.
Background: Last night I restored my original rooted 2.1 nandroid backup to retrieve some notes and got distracted by a phone call and left it on too long. Maybe I missed my chance to avert disaster, so be it, but when i picked up my phone it was at the "ready to install update" screen and i *think* i just turned it off and tried to reboot into recovery. ( i was still distracted ). I became undistracted when i found that instead of good ol' CWR i had the white triangle / phone icon and no user recovery. So I sbf'd SPR onto it, then the busybox/su/root file, then rebooted, opened RomManager, flashed CWR, set up a restore to my current CM6.1RC3 and let it reboot. No joy; SPR came up instead and just sat there. Since then i've gone back into RM and "reflashed" CWR a few hundred times, tried several times to unsinstall and reinstall RM (same result). I've also downloaded the correct CWR.img file and tried to flash it from terminal emulator, no joy. I've tried using ROM Manager to flash an older version of CWR and can't, getting "An error occured while flashing your recovery."
lol i've also (inadvertantly/frustratedly) ended up removing the recovery altogether (probably from accidentally initiating an SPR backup and then battery pulling when it was an hour later and still not finished); after that booting while holding the "X" was stuck at "M"; but reflashing the SPR file from RSDLite got me the SPRecovery again.
When I have freshly flashed the SPR.sbf file, or flashed alternate recovery in RomManager, it reports SPR as the current recovery, and when i "flash" CWR from RomManaGER, it changes and reports that CWR 2.5.01 is the currently installed recovery, but no matter what i've tried, when i boot into recovery the text is blue not green. grr.
i've searched quite a bit before posting and am quite frustrated at this point. i've got a bazillion nandroid backups, but they are all clockwork and not SPRecovery format. The only way I now seem to be able to flash a different recovery is via RSDLite.
SO, either an sbf file to flash ClockworkModRecovery, an alternate way to change my recovery, or if there were some way to use SPR to restore from a nandroid backup created with CWR, but i'm not sure if the recovery itself is in the nandroid backup?
not pulling my hair out yet, but quite a bit past simple frustration.
TIA!

nevermind. after trying everything including reformatting my SD card, i took the latest update to RomManager and it successfully reflashed CWM. lol 69 views. Thanks for the tips.

Clockwork only sbf
Teddy helped me immensly on droid-forum when i had this issue, but i came across one of the things i could have used back then recently so wanted to post it up here if anybody else ends up in this situation.
Here's an .sbf that will reflash clockworkmod recovery, from Raidzero's thread on his RZRecovery:
http://rzdroid.com/ftp/recovery/Clockwork_2.5.0.1_sholes_recovery_only.sbf

CWM for Milestone?
Are U sure?

No, not at all. Forgot this was a combined device forum; I'm only talking about the Droid.
If all the recoveries and tools I've mentioned work on a milestone too I don't know. Apologies for not being more specific.
Sent from my Droid using Tapatalk

No problem... just that milestone uses Open Recovery...
Sent from my Milestone using XDA Premium App

[Q] Checking/ Verifying File System Health

My question is this: is there a way to verify that the file system and the overall ROM is operating healthy and without any corruptions/problems?
This is why I ask.
So, to make a long and frustrating story short I am/was running the Ginger Clone 2.2 Final R5 ROM and after disabling the lagfix, I installed the SpeedMod Captivate Kernal.
The installation of the kernal seemed to go just fine, after the initial startup I deleted the "disable-lagfix" folder/file and rebooted the device. However, when the phone restarted it froze on the "Galaxy S I9000" screen and would not boot into recovery mode.
After much profanity and futile ADB "reboot recovery" commands, I flashed the phone back to stock with Odin. When the phone loaded again I rooted and installed ROM manager, then I proceeded to restore the ROM backup that I made prior to flashing the new kernal. The backup loaded successfully, but when I started the phone again, it went into boot-loop at the AT&T screen.
Now at this point I'm really pissed off . I went back into recovery and cleared the partition cache and reinstalled the Ginger Clone Rom, fresh. Thankfully I heard the lady cyborg voice stating that the lagfix was being applied, success . The phone started up just fine, and I was able to reinstate the backup rom that I had created earlier.
So now, I'm left wondering if my file system is operating how it should be, sans kernal flash.
Thanks in advance for any and all help.

Again... I hate to be that guy but you are posting in the wrong forum.
Please read the stickies and the rules before you decide to post.
Sent from my GT-I9000 using XDA App

yogib83 said:
My question is this: is there a way to verify that the file system and the overall ROM is operating healthy and without any corruptions/problems?
This is why I ask.
So, to make a long and frustrating story short I am/was running the Ginger Clone 2.2 Final R5 ROM and after disabling the lagfix, I installed the SpeedMod Captivate Kernal.
The installation of the kernal seemed to go just fine, after the initial startup I deleted the "disable-lagfix" folder/file and rebooted the device. However, when the phone restarted it froze on the "Galaxy S I9000" screen and would not boot into recovery mode.
After much profanity and futile ADB "reboot recovery" commands, I flashed the phone back to stock with Odin. When the phone loaded again I rooted and installed ROM manager, then I proceeded to restore the ROM backup that I made prior to flashing the new kernal. The backup loaded successfully, but when I started the phone again, it went into boot-loop at the AT&T screen.
Now at this point I'm really pissed off . I went back into recovery and cleared the partition cache and reinstalled the Ginger Clone Rom, fresh. Thankfully I heard the lady cyborg voice stating that the lagfix was being applied, success . The phone started up just fine, and I was able to reinstate the backup rom that I had created earlier.
So now, I'm left wondering if my file system is operating how it should be, sans kernal flash.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
Well when you flashed back to stock and then restored your backup it went into a boot loop because the backup does not back up the kernel so the ROM you restored was trying to boot with the stock AT&T kernel...Not going to work. But when you did the fresh install of the ROM it had the kernel so it worked...

try afv or something like that in the market. Its by scary alien and you can verify md5 sum nand backup. i just flashed a new rom but once I get all set up I will come back with the name. Its a free in the market.
Sent from my GT-I9000 using XDA App

jhernand1102 said:
Well when you flashed back to stock and then restored your backup it went into a boot loop because the backup does not back up the kernel so the ROM you restored was trying to boot with the stock AT&T kernel...Not going to work. But when you did the fresh install of the ROM it had the kernel so it worked...
Click to expand...
Click to collapse
Thank you good Sir! That makes perfect sense.

yogib83 said:
Thank you good Sir! That makes perfect sense.
Click to expand...
Click to collapse
No problem Glad to help. Next time if you flash stock after installing ROM manager you can flash the kernel first and then don't boot up just go back into CWM recovery and then restore your backed up ROM and it will work fine.

[Q] Tab Missing Recovery?

Hello all..
So I picekd up a t-mobile tab off craigslist yesterday, which was pre-rooted (no superuser though) and has the Roto JMI rom (if that's what it is) installed with the 2.6.32.9 [email protected] #1 kernel.
Last night I tried rooting/installing CWM with the one click thing, run.bat or run.sh in my case since I'm on a mac. It wouldn't work and got stuck in a recovery loop. Every time I would boot, it would go straight to recovery. So I managed to get a data wipe done and now I'm back to the way it was before.
I rooted it with SimpleOneClick and it's rooted with superuser now. I've installed rom manager, tried to flash CWM, but when I do it just says successfully installed CWM.
When I try to boot to recovery, it just stops at the 'Galaxy Tab' loading screen. No stock recovery, no CWM, no nothing. The only way to get it out of this mode is to issue an ./adb reboot bootlaoder command. After I do that, it works fine. Can start up, shut down etc.
What did I do??? Is there any way to flash the recovery via adb push like I did the first time I rooted my phone? I can't seem to find the recovery to push to the phone, so yeah.. I'm confused here.
Thanks!!

sanchez said:
Hello all..
So I picekd up a t-mobile tab off craigslist yesterday, which was pre-rooted (no superuser though) and has the Roto JMI rom (if that's what it is) installed with the 2.6.32.9 [email protected] #1 kernel.
Last night I tried rooting/installing CWM with the one click thing, run.bat or run.sh in my case since I'm on a mac. It wouldn't work and got stuck in a recovery loop. Every time I would boot, it would go straight to recovery. So I managed to get a data wipe done and now I'm back to the way it was before.
I rooted it with SimpleOneClick and it's rooted with superuser now. I've installed rom manager, tried to flash CWM, but when I do it just says successfully installed CWM.
When I try to boot to recovery, it just stops at the 'Galaxy Tab' loading screen. No stock recovery, no CWM, no nothing. The only way to get it out of this mode is to issue an ./adb reboot bootlaoder command. After I do that, it works fine. Can start up, shut down etc.
What did I do??? Is there any way to flash the recovery via adb push like I did the first time I rooted my phone? I can't seem to find the recovery to push to the phone, so yeah.. I'm confused here.
Thanks!!
Click to expand...
Click to collapse
Not sure about t-mobile tabs (I've heard they can be a bit tricky) but if you can install Modaco/paulobrian kernel (thread in the dev section) then that has a fully working CWM built in. Backups and restores work perfectly with this. The "official" one from koush (sp) is abandonware...

paulshields said:
Not sure about t-mobile tabs (I've heard they can be a bit tricky) but if you can install Modaco/paulobrian kernel (thread in the dev section) then that has a fully working CWM built in. Backups and restores work perfectly with this. The "official" one from koush (sp) is abandonware...
Click to expand...
Click to collapse
I actually just got it all set up after trying many things using this thread:
http://forum.xda-developers.com/showthread.php?p=11713685
Worked like a champ.

sanchez said:
I actually just got it all set up after trying many things using this thread:
http://forum.xda-developers.com/showthread.php?p=11713685
Worked like a champ.
Click to expand...
Click to collapse
Excellent .

[Q]A problem in flashing mini(stuck at samsung screen)

I rooted my mini and then reverted back to factory settings(froyo).
Then,
using odin, with TASS_v1.0.ops and tass-recovery-cwm.tar I flashed Clockworkmod.
Using CWM, as said in http://forum.xda-developers.com/showthread.php?t=1167750, I installed update-cm-7.1.0-GalaxyMini-KANG-signed-09102011.zip. I wiped data and cache before and after. But still after reboot, My screen is stuck at samsung splash.
possible mistake:- using tass-recovery-cwm.tar on froyo as said in a forum. There, CWM-Froyo.tar was used for flash which I repeated to no vail.
Device is Indian.
I want to have a Cyanogenmod 7 ROM
edit:- Now, if I use tass-recovery-cwm.tar while flashing with odin, I nomore get a recovery screen

Since I couldn't do anything, I just rolled back over to GB again.

To get cmw working you need to have GB. After you can successfully install cm 7 following the guide

Yes.
My changing to fyro was accidental.

rak111esh said:
Yes.
My changing to fyro was accidental.
Click to expand...
Click to collapse
All you want to know about Samsung Galaxy Mini, rooting Flashing and Overclocking just click the link on my signature and you are there where everything will be very easy to do.

rak111esh said:
I rooted my mini and then reverted back to factory settings(froyo).
Then,
using odin, with TASS_v1.0.ops and tass-recovery-cwm.tar I flashed Clockworkmod.
Using CWM, as said in http://forum.xda-developers.com/showthread.php?t=1167750, I installed update-cm-7.1.0-GalaxyMini-KANG-signed-09102011.zip. I wiped data and cache before and after. But still after reboot, My screen is stuck at samsung splash.
possible mistake:- using tass-recovery-cwm.tar on froyo as said in a forum. There, CWM-Froyo.tar was used for flash which I repeated to no vail.
Device is Indian.
I want to have a Cyanogenmod 7 ROM
edit:- Now, if I use tass-recovery-cwm.tar while flashing with odin, I nomore get a recovery screen
Click to expand...
Click to collapse
you just tried to install cm7 on froyo which is note possible cm7 is made for gingerbread not for froyo first install gingerbread on your pop

Phone Stuck At Samsung Logo After Nandroid Backup

Hi,
Sorry for the long post but these are the events that took place.
Hope someone could enlighten me on the questions below. Thanks.
Questions:
1) What was the source of the problem, stuck at Samsung Logo (with Hydracore) ?
2) Is it safe to restore the first backup image (with Hydracore) with the existing CWM Manager or CF CWM Recovery ?
-----------------------------------------------------------
Problem: Stuck At Samsung Logo.
I was on stock LRQ / Hydracore Kernel 4.3b (std) and the phone was operating normally. A couple of hours ago, I did a nandroid backup with CWMR.. As usual, backup completed and phone rebooted. However, it was stuck at Samsung Logo but managed to go to Download & CWM Recovery.
Recovery processes:
Step 1:
- Recover last image backup with CWMR
- Clear cache & dalvik cache.
- Phone rebooted
- Stuck at samsung Logo.
Tried 3 times without avail, always stuck at the same place. So decided to reflash stock LRQ in Download mode.
Step 2:
- Reflashed stock LRQ with PC Odin
- Phone rebooted normally.
- Rooted phone with Super SU 0.95
- Phone rebooted normally.
- Installed Mobile Odin
- Reflashed Hydracore kernel 4.3b (std)
- Phone rebooted normally.
Not satisfied, tried Step 1 again a few times and the same problem; stuck at Samsung logo.
Step 3:
- similar process as Step 2 , ie, reflashed stock LRQ again.
- phone rebooted without problem.
The funny part is all my apps came back after boot, including the the crapwares from flashing LRQ.
Thereafter, upgraded firmware from LRQ to LRT via phone.
Also flashed a different safe kernel, CF-Root LRQ.
Step 4:
- flashed CF-Root LRQ with Mobile Odin
- phone rebooted without problem.
- made a backup with CWM Manager

I guess the backup got corrupted
When you restored the backup,all the apps got restored but there is something wrong in the backup and thats the reason the phone stuck at the boot screen
And when you flashed the rom using pc odin,you got those restored apps

could be a corrupted backup issue.
or was the nandroid made on the same kernel?
edit: not sure... but but ur post says ur phone was stuck after a nandroid backup .. or was it restore?

Thanks, it was after the nandroid backup, as written above. Any idea?
Sent from my GT-N7000 using Tapatalk 2

vfusion393 said:
Thanks, it was after the nandroid backup, as written above. Any idea?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
so u mean to say..
- phone working properly
- u reboot into recovery CWMR and do a BACKUP and not restore
- after the backup completes.. u select reboot system now
and the phone wont boot ?

YES...
Sent from my GT-N7000 using Tapatalk 2

vfusion393 said:
YES...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thats weird.
have u tried speedmod and a cwm backup on that?

nokiamodeln91 said:
thats weird.
have u tried speedmod and a cwm backup on that?
Click to expand...
Click to collapse
Read Step 4 (with CF-Root LRQ). No problem whatsoever until now.
Phone is operating even better now with LRT.
Thanks anyway.