Related
NOTE: THIS GUIDE WILL WORK ANY ANDROID DEVICE BUT HAS FEW EXTRA PRE-SUGGESTED LINKS FOR GALAXY ACE PLUS USERS.
Click to expand...
Click to collapse
Special Thanks to -
dsixda for his awesome kitchen. Please Hit Thanks button for him.
inspired by isidromxz's thread.
Please kindly remind me if i have forgotten to write any name in thanks section, i have collected all things from many many sources and with modification.
Click to expand...
Click to collapse
Who is this tutorial for?
Absolute Beginners.
People with little or no programming skills.
people who really want to learn how to make custom rom's
people who want to learn android and don't know where to start.
Click to expand...
Click to collapse
Tools Required : (Update them manually and report me dead links please)
Java JDK FROM HERE OR JAVA.SUN.COM - FOR INSTALLING CYWIGN
(WARNING: Do not install Cygwin before the JDK!!
Click to expand...
Click to collapse
Cywign Direct Download- Linux Terminal For Windows
Android Kitchen (ROM Development Tool)- For Cooking custom ROM and many more things, Please update this Kitchen to latest version when available.
Official Link to dxda's Kitchen - Official Thread and Github source. Please refer FAQ on official thread for Kitchen related problems.
Click to expand...
Click to collapse
Demo META-INF Folder Download- For Making Flashable zip files and comparing updater script.
Custom Booting.zip - for custom boot animation
notepad++ - for editing files like build.prop, updaterscript
MOST IMPORTANT TOOL YOUR BRAIN... AND ALSO LOTS OF TIME... [DOWNLOAD LINK NOT AVAILABLE...lol]
Click to expand...
Click to collapse
Step one: Installing the JAVA JDK, Cygwin and Setting up the Kitchen.
*Before you do anything install the java jdk*
Try this Dsixda Kitchen Install Picture Tutor(recommended)
OR
watch this video tutorial by gitagaire for how to setup cygwin and kitchen(recommended)
Click to expand...
Click to collapse
INSTRUCTIONS
Download and extract the cygwin_packages.zip
Run the set up(make sure there is no previous cygwin installation)
NOTE: INSTALL CYGWIN IN ROOT DISK LIKE C:\
Follow the kitchen read me txt!!!
local package directory *must* be the path to the cygwin_packages folder that you just extracted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
when it shows all the package names, go to the top and select "all default" until it changes to "all install" (you must click on the arrows)
Click to expand...
Click to collapse
Download the kitchen from above. Then, extract the kitchen's .zip file to a folder under your home account. Rename the dsixda-android-kitchen-*** folder to just "kitchen". In Cygwin, this folder would depend on what was set for your Cygwin install directory, e.g. C:\cygwin\home\John\kitchen
NOTE!! If your user folder contains spaces (e.g. C:\cygwin\home\John Smith\kitchen), then the kitchen will not function properly. Instead, copy it under C:\cygwin\home\kitchen.
Now your ready to run the kitchen type:
those who have their kitchen like this C:\cygwin\home\John\kitchen use these commands given below.
cd kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
those who have their kitchen like this C:\cygwin\home\kitchen use these commands given below.
cd ../kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you did things right you should see this:
congratulations!!
Click to expand...
Click to collapse
Step Two: Setting up a working folder
THERE ARE TOW METHODS FOR THIS.
1. WHEN YOU HAVE BASE ROM AVAILABLE.
2. WHEN YOU DON'T HAVE BASE ROM.
FIRST METHOD -
First our folder structure should look like this:
Code:
cygwin folder/home/your user name/kitchen
Inside the kitchen it should look like this:
Now we need a rom to work on, for GALAXY ACE PLUS[s7500] users i will recommend this rom by blackburner but you can use any rom.
Just Place the original rom zip in the original_update folder inside the kitchen.
run the cygwin.exe again type:
Code:
cd kitchen(enter)
./menu(enter)
now enter option 1, enter again. You should see your rom listed, choose and enter
you will be asked about changing the working folders name, at this point it makes no difference so just continue.
congratulations you have a working folder!!!
SECOND METHOD - this method is by neroyoung
FIRST MAKE A WORKING FOLDER IN CYGWIN FOLDER
IT SHOULD LOOK LIKE THIS
cygwin folder/home/your user name/kitchen/WORKING_(your rom name)
Click to expand...
Click to collapse
NOTE: FOR THIS MEETHOD WE NEED 3 FILES AND FOLDERS TO BE PLACED IN WORKING FOLDER.
1. META-INF FOLDER - GET THIS FROM DOWNLOAD FILES LIST IN FIRST POST
2. SYSTEM FOLDER - TUTORIAL BELOW
3. BOOT.IMG - TUTORIAL BELOW
2. getting system folder
(NOTE - YOU MUST BE ROOTED FOR THIS MEDHOD)
This is universal method and can be done easily using terminal emulator.
For this simply download Terminal Emulator from Android Market.
we need freshly flashed device here. OTHERWISE YOU WILL HAVE LOT OF JUNK FILES.
Open it and type:
su
tar -c system/* >> sdcard/system.tar
Click to expand...
Click to collapse
This will copy all your /system folder to your SDcard with name System.tar
This will take some time to finish so be patient.
After it's done you should have a tar file in your /sdcard named system.tar
You can extract it using Winrar or 7zip software. But yes this will have huge size , as it has other useless folders so you will have to delete them. After extracting this system.tar file you will get following folders (Similar one)
/etc
/fonts
/framework
/lib
/lost-found
/media
/sd
/semc
/usr
/xbin
build.prop
And some other files and folders like ""autorooted,kernel files" etc
Click to expand...
Click to collapse
Now simply delete the folders marked in red color and its done.Don't worry if you don't have folders with red colors above,we don't need them.
And the final files that we will have in our system folders will be
/app
/bin
/etc
/fonts
/framework
/lib
/media
/semc
/usr
/xbin
build.prop
Click to expand...
Click to collapse
If it dont have semc folder no need to worry.
NOTE: YOU CAN ALSO GET THIS SYSTEM FOLDER BY USING ANY ROOT BROWSER. JUST FIND THIS FOLDER AND COPY/EXTRACT TO SDCARD
NOW COPY THIS system FOLDER TO WORKING FOLDER
3. getting boot.img
Here we have 2 options
1. stock boot.img from stock rom - simple kernel which we get in brand new mobile.
2. custom boot.img from custom kernel - kernel which are modified for overclock or other features
1. getting stock boot.img from stock rom.
extract your stock rom with winrar or 7zip. you will see boot.img there. copy it to working folder
2. getting custom boot.img from custom kernel.
download any custom kernel which is only for your device. [galaxy ace plus [s7500] users get from here or here]
extract it with winrar or 7zip and copy boot.img to working folder
NOTE: many of new devices have kernel.bin and other files instead of boot.img so skip this part if your device don't have it...
Click to expand...
Click to collapse
Step Three :change/modify/update rom
YOU CAN MODIFY YOUR ROM IN TWO STEPS:
MODIFY USING ANDROID KITCHEN - for basic modification.
MODIFY MANUALLY. - for advanced modification.
1. MODIFYING USING ANDROID KITCHEN
watch this amazing tutorial by neroyoung on how to editing rom with kitchen
NOTE: DON'T FORGET TO DEODEX YOUR ROM
Click to expand...
Click to collapse
2. MODIFYING MANUALLY.
FOR ALL ANDROID PHONES (ESPECIALLY FOR GINGERBREAD ROMS) USE THIS GUIDE FOR COOL MODS. like center clock,CRT animation, ics and jelly bean style mods etc... ANOTHER GUIDE BY ME
Adding/removing applications
1. Go to the working folder where you extracted your rom, inside you will find:
OR
2. Then go to "system/app" inside this folder you will find all the rom applications(apks) you may also find some in the data folder if your rom has this folder.
3. Copy, replace, and change any app(apk) be carefull if you dont know what the apk is do not delete!!
LIST OF APPS YOU CAN DELETE - HERE OR HERE
If you can not find some apps in this guide then try opening all those app in your phone and see app name and icon or move those apps from system/app to sdcard and see what is not working...
Adding new boot animation
android kitchen doesn't works for this in Samsung phones. So we need a different method.
1) Download and extract the bootanimation and samsungani file from Custom Booting.zip attached in first post.
2) Put them in the /system/bin folder and replace the existing files there
3) Now download any boot animation, and rename the bootanimation to “sanim.zip”.
4) Now, navigate to /system/media and replace the “ODEanim” with “sanim.zip”
You are done with the bootanimation change
customizing the theme
1. replace stock launcher with launchers like nova launcher
2. theming using uot kitchen (fonts, status bar, batery and other icons etc
watch this amazing toutorial by jdlogan151
Click to expand...
Click to collapse
Edit the gps script for your country/location
1. In the workingfolder/system/etc/ you will find a file named gps.conf, you can
edit this file with notepad++ or even word.
2. using the right gps script in this file can speed up gps lock, you can
find some from angeldeath, download extract and replace the gps.conf.
Adding ringtones :
Take your ringtone file...it should be in .ogg format..If not then convert it to .ogg..
Locate to the folder system>media>audio>ringtones>
Copy and paste your .ogg files here in ringtones folder..
You can also change notifications, alarm and UI tones like this..
Changing the Fonts :
Take your desired font.ttf file and rename it as DroidSans.ttf..
Locate to the folder system>fonts>
Now, replace the file DroidSans.ttf with your desired DoridSans.ttf...
To change the lock screen clock font...replace the Clocktopia.ttf with your desired one..(rename first)..
build.prop tweaks!!
check this or this or this post for build.prop
NOTE: EDIT BUILD.PROP WITH NOTEPAD++. SIMPLE NOTEPAD WILL CORRUPT THE FILE.
adding mods and scripts...
download mods and scripts from links below and copy past all files in same folder as your rom... like for init.d scripts add them to system/etc/init.d/here and all permissions in updater script to your updater script...(dont forget to give them credit for it...)
links:-
[TweakZV6] Init.d best tweaks[Flashable] Increase your performance by [email protected]
Collection build.prop; init.d; etc. by optik19918
init.d Tweaks collection by dsexton702
[SCRIPTS][TWEAKS][CWM]SlaidyBoost-V2.3 by slaid480
[CWM][SCRIPTS][TWEAKS] Adrenaline™ Engine by ImbaWind
V6 SuperCharger by zeppelinrox
[SCRIPTS]CronMod-A2SD/D2EXT/INT2EXT by croniccorey
Xloud and Bravia engine by aiman112
AwesomeBEATS™ v.3 by ...Awesome...
(MOD)Beats Audio(2.3+up) by RockoDev
Tuned MegaBassBeat by kurotsugi
Maximum MultiTasking Mods + V6 SuperCharger BY zeppelinrox
[AROMA] Beats Mode - Enhanced Beats sound V7.5 by MemAllocatoR
Interactive Phone Modification [GUIDE]
ICS Style 'Settings.apk' - Make it yourself by balamu96m
StatusBar Tweaks by Master&Slave™
Change lockrings on any rom by daveyannihilation
change ICS lockscreen animation to Honeycomb style by evilisto
S Voice for any devices [ICS] by PlaYOuT
Implement Swipe to Remove Notification by hansip87
Remove SMS log from Call log by wilfredcool007
Activate the rotation of the lockscreen by GalaxyUser
How to use AROMA INSTALLER in any ROM/MOD by pankaj88
All in one tweaks build.prop,init.d,Wifi,Xloud,Bravia,A-Gps,A/V Sync,Modules by XtremePeople
Add 6 lockscreens Mod + Lockscreen Gestures by pratyush.creed
How to add customizable 14 statusbar toggle buttons for samsung ROM by lidroid
Create a custom notification dropdown by jeffsanace
these are few i love, find more yourself...
MORE WILL BE ADDED SOON...
MORE ADVANCE MODIFICATION (not advised for beginners)
editing .apk files
THERE ARE TWO BEST TOOLS FOR EDITING .APK FILES
1. APKTOOLS
This video by neroyoung teaches you how to setup APKTOOL folder as well as teaches you how to edit .apk files.
2. APK Manager
this video by adgoosuc teaches you How to unpack,repack and sign an APK File with APK Manager
Click to expand...
Click to collapse
[*]Editing .JAR Files
In this video by neroyoung you will get information on how to edit .jar files like services.jar using APKTOOL.
Click to expand...
Click to collapse
[*]THEMEING .apk FILE
HERE IS A AWESOME TUTORIAL BY Andrewtst FOR THEMEING ANY .apk FILE.
for porting themes:
1. download and extract theme you want to port.
2. open both apk(base and port) in 7zip/winrar
3. drag and replace png files with same name
this works with only png files not with xml and others
FOR THEMING YOUR ROM YOU CAN EDIT framework-res.apk AND GET MANY COOL THINGS
LIKE you can change smiles, default wallpaper, default lockscreen wallpaper, add 14 toggle mod and many cool things...
for that use Framework Flasher or apktools or any other tool and do changes manually.
CHECK THIS GUIDE BY dully79 TO KNOW WHICH FILES YOU CAN MODIFY AND HOW.
HERE ARE FEW MORE COOL GUIDES -
ICS Style 'Settings.apk' BY balamu96m
Implement Swipe to Remove Notification BY hansip87
add customizable 14 statusbar toggle buttons for samsung ROM BY lidroid
FOR MORE SEARCH MORE...
Click to expand...
Click to collapse
CHANGING HARD KEY FUNCTION (REMAPPING BUTTON)
1. open /system/usr/keylayout/[phone model]-keypad.kl with notepad++
(Some phone may have different names, but it will always end with "keypad.kl)
it will look like this --
Code:
# Copyright (c) 2011, Code Aurora Forum.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# [url]http://www.apache.org/licenses/LICENSE-2.0[/url]
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
#
key 2 1
key 3 2
key 4 3
key 5 4
key 6 5
key 7 6
key 8 7
key 9 8
key 10 9
key 11 0
key 158 BACK WAKE_DROPPED
key 230 HOME WAKE
key 60 SOFT_RIGHT WAKE
key 62 ENDCALL WAKE_DROPPED
key 229 MENU WAKE_DROPPED
key 59 MENU WAKE_DROPPED
key 139 MENU WAKE_DROPPED
key 228 POUND
key 227 STAR
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 232 DPAD_CENTER WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 103 DPAD_UP WAKE_DROPPED
key 102 ENDCALL WAKE_DROPPED
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 212 SLASH
key 213 DEL WAKE_DROPPED
key 355 DEL WAKE_DROPPED
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 14 DEL
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
key 51 COMMA
key 52 PERIOD
key 28 ENTER
key 56 ALT_LEFT
key 42 SHIFT_LEFT
key 215 AT
key 57 SPACE
key 53 SLASH
key 127 SYM
key 100 ALT_RIGHT
key 399 GRAVE
HERE YOU WILL FIND 3 ROWS...
1. As you can see, there are different attributes assigned to each key. like this
Code:
key 102 HOME
key 139 MENU
key 158 BACK
key 115 VOLUME_UP
key 114 VOLUME_DOWN
2. Specific application/action launchers:
Code:
HOME #Launches "Home"
MENU #Launches "Menu"
BACK #Takes you back to the last activity
SEARCH #Launches "Universal Search"
CALL #Launches the "Phone" activity and corresponding .apk or initiates a call
ENDCALL #Ends a call
CAMERA #Launches "Camera" activity and corresponding .apk
FOCUS #Initiates Auto-Focus while using the Camera
VOLUME_UP #Self explanatory
VOLUME_DOWN #Self explanatory
3. And attributes saying if it should wake the phone at button push to complete the action, or if it should just complete the action without waking the screen.
Code:
WAKE #Completes the action without waking the screen
WAKE_DROPPED #Wakes the phone to complete the action
Click to expand...
Click to collapse
2. NOW WE WILL EDIT SECOND AND/OR THIRD ROW
Erase the center row value for any key to completely disable it. To reassign the key, replace the center row value with another one from the same row. Change the right row value to either "WAKE" or blank to enable the wake function. Do not modify the left row.
NOTE: don't edit left row i.e. first row which contains specific key identity number.
FOR EXAMPLE I DO THESE CHANGES
DEFAULT VALUES ---
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
CHANGED VALUES ---
Code:
key 115 CAMERA WAKE
key 114 FOCUS WAKE
NOW VOLUME UP KEY WILL WORK AS CAMERA KEY AND VOLUME DOWN KEY WILL WORK AS FOCUS KEY....
NOTE: all words should be in BOLD letters i.e. capital letters...
Click to expand...
Click to collapse
MORE COMING SOON
FOR ADVANCE ROM DEVELOPMENT GUIDES (like porting rom) SEE THIS COLLECTION BY F3niX
Step Four: repackage the rom
AFTER YOU HAVE DONE ALL CHANGE/MODIFICATION YOU WANTED OPEN CYGWIN AGAIN AND TYPE
cd kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
now convert update script to updater script(in option 23)
now lets edit updater script(optional)
Thanks to user langthang for a great updater-script guide.
Download it HERE
Click to expand...
Click to collapse
the updater-script basically tells CWM what steps to take during the installation(flashing rom).
If you don't have any experience please don't edit anything other than what is in this simple tutorial.
TO EDIT UPDATER SCRIPT -
1.Go to META-INF/com/google/android
2.Open the updater-scrip file with Notepad++
3.Any text that would appear during the CWM install should be in this format :
Code:
ui_print("Put your text in HERE");
Add your text start at top and save,
then replace with new updater-scrip
IF YOU GET ANY ERROR YOU CAN COMPARE YOUR UPDATER SCRIPT WITH MINE (attached in 1st post)
NOTE: DO NOT COPY WHOLE UPDATER SCRIPT JUST EDIT PART WHERE YOU GET ANY ERROR...
most common errors will be in mount, remount part in starting and end and boot.img installing part... so replace only those lines....
AND AT LAST
[*]Now that you have made some changes it's time to pack the rom and test!!
Run the cygwin and type
cd kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
enter option 99 - "biuld rom from working folder"
Choose your build option and few more enters
I recommend that you go with all default options until you get more experience with the kitchen.
When rom is packed and signed it will ask to change rom zip name (type name of your rom)
When its all done you will find a folder inside "cygwin/home/yousername/kitchen" called output_zip
Inside the folder is your new rom ready to be flashed and tested!!!
IF YOU WANT THAN YOU CAN MAKE CWM FLASH ABLE ZIP'S MANUALLY USE THIS TOOL BY I.AM.H3RO
congratulations you have build your own rom
TROUBLESHOOTING (by hell_lock)
If you are facing java related problem with cygwin than refer to this post. and Google search
If you get problems in installing a rom then compare your updater-script in META-INF folder with one attached in first post.
If you have a rom without kernel then remove these lines:
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p8"),
delete("/tmp/boot.img"));
NOTE: mmcblk0p8 can be different with different devices... this works fine with galaxy ace plus...
If there is a package error then extract the files of the rom and repack them using any compression software.
If rom installed correctly but stuck onto logo screen?? Then remove try removing kernel and flashing rom again.
If rom installed correctly but got onto bootloop then there could be many possibilities which could lead to this. If you want accurate cause of it then do a logcat.
If there are some apk's which are not working then check if you correctly modded them.
For status errors like status error 0, status error 6, status error 7 see this guide by Tha TechnoCrat and for rest go here and type your error.
NOTE: Most of the problems occur because of updater-script problems so before trying any of the troubleshooting try the first tip.
IF YOU HAVE ANY QUESTIONS OR PROBLEMS FEEL FREE TO POST HERE OR PERSONAL MESSAGE ME.
omg all my thanks goes for you today
●๋•ηι¢є ιηƒσ●๋•
how about using dsixda, toolchain etc in linux? would u please add some tutor for that...even i guess it has the same way... i mean in ubuntu what version of dsixda that work well and what lib is needed for that? cos i have made my own kernel on my last device galaxr fit(gt-s5670) that use armv6 procie..maybe it need diferent type n bersion of tools?
thanks in advance
Sent from my GT-S7500 using xda app-developers app
Sorry i dont use lunix so i know nothing about it..... there are more threads related to this... they can help you....
Sent from my GT-S7500 using xda premium
Can i use this for micromax funbook tablet?
Yes it will work on any device... good luck
Sent from my GT-S7500 using xda premium
Had a quick read through, seems fairly easy to get started, so thanks for that!
What I want to achieve is to be able to take an existing ROM, and customise it for my organisation. I want to be able to remove the initial set up that you get when you flash a new ROM, e.g. name, Google account etc. Do you know how I would achieve this, or the files I would need to edit?
I also want to remove some APKs and preload some APKs, I think I know how to do this its just a case of replacing them in the system folder?
Also I want to preload some Wifi settings on so set it to know our SSID and PSK, is this something which is possible?
Thanks for your help!
fro5tie said:
Had a quick read through, seems fairly easy to get started, so thanks for that!
What I want to achieve is to be able to take an existing ROM, and customise it for my organisation. I want to be able to remove the initial set up that you get when you flash a new ROM, e.g. name, Google account etc. Do you know how I would achieve this, or the files I would need to edit?
I also want to remove some APKs and preload some APKs, I think I know how to do this its just a case of replacing them in the system folder?
Also I want to preload some Wifi settings on so set it to know our SSID and PSK, is this something which is possible?
Thanks for your help!
Click to expand...
Click to collapse
1st for rom you will use as base, get permission of its developers before doing it...
2nd the setup wizard you are talking about(i guess where we have to touch android) is by app in system/app named SetupWizard.apk but i think you should not delete it. it also controls few other things.
3rd replace/delete app you know about...(system/app)
4th i don't know much about preloaded settings... all i know is you will need to edit smali files of apk....
Hi
I've been playing around with this, I've extracted the ROM to a working folder and made a few changes, e.g adding and removing APKs. Then I've repackaged the ROM, but when I copy the .zip onto my SD card and try flashing it, I get an error:
Install /sdcard
Finding update package
Opening update package
Verifying Update package
E:signature verification failed
Installation aborted
I can't install CWM on this device so its just using the Android System Recovery 3e
Is there something else I have to do to get it flashable?
hiii
okay.. so first get cwm recovery as you say you dont have cwm... then while making a zip with android kitchen make sure when it ziplangs all apks then it signs your rom zip... make sure you press enter or press y and then enter...
while flashing rom with cwm you get this error again then in 'ïnstall zip from sdcard' select 'toggle signature verification' then try again if still no luck rply back....
and it seams like you used this guide and you found it helpful i guess and you dint even pressed a thanks button... i don't know why you guys enjoy all stuff and don't even press thanks button.. i am not asking you for money... it wont cost you anything...
fro5tie said:
Hi
I've been playing around with this, I've extracted the ROM to a working folder and made a few changes, e.g adding and removing APKs. Then I've repackaged the ROM, but when I copy the .zip onto my SD card and try flashing it, I get an error:
Install /sdcard
Finding update package
Opening update package
Verifying Update package
E:signature verification failed
Installation aborted
I can't install CWM on this device so its just using the Android System Recovery 3e
Is there something else I have to do to get it flashable?
Click to expand...
Click to collapse
Hi
Thanks for this, I've got it sorted now.
I can't install CWM as its not compatible with my device, but it was just that the zip needed signing for my device. I found info on another forum to sign it properly, and its flashing fine now.
Thanks for your help.
fro5tie said:
Hi
Thanks for this, I've got it sorted now.
I can't install CWM as its not compatible with my device, but it was just that the zip needed signing for my device. I found info on another forum to sign it properly, and its flashing fine now.
Thanks for your help.
Click to expand...
Click to collapse
Wich device you have?
use this to make your own cwm recovery.... http://builder.clockworkmod.com/
fro5tie said:
Hi
Thanks for this, I've got it sorted now.
I can't install CWM as its not compatible with my device, but it was just that the zip needed signing for my device. I found info on another forum to sign it properly, and its flashing fine now.
Thanks for your help.
Click to expand...
Click to collapse
androsamace said:
Wich device you have?
Click to expand...
Click to collapse
Its an Ainol Novo 7 Elf 2 (chinese tablet)
lokeshsaini94 said:
use this to make your own cwm recovery.... http://builder.clockworkmod.com/
Click to expand...
Click to collapse
I'll take a look.
HTC One X
- no ROM support, but de-odexing only! (Here is the guide to de-odex)
So i wanted to start building a ROM the easy way, guess I have to find the manual method..
i dont know what are you talking about... here is link for htc one x roms
http://onexroot.com/category/one-x-roms/
xSilv85 said:
HTC One X
- no ROM support, but de-odexing only! (Here is the guide to de-odex)
So i wanted to start building a ROM the easy way, guess I have to find the manual method..
Click to expand...
Click to collapse
Oh i mean the kitchen.. not suited for htc one x is stated in the op.
Sent from my HTC One X using Tapatalk 2
here is an edited venom Boot animation , i just removed the moving snake from it ( i hate snakes ) , so it is for any one who feel like i do
thanks to the Developer for a nice Rom
Modified Bootanimation
Update , it will work with ViperS v1.4.0 ( md5 is the same for all 3 Bootanimations for both v1.4 and v1.3.5 )
Update , i modified the Bootanimations to play better ( the whole Sensation / Sensation XE / Sensation 4G appear in the first cycle )
Update , i added both Sensation and Sensation 4G as requested by users
just push it to system \ customize \ resource ( make sure it replaced the old one ) , change permission and ownership same as the old Bootanimation .
reboot into recovery , clear dalvik cache and cache let it boot up ( you may need to do this step for a second time if it hangs in a full reboot
or just put it in your rom.zip before flashing in :
For Sensation XE and Sensation 4G , Path is extra \ model \ ( XE or 4G ) before flashing according to your choice
For Sensation , Path is system \ customize \ resource
or just use tweaks to set it as custom bootanimation
Download links
Modified Bootanimation link Sensation XE http://d-h.st/Zaa
Modified Bootanimation link Sensation 4G http://d-h.st/SIp
Modified Bootanimation link Sensation http://d-h.st/Oif
permissions link http://d-h.st/8EI
attached Permissions is also below
Modified Initial Wallpaper
if you would like to change the Snake wallpaper that appears after the initial flash of the Rom
Method 1
open rom.zip in winrar window and navigate to system \ customize \ resource
choose any htc wallpaper ( usually is named sense_wallpaper_***.jpg ) and drag it to the desktop
rename it to Viper3.jpg and drag it back to the winrar window to replace the existing Viper3
Method 2
open rom.zip in winrar window and navigate to system , and drag build.prop to the desktop
edit the build.prop using Notepad++
Original Value : dev.defaultwallpaper , value is /system/customize/resource/viper3.jpg
New Value : dev.defaultwallpaper , value is /system/customize/resource/ sense_wallpaper_***.jpg
( *** means the name of the wall paper you choose ,example sense_wallpaper_htc_default.jpg )
Save changes , drag the edited build.prop back to the winrar window to replace the existing
thanks for this, i hate snakes too
alphaz1 said:
thanks for this, i hate snakes too
Click to expand...
Click to collapse
plz modified for sensation also..........plz.....!!! plz remove xe in last 4 pic in bootanimation.zip.........plz
[Rooted Phones Only]or if you have adb or acces to root!
Hi,
so there are many threads regarding custom boot animations , but all of them are missing 1 or 2 information which others specify , so I decided to make a thread that contains all of the needed info (and of course I have a 50% chance of missing some information just as others did).
Ok so lets begin in a step by step tutorial:
Step 1
Creating Folders:
So the first thing you wanna do is make the folders where all the images are going to be located.
You can name the folders ANYTHING! and just to make it easier , don't use spaces , or else you might have to use quotation marks.
If you're creating an animation that loops , create 1 folder.
If you're creating an animation , followed by other animation that loops , then create 2 folders.
If you have multiple animations , such as : "Animation , Loop, Animation , Infinite Loop". Create as many folders as you want.
Looping doesn't mean infinite loop , you can set an animation to loop for a period of time , not necessarily forever!
Step 2
The Images:
Ok so you're gonna need to create the images in order to make them available for your device.
So you are going to decide the dimensions of your device , go to http://www.gsmarena.com/ (gsm arena , for non registered users) search for your device and under the display check your resolution , I'm gonna use 320x480 as that's my mobile's display size.
320 = width and 480 = height.
Prepare an image editing program , I'll use Photoshop , GIMP is an alternative but since I have photoshop , why not use it?
Create as many images as you want that you want them to be the animation , just like you are creating a gif , but frames are pictures , so each frame must be a different picture. Make sure you save them as .png and that they do not exceed 300 image in total.
Organize the pictures in folders , the animation into folder 1 and the looping animation into other folder , and others into other folders.
Make sure you name them in a sequence , such as : 01 02 03 , or 001 002 003 , or picture1 picture2 ...etc The devices uses Sort By Name to determine which goes first ,so the order the pictures are put in on your PC's screen ,is the same as the boot animation order.
It doesn't matter if the folders have the same or different sequence , as long as they are sequenced correctly.
Example:
Folder 1: 01 02 03 04 05
Folder 2: 06 07 08 09
This method is better because you can keep track of your image count and you can determine which folder to go first.
Now you're ready to the next step.
Step 3
Creating the DESC.TXT
Desc.txt is the file that the android reads in order to know which animation to play first.
this is how you create your Desc.txt
First make sure that you have Notepad++ installed , as notepad and wordpad can't run it correctly.
In Notepad++ go to Edit>EOL Convertion>UNIX Format , this way the android can read it perfectly , avoiding any errors.
Now this is how a Desc.txt would be :
Line 1 = Width Height FrameSpeed
Line 2 = p PlayTime FolderSwitchSpeed FolderName
Line 3 = p PlayTime FolderSwitchSpeed Folder2Name
In the first line you're going to put the resolution you chose for your device , I'll put 320 480 , then I'd put 20 Frames per second , so it plays at a normal speed , you can use anything from 10~30 , 10 = Slow , 30 = Fast. 20= Medium.
This is what my file looks like now:
320 480 20
Click to expand...
Click to collapse
Line 2 is going to have the folder's name and play duration , you must start by typing "p" without the quotation marks ( " " ). Followed by the Playtime , if you want it to play once , type 1 , play twice , type 2 , Infinite Loop , type 0 .... and so on. Next is the folder switch speed , which means how much should the animation pause between switching from folder to folder. I'll always use 0 so switching becomes instant. Then you type the folder's name , such as Main , if you have spaces (not recommended) use "Folder Name". My Desc now shows:
320 480 20
p 1 0 Main
Click to expand...
Click to collapse
Now the 3rd line (if present) is the same as Line 2 , but we'll set it to loop now , so instead of p 1 0 , I'm using p 0 0. so my Desc now says:
320 480 20
p 1 0 Main
p 0 0 Loop
Click to expand...
Click to collapse
Now , most of the Guides miss this step , YOU HAVE TO ADD AN EMPTY LINE IN THE END! because the final line is always ignored , so if you leave it as blank , the blank will be ignored , if you set an animation sequence here , the sequence would be ignored resulting of bad things :'(
Now you are done.
Step 4
Packaging:
Now you need to use winrar to pack them , because it has the features that we want.
Select all the folders that contain your animation and the Desc.txt , and right click them , click on Add to Archive.
On the left choose the format to "zip" , instead of rar , and in the compression method choose "store".
Name it as anything , but after that you have to name it bootanimation.zip
Step 5
Copying to your Mobile
Now you are ready and you have your animation , you need to copy it to your device , your phone must be rooted in order to access the System Files and be able to write on them.
Rename your zip file into bootanimation.zip , and put it on an SD Card. Then you can use your mobile and your preferred File Explorer to put it in the right destination.
You can use Root Explorer , or ES File Explorer (recommended).
Root Explorer:
Make sure the memory is set to R/W by click on the button that says "mount r/w"
ES File Explorer:
Go to the settings , Scroll to the bottom and open Root Settings , make sure ReMount as Root is selected so you have root Write Access.
Now , you have to place the bootanimation.
If your mobile phone doesn't have an animation , or if it uses the Default "Android animation" which is the blue Android Text Shining , then you have to put the bootanimation.zip into /Data/Local/ , from there it will be automatically read.
If you own Samsung , If you're lucky you can find it in /System/Media/ , Or you can find animation files that are NOT EDITABLE! sorry about that , just search in your mobile's section here on the XDA forums.
If you Own hTC , then you'll probably find it in /system/custom/resources .
If you couldn't find it anywhere , use the search and search for bootanimation.zip
I believe that you can use the /Data/Local/ method with any mobile except for hTC....because /Data/Local/ has higher priority.
If you find bootanimation without any extensions , do not edit it , you might loose your boot animation and crash your mobile , but don't worry , you'll only loose the ability to boot an animation , and you'll just have black screen
After you place your bootanimation.zip open its properties and make sure the following is checked:
Read
Write
Execute
in ES File Explorer you'll have three checkboxes under each one , and in the properties it should then say rwx rwx rwx (Read Write eXecute). This step is also forgotten by some guides.
Now just reboot your phone and you're good to go!
If I missed anything just let me know.
Check out some of these animations that I made , I won't give download links to them , just a gif that you may copy.
Regarding the Sound on Bootanimation
It Won't work , because there are 2 methods , :
1-playing an mp3/ogg on starting init.rc which startes soundboot.
2-mp3 can't be read on boot , soundboot corrupts the OGGs it is associated with.
there's one method which is using Java to build a file for the soundboot which I'm not sure yet about , which is using the media player , but it won't probably work because the media player hasn't been launched yet , will give you a heads up.
(for how to make your own media player for that purpose , check out thenewboston on youtube , he has 200 episodes of JAVA Android.)
Update...these methods work with any mobile except for mobiles Running Android on SD via Haret or BADA. it should work fine on android phones.
To try it out on your phone , your phone must be rooted and follow this post:
http://forum.xda-developers.com/showpost.php?p=8274824&postcount=2
These animations are on my Android version of my hTC HD Mini , so thats why they have the Windows Logo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
new animations by me
Cyanogen 7 Red Flare - thethiny 320x480
Cyanogen 7 based on Cyanogen 9 - thethiny 320x480
Sonic vs Shadow - thethiny 320x240
Click to expand...
Click to collapse
Links:
WinRar
Notepad++
Photoshop
List of Some Boot Animations
Need to know how to get the sounds going, that's what you and all of them forget (sorry) it's not all about the animation without the sound right?? I've played with about 5 boot animations and all work fine but don't have sound, I'm with HTC Viper 2.0 ROM
Sent from my HTC One S using xda premium
TheCrow1372 said:
Need to know how to get the sounds going, that's what you and all of them forget (sorry) it's not all about the animation without the sound right?? I've played with about 5 boot animations and all work fine but don't have sound, I'm with HTC Viper 2.0 ROM
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
even though I do love this too , but I didn't include this because there is no working version of sound ...I didn't forgot , just didn't find , I'll keep you updated.
thethiny said:
even though I do love this too , but I didn't include this because there is no working version of sound ...I didn't forgot , just didn't find , I'll keep you updated.
Click to expand...
Click to collapse
What about their method, I've tried but maybe u guys can figure it out?
http://forum.xda-developers.com/showthread.php?t=2133856
Sent from my HTC One S using xda premium
TheCrow1372 said:
What about their method, I've tried but maybe u guys can figure it out?
http://forum.xda-developers.com/showthread.php?t=2133856
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
trying it now ...meanwhile , This has Worked for me , but it's complicated , try using it as a temp solution (works one time then gets deleted)
http://forum.xda-developers.com/showpost.php?p=8274824&postcount=2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Success Stories)
jonathanmohamed said:
I have successfully ported s7 and n7 firmware using this guide.
Awesome guide!. 9/10
Click to expand...
Click to collapse
corsicanu said:
@malbert16442 this is pure GOLD. Gave you all my thanks for today. I'll try it myself today. Also waiting patiently for updates [emoji28] . Cheers!
Click to expand...
Click to collapse
armaowl said:
is the reason i was allowed me to port my own Rom!
Click to expand...
Click to collapse
1. Kernel is second most important because it determines if rom boots or whether
we could access a log.
2. Since we are trying to boot a rom not meant to be on our device, it could be alittle hard getting this thing to run.
3 Contact a kernel dev and ask them for adb insecure kernel or a kernel with usb debugging enabled at boot. This will help us obtain those logs at boot.
4. In some rare cases Logs might show that specific kernel services are not accessible.
In this case we only change the init.environ.rc. Which has the frameworks needed to boot.
5. If you can't get kernel logging at boot use this in recovery after 2 mins of booting.
Code:
adb pull /data/tombstones
6.Update
DaKillaz98 said:
Hello All! I am posting this fix because on my Note Edge, I wasn't able to get logcat or adb access at boot, no matter what property I set, it didn't work. I finally figured out a way to get true logcat right as the boot animation comes up.
First off, you NEED Notepad++ if you don't want garbage clumped up editing.
1. In Android Image Kitchen, depack the Boot image.
2. Then, go to split image and modify boot.img-cmdline and add
Code:
buildvariant=userdebug
.
3. Save that file, then go to the ramdisk folder and edit your default.prop. change these values.
Code:
ro.secure=1 > ro.secure=0
ro.adb.secure=1 > ro.adb.secure=0
ro.debuggable=0 > ro.debuggable=1
4. Save that file, then go to init.rc, and use find to search for adbd to jump to this.
Code:
# adbd is controlled via property triggers in init.<platform>.usb.rc
5. Change the original code from
Code:
service adbd /sbin/adbd --root_seclabel=u:r:su:s0
class core
socket adbd stream 660 system system
disabled
seclabel u:r:adbd:s0
TO:
service adbd /sbin/adbd --root_seclabel=u:r:su:s0
disabled
socket adbd stream 660 system system
seclabel u:r:adbd:s0
6. Change this to new code.
Code:
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
TO:
# allows adbd at boot with property trigger below
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04E8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/functions adb
write /sys/class/android_usb/android0/enable 1
start adbd
7. Rebuild the kernel and install in TWRP or however you install kernels, ADB will be accessible right at boot so nothing is lost during logging. If your kernel doesn't need this, don't bother, but if like me, you couldn't get anything, this will fix your issues.
In some cases, you will still need to push adb_keys to /data/misc/adb/, however.
@malbert16442 Please consider putting this in OP for those who have issues getting logcat at boot.
Click to expand...
Click to collapse
Part 2
Adb is key in any port. Adb is the secret. It gives us the ability to access logs be able to debug issues in our ROM.
1. Download adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Thanks Member @Snoop05
2. Test adb by using 'adb devices" in cmd
You should see online
3. If offline try using adb kill-server and repeat step 2.
4. When making a loging for these ports we use the phrase adb logcat *:E > filename
this ensures that we filter the logs by errors and remove the long set of lines like thermal updates ...etc
Part 3
In order to port firmware
1. Download Stock firmware extract it with tool
Websites to get stock firmware are
http://updato.com/firmware-archive-select-model
or https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
2.We will deodex our rom using Fulmics or similar deodexer
Either a kitchen like "http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296/page26" or similar.
Thanks @SuperR
https://forum.xda-developers.com/android/software-hacking/tooll-03-12-fulmics-deodexer-1-0-t3512081
Thanks @xpirt
3. Learn how to use APK DECOMPILE TOOLS SUCH AS TICKLEMEANDRIOD
http://forum.xda-developers.com/showthread.php?t=1633333
Thanks @Ticklefish
4. Remove Apps Priv-app and Framework of base. In a new folder use Fulmics to deodex this. Store somewhere safe.
5. Deodex Port and copy the Apps, Framework and Priv-app into the Base of stock rom.
6. In Ticklemeandriod you notice we have 6 work Areas. For our Roms we will only need two. The most common files we will use are services.jar, and framework.jar.
7. Take the services and framework our our Port and decompile in work area 1.
8. Take the services and framework of our Base and decompile in work area 2.
9. We will Perform a quick Step to help if App signatures become corrupt or cannot be read.
Follow this guide by @ikrom
http://forum.xda-developers.com/showpost.php?p=62496153&postcount=2957
10. After this lets move to debugging our apps and frameworks.
Part 4 (Tools and debugging)
My favorite tools to use include WinMerge and FileSeek
1. Winmerge enables us to compare two files. For example a stock jar and one of our port.
2. File seek allows us to search for a specific references.
I use file seek to search for weird terminology I see on my log.
3. Terminology
Part 5 ( Terminology)
1. In a logcat we are looking for three things when debugging. "E JavaBinder:", "E art", "E AndroidRuntime: FATAL EXCEPTION:"
2. The order to debug we search in logcat. When beginning it is not specific but, I usually search for Art errors first.
3. So for example if I get in my logcat
Code:
"01-01 01:26:25.169 5599 7183 E JavaBinder: java.lang.NoSuchMethodError: No virtual method activityPauseTrigger(Landroid/content/Intent;Landroid/content/pm/ActivityInfo;Landroid/content/pm/ApplicationInfo;)V in class Lcom/android/internal/app/ActivityTrigger; or its super classes (declaration of 'com.android.internal.app.ActivityTrigger' appears in /system/framework/framework.jar:classes2.dex)"
I got the location which is framework jar Class2
Code:
activityPauseTrigger(Landroid/content/Intent;Landroid/content/pm/ActivityInfo;Landroid/content/pm/ApplicationInfo;)V is the missing info in the port smalis and
log says it is somewhere in
Code:
Lcom/android/internal/app/ActivityTrigger; or the files with idential names to Activity trigger
4. In this case missing method could be found in stock smali. This is where we use win merge to cleanly copy new method from stock to port.
5. But Mike what if The logcat doesnt tell me location. We will then use fileseek in this instance.
Example: Log tells me
Code:
"01-01 00:24:17.509 7524 7539 E JavaBinder: java.lang.UnsatisfiedLinkError: No implementation found for void com.android.internal.app.ActivityTrigger.native_at_pauseActivity(java.lang.String) (tried Java_com_android_internal_app_ActivityTrigger_native_1at_1pauseActivity and Java_com_android_internal_app_ActivityTrigger_native_1at_1pauseActivity__Ljava_lang_String_2)
"
No implementation means that we must remove this file as it is not found in the libs. What location? We dont know yet ?
Code:
com.android.internal.app.ActivityTrigger.native_at_pauseActivity(java.lang.String
is what we are looking for
According to fileseek I would look for pauseActivity because it is a keyword
According to file seek I may get 100 references but I see one that says
Code:
.method ActivityTrigger.native_at_pauseActivity
I would then use winmerge to cleanly delete/copy the file from my stock smali to the new one. From the location I found in Fileseek.
6. Let me give a example of a Runtime error.
Code:
"07-25 09:17:08.975 16379 16379 E AndroidRuntime: java.lang.NoSuchMethodError: No interface method setDataFromNSFLP(ILandroid/os/Bundle;)V in class Landroid/location/ILocationManager; or its super classes (declaration of 'android.location.ILocationManager' appears in /system/framework/framework.jar)
So log told us to look in framework for a file with
Code:
setDataFromNSFLP(ILandroid/os/Bundle;)V
Boot up file seek and repeat steps above.
Part 6
So we booted now what.
Lets now work on fixing local errors.
Use logcat to possible fcs and reboots.
All firmware edits are different so this guide will help if you are learning the way android works.
What to look out for
Remember the Base folder we deodexed. We will use this to help fix issues in our rom.
1. Take the McRegistry Folder and ffffffff0000000 File move this to our booted rom.
2. Now in the Ported firmware copy the Fonts folder and the files named font in /etc to our booted rom.
3. Delete these folders - " preloadedmdm ", " sipdb " and " tts from booted rom and replace with that from ported firmware.
4. Open " Media " folder in booted rom
Delete Audio folder
Replace with Ported firmware audio folder.
5. In /etc/permission add the missing software permissions not hardware like slocation or camera-flash.
6. In build-prop
Replace these values with that of port.
Code:
ro.build.scafe.size=
ro.build.scafe.shot=
ro.build.scafe.cream=
ro.build.scafe.version=
ro.com.google.gmsversion=
ro.build.version.sdl=
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.config.media_sound=
ro.config.ringtone_2=
ro.config.notification_sound_2=
7. Add this code to build-prop
Code:
wlan.wfd.hdcp=disable
Let's Fix Messages and Phone FCS on first boot
1. From ported from take the libselinux.so to fix message fcs
2. To fix Phone fcs take the mapconprovider.xml from port
64 bit firmware to 32bit
1. Replace 64 bit libs with 32 bit alternatives.
2. You could find 32 bit libs in 32 bit firmware.
32bit all that could be found will be attached here for all users
Fix location problems in Rom
With our services.jar decompiled take these smalis from base and use Winmerge to copy to Port jar.
Code:
services.jar\smali\com\android\server\location folder to that of port
also take the
Code:
services.jar\smali\com\android\server\LocationManagerService$xxx
Smalis and move from base to port location.
1. Take NFC.apk and Bluetooth.apk from base and move to new Rom folder.
OR A more complex NFC fix would be to look in PackageManagerService.smali
of services.jar
look for the NFC model of the device you are porting from
1. So use FileSeeker
to search for method with "supportNfc"
2. Replace it with your model number.
Example the NFC number of Note 7 is S3FWRN5
I would replace it with the NFC number of S5 which is NXP_PN547C2
Blur
https://forum.xda-developers.com/showpost.php?p=69547250&postcount=10031
AOD FRAMEWORK FIX
Credits :
@Patrick.H (NX Team)
@karkasss (NX Team)
@Develoid ALT and F4 (AOD touch / Bluelight filter fix)
@asc1977, @DaOldMan (AOD brightness control)
(Please copy & paste when you add our credits)
Download this file extract to services.jar
https://mega.nz/#!KgMxwQDR!g0yy7a6Izk8U8szRsggaZAXLaF4pjSMYAc8p6kOjIs4
Compare the PowerManagerService Smails.
then recompile
OR
thanks @oluwaponmile
follow this guide
https://forum.xda-developers.com/showpost.php?p=69594939&postcount=8139
Lets fix ported Cameras
Code:
[SIZE="3"]GUIDE IS IN PROGRESS[/SIZE]
Debug solution not fix:
This will be a hard thing to accomplish. Also make sure that Camera is recompiled using New signatures.
First lets find the native resolutions of your camera. For this we look in native camera apk.
Find the native resolutions in arrays or strings xml.
Save resolutions found in port apk for later reference. These are the values we are going to replace with stock hexadecimal values.
Use a Decimal to Hexadecimal Converter to find the values for the resolutions in smali.
For example 1080 would be 438 and 1920 would be 780.
For this value we will intrepid the hexadecimal value as 0x438 and 0x780 respectively in andriod.
When we are looking for the resolutions in port apk we grep the values based on the hexadecimal.
So in an example if resolution of port camera is 1920x1080 and stock is 1080x1920, then in smali we might get a value of 0x438, 0x780 in assortment. Simply replace 0x438 with 0x780 and 0x780 with 0x438.
Replace these values in port apk with the stock equivalent. Recompile.
Keep this open in one window.
Now open up camera and take log.
Most likely you would get a error saying missing resolution
KNOX STATUS REVERT (Kernel)
@topjohnwu for reset prop
The reset prop source was removed from topjohnwu thread however you could use the prebuilt binary in his magisk release zips.
1. Pick your device arch and remove binary from zip
2. Now download a tool to extract boot images.
3. Navigate to sbin and drop your resetprop binary.
4. Get back to root directory and add this file http://www106.zippyshare.com/v/AzldZO7A/file.html
5. Now in init.rc add this code
Code:
# Call Knox Reset
service knox-daemon /system/bin/sh /init.knox.sh
class main
user root
oneshot
Device Specific Section
(Section will detail device specific edits for particular devices once users post.)
mitko7411 said:
So I haven't really made a new list of smalis for porting roms, but here's the ones just to boot ANY 6.0.1 firmware on J5 2015.
Debug
GpsLocationProvider
KnoxVpnPacProcessor
TADriver
SchedPolicyManager
Click to expand...
Click to collapse
No Pm type message below.
Also I will post below all the logs I used to boot Note 7 firmware on my s5
All the edits used to boot Note 7 firmware on S5 it is different for every device.
https://mega.nz/#!8ZtzWCJR!rqTrvD5K3pUvHOAMq_540L_z7Hx0LFZawSzpobFDF98
Thanks for this guide..
A nice guide. Thanks! :highfive:
Ticklefish said:
A nice guide. Thanks! :highfive:
Click to expand...
Click to collapse
Thanks
Sent from my SM-A810S using Tapatalk
Great Extremely helpful, time for noobs to port now
Thanks mate you finally did it big help
Thanks manYou helped me.
Well ,,
Malbert , im sure 100% , too much things missed in ur guide mate , this way how u do it isn't an how to ported rom from different devices , or high end to previous years device's , sorry to say this but this isn't a full guide & its just a point for drop app/prev/fram to ur stock base then try to booted then with bootloop logcat u will got what's the missing things well ,
Sorry to say it but this isn't a Full guide for HOW TO PORT Roms , ....
Edit ::
Next time try to be more specific & gives more details & which files / jars / smali / apks / libs / xml / config & which we can use & got from ported base to stock base ,
thereassaad said:
Well ,,
Malbert , im sure 100% , too much things missed in ur guide mate , this way how u do it isn't an how to ported rom from different devices , or high end to previous years device's , sorry to say this but this isn't a full guide & its just a point for drop app/prev/fram to ur stock base then try to booted then with bootloop logcat u will got what's the missing things well ,
Sorry to say it but this isn't a Full guide for HOW TO PORT Roms , ....
Edit ::
Next time try to be more specific & gives more details & which files / jars / smali / apks / libs / xml / config & which we can use & got from ported base to stock base ,
Click to expand...
Click to collapse
Thanks assaad will fix when I get time I get what you are saying but this is a intro. I can't explicitly state which jars apks or libs are needed because they are all different for different devices. XML and permissions I could elaborate on but you can't expect me to possibly give a overview of everything right. Hope you understand thanks. I never explicitly stated this was a full guide and you shouldn't treat it as such.
Sent from my SM-A810S using Tapatalk
Well my friend , i never do ,,
For example without editing systemserver.smali the rom will never booted & u know this very well , i just means to be very static for some useful tips for such framework / & well known smali that need to be our eyes on them .. that's all my point means ..
Good luck my friend
thereassaad said:
Well my friend , i never do ,,
For example without editing systemserver.smali the rom will never booted & u know this very well , i just means to be very static for some useful tips for such framework / & well known smali that need to be our eyes on them .. that's all my point means ..
Good luck my friend
Click to expand...
Click to collapse
Ohh I understand what you are saying. I will expand on this guide when I get time hopefully you also could help support and add to this guide as XDA is a community. ? Over time we could help many users thanks for your advice.
Sent from my SM-A810S using Tapatalk
@malbert16442 Can you help me with my S5 which is G9008V China Mobile variant?
I can't boot on Thunderbolt A8 rom...
What should I Fix?
I have successfully ported s7 and n7 firmware using this guide.
Awesome guide!. 9/10
I have one small issue, in your log n79 you have "E SQLiteDatabase: " How did you fix this error? I am having the same issue, with one of my builds.
Solved:
FileSeek ftw!
jonathanmohamed said:
I have successfully ported s7 and n7 firmware using this guide.
Awesome guide!. 9/10
I have one small issue, in your log n79 you have "E SQLiteDatabase: " How did you fix this error? I am having the same issue, with one of my builds.
Solved:
FileSeek ftw!
Click to expand...
Click to collapse
Thanks happy for you. How would you rate your level of expertise so I could set a difficulty level for this
Sent from my Pixel XL using Tapatalk
Learned new debug problems in Sammy Roms updating guide soon, making it more appealing too. Happy that one person actually made a port from this guide.
thnx alot @malbert16442 .... but i have 2 bugs i didnt manage to fix
1-wifi work and i can see available network but when i try to connect i get 'failed to connect' .. I tried to use my stock wifi-service.jar but the device not boot)
2-Camera work (back and front) and i can take photos...but when i try to record video i get 'Recording faield' fixed
Allooosh98 said:
thnx alot @malbert16442 ...using this guide i ported S7e, G532F to j7.....but i have 2 bugs i didnt manage to fix
1-wifi work and i can see available network but when i try to connect i get 'failed to connect' .. I tried to use my stock wifi-service.jar but the device not boot)
2-Camera work (back and front) and i can take photos...but when i try to record video i get 'Recording faield' fixed
Click to expand...
Click to collapse
When you add wifi serivce jar you have edits to make in framework you will see in your log
But don't work I have a fix for stock files too. I work on this guide this weekend make it look better
Okay so alot of people are pming me about fixing camera will post solution or debug solutions here soon
hey @malbert16442 bro can u help me to fix the problem?? there is a E art error in logcat that i cant fix it :
E art : No implementation found for int android.os.storage.sensitive.SecureStorageLSM.lsmInitialize() (tried Java_android_os_storage_sensitive_SecureStorageLSM_lsmInitialize and Java_android_os_storage_sensitive_SecureStorageLSM_lsmInitialize__)
i checked smali files but its as same as stock,i attached the log,if its ok look at it and tell me what should i do
1. Search and download the ROMs which u wanna port (Phone from which u port the rom must be running on chipset mt6582 and android 4.4.2)
2. No need of any stock rom, download the autoport ,link is given below (in autoport.zip u'll get all the the files/folders that u'll have to replace)
3. And a little patience.
It is only for stock based roms , not for roms like miui, emui, lewa os, etc..
STEPS FOR PORTING-
1. Extract the port rom and Autoport
2. Copy boot.img from autoport to port rom
3. Open system then go to bin folder, copy both pq and vold from autoport to port rom
4. Open lib folder and copy all files from lib of autoport to port rom (only files not folders)
5. Now delete hw folder that is in lib from port rom and copy it from autoport
6. Go back and delete vender folder from port rom and copy it from autoport
7. Go to etc folder and delete firmware and wifi folder from port rom then copy them from autoport , u're done
8. Now zip the port rom and flash via recovery.
9. (most important) dont forget to give credits to the developer of that rom
]
SOLUTIONS FOR MOST FOUND BUGS-
Stuck on bootlogo or black screen comes after boot logo = replacelibMali.so from any working rom for ur device.
Location - system/lib
Screen upside down = open build.prop of ur port rom with notepad++ find this line ro.sf.hwrotation=180 and change 180 to 0 , if it is already 0 then change it to 180.
If u will find more bugs then i m here to help u..
DON'T FORGET TO INFORM WHETHER IT WORKED FOR U OR NOT..
FIND ME ON FACEBOOK
OFFICIAL x1Grand FB GROUP
Solution of bugs..
--Bugs Solution --
This post is for those porters who have facing
bug after successful boot into custom rom
BUG FIXING
Here is few most encountered bugs after porting
and their solutions.
(If you get any more bugs and solutions please
let me know. I will add them here. It will be
helpful for all.)
These r
the
solutions:-
1. FOR NETWORK RELATED ISSUES (3G)
Replace from /etc folder, mddb then replace
agps_profiles_conf, apns-conf,epo_conf, spn-
conf, virtual-spn-conf-by-efpnn, virtual-spn-conf-
by-efspn, virtual-spn-conf-by-imsi
2. FOR WIFI TOGGLE PROBLEM
Replace wide-dhcpv6, wifi in /etc folder
3. FOR INTERNAL / EXTERNAL MEMORY NOT
MOUNT PROBLEM
Replace vold.fstab from /etc folder
4. FOR HIGH AUDIO VOLUME ISSUE
Replace libcustom_nvram.sofrom /lib
5. FOR CAMERA NOT CONNECTED ISSUE /
CAMERA GREEN / CAMERA FORCE CLOSE
"unfortunately camera has stopped"
Replace first libcamdrv.so (needed for 6582
devices) and check if not success then replace
libcameraservice.so from/lib. If still not success
then keep on replacing one file at a time and
check.
Camera problem is the one major bug in this type
of porting. You have to have patience. This will
take half of your energy.
6. FOR AUDIO NOT COMING IN LOUDSPEAKER
MODE
Replace libaudio.primary.default.sofrom /lib
If still sound related problem:
Replace all libaud*.so
Sometimes replacing all audio files give you a
boot loop in that case replace only
libaudio.a2dp.default.so
libaudio.primary.default.so
libaudiocompensationfilter.so
libaudiocustparam.so
libaudiosetting.so
libaudioutils.so
7. FOR FLASH LIGHT NOT COMING FROM
CAMERA
Replace libfeatureio.so from /lib
8. FOR FM PROBLEM
Replace from /lib/module folder mtk_fm_drv.ko
9. TO FIX GPS
Replace from/lib/module folder mtk_stp_gps.ko
10. TO FIX COMPASS
Replace libsensorservice.so from /lib
11. TO FIX VIDEO SHOWING PIXELS AND
GLITCHES
Replace libvcodecdrv.so from /lib
12. SHOWING WRONG RAM INFO IN TASK
MANAGER
Don't change ro.product.device value in the
build.prop.
13. FOR GREEN CAMERA/ LAG / NO WALLPAPER /
NO STATUS BAR (IMPORTANT FILE FOR MT6582)
Replace libdpframework.so from lib folder
14. PROBLEM WITH 2G/3G SWITCH
Open Dialer and type *#*#4636#*#*
If a Pop Up appears go to Phone Information and
choose your preferred network type.
15. PROBLEM DOWNLOADING EPO
Replace in framework folder
mediatek-common.jar
mediatek-framework.jar
mediatek-op.jar
mediatek-telephony-common.jar
16. ANY RESOLUTION PROBLEM
Add this line to build.prop
ro.sf.lcd_density=your phone screen dpi
ex- ro.s
17. SOME KEYS NOT WORKING
Replace keylayout folder under /usr. If still not
work then replace the whole /usr folder.
18. TOUCH SCREEN PROBLEM
(Sometimes screen behaves weird ..means for
example if you touch bottom left effect on top
right ...almost opposite response)
Replace libinput.so from /system/lib folder.
19. BOOTLOOP ON HDC CLONES
Replace libsync.so from /system/lib folder.
20. WIFI TETHERING PROBLEM
Replace dnsmasq from /bin folder.
21. SCREEN IS UPSIDE DOWN
In build.prop find this line
ro.sf.hwrotation=0
change the value 0 to 180.
ro.sf.hwrotation=180
22. Problem with Proximity Sensor
Replace nvram.so, nvram_platform.so,
nvram_daemon_callback.so
23. For inverted touch
Replace libinput.so from system/lib
24. hese are list of libs for responcible for
aoutofocus
system\lib\hw\camera.default.so
system\lib\libcamera_client.so
system\lib\libcameracustom.so
system\lib\libcameraprofile.so
system\lib\libcameraservice.so
system\lib\libmhal.so
system\lib\libmhalcontent.so
system\lib\libmhaldrv.so
system\lib\libmhalmdp.so
system\lib\libmhalpipe.so
system\lib\libmhalscenario.so
system\lib\libmhalutility.so
system\etc\permission
\android.hardware.camera.fron t.xml
system\etc\permission
\android.hardware.camera.xml
25. Sim1/2 (RIL):
\system\etc\firmware\modem.img
\system\etc\permission (RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
26.For Stuck in boot logo
Replace Libmali.s