Related
I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
i'd really like to help you, but i'm not able... this morning i studied some tutorial such as http://pdk.android.com http://android.git.kernel.org http://d.android.com, but i'm new with linux and i can't understand anything... however i was asking myself the same questions...
Quick catch-up:
Dexter_nlb said:
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
Click to expand...
Click to collapse
Check, Possible: http://forum.xda-developers.com/showthread.php?t=767431
Dexter_nlb said:
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
Click to expand...
Click to collapse
Well, IDK if this easy, but manageable. Both odin (easier) and update.zip (more stable) options available.
Dexter_nlb said:
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
You could contact people at #project-voodoo to get more detailed information.
Best of luck.
Dexter_nlb said:
I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
thanks , very usefull.. so the .md5 extension on odin files are related to?
anyways i have made zImage for other platforms so changing the ramfs should be straight forward...
Finally a person who knows their stuff is attempting at a sense ui port.
Hope you succeed
I really hope you succeed - I have time but no knowledge - if you need help pm me
DesireHD rom? YES PLEASE!!!
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
Same here.
MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
thanks, im primarily persuing this as a personal challenge, but of course if ppl likes my work its great.
one note is, as written earlier, more experienced guys will be required to finish the bluetooth adaption, its alot more complex than the remaining parts.
and im told even on older htc phones it was hard to port drivers for bt.
my 2.1 sense mod on milestone was ok, except milestone only had 256MB, which resulted in many reloads of senseui.. here i think we can stabilize, even with a modified kernel to add swap if needed (if the 512MB utilization becomes a problem)
I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
xan said:
You could contact people at #project-voodoo to get more detailed information.
Click to expand...
Click to collapse
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.
jjwa said:
I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=8254744#post8254744
A thread for bounty to devs porting for SGS succeed
-Fraction
Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
Wasn't the JPM source leaked for a little while about a week back? Is that the source code to which you're referring?
Edit: Sorry forgot to check the post date, so at the time you posted that, the source code had not been leaked
Alright, here is the z4mod app at long last! This release needs a lot of testing for different devices still, so make sure you check the compatibility table below unless you know how to use Odin to flash back your original kernel. Thanks for helping to test this!
[size=+1]This is still in beta! If you know how to flash with Odin, please help test so all bugs can be found and fixed to allow for wider release![/size]
What is this?
Another lagfix. This one is a bit different from existing lagfixes though:
- Differences from OCLF: Uses native EXT/JFS instead of loopback mounts. Loopback mounts in linux can be a bit flakey at times, especially when they're on RFS. So this is generally better.
- Differences from lagfix kernels such as voodoo or sztupy's: These types of lagfixes are kernels compiled from GPL sources for specific devices. This can cause a number of issues, such as losing out on bug fixes in later Samsung kernels released after the GPL code, or differences in devices such as the I9000B, etc. z4mod also has (imo) a nicer design, in that it uses /etc/fstab for filesystem mounting, as well as keeping the convert scripts outside the kernel. It should also work across ALL (or many?) Samsung devices without changes!
How do I use this?
Install the app. Click the buttons. It should all just work. Let me know of any issues or complications! This is still in testing!
Device/firmware compatibility table
Samsung Galaxy S Devices
Stock Samsung
I9000 Stock Samsung 2.2 : WORKING
I9000 Stock Samsung 2.1 : NOT TESTED
I9000B Stock Samsung 2.2 : NOT TESTED
I9000B Stock Samsung 2.1 : NOT TESTED
I9000T Stock Samsung 2.2 : NOT TESTED
I9000T Stock Samsung 2.1 : NOT TESTED
I9000M Stock Samsung 2.2 : NOT TESTED
I9000M Stock Samsung 2.1 : NOT TESTED
Captivate Stock Samsung 2.2 : NOT TESTED
Captivate Stock Samsung 2.1 : NOT TESTED
Vibrant Stock Samsung 2.2 : NOT TESTED
Vibrant Stock Samsung 2.1 : NOT TESTED
Epic Stock Samsung 2.2 : NOT TESTED
Epic Stock Samsung 2.1 : NOT TESTED
Fascinate Stock Samsung 2.2 : NOT TESTED
Fascinate Stock Samsung 2.1 : NOT TESTED
Stock Japanese Docomo Galaxy S (SC-02B) : WORKING
Stock SHW-M110S (Korean SGS) : WORKING
Custom Firmwares
Any custom firmware that uses a stock kernel works as the stock kernel in the table above
Custom kernels that make use of changed filesystems or boot up scripts are unlikely to work at this time. Emphasis is on stock kernels currently.
Custom Kernels
BLN (backlight notification) custom kernel for GT-I9000 works
Voodoo kernels do not work
Kernels with heavily modified boot procedures such as rooted Vibrant kernels do not work
CFRoot kernel does not work.
DamianGto's kernels work
Other Samsung Devices
NOT TESTED
More info on z4mod
http://www.sgscompilebox.dreamhosters.com/about.html
Source Code
http://github.com/z4/z4mod
V0.9.2 Changelog
Fix for EXT2->RFS Conversion. Please update to this app version before using this conversion.
Other small bug fixes.
Conversion page now has scrolling text informing you of progress and any errors.
V0.9.3 Changelog
Critical: Upload kernel now passes binary MIME type to prevent corrupt kernels
Fixes for text in conversion screen.
Fix for 'mmcblk0p2' always being chosen for /data, even on devices that use 'mmcblk0p1'
Bug fixes for UI
Donations
Donate link is available at https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
quick question I need to disable vodoo before using this right ?
anyways im running vibrant rom ( axura ) on my rogers captivate ( i896 )
testing now
DAGr8 said:
quick question I need to disable vodoo before using this right ?
anyways im running vibrant rom ( axura ) on my rogers captivate ( i896 )
testing now
Click to expand...
Click to collapse
This probably won't work if you have a Voodoo kernel installed. The Voodoo kernel is unlikely to be patchable, since it's not native RFS, and does not use /etc/fstab.
RyanZA said:
- Differences from OCLF: Uses native EXT/JFS instead of loopback mounts. Loopback mounts in linux can be a bit flakey at times, especially when they're on RFS. So this is generally better.
Click to expand...
Click to collapse
I have a Vibrant and this is why I have avoided using the OCLF in the past. Many ROMs don't even need a lag fix. However, with that issue gone, I'll at least try it and report back on it.
RyanZA said:
This probably won't work if you have a Voodoo kernel installed. The Voodoo kernel is unlikely to be patchable, since it's not native RFS, and does not use /etc/fstab.
Click to expand...
Click to collapse
hey I forgot to mention I had flashed setiron's reoriented kernel on it , so yea result is could not patch kernel ..
I guess i have more test to do. But right now Im stuck with 0.12 problem.
I did test it
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.
Instead of restarting the phone.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
can i use this with speedmod kernel?
DamianGto said:
I guess i have more test to do. But right now Im stuck with 0.12 problem.
I did test it
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.
Instead of restarting the phone.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Click to expand...
Click to collapse
It checks for a /z4mod/z4version file to determine if it's been patched already. If you are using an earlier patched z4mod kernel that doesn't have that file, then it won't work right. If you start with a stock samsung kernel then it should work fine.
specialex said:
can i use this with speedmod kernel?
Click to expand...
Click to collapse
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels. At present, any custom kernel that does not change the initramfs (in particular, the /init binary and init.rc mount options) too heavily should work fine.
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Whitehawkx said:
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Click to expand...
Click to collapse
Thanks for testing!
Could you upload the z4mod.log file in your sdcard? /sdcard/z4mod.log
Okay. Then its just because the bug in the latest z4build then.
That's why it tried to apply the change.
Z4ziggy is working on that problem
Hope he will solve that soon. Right know Im on stock filsystem with my new kernel. Lol.
Kind of fun to compare them.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
RyanZA said:
Thanks for testing!
Could you upload the z4mod.log file in your sdcard? /sdcard/z4mod.log
Click to expand...
Click to collapse
I just looked and there isn't one there.
Whitehawkx said:
I just looked and there isn't one there.
Click to expand...
Click to collapse
Hah... Okay that's pretty strange. What method did you use to root btw? Perhaps it's a busybox conflict of some type.
RyanZA said:
Hah... Okay that's pretty strange. What method did you use to root btw? Perhaps it's a busybox conflict of some type.
Click to expand...
Click to collapse
Hmmm the rom/kernel I flashed came pre-rooted. Now that I think about it, I was using the stock JK2 kernel but it has a custom init script to allow the use custom boot animations. Could this be effecting the conversion process by chance? Anytime I manually root though I use OCLF from the market.
Hey RyanZA,
I see that there is a list of devices in the first post but I dont see a listing for the GT-i9000M specifically. I see the i9000, i9000B and i9000T but no "M". Is there a reason for this? Is the i9000M considered in the generic i9000 family? Also...
A bit off topic here but I am curious to know if I root using z4root and need to unroot for warranty purposes, will it remove ALL traces that it had been rooted including Busybox and Superuser app?
I know that Samsung has issued a memo stating that if a phone shows up rooted to a service center that the warranty will be voided and Id really like to try this rooting method.
Also, as you are probably aware, the i9000M here in Canada has issues with internal sd card failures and I am curious to know if just rooting with z4root will possibly kill my internal sd?
Thanks...
Flashed my Epic using the DK05 2.2 Rom, ran Z4mod, get error: zimage test failed when i try and patch the kernal.
RyanZA said:
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels.
Click to expand...
Click to collapse
should probably put this on OP , less hassle probably .
if nobody else test it on the cappy ill flash to stock just to test ..
@DamianGto:
The problem is with CWM recovery - it's busybox-tar is not working properly.
I think I found a way to overcome this and I updated the git, so now CWM option should be working again.
Whitehawkx said:
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Click to expand...
Click to collapse
If you could paste the contents of the following 2 files we might learn more:
/z4mod/log/init
/sdcard/z4mod.log
Just installed on my device (GT-I9000 with official JPA just released today in Thailand)
It worked fine. I got 1730 from quadrant.
Thanks for your excellent job. ^__^
Change of plans, hopefully with the help of anyone who is willing I'd like to compile an aosp build for the Sprint GS2 from source instead of trying to hack a port together, as suggested in this thread and other places, it just feels like it will be a lot more of a fruitful experience for all involved and have a better end result.
(a big thank you to everyone who so far have been super encouraging and friendly with noob questions, it's much appreciated!, I hope that if you wanted to help with the port you'll help with this build as well!)
This is a WIP. Starting out with Samsung's open source platform and kernel instructions on how to build from aosp and I'll take it from there.
I've setup some repos to get this all started in one place:
Samsung SPH-D710 platform source - https://github.com/thefredelement/sph-d710_platform_source
Samsung SPH-D710 kernel source - https://github.com/thefredelement/sph-d710_kernel_source
Team Hacksburg kernel source - https://github.com/thefredelement/android_kernel_samsung_c1spr
Stock kernel initramfs (thanks buddy323!) - https://github.com/thefredelement/stock-initramfs-eg30-epic-4g-touch
https://github.com/thefredelement/Samsung-Galaxy-S2-Sprint-Epic-4G-Touch-AOSP-Build - will be where the build will live after I push over Samsung's platform make and upload it!
--- old stuff that will make your head spin ---
If anyone wants to continue working on this, feel free.
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: you don't want this...
Reserved for changelog, when hopefully it gets that far
Awesome to see a project like this, good luck in the port!
Sent from my SPH-D710 using XDA App
O_OMG <3 :-!
Sent from my SPH-D710 using xda premium
Good luck! Looking forward to this.
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
deano0714 said:
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This boots using the stock Sprint/Samsung kernel.
xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
What kernel are you using?
thefredelement said:
What kernel are you using?
Click to expand...
Click to collapse
im using stock
xploPR said:
im using stock
Click to expand...
Click to collapse
Did you wipe all of your user data before installation?
Do you get to the boot animation?
Constructive criticism would be for me to point out you must not have read the OP because it clearly said nothing works because we don't have a aosp kernel yet but you are just rude.
Sent from my SPH-D710 using xda premium
xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
ehusidic said:
The title clearly states its not ready or stable so chill out while the devs do what they do
Click to expand...
Click to collapse
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic ore infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
Sorry for the horrid insults I aimed at the complaining member. Too uncouth.
Sent from my SPH-D710 using xda premium
Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. I agree this is a much better idea.
jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
i like that mandatory vacations with paid vacations to hawaiii, can xda hook it up or what?
thefredelement , good luck. glad to see new devs... i hope to be there one day but i'm way off...
Thanks!
thefredelement said:
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: http://www.multiupload.com/OF1HXSSOCJ
Click to expand...
Click to collapse
hit me up i can get ur rom working with wifi/3g/4g/whatever. zedomax at gmail dot com
Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
I recall rumor about samsung sending a GS2 to Cyanogen so that he could "get to work". Guess that never materialized - or they gave him something else to do once they hired him...
Sent from my SPH-D710 using xda premium
it was one of the cyanogen devs that got a galaxy2 & they have nightlies for the gs2 now.... It should not be hard to get it ported over
....
One of the devs on teamhacksung was asking for people with the phone to help with it ..he ask on twitter like the 16th so they are probably working on it....
Sent from my SPH-D710 using xda premium
Hello,
Some users requested this so I put it together as well as a template for devs to include with their kernels.
i927_rooted_initd_boot.tar.md5
Flash this via ODIN as usual.
The initial ramdisk can be found here on my github: android_samsung_i927_initrd
Feel free to use/modify this devs, just give credit.
Credit to: the provider of the insecure stripped down kernel
Da_G for his script in the ramdisk
Enjoy.
This kernel works great, provides root on stock ROM as expected and scripts run. Good work.
It may be useful...
For the i927_rooted_initd_boot.tar.md5 file:
CRC32: 7031B711
MD5: FED634B455931E667FFE31BEC3857A66
SHA-1: F4B8AEBF3C6C531C4C24CDBB425DDAAB530C6350
I do not have root after flashing this kernel.
Edit: I finally got it working by reflashing and rebooting.
utkanos said:
Hello,
Some users requested this so I put it together as well as a template for devs to include with their kernels.
i927_rooted_initd_boot.tar.md5
Flash this via ODIN as usual.
The initial ramdisk can be found here on my github: android_samsung_i927_initrd
Feel free to use/modify this devs, just give credit.
Credit to: the provider of the insecure stripped down kernel
Da_G for his script in the ramdisk
Enjoy.
Click to expand...
Click to collapse
If you don't mind, how did you go about getting init.d to work? I am working on a similar kernel but have not yet been able to get my scripts to run.
Wetzel402 said:
If you don't mind, how did you go about getting init.d to work? I am working on a similar kernel but have not yet been able to get my scripts to run.
Click to expand...
Click to collapse
It's in the source I posted on my github.
https://github.com/utkanos/android_samsung_i927_initrd/blob/master/init.superuser.sh
Thanks! I actually looked through your git earlier today but must have read over that line. Looks very easy to get going on a Samsung device. I tried that exact line on my device but it didn't work unfortunately. I think I may have a work around but haven't tested it yet.
I can't seem to get rooted with this. I've got it stock besides have flashed CWM via Odin.
I should just be able to get root by flashing a custom ROM and kernel through CWM, right? This device is a little different than my last one.
this is for GB only if you are using ICS then install likekernel or other root ICS based kernel.
Am on GB, but thanks anyways. I got it by other methods.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** If one of this builds bricks your phone, kills your cat or causes
** a thermonuclear war, don't point at us. We'll laugh at you.
** You decided to make this modifications to your Phone.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on experimental builds is the leading
** cause of male impotence.
Hey all, you may remember me from back on the cdma hero. Well, I decided to pick up dev'ing again, and have been pushing source up to my github for working code for ice cream sandwich on our Epic 4G touches. It's my pleasure to say it's mostly functional, with just a few bugs remaining, of which i'll post at the end of my thread here. If I didn't list some functionality you're looking for in the bugs list, either it already works, or i forgot about it. Chances are high that it already works, though . Once I get nightlies to run, i'll make another thread for that.
Follow me on twitter for updates, and testing builds Please, follow the instructions listed below for flashing, to prevent any damage to your phone
Or, for the lazy, click HERE which is also mirrored for a download, which will also be mirrored HERE. note that my laziness will probably hinder me from updating the OP frequently to keep up with my updates i post on twitter.
Don't forget to flash GAPPS if you're coming from a non-CM-based ROM
Kernel: FC07
Recovery: CWM
What works
- GPS
- Camera
- SMS/MMS
- YouTube
- External SD mounted to /emmc
- Pretty much everything else
Bugs
- apps2sd doesn't work for EXTERNAL SD
- Video recording doesn't decode the files properly to mp4, so the output is unusable
- Music occasionally FCs. Feel free to post some logcats (pastebin'd only) if this happens to you
Installation Instructions
*WARNING* There have been a number of people over the past 6 weeks experiencing HARD BRICKS of their E4GT when flashing ICS from ROGUE 1.2.1 on FB15 AND NEWER KERNELS. Please see THIS THREAD for more information. As such, I am STRONGLY recommending that ALL FLASHING of this ROM be done ONLY from the STOCK CWM EL26 RECOVERY (download) EDIT: As an update to this, we're fairly certain this issue is sporadically occurring whenever a partition is being formatted by the recovery. this led us to believe that the problem lies in the kernel samsung has been putting out in the leaks. Please, for your sake, use, a recovery with a gingerbread kernel when flashing this rom, or doing nandroids, or even doing data wipes.
First install of CM9
BACKUP your existing ROM
Did you backup your existing ROM? No? BACK IT UP, GENIUS
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED (*note* backup/restore seems okay, it's only the actual zip/kernel flash that risks bricking. See THIS THREAD for more information.)
Reboot to recovery (power+vol-up)
WIPE DATA
Flash CM9
Flash GAPPS
Reboot to system
After rebooting, if you go BACK to recovery, you'll be on Rogue 1.2.2
Upgrading CM9
This build will upgrade from any CyanogenMod rom just fine. Just, be sure you're using the EL26-CWM recovery when flashing this rom. read my Edit up above for further details.
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED (*note* backup/restore seems okay, it's only the actual zip/kernel flash that risks bricking. See THIS THREAD for more information.)
Reboot to recovery (power+vol-up)
Flash CM9
The newest update changes the way backuptools work for the install script. it reads custom user scripts in /system/add.d. Since the first rom i put out didn't have that, you'll need to reflash google apps after flashing cyanogenmod. after flashing this latest update, subsequent updates won't need you to reflash Google Apps
Wipe cache
Reboot to system
Enjoy!
EDIT: I updated the OP with the link to the rom. This is using some better coding for mms and sms receiving, and the LOS bug was fixed by the epiccm group, and pushed to mainstream cyanogenmod, so we we're benefiting from this. also, added in were sprint visual voicemail and sprint updates. There's surely other stuff i'm missing to add to what's working and what's not . Note that Cyanogenmod doesn't normally use stock kernel, rather it uses cm-kernel. the issue is that we don't have source for the kernel in ics, so we can't merge our board-files, etc into it just yet. But this isn't an issue, as far as functionality. It's just not the full CyanogenMod experience .
EDIT2: I had jerdog change the thread title to unofficial, because we aren't really in CM just yet. It's more because of my discrepancy, with not wanting the device tree to be pulled, because i'm still doing work on it.
EDIT3: Guys, don't be flashing any themes over this rom, reason being because i changed the framework files a bit in my source, and it hasn't been pulled into mainstream cyanogenmod yet.
Wow, I ran your stuff on my hero. So nice to have you here.
Sick great to have you here
Wow thank you so much I've heard great things about your work!
Sent from my SPH-D710 using xda premium
Woot woot I remember the old hero days...
Sent from my GSII.
Wow dude, my hero memories are rushing back to me! Great to see you here!
Sent from my SPH-D710 using xda premium
Nice, glad to have you here!
Man your about to be a real "hero", darchstar to the rescue, glad to have you here man. Ill be installing this since it comes with recovery, very small chance of a brick now,,, THANKS again.
Sent from a phone with kNOw CIQ ...
Good stuff buddy!
Sent from my SPH-D710 using xda premium
damn epic touch scene getting better and better with all these ics
**** yea glad to see you again
Sent from my SPH-D710 using xda premium
A quick note:
As with all CM9 ROMs, we have been seeing some RARE bricks (hard brick, unbootable, no download mode, blue LED of death) when flashing from FB?? and newer Rogue kernels. These are RARE but they DO happen. See this thread for more info: http://forum.xda-developers.com/showthread.php?t=1525495
I would recommend doing ALL of your flashing from EL26 StockCWM (if you can still find it).
You have been warned.
darchstar said:
Bugs
- Sporadic instances where 3g doesn't pick up coverage again, after coming out of low signal areas.
Click to expand...
Click to collapse
Have to keep waiting.
neatchee said:
A quick note:
As with all CM9 ROMs, we have been seeing some RARE bricks (hard brick, unbootable, no download mode, blue LED of death) when flashing from FB?? and newer Rogue kernels. These are RARE but they DO happen. See this thread for more info: http://forum.xda-developers.com/showthread.php?t=1525495
I would recommend doing ALL of your flashing from EL26 StockCWM (if you can still find it).
You have been warned.
Click to expand...
Click to collapse
thats some excellent advice
Oh man, darchstar's in? sh*t just got real. I wish I could just jump forward a few weeks.. Good to see you here!
EDIT: Darchstar, let me know if you want me to take this down, but I'm gonna put a link here to make it a bit easier: http://t.co/bn3AW0bD
EDIT 2: I evidently didn't make it big enough...LINK IS IN THIS POST [and Darchstar's twitter]UNTIL FURTHER NOTICE
I just put it here to save from the "where's the link" posts..
P.S. Downloading and I'm tweaking cause I'm so excited to flash this.
just flashed from fb27 with no issues but dont do it if your scurrrrrrred
Where's the link.
Sent from my SPH-D710 using Tapatalk
Will of fire said:
Where's the link.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
post 15 has the link
both links from your twitter and the one provided Above are not working.
Sent from my SPH-D710 using xda premium
Mms is sending but not able to download. Charging light works. Woohoo. Thanks for the release.
Sent from my SPH-D710 using Tapatalk