[HELP]How to build own rom? - XPERIA X8 General

Many of my friends have x8.
I want to build own room so i can install it on thoose phones.
Can anyone tell me how to do that step by step. Starts from begining. I search xda and google but not find nothink usefull.
I notice i waanna build from stock room 2. 1u1, and i dont want to share it.
I know how to edit files, etc. But nothink about build to work like update in xrecowery or cwm, no care.
Any help?
Wysłano z X8 z użyciem Tapatalk

See here

dsixda's kitchen will not work if you're modifying stock Eclair. when you flash the built ROM with xrecovery, the xrecovery cannot read the file.
but if you are modifying Froyo or Gingerbread ROM, it will work.
Also, if you are refering building your own ROM to build it from android/CM source, then you need to download the source, well, it is more complicated than using dsixda's kitchen. but dsixda's kitchen is only doing the options provided, if you want to edit the files, you have to edit it yourself.

Grr... i wana build stock. Anyway... I can base on minicm... How to do that?
Wysłano z X8 z użyciem Tapatalk

it wont work if you use dsixda's kitchen. but there is another kitchen, it is created by aZuZu, but i forgot where i found it, also i didnt test it yet though.
just search XDA.

aldee_s said:
it wont work if you use dsixda's kitchen. but there is another kitchen, it is created by aZuZu, but i forgot where i found it, also i didnt test it yet though.
just search XDA.
Click to expand...
Click to collapse
dsixda works on SE 2.1.1 rom.. ive made mine with that long ago.
as far as i can remember,
dont start by extract system.img.. otherwise u'll find several broken file..
if you know which file is broken, just find it in your phone.
otherway just copy all your system folder to your pc.
this is just one thing.. there are other dependencies to make it work.
but, you can start by learning those kitchen and adb.
like our dev said.. think, read, discuss.
btw.. im not dev, still learn like you do.

Hmmm... what about building without kitchen? How to?
Wysłano z X8 z użyciem Tapatalk

http://forum.xda-developers.com/showthread.php?t=667298
this is a great advice , read it if you want to build a rom from scratch

Related

NO LONGER ACTIVE PLEASE CLOSE [devs] deodex version of ivanmmj Eris_Official 1.0

All,
per positive response below is a link to a copy of ivanmmj Eris_Official 1.0 ROM that I have fully deodexed. This is more meant for devs for continued play time, but it is a flashable ROM. PLEASE NOTE that ivanmmj himself looks to be coming out with the next version of Eris_Official 1.0 per his thread http://forum.xda-developers.com/showthread.php?t=652044.
Hope this is helpful and Enjoy
Link: REMOVED FROM HOST SERVER
P.S. please let me know of any issues as this is my first full deodex also I would like to encurage using this tread to exploring moding some of the system files on Eris ROM builds as it has been fun to tweak things
P.P.S. If you want the Zanfer kernel let me know and I will look at adding it in however ivanmmj's new version should have it...
what is Deodex?
I'm definitely interested, but I also think Ivan is working on the same project himself. I'm pretty sure his "1.1" is deodexed and has Zanfur's kernel. Not sure what other changes he has in mind, but you might want to check with him before posting since you'll end up being the one getting all the PM's from people wanting help. ;-)
Yes please I'm looking for exactly that
-------------------------------------
Sent via the XDA Tapatalk App
That would be awesome.
Sent from my Eris using XDA App
BTW jcase's plain jane1.0 has zanfur overclocking kernel.....
i dont know what you think but it might be a better platorm than ivanmmjs
a deodexed version of that would be tight....
kernels are easy to compile and swap out, a different kernel isnt going to influence the build at all
i always seem to get better battery life from the non oc'ed kernel.
Morkai Almandragon said:
what is Deodex?
Click to expand...
Click to collapse
Yes, what does that mean ?
hallstevenson said:
Yes, what does that mean ?
Click to expand...
Click to collapse
it means you have a classes.dex file rather than a .odex file
it makes things easier, its also possible to metamorph these builds and its possible to install a deoexed app on multiple platforms.
anonomouse said:
it means you have a classes.dex file rather than a .odex file
it makes things easier, its also possible to metamorph these builds and its possible to install a deoexed app on multiple platforms.
Click to expand...
Click to collapse
Means I can finally modify Rosie.apk to my liking.
hallstevenson said:
Yes, what does that [deodex] mean ?
Click to expand...
Click to collapse
A more experienced developer can add more but a few quick basics:
.odex files are precompiled class flies that correlate to a .apk or .jar file. In an odex ROM an .apk/.jar file will not function without it's correlated .odex.
a deodex build takes all of the .odex files converts them to a classes.dex and puts them into the .apk or .jar file package
deodex ROM are easier to mod because each .apk or .jar is a "complete" package and can be more easily decompiled and ported (i.e. you do not have to worry about the .odex files)
A deodexed build requires less space in /system, but more space in /data
A deodexed build requires a longer initial boot because they must regenerating those odex files from the dex files in the .apks/.jars and save them to /data/dalvik-cache
Thats a quick list of what I know
odex only help speed up app loading time and first time boot. Think of this as Windows' prefetch.
If you want to re-create odex for apk for porting, etc... I suggest only do this to /system/app not /data/app because when you do update from market and your app will break, unless you wipe out dalvik-cache.
zach.xtr said:
This is more meant for devs for continued play time, but it is a flashable ROM.
Click to expand...
Click to collapse
Would this be ok for an every day ROM? Or should it just be used by dev's as a base ROM?
Hey guys I've been testing this for Ivan. same thing he has a version deodexed.
I edited this
http://forum.xda-developers.com/showthread.php?t=664951
to work for this rom. which works great, but I get an error of
com.htc.bgp because of it, does anyone have any idea why?
Romparoo said:
Would this be ok for an every day ROM? Or should it just be used by dev's as a base ROM?
Click to expand...
Click to collapse
Technically it is fine as an everyday ROM, however I do not recomend using it for such because it is not support and will have no additional features over ivanmmj origional 1.0.
So I guess, yes it meant to be used as a base ROM or "spare parts" for devs.
BlazeD OnE said:
Hey guys I've been testing this for Ivan. same thing he has a version deodexed.
I edited this
http://forum.xda-developers.com/showthread.php?t=664951
to work for this rom. which works great, but I get an error of
com.htc.bgp because of it, does anyone have any idea why?
Click to expand...
Click to collapse
Someone else did this, on androidforums.com. I haven't replied to his posting, but it's in like page 19 of the 'show off your UI layout' thread there. I'm working on a modified Rosie.apk right now, as soon as I get this de-odex'd Ivan's on my phone running. Titanium backup here I come.
FYI, I was able to flash the deodexed version over the original Eris_Official 1.0 Alpha without having to do a full wipe (just wiped dalvik-cache). Naturally, I went back and re-flashed Zanfur's overclock kernel after that.

Stockwells porting script question.

As some of you know, stockwell has a miui porting script. I just began to wonder, can it be modified to port other roms from desire z? If someone could alter it a bit try to port one of desire z roms. I have very little knowledge on linux, but someone with more could do it.
Ret4rt and darksage have this script. They can answer to this question.
Sent from my Huawei Ideos X5
julle131 said:
As some of you know, stockwell has a miui porting script. I just began to wonder, can it be modified to port other roms from desire z? If someone could alter it a bit try to port one of desire z roms. I have very little knowledge on linux, but someone with more could do it.
Click to expand...
Click to collapse
U could try and just read the script from the github.. U could see the script will automatically add and replace some files and delete unnecessary file from Desire-Z ROM.. U can do it using windows AFAIK... Try using this tutorial
http://www.freeyourandroid.com/guide/porting-android to know exactly what to put to get the phone booting..
Do you have a link to the script?
PaulMilbank said:
Do you have a link to the script?
Click to expand...
Click to collapse
https://github.com/stockwell/MIUI-U8800-Port-Script/blob/master/miui_u8800_port.sh
For those who dont know Linux that well (Me too!), u need to figure out those function(rm=remove, cp=copy) and replace it manually in windows..
But updater-script could make it even harder.
Sent from my u8800 using XDA App
julle131 said:
But updater-script could make it even harder.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Stockwell make it easy for us actually, if u check that github, there's an "overlay" folder.. Inside is all the file needed to add into the desire-z rom,
including the updater script (/ overlay / META-INF / com / google / android )..
izzoe said:
Stockwell make it easy for us actually, if u check that github, there's an "overlay" folder.. Inside is all the file needed to add into the desire-z rom,
including the updater script (/ overlay / META-INF / com / google / android )..
Click to expand...
Click to collapse
Okay. I need to install ubuntu to my pc then amd try.
Sent from my Desire HD using XDA App

[For DEV] Samsung Galaxy S I9070 Advance kernel & platform source code

Hello!
This is a thread where potential developers can get kernel and platform source code for Samsung Galaxy S I9070 Advance, and other info. I will try to update this until we will have first custom rom ready. I encourage everybody with some experience with android development, to share their knowledge with other users here. Please if any of you will make any progress in rooting, making recovery or developing custom rom, to write here in this thread or even start a new one if some major break trough will be made.
Ok so here are the links to sources (I don't know the diference between those to, but I guess it is region related):
GTI9070_GB_OpenSoruce
GTI9070_LA_GB_OpenSoruce
All sources, can be found HERE.
In the attachment you can also find some other info I've pulled from my phone, which used to be rooted, cause I had some test version. I hope all this stuff will help us get root access, custom recovery and last but not least a whole bunch of custom roms.
NOW LETS HACKING AND DEVELOPING BEGIN!!!
One more thing, PLEASE take a minute to VOTE for this phone to get its own forum section here on XDA. Just make a post in THIS THREAD. The device is not in the poll yet, so you must write a post in thread. THANK YOU!
We've made a step into a right direction with a lot of help from forum I've made a working root method!
I've hard bricked my phone, so I am off the developemnt from this phone, only if by some chance I get a replacement. Sorry guys, in spirit of developing I've killed my phone .
I wish I was better at kernel development... I would love some development for this phone!
Sent from my GT-I9070 via Tapatalk 2
I've somehow managed to configure linux and pulled andorid sources from the repo, now I have to figured out how to compile a kernel. I have much to learn but if nobody else will give it a try, maybe I will succeed.
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
kilsmap said:
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
Click to expand...
Click to collapse
Dear friend. I come from China, now I already have a good i9070, I can help you with your test, you can send to my mailbox [email protected]
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
kilsmap said:
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
Click to expand...
Click to collapse
Same thing here. I have no idea how to get those, been asking around the forum an searching, but for now all the directions indicates that you need to have root access to get iniramfs. That really sucks...
hahaha...from this point of view, all Samsung phones after Galaxy S Advance will be quite hard to root... I'm waiting for the Galaxy SIII to launch, and for someone to root it... Maybe then we will be able to use the same way to root our phone... If only we can see what's inside our kernel.bin.md5... I'm sure the files we needed are in there...
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
an0nym0us_ said:
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
Click to expand...
Click to collapse
Yeah.. We have the stock rom, but can't figure out which one should we extract the boot.img from.. There was system.img.md5, cache.img.md5, hidden.img.md5, modem.bin.md5, and kernel.bin.md5... So which one? My suspicion lies to the kernel.bin, but I have no idea how to extract it..
Sent from my GT-I9070 using XDA
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Good luck!
Hope you get to a solution soon
I can't work on it as I currently don't have a phone to test on, sent it in for repairs.
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Have u tried flashing it directly to the phone? You don't have to make it into a boot.img to flash it.. Because I'm afraid that the zImage will be useless if not paired with working initramfs.. Compiling the kernel is quite straightforward, the thing is to get the initramfs to turn the kernel insecure.. There are also scripts to extract initramfs from zImage, but I haven't had time to test it..
Sent from my GT-I9070 using XDA
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
qzem said:
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
Click to expand...
Click to collapse
Yep, you got everything right there, I think.. Initramfs, ramdisk are the same thing.. They should include the cpio.gz, init.rc, default.prop etc... Have you extracted these files from the source kernel? Cos I don't think we can copy directly from phone, cos we need to preserve the permissions set on the files... Can you do that with kitchen?
Sent from my GT-I9070 using XDA
I am following the topic and hoping it works out the development of kernels and roms to the device.
Come on it has to be a way to compile an insecure kernel without having the access to rooted phone. Cause all the options I found till now, required some files, that can only bee pull from rooted phone. But the whole point of an insecure kernel is the possibility to root the phone. Anybody can help us? Maybe I should start another thread, damn it!
Haha... Yeah, somehow I feel that Samsung is screwing with us, what with the new firmware format (never had kernel.bin before) and secured kernel, this is becoming impossible.. If we just have some devs good-hearted enough to port CWM recovery for us.. But without initramfs, I don't know if it's possible..
Sent from my GT-I9070 using XDA
The initramfs is inside kernel.bin.md5 (as for the Galaxy S firmware).
kernel.bin.md5 is a normal zImage Linux kernel (+md5).
the initramfs is included in the kernel image (see http://forum.xda-developers.com/wiki/Extract_initramfs_from_zImage)
the initramfs is in our case a uncompressed cpio archive, therefore the script in the wiki does not work, but https://github.com/mistadman/Extract-Kernel-Initramfs/blob/master/unpack-initramfs can extract it without problem.
So, there should be no difficulty to root the i9070...
The easiest way would be to change the initramfs and repack everything.

Making roms and soft mods?

Dont know whether I should put this here or in general.....
Anyways, I do have a laptop now. I can make mods etc, but I do not know how. What is the best way to make soft-mods?
What devs allow softmods?
What do people want in a softmod?
Any suggestions would be welcome!
Thanks for your Offer.
I recommend you to make a Froyo Soft-Mod, cause we've a lot of GB CM7 on this forums, will be great to see more Froyo's ROM updated.
Take (with his permission) Miroslav's Utopia to start.
leoposas said:
Thanks for your Offer.
I recommend you to make a Froyo Soft-Mod, cause we've a lot of GB CM7 on this forums, will be great to see more Froyo's ROM updated.
Take (with his permission) Miroslav's Utopia to start.
Click to expand...
Click to collapse
So, what should I put in it?
What should I do?
Making mods without any ideas. It will be hard...
Sent from GT540.
haha this should be in general Either way 2.2 would be good i think i made a hell to many for 2.3 But for 2.2 its rather hard to theme but for tweaks its still fine.
bs828 said:
haha this should be in general Either way 2.2 would be good i think i made a hell to many for 2.3 But for 2.2 its rather hard to theme but for tweaks its still fine.
Click to expand...
Click to collapse
Well you can always edit png's in framework. You can use uot kitchen, dsixda kitchen, xultimate.
Init.d can be tweaked
If you want a complete ROM build you can try aosp froyo. You might use pcfighter / zice kernel .....
Sent from my GT540 using xda premium
Aosp froyo with notification bar togles, init.d script and ginger or some other theme would by nice.
When i created my soft-mod i didn't use a computer.
U don;t really need a computer to create a mod.
U just need root explorer. unless u want to create it into a recovery zip
Yes
androidboss7 said:
When i created my soft-mod i didn't use a computer.
U don;t really need a computer to create a mod.
U just need root explorer. unless u want to create it into a recovery zip
Click to expand...
Click to collapse
How did you decompile, and compile apk without windows?
bataya said:
How did you decompile, and compile apk without windows?
Click to expand...
Click to collapse
he just deleted apk's and added scripts etc
Hi.
I want start to make Rom .
Where should I start *?
Sent from my HTC Explorer A310e using xda app-developers app
Start by making soft-mods. Get a Rom flash it on your phone, dont add any personal stuff like contacts yet. Put in some nice apps themes tweaks and mods and after that use CWM to back it up and it "should" be ready to share... well at least that is somewhere to start from.
Edit: For those planning to make 4.0 softmods maybe you can also see this http://forum.xda-developers.com/showthread.php?t=1680328 i know its from the SGSII but i guess the way to do things is similar. (just dont use the flashable thing from the mediafire link!)

[GUIDE] How to port sense to non-HTC devices.

How to port Sense.
Source: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/164989-guide-how-i-port.html (second post)
This is NOT my guide, just posting it here!
This is a very difficult process that I hope you'll understand.
First step is to find a device that is preferably VERY similar to your device, in this instance I guess we would use the htc thunderbolt, which I've been told multiple times that it is used for the MT.
You're going to want to use CM7 for parts. Simple enough.
I will be referring the Sense ROM to SENSE and CM7 as BASE to simple things up. So remember that.
When I say replace, I would recommend deleting from one and adding it with the other
Open up Sense and Base in different windows.
Put in the boot.img from Base into Sense (make sure you put the original boot.img in some other place that you'll remember)
go into /system/usr on both
replace keylayouts and keychars from Base into Sense (this is just your keys)
download dsixda's kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
Get the ROM you have so far set up in it and what not (I'm a little fuzzy at this part)
Once you get done with that, run the menu in terminal and navigate your way to decompile the boot.img (action key- "a") and then run the same thing except run the action key "w" to decompile the original boot.img. So the key here is to decompile both boot.img's.
Go into the ramdisk on both and go into init.rc
THE MOST IMPORTANT PART IN THIS (THE MATTER OF BOOT AND BOOTLOOP) IS THE LINE
"export BOOTCLASSPATH" near the top. It will have a bunch of lines after it. Now in the Base's boot.img, delete this whole line. Replace it with the lines from Sense's boot.img.
Now you can add anything else you want that looks like it belongs (preferably anything sense related)
Don't recompile the boot.img yet.
Now we add a2sd. To do this, just follow this guide (https://www.facebook.com/note.php?note_id=158823170833688)
The only thing you do in there is the edits to the init.rc, don't listen to the decompiling/recompiling mentions. Now you can go back into the menu for the kitchen and recompile the boot.img (action key - "b"). Now don't compile the WHOLE ROM, just take the new boot.img in working_** and put it into the Sense zip.
Now you're going to want to download my ROM (sorry, just don't feel like uploading each individual file) http://gannon5197.blogspot.nl/2012/03/got-sense-booted.html
And go into the /system/bin on both
these are the files you're going to need: a2sd, bash, apps2sd.hlp, busybox.a2sd, chka2sd, jita2sd, launcha2sd, starta2sd, and maybe possibly sh (try once without it)
And you're going to want to set permissions for each one of these in the updater-script (look at mine for references)
Now also look at my zip and you'll see move_cache_sd. Put that in yours and set permissions for it in updater-script (use mine for references)
After that, the other stuff is mainly just getting rid of all the bloatware, (look in /system/app and /system/media) I wouldn't delete any libs as of right now. If you try to flash it and it reboots recovery then it is too big.
If it is too big, you're probably going to want to move a lot of the apps to data. To do this, just make a file called data/app/put_your_apps_here on the root of the zip. You're going to have to set permissions for it in the updater-script, but use the test.zip I sent you in the original.
This will most likely get you booted. Nothing will likely work. Which is expected. If you have any problems, just use logcat. It will be your bestfriend. Have fun porting
Click to expand...
Click to collapse
reserved
Thanks for reopening it bro...
Sent from my LG-P500 using Tapatalk 2
No problem :thumbup:
Don't know how this above awesome thread is so blank
Have u tested if this way works
Sent from my LG-P500 using Tapatalk 2
great guide, gonna try out soon
hmm this one's new for me. saved
should come in handy sometimes
someone has to do this for the Galaxy S2.
Will it also work for ICS ROMs?
I must do this. Anybody know where I can get the firmware for the One S?
Can i use a Gingerbread ROM as a base instead of cm7?
Hello for lg p500 there is 2 sense rom but data and mic not working in both rom can you help to solving that problems????btw great tutorial.
in fact sensse porting is differnet from the tutorial showed it is a little bit more difficult and there are some libs needed that there is only for the devices you are porting to. so a general tread will not really work
QuBe2 said:
in fact sensse porting is differnet from the tutorial showed it is a little bit more difficult and there are some libs needed that there is only for the devices you are porting to. so a general tread will not really work
Click to expand...
Click to collapse
Well this is not my tutorial just found it on the internet so I don't know if it works
Lord Inglip said:
Well this is not my tutorial just found it on the internet so I don't know if it works
Click to expand...
Click to collapse
why sharing things on the internet
QuBe2 said:
why sharing things on the internet
Click to expand...
Click to collapse
Because it's the internet. This guide was the only thing I could find.
Well you ported a htc sense One x rom to the Nexus S, so can you show us how you did it?
Lord Inglip said:
How to port Sense.
Source: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/164989-guide-how-i-port.html (second post)
This is NOT my guide, just posting it here!
Click to expand...
Click to collapse
Similar phone means the same chipset,processor and gpu??
a2441918 said:
Similar phone means the same chipset,processor and gpu??
Click to expand...
Click to collapse
Yes it's better if the phones have the same hardware
Lord Inglip said:
Yes it's better if the phones have the same hardware
Click to expand...
Click to collapse
I have an xperia x10.. will the nexus one and HTC desire be suitable??
My cm7 rom which i downloaded doesn't have a boot.img file.. So how to get it?? Is it the system.img got from a nandroid backup?? and the sense rom which the post refers to is the stock sense rom of the phone in a zip format or a modded one??
Not working..stuck at boot logo

Categories

Resources