yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] gverma1:
Pawitp has managed to enable dual sim function for i9082 but that is experimental. Also, Pawitp's CM11 implementation on i9082 is unofficial as mentioned on that thread.

But I agree it doesn't make sense to use custom ROM on that phone - simply rooting it would be good enough.
[Galaxy S I9000 Android Development] Trainer_H:
Can anybody tell me, why i have a high battery usage from android OS?

The system is a little bit slow as well.
[Galaxy S I9000 Android Development] TearsDontFalls:
Hmm df reports the same free space like disk usage, but counts the "System Data" as used space, so I guess there are some hidden files?
[Galaxy S I9000 Android Development] pawitp:
There are no hidden files, du would have accounted for all of them if there are. It may be an issue with yaffs garbage collection, which I'm not too familiar with. Try getting the output of /proc/yaffs and read some information here: http://lists.aleph1.co.uk/lurker/message/20130924.225734.206182d1.en.html.
[Galaxy S I9000 Android Development] turtuv:
Why i can't see any ringtones and notifications sounds in "Settings --> Audio"? I tried to wipe media storage cache, but nothing.
[Galaxy S I9000 Android Development] Steephig:
Had the same.

All sounds somehow all were replaced with the Sheep ringtone/sound. Not the actual file, but it was all it would play. Deleted data and cache for the Media Manager and updated to cm-11-20140403-NIGHTLY-galaxysmtd.zip and after a little of time the sound library was rebuilt and all ringtones and notifications were working properly again.

Guess something has been changed in the media manager.
[Galaxy S I9000 Android Development] turtuv:
I wiped data and cache of media storage, what media manager is exactly?
[Galaxy S I9000 Android Development] slaj76:
Your problem is in the cache of the apps. It is becoming huge after wile simply delete the cache of the apps like g+, browser ,Facebook... There won't be any force closing but you have to do that again and again .
[Galaxy S I9000 Android Development] freakymod2120:
Problem with latest CM-Nightly

HI,

with latest nightly and standard-kernel, normal way of flashing as every day i have bootloop with "Samsung S-Branding" and "Galaxy S Cyanogenmod" ...

What is the best way to recover my phone???

Thanks in advance !!!
[Galaxy S I9000 Android Development] BeriCud:
HI after flashing latest cm-11-20140405-NIGHTLY-galaxysmtd.zip I´m unable to boot up and enter to CWM. Have someone the same experience or I´m doing something wrong. Before flash I do factory reset and format system. After flashing cm-11-20140405-NIGHTLY-galaxysmtd.zip + gapps-kk-20140105-signed.zip and formating cache I´m try to reboot but it´s didnˇt boot up. I only see sign cyanogenmod but face with circle never come and when cyanogenmod disappear it strats from begening again and again...

Can someone help me?
[Galaxy S I9000 Android Development] freakymod2120:
hi i have the same issue after flashing latest nightly ...
[Galaxy S I9000 Android Development] tetakpatak:
The cause of bootloop might be, that the last recovery didn't wipe well.

Try to flash with Odin any compatible KK kernel. Disable auto reboot, turn off the phone, boot to recovery, wipe again all and flash the CM11 rom and gapps again. If it still doesn't boot, back to stock with GB and PIT file.

tetakpatalked from my i9000
[Galaxy S I9000 Android Development] BeriCud:
Hmm OK but do you know any compatible kernel flashable by odin? Can you help me with I always flash by CWM...

I go back to GB + cfroot kernel and try to go back to KK but not the latest KK. In CWM I found none partition is it normlal?

I´m not able to boot up to kk it enter in CWM it self now. Maybe I do something wrong. I´m going to try it again and we´ll see...
[Galaxy S I9000 Android Development] tetakpatak:
Semaphore 3.4.3 or Mackay 0.613. You can also get PhilZ-CM11 kernel from the i9000 PhilZ thread, I have repacked it few days ago with the stock CM11 kernel and attached the Odin flashable version. It has booted with CM11 M2

EDIT: also [MENTION=3878858]didhiy[/MENTION]'s kernel should boot!

tetakpatalked from my i9000
[Galaxy S I9000 Android Development] BeriCud:
Thanks I´ll try it...

Not working for me. But if I flash PhilZ-CM11 kernel I´m able to boot up but in the end boot up it says that phone proces crash so I gess there is some trouble in stock kernel.

In the end I flash latest x-aries kernel and it boot up usefull and working fine. For now I didn´t found any issue. The developers should look at stock kernel and fix this bug.

I guess that other kernel for latest CM11 should work fine too.
[Galaxy S I9000 Android Development] pawitp:
Seems like a problem with the nightly. Flash an older kernel (or a compatible custom kernel) with Odin and then flash an older nightly. Do not flash newer nightlies until further notice.
[Galaxy S I9000 Android Development] turtuv:
Can anyone help me? I have the phone without any ringtones and notifications sounds :(
[Galaxy S I9000 Android Development] tetakpatak:
Reflash exactly your rom.zip without any wipe

tetakpatalked from my i9000
[Galaxy S I9000 Android Development] freakymod2120:
thanks i flashed Sema 3.4.3 via Odin and now my Device is online :o)

---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------

Hi,

flashed Sema-Kernel 3.4.3 over latest nightly and everything works fine...next nightly i`ll only flash when i got some info from you or the Flasher in the Form here ...:highfive:

Thanks!
[Galaxy S I9000 Android Development] tetakpatak:
[MENTION=3117667]pawitp[/MENTION] it must be kernel related then. CM11 stock kernel for other devices uses new blobs and they often don't work fine. I didn't check for the i9000 (I'm back to ICS) but you will know.

tetakpatalked from my i9000
[Galaxy S I9000 Android Development] sanguinesaintly:
Confirmed - Semaphore 3.4.3 via Odin solves the problem. Let's see what happens next.
[Galaxy S I9000 Android Development] turtuv:
I tried, but the problem is still there.
[Galaxy S I9000 Android Development] geckoas:
Also confirmed - Flashed Semaphore 3.4.3 via Odin V3.07 and my phone is back at live, even with cm-11-20140405-NIGHTLY.:good:

Thanks a lot.
[Galaxy S I9000 Android Development] rajeshbabushrestha:
i can confirm this... had bootloop after flashing april 5th nightly... but everything is working well after odin flashing semaphore 3.4.3 :good:
[Galaxy S I9000 Android Development] need4steer:
preferred solution for the boot loops after flashing cm-11-20140405-NIGHTLY

So what is your suggestion for those who wish to keep using the latest nightly and keep updating their ROM with the newer ones?

Flash the latest Semaphore_KK_3.4.3.tar and then continue using the built-in auto updater?

Or maybe we should

in order to avoid any problems that can occur from flashing the latest nightly on top of Semaphore_KK_3.4.3?
[Galaxy S I9000 Android Development] tetakpatak:
I consider it as 99% sure, that some automatically generated kernel related commits on the CM-jenkins server have caused the bootloops. Pawitp will take care of it ASAP.... (and many people here seem to not understand that pawitp is possibly the greatest expert for i9000 kernels here on the forum, all our kernel developers have had benefits of sharing pawitp's commits and knowledge). So you'll see soon good builds again ;)

FYI: there were massive problems with the new Cyanogenmod blobs also with other Samsung devices (I'm now ever more included in the development for the six Tab 2 models). Neither CM11 nor SlimKat could play videos or use Gallery, some people had bootloops or huge, mysterious battery drain. We have solved it by reverting the change of the blobs and still using now the old ones until it gets fixed.

The safest way would be to update manually:

wipe like you always do, (most of people don't do it, but I would always manually format /system)

flash the CM11 build

flash any CM11 compatible kernel (Semaphore 3.4.3, Mackay >0.609, [MENTION=3878858]didhiy[/MENTION]'s kernel or CyanCore etc)

Those who have wiped /system should also flash GApps after the kernel.

tetakpatalked from my P5110
[Galaxy S I9000 Android Development] tetakpatak:
OK, I understand, the kernel codes have been changed meanwhile.

I have PM'ed to pawitp some weeks ago to point me to the new sources to give it further to Phil3759 to recompile the PhilZ recovery image, but pawitp didn't answer me. I am too busy to search for it myself right now. The i9000 is not my primary target of interests, although I will use it as long as it lives....

PhilZ-CM11 package works with the CM11 build snapshot M2 but no more with the recent builds!

Therefore, also my advice to flash Semaphore v.3.4.2 was wrong, now only 3.4.3 works with the new builds! (my initial post edited) That was also the reason for stratosk to build the new version.

Regeretably, stratosk doesn't own the i9000 anymore and it is unfortunately only matter of time when will he totally abandon his kernel development for it. Ever less developers left on the board :(
[Galaxy S I9000 Android Development] need4steer:
A little off topic, but maybe it'd be a good practice flash procedure for others also, so I'll ask here: if I'm using the built in update mechanism, which not performing format of /system, is it considered to be more "dirty"?

(though I can feel that there's nothing like using a ROM after full wipe - a factory reset + a format of /system and /sdcard)

Is it a good practice to format /system before any flashing of a nightly?

What about all the apps and their configuration for those who don't use a 'backup and restore' app, and like it as clean and neat as possible? (It's about 30 minutes to download, install and configure them all)

My procedure until now was to perform full wipe before flashing CM11 for the first time, and then update regularly via the built in mechanism.
[Galaxy S I9000 Android Development] valenparra:
ODIN does not recognize the phone

I have installed today's nightly and I have the bootloop problem.

ODIN does not recognize my phone when connecting it in download mode to flash the new kernel. I have installed Kies to have the USB drivers, and when I connect the phone in download mode the computer installs the USB drivers, but ODIN does not detect the phone...can someone give me a hand here?

EDIT: Problem solved, I just tried with a different computer and it worked. Everything's fine with Semaphore kernel
[Galaxy S I9000 Android Development] albgen:
What worries me is that people that makes changes in the code don't even test them. Than on the nightly build **** happens.

I got now a device not working and i have to loose time because of this
[Galaxy S I9000 Android Development] valenparra:
Snapshot M5

Does the snapshot have the same bootloop kernel problem? Has someone tried?

EDIT: I have just installed Snapshot M5 coming from nightly 20140405 with Semaphore 3.4.3 and the bootloop problem is no longer there :)
[Galaxy S I9000 Android Development] tetakpatak:
Pawitp configures the nightlies the way that wipe of /system usually isn't required. Yet, it would be the "cleaner" way to install the nightlies. Unless you've wiped /data (made factory reset) all your settings, accounts and self-installed apps will remain saved. Yet the gapps will be gone with wipe of the /system so they have to be flashed again if the system was formatted. But the settings for the gapps are saved under /data, so after reboot nothing has to be configured again. ;)

tetakpatalked from my N7100
[Galaxy S I9000 Android Development] pawitp:
Skip nightlies until it's fixed, it won't be long.

It's impossible to test for every single build configuration. Read the first post about what a nightly is. Nightlies are designed to allow adventurous testers to test new features and find new bugs. Nightlies are not meant to be stable and may sometimes break. If you need a stable build, use the M releases.

---

Nightlies should work again once http://review.cyanogenmod.org/#/c/62235/ is merged.
[Galaxy S I9000 Android Development] RowanDDR:
You want bleeding edge software, and 100% stabiity? Not asking for much are you. Why not stick to the M releases if stability is so important to you?

EDIT: Pawitp beat me to it!
[Galaxy S I9000 Android Development] albgen:
What i actually do is the following before any upgrade to another nightly: backup first than upgrade. If does not have big problems than keep yje nigthly otherwise revery back to the backup.

Next time i will be more carefull and use m releases

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S I9000 Android Development] DerRomtester:
This is called nightly and not stable. We are the testers and than we report bugs and they fix all the not working things and than when everything is fixed they release a stable build and when you flash the stable build everything is working.
[Galaxy S I9000 Android Development] p.chi:
excuse me for posting this rookie issue here but I hope I can get bit of help. I also have the bootloop but I can't get into recovery at all to repair it. I've been holding the volume buttons and power while powered off and it just cycles the AT&T logo. Have tried a few different combinations like the volume up and power; volume down & power; home, vol up & down, power; but just keeps restarting. It gets to the first cyanogen mod boot screen, after the ATT world phone logo, but then reboots. Any ideas I can try to get this working again?
[Galaxy S I9000 Android Development] need4steer:
I solved it by flashing the latest Semaphore_KK_3.4.3.tar in download mode with Odin3 1.83.

BTW, you're entering download mode with volume down + home + power buttons.

There are other options for you, within them:

Flash the stock version and then flash cm-11-20140405-SNAPSHOT-M5-galaxysmtd.zip or cm-11-20140404-NIGHTLY-galaxysmtd.zip .

Wait for tommorows nightly (cm-11-20140407-NIGHTLY) in which this issue is fixed (and flash it on top of a stock version).

Flash other kernels.

Read a few comments back - most of the people flashed other kernels. I did it also.

However, I love being on the latest nightly, and I prefer CyanogenMod's kernel. If you love it too - I believe it'll be better for you to flash stock, and then flash the M5.

And when tomorrow's release will be available - flash it.

I hope I gave you enough information.

Don't forget that there are great threads for us, among them great FAQ's, guides and tutorials in the Galaxy S I9000 Q&A, Help & Troubleshooting which will help you with flashing.

Good luck!
[Galaxy S I9000 Android Development] ciano865:
Next nightly will have this patch in.

http://www.cmxlog.com/11/galaxysmtd/
[Galaxy S I9000 Android Development] p.chi:
Thx for the information need4steer, I was just needing some other way to be able to get into recovery or download mode. No key combination was working for me. I'm now able to get into download mode by removing the battery, attaching usb cable from pc, holding down the volume buttons and then placing battery back in, download mode immediately appeared. Opened Odin 1.85, see it recognized and placed the semaphore.tar file in the bootloader field and it seems I'm back up.
[Galaxy S I9000 Android Development] CatalystWon:
I'm trying to install the Samsung USB Debugging mode drivers on Windows 7 (32). The basic USB drivers were automatically installed by Windows Update and I have no problem reading/writing to internal SD or external microSD.

I successfully installed SAMSUNG_USB_Driver_1.4.2.2 which worked fine under XP.

In Device Manager/Other devices/GT-I9000/Update Driver Software - GT-I9000.... under Manufacturer, I see many Samsung entries. When I look under MODEL I don't see GT-I9000 anywhere. Instead I see entries like SAMSUNG Android ADB Interface, SAMSUNG Android Composite ADB Interface.

Instead of either of the above, I installed the latest Android SDK + the Goggle ADB Driver (android_winusb.inf), but I prsume thats just for Nexus devices. It installed but did not work. I un-installed and tried the SAMSUNG Android Composite ADB and it also installs but does not work. I also tried from SAMSUNG Android ADB Interface Driver v2.9.510.0 with no success.

After hours of searching, installing, un-installing, rebooting I would appreciate knowing what has been proven to work with Windows 7 and the GT-I9000. Clear steps are always appreciated. Thanks!
[Galaxy S I9000 Android Development] pawitp:
20140407 is safe to flash.
[Galaxy S I9000 Android Development] tetakpatak:
[MENTION=2867819]Catalyst2012[/MENTION]

This is much better thread for your question:

http://xdaforums.com/showthread.php?t=961956

tetakpatalked from my i9000
[Galaxy S I9000 Android Development] AusMatt:
Confirmed.

I have flashed it without problem.
[Galaxy S I9000 Android Development] Alunduyn:
I'm facing the same problem described by TearsDontFalls, and have not been able to solve it even by formatting the whole /datadata partition by recovery. Today is the third day I'm running my CM. I did a full wipe three days ago (formatted everything form recovery except SDcard0 and 1), flashed CM and gapps. Booted up and my free space in datadata was less than 50mb. By now, my "System data" used space is 373 mb, all the rest is filled by "true" system data, as example com.android.providers.media. I've read the whole mail you linked without being able to find a solution, it just explains (as I got it, I'm not that good) what happens, that some files are marked to be reused but not actually reused. Can I get any hint? My phone is being unusable and not even a wipe gave it back to me working.
[Galaxy S I9000 Android Development] pawitp:
The point is I don't know either.

In recovery, make sure /datadata is unmounted. Run the following command from adb "erase_image datadata". Post the error messages (if any) and the output of "dmesg". Then mount the partition and check the free space.

Note: the command will wipe your /datadata
[Galaxy S I9000 Android Development] tetakpatak:
Did you reboot since installing CM11? I remember it solved similar situations for some people.

tetakpatalked from my N7100
[Galaxy S I9000 Android Development] albgen:
I installed the semaphore kernel than cyanogm started. Than i have made an upgrade to the latest nightly(04.07) and it is working

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S I9000 Android Development] ranjib:
Haha, I did the whole thing during a car ride to a gig with my band. A Samsung netbook and internet via Sony experia were my friends....when we arrived at the location, my I9000 was ready again....:eek:
[Galaxy S I9000 Android Development] AfXv237:
Bootloop out of space. How to wipe all data?

Hello, I have a big problem. I updated my Galaxy S i9000 last night with cm-11-20140406-NIGHTLY-galaxysmtd.zip . Everything has been installed perfectly, but after it rebooted, I got stuck into a bootloop. Obviously, I went into Recovery mode and tried to Wipe data and cache, but it does not work. It shows this message everytime I try to Erase data/factory reset : E:format_volume: rfs format failed on /dev/block/stl10 after that however it says that Data wipe has been completed, but still does not wipe anything. I tried to install a previous version of CM-11 but it shows another error suggesting that there is no space left on the device. The thing is that I cannot access anything, neither via PC (via Kies). It works with Odin 1.83. I reinstalled 2 types of official firmwares, it installed them perfectly, but it still bootloops. I tried to tick the Re-Partition, but it wouldn't install the firmware this way showing another error. Practically, I cannot do anything, I cannot erase anything as I cannot access phone's internal storage.

Is there anybody that can help me out? I know, I should've searched the forum, actually, I did, but didn't find this situation. If is there anybody that can suggest me what to do (programs via PC that wipe all data or sth like this) please help me out. I do not really have much free time to fix it myself as I work all day long + college.

P.S: Phone does not get recognised when I connect it to USB to the PC (obviously phone is turned off)

P.S2: I do not care about the data, it is my old phone, I've noticed that cyanogenmod updates occupies all the space.
[Galaxy S I9000 Android Development] tetakpatak:
[MENTION=5211612]AfXv237[/MENTION] you did whole row of mistakes, reading just few posts back could have saved you of troubles.

We have several excellent sticky help threads, please move there to find the answers how to unbrick your phone.

If you don't read and learn before doing, it will be ever worse.

tetakpatalked from my N7100
[Galaxy S I9000 Android Development] AfXv237:
But is there anything I can do now to get it back to work?
[Galaxy S I9000 Android Development] kodea:
Ok i'm bootlooped from that rotten nightly.

Problem is flashing semaphore with odin did NOT fix it. It still bootloops.

I can acess download mode and use cwm. But no nightly i install solves the bootloop.

Any nightly i install > reboot system > goes straight to cwm.

How can i fix this? (i already tried wipe data and fresh install a nightly = same crap)

EDIT: Solved by going back to stock 2.3.6 with odin > cwm root > cm11 from internal
[Galaxy S I9000 Android Development] tetakpatak:
If the download mode still works, there should be no problems.

tetakpatalked from my N7100
[Galaxy S I9000 Android Development] gverma1:
As tetakpatak said, if download mode works, there is no problem, else you will have to purchase a JIG (sold on some sites and you could even make one - instructions are there on youtube).

Pls remember if you ever tick Repartition in Odin, you have to have the relevant pit file, else you will brick your phone. Normally checking repartition in odin is not required. If you have your stock firmware, after flashing it via Odin, you may have to flash (as pda) dbdata.rfs.tar. Search for it... its on XDA.
[Galaxy S I9000 Android Development] pawitp:
Maybe it is damaged, or maybe the driver thought it is damaged. If you flash a stock ROM, it'll revert back to BML format then you can convert it back to MTD again by installing CM11. If the problem still appears after that, then the partition may be damaged. You can disable the use of /datadata (which moves all data into /data) by running "touch /datadata/.nodatadata", however, it may result in lag if your NAND chip is slow.
[Galaxy S I9000 Android Development] kodea:
--- solved by turning off and on (a classic) ---
[Galaxy S I9000 Android Development] Alunduyn:
Oh my God I really tried to flash a stock ROM. Never going to do this again. Getting back to CM was like a ride out of hell because all the official firmwares download were down and I was struck with 2.2.1 and I had no way to root 2.2.1. I just got mad. Now at least I'm on 2.3.6. CM Installer doesn't support sgs on 2.3.6, so the ride is going to be still long I fear. Reporting ASAP.

EDIT: Hurrah! My poor old sgs is back running CM11 (and dammit, I was starting to forget how AWFUL it was before CM, Thanks guys for your wonderful work one more time), and not only : my /datadata is completely empty! All hail mr pawitp, totally saved my day.

EDIT 2x: I'm reading only now the post from rodman01. Thanks a lot, that would probably have saved me 2 or 3 hours, just damn me for not reading :P Still, thank you a lot mate
[Galaxy S I9000 Android Development] rodman01:
I uploaded slappys rescuepack a couple of days ago. There included is a odin version, a rom version, root kernel and as well as a readme file. Please read it carefully and follow the steps.

Hope it helps :fingers-crossed: and Good luck: http://www.mediafire.com/?t30r06thh2dvphk
[Galaxy S I9000 Android Development] CatalystWon:
Good for you, but your useless post is of no help to anybody.:eek:

Thanks tetakpatak; I've been there many times; only after not finding a solution I decided to try to get solution here.
[Galaxy S I9000 Android Development] tetakpatak:
I think 1.5.33.0 is indeed the most recent Samsung mobile USB driver version and it is updated in the OP there with direct download link, it works flawless on my Windows 7 64-bit..... I hoped it will help :(

And it was correct what you wrote, google USB driver is for Nexus devices.

tetakpatalked from my P5110