Related
Hi all, im making a NEW thread for how to make custom ROM, change build.prop, how to theme (coming later)! i will make a colection of how to´s to this thread for now all of the how to´s are made by me but in future i will take how to´s from others too (with their permission ofc )
so subscribe to this thread!!
i hope that there will be many custom ROMs after this
now you all think why did i do this if theres another tutorial for making custom ROM? answer: this is good alternative and this is not just one HOWTO!
HOWTO´S
-custom ROM
-edit build.prop
-5 lockscreen mod and extended power menu
-deodexing
-install android sdk and use ADB
-port themes (coming later)
-make own bootanimation (coming later)
** you can also post your ideas for new how to´s!!!
have a nice day
p.s dont blame me if something happens to your device while doing these how to´s
p.p.s if you want some special how to you can always suggest it in this thread
[HOWTO] make a custom ROM
How to make custom rom:
you will need: ADB, root explorer (maybe) and the files that are going to be in your rom!
the guide is based on The Dark Lestat's guide, i made it more easier and specific
code to delete unwanted apps: (if ADB)
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
rm /system/app/nameofapk.apk
code to add apps and stuff: (if ADB)
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameofapk.apk /system/app/
1. flash the ROM that will be your ROMs base. example: my ROMs base is JPM so i flashed clean JPM
2. make a list of the features that are going to be in your ROM
3. then start adding those features. example: i added live wallpaper support so i did this --> http://forum.xda-developers.com/showthread.php?t=793823 i also added JIT so i ran the automatic batch file from the thread --> http://forum.xda-developers.com/showthread.php?t=1026870 . then you just add those features.
4. put your sd card on to your phone (if it isnt there already )
5. when your done adding different features you go to ADB and type this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
then you wait about 2 minutes and there will be some text and then you type this
Code:
exit
exit
and in your sd-card will be freshly created factoryfs.rfs, import your freshly created factoryfs.rfs to your desktop. now you choose your kernel.
5. kernel, download the kernel you want to your desktop.
6. download total commander to your pc
7. open total commander, open the base ROM.tar. example: my base ROM was JPM so i opened the JPM.tar and replaced the kernel and factoryfs.rfs with my factoryfs.rfs and my kernel (fugumod 2.2) using total commander.
delete everything else in the .tar but, Cache.rfs, factoryfs.rfs, zlmage and data.rfs and the logo!
then you test if you can flash your ROM... if it boots, you did it. if it doesnt, try again.
[HOWTO] edit BUILD.prop
HOW TO change firmware version, phone model, build version in "about phone"
1. open root explorer
2. go to /system, find build.prop, change to read/write mode. open the build.prop in text editor
* change build version: 4th line should say ro.build.display.id=(here you write your build version name), reboot and check build version in "about phone"
* change model number: 15th line should say ro.product.model=(here write your model number ), reboot and check model number in "about phone"
* change firmware version: 8th line should say ro.build.version.release=(here write your firmware version, like 3.0 honeycomb ), reboot and check firmware version in "about phone"
you can also change different things but ill write a guide of that later
hope you like it!
[HOWTO] port a THEME
reserved for later use
[HOWTO] get 5 lockscreen mod and extended power menu
-your ROM must be deodexed!
-you can get extended power menu and 5 lockscreen mod by downloading this --> http://www.megaupload.com/?d=PKHVA57W
-extract it to root of your sd-card
-open root explorer and copy/paste the files to /system/framework
-reboot and done
OR
use adb like this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameoffile.jar /system/framework/
-reboot and done
***NOTE rebooting might take some time so dont panic
[HOWTO] deodex ROM
you must be rooted
What you'll need:
A Windows based machine
xUltimate v2.2
Patience
Process:
-Unzip xUltimate v2.2, and launch "Main.exe"
-If everything goes well xUltimate should recognize the phone and make a connection. You now should see a list of options.
-Run option 1. After option 1 is done, run option 2.
-Now these well take a while. Run option 3.
-IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex" (if you even have it). It's a bad file, and interferes with deodexing process.
-Now run option 4, and wait.
-Exit xUltimate, and put the phone in USB mass storage.
-Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
-Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
and voila your phone is deodexed
original guide by webst3r, i changed it so its easier to understand
[HOWTO] get ADB up and running (easy way)
ADB is an acronym for Android Debug Bridge and is a development tool for the Android Mobile Operating System
NOTE this is only for windows!
-open this link --> http://adf.ly/Xfyl wait 5 secs and click upper right corner "skip ads" it will download a program that automaticly installs android sdk (wich includes ADB)
-Open the app, leave the destination as C:\ and click ok/install
-Installing ADB/USB Drivers:
*NOTE* You may need additional (Device Specific) Drivers for your Device!
- Connect your Android Device to your PC using the provided USB Cable or just a plain ole 6-pin to 4-pin usb cable... (I prefer to use one with a ferite core)
- When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android-sdk-windows\google-usb_driver) and install the adb driver.
** if your having issues with installing ADB drivers read this --> http://dl.dropbox.com/u/20575563/ADB_Drivers_for_dummies.pdf
-Running ADB from the Command Prompt:
-Windows XP: Select Start or Tap the Windows Key on your Keyboard, select
"Run" and type "CMD" then hit "Enter".
-Windows Vista/Win7: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type "cmd" then hit "Enter".
Add the "ADB" directory path as a system variable in windows:
-To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista/7) then select Environment Variables.
-Click "New" under System Variables and add the following:
Variable =
Code:
adb
Value =
Code:
C:\android-sdk-windows\platform-tools
-Call up your Command Prompt:
Time to start adb
- Open up a Command Prompt Windows
- Type the commands below:
Code:
cd C:\android-sdk-windows\platform-tools
<-- Press Enter
Code:
adb.exe
<--Press Enter
and voila You will see alot of scripting fly through the command prompt window.
***note! you have to enable usb debugging in --> settings --> applications --> developement --> check usb debugging
tutorial is not made by me, its made by AndroidSamurai. i found it after lot of researching
[HOWTO] make your own update.zip
download and install, then watch the video
http://youtu.be/i0KzFPMA6-8
program and video made by Daneshm90
balaji.admin said:
Please include a Post for Deodexing the ROM. I've tried to deodex the DDJP2. But never succeeded.
Hope your post will help me.
Click to expand...
Click to collapse
there is a tut by rudolf..
[HOWTO] change app icon
How to change icons for app!
1.)
Things you need:
original app
your custom icon (size should be 48x48)
win rar
2.)
Unpack APK
3.)
Find file, for example: ic_launcher_settings.png (for settings.apk)
It should be in: res/drawable-mdpi or res/drawable-ldpi (dont know which icon phone uses, just replace both)
4.)
Rename you icon to, for example: ic_launcher_settings.png (for settings.apk)
5.)
Replace it
6.)
Final step is add files to old settings.apk archive and using root explorer copy it into /system/app/
DONE!
guide by peldax
jazux said:
hey, one question coming from me our device has the same resolution as htc wildfire? right? and device is ldpi or mdpi? please answer ASAP!!! i may have found very useful HOWTO that you will LOVE!!!
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
Click to expand...
Click to collapse
galaxy3 has ldpi - look there: http://developer.android.com/guide/practices/screens_support.html
jazux said:
-your ROM must be deodexed!
-you can get extended power menu and 5 lockscreen mod by downloading this --> http://www.megaupload.com/?d=PKHVA57W
-extract it to root of your sd-card
-open root explorer and copy/paste the files to /system/framework
-reboot and done
OR
use adb like this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameoffile.jar /system/framework/
-reboot and done
Click to expand...
Click to collapse
is this suit for every rom？
dxdiag32 said:
is this suit for every rom？
Click to expand...
Click to collapse
what do you mean? like does this work on other fw's than JPM? im not sure because i havent tested it, but i think it should work.
but it will surely work on every JPM based ROMs
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
Hey man a really nice tutorial
Can you add my tutorial on how to make bootanimations too
It would be appreciated
P.S. : If you tell yes,i'll give you a shortened version too
Deodexed Rom? How can i do it?.
cdesai said:
Hey man a really nice tutorial
Can you add my tutorial on how to make bootanimations too
It would be appreciated
P.S. : If you tell yes,i'll give you a shortened version too
Click to expand...
Click to collapse
yes i can add it
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
AndroKite said:
Deodexed Rom? How can i do it?.
Click to expand...
Click to collapse
ill do a tutorial later tonight!
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
AndroKite said:
Deodexed Rom? How can i do it?.
Click to expand...
Click to collapse
for now you can use this:
Thanks,i dont remenbre that you make a tutorial ,Thx.
AndroKite said:
Thanks,i dont remenbre that you make a tutorial ,Thx.
Click to expand...
Click to collapse
you welcome
Advantages or disadvantages
- Odexed ROMs are slightly faster, deodexed ROMs are slightly slower
+ You can make custom themes for your ROM
+ Performance los is negligible.
Requirements
xUltimate - http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
Busybox installed
Root
Automatic deodexing - Method 1, by r33p
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. Select option #15 then "do it all".
Deodexing (little harder, but contains useful information for your future Galaxy Gio modding experience)- Method 2, by me
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. On the main menu of xUltimate, choose option 5 (Pull and deodex all). Everything will be done for you here. Don't worry. You will see all your finished files in the folders 'done_app' and 'done_frame' which are located in the installation directory of xUltimate.
4. move folders 'done_app' and 'done_frame' folders to your sdcard, you can find these folders in the directory of xUltimate as described in the previous step.
5. Make sure the sdcard is not mounted to pc anymore
6. Open Windows Command Prompt and type the following commands.
adb shell
su
stop
mount -o remount,rw /dev/block/stl12 /system
rm /system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/stl12 /system
sync
reboot recovery
Click to expand...
Click to collapse
7. Now data and cache reset in the recovery menu...
8. reboot
If one of the commands, for example 'cp' is not found, try putting busybox in front of the command:
eg: busybox cp /sdcard/done_frame/* /system/framework/
How to odex again
This may put you in the right direction. You may need to edit some steps.
http://forum.xda-developers.com/showthread.php?t=1124034
If you like my work please donate
Paypal:
Bankaccount: in private message
Updated my tutorial. Now everything works.
What does this do to my gio?
// Thanks from the noob
why the hassle? just let xultimate do it all automatic -> select option #15 then "do it all"
yep
Thanks.. ;-)
Would it work with others samsung devices?
Gonna try with 5510
Sent from my GT-I9100 using Tapatalk
dann3_86 said:
What does this do to my gio?
// Thanks from the noob
Click to expand...
Click to collapse
I am curious to
I suggest you google deodexing and zipaligning.
Deodexing in short means that it will allow you to have custom themes.
Zipaligning improves performance of the apk/jar files when reading
There is a lot of information you might want to look up!
I just added r33p's suggestion. Thanks!
Dhuu, just google it.............
I did, but it gives no answers.
I thought it was about the holy grail, or the fountain of youth..............
But no..........
But comes close
So tell me, does it works on the fly or must you reboot to aply changes?
I tiedy this metod and it works. Tank you
I'm having a problem..
I'm on xUltimate, I go to the advanced menu (15) and I type 1 (Do everything) and then it says that I don't have files in done_app folder.
Please help
Edit: I have rooted my phone, it's on Gingerbread.xxkpo. Do I have to Un-Root my phone and then do this ? Also can I root it back when the ROM is on ?
Please reply fast :S
I'm having this issue,,, what does it mean? i pulled out all the files with the automatic process and went fine. But then in the deoxed process:
How can i solve it? Thanks :3
THIS HAS NOT BEEN TRIED ON THE ATRIX 2 YET! THIS IS JUST FOR HELP DECIDING IF THIS IS SAFE! I HAVE NOT PULLED THE TRIGGER YET! WITHOUT A WAY TO RECOVER I SUGGEST YOU DO NOT TRY IT.
I was thinking and remembered the original and deodexing the stock rom. The Atrix stock rom could be deodexed with a locked bootlader. In comparing the instructions below to our Atrix 2 I don't see a reason why this wouldn't work. Can some of you chime in with what you think?
Original post here:
http://forum.xda-developers.com/showthread.php?t=1162764
and post 50 -
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. Now run option 4, and wait.
6. Exit xUltimate, and put the phone in USB mass storage.
7. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
8. Put the phone in PC mode "MOTOROLA PHONE PORTAL"
9. Open a command prompt, and ENTER THE FOLLOWING COMMANDS: AFTER YOU ENTER su make sure you hit accept on your phone
C:\>cd\
C:\>android-sdk-windows\platform-tools\adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Some input from a little more experience than me?
I was thinking of trying the same thing, but I didn't want to run this without a way back.
I know they had tried it on the RZR and I think it caused a soft brick so they backed off till a way to flash. I was gonna try the way they had performed it till I seen they were having problems.
We are really stuck right now with no option to flash back to stock if we brick and I'm getting withdrawals LoL
I'm unfamiliar, whats the point?
Sent from my NookColor
Basically so you can change the look of system apps through theming the framework
Sent from my MB865 using xda premium
Is it possible for someone to upload the files from option 7. I cant seem to get xultimate to work, I always end up with a java error. And I'd like to play with some themes.
lfaber06 said:
Is it possible for someone to upload the files from option 7. I cant seem to get xultimate to work, I always end up with a java error. And I'd like to play with some themes.
Click to expand...
Click to collapse
Do u have the jdk installed?
Yup. Even tried uninstalling all java and re-installing then unzipped xultimate to another directory. And no dice..
halfevildruid said:
Do u have the jdk installed?
Click to expand...
Click to collapse
Step 7 is just a copy and paste from pc folder to sdcard.
That's what I want is all of the deodxed files so I can push em to my phone.
Sent from my Nexus S using Tapatalk
halfevildruid said:
THIS HAS NOT BEEN TRIED ON THE ATRIX 2 YET! THIS IS JUST FOR HELP DECIDING IF THIS IS SAFE! I HAVE NOT PULLED THE TRIGGER YET! WITHOUT A WAY TO RECOVER I SUGGEST YOU DO NOT TRY IT.
I was thinking and remembered the original and deodexing the stock rom. The Atrix stock rom could be deodexed with a locked bootlader. In comparing the instructions below to our Atrix 2 I don't see a reason why this wouldn't work. Can some of you chime in with what you think?
Original post here:
http://forum.xda-developers.com/showthread.php?t=1162764
and post 50 -
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. Now run option 4, and wait.
6. Exit xUltimate, and put the phone in USB mass storage.
7. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
8. Put the phone in PC mode "MOTOROLA PHONE PORTAL"
9. Open a command prompt, and ENTER THE FOLLOWING COMMANDS: AFTER YOU ENTER su make sure you hit accept on your phone
C:\>cd\
C:\>android-sdk-windows\platform-tools\adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Some input from a little more experience than me?
Click to expand...
Click to collapse
deodexed make it zipalign or not?? in xultimate have zipalign.exe . how to use it??
How to prepare your i9001 stockROM for modding
First of all I want to say that I know that there already are tutorials about this, but this is just my sites "well explained aio tutorial" that everyone should be able to follow successfully, just as my other tutorials. I added loads of screenshots to make everything a lot easier. So please no complaining about duplicates
Short description:
In this tutorial I will explain you how to prepare a stock rom for modding, the files in this tutorial (cwm and root) are for the Samsung Galaxy S Plus (GT-i9001) only!
The deodex part will work for every device, So if you have an other device then the i9001 you can only follow the deodex part if you would like to.
General notes
- I know I already made a tutorial about how to root the i9001, but this method is faster and easier, so forget the old method and use this one!
- In this tutorial I assume that you have installed your new stock ROM (or still have the original one) and made no modifications to it yet (this excludes apps & settings)
Chapters:
1. ClockWorkMod Recovery (CWM)
2. Getting full access to your system files (Root)
3. How to make system apks available for modding (Deodex)
Chapter 1. ClockWorkMod Recovery
The first step of this guide is to get rid of the stock recovery, the stock recovery is very useless if you compare it to CWM.
CWM is a custom recovery that it known worldwide, it has a great number of options and actually should be installed by default on any smartphone!
The method of flashing the recovery will be Odin (Mutli Downloader 4.43), this method doesn’t require root access and is very trusted.
What you have to do on your pc:
1. Download and unpack Odin and AriesVE.ops
2. Download and unpack CWM v5.5.0.4 (ICS Compatible)
3. Download and install Samsung USB Drivers
4. Now go to the folder where you extracted odin and AriesVE.ops, and open odin (Multi_Downloader_v4.43_with_smd0425.exe)
{
"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"
}
5. Click on the “OPS” button, now choose the AriesVE.ops file you downloaded earlier, after this check the “One package” checkbox
6. Now click the “One Package” button and choose the “recovery-clockwork-5.5.0.4-ariesve.tar.md5″ file you downloaded earlier, now it will perform an md5 check
7. Now turn off your i9001 if it’s on at the moment.
8. Turn it on by holding: Volume Down + Home + Power (hold it for about 6 seconds) until the Download Mode comes
9. Now put the USB cable in your phone and computer, your computer will now install all needed drivers
10. Once the driver installation is complete you will see a yellow block in your upper left odin window
This means it’s detected and ready to flash
11. Now click the “Start” button and the flashing will start
(as you see this process only takes a few seconds)
12. Now your phone will reboot and CWM is installed correctly. (You can also press the “Volume up + Power” buttons when you see the Samsung logo (when odin reboots your phone), It will force your device to go to cwm.
What I strongly advice is to make a backup of your current rom (backup & restore > backup)
Now see the next chapter for quick rooting!
Chapter 2. Getting full access to your system files (Root)
Once CWM is installed it’s very easy to root your phone very fast.
1. Download Root-i9001-Signed.zip or scan this barcode on your phone:
2. Put the zip on your sdcards root, and turn off your phone.
3. Now turn your phone on by holding: Volume Up + Power, when you see the Samsung logo wait another 2/3 sec and then release both buttons.
4. Now CWM Recovery will show, use the volume buttons to scroll up and down, use the home button to choose something
5. Scroll to “install zip from sdcard” and press the home button
(using the volume down button to go down in the menu)
(after pressing home in main menu)
6. Now Press home again to go to “choose zip from sdcard, this will let you browse your internal sdcard, now search for the root-i9001-signed.zip file
(my sdcard is a bit messy ^^)
7. When you found the zip press Home to choose it
8. Now scroll up (it’s faster then down) until you reach Yes, then press the home button again. This will install the root zip on your phone
9. Now press the back button once to return to the main menu, with “reboot system now” selected, press the home button once to reboot your phone
10 . When your phone is rebooted you should look for the SuperUser app and open it, now press the menu button and choose “Preferences”
11. Now scroll all the way down to Superuser information, then press the second button “Su Binary v3.0-beta2″, this will open the updater
(dutch language)
12. As you see it’s outdated and needs to be updated, press the Update button to do this
13. Now the updating will start, and soon SuperUser will ask for SuperUser permissions, click Grant
(dutch language)
14. After clicking grant the update process will continue and will be done in a few seconds
15. Now your Su Binaries are updated you need to update the app itself, just go to the market and search for “Super User”
16. Choose the one contributed by: ChainsDD, now click the “Update” button to update it. You are now done with the rooting.
Chapter 3. How to make system apks available for modding (Deodex)
Requirements for deodexing:
- Android SDK (x86)
- Java Development Kit (x86)
- Busybox Installed on your phone (the download from the market is the installer, so you will need to run the app to install it)
1. Download xUltimate Script v2.3.3, unpack it in some folder and if you have an anti-virus, scan the jar folder and add “auto_app.exe” and “auto_frame.exe” to exclusions/trusted files. (at least my anti-virus thinks it’s dangerous, but it’s not..)
2. Run “Main Skip.bat”, now the main menu of xUltimate will open
3. Now connect your phone in debugging mode to your pc (but not in mass storage mode!), and choose “1″ then press enter, this will pull all system apps from your device
4. When the pulling is complete choose “2″ and press enter, this will pull all system framework files.
5. Now that you’ve collected all apks/odex files, you will probably need to remove these apks from the “origi_app” folder, since they will probably fail to deodex.
- GoogleQuickSearch.apk / GoogleQuickSearch.odex
- Maps.apk / Maps.odex
- Phonesky.apk / Phonesky.odex
- PlusOne.apk / PlusOne.odex
- Voicesearch.apk / Voicesearch.odex
These apps can be redownloaded at the market later! (Phonesky is just the market installer, not the actual market installation)
6. Now choose “3″ and press enter, now the deodexing of the system apps will start.
This may take a while, but at least it will deodex until the end, since the trouble makers are already removed.
7. When the deodexing of the system apps is done you will return to the main menu, now choose “4″ and press enter to deodex the framework files
Luckily deodexing the framework goes a lot faster then the apps. When this process is also done you will have 2 output folders, called “done_app” and “done_frame”
8. What you will need to do is copy both folders to your internal sdcard’s root (since you’re still in debugging mode, drag down the status bar and click on the usb notification, then click on “Mount Storage” to mount your internal sdcard on your computer (Mass Storage Mode)
9. After you copied both folders, you need to press “Unmount Storage” on your phone, now it will be back in normal debugging mode, keep the usb cable in because we are not done yet.
10. Download ADB (Android Debug Bridge) and unpack it in some folder, Now in that folder “Shift+Right Click” at some empty spot > Open command window here (This is only for Windows 7). XP users will have to open cmd manually and “cd” to the adb directory
11. Once your in cmd, enter the following commands to successfully deodex your phone (an explanation of the commands can be found below them, make sure you don’t enter the symbols as well, I added those so you can see if you’re in the right mode)
> adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# busybox cp /sdcard/done_app/* /system/app/
# busybox cp /sdcard/done_frame/* /system/framework/
# busybox chmod 644 -R /system/app/*
# busybox chmod 644 -R /system/framework/*
# reboot
What did those commands actually do?:
“adb shell” – opens a shell interface for your phone, this is the same as a unix shell
“su” – asks for superuser permissions (and gets it right away)
“stop” – this command freezes your phone completely, except the adb traffic, that means you can replace system files without crashing your device
“mount -o remount rw /system” - this remounts the system partition but writable
“rm /system/app/*.odex” / “rm /system/framework/*.odex” – This deletes the old .odex files which are not needed anymore after deodexing
“busybox cp /sdcard/done_app/* /system/app/” / “busybox cp /sdcard/done_frame/* /system/framework/” – This copies the apks from the folders in your sdcard to the right destination.
“busybox chmod 644 -R /system/app/*” / “busybox chmod 644 -R /system/framework/*” – This command sets the permissions to RW-R-R, some users say it’s not needed but just remember to do it always, it’s a good thing! (and bad permissions may even crash your device)
“reboot” – well, I think you know what this does.
Ok so If you entered all commands correctly your phone will now reboot and succeed to boot. be ware that it takes a lot longer then a normal boot since the dalvik-cache has to rebuilt, this takes about 1 minute and 30 seconds at the i9001. (also depending on the amount of apps you have)
12. Now that your phone is successfully deodexed it’s ready to be customized! This means you can install Theme’s and Mod’s, but you can also do all other kinds of customization, since your phone is also rooted, such as installing Thunderbolt. But don’t forget to redownload the apps that you removed before deodexing
I hope you’ve learned something in this tutorial, I’ve already written a tutorial about rooting, but this way of rooting is just way better then the traditional method.
As always, good tutorial :good: I'll probably never need it, but good to know i could if i want.
regards
busprofi said:
As always, good tutorial :good: I'll probably never need it, but good to know i could if i want.
regards
Click to expand...
Click to collapse
Thanks . The tutorial is really focussed on beginners, so they have a well explained tutorial to follow, that they will probably understand the first time they read it. (atleast I hope they do ^^)
broodplank1337 said:
Thanks . The tutorial is really focussed on beginners, so they have a well explained tutorial to follow, that they will probably understand the first time they read it. (atleast I hope they do ^^)
Click to expand...
Click to collapse
:thumbup: Always the Best!!!
Sent from my GT-I9001 using xda app-developers app
raptor92 said:
:thumbup: Always the Best!!!
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Thanks And the good thing is, I keep getting new idea's for apps and tutorials. my idea source will never go dry! (I guess, since sometimes I suddenly have 3 new apps in my mind, that I can make) In a few years I will have loads of stuff lol (If I keep this tempo of developing/writing tutorials)
Wow another awesome noob-friendly guide. Love your work. Keep it up.
Sent from my GT-I9001 using xda premium
iCloud said:
Wow another awesome noob-friendly guide. Love your work. Keep it up.
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Thanks will do, btw I just noticed that I forgot to post all links! (I just copied it from my blog without thinking about all links). my mistake
I respect your work.thanks for the tutorial,exactly what I need.
john9 said:
I respect your work.thanks for the tutorial,exactly what I need.
Click to expand...
Click to collapse
Thank you, you're welcome Nice that it's exactly what you need haha
broodplank1337 said:
Thank you, you're welcome Nice that it's exactly what you need haha
Click to expand...
Click to collapse
Brood, i have a question on this. After deodexed the app and jar files can these file considered as zipaligned? Because i found that it take a lot of memory compared to the odexed ROM. However, in the xUltimate there is a optimization command available to optimize all the apk files but it also bring many FC after push all the files to the phone.
DreamerTKM said:
Brood, i have a question on this. After deodexed the app and jar files can these file considered as zipaligned? Because i found that it take a lot of memory compared to the odexed ROM. However, in the xUltimate there is a optimization command available to optimize all the apk files but it also bring many FC after push all the files to the phone.
Click to expand...
Click to collapse
The deodex process calls it aligning, and I'm not sure if that's really a zipalign, but it's very easy to zipalign, just run the attached "03zipalign" in script manager, (with su icon checked), But the fc's are are not normal, you must have made a mistake somewhere, do you still have the odex files inside /system/app and system/framework for example?
broodplank1337 said:
The deodex process calls it aligning, and I'm not sure if that's really a zipalign, but it's very easy to zipalign, just run the attached "03zipalign" in script manager, (with su icon checked), But the fc's are are not normal, you must have made a mistake somewhere, do you still have the odex files inside /system/app and system/framework for example?
Click to expand...
Click to collapse
Nope. During the push process i already write the remove command in adb to delete them all. For the FC case this won't happen if i didn't run the command in xUltimate>Advanced>Optimize all apk>Extreme.
After the optimization i found out that the apk files become smaller in size but sometimes some of the apk will get FC in phone. What i have experienced are camera.apk, AxT9IME.apk, Phone.apk and so on.
DreamerTKM said:
Nope. During the push process i already write the remove command in adb to delete them all. For the FC case this won't happen if i didn't run the command in xUltimate>Advanced>Optimize all apk>Extreme.
After the optimization i found out that the apk files become smaller in size but sometimes some of the apk will get FC in phone. What i have experienced are camera.apk, AxT9IME.apk, Phone.apk and so on.
Click to expand...
Click to collapse
Well, I assume you pushed the files while in mass storage mode?, (or did you use adb push?). When you're in mass storage mode you cannot access your sdcard in adb, so what you actually do when using the remove command: nothing.
Then If you place the done_app and done_frame folder in /system/app & /system/framework you will still have the .odex files , Right?
Please follow all steps correctly, I also screwed up at my first deodexes, but when I red the whole tutorial (I believe that was the i9003 one) again it worked
But you can also use deodex packages (KQE for example) which is posted at the KQE rom topic.
broodplank1337 said:
Well, I assume you pushed the files while in mass storage mode?, (or did you use adb push?). When you're in mass storage mode you cannot access your sdcard in adb, so what you actually do when using the remove command: nothing.
Then If you place the done_app and done_frame folder in /system/app & /system/framework you will still have the .odex files , Right?
Please follow all steps correctly, I also screwed up at my first deodexes, but when I red the whole tutorial (I believe that was the i9003 one) again it worked
But you can also use deodex packages (KQE for example) which is posted at the KQE rom topic.
Click to expand...
Click to collapse
Brood, i redownload the xUltimate using the link that you provided in this forum and now the deodex process run smoothly and successfully. Finally i can manage my phone freely. Thanks again~
DreamerTKM said:
Brood, i redownload the xUltimate using the link that you provided in this forum and now the deodex process run smoothly and successfully. Finally i can manage my phone freely. Thanks again~
Click to expand...
Click to collapse
Good! You know I've only managed to deodex roms successfully using the 2.3.3 version, I just think that 2.3.3 is the magical version . Enjoy the deodex
broodplank1337 said:
Good! You know I've only managed to deodex roms successfully using the 2.3.3 version, I just think that 2.3.3 is the magical version . Enjoy the deodex
Click to expand...
Click to collapse
Really? maybe also caused by last time im using the ver 2.4 so this might be the main cause for such problem
Thanks for this guide, but (there's always a but)....
... my I9001 keeps rebooting into CWM now. Whenever I boot it, or reboot it, it will always go back into CWM. I reflashed CWM using this guide, step by step, 4 times with the same result. It's great to have CWM on the phone, but it would be nice to also use the phone as a,... well "phone".
I tried flashing Broodrom (business) and it flashes alright. No way to test it however since all I see after a reboot is,... CWM. I tried 3 different ROMs, but all I see is CWM.
Do I have a seriously strange i9001, or is there something I am missing in this guide? I've flashed quite a few phones so maybe I can't be considered to be a beginner anymore, and maybe that's why this guide won't work for me
Anyways, back to odin and stock ROM for me.
FrepA said:
Thanks for this guide, but (there's always a but)....
... my I9001 keeps rebooting into CWM now. Whenever I boot it, or reboot it, it will always go back into CWM. I reflashed CWM using this guide, step by step, 4 times with the same result. It's great to have CWM on the phone, but it would be nice to also use the phone as a,... well "phone".
I tried flashing Broodrom (business) and it flashes alright. No way to test it however since all I see after a reboot is,... CWM. I tried 3 different ROMs, but all I see is CWM.
Do I have a seriously strange i9001, or is there something I am missing in this guide? I've flashed quite a few phones so maybe I can't be considered to be a beginner anymore, and maybe that's why this guide won't work for me
Anyways, back to odin and stock ROM for me.
Click to expand...
Click to collapse
The problem you're facing is the bootloop bug in cwm, some people experience this bug, you can find the fix in this post: http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
broodplank1337 said:
The problem you're facing is the bootloop bug in cwm, some people experience this bug, you can find the fix in this post: http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
Click to expand...
Click to collapse
Thanks for your reply. I did try that solution before I posted (I should have mentioned it, sorry). It didn't solve my problem however. I could boot without going into recovery, but nothing would happen, so the ROM would not be loaded. I should mention however that I had no problems with a different i9001, so I might have a phone with some special issues.
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# busybox cp /sdcard/done_app/* /system/app/
# busybox cp /sdcard/done_frame/* /system/framework/
# busybox chmod 644 -R /system/app/*
# busybox chmod 644 -R /system/framework/*
# reboot
Click to expand...
Click to collapse
I could not do the above. when i type stop, there is no #.
Edited: I have done it. It is deodex now but when I flash the mod such as the extended toggle bar, when the the phone restart the status bar missing. How can I fix it???
what is deodexing :
SilverZero said:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
I think that's the general idea, anyway.
Click to expand...
Click to collapse
STEPS :
*Go HERE root tour device .
*Download Busybox installer and install the latest version of busybox compatible with your device.
*Install ADB :
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
credits : DEADLY
*Download Xultimate.
*Connect your phone to computer.(Make sure you have select USB debugging in Settings>Applications>Development)
*Extract xUltimate v2.3.3.zip and Launch Main.exe
*If everything goes well xUltimate should recognize the phone and make a connection.You now should see a list of options.
*Select option (1) pull /system/app. Wait until it complete.
*Select option (2)pull /system/framework. Wait until it complete.
*Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder]
*Then select option (4)Deodex /system/framework. Wait until it complete.
*Now Exit from xUltimate.
*Put the phone in USB mass storage.
*Go to xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
*Now get out from USB storage mode.
*Open Command prompt.
( Goto folder where android sdk installed. Then goto platform-tools folder in it. Right click on free space in folder while pressing shift key.Select open command prompt here.
Now enter commands. )
*Enter following codes.
(if you are using adb shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
*Enjoy your DEODEXED rom ! also thank : chamatht (for i learnt this from him ).
Troubleshooting :
srt99 said:
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
Click to expand...
Click to collapse
____________________________________
thoughtfully scribbled by nikufellow
Hi! Thanks for the Guide!
I don't know if I am doing something wrong, but I can't make it work. Every .odex file give me a error, so delete every odex will not help, I guess. Have you or anyone tested this guide with our firmware? (original 2.3.6, Only root).
I was trying to deodex, so I could make some little changes (like battery icon) without flash another rom.
battery icon is working for me but the rest not.... I'm using Rom toolbox
Sent from my GT-I9070 using xda app-developers app
johnnybr said:
Hi! Thanks for the Guide!
I don't know if I am doing something wrong, but I can't make it work. Every .odex file give me a error, so delete every odex will not help, I guess. Have you or anyone tested this guide with our firmware? (original 2.3.6, Only root).
I was trying to deodex, so I could make some little changes (like battery icon) without flash another rom.
Click to expand...
Click to collapse
You need xUltimate v2.3.3 only
I do not respond to tech support via PM
Battery icon works on odexed stock rom. I try this method tonight
GT-I9070P®land
Just done deodexing a stock jb rom for i747 through kitchen, then I read this post. Awesome job, man. :good:
At first this method works,
later after i reflash rom, rooted and do this again,
i get bootloop, any idea?
I tried 5 times and everytime bootloop
But why use the stop command ? Doesn't that stop Android itself entirely ?
I give up writing anymore signatures.
hey bro why this method shows error of insufficient space...
can you help me in dis...
i m having samsung galaxy fit running on 2.3.6 ddkt3
Why i cant!? Heeeelp please!!
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
srt99 said:
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
Click to expand...
Click to collapse
Thanks for the info added to first post
____________________________________
thoughtfully scribbled by nikufellow
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
edit: I own a Samsung Galaxy R (i9103)
ROKronoS said:
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
edit: I own a Samsung Galaxy R (i9103)
Click to expand...
Click to collapse
This is for I9070, you only can get bootloop if you use this.
Somebody gave me this link in the R section
Thanks anyway
Me too
ROKronoS said:
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
Click to expand...
Click to collapse
And now?
S Advance I9070
Do this has chances to brick my device if i do it wrong?
Sent from my GT-I9070 using xda app-developers app
Одг: [GUIDE]DEODEX stock ROM !!!!
AnMotass said:
Do this has chances to brick my device if i do it wrong?
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
If there is any possibility to brick, it would be soft brick, that you can repair by flashing firmware with Odin.
Sent from Galaxy S Advance
ive got the error message for every app too. deleted many odex files. but it wouldn´t getting better. adb not running in taskmanager.
Starting BluetoothAvrcp.odex
*****************************************
* Deodexing... *
UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: Unknown opcode: f1
at org.jf.dexlib.Util.ExceptionWithContext.withContext(Exception
ext.java:54)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(In
nIterator.java:87)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:157)
at org.jf.dexlib.Item.readFrom(Item.java:76)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.jav
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.baksmali.main.main(main.java:254)
Caused by: java.lang.RuntimeException: Unknown opcode: f1
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(In
nIterator.java:51)
... 6 more
Error occured at code address 36
code_item @0x13dc
Drücken Sie eine beliebige Taste . . .
*****************************************
MAJOR ERROR!! WITH DEODEXING! BluetoothAvrcp.odex
*****************************************
********DELETING INCORRECT FILES*********
please exit out of window "***Deodexing ADB Window, DO NOT EXIT!***"
any ideas?
shut_down said:
This is for I9070, you only can get bootloop if you use this.
Click to expand...
Click to collapse
I disagree , this is a generic method for deodexing most phones , it's just that the stupid Sammy made un-deodexable .apks for us to suffer in
"Viper kills.....again!"