Trying to install the Cynogen ICS ROM, and when installing the .zip, it loads the Samsung flash screen with Cynogen, then get the green guy and loads of text for about half a second, then it just reboots. Over and over for about 10 mins. WHat went wrong? What should I do?
It happend the same to me.
I just removed the battery and put it back, entered in CWM and reinstalled the ROM.
Good luck!
I somehow got into a recovery mode, but with the assumption it would all go wrong again, tried to install the .zip Darky rom instead, went through the process and said it worked but then it just went back to the Cynogen loop problem!? I just tried a Restore instead, but I haven't rebooted yet, should I wipe everything again, and try the ICM .zip again?
Yep, just go with the whipe. I hope you did a backup.
OK turns out the Restore failed, so now trying to reinstall ICS .zip again. fingers crossed!
yep backed it up, not that its seems to have helped.
Well now it's stuck in the Galaxy S bootscreen...
that really sucks....did you deactivated the lagfix before running the rom?
If the problem persists you have to run a basic ROM using ODIN.
Yes deactivated the lagfixI can't get into recovery or anything now, except download mode.
Download mode is all you need to run a ROM with Odin.
I recommend Amestris, it is a good ROM, good battery life but the thread in not complete, there are some files missing...for now.
I've put some older ROM on I had, then tried to install ICS again but now when I use Clockwork, and select the file it goes to recovery but I can't select any zip files, just reboot back to this awful old ROM!
I had same issue when I installed ics, what I did that worked was pull battery and go back into cwm, reflashed ics zip and it fully installed that time. Had same experience when flashing cm7 before.
Not getting anywhere with this. I get an option to install zip from sdcard which is where the update is (an where the darky update also is which worked), but there is an option to update from internal SD, which is not where the file is. Is it in the wrong place?
I think you would be best to use Odin 1.3 to flash DarkyROM Ficeto JVT base rom.
are you sure those files are still on your sd card?
The reason you need to pull the battery and reflash the ICS rom a few times is because Samsung ROM (most) have a different partition layout to CM7 based roms (which the ICS port is one).
GL.
Related
Hi,
I recently flashed a new rom (ultimate galaxy s v.7) from xda, and I flashed it via clockwork.
clockwork installed it and I rebooted, and it seemed to hang on the lockscreen for an abnormally long amount of time.
when i take the battery out and try to boot into recovery mode, it flashes to black then shows the galaxy s boot again.
previous to flashing this rom i have cleared the cache and all data on the phone. i have a nandroid backup so if i could get back to clockwork recovery this would be helpful.
also previous to flashing this rom i had a 3 UK rom which i installed by accident via kies, running 2.1...this rom seemed to be quite resistant to installing another rom from kies.
help would be MUCH appreciated...
thanks in advance
so recovery mode isnt an option then ?
What about Download mode ?
Hi,
Download mode worked before.
I have now managed by some miracle to get into recovery mode and now have gained options about a speedmod universal lagfix.
Is this associated with clockwork / ultimate 7.0 rom / a sign that the rom has installed in some form, and should i reboot, or should i now do a nandroid back to the rom i had before?
I believe speedmod uses CWM, so you can just do the rollback to your previous rom
nwsk said:
I believe speedmod uses CWM, so you can just do the rollback to your previous rom
Click to expand...
Click to collapse
however would it be safe to reboot, as i'm currently in recovery mode and considering to do a nandroid OR alternatively reboot and see if the new rom starts up..
well u cant leave it in recovery mode forever lol, reboot it, if it doesnt come on, try recovery mode again or just flash another ROM thru ODIN
ok. how long do you think is a reasonable time to wait before concluding that the rom doesn't work and I should nandroid back to my old rom...?
Half an hour gives plenty of time .
jje
what would be the reason that it hangs on the galaxy s bootscreen?
could be anything.... installing process not completed properly. best to just re flash .
azzledazzle said:
could be anything.... installing process not completed properly. best to just re flash .
Click to expand...
Click to collapse
do you mean recover via nandroid or reflash the same rom, then leave it?
choice is yours, ive never restored using nandroid so dunno what its like. but try it first, if no success re flash using odin. u will lose all your data
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
+1 get clockwork recovery...you need to make sure the rom you are flashing is compatible with the version of CWR you are using.
For example a rom that needs to be installed with CWR3 you will need to install the zip presumably from CWR2. Pull the battery and reboot back to recovery - you should now be in the updated version of CWR. Then for safety sake - re install your zip.
Reboot and you should be all set.
I had lots of trouble going from 2.2 to 2.3. Flashing between 2.3 roms is very easy comparatively
milkytron said:
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
pwnerman said:
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
Click to expand...
Click to collapse
I did have the bootloaders, I went back to stock before I did anything just to be safe. I'm gonna try what the other guys said though right now, wish me luck haha
jmtheiss said:
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
Click to expand...
Click to collapse
Alright so I have Andromeda 2.1 which is a froyo rom. Which method should I use to get to stock GB?
use Odin to flash gingerbread bootloaders then flash gingerbread roms
howtomen said:
use Odin to flash gingerbread bootloaders then flash gingerbread roms
Click to expand...
Click to collapse
I flashed the gingerbread stock rom and have it rooted with xcal's kernel, but when i flashed mosaic IV it got stuck at formatting partitions and i pulled the battery after about 15 minutes and then restarted my phone to find it stuck in a bootloop. So i had to start from stock again and now im back to gingerbread stock with root. I'm kinda scared to try again because it takes me like 30 minutes to get back to gingerbread stock with root. I think ill just stick with stock for a little bit
So today my phone was on and everything was fine, then while I was charging it, went away from it a few minutes then came back it was on the boot menu. It now can not get past the boot menu ever.
I have ClockWork Mod recovery installed, and CM7.1 stable.
I did a "backup" via the ClockWork Mod Recovery of the system.
I am also quite tempted to get the CM9 RC2 installed. But screw it if it any kind of unstable. CM7.1 stable is unstable enough.
What should I do? I would prefer it if I did not lose all my stuff (like app notes etc).
Can I like just put my phone into Download Mode, place the CM9 RC2 on the root folder, then do the good old
cyanogenmodWiki Full Update Guide method via recovery
without losing anything?
tottycs said:
So today my phone was on and everything was fine, then while I was charging it, went away from it a few minutes then came back it was on the boot menu. It now can not get past the boot menu ever.
I have ClockWork Mod recovery installed, and CM7.1 stable.
I did a "backup" via the ClockWork Mod Recovery of the system.
I am also quite tempted to get the CM9 RC2 installed. But screw it if it any kind of unstable. CM7.1 stable is unstable enough.
What should I do? I would prefer it if I did not lose all my stuff (like app notes etc).
Can I like just put my phone into Download Mode, place the CM9 RC2 on the root folder, then do the good old
cyanogenmodWiki Full Update Guide method via recovery
without losing anything?
Click to expand...
Click to collapse
If you have done a "backup" from CWM before the failure just restore that.
From CWM menu try to do a dalvic and cache clean up. also clear init.d and nstool settings and try to reboot
If you want to be more adventurus and loose your contacts, sms, settings...and other stuff from CWM do full wipe and cache and dalvic and then install your favorite rom.
I tried to installthe Gnexus port rom jr03l 4.1.1 rc 10. I was on TAJB'S Jellybean rom with devil kernel. I tried to install the rom as per the instructions given. I did a nandroid backup of the current rom before attempting to do so. The flash failed as the phone rebooted into recovery after a few minutes. I tried to restore from my nandroid backup. That failed too and it came up with a message of "no free space". I rebooted the phone and the phone automatically tried to flash the gnexus port rom again. It failed rebooted and got stuck on the devil kernel screen.
After about 20 mins, i took the battery out and rebooted into recovery. I really dont know where to go from here. I need to backup my efs folder too somehow.
I have a flash zip of the gnexus port rom, the tajb rom and a cm9 nightly in my internal sd card. I also have a nandroid backup of my cm9 rom.
Any help will be greatlyy appreciated!!!
Please help me.
Hey
Just flash any firmware (Official is preferred)..root it and do a restore of the backup u have..
Done
Hey do a factory reset then try to restore your backup
Sent from my Awesome I9000 using Slim Bean
Hi,
I flashed my GT-i9000 (Firmware was Gingerbread BUJVY) using CF Root (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar) through ODIN.
All worked fine and I was able to boot into Recovery using the regular Volume Up+Home+Power.
I then proceeded to flash CM10 nightly (23/9/12) (from my external Micro SD card) by wiping data, wiping cache and wiping Dalvik Cache.
I then navigated to the zip file for CM10 and run it. It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4).
From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
I'm hoping someone may be able to help, I would really appreciate it!
TIA!
zim_zimmer said:
It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4). From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
Click to expand...
Click to collapse
Do you know what version is your Firmware? is it 2.3.3 or 2.3.6?, IF its 2.3.3 your boot loader needs to be updated to 2.3.6 for you use , If its already 2.3.6, than you should be able to use CWM recovery to reinstall the CM 10 from your SD card. (But by doing this you may lose your IMEI as you should do a progressive upgrade , like from GB 2.3.6>ICS CM9>JB) or flash a semaphore JB kernel
Easiest way out would be for you to use a JVU ROM to recover, safe your EFS, than proceed to CM 9 and than to CM 10...
you can get a rescue kit or JVU+CFRoot from My Android Collections and or a solution from My Android Solutions
Hi there,
I was on Gingerbread 2.3.6 before I ran the above.
I have gotten a bit further than the above. I managed to mount the phone as a USB whilst in CWM and put the CM10 zip file on the actual phone memory. I then wiped data/cache/dalvik and rerun the install. It installed but didn’t reboot itself, so I rebooted manually and then the Cyanogenmod logo started up and it booted into CM10. Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Rooting this phone and flashing ROMS is more difficult than my Galaxy S3!!
Cheers
zim_zimmer said:
Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Click to expand...
Click to collapse
Since you are already on CM 10, you need to solve your home button problem, try doing a wipe in recovery, if fails, flash again the CM 10
Hmmm, it didn’t work.
What I’ve done since though is try to flash another ROM.
I’ve flashed the ‘xBean’ ROM with success, however, I did encounter the exact same problem when flashing the ROM as mentioned above
I wiped data/cache/dalvik and run the install for xBean. It stopped after the first install attempt and rebooted itself, however it just brought me back to the CWM screen (although this time different from the CM CWM).
So I wiped data/cache/dalvik, then run the install again. This time it went through the full install but again (like with CM) it didn’t rebooted automatically. I manually rebooted and then the xBean logo came up and booted in.
This time the home button is working, and pretty much everything else is too by the looks of it. So far so good!
I guess my question would be, why does the ‘ghost installs’ keep happening???
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.