• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Curious minds want to know....

pilot03 said:
I wouldn't mind. I'll be happy to help. I'm always Plan B. :laugh::laugh::laugh:

I just haven't seen any Sprint users making roms.
Click to expand...

I'm not a Sprint user but I don't see why I can't just a Sprint base, add my stuff on top and that's it. I'll try to have something for you by tonight.

I have my Sprint base rom, I'll port over my Ecksperia rom I'll pm you when I'm done so you can test before I officially release it. Is that ok with you?
 
There's instructions in Hydra IIRC for building a Sprint version. If not, it's easy: take the build.prop from the Sleipnir Sprint ROM, and that's all you need.
 
kenharkey7 said:
So you are saying all I have to do is change the build.prop
Click to expand...

Swap it out with the one in the Sleipnir Sprint ROM, and you're good to go. As long as the kernel modules match the kernel, which is the other key part to the Sprint versions of ROMs for this phone, then you're all set with that build.prop. Pilot and I spent a few hours coming up with the solution to Sprint-specific versions, along with giantpune's help too. It also turns out that the kernel can be the latest VM one, and as long as the kernel modules match VM in that case, all that's needed is the build.prop (which Pilot provided, and I modified with Leslie's improvements) switch.

TL;DR: Yep.
 
kenharkey7 said:
What modules
Click to expand...

In /system/lib/modules. In short, this means you can have the most up to date kernel for the phone, with modules that match it, and have two different builds (Sprint and VM) on the same kernel, without instability. If your VM version is already working just fine, you have kernel modules that match the kernel. In which case, all you need is the Sleipnir Sprint build.prop.

Which I've just attached to this post. Enjoy.

Also, I should mention that you'll want to edit the following lines:

Code: 
ro.build.id=[B][U]Sleipnir 2.4.0.1[/U][/B]
ro.build.display.id=[B][U]Sleipnir[/U][/B]

The first line is what shows up in System Settings -> About Phone, under "Build Number." The second is just for your reference.
 

Attachments

Artine said:
In /system/lib/modules. In short, this means you can have the most up to date kernel for the phone, with modules that match it, and have two different builds (Sprint and VM) on the same kernel, without instability. If your VM version is already working just fine, you have kernel modules that match the kernel. In which case, all you need is the Sleipnir Sprint build.prop.

Which I've just attached to this post. Enjoy.
Click to expand...

Ok ok, let me get this straight. I take my rom it works which means the kernel matches the module which means all I need is the Sprint build.prop. if for what ever reason it wasn't working then the build.prop plus the modules you provided would get it to work?

Since mine work I just have to update the build.prop ok pilot I'll have a couple more roms for you asap lol
 
kenharkey7 said:
Ok ok, let me get this straight. I take my rom it works which means the kernel matches the module which means all I need is the Sprint build.prop. if for what ever reason it wasn't working then the build.prop plus the modules you provided would get it to work?

Since mine work I just have to update the build.prop ok pilot I'll have a couple more roms for you asap lol
Click to expand...

ROM already works = kernel modules match kernel. Which means that all you need to do is switch the build.prop with the Sprint one I attached to my earlier post. And *~*BAM!*~* correctly-functioning Sprint version.

So... yup. That's all it takes.
 
kenharkey7 said:
Alright, thank you Artine let's rock and roll
Click to expand...

You'll probably also want to use the Sleipnir VM build.prop too. And the installer and the installer binary as well - though for the installer, you'll of course want to modify the creators list, the ROM name, and the permissions-lines for the init.d scripts if you've removed some or all of them. Also the kernel name. The only reason I suggest using those is because they do everything for the end-user, which makes installation basically painless as, unless they're swapping ROMs, they don't have to do anything except flash the ROM.

...There's a reason Hydra exists :D

Anyway, I've attached the VM build.prop and the META-INF folder to this post just in case. Enjoy.
 

Attachments

Alright thanks, uploading now

Might have to wait, it's taking forever, I've been using for like 30 min and have only gotten 40mb done

Yeah this ain't working, I'm going to need so I can hit the freeway tomorrow and get my phone turned back on. I'll upload them Sunday or Monday at the latest.
 
You must log in or register to reply here.
Back
Top Bottom