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
For those of you who want to use Quickboot
OR
Have ROM Manager from market and want to "Reboot into recovery" directly, do this
Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
And of course, this can't be done in Android system. You would have to boot to toast's recovery.
Also, i didn't know the command to push from shell, therefore the redundant adb shell. =)
so this takes out the HBoot? and goes straight to Recovery Rom?
unfortunately no,
but it lets you skip the step "Vol up+power" and go straight to stock recovery.
From there you can use the "fake-flash"
awesome...Thanks for sharing, i will try this
I would recommend "rm /system/bin/reboot" before pushing the new one.
Great job! Works like a charm!
I guess TheBiles and I were posting in the wrong sub-forum?
http://forum.xda-developers.com/showthread.php?t=695978
wcasdf said:
For those of you who want to use Quickboot
OR
Have ROM Manager from market and want to "Reboot into recovery" directly, do this
Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
And of course, this can't be done in Android system. You would have to boot to toast's recovery.
Also, i didn't know the command to push from shell, therefore the redundant adb shell. =)
Click to expand...
Click to collapse
C:\Documents and Settings\Owner>adb shell
# mount /dev/block/mtdblock4 /system
mount /dev/block/mtdblock4 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# exit
what am i doing wrong??
worked great, we are only one step away now
Help......
Hi Sorry to bother..
Have started the process got to push the file to the system bin. However when then attempting the next command adb shell, i recieve the following error:-
- exec '/system/bin/sh' failed: Not a directory (20) -
Any advice????
Cheers
Andy
.....Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
wcasdf this will also useful for desire user, i have pushed reboot into /system/bin but didnt sames to work
desire /system is /dev/block/mtdblock3, this is the problem?
Sorted....
Kali- said:
wcasdf this will also useful for desire user, i have pushed reboot into /system/bin but didnt sames to work
desire /system is /dev/block/mtdblock3, this is the problem?
Click to expand...
Click to collapse
Absolutely right Kali........the mtdblock3 resolved the issue.....now able to enter recovery mode and also back up rom.....
Brilliant....many thanks......
watzone69 said:
I guess TheBiles and I were posting in the wrong sub-forum?
http://forum.xda-developers.com/showthread.php?t=695978
Click to expand...
Click to collapse
I was just afraid the thread would get moved with these super-strict mods in this board.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Worked great. Now the reboot commands in ROM Manager and Quick Boot work.
tells me reboot file is not there its in the androidsdk\tools folder
Sporkman said:
tells me reboot file is not there its in the androidsdk\tools folder
Click to expand...
Click to collapse
adb push is pretty versatile, you can give it absolute paths. if you downloaded the reboot file to a different directory, example:
adb push c:\downloads\reboot /system/bin/reboot
hope that helps!
OP: where did this reboot binary come from?
im running PC36IMG.zip and reboot recovery and reboot bootloader both work in normal android mode ...
joeykrim said:
adb push is pretty versatile, you can give it absolute paths. if you downloaded the reboot file to a different directory, example:
adb push c:\downloads\reboot /system/bin/reboot
hope that helps!
OP: where did this reboot binary come from?
im running PC36IMG.zip and reboot recovery and reboot bootloader both work in normal android mode ...
Click to expand...
Click to collapse
i dropped the file in C:\androidsdk\tools WHERE it needs to be
trying to figure this for my desire i understand block needs to be 3 and the rest the same but
keep getting device or resource busy when trying the mount command?
fixed it..you need to be in recovery before doing the above-otherwise you get a resource busy message
dont forget to change to block3 not 4 if using desire- rom manger now works as it should !! thanks
joeykrim said:
...OP: where did this reboot binary come from?
Click to expand...
Click to collapse
I'm not the OP but I originally got mine from the Hero sub-forum:
http://forum.xda-developers.com/showpost.php?p=5356050&postcount=623
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
I have made a few changes in the SystemUI.apk file and framework-res.apk using apk multi tool. After compiling it and trying to push the apk it shows an error saying Remount fail :Operation not permitted. The log says system cannot find the file specified. I tried making a flashable file but it just would not work. I really want to start off theming, please guide me as I have searched for one full day now, but nothing worked.
preshit10 said:
I have made a few changes in the SystemUI.apk file and framework-res.apk using apk multi tool. After compiling it and trying to push the apk it shows an error saying Remount fail :Operation not permitted. The log says system cannot find the file specified. I tried making a flashable file but it just would not work. I really want to start off theming, please guide me as I have searched for one full day now, but nothing worked.
Click to expand...
Click to collapse
I'm not an expert on adb, but is your phone's usb debugging on? Do you have su, and have you mounted rw? Also, is the file in the same folder as your adb folder?
Sent from my GT-I9003 using xda app-developers app
bscraze said:
I'm not an expert on adb, but is your phone's usb debugging on? Do you have su, and have you mounted rw? Also, is the file in the same folder as your adb folder?
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Just enabled root access to adb but still no luck. I am also facing this problem http://forum.xda-developers.com/showthread.php?t=1765379
Procedure
Make sure that SystemUI and framework-res are in the same folder as ADB and in the \tools folder. For example mine is:
C:\AndroidSDK\tools
So I would place SystemUI and framework-res in that directory.
After starting CMD in windows (assuming you are on windows) type these commands in this order:
adb remount
adb push SystemUI.apk /system/app/
adb push framework-res.apk /system/framework/
adb shell
su
cd /system/app
chown 0.0 SystemUI.apk
chmod 0644 SystemUI.apk
cd /system/framework
chown 0.0 framework-res.apk
chmod 0644 framework-res.apk
reboot
Explanation: first line remount system as read-write. 2 & 3 pushes the files. 4-7 sets proper permissions for the files. 8 reboots your phone.
P.S. If you EVER decompile framework-res.apk, open it in 7-zip and copy AndroidManifest.xml from the OLD PRE-MODDED framework-res.apk (using 7-zip) into your NEW framework-res.apk to prevent BootLoops. Apktools isn't really configured that well for our phone so it doesn't copy AndroidManifest.xml and you have to do it manually.
Deodexed files for build 15.3.A.1.14 from here
1. Copy app and framework folder to root of internal sd
2. Place adb tools somewhere on your windows PC
3. Turn on USB Debugging on and stay awake under developers options (If you didnt didn't get the developer options press build number 7 times)
4. Connect your phone to PC and make sure drivers are installed
5. Run the bat "Copy_Deodexed_and_Reboot.bat" under adb tools
6. The phone will reboot and if all worked fine, you will see "Android is Upgrading" on next boot as it creates Dalvik Cache
Enjoy !
Note: Those who are facing unexpected system reboots during deodexing process please first install remountrebootfix by [NUT]. You can download it from here.
Thanks to serajr for bat file
Great bro... :good:
I think this script will help! It worked here with no "remont fix" by [NUT] !!!
Code:
adb devices
adb shell "su -c 'stop'"
adb shell "su -c 'mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system'"
adb shell "su -c 'chmod 777 /system/app'"
adb shell "su -c 'chmod 777 /system/framework'"
adb shell "su -c 'cp /sdcard/app/* /system/app/'"
adb shell "su -c 'rm /system/app/*.odex'"
adb shell "su -c 'cp /sdcard/framework/* /system/framework/'"
adb shell "su -c 'rm /system/framework/*.odex'"
adb shell "su -c 'mount -o ro,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system'"
adb reboot
.
.
don't need remountfix but do need to be rooted.
i cant download dedexed files, it says "there's an error during download"
Download this LINK
I have edit some batch with your deodex folder....app and framework..
Just Extract to Computer then connect your devices with enable USB DEBUGGING.
Then Open Menu.bat, choose number 2 for deodex...
wait untill all file have push to system, then enter any key to reboot..
BTW great job:good:
Levered said:
Download this LINK
I have edit some batch with your deodex folder....app and framework..
Just Extract to Computer then connect your devices with enable USB DEBUGGING.
Then Open Menu.bat, choose number 2 for deodex...
wait untill all file have push to system, then enter any key to reboot..
BTW great job:good:
Click to expand...
Click to collapse
Does not work for me says push completed at the end but my files still have .odex changed nothing i have root access and latest busybox also developer options> USB dedugging on help
Taher.apk said:
Does not work for me says push completed at the end but my files still have .odex changed nothing i have root access and latest busybox also developer options> USB dedugging on help
Click to expand...
Click to collapse
does you enable unknown sources?
Levered said:
does you enable unknown sources?
Click to expand...
Click to collapse
Yes i do
Levered said:
does you enable unknown sources?
Click to expand...
Click to collapse
i did it via root explorer any way thank you very much for the deodex
How did You replace files using root explorer , i have problem with busybox (system halt on remount system) with system ver.15.3.A.0.26 ?
Levered said:
Download this LINK
I have edit some batch with your deodex folder....app and framework..
Just Extract to Computer then connect your devices with enable USB DEBUGGING.
Then Open Menu.bat, choose number 2 for deodex...
wait untill all file have push to system, then enter any key to reboot..
BTW great job:good:
Click to expand...
Click to collapse
I've enabled USB Debugging an Unknown Sources, the batch pushes everything and when it's time to copy to system, i'm getting error: device not found... and my L reboots...
I don't have installed remountrebootfix, because i think it's not necessary; i've mounted r/w with root explorer and my device didn't reboot... even i deleted a lot of bloatware before
still got odex files.. i'm trying to delete it manually using rootex but when i'm trying to restart it i've got bootloop :crying:
me too still odex files help please!!!!!!!
Its work!i dont have odex files..:good:
Hipom said:
Its work!i dont have odex files..:good:
Click to expand...
Click to collapse
How did you make it work? Have you used remount reboot fix?
Escrito desde mi Xperia L y weá
EDIT: Worked like a charm... Steps i did:
1. Root by the VRoot method, the installed SuperSU
2. Installed RemountRebootFix
3. Used the batch file by Levered
No odex files remaining!
Thanks all!
I just use deodex JB.zip extract zip and run the bat..odex files gone..
Sent from my C2105 using xda app-developers app
Deodexing working fine!
just download the deodexed files link mentioned in first post
then copy the app and framework folder to the deodexer tool which we had used for .17 firmware.
next execute the batch file and follow onscreen instructions!
your'e done!
Deodex build 15.3.A.1.12
Download files from here
Extract somewhere
Copy "app" and "framework" folder to root of your internal sd card
Make sure that USB Debugging is on
Run the batch under "adb tools" folder
Thanks to serajr for bach file
After i use this deodexed files my XperiaHome not working The latest XperiaHome 6.1.T.0.6 not working but version 6.1.A.0.5 working well )
[r[/QUOTE] Heh, You think giving us complicated code without instruction will deodexed the new firmware with just one touch ? huh,,i know you're A PRO (whoa tat crazy pro fuyoo giler ar sheram nih ,,) but PLEASE TEACH THE NOOBS STEP BY STEP .. Please give us a simple step for putting the code through Command prompt(it should run as admin etc) bla2,,man you take this really easy..this really dissapointed me,,