Database Info

Android Permision - Porting Of Rosie To Emulator Etc

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

adb how to use notepad, please help

Hey Guys, I am totaly new to android(adb), but yet fascinated...I recently downloaded all the files needed for adb, got it working, but I've found that I'm not sure how to use commands...For most, this question may seem very simplistic, but for me, it's not so simple...lol Here is my dilema
adb remount
adb shell rm /system/app/*.odex
adb pull /system/bin/user.conf c:\user.conf
Used Notepad++ to edit and
adb push c:\user.conf /system/bin/user.conf
adb shell chmod 755 /system/bin/user.conf
adb shell reboot
##Optional##
after you get everything setup the way you want it do a backup... I found switchrom.sh to be more dependable than purely nandroid backup.
reboot in recovery
adb shell
/#mount /system/sd
/#sh /system/sd/switchrom.sh -s <name>
To restore it...
reboot in recovery
adb shell
/#mount /system/sd/
/#sh /system/sd/switchrom.sh -r
##select the rom you want to restore##
What is Notepad and how do I use it, is it in adb ?
This is for ZeroXd 6.10 ROM
Thanx in advance for all of those who took time to help a real N00B
G1 Black
MT3G Merlot
Rooted

[9001][MOD] Replace stock Samsung TW email/calendar + CarHome/DeskClock [2011-12-21]

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

[HOW TO] re-odex your ROM by yourself...

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..

problem with camera apps

In my z5 in camera 2.0 installed so in apps stopped working but when launch camera apps from app drawer works fine
Also tried to remove update but without update camera (stock apk) shows fc
I have rooted z5 dual

If you rooted, your DRM keys are gone (from unlocking bootloader). Someone reported their camera working after this hack to trick DRM keys being there:
http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Not sure it'll fix your issue, but worth a try since you are already rooted. All else fails, factory reset.

rajdeep312 said:
In my z5 in camera 2.0 installed so in apps stopped working but when launch camera apps from app drawer works fine
Also tried to remove update but without update camera (stock apk) shows fc
I have rooted z5 dual
Click to expand...
Click to collapse
Try push deodexed Camera.apk
by ADB (download attachment and copy it to folder where ADB is :
Code:
adb push CameraCommon.apk /data/local/tmp
adb shell
su
busybox mount -o remount,rw /system
dd if=/data/local/tmp/CameraCommon.apk of=/system/priv-app/CameraCommon/CameraCommon.apk
chmod 644 /system/priv-app/CameraCommon/CameraCommon.apk
rm -rf /system/priv-app/CameraCommon/arm
rm -rf /system/priv-app/CameraCommon/arm64
RootExplorer or any other file manager :
Download CameraCommon.apk, copy-paste it to /system/priv-app/CameraCommon/CameraCommon.apk, change chmod to 644 (read write, read, read) and delete arm and arm64 folder.

Thanks you saved my z5

Siudzix said:
Try push deodexed Camera.apk
by ADB (download attachment and copy it to folder where ADB is :
Code:
adb push CameraCommon.apk /data/local/tmp
adb shell
su
busybox mount -o remount,rw /system
dd if=/data/local/tmp/CameraCommon.apk of=/system/priv-app/CameraCommon/CameraCommon.apk
chmod 644 /system/priv-app/CameraCommon/CameraCommon.apk
rm -rf /system/priv-app/CameraCommon/arm
rm -rf /system/priv-app/CameraCommon/arm64
RootExplorer or any other file manager :
Download CameraCommon.apk, copy-paste it to /system/priv-app/CameraCommon/CameraCommon.apk, change chmod to 644 (read write, read, read) and delete arm and arm64 folder.
Click to expand...
Click to collapse
I also have an issue with my Camera, if I open Camera Apps, for example Style Portrait, AR Mask, Sticker creator, Creative effect, they all force-close.
Will pushing the deodexed Camera.apk also fix my issue? And am I still able to update after pushing this update?
Thanks!

Meneer_A said:
I also have an issue with my Camera, if I open Camera Apps, for example Style Portrait, AR Mask, Sticker creator, Creative effect, they all force-close.
Will pushing the deodexed Camera.apk also fix my issue? And am I still able to update after pushing this update?
Thanks!
Click to expand...
Click to collapse
Yes deodex solve your problem

Siudzix said:
Try push deodexed Camera.apk
by ADB (download attachment and copy it to folder where ADB is :
Code:
adb push CameraCommon.apk /data/local/tmp
adb shell
su
busybox mount -o remount,rw /system
dd if=/data/local/tmp/CameraCommon.apk of=/system/priv-app/CameraCommon/CameraCommon.apk
chmod 644 /system/priv-app/CameraCommon/CameraCommon.apk
rm -rf /system/priv-app/CameraCommon/arm
rm -rf /system/priv-app/CameraCommon/arm64
RootExplorer or any other file manager :
Download CameraCommon.apk, copy-paste it to /system/priv-app/CameraCommon/CameraCommon.apk, change chmod to 644 (read write, read, read) and delete arm and arm64 folder.
Click to expand...
Click to collapse
Thank you for this, it really helped me a lot. now I could get camera and plug-ins run again after root. you just bring lots of fun back.:good: