Related
Here is a step by step guide to root your xoom that is already updated to 3.1
You might also find this useful if you relocked your device to get the 3.1 update.
****** WARNING************ WARNING************ WARNING******
1. All steps are for the 3G Verizon Wireless Xoom. The steps are almost the same for WiFi but the files you need to download are different. You can find everything for your Wifi Xoom here: http://forum.xda-developers.com/showthread.php?t=1078019
2. You will lose all data by unlocking your device. This is just something you will need to plan for. Backup everything BEFORE you start this. If you Have any questions about backing up your data I will be happy to help. If you are already unlocked then you dont need to worry about this. /win
****** WARNING************ WARNING************ WARNING*******
How to use this guide
.....PLEASE READ THIS!......
This guide is divided into 3 sections:
1. Root Your Xoom
2. Flash CWR
3. Flash Kernal
These sections must be completed in order. If all you want is root then just do the 1st section. If you want SD card support then you must do all 3 steps.
Each section has its respective folder in the .rar file that I’ve linked Below.
1. Root files
2. CWR files
3. Kernel
As you work your way through this guide I will refer to files located in these folders.
All files used in this guide can be found here:
https://rapidshare.com/files/2447837220/3.1_Root_and_Recovery_Tools.rar
Or Here:
http://www.megaupload.com/?d=S9BTBCC6
***If people are having issues or don't understand how to set up ADB, this post helps a ton, and cuts out things you don't need***
http://www.xoomforums.com/forum/moto...platforms.html
Lets get started!!!!
**********************************
**********************************
Unlock and Root Your Xoom
>Root Files folder<
Steps found here:
http://forum.xda-developers.com/showthread.php?t=968342
1. Download the Motorola Xoom Root Zip file and unzip it.
(I replaced thes files with "root31.img", "SU", "superuser.apk" All found in the "Root Files" folder if you use my download link)
2. Place the files in the SDK Tools folder.
(You can skip the next 3 steps if you’ve unlocked with fastboot previously or if you lost root due to upgrading to 3.1)
3. adb reboot bootloader
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot (name of new boot.img(root31.img attached))
7. fastboot reboot (wait for reboot)
(you will need to enable usb debuging here)
8. adb remount
9. adb push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
_______________________________________________________
Flashed CWR
>CRW Files folder<
Steps found here:
http://forum.xda-developers.com/showthread.php?t=1074979
1. Download the recovery image (CWR.img attached)
2. Pull up your command prompt
3. Adb reboot bootloader
4. Fastboot flash recovery (name of recovery.img (CWR.img))
5. Fastboot reboot
_______________________________________________________
Flashed Kernel
>Kernel folder<
Steps found here:
http://forum.xda-developers.com/showthread.php?t=978013
1. Reboot into recovery. (adb reboot recovery or volume down while booting)
2. Go into "mounts and storage"
3. Select "mount USB storage"
4. Your SD Card will now be mounted on your computer. Drop the kernel (and boot image pack if applicable) onto SD Card.
5. "Go Back" then go into "install zip from sdcard" then "choose zip from sdcard"
6. If you are flashing a boot image pack, flash it first. (3G_light_ON_Speed.zip) Then flash the kernel zip. (Tiamat_Xoom-1.4.2_1.4Ghz.zip)
7. Back out to main menu and reboot.
_______________________________________________________
I am not taking credit for any of these steps I am simply trying to put the info in one place for people who need it.
The files I have attached Via download link are files taken from the threads listed above, I have not modified ANY of these files!
Where did you attach the files?
soooooo could have used this last night! Great job compiling all the stuff into one place!
Sorry, They are still attaching. Its taking forever. I will throw it up on rapidshare or something like like 2 min
2 min 10 sec
z06mike said:
Where did you attach the files?
Click to expand...
Click to collapse
Ok, download link is up there
https://rapidshare.com/files/503342030/3.1_Root_and_Recovery_Tools.rar
Awesome! Thanks
Updated Files.
https://rapidshare.com/files/1651389459/3.1_Root_and_Recovery_Tools.rar
sgtagem said:
Here is a step by step guide to root your xoom that is already updated to 3.1
All steps below were for my 3G Verizon Wireless Xoom. The steps are almost the same for WiFi but the files you need to download are different and must be found on the threads listed below.
All tools can be found here:
https://rapidshare.com/files/1651389459/3.1_Root_and_Recovery_Tools.rar
Unlocked and rooted my Xoom
Steps found here:
http://forum.xda-developers.com/showthread.php?t=968342
1. Download the Motorola Xoom Root Zip file and unzip it. (I replaced this file with the root31.img)
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot (name of new boot.img(root31.img attached))
7. fastboot reboot (wait for reboot)
(you might need to enable usb debuging here)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
_______________________________________________________
Flashed CWR
Steps found here:
http://forum.xda-developers.com/showthread.php?t=1074979
1. Download the recovery image ( I used the image that keeps charging light on)
2. Pull up your command prompt
3. Adb reboot bootloader
4. Fastboot flash (name of recovery.img (CWR.img attached))
5. Fastboot reboot
_______________________________________________________
Flashed Kernal
Steps found here:
http://forum.xda-developers.com/showthread.php?t=978013
1. Reboot into recovery.
2. Go into "mounts and storage"
3. Select "mount USB storage"
4. Your SD Card will now be mounted on your computer. Drop the kernel (and boot image pack if applicable) onto SD Card.
5. "Go Back" then go into "install zip from sdcard" then "choose zip from sdcard"
6. If you are flashing a boot image pack, flash it first. Then flash the kernel zip.
7. Back out to main menu and reboot.
_______________________________________________________
I am not taking credit for any of these steps I am simply trying to put the info in one place for people who need it.
Click to expand...
Click to collapse
When I clicked on the rapidshare link, my anti-virus warning went off with a vengence.
any chance this could be compiled into a one click methods for tards like me?
One adjustment needed, found on my end:
On step 9: "adb shell push su /system/bin" remove "shell", otherwise you end up with "push: not found" error
all the other lines are fine.
First off great instructions for rooting the 3G Xoom. But after going through the process last night there are a few things that may catch up users...
The "adb shell push su /system/bin" command may not work for at least some users or they may get a error. Should be changed to "adb push su /system/bin" or at least put a note to try that if the first does not work.
The "Fastboot flash (name of recovery.img (CWR.img attached))" should be "Fastboot flash recovery (name of recovery.img (CWR.img attached))" I know they should be able to figure this out but may cause some users a headache for a while while they figure it out.
You might also put a note that if you lost root due to upgrading to 3.1 but had earlier did the "fastboot oem unlock" when you were 3.0 or 3.0.1 you don't have to do the "fastboot oem unlock" again. The "fastboot oem unlock" wipes all the data which I don't think is necessary.
Overall though great instruction and I love how you provide a link with all the files right there in the instructions. I hate instructions that vagely tell you to get the files from another post and then not even provide a link to that post.
Dan
I updated the commands should work for all now
This is the 1st guide Ive done so I knew things would be missing, thanks for the heads up. I hate how some of those threads bounce you around like a ping pong ball.
Kamau54 said:
When I clicked on the rapidshare link, my anti-virus warning went off with a vengence.
Click to expand...
Click to collapse
If you are worried about the DL link you can get the files from the threads directly. I would never put my reputation at risk by spreading infected files. Cant really say much more
Brenardo said:
any chance this could be compiled into a one click methods for tards like me?
Click to expand...
Click to collapse
Im sure someone will. I would have no clue how sorry
thanks for the guide!!!
has there been any news about geting the SD working? i had it working om 3.0.1
iDroidNow said:
thanks for the guide!!!
has there been any news about geting the SD working? i had it working om 3.0.1
Click to expand...
Click to collapse
It works after doing all these steps. It will show up as "External"
it does not work on mine with these exact instructions and i have read about others having the same issue.
iDroidNow said:
it does not work on mine with these exact instructions and i have read about others having the same issue.
Click to expand...
Click to collapse
If you boot into recovery and go into mounts and storage can you mount it. if you plug in your computer from this point you should see external.
ok i was referring to seeing it in a File browser (Astro) etc... i guess that is not working yet?
thanks for the information.
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE
Awesome!
does not work for me...
Worked perfect here, that fixes my only serious issue with the ICS rom.
I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.
Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.
Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!
Can anyone help me with this via step by step?
I could use a little help as well
Sent from my SGH-I927 using xda app-developers app
Yea, i could use some help too, after re-writing over the existing file didn't work
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch
ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man
LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?
Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister
Hummm is their gonna b a flashable zip for this ?
Deodexed using DsiXda's Rom kitchen, so credit goes to DsiXda.
Do it at your own risk ! I'm just as NOOB as any on this forum. I just followed few topics and made this up.
I'm not responsible if your Xperia S gets bricked , because mine is working fine.
Follow steps correctly or else you get bootloops and you have to flash your rom again.
Your SXS must be rooted (with Locked Bootloader or Unlocked boot loader) on Stock ICS ROM 6.1.A.2.45 without any mods like toggles or reboot menus.
So i recommend to do this just after you flash & root your Stock ICS ROM 6.1.A.2.45.
Install Latest 'BusyBox' from Andriod Market.
Make complete backup first.
Step1: Downloading & Copying files on to phone's internal storage
These are NOT and i repeat NOT flashable zips through recovery.
Extracting the below zips on your PC you get two folders namely done_app & done_frame.
Copy these two folders on to your Xperia S. (Please Do Not rename the folders)
Deodexed_app .45(146mb)
Deodexed_frame .45(24mb)
Deodexed_app .50(150mb)
Deodexed_frame .50(24mb)
Step2: Pushing them onto your phone. (Adopted from xUltimate method, credits to him )
You should have ADB correctly setup on your PC.
Turn on your Xperia S.
Enable Settings>Security>Unknown Sources.
Enable Settings>Developer Options>Usb Debugging.
Disable Xperia>Connectivity>Install PC Companinon.
Connect phone to your PC . Wait for PC to show up internal storage.
Go to 'platform-tools' folder in your adnroid-sdk folder, hold shift down and right click mouse, select 'Open Command window here' , You'll get a cmd window.
Enter the below code in the cmd window line by line
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
After the phone reboots you'll have deodexed rom.
I also made 30 steps Volume mod i'll share it once deodexing works perfectly for you guys because it works only on deodexed roms. Have fun !
iamsuperuser said:
Great ! Thanks for your interest. Deodexed using DsiXda's Rom kitchen, so credit goes to DsiXda.
Do it at your own risk ! I'm just as NOOB as any on this forum. I just followed few topics and made this up.
I'm not responsible if your Xperia S gets bricked , because mine is working fine.
Follow steps correctly or else you get bootloops and you have to flash your rom again.
Your SXS must be rooted (with Locked Bootloader or Unlocked boot loader) on Stock ICS ROM 6.1.A.2.45 without any mods like toggles or reboot menus.
So i recommend to do this just after you flash & root your Stock ICS ROM 6.1.A.2.45.
Install Latest 'Busybox' from Andriod Market.
Make complete backup first.
Step1: Downloading & Copying files on to phone's internal storage
These are NOT and i repeat NOT flashable zips through recovery.
Extracting the below zips on your PC you get two folders namely done_app & done_frame.
Copy these two folders on to your Xperia S. (Please Do Not rename the folders)
Deodexed_app(146mb)
Deodexed_frame(24mb)
Step2: Pushing them onto your phone. (Adopted from xUltimate method, credits to him )
You should have ADB correctly setup on your PC.
Turn on your Xperia S.
Enable Settings>Security>Unknown Sources.
Enable Settings>Developer Options>Usb Debugging.
Disable Xperia>Connectivity>Install PC Companinon.
Connect phone to your PC . Wait for PC to show up internal storage.
Go to 'platform-tools' folder in your adnroid-sdk folder, hold shift down and right click mouse, select 'Open Command window here' , You'll get a cmd window.
Enter the below code in the cmd window line by line
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
After the phone reboots you'll have deodexed rom.
I also made 30 steps Volume mod i'll share it once deodexing works perfectly for you guys because it works only on deodexed roms. Have fun !
Click to expand...
Click to collapse
this should be stickied! Post this in Development mate! :good:
I've been waiting for this. I'll try it with pdroid once I have the time.
blakwhite said:
I've been waiting for this. I'll try it with pdroid once I have the time.
Click to expand...
Click to collapse
Report back I wanna try this too! But I'm kind of busy
iamsuperuser said:
Great ! Thanks for your interest. Deodexed using DsiXda's Rom kitchen, so credit goes to DsiXda.
Do it at your own risk ! I'm just as NOOB as any on this forum. I just followed few topics and made this up.
I'm not responsible if your Xperia S gets bricked , because mine is working fine.
Follow steps correctly or else you get bootloops and you have to flash your rom again.
Your SXS must be rooted (with Locked Bootloader or Unlocked boot loader) on Stock ICS ROM 6.1.A.2.45 without any mods like toggles or reboot menus.
So i recommend to do this just after you flash & root your Stock ICS ROM 6.1.A.2.45.
Install Latest 'Busybox' from Andriod Market.
Make complete backup first.
Step1: Downloading & Copying files on to phone's internal storage
These are NOT and i repeat NOT flashable zips through recovery.
Extracting the below zips on your PC you get two folders namely done_app & done_frame.
Copy these two folders on to your Xperia S. (Please Do Not rename the folders)
Deodexed_app(146mb)
Deodexed_frame(24mb)
Step2: Pushing them onto your phone. (Adopted from xUltimate method, credits to him )
You should have ADB correctly setup on your PC.
Turn on your Xperia S.
Enable Settings>Security>Unknown Sources.
Enable Settings>Developer Options>Usb Debugging.
Disable Xperia>Connectivity>Install PC Companinon.
Connect phone to your PC . Wait for PC to show up internal storage.
Go to 'platform-tools' folder in your adnroid-sdk folder, hold shift down and right click mouse, select 'Open Command window here' , You'll get a cmd window.
Enter the below code in the cmd window line by line
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
After the phone reboots you'll have deodexed rom.
I also made 30 steps Volume mod i'll share it once deodexing works perfectly for you guys because it works only on deodexed roms. Have fun !
Click to expand...
Click to collapse
Mate you got to share the 3o step volume thing..
Sent from my LT26i using xda premium
Harsh7689 said:
Mate you got to share the 3o step volume thing..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
No big deal man chill ! Let some of the users confirm this method, I'll share it. It is only for deodex users. If I share it now stock odex users will have bootloops.
Links Updated. Please discard old files and download new ones .
great work buddy...
Has anyone tried this yet ?? Please give feedback so that i can post in development section.
iamsuperuser said:
Has anyone tried this yet ?? Please give feedback so that i can post in development section.
Click to expand...
Click to collapse
I'm trying it... will post as soon as i finished...
I have done it.. all step went without any errors... after reboot showed rebuilding cache (android is updating showed up).. no .odex in app folder..
I hope thats... DeOdexed...voilaa....
s-X-s said:
I'm trying it... will post as soon as i finished...
I have done it.. all step went without any errors... after reboot showed rebuilding cache (android is updating showed up).. no .odex in app folder..
I hope thats... DeOdexed...voilaa....
Click to expand...
Click to collapse
What about framework folder ?
yaaa both are pushed to respective folders... but i donno how to confirm framework is doedexed?
Nice job.... 30 Steps media volume is already there... By krabappel2548
s-X-s said:
yaaa both is pushed to respective folder... but i donno how to confirm framework is doedexed?
Click to expand...
Click to collapse
Check if there is any .odex files on framework folder.
I request the forum mods to move this topic to development section . Thanks s-X-s for testing.
iamsuperuser said:
I request the forum mods to move this topic to development section . Thanks s-X-s for testing.
Click to expand...
Click to collapse
Pm the moderators... E.Cardo or cooleagle
Hi noob question..what this tutorial does?
nemer12 said:
Hi noob question..what this tutorial does?
Click to expand...
Click to collapse
you should give a look here : http://forum.xda-developers.com/showthread.php?t=1363749
Sorry, a wrong post, please del it
Sent from my LT26i using xda app-developers app
milton.bain said:
Nice job.... 30 Steps media volume is already there... By krabappel2548
Click to expand...
Click to collapse
Yes but I need to update it to the latest fw and this method works for more devices then our XS I did it for 2011 line in my starting days there
In fact it will deodex most firmwares for most Android devices on Gingerbread, ICS or even Jellybean with the latest update, so it's not strictly for Xperia S and ICS
Sent from my LT26i using xda app-developers app
My first post on Nexus forums..!!! This post aims to collect all mods that are working on stock 4.2 In order to use them, you need to deodex you roms. The good news is that this job was done already. I deodexed system/app folder myself and used system/framework files from bigxie's rom cause I had trouble deodexing core file in that folder. I will go through a very brief tutorial - everybody can do this!!!
You are very welcome to post links for more mods at this thread so I can add it here in order for everybody to be aware off.
=======================================================================================================
Part 1 - Pushing Deodexed Files To System
1. You must be rooted, have busy box installed and have USB Debuggind ON under Developer Options in Settings
2. Extract done_app and done_frame folders from here on your PC and copy/paste them on your SD Card
3. You need to install android-sdk on your PC and set it up. It will be installed in c:\program files or c:\program files (x86) depending on what system you have (32-64bit)
4. Once that done open command promt and taking for example you have a 64-bit system. Please note that code must be done as follows. If you can't tell if there's a space between words, copy/paste code on a notepad for you to see it more clearly
cd..
cd.. (this will bring you to c:\> line)
cd program files (x86)
cd android
cd android-sdk
cd platform-tools
adb shell (wait a second for adb to start)
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
Your rom is now deodexed!!! Note that during the procedure you must not touch your phone.
=======================================================================================================
Part 2 - Mods working on stock JB 4.2 - TESTED!
You must have CWM or TWRP recovery installed
1. Android 4.2 Quick Settings & Lockscreen Widgets Mods
2. White Navbar Mods 24dpi/28dpi/32dpi/36dpi
3. Blue Navbar Mods 24dpi/28dpi/32dpi/36dpi
4. Rotation Lock in Quick Settings / Screen Lock button to Statusbar
5. Lockscreen Policy - Disable Android 4.2 Lockscreen Widgets, Camera
Compatibility:
** 1+2 YES
** 1+3 YES
** 4 is not compatible with 1, 2 and 3 cause the framework-res.apk is different. You won't get a bootloop or anything, it's just that one mod erases the other BUT you can have only the "volume rocker wake" mod without the rotation lock. There's a link on developer's thread
** 5 is compatible with all
=======================================================================================================
PS - Kernels: Latest Leankernel works very well on 4.2, give it a go!!!
It's STOCK alright...
Sent from my Galaxy Nexus using xda premium
Hi thanks for the guide
how bout transparent nav bar? i would love to add that to my stock JB! Thanks!
off-topic...just happy to announce that very shortly, my first ROM for the NEXUS is going live. Stay tuned!
Compatible
Is this MOD only compatible with 4.2 stock?
Warning: This is very advanced, if you do not know what it is, dont play play.
I'm not responsible if your device bricked during deodexing process.
This method has been commonly used, I just improved it and included important cautions and precautions.
Requirements:
- Rooted firmware (Search XDA)
- Busybox installed (included when root with Root Many Droid)
- ADB correctly set up on computer *(sdk + environment variables setup)* ? - if u dont know what it is, as long as sdk installed is ok *(only sdk installed)*
- Xperia S with coresponding firmware version.
- In phone, usb debugging enabled, unknown sources enabled
- Downloaded app and framework zips
Downloads:
LT26i - 6.2.B.1.96 deodexed **not tested** by zhuhang
http://www.androidfilehost.com/?fid=23060877490002553LT26i - 6.2.B.0.200 deodexed **not tested** by @davidbar93
https://www.dropbox.com/s/saog0fip6m8gsyf/done_app.rar
https://www.dropbox.com/s/d8s6rll8esatzny/done_frame.rarLT26i - 6.1.A.2.55 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593433
http://www.androidfilehost.com/?fid=9390244042945593434LT26i - 6.1.A.2.50 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593431
http://www.androidfilehost.com/?fid=9390244042945593432LT26i - 6.1.A.2.45 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593350
http://www.androidfilehost.com/?fid=9390244042945593351
Instructions:
1. Extract downloaded zips
2. Copy done_app and done_frame to /sdcard/ (via MTP acceptable)
3. Make sure debugging mode connected
4. (i) Open Command Prompt on PC (Ctrl + R > cmd) *(sdk + environment variables setup)*
4. (ii) Go to /android-sdk/platform-tools/ folder, hold Shift button and right click mouse, 'Open Command window here' (Win 7) *(only sdk installed)*
5. Enter lines ony by one:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
busybox cp /sdcard/done_app/* /system/app/
busybox rm /system/app/*.odex
busybox cp /sdcard/done_frame/* /system/framework/
busybox rm /system/framework/*.odex
chmod 644 /system/app/*
chmod 644 /system/framework/*
busybox mount -o ro,remount /system/ /system/
reboot
6. Close Command Prompt
7. Wait for phone to reboot, you'll see "Android Upgrading, Optimizing aplications..."
8. If optimizing aplications succeed, congratulations, ur stock rom is deodexed! Done.
Note: Every time u put apks into /system/app/ and restart, Android Upgrading will appear for once.
Donations:
Its also recommended to make donation using Paypal balance. (lower transaction fee)
My Paypal Account is ready! Malaysian please PM me for local bank account.
I would appreciate if you can donate to me so I can maintain this OP. I'm also making IRS for you guys.
Credits:
Deodexed using dsixda's kitchen
Compressed using Winrar
Is it as simple as that?
eScapeeXc said:
Is it as simple as that?
Click to expand...
Click to collapse
Definitely yes if u know the commands and steps.
Try it yourself then, i've done hundred times on acroS and XS
Link to acroS in my sig.
zhuhang said:
Warning: This is very advanced, if you do not know what it is, dont play play.
I'm not responsible if your device bricked during deodexing process.
This method has been commonly used, I just improved it and included important cautions and precautions.
Requirements:
- Clean Rom (best with data wiped, orelse FCs)
- Rooted firmware (Root with Root Many Droid : here)
- Busybox installed (included when root with Root Many Droid)
- ADB correctly set up on computer *(sdk + environment variables setup)* ? - if u dont know what it is, as long as sdk installed is ok *(only sdk installed)*
- Xperia S with: usb debugging enabled, unknown sources enabled
- Downloaded app and framework zips
Downloads:
LT26i .45 deodexed
http://www.androidfilehost.com/?fid=9390244042945593350
http://www.androidfilehost.com/?fid=9390244042945593351
Instructions:
1. Extract downloaded done_app and done_frame zips
2. Copy done_app and done_frame to /sdcard/ (via MTP acceptable)
3. Make sure debugging mode connected
4. (i) Open Command Prompt on PC (Ctrl + R > cmd) *(sdk + environment variables setup)*
4. (ii) Go to /android-sdk/platform-tools/ folder, hold Shift button and right click mouse, 'Open Command window here' (Win 7) *(only sdk installed)*
5. Enter lines ony by one:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
busybox cp /sdcard/done_app/* /system/app/
busybox rm /system/app/*.odex
busybox cp /sdcard/done_frame/* /system/framework/
busybox rm /system/framework/*.odex
busybox mount -o ro,remount /system/ /system/
reboot
Note: Do not change permissions of files to 644 or folders to 755! We'll do it later.
6. Leave Command Prompt open
7. Wait for phone to reboot, if optimizing aplications succeed, congratulations, ur stock rom is deodexed!
8. Now let's manually fix some permissions
9. Return to Command Prompt
10. Enter lines ony by one:
Code:
adb shell
su
mount -o rw,remount /system/ /system/
chmod 644 /system/app/*
chmod 644 /system/framework/*
busybox mount -o ro,remount /system/ /system/
reboot
11. After phone reboot, there should be no more "Android Upgrading, Optimizing aplications..."
12. Viola, Done!!
Note: Every time u put apks into /system/app/ and restart, Android Upgrading will appear for once.
Credits:
Deodexed using dsixda's kitchen
Packed using Winrar
Click to expand...
Click to collapse
Is this what u used for AC!D V6? is the internal speaker volume low?
darkace007 said:
Is this what u used for AC!D V6? is the internal speaker volume low?
Click to expand...
Click to collapse
This is deodexing stock ICS rom, nothing to do with any mod or acid v6
Do u know what's deodexing?
I dont exactly know but its about theming possibilties right but I saw one of ur posts that AC!D works for stock .45.
Sent from my LT26i using xda app-developers app
darkace007 said:
I dont exactly know but its about theming possibilties right but I saw one of ur posts that AC!D works for stock .45.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Deodex is not for theming. U can understand it somewhere else
I will add advantages of deodexing to 1st post.
Acid v6 not working yet, I haven't really tested. V5 works.
It doesn't matter whether ur Rom is odexed or deodexed, the advantage is no android upgrade loop on deodexed Rom.
Sent from my LT26i using xda app-developers app
You can actually a package, which used here man. Sdk, busybox, etc. It would be better. And one more question. Is it exactly at .55?
eScapeeXc said:
You can actually a package, which used here man. Sdk, busybox, etc. It would be better. And one more question. Is it exactly at .55?
Click to expand...
Click to collapse
Sdk has to be installed (few hundred Mbs) + Java
Root+busybox link given.
I can't make a package for that. Maybe links. I will consider.
Its .45, I'll do .50 and .55, can anyone provide me the app and framework?
There was another Deodexed .45 thread here.... if it was .55 would been better...
s-X-s said:
There was another Deodexed .45 thread here.... if it was .55 would been better...
Click to expand...
Click to collapse
Very soon...
Sent from my LT26i using xda app-developers app
zhuhang said:
Sdk has to be installed (few hundred Mbs) + Java
Root+busybox link given.
I can't make a package for that. Maybe links. I will consider.
Its .45, I'll do .50 and .55, can anyone provide me the app and framework?
Click to expand...
Click to collapse
s-X-s said:
There was another Deodexed .45 thread here.... if it was .55 would been better...
Click to expand...
Click to collapse
Just a thought why don't take .55 deodex both app and framework from the ROM I post long ago. It is in zip format so you could easily extract app and framework then follow instruction in first post to inject to your ROM.
tosa.th said:
Just a thought why don't take .55 deodex both app and framework from the ROM I post long ago. It is in zip format so you could easily extract app and framework then follow instruction in first post to inject to your ROM.
Click to expand...
Click to collapse
Where did u posted it?
zhuhang said:
Where did u posted it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2005595
tosa.th said:
http://forum.xda-developers.com/showthread.php?t=2005595
Click to expand...
Click to collapse
U modified a little things.
zhuhang said:
U modified a little things.
Click to expand...
Click to collapse
Yes, I delete few app that recognize as bloat ware (this is recommended by rom kitchen) I see that you also use rom kitchen I believe you should see that as well.
The other change is not relate to app and framework.
tosa.th said:
Yes, I delete few app that recognize as bloat ware (this is recommended by rom kitchen) I see that you also use rom kitchen I believe you should see that as well.
The other change is not relate to app and framework.
Click to expand...
Click to collapse
Nope, i didnt saw which is recognized bloatware.
Which one?
zhuhang said:
Nope, i didnt saw which is recognized bloatware.
Which one?
Click to expand...
Click to collapse
Didn't write it down so can not tell you exactly which one.
It said some thing like do you want to remove bloatware ? I just say yes.
May be you could try to deodex .55 ROM then see if it detect any bloatware.
tosa.th said:
Didn't write it down so can not tell you exactly which one.
It said some thing like do you want to remove bloatware ? I just say yes.
May be you could try to deodex .55 ROM then see if it detect any bloatware.
Click to expand...
Click to collapse
I never encounter bloatware detected, anyway i will remove any apps.
Updated 27/12/12
Added:
LT26i - 6.1.A.2.50
LT26i - 6.1.A.2.55
Both not tested, let me know the result.
EDIT: Should be LT26i