hey guys,
as the ace is a very simular device and multiple roms have already been ported by our devs, I would like to introduce a guide wich makes it very easy to port, as most guides take much time and some experience, but porting from a device that only has a different camera and sensors and some more(from inside), it isn't neccesairly needed..
so here's what I do:
WARNING:
im not responsible if anything goes wrong and your device will be bricked. you have been warned.
I'll be saying ''ACE rom'' to the rom you want to port from ace, and ''GIO rom'' to the rom you are going to use as base
1. preparations before we begin porting:
- make a new folder and paste your rom you want to port inside, and extract it.
- if you're rom is cm7/9/ based, you should download a rom for gio that is too.
if you're rom is stock firmware based, you should download a stock based custom rom for gio.
- after you did that extract them both in seperate folders.
- it will look like this:
''Meta-Inf'' - updaterscript and binary, actual commands to install in recovery
''System'' - the system folder, contains all sounds, apps, framework, etc.
''boot.img'' - the kernel
2. Boot.img/kernel
- delete the kernel from ACE rom and copy GIO rom boot.img to
/ace-rom-name
3. Updaterscript
-head into meta-inf > com > google > android in both roms, and open the updater-script with Notepad ++(use google), so you can browse both scripts in one window.
- delete any lines looking like these:
Code:
assert(getprop("ro.product.device") == "ace" || getprop("ro.build.product") == "ace" || getprop("ro.product.board") == "ace" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.board") == "GT-S5830");
- Optional: you can choose ui-prints( the text you see while installing a rom in recovery) if it contains anything like ''rom for galaxy ace'', but it isn't needed.
take a break here. your meta-inf folder should be good now, even as your boot.img/kernel. now we're going to modify the system folder.
Camera and Bluetooth
- open /system on both roms.
- copy camera.apk and bluetooth.apk from GIO rom to ACE ROM in /system/app
NOTE:
- when your camera doesn't work while testing also do this:
go to /system/lib, and use CTRL+F(windows) to search. search for any called ''camera''. when the search is done copy the libs found from GIO ROM to ACE ROM in system/lib.
- some roms also have a cameradata folder located in /system. if so, delete the ace one and add a gio's. if not, skip this step.
4. Modules and HW
- now head to /system/lib on both
- replace the ''Modules'' and ''HW'' folder from GIO ROM to ACE ROM
5. Build.prop
- now go to /system and open both the build.prop's with notepadd++
- delete these lines for ACE's build.prop and add these into them from your gio build.prop
example:
Code:
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5830-user 2.3.3 GINGERBREAD DQKK6 release-keys
ro.build.fingerprint=samsung/GT-S5830/GT-S5830:2.3.3/GINGERBREAD/DQKK6:user/release-keys
TO:
Code:
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5660-user 2.3.4 GINGERBREAD DXKP6 release-keys
ro.build.fingerprint=samsung/GT-S5660/GT-S5660:2.3.4/GINGERBREAD/DXKP6:user/release-keys
- use CTRL+F to search, and search for GT-S5830. change any GT-S5830 in any line to GT-S5660.
after you changed them all search ''cooper'' and change those to ''gio''
6. Testing
if its good you are now good to go, and you can try your rom.
make a .zip of
''Meta-Inf'' - updaterscript and binary, actual commands to install in recovery
''System'' - the system folder, contains all sounds, apps, framework, etc.
''boot.img'' - the kernel
at your ACE ROM FOLDER wich you modified to work on gio.
I hope this works, as this method is how I port roms from ace.
it is only to port from ace, because the device is almost the same, but most things you modified can also be used for other roms, but need more modification.
6. Frequently Asked Questions
coming soon
<dutch mode on>
Hee, hendig!
<dutch mode off>
Nice!
Foolproof way to not having to beg for someone to ’port' some acerom I might like...
Thanx!
it would be nice and many thanks if you can make tutorial how to port roms that need resizing any framework like copper to tass
luckymouse17 said:
it would be nice and many thanks if you can make tutorial how to port roms that need resizing any framework like copper to tass
Click to expand...
Click to collapse
well I can tell you how to do it, but I don't have experience for that so than I will make a guide from a guide ..
This is very usefull. Thanks for posting!
Wow.. Some people need a guide for it ?! O.O
Btw .. Good guide .. there are many noob on xda
Frankin96 said:
Wow.. Some people need a guide for it ?! O.O
Btw .. Good guide .. there are many noob on xda
Click to expand...
Click to collapse
It is for the people that have less experience but still want to start porting, you do better do that from ace, and port the full rom instead of just 2 folders
Sent from my GT-S5660 using xda app-developers app
Yeah I know ... in case of porting miui or other rom based on cm I've done it but a bit different..
Thank u voetball now everybody could port each rom from ace.
Cheers
Sent from my GT-S5660 using xda premium
Thanks for this guide! I would like to try porting some Ace ROMS to the Gio so that I learn more about ROMs.
I wanted to make my first target Xperiatized V13, for which there was a Gio port of the previous version - V12. I thought I'd use the ported V12 of this ROM as the GIOROM and the V13 ROM from the Ace forums as the ACEROM. I unpacked both without any trouble but immediately came to a halt. V13 (the Ace ROM which I wanted to port) had a kernel file named "boot.img" but V12 (already ported) did not. The V12 ROM did have a file named "kernel".
Did I take this wrong approach or have I perhaps misunderstood the instructions?
Thanks its very useful
But what about signature?
How can sign that .zip file?
ارسال شده از GT-S5660 با استفاده از تپاتالک 2
MH-Droid said:
Thanks its very useful
But what about signature?
How can sign that .zip file?
ارسال شده از GT-S5660 با استفاده از تپاتالک 2
Click to expand...
Click to collapse
you can sign with different tools, but it is not required to get your rom booting, so its not included in the guide
by the way some good news(atleast for me); I ordered a new battery, so I will continue on projects soon, have to stop till it is delivered cuz my battery is broken...
hey ive ported gingerice from ace but its boots then its viberates and then its black screen that i can set on standby and on but theres no display also the ringtone beeps are working but theres no Display .. any help ?
got camera problem (no recording). Do you have a solution?
copy over these files from ur base rom in /lib folder:
*libcamera.so
*libcamera_client.so
*libcameraservice.so
*liboemcamera.so
*libseccamera.so
*libseccameraadaptor.so
and from base rom in /app folder
*camera.apk
Dont forget cameradatafolder
Sent from my GT-S5660 using xda app-developers app
voetbalremco said:
hey guys,
as the ace is a very simular device and multiple roms have already been ported by our devs, I would like to introduce a guide wich makes it very easy to port, as most guides take much time and some experience, but porting from a device that only has a different camera and sensors and some more(from inside), it isn't neccesairly needed..
so here's what I do:
WARNING:
im not responsible if anything goes wrong and your device will be bricked. you have been warned.
I'll be saying ''ACE rom'' to the rom you want to port from ace, and ''GIO rom'' to the rom you are going to use as base
- make a new folder and paste your rom you want to port inside, and extract it.
- if you're rom is cm7/9/ based, you should download a rom for gio that is too.
if you're rom is stock firmware based, you should download a stock based custom rom for gio.
- after you did that extract them both in seperate folders.
- it will look like this:
''Meta-Inf'' - updaterscript and binary, actual commands to install in recovery
''System'' - the system folder, contains all sounds, apps, framework, etc.
''boot.img'' - the kernel
now comes the part you need to edit some files...
- delete the kernel from ACE rom and copy GIO rom boot.img to
/aceromname
-head into meta-inf > com > google > android in both roms, and open the updater-script with Notepad ++(use google), so you can browse both scripts in one window.
- delete any lines looking like these:
Code:
assert(getprop("ro.product.device") == "ace" || getprop("ro.build.product") == "ace" || getprop("ro.product.board") == "ace" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.board") == "GT-S5830");
- Optional: you can choose ui-prints( the text you see while installing a rom in recovery) if it contains anything like ''rom for galaxy ace'', but it isn't needed.
take a break here. your meta-inf folder should be good now, even as your boot.img. now we're going to modify the system folder.
- open /system on both roms.
- copy camera.apk and bluetooth.apk from GIO rom to ACE ROM in /system/app
- now head to /system/lib on both
- replace the ''Modules'' and ''HW'' folder from GIO ROM to ACE ROM
- now go to /system and open both the build.prop's with notepadd++
- delete these lines for ACE's build.prop and add these into them from your gio build.prop
example:
Code:
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5830-user 2.3.3 GINGERBREAD DQKK6 release-keys
ro.build.fingerprint=samsung/GT-S5830/GT-S5830:2.3.3/GINGERBREAD/DQKK6:user/release-keys
TO:
Code:
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5660-user 2.3.4 GINGERBREAD DXKP6 release-keys
ro.build.fingerprint=samsung/GT-S5660/GT-S5660:2.3.4/GINGERBREAD/DXKP6:user/release-keys
- use CTRL+F to search, and search for GT-S5830. change any GT-S5830 in any line to GT-S5660.
after you changed them all search ''cooper'' and change those to ''gio''
if its good you are now good to go, and you can try your rom.
make a .zip of
''Meta-Inf'' - updaterscript and binary, actual commands to install in recovery
''System'' - the system folder, contains all sounds, apps, framework, etc.
''boot.img'' - the kernel
at your ACE ROM FOLDER wich you modified to work on gio.
I hope this works, as this method is how I port roms from ace.
it is only to port from ace, because the device is almost the same, but most things you modified can also be used for other roms, but need more modification.
I am not done with this Guide yet, I need to make it more easy to read and some other things./.
Click to expand...
Click to collapse
hello bro. hope u doing great. well firstly thnx for this lovely article. i'm playing and experimenting a lil. can i seek your help. i want to port gio or ace cyanogen mod 10 jelly bean on my galaxy fit mobile. i followed your procedure and somehow got success. but i have the image graphics re-sizing issue. it doesn't fits my screen well. can u suggest something so i can get an idea.
i would be really thankful and grateful to u if u can help me out in porting gio rom to fit. i just need few tweaks as u see i'm almost done. just need some idea or any tutorial link where i can read and do some R&D which can help me in fixing the graphics and making the gio or ace rom run on my galaxy fit s5670 mobile.
creativeguy09 said:
hello bro. hope u doing great. well firstly thnx for this lovely article. i'm playing and experimenting a lil. can i seek your help. i want to port gio or ace cyanogen mod 10 jelly bean on my galaxy fit mobile. i followed your procedure and somehow got success. but i have the image graphics re-sizing issue. it doesn't fits my screen well. can u suggest something so i can get an idea.
i would be really thankful and grateful to u if u can help me out in porting gio rom to fit. i just need few tweaks as u see i'm almost done. just need some idea or any tutorial link where i can read and do some R&D which can help me in fixing the graphics and making the gio or ace rom run on my galaxy fit s5670 mobile.
Click to expand...
Click to collapse
You need to decompile all .apks and resize the .png's
But this guide is only for ace to gio, so not included.
Search xda for tuts for that
Sent from my GT-S5660 using xda app-developers app
voetbalremco said:
Dont forget cameradatafolder
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
wait, what?
nathan-96 said:
wait, what?
Click to expand...
Click to collapse
Some roms have a folder called "cameradata".
Delete and use thle gio's one.
Preferably on stock roms.
Sent from my GT-S5660 using xda app-developers app
Related
Hi, I would like to ask you some things
How to mod the bootanimation in zip flashable rom?
How to mod the version mod and kernel credits?
...with some of my friends, we want to create a rom
Thank's to all!
Well, good luck with creating a whole new rom, youll need it, and test by yourself before releasing, but here some things:
1. Bootanimation.zip is in /system/media, you can just take the zip, open it, change the frames with your modified frames, and zip it back with store compression method
2.the build information is in the build.prop : /system/build.prop
Sent from Sony Xperia Gio
better try out and test before releasing anything!
we've had enough '''''developers''''
that thought it was easy, but failed.
even bricked some devices...
Sent from my GT-S5830 using xda premium
PORTING GUIDE By kD
Disclaimer : I'm not responsible for any damage caused to your phone due to this guide or me! if you will point over me. I will simply laugh at you!
This isn't gonna make fully functional rom port for you! it is just the start!
Prerequisites :
1.You need one ROM of LG P350 and Other ROM from the device you want to port it
2. ADB [ Please google for that! it is Universal android package ]
3. Little Mind
Now Let's start the Port
First of all
EXTRACT Both ROMS ZIP One should be P350 ROM and Other should be the ROM you want to port!
Name P350 ROM as BASE and Other Device ROM as PORT
CHANGE KERNEL:
1. Open both BASE and PORT Folders
2. Copy & Replace Boot.img file from BASE TO PORT
3. You're Done
Click to expand...
Click to collapse
NOTE NOW BELOW DONE ALL THE FOLDERS ARE LOCATED IN SYSTEM FOLDER
CHANGE BIN FILES
1. Open BASE AND PORT Bin Folders
2. Copy the below written bin files from BASE TO PORT
Code:
am
ami304d
bmgr
brcm_patchram_plus
hci_attach
fix_permissions
ime
input
monkey
pm
port-bridge
rild
servicemanager
vold
3. You're done
Click to expand...
Click to collapse
CHANGE ETC FILES:
1. Open ETC Folder in
2. Now Delete the Below written etc files from PORT
3. Now Get these etc files from BASE and Copy them to PORT
Code:
bluetooth
dhcpd
firmware
permissions
ppp
wifi
wl
apns-conf.xml
dbus.conf
gps.conf
hosts
media-profiles.xml
resolv.conf
vold.fstab
4. You're done
Click to expand...
Click to collapse
CHANGE LIBS:
1. Open lib folder in Both PORT and BASE
2. Delete the below written libs from PORT
3. Now Copy ALL the Folders and libs which are written below from BASE TO PORT
Code:
hw
egl
libauth.so
libcm.so
libbluedroid
libbluetooth
libbluetoothd
libcamera
libcameraservice
libdiag.so
libdbus.so
libdss.so
libdsm.so
libdll
libgsl.so
libgstk_exp.so
libmiscta.so
libmmgsdilib.so
libmmipl.so
libmmjpeg.so
liblog
libnv.so
libinput.so [ it is only needed for ics and above based roms ]
liboem_rapi.so
liboemcamera.so
libhardware_legacy
liboncrpc.so
libpbmlib.so
libqmi.so
libqueue.so
libril.so
libril-qc-1.so
libsensorservice
libwebcore
libwms.so
libwmsts.so
4. Yeah! You're done!
Click to expand...
Click to collapse
CHANGE USR Files
1. Open USR folder in both PORT and BASE
2. Now Change the below given folders from BASE to PORT
Code:
keylayout
keychars
3. You're done!
Click to expand...
Click to collapse
CHANGE XBIN FILES
1. Open xbin folder in both PORT AND BASE
2. Change below given xbin files from BASE TO PORT
Code:
HCIDUMP
HCITOOL
HCICONFIG
3. You're done
Click to expand...
Click to collapse
CHANGE BUILD.PROP File
1. Open both Build.prop file with Notepad of PORT AND BASE
2. Now change the below given lines from BASE TO PORT
Code:
ro.product.board=
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.manufacturer=
ro.build.product=
ro.sf.lcd_density=120
ro.sf.hw_lcd_density=120
3. You're done
Click to expand...
Click to collapse
Now Just make zip of PORT Folder contents! Now you need to sign it!
You can sign your rom with [TOOL] RegawMOD Zip Signer v1.0 | 9-28-2010 - xda-developers
If you don't sign your rom you can disable signature verification in recovery!
Now you've finished porting your first rom! I'm not 100 % that it will boot but most likely it should boot up! if it don't boots! Adb logcat is still there!
Hit thanks if you liked my work!
nc tutorials..
but i think you have to give links.
for the roms?
and put some pics and videos for complete tutorials.
bcoz for a newbies like me. its to complicated to understand.
but thanks anyway
Will do that soon thanks for recommdation :d
And yeah don't say thanks press thanks is sexy
rom2maru said:
And yeah don't say thanks press thanks is sexy
Click to expand...
Click to collapse
LOL. i already press it. sory for that .
Sent from my LG-P350 using xda premium
Anyway plz have a try porting with this menthdod :d
rom2maru said:
Anyway plz have a try porting with this menthdod :d
Click to expand...
Click to collapse
i will try it later. for now im too busy with my work.
Sent from my LG-P350 using xda premium
ohh ok no problem ;D
n1ck018 said:
nc tutorials..
but i think you have to give links.
for the roms?
and put some pics and videos for complete tutorials.
bcoz for a newbies like me. its to complicated to understand.
but thanks anyway
Click to expand...
Click to collapse
yes please, some pics and links
pd: may pass this rom to p350?: http://forum.xda-developers.com/show....php?t=1836116
rom2maru said:
THIS IS THE PORTING GUIDE FOR YOU ALL. SO GUYS YOU CAN ALSO BE ANDROID DEVELOPER.....
NOTE : THIS GUIDE IS FOR PORTING P500 ROMS TO P350 BUT ONLY OLD BASEBAND. YOU CAN TRY WITH VARIOUS DEVICES LIKE GT540 BUT P500 IS BEST FOR PORTING..
IMPORTANT : I'M NOT RESPONSIBLE FOR ANY HARM CAUSE TO YOUR PHONE. IT WILL NOT DO ANY HARM BUT THEN ALSO SAFETY IS NECCESSARY...
'''''''''''''''''''''''''''''''''''THIS WILL NOT MAKE A FULLY FUNCTIONAL ROM'''''''''''''''''''''''''''''''''''''
Code:
FIRST OF DOWNLOAD The Rom You Want to Port and One Rom For Base
NOW COPY BOTH THE ROMS SOMEWHERE
NOW EXTRACT BOTH THE ROMS
''''''''''''''''''''''''''''''''''''SO NOW THE PORTING STARTS'''''''''''''''''''''''''''''''''''''''''''' '''''''''''''''
Code:
OPEN BOTH THE FOLDERS
NOW RENAME BOTH THE FOLDER AS The rom you want port AS PORT
AND The ROM Which u take as base AS BASE
NOW OPEN BOTH PORT AND BASE FOLDER
SO GUYS NOW PORTING STARTS :
Code:
first copy this boot.img from base folder to port folder. boot.img is main
NOW OPEN THE SYSTEM > BIN FODLDER AND COPY THIS FILES FROM BASE TO PORT
Code:
am
ami304d
bmgr
brcm_patchram_plus
hci_attach
fix_permissions
ime
input
monkey
pm
port-bridge
rild
servicemanager
vold
NOW OPEN SYSTEM > ETC FOLDER AND COPY THE FOLLOWING FILES FROM BASE TO PORT BUT FIRST DELETE THIS FILES FROM PORT
Code:
bluetooth
dhcpd
firmware
permissions
ppp
wifi
wl
apns-conf.xml
dbus.conf
gps.conf
hosts
media-profiles.xml
resolv.conf
vold.fstab
THIS WERE THE ETC FOLDER FILES NOW GO TO SYSTEM > LIB FOLDER AND COPY THIS FILES FROM BASE TO PORT. BUT FIRST DELETE THAT FILES FROM PORT
Code:
modules
hw
egl
THIS THREE WERE FOLDER NOW THE LIBS. COPY IT FROM BASE TO PORT
Code:
libauth.so
libcm.so
libbluedroid
libbluetooth
libbluetoothd
libcamera
libcameraservice
libdiag.so
libdbus.so
libdss.so
libdsm.so
libdll
libgsl.so
libgstk_exp.so
libmiscta.so
libmmgsdilib.so
libmmipl.so
libmmjpeg.so
liblog
libnv.so
liboem_rapi.so
liboemcamera.so
libhardware_legacy
liboncrpc.so
libpbmlib.so
libqmi.so
libqueue.so
libril.so
libril-qc-1.so
libsensorservice
libwebcore
libwms.so
libwmsts.so
THIS WERE THE LIBS THAT WERE NEEDED FOR PORTING
NOW OPEN THE SYSTEM > USR FOLDER NOW COPY THE TWO FOLDERS FROM BASE TO PORT BUT FIRST DELETE THAT FOLD FROM PORT
Code:
keychars
keylayout
THIS WERE THE USR FILES NEEDED FOR PORT
NOW OPEN THE SYSTEM > XBIN FOLDER AND COPY THE THREE FILES FROM BASE TO PORT
Code:
HCIDUMP
HCITOOL
HCICONFIG
SO GUYS NOW THE LAST PART OF PORTING THAT IS BUILD.PROP. OPEN THE BUILD.PROP FROM SYSTEM > BUILD.PROP OPEN IT USING NOTEPAD. OPEN BOTH BASE ND PORT BOTH BUILD.PROP
NOW U NEED TO CHANGE THE FOLLOWING FROM BASE TO PORT
SO GUYS JUST CHANGE THIS FIELDS FROM BASE TO PORT AND ADD ONE LINE AT THE END
SO GUYS SAVE IT AND CLOSE BOTH THE FOLDERS. NOW YOU JUST NEED TO CREATE ZIP OF IT (DONT MAKE FOLDER ZIP MAKE CONTENTS ZIP)
AND GUYS FOR SIGNING DOWNLOAD ZIP SIGNER FROM HERE AND SIGN IT
[TOOL] RegawMOD Zip Signer v1.0 | 9-28-2010 - xda-developers
IF NOT SIGNED THEN AT THE TIME OF FLASHING TURN OFF ZIP VERIFICATION. SO GUYS YOU HAD GOT UR OWN ROM. NOW YOU ARE ANDROID DEVELOPER
Enjoy Porting !
Click to expand...
Click to collapse
your tutorials are always awesome :good:
i want to ask that can i port cm 10 of p500 to our device using cm 7 or cm 9 of our device????????????????????
if yes then.....
i tried with cm 9 but when flashing got error like getprop ro.product.name == p500 and unknown commands so what can be cause??????
pkprasanna said:
i want to ask that can i port cm 10 of p500 to our device using cm 7 or cm 9 of our device????????????????????
if yes then.....
i tried with cm 9 but when flashing got error like getprop ro.product.name == p500 and unknown commands so what can be cause??????
Click to expand...
Click to collapse
I had this error when porting a rom CM9 from p500 to p350, but I exclude this part of the update script, and the rom installed, however it is not on the screen starts Penguin.
Re: ICS
gabripop said:
I had this error when porting a rom CM9 from p500 to p350, but I exclude this part of the update script, and the rom installed, however it is not on the screen starts Penguin.
Click to expand...
Click to collapse
I have the same problem ...
prachetas13 said:
I have the same problem ...
Click to expand...
Click to collapse
I do not think there is a kernel that works legally in the CM9 p350 must be why the system does not start ...
Its a problem of updater-script.
There is a line starting with assert(getprop(.....
Delete this line...
If you find any other line starting with this then delete them also.
And you can only port roms only with same version . Like if the port rom is cm9 than base should also be cm9.
I will try this. I have bad exeperience whith another thread, only get kernel pannic and don't boot.
But your thread look s with more details.
Sent from my LG-P350 using xda app-developers app
Sir can i port
Sir Can i port CM9 From P500 or AOKP or Slim based I mean any ics based rom ? to p350 from gt540 or p500 ? If yes i would surely like to try ;D
Hi man, I use your guide and it works, only whith 2 of P500, but i have a trouble, I can't see the status bar and the screen on calls. any tip????
Thank's for all.
Porting Rom's whith you guide.
Your_girlfriend_cheats_us said:
Hi man, I use your guide and it works, only whith 2 of P500, but i have a trouble, I can't see the status bar and the screen on calls. any tip????
Thank's for all.
Click to expand...
Click to collapse
View attachment 1457794
View attachment 1457795
this are the logcat s of both Roms, I hope not being abussing you.
Thanks for all man, U R cool.
LuisAkira2301 told me that I must add libs:
libui
libsurfarcefinger
And it really works. So, It's fixed now, Thanks man, you too.
So Release it !!!!!!!!!! Man !! and Don't Forgot to Add Credits
I want to know how hard it is to make your own custom ROM. How much time will it take me and is there a good and clear guide?
Thanks
Sent from my Galaxy Nexus using xda app-developers app
First, you should read the sticky that talks about setting up and compiling aosp. It's in General. You'll need Linux.
sent from my Google Galaxy Nexus
What results are you trying to achieve by doing your own Rom?
It really isn't hard once you're set up for it. You'll need Linux which isn't a big deal cause its free just make sure if you don't straight boot to Linux you give your VM enough space to sync a repo
Sent from my Galaxy Nexus using xda premium
Thanks everybody. I am quite a noob. Anyone knows a clear guide?
Sent from my Galaxy Nexus using xda app-developers app
Creating ROM from OTA is really easy, I don't like ROMs which is built from sources so I don't never use AOSP ROMs..
Creating Rom OTA (the easy way):
Make Custom nandroid backup via Nexus toolkit: System folder and boot files "system.img" & "boot.img"
then add system.img and boot.img to .zip file and then you have to use Ubuntu to install Dsixda's Android kitchen and then add the .ZIP file to Original_update folder.
Then open menu.sh via terminal and then choose:
"1. Set up working folder from ROM"
when it asks something then always write yes, except then if it asks do you wan't to delete recovery bla bla bla...
and when it asks about the update script then select the default one "amend bla bla bla (1)"
Now it is ready to begin modifying it..
select (0) and then (11) and de-odex ROM then add init.d support, add busybox and root permissions, extract boot.img and ipen default.prop from boot_extracted folder and change the ro.secure line from 0 to 1, then it is insecured.. build boot.img from the extracted files..
then (99) build ROM..
or download apktools and modify apps, e.g. enabling rotation from default android launcher or from lockscreen..
etc.
It's easy.. but building ROM from sources is harder and requires enough good PC with 64-bit CPU..
DDd
manumanfred said:
and ipen default.prop from boot_extracted folder and change the ro.secure line from 0 to 1, then it is insecured..
Click to expand...
Click to collapse
Wrong, ro.secure=0 IS already insecure.. And another tip: ccache.
Lol... This is a Nexus, why don't you like to build from source? That's a joke, right? Seems to me that you are holding it wrong.
sent from my Google Galaxy Nexus
manumanfred said:
Creating ROM from OTA is really easy, I don't like ROMs which is built from sources so I don't never use AOSP ROMs..
Creating Rom OTA (the easy way):
Make Custom nandroid backup via Nexus toolkit: System folder and boot files "system.img" & "boot.img"
then add system.img and boot.img to .zip file and then you have to use Ubuntu to install Dsixda's Android kitchen and then add the .ZIP file to Original_update folder.
Then open menu.sh via terminal and then choose:
"1. Set up working folder from ROM"
when it asks something then always write yes, except then if it asks do you wan't to delete recovery bla bla bla...
and when it asks about the update script then select the default one "amend bla bla bla (1)"
Now it is ready to begin modifying it..
select (0) and then (11) and de-odex ROM then add init.d support, add busybox and root permissions, extract boot.img and ipen default.prop from boot_extracted folder and change the ro.secure line from 0 to 1, then it is insecured.. build boot.img from the extracted files..
then (99) build ROM..
or download apktools and modify apps, e.g. enabling rotation from default android launcher or from lockscreen..
etc.
It's easy.. but building ROM from sources is harder and requires enough good PC with 64-bit CPU..
DDd
Click to expand...
Click to collapse
Isn't that just modifying my current ROM with my own name?
bk201doesntexist said:
Wrong, ro.secure=0 IS already insecure.. And another tip: ccache.
Lol... This is a Nexus, why don't you like to build from source? That's a joke, right? Seems to me that you are holding it wrong.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
Building from source is a lot harder, or isn't it?
Sent from my Galaxy Nexus using xda app-developers app
It's not hard to build from source, it just takes a LONG time! Then you've gotta learn how to add mods from Gerrit code, etc. and it can be annoying.
Making a ROM using dsixda's kitchen is easier as you're using the stock image as a base so it'll work but you've then got more of a task getting new code in as you've gotta decompile it all, edit it and then recompile
mrgnex said:
Isn't that just modifying my current ROM with my own name?
Building from source is a lot harder, or isn't it?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yep, then you make own ROM from the stock ROM..
Building ROM from source is different thing and harder..
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
bk201doesntexist said:
Wrong, ro.secure=0 IS already insecure.. And another tip: ccache.
Lol... This is a Nexus, why don't you like to build from source? That's a joke, right? Seems to me that you are holding it wrong.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
oh yeah, sorry: from 1 to 0!
I don't like AOSP ROMs, except CM ROMs but I don't want to use CM ROM on my Nexus.
Ummm. Any ROM you compile is from source. It doesn't take a long time. My dual core 2.4 GH laptop will do it in a couple hours. There are several tutorials online. If you're willing to learn it's not that hard. Compiling aosp or cm is pretty much the same process.
Hi,
this is a thread with guide for porting ROMs from Galaxy Ace to Galaxy Y.
Step 1: Extract SGY Stock ROM to BASE folder (I used XXMB1 stock ROM)
Step 2: Extract SGA ROM what you want to port to PORT folder (I used Simplicity V5)
Step 3: Remove boot.img from PORT folder (if exist)
Step 4: Remove this lines from PORT updater-script: assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
Step 5: Go to PORT build.prop and replace this lines with stock:
ro.product.name=GT-S5360
ro.product.device=GT-S5360
ro.product.model=GT-S5360
ro.sf.lcd_density=120
Step 6: Go to PORT folder system/lib and replace these files with files from stock ROM:
libcamera.so
libcamera_client.so
libcameraservice.so
libsensorservice.so
Step 7: Go to PORT folder system/lib/hw and replace this files with files from stock ROM:
sensors.goldgish.so
sensors.cooperve.so to sensors.default.so
Step 8: Go to PORT folder system/app and replace DialerTabActivity.apk with file from stock ROM
Step 9: ZIP the PORT ROM and flash it on your phone
It will boot, but you will have some Apps FC, to fix it, resize them for LDPI.
Thanks
Will try
Nice Guide! Working...
EDIT: Can you refer me a tool for Resizing Apps :good:
A N D Y said:
Nice Guide! Working...
EDIT: Can you refer me a tool for Resizing Apps :good:
Click to expand...
Click to collapse
Nvm! For resizing use GIMP but it will create weird black lines at the outer side of the pic you need to be careful
i am using idiot! it has some problems!! >_<
A N D Y said:
i am using idiot! it has some problems!! >_<
Click to expand...
Click to collapse
Firstly, Mind your language! Secondly, We people here are not for spoonfeeding! Try, try and try then ask for help
nolinuxnoparty said:
Firstly, Mind your language! Secondly, We people here are not for spoonfeeding! Try, try and try then ask for help
Click to expand...
Click to collapse
IDIOT is a theming tool!!
EDIT: IDIOT= http://forum.xda-developers.com/showthread.php?t=1005862
A N D Y said:
IDIOT is a theming tool!!
EDIT: IDIOT= http://forum.xda-developers.com/showthread.php?t=1005862
Click to expand...
Click to collapse
LOL xD HahahahhahHaha Obiviously I think you are idioting someone.
Sent from my GT-S5360 using xda app-developers app
Can you port CM7 using this method?
TrojanHorses said:
Can you port CM7 using this method?
Click to expand...
Click to collapse
Porting CM7 Based roms is very easy their is a guide by rishabh.raj37 in the Misc Android Dev Section, its a sticky
nolinuxnoparty said:
Porting CM7 Based roms is very easy their is a guide by rishabh.raj37 in the Misc Android Dev Section, its a sticky
Click to expand...
Click to collapse
But I've heard that CM based roms are crawling with bugs, why is that?
TrojanHorses said:
But I've heard that CM based roms are crawling with bugs, why is that?
Click to expand...
Click to collapse
Because of no correct drivers for our phone
Hi everyone,
first I've done some research about this topic but couldn't find a tutorial.
As the title says, I want to create a rom based on the latest KitKat firmware CNE6.All tutorials I found wre based on aosp/cm source. Therefore you have to setup the android kitchen with Cygwin. But this doesn't apply to my concern, does it?
So what id the easiest way to create flashable zip?
Thanks in advance!
XxM4tzexX said:
Hi everyone,
first I've done some research about this topic but couldn't find a tutorial.
As the title says, I want to create a rom based on the latest KitKat firmware CNE6.All tutorials I found wre based on aosp/cm source. Therefore you have to setup the android kitchen with Cygwin. But this doesn't apply to my concern, does it?
So what id the easiest way to create flashable zip?
Thanks in advance!
Click to expand...
Click to collapse
Here some guides for your needs:
1. [GUIDE] How To Port Different Roms to Your Device - For CM, AOSP & AOKP
2. [GUIDE]How To Port ROMS to Your Device [AOSP]
3. [GUIDE] How to port ROMS
4. [GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
5. [HOW TO] Beginners Guide to Android ROM Development
6. XDA University: Building Your Own Android Rom
Good luck
Sorry but all these threads are for aosp Roms and not stock Roms.
i made my custom rom for the i9192 full s5 stuff ports and look etc etc ... just a bit to release ...the point is how to .. here is a simple guide for making a stock modded firmware
you need:
-cygwin+android kitchen
-orignal .tar.md5 firmware of the phone
-apktool(optional)(for modding apk's)
-ext4 unpacker tool
1-open the .tar file and extract "system.img.ext4" file
2-using the etx4 tool extract the contents of the file to "C:\cygwin\home\>user<\kitchen\WORKING_>rrgrrg_BND2<\system"
NOTE : text between >< is according to you (>user< == your pc username)(>rrgrrg_bnd2< == can be anything)
3-add any meta-inf folder and any boot.img with the system folder so it fools cygwin
3-add root+busybox via cygwin....&...customize your apk's and dexoed (optional)
4-copy the system folder to any other place and add a proper boot.img and a proper meta-inf folder with cwm script tada
NOTES :
- i didnt use a specific kitchen things .. just a normal kitchen enviroment with cygwin
- if you dont have a knox-free boot.img .. please find\make one so you can get rid of knox and errors
- my script is for 4.2.2 .. you need to find a how-to for kitkat symlinks\perms... partitions targets are easy to get .. if u want pm me
-i didnt use cygwin except for deoxeding ... root+busybox i added them manually via a pack pm me if you want it
Click to expand...
Click to collapse
Thanks this is really helpful but I don't want to mod anything, just pure stock rom ☺
Gesendet von meinem GT-I9195 mit Tapatalk
XxM4tzexX said:
Thanks this is really helpful but I don't want to mod anything, just pure stock rom ☺
Gesendet von meinem GT-I9195 mit Tapatalk
Click to expand...
Click to collapse
Then, flash stock with Odin and there you go. :highfive:
R_a_z_v_a_n said:
Then, flash stock with Odin and there you go. :highfive:
Click to expand...
Click to collapse
yea flash a no-knox tar and thats it
Nevermind, it's already sorted out. There are threads with kk roms.
Gesendet von meinem GT-I9195 mit Tapatalk