Related
NEWS:
Just a teaser to people who use Theme Pro...
I am completely re-building the program in Java, what does this mean?
- Theme Pro will work on every OS, whether it is Windows, Mac, Linux, etc..
- Theme Pro now has a GUI, no more command prompt or terminal windows.
- Functionality and ease-of-use * 1000
I am building Theme Pro from scratch in Java. I am constantly developing the application and I will upload betas on a regular basis. Just because it is a beta does not mean it is dangerous, it just means some buttons do nothing yet
Attached is ThemePro, to run it, just double click it like any application, note it is very limited in functionality but please show your support by letting me know what you think, thanks!
REQUIREMENTS:
1) Java.
2) ADB is set up.
JAVA CHANGELOG:
v1.3
- ADB Application List (saves a list of all installed applications on your computer).
- ADB Delete (lets you delete files/folders on your device).
- ADB Pull (lets you copy files/folders from your device to your computer).
- Device check for bootanimation and font menus.
Code:
v1.2
- ADB Logcat with file chooser - [URL="http://img526.imageshack.us/img526/8805/screenshot20101111at002.png"]SCREENSHOT HERE.[/URL]
- ADB Reboot normal/recovery/fastboot completely working.
- Warning if device is not connected and the ADB button is clicked.
- Warning if ADB is not installed on machine.
v1.0
- Initial release.
{
"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"
}
-----------------------------------------------------------------------------------------
WHAT IT DOES:
This application use to allow you to modify the main Android framework files responsible for theming your phone, however...
Theme-Pro has evolved where it is not just for theming your phone. With the ability to extract, decompile/compile, flash ANY APK/JAR file, in-built ADB, font manager, boot animation/audio manager, ROM manager, and the ability to make and restore device back-ups, Theme-Pro has become a complete Android device manager, providing you with a wide variety of features, some of which are shown below:
01. Edit ANY APK/JAR file
02. Auto-extract files from a zipped ROM (supports multiple files)
03. Automatically decompile files
04. Automatically compile the files
05. Flash these files to your device
06. Backup device applications and media
07. One-click ADB push (supports multiple files/folders)
08. One-click ADB pull (supports multiple files/folders)
09. One-click ADB install (supports multiple files)
10. One-click ADB delete (supports multiple files/folders)
11. List all applications on your device
12. One-click ADB logcat
13. ADB dial (allows you to dial numbers from your computer)
14. Remotely reboot your device
15. Remotely reboot your device into recovery
16. Remotely reboot your device into fastboot
17. Backup boot animations and audio
18. Flash boot animations and audio
19. Customize ROM apps before flashing (supports multiple ROMs)
20. Automatically zip-align a ROM (supports multiple ROMs)
21. Automatically deodex a ROM (supports multiple ROMs)
22. Automatically sign a ROM (supports multiple ROMs)
23. Backup system fonts
24. Flash new fonts
NOTIFICATIONS:
Just to say, I enjoy working on this application, so please feel free to post ANY feedback/suggestions/complaints/bugs and comments. Thanks
DONATIONS:
A BIG THANKS TO:
- Sven
- Matthias
- Josh
For the donations received!
If you would like to donate, then please click the 'Donate' button in my signature.
It is very highly appreciated - it is not easy being a student
CHANGELOG:
v5.3
- Ask if all files are in same location ONLY if there is more than 1 file.
- Resource and program check on startup (Java etc).
- Error replies more efficient.
- Script cleanup and optimisations.
- Removed 200kb from overall file size
OLDER RELEASES:
Code:
[SIZE="2"]v5.2
- ADB from the same location (so location is only entered once) - [URL="http://forum.xda-developers.com/attachment.php?attachmentid=399841&d=1284336249"]SCREENSHOT HERE[/URL]
- Fixed error check for ADB services.
- Removed rebooting into recovery for writing to /system as most ROMs now support this.
v5.1
- New code added to ADB services - [URL="http://forum.xda-developers.com/attachment.php?attachmentid=398205&d=1284069111"]SCREENSHOT HERE,[/URL] [URL="http://forum.xda-developers.com/attachment.php?attachmentid=398233&d=1284073133"]HERE,[/URL] [URL="http://forum.xda-developers.com/attachment.php?attachmentid=398234&d=1284073133"]AND HERE![/URL]
- New code made even better and more efficient.
- Fixed all bugs found and added more checks to new code.
v5.0
- New code makes the script much more efficient, completely re-built - [URL="http://forum.xda-developers.com/attachment.php?attachmentid=396966&d=1283890212"]SCREENSHOT HERE[/URL]
- New code also supports multiple variables, completely re-built - [URL="http://forum.xda-developers.com/attachment.php?attachmentid=397528&d=1283976854"]SCREENSHOT HERE[/URL]
- Generic APK/JAR scripts as well as ROM manager now self maintaining.
- Framework files removed, generic APK/JAR is now better.
- Extract generic APK/JAR scripts now delete folders that were created if Error occurs.
- Error detection now detects ALL types of errors.
- Java functions are now CD'd to to prevent rare 'Could not locate Directory' errors.
- 'Check if device is connected' script updated to support Recovery.
- Work Directory layout improved
- Instructions updated.
- De-odexing script made more user friendly.
v4.2
- Rom manager has a build feature making it more efficient.
- ADB logcat.
- Remote dial.
- Automatic work directory.
- Fix permission problem.
- Added comments and improved script layout to encourage users.
- ADB list now allows more than one file to be created.
- All bug fixes so far corrected.
- If bootanimation.zip is not found, then look for it in other locations.
- Backup device Apps/Media.
- Provide more feedback.
- New menu layout to support more features.
- Make directory code more efficient.
v4.1a
- Fixed zipalign (resource file named incorrectly).
v4.1
- Completely tested and no bugs found on both MAC and LINUX!
- Completely new menu AND script layout.
- Generic APK/JAR editor!
- Auto-detect + setup ADB for Linux users.
- ADB list applications are now sorted alphabetically.
- Added a phone reboot menu.
- Ask for confirmation when clearing/deleting Work Directory.
- Browser fix for Linux.
- ADB pull bug fix.
- Base name fix for Linux.
- Fixed spaces in names bugs.
- Auto-start ADB server on application start-up.
v4.0
- Completely rebuilt scripts into one portable file.
- Much faster scripts/efficiency.
- Linux drag and drop issue fixed !
- Fixed Java path for Linux users.
- ADB list shows both Froyo A2SD and A2SD+
- Make directory now in-built into scripts for efficiency.
- Error replies now work for ADB scripts.
- Hidden Mac files deleted before making zips (.DS_Store).
- Fixed some bugs.
v3.7
- Now completely supports the editing of android.policy.jar.
- No longer have to type in "Name of new ROM" - done automatically.
- Fixed a LOT of bugs.
- ADB list now shows apps installed with Froyo A2SD.
- Better work directory names are used.
- Fixed a mistake in the services.jar compile/decompile script.
v3.6
- Option to backup your current fonts.
- Can now flash new fonts.
- ADB wait-for-device introduced to make things easier.
- Lots of bug fixes.
v3.5
- Added default option to all scripts to increase efficiency.
- Menus automatically read input - no need to press Enter.
- Customize ROM script now allows you to edit data/app/.
- Better menu layout.
- Bug fixes.
v3.4
- Able to delete files on your device.
- Able to view and list all applications and data on your device.
- A new About page providing quick links to everything you need.
- Option to Tweet My Work - very quick and easy - would appreciate it :)
- Each script comes with easy-to-use instructions.
- Main Menu fixes.
- Main Menu prompts after clear/delete.
- Able to reboot into fast-boot.
- Able to shut-down your phone.
- More efficient script clean-up.
- Various bug fixes.
v3.3
- Major script clean-up.
- Script now starts up faster.
- Individual scripts now launch faster.
- Default value of scripts changed to 'Y' for more efficient use.
v3.2
- Better process feedback.
- More user interactive.
- All bugs of previous version fixed.
- Script clean-up.
- Spaces in file names are now accepted.
v3.1
- The app now works from all locations!
- No longer required to be on the Desktop.
v3.0
- Auto-detect Mac/Linux.
- Auto-setup for Mac/Linux.
- Validations added, scripts are completely interactive.
- Major script clean up.
- Ability to return to Menus from each script.
- Scripts auto-resize for best viewing.
- Can ADB push/pull from anywhere in the device.
- New application icon.
v2.9
- You can now completely deodex a ROM + option to sign.
- Auto Terminal resize for better viewing.
v2.8
- Option to zip-align a ROM.
- Major script clean-up.
- Changed some scripts with optimized ones, zip functions are much faster.
- New splash screen.
- Each script has a description at the top.
- Work Directory script optimized.
v2.7
- New ROM manager menu.
- You can now change ROM apps before flashing + option to sign.
v2.6
- Changed appearance, more user friendly.
v2.5
- Option to automatically flash files.
- Re-designed all the scripts, much more clean.
- Removed sleep function from all scripts.
- More user-friendly scripts.
v2.4
- Fixed a bug where ADB reboot/reboot recovery would exit the script.
- Fixed system mounting bug in the boot animation scripts.
v2.3
- Able to backup your current boot animation / boot audio.
- Able to flash a new boot animation / boot audio.
v2.2
- Linux users are now able to view their working directories.
- Linux users are now able to view their own user manual from the menu.
v2.1
- Fixed the exit.
- Fixed some aesthetic features.
- Scripts now close once run for better performance and exit ability.
v2.0
- Should now be completely stable on both Mac and Linux systems.
- Fixed shell exiting problems for Linux users.
- Fixed case sensitivity problems for Linux users.
v1.9
- Allows for both 'Y/N' and 'y/n' :D
- Fixed ADB for both Linux and Mac.
- New setup script to distinguish between Linux and Mac.
v1.8
- Universal release for both LINUX AND MAC.
- Scripts now check for Work Directory.
- Have fixed the option to clear the Work Directory in the individual menus.
v1.7
- Completely redesigned all of the ADB scripts.
- ADB Push/Pull working perfectly.
- ADB now supports writing to the system.
- Sign ROM script now supports folders as well as zipped files.
- ADB reboot is now available.
- Ability to completely delete (not clear) working directory.
- New application icon.
v1.6
- Updated user manual with new ADB features.
- Script cleanup.
- Made the file even more user-friendly. See it to believe it ;)
v1.5
- A new ADB menu.
- ADB pull.
- ADB install.
- Better signing functionality.
v1.4
- ADB is now built into the application.
- Automatically ADB push file/ROM to SDCard.
- Option to automatically reboot into recovery.
v1.3
- Fixed menu switching bugs.
- Improved the ROM-signing process.
v1.2a
- Added a user manual which is accessible via the main menu.
- Theme-Pro now comes in a smaller .dmg format to save space and improve ease-of-use.
v1.2
- Ability to insert files into a ROM
- Fixed the script responsible for extracting com.htc.resources.apk from a ROM.
- Improved and cleaned usability of the menu system.
v1.1
- Each menu deletes its own working directory, not all directories
- Automatically compile into a ROM.
- Automatically sign a ROM.
v1.0
- Initial release.[/SIZE]
SCREENSHOTS:
Was wondering if it is possible to copy a framework from a theme and put it into a ROM's framework with this?
I tried doing it manually but BIG **** happened lol.
UltraLinx said:
Was wondering if it is possible to copy a framework from a theme and put it into a ROM's framework with this?
I tried doing it manually but BIG **** happened lol.
Click to expand...
Click to collapse
That's a great idea, will have it done by tomorrow
cgrec92 said:
That's a great idea, will have it done by tomorrow
Click to expand...
Click to collapse
How the hell do you even start the application?
UltraLinx said:
How the hell do you even start the application?
Click to expand...
Click to collapse
Unzip the attachment and click on the file called CLICKME, you're using a MAC right?
cgrec92 said:
Unzip the attachment, open it and click on the file called CLICKME, you're using a MAC right?
Click to expand...
Click to collapse
Nope, using Windows 7.
Can you add the ability to sign zip files that aren't theme related?
UltraLinx said:
Nope, using Windows 7.
Click to expand...
Click to collapse
check the 1st post ^^ its only for Mac
Ireas said:
check the 1st post ^^ its only for Mac
Click to expand...
Click to collapse
ahh ****, i didn't see that
dancedreamfly said:
Can you add the ability to sign zip files that aren't theme related?
Click to expand...
Click to collapse
I'm on it now, will add the ability to sign individual files or entire ROMs.
Now do you mean to sign a file that's already zipped, or signing a folder into a signed zip?
Ok, atm i'm adding the choice of compiling each of the files into the ROM of your choice, all you do is drag and drop the ROM into the window and it will remove the current file within the zip, replace it with your modified one, AND sign it.
Will add after the ability to sign ANY file into a ROM although this required more user input.
Anyone have any feedback on the app?
Looks brilliant cgrec92 ......
not a mac user myself, so i guess you have been asked, but any chance this will be coming to us lowly ( ) PC users ????
great job again...!
That is nice ! I also update my thread ( http://forum.xda-developers.com/showthread.php?t=722993) for creating a custom framework by promoting your thread (for Mac Users)
Sulphy said:
Looks brilliant cgrec92 ......
not a mac user myself, so i guess you have been asked, but any chance this will be coming to us lowly ( ) PC users ????
great job again...!
Click to expand...
Click to collapse
Would be difficult as CMD is very different from Terminal, will have to take a look into CMD and see if I can work something out
Fightspit said:
That is nice ! I also update my thread ( http://forum.xda-developers.com/showthread.php?t=722993) for creating a custom framework by promoting your thread (for Mac Users)
Click to expand...
Click to collapse
Thank you very much
Version 1.1 released, big changes.
Changelog in first post
Let me know what you guys think of this.
Version 1.2 released.
Changelog in first post.
All feedback/requests welcome
Thanks for hearing my request out. Been using this since your initial release, and it's great! Keep it up!
dancedreamfly said:
Thanks for hearing my request out. Been using this since your initial release, and it's great! Keep it up!
Click to expand...
Click to collapse
Thanks for the feedback, it's really quiet around here so I really don't know how people are finding the application so thanks
All requests are welcome!
Version 1.3 released.
Fixed a couple of bugs and improved scripts.
Would love to give you feedback, but i'm on win7... :/
Nevertheless, looks like good work, please keep it up!!!!
zsdr said:
Would love to give you feedback, but i'm on win7... :/
Nevertheless, looks like good work, please keep it up!!!!
Click to expand...
Click to collapse
Thanks!
HOW to install a distribution of GNU/Linux and configure the necessary tools for the development of ROMs
Autores: TugaPower aka danieldmm e porfirio
Firstly, it is important to say that GNU/Linux is open source software / free, robust, reliable, free and easy installation for any user, even if you have few computer skills.
There are dozens of distributions of GNU/Linux, all available free at: http://distrowatch.com/, so choose that of your choice and according to the hardware capabilities of the machine will be installed where the distribution chosen by you.
The choice of authors this "HOWTO" is based on the distribution of GNU/Linux, Ubuntu 11.10, with the XFCE desktop environment and also the GNOME desktop environment. This is abolished by default the manager's main Gnome desktop environment and in its place put XFCE, to perform the daily tasks of work, which is very lightweight and fast. Or if they want to be more direct, Xubuntu and will soon install from scratch, which will get the same results. Personally, I'm a fan of this graphical environment (XFCE), attending to its lightness, speed, customization, etc..
What will be explained in this HOWTO:
1. Install Ubuntu or any other distribution, such as: Xubuntu, manager native XFCE desktop environment, Kubuntu, manager native KDE graphical environment; Lubuntu, manager native LXDE graphical environment, which uses less hardware resources on the machine all present in this work. Basically, we are always talking about Ubuntu, what changes is only the GUI (Graphic User Interface), where the user goes to work.
2. The process of installation and basic configuration for any of these variants, it is always the same.
3. Do not expect to find in this work, the whole process complete installation and configuration. Only the main roads and where possible, with visual aids. However there are situations so redundant, that does not need that same help. Not the purposes of this HOWTO, other possible configurations, eg setup SAMBA, APACHE, a home FTP server, desktop, etc..
4. Let's begin as follows:
4.1 Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer;
4.2 From the field 16 is a normal installation via live DVD of Ubuntu (Xubuntu, Kubuntu, Edubuntu, Lubuntu).
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU/Linux.
4.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
GETTING STARTED
1. Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer.
1.1 To start this process, you must be made to download an image of the Ubuntu operating system for the machine architecture, or x86 (for CPU 36 bit) or x64 (for 64-bit CPUs).
1.1.1 However, this day, there is some controversy on this subject. Some say that if the machine has 4GB of RAM or more, we always use the 64 bit version, even if the CPU is x86 and also say that if the machine has less than 4GB of RAM, we use the 32 bit version regardless of the CPU is x36 or x64.
NOTE: Rarely, modern computers, whether desktops, laptops, at least have at least 4GB of RAM standard. However, do not relinquish that each CPU (x86 or x64), must have the OS corresponding to your architecture. Therefore it is up to each one choose the best option.
2. ISO Images
2.1 Ubuntu 02.01 11.10 (32bit)
2.2 Ubuntu 02.02 11.10 (64bit)
3.Universal USB Installer
3.1 Now we do download the appropriate version of the distribution, we will have to download the USB Installer: www.pendrivelinux.com/downloads/Universal-USB-Installer/
But what is the purpose of this installation process?
3.2 Firstly, we can be a machine, you have not installed a drive read / write CD / DVD.
3.3 Secondly, avoid using a CD or DVD drive for installation.
4. Run the USB Installer, as Administrator of the OS and this not to happen errors during the copy of the OS to the thumb drive. This procedure is performed as follows:
- Click on the icon of the program with the button on the right mouse button and select Run as Administrator option.
5. After installing the USB Installer, run the program and click on I Agree.
{
"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"
}
6. Now we set the distribution of GNU/Linux, we will be using. I choose Ubuntu 11.10.
7. Now calm down! I hope you remember where it was saved the iso image of Ubuntu! Only then will the USB Installer will be able to recognize and perform the installation on the pen drive. Will normally be in downloads.
8. Insert the flash drive and expect it to be recognized by Windows. In this case explanation, their location is in F.
9. At this point, we select the Format F: Drive to FAT32.
NOTE: If you wish, can create a little more memory to the pen, in case it is likely to change. This is an optional. If your interest, as it is put in the picture.
Now we have everything configured properly, we will click Creat.
10. At this point you will get a WARNING message. All contents of pen drive will be erased. Click YES and continue.
11. Now it is time for a coffee, etc., etc. and wait for the installation process to complete. After this step, we will be ready for installation on the computer distribution.
11.1 While the above task does not end, we can and must perform other actions, such as creating a partition for the Ubuntu operating system.
11.2 Let's Start Menu;
11.3 Clicking the right-click Computer and then Manage;
11.4 Now on the left menu, click Disk Manager;
Arrived here, the C partition, let's click and select Shrink Volume.
12. Let us wait quietly, and very soon we will be faced with the option to reduce the partition chosen. For a minimal installation of Ubuntu, will require approximately 10 GB. However, if we want to later install the updates, music, videos, etc. ... recommend 25 GB. To be closer to the 25GB, 26GB put!
13. The next step is to reduce and click new partition will be marked in black. We will then activate this partition:
13.1 Click on the partition, with the right mouse button and select New Simple Volume.
13.2 Click Next> Next> and choose a letter to the new drive (eg U).
13.3 Now let's change the Volume Label. Put Ubuntu.
13.4 Next Run. We have created the partition and active.
NOTE: Wait now that Universal USB Installer program in the following screen appears indicating that the installation was completed and then click Close.
14. Restart the computer.
15. Immediately press F12 and select USB stick and then press ENTER.
15.1 will appear something like this:
Calm ..... very quiet .... Choose the option Install Ubuntu on a Hard Disk.
16. Now it is like to install via DVD, which I dispense to comment on "How to install Ubuntu 11.10 per DVD." See 4.2 The field from the field 16 is a normal installation of Ubuntu live via DVD.
16.1 After appearing Choose Setup Language, Portuguese choose and click Next. (You pick the language that you anderstand)
Preferably, you must have a fast Internet connection, so that the OS be upgraded soon. In the situation of not being currently available internet connection, do not put the "seen". No problem your installation will proceed smoothly. You can do it later.
17. Then will click on: One more thing, in order to choose the partition for installation.
18. CAUTION ... CAUTION!
18.1 In this field, we have all the possible CARE! The Windows partition can die!
18.2 Should be selected before the partition created in Windows (which is named Ubuntu), and then click Modify. After selecting the partition that was created on Windows (Ubuntu). In the new partition size, and put 21,000 Mount Point select /. After running OK.
The aspect should be this:
19. Now let us take the remaining space in the example 1490MB. Click Modify, and followed by the option Use as we choose and swap area and click OK.
It should be something like this:
20. Next, click Install Now and wait ......
21. Choose the location of the user:
22. Now the installation of the default keyboard ....
23. Enter personal information and click Continue.
24. Installation completed. Reboot the PC.
25. And Behold .....
Choose from the boot menu option Ubuntu .... There is also the option Windows ... Choose!
26. I chose .... Ubuntu with the Gnome GUI!
7. There is a method, also very reliable, to expedite this process, but directed to Mint distribution, which can be obtained here: community.linuxmint.com/tutorial/view/744
NOTE: TugaPower friend and colleague, will use the Mint 12 in the process of compiling ROMs. (In this case S2 i9100 ROM 4.0.3 ICS)
Version used: Linux Mint x64 12 vKDE
Download Links: http://blog.linuxmint.com/?p=1927
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU / Linux.
4.3.1 Installing the JAVA
Open the Synaptic package manager and install the openjdk-7-jdk and mark their dependencies:
Approval for the changes made:
Download the required files:
Installation of the necessary files and OpenJDK 7:
Now we have to install JAVA on the machine fully realized, we will proceed to their inspection.
To do so open the command line terminal to write the following command: java-version
4.3.2 Check if the package is installed 7zip more specifically p7zip-full, if not select for installation:
Once this is done we can then proceed with the installation of the Kitchen.
4.4 Installing the Kitchen
4.4.1 Initial Procedures
All information to carry out this section were collected on: forum.xda-developers.com/showthread.php?p=5626292#post5626292
Therefore, our choice falls on dsixda Android's Kitchen (Support Several devices)
(The Custom ROM made in this Guide its based to the Galaxy S2 i9100)
Download link of Kitchen: http://github.com/dsixda/Android-Kitchen/archives/master
Informational Page on Kitchen: http://forum.xda-developers.com/showthread.php?p=5626292#post5626292
After these preliminary procedures have been performed, we proceed to next steps.
By default, you will be allocated in the Downloads folder files.
4.4.2 Click on the file up with the right button of mouse and perform the extraction of the file to the Downloads folder:
4.4.3 Change the file name for kitchen (it's easier to work).
4.4.3.1 Move or Copy to folder or Personal Home:
They should stick with a structure like this:
4.5 Perform download the ROM Stock
NOTE: I personally recommend two sites:
http://forum.xda-developers.com/showthread.php?t=1075278
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regional
Download the ROM to be used in Kitchen, in this case we use the XDA, specifically the XWLP7:
NOTE: The screenshot references XWLP4 because at that time had not XWLP7
4.5.1 Download the kernel corresponding CF-root (This way remains CWM Recovery Busybox and SuperUser GB, if ICS SuperSU depends the kernel used to cook the ROM.
4.5.2 Download the kernels on CF-root: http://forum.xda-developers.com/showthread.php?t=1103399
NOTE: This case will be used the latest available to ICS, the CF-root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip
NOTE: It is already available in the XDA KERNEL CF ROOT XWLP7.
4.5.3 Copy the file from the ROM inside the Kitchen to the folder original_update
4.5.3.1 If the file is in the form *******. Tar.md5 have to remove the. Md5 so that it only ********. Tar
After these steps have been made in all its fullness, then we have all the necessary files to start our cooked
4.5.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
4.5.4.1 In order to run our furnace we have run the Kitchen in a command line also known as terminal or console, for it will open a command prompt within the folder Kitchen:
In order to execute the Kitchen just run the following command as root sudo. / Menu in the terminal:
6. First thing to do is point 1 or set a folder where we work. In this process the Kitchen will get to select and give the stock ROM original_update previously placed in the folder, simply enter the next screen and then select the ROM list:
Therefore, we select the first option because we only have a ROM in the kitchen, so just to enter a default because it's one
6.1 In the kitchen will then ask if we want to keep the name.
This name stock is organized as follows: WORKING_DATA_HORA, this can be changed to whatever you want, the only thing required is to keep the WORKING_
In this case I press the button to change the name ye WORKING_XWLP7_TugaPower:
To continue then just press Enter.
7. The kitchen will start the process of extracting the file from the ROM to the folder with the name we gave earlier WORKING_ ********
In this process we have to decide if we want to use the CSC (NET configuration and applications) that are included with the Stock ROM or NO.
By default this is set to YES ...
Thus, we can, because the Kitchen gives the following list of apks existing CSC and if we add the folder WORKING_ *****
Remember that in most cases, there is no problem in using the CSC Stock ROM, just advise not to use the apks the CSC because they are essentially propaganda NETWORK, which can be set to follow in the next menu to the Kitchen already well default to not add the apks:
Ready to the next step?
8. After the CSC will appear in the information regarding the boot.img, here we select the letter n because for the effect of Custom ROM do not need!
9. Then will come the question if we want to see information about the ROM.
This option is your choice will; default is Y. I personally put n. Now let's return back to the first screen which means that the necessary files are all ready ....
10. In this field, you may want to check whether there is a need to use option 2 and 3.
10.1 In the case of using the KERNEL Stock are advised to do option 2 and 3.
If the kernel you are going to use is for example the CF ROOT or any other that already have root then there is necessary to make the option 1 and 2.
10.2 In this case I will use the CF KERNEL, we will open the zip file of CF ROOT Kernel, find a file ****.tar, opening the file we find the zImage (KERNEL), selecting the zImage we proceed to the extraction process to the working folder of the Kitchen, in this case to the folder: Working_XWLP7_TugaPower
A new window will appear saying that the file already exists, just select and replace the existing ...
11. We will now switch to the Kitchen 7. Kitchen is a default to NO WIPE ROM, option 7 serves to change this ...
12. In this case I do WIPE version, you just will access option 7 in the next field and put y:
12.1 This procedure will eventually lead back to the main menu of the Kitchen. Now we have to think whether we want a ROM or deodexed ODEXED Stock ...
12.2 If we use a version ODEXED we can switch to the option 99 which will be explained below, because I'll use this version deodexed and before passing the option will be option 0 99: ADVANCED OPTIONS
IMG]http://i.imgur.com/XtfZp.png[/IMG]
13. Here I select option 11 to deodexed ROM:
13.1 Now we need one more aspect to consider: what kind of ROM, if GB or ICS.
In this case as I am using a ROM ICS will change the level of API's Kitchen and they default to GB, so I'll use the v
14. Then I confirm that I change the level of the API key y.
In this case I set the API level to 15 which corresponds ROM will be concerned that I'm using ICS 4.0.3:
14.1. Now set the API, I will proceed to the DEODEX ROM for option b, which is advised, because this way, will deodexed the system / app and system / framework.
15. Will be asked if you want a log deodex, this is your charge, if you put y, a file will be created in the root folder of the Kitchen with Deodex process, this log can be used to screen for possible errors that occur in deodexed; I always use the log file because the design is not great and always give way if there are problems in deodexed.
16. After this step made the Kitchen will carry out the relevant technical Deodexed ROM:
17. Now just wait, if you can go for a coffee or a cigarette because it still takes a bit if they do not get any errors and the process goes well deodexed will be presented the following screen:
18. Pressing the Enter, go to the submenu of Kitchen Advanced Menu.
We will then press 0 to return to the main Kitchen; next step we change the name of the build of the ROM (this information that appears in the menu on the About the Phone.
18.1 For this press the key 8 from the Main Menu of the Kitchen, in which case I will change to XWLP7 Stock by TugaPower:
http://i.imgur.com/I6ZXw.png[IMG]
19. Press Enter, then we will change back to the Main Menu Kitchen, now is the time better, create CWM zip file for flashing the ROM :)
19.1 For this we will then press the Option 99:
[IMG]http://i.imgur.com/eYhj4.png
NOTE: Because you are beginning to learn how to make Custom ROMs recommend the first option which is already the default and that the Kitchen, then just do enter in the respective options that appear to the end:
Until we reach the end of file creation can change the name of it, this is the last question that makes the kitchen:
Done this you can find the ROM inside the OUTPUT folder in the Kitchen ...
You only need to copy to the memory of the phone and make the flash.
Have a good cooked and good flash
ROM that was created in TUTU --->
XWLP7 Stock By TugaPower
a hell lot of screenshots, foolproof guide, really great one for beginner
Thanks.. Must have !!
Thanks fool proof, full of screens and has each and every detail.
:thumbup:
randommmm said:
a hell lot of screenshots, foolproof guide, really great one for beginner
Click to expand...
Click to collapse
aditya_7298 said:
Thanks fool proof, full of screens and has each and every detail.
:thumbup:
Click to expand...
Click to collapse
Thanks guys...
Cheers
wow really Great Guide.....................
--------------------------------------------------------------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------------------------------------------------------------
Articles About Droid Manager:
1. Droid Manager – Uma interface de gestão gráfica para o ADB
2. Droid Manager: When Doing Only a Few Things is Not Enough (Xda)
3. Droid Manager: Comprehensive ADB Front End & Management Suite For Android
4. Droid Manager Review - Droid-Now.com
5. Droid Manager Given Major Overhaul and New Functionality (xda)
6. Droid Manager Android PC Software fuer Root User - CHIP.de
--------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------
Requirements - Download Links - Features--------------------------------------------------------------------------------------------------------------------
Requirements:
Rooted Android Device.
.Net Framework 4. (Download Here)
Fastboot & ADB drivers installed. (Check Here)
Android 2.1+
Device USB Debugging turned on (Settings -> Developer Options -> USB Debugging).
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Additional Features for Droid Manager Pro Only:
Connect and use multiple devices with Droid Manager
Adb Wifi: Connect your device with Droid Manager over wifi
Ability to perform multiple tasks at once (lite version of Droid Manager can only perform one task at a time)
Speed improvements
More to come in the future
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Buy Droid Manager Pro for 1.99$ - Fastspring.com - Official Website
Droid Manager Pro Features:
Media Sync Manager: Sync media files with from within the app, or simply right click on your media folder on your computer and Droid Manager will handle the rest.
Adb Wifi: Connect to Droid Manager using your Wifi connection (requires configuration to be applied on the device)
Add "Rename" to file browser, now files and folders can be renamed the same way files on your computer are renamed.
Minor UI Changes.
Droid Sync Manager is now part of Droid Manager Pro.
Send files from your Android smartphone to your computer
Send files from your computer to your Android smartphone using your phone.
Introducing Programs and Features Center with the following features:
Install additional features to Droid Manager.
Allow Droid Manager, SMS Center & Droid Sync Manager through firewall.
Control start up for programs installed using Programs and Features Center.
Be sure to check Droid Manager folder in Windows Start Menu.
Introducing Message Center:
Receive notification on your desktop about incoming text messages.
Compose a new SMS Message.
Reply to received SMS Messages.
Sync contacts with your computer.
Click to expand...
Click to collapse
Pay once and get all future updates and goods for free :good:
--------------------------------------------------------------------------------------------------------------------
Download Link:
If you like my work and would like to donate to me ( Here ) I appreciate it
Download Droid Manager v6.3 Released: June 23
Droid Manager Beta Downloads Released: October 11
Droid Manager RC Released: July 22
Download Cygwin.zip
Download Android App (Google Play Link)
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Quick Start Videos:--------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------
Features:--------------------------------------------------------------------------------------------------------------------
Notes you MUST know about:
USB Debugging Bridge must be turned on in device settings, can be found at: Settings -> Developer Settings -> USB Debugging
If You Can't Copy Files To Your Device:
CM Users please enable root access for ADB in: Settings -> Developer Settings -> Root Access, change it to allow Adb & Apps.
If problem exists for non-CM users use adbd Insecure
For Dealing with Boot.img, Download Cygwin (No Instillation Required for Cygwin, Unzip the downloaded file to where ever you want, and in Droid Manager "Boot Image" tab, point the program on where you have extracted the contents of the zip file.)
System Sounds must be in .OGG extension if you want to add your own. Droid Manager doesn't convert to .OGG
Rom management section is meant for noobs in custom rom building who only care about changing default apps, some build.prop values, kernel and user apps before they install a custom ROM
Back Up is created on SD Card, make sure USB Mass Storage Is disabled.
If you are experiacing lags when Browsing phone files, Copy / Delete ..etc. Please update your Superuser app & binary. If problem is still there please use adbd Insecure and patch your Adbd (you will know what to do once you open the app)
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Features mentioned below are found in both Lite and Pro version
--------------------------------------------------------------------------------------------------------------------
File Manager
Navigate through phone files / folders + SD Card files (no need to mount it)
Show Properties of desired file / folder
View / Edit permissions.
Rename files / folders.
Delete files / folders.
Create new files / folders.
Search for files on phone.
Move files.
Copy files / folders to PC
Copy files / folders from PC
Get files / folders copied from Windows explorer (Windows default file manager) by using "Paste from Clipboard" option.
Send any desired file / app to another phone by connecting the other device through wifi (using Droid Manager android app)
Backup selected file / folder directly to pc, or in the form of tar file.
View / Extract and Create Tar / Tar.gz files.
Create Shortcut to any folder on your desktop.
View / Edit any file (Text files, RC files, Scripts ..etc) from your device (Permissions will be handled by Droid Manager if you are editing System files)
Generate and Compare MD5 Sum
Extract HexDump for files.
View Partition Info
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Apk Manager
Install User / System Apps
Backup All apk files installed on device (system & user apps)
Backup any desired app with it's data.
restore apps / data
Install Apps on Sd Card.
Find apk files in specific Directory on Pc & install.
Send any app to another device connected via Wi-Fi (connected using Droid Manager android app).
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Build.prop Editor
Load build.prop File.
Edit build.prop file.
Save Changes back to device.
Recommended values already included.
Ability To Add Your Own Build.prop Values To List of Recommended Values.
Ability To Edit Existing Build.prop Values.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Init.d Script Manager
Add support for init.d scripts for stock kernel.
Check if currently installed kernel supports init.d script.
Add / Edit / Remove init.d scripts
Recommended scripts already included.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Bootanimation and System Sounds Manager
Change Boot Animation file.
Load System sounds (Alarms / Notifications / UI Sounds / Ring Tones)
Remove / Add new sounds.
View currently selected system sound file.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Backup Manager
Backup manager is about preventing device from boot loops after flashing theme / mod.
To Do: Browse to your desired zip file (Theme / mod), Backup manager will pull effected files from the device and create a zip file that can be flashed via your recovery installed on device.
In case of bootloops after flashing theme or mod, use the zip file created by Droid Manager to get things back to normal and make the device boot up again.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Fastboot Center
Execute Fastboot commands.
Flash any .img file
Erase paritions.
Use with cautious, using the wrong Fastboot command might wipe your device or brick it.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Custom Rom Tools
Browse Rom Files
Edit Build.prop File
Add / Remove System & User apps
View Application Info Like: Package Code Name, Code Version, Version Name, SDK Version, Target SDK, and Permissions.
Add / Remove or change boot animation.
Add / remove init.d scripts.
Edit / Write updater script.
Include Themes / Kernel Modules / Mods into your project.
Write your change log and keep track with changes you make for your project.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Wifi Transfer & Boot Image Tools
Send / Receive Files via Wifi
Supports Multiple file sending.
Supports for sending folders via Wifi. (result: sending folder C:MyMusic, will lead to all files in the "MyMusic" folder will be on the device in: /sdcard/MyMusic)
[*]If no directory was provided in the Android app while receiving, files will be saved in /sdcard/Droid_Manager
while folders will be saved on /sdcard/Name_of_Folder_You_Sent.
Unpack, edit and repack boot.img file.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Extras (The following options can be found in the "Rom Management & Device" tabs on top)
Mount System As Read / Write or Read Only
View Installed Modules
Install Modules Located on Device SD Card or on PC (Needs reboot of device)
Execute Custom ADB Commands
Extract Kernel Log File, Logcat and Recovery Log
Up Time info for the device.
Wipe Cache / Dalvik Cache / Data Partition
Create Nandroid Backup Without The Need To Reboot Device
Install & update onAndroid
One Click Tweak will edit build.prop file, provide support for init.d scripts if current kernel doesn't support and add init.d scripts.
Undo changes made by "One Click Tweak"
Install & update Superuser app.
Install & update SU Binary.
Update Busybox
Snap screenshot (it will be automatically pulled to PC.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Some Additions (The following options can be found in the "Extras" Tab on top)
Added Link To Facebook Page
Added Link To Google+ Page
Added Link To Suggest Ideas
Added Link To Report Errors
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
-- Feedback's are much appreciated, it helps me evaluate my work
--------------------------------------------------------------------------------------------------------------------
-- Change Log & Screenshots In Second Post.
--------------------------------------------------------------------------------------------------------------------
-- Thanks To regaw_leinad for providing AndroidLib which helped me in creating the windows app.
-- Thanks To Jimbo77 For This Tool Which Droid Manager Interacts With For UnPacking & RePacking Boot.img
-- Thanks To Ryuinferno For This Script For Enabling Init.d Support on Stock Kernel.
-- Thanks To ameer1234567890 For Online Nandroid Backup.
-- Thanks To iconfinder Got My Icons From There.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Always Remember:
Please Don't mirror my files, I like to keep track of download count.
Report Bugs in this thread and I will fix them as soon as possible.
If you want any new feature I will be happy to work on including it (if it's possible).
If you like my app please rate it
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
Droid Manager, Tool/Utility for the Android General
Contributors
DeepUnknown
Version Information
Status: Stable
Current Stable Version: 6.3
Stable Release Date: 2014-07-22
Created 2013-10-11
Last Updated 2014-12-01
Android Client Screenshots
Full Change Log on Google Docs: Droid Manager Change Log
-----------------------------------------------------------------------------------------------------------------------------------------------------
Droid Manager v6.1.2 Stable
-----------------------------------------------------------------------------------------------------------------------------------------------------
New Features:
More UI changes.
Ability to view bootanimation file before applying it to device.
Speed improvements.
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------------------------------------------------
Bug Fixes:
Fix bug that was causing the app for some users to either crash or not work at all.
Fix bug prevented files to be sent to device when using "Send To Android" from windows menu.
Click to expand...
Click to collapse
Change Log:
------------------------------------------------------------------------------------------------------------
List of Commands That Droid Manager Accepts:
droidmanager -o path_to_directory_on_device
This will start Droid Manager and navigate to path passed in the command.
droidmanager -s destination_on_device file1_onPC file2_onPC ..etc
This will copy file(s) from PC to destination address passed in the command.
System will be automatically remounted as RW.
More to come in the future.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------
Additional Screenshots
------------------------------------------------------------------------------------------------------------
I respect your work.Thank
john9 said:
I respect your work.Thank
Click to expand...
Click to collapse
Thanks for your comment
53 downloads and yet no feedbacks
2.1+
Does the current download include 2.1+ android app? all my devices are <4.0
looks clean!
ciscogee said:
Does the current download include 2.1+ android app? all my devices are <4.0
looks clean!
Click to expand...
Click to collapse
Sorry I forgot to include the 2.1+ app, will upload it right a way and send you the link in a PM
Ran it last night. I like the gui for actually seeing folders. Anyway to make an .img without 4ext though. I'm trying to figure out how to flash a deodexed /system to my phone.
Sent from my SPH-M580BST using Tapatalk 2
ciscogee said:
Ran it last night. I like the gui for actually seeing folders. Anyway to make an .img without 4ext though. I'm trying to figure out how to flash a deodexed /system to my phone.
Sent from my SPH-M580BST using Tapatalk 2
Click to expand...
Click to collapse
Actually I haven't implemented creating IMG files or flashing zip files. I'm trying to find a way to make it possible to create img files and flash zip files
Great job !
It would be nice to add the possibility to edit files permission
plopingo said:
Great job !
It would be nice to add the possibility to edit files permission
Click to expand...
Click to collapse
Actually you can change permissions, right click on any file / folder click properties and from there you will be able to change the permissions
DeepUnknown said:
Actually you can change permissions, right click on any file / folder click properties and from there you will be able to change the permissions
Click to expand...
Click to collapse
my bad, thanks you !
DeepUnknown said:
Actually I haven't implemented creating IMG files or flashing zip files. I'm trying to find a way to make it possible to create img files and flash zip files
Click to expand...
Click to collapse
I have a couple of ideas for you on these, check your pm.
ciscogee said:
Ran it last night. I like the gui for actually seeing folders. Anyway to make an .img without 4ext though. I'm trying to figure out how to flash a deodexed /system to my phone.
Sent from my SPH-M580BST using Tapatalk 2
Click to expand...
Click to collapse
I have an idea for you as well, check your pm.
plopingo said:
my bad, thanks you !
Click to expand...
Click to collapse
your welcome
---------------------------------------------------------------------------------------------------
Волк said:
I have a couple of ideas for you on these, check your pm.
Click to expand...
Click to collapse
Thanks, waiting for your PM
--
Just sent, sorry, I wanted to do some research on my own as well.
I connect the phone to the computer run the program. But it is always waiting for the phone.
What should I do?
I connect in both MTP and USB Storage...
ardicli2000 said:
I connect the phone to the computer run the program. But it is always waiting for the phone.
What should I do?
I connect in both MTP and USB Storage...
Click to expand...
Click to collapse
I'm sorry I forgot to mention it, USB Debugging (Settings -> Developer Options -> USB Debugging (or Android Debugging)) must be turned on
DeepUnknown said:
I'm sorry I forgot to mention it, USB Debugging (Settings -> Developer Options -> USB Debugging (or Android Debugging)) must be turned on
Click to expand...
Click to collapse
I turned on the USB Debugging and install .NET Framework 4.
Phone connected to program.
However, I edited build.prop. Saved it to the device. It said pushed to device. Reboot now?
I said "Yes". But nothing happened. Reboot myself. Check the build.prop and saw that nothing has changed.
What am I doing wrong??
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.