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???
Just got my Galaxy S back from my Mum today (After I bricked it and sent for repair) she got a note2 omg... Decided to flash a custom rom..
Here goes..
First I followed this guide completelyhttp://http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. After I flash the CM 10, my recovery was upgraded to v6.0.1.5 after reboot. But I cannot get pass the recovery. I will have the cm boot animation, then back to recovery again. Tried reflashing the rom, doesnt say any errors but still gets stuck at recovery.
Then I went thru the method at the wiki.cyanogenmod again and successfully flashed cwm recovery 2.5 again. Tried flashing the CM10 rom again but this time round, It shows a long error message ending with "status 7"
I am still able to go into download mode.
Was on stock unrooted 2.3.3 DXJV9.
I made the super no.1 noob mistake of not making a backup........... But, why is rooting and flashing of this phone so hard.....
Pls, any help is greatly appreciated.
Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.
It will work
scpion said:
Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.
Click to expand...
Click to collapse
When u see red error message in stock recovery........u just wipe cache and reboot.......it will work.....
i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.
try this
scpion said:
i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.
Click to expand...
Click to collapse
U just use GB jw4(your region) ROM (don't use single file like PDA).........you use files separately like this [PDA,phone,CSC,pit(512 or 513)]...............use Odin 1.85 for flashing files......,when u complete the flashing it automatically reboot to fulfill the flashing...........then also it gives red error means........ clear only wipe cache and don't clear wipe all data...........reboot your system..... I think this will work for u...........:fingers-crossed:
Thanks. Have it solved. Flashed with another rom with seperate files. I was using the the all in one previously. Got it to run CM10 nightly though till now still not too sure how... But, I m real happy now. It works great so far and I couldnt understand why Sammy refuse to roll out official ones even for 4.0..
Still trying to figure out how to root, flash SGS though.. I have done so for many other device but by far,... this phone is the most complicating....
Aj rocker root
By processor only we not getting stock ICS rom but we getting custom ROM by hacking processor.............
For rooting the ROM u want to be in stock GB ROM like 2.3.5 or 2.3.6 and then u want to download this file(http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip)............. after download u want to open Odin 1.85 and select PDA then choose the downloaded file...........select start to flash the file.........reboot and enjoy the root bosssss......if u like this press thanks:fingers-crossed:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Try to see if you can flash another custom Rom, if that works then it could be that your files are corrupted..
Have you stated your problem over at CM forums..
# Sent from my blazing slimbean SGS i9000 using Tapatalk 2 #
scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:
scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:
Most times from GB to JB u have 2 flash custom 2, 3 times. So its normal when flashing custom the first time it takes u to bootanimation and hangs (take out battery and go to recovery with 3 button combo and flash again till it says install is completed) or directly into recovery.
If u wanna flash other jb rom just full wipe and flash new custom. Make sure u make a nandroid backup so u can go back easily
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.
Hi all, my name is Daniel.
I am using a motorola Milestone A853 for the past one year and never faced any issue while rooting or installing custom roms right upto cm10.
from last two months the milestone has not been working properly. It so happened i had installed CM 9.0.1d and everything worked fine. but once the battery died the phone did not boot up and was stuck on moto boot logo and kept restarting from there. I tried to go into open recovery (fufu minimod) using the X+power key and it goes into recovery but after loading recovery it did not display any options and the other text was red in color and it showed the error failed to load menu.init. I replaced the update.zip file along with the open recovery folder, but still nothing worked. I then tried another open recovery but still open recovery never loaded. Then i SBF'ed the device and went back to stock and was able to use my phone again. But then when i try to root the device again i am not able to root using vulnerable SBF as it does not install though RSDLite shows pass. Then i used superoneclick to root and that did the trick. But still open recovery never installed or load. Luckily androidiani recovery which displayed an error cannot mount but still created the menu and i was able to install custom OS but only cm 7.2.4e and not cm9 nor cm10. I cannot reboot the phone as the phone never starts up. only after clearing dalvik and wiping cache phone boots up. After a certain time now i still cannot install cm7.2.4e as it does not load and gets stuck on custom bootscreen, so i installed MIUI rom which works and starts up but i still can never reboot my phone.
Errors Seen E: cant mount /cache/recovery/command
Kindly help as the phone is just barely working.
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Tried Everything
Erovia said:
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Click to expand...
Click to collapse
Thank you for your reply. I have tried flashing stock 2.2 and still I cannot reboot the phone without wiping cache and using the reset factory option in stock recovery. Using superoneclick I can root it and install androidiani recovery but I cannot use cm10 or cm 9. after installing cm9 the phone just restarts after cm9 boot screen and after installing cm10 the phone shows the stock android boot screen. cm 7.2.4e installs as well as miui but if battery dies or if I have to restart the phone if it gets sluggish and slow then I cannot...everytime for the phone to boot I have to wipe dalvik and cache for custom roms and for stock roms I have to wipe cache and factory reset.
SO basically I am stuck...have tried changing the sd card, repartitioning the sd card, but nothing worked
Open recovery cannot be used only andoidiani works after popping up some errors.
Kindly help.
I really was checking the whole internet to find the solution for this but I couldn't find it (I'm a begginer so that might be the problem).
Problem is this.
I have a Samsung I9000 with rooted Gingerbread (BOJV9). I have rooted it with the CF-Root-XX_OXA_JVZ-v4.3 KERNEL.
So now my phone has a Kernel version: 2.6.35.7-I9000XWJVZ-CL762604 [email protected] #2.
And the next thing that I wanted was to install the Slim Bean 4.2.2. So I went to the CWM recovery and I have done the wipe of cache, dalvik cache and data/factory reset. everything went ok and fast. then I went to install the Slim Bean and started the install but just when it started, showed on the screen that it is instaling updates, phone just reseted, and Semaphore logo showed up, and was standing there for 10minutes. So I googled and saw that that was some kind of error. So I went CWM recovey and it had a new look because the version changed (from v3 to v6 I think) but I couldnt find data on my external SD card, as if it was deleted, but it was not, the data was there. Then I found this page http://forum.xda-developers.com/showthread.php?t=1494493 and was able to start the phone by flashing it with the original I9000 rom, and then installed the CWM again and then i returned my backup that I made of my phone. Then I started again to install Slim Bean again but this time I got an error at the wipe dalvik cache saying E:unknown volume for path. Now I dont know what could be the problem but please can you help me. Should I first install some other custom rom or should I put the rom files on to the I9000 memory or what. I am really confused
Also the same thing happend when I tried to install CM10. it starts the installation but it restarts after few seconds.
Files that I have used
Slim-I9000-4.2.2.build.3-OFFICIAL.rar
cm-10.0.0-galaxysmtd
Anyone? Help?
Do what you did again till the recovery changes to v6 as you said & then flash the slim bean or any other rom again... it will work.
Good luck
yatharthsims said:
Do what you did again till the recovery changes to v6 as you said & then flash the slim bean or any other rom again... it will work.
Good luck
Click to expand...
Click to collapse
Thank you sir. This helped me. God bless you