[TOOL] Flash_Patch v1 "The easiest Way to Port a ROM" UPDATED 10/21 With AOSP Version
Credits: IncDoes, myself.
This is the first stage of flash-patch development, this will be used to get the ports done on the Evo/Nexus over to the Inc in an easy suitable way that fits us all. No more rebuilding or packing a whole new zip
I will be updating the patch as we get more fixes.
What the patch does:
- flashes Inc system files replacing the Evo/Nexus system files
- flashes Inc boot.img replacing Evo/Nexus boot.img
THIS PaTCH NOW SUPPORTS PORTING OF N1 ROMS, TOO!!!
Download:
(SENSE): http://bit.ly/asxO8s
(VANILLA): http://bit.ly/aC9bSr
(ENOMTHER'S THENEXUSONE): http://bit.ly/ajrWsn
How to install:
- download flash-patch (posted above)
- download an Evo/Nexus ROM
- full wipe required
- flash the Evo/Nexus ROM but DO NOT REBOOT after install
- flash the patch over the Evo ROM
- now reboot
CHANGELOG:
v1 Sense/Vanilla/Enom- Initial Release
v1.5 Sense- Install Script deletes kernel modules before reboot
this patch was designed to work on any rom from the nexus or evo>>>any other rom will be unsupported!
cool idea guys
thank ID for the idea
this is sick.
going to try this tonight
chrisloveskaos said:
this is sick.
going to try this tonight
Click to expand...
Click to collapse
Right now, it was only tested on EVO Sense ROMs, just to let you know...i should have a working version for Vanilla roms later or tomorrow.
Yeah, I remember ID talking about this yesterday. Cool idea. I guess, but why would you want a evo sense rom? Anything that's been done for the ego has been done for the dinc, no?
jdkoreclipse said:
Right now, it was only tested on EVO Sense ROMs, just to let you know...i should have a working version for Vanilla roms later or tomorrow.
Click to expand...
Click to collapse
i want to try virus's work here its sense so should be a go..
and one other thing ..what about themes? will his themes work ?
chrisloveskaos said:
i want to try virus's work here its sense so should be a go..
and one other thing ..what about themes? will his themes work ?
Click to expand...
Click to collapse
Themes would be able to work, yes.
NickkxNekro said:
Yeah, I remember ID talking about this yesterday. Cool idea. I guess, but why would you want a evo sense rom? Anything that's been done for the ego has been done for the dinc, no?
Click to expand...
Click to collapse
They have their own roms (ava froyo, virusrom, nosenseevo just to name a few)
I am also working on one that will port from the nexus
rom kitchen does this, but does it even better. using this may cause issues if your replacing the whole boot image. if you want to make it better, include a kernel and use koushs any kernel flasher. some roms have rom specific data in the ramdisk that if you remove it, can cause issues.
es0tericcha0s said:
rom kitchen does this, but does it even better. using this may cause issues if your replacing the whole boot image. if you want to make it better, include a kernel and use koushs any kernel flasher. some roms have rom specific data in the ramdisk that if you remove it, can cause issues.
Click to expand...
Click to collapse
This is a WIP...i will concider what you said, and will add some elements from the kitchen.
the AOSP porting tool looking good as well!
Glad to see your working hard to contribute real things to community. Keep it up man.
This could be cool. I'm not a dev though.
Is this what ported CM6 Night97 Into Blackhawkmod?
es0tericcha0s said:
rom kitchen does this, but does it even better. using this may cause issues if your replacing the whole boot image. if you want to make it better, include a kernel and use koushs any kernel flasher. some roms have rom specific data in the ramdisk that if you remove it, can cause issues.
Click to expand...
Click to collapse
ROM kitchen is a little different, my way makes corrections and fixes, no major issues will be caused using my method.
ToyTank said:
This could be cool. I'm not a dev though.
Is this what ported CM6 Night97 Into Blackhawkmod?
Click to expand...
Click to collapse
No that was before I knew to do this method.
Sent from my ADR6300 using XDA App
The Nexus porting tool sounds pretty sweet. Good work and thanks
Rahshaka said:
The Nexus porting tool sounds pretty sweet. Good work and thanks
Click to expand...
Click to collapse
Your welcome if all goes well, it should be out tomorrow.
Sent from my ADR6300 using XDA App
Just an status update....while vanilla patch is working fine, one Rom doesn't work...ENOM's the nexus one doesn't work...so I gotta make the patch compatible with the ENOM rom
Sent from my ADR6300 using XDA App
Related
Hi all,
If anyone wants to play with this and let me know how it works feel free.Its the system directory from an AOSP eclair build using the Samsung Vibrant source download from the opensource website.I have no Vibrant myself I just built this as a test to see if it would build clean with no errors using the samsung files as a test for when the Epic 4g sources get released.Please feel free to use it in a rom or whatever you chose and post back if it works or not.
www[DOT]mediafire[DOT]com/?wytytv44odtdsdx
EDIT: This is not flashable! This is a stock /system filesystem from a build of AOSP android this is the base for a ROM not a complete ROM in itself.
Most likely it won't work cause Eugene is working from the aosp but is running into problems getting sound and camera to work.
I was just surprised it compiled the first run I saw another post where they were getting a lot of errors.And I figured there would be corrupt files I had a hell of a time extracting the archieve.
Sent from my SPH-M900 using Tapatalk
Thanks for posting that. I would like to have a look around but I wasn't sure where and what to grab.
www.mediafire.com/?wytytv44odtdsdx
heh
10char
Rhcp thanks for reposting a real link kinda sucks not being able to post them.
Sent from my SPH-M900 using Tapatalk
skeeterslint said:
Rhcp thanks for reposting a real link kinda sucks not being able to post them.
Sent from my SPH-M900 using Tapatalk
Click to expand...
Click to collapse
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
rhcp0112345 said:
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
Click to expand...
Click to collapse
There is no Kernel in a system image.
just got home, gonna dl and see what cooking
rhcp0112345 said:
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
Click to expand...
Click to collapse
I haven't tried building the kernel yet but I pulled the intramfs from a vibrant and captivate kernel to compare them togther and see if there are any real differences which it seems there really isn't that I noticed.One thing I did notice though is that the samsung kernel sources don't build the initramfs into the kernel that I noticed.With the Samsung Moment the sources had a file to build the kernel modules and a couple other programs that went into the intramfs and it had the initramfs_list file hidden inside the source somewhere it doesn't seem like they did that with the vibrant kernel source.How do they expect you to build a kernel that requires an initramfs in it and not build it into the kernel during the compile?I am gonna tinker around and probably use the initramfs_list file from the Moment initramfs and just add in all the directorys and files that are in the vibrant/epic/captivated initramfs.
it gets stuck on "installing update"
my clockwork does that from time to time with any zip file, just pull the battery and retry
Thats just a raw /system filesystem it would need to be cooked into a rom for it to be flashable.I threw it up there for someone to try and cook a rom out of it.
Has anyone had the problem when trying to compile a kernel that the suppiled build script doesn't build the modules?I can get the zImage to build but it won't build the modules at all.I would like to at least get it built with the samsung script and get the modules built then use the modules in the initramfs and try to build it with another script with the initramfs in the kernel.
skeeterslint said:
Thats just a raw /system filesystem it would need to be cooked into a rom for it to be flashable.I threw it up there for someone to try and cook a rom out of it.
Has anyone had the problem when trying to compile a kernel that the suppiled build script doesn't build the modules?I can get the zImage to build but it won't build the modules at all.I would like to at least get it built with the samsung script and get the modules built then use the modules in the initramfs and try to build it with another script with the initramfs in the kernel.
Click to expand...
Click to collapse
same problem I had with building the kernel
chaoscentral said:
same problem I had with building the kernel
Click to expand...
Click to collapse
The captivate kernel builds with the samsung script with no problem modules and all, used the captivate script with the vibrant kernel source same deal builds the kernel but no modules.
Almost Done! http://twitpic.com/2et5cb
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
You're out of your mind - in a good way. Vanilla has got to FLY on this thing, right?
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
Thank you so much for your hard work Eugene! Now if only we can get a mod or someone to lock your threads so only you can update, I'm tired of having to explain adb push/pull to people over-and-over, so I know you must be too.
Cheers,
=)
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
Eugene,
If I'm not mistaken...that's the stock home launcher for 2.2 isn't it? Or are you running adw/launcherpro
Sent from my SGH-T959 using XDA App
This is a flashable ROM from generated from 911Sniper's Incredible_C_GB_S_VERIZON_WWE_4.01.605.0. This is test build from HTC and may be buggier than a typical release. It includes all applications and original vendor configuration. In other words, it is untouched with the exception of the following:
Rooted with my customized version of Superuser (required until ChainsDD releases a version with my patches).
Busybox installed in /system/xbin.
There are no other changes. Just to be blindingly clear, this is NOT Virtuous; although a future version of Virtuous may be based on this ROM. Anyone building ROMs is welcome to use this as a base.
Disclaimer: This is a one-time release. Unless a problem can be identified with the changes mentioned above (rooting, deodexing, etc), it will not be updated or supported. In other words, use this as-is or find a ROM which uses this release as its' base if you would like support and/or expect to see changes.
Download ROM
(MD5:806a330639aeed3eae66ad547e00e86c)
Please Remember to hit the "Thanks" button if my work ends up being useful to you.
link is broken
Tested a bit now. Flashes and boots properly. Enjoy.
rmk40 said:
I am still testing this! Flash at your own risk!
(Will update the thread when testing is done).
Click to expand...
Click to collapse
LOL, I am very excited to get some of your work in the future. You did a great job with Virtuous Rom!
Thanks, I'll flash this later tonight, one question do I need to change my radio at all? I'm on 04.08.
CM7 nightly
masully1984 said:
Thanks, I'll flash this later tonight, one question do I need to change my radio at all? I'm on 04.08.
CM7 nightly
Click to expand...
Click to collapse
I'm on an even older radio and it's working fine (camera and all).
rmk40 said:
Tested a bit now. Flashes and boots properly. Enjoy.
Click to expand...
Click to collapse
Sense 1.0?
Sent from my ADR6300 using Tapatalk
phoenixs4r said:
Sense 1.0?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Yes unfortunately and no backported features from 2.x that I can see.
rmk40 said:
I'm on an even older radio and it's working fine (camera and all).
Click to expand...
Click to collapse
Cool, that's all I needed. Looking forward to trying this out.
CM7 nightly
Great minds think alike but I beat ya by 17 minutes lol
Nice work!
Smooth so far... No gbkeyboard... Oh well. I hate the stock keyboard! Still playing with it.
Sent from my Bad Seed Customs themed XDA app!
WOW
RMK - So glad to see you back on the scene. There have been no updates to Virtuous in forever. Very very excited at the possibility that a new Virtuous may be developed. WELCOME BACK.
Ahh. What a pleasant surprise to see this on XDA upon waking up. Cheers and thanks devs!!
Android community rocks.
Dinc via XDA
jdmba said:
RMK - So glad to see you back on the scene. There have been no updates to Virtuous in forever. Very very excited at the possibility that a new Virtuous may be developed. WELCOME BACK.
Click to expand...
Click to collapse
Indeed.
Dinc via XDA
rmk40 said:
I'm on an even older radio and it's working fine (camera and all).
Click to expand...
Click to collapse
what is the most up-to-date radio?
Radio
This one? The first two digits are month and day (which I think is an awful choice).
JoeyBert said:
what is the most up-to-date radio?
Click to expand...
Click to collapse
4.08 I believe.....can find in original post of CM thread or download INC Bits on the market which has everything. Here is link for Inc Bits in market
https://market.android.com/details?id=com.DPE.MuchSuck&feature=search_result
Sad they couldn't update sense to 2.0 so we could have a official version. Oh well warm Z rocks. Hopefully you crazy modders can get sense 3.0 on the DINC cause I love this phone
I have a Radio thread here for the Radio from this leaked GB release. 2.15.10.05.06
http://forum.xda-developers.com/showthread.php?t=1087166
wetbo529 said:
4.08 I believe.....can find in original post of CM thread or download INC Bits on the market which has everything. Here is link for Inc Bits in market
https://market.android.com/details?id=com.DPE.MuchSuck&feature=search_result
Click to expand...
Click to collapse
As of today, 05.06 is going to be the newest. Inc Bits has not had a chance to update yet as it is so new.
This ROM is based on the OTA that t3rabyte received, it's completely stock with root and busybox. This is meant as a flashable version of the dump he posted, so I don't plan on posting mods or fixes for it as I am also posting a custom ROM later based on this that I will do that for.
Also the kernel has been slightly modded to disable secure mode & enable init.d support.
I HIGHLY recommend you factory reset/wipe data before you flash this, even if your coming from the other TouchWiz ROM
The 2 version are:
Calkulin's_GT-P7510_HMJ37.UEKM7_ROM - Stock form
Calkulin's_GT-P7510_HMJ37.UEKM7_De-odex'd_ROM - De-odex'd for theming, mods, etc
Special thanks to t3rabyte
Nice, i add some mods to it
Very cool, thanks for the effort. Can't wait to see what you come up with! I need to root my GT, was waiting for the weekend but maybe tonight...
So installing the first one is basically like getting the update straight from the horses mouth? Sans the root and busybox of course.
Raistlin1 said:
So installing the first one is basically like getting the update straight from the horses mouth? Sans the root and busybox of course.
Click to expand...
Click to collapse
Correct, completely stock besides root & busybox
Thanks bro. Good to see some more devs coming in here.
Can anyone tell me how I should flash this? I'm running stock, locked bootloader gtab10.1 from staples. Thx. Never rooted tablet before. Not sure if I need to root before flashing this.
Sent from my Inspire 4G using XDA Premium App
gordec said:
Can anyone tell me how I should flash this? I'm running stock, locked bootloader gtab10.1 from staples. Thx. Never rooted tablet before. Not sure if I need to root before flashing this.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
The Rom is in .zip so you need CWM in order to install.
Look here or Here For instructions on how to install CWM.
Then download the .zip install it through CWM. The rom is already rooted.
For a locked tab, your only option probably is to flash the clockworkmod recovery through ODIN, instructions are in this that thread
http://forum.xda-developers.com/showthread.php?t=1150732
Ach double post. Sorry please remove.
Oh $h1t! For those of you who don't know calkulin is one the best dev's on this site. This work on the evolution 4g was epic.
Are you going to be fully supporting this device? Do you have a tab Calkulin?
dsh897 said:
Oh $h1t! For those of you who don't know calkulin is one the best dev's on this site. This work on the evolution 4g was epic.
Are you going to be fully supporting this device? Do you have a tab Calkulin?
Click to expand...
Click to collapse
Correction: His work on the evolution 4g IS epic.
dsh897 said:
Oh $h1t! For those of you who don't know calkulin is one the best dev's on this site. This work on the evolution 4g was epic.
Are you going to be fully supporting this device? Do you have a tab Calkulin?
Click to expand...
Click to collapse
+1
Stoked to see you working on the tab! If you are putting half as much attention on the tab as you did the Evo, things just got real up in here!
This rom is good for 10.1 Tab WiFi (P7510XXKFC)?
Thanks
First impression: very similiar as previous TW roms, maybe slight speed bump.
WOW: the keyboard input lag in stock browser is more or less gone!
Calkulin said:
This is meant as a flashable version of the dump he posted, so I don't plan on posting mods or fixes for it as I am also posting a custom ROM later based on this that I will do that for.
Click to expand...
Click to collapse
Highly highly looking forward to this. Can't wait! thanks!
DocRambone said:
First impression: very similiar as previous TW roms, maybe slight speed bump.
WOW: the keyboard input lag in stock browser is more or less gone!
Click to expand...
Click to collapse
Which one did you flash? Stock version or De-odex'd?
sdotk said:
Which one did you flash? Stock version or De-odex'd?
Click to expand...
Click to collapse
Stock, but i stripped it done a bit tho
Did anyone try the ram optimization mod that is posted on the board with this rom?
deodexed version is unavailable?
Good to see you working on the 10.1 Calkulin!
Disclaimer.
This is a largely untested alpha for a very expensive phone. I am not responsible for anything you do with it.
Information.
This is the initial release of HTC-Holiday-2.6.35-kx, a custom kernel for the HTC Vivid.
This is currently only for PirateGhosts's RumRaider Beta10, but may work with other versions of RR.
More information to follow.
Instructions.
If you don't know how to use this, you shouldn't be using it anyways. BUT....
1. Fastboot flash the boot.img
2. adb push the bcm4330.ko (WiFi module) to /system/lib/modules
Changelog.
001:
Snapdragon compile tweaks
Perflock disabled
Future Plans.
OC/UV
SPEED
Loopback?
Whatever
Download.
kx_kernel_001.zip - 3.53MB
Known Issues.
Kernel breaks camera
Instructions for porting to other ROMs.
Unpack the kx boot.img
Unpack the boot.img of the ROM you are porting to
Replace the ROM's zImage with the zImage from this kernel
Repack boot.img, flash with fastboot, and push the wifi module
This should, but is not guaranteed to work. Flash at your own risk.
I wish I knew more about this stuff, but unfortunately I don't and here comes a noob question:
Should the kernel not work properly or cause a boot loop etc...would I need to just re-flash the ROM from CWM? Also, will this still work with the Rogers HTC Raider?
So this is based on the Sense 3.5 kernel from Telstra? I guess it will work on any ROM based on this one, right?
Thank you so much!
Yesss
Can you add loop device support in the fuuttuureee!?
Sent from my HTC PH39100 using xda premium
Looks like I f'd the camera up... Can anyone confirm?
Updates tomorrow
Sent from my HTC PH39100 using xda premium
kxhawkins said:
Looks like I f'd the camera up... Can anyone confirm?
Updates tomorrow
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Yup camera is borked , had to pull the battery. Everything else seems to work fine tho.
finsilva said:
Should the kernel not work properly or cause a boot loop etc...would I need to just re-flash the ROM from CWM? Also, will this still work with the Rogers HTC Raider?
Click to expand...
Click to collapse
If something goes wrong, you should be able to just fastboot flash the original boot.img. It's always a good idea to make a nandroid / Titanium backup before flashing anything though.
vhjc said:
So this is based on the Sense 3.5 kernel from Telstra? I guess it will work on any ROM based on this one, right?
Click to expand...
Click to collapse
This is based on HTC's ATT Vivid sources, packed with the ramdisk from RumRaider 10. It should work with any ROM currently available, but would have to be repacked with the respective ramdisk. Read: This will not work out of the box for any ROM other than RumRaider.
MazinDLX said:
Can you add loop device support in the fuuttuureee!?
Click to expand...
Click to collapse
Please read OP; Loopback is planned.
User Error said:
Yup camera is borked , had to pull the battery. Everything else seems to work fine tho.
Click to expand...
Click to collapse
Thanks. Why'd you have to pull the battery?
kxhawkins said:
Thanks. Why'd you have to pull the battery?
Click to expand...
Click to collapse
it locked up while initializing the camera. tried it again just now and it was fine, aside from the camera not working part.
This is on hold until I can figure the overclocking on this out. I compiled Raider sources, and bananacake's kernel, and am unable to change clock speeds past 1.2GHz in SetCPU.
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed