Database Develop

[kernel][testing]Unhelpful Kernel (from Captivate)

I'm trying to get the kernel I've been working on for Captivate working on Vibrant. This poses a bit of a problem, because while I have access to a Vibrant kernel and initramfs, and a known-working config for Vibrant, I lack access to a phone.
I've forked a test branch based on what I have so far. I would appreciate pretty much any of the following:
a volunteer to build this kernel or test a binary
a volunteer to help with Vibrant development
any other Vibrant-specific details that don't apply to Captivate or to SGS in general
I have already built a binary, but it is mostly untested. I want to make it very clear that this is a testing kernel. It should work, it should not break anything... but it might not boot, it might wipe data, I haven't heard of it happening to anybody yet but it's certainly not impossible that it might damage hardware. These are unlikely, except for not working, but are all possible outcomes of trying this kernel. If you want to test this, read the OP in the thread for the Captivate version, have backups of your data ready, preferably duplicated to a hard drive or an SD card that is removed before testing. Have Odin3 and a stock Vibrant kernel on hand, and have ClockworkMod recovery installed.
If it hangs starting up, wait a bit, then pull the battery and start in recovery without trying to start up normally. Then, start clockworkmod, mount /system, and use adb to pull /system/user.log - this should contain a log of what happened when the user init scripts ran, and may provide clues as to what went wrong. You can make sure it doesn't include anything you don't want to reveal, and just PM it to me or join #sgs_dev on freenode and talk to me or some other developers there - perhaps a dev with a Vibrant will have a better idea where to start.
In the long term, I would not mind somebody forking the github repository to work on any Vibrant-specific issues. I can then try to pull changes from a fork and do builds for both phones, if somebody doesn't want to do the Vibrant builds themselves.
Good luck, and thank you.

if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk

ill be more than happy to test the binary

I too will be more than happy to give any sort of help possible. Should this be a start from a stock kernel and build deal, ie stock kernel stock rom just rooted with clockwork?
Sent from my Vibrant using tapatalk pro

If you're using a lagfix with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
EDIT: "lagfix", thx swype.

Unhelpful said:
If you're using a ladies with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm about to build from your source i just forked to see whats diff then mine. They look though to be about the same except for nilFS
I will probably fork and maintain a vibrant tree with ivan who also has a Vibrant. That way we can get the best of both worlds. And being that we are in the same IRC we pretty much have identical mods to our kernels.
So most likely any changes you make to your captivate Kernel will end up in the vibrant branch as well and I also have the device to test with
See ya in IRC

anomalous3 said:
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
haha if ur talking about the linux distro i know what u mean

Excellent news! I have some things in my tree I think you could use here, too, but it's much easier to have a developer with a Vibrant who can build them and test immediately.

What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk

rei165 said:
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The stock captivate kernel doesn't have any "advantages" and wouldn't really work. Unhelpful, however, has added nilfs support to the captivate kernel as well as some other tweaks, and has now made these changes available to the Vibrant community. As I understand it, NILFS mounts, reads, writes, and unmounts faster on our devices than any of the other filesystems he tested, so there's hope for a permanent lagfix.

I tried this kernel, it does boot but my existing lagfix scripts don't work with it, so I lose all my data. No big deal to fix from recovery, just revert to stock before messing with it if you want to test it. As mentioned, no real advantage either way, but it's nice to have options.
If there is interest, I'll fix my lagfix scripts to run on this kernel. Reverting back to JAC OVv4 works without hassle via clockwork.

Droid x Aosp Boot!!!!

This was the tweet fromCvpcs!!! (We haz a booting "true" AOSP system with 0 blur! http://www.youtube.com/watch?v=PPqfIRZP7Mc Still very buggy but I'm working on it)
Sent from my DROIDX using XDA App

booyah! let get er done!

Sound like good news!
Still, could anybody explain what AOSP boot means? Will this enable us to boot a custom kernel on the x?

I have no idea what this means except 100% no blur sounds awesome!

AOSP essentially means it was built completely from source. Not built based on Moto's own build with their custom framework (blur) crap. It is a true complete Vanilla rom.

Android Open Source Project
http://source.android.com/

So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App

If they got an aosp to run they should be able to modify the kernel no? Thought that was the while point of the exploit nenolod is working on.
Sent from my DROIDX using Tapatalk

this is too awesome.

Joe92T said:
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.

vonfeldt7 said:
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
Click to expand...
Click to collapse
This AOSP has actually been running for a while now. Its being developed by cvpcs, the same guy who's been developing the Sapphire roms for Droid. I don't know if he's using the recent exploit that has made the rumor-mill lately. He claims its a true AOSP boot, which implies a custom kernel compiled from source. However, for all we know he could still be using the Moto 2.2 kernel, but replaced everything else in user space with fresh, compiled code.
Either way, its interesting. Despite Motorola's best attempts, it looks like the Droid X (and Droid 2 by implication) will soon be free of its eFuse prison, allowing us users the choice of what to run on this device.

We won't be getting rid of eFuse, as it's hard coded into the silicon itself in NVRAM, as I understand it. Its just that folks are working on getting the keys to the prison .

hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.

sniffle said:
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
Click to expand...
Click to collapse
Thank you guys for your hard work, I am sure that most of the community is as excited as I am to see your work make it to the X. I love the boot ani from the video, and even though this is my first android phone the things Ive read about your teams previous releases has me EXCITED for this to hit.

appreciate your update and clarification, sniffle!

OMG, aosp 2.2 for my droidx would be awesome. Nice to set someone working on it, props and kudoes.
Sent from my PC36100 using XDA App

i hear this is almost 100% working!

LT1UltraZ said:
i hear this is almost 100% working!
Click to expand...
Click to collapse
Heard the same this morning. Very excited!

dogswind said:
Heard the same this morning. Very excited!
Click to expand...
Click to collapse
Would love a source on this info.

Almost 100% is a bit too strong of a descriptor, there are still some major bugs like rebooting on sleep(hitting the power button to turn the screen off) and a few others on top of that. With our next sapphire and Ruby release we will be making the latest build publicly available for other development to help figure out a fix for these problems.

[Project] 2ndboot for the Atrix (custom kernels)

So a thought that has occurred to me since I got this phone is one of haret.exe on winmo phones. basically boot up past the bootloader and kernel(that are locked) then using either 2ndboot or kexec dump out of that kernel and launch out own kernel/filesystem
Sadly in looking around 2ndboot seems to require the phones kernel source(which we don't have, unless i'm totally wrong)
kexec on the other hand seems to be a much better way to accomplish it. Again this is mostly useless without a kernel BUT we could take our current kernel to use as a test bed for if (as is required) the release the kernel source.
Thoughts? anyone wanna join with me on trying to get this running and tested?

art3mis-nyc said:
So a thought that has occurred to me since I got this phone is one of haret.exe on winmo phones. basically boot up past the bootloader and kernel(that are locked) then using either 2ndboot or kexec dump out of that kernel and launch out own kernel/filesystem
Sadly in looking around 2ndboot seems to require the phones kernel source(which we don't have, unless i'm totally wrong)
kexec on the other hand seems to be a much better way to accomplish it. Again this is mostly useless without a kernel BUT we could take our current kernel to use as a test bed for if (as is required) the release the kernel source.
Thoughts? anyone wanna join with me on trying to get this running and tested?
Click to expand...
Click to collapse
I believe this was discussed already in the thread about cracking the bootloader, however, if you do manage to get this running I will gladly beta a new kernel as long as there is an SBF file available at the time to allow flashing back to stock.
Cheers

Ill gladly beta as well. So long as we have a method for recovery.
Sent from my MB860 using XDA App

Anybody willing to guide a newbie?

Hi everyone!
I'm looking to become a future dev of the Samsung Captivate Glide, but as we're awaiting the official ICS from AT&T the forum right now is pretty dead. We have a project going but nobody to guide us, and we wish to compile CM9 or AOSP ICS. Would anyone take me in and teach me the basics of ROMing? I would greatly appreciate it! I have a Mac and Windows, I'm not sure if Linux is required :|
~Aquethys

the rom is the least of the worries to get dev going on your phone, getting the kernel going is the hard part. does your phone have the source code released?

I don't believe so, people in our ics port thread are saying we don't have a working ics kernel. We do have a gingerbread kernel though... :/
How would I start?
Sent from my SAMSUNG-SGH-I927R using xda premium

well you take parts from the GB kernel and apply it to parts from the AOSP kernel, and troubleshoot until it boots. then you troubleshoot all the other issues, there will be issues, then you can start doing fancy things like add cwm. then tweak the kernel....
start reading on kernels, ramdisk, rils, libs, and drivers, linux, compiling, AOSP, github repositories.
you might be ready to take on this task in 6 months.... minimum
dont take that as snooty, ive been on here over a year, and know jack squat about half the things i just told you to study. though i have no desire to build kernels myself. there is lots of great info scattered all over xda. but you will need an experienced dev, to port ICS. you need to know basic kernel modification stuff before trying to do something as big as porting a new android version from out your but.
automated compiling isnt as automated as it sounds.

Alright. What programs will I need to begin with? Hopefully an experienced dev can guide me, I'm not too good @ following guides/tutorials but I'll try my best!
Sent from my SAMSUNG-SGH-I927R using xda premium
EDIT: Made a dropbox account, hopefully you could guide me through the basics?

So, is this the source code for SGH-I927 you were talking about? I downloaded it, what do I do with it? Is it different for ICS and GB?

Porting Roms for Samsung Exhilarate

I read the touchpad shares the same exact chip set as the exhilarate. Will I be able to port say, cm9? I'm new to development and porting so any details and help would be appreciated and there is currently no dedicated form for this phone, yet
Sent from my MB860 using Tapatalk 2

It sounds like you intend to port a Touchpad ROM to this phone? I wouldn't suggest doing that, as there are many phones that have the same chipset as the Touchpad, such as the T989. However, the thing with porting is that you are always using the Kernel from YOUR device, not the one you are porting from. This limitation means that you can only port from an existing level of development. Take for example, if you are currently on 2.3.3, you will be limited to porting CM7 ROM's.
I would not suggest flashing a Kernel from another device on your phone unless you are 100% sure it will work. Even with the same chipset, I think some things in the Kernel are executed differently in different devices.
Let me use the Touchpad as an example. I consider it a great device for playing around with because you have Moboot as a protective layer to ensure you do not brick anything. You can flash whatever Kernel you like and it should not brick, but will certainly not work! I flashed a Kernel from my T989 on to it, and all you get is a black screen when trying to boot. Same chipset, different Kernel execution... see my point?
If you were to do that with your phone you would mess up your boot partition and get a hard brick!
Edit: I seen that you found the Forum in Android General about pushing CWM to the phone, that's a good stepping stone!
If you wanted to be brave, I would try pushing CWM from the Blaze 4G, and then Flash one of those ROM's with your Kernel and Radio.

Very informative thanks man!
Sent from my MB860 using Tapatalk 2