Cari Blog Ini

Rabu, 31 Desember 2014

[GUIDE] ODEX TO DEODEX AND DEODEX TO ODEX

1.ODEX KE DEODEX

Pastikan hh kamu sudah di root, framework-res.apk ( ada di folder system/framework ) salin apk tersebut ke folder apktool. Buka apktool.apk lalu tekan pilih framework-res.apk yang ada di folder apktool. Nanti muncul beberapa pilihan, pilih import as framework jika sudah pilih apk beserta odex nya yang mau kamu ubah ke deodex. Misalnya, Browser.apk dan Browser.odex pindahkan ke folder apktool. Decompile keduanya, buat folder dengan nama smali ( buat nya di dalam folder hasil decompile apk nya ya, misal Browser_src ) lalu pindahkan semua folder hasil decompile odex nya ke folder smali yang tadi kamu buat, terus recompile nanti muncul file baru nama-apk-nya_src.apk klik apk tersebut lalu pilih sign nanti akan muncul lagi file baru nama-apk-nya_src_sign.apk ubah nama apk tersebut ke nama semula. Proses selesai, deodex berhasil.

2.DEODEX KE ODEX

Pilih apk deodex yang ingin di rubah ke odex, misalnya Browser.apk klik apk tersebut pilih make odex lalu klik lagi pilih delete dex of apk. Proses merubah deodex ke odex berhasil.

Sebelum melakukan cara ini sebaiknya backup rom dulu lewat cwm.

Rabu, 10 Desember 2014

[GUIDE] AMAN MEMASANG TWEAK VIA INIT.D

MEMASANG TWEAK VIA INIT.D


Tweak-tweak yang diklaim bisa menambah performa, irit baterai dan sebagainya  banyak betebaran di forum-forum. Mungkin Anda akan langsung tergiur setelah membaca fitur-fitur yang mereka tawarkan. Berikut ini ada beberapa tips aman dalam memasang tweak yang berhubungan dengan init.d;
Backup
Biasakan backup dulu jika Anda tidak terlalu yakin tweak tersebut bisa 100% berhasil terpasang. Bagi yang gemar memodifikasi Android system saya anggap sudah mengenal dan sudah terinstall custom recovery pada device-nya. Jika hal ini terasa ribet untuk Anda karena setiap kali backup padahal Anda gemar utak-atik, Anda bisa melakukan full backup setiap 1 bulan sekali dan menghapus backup yang lama supaya tidak memenuhi media penyimpanan.

Custom recovery saya anggap sebagai "senjata pamungkas" yang paling simple dan manjur. Jika tidak ada custom recovery untuk device Anda, setidaknya tersedia recovery tool seperti Livesuit beserta firmware untuk device Anda masing-masing. Dengan begitu, Anda tidak perlu panik ketika system Android anda rusak.
Pelajari dan cermati
Simak baik-baik deskripsi tweak yang akan Anda pasang. Baik itu flashable zip, apk file ataupun installasi manual. Cari informasi sebisa mungkin hasil dari orang lain yang memakai device dan/atau sama dengan Anda. Jika sebagian besar mengeluh setelah memasang tweak tersebut maka hindarilah memasangnya. Dan jika Anda bersikeras jangan terkejut jika hasilnya sama.

Jika tweak tersebut berupa flashable zip, cobalah mempelajari apa yang ada pada file zip tersebut. Ekstrak dan pelajari file didalamnya terutama script-script yang ada pada folder init.d dari tweak tersebut. Hal ini untuk menghindari adanya double script jika Anda telah memasang script lain sebelumnya. Sebagai contoh zipalign script, beberapa tweak menyisipkan script ini didalamnya. Jika Anda biarkan maka proses booting akan menjadi lebih lama.
Pasang seperlunya
Hindari pemasangan tweak yang berlebihan dan jangan sekali-kali memasang 2 tweak dengan fungsi yang sama agar tidak terjadi overwrite. Bisa Anda atasi dengan point diatas (pelajari dan cermati).
Pertahankan atau Buang
Tips terakhir adalah setelah Anda merasakan efek dari tweak yang Anda pasang tersebut. Sesuai harapan, tidak ada perubahan atau malah sebaliknya.

Jangan tergantung pada nilai skor benchmark!!! Benchmarks are useless!!! Benchmark mungkin lebih tinggi setelah pemasangan tweak, tetapi apalah artinya jika hari berikutnya system menjadi tidak stabil. Anda harus mengetesnya beberapa hari untuk mengetahui hasilnya.

Jika memang sesuai harapan, gunakan tweak tersebut. Jika hasilnya bertolak belakang dan justru system menjadi tidak stabil, buanglah. Bagaimana jika tidak ada beda? Performa tidak meningkat tidak juga turun. Kalau sudah begitu, apa guna tweak tersebut dipertahankan?

Selasa, 09 Desember 2014

[ROM] FLY_UI V2 A7V+


FLY_UI V2 A7V+



.Masuk CWM recovery
.Wipe Data 
.Wipe Cache Partition
.Advanced>Wipe Dalvik Cache
.Install Zip from SD Card
.Tunggu sai selesai
.Reboot system now

Credit :
.ALLAH SWT
.XDA

.GOOGLE
.NEEDROM

Link ROM :

http://www.4shared.com/zip/Fndtfh0Kce/ROM_FlyUI_A7V.html

[ROM] COLOR_OS R829 V2 A7V+

ColorIJO R829 V2 A7V+


Feature :

.APN SETTING √
.DUAL 3G √
.ALL STORAGE SHOWING √
.INCLUD GAPPS √
.BRAVIA ENGINE 3 √
.GPU RENDERING √
.GAK ADA BAHASA CHINA DISETIAP APP √
.LOGO.BIN ColorIJO √
.CAMERA 13MP √
.NO MOD √
.ODEX ROM √
.SMOOTH √
.GAME GEDE LANCAR √
.ROOTED √

Jika masih menemukan BUGS harap LAPOR SAMSAT terdekat TQ


Credit :
ALLAH SWT
XDA
GOOGLE
NEEDROM


Link : 

http://www.4shared.com/zip/o4QTdhXJce/ROM_ColorOS_R829_V2_A7V.html

Senin, 08 Desember 2014

[ROM] MIUI FINAL StevenLiant_A7V+

MIUI FINAL A7V+

Download Lewat HH harus punya Mega.apk dlu cari di google/PS.

.Go to CWM recovery

.Wipe data
.Wipe cache partition
.Advance > Wipe dalvik cache
.Instal ZIP from SDcard
.Reboot system now

Special Thanks to :

MIUI INDIA (ansuman_karlinu)
MIUI ENGLISH
Ansuman Karlinu
Fitriyana Febriyanti

Link:
https://mega.co.nz/#!o5cWiaga!yfrOwjoe-16VI-EU8XQByJYwFVf7_SeqfU-aIBzo-EE

[PORTED ROM] MT6582 TO MT6572

Now was that so hard?? Its a Really Easy thing to d0!!

Now Come to the Hard Part!!

Porting From Different SoCs ( Ex: MT6582 to MT7572 )


Read this carefully & apply the way i say!

* Take the ROM u want to port & name it PORT!
* Take your Stock ROM & Name it Stock
* Now Replace These files from Stock to PORT--


Code:
*system/vendor
*system/usr
*system/lib/modules
*system/lib/hw
*system/lib/libncurses.so
*system/etc/firmware
*system/etc/vold.fstab
*system/etc/vold.fstab.nand
*system/etc/bluetooth


* Now Open build.prop in notepad++ & Search for this line

Code:
ro.mediatek.platform=MT65xx


Now Replace this (MT65xx) with your CPU!!

For Example

Code:
ro.mediatek.platform=MT6572


* Now Go To META-INF/google/android and open updater-script in notepad++

* Add this line between the lines of "set_perm"

Code:
set_perm(0, 0, 0644, "/system/vendor/lib/hw/gralloc.mt65xx.so");


[Replace the mt65xx with your cpu]

Example:

Code:
set_perm(0, 0, 0644, "/system/vendor/lib/hw/gralloc.mt6572.so");


* Now Go back to the Rom folder and Take the boot.img and decompile it with any bootimg-unpack tool!

* Now delete the zimage and rename boot.img-ramdisk to PORT-Ramdisk

* Now Do the Same for Stock boot.img and open the folder named PORT-ramdisk and copy all the fil PORT-[QUOTE]ramdisk to boot.img-ramdisk of your Stock boot.img

* Now Go to boot.img-ramdisk and open init.rc

* Now find these lines and replace with your cpu
Code:
#Create Chip Property
on early_property:ro.hardware=mt6582
setprop ro.mtk.hardware mt6589

on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6589



example :

Code:
#Create Chip Property
on early_property:ro.hardware=mt6582
setprop ro.mtk.hardware mt6572

on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6572



* Now Compile your New boot.img and Pack your New ROM and Flash!!

[GUIDE] FIX STORAGE PROBLEM AFTER PORTED ROM

Here is My little Guide To fix the storage problem like internal or external sdcard is not showing or mounting to PC On Ported Rom.

Quote:
Things Require :
7zip
Notepad++
Stock Rom framework-res.apk Of your Device

Quote:
Method : 7zip (easiest Way)

Quote:
extract the framework-res.apk from your Ported rom (which has storage issue) to desktop or another place

Open the framework-res.apk using 7zip

Then Go to res/xml....... here you will find storage_list.xml

Just replace the storage_list.xml with your stock rom framework-res.apk

that it close the winrar.... add the framework-res.apk to your ported rom install the rom and enjoy



Quote:
Please Note : After Using This Method on Some Rom the internal and external sdcard get swap like internal become external and external become internal.....
to fix this you have to decompile the framework-res.apk using apktool and then edit the storage_list.xml.....
in storage_list.xml ....you have to just rename the sdcard0 and sdcard1 to sdcard1 and sdcard0 vise versa receptively


Another Storage Problem Solved

For other who has allway problems to found:
The SD entry card is wrong. My external SD card is shown as internal and so, every files like cache, temp files etc. where written to external SD card.
So i have change the the vold.fstab  in system/etc. and change the this two line from:
dev_mount sdcard /storage/sdcard0 emmc@fat /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host

dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host

to
dev_mount sdcard /storage/sdcard1 emmc@fat /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host

dev_mount sdcard2 /storage/sdcard0 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host

And now, the cards are correct mounted.

[GUIDE] FIX DUAL SIM 3G

FIX DUAL SIM 3G 


1.decompile framework.jar from firmware where there is this support and framework.jar firmware where you want to add.

2.With the help of the program Beyond Compare.

3.very convenient and you can see where everything is and how it differs) open those decompiled jar files (their catalogs) to compare and you copy from framework.jar (where there is a switching function), all telephony folders in your framework. jar. This of course is not quite right and from the professionals seem very silly, but I do not know what files need to edit, so I produce stupidly replacement. After going back your framework.jar.

4.Decompile your Phone.apk and using Beyond Compare 3 compare with files from this archive (attached below) (open files that are in the archive and see how they differ from those in our Phone.apk and add these differences in the corresponding our file Phone.apk).

5.Compile Phone.apk. Now replace our new framework.jar and Phone.apk.
If interested in this platform mtk6589 I can advise simply port the firmware from Jiayu G5, there comes already integrated switch.
Then go multilingual assembly each week.

[PORTED ROM] MEDIATEK ALL CHIPSET

PORTED ROM MEDIATEK


* Take the ROM u want to port & name it PORT!
* Take your Stock ROM & Name it Stock
* Now Replace These files from Stock to PORT.


/system/app:
Bluetooth.apk → To fix the bluetooth problem
Phone.apk → To fix the proximity sensor issue
Added liquid settings & GApps

/system/bin:
Since you probably use the old sensor, you need to add all the *_yamaha files.
brcm_patchram_plus → To fix the bluetooth
dhcpcd
netd → To fix the wifi hotspot (you MUST change also /lib/libhardwarelegacy.so too, else you will get a bootloop)
rild → To get the network working
servicemanager → To get the sensors working
vold → To get the vold working

/system/etc:
the entire firmware folder to get wifi and sensors working
the init.d folder to tweak the rom
the permissions folder, added missing xmls
the entire wifi folder to get the wifi working
gps.conf → To improve the GPS
hosts → To fix ads
media_profiles.xml → To fix problems with camera and camcorder
vold.conf and vold.fstab → To fix vold, if you don't change them the rom won't boot.

/system/framework:
Added com.google.android.maps.jar to fix problems with the apps which uses GMaps.
You can find there the files to tweak with smali to get some stuff working. For example, if you want to get the prox. sensor working well, you need to edit the PowerService class in services.jar.

/system/lib:
the entire egl folder
the entire hw folder
the entire modules folder
all the libOmx* .so files → To get the camcorder working
all the libaudio* .so files → To get the audio working (if you don't change them, it won't boot)
libandroid.so
libauth.so
libcamera.so and libcameraservice.so → These depends on the ROM.
libcm, libcommondefs.so, libdiag.so, libdll.so, libdsm.so, libdss.so, libeffects.so, libg*.so
libhardare_legacy.so
libloc*.so
liblog.so
libmedia.so
libmmgsdilib.so, libmmipl, libmmjpeg.so, libnfc_ndef.so, libnv.so
libms3c_yamaha.so → To fix the sensors
liboemcamera.so → To fix the camera & camcorder
liboncrpc.so, libpbmlib.so, libqmi.so, libqueue.so
libril*.so
librtp_jni.so
libsensor*.so
libspeech.so
libsqlite_jni.so
libstagefright_*.so → These are usually not required
libt99.so
libvoicesearch.so
libwebcore.so
libwms.so
libwmsts.so

/system/sd:
The placeholder file. → To get sd working

/system/usr:
the entire 'keychars' and 'keylayout' folders

/system/vendor:
The entire folder.

/system/etc" and delete only these files and directories.
vold.fstab
/wifi
/ppp