I installed CM 10 stable and Semaphore Kernel. Worked great. Then went to install gapps and got lots of FC's so I went on to clean cache, dalvik and to do a factory reset and suddenly I got stuck at semaphore/boot logo and couldn't go into recovery. Got the recovery fix and installed it via Odin, and it works. But, it doesn't allow me to install anything from external SD card, only internal. Of course, I don't have anything there.
What should I do? Any links for tar versions of CWM and CM 10 for i9000?
Hmmm, is it safe to assume everything will be OK if I just flash any stock firmware from sammobile?
Yup, that combined with this did the trick.
Related
I have CWM 4.00.15 installed and I tried to install Ryyu's Rom (Wipe) by putting it on the SD card and rebooting into recovery, then selecting the zip file and hitting apply. When the installation tried to update my kernel, it just froze and rebooted. I was then stuck on a boot loop between the Galaxy S screen and the CyanogenMod boot screen. I know that Ryyu's did not install correctly because the CyanogenMod boot screen was still there. I had to use 3 button recovery and erase cache, davlik cache and user data before trying to install AOSP Essence, but same problem happened. Installation dies and phone keeps rebooting in loops. Finally, gave up and went back to CyanogenMod Nightly and it worked.
Why can't I seem to install any other ROMs besides Cyanogen? I know I am doing something wrong, but not sure what. Any advice/help appreciated. Thanks.
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Br1g0 said:
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Click to expand...
Click to collapse
Hi,
this is what I initially did to get Cyanogen on:
1. Used Superoneclick root to root phone
2. Check that 3 button recovery and download mode works. Recovery version was 3e, so installed superlagfix from android market. This automatically installed ClockworkMod Recovery as well.
3. Use CWM and flashed recovery for Samsung Galaxy S i9000
4. Reboot into recovery and select the CyanogenMod zip file and click apply to install.
To install subsequent ROMs, I just put the zip file on my SD card, reboot into recovery and repeat step 4 above, after clearing cache and user data. It is after that I get stuck on boot loops.
I did do a Nandroid backup before my initial Cyanogen install so I can go back and restore it, but it would be Froyo.
when coming from CM / MIUI - Samsung based ROM
you MUST flash a 3 file firmware with pit and re-partition.
Cyanogen and MIUI use different partitions than samsung ROMs so this is why you are having issues.
Ok, just managed to flash Darky's EE 10.2 using Odin. Not sure if Odin is the ideal way, but it worked. Really enjoying Darky's. Thanks folks!
Hi,
I have many times tried to flash CM7, but always happens weird thing.
I have stock 2.3.5 XXJVS with Semaphore 2.5.0 kernel
1.I boot into CWM
2.I wipe cache then wipe data/factory reset then i go advanced and choose wipe Dalvik cache
3.Choose .zip from sd card
4.I choose update-cm7.1.0-GalaxyS-signed.zip
5.My phone flashes it
6.It reboots
7.Normal Galaxy S GT-i9000 then Galaxy S
Cyanogen Mod
8.It goes to recovery and posts text very fast then reboots again
9.It repeats everything what it does from section 7.
Im very confused so please help!
Have you tried flashing it again?
redo step 3 and onwards,
sometimes you just need to flash twice.
It seems like a corrupted download... Are you flashing from internal or external? Have you mounted before?
i tried to flash from internal
What version of CWM recovery do you have? Maybe flash a different ROM just to update CWM, and then flash the rom you want?
I had the same, or atleast a similar problem whilst trying to flash CM9. I fixed it by flashing the rom again.
You also might want to redownload the file incase it's corrupt.
i have CWM 5.0.2.7 and i downloaded the CyanogenMod file again so i try to flash it again
Any luck with your efforts this far?
yes, i succesfully installed CM9 about 3 months ago.
I'm not sure which build it was but it was the newest build
Update: Solved
Thank you for everyone's reply and help.
What worked for me:
Downloaded Mobile ODIN v3.10
Downloaded Goku v1.5-10 TAR (Kernel-Goku-V1.5-10.tar)
Flashed firmware with Mobile Odin with MD5 signature check
Can now boot into recovery
Currently on:
CM9 Version 9-20120515-Nightly-n7000
Build date Tue May 15 23:06:26
Kernel version 3.0.30-CM-q6804ca8
I cant seem to get into recovery while using any of the ICS roms. I've tried several CM9 bulds, Kindgroid, Stunner and a few others. I doesn't matter if i try to access it through the hardware keys (press and hold the Volume UP+Home+Power) or through one of the software options (reboot into recovery). After the samsung logo apears the screen will turn black. I'll have to restart the phone with the power key.
Everything else seems to be fine. I can get into download mode just fine. I have no problems downgrading to a gingerbread rom from pc odin or mobile odin. Also theirs no problem for me getting into recovery from any of the gingerbread roms I've tried.
I first noticed this while I was on ICS stunner. It was the build with the affected kernel. Everything was running smooth for me. Recovery and everything else seemed to be working fine but when i started reading posts about the brick scare i became afraid of doing anything else on that kernel.
I followed Entropy512's advise:
If you are running an affected kernel:
STOP USING IT IMMEDIATELY. FLASH A SAFE KERNEL USING ODIN/HEIMDALL.
DO NOT wipe in recovery
DO NOT flash anything else in recovery
In general, DO NOT use recovery at all
I flashed his DAFUQ releas using mobile odin while still on stunner. Everything seemed to go smooth. After flashing I checked under setting -> about phone -> kernal version and his kernel was properly displayed. I tried going into recovery but the screen would turn black after the samsung logo.
I've must of done something wrong while flashing Entropy512's kernel because ever since I flashed his kernel I havent been able to get into recovery while running an ICS rom.
TL;DR
Cant access recovery from ICS roms but recovery works fine while on gingerbread roms
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
jonpaslim said:
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
Click to expand...
Click to collapse
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
runnin4mayor said:
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
Click to expand...
Click to collapse
How about 4 wipes including format/system and also use jbroid even though your not installing a kernel but rom still use it.
Flash stock GB rom. Reroot it and then check everything is working fine? If yes then flash ICS rom.
Sent from my GT-N7000 using XDA Premium App
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
jonpaslim said:
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
Click to expand...
Click to collapse
Yes.. I've tried that before installing my current ICS rom. Actually I formatted both the internal and external SD while still on GB. I'm still wondering if the recovery stored in the same partition space in both GB and ICS. I can't understand why I can access CWM recovery on GB but not while I'm on ICS.
i too have the same problem even though i can access cwm manually cant install any zip file but if i use abyssnote kernell everything works fine the problem started when switched over to ics from gb
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
Wiping more than once is pointless... I don't know where people get silly ideas like "wipe 3 times".
When you switched to something else, did you flash it using CWM or Odin?
Try flashing a different kernel using Odin. I have seen that in rare cases on some devices, doing something like the following:
Flash one kernel from a recovery
Reboot directly to recovery using CWM's Advanced menu
At this point, the device will be stuck either always booting to recovery or never booting to recovery
Flashing a kernel with Odin/Heimdall - NOT "Mobile Odin" (I hate that name because it's completely different from Odin) or CWM often breaks these loops.
problem accessing recovery
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Thank you sir for your swift action.
deepalakshmidas said:
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Click to expand...
Click to collapse
How did you flash abyssnote kernel without being able to enter recovery?
Edit: Solved my problem. Updated 1st post
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???
I tried to flash CWM10 into my Samsung Galaxy I9000 Device And here's what happened:
I got into the CWM Recovery screen and chose install from sdcard (after a wipe data + wipe cache factory ofcourse).
Everything seem to go OK, no errors or special things, but when I restarted the device to boot into Android OS, it just came back to the CWM Recovery screen.
Since then, I have tried to install many other ROMS and the phone simply won't boot to android OS.
I have also noticed that usually after a successful ROM flash, folders are created in the internal SD card a thing which DID NOT happen this time.
The only difference that the new ROMS installation does is change the CWM Recovery version/Mod.
So basically, I am stuck at CWM Recovery Screen.
I am clueless and I will really appreciate any thing you can.
Any thoughts?
MPolo1989 said:
I tried to flash CWM10 into my Samsung Galaxy I9000 Device And here's what happened:
I got into the CWM Recovery screen and chose install from sdcard (after a wipe data + wipe cache factory ofcourse).
Everything seem to go OK, no errors or special things, but when I restarted the device to boot into Android OS, it just came back to the CWM Recovery screen.
Since then, I have tried to install many other ROMS and the phone simply won't boot to android OS.
I have also noticed that usually after a successful ROM flash, folders are created in the internal SD card a thing which DID NOT happen this time.
The only difference that the new ROMS installation does is change the CWM Recovery version/Mod.
So basically, I am stuck at CWM Recovery Screen.
I am clueless and I will really appreciate any thing you can.
Any thoughts?
Click to expand...
Click to collapse
cos of new partitions u have to install 1 ROM 2x. sometimes 3x. thats all.
so take ur cm10 zip and flash it. after reboot to recovery just flash the same file again.