Database Develop

[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] ClockworkMod: An error occurred while attempting to run privileged commands.

ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n

nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
You prolly fixed this already but in case someone else has this issue. Try installing Busybox from the market.

Same issue and won't boot into clockworkmod recovery
nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
I rooted my phone with eclair installed and used clockworkmod recovery with no issues until I one day wanted to go back to stock and attempted a restore of the backup I made right before flashing the OverStock ROM. The phone wouldn't boot, so finally got the Overstock to go back. Phone worked fine for the most part, but from then on to get into recovery mode, required shutting down and using button presses (Up/down vol/PWR button) and it would go in fine. Could never get Clockworkmod to go into recovery mode with a click. Saw that (finally) Samsung has published a Froyo update, so took back to stock eclair using ODIN3 so I could use Kies mini to update. Did a factory reset to remove all old info directories and data. Update went perfect, but want the option to use the rooted apps (Titanium backup and ClockworkMod--purchased apps) to play with my phone as I see fit. Used SuperOneClick to root phone and verified I can get superuser with using terminal emulator, successfully executing "su" command. Problem is I can't get into CWM recovery. Only get "Android system recovery <3e>". Tried uninstalling CWM and reinstalling. Re-Flashed CWM recovery and it lists version 2.5.1.2 as current and latest.
I obviously need CWM recovery to flash different ROMS, but wanted a current backup before starting. Can't get any further until I figure this out. Any help would be appreciated. I was a noob, just a month ago, but was feeling pretty confident until this happened. Guess I'm still a noob, but just a little more dangerous now. Thanks in advance.
Just noticed that I wasn't in a phone specific thread, so here's my phone details... Samsung Vibrant (T-Mobile).

CWM issues with Milestone
In the last update of the RomManager was added support for version ClockWorkMod 3.x for Milestone - but still unable to use the CWM as standard recovery.
Using another recovery as OR1.4 you can start CMW from the SD card - but that does not solve the problem of RomManager stay with completely limited functions.
The Rom Manager is having updates constantly and I think we have a working version for Milestone soon - but in part I'm upset to see that the Milestone is listed as a supported device - when in fact it is not.
I bought the full version of Rom Manager because I believe it is a great tool and I hope someday I can use all its functions.

I have the same problem. I use OpenRecovery for Sholes to do those things. I hope we can use those tools like a normal user even a day.

[Q] Trying to flash Serendipity 6.3...

I've never flashed a rom before. I currently have stock froyo with the paragon kernel i flashed using the app sgs kernel flasher. I have clockwork mod rom manager, I created a backup of my current rom. So then I tried installing the serendipity rom from the sd card but i get an error message. I read on the sticky on how to flash a custom ROM you need to use ODIN and flash back to stock 2.1 then do a master wipe and re root it and stuff.
Their link to download ODIN is broken so I don't know how to get it. And is there really no other way to flash it besides doing a master wipe and using ODIN?

flash to stock and master clear is not needed. what IS needed are specifics on WHAT error message you get when trying to flash the rom you want

The error message is
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted"
Then it brings be to the blue menu so i just select reboot system now

bad download, re-download rom.

May be completely off, but it doesn't sound like you're actually in clockwork mod recovery, but rather stock recovery.
But here's the post with the one click odin with mirrors and I personally would suggest useing it since I generally like to stick to as clean a flash as I can:
http://forum.xda-developers.com/showthread.php?t=731989
Second, I don't know if you've ever seen MobileTechVids tutorial on how to flash custom roms, but I suggest you watch the full series first if you haven't already.
here: http://www.youtube.com/watch?v=MsafJ-9uRqk
I watch the series and try and stick as close to the tut as I can when I'm unsure (or the one provided by the Rom maker as they know what's best for their rom)...
One suggestion, when flashing Serendipity disconnect your phone from cable right before the actual flashing (gave me a glitch in which I couldn't mount storage via usb). Other than that, read read read. I feel it's all I do when it comes to this stuff, but proper research is indispensible.

thresherhorn said:
May be completely off, but it doesn't sound like you're actually in clockwork mod recovery, but rather stock recovery.
Click to expand...
Click to collapse
+1
Is the text on Recovery mode blue or green? If its blue, you're on stock recovery.

+2
Sent from my SGH-I897 using XDA Premium App

Ok I got the stock rom flashed back and rooted it using one click. Now for some reason I can't reboot into clockwork recovery mode. I flashed it successfully. So i click on reboot into recovery and nothing happens. I try clicking on install room from sd card and that doesnt work either

Power off, hold 3 buttons att screen will come on. Keep holding. Screen will go off. Keep holding. Screen comes on again let off the power button but keep the volumes held, this will boot you into stock recovery, since you said you flashed cwm already I'm assuming you mean with rom manager, so the update.zip should be on your sdcard, so just reinstall packages twice and you should boot into cwm.

AIO tools work well and make flashing roms for new people easy and painless
use a search for it

steph2 said:
AIO tools work well and make flashing roms for new people easy and painless
use a search for it
Click to expand...
Click to collapse
+1.
AIO and superoneclick for root/flashing roms makes the process much easier.

crag11 said:
Ok I got the stock rom flashed back and rooted it using one click. Now for some reason I can't reboot into clockwork recovery mode. I flashed it successfully. So i click on reboot into recovery and nothing happens. I try clicking on install room from sd card and that doesnt work either
Click to expand...
Click to collapse
On serendipities main "download" page they have instructions to install. In those instructions is a link to a file you can download. Place that file along with the serendipity 6.3.zip file in the root of your sd card. Use the " 3 button" technique or Rom managers "reboot to recovery" option to get into stock recovery. Hit "reinstall packages" once/possibly twice. That will put you into clockwork mod recovery. Select install zip from sd card, find the serendipity6.3.zip and click power to flash. Confirm. And after it does some stuff it will ask you to reboot. Upon reboot it will as if you want to enable lagfix. Hit plain "Yes". Watch it do its thing and viola...
You have the "dirty" way of how to flash serendipity... But first I please ask you to spend atleast a day reading this forum or others and understanding these instructions and the reasons behind them.

followed instructions off the website and still doesn't work
I was running 2.2 and have done a lot of reading a video watching (thanks Mobile Tech videos) and finally conjured the guts to flash serendipity.
I flashed stock using odin...that went great. Copied the update.zip to sd card. Installed zip twice in 2e recovery. Copied Serendipity.zip file to sd card. started in recovery mode, selected "install from sdcard" selected serendipity.zip file and it seemed to go through that process rather quickly. Then I selected reboot and then everything just started FCing all over the place. Can't even load the stock that I had on there. I don't know what to do. Help please. I can get it back into recovery mode. Tried doing the wipe data/factory reset. That did help either. Help please. I really want to try serendipity. Thanks again in advanced.

Did you run a restore using TiBu at all? Or was it just a straight flash from stock to Serendipity?
Plus, were you running a phone that came with 2.2 out of the box? Or did you upgrade to stock Froyo yourself?

m3thods said:
Did you run a restore using TiBu at all? Or was it just a straight flash from stock to Serendipity?
Plus, were you running a phone that came with 2.2 out of the box? Or did you upgrade to stock Froyo yourself?
Click to expand...
Click to collapse
I did run TB and I had originally flashed up to froyo (took me all night one night) and then went through the process I explained and hit the dead end. I finally was able to get odin to read the phone and flash back to stock. It was a learning process. I realized that I needed not only the Serendipity_6.3.zip file but ALSO the kitchen file to included with it. That wasn't in the directions I don't think. Finally got it all on there. I love it now. I appreciate everyone's help. Any word on a how-to for Bluedipity?

First time, Still trying to figure it all out.

So this is my first time at this, and could use a little guidance. I really dont want to Brick my phone. I don't have the money right now to get a new one. lol
Well I have done some research, but there is so much information out there that it is hard to figure it all out. I own an HTC Hero CDMA through Alltel, and I plan on installing CyanogenMod 7.2.
Right now I am looking at rooting with Z4Root, then using Rom Manager to install CM 7.2
I cant find a link to the Google apps I need, so if anyone has a link on hand that would be awesome.
Does anyone have some suggestions before I start?

gapps are usually posted in the op with the rom.

Here is the link to Google Apps.
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps
Notice there is only one Google Apps file for all devices running CM7 so you don't have to worry about downloading the wrong one
Your plan sounds fine. Personally I would rather use this as a chance to get more acquainted with ClockworkMod recovery than Rom Manager, as it is usually the tool that will save you if your phone goes wonky (you can use recovery to save you from any messed up ROM, but you can only use ROM Manager when your ROM is working in the first place). This is what I would do.
1) Z4 Root.
2) Install ROM Manager
3) Flash ClockworkMod Recovery
4) Download CM 7.0.2, place anywhere on SD card
5) Turn off phone, then hold Home + power to boot into ClockworkMod Recovery
OR in Rom Manager, click on Reboot to recovery
7) In ClockworkMod Recovery, go to Backups and restore > create nandroid backup
8) wipe factory settings from the main menu
9) Install zip from sdcard > flash CM 7.0.2 + Google apps
10) reboot
Done!
By the way, there are only two ways to brick the phone, AFAIK: flashing a wrong radio/bad radio flash or bad flash of an SPL. Installing a ROM (at least on the Hero) does neither of these, so you don't have to worry.

Thx for the guide, but I am having a problem when trying to Z4Root, it just stops at the ...Rebooting screen and never rebots. Also when I try to go into recover it comes up witha phone and a ! with a red triangle around it. Any advice?

I was stuck with Z4Root at the ...rebooting screen also. I just pressed Home or back to get out of it. Then I looked in my app drawer and saw Superuser was there. After that, I went to the Market and downloaded ROM Manager and flashed ClockworkMod recovery.

Z4 root hung up for me too. I ended up having to do it twice before it took. Imediately after you have superuser in your app drawer install Rom Manager....
That's where you get your custom recovery. If you don't have Rom Manager yet, you won't have custom recovery. Also, as tedius as some of these forums are, they are the best way to learn. Since rooting my hero, I have also rooted two Nook Colors and an LG Optimus, and become pretty familiar with using ADB......waiting to get my paws on my wife's Evo now.
****EDIT**** FYI Z4 Root took almost 15 minutes to run its course on my phone....Make sure you have a good battery.

[Q] CWM Error - Status 7

Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.

adobih said:
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
Click to expand...
Click to collapse
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)

Samtan4326 said:
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Click to expand...
Click to collapse
First off all thanks for helping.
I tried this one:
CF-ROOT-4.4-I9000BGJW5-1187857
CF-Root-4.4-I9000BOJW6-CL1177078
CF-Root-JP6-v1.2-Busybox-1.17.1 (this one didn't want to start recovery at all)
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
all I got from all of them is this
imageshack.us/f/805/08032008449.jpg (copy link to address bar )
Member Chainfire said "THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device"
I don't know really what that means. Probably that I have to install something else too, but what ?
Please can you tell me ?
And which of these CF-Roots is the right one, or the newest one, or how do recognize that ?
Thanks everyone who helps me.

eba
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After it's done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.

adobih said:
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After is done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
Click to expand...
Click to collapse
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz

beckzz said:
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
Click to expand...
Click to collapse
Well, I help you as much as I can and know, just write me where you stuck. And if you have some difficulties explaining it in English, dann kannst du mir auch auf deutsch schreiben, das verstehe ich auch

I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & -->release buttons the moment u see bootanimation<--) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough). If not getting into recovery with waiting the first time just try to keep getting in recovery with 3 button combo & wait a couple of minutes. Eventually it does. I had the same thing 2 months ago coming from jb-->ics-->cm10, thats how I remembered.
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen. Didnt wipe nothing in between the flashing
Then flashed gapps & voila

Donovan662 said:
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & release buttons the moment u see bootanimation) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough)
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen
Then flashed gapps & voila
Click to expand...
Click to collapse
I tried like hundred times or more, but every time with the same result and I also tried with different kernels without success. Maybe some other error caused your status 7 error than mine. But anyway, it's always good to try all possibilities to resolve the problem.

Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture

Donovan662 said:
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Click to expand...
Click to collapse
Unfortunately I wasn't that lucky, but I tell you something else. Now I know that no matter what I do and how badly i brick my phone I can always use that method to bring it to life back. So it's kind of final help that works if nothing else works

by the way did you apply sdcard:update zip? Or choose zip from sd card?

Donovan662 said:
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Click to expand...
Click to collapse
I choose zip from sd card because I forgot to rename the file before copying to sd card, and when I lost my bricked my phone it was already to late to rename it. But i don't think that that was the problem, I mean it's just a name string that has no meaning after all.

hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz

beckzz said:
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
Click to expand...
Click to collapse
More or less I think we both had the same problem, because I also used this link wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide and heimdall 1.3.2 for flashing my phone. Just it always finished successfully so I didn't realize it was the root of all problems. I used also then Odin from the youtube video that I posted in a few posts earlier, installed Android 2.3.6 and then installed ROM Manager from Google play, and used the app to flash to ClockworkMod Recovery. After that I installed directly CM10 stable with success, and without CM9 detour.