Database Develop

[Q] First time trying to flash a ROM - Help

Hi!
I have a brand new Galaxy S with Android 2.2 FROYO installed, and I want to install a custom ROM (F1 Galaxy SII V6). Since I´ve never flashed a rom before, I started to read lots of information and I would like for you to confirm if im planning the flashing properly:
Step 1: Root my phone with SuperOneClick.
Step 2: Install Rom Manager from Android
Step 3: Backup the current system from Clockworkmod
Step 4: Download the ROM and put it in SD Card
Step 5: Enter Recovery Mode and Wipe everything
Step 6: Install Zip (ROM) from SDcard
Am I missing something? Do I need to do something more before installing the ROM? Am not sure if I need to this step: http://forum.xda-developers.com/showthread.php?t=1047924
Please give me your advices so I can perform a safe flash
Thanks!

This will help you: http://forum.xda-developers.com/showthread.php?t=1139050.
Before the installation of the rom you MUST have gingerbread bootloaders. And so before doing it you have to flash via odin a gingerbread firmware.
I suggest to use xxjvp firmware because f1 gs2 rom is based on this (you can download it from samfirmware). After you flashed via odin you have to download semaphore or any other kernel (semaphore http://forum.xda-developers.com/attachment.php?attachmentid=703841&d=1314631488) which has cwm. Flash it via odin. Now you have to download f1 gs2 v6 rom (wipe version). Go in recovery and choose install zip from sd card and select the rom( you don't have to unzip anything!). After the installation probably you will hear a strange voice. If it happens the phone is converting the system to ext4. Be careful! If you want to install another rom you have to disable it in recovery in voodoo--disable lagfix and system lagfix/off. Now that you installed the rom you have to install f1 service pack 1 and then root su fix. Now enjoy the rom

If you really want to use a custom ROM my suggestion is go for Darky v10.2RE
http://samsung-sgs.blogspot.com/2011/08/how-to-flash-darkys-rom-v102-re.html

Thanks for your feedback.
Another Question: Since the equipment is brand new and has a 2 years warranty, what do I need to do, if someday the phone has somekind of malfunctioning and needs to go the factory for repairing? Rooting and installing other ROMS voids the warranty, right?

I think so..

You have to flash the firmware that you had when you bought the phone via odin. You can find it on samfirmware

Spezia12 said:
This will help you: http://forum.xda-developers.com/showthread.php?t=1139050.
Before the installation of the rom you MUST have gingerbread bootloaders. And so before doing it you have to flash via odin a gingerbread firmware.
I suggest to use xxjvp firmware because f1 gs2 rom is based on this (you can download it from samfirmware). After you flashed via odin you have to download semaphore or any other kernel (semaphore http://forum.xda-developers.com/attachment.php?attachmentid=703841&d=1314631488) which has cwm. Flash it via odin. Now you have to download f1 gs2 v6 rom (wipe version). Go in recovery and choose install zip from sd card and select the rom( you don't have to unzip anything!). After the installation probably you will hear a strange voice. If it happens the phone is converting the system to ext4. Be careful! If you want to install another rom you have to disable it in recovery in voodoo--disable lagfix and system lagfix/off. Now that you installed the rom you have to install f1 service pack 1 and then root su fix. Now enjoy the rom
Click to expand...
Click to collapse
Thanks for your detailed explanation!
I only didnt understand two things:
1- What is "Voodoo" and what is the "lag fix"?
2- How do i install SP1? In recovery mode trough the zip file?
Thanks!

Lagfix: the filesystem of the galaxy s is in rfs. When you apply the lagfix it is converted to ext4. This makes your phone faster when you launch an app. Voodoo is a "type" of lagfix developed by supercurio. You have to install f1 service pack 1 and root su fix via cwm trough install zip from sd card.

Spezia12 said:
Lagfix: the filesystem of the galaxy s is in rfs. When you apply the lagfix it is converted to ext4. This makes your phone faster when you launch an app. Voodoo is a "type" of lagfix developed by supercurio. You have to install f1 service pack 1 and root su fix via cwm trough install zip from sd card.
Click to expand...
Click to collapse
Thanks again! Today I will try to flash the F1 ROM. Hope I dont brick my SGS!

By the way, after installing the ROM I can install another Kernel, right? Do you recomend the Galaxyan Kernel, or should I stick to Darkys?
Tks once again

Yes you can. I suggest to try this kernel developed by simone 201. Normal version has got 340 mb and bigmem version 353 but this hasn't got 720p video recording http://forum.xda-developers.com/showthread.php?t=1233215. Be careful! Disable lagfix before installing the kernel.

Spezia12 said:
Yes you can. I suggest to try this kernel developed by simone 201. Normal version has got 340 mb and bigmem version 353 but this hasn't got 720p video recording http://forum.xda-developers.com/showthread.php?t=1233215. Be careful! Disable lagfix before installing the kernel.
Click to expand...
Click to collapse
Nice! Do yuo recomend using SGS kernel flasher to install kernels?
Tks!

I reminded of something...Do I need to disable lagfix to install F1 SP1 a and root SU Fix??

It would be better if you install it from cwm. You don't have to disable lagfix before installing root su fix and f1 service pack 1. (Faryaab is going to release a new version of his rom in few days)

I´ve sucessfully installed the F1 Galaxy S2 V6 ROM, and everything is working great! The only problem im noticing is the fact that the phone hangs and then restart by itself in games...any solution for this?
Thanks

Hi again! Currently im using Darcore Kernel and I want to try the Galaxian Kernel. In order to install it properly, do I need to disable the lagfix?
Tks!

By the way, im only scoring 1900 in quadrant...is it normal? I installed setcpu but the max frequencie is only 1000mhz. How can i set the cpu to 1200mhz??
Thanks!
Sent from my GT-I9000 using Tapatalk

[GTP6800][ZSKL2] [3g] EzyKernel OC/UV + Deodex + PowerMenuMod

EzyKernel v1 - 23/02/2012
This Kernel is more geared towards functionality & real life user experience as opposed to benchmarks etc.
(Need to be running a ZSKL2 firmware - see installation instructions)
Update 23/02/2012 - Kernel Bluetooth fix.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Features:
1) Overclocking & Undervolting support
Added overclocking up to 1600 / 1800 mhz
Added sysfs uv interface for setcpu support.
Undervolts quite well
Set default max overclock to 1600 mhz.
1800 mhz is not stable for me causes freezes/lockups for me. I dont tend to use voltages higher than 1350mv but the option is there for anyone who feel the burning itch
(1.8 is not recommended - untill further tests)
2) init.d support for boot up scripts - place start up scripts in /etc/init.d/
3) support for boot animations - place bootanimations.zip in /system/media/
4) I have built in cifs / nls_utf8 support into kernel so no need for seperate modules
Tested ok. Not sure what nls_utf8 does but seems to be requested quite a bit. If problems of unmounting shares, try umount -l /path/to/mount normally does the trick.
5) Added ntfs read/write support for kernel - Not tested myself
6) Added udf / iso support to kernel -Tested ok - can mount bluray iso's etc.
7) Added support for Interactive governor
Tested seems bit of a cpu hog / not properly optimised enough so would not recommend using it.
Ondemand seems to work the best. May look into porting other governors but not anytime soon
8) Slightly modified touchscreen driver
decreased the tsp_threshold level for 50 to 20.
You can set this value manually by
echo "X amount" > /sys/class/sc/sec_touchscreen/tsp_threshold/
However the problem is that the value gets reset to 50 every time the screens switches off. Hardcoded 20 as the default value it changes to after screen turns off.
Also changed the default ontouch frequency from 500mhz to 800mhz. The voltages for each are roughly the same so should be a wee bit more responsive without impacting battery life. Can set higher if anyone wants this.
Other general stuff - removed some debug info from kernel.
----------------------------------------------------------------------------------------------------------------------------------------------------------
EzyKernel Download link
p6800_EzyKernel.zip
http://www.mediafire.com/download.php?5xkglbje6ndo2ge
----------------------------------------------------------------------------------------------------------------------------------------------------------
Additional Mods:
Kernel works fine with deodexed /odexed system. Theoretically odexed is faster but I cant notice much difference between the two.
1) Deodexed & Zip-aligned Stock System / App folders from the ZSKL2 firmware
Download Links:
(Use Hjsplit or another tool to combine the following into one
GTP6800DOX.zip.001
GTP6800DOX.zip.002
http://www.mediafire.com/download.php?2pqwdbcox5o7pdv
http://www.mediafire.com/download.php?6ykpook81both85
GTP6800DOX.zip.001 : D844D0F20CA5C5CA4EDDC2F4BE993FE3
GTP6800DOX.zip.002 : D0AF7C4B7C43D2F0974DA2E9C42EF5AC
2) Custom boot animation modified from
http://forum.xda-developers.com/showthread.php?t=985251(thanks to aph)
Download link:
bootanimation.zip
http://www.mediafire.com/download.php?yvpv0y1bgp5bcne
3) Custom init.d scripts for slighty better wifi /ram management.
There seems to quite a few of these ram/performance scripts flying about. Not tested myself properly as these are os level tweaks so needs some time to adjust for best values i presume.
literally cut&paste jobbie thanks to juwe for his ram tweaks.
slightly modified: thanks to joker.20 for his general / wifi tweaks http://www.android-hilfe.de/root-ha...imus-3d/145592-tweaks-scripts-collection.html
Download link:
S97Ramscript
http://www.mediafire.com/?k45pjvf083d8rp4
Mods for Deodexed system only:
1) Modified Black status bar & Power menu - added reboot / reboot recovery options.
The framework-res.apk contains my grey battery icons mod. You can easily change to blue stock by just copying over the grey icons with the blue ones using winrar for example. (all icons are ok now )
Download link:
http://www.mediafire.com/download.php?zmnbun90z9w0az9
If you found this useful for you please try using one of my apps such as EzyMount which is on the google market:
https://play.google.com/store/apps/d...zymountcontrol
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INSTALLATION:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit - it seems there maybe a problem flashing kernel through cwm recovery. Samsung are playing games again!! Flashing kernel through stock recovery works. Confirmed working by kazuni & does not increase binary counter You still may want to flash kernel via cwm first if you are already using it, then try stock recovery if it does not work for you.
Modified install steps below.
1) Need to be running ZSKL2 based firmware -if yes then just flash kernel in stock recovery
Otherwise follow the steps below
Download firmware from here:
http://www.filefactory.com/file/c2c681d/n/P6800ZSKL2_CSC_TGY.exe
Flash in odin
Thanks to xenix96 for this & see his thread for flashing instruction & other useful info
Fortunately, ZSKL2 firmware is not a full wipe firmware. It keeps you apps,settings. I was using ZSLA2 firmware and even after flashing the ZSKL2 firmware, i still had my settings, user data etc.
Once you change the default language to English you are good to go.
Off course in any event backup your sdcard contents to an external drive.
Make a full cwm recovery backup so you can always revert.
2) Root
(see respective threads on how to do so)
root - http://forum.xda-developers.com/showthread.php?t=1454112
3) Flash the kernel in stock recovery
Reboot- Finger Crossed everything should run ok
4) Flash cwm recovery
cwm - http://forum.xda-developers.com/showthread.php?t=1470896
Should be good to go !!
Install of ExtraMods:
1) System DEODEX - just flash deodex zip in cwm recovery
2) Modified Power menu - flash in cwm recovery
3) Boot animation - manually copy bootanimation.zip over to /system/media/
4) Tweaks script - manually copy over to /etc/init.d/. You may need to mkdir init.d if it does not exist. Set proper permissions (chown root.shell yourscript && chmod +x yourscript - google it!) for any script you place there.
Possible Issues:
(not issues for me - i should add)
1) Kies updates might be broken. If this is a problem for you dont flash.
Personally, until we get an ICS update, i am not bothered with kies or android 3.2 incremental updates.
2) CSC is not for my country. If this is a problem dont flash.
I am in the uk and the hongkong csc works fine for my mobile provider.
In any event, csc information is stored in cache.img of stock firmwares. You could possibly manually change csc info and see if stock recovery automatically picks its up after flashing cache.img taken from your stock firmware. Might work
3) Flashing custom kernels can increase binary counter
So far flashing in cwm or binary copying zImage does not / should not increase the flash counter. Flashing kernel in odin / download mode will do this. No guarantees. If this is a problem for you dont flash.
source diffs - available once everything has been tested reliably
Usual disclaimer - these mods are to be used at personal risk only !
cheers ezynow

Reserved for updates, bugs,issues, boootloops etc
1) 23/02/20012 - Kernel Bluetooth fix.
Main kernel downlink link update. Should be fine to flash in cwm recovery if not you may have to try stock recovery.
Some points:
1) I know browser is not the best. But to enable browser at full speed u need to remove cpu limit. Change settings after entering about:debug in address bar.
2) be very careful with setcpu dont apply settings at boot untill sure of settings. It seems to stick settings after freeze. U may have to manually delete setcpu xml files if it happens

6800 tabs only or will it work on 6810's?

Nice work, my friend. Looking forward to to trying this out...
Sent from my ADR6425LVW using XDA App

got556 said:
6800 tabs only or will it work on 6810's?
Click to expand...
Click to collapse
sk806 said:
Nice work, my friend. Looking forward to to trying this out...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
6800 only but changes should be easily ported to 6810.
Cheers sk806.

ZSKL2 variant or ZSKL2 only ?
nice works btw..

sg10 said:
ZSKL2 variant or ZSKL2 only ?
nice works btw..
Click to expand...
Click to collapse
ZKSL2 is only tested working - will change thanks.

just FYI, tried on DXLA2, bootloop.

Ezynow, the link you have provided for the firmware is P6800ZSLA2_CSC_TGY.exe. I'm assuming this is the ZSLA2 firmware. Is this the same as ZSKL2?

reiconol said:
Ezynow, the link you have provided for the firmware is P6800ZSLA2_CSC_TGY.exe. I'm assuming this is the ZSLA2 firmware. Is this the same as ZSKL2?
Click to expand...
Click to collapse
ZSKL2 is P6810 firmware csc zzt for asian countrys

xenix96 said:
ZSKL2 is P6810 firmware csc zzt for asian countrys
Click to expand...
Click to collapse
Not completely correct. Both ZSKL2 and ZSLA2 is available for 3G (P6800) and both are set to TGY (Hong Kong) for CSC.

I've installed as per instruction of yours, installing the ZSKL2 firmware through odin on my P6800 3G tab. Did a complete wipe in recovery (no custom recovery yet) and rebooted. The unit kept bootlooping with the samsung logo.
I wish I can do a logcat through adb but it seems like adb doesn't want to bridge into my unit.

xenix96 said:
ZSKL2 is P6810 firmware csc zzt for asian countrys
Click to expand...
Click to collapse
I mean the firmware link ezynow has provided points to the ZSLA2 (LA2) firmware but these modifications of his are for the ZSKL2 (KL2) firmware. So my question is whether the link pointing to the LA2 firmware is the same as KL2 firmware.
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
I've just noticed ezynow has updated the link to ZSKL2 firmware. Downloading this version now but will hold off install it. Seems some people are having problems...

kazuni said:
I've installed as per instruction of yours, installing the ZSKL2 firmware through odin on my P6800 3G tab. Did a complete wipe in recovery (no custom recovery yet) and rebooted. The unit kept bootlooping with the samsung logo.
I wish I can do a logcat through adb but it seems like adb doesn't want to bridge into my unit.
Click to expand...
Click to collapse
Updated the download link in main post.
will try reflashing to stock myself.
It could be samsung has properly prevented flashing of custom kernels through cwm etc.
will do some testing later today

ezynow said:
Updated the download link in main post.
will try reflashing to stock myself.
It could be samsung has properly prevented flashing of custom kernels through cwm etc.
will do some testing.
Click to expand...
Click to collapse
I believe you are right.
Scenario 1:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, reboot into recovery to wipe, reboot into normal, go into odin, flash recovery kernel,reboot into recovery and install root zip, rebootinto recovery and installed ezyNow kernel, bootloop.
Scenario 2:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, finish setup, reboot into recovery to wipe, reboot into normal, reboot into recovery and install root.zip, reboot into normal, reboot into recovery to install ezyNow kernel, boot fine.
Scenario 3:
Gonna try Scenario 2 with ZSLA2.
All in all, great job!
p.s. before scenario 3, i am actually wondering i should install recovery kernel now, but as far as i remember, the recovery kernel install will override your ezyNow kernel install perhaps (on new samsung devices, they do not distinguish kernel and recovery anymore i believe, as I have talked to tegrak about my korean Galaxy Note (SHV-E160S) it takes a lot longer time to create a recovery + kernel mod.)
p.s.2 screenshot of ezy installed:

Some updates:
1800Mhz freeze my tab (using SetCPU)
Not very stable with those uv rates. I'm gonna try to raise them by 50mV per setting, let's see if that helps.

kazuni said:
I believe you are right.
Scenario 1:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, reboot into recovery to wipe, reboot into normal, go into odin, flash recovery kernel,reboot into recovery and install root zip, rebootinto recovery and installed ezyNow kernel, bootloop.
Scenario 2:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, finish setup, reboot into recovery to wipe, reboot into normal, reboot into recovery and install root.zip, reboot into normal, reboot into recovery to install ezyNow kernel, boot fine.
Scenario 3:
Gonna try Scenario 2 with ZSLA2.
All in all, great job!
p.s. before scenario 3, i am actually wondering i should install recovery kernel now, but as far as i remember, the recovery kernel install will override your ezyNow kernel install perhaps (on new samsung devices, they do not distinguish kernel and recovery anymore i believe, as I have talked to tegrak about my korean Galaxy Note (SHV-E160S) it takes a lot longer time to create a recovery + kernel mod.)
p.s.2 screenshot of ezy installed:
Click to expand...
Click to collapse
kazuni said:
Some updates:
1800Mhz freeze my tab (using SetCPU)
Not very stable with those uv rates. I'm gonna try to raise them by 50mV per setting, let's see if that helps.
Click to expand...
Click to collapse
Good to see
So the second way of installed worked for you.
You should be able to flash cwm recovery now. Cwm recovery uses a seperate partition/kernel which should be fine. I am running it off course. I have flashed kernel using cwm afterwards fine but the first time might need be through stock recovery.
Please could you check if your binary counter has increased by going into odin download mode. Samsung may have been sneaky in different bootloaders
Oc to 1.8 was not stable for me at stock volts so this just experimental - may try lowering to 1.7 as max overclock or introducing an intermediate frequency step so the "jump" from low to high frequency is not that large but 1.6 undervolted is ok for the time being.
cheers

ezynow said:
Good to see
So the second way of installed worked for you.
You should be able to flash cwm recovery now. Cwm recovery uses a seperate partition/kernel which should be fine. I am running it off course. I have flashed kernel using cwm afterwards fine but the first time might need be through stock recovery.
Please could you check if your binary counter has increased by going into odin download mode. Samsung may have been sneaky in different bootloaders
Oc to 1.8 was not stable for me at stock volts so this just experimental - may try lowering to 1.7 as max overclock or introducing an intermediate frequency step so the "jump" from low to high frequency is not that large but 1.6 undervolted is ok for the time being.
cheers
Click to expand...
Click to collapse
got custom recovery working. was gonna do a full nandroid but i can't because the kernel isn't stable enough for me.
the counter hasn't increase, but then i was planning to make a jig cable to reset it anyway
I believe you are right - the jump from 1.6 is a big gap. I've placed both 1.6 and 1.8 at 1400 and it seems to be a bit more stable.

kazuni said:
got custom recovery working. was gonna do a full nandroid but i can't because the kernel isn't stable enough for me.
the counter hasn't increase, but then i was planning to make a jig cable to reset it anyway
I believe you are right - the jump from 1.6 is a big gap. I've placed both 1.6 and 1.8 at 1400 and it seems to be a bit more stable.
Click to expand...
Click to collapse
Good news. Be aware setcpu can be buggy it can set voltages / max frequency at boot even though you say not too after a freeze/lockup
Once I had to boot into cwm recovery (no overclocking here), use adb shell to delete the setcpu.xml files in /data/data/com.mhuang.overclocking, just to clear all the setcpu stuff.
Been running 1.6 undervolted solid for a couple of days no problems

ezynow said:
Good news. Be aware setcpu can be buggy it can set voltages / max frequency at boot even though you say not too after a freeze/lockup
Once I had to boot into cwm recovery (no overclocking here), use adb shell to delete the setcpu.xml files in /data/data/com.mhuang.overclocking, just to clear all the setcpu stuff.
Been running 1.6 undervolted solid for a couple of days no problems
Click to expand...
Click to collapse
Thanks for the advice, I managed to reset set CPU back to stock by deleting the files under data data com.mhuang.overclock, because I didn't know that its the xml file actually contains boot time configurations.
After maximizing the clock and set it to 1400, the unit still randomly reboots. Anyway I'm still keeping your kernel because I like the under voltage
Sent from my GT-P6800 using xda premium

[Q] Format/Cleaning my SGS, going for ICS cleanest as possible!

Hello,
First I want to say sorry because my english isn't on a high level.
I'm a SGS user for some months and I flashed it many times ago (MIUI, CM7, other custom roms...). Now I'm on "teamhacksung ICS 4.0" by... lets say 1-2months.
I was thinking of upgrading to the latest version of your ROM and wanted to use to try to leave my SGS as if it was just purchased.
I was wondering which is the most appropriate way to do it.
As much as I wanted (I started looking more than 1 hour ago) I have not enlighten.
I searched about clean "Stock ROMS" but I think that I will not be able go to into CWM and I will not be able to install again CM9 via .zip
So.. whats the solution???!!!!!! I'm getting crazy...
Thanks guys.

Do a factory reset and clear catched data
Sent from my GT-I9000 using XDA

1. in CWM factory reset
2. wipe cache partition
3. advanced > wipe dalvik cache
4. mount & storage > format sdcard
5. install an Kernel cleaning script (like this one from lippo) under install zip (from an e.g. extern sdcard)
6. than flash a rom 2 a clean system
there you go

Schlabbernr1 said:
1. in CWM factory reset
2. wipe cache partition
3. advanced > wipe dalvik cache
4. mount & storage > format sdcard
5. install an Kernel cleaning script (like this one from lippo) under install zip (from an e.g. extern sdcard)
6. than flash a rom 2 a clean system
there you go
Click to expand...
Click to collapse
1. So with that, I won't lose "Root" and the "CWM" wich I have at my phone?
2. Doing that will clean completly the system?
3. It isn't better to first install a stock rom (eg JVT or JVU), install a kernel that makes me automatically "Root" and installs "CWM", and then install CM9?
I don't know wich "kernel" or "rom" I have at the moment under my CM9 (...maybe I'm confusing concepts...).
Thank you so much!

atmos7fera said:
1. So with that, I won't lose "Root" and the "CWM" wich I have at my phone?
2. Doing that will clean completly the system?
3. It isn't better to first install a stock rom (eg JVT or JVU), install a kernel that makes me automatically "Root" and installs "CWM", and then install CM9?
I don't know wich "kernel" or "rom" I have at the moment under my CM9 (...maybe I'm confusing concepts...).
Thank you so much!
Click to expand...
Click to collapse
1. You will lose Root and CWM, cause you go back to stock.
2. No. To format "as from the store" you need to flash stock gingerbread - JVU, JVT, with repartition checked in Odin (it wipes also sd card);
3 After you install stock gb, flash a rooted kernel, like CF-Root or Semaphore and then flash ICS.
CM7 and Gingerbread(GB) are Android 2.3.x
CM9 and ICSSGS and other are Android 4.0.x
Make sure what you have. Cm9 is another build than ICSSGS.

Trak-X said:
1. You will lose Root and CWM, cause you go back to stock.
2. No. To format "as from the store" you need to flash stock gingerbread - JVU, JVT, with repartition checked in Odin (it wipes also sd card);
3 After you install stock gb, flash a rooted kernel, like CF-Root or Semaphore and then flash ICS.
CM7 and Gingerbread(GB) are Android 2.3.x
CM9 and ICSSGS and other are Android 4.0.x
Make sure what you have. Cm9 is another build than ICSSGS.
Click to expand...
Click to collapse
At the moment I got: "teamhacksung's CM9 ALPHA (Build 16)"
- Wich stock rom do you recommend me for CM9 or ICSSGS then? I got JVT at the moment with modem JVT from "siky_dude" post but my conex isn't working propely...
How can I know wich is the most aproppiated stock for my phone? I'm from Spain and I'm Vodafone (I dont know if that matters).
Thank you again guys!

atmos7fera said:
At the moment I got: "teamhacksung's CM9 ALPHA (Build 16)"
- Wich stock rom do you recommend me for CM9 or ICSSGS then? I got JVT at the moment with modem JVT from "siky_dude" post but my conex isn't working propely...
How can I know wich is the most aproppiated stock for my phone? I'm from Spain and I'm Vodafone (I dont know if that matters).
Thank you again guys!
Click to expand...
Click to collapse
Well.. if you are on Vodafone in Europe, use XXJVU (don't forget to check repartition). You can find it on Sammobile.com or here on XDA. Flash that one. Then flash Semaphore 2.5.0 (not 2.5.0 BM).
After that you can copy on your phone the rom that you want. I am on ICSSGS. I found it the best (this is up to you).
For the modem, you have to try to see which one has the best reception in your area. In Romania, i use JVT and JVU. Both work fine.
After you flash ICS, you can also try KF1 and KB3 for modems: http://forum.xda-developers.com/showthread.php?t=1548815
As a further reference, ICSSGS has a RC5 in testing, and in the next few days will be updated to 4.0.4 because Google has started releasing the sources.

Help newbie with installing new ROM

Hi, I'm stuck with installing new rom, so I hope, that you'll help me.
There are steps what I've done:
- followed THIS topic and ROOT the device with ODIN and CF-Root 4.4 file.
- OKAY, I'm rooted, so let's flash the new ROM
- entered in Clockworkmod Recovery and format EVERYTHING ( /data, /system, /cache, /sdcard etc.... just everything) for clear system
- next I load package with ROM and than INSTALLL
and here is the most important part
- when installed ROM gets something like bootloop but with restart - ROM is loading and after about 40 sec its RESTART
- and the same thing over and over again - restart ->loading->restart.... System never start up correctly to the end
- then when I saw that it does not work, I tried go into the CWM, but there was no CWM (!!!) - it was erased (by installing new ROM maybe???)
- so I must flash (old and stock) ROM via ODIN and again root device with CF-Root (with CWM) - that was only functional rom, what I was able to run, and again did this procedure
I tried this way, perhaps with millions of different ROM and EVERY was stucked (restart) while loading.
I think there are some non-deleted files in device, which should be erased (and which cannot be erased by CWM) for clear start of new installed ROM, what do you think?
Would someone please help me? I don't want old Gingerbread with Kies
Thanks for every responce!

Does it say in the thread that you have to flash a custom kernel?? Give.me the link for the thread so I can make sure that you've done everything right
Sent from ma 5assak

there is a link, but in hypertext THIS, i repost it in full text:
http://forum.xda-developers.com/showthread.php?t=788108
I think, when I've root and CWM, there is no problem and install a new rom will be very least, so not as it seems

Dude this is a kernel not a rom what's the matter with you??:what:
Sent from ma 5assak

please read all my topic - i flash this kernel only for clockworkmod recovery
through CWM I can flash any other rom
through ODIN only stock - cant find any ICS or JB rom which I can flash via ODIN (.tar file)

What variant of i9000 do you have? Are you sure that the rom you are trying to flash is made exactly for your variant?
EDIT: Try Darky ROM, they have an ODIN flashable version called "Resurrection Edition" or something.

I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak

Samsung Galaxy S I9000, i'm sure 100%. NOT I9001, NOT Samsung Galaxy S2. Tried many roms from Development section for I9000, tried from get.cm etc... always the same result bootloop with restart
donhashem.dh said:
I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak
Click to expand...
Click to collapse
OK. For example: this rom cm-9.0.0-galaxysmtd and cm-9-20120815-NIGHTLY-galaxysmtd from http://get.cm/?device=galaxysmtd
Or this one last ([ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S) http://forum.xda-developers.com/showthread.php?t=1778526 and 20120808 build.
and [ROM][PORT][ANDROID 4.1.1][BETA] TAJB: Jelly Bean port for Galaxy S V7.1 http://forum.xda-developers.com/showthread.php?t=1747042
and this too [4.0.4][ROM] Dark Knight 5.5 [27/4/2012] http://forum.xda-developers.com/showthread.php?t=1510940
and many more....
realy unhappy from this

Nikishek said:
Samsung Galaxy S I9000, i'm sure 100%t
Click to expand...
Click to collapse
I meant I9000 or I9000B or I9000M or I9000T there's a difference between them

I9000 only, checked it several times

Ok so you can flash Darky Rom Resurrection Edition through ODIN with no problem. Its GingerBread if i remember correctly, but it should give you a recovery mode and fully operating phone. From this point you can flash whatever you want.

....And there is one more important thing:
When I have a stock kernel and stock rom from Samsung, cant get into recovery mode - VOLUME UP and POWER non functional. Only when I type: "adb reboot recovery" in terminal.
Just after when I flash a new pre-rooted kernel with CWM, VOLUPE UP and POWER is now functional
k4Z3666: OK, I try and give you an echo I think, when I format everything in CWM, there will be no sign of the earlier system and ALL WILL BE CLEAR

Nikishek said:
I9000 only, checked it several times
Click to expand...
Click to collapse
ok, flashing ICS, may need to be done twice, as first flash may bootloop, IF you want to return to stock to get out of this mess, since you are not sure as to where you are now, due to flashing many roms, use any kit from My Android Collections, link below to get you to a booting ROM, than add a kernel with CWM (use EZbaze package with kernels)

that's helped me too thank you
Sent from my GT-I9000 using xda app-developers app

A couple of questions about flashing

I flashed my phone first with stock 2.3.6 ROM using Odin 1.85 (with re-partition). Now I'd like to install CM11.
The problem is that CM11 requires CWM 6.0.4.5 and all CF-root kernels come with CWM 3.0.x.x. Is there any way I can root stock ROM with Odin and get the latest CWM immediately?
The way I came around this problem was to first root it with CF-Root-XX_OXA_JW4-v4.4-CWM3RFS, then install stable CM 10.2.1 which comes with the right version of CWM, then data wipe/factory reset + cache wipe, then installed CM11. Next came gapps, Semaphore 3.4.3s and KK44_BigMem_18-nov-13.
I'm thinking that something could have gone wrong because the install wasn't clean enough (the clock once showed 4 different time values, depending on which clock I was looking at on my screen - main clock, upper right or from the drop down menu). That was with bigmem enabled in Semaphore.
1) To perform a 100% clean install do I have to re-partition it with Odin? Or can I perform 'complete format' from within CWM that's important when installing new ROM?
2) If I'd like to switch kernel from Sema 3.4.3s to 3.4.3, what should I do? Is it enough to just install it with CWM recovery? Are wipes necessary? I think kernels are installed on 'Kernel' hidden partition, so there's nothing I can do to clear it somehow. Or do they put alter the boot partition as well?