Could anyone teach me how to port a rom, or could someone do it for me, I am trying to port Tweaky Rom from Galaxy S I9000 2.3.3?
Thanks
The question is like asking "how do you write music" A bit complex....
You can use some of the apps and tool out there to help you extract the rom and or other information you want, kitchen and rom oven are a couple that come to mind.
You need some understanding of Linux and ADB
Here is a basic explanation of sorts but this not complete:
Take a base ROM from another phone. First thing, delete the boot.img. That boot.img contains the kernel, which usually will not be compatible for your phone.
Next,
Add the boot.img from your phone to this rom (use commom sense, if you are porting a vanilla rom, use an AOSP kernel, if porting sense, use HTC kernels, if you are porting other UI’s like blur, use an AOSP kernel.)
Then>
Go into the /system folder. In here, we want to first delete the usr folder. The usr folder has hard button and keypad drivers. Replace the usr folder with the one from your phone.
Then>
Go into the etc folder. delete the vold.fstab andapns-conf.xml and replace with the one from your phone. Next, we want to go into the lib folder. Here, we will want to replace the lights.(device name here) (and the sensors.name if it is an AOSP port) and replace with files from your phone.
-There much more to it but this is a basic overview-
Every phone is slightly different I have never ported on a Vibrant but this was my memory of how I did it on my HTC.......... hope that clarifies for you......
If your porting w i9k rom, replace the kernel and modem with the ones from our phone. Since its gingerbread, you will need a special modified gb kernel. Simply honey 2.3.3 uses chainfires modded kernel. See if you could use it. Or register at the edt site. We have custom gb kernels on our site. Then you will have to modify the two files in system/usr/keylayout; malfes_touchkey.kl to get the home button to work, and aries-keypad.kl to fix the volume buttons. Next you need to decompile the android-policy.jar and edit the phone window manager to make the haptic feed back work on the home key. Hope this helps.
Sent from my GT-I9000 using XDA Premium App
Dan_Brutal said:
If your porting w i9k rom, replace the kernel and modem with the ones from our phone. Since its gingerbread, you will need a special modified gb kernel. Simply honey 2.3.3 uses chainfires modded kernel. See if you could use it. Or register at the edt site. We have custom gb kernels on our site. Then you will have to modify the two files in system/usr/keylayout; malfes_touchkey.kl to get the home button to work, and aries-keypad.kl to fix the volume buttons. Next you need to decompile the android-policy.jar and edit the phone window manager to make the haptic feed back work on the home key. Hope this helps.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
There you have it from the porting legend
Thanks, both your responses were really helpful, I really appreciate it.
One more question, would it be possible to use the custom gb kernels with jvh which is what I plan on porting?
Sent from my GT-I9000 using XDA Premium App
That's what I'm using. All the vibrant gb kernels, with the exception of the cm7/miui kernels, will work with 2.3.3.
Sent from my GT-I9000 using XDA Premium App
Related
I believe it's time for us mophos to come together and make an up to date community rom. We can use yays deodex base, shabby and i will cover the kernel. Loki could handle webtop, and of course everyone can theme/pitch in. This will be multiple roms of course. As much as I want cm7 I love webtop(loki thank you so much). I will eventually try to help with cm7 and maybe an aosp with webtop still attached and some cm7 goodies. The everything is there for people to start making roms. Repack yays newest how you like with an oc kernel maybe some scripts themes and edit and bam. You a dev. When I get the time I'll make a starter pack so everyone can contribute. Till then ask, Google and at least try instead of complaining.
Sent from my MB855 using XDA App
I'm heading to Google right now. Is there a specific Linux distro better suited ex. 64 bit vs 32 bit?
Sent from my MB855 using XDA App
64 ubuntu.
Sent from my MB855 using XDA App
To build anything GingerBread and up you will have to have a 64 bit os - supposedly you can trick it, but I haven't had any luck with that so far on my old machine that is stuck in 32 bit hell.
I have 64-bit Windows 7 at home...I can assist if necessary...the only thing is that I'll need clear instruction on what to do..cuz I don't have a clue where to begin.
KTT16 said:
I have 64-bit Windows 7 at home...I can assist if necessary...the only thing is that I'll need clear instruction on what to do..cuz I don't have a clue where to begin.
Click to expand...
Click to collapse
1) Start with getting rid of that Virus you have....Windows. Install a dual boat of Ubuntu x64 if you must have windows.
2) Install the Android SDK for Linux.
3) Google has a good walk through on how to build a Vanilla version of Android - not specific to any device - except maybe the emulator....but I'm not sure if it is or not.
3a. It takes a long time to download the source....
teh sdk is not needed. tahts if you wanna build apps. you guys do realize that to build a rom you dont need a certain os or anything? granted having linux makes it easier. now if you want to compile aosp or cm7 from source you will need 64 bit linux (preferably a debian/ubuntu based release)
all you need to make a rom is take the files off your phone and edit them.. there are a gazillion tweaks out there that could be brought over from other phones and made to work on it. the only roms you are going to be compiling at this time wont have voice/data just like cm7
Unless someone builds from motos src
shabbypenguin said:
teh sdk is not needed. tahts if you wanna build apps. you guys do realize that to build a rom you dont need a certain os or anything? granted having linux makes it easier. now if you want to compile aosp or cm7 from source you will need 64 bit linux (preferably a debian/ubuntu based release)
all you need to make a rom is take the files off your phone and edit them.. there are a gazillion tweaks out there that could be brought over from other phones and made to work on it. the only roms you are going to be compiling at this time wont have voice/data just like cm7
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
idk how it is in moto land but the samsung "platform" source was never even enough to get a booting version of android on that phone
Sounds cool Ill try it out when it gets made
personally id be happy to get rid of motorola's widgets and stuff and run a generic rom. they are butt ugly
Ryan92394 said:
Sounds cool Ill try it out when it gets made
Click to expand...
Click to collapse
Smh
Sent phrom my Mo-Pho
UOT Kitchen
Hey joker - per your request:
UOT Kitchen - http://uot.dakra.lt/kitchen/ - An easy way to theme
How to use it for our Photon (some mods do not work on it unfortunately)
1) Copy your framework-res.apk and SystemUI.apk from the framework and apps folder onto your computer's desktop
2) Whichever mod you want, click on the tab on the horizontal nav menu and click "Use this mod". Choose the mod. Ex: Battery Mod - Click Battery, Click "Use this mod", and then choose which battery icon you want. You can also change the color of the percentages as it drains down by using a HEX code at the bottom of the page. You can even see the preview so you know what the mod looks like.
3) When ready to cook your new theme, go to the File Upload tab
4) Select "AMEND SCRIPTING" on the left menu
5) Deselect "Generate Preview for Theme Chooser"
6) Select "System Files" from the right menu and upload the framework-res.apk and SystemUI.apk files. Ignore the other two.
7) Once they upload, go to summary and click "Submit work to kitchen" there'll be file name that you should probably write down so you don't forget it.
8) Wait for your theme to cook and once it's ready (it could take a while), download it and put it on your sdcard.
9) Get into ClockworkMod or Bootstrap Recovery and wipe both cache and dalvik cache
10) Install the UOT zip file
11) Reboot and enjoy your new theme
you want edify scripting, amend should have been phased out in cwm 3.x
By mistake I did edify scripting and I got an error when trying to flash the UOT zip. Then again, I did flash via Bootstrap so I'm not sure if that's the reason. Anyway, if you're using Bootstrap, amend scripting is the way to go.
Best,
K
yea tahts because teh edify scripting requires mounts, and since the kitchen is old and outdated it doesnt auto detect /system so you need to go in and add it properly as we arent a true mtd device
Ok well my rom is uploading if anyone feels like theming go ahead, the best theme will become default on all nonstock joker roms, and we really need our own cwm shabby
Sent from my MB855 using XDA App
bleh but making cwm is such a PITA, porting tends to be worlds better, sides isnt the version we have now like 99% working.. its just not official?
I agree im just sayin
shabbypenguin said:
bleh but making cwm is such a PITA, porting tends to be worlds better, sides isnt the version we have now like 99% working.. its just not official?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
sides id much rather get twrp working for twrp 2.0 the fully touchscreen modable recovery
I'm trying to port HTC ROM to my LG, but any try result on non-booting ROM. I used dsixda kitchen just to extract both ROMs in separate folders, but when I replace some files ex. under /system/lib or /etc it does not boot when flashing with clockwork zip. I removed unnecessary apps just to fit system to my phone.
Which files do I need to take from custom ROM for my LG to make HTC ROM working/booting. I took /hw /modules /egl under /lib some files /etc and keychars according to:
http://forum.xda-developers.com/showthread.php?t=815265
http://forum.xda-developers.com/showthread.php?t=1222746
Also I took boot.img from my GT540 and modified build.prop. I can't find a reason why it doesn't work, sadly logcat doesn't work too.
There are many ports but all sense to sense device. Any tips what to do? Just at least to boot it up, later is the time to make everything else, now its important.
I booted Eclair Sense ROM in past but nothing was really working good, just 3d, bt and gps but I see its possible according to 2.2 Sense ROM port made by cile for gt540.
I used HTC Pico RUU CHS latest leak 1.20 as ROM I wanted to port and I used libs from pcfighter .32 kernel one time and same result as with .29 libs from DevSwift's OXYGEN and miroslav_mm SDSL so I think its nothing wrong with my libs, just Im making mistake somewhere.
mesaj said:
I'm trying to port HTC ROM to my LG, but any try result on non-booting ROM. I used dsixda kitchen just to extract both ROMs in separate folders, but when I replace some files ex. under /system/lib or /etc it does not boot when flashing with clockwork zip. I removed unnecessary apps just to fit system to my phone.
Which files do I need to take from custom ROM for my LG to make HTC ROM working/booting. I took /hw /modules /egl under /lib some files /etc and keychars according to:
http://forum.xda-developers.com/showthread.php?t=815265
http://forum.xda-developers.com/showthread.php?t=1222746
Also I took boot.img from my GT540 and modified build.prop. I can't find a reason why it doesn't work, sadly logcat doesn't work too.
There are many ports but all sense to sense device. Any tips what to do? Just at least to boot it up, later is the time to make everything else, now its important.
I booted Eclair Sense ROM in past but nothing was really working good, just 3d, bt and gps but I see its possible according to 2.2 Sense ROM port made by cile for gt540.
I used HTC Pico RUU CHS latest leak 1.20 as ROM I wanted to port and I used libs from pcfighter .32 kernel one time and same result as with .29 libs from DevSwift's OXYGEN and miroslav_mm SDSL so I think its nothing wrong with my libs, just Im making mistake somewhere.
Click to expand...
Click to collapse
Its because (you have found this on a search) Sense is built deeply into the framework and drivers. It will only work on HTC devices. Same goes for Samsungs touchwiz and Motos Motoblur.
Anyway older sense worked, atleast it was booting and wasn't that far from working. In ciles port there were just some 3d problems, but I've found a solution for it, wifi(as usual), microphone(so calls, but gsm module was working), some other bugs like tethering, but look, it was developed recently even for other working roms, usb storage, but I think it was possible to be fixed with some kernel changes if devs made it in .32 and .35 kernels by yourself.
mesaj said:
Anyway older sense worked, atleast it was booting and wasn't that far from working. In ciles port there were just some 3d problems, but I've found a solution for it, wifi(as usual), microphone(so calls, but gsm module was working), some other bugs like tethering, but look, it was developed recently even for other working roms, usb storage, but I think it was possible to be fixed with some kernel changes if devs made it in .32 and .35 kernels by yourself.
Click to expand...
Click to collapse
Well if you can get it working then great you will be able to do something that many of the great developers here have been trying to do but have all failed.
I'm porting sense to sense so I understand some of what you are trying to do, a major problem for me was update script just so it can flash and you have to replace all hardware libs from target device but I don't know anything about framework and stuff like that. Hope this helps a little
Sent from my HTC Desire HD A9191 using xda premium
It works on galaxy s and nexus s. First order of business is to add bootclasspath from sense in init.rc which is part of intramfs which is part of the kernel to your init.rc.
Sent from my SPH-D700 using Tapatalk
I want to include a custom kernel in my next rom update, not to sure the best way to go about it? My roms currently just have stock kernel, I've found a great custom kernel I would like to include, I did Google didn't find too much help.
Sent from my HTC EVO 3D X515a using xda premium
markdexter said:
I want to include a custom kernel in my next rom update, not to sure the best way to go about it? My roms currently just have stock kernel, I've found a great custom kernel I would like to include, I did Google didn't find too much help.
Sent from my HTC EVO 3D X515a using xda premium
Click to expand...
Click to collapse
You can use dsixda's amazing android kitchen to bake it in. What you need to do is take your ROM and set up the kitchen with it. Once that is done you go into the advanced option of the kitchen and select unpack boot. Then in the boot-extracted folder you replace the zImage with the zImage of your new kernel you want. Once copied you repack the boot.img and then copy the modules from the new kernel into the ROM.
私のEVO 3Dから送信される。
Great answer, Thanks buddy!!
markdexter said:
I want to include a custom kernel in my next rom update, not to sure the best way to go about it? My roms currently just have stock kernel, I've found a great custom kernel I would like to include, I did Google didn't find too much help.
Sent from my HTC EVO 3D X515a using xda premium
Click to expand...
Click to collapse
If you're interested in learning how to integrate the kernel yourself instead of using a kitchen, the process is fairly simple.
There are two main areas you'll need to add into the ROM
1) The actual kernel, generally a boot.img file.
2) The associated kernel modules, usually stored in /system/lib/modules.
The best way to add in these two sets of files.
1) The kernel boot.img can be added into the root of the update.zip file. The associated code needs to be added to the updater-script file which will essentially write the boot.img into the boot partition memory. Great example can be found in my ROM . The updater-script code should be the same for CDMA and GSM, as the function is fairly generic.
2) Associated kernel modules can be easily copied into the system/lib/modules directory of the update.zip file and will be copied over along with the rest of the ROM by the current package extract command in the updater-script.
Hope that helps add some technical detail and best of luck!
I asked for help to build a rom ics on our xt615
I present the trick:
we recover a leak motorola ics for our phone (. sbf)
we extracted the boot.img system.img recovery. etc. .....
we have for the moment a Chinese cwm recovery but works in English or a problem with the nandroid
the problem is that when trying to build the rom for our phone and flash that we have a "status 0"
then here we ask a person who could help us build a rom ics
thank you
links:
extracted from sbf
https://docs.google.com/file/d/0B2k1N5APM4JQLWZ3ajVETG54UTQ/edit
testing the construction of the ROM
https://docs.google.com/file/d/0B2k1N5APM4JQaWF0N0Q0TV9pWTA/edit
and the subject of motoluxe xt615 not play pass all first pages on pages 65 to
http://forum.xda-developers.com/showthread.php?t=1660377&page=77
Up please
Thank
Sent from my XT615 using xda app-developers app
I don't know anything about your phone, but your zip file is incorrect.
You want to put all the files except META_INF into a folder called system. Look in META_INF/com/google/android/updater-script and you will see this is what the recovery is expecting.
Also, add a boot.img since it will try to flash that as well.
This is what the root directory of the zip file should look like:
Code:
[email protected]:/android/work/moto/zipper# ls
boot.img META-INF system
[email protected]:/android/work/moto/zipper# ls system/
app bin build_proj etc framework media usr
arcsoft build_id build.prop fonts lib tts xbin
gee one said:
I don't know anything about your phone, but your zip file is incorrect.
You want to put all the files except META_INF into a folder called system. Look in META_INF/com/google/android/updater-script and you will see this is what the recovery is expecting.
Also, add a boot.img since it will try to flash that as well.
Click to expand...
Click to collapse
Yes but try various solution and i have always error status 0
If you look the topic we have try
Page n° 70\80
Thank
Sent from my XT615 using xda app-developers app
gee one said:
This is what the root directory of the zip file should look like:
Code:
[email protected]:/android/work/moto/zipper# ls
boot.img META-INF system
[email protected]:/android/work/moto/zipper# ls system/
app bin build_proj etc framework media usr
arcsoft build_id build.prop fonts lib tts xbin
Click to expand...
Click to collapse
I don't understand
I took example on several
can you help me to do this update
A big thank
Sent from my XT615 using xda app-developers app
I read that thread a little- it looks like a lot of people trying different things. Also, use post numbers because it's page 17 on my computer
So, where did the updater-binary and script come from? The script has to match the rom, but I think the binary is a lot more forgiving. I think a binary from another ics or gb rom should work. Your phone uses yaffs, so maybe an older binary? I thought a lot of the ics devices were moving to ext3/4?
I think the stock recovery won't work. Usually, they will only accept zips that are signed by the manufacturer.
sent while running with scissors
gee one said:
I read that thread a little- it looks like a lot of people trying different things. Also, use post numbers because it's page 17 on my computer
So, where did the updater-binary and script come from? The script has to match the rom, but I think the binary is a lot more forgiving. I think a binary from another ics or gb rom should work. Your phone uses yaffs, so maybe an older binary? I thought a lot of the ics devices were moving to ext3/4?
I think the stock recovery won't work. Usually, they will only accept zips that are signed by the manufacturer.
sent while running with scissors
Click to expand...
Click to collapse
we have a custom recovery rom just leaked motorola
I built the rom update with kitchen
I get a flash of themes yet but they put me in error
and I saw no or that I can just
I can not make a updater-script
can you tell me the way to follow
Thank
Sent from my XT615 using xda app-developers app
dams161 said:
we have a custom recovery rom just leaked motorola
I built the rom update with kitchen
I get a flash of themes yet but they put me in error
and I saw no or that I can just
I can not make a updater-script
can you tell me the way to follow
Thank
Sent from my XT615 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=31086093
Sent from my XT615 using xda app-developers app
Flash at your own risk- I didn't read the thread and I wouldn't know you device from an iphone.
https://rapidshare.com/files/2281343112/xt615ics1.2_mod1.zip
I cleaned up the system and added the boot.img. if you can get the /etc/recovery.fstab from your recovery, it might help since the partitions might have different names.
sent while running with scissors
gee one said:
Flash at your own risk- I didn't read the thread and I wouldn't know you device from an iphone.
https://rapidshare.com/files/2281343112/xt615ics1.2_mod1.zip
I cleaned up the system and added the boot.img. if you can get the /etc/recovery.fstab from your recovery, it might help since the partitions might have different names.
sent while running with scissors
Click to expand...
Click to collapse
thank you
i try and i say if work
does not work I toujour error status 0
I think that is an error with the update binary. Maybe you can get one from a similar phone? It should be pretty generic, as long as it uses a similar file system/android version. So try to find a binary from an ics device that uses yaffs/MTD.
sent while running with scissors
i try and i say if work
yes works but the boot.img is bad thank you
I thought this was the stock firmware? Could you just put in a similar ics kernel and see if that works? A kernel from an ics moto phone might work, but you'll have to change the ramdisk.
sent while running with scissors
gee one said:
I thought this was the stock firmware? Could you just put in a similar ics kernel and see if that works? A kernel from an ics moto phone might work, but you'll have to change the ramdisk.
sent while running with scissors
Click to expand...
Click to collapse
the concern is that the bootloader is locked
and I think he does not want ics files
you have ideas on how to bypass the UNLOCK or
thank you again
Do you have a copy of a working boot.img or kernel? Even a dump from a running phone would work.
sent while running with scissors
gee one said:
Do you have a copy of a working boot.img or kernel? Even a dump from a running phone would work.
sent while running with scissors
Click to expand...
Click to collapse
my boot.img
So the zip that I uploaded flashes, but it doesn't boot?
I think your working boot image is GB or Froyo and the new one is ICS. So maybe if I take the kernel from the ICS boot.img and add the ramdisk from your working one, then maybe it might work.
Maybe...
This is the new kernel with the old ramdisk. Again, flash at your own risk.
https://rapidshare.com/files/908298923/xt615ics1.2_mod3.zip
hi im currently in process of porting a stock deodexed rom.
i have changed system files and the update script.for out i9305. at moment i am able to install the rom fine and loads up with or without wipe. i also included the ee modem.
my issue is that when the rom starts all is ok and there are no force closes however i get no network and imei shows null. to resolve this i just flash param.tar in odin and stock file and all is back to original with imei restored.
any ideas on whats causing the loss of imei number
in setting imei and baseband showbas unknown
edit whilst restoring to stock i did not have to restore imei backups so am asuming efs part is fine
Sent from my GT-I9305 using Tapatalk 2
Check 9500 partition layout and update install script. Dont rewrite the efn part.
Sent from my GT-I9305 using xda app-developers app
have done that part rom installs fine baseband is unknown
Sent from my GT-I9305 using Tapatalk 2
I think u need to Flash a baseband from our i9305 after flashing The Potter rom
but wouldnt that be the modem file iv tried flashing it on radio partition
Sent from my GT-I9305 using Tapatalk 2
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
i am really into this thread. I opened a thread similar at the beginning but they moved it, hope this one stays in here otherwise it will get lost in the i9300 section...... this is really good lets all try get into this, like i said I am going to play around on monday when i return home, so far we got everything going exceept the Modem is not connecting to the Imei correctly, We need an experienced dev.
---------- Post added at 09:25 AM ---------- Previous post was at 09:14 AM ----------
Just think how many roms we can have if we get this going
Sent from my GT-I9305 using xda app-developers app
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
going to check ril today see if that sorts it
Sent from my GT-I9305 using Tapatalk 2
Great thread, wish I could contribute more.
At the moment I'm hanging to see what the more clued up guys around here work out!
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
chwads2k8 said:
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Basically there are some intensely different changes within the services.jar, framework.jar, android-policy.jar and so forth. 4G LTE is sooo much different than the stock i9300. I am not saying it CAN'T be done. But I am saying it is going to be a complete bastard to do. Put it this way, you'd be better off looking into all of the modifications that have been done to create these ROMS and re-doing them to the i9305.
Trust me, I have looked into doing this with a "customised" build to from sources for ICS for the P7320T tablet that I had. It is the only 4G tablet released here in Australia. The closest I could find in sources for being able to make the connection was grabbing settings systemUI and the others I have listed above ^^^ from the S2 4G LTE. Then I was going to have to modify the systemUI specifically for tablet mode.
I no longer have the tablet nor the patience to want to take on anything like it again.
All I can say is good luck. Feel free to check my threads to confirm that my choices are not a conflict of motivation or lack of determination...god I can assure you that much
Just for a tip. I started today with decompiling the android-policy.jar file to see if I could enable the torch app double click home from lock screen feature....this has been done on i9300 right? Go take a look at the full guide on how to do it...go decompile 1 file that I am talking about and you will see just how different the methods are in all of the smali code. JOY!
---------- Post added at 03:34 AM ---------- Previous post was at 03:23 AM ----------
chwads2k8 said:
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
Click to expand...
Click to collapse
What tools are you using to "port" this ROM to our device?
I have tools that can port ROMs in about 30-40min.
What have you got in the build.prop for this thing? Do you want to upload the ROM for me to take a look at? The least I could do is offer some help before raining on your parade lol.
Have you considered doing maybe a "splice" of the ROM. Rather than porting the full version, you could do a diff/compare of the modded ROM against it's stock counterpart. Then you migrate those changes over to your "stock i9305" base. That is going to be your best chance of doing this I reckon? also you won't be able to copy across the firmware version. That won't work. Your framework and the firmware version are going to be device specific.
The absolute best thing I can think of suggesting is to go with a known base equivilant?? Like it seems that there is a release of XXALI5 (for touchwiz at least?) on both devices. That would be where I would start first and foremost. I would port with that common version using what I described above and then migrating any further or additional functionality (developer made i.e. Wanams mods) that have been done since the XXALI5 release.
That is going to be your best bet.
Or you guys could just wait for me to release my ROM haha...subtle promotion? I think not.
btemtd said:
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Exactly
I have a methodology that does this very easy. I wanted the OP to upload his work so far to save me a download. But I might just go ahead and do it anyway.
Have you guys got permissions from Wanam to use his work? I will ask on your behalf if not. He is a great contributor to this forum, I don't wish to have him offside.
What I mean is that I will go ahead and play, but I won't re-upload any test files to the forum without his consent This shouldn't be too hard
---------- Post added at 12:40 PM ---------- Previous post was at 11:53 AM ----------
Contacted Wanam. I will wait to see what he says and recommends. I have claimed I am not releasing anything of his, so this can be owned by you guys who want it. I am happy to help get the ball rolling to help yous though. I have my own dev team that I work with so that makes me kinda busy. That is why I haven't released my own ROM on here yet lol
Downloaded XXLAI5 Wanam, Downloaded XXLAI5 stock i9300, have already downloaded XXLAI5 stock i9305 and I am currently deodexeding it as we speak.
Will deodex i9300 XXALI5 next and then do a comparison to Wanams. Segregate changed files - > port to stock deodexed base = Wanam i9305 for you guys
That's if Wanam approves of course?
EDIT: Hey Mr OP can you please contact me? I cannot send you PMs? Holy smokes you've been around this place since 09!
Ok Analysis done on Wanam compared to stock XXALI5 and have all the of the files seperated and within their directory structure that had changes.
There is going to be some work needed to be done on these main files:
/system/framework/android.policy.jar
/system/framework/framework2.jar
/system/framework/services.jar
/system/app/systemUI.apk
As I expected
Now the fun n games start I will decompile all of these files and then diff them against the standard i9300 smali coding and then *attempt* (and I say that with all great intension too) to migrate the changes across into decompiled i9305 files.
I can tell this is going to be a head ache!
Otherwise though....I can honestly say that what I have got so far I know for certain will boot and you will not have baseband issues. You won't however have 15 toggle mod as it stands. Services.jar and Android policy.jar both control this feature. I see that this *IS* available as a mod already on this forum but I am not certain that the creators realise that these modifications (mentioned here) actually do need to be performed.
Lidroid-res.apk within framework will have no rights to control the toggle on the systemUI cause it won't have permissions due to conflicting signature checking. note...toggles may appear, but they won't do anything when you touch the widget toggle, it will be non-responsive.
Thanks guys
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
btemtd said:
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
System app is fine, but that isn't where the changes are that make Wanams ROM. You'd have your self a standard ROM otherwise. As in no difference. Or if you just copied the system/app folder ROM would boot but systemUI would force close. You would also have no reboot menu and no USB read from the phone. That would equal disasterous....cause as we all know we don't have SD mount in recovery do we?
Fancy doing an adb push on a phone that doesn't install USB connection files?
See I wouldn't be stupid enough to do that without having at least a clockwork recovery backup lol.
It's ok. for the android.policy.jar they are identical (well for XXALI5 they are anyway) to the i9300. So simple trade in there.
Only 4 more files to go and I will have you guys a port
Wanam still has not contacted me back yet though so I we need approval before anything.
Reset scrolling caches. In framework2.jar
This took a bit of work because my notepad++ kept crashing running compare. If you guys ever have this issue, right click the executable in program files go to properties and compatibility and then check the boxes for:
- disable visual themes
- disable desktop composition
- disable high dpi scaling.
Apply.
No more crashing. Windows 7 aero apparently doesn't like the compare dll?
Anyway not related. I am back on track. last jar file and then it should be ready to package up and it will be the same as Wanam ROM XXALI5
Got approval from Wanam. Just about to test flash now. Will upload it here if everything works out
Well, I had a few mishaps with my own device. Namely no root access and also lost hardware ID...meaning no Android Market. This all happened sometime during my lengthy list of modifications so I was not sure where. That mean flash back to stock and restore my data bit by bit until I was set up again. This take for EVER!
So yeah no real feedback from anyone in here so have decided to finish off my own ROM instead. XXALI9 (newer) and a heap more mods than stock Wanam. So far so good.
I can upload what work I did on getting Wanam's up and running (I have not flashed it yet) but will wait till someone actually wants before I go ahead and do that.
Thanks guys
James