Related
Just for fun I have been looking at getting Rosie on to the Android Emulator and to see what I can do. All is well I believe except I am missing some shared librarys and a permisions file...
adb push com.htc.android.easopen.jar /system/framework/
adb push com.htc.android.pimlib.jar /system/framework/
adb push com.htc.framework.jar /system/framework/
adb push com.scalado.util.ScaladoUtil.jar /system/framework/
adb push com.htc.resources.apk /system/framework/
adb push framework-res.apk /system/framework/
adb push com.htc.framework.xml /etc/permissions/
Any way - I cant get these on to the relevant directory due to them ( framework / permissions ) been read only. I'm trying to do this in a way that wont massivly change a rom so i was hoping that I would be able to install to an unrooted device by changing just those directorys permissions.... in fact I assumed the emulator would be unrooted ???
Any way - pointers for this Android noob would be much apprciated......
PS I started by using the Android Toggle.bat so cudos to the Dev who started that.... I forgot your user name
Also is there any way to read the dependancys of an apk ? The know what they need and I am guessing by using logic..... might help to optimise my mess.
Heres the rest as is.... still a lot of messing to go...
Code:
@echo off
:start
cls
ECHO ********************************************************
ECHO * 1. Install HTC 2. Nothing to See *
ECHO ********************************************************
ECHO.
:opt
Set /p xch=Select Option:
If '%xch%'=='1' Goto choice1
If '%xch%'=='2' Goto choice2
ECHO That is not a valid choice, please try again.
ECHO.
Goto opt
:choice1
ECHO.
ECHO **********************
ECHO * Installing HTC *
ECHO **********************
adb push com.htc.android.easopen.jar /system/framework/
adb push com.htc.android.pimlib.jar /system/framework/
adb push com.htc.framework.jar /system/framework/
adb push com.scalado.util.ScaladoUtil.jar /system/framework/
adb push com.htc.resources.apk /system/framework/
adb push framework-res.apk /system/framework/
adb push com.htc.framework.xml /etc/permissions/
adb install AndFTP.apk
adb install AndExplorer.apk
adb install FlashPlayer.apk
adb install framework-res.apk
adb install com.htc.resources.apk
adb install Launcher.apk
adb install Rosie.apk
adb install com.htc.TwitterWidget.apk
adb install com.htc.MusicWidget.apk
adb install com.htc.StockWidget.apk
adb install com.htc.WeatherWidget.apk
adb install AccountManager.apk
adb install AndroidMarket.apk
adb install HTC_CIME.apk
adb install HtcAddProgramWidget.apk
adb install HTCAlbum.apk
adb install htccalendarwidgets.apk
adb install HtcClockWidget.apk
adb install HtcContacts.apk
adb install htccontactwidgets.apk
adb install HtcFootprints.apk
adb install HtcFootprintsWidget.apk
adb install htcinternetwidget.apk
adb install HtcLocationPicker.apk
adb install HtcLocationService.apk
adb install HtcLockScreen.apk
adb install HtcLog.apk
adb install htcmailwidgets.apk
adb install htcmsgwidgets.apk
adb install HtcMusic.apk
adb install com.htc.WeatherWidget.apk
adb install HTCNew.apk
adb install HtcPhotoWidget.apk
adb install HtcRingtoneTrimmer.apk
adb install htcsearchwidgets.apk
adb install HtcSettingsProvider.apk
adb install htcsettingwidgets.apk
adb install HTCSetupWizard.apk
adb install HtcSoundRecorder.apk
adb install HtcStreamPlayer.apk
adb install HtcTwitter.apk
adb install IM.apk
adb install ImProvider.apk
adb install Stk.apk
adb install SocialNetworkProvider.apk
ECHO.
ECHO Completed! Rebooting...
Pause
adb shell reboot
Exit
:choice2
ECHO.
ECHO **********************
ECHO * Nothing to see *
ECHO **********************
Exit
Terran
It would be easier to create a ROM that did not require the SWAP file, then flashing it into a G1, then doing a nandroid backup and using that for the Emulator (and adding much more RAM in the emulator.)
ivanmmj said:
It would be easier to create a ROM that did not require the SWAP file, then flashing it into a G1, then doing a nandroid backup and using that for the Emulator (and adding much more RAM in the emulator.)
Click to expand...
Click to collapse
Can you please elaborate on this a bit? How do I translate a nandroid backup into an avd file that the emulator can boot? I wanted to do this exact thing but never really figured out how. Will really appreciate your step by step?
devsk said:
Can you please elaborate on this a bit? How do I translate a nandroid backup into an avd file that the emulator can boot? I wanted to do this exact thing but never really figured out how. Will really appreciate your step by step?
Click to expand...
Click to collapse
This is a step by step walkthrough:
http://forum.xda-developers.com/showpost.php?p=3952890&postcount=7
If you get it up and running, I'd appreciate a copy of that system.img (without the swap partition requirement). ^_^
ivanmmj said:
It would be easier to create a ROM that did not require the SWAP file, then flashing it into a G1, then doing a nandroid backup and using that for the Emulator (and adding much more RAM in the emulator.)
Click to expand...
Click to collapse
MMmmmm - where I was trying to get to was the point where some one could just run this batch and update their eum / phone with out messing around with custom roms etc.... I have a feeling I am flogging a dead donkey going down that route though.
Terran
ccsnet said:
Just for fun I have been looking at getting Rosie on to the Android Emulator and to see what I can do. All is well I believe except I am missing some shared librarys and a permisions file...
adb push com.htc.android.easopen.jar /system/framework/
adb push com.htc.android.pimlib.jar /system/framework/
adb push com.htc.framework.jar /system/framework/
adb push com.scalado.util.ScaladoUtil.jar /system/framework/
adb push com.htc.resources.apk /system/framework/
adb push framework-res.apk /system/framework/
adb push com.htc.framework.xml /etc/permissions/
Any way - I cant get these on to the relevant directory due to them ( framework / permissions ) been read only.
Click to expand...
Click to collapse
You can make /system rw by using a remount command. It's not enough to just push the framework files onto system though. They need to be added to BOOTCLASSPATH in the init.rc as well. You'll have to unyaffs boot.img
Also is there any way to read the dependancys of an apk ? The know what they need and I am guessing by using logic..... might help to optimise my mess.
Click to expand...
Click to collapse
Look in the AndroidManifest.xml
jashsu said:
You can make /system rw by using a remount command. It's not enough to just push the framework files onto system though. They need to be added to BOOTCLASSPATH in the init.rc as well. You'll have to unyaffs boot.img
Look in the AndroidManifest.xml
Click to expand...
Click to collapse
Thanks....
Terran
EDIT - Remount command info - http://groups.google.com/group/andr...7ecb631689/da581f1b398fdf8b?#da581f1b398fdf8b
Last updated 2/28/2011
This is a pure stock rom with root+hsupa+sideload.
Warning: the following steps to flash the rom will wipe your data.
- Use HTC Inspire Hack Kit or some other way to get S-off so that you can flash custom roms.
- Download the rom, rename it to PD98IMG.zip, put it to the sdcard.
- Go to Settings -> Applications, turn off fast boot and then power down the phone.
- Boot into hboot by pressing volume down + power button and flash.
After flashing you should have a pure stock rom rooted, with hsupa on, and sideloading as an option. I don't have any problem with this rom while I got superuser permission, sideloading back on and noticed a higher upload speed.
Some people report to have problem with ClockWorkMod recovery on the stock rom. You can try the suggestion from this thread.
Link for the ROM: http://www.multiupload.com/93I04ACXYU
--------------------------------
Below are the steps that I took to made this rom, you can ignore it if you are not interested into know how to cook system.img or hack a rom.
I basically added the root files to the system.img and change ro.ril.hsxpa=1 inside of the build.prop file to ro.ril.hsxpa=3 to make hsupa work, edit the customize/CID/default.xml file and change <item name="unknown_sources_visibility">false</item> to <item name="unknown_sources_visibility">true</item> to enable the sideloading option in settings, no need to flash any custom radio or kernel.
Here's how to do it:
- Download the RUU for the stock rom.
- Open the RUU you downloaded, wait for the screen that says Welcome to the Rom Update Utility to come out, but don't flash yet!
- Navigate to the temporary folder and locate rom.zip, which is a file that the installer extracted. I found it by navigating the folder with the most recent Date modified.
- Copy rom.zip to some other folder. This is the zip file which you can use on the phone to flash back to stock.
- Extract android-info.txt and system.img from rom.zip and put system.img in a place where Linux can access.
Right now for the cooking part linux is required. I used Ubuntu to do it.
Code:
sudo mkdir /mnt/system
sudo mount -o loop,norelatime /path to/system.img /mnt/system
Code:
nano /mnt/system/build.prop
update ro.ril.hsxpa to 3 to enable hsupa
You also need the root files busybox, su, and Superuser.apk, which can be found at ace-hack-kit-v002/tools/root
Code:
sudo
cp /path to root files/busybox /mnt/system/xbin/busybox
chmod 4755 /mnt/system/xbin/busybox
cp /path to root files/Superuser.apk /mnt/system/app/Superuser.apk
chmod 644 /mnt/system/app/Superuser.apk
cp /path to root files/su /mnt/system/bin/su
chmod 4755 /mnt/system/bin/su
nano /mnt/system/customize/CID/default.xml
(update <item name="unknown_sources_visibility">false</item> to <item name="unknown_sources_visibility">true</item> to enable the sideloading option in the menu.)
umount /mnt/system
Right now you have a cooked system.img
- extract all files from rom.zip, replace system.img with the one we just cooked, then put all the files back to a new zip named PD98IMG.zip.
--------------------------------
Couldn't you post your cooked PD98IMG.zip for us? Shouldn't it work for all Inspire devices if it was taken from the official RUU?
it is very big, hold down. The phone needs to be S-off first in order to flash.
angelchen1111 said:
it is very big, hold down. The phone needs to be S-off first in order to flash.
Click to expand...
Click to collapse
Yeah... but you should still be able to post it. That would be a WHOLE lot easier than every one of us making the exact same file when we could just flash the one you made. Make sense?
If you want to share, try uploading it to multiupload.com
Pre-rooted stock system.img
File name: PD98IMG.zip File size: 242.81 MB
More links
have fun
Here's the link [removed]. Revert back to stock after being S-off to flash it. Also flashing system.img seem to factory reset the phone, so back up your data inside of your phone if any before flashing.
I just tried it and it did give me root access. Upload speeds are still crappy for me. It was worth the time just for root access. Thanks!
so let me ask a question. If someone were to use temp root with say visionary, can S-off be set from there without a gold card?
angelchen1111 said:
I found a way to enable hsupa and root the phone on the stock rom by "cooking" system.img from the stock rom and flash it over after the phone has been S-off and returned to stock.
I basically added the root files to the system.img and change ro.ril.hsxpa=1 inside of the build.prop file to ro.ril.hsxpa=3 to make hsupa work, no need to flash any custom radio or kernel.
Here's how to did it (this still looks kind like rough draft, I don't know if someone can help me to edit this to make it better or if I can put it up to wiki):
- use HTC Inspire Hack Kit or some other way to get S-off so that you can flash custom roms.
- Download the RUU for the stock rom.
- Open the RUU you downloaded, wait for the screen that says Welcome to the Rom Update Utility to come out, but don't flash yet!
- Navigate to the temporary folder and locate rom.zip, which is a file that the installer extracted. I found it by navigating the folder with the most recent Date modified.
- Copy rom.zip to some other folder. This is the zip file which you can use on the phone to flash back to stock.
- After done copying rom.zip proceed with RUU to flash back to stock.
- Extract android-info.txt and system.img from rom.zip and put system.img in a place where Linux can access.
Right now for the cooking part linux is required. I used Ubuntu to do it.
Code:
sudo mkdir /mnt/system
sudo mount -o loop,norelatime /path to/system.img /mnt/system
use an editor to edit /mnt/system/build.prop and update ro.ril.hsxpa to 3 to enable hsupa
You also need the root files busybox, su, and Superuser.apk, which can be found at ace-hack-kit-v002/tools/root
Code:
sudo
cp /path to root files/busybox /mnt/system/xbin/busybox
chmod 4755 /mnt/system/xbin/busybox
cp /path to root files/Superuser.apk /mnt/system/app/Superuser.apk
chmod 644 /mnt/system/app/Superuser.apk
cp /path to root files/su /mnt/system/bin/su
chmod 4755 /mnt/system/bin/su
umount /mnt/system
Right now you have a cooked system.img
put android-info.txt and the cooked system.img to a zip named PD98IMG.zip and put it to the sd card.
boot into hboot by pressing volume down and power button and flash.
After flashing you should have a pure stock rom rooted and with hsupa on. I don't have any problem with this rom while I got superuser permission and noticed a higher upload speed.
Click to expand...
Click to collapse
The install was fine and i have not had any fc yet. the only problem that i have is that i cant install non market apps. any suggestions on how to allow restore from titanium backup?
farmercyst said:
The install was fine and i have not had any fc yet. the only problem that i have is that i cant install non market apps. any suggestions on how to allow restore from titanium backup?
Click to expand...
Click to collapse
Once it is rooted, it is trivial to enable sideloading.
Code:
adb shell
su
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /sdcard/settings.db
adb shell
su
busybox cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chown system.system /data/data/com.android.providers.settings/databases/settings.db
chmod 660 /data/data/com.android.providers.settings/databases/settings.db
exit
exit
After thar reboot and you should have sideloading
if it says command not found, try to append busybox in front of the commands.
thanks a lot. stock with root and sideloading is what i have been wanting.
Guess I will be going this route in the meantime as well. Can't handle the "tinny" audio in DHD ROMs.
Sent from my Desire HD using XDA App
So with the way you have this setup as of right now, it only works with a computer running the Linux OS?
Sent from my Inspire 4G.
slapdaddy said:
So with the way you have this setup as of right now, it only works with a computer running the Linux OS?
Sent from my Inspire 4G.
Click to expand...
Click to collapse
You need Linux to open the system.img in order to cook.
angelchen1111 said:
Once it is rooted, it is trivial to enable sideloading.
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /sdcard/settings.db
adb shell
su
cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chmod 666 /data/data/com.android.providers.settings/databases/settings.db
chown system.system /data/data/com.android.providers.settings/databases/settings.db
After thar reboot and you should have sideloading
if it says command not found, try to append busybox in front of the commands.
Click to expand...
Click to collapse
After "cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db", I get "cp: not found".
after using this method getting everything setup I ran across one issue so far
ROM manager "clockworkmod" issue ,,when rebooting into recovery, screen freaks out white then fading to black ,wait for a while & nothing ,hit power button phone reboots like nothing happend.
How is this done with the file that I'm downloading? The "cooked" file
how do you boot into hboot?
i wish you guys would enlighten me! I guess it's hard for a noob to get any help! Maybe I should just go back to modmyi and be a snob.
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
First of all: NO WARRANTY AT ALL. I have no idea what I'm doing... it simply worked what I did
Attached is also the Calendar and Email APK files - I got them from the stable Cyanogenmod repository for HTC Desire HD (update-cm-7.1.0-DesireHD-signed - thanks crybert!!)
Not documented as well as the method to do it manually, I now also created a Faemod/CWM installable zipfile:
http://forum.xda-developers.com/showpost.php?p=20520096&postcount=38
If you want to do it manually, continue the guide below...
In all cases:
1. Stop all internet access on device (Data & Wifi, preferably Flight Mode) to avoid sync
2. Go to Settings
3. Select Applications
4. Select Manage Applications & Select All tab & scroll to Calendar
5. Select Calendar
6. Press Clear Data (WARNING: make sure you have a backup using Sync!)
7. Press OK to Clear all Calendar data
8. Press Back (hardbutton) & scroll to Email
9. Repeat Clear data for Email applications (also Force Stop first, if available, may be a good idea)
Then for replacing using Root Explorer:
1. Download & install Root Explorer (or any explorer app that allows you to mount /system/app as writable)
2. Enable Mass Storage or Mound SDCard in PC
3. Copy ICS folder (with APK files in it) to SDCard
4. Disable Mass Storage (!)
5. Start Root Explorer
6. Browse to /sdcard/ICS and click Menu (hardbutton)
7. Select all of the files (Select All button)
8. Press Copy
9. Browse to /system/app folder, by default system is mounted as Read Only
10. Press "Mount R/W" button
11. Press Paste (and sometimes accept warning)
12. Delete the ApplicationsManager.odex, Email.odex and TouchWizCalendar.odex files
13. Modify the permissions of Email.apk and TouchWizCalendar.apk
14. Restart your device
Optionally, here's the steps for replacing using ADB:
1. Root your device
2. Install the Android SDK or ADB Tools
3. Take Email.apk, ApplicationsProvider.apk and TouchWizCalendar.apk and copy them to your adb folder
4. If also doing the calendar from another source, make sure to rename Calendar.apk to TouchWizCalendar.apk
5. Run the following code using (USB debugging and root access are required for this!):
Code:
adb -d pull /system/app/Email.apk Email.apk.bak
adb -d pull /system/app/Email.odex Email.odex.bak
adb -d pull /system/app/ApplicationsProvider.apk ApplicationsProvider.apk.bak
adb -d pull /system/app/ApplicationsProvider.odex ApplicationsProvider.odex.bak
adb -d pull /system/app/TouchWizCalendar.apk TouchWizCalendar.apk.bak
adb -d pull /system/app/TouchWizCalendar.odex TouchWizCalendar.odex.bak
adb -d remount
adb -d push Email.apk /system/app/
adb -d shell chmod 644 /system/app/Email.apk
adb -d shell rm /system/app/Email.odex
adb -d push ApplicationsProvider.apk /system/app/
adb -d shell chmod 644 /system/app/ApplicationsProvider.odex
adb -d shell rm /system/app/ApplicationsProvider.odex
adb -d push TouchWizCalendar.apk /system/app/
adb -d shell chmod 644 /system/app/TouchWizCalendar.apk
adb -d shell rm /system/app/TouchWizCalendar.odex
adb -d remount
6. Clear E-mail and Calendar cache's from Manage Applications
7. Reboot your device (for instance with adb -d reboot)
Then, when you are finished copying the files, you need to resynchronize your Calendar and Mail:
1. Enable all internet access again
2. Start Calendar (is still empty!)
3. Start Email and finish wizard
Last but not least, here's some examples of how it can look like:
All done
Regards,
Nika.
nikagl said:
First of all: NO WARRANTY AT ALL. I have no idea what I'm doing... it simply worked what I did
Here's the steps:
1. Root your device
2. Install the Android SDK or ADB Tools
3. Take Email.apk and ApplicationsProvider.apk from for instance the Galaxy S Cyanogenmod (I used cm_galaxysmtd_full-181) and copy then to your adb folder
4. Run the following code using (USB debugging and root access are required for this!):
Code:
adb -d pull /system/app/Email.apk Email.apk.bak
adb -d pull /system/app/Email.odex Email.odex.bak
adb -d pull /system/app/ApplicationsProvider.apk ApplicationsProvider.apk.bak
adb -d pull /system/app/ApplicationsProvider.odex ApplicationsProvider.odex.bak
adb -d remount
adb -d push Email.apk /system/app/
adb -d shell chmod 644 /system/app/Email.apk
adb -d shell rm /system/app/Email.odex
adb -d push ApplicationsProvider.apk /system/app/
adb -d shell chmod 644 /system/app/ApplicationsProvider.odex
adb -d shell rm /system/app/ApplicationsProvider.odex
adb -d remount
5. Clear E-mail cache from Manage Applications
6. Reboot your device (for instance with adb -d reboot)
Start your mail and complete the wizard
Regards,
Nika.
Click to expand...
Click to collapse
Would love to see the CM Calendar in action
Lol, me too. Didn't work, can't get it to go whatever I try. Probably something to do with different naming of the Calendar as the Samsung calendar is called TouchWizCalendar.apk and the stock calendar is called Calender.apk. Tried whatever was suggested in older threads (remove TouchWizCalendar, InfoAlarm and CalendarProvider files and delete them from Applications after a reboot en then install Calendar.apk and CalendarProvider.apk) but it did not work
Still gotta try simply renaming Calendar.apk into TouchWizCalendar.apk and replace it, but first came accross a market Calendar replacement which seems good enough too:
Calendroid
Will post results whenever I do decide not to use Calendroid and try again to go back to the Stock Calendar.
By the way: the stock email client has possibility to correctly accept and go to meeting invitations... Much better than that horrible Samsung TW client
Regards,
Nika.
Tested it a minute ago, nope - renaming Calendar to TouchWizCalendar and repeating same procedure didn't work... Gotta stick with Calendroid I guess... Will add some pictures of mail in a moment!
Added some pics to the first post...
And here's some pictures of what happens when an invite is received and why I would love to get the stock calendar app... this is from Calendroid which is good enough for me, but it doesn't integrate 100% for instance from mail...
Regards,
Nika.
just copy the aosp calendar over deodexed rom,it works
sakindia123 said:
just copy the aosp calendar over deodexed rom,it works
Click to expand...
Click to collapse
I'll try deodexing the ROM and getting it from the AOSP build, but I tried to avoid that as I do not want the entire ROM to be deodexed.
As mentioned I tried copying calendar from the cm_galaxysmtd_full-181 build, but that did not work...
Regards,
Nika.
sakindia123 said:
just copy the aosp calendar over deodexed rom,it works
Click to expand...
Click to collapse
Sakindia,
I have tried it with my fully deodexed ROM, but still nothing.
1. First I deodexed the current ROM (using xUltimate-2.3.3)
2. I put all files from done_app and done_frame in /system/app and /system/framework
3. Removed all *.odex files from /system/app and /system/framework
4. Uploaded Calendar and CalendarProvider apk's using following script:
Code:
adb -d pull /system/app/Calendar.apk Calendar.apk.bak
adb -d pull /system/app/Calendar.odex Calendar.odex.bak
adb -d pull /system/app/CalendarProvider.apk CalendarProvider.apk.bak
adb -d pull /system/app/CalendarProvider.odex CalendarProvider.odex.bak
adb -d remount
adb -d push Calendar.apk /system/app/
adb -d shell chmod 644 /system/app/Calendar.apk
adb -d shell rm /system/app/Calendar.odex
adb -d push CalendarProvider.apk /system/app/
adb -d shell chmod 644 /system/app/CalendarProvider.apk
adb -d shell rm /system/app/CalendarProvider.odex
adb -d remount
adb -d reboot
But it still FC's
5. Tried renaming Calendar.apk into TouchWizCalendar.apk and uploaded that file...nope, still FC...
Any help appreciated
Regards,
Nika.
I use the Galaxy S build of Cyanogenmod btw (cm_galaxysmtd_full-181)... not sure whether that was the AOSP one you meant (I haven't spent much time yet compiling my own AOSP build)? If not, can you point me to the one you'd recommend?
i added to my rom without setting perms or anything..
try to simply copy with root exploere
sakindia123 said:
i added to my rom without setting perms or anything..
try to simply copy with root exploere
Click to expand...
Click to collapse
Just to make sure, what file did you copy? Only Calendar.apk or also CalendarProvider.apk?
nikagl said:
Just to make sure, what file did you copy? Only Calendar.apk or also CalendarProvider.apk?
Click to expand...
Click to collapse
just the calendar.apk(or calculator.apk)
i doubt calendarprovider would work bcoz of touchwiz dependencies!
cell4review said:
very goood and working
latest mobiles
Click to expand...
Click to collapse
spam!!!!!!!!!!!!
Agree, and judging from all the different posts in different threads:
http://forum.xda-developers.com/search.php?searchid=102046930
I will have him banned!
Regards,
Nika.
sakindia123 said:
just the calendar.apk(or calculator.apk)
i doubt calendarprovider would work bcoz of touchwiz dependencies!
Click to expand...
Click to collapse
Ok, so I now only renamed Calendar.apk to TouchWizCalendar.apk and copied it over, and now it works. I thought the CalendarProvider.apk had a dependency to Calendar.apk...
I updated my first post with some new pictures, changed the instructions and added the apk files too
nikagl said:
Ok, so I now only renamed Calendar.apk to TouchWizCalendar.apk and copied it over, and now it works. I thought the CalendarProvider.apk had a dependency to Calendar.apk...
I updated my first post with some new pictures, changed the instructions and added the apk files too
Click to expand...
Click to collapse
renaming isnt necessary though
good to hear u got it working!
sakindia123 said:
renaming isnt necessary though
good to hear u got it working!
Click to expand...
Click to collapse
For me it was, I really tried it without renaming. Calendar.apk does not exist, just added it to the system (copied with root explorer), rebooted and tried accessing "Agenda" which still opened the horrible TouchWizCalendar
Then I replaced TouchWizCalendar.apk with the renamed version of Calendar.apk and it worked
How else does the system know that the Agenda shortcut in the App Drawer should open the app from Calendar.apk instead of TouchWizCalendar.apk?
Regards,
Nika.
if u delete the touch wiz one
@nikagl
I just copied the files from the first post to \system\app using root explorer (after taking a backup ) rebooted and cleared the cache as you suggested and it works great, many thanks! I really disliked the TW Calender interface
Big Thanks: original [email protected] [http://classic.cx/android/dexo-universal-odex-tool/]
ADVANTAGES & DISADVANTANGES OF RE-ODEX
Advantages:
-All needed things are in one apk, so modding/theming is (better) possible
-Needs less space on /system
Disavantages:
-Needs more space on /data
-Is not so stable than a odexed rom
-Slower on first boot(because a odexed rom has already execute ready .odex files, a deodexed rom needs to generate dalvik cache)
===============================================
First step, please make a nandroid if you are unsure of what you are doing.
Second step, install busybox if it is not already installed. Either from the app or
from the binary I included (ie, adb shell busybox –install /system/xbin/)
Third step, push the four files zip, zipalign, dexo and dexopt-wrapper to /system/bin/
Fourth step, give the three files executable permissions (ie, chmod 755 zip zipalign dexo dexopt-wrapper)
Fifth step, run it!
Once the script is done, your phone will reboot. Your device will appear to be “frozen” until it reboots. That is ok.
Then all you will have to do is run:
adb pull /system/framework # JUST INCASE...YOU CAN SKIP THIS STEP.
adb pull /system/app # JUST INCASE...YOU CAN SKIP THIS STEP.
You are now done! The tool will automatically remove the classes.dex from your files as well as zipalign them. So you are optimized and ready to go.
Sample Terminal/Command prompt session. Basically you can copy and paste, ignoring the text after the # of course:
# Commands on Host computer
cd Downloads/universal-odex # change to the location you unzipped the odex tool.
adb remount
adb push dexo /system/bin/
adb push dexopt-wrapper /system/bin/
adb push zip /system/xbin/
adb push zipalign /system/xbin
adb push busybox /system/xbin # you may or may not already have busybox installed, but this will ensure that you have the correct applets installed
# Commands in ADB SHELL
adb shell # you just entered your Device’s shell
chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin/zip /system/xbin/zipalign /system/xbin/busybox
busybox –install /system/xbin # maybe fail in this step..but it seems okay,go to the next step anyway.
dexo # this will be the last command before your exit adb shell and your device reboots
# The “dexo” command executes SUPER fast. It should be done within 30s-1m, depending on ROM and device
# Commands on Host computer
cd Desktop
mkdir framework
mkdir app
adb pull /system/framework framework
adb pull /system/app app
# Rejoice.
If it doesn’t work for you, then you did something wrong. This is version 3.1 of the script and I’d like to think that I’ve fool-proofed it pretty well.
If you have any questions, comments, or suggestions, please post here.
Exclusive to theMikMik.
Tommy
enjoy the possibilities…
FILES_NEEDED:
View attachment re_odex_needed.tar.gz
Bro, you mean de-odex instead of re-odex??
Or even re-de-odex lol
Sent from my Nexus 7 using Tapatalk 2
kingCV said:
Bro, you mean de-odex instead of re-odex??
Click to expand...
Click to collapse
yesyes..