Develop Bugs

[Q] [HELP]Custom Rom Help!!!

I created a Custom rom using dsixda kitchen and all the roms work fine until i deodex them and add su permissions the rom doesnt boot and if use the boot.img file after building the custom rom i get a Status 7 error for the tmp\boot.img file
i reffered some sites it says this is a problem with the updater-script
can someone help me out with this error

yup...the problem comes from the updater script. you need to replace the updater script with the modified one. if you need to install only the rom (without the kernel) you can find one in my post. check my sig about customizing a rom. if you want to install the kernel you need to modify the script used to install the kernel. the other way, you can install the kernel separately with faqbly or mai77's method.

SSSidGGG said:
I created a Custom rom using dsixda kitchen and all the roms work fine until i deodex them and add su permissions the rom doesnt boot and if use the boot.img file after building the custom rom i get a Status 7 error for the tmp\boot.img file
i reffered some sites it says this is a problem with the updater-script
can someone help me out with this error
Click to expand...
Click to collapse
boot.img is for kernel and you can install it after installing ur rom... and yes, wenever u deodex ur rom it will show bootloop so u can manually deodex ur rom, if u add su permissions then nothing would happen.. another solution to make deodexed rom to work could be by replacing the META-INF from another rom. u can make ur kernel work by copying the META-INF from a rom which has custom kernel in it
SOURCE:i hav tried all this

I have installed the roms without the kernel but the problem is i want it to be deodexed and if i build a rom which is deodexed without the boot.img file the phone is stuck at the samsung galaxy y boot screen
can u put up a detailed explanation on how to make custom roms and all plz i really need help
i have reffered a lot of post but the only working method was of dsixda kitchen and
the roms only boot if i just rename it and build it if i add any su or deodex the phone doesnt boot

hell_lock said:
boot.img is for kernel and you can install it after installing ur rom... and yes, wenever u deodex ur rom it will show bootloop so u can manually deodex ur rom, if u add su permissions then nothing would happen.. another solution to make deodexed rom to work could be by replacing the META-INF from another rom. u can make ur kernel work by copying the META-INF from a rom which has custom kernel in it
SOURCE:i hav tried all this
Click to expand...
Click to collapse
Thanks for the help i will try it out
and another thing can u insert the uot kitchen theme to the custom rom without acctualy having to flash it again and again from the recovery

don't forget to clean your dalvik-cache after install your rom. in most cases it can causes bootloop if the dex file isn't match with the apk file.

SSSidGGG said:
Thanks for the help i will try it out
and another thing can u insert the uot kitchen theme to the custom rom without acctualy having to flash it again and again from the recovery
Click to expand...
Click to collapse
after getting the modded files from UOT kitchen u can directly flash them... no need of reflashing the rom..

I will try that and is the only solution to get rid of the bootloop caysed by deodexing

hell_lock said:
after getting the modded files from UOT kitchen u can directly flash them... no need of reflashing the rom..
Click to expand...
Click to collapse
no i meant getting the uot theme into the custom rom
like if i flash my rom the theme automatically gets flashed kind of that

SSSidGGG said:
no i meant getting the uot theme into the custom rom
like if i flash my rom the theme automatically gets flashed kind of that
Click to expand...
Click to collapse
Open zip folder you got after modding the files after that copy those files and replace the stock files with them for
eg: moded.zip>app>xxx.apk ---copy
customrom.zip>app> ---- paste and replace the old files

tried that already i get stuck at the main flash screen
thanks anyways

SSSidGGG said:
tried that already i get stuck at the main flash screen
thanks anyways
Click to expand...
Click to collapse
Sometime not all application can deodex in my case with ultimate deodex samsung keyboard n email can deodex. But when i try with dsixda kitchen email app can deodex.
Sent from my GT-S5360

^ he is right.. some apps cant be deodexed.. try installing the rom with no special features except su... then keep adding features one by one... dont put the modded files from UOT directly before flashing the custom rom cuz sometimes they can also lead to bootloop... first check whether ur rom is booting or not and then all kind of stuffs

if you replace the theme you 'must' clean your dalvik cache. please make sure that you also have delete systemUI.odex file in /system/app.

Can someone give a real detailed explanation on how to create a fll custom including themes in the rom and how to create kernel for that particular rom
and how to fix the status 7 bug even with other custom rom's lernel i get the same status 7 error some one plz help
and also how do i deodex without getting stuck for a bootloop

check my sig. you can also visit hell_lock's post about make a rom from kitchen. the only one method to solve your error 7 problem is by using meta-inf folder from other custom rom. for deodexing method you can see chamatht's post about how to deodex system app and framework.

SSSidGGG said:
Can someone give a real detailed explanation on how to create a fll custom including themes in the rom and how to create kernel for that particular rom
and how to fix the status 7 bug even with other custom rom's lernel i get the same status 7 error some one plz help
and also how do i deodex without getting stuck for a bootloop
Click to expand...
Click to collapse
this is u need
http://forum.xda-developers.com/showthread.php?t=1590330
&
http://forum.xda-developers.com/showthread.php?t=1616501

thanks for the reply but these are the two posts fom where i actually learned creating rom and hell_lock also had this status 7 problem
so guys using meta inf from other rom should be done after building the whole rom or during the working folder step

you can find a meta-inf folder in my post you can use that instead if you only want to install the rom without the kernel.

Thanks dude but when i add the meta inf folder during zipalign there is a error and guys i got go launcher ex as the launcher but it is not the default one i get an option to choose and i remember that i deleted the launcher.apk file
And the alarm is missing in my phone after installing this rom
:thumbup:
Sent from my GT-S5360 using XDA

[GUIDE][ONLY-P350]Porting Guide for LGE P350

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

Meta-inf

Hi guys i made a new Rom but i have a problem , how can i change the name in the meta-inf , if i change it i get error status 6.... how can i edit the name into meta-inf? this is the meta-inf https://mega.co.nz/#F!2R9i1R4K!AV8LFRRRkFNts2SiSHw3bw i want to change that name with XxX ROM By Savergiggio but if i do this when i flash the rom i get 6 error status...

savergiggio said:
Hi guys i made a new Rom but i have a problem , how can i change the name in the meta-inf , if i change it i get error status 6.... how can i edit the name into meta-inf? this is the meta-inf https://mega.co.nz/#F!2R9i1R4K!AV8LFRRRkFNts2SiSHw3bw i want to change that name with XxX ROM By Savergiggio but if i do this when i flash the rom i get 6 error status...
Click to expand...
Click to collapse
Hi,
If you mean the Rom version in settings--->about phone, then you must change the value of ro.build.display.id in your rom's build.prop file.
So, it should be like this in your build.prop -
Code:
ro.build.display.id=XxX ROM By Savergiggio
Good luck

abcdjdj said:
Hi,
If you mean the Rom version in settings--->about phone, then you must change the value of ro.build.display.id in your rom's build.prop file.
So, it should be like this in your build.prop -
Code:
ro.build.display.id=XxX ROM By Savergiggio
Good luck
Click to expand...
Click to collapse
No i meant in meta-inf....

savergiggio said:
No i meant in meta-inf....
Click to expand...
Click to collapse
I didn't get you.. Which file are you trying to edit?

abcdjdj said:
I didn't get you.. Which file are you trying to edit?
Click to expand...
Click to collapse
updater-script..

abcdjdj said:
I didn't get you.. Which file are you trying to edit?
Click to expand...
Click to collapse
if you open this meta-inf https://mega.co.nz/#F!2R9i1R4K!AV8LFRRRkFNts2SiSHw3bw
you can see in updater.script a name at the top and if i try to edit it i get error status 6..

can you resolve it?

savergiggio said:
can you resolve it?
Click to expand...
Click to collapse
Yes, it is a common problem. Changing the name should do no harm at all so I am guessing that it is a problem with the character encoding. Firstly, you must use only a program called Notepad++ for editing the updater-script. Then try flashing the rom.zip file. If you still get status 6 then in Notepad++ go to Edit--->EOL Conversion--->Convert to UNIX Format. Then try and let me know if it works

[GUIDE] How to port ROMs from S5830i

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

make custom rom

Hi everyone recently i install kitchen on my ubuntu Linux and i tried to modify a already modified rom but when i tried to install it ...it failed...do i need a stock rom only to modify it or i can modify a already modified rom too please help i am stuck

ashwinb143 said:
Hi everyone recently i install kitchen on my ubuntu Linux and i tried to modify a already modified rom but when i tried to install it ...it failed...do i need a stock rom only to modify it or i can modify a already modified rom too please help i am stuck
Click to expand...
Click to collapse
Hi Ashwin
No need for stock rom, u can edit the modified rom too, which phone you are using.. and what is the error you get?
Naresh

making custom rom galaxy gts5360
naresh.garapati said:
Hi Ashwin
No need for stock rom, u can edit the modified rom too, which phone you are using.. and what is the error you get?
Naresh
Click to expand...
Click to collapse
I am using samsung galaxy y gts5360 i get some script errors when i see log sometimes its error 6 and sometimes error 0 what i figured out is there is some problem with the updater-script ...also i need to know how to put apk in system/apps folder do i need to make .odex file for specific apk i put or the kitchen will create it once i put apk and also i want to integrate my choosen launcher and keyboard.Do i need to make my own updater script or modify that came with a rom?