yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] slick_rick:
Well download whatever rom+mods/etc and put the files on your phone. Then just odin/mobile Odin the el26 cwm kernel and flash whatever you want from there, ICS or GB without no chance of a brick.

On our phone and I think most Samsung's for that matter, the recovery isnt separate from any other partition like with HTC. It must be packed into the kernel. So whenever you flash a rom, whatever recovery is packed in with that kernel included with the rom is what you're getting. Most devs are packing in stock Android recovery to cut down on bricks and instead recommend always flashing from el26 cwm kernel.

So yea that's what makes mobile Odin so great. Have el26 on your storage and you can switch roms very fast, easy, and safe.

Anymore questions just ask.

Edit: are you on GB or ICS Blue Kuban and what rogue also?
[Samsung Epic 4G Touch] mjs2011:
Thanks, really good info. I'm on Blue Kuban ICS right now with Rogue CWM 5.0.2.7. Looks like Odin will be a very easy way once I get comfortable with it.

So basically, I'll put the kernel zip in the PDA slot in Odin and let it do its thing, then my phone will auto reboot into the kernel's recovery where I can flash the ROM? Or do I flash the kernel in Odin, and also flash the ROM in Odin as well?
[Samsung Epic 4G Touch] slick_rick:
Odin is just used to flash the safe el26 cwm kernel onto your phone. It will auto reboot and just hang at the Galaxy S II screen since the GB kernel can't boot an ICS rom so just power+volume up into it. Hold it for maybe up to 15 seconds but it'll come around. You then flash the rom in recovery from there. So put you rom files, etc on your phone before you Odin the kernel.
[Samsung Epic 4G Touch] mjs2011:
oh ok sweet. That sounds pretty easy, actually! LOL! One last question hopefully, do I need to extract the kernel zip or do I just place the zip in the PDA slot?

Thanks again for your help today. It really cleared a bunch of questions I had.
[Samsung Epic 4G Touch] slick_rick:
Kernels flashed through PDA slot in Odin will be in either .tar or tar.md5 format, .zips are for cwm recovery only. You can find the el26 cwm kernel in the kernel repository sticky in dev section, its the first kernel listed. No problem, glad to help.
[Samsung Epic 4G Touch] bmckinney212:
or u can use the 34gt auto

http://xdaforums.com/showthread.php?t=1342728
[Samsung Epic 4G Touch] mjs2011:
Thanks again everyone. I successfully switched roms today with no issues.
[Galaxy S III Android Development] cdesai:
Hi everyone.

As you all know, Samsung distributes source code as tarballs which isn't the best way to redistribute kernel source code

git is the best modern way to work with Linux Kernel sources, designed by Linus himself in this purpose.

So, i made an organization on github for that.

https://github.com/sgs3

And yea, that means source code has been released, head on to http://opensource.samsung.com/

Kernel Sources :

https://github.com/sgs3/GT-I9300_Kernel

Branches :

master :- branch you should use(for developers), will contain fixes and more in the future (currently identical to stock_update4)

stock :- Kernel sources from GT-I9300_ICS_Opensource.zip, unmodified

stock_update1 :- Kernel sources from GT-I9300_ICS_Opensource_Update1.zip, unmodified

stock_update4 :- Kernel sources from GT-I9300_ICS_Opensource_Update4.zip, unmodified

If anyone wants to commit any fixes / anything else, fork and shoot a pull request :)

How to Build :

Get teh sauce:

git clone git://github.com/sgs3/GT-I9300_Kernel.git
cd GT-I9300_Kernel
git checkout master

Tell it to use our config:

make ARCH=arm CROSS_COMPILE=/path/to/toolchain m0_00_defconfig

Teh real build:

make CROSS_COMPILE=/path/to/toolchain

or

make -j `cat /proc/cpuinfo | grep "^processor" | wc -l` CROSS_COMPILE=/path/to/toolchain

The compiled kernel is arch/arm/boot/zImage
[Galaxy S III Android Development] AndreiLux:
Was about to post this :)

Will start compiling and have a kernel up and running soon I hope. This time in contrast to the S2, it's time for serious developing.

Here's a direct link to the S3 files: http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-i9300
[Galaxy S III Android Development] ::indie:::
This is great news guys,

lets hope that we will also have a proper CWM recovery soon.
[Galaxy S III Android Development] Chainfire:
stickied

@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters :)

EDIT: this is the patch in question: http://git.kernel.org/?p=linux/kern...it;h=371a689f64b0da140c3bcd3f55305ffa1c3a58ef. Apparently Sammy took this out again in their sources (according to somebody else, I haven't had time to confirm yet, but I can see the boot partitions do *not* appear on my device), they may have bastardized it further ...
[Galaxy S III Android Development] Toss3:
No CF-Root Kernels for the i9300? :)
[Galaxy S III Android Development] Chainfire:
Well it's not needed as much due to the separate recovery, but if there's demand, I'll build CF-Root's... but those are based on Samsung binaries, not source.
[Galaxy S III Android Development] Intratech:
Great! I'll go through this when I get the time.
[Galaxy S III Android Development] pglmro:
Of course I want a CF kernel ;)
[Galaxy S III Android Development] Roughnecks:
I think everyone of us want a CF-Root-Kernel :D
[Galaxy S III Android Development] 9Lukas5:
I don't really see the point why we should make that. I have flashed cwm with Odin and then the SuperSu cwm flashable zip available here on xda. Then installed busybox installer from the play store. Much easier to do as letting Cainfire always compile a cf-root kernel for us. :confused:

L
[Galaxy S III Android Development] pitje222:
great seeing some a class developers here!!

thanks for opening this thread..

and good to know ya'll have a s3 aswell.. :D

grtz!
[Galaxy S III Android Development] Stevemeister:
Great news :D, hope to see some nice custom kernels soon!
[Galaxy S III Android Development] torxx:
Kernel dev's:

Please share your github if you start then :)
[Galaxy S III Android Development] sakindia123:
what?update#1 is already out?

Hope Samsung release a cleaner source this time :)
[Galaxy S III Android Development] cdesai:
Looks like they messed up the first zip, so the quick update

Only change i can see from stock to stock_update1 is the changing of file mode from 0755 to 0644
[Galaxy S III Android Development] xos84292:
Samsung releases source code for the Galaxy S III

UPDATE 1 is out.
[Galaxy S III Android Development] detule:
They seem to have hacked it out pretty crudely (certainly the korg patch won't apply cleanly). No device here, can't really test this, but the attached patch should properly allocate any mmc boot partitions.
[Galaxy S III Android Development] detule:
A couple more patches before I rm

No device here and no idea if I'll ever get one, but I thought I would post couple more cosmetic (yet instrumental) patches for your tree so that my last 15 minutes wouldn't be in vain.

#1: m0_00_defconfig: Run through menuconfig;disable GCC strict checking. Otherwise I get a lot of noise with codesourcery toolchains

#2: Add .gitignore files from korg trees.

Take care
[Galaxy S III Android Development] stratosk:
Anyone else get compilation error due to SVN_REV variables in these Makefiles:

drivers/media/video/samsung/mali/Makefile

drivers/media/video/samsung/ump/Makefile

I comment out the lines and replaced them with

SVN_REV=:0000

I used 0000 because of the comment in the Makefile.

Now, it compiles without error (though untested since I don't own S III)
[Galaxy S III Android Development] Chainfire:
Nope ... didn't get those errors!
[Galaxy S III Android Development] stratosk:
According to this line in Makefiles:

SVN_REV:=$(shell ((svnversion | grep -qv exported && echo -n 'Revision: ' && svnversion) || git svn info | sed -e 's/$$$$/M/' | grep '^Revision: ' || echo ${MALI_RELEASE_NAME}) 2>/dev/null | sed -e 's/^Revision: //')

the SVN_REV variable takes its value from one of the 3 commands:

1) svnversion | grep -qv exported && echo -n 'Revision: ' && svnversion

2) git svn info | sed -e 's/$$$$/M/' | grep '^Revision: '

3) echo ${MALI_RELEASE_NAME}

I get the following:

1) Revision: Unversioned directory

2) Unable to determine upstream SVN information from working tree history

3) Of course the MALI_RELEASE_NAME is not set in my shell

May I ask which of these 3 commands succeeds in your Linux box?

Thanks in advance.
[Galaxy S III Android Development] detule:
OC

Try this patch for overclocking to 1.5GHz.

Absolutely untested. Ok, done for real.
[Galaxy S III Android Development] etherez:
Will anyone make a i9100 port of this ?

Because i really loved 4.0.4 on i9300
[Galaxy S III Android Development] ale0crysis:
pls stop asking requests of other devices on GT-I9300 forum section
[Galaxy S III Android Development] sak500:
Are you sure it wont brick our phones if we try?
[Galaxy S III Android Development] arian009:
I got an S3 today morning I wos wondering how far can push the clock speed of this baby up. Looking at it's structure and slim design seems that anything over 1.6ghz can cause major over heating issues. But good work guys. Looking forward to see great releases in future!
[Galaxy S III Android Development] stratosk:
I'm sorry for asking this again. I would be grateful if someone could find the time to check the above commands.

Thanks.
[Galaxy S III Android Development] detule:
My guess is "svnversion" does not return "exported" in your build directory. If that's the case, then there should be an easy fix.
[Galaxy S III Android Development] stratosk:
Yes, this can be fixed. I found this commit from codeworkx's github. But, then it fails on the second condition.

Actually I wonder why we need these lines that checks then svn revision (obviously we will never synced with the original Samsung repositories). That's why I thought we could hard coded the revision to '0000' as the comment in the Makefile suggests.
[Galaxy S III Android Development] johku12:
No bricks

It's virtually impossible to brick samsung smartphones because of the download mode and easy way to flash stock rom besides hard brick bug on some sgsII variants. I wouldn't be worried when flashing the SIII and I'm going to as soon as I get mine. It's almost essential to root just to restore apps via titanium backup.
[Galaxy S III Android Development] tvhak:
anybody did this???
[Galaxy S III Android Development] AndreiLux:
Yes I already put it in, aside from enabling it in the defconfig you also need to populate the ASV table with some voltage values. But the problem is that there's something else blocking the cpu driver or something from going over 1400MHz, haven't found the issue yet.
[Galaxy S III Android Development] tvhak:
thanks for the answer. and for alpha 6.
[Galaxy S III Android Development] Chainfire:
I'm still wondering why you even get this ... the problem doesn't exist at all for my build, and I just followed the instructions ...
[Galaxy S III Android Development] stratosk:
I'm also still wondering what is the difference. :)

I wonder what is the value of SVN_REV variable after the execution of the specific line in your box.
[Galaxy S III Android Development] Chainfire:
It's empty ...
[Galaxy S III Android Development] stratosk:
So, even if I fix my svn or git svn config in my box I will get an empty variable.

I wonder if this is OK because of the remark in the Makefile:

# Get subversion revision number, fall back to 0000 if no svn info is available

That's why I said that maybe we could simply change it to a hard coded value 0000. But maybe this revision number is for informational purpose only.

Anyway, thanks a lot for your answer
[Galaxy S III Android Development] detule:
Perhaps it's this

https://github.com/sgs3/GT-I9300_Kernel/blob/master/arch/arm/mach-exynos/cpufreq.c#L704

Need to get myself one of these fancy devices and stop doing this blindly.

Edit:

Nevermind, max and min are (re)set in the return function call

return cpufreq_frequency_table_cpuinfo(policy, exynos_info->freq_table);
[Galaxy S III Android Development] AndreiLux:
There are issues with the stock APLL settings for 1500MHz, those are kind of fixed and it works with the performance governor, but now the problem is that pegasusq won't scale over 1400MHz... which is weird.
[Galaxy S III Android Development] iphdrunk:
[Q] default kernel config file?

Sorry for the dumb question, but it seems running kernel was not compiled with CONFIG_IKCONFIG so /proc/config.gz is missing. Is the .config file of stock firmware available somewhere? thanks
[Galaxy S III Android Development] cdesai:
Indeed, it's present in the kernel source.

https://raw.github.com/sgs3/GT-I9300_Kernel/master/arch/arm/configs/m0_00_defconfig

EDIT : Added how-to-build in the first post.
[Galaxy S III Android Development] iphdrunk:
Thanks, useful edit :)

I'm using the toolchain from the NDK, editing the Makefile

CROSS_COMPILE ?= /opt/android-ndk-r8/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-

but I wonder if anyone has tried using a 4.7 (e.g. from ubuntu) gcc-4.7-arm-linux-gnueabi 4.7.0-7ubuntu3cross1.64 basic pointers / posts would be appreciated
[Galaxy S III Android Development] harunjo:
when compiling just excute:

make arch=arm m0_00_defconfig

README_Kernel.txt:

1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.3

- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) CROSS_COMPILE= $(android platform directory you download)/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain

$ make arch=arm m0_00_defconfig
$ make

2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko

3. How to Clean
$ make clean

Galaxy S3 boot.img info:

Base address: 0x10000000

Page size: 2048
[Galaxy S III Android Development] manveru0:
hmmm if I made not any mistake the only difference was in block.s:

https://github.com/manveru0/FeaCore_Phoenix_S3/commit/9c04a6f6cf229261f0e4a94cdb31898b58edc929

edit: just by the way, pegasusq together with sio scheduler, spiced with oc to 1600MHz seems to be a nice combo
[Galaxy S III Android Development] ErGo_404:
I tried to build the kernel and the build seems ok (I see no error). I then renamed the zImage into boot.img and tared it to flash it with Odin but the phone doesn't boot anymore (I see the Samsung logo, a black screen and then the phone reboots).

Do I have to make any additionnal change to the kernel before building it ?

Thanks.
[Galaxy S III Android Development] cdesai:
No, zImage is just the kernel for i9300, you need to get a stock boot.img from either the phone or one of the stock ROMs, then unpack it, and replace the kernel in it, and then repack.

Googling "How to repack a boot.img" would help :)
[Galaxy S III Android Development] manveru0:
google for mytools (sripts named unpackbootimg.pl and repackbootimg.pl) and you should get your answers
[Galaxy S III Android Development] ErGo_404:
Oh ok thanks ! I hadn't noticed it did not work as on the I9100.
[Galaxy S III Android Development] Perka:
Hi I compiled ok a week ago and now I get this error

make ARCH=arm CROSS_COMPILE=/usr/local/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-eabi-androideabi-
make: /usr/local/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-eabi-androideabi-gcc: Command not found
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/bin/sh: /usr/local/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-eabi-androideabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2

even that gcc is there O_O

What should I do to get it compiling again?
[Galaxy S III Android Development] Quacktop:
Check if the path: /usr/local/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/ still exists.

Else it maybe because of the path and check that: arm-eabi-androideabi-gcc is in your PATH

See: echo $PATH and see if there is /usr/local/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/
[Galaxy S III Android Development] manveru0:
which gcc version are you using? I've updated my debian sid last night and it seems there are some broken libraries in gcc 4.7. Anyway I can't compile the kernel anymore with gcc 4.7 and arm-eabi-4.3.3. as it always stops while compiling the mali_kernel_core object. The compiler doesn't find arm-eabi-gcc anymore and stops with some messages about missing " in line MALI_PRINT(("Mali device driver %s loaded\n", SVN_REV_STRING));.

So I'd better go back to 4.4
[Galaxy S III Android Development] harunjo:
what is the different beetwen update 1 >> update 2 and update 3?
[Galaxy S III Android Development] FadeFx:
This should be moved to original android development section...

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Android Development] Perka:
Will the new sources be merged?

Thx.
[Galaxy S III Android Development] cdesai:
Well no, as i didn't actually create this kernel, just uploaded the sources from Samsung Opensource release

Surely, update3 shall be on github in a few.
[Galaxy S III Android Development] harunjo:
new kernel source update 4

GT-I9300_ICS_Opensource_Update4.zip

http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-i9300
[Galaxy S III Android Development] cdesai:
Pushed, thanks :)
[Galaxy S III Android Development] cdesai:
For those interested, i've uploaded i9305 sources as well :)

It's the EU Galaxy S3 LTE, with the same processor but more RAM, 2GB.

https://github.com/sgs3/GT-I9305_Kernel

https://github.com/sgs3/GT-I9305_Platform
[Galaxy S III Android Development] harunjo:
FYI

http://xdaforums.com/showpost.php?p=31923487&postcount=6517
[Galaxy S III Android Development] harunjo:
FYI, Its official now

http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-i9300

GT-I9300_JB_Opensource_Update5.zip
[Galaxy S III Android Development] cottino:
GT-I9300_JB_Opensource_Update7.zip now available on OSRC.

Is it jelly bean 4.1.2?
[Galaxy S III Android Development] kevinf28:
yes.

http://www.androidgalaxys.net/news-...gente-samsung-per-galaxy-s3-di-android-4-1-2/

http://www.androidgalaxys.net/appro...punto-esclamativo-rosso-come-nuovo-controllo/

[Edit:]

Also, read README_Platform.txt inside the zip file, now that I have finished downloading it...
[Galaxy S III Android Development] Perka:
Seems this is outdated, I have the update 8 source here https://github.com/perkarom/GT-I9300.git
[HTC Incredible S] XtrKiL:
AOKP for Incredible S

This is a port of the AOKP port of Desire S<--[a bit of inception, but bare with it]

Original thread herehttp://xdaforums.com/showthread.php?t=1616719

(Will try to port from the official devices later on)

Nothing is changed in this build except the addition of the Tiamat kernal(Thanks :D)

Credits: twistedumbrella for his camera drivers

As of now, only the older milestone 5 have been ported, the newer builds would be available soon.

DISCLAIMER: I am not responsible for any bricked devices, unhappy people and anything else.

Please Visit http://aokp.co for features and changelog

Installation:

- Make sure you're running the latest 4Ext or CWM Recovery

- Download the zip from the link

- Copy it to sdcard

- Reboot to recovery

- Backup your current rom

- Wipe data / factory reset

- Choose flash zip from sdcard

- Choose the zip and confirm flashing

Optional:

-Flash Gapps

Bugs:

-Menu Backlights(Working on it, hope someone could help)

-Graphic Problem on first startup

-More to come[Please post any bugs found here]

Downloads:

Milestone 5: http://d-h.st/lzK

Gapps: http://wiki.rootzwiki.com/Google_Apps#Ice_Cream_Sandwich_.28Android_4.x.29
[HTC Incredible S] Surajkumar:
(first one)

will you post some screen shots
[HTC Incredible S] kensheen:
does this support theme engine??
[HTC Incredible S] XtrKiL:
It is the same stock AOKP, so there is no difference in how it looks.
[HTC Incredible S] john9:
I look forward to seeing the screen shots.
[HTC Incredible S] chemist80:
will be keeping an eye on this
[HTC Incredible S] Billabong81:
Exciting day in the Inc S world...AOKP port, news of a 3.0 kernel from HTC...awesome!
[HTC Incredible S] vieose:
Works Camera/Camcorder?
[HTC Incredible S] crunchyHTC:
Don't have anymore thanks to give so thanks for porting this over! Gonna give it a try back home
[HTC Incredible S] XtrKiL:
Camera and video camera both works, thanks to twisted's drivers
[HTC Incredible S] naqn:
Thank you!!!
[EVO 4G Q&A, Help & Troubleshooting] Kuchek:
Hello all,

I can't get my evo to load past startup with any Ice cream sandwich rom. I backed it up so I'm good but I want to know why it won't load them. I cleared all the cache and such so what am I missing. I appreciate any help
[EVO 4G Q&A, Help & Troubleshooting] klharalson:
Which one are you trying to install? Are you flashing anything extra with it?
[EVO 4G Q&A, Help & Troubleshooting] Kuchek:
No. I've tried four different ones and I have to load the nandroid i made on all of them to restore it. When I try to install amon instead of supersonic it says current version is newer. I dont know exactly what I have to do but this is the first time I haven't been able to get it. Argh. Whatcha thinkin?
[EVO 4G Q&A, Help & Troubleshooting] moreno4xl:
Is your Secure Digital Card partitioned? Keep in mind that some of the ICS Roms for the OG have A2SD baked in and if you're not partitioned it may cause for you not to get past the startup. Try this one from MazdaRider and be sure to wipe everything EXCEPT for your SD card and see if it works for you. Now if you do have your SD card partitioned wipe EVERYTHING DOWN and once again with the exception of your SD card and reflash your ICS Rom.
[EVO 4G Q&A, Help & Troubleshooting] CRIME INC.:
What exactly is ur flashing process?
[EVO 4G Q&A, Help & Troubleshooting] cueballri:
just flashed this http://xdaforums.com/showthread.php?t=1481091

!st ICS I've tried and it's working great
[EVO 4G Q&A, Help & Troubleshooting] Kuchek:
Put on root of sd, boot into recovery, wipe cache, wipe dalvich, install zip from sd.
[EVO 4G Q&A, Help & Troubleshooting] CRIME INC.:
U have to wipe more than just ur caches. What recovery are u using?
[EVO 4G Q&A, Help & Troubleshooting] Kuchek:
I simply love you. No homo
[Verizon Droid Incredible 2] sneakysnake16:
I need help rooting a droid incredible 2 with android 2.3.6. Any help at all woukd be awesome thabks :)
[Verizon Droid Incredible 2] sneakysnake16:
2.3.4 sorry bout that
[Verizon Droid Incredible 2] brymaster5000:
Check the hboot version. There are different methods for each one.
[Verizon Droid Incredible 2] sneakysnake16:
i dont know how and the phone has no service yet if thats required its just an expensive game/mp3 player till i activate it
[Verizon Droid Incredible 2] brymaster5000:
Its shown in the bootloader. Hit volume down and power button (while off) to get into it. I suggest you do a little research before proceeding. There are some good threads about rooting the inc2.
[Verizon Droid Incredible 2] sneakysnake16:
Thanks and what kind of research would you suggest. Like what should I search for on google? And does entering bootloader mess anything up or is it like recovery where I can just turn the phone off and on again and it'll be normal?
[Verizon Droid Incredible 2] farcus211:
What model do you have if its 6.01.605.05 thats what I have and the tool downgrade vivow hboot .98 would not work I had to work around that and do it a different way.