Related
this is an older tutorial i found for the evo way back. it needs to be updated..
this could possibly work on other android htc phones to that have the fm transmit capability....
the evos Broadcom chip has a built in fm receiver and also a transmitter.
according to some threads and diagrams ive seen the transmitter does have a power source, it just doesnt have and software code to actually work.
like hdmi the hardware was there but there was no code set up, therefore we didnt have full hdmi out. it had to be built from scratch.
the hardware for the fm transmitter is there we just need some one to build the code for it.
some one please take this on!!
This tutorial was originally posted in > android development and hacking > android software development.
i am reposting it here in the evo forums for guidelines
its a nice tutorial but its old. i think it was for android 2.0 ive followed the tutorial but i couldnt get it working, and i by no means have the experience to switch things up and get it working.
[TUTORIAL] Reverse engineering HTC FM Radio for noobs (on EVO 4G)
Okay, I'm writing this because I want to help any other newbies trying to learn how to reverse engineer. The technical details involved in this are extremely daunting, so the purpose of this tutorial is to first explain in layman terms exactly what you're trying to accomplish and what to expect. Then we'll go over the details. That way you're not completely blind going into this. I'm fairly new to the scene, so I'm not as knowledgeable as everyone else. If you see any errors in my post, let me know so I can change. I'm going to assume you know a little bit of Java, can find your way around a computer, and know nothing about Android. The techniques used should work with other Android phones. For this tutorial I'm using Windows 7, Cygwin, and my stock (not rooted) EVO 4G mobile phone.
The FM tuner for the Evo is run by a Broadcom chip: BCM4329. This chip is pretty amazing in that it does wireless, bluetooth, and it has an FM receiver/transmitter. We're interested in the FM receiver / transmitter.
Now, all android phones are based on a Linux kernel. Basically they're Linux running computers. The Android operating system is then installed onto the linux system. Every app is then run off of Android.
Android is based on Java but it is not a Java system. It uses a virtual machine called Dalvik. Google did this to get around licensing issues with Sun Microsystems. So they pretty much invented their own machine language (called byte code) for the Java language. This makes things complicated for the reverse engineer because from what I've read, once Java is converted into this machine language or byte code, it can't be converted back.
So let's rehash.
If you were programming strictly in Java, you would see these extensions:
Java source code = .java
Compiled Java source code = Java byte code = .class
Compressed file to package your program = .jar (Java Archive)
But since you're programming in Android and Dalvik, you will see these:
Java source code = .java
Compiled Java source code = Dalvik byte code = .dex
Compressed file to package your program = .apk
(I haven't mentioned this, but HTC further Optimizes their .dex code)
Optimized Dalvik byte code = .odex
I'm writing all of these down because it's very easy to get confused with all of the extensions. (for me at least!). remember how I said once you go dex, you can't go back to java? That's where JesusFreke comes in. He's a senior member of XDA, and he created "baksmali" and "smali", two programs that can convert the Dalvik code back into a human readable format. These files have extensions of .smali
Decompiled Dalvik byte code = .smali
But what can you do with .smali files? That's where this other senior member, brut.all comes in: He developed apktool. apktool takes JesusFreke's work to the next level. This program in conjunction with NetBeans, actually lets you trace through any program using the .smali code taken from JesusFreke's programs!
apktool does this by converting those .smali files into "fake" .java files that can be used by the NetBeans (program that compiles and makes java programs) IDE. I say "fake" because apktool embeds the .smali code into java files as comments. However, once you attach a debugger to NetBeans, you'll see that the debugger will follow line by line every execution statement found in the smali code!
So...... you can take the program you want, plug it into Net Beans using a debugger (using the default ddms command provided by Android SDK), and you can trace everything you do in the program. I have it connected to my phone, so whenever I push a button while running my HTC FMRadio app or unplug my headphones,I see the corresponding response to the HTCFMRadio code I have loaded in NetBeans. I can now see in real-time how the program operates from my own interactions... JAM.
Technical Aspects: How to get from ground zero to tracing HTCFMRadio?
1.) Download Android SDK - Go to google development site and follow instructions: Make sure to download the latest Java JDK. Once that is installed, download NetBeans 6.8. Unfortunately, smali debugging does not work with the lastest versions of NetBeans.
Download the "Java SE" version for minimal space
http://netbeans.org/downloads/6.8/index.html
You can follow the rest of Google walkthrough and download Eclipse and ADT plugin, but it's not pertinent to this. You're going to be using adb and ddms from the android SDK extensively, so make sure the path for </android SDK/tools> is included in the PATH variable in your ENVIRONMENT SETTINGS. To get here, right click My computer, click properties, Advanced Settings, ENVIRONMENT SETTINGS.
2.) Search for 7z and download it. It is an awesome and free compression tool that will be extremely useful. It can be used to "unzip" .jar, .apk, and other compressed formats.
3.) Get the Radio app. You can do this by going to "shipped-roms" website, downloading the latest Supersonic image, and following the directions in the unlockr tutorial for HTC kitchens at the unlockr website... (once you have extracted the files from the image, you can look in the system/app and system/framework directories to get the files listed below) or:
you can pull the following files from your phone:
Using the command prompt type (and with phone plugged in, and with USB debugging enabled on phone):
adb pull /system/app/HtcFMRadio.odex
adb pull /system/app/HtcFMRadio.apk
adb pull /system/framework ./framework
This will put HtcFMRadio.odex and HtcFMRadio.apk in the current directory and create a framework directory with more files. A couple of the files in the framework are needed for the HtcFMRadio app, but for simplicity, we're just going to pull the whole directory.
Now that we have the files, we have to make a few changes to make the app installable and to be viewable by the debugger. To do this we have to decompile the .odex format into a human readable format we can edit. That brings us to:
3.) Download baksmali and smali from Project Hosting on Google Code (google search smali).
Usually an Android application is made up of one file, an apk file. Inside the apk file is an AndroidManifest.xml file, a classes.dex file (compiled Java code for the program), and other folders. The other folders contain either graphics or other .xml files that tell the program how it should look to the user. We don't have to worry about those for now. This is important because APKTOOL only opens programs set up this way. But wait up? We didn't download one .apk file, we downloaded an .apk file and an .odex file! What gives? Well, if you right click the apk file and open it (using 7z), you'll see that it's missing the classes.dex file. The dex file for the app is actually the HtcFMRadio.odex file we downloaded. So, to make this system app more like a nominal app, we have to find a way to convert the HtcFMRadio.odex to a classes.dex file. That's easy with baksmali and smali!
Once you download goto command prompt and type:
java -jar baksmali-<version>.jar -d framework -x HtcFMRadio.odex
(Remember to match baksmali-<version>.jar with the filename of baksmali you downloaded)
If done correctly, you should see a newly created \out directory
This creates an out\com\htc\fm directory with many .smali files.
Now let's reverse the process and put it back as a dex file. Type at command prompt:
java -jar smali-<version>.jar out -o classes.dex
If done correctly you'll see a newly created classes.dex.
now, right click on HtcFMRadio.apk (select 7z and open). Drag classes.dex into the file. Say yes to the prompt. Now you have a normal apk file APKTOOL can read!
4.) Download APKTOOL from Project Hosting on Google Code and the helper apps for your OS. (If you're extracting files for windows OS you should have apktool.bat and aapt.exe). Extract (again using 7z, don't you love this program?) apktool.jar (keep it as a jar file, don't extract the stuff inside of it), apktool.bat, and aapt.exe to the directory you're working on. To make things neat, you can also delete HtcFMRadio.odex (you don't need it anymore) and classes.dex (make sure you put it in the HtcFMRadio.apk file first!)
If this is the first time you're using apktool, then you have to install the htc framework so apktool can baksmali the Radio app. You only have to do this once:
apktool if ./framework/com.htc.resources.apk
Alright, at the command prompt:
apktool d -d HtcFMRadio.apk
This extracts the contents of HtcFMRadio.apk and places them in the HtcFMRadio directory. However, there are two major differences between this content and the content created in step 3. If you go into the smali directory you'll see that instead of .smali files, you'll see .java files. And if you go back and edit the AndroidManifest.xml file, you will also see that it's in text! Android applications convert their xml files to binary format. Now that APKTOOL has converted everything to an IDE friendly format, we can use NetBeans to edit everything. The first thing we're going to do is edit AndroidManifest.xml (using notepad) and add the following:
android:debuggable="true" to the Application tag.
IT should now look like this:
<application android:theme="@android:style/Theme.Black.NoTitleBar" android:label="@string/fm_app_name" android:icon="@drawable/fm_radio" android:taskAffinity="android.task.fmradio" android:description="@string/htc_corp" android:allowTaskReparenting="true" android:debuggable="true">
This permission lets the debugger watch the program while it's running on the phone.
We are going to run into two problems if we try to install this program. One is that Android doesn't let you install more than one copy of a system app. The second issue is that if we change the signature of our system app, then we'll have to change the signatures of our other system apps as well! Ahh.... So, to get around that, we're going to trick Android into thinking we have a completely new program. We're going to do that by renaming the com.htc.fm class to com.htc.modradio class. Next step:
5.) Cygwin (or Linux virtual machine)
The easiest way that I can think of to replace strings in multiple files is by using linux. You can most definitely do it in WIndows, but I dont know how. If you let me know how, I can put it in this tutorial.
(update: you can use Notepad++ to easily find/replace strings in multiple files for Windows. You still, however, want to download Cygwin if you're going to develop with Android-NDK.)
For now, just search for Cygwin (Cygwin is a program that lets you run Linux commands from a command prompt using your Windows directories), and install it. Make sure to have the Perl option selected. You'll need Perl to make the following commands work.
Once you get Cygwin up and running
cd <to your HtcFMRadio directory>
in my case it's
cd /cygdrive/c/Users/Jerry/Desktop/HtcFMRadio
now type the following commands in this order:
this command changes all occurances of htc/fm to htc/modradio in your xml and .java files.
find ./ -type f | xargs perl -pi -e 's/htc\/fm/htc\/modradio/g'
this command changes all occurances of htc.fm to htc.modradio
find ./ -type f | xargs perl -pi -e 's/htc.fm/htc.modradio/g'
If you don't follow this order, your source code will get messed up.
If using cygwin, a bunch of .bak files will be created. Using windows search, find all .bak files in your HtcFMRadio directory, then select them all and delete them (Make sure they are only files with .bak!)
Now just rename the fm directory to modradio. It is located in HtcFMRadio/smali/com/htc
Now go to your windows command prompt and type:
apktool b -d .\HtcFMRadio modradio.apk
Now sign and install modradio.apk on your phone.
adb install modradio.apk
If you have never signed before, then you need to use keytool and jarsigner. These two files are in your JDK directory, so make sure you include your JDK directory in the PATH variable of your ENVIRONMENT SETTINGS. (To get here, right click on My Computer, click Properties, Advanced Settings, Environment Variables. Once you make change, open up a new COMMAND prompt to see changes).
cd to the directory which has modradio.apk
now type:
keytool -genkeypair
Answer all questions, then use the same password for all password prompts.
Next type:
jarsigner -verbose modradio.apk mykey
Type in the password you created in the above step. Your apk should now be signed.
Next install:
adb install modradio.apk
Success!
6.) Testing the app on phone
Go to your phone and you'll now see a new FMRadio icon next to your first. Click on it and watch it open. It should now be able to play music. Keep it open.
7.) Using Netbeans
Go into HtcFMRadio and delete the build directory created by APKTOOL.
Now open up Net Beans and click on File, New Project, Select Java Project with Existing Sources, click on Next
Select HtcFMRadio directory for Project Folder, rename Project Name to whatever you want. Let's type in ModRadio. click on Next
Next to "Source Package Folders" click on "Add Folder" and select the smali directory.
Click Finish. For a quick tutorial by Brut.all, search APKTOOL in youtube and click on: Apktool Demo 2 - Smali improvements
Right click on Libraries. Click on "Add Jar / Folder". You want to add Android.Jar. Since I have Android 2.1 loaded I went to /platforms/android-7 located in my android SDK directory.
Your project is now ready for editting!
8.) Running the Debugger to trace through program.
Next go back to Windows command prompt and type ddms. This runs the Dalvik Debug Monitor. A window should open up. In the left hand side you should see com.htc.modradio. That's our app! To the right you're going to see 2 numbers, you're interested in the one to the right, 4 cells away from com.htc.modradio. This number is a port number, and you're going to use it to communicate with NetBeans. (In my case it is 8603)
Go back to NetBeans and click on Debug, Attach Debugger.
In the host field type: localhost
In the Port field: type in the second number you saw. (8603)
If everything is working you'll see a bug appear next to com.htc.modradio in the Dalvik Debug Monitor. Look at the bottom bar of NetBeans for feedback. If you get errors make sure the numbers match, or try port 8700 and make sure you select com.htc.modradio in the Dalvik Debug Monitor. Port 8700 is the default port used for whatever program you select in Dalvik Debug Monitor.
9.) Setting a breakpoint
I'm making this a seperate step because it is completely arbitrary. When creating a break point be sure to follow this rule:
You must select line with some instruction, you can't set breakpoint on lines starting with ".", ":" or "#".
Rather than looking for a spot to breakpoint, though, I'll tell you where to put one so you can quickly see how the debugger traces through the code. You aren't "REQUIRED" to do the next step, but if you want to trace you have to put a breakpoint somewhere.
In Net Beans click on the Project tab, click on Source Packages, com.htc.modradio, and then doubleclick on BroadcomFMTuner.java
We're going to insert a breakpoint. Scroll down to line 3226 and on your keyboard press: CTRL-SHIFT-F8, select line in dropdown box and hit ok. (To keep it simple, I usually look for "invoke" instructions to set breakpoints at)
Now go to your phone and click on the physical "back" button on your phone. This will clear the radio,(you should still be able to listen to music). Drag your status bar down. You should see a radio icon. Click on it again. The radio backgroudn will appear, but you wont' see any text or anything. Now go back to your netbeans application. You should now see debug options highlighted! Click on Step Over (F8) to step through!
{
"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"
}
i found a few things.
http://pdf.eccn.com/pdfs/Datasheets/Broadcom/BCM4329.pdf
http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM4329
I didn't read all of this but I have to mention that byte code is not a type of machine code..
byte code is what is created when you compile a java file. The JVM or dalvik-VM in this case, then converts this byte code to machine code at run time.
Hi guys! I see many people trying to learn how to make roms, Here i show the easiest and shortest way on how anyone can begin making roms for the Galaxy S3.
Requirements:
Prepared CWM Stock Package.
Apktool
7-zip
Notepad ++
Setting Up, and Introduction
IF you have downloaded firmware from sammobile instead of zoot1's package, use this part for Setting up and introduction: http://forum.xda-developers.com/showpost.php?p=37812381&postcount=33
OR ELSE THE EASIER WAY
To start with, Download the prepared CWM Stock Rom by zoot1 here: http://forum.xda-developers.com/showthread.php?t=1868004
I personally use firmware from sammobile, because i like to do everything myself. Though this method would be easier for beginners.
Extract the zip file to folder called "ROM".
Now lets head towards the customizing.
Thanks to Prawesome alot for this part. I took some info from his guide.
So now, open up the system folder. You'll find loads of folders in it. Here is a brief introduction to each of those folders:
1. apps
When you open this folder. You will find apk's. An apk is an install-able app package for any Android Device.
You can delete specific apps incase you want to delete. But take extra precautions on what you're deleting. As some apps are useful. You can add apps here as well in formats of apk's. But note, adding Play Store apps to the system/app folder is not recommended. For example you don't want Google Talk in your rom, you just have to delete the Talk.apk.
2. bin
Nothing really to mod in this folder. Full of advanced techy stuff. xD
3. etc
Here is where most of the tweaks come in. There is a folder called init.d where mods like the V6 Supercharger or multi-tasking fixes can be applied. Note! Don't add more than 1 or 2 scripts. Most of them usually conflict with each other.
In the gps.conf file, you can edit your gps info to make the gps more accurate. Pretty good guides about this, search them out.
Next is the hosts file. Devs use this to block sites from generating ads, and keeping their roms ad-free. Take a look at my DroidS3 hosts file, there are over 20,000 hosts blocked. You can use the same hosts file for your rom too.
4. Fonts
Very easy folder to understand. All you need to do here is replace ttf files, and you'll change the fonts.
5. Framework
Here is where the big mods come in. I'll explain further on about this. It contains the android.policy.jar, a useful element to add many mods. Framework-res is used to change wallpapers and theme the rom. I'll explain later.
6. libs
Contains all the libs needed for specific system apps to work. Don't mess here unless you're adding a mod.
7. Folders like csc, hdic, sipdb, wakeupdata, vendor, excetra..
These are the folders, there isn't much to do. Csc folder contains the feature.xml where some mods can be added. Search the forums for that. The rest contain multi-languages and more stuff.
8. xbin folder
Used to add scripts like busybox, dexdump, openvpn support. More like the bin folder but smaller.
9. Build.prop
Ever wondered how some roms have android 5.0, when it hasn't even released? All you need to change is the ro.build.version.release to any number you like. Even Android 20! Go change it, and fool some noobs out there. More mods can be added to this file. e.g:
Code:
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=15
mot.proximity.delay=15
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
ro.config.nocheckin=1
The codes listed above are for improving jpeg quality, saving some battery life, reducing call delay and more. Search for build.prop mods, you'll find loads of them. Now, a small explanation of the Meta-inf folder.
In Meta-Inf you'll find the updater-script.
Since this is aimed at beginners, I'll just show you how to change what text is shown during install in CWM.
Just edit what's in the quotes of the ui_print code in the file, and enter your own text. e.g:
Code:
ui_print("Hi, This message in quotes is displayed in recovery");
Modding!
It's time for the modding to begin.
Get apktool from: http://forum.xda-developers.com/showthread.php?t=1755243
Now, first copy your framework-res from the /system/framework directory to where you extracted apktool files. Let's call this folder "apktool"
Open the folder apktool, press shift and right click. Click on "Open command window here". Type:
Code:
apktool if framework-res.apk
Now you are ready to decompile apk's.
I'm going to show you how to mod different files. Copy over:
SystemUI.apk
android.policy.jar
framework-res.apk
1. SystemUI.apk
Just showing you basic modding here. Copy over SystemUI.apk to apktool folder. In the command prompt, type
Code:
apktool d SystemUI.apk
After it's done, you should see a SystemUI folder in the apktool directory.
I'm going to show you how to make the status bar transparent, thanks to raubkatze for this part.
Navigate to res/layout/tw_super_status_bar.xml and change android:background to match the red line.
Code:
<com.android.systemui.statusbar.phone.StatusBarWindowView [B][COLOR="Red"]android:background="#00000000[/COLOR][/B]" android:focusable="true" android:fitsSystemWindows="true" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
Save and close.
Then navigate to /res/values/drawables.xml
Edit to match:
Code:
<item type="drawable" name="status_bar_background">[COLOR="red"][B]#00000000[/B][/COLOR]</item>
That's it. Save and close.
Go back to your command prompt and type
Code:
apktool b SystemUI SystemUI-new.apk
After it's done, probably will take around 5-10 minutes. You'll find SystemUI-new.apk in your apktool folder. Open both SystemUI.apk and SystemUI-new.apk with 7-zip. Delete AndroidManifest.xml from SystemUI-new.apk and copy AndroidManifest.xml and META-INF from SystemUI.apk to SystemUI-new.apk
That's it. Close the zip files.
If you have adb or android-sdk push SystemUI-new.apk to your phone using:
Code:
adb remount
adb push SystemUI-new.apk /system/app/SystemUI.apk
adb reboot
If you don't have adb, just copy over SystemUI-new.apk to your phone. Rename it to SystemUI.apk and copy to system/app with root explorer. Reboot.
There you have transparent statusbar now!
2. android.policy.jar
Decompile android.policy.jar with:
Code:
apktool d android.policy.jar
You will find android.policy.jar.out, open it and use Cristiano Matos guide to mod the files: http://forum.xda-developers.com/showthread.php?t=2018633
After that use:
Code:
apktool b android.policy.jar.out
Open the android.policy.jar.out folder, you will find a dist folder created and inside that is your modified android.policy.jar.
You can use adb again by:
Code:
adb push android.policy.jar /system/framework
or the normal root explorer method.
3. framework-res.apk
Here i'll show you small mods.
Decompile it using
Code:
apktool d framework-res.apk
Navigate to res/values/bools.xml. Here you can add these. Thanks to DSA for this! :
4 Way Rotation:
Code:
Code:
<bool name="config_allowAllRotations">false</bool>
Change to:
Code:
Code:
<bool name="config_allowAllRotations">true</bool>
Lock Screen Rotation:
Code:
Code:
<bool name="config_enableLockScreenRotation">false</bool>
Change to:
Code:
Code:
<bool name="config_enableLockScreenRotation">true</bool>
and
Code:
Code:
<bool name="lockscreen_isPortrait">true</bool>
change to
Code:
Code:
<bool name="lockscreen_isPortrait">false</bool>
Disable Keyboard Switch In StatusBar When Typing
Code:
Code:
<bool name="show_ongoing_ime_switcher">true</bool>
Change to:
Code:
Code:
<bool name="show_ongoing_ime_switcher">false</bool>
Unplugging From USB doesn't Turn Screen On
Code:
Code:
<bool name="config_unplugTurnsOnScreen">true</bool>
Change to:
Code:
Code:
<bool name="config_unplugTurnsOnScreen">false</bool>[/indent]
Now to change wallpaper. Change the default_wallpaper.jpg in drawable-xhdpi and to change lockscreen wallpaper change keyguard_default_wallpaper.jpg.
Now recompile using:
Code:
apktool b framework-res framework-new.apk
Delete AndroidManifest.xml from framework-new. Copy AndroidManifest.xml and META-INF from framework-res.apk to framework-new.apk
To test use adb:
Code:
adb push framework-new.apk /system/framework/framework-res.apk
Or rename to framework-res.apk and copy to system/framework using root explorer. Reboot.
Once you've added everything, your modified apks. Ui_print mods, A custom kernel (just replace boot.img) it's time to compile. Now this is really easy. Just highlight all the folders/files like system, meta-inf and boot.img. Right click. Hover over 7-zip and click Add to Rom.zip. Wait for it to be done, and copy Rom.zip to your sd card and flash. Voila! You've made your rom!!
You can get more mods to add from here: http://forum.xda-developers.com/showpost.php?p=26583654&postcount=4
I was a beginner once, everyone was a beginner once. People helped me, and now I want to help people.
Press the Thanks button, and/or rate this thread 5 stars to show your support.
FAQ
- How do i add a mod?
To add a mod, just download it. Open it and copy over all the folders from the zip file EXCEPT the META-INF.
- How can i set up apktool on windows?
To set up apktool on windows, you need aapt, apktool.jar and apktool.bat
- My modified apk is not working?
Do some testing and get to know what went wrong. I'm always here. I'll be glad to help.
- Are these the only apps i can modify?
Ofcourse not! Any apk can be modified. Just decompile it, and make your changes.
- I'm looking for a guide on something i want to learn. Can you add it here?
I'll try my best.
Reserved
Reserved one more.
Any feedback guys? I hope this is useful.
Forget that i had to reserve one more.
R: [GUIDE] Beginners/Ref Guide to Making Roms.
Looks interesting...when i will finish my exam i will check with more attention
Sent from my GT-I9300 using xda app-developers app
Willy89 said:
Looks interesting...when i will finish my exam i will check with more attention
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Glad it's of help.
Sent from my GT-I9300 using xda premium
Thnx for making this thread.
It's always useful to read thread's like this.
Nice job.
Verzonden door mijn GT-I9300 met xda premium
Great guide, thanks, I will point Theshawty in this direction :thumbup::thumbup:
slaphead20 said:
Great guide, thanks, I will point Theshawty in this direction :thumbup::thumbup:
Click to expand...
Click to collapse
Too late old man. Not interested in building roms anymore.
Thanks guys.
If there's anything you'd like to have added.
Let me know.
AW: [GUIDE] Beginners/Ref Guide to Making Roms.
Thanks. That's it what i searched for to start. Great.
weli..this would be intersting..and will c hw thread moves...
I Need Help In Building the ROM
Hi,
I am steinert. i need your help in biulding the rom, actually i finished everything but getting the problem while flashing the rom. when i googled it. i came to know that the problem lies in updater-script. i used root explorer to find out the reason. it was like.
FINISHED EXECUTING SCRIPT FILE
EXIT VALUE:126
STDOUT:
NULL
STDERR:
SH:<STDIN>[1]:/CACHE/RECOVERY/LAST_LOG:CAN'T EXECUTEERMISSION DENIED.
I Hope that You help a NOOB like me....
Thank you in advance....
Jacqueline Steinert said:
Hi,
I am steinert. i need your help in biulding the rom, actually i finished everything but getting the problem while flashing the rom. when i googled it. i came to know that the problem lies in updater-script. i used root explorer to find out the reason. it was like.
FINISHED EXECUTING SCRIPT FILE
EXIT VALUE:126
STDOUT:
NULL
STDERR:
SH:<STDIN>[1]:/CACHE/RECOVERY/LAST_LOG:CAN'T EXECUTEERMISSION DENIED.
I Hope that You help a NOOB like me....
Thank you in advance....
Click to expand...
Click to collapse
After flashing the rom.
Check the error through Advanced > Show recovery log in recovery.
Post results here.
I : checking for entendedcommand..
I : skipping execution of extendedcommand, file not found...
Jacqueline Steinert said:
I : checking for entendedcommand..
I : skipping execution of extendedcommand, file not found...
Click to expand...
Click to collapse
Huh?
Get me a screenshot of your meta-inf/com/google/android directory.
What exactly did you modify? It should work if you left the meta-inf untouched.
masterex567 said:
Huh?
Get me a screenshot of your meta-inf/com/google/android directory.
What exactly did you modify? It should work if you left the meta-inf untouched.
Click to expand...
Click to collapse
I just removed all the apps and inserted new apps...!!
Should i send you my updater-script?
Jacqueline Steinert said:
I just removed all the apps and inserted new apps...!!
Should i send you my updater-script?
Click to expand...
Click to collapse
Removed all?
Some are core apps like SystemUI, etc.
Get me a screenshot of your rom.zip..
masterex567 said:
Removed all?
Some are core apps like SystemUI, etc.
Get me a screenshot of your rom.zip..
Click to expand...
Click to collapse
{
"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"
}
This is the screenshot of my rom..! and before also i got the same problem with out changing the system .apk's
Jacqueline Steinert said:
View attachment 1700664
This is the screenshot of my rom..! and before also i got the same problem with out changing the system .apk's
Click to expand...
Click to collapse
Highlight those 3 and in 7zip options click add to " ".zip
Sent from my GT-I9300 using xda premium
THIS GUIDE WILL NOT MAKE YOU DEVELOPER OVERNIGHT. THIS GUIDE ONLY GIVEN TO GIVE YOU HEAD START IN ROM DEVELOPMENT.
I am glad that i am posting this in our new forum...(thanks xda)
IT IS HIGHLY RECOMMENDED THAT YOU SHOULD KNOW SOME BASICS OF LINUX COMMANDS FOR ANDROID DEVELOPMENT.
DISCLAIMER- I AM NOT RECOMMENDING TO ADD PAID APPS OR SOME OTHER DEVELOPER'S WORKS IN UR ROM. PLEASE DON'T PUBLISH ROM WITH PAID CONTAINS OR OTHER DEVELOPER WORKS.
AND
"DON'T SPAM DEVELOPMENT FORUM WITH UR ROMS IF IT DOESN'T CONTAINS ANYTHING NEW."
STEPS:-
1.Things needed
2.Setting up Cygwin in windows
3.Setting up linux (if you are going to use windows then skip this)
3.Setting up a dsixda kitchen
4.Using a kitchen to make a rom
5.Customise the rom
Click to expand...
Click to collapse
1.THINGS NEEDED
1.DSIXDA Kitchen
http://github.com/dsixda/Android-Kitchen/tags
(for any kitchen related issues please report to original kitchen THREAD
2. GT-I9082 /I9082L kitchen compatibility file http://d-h.st/qr5
3. Latest Firmware from sammobile.com/firmwares or samsung-updates.com
4. 7-zip (to extract tar.md5 file) in windows.
5. Notepad++
6.cygwin or linux (ubuntu or its variant preferred)i recommend using Linux for your development (sometimes cygwin causes symlink errors in updater script)
i use linuxlite or ubuntu 10.04 or ubuntu 13.04 64bit.
In windows android development is difficult and for porting and debugging ,tar,untar and many other functions linux is the only way.
7.JDK www.java.com
Click to expand...
Click to collapse
2.SETTING UP CYGWIN IN WINDOWS
(I am not using cygwin for my development ,although it is setup in my pc.I personally prefer linux)
Download Latest JDK from http://www.java.com/en/download/manual.jsp choose windows offline version
Download cygwin package from http://content.wuala.com/contents/neroyoung/XDA%20ROM%20Dev%20Tools/Cygwin.zip
-->Install JDK first .
-->extract cygwin.zip C:\
-->We need to install cygwin, open the setup.exe, just keep hitting next until you are on the select packages screen, go to "Devel" menu and select to install gcc, gdb and make, in "Interpreters" check perl, in "Archive" check zip and unzip, in "Web" check wget, in "Editors" check nano and vim and in "Utils" select cpio, util-linux and ncurses. Make some tea and wait for the cygwin install to finish and we are ready to go to the next step.
Click to expand...
Click to collapse
NOW CYGWIN IS READY TO GET KITCHEN
3.SETTING UP LINUX
i personally recommend linux for kitchen and other android development use.
i use linux lite(based on ubuntu LTS release) http://www.linuxliteos.com/ I also use ubuntu 13.04
if u want to use ubuntu then i recommend version 10.4 or 13.04 or use kubuntu latest release.
Installing linux along with windows on other partition as dual boot can be done but need experience.
Following are 2 methods are easiest and currently recommended by me.
FIRST METHOD
Most easy and recommended
INSTALLING UBUNTU ALONG WITH WINDOWS WITHOUT FORMATING HARD DRIVE OR PARTITION
-->Download Ubuntu 13.04 64bit
-->Download WUBI 13.04
-->make sure ur one of the partitions on ur pc have atleast 25 to 30 gb space.
-->After downloading put wubi and ubuntu iso in same folder
(note don't use wubi on windows 8 pc)
-->Double click on wubi.exe
-->Select Drive with maximum space. select 22gb in installation size.
-->set ur administrator password & re-enter it in confirm password box.
-->click install & wait for finish screen.
-->select reboot.
-->on rebooting it will start installation automatically.
-->wait till installation finishes & reboot to default ubuntu log screen.
-->login with ur username/password
-->make sure ur internet is connected.
-->Press Ctrl+Alt+T to open terminal & type following
(if it ask for password then type it and press enter)
Code:
sudo apt-get install gnome-shell gnome-session-fallback indicator-applet-appmenu gnome-tweak-tool ia32-libs
-->after that logout (it is round setting like icon in top corner) and select the session as "genom fallback with no effects" from login screen (round icon beside ur_username on login screen)
-->now relogin
-->go to applications>>ubuntu software center
-->search java>>select openjdk7 java runtime environment>>click install. Wait till installation.
Click to expand...
Click to collapse
NOW SETUP KITCHEN
SECOND METHOD
Those who want to set up linux in virtual machine need fast pc with lots of ram.
--> install virtual box http://www.virtualbox.org/
-->after installation open virtual box
--> click new-->in name box type ubuntu or kubuntu , it will automatically select linux and ubuntu or kubuntu in below boxes.-->click next-->select ram size u want to devote to virtual machine i recommend atleast 1024mb.
-->click next you will see menu to creat a virtual hard disk.Select create new hard disk-->select hard disk type as vdi in next screen.-->in next screen select dynamically allocated.-->in next screen click yellow icon beside ubuntu or kubuntu and select where you want to put your hard disk. You need atleast 15 to 20 gb space for hard disk. then click create.
-->now click start in virtual box on selecting kubuntu. it will ask for you bootable disk. browse and select ubuntu or kubuntu or linuxlite bootable disk. It will boot into boot menu. select install to hard drive.(google for installation instructions for ubuntu or kubuntu or linuxlite)
-->now boot up your virtual machine
-->login with user you created.
then follow the instruction s in this post http://forum.xda-developers.com/showpost.php?p=5626300&postcount=3 under linux/ubuntu section.
Click to expand...
Click to collapse
NOW YOUR VIRTUAL MACHINE IS READY TO SETUP KITCHEN
4.SETING UP DISXDA KITCHEN
A] cygwin instructions
-->Download kitchen from above link.
-->extract it to C:\cygwin\home\
-->rename the extracted folder to "kitchen" from "Android-Kitchen-xxx" (easier to navigate)
-->Now fireup cygwin from desktop icon.
-->In command window type "cd ../kitchen" press enter
-->then type ./menu
--> and you ready to go...!!!
Click to expand...
Click to collapse
B] Linux instructions
-->Download the kitchen
-->extract it to home/your_username directory
-->rename the extracted folder to "kitchen" from "Android-Kitchen-xxx" (easier to navigate)
-->Open the terminal & type "cd kitchen" press enter
-->then type ./menu press enter.
--> and you ready to go...!!!
Click to expand...
Click to collapse
NOW YOU HAVE YOUR KITCHEN SETUP FOR USE.
MAKING I9082/I9082L ROM DEVELOPMENT COMPATIBLE WITH KITCHEN
-->Now go to \kitchen\tools\edify_defs in linux or cygwin folder
-->copy the compatibility file I provided above to this folder.
-->VOILA NOW OUR GRAND IS COMPATIBLE WITH KITCHEN.!!!!
Click to expand...
Click to collapse
4.USING KITCHEN TO MAKE A ROM
-->Download the firmware of choice from www.sammobile.com/firmwares or www.samsung-updates.com
-->Unzip it.
-->You will get tar.md5 file.
-->If you are using windows then open the tar.md5 with 7-zip. or in linux open it with archiever
-->7-zip will show an error just click ok.
-->Now your tar.md5 is open.
-->extract system.img,boot.img,cache.img to"original update" folder in kichen folder.
-->Fireup the kitchen as stated above.
-->select option 1 - Set up working folder from ROM
-->press enter to continue.
-->press enter again to copy imgs to working folder
-->now in linux it will automatically copy them ,extract them to working folder
-->but in cygwin it will show prompt to extract system.img. (read the instructions when it prompt) extract it to working folder.-->it will show prompt to extract cache.img to system folder.-->Now you have your working folder setup for use. do it.
-->now select option 2 , 3 one by one to get root and busybox respectively.
-->now select 0 advanced options
--> in that select 14 to add init.d support
-->select 11 Deodex files in your rom . here press "v" to change the API level. Set it to 16 or 17 .(JB4.1.2 is level 16 and JB4.2.2 is level 17 )Now select "b" to deodex both app and framework folder.
--> now go back to main menu. and select 99 build the rom from working folder. here select 2 lazy mode.
--> Wait for some time. you will get prompt that baffin_signed_xxxx.zip is created in output_zip folder.(this lies in kitchen's folder)
Click to expand...
Click to collapse
HERE IT IS... YOUR FIRST CUSTOM ROM.:good:
5.how to customise your rom.
So first thing now for you to customize your own rom.
You can do this in linux or windows
DISCLAIMER- I AM NOT RECOMMENDING TO ADD PAID APPS OR SOME OTHER DEVELOPER'S WORKS IN UR ROM. PLEASE DON'T PUBLISH ROM WITH PAID CONTAINS OR OTHER DEVELOPER WORKS
A]Remove & add apps
B]Remove unnecessary files.
C]Add your own ringtones,alarm,notification sounds
So lets start....
First u have to make back up copy of ur rom.(I am a back up freak...)
A]Remove & add apps
REMOVE APPS
Extract your rom to some directory like "myrom"
Now you get system,boot.img,meta-inf folder extracted.
Go to >>system/app
DELETE THE APPS YOU DON'T NEED.
I AM GIVING YOU THE NAME OF FILES I REMOVE AS PER MY NEED.
\system\app
ACCUWEATHER
AccuweatherDaemon.apk
AccuweatherWidget.apk
AccuweatherWidget_Main.apk
WeatherWall.apk
ALLSHARE
AllshareMediaServer.apk
AllSharePlay.apk
AllshareService.apk
CLOCK
AnalogClockSimple.apk
DigitalClock.apk
DualClockAnalog.apk
DualClockDigital.apk
SimpleAlarmClock.apk
CAMERA FEATURE
BestGroupPose.apk
FaceLock.apk
GroupCast.apk
SAMSUNG MESSANGER
ChatON_MARKET.apk
FONTS
ChocoEUKor.apk
CoolEUKor.apk
HelvNeueLT.apk
RoseEUKor.apk
CHROME BROSWER
ChromeBookmarksSyncAdapter.apk
ChromeWithBrowser.apk
CSC
CSC.apk
LIVE WALLPAPER
DeepSea.apk
LuminousDots.apk
NoiseField.apk
PhaseBeam.apk
SecLiveWallpapersPicker.apk
DROPBOX
Dropbox.apk
DropboxOOBE.apk
GALLARY
EasyGalleryWidget.apk
EMAIL,EXCHANGE,VPN
EdmSysScopeService.apk
EdmVpnServices.apk
EnterprisePermissions.apk
Gmail.apk
SecEmail.apk
SecExchange.apk
FLASH ANNOTATE SERVICE
FlashAnnotate.apk
FlashAnnotateSvc.apk
SOFTWARE UPDATE CLIENT (MUST REMOVE BECOZ IT WONT WORK)
FotaClient.apk
GAME HUB
GameHub_2.0_ICS.apk
MAPS
GMS_Maps.apk
Street.apk
Velvet.apk
GOOGLE SEARCH AND OTHER SERCICES
GoogleSearchWidget.apk
GoogleTTS.apk[TEXT TO SPEECH SERVICE]
Magazines.apk[PLAYSTORE MAGAZINES]
Music2.apk
MusicHub_31.apk
PlusOne.apk[GOOGLE+1]
VoiceRecorder.apk
VoiceSearchStub.apk
YouTube.apk
HELP
HelpHub.apk
PickUpTutorial.apk
WebManual.apk
KIES OVER WIFI
kieswifi.apk
SAMSUNG SERVICES AND APPS
MobileTrackerEngineTwo.apk
S-Voice_Android_phone.apk
SamsungApps.apk
SamsungAppsUNA3.apk
Samsungservice.apk
SamsungTTS.apk
SamsungWidget_FavoriteApp.apk
SamsungWidget_ProgramMonitor.apk
SimpleFavoritesWidget.apk
SlideShow.apk
SMemo2.apk
SNoteProvider.apk
SSuggest.apk
PAGE BUDDY
PageBuddyNotiSvc.apk
POLARIS
PolarisViewer.apk
CLOUD SERVICES
sCloudDataRelay.apk
sCloudDataSync.apk
sCloudSyncBrowser.apk
sCloudSyncCalendar.apk
sCloudSyncContacts.apk
sCloudSyncSNote.apk
WIFI DIRECT
SecFileShareClient.apk
SecFileShareServer.apk
SETUP WIZARD
SecSetupWizard.apk
SOCIAL
SNS.apk
GTALK
Talk.apk
talkback.apk
VIDEO & OTHER VIDEO APPS
TrimApp_phone.apk
VideoHub.apk
YAHOO SERVICES
YahoonewsDaemon.apk
YahoonewsWidget.apk
YahoostockDaemon.apk
YahoostockWidget.apk
Click to expand...
Click to collapse
Now that u deleted the apps u dont need.
make a zip of "system,boot.img & meta-inf" by selecting all . >>>right click >>add to archive(winrar) or some other zip program u use>>ur zip is ready to flash through cwm.
ADD APPS
There are 3 ways to add apps to your rom
1.Including apps in system/app
2.including apps in data/app
3.Using cwm zip for adding apps
1. Including apps in system/app
This can be done by following method
>> install apps from play store in ur rooted rom.
>>go to file manager like es or root browser or root explorer
>>open data/app folder
>>you will get your install app apks there.
>>copy them to your external sd card.
>>now open ur extarcted rom's system/app folder
>>copy the apps u wanted to install in this folder.
>>make a zip of system,boot.img and meta-inf
>>now flash ur rom .
2.Including apps in data/app
This can be done by following method.
>>enable data/app in ur rom while making rom in dsixda kitchen.
>>extarct ur rom
>>copy the applications u want in data/app
>>make a zip of all the containts in extracted folder & flash.
3.using cwm flashable zip to add apps
this is done as follows
>>extract cwm zip
>>mostly u will get system & meta-inf folder
>>open system folder and see what folders u have in that.
>>copy these folders in ur rom's system folder.
>>make a zip of ur rom
>>flash through cwm.
reserved#1
reserved #2
reserved#3
k2wl said:
THIS GUIDE WILL NOT MAKE YOU DEVELOPER OVERNIGHT. THIS GUIDE ONLY GIVEN TO GIVE YOU HEAD START IN ROM DEVELOPMENT.
I am glad that i am posting this in our new forum...(thanks xda)
IT IS HIGHLY RECOMMENDED THAT YOU SHOULD KNOW SOME BASICS OF LINUX COMMANDS FOR ANDROID DEVELOPMENT.
STEPS:-
1.THINGS NEEDED
2.SETTING UP CYGWIN IN WINDOWS (I am not using cygwin for my development ,although it is setup in my pc.I personally prefer linux)
NOW CYGWIN IS READY TO GET KITCHEN
3.SETTING UP LINUX
i personally recommend linux for kitchen and other android development use.
i use linux lite(based on ubuntu lts release) http://www.linuxliteos.com/
if u want to use ubuntu then i recommend version 10.4 or use kubuntu latest release
instaling linux along with windows is complex and i am not covering that in this guide.
NOW YOUR VIRTUAL MACHINE IS READY TO SETUP KITCHEN
4.SETING UP DISXDA KITCHEN
A] cygwin instructions
B] Linux instructions
NOW YOU HAVE YOUR KITCHEN SETUP FOR USE.
4.USING KITCHEN TO MAKE A ROM
HERE IT IS... YOUR FIRST CUSTOM ROM.:good:
Click to expand...
Click to collapse
hi k2wl,
i also use cygwin+kitchen and have a same file as baffin on home\kitchen\tools\edify_defs, and also do the same steps as you mentioned, but the updater-script is not same as yours. it stuck on boot loop--WO 3G, when i flash my baffin_zip, no samsung arround on the screen.
i upload my updater-script, can you help me check it? what's wrong with it ?
my device : I9082_CU Chinese Unicom mobile, wether i should change the device name to cu_baffin or not ? confused.........
i also can flash your roms based on XXAMCD and ZTAMD1, maybe not the name issue.
help.........
tonylin880806 said:
hi k2wl,
i also use cygwin+kitchen and have a same file as baffin on home\kitchen\tools\edify_defs, and also do the same steps as you mentioned, but the updater-script is not same as yours. it stuck on boot loop--WO 3G, when i flash my baffin_zip, no samsung arround on the screen.
i upload my updater-script, can you help me check it? what's wrong with it ?
my device : I9082_CU Chinese Unicom mobile, wether i should change the device name to cu_baffin or not ? confused.........
i also can flash your roms based on XXAMCD and ZTAMD1, maybe not the name issue.
help.........
Click to expand...
Click to collapse
my friend its a issue of symlinks....
i recommend to use linux+kitchen for perfect rom making....i have faced this for some other device previously and from that time i always use linux for development.
(i have been linux user since 2000...)
install linuxlite/ubuntu/kubuntu in virtual box and put kitchen in it. copy the compatibility file in the fore said folder and and fire up your kitchen. Rest procedure is same.
i am giving u my updater script for your convenience . replace your updater script with this and reflash again.
TELL me the results of reflash!!!
also attach build.prop here ...i wana look at it.
k2wl said:
my friend its a issue of symlinks....
i recommend to use linux+kitchen for perfect rom making....i have faced this for some other device previously and from that time i always use linux for development.
(i have been linux user since 2000...)
install linuxlite/ubuntu/kubuntu in virtual box and put kitchen in it. copy the compatibility file in the fore said folder and and fire up your kitchen. Rest procedure is same.
i am giving u my updater script for your convenience . replace your updater script with this and reflash again.
TELL me the results of reflash!!!
also attach build.prop here ...i wana look at it.
Click to expand...
Click to collapse
hi, k2wl
i have try to use your updater-script to replaced.but also faild....i have wiped all before flash.
the build.prop and boot.img are attached, please check it.
i also unpack the cache.img to the system file, is this the reason why can not flash? because i see nothing csc related files in your roms.
and i will try to build lunix, and do it again.
tonylin880806 said:
hi, k2wl
i have try to use your updater-script to replaced.but also faild....i have wiped all before flash.
the build.prop and boot.img are attached, please check it.
i also unpack the cache.img to the system file, is this the reason why can not flash? because i see nothing csc related files in your roms.
and i will try to build lunix, and do it again.
Click to expand...
Click to collapse
it is not the csc... ur build.prop and boot imgs are ok. do rom building in linux and give me feed back.
if u going to use ubuntu then use HELLS-KITCHEN | Ubuntu-Based | ROM Developing Distro http://forum.xda-developers.com/showthread.php?t=2152398
it already contains kitchen.
awesome guide brother..
Making rom is jst about experience. When a person like you makes rom they keep getting better and better. So rom made by you will be any day better than a first time user.
People should be able to make their own Rom. So that you can focus on development of powerful custom Rom and kernels. Your contributions for sgg are huge...
Just a note, installing linux alongside windows is a very, very simple job. You only need to partition your hard disk to have like a 100GB empty partition, and make an Ubuntu bootable USB using Rufus (Awesome program), and just boot using the USB and follow the steps to install Ubuntu.
@DBZo07
ya basically that is main purpose of this tutorial.
@panda00
or u can use UNetbootin to have bootable linux usb.
k2wl said:
@panda00
or u can use UNetbootin to have bootable linux usb.
Click to expand...
Click to collapse
Yes, Rufus has the same function, but I prefer Rufus, because Rufus is universal (i.e. works with windows ISO as well) and it's portable (no need for an install)
k2wl said:
it is not the csc... ur build.prop and boot imgs are ok. do rom building in linux and give me feed back.
if u going to use ubuntu then use HELLS-KITCHEN | Ubuntu-Based | ROM Developing Distro http://forum.xda-developers.com/showthread.php?t=2152398
it already contains kitchen.
Click to expand...
Click to collapse
finally i have download the big file 1.5G hells-kitchen beta5, work on virtualbox ,but no password to login. confused
what's the passwords?
shall i try to download ubuntu and kitchen.....
tonylin880806 said:
finally i have download the big file 1.5G hells-kitchen beta5, work on virtualbox ,but no password to login. confused
what's the passwords?
shall i try to download ubuntu and kitchen.....
Click to expand...
Click to collapse
password is "p"
This guide helped me to have my own customized rom.. Thanks k2wl for your efforts... Hats off man..
Possible customization were done looking at your rom features and my requirements.
Turned out to be awesome one..
Further, dpi is set to 160 without any single bug.
Battery usage is awesome. Still haven't used your custom kernel, which I don't wanna try for now.
Again, thanks man for this guide finally got perfect awesomeness. Now, I can focus on my exams rather than such hunting around for better.
God bless you.. Later...
Here are screens
{
"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"
}
Sent from my GT-I9082 using Tapatalk 2
DBZo07 said:
This guide helped me to have my own customized rom.. Thanks k2wl for your efforts... Hats off man..
Possible customization were done looking at your rom features and my requirements.
Turned out to be awesome one..
Further, dpi is set to 160 without any single bug.
Battery usage is awesome. Still haven't used your custom kernel, which I don't wanna try for now.
Again, thanks man for this guide finally got perfect awesomeness. Now, I can focus on my exams rather than such hunting around for better.
God bless you.. Later...
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
hey thanks for those kind words...u r using xperia launcher... does it block ur notifications??? or any other errors u may got???
Nope, no such errors... There was a guy who posted https://www.dropbox.com/s/reyimmczzn7e6nq/Sony_Xperia_Z_Walkman_by_Ravi.zipWalkman + launcher flushable zip which worked well.
Sent from my GT-I9082 using Tapatalk 2
DBZo07 said:
Nope, no such errors... There was a guy who posted https://www.dropbox.com/s/reyimmczzn7e6nq/Sony_Xperia_Z_Walkman_by_Ravi.zipWalkman + launcher flushable zip which worked well.
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
ok i thought that u include in the rom and then install the rom....becoz if u try to include it in rom..it will generally crashes the notifications and many other problems...
Android Multitool
Hello,
I´m glad to present my Android Multitool wich makes it easier to decompile/recompile applications + jar framework files. You can also sign your apk by easily clicking a button.
Requirements:
Winows OS XP / 7 / 8 / 8.1 / 10
Installed Java on Windows
Installed Microsoft Powerpacks
Installed .NET framework
- Easy handling: Select your apk and push the "decompile" button!
- This tool makes modding much faster and easier, no cmd handling any more.
- You can read the log which is integrated in the tool to find your mistake in the error.
- ADB inside: Push files into your file system with a few clicks
It looks like this so far:
{
"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"
}
How to use this tool?
Follow this small how to!
Here you go..
Well, first extract the AndroidMultitool folder to C:\. Otherwise it probably won´t work
-copy your framework-res.apk in the Framework-Files folder and other files you want to mod in the "Files" folder (this folder is for all your files you want to mod, don't pick files from any other location)
-Next you have to start AndroidMultitool.exe
-select your framework-res.apk and push the "install" button (check log for errors)
Decompiling and recompiling apk files:
-select the apk you want to mod/decompile and push the "decompile" button (check log for errors)
Note: You can check the "use baksmali" checkbox, then e.g. the useless .line text will be removed
-your decompiled apk will be located in C:\AndroidMultitool\Decompiled_apk"apkname" as a folder
-if you want to compile your apk again, select your decompiled folder, check the "apk" radio button and compile it again (check log for errors)
-your recompiled apk will be located in C:\AndroidMultitool\Compiled_apk"apkname"
Decompiling and recompiling jar files:
-select in the combobox ".jar" (check the "use baksmali" checkbox for deleting the useless .line comments)
-select the ".jar" file you want to mod
-push the "decompile" button
-your decompiled jar file will be locaten in C:\AndroidMultitool\Decompiled_jar"jarname"
-for recompiling you have to check the "jar" radiobutton and select the folder within your decompiled ".jar" file
-push the compile button
-your compiled jar file will be located in C:\AndroidMultitool\Compiled_jar"jarname"\classes.dex
-delete the "classes.dex" file in your ".jar" file
-copy the new "classes.dex" file you compiled in the ".jar" file
Signing apk files:
-select the ".apk" you want to sign
-push the "sign" button
-the signed apk file is located in C:\AndroidMultitool\Signed_apk"apkname_signed"
Using tags:
You want to decompile many files from different devices or different android versions / frameworks? Tagging makes it possible!
- before installing your framework type in any tag (like "hero")
- then install your framework and work normally
Android Debug Bridge
You want to push files with adb to your device? Follow these instructions:
Please klick on the "advanced" register in the tool
-push "check" to control if your device is ready
-if the device is not ready please follow the instructions, which are listed in the tool (device offline, no device...)
-if the device is ready, choose a file you want to push
-choose a path on the device, where the file should be placed later
-push the "push" Button
-alternately: press "Reboot device" to reboot your device and to let changes take effect
If there are any questions or bugs, please post them in the thread.
Follow me on Google+ : Daniel Huber
[DOWNLOAD] see next post #2
Enjoy easier apk handling!
Having issues with the program?
Try the batch version developed by @bovirus (it's also in the AndroidMultitool folder)
Questions and answers:
Q: The programm does not start, it crashes.
A: Please install Powerpacks, this one: http://go.microsoft.com/fwlink/?LinkID=145727&clcid=0x804
Q: What do you mean exactly with "!!!NOTE!!! After compiling you have to copy the AndroidManifest.xml and the META-INF folder from your old apk to your newly compiled one!! Otherwise you´ll get bootloop! " .. I don't understand.
A: You have to open your old apk (this one you selected for decompiling in the folder /files) and copy from that apk the AndroidManifest.xml and the META-INF folder to the apk you just decompiled and recompiled.
Q: I followed all steps in the startpost but I'm still getting this error: "apktool is not recognized as internal or external command"
What can I do?
A: Please refer to this post by @LasVegasRomeo: http://forum.xda-developers.com/showpost.php?p=51017662&postcount=681
Credits:
Developers (brut.all, iBotPeaches) of the base Apktool
mike_galaxy_s for his help on testing
@bovirus for batch development
------------------------------------------------------
Changelog:
v3.5.9:
updated build tools and platform-tools (aapt, adb and needed dll's)
updated 7za, apktool, smali and baksmali to latest version
added bovirus's batch version to the main directory (users can choose between gui and batch now)
added a folder (Framework-Files) for the framework-res.apk (only use this folder for the framework files from now on)
added a Help folder with all commands
v3.5.8:
updated build tools and platform-tools (aapt, adb and needed dll's)
updated apktool, smali and baksmali to latest version
v3.5.7:
updated build tools and platform-tools (aapt, adb and needed dll's)
updated apktool, smali and baksmali to latest version
v3.5.6:
fix progressbar not disappearing after decompiling
fix loop after/while compiling
save compiling path and jump into it when he starts folder browsing
update user interface
v3.5.5:
fix infinite loop on compiling when errors appeared
folderbrowserdialog (compiling): jump into /decompiled_apk default
update build tools and platform-tools (aapt, adb and needed dll's)
v3.5.4:
add option to copy AndroidManifest.xml automatically into the apk after compiling
layout cleanup
force overwrite already compiled or decompiled files when new compiling/decompiling thread started
update to apktool rc3 (mainly lollipop support)
v3.5.3:
copy AndroidManifest.xml and META-INF folder automatically into the apk after compiling
added some links
code cleanup
v3.5.2:
add more detailed log
fix decompiling/compiling/signing/installing framework multiple times sometimes
add batch decompiling (preview)
fix donation image not fitting center
add txt files with descriptions for all tools inside (thanks to @bovirus)
v3.5.1:
update all files
v3.5:
code rework
fix UI freezing on long tasks
add progress bar
many other small fixes
v3.4:
access files from all locations of the pc (you're not limeted to the /Files folder)
add version number to the tool
v3.3:
add tag support (tagging allows multiple framework support)
rework interface
small additions and fixes
support for Win7 / 8 / 8.1 (no extra versions)
v3.2.1:
add apktool b9
v3.2:
add different apktool, aapt and batch files
should solve some problems on de - and recompiling
v3.1:
Fixes for adb push
button to reboot device
many other fixes and code rework
v3.0:
SlimBean apktool ((de)compiling also with inverted folders from trds)
ADB (AndroidDebugBridge for pushing files to your device)
Some Links in the tool for support and donation
v2.2 Beta1:
apktool 2.0.0
Details:
Details
v1.5.x -> v2.0.0
Java JRE 1.7 is required!
Update apktool to v2.0.0
aapt is now included inside the apktool binary. Its not required to maintain your own aapt install under $PATH. (However, features like -a / --aapt are still used and can override the internal aapt).
Remove framework $HOME/apktool/framework/1.apk or manually update via (FrameworkFiles)
Eagle eye users will notice resources are now decoded before sources now. This is because we need to know the API version via the manifest for decoding the sources.
Parameter Changes
Smali/baksmali 2.0 are included. This is a big change from 1.4.2. Please read the smali updates here for more information.
-o / --output is now used for the output of apk/directory.
-t / --tag is required for tagging framework files
-advance / --advanced will launch advance parameters and information on the usage output.
-m / --match-original is a new feature for apk analysis. This retains the apk is nearly original format, but will make rebuild more than likely not work due to ignoring the changes that newer aapt requires.
After [d]ecode, there will be new folders (original / unknown) in the decoded apk folder.
original/ = META-INF folder / AndroidManifest.xml, which are needed to retain the signature of APKs to prevent resigning. Used with -c / --copy-original on uild.
unknown/ = Files / folders that are not part of the standard AOSP build procedure. These files will be injected back into the rebuilt APK.
apktool.yml collects more information than before
SdkInfo = Used to re-populate the sdk information in AndroidManifest.xml since aapt requires it to be passed at runtime.
packageInfo = Used to help support Android 4.2 due to renamed manifest packages. Automatically detects difference between manifest and resources and performs automatic --rename-manifest-package on uild.
versionInfo = Used to re-populate the version information in the AndroidManifest.xml since aapt requires it to be passed at runtime.
compressionType = Used to determine the compression that resources.arsc had on the original apk to duplicate on uild.
unknownFiles = Used to record the name/location/compression type of non-standard files in Apk.
v2.1:
fixed freezes
bigger UI for better overview
option to save log to a text file
other small fixes
v2.0:
complete code rework
folder structure for a better overview
decompiled, recompiled, signed files will be located in their own folder
no more messy file handling
added radio buttons for choosing jar or apk
some graphical changes
added info button in the "installing framework" section
V1.2:
Added ability to decompile and recompile ".jar" files
Added baksmali
FolderBrowserDialog: If you push the "browse" button you are in the right directory now and needn't to scroll and search the "AndroidApktool" folder
other small fixes
V1.1:
Added ability to sign .apk
Changed comboboxes to browse buttons
bigger log - screen
Initial Release
- Latest mod version
Latest version is: 3.5.9 (23.10.2018) updated by bovirus
This version is based on original v. 3.5.9 by Flextrick plus with these updates
- apktool (by iBotPeaches) v. 2.3.4 stable
- apktool commands list
- baksmali/smali (by JesusFreke) v. 2.2.5 stable
- baksmali/smali command list
- Android Build Tools (by Google) v. 28.0.3 stable
- Android Build Tools commands list
- Android Platform Tools (by Google) v. 28.0.1 stable
- Android Platform Tools commands list
- 7zip (by Igor Pavlov) v. 18.05
- DOS batch updated (now support file names with spaces)
With the DOS batch (file AMT.BAT) you can
- install framework file
- select application
- decompile application
- compile application
- sign application
Android Multitool v. 3.5.9 (updated) - Download
- Android Multitool previous version
Library of previous version (Google Drive)
Note: Please take care that v. 3.5.9 (stock) included in the Google Drive repository DON'T include all updates reported before.
- Use always updated framework-res.apk
If you get error during decompilation/compilation of the apk, please check if you are using and updated version of framework.res.apk.
Please try to search, find and download an updated version of framework.-res.apk
Note: I suggest to rename the framework downloaded file name (without spaces) adding some info about it (like brand-model of device and Android version), like
framework-Samsung-S8-Android-7.1.2.apk
put the file in it in Framework-Files sub-folder of Android Multitool and install it in Android Multitool.
Then try again to decompile/recompile the application.
- External references
- apktool by iBotpeaches
apktool by iBotPeaches - XDA thread
apktool by iBotPeaches - XDA thread
- baksmali/smaly by JesusFreke
baksmali/smaly by JesusFreke - Download (bitbucket.org)
baksmali/smaly - XDA discussion thread
baksmali/smaly by JesusFreke - Source (Github)
- 7zip by Igor Pavlov
7zip by Igor Pavlov - Tool to decompress/compress files
- Android Platform Tools by Google
Android Platform Tools by Google - latest Windows version
..
Very nice tool!
One feature request, could you have a checkbox for say the -b command so that we can get rid of the useless .linexx and .prologue lines? That would make this tool perfect
Another feature is adding the twframework-res.apk as a framework file? Thats essential for modding samsung system apk's. I usually have to install both twframework-res.apk and framework-res.apk before decompiling. Maybe adding 2 slots for the framework in the tool?
Thanks again!!
Good work bro....
Very nice..
Sent from my GT-S6312 using xda app-developers app
clark44 said:
Very nice tool!
One feature request, could you have a checkbox for say the -b command so that we can get rid of the useless .linexx and .parameterxx lines? That would make this tool perfect
Another feature is adding the twframework-res.apk as a framework file? Thats essential for modding samsung system apk's. I usually have to install both twframework-res.apk and framework-res.apk before decompiling. Maybe adding 2 slots for the framework in the tool?
Thanks again!!
Click to expand...
Click to collapse
Sure, adding a second slot will be no problem!
But I don't know what you mean with this checkbox, could you explain me exactly what you mean?
~ via Nexus
Flextrick said:
Sure, adding a second slot will be no problem!
But I don't know what you mean with this checkbox, could you explain me exactly what you mean?
~ via Nexus
Click to expand...
Click to collapse
When I decompile using baksmali this is the command I run...
Code:
java -jar baksmali.jar -b -o c:/smali c:/smali/classes.dex
The -b command prompts baksmali to remove all .line type code from the smali.
Here is an example .smali file before and after the -b command...
BEFORE: http://pastebin.com/gYKQ90cW
AFTER: http://pastebin.com/17i8k1X2
This method of decompiling smali makes it much much simpler to compare to other code.
Thanks!! :highfive:
Ah, I'm understanding. Yes, I think that's possible as well!
~ via Nexus
Flextrick said:
Ah, I'm understanding. Yes, I think that's possible as well!
~ via Nexus
Click to expand...
Click to collapse
Cool. Cant wait
One more thing, will you be adding the ability to decompile more then one apk/jar?
At once? Would work, I think.
Two possibilities:
The first apk decompiles, and then the second one
Or: Both are decompiling at the same time, but in two different processes.
~ via Nexus
Flextrick said:
At once? Would work, I think.
Two possibilities:
The first apk decompiles, and then the second one
Or: Both are decompiling at the same time, but in two different processes.
~ via Nexus
Click to expand...
Click to collapse
One then the second and so on would save the most memory and prevent crashes on weaker machines
androidapktool.exe does not open on my win 7 32 bin in admin mode.... i have java 7u25 installed.
need java 6?
Flextrick said:
ANDROID APKTOOL
exe crashed on my PC
Win 7 x64, Java 7 w/ update 21 (64-bit) installed.
(AMD FX-8120, 16Gb ram)
Just try with java 6
Click to expand...
Click to collapse
fvadym said:
Flextrick said:
ANDROID APKTOOL
exe crashed on my PC
Win 7 x64, Java 7 w/ update 21 (64-bit) installed.
(AMD FX-8120, 16Gb ram)
Just try with java 6
Click to expand...
Click to collapse
AndroidApktool.exe won't start, neither with 6u45 nor with 7u25 (latest versions)
whats wrong... ?
i have copied framework-res.apk into C:\AndroidApktool from my samsung galaxy s3 i9300, FW XXEMD3 / 4.1.2 jelly bean.
i tried to run it as normal and as an adminstrator... nothing happened at all.
Click to expand...
Click to collapse
yeah not running on windows 8 either
is there something we have to install, too?
Hello, there can be a lot of things.
Maybe you are missing the .NET framework, or some dll´s.
I also uploaded a new .exe just for testing. New is the progressbar.
Download: http://www.mediafire.com/?6y7qi0x8h9q6pt7
Cheers
Flextrick said:
Hello, there can be a lot of things.
Maybe you are missing the .NET framework, or some dll´s.
I also uploaded a new .exe just for testing. New is the progressbar.
Download: http://www.mediafire.com/?6y7qi0x8h9q6pt7
Cheers
Click to expand...
Click to collapse
Test new .exe......
best regards "D"
Could anybody test trying to install .NET Framework?
Hopefully I get a solution for this problem, otherwise I'll make an Installer.
~ via Nexus
@Flextrick
I have NET Framework 4.5, Java 7 Update 25 and Java SE Development Kit 7 Update 25.
Edit:
You've got a Private Message
"D"
Ok. For starting the Tool is no Java necessary.
I think the dll's are missing, hopefully I get it working as far as possible.
~ via Nexus
{
"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"
}
This software will ask for sudo permissions in your machine to download and install all required tools for this program to run correctly, also, it'll execute chmod and chown to this program files and ~/.megarc (if exists) for the correct functioning of all the code, I'm not responsable if this program breaks your Machine (which it shouldn't be able by no ways). When you run for the first time this program, it will proceed to his first run configuration after the user authorization.
Welcome, I've been developing this program a long time ago with my free time after college, this is my first project made in Bash, the main purpose of all this software is to make a lot easier the process of building a Kernel, no matter which device you're building to (excluding MTK and those without source). This program will automatically download all required tools for Kernel building (~1.5GB), including the CrossCompiler (GCC arm/arm64) and other misc tools. You don't need a lot of knowledge to build your kernel with this software and it has all the tools for automatically build everything in just one command!
Requeriments:
A machine with Linux
Git
This program
Once you've downloaded the program to your Machine, you have to cd with Terminal to where you downloaded all the files and execute "core.sh" (bash core.sh or . core.sh) (Like this Example), this is indispensable every time you want to run the program, because it sets the program paths (Otherwise it'll not work)
Now, How it works?
Once you run the program, if it's for the first time then it'll automatically download all required tools and install them, after this it's time to setup your environment. You'll see a folder named "source", you have to put there the folder with the Kernel source contents like this and another folder named "templates" where you can set your AnyKernel (only AnyKernel for now) templates for different devices (Or just use the local one).
That's all, this program only needs you to set the Kernel source, now you've to run again core.sh and it'll prompt to you all the data needed for that session, like the name of the kernel, target android, version, kernel source folder, etc... When you've to select the architecture of your device, arm or arm64 and it'll download the correspondent CrossCompiler (GCC 4.9), after this, it'll promt to you how to set Kernel Installer template, the first option is to extract the local AnyKernel source into "./out/ak_template/" (Thanks to @osm0sis), second option is for select a user template from "./templates/" folder and the third option requires you to set manually the installer template inside "./out/ak_template/" similar or like this (Remember to configure it).
When it promt to you the variant, you've to put preferably the codename of your device (For example: Oneplus One codename is "bacon") and then select a defconfig for that device (For example: For Oneplus One it would be "lineageos_bacon_defconfig"), now that the program knows for which device It's going to compile, (You can add more variants) then, you can enable the KernelDebug option to enable the creation of the Device tree image (Applies for arm devices only) and allow the kernel source cleaning on every compiling process...
Now, let's get into the commands:
Command: "essentials <flag>": Here is where you start once you finish setting all the configs, 'essentials' is the main command of this program, but it only works with flags, otherwise it'll display the flags information that I'm gonna show right now:
Flags:
--kernel (Start the process of compiling your kernel)
--dtb (Generates the device tree image, applies to arm devices only)
--anykernel (Builds a installer for your kernel based on Anykernel by @osm0sis)
--upload (Uploads your Kernel installer to the root of your MEGA storage)
--all (This flag does all processes mentioned above)
You can combine all the flags except for "--all", because this one already does everything, also, no matter in which order, all the functions are going to be done in order to prevent an error (For example: 'essentials --anykernel --kernel' will build the kernel and then build the installer).
Also, after the first run, theres a file named: "defaultsettings.sh", it has a variable inside named "DSENABLED", if you set it to 1, the program instead of prompt you for information when you run "core.sh", it'll take all the config directly from that file, just make sure you've configured it first. :good:
Command: "auto <device> <flag>": This command allows you to make pre-configured files for a specified device, it requires that you have executed the program core.sh for the first time because it stores some config in your ~/.bashrc file, then, you can turn on or restart your machine and this command will still be available for it's use.
When you run 'auto' and next to it you specify the device (for example: auto oneplus), if the device (oneplus) doesn't exist in the device database (./resources/devices/) then, it'll promt to you all the data required for kernel, dtb (if applies), anykernel and upload process.
Once you have configured your device it'll be stored and when you run again the command 'auto' followed by the device name you configured before, (for example: auto oneplus) it'll load that device config file and build everything automatically (Kernel, dtb if applies, anykernel and upload if its enabled).
The Flags for this commands are:
--edit (Opens you the <device> config file for editing with nano)
--remove (Simply removes the <device> config file)
For more information I highly recommend to read the README.md in this program source on Github (It contains a more datailed and complete information).
This program has been tested and used on the following Linux distributions:
Ubuntu
Debian
I will really appreciate any feedback about how it performs on other Linux distributions
You can contact me with a PM (private message) here or in my Telegram group! (I'm @ArtxDev)
Me, @Stayn (Artx)
@osm0sis for his AnyKernel
This project on Github is open to pull requests, I will not hesitate to dedicate you a space here if you contribute for this project :good:
I'll be updating this program fixing bugs and bringing new features :good:
If you like it and want to do a small donation it for sure is gonna help me a lot and keep me motivated! :laugh:
Thank you and enjoy it!
XDA:DevDB Information
Kernel Building - Essentials, Tool/Utility for all devices (see above for details)
Contributors
Stayn
Source Code: https://github.com/KB-E
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-07-30
Created 2018-07-09
Last Updated 2018-07-30
In progress...
Mini Guides for absolutely newbies in progress...
Thanks
I just tried it and I get an error:
./core.sh: line 125: .: defaultsettings.sh: file not found
This file exists in Kernelbuilding-essentials directory though.
EDIT:
I tried to change ". defaultsettings.sh" with the full path of this file in line 125 and then I get another error on line 126
err: unary operator expected
dancer_69 said:
I just tried it and I get an error:
./core.sh: line 125: .: defaultsettings.sh: file not found
This file exists in Kernelbuilding-essentials directory though.
EDIT:
I tried to change ". defaultsettings.sh" with the full path of this file in line 125 and then I get another error on line 126
err: unary operator expected
Click to expand...
Click to collapse
Don't use sh to execute core.sh, use ". core.sh" or "bash core.sh"
Stayn said:
Don't use sh to execute core.sh, use ". core.sh" or "bash core.sh"
Click to expand...
Click to collapse
Thanks, I'm using arch linux and zsh as default. With "bash core.sh" the script runs fine.
dancer_69 said:
Thanks, I'm using arch linux and zsh as default. With "bash core.sh" the script runs fine.
Click to expand...
Click to collapse
Thanks for the feedback! If you have any other problem tell me
Cool project! You should specify bash in the shebang (normally the first line of a shell script) to fix issues where bash isn't default:
Code:
#!/bin/bash
osm0sis said:
Cool project! You should specify bash in the shebang (normally the first line of a shell script) to fix issues where bash isn't default:
Code:
#!/bin/bash
Click to expand...
Click to collapse
Done! Thanks
Hey guys, now Kernel Building - Essentials it's stable!
I've been working on fixing a lot of bugs and updating the program structure, now that the structure is totally defined and I don't need to change it anymore, I'll upload the first release at GitHub, version 1.0 and the next versions will be coming with a file to update your old version on KB-E (In this way there's no need to clone the repo again and again and merging your devices or configuration...)
There is all the updates and changes:
- Added a folder for Multiple Installers Templates: I've been thinking that anyone could have various kernel projects for different devices, so this means, that the templates for the installers needs to be different, so, now you can trow all the templates you want inside "templates" folder and the program will prompt to you which one you'll use for the current session (using core.sh "essentials" command) or a pre-configured device (using auto.sh "auto" command)
- Replaced option 2 in the program installer template config method, removed the ability to download the template from your MEGA Cloud and replaced by a selection of user templates inside "./templates/" folder
- Changed the "setuptools.sh" file name to "programtools.sh" because, all program misc functions are going to be stored there and "programtools" makes more sense
- Fixed a bug that happened when you didn't gave to the program the device variant (or codename) and then, "essentials" and "auto" command were not working, now the program forces you to set it (You can set your device name as device variant but it's preferably the device codename)
- Now when the program downloads the correspondent crosscompiler, it shows you the process
- Added the package "device-tree-compiler" into the download list of the function "installtools" (Executed when you run the program for the first time), this package is necessary for some arm64 sources to build device tree
- Fixed a annoying bug that cd's you to your "~/" directory instead of the current directory you were after executing "essentials" or "auto" command
- Now core.sh doesn't change the whole file permissions of your sources (sorry for this)
- Added a boost functionality for "auto" command that sums 2 threads to the compiling jobs when compiling the kernel (Recommended for machines with more than 2 real cores)
- Updated README.md
I would really apreciate some feedback guys, if you have any problems or you need help, feel free to contact me via my Telegram Group, enjoy!
Hi, it looks good so far...I have an MT6580 that I play around with but it's been stuck on kernel 3.10 for a long time. I've spent weeks trying port kernel from other MT6580 devices but haven't gotten any success yet. I got through the core.sh part. Is the essentials commands next ? I don't see it anywhere in the program.
Now I know how you automatically upload kernel to Mega Drive using code.. Unfortunately my G3 was Died...:crying:
Anyone know how to remove unwanted feature from a cooked/compiled kernel?
Excuse me, does this work on Ubuntu that runs on Windows Subsystem for linux?
By the way, thank you for the amazing artx-powered TWRP on my G3.