im port cm9.1 latest stable,,,its very good ,,,fast,,smooth too,,,but auto dim isnt not working,,,how to get it working???
great man.
auto brightness not working may be sensor files are missing, I noticed same issue in cm10 by rcset.
elol we need you for solving this
ryan just upload your ROM please
not worried much about auto brightness
reversegear said:
great man.
auto brightness not working may be sensor files are missing, I noticed same issue in cm10 by rcset.
elol we need you for solving this
ryan just upload your ROM please
not worried much about auto brightness
Click to expand...
Click to collapse
my connection is very slow for upload bro,,,but u can try this alone,,its easy,,,,just go to cynanogen site,,,download latest cm 9.1 for xperia arc(anzu) or latest nightly,,,,,next follow my tutorial above,,,take file from cm9 rc2 by rcset
META-INF - delete and replace all folder
edit build.prop or replace
replace boot.img
system/bin - replace and add dif files
applypatch
btwlancoex
geomagneticd
hci_qcomm_init
hlr_auc_gw
hostapd
hostapd_cli
lightd
nt_password_hash
orientationd
port-bridge
proximityd
recovery
rild
rmt_storage
vold
wpa_supplicant
system/etc
firmware - delete and replace all folder
permissions - delete and replace all folder
- add or replace
init.qcom.bt.sh
init.qcom.fm.sh
init.qcom.sdio.sh
init.qcom.wifi.sh
loc_parameter.ini
vold.fstab
system/framework
framework-res.apk - mod vibrate
services.jar - fix headset
system/lib - add or replace
libandroid_runtime.so
libcamera.so
libcamera_client.so
libcm.so
libgps.so
libhardware_legacy.so
libmmjpeg.so
liboemcamera.so
libril.so
libril-qc-1.so
- and add all dif files from base work
system/lib/hw - add
camera.fb0.so
gps.fb0.so
lights.fb0.so
sensors.fb0.so
system/lib/modules - delete and replace all folder
system/usr - replace all folder
idc
keychars
keylayout
its tutorial from rcset,,,if you follow this,,im guarantee you will be sucsess...keep spirit
From what device ROM you have ported??I use crespo device,but failed,stuck on splash.img
Sent from my Spice Mi-410 using Tapatalk 2
Arya_3RDNumber said:
From what device ROM you have ported??I use crespo device,but failed,stuck on splash.img
Sent from my Spice Mi-410 using Tapatalk 2
Click to expand...
Click to collapse
try change libhardware_legacy.so cm9 mtdev latest or take from my ported IceColdSandwicth V8.7....use rom htc Sensation ''pryamid'' base rom to need porting rom cm9,it will easy you..
---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------
ryanroxx said:
my connection is very slow for upload bro,,,but u can try this alone,,its easy,,,,just go to cynanogen site,,,download latest cm 9.1 for xperia arc(anzu) or latest nightly,,,,,next follow my tutorial above,,,take file from cm9 rc2 by rcset
META-INF - delete and replace all folder
edit build.prop or replace
replace boot.img
system/bin - replace and add dif files
applypatch
btwlancoex
geomagneticd
hci_qcomm_init
hlr_auc_gw
hostapd
hostapd_cli
lightd
nt_password_hash
orientationd
port-bridge
proximityd
recovery
rild
rmt_storage
vold
wpa_supplicant
system/etc
firmware - delete and replace all folder
permissions - delete and replace all folder
- add or replace
init.qcom.bt.sh
init.qcom.fm.sh
init.qcom.sdio.sh
init.qcom.wifi.sh
loc_parameter.ini
vold.fstab
system/framework
framework-res.apk - mod vibrate
services.jar - fix headset
system/lib - add or replace
libandroid_runtime.so
libcamera.so
libcamera_client.so
libcm.so
libgps.so
libhardware_legacy.so
libmmjpeg.so
liboemcamera.so
libril.so
libril-qc-1.so
- and add all dif files from base work
system/lib/hw - add
camera.fb0.so
gps.fb0.so
lights.fb0.so
sensors.fb0.so
system/lib/modules - delete and replace all folder
system/usr - replace all folder
idc
keychars
keylayout
its tutorial from rcset,,,if you follow this,,im guarantee you will be sucsess...keep spirit
Click to expand...
Click to collapse
if you use base ''anzu'' you will not get unmount and mount usb working..
Arya_3RDNumber said:
From what device ROM you have ported??I use crespo device,but failed,stuck on splash.img
Sent from my Spice Mi-410 using Tapatalk 2
Click to expand...
Click to collapse
im take base from xperia arc,,i think ist better because have same gpu
elol said:
try change libhardware_legacy.so cm9 mtdev latest or take from my ported IceColdSandwicth V8.7....use rom htc Sensation ''pryamid'' base rom to need porting rom cm9,it will easy you..
---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------
if you use base ''anzu'' you will not get unmount and mount usb working..
Click to expand...
Click to collapse
do you mean mount usb on cwm????i dont test it,,but usb storage its working good,,,
buy hey elol,,very nice to see u in fb0 thread,,:good:
elol can u teach me,,how to get auto dim working??
you need complie framework-res.apk then open array.xml compare framework fb0 ics with framework what do you want to porting
oh ...
Sent from my SH8188U using xda premium
Related
Lets discuss about ROM port guidance for dummies like me. Hope it will help others also who want to port it.
Here is my experience for porting several MIUI in my phone, shall other to make it perfect.
First we must have a source rom to port. Desire HD is my chosen since it has some similar hardware.
I replace the source rom using several files from the previous working MIUI rom.
I never mix framework with any other files from previous miui version, I just patch framework.jar and services.jar (decompile and recompile). And for system app files I let them as is, except for torch.apk taken from 1.11.11 and systemUI.apk with manual patch (decompile and recompile).
I use the same driver modules files in every my port (wifi, sensor, light, gps), the rest drivers are compiled in the kernel so we can't touch them except if we can build from source. I use almost the same library in every port. ( You can see the same files from my 2.2.3 and my 2.3.9)
The other files are came from the source dhd rom and additional apps taken from other rom or any mod as long as they're not accessing the hardware directly.
And for the kernel, lately I use SDKernel and mOCK kernel. I've modified both boot image of them. At 2.3.9 as you knew, I use modded SDKernel, I've change default cpu clock and also bringing up the fm radio service in it. And for my current miui (2.3.16) I'm using mOCK kernel, I've change the default cpu clock also, but not bringing up fm service (since I've not succeded yet using FM radio).
Here are some files I don't use from source rom (replace by following files):
- Torch.apk
- hciattach
- netd
- wpa_supplicant
- liba2dp
- libc****
- libcamera
- libcamera_service
- libffmpeg
- libgemini
- libhardware_legacy
- libmmipl
- libmmjpeg
- liboemcamera
- libril
- librpc
- libskia
- libwebcore
- vold
- vold.stab
- btwlancoex
- compassd
- geomagneticd
hci_qcomm_init
hostapd
hostapd_cli
lightd
load_wifi
modempre
netmgrd
nt_password_hash
oem_rpc_svc
orientationd
port-bridge
proximityd
pwgen
qmuxd
rmt_oeminfo
zipalign
all files from system/etc/firmware/wlan
some files in init.d script, I use just hostapd, tweak sdcard read and zipalign. The rest setting I let the default config.
init.qcom.xxx
loca_parameter.ini
wpa_supplicant.conf
all files from /system/lib/hw and /system/lib/modules from previous port ( taken from 1.11.11 and triumph if I'm not wrong... not exactly remembered)
libaudio***
libauth
libcm
libcommondefs
libdiag
libdll
libdsi_netctrl
libdsm
libdsmutils
libgsd**
libidl
libloc***
libmmgsdilib
libnetmgr
libnv
liboem_rapi
liboncrpc
libOpenVG
libpbmlib
libposteffect
libqdp
libqmi
libqueue
libreference-ril
libril***
libwms**
and also all file in /system/usr/keychars and /system/usr/keylayout
If I'll change kernel, then I'll change wifi lib also which work with it.
And add some addons... not related to the core.
wpa_supplicant.conf, gps.conf, build.prop are changed as needed
I think those files are sufficient to make a new port...
Tools to decompile and recompile apk and jar files is apktool, you can use apkmultitool from apkmultitool.com.
How to fix headset:
Decompile services.jar, use this command line;
apktool d services.jar
You'll find services.jar.out folder as output. Find HeadsetObserver.smali file and replace any "h2w" word with "headset_sensor". Use notepad++ to do it. And recompile using this command line:
apktool b services.jar.out
Find the new compiled file at services.jar.out/dist folder.
How to fix native wifi tether and haptic feedback:
The file need to modify is framework-res.apk. You can do the same to decompile and recompile just like fixing headset. Decompile the file and find array.xml in framework-res.out/res/values. Find "wl.0" replace with "softap.*". You'll easily find the level values pattern for haptic feedback in the same file. The pattern values is "off,on,off,on" format to turn off and turn on vibrate in milisecond. Recompile again.
The new compiled file can not be used yet, you should restore the META-INF folder and AndroidManifest file from the original framework-res.apk file. Use 7zip application to open both old and new framework-res.apk and drag META-INF folder and AndroidManifest file to the new compiled framework-res.apk then it ready to use.
Happy porting......!!!
I'll update this post if there are some more useful...
Any suggestion are welcome...
Thank you very much for this. Will surely help newbies like me
FR... I got an idea... if there is an app which will do just like your future release miui kitchen BUT it run in device, so it will have an OTA update, how cool....! I want to help to port it to an android app (apk file), but I just only have several hours in a week for this fun.
I have already scripted what you have written in the first post.
What needs to be done with the framework files?
Free Radical said:
I have already scripted what you have written in the first post.
What needs to be done with the framework files?
Click to expand...
Click to collapse
I think we have to let the original theme and standard apps, the customization is optional due to different need of users. (For example you and me could be like beat audio or maybe not).
For the headset, you have to decompile service.jar, open headsetobserver.smali (i forgot for the exactly name) and change every "h2w" word to "headset_sensor" then recompile, then headset will work.
Sent from my CSL-MI410 with my MIUI 2.3.16 using tapatalk
The kitchen app shall be ready in a day or two.
Shall experiment later when I return home.
Btw, what to change in the framework folder?
Also, you need to mention in your guide that the proprietary hw, keylayout,keychar, module files need to be preserved.
I have pmed zuk regarding his set of proprietary fih/fb0 files so that we can make a skeleton framework to be used for cooking every Rom.
Sent from my Spice MI-410 on my rom!
Free Radical said:
The kitchen app shall be ready in a day or two.
Shall experiment later when I return home.
Btw, what to change in the framework folder?
Also, you need to mention in your guide that the proprietary hw, keylayout,keychar, module files need to be preserved.
I have pmed zuk regarding his set of proprietary fih/fb0 files so that we can make a skeleton framework to be used for cooking every Rom.
Sent from my Spice MI-410 on my rom!
Click to expand...
Click to collapse
Service.jar is in framework folder FR. My prev post mention the change of this file.
Yes, any files in hw,modules,keychar and keylayout folder at the source rom should be deleted and replaced by files from the working rom.
The skeleton for other rom willbe different. You have to make different folder for skeleton files for different rom. Several are the same files, but separating them will make you easier to manage. So the list file names is not too important, just put them in the folder will be enough. Sorry .... Just my though...
Sent from my CSL-MI410 with my MIUI 2.3.16 using tapatalk
AND LADIES & GENTLEMEN... WE HAVE LIFT OFF!!!!!!!!!!!
REJOICE.
I have made an automatic miui rom porter.
I am calling the app F-CuK-R
Thank you CK, edowar, zuk and elol.
Just booted up 2.3.16 successfully. Ported using my app (Testing the rom it churned out. I am hoping native wifi tethering is fixed)
Shall upload after midnight.
Now we can have MIUI GB release the same day after every official release
Although I must confess a lot of the files I am using are missing in this post.
but fear not, I shall make them public as soon as the app is ready for prime time with a nice gui.
Made the list after several failed experiments over the last week. Finally a simple file comparison (using a script I made) between the official MIUI release and the original 1.11.11 release helped.
Free Radical said:
AND LADIES & GENTLEMEN... WE HAVE LIFT OFF!!!!!!!!!!!
REJOICE.
I have made an automatic miui rom porter.
I am calling the app F-CuK-R
Thank you CK, edowar and zuk.
Just booted up 2.3.16 successfully. Ported using my app (Testing the rom it churned out.)
Shall upload after midnight.
Now we can have MIUI GB release the same day after every official release
Although I must confess a lot of the files I am using are missing in this post.
but fear not, I shall make them public as soon as the app is ready for prime time with a nice gui.
Made the list after several failed experiments over the last week. Finally a simple file comparison (using a script I made) between the official MIUI release and the original 1.11.11 release helped.
Click to expand...
Click to collapse
Greaattt FR... Can't wait to taste it....!!!!
Sent from my CSL-MI410 with my MIUI 2.3.16 using tapatalk
I guess I spoke too soon.
My port again has an issue with the headset. :sigh: back to the drawing board
sorry FR, for not replying for your PM. I was away for internet for some time...!!
You have already done a really Good job. I should say, really quick...!!
This will real Good deal for MIUI lover's.
Good Luck...!!
Can someone enumerate changes to be done to systemUI, android.policy, framework.jar and framework-res in different mods so that I can script them for my cooker?
Sent from my Spice MI-410 on my MIUI 2.3.16 port
CacingKalung said:
Lets discuss about ROM port guidance for dummies like me. Hope it will help others also who want to port it.
Here is my experience for porting several MIUI in my phone, shall other to make it perfect.
First we must have a source rom to port. Desire HD is my chosen since it has some similar hardware.
I replace the source rom using several files from the previous working MIUI rom.
I never mix framework with any other files from previous miui version, I just patch framework.jar and services.jar (decompile and recompile). And for system app files I let them as is, except for torch.apk taken from 1.11.11 and systemUI.apk with manual patch (decompile and recompile).
I use the same driver modules files in every my port (wifi, sensor, light, gps), the rest drivers are compiled in the kernel so we can't touch them except if we can build from source. I use almost the same library in every port. ( You can see the same files from my 2.2.3 and my 2.3.9)
The other files are came from the source dhd rom and additional apps taken from other rom or any mod as long as they're not accessing the hardware directly.
And for the kernel, lately I use SDKernel and mOCK kernel. I've modified both boot image of them. At 2.3.9 as you knew, I use modded SDKernel, I've change default cpu clock and also bringing up the fm radio service in it. And for my current miui (2.3.16) I'm using mOCK kernel, I've change the default cpu clock also, but not bringing up fm service (since I've not succeded yet using FM radio).
Here are some files I don't use from source rom (replace by following files):
- Torch.apk
- hciattach
- netd
- wpa_supplicant
- liba2dp
- libc****
- libcamera
- libcamera_service
- libffmpeg
- libgemini
- libhardware_legacy
- libmmipl
- libmmjpeg
- liboemcamera
- libril
- librpc
- libskia
- libwebcore
- vold
- vold.stab
- btwlancoex
- compassd
- geomagneticd
hci_qcomm_init
hostapd
hostapd_cli
lightd
load_wifi
modempre
netmgrd
nt_password_hash
oem_rpc_svc
orientationd
port-bridge
proximityd
pwgen
qmuxd
rmt_oeminfo
zipalign
all files from system/etc/firmware/wlan
some files in init.d script, I use just hostapd, tweak sdcard read and zipalign. The rest setting I let the default config.
init.qcom.xxx
loca_parameter.ini
wpa_supplicant.conf
all files from /system/lib/hw and /system/lib/modules from previous port ( taken from 1.11.11 and triumph if I'm not wrong... not exactly remembered)
libaudio***
libauth
libcm
libcommondefs
libdiag
libdll
libdsi_netctrl
libdsm
libdsmutils
libgsd**
libidl
libloc***
libmmgsdilib
libnetmgr
libnv
liboem_rapi
liboncrpc
libOpenVG
libpbmlib
libposteffect
libqdp
libqmi
libqueue
libreference-ril
libril***
libwms**
and also all file in /system/usr/keychars and /system/usr/keylayout
If I'll change kernel, then I'll change wifi lib also which work with it.
And add some addons... not related to the core.
wpa_supplicant.conf, gps.conf, build.prop are changed as needed
I think those files are sufficient to make a new port...
I'll update this post if there are some more useful...
Any suggestion are welcome...
Click to expand...
Click to collapse
How do you decompile and recompile service.jar n framwork.jar???
nitin1978 said:
How do you decompile and recompile service.jar n framwork.jar???
Click to expand...
Click to collapse
I have added how to fix the headset, haptic feedback and native wifi tether at the first post including how to decompile and recompile files.
Happy porting....!!!
Sent from my CSL-MI410 using Tapatalk
thanks bro...
good evening everybody god bless you all...
okay straight to topic,anyone knows how to hack/tutorial taking picture with power button on stock camera?? like emanoN ROM did thanks
__________________________________________
solved,thanks to adib_17
Junnie said:
good evening everybody god bless you all...
okay straight to topic,anyone knows how to hack/tutorial taking picture with power button on stock camera?? like emanoN ROM did thanks
Click to expand...
Click to collapse
open emanon rom's zip file from there copy camera app and paste it in your current rom
dhlalit11 said:
open emanon rom's zip file from there copy camera app and paste it in your current rom
Click to expand...
Click to collapse
the ROM is odexed,can it ?
Junnie said:
the ROM is odexed,can it ?
Click to expand...
Click to collapse
if your rom is deodex:
first deodex emanoN5 then open camera.apk and drag classes.dex to your desktop.
put this classes to your camera app. use 7-zip for put classes.dex file
i test on godell rom and work perfect without bug or force close
helped! ty
adib_17 said:
if your rom is deodex:
first deodex emanoN5 then open camera.apk and drag classes.dex to your desktop.
put this classes to your camera app. use 7-zip for put classes.dex file
i test on godell rom and work perfect without bug or force close
Click to expand...
Click to collapse
where I can find the classes.dex?? or can you give me the camera.apk deodexed?? I need it bro
pull camera.apk with from emanon zip file
rename camera.apk to Cramer.zip file open it from there take out classes.dex file and copy it to your desktop copy your current camera app to desktop rename it to camera.zip and open it from there delete classes.dex and copy the previous one to new camera app
rename the modified camera.zip to camera.apk and resign it with zipsigner 2
dhlalit11 said:
pull camera.apk with from emanon zip file
rename camera.apk to Cramer.zip file open it from there take out classes.dex file and copy it to your desktop copy your current camera app to desktop rename it to camera.zip and open it from there delete classes.dex and copy the previous one to new camera app
rename the modified camera.zip to camera.apk and resign it with zipsigner 2
Click to expand...
Click to collapse
no man emanoN rom is odex ... and don't sign system app.
here classes.dex
extract rar file the dex file in that. put in your camera app with 7-zip (better use this progeram, it's free software)
Do't forgot backup your rom!!!
adib_17 said:
no man emanoN rom is odex ... and don't sign system app.
here classes.dex
extract rar file the dex file in that. put in your camera app with 7-zip (better use this progeram, it's free software)
Do't forgot backup your rom!!!
Click to expand...
Click to collapse
wow,thanks mate +1 for you then where i put the classes.dex ?? thanks
adib_17 said:
no man emanoN rom is odex ... and don't sign system app.
here classes.dex
extract rar file the dex file in that. put in your camera app with 7-zip (better use this progeram, it's free software)
Do't forgot backup your rom!!!
Click to expand...
Click to collapse
oh just for knowledge can you tell me what is the difference between classes.dex of an odex and deodex app
---------- Post added at 12:00 PM ---------- Previous post was at 11:58 AM ----------
dhlalit11 said:
oh just for knowledge can you tell me what is the difference between classes.dex of an odex and deodex app
Click to expand...
Click to collapse
as soon as you open the camera app you will see classes.dex file just replace with the one you have downloaded
dhlalit11 said:
oh just for knowledge can you tell me what is the difference between classes.dex of an odex and deodex app
---------- Post added at 12:00 PM ---------- Previous post was at 11:58 AM ----------
as soon as you open the camera app you will see classes.dex file just replace with the one you have downloaded
Click to expand...
Click to collapse
ok thanks,i find it !! haha will report later
dhlalit11 said:
oh just for knowledge can you tell me what is the difference between classes.dex of an odex and deodex app
Click to expand...
Click to collapse
when a rom is odex classes.dex convert to odex file behind that app like:
Mms.apk
Mms.odex
if you open Mms.apk you can't find any classes.dex
for de-odex rom all java code in apk. better thameing but slow boot and slow app start on coold start, more RAM use and more cpu and internal memory use.
if you open apk fine classes.dex in it.
but you can make dex file from odex file. with backsmali.jar and smali.jar.
adib_17 said:
when a rom is odex classes.dex convert to odex file behind that app like:
Mms.apk
Mms.odex
if you open Mms.apk you can't find any classes.dex
for de-odex rom all java code in apk. better thameing but slow boot and slow app start on coold start, more RAM use and more cpu and internal memory use.
if you open apk fine classes.dex in it.
but you can make dex file from odex file. with backsmali.jar and smali.jar.
Click to expand...
Click to collapse
thanks for the info
Hey guys
i made this guide for new users that want to learn something about android development and make their own custom rom
*NOTE:this guide is made for new users, and here u will only learn how to mod custom rom not how to build it from source
Things u need are:
[*]"7zip" or "winrar" or "winzip"
[*]base rom
[*]patience
[*]notepad
[*]and signer (get it here)
Things u see when extract rom:
1.META-INF
2.system
3.boot.img
U wont need to touch "META-INF" and "boot.img" so open "system" folder.
There u see many folders (and build.prop) but since this is guide for new users we gonna rely only on this folders:
app
fonts
framework
media
some other folders if u want to use scripts ˙(gonna teach u how just continue reading xD)
Now go to "app" folder
there u see many applications and maybe .odex files
here choose what u want to delete (*NOTE- if u delete application u should delete .odex file)
here is list which apps u can delete
*NOTE-make sure that if u deleted launcher that u replace it with your desired launcher
If u want to change fonts, framework and theme system ui then go to uot kitchen .U will just have to copy and replace files
build.prop
this is where u can change your roms name and add some tweaks
to change roms name u have to change this line
ro.modversion="here write your roms name"
*NOTE-without "" xD
here are some tweaks for build.prop tweaks
just copy<paste them
# Signal Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# NetSpeed Tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
# Google DNS Tweak
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Photo And Video Quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
# Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Scrolling Responsiveness
windowsmgr.max_events_per_sec=500
# Call Tweaks
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=25
mot.proximity.delay=25
# Power Save Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Performance Tweaks
ro.kernel.android.checkjni=0
ro.config.nocheckin=1
# Disables Debug Icon On Status Bar
persist.adb.notify=0
Click to expand...
Click to collapse
Scripts
to use scripts like Adrenaline™ Engine | 3.0 | or SlaidyBoost-V2.3
u just have to copy files from folders to the same folder
example for slaidy boost:
when u extract it u will see:
META-INF *folder
system *folder
navigate to "system"
and copy files from "etc" to "etc" rom
*NOTE- copy just files u see in folder not whole folder
and then copy files from "xbin" to xbin in your rom
1.Download base rom
-its best to take stock cyanogenmod that isnt already modded or some stock based
2.Extract rom with 7zip or winzip
3.Go to /./"rom"/system/app and delete apps u will replace or just delete
-its best to make rom as light as it can get (list of apps u can delete is given above)
4.Replacing bootanimation
-download bootanimation u want to use and rename it to "bootanimation"
-delete animation u find in /./"rom"/system/media and then paste bootanimation u downloaded
5.Adding scripts
-everything is explained in above post
6.Giving your rom name
-to change roms name u have to change this line in build.prop
ro.modversion="here write your roms name"
*NOTE-without "" xD
7.Adding build.prop tweaks
-explained in above post
8.Compress it in .zip
9.Sign it with signer given above
Plz also post tut for making kernel and rom from source in future
vishal007 said:
Plz also post tut for making kernel and rom from source in future
Click to expand...
Click to collapse
I dont know to build from source
but there are some guides i think
Thank you mv_style. Good source for beginners.
winkan said:
Thank you mv_style. Good source for beginners.
Click to expand...
Click to collapse
np
after u master this
things will go by them self
How to unpack boot.img
Hello.
This guide is awsome, but. How to unpack boot.img? I can't do that...
I have a backup of my Rom. Inthis backup is boot.img and recovery.img. I want to extract boot.img, because here is all folders to Rom... I did it once in DSIXDA Kitchen, but now i dont remember how do i did it
Help me plz
Filipm95 said:
Hello.
This guide is awsome, but. How to unpack boot.img? I can't do that...
I have a backup of my Rom. Inthis backup is boot.img and recovery.img. I want to extract boot.img, because here is all folders to Rom... I did it once in DSIXDA Kitchen, but now i dont remember how do i did it
Help me plz
Click to expand...
Click to collapse
dont know what u need it for
but here it is
http://forum.xda-developers.com/showthread.php?t=1494036
Filipm95 said:
Hello.
This guide is awsome, but. How to unpack boot.img? I can't do that...
I have a backup of my Rom. Inthis backup is boot.img and recovery.img. I want to extract boot.img, because here is all folders to Rom... I did it once in DSIXDA Kitchen, but now i dont remember how do i did it
Help me plz
Click to expand...
Click to collapse
Extract system.rfs !!
No need to xtract boot.img
Sent From my lovely FIT..... !! lOvE u Fit
What about Dsixda's android kitchen? Ain't that easier way to customise existing roms? And btw: Brace yourself! ****ty roms are comming!
daxdax89 said:
Brate
1. rename your unsigned zip file to "update.zip"
2. execute "sign.bat", wait for completion
3. "update-signed.zip" is your signed rom file
Koji unsigned file ?
Click to expand...
Click to collapse
taj zip od roma kaj si napravio
renameas ga u "update"
stavis u taj folder i pokrenes sign.bat
How can I add s2e and screenshot shortcut in power menu?
Another question: if I have titanium backup FCs, how can I fix that?
Man, i deleted adwlauncher.apk and i putted Sony ericsson launcher, but i renamed sony ericsson launcher.apk to adwlauncher.apk but my phone crashes on bootanimation. And i putted sladyboost and adrenaline. I used official cm 7.2
please help me!
thankz!
zarpel said:
Man, i deleted adwlauncher.apk and i putted Sony ericsson launcher, but i renamed sony ericsson launcher.apk to adwlauncher.apk but my phone crashes on bootanimation. And i putted sladyboost and adrenaline. I used official cm 7.2
please help me!
thankz!
Click to expand...
Click to collapse
what else did u do?
and try to build rom again
just follow steps
zarpel said:
Man, i deleted adwlauncher.apk and i putted Sony ericsson launcher, but i renamed sony ericsson launcher.apk to adwlauncher.apk but my phone crashes on bootanimation. And i putted sladyboost and adrenaline. I used official cm 7.2
please help me!
thankz!
Click to expand...
Click to collapse
Slaidyboost and adrenalin are not compatible with each other.
Sent from my GT-S5570 using XDA
huzzahpenguin said:
Slaidyboost and adrenalin are not compatible with each other.
Sent from my GT-S5570 using XDA
Click to expand...
Click to collapse
uhhh didnt notice that he wrote that
zarpel said:
Man, i deleted adwlauncher.apk and i putted Sony ericsson launcher, but i renamed sony ericsson launcher.apk to adwlauncher.apk but my phone crashes on bootanimation. And i putted sladyboost and adrenaline. I used official cm 7.2
please help me!
thankz!
Click to expand...
Click to collapse
You actually don't have to rename launcher, because adw settings are embedded in cm7 and it might be the problem. It's safe to remove adw and put different launcher in tho...
I've tried using cm 7.2 rc5.7 and it works perfectly!
But on CM 7.2 Official, I've tried using the same, but doesn't work.
Do i must remove sladyboost and adrenaline ?
And I can't see the .odex files.
zarpel said:
I've tried using cm 7.2 rc5.7 and it works perfectly!
But on CM 7.2 Official, I've tried using the same, but doesn't work.
Do i must remove sladyboost and adrenaline ?
And I can't see the .odex files.
Click to expand...
Click to collapse
all versions dont have .odex files
and u can only use 1 of scripts
Mr. MV, thanks for tutorial...
In my case...i just want change / substitute boot.img emanon6 with andro-id331..rom can boot and work normally but without bootanimation.. What can i do for display boot animation????
Sorrry my bad english n thx..
Lumantar Galaxy Mini Gadahan Piyambak.
many people ask me about this, and i have a very limited time to write this, so i hope you guys will appreciate what i'm going to write here.
porting rom is about replacing files in ported rom with our fih-fb0 proprietary files, which can be taken FROM ONE OF MY ROM, such as MIUI 2.4.20.
(for ics porting, u need an extracted rom from edowar's cm9, for GB rom with .35 kernel, take it from edowar's cm7.2 .35 rom)
files need to be changed:
system/bin folder:
btwlancoex
geomagneticd
hci_qcomm_init
hciattach
hostapd
hostapd_cli
lightd
netd
netmgrd
nt_password_hash
orientationd
proximityd
qmuxd
rild
rmt_storage
wpa_cli
wpa_supplicant
(for ics rom porting, u also need to change: hlr_auc_gw, port-bridge, wpdiagd)
system/etc folder:
apns-conf.xml
bluetooth folder
dbus.conf
dhcpcd folder
firmware folder
gps.conf
hosts
all init.*.sh files
(except init.local rc)
media_profiles.xml
resolv.conf
spn-conf.xml
sysctl.conf
vold.fstab
wifi folder
(please also copy file 08hostapd in system/etc/init.d folder from edowar's rom & paste it to the same folder in your new rom)
system/lib folder:
all files in system/lib/egl folder except libGLES_android.so
copy gps.msm7x30.so, lights.msm7x30.s0 & sensors.qcom.so from system/lib/hw folder of my rom & paste it in the same folder of your new rom, delete same files with original device name extension, such as gps.u8800.so
libauth.so
libc.so
libc_malloc_debug_leak.so
libc_malloc_debug_qemu.so
libcamera.so
libcamera_client.so
libcameraservice.so
libcm.so
libcommondefs.so
libdiag.so
libdll.so
libdsi_netctrl.so
libdsm.so
libdsutils.so
libgemini.so
libgsdi_exp.so
libgsl.so
libgstk_exp.so
libhardware.so
libhardware_legacy.so
libidl.so
libmmgsdilib.so
libmmipl.so
libmmjpeg.so
libnetmgr.so
libnv.so
liboem_rapi.so
liboemcamera.so
liboncrpc.so
libOpenVG.so
libpbmlib.so
libqdp.so
libqmi.so
libqueue.so
libreference-ril.so
libril-qc-1.so
libril-qcril-hook-oem.so
libril.so
libwms.so
libwmsts.so
libwpa_client.so
modules folder
(for ics rom porting, you also need to change: libC2DC.so, libscc-a2xx.so)
system/usr folder
keychars folder
keylayout folder
(idc folder too for ics rom porting)
as you all guys know, i just port roms from huawei u8800, you still can use this way to port roms from other device, such as htc dhd, for sure it works, but i cannot give guarantee about wifi.
ok. i'll write again later, maybe about build.prop & updater script changes in porting rom.
OK, DO IT YOURSELF, ENJOY!!!
Thanks bro. I have been waiting this for a long time. Will definitely try out.
Thankz mr.zuk
I'll try it
Sent from my CSL-MI410 using Tapatalk 2
zukriaksah said:
many people ask me about this, and i have a very limited time to write this, so i hope you guys will appreciate what i'm going to write here.
porting rom is about replacing files in ported rom with our fih-fb0 proprietary files, which can be taken FROM ONE OF MY ROM, such as MIUI 2.4.20.
(for ics porting, u need an extracted rom from edowar's cm9, for GB rom with .35 kernel, take it from edowar's cm7.2 .35 rom)
files need to be changed:
system/bin folder:
btwlancoex
geomagneticd
hci_qcomm_init
hciattach
hostapd
hostapd_cli
lightd
netd
netmgrd
nt_password_hash
orientationd
proximityd
qmuxd
rild
rmt_storage
wpa_cli
wpa_supplicant
(for ics rom porting, u also need to change: hlr_auc_gw, port-bridge, wpdiagd)
system/etc folder:
apns-conf.xml
bluetooth folder
dbus.conf
dhcpcd folder
firmware folder
gps.conf
hosts
all init.*.sh files
(except init.local rc)
media_profiles.xml
resolv.conf
spn-conf.xml
sysctl.conf
vold.fstab
wifi folder
(please also copy file 08hostapd in system/etc/init.d folder from edowar's rom & paste it to the same folder in your new rom)
system/lib folder:
all files in system/lib/egl folder except libGLES_android.so
copy gps.msm7x30.so, lights.msm7x30.s0 & sensors.qcom.so from system/lib/hw folder of my rom & paste it in the same folder of your new rom, delete same files with original device name extension, such as gps.u8800.so
libauth.so
libc.so
libc_malloc_debug_leak.so
libc_malloc_debug_qemu.so
libcamera.so
libcamera_client.so
libcameraservice.so
libcm.so
libcommondefs.so
libdiag.so
libdll.so
libdsi_netctrl.so
libdsm.so
libdsutils.so
libgemini.so
libgsdi_exp.so
libgsl.so
libgstk_exp.so
libhardware.so
libhardware_legacy.so
libidl.so
libmmgsdilib.so
libmmipl.so
libmmjpeg.so
libnetmgr.so
libnv.so
liboem_rapi.so
liboemcamera.so
liboncrpc.so
libOpenVG.so
libpbmlib.so
libqdp.so
libqmi.so
libqueue.so
libreference-ril.so
libril-qc-1.so
libril-qcril-hook-oem.so
libril.so
libwms.so
libwmsts.so
libwpa_client.so
modules folder
(for ics rom porting, you also need to change: libC2DC.so, libscc-a2xx.so)
system/usr folder
keychars folder
keylayout folder
(idc folder too for ics rom porting)
as you all guys know, i just port roms from huawei u8800, you still can use this way to port roms from other device, such as htc dhd, for sure it works, but i cannot give guarantee about wifi.
ok. i'll write again later, maybe about build.prop & updater script changes in porting rom.
OK, DO IT YOURSELF, ENJOY!!!
Click to expand...
Click to collapse
thanks zuk,and you forget to tell about how to make handsfree working,,[remember dont forget to extract the service.jar at system/framework,open the class.dex and change the line h2w to make handsfree working]....to make easy handfree working,if you porting from rom base cm7,you can take class.dex on service.jar from rom cm7 edowar,yash and me,just extract the service.jar and take the class.dex and put the class.dex on service.jar base rom you want porting,and make it sign in the service.jar..DONE..this toturial can be use on rom CM7 and MIUI..if im wrong please tell me
elol said:
thanks zuk,and you forget to tell about how to make handsfree working,,[remember dont forget to extract the service.jar at system/framework,open the class.dex and change the line h2w to make handsfree working]....to make easy handfree working,if you porting from rom base cm7,you can take class.dex on service.jar from rom cm7 edowar,yash and me,just extract the service.jar and take the class.dex and put the class.dex on service.jar base rom you want porting,and make it sign in the service.jar..DONE..this toturial can be use on rom CM7 and MIUI..if im wrong please tell me
Click to expand...
Click to collapse
Thanks for yr addition i never touch service.jar file, i hv whyzee in helping me fix the headset... this is a community, not a private limited co., we help each other. I port roms just tru' my phone, so i hv no capability to decompile & recompile .jar files
Sent from my Huawei Ideos X6 using xda premium
Changes in build.prop:
ro.product.model=U9000
ro.product.brand=huawei
ro.product.name=u9000
ro.product.device=fb0
ro.product.board=FB0
ro.build.product=fb0
ro.cm.device=fb0 (if applicable)
rild.libargs=-d /dev/smd0
ro.telephony.ril_class=fih
rild.libpath=/system/lib/libril-qc-1.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=90
Sent from my Huawei Ideos X6 using xda premium
zukriaksah said:
Thanks for yr addition i never touch service.jar file, i hv whyzee in helping me fix the headset... this is a community, not a private limited co., we help each other. I port roms just tru' my phone, so i hv no capability to decompile & recompile .jar files
Sent from my Huawei Ideos X6 using xda premium
Click to expand...
Click to collapse
nevermind mate i kown you are the best and first port the rom for device fih/fbo and thanks for you share this toturial...
---------- Post added at 03:33 PM ---------- Previous post was at 03:30 PM ----------
zukriaksah said:
Changes in build.prop:
ro.product.model=U9000
ro.product.brand=huawei
ro.product.name=u9000
ro.product.device=fb0
ro.product.board=FB0
ro.build.product=fb0
ro.cm.device=fb0 (if applicable)
rild.libargs=-d /dev/smd0
ro.telephony.ril_class=fih
rild.libpath=/system/lib/libril-qc-1.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=90
Sent from my Huawei Ideos X6 using xda premium
Click to expand...
Click to collapse
ro.tethering.kb_disconnect=1
dont forget this line to,to make wifi terther working...
Originally Posted by zukriaksah
Thanks for yr addition i never touch service.jar file, i hv whyzee in helping me fix the headset... this is a community, not a private limited co., we help each other. I port roms just tru' my phone, so i hv no capability to decompile & recompile .jar files
Sent from my Huawei Ideos X6 using xda premium
Click to expand...
Click to collapse
nevermind mate i kown you are the best and first port the rom for device fih/fbo and thanks for you share this toturial...
---------- Post added at 03:33 PM ---------- Previous post was at 03:30 PM ----------
Originally Posted by zukriaksah
Changes in build.prop:
ro.product.model=U9000
ro.product.brand=huawei
ro.product.name=u9000
ro.product.device=fb0
ro.product.board=FB0
ro.build.product=fb0
ro.cm.device=fb0 (if applicable)
rild.libargs=-d /dev/smd0
ro.telephony.ril_class=fih
rild.libpath=/system/lib/libril-qc-1.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=90
Sent from my Huawei Ideos X6 using xda premium
Click to expand...
Click to collapse
ro.tethering.kb_disconnect=1
dont forget this line to,to make wifi terther working...
Click to expand...
Click to collapse
Maybe its a necessity for htc-based roms, but not for u8800 based roms, native tether working without that line
Sent from my Huawei Ideos X6 using xda premium
zukriaksah said:
Maybe its a necessity for htc-based roms, but not for u8800 based roms, native tether working without that line
Sent from my Huawei Ideos X6 using xda premium
Click to expand...
Click to collapse
yes you right mate..who porting from another rom use this line to make wifi terther working..
edit;hye zuk what rom on you screenshoot?
elol said:
yes you right mate..who porting from another rom use this line to make wifi terther working..
edit;hye zuk what rom on you screenshoot?
Click to expand...
Click to collapse
That is miui 2.4.20 using concepto ics theme
Sent from my U9000 using xda premium
zukriaksah said:
That is miui 2.4.20 using concepto ics theme
Sent from my U9000 using xda premium
Click to expand...
Click to collapse
how about updater script changes
uemuem said:
how about updater script changes
Click to expand...
Click to collapse
later ok
Sent from my U9000 using xda premium
zukriaksah said:
That is miui 2.4.20 using concepto ics theme
Sent from my U9000 using xda premium
Click to expand...
Click to collapse
owh,need to ask you how do you get rom aurora booting?what update script are you using and what kernal are you using?
elol said:
owh,need to ask you how do you get rom aurora booting?what update script are you using and what kernal are you using?
Click to expand...
Click to collapse
no, so far aurora cannot be booted up, other ics roms that successfully booted up were honor ics demo & one of the ligux v4 version
Sent from my U9000 using xda premium
zukriaksah said:
no, so far aurora cannot be booted up, other ics roms that successfully booted up were honor ics demo & one of the ligux v4 version
Sent from my U9000 using xda premium
Click to expand...
Click to collapse
yes you right zuk,i already tried aurora but fail booted..but another ics can be booted..i think aroura use 3.3 base kernal,that is to hard give booted the rom..i need to pM mr nasptar,give he source base kernal 3.3 ics...
zukriaksah said:
no, so far aurora cannot be booted up, other ics roms that successfully booted up were honor ics demo & one of the ligux v4 version
Sent from my U9000 using xda premium
Click to expand...
Click to collapse
bro zuk have u tried the latest honor ics demo?
released 1st april i posted it on edo's AOSP thread
changes in updater scriptt:
assert(getprop("ro.product.device") == "fb0" || getprop("ro.build.product") == "fb0" || getprop("ro.product.board") == "FB0");
(some roms come only with the 1st 2 lines, some even come without getprop, so change nothing)
if ported from u8800:
format("ext4", "EMMC", "/dev/block/mmcblk0p7", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");
mount("vfat", "EMMC", "/dev/block/mmcblk0p5", "/cust");
if ported from htc devices:
format("ext4", "EMMC", "/dev/block/mmcblk0p7");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
note: these are examples, some roms may come exactly like these, some may not!
Sent from my U9000 using xda premium
zukriaksah said:
changes in updater scriptt:
assert(getprop("ro.product.device") == "fb0" || getprop("ro.build.product") == "fb0" || getprop("ro.product.board") == "FB0");
(some roms come only with the 1st 2 lines, some even come without getprop, so change nothing)
if ported from u8800:
format("ext4", "EMMC", "/dev/block/mmcblk0p7", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");
mount("vfat", "EMMC", "/dev/block/mmcblk0p5", "/cust");
if ported from htc devices:
format("ext4", "EMMC", "/dev/block/mmcblk0p7");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
note: these are examples, some roms may come exactly like these, some may not!
Sent from my U9000 using xda premium
Click to expand...
Click to collapse
Port from U8800 and flash,but error:format() expects 3 args, got4
...
(Status 7)
uemuem said:
Port from U8800 and flash,but error:format() expects 3 args, got4
...
(Status 7)
Click to expand...
Click to collapse
Can u post here the original updater script?
Sent from my U9000 using xda premium
uemuem said:
Port from U8800 and flash,but error:format() expects 3 args, got4
...
(Status 7)
Click to expand...
Click to collapse
Change this
format("ext4", "EMMC", "/dev/block/mmcblk0p7", "0");
To this
format("ext4", "EMMC", "/dev/block/mmcblk0p7");
Sent from my U9000 using xda premium
FIH-FB0
EASY WAY PORTING ROM
Hye guys,i will shared my mettod how to porting rom for fih-fb0,this mettod is very easy for you all because i will give you all vendor file for need working on device fih-fbo.....
FIRST DOWNLOAD THIS FILE .ZIP
http://d-h.st/tys
-after you finish download you will see on .zip folder like bin,etc,lib,usr and bulid.prop..what you need to do extract first what rom do you want to porting,,after done extract,,put all the file on like the same folder..after done copy-paste the file,,edit the bulid.prop ''see my bulid.prop its is the simple bulid.prop my guide porting''..after done at all use any kernal cm9 and dont forget replace the module..
-if you want need vibrate on touch working edit the framework-res.apk
**complie first the framework-res.apk
-open framework-res
-open res
-go to value
-edit arrays.xml like this
<integer-array name="config_longPressVibePattern">
<item>0</item>
<item>1</item>
<item>50</item>
<item>50</item>
</integer-array>
<integer-array name="config_virtualKeyVibePattern">
<item>0</item>
<item>20</item>
<item>30</item>
<item>50</item>
</integer-array>
<integer-array name="config_keyboardTapVibePattern">
<item>50</item>
</integer-array>
<integer-array name="config_safeModeDisabledVibePattern">
<item>0</item>
<item>1</item>
<item>20</item>
<item>31</item>
</integer-array>
<integer-array name="config_safeModeEnabledVibePattern">
<item>0</item>
<item>1</item>
<item>20</item>
<item>21</item>
<item>500</item>
<item>600</item>
</integer-array>
<integer-array name="config_scrollBarrierVibePattern">
<item>0</item>
<item>45</item>
<item>20</item>
<item>20</item>
</integer-array>
-then save it and recompli again the framework again
**for other mod you want to put at framework-res.apk,,do with you self**
**for handfree need to working**
-complie the service.jar
-then search WiredAccessoryObserver.smali
-edit this line
const-string v2, "DEVPATH=/devices/virtual/switch/headset_sensor"
aput-object v2, v1, v3
const-string v2, "/sys/class/switch/headset_sensor/state"
aput-object v2, v1, v4
const-string v2, "/sys/class/switch/headset_sensor/name"
NOW DONE
-DONT FORGET EDIT THE UPDATE-SCRIPT,,IF YOU LAZY TO EDIT THE UPDATE-SCRIPT JUST TAKE FBO UPDATE-SCRIPT AND REPLACE WHAT ROM DO YOU WANT TO TRYING PORTING..REPLACE 2 FILE..:good::good:
HAPPY PORTING
POST ON THIS THREAD IF NEED SOME HELP,I WILL HELP THE BEST TIME WITH YOU ALL
SORY IF MY ENGLISH VERY BAD:silly::silly:
Thankx
Sent from my A99 using Tapatalk 2
problem
I am trying to port aurora ics from u8800. i replaced all the files from your zip file. replaced both update and updater script and build property from CM9 RC2 by RCsET. it is flashed but when i boot it give black screen.
elol can you help where i am going wrong
Can I port ICECOLDSANDWITCH 8.8 From above method or can you suggest any rom which will be easy to port.
Tanuj Chhibber said:
I am trying to port aurora ics from u8800. i replaced all the files from your zip file. replaced both update and updater script and build property from CM9 RC2 by RCsET. it is flashed but when i boot it give black screen.
elol can you help where i am going wrong
Can I port ICECOLDSANDWITCH 8.8 From above method or can you suggest any rom which will be easy to port.
Click to expand...
Click to collapse
as far as i remember i think zuk and ck already tried to port aurora ics but never succeeded probably because it was on 3.0.8 kernel.
Sent from my CSL-MI410 using xda app-developers app
nayneshdev said:
as far as i remember i think zuk and ck already tried to port aurora ics but never succeeded probably because it was on 3.0.8 kernel.
Sent from my CSL-MI410 using xda app-developers app
Click to expand...
Click to collapse
yes you right mate,even this device have kernel 3.0..
Icecoldsandwitch 8.8
I have ported 8.8. ICECOLDSANDWITch but the problem is it goes into bootloop and only installs when installing previous rom 8.7 and boot it and then installing 8.8 everything is OK but it lags so much any solution. ?
Tanuj Chhibber said:
I have ported 8.8. ICECOLDSANDWITch but the problem is it goes into bootloop and only installs when installing previous rom 8.7 and boot it and then installing 8.8 everything is OK but it lags so much any solution. ?
Click to expand...
Click to collapse
Try extracting 8.7 and 8.8 in different folders, copy folders from 8.8 to 8.7 and merge folders and replace files. Then use a stable rom like mtdev as base and your new 8.7 folder as port and add v6 supercharger. Zip align and pack via dxdia kitchen.
Hope this helps
Urgent Help
Hi to everyone
I used this Guide
forum.xda-developers.com/showthread.php?t=1598713
and I replace full meta-INF Folder and androidruntime.so (No change to Build. Prop)
But it goes into boot loop.
Can some-one guide which files are missing and what should I DO.
Urgently required as I am Seriously trying to port some serious stuff
Tanuj Chhibber said:
Hi to everyone
I used this Guide
forum.xda-developers.com/showthread.php?t=1598713
and I replace full meta-INF Folder and androidruntime.so (No change to Build. Prop)
But it goes into boot loop.
Can some-one guide which files are missing and what should I DO.
Urgently required as I am Seriously trying to port some serious stuff
Click to expand...
Click to collapse
Do a logcat. Very simple. Download android sdk and googles USB driver from sdk. Then using terminal or command prompt navigate to that folder of the sdk and search for adb file ( for me it is in platform-tools). Then type adb logcat.
While reading logcat code, no matter what errors come, search for the 'error couldn't find native method' and read. It tells you the name of a file in the rom in an archive called framework.jar. You have to replace this file with the one in the framework.jar of the original rom. To unpack framework.jar is a process called backsmaling. Google for tutorials though I use this one :-
http://forum.xda-developers.com/showthread.php?t=1466100
You don't have to sign jar files but you need to sign apk files so its easier to do.
Also don't replace full meta inf folders. Use win merge to compare updated scripts
Hope this helps
nachiketa.ramesh said:
Do a logcat. Very simple. Download android sdk and googles USB driver from sdk. Then using terminal or command prompt navigate to that folder of the sdk and search for adb file ( for me it is in platform-tools). Then type adb logcat.
While reading logcat code, no matter what errors come, search for the 'error couldn't find native method' and read. It tells you the name of a file in the rom in an archive called framework.jar. You have to replace this file with the one in the framework.jar of the original rom. To unpack framework.jar is a process called backsmaling. Google for tutorials though I use this one :-
http://forum.xda-developers.com/showthread.php?t=1466100
You don't have to sign jar files but you need to sign apk files so its easier to do.
Also don't replace full meta inf folders. Use win merge to compare updated scripts
Hope this helps
Click to expand...
Click to collapse
Can I Port using DXIDA Kitchen.
I tried but it is not useful for updater script.
Tanuj Chhibber said:
Can I Port using DXIDA Kitchen.
I tried but it is not useful for updater script.
Click to expand...
Click to collapse
I don't know if apktool is included in dxdia kitchen. It is needed however to unpack apks and jars which is needed to port roms. I think it includes logcat tho
---------- Post added at 06:32 PM ---------- Previous post was at 06:23 PM ----------
I don't think the kitchen includes apktool to unpack and repackage jar and apk files. Most boot loops are caused by incorrect framework.jar services.jar so you can't use kitchen for that. You cannot use the kitchen to logcat either I think. I prefer to use winrar to compile and decompile roms and the kitchen to just zip align and check for errors in updated script.
---------- Post added at 06:33 PM ---------- Previous post was at 06:32 PM ----------
I don't think the kitchen includes apktool to unpack and repackage jar and apk files. Most boot loops are caused by incorrect framework.jar services.jar so you can't use kitchen for that. You cannot use the kitchen to logcat either I think. I prefer to use winrar to compile and decompile roms and the kitchen to just zip align and check for errors in updated script.