Related
A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
gtcochran said:
A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
Click to expand...
Click to collapse
Common knowledge that the version of Cognition you are running is not supported by ROM Manager, it is 3e recovery and Clockwork needs 2e. You can update to the newer Cognition which has 2e recovery. I recommend you read the facts sheet befor flashing, the method you should use is Odin one click back to stock http://forum.xda-developers.com/showthread.php?t=731989, then master clear so that nothing is lingering from your previous setup, backup everything from your internal storage to your pc first, this will wipe everything from your internal, replace it after you finish Master clear. you should only replace the update.zip, ClockworkMod and your music, photo's and that stuff. Backup your apps using Titanium Backup.
Here's the link for the new Cognition http://forum.xda-developers.com/showthread.php?t=786532
So I tried what you recommended and got my phone back to the stock condition but I'm still not able to use ROM manager or flash another ROM. After I root the phone I install ROM Manager, flash it to the current edition and then try to reboot into recovery but when it gets to recovery it gives the following error message...
--Installing from package...
Finding update package...
Opening update package...
E:Can't open /cache/update.zip
(bad)
Installation aborted
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
gtcochran said:
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
Click to expand...
Click to collapse
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Pirateghost said:
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Click to expand...
Click to collapse
LOL, +1
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
gtcochran said:
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
Click to expand...
Click to collapse
so put it in download mode, and use ODIN one click back to stock...then leave it the hell alone....
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
When you go into stock recovery now is it version 2e or 3e?
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
if you used the one click back to stock then you are on the stock kernel.....what makes you think you are not on the stock kernel?
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
gtcochran said:
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
Click to expand...
Click to collapse
Rom manager will work just fine with 2e recovery. Just delete any update.zip files you have in your home directory - then open rom manager and reflash clockworkmod the cappy - then you should be good to go.
As for whether or not that is the stock kernel I am not sure, but how can you tell just by looking at it if you don't know which kernel is the stock one?
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
Master clear should've done that. If you are restoring your apps and settings using Titanium Backup then you are restoring user data which you should not do.
When you Master Clear is your device on and on the home screen, it needs to be. Don't Master Clear in Recovery mode or Download mode or it does nothing. Also you need to have debugging on.
2.6.29
[email protected] #2
That is the stock kernel. Just so you know if you are running stock with root you can simply place the update.zip from the Clockwork folder, you should have backed up before flashing and Master clear, back into your internal. ClockworkMod does fail on first attempt to flash sometimes, it happenned to me the first time I flashed it, the second time worked like a charm. Are you rooted? You need root to use ROM Manager and debugging should be on.
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
After you deleted the update.zip then opened rom manager and flashed clockworkmod it should of put a new update.zip on your phone in your home directory - can you confirm that this is the case?
Also you may not have had a successful master clear - you may want to do it again then redo odin3 one click. Also if I am remembering correctly I believe you have the option to clear cache or user data or both in stock recovery you may want to try that as well.
It all works now. The issue was with the master clear. I guess that I did try to run it in the download mode. Thanks a million guys, i really appreciate it.
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
gtcochran said:
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
Click to expand...
Click to collapse
/sdcard/update.zip should only boot into clockwork recovery from stock recovery or boot to stock recovery from clockwork recovery if you flashed clockworkmod correctly from rom manager - and so long as you are not renaming any other files as update.zip after you flash clockworkmod recovery.
Which custom rom are you attempting to install?
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
gtcochran said:
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
Click to expand...
Click to collapse
When you first boot into recovery it should be stock recovery. While in stock recovery when you select reinstall packages it will reboot into clockwork recovery - if you flashed clockworkmod recovery correctly from rom manager and it put the appropriate update.zip into your home directory.
And just to note: don't be renaming any files as update.zip if you are using clockwork recovery to flash something.
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
Hi,
I really need some help as I began to get crazy about this.
I also have to mention it's my first time into Root/Mod/Custom/etc...
I Have a GT-I9000M (BELL) with Android 2.2 (version FROYO.UGJK4) Kernel 2.6.32.9
I successfully Rooted the phone with Superoneclic (Have Super User app in menu)
I Installed Rom Manager 3.0.0.0 Then authorized sudo when prompted to do it.
After that in the recovery menu of Rom Manager i've downloaded the Clockworkmod thing. (2.5.1.2)
I've tried to boot into clockworkmod but I got the standard Recovery Boot from Samsung instead. (tried to re-install rom manager to see if work but no)
I also tried to install it by using the update.zip version got here http://www.multiupload.com/5CUIK88JM0 and put it at the root of the internal sd.
Booted into the Samsung Recovery Boot and press apply Update.zip then i got
the following error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborded
(Tried Twice still nothing new)
The goal of all this is to install Darkys_v6.0_Gingerbread_Edition_Voodoo_signed seen here: http://forum.xda-developers.com/showthread.php?t=814091
What do I do wrong???? Help me please i'm tired of the Android Froyo version from Samsung+Bell
To get ClockWorkMod compatibility, you need to use ROM Manager to start them.
This way, Voodoo recognize it's CWM recovery, intercept the call to the update.zip and install Ext4 wrappers.
If the new version is not yet available in ROM, be patient
I found the recovery app doesn't work very well. I suggest installing a kernel with CWM , that's compatible with Bell hardware? via Odin and you're good to go. From recovery menu you can do anything, including a full backup.
Supercurio I Need Help
MOD EDIT: Teranox, our forum rules specifically state that non-engish posts are allowed only if an english translation is provided as well. Please add that here, or the post will be removed
supercurio this one is for you:
What is voodoo
i'm using Rom Manager but notjing seems to work. even OCLF
it's like even if i'm rooted i can't do anything....
can't use lagfix
can't use le clockworkmod
can't use le rom de darky....
you seem enough advance in android to answer me (I saw you post & video on the Nexus S ported to SGS)
Thank you to answer me
You must be in 2e recovery for CWM
Sent from my GT-I9000 using XDA App
jsen said:
You must be in 2e recovery for CWM
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
How to get from 3 to 2e? I'm on JPO 2.2. Thanks
It is not the first time i heard about 2e recovery and cwm
thing is: i'm new to all of this. Can someone explain me what those 2 things mean and do?
Do you mean that i have everything to do it right but there is something i do wrong or forgot?
mirzahodzic said:
How to get from 3 to 2e? I'm on JPO 2.2. Thanks
Click to expand...
Click to collapse
You can find the thread called 'CFroot' at the android development section.
Download the correct version based on your current firmware and follow the instructions there. When you are done, your recovery would be 2e.
Sent from my GT-I9000 using XDA App
My only concern after had read cf-root post is that none of the zip package offer somethong for ugjk4
Teranox said:
My only concern after had read cf-root post is that none of the zip package offer somethong for ugjk4
Click to expand...
Click to collapse
Sorry dude, the only solution would be to flash to an Eclair ROM (which by default has a 2e recovery) or flash Froyo which is supported by CFroot.
I have the same issue as well. Wanted to try Darky's v6.0 rom, however stucked in getting to CWM since I'm on 3e. I did look at CFRoot, but nothing stated for JK4.
Teranox said:
Hi,
I really need some help as I began to get crazy about this.
I also have to mention it's my first time into Root/Mod/Custom/etc...
I Have a GT-I9000M (BELL) with Android 2.2 (version FROYO.UGJK4) Kernel 2.6.32.9
I successfully Rooted the phone with Superoneclic (Have Super User app in menu)
I Installed Rom Manager 3.0.0.0 Then authorized sudo when prompted to do it.
After that in the recovery menu of Rom Manager i've downloaded the Clockworkmod thing. (2.5.1.2)
I've tried to boot into clockworkmod but I got the standard Recovery Boot from Samsung instead. (tried to re-install rom manager to see if work but no)
I also tried to install it by using the update.zip version got here http://www.multiupload.com/5CUIK88JM0 and put it at the root of the internal sd.
Booted into the Samsung Recovery Boot and press apply Update.zip then i got
the following error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborded
(Tried Twice still nothing new)
The goal of all this is to install Darkys_v6.0_Gingerbread_Edition_Voodoo_signed seen here: http://forum.xda-developers.com/showthread.php?t=814091
What do I do wrong???? Help me please i'm tired of the Android Froyo version from Samsung+Bell
Click to expand...
Click to collapse
This Might Work.... Although I Have A Different Phone (Cdma Hero), But Had A Similar Issue....
The Way I Was Able To Correct My Problem Was To Re-Install A Older Version Of "Rom Manager" (Let Me Know If You Have or Need A Older Version, I Keep'em All Now!! Lol!!
Also In "Rom Manager" I Would Try To Flash Alternate Recovery, And Then Clockwork Recovery Right After!! Make Sure It Says *Current Recovery* -And- *Latest Recovery* (Up At The Top) Then Try To Boot Into Recovery!!
PM Me If You Need More Help!!
Sent from my HERO200 using XDA App
Fresh Start
Ok well I got a good night of sleep so i'll resume where I am
I learned yesterday the following:
CMW: Clockworkmod
OCLF: One Clic Lag Fix
Now what I could try is to get back to Original Firmware of the GT-I9000M (Eclair) and from then what I've understood is that I don't need 2e recovery? Am I right?
From then I could install Darky without anything.
By going back this way will i'll stay root of will I have to root again?
If all this is right, how do i go back to eclair? can it be done via the 3e recovery menu or I have to flash? Is so I don't know anything about odin and the way it work so i'll need your help loll
rafi92 said:
Sorry dude, the only solution would be to flash to an Eclair ROM (which by default has a 2e recovery) or flash Froyo which is supported by CFroot.
Click to expand...
Click to collapse
here's what I did now:
Used Odin and Flashed my firmware to the previous one (2.1 Eclair.UGJH2)
Re-rooted
Re-installed Rom Manager
When in recovery mode i see 2e but it's the recovery from Samsung. Can't see the CWM......
Think i'm pretty close compared to yesterday from Darky 6.0 but STILL NEED CMW lolll
Fist timer Root and Flash never easy lolll
OK GUYS GOOD NEWS!!!!
Don't know what I did but CWM WORK NOW!!!!
What i've read somewhere is to never open the zip files (what i did). Got the idea of flushing them and download it again. This time it worked.
Gonna let you know when running Darky
----!!!!WORKING!!!!----
I Have Darky 6.0 Running on my Bell GT-I9000M!!!!!
First I want to thanx everyone of you who helped me out! You've been a great help.
Also I want to get the summary of my actions so Others could take advantage of this thread.
-Froyo version FROYO.UGJK4 (that is the official GT-I9000M update from BELL Mobility) was painfull to do anything so I downgraded to the eclair.UGJH2 (that is the Original Firmware from Bell)
First I've Rooted my phone using Superoneclic 1.5.5.0 that you can find here:
http://forum.xda-developers.com/showthread.php?t=803682 (enable debuging mode on the phone in Settings-applications-developpement-debuging) then plug the phone and on superoneclic press ROOT...wait and follow indications
Then went to ODIN 1.7 that you can find here
http://www.general-search.com/fileinfo/20192867
You can find the BELL 2.1 firmware
here http://www.multiupload.com/ZNBT2RY5Y0 Password is samsung-firmwares.com
In odin i've used the 512.pit file (place it in the Pit section)
Then placed the 2.1 Firmware in the PDA section.
Took care Repartition, auto-reboot, F.Reset Time check box was check.
Booted in download mode (to get it right with odin i've booted in recovery first: Vol Up+Home+Power when bootscreen appear released it. After Pressed on Reboot now and immediatly pressed Vol DOWN+HOME+Power) I GOT THE BIG YELLOW LOGO OF ANDROID and in ODIN i got the Yellow icon appeared.
At this moment I've pressed START in odin and waited. The phone was acting like when updating through Kies.
When finished I was on ECLAIR
After, I've Re-Rooted the phone with superoneclic again.
Installed Rom Manager
Downloaded the CMW (CLockworkmod) that you can find here:
http://www.multiupload.com/5CUIK88JM0 (DON'T OPEN THIS ZIP BECAUSE IT WILL BREAK THE SIGNATURE NEEDED TO VALIDATE THE FILE)
I've placed the update.zip file (CMW) at the root of the internal SD Card of the phone and rebooted into recovery mode. I went on the apply update.zip (first time it was not working, then second time it worked)
At this moment I was on Android 2.1, Rooted, and CWM Recovery was working.
To Install the Darky's v6.0 Gingerbread Edition, I've downloaded it here:
http://www.multiupload.com/YPQVS4WO9C (ONCE AGAIN DON'T OPEN THE ZIP)
I've placed it at the root of the phone (same place than update.zip)
Opened Rom Manager, and selected Install a Rom from SD Card.
I've selected the zip File and applied it.
Phone went into recovery mode by itself then started installing Darky. (took like 5 minutes but it is said to be between 5-10 minutes so...)
HURRAY I'M ON DARKY CUSTOM ROM!!!!
PS: (at boot screen GT-I9000M will change to GT-I9000), Boot Screen Animation will also change for the Nexus One Boot animation.
Took me a day and half from Noob to This but hope other Bell user (or SGS user) will find their solution here.
Now let me alone I have to play with my new toy lolll
Just got back home. I will follow your footsteps. Do you have 850 mhz band ?
You with Bell ? Any problem making and receiving calls using Darky's rom ?
Followed your steps. Now I'm running Darky's v6.0 rom.
Even if it's a Bell phone, i'm using it on rogers.
I don't have any band problems(yes i have the 850 band). In fact, since i'm on Darky it look like if the wifi and phone antenna is far better. I got reception in places i wasn't before...and can even say GPS lock my position accuratly in less than 10 sec
Everything is.better since darky run on my phone
Sent from my GT-I9000 using XDA App
Hey, can you please clarify the ODIN steps? I have the exact same problem seen here.
I've completed up until where you put the phone in download mode. I set up ODIN as described, then connected my phone via USB, then enetered Download mode - but I only get a yellow icon on the phone, not in ODIN. Have I gone wrong somewhere?
Hey guys, I'm fairly new to Android, and even smart phones in general, but I need a bit of assistance.
I bought a phone from a friend in Canada, the GT-I9000M.
I live in Australia, and I'm trying to unlock it to work here. I wasn't having much success with getting root of the phone etc, so I decided to have a look at cyanogenmod.
I have followed this wikipedia article by every character: wiki.cyanogenmod[dot]com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
However, the phone acts a bit odd. It'll boot up, show the cyanogenmod splash screen, then load to a recovery menu, but then the text will fly up very fast, and the phone just reboots itself in an endless loop. I managed to get a photo of the menu before it rebooted itself, and found this (Link to an external image, since I can't post them yet):
dl.dropbox[dot]com/u/203420/DSCF2542.jpg
And this is where I'm stuck. I have the cyanogenmod update zip on the SD card, but it seems to give a "SD card marker not found", and resort to looking on the phones internal memory (Which obviously fails).
I've tried a few other things, like flashing the boot.img file instead of the zImage (Which actually gets me further than just the zImage, which sits in the galaxy S splash screen).
Any help would be greatly appreciated
Regards,
Dan
Have you tried reflashing the phone with the KG3 firmware?
Have you tried reflashing the phone with the KG3 firmware?
Click to expand...
Click to collapse
same problem here... CyanogenMod wiki articles have instructions for I9000 and the T959, but not the I9000M. I'm looking for a kernel zImage with CWM recovery for the I9000M.
As for the KG3, I've found a 3-files version, but couldn't manage to flash it with Heimdall...
This is not bad, I had this when trying to boot one of my ports.
To fix:
1. Flash custom kernel through Odin (devil, semaphore for example)
2. Now directly boot into recovery, which should now be cwm.
3. Flash desired ROM and wipe data/factory reset, clear dalvik, cache etc.
4. Boot up!
Sent from my GT-I9000 using xda premium
So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.