Related
I am willing to pay someone if someone can figure out how to remove factory apps like
facebook
footprints
peep
quickoffice
stock
visual vm
stock massages
i never use them for some reason they run in the background
Just take a look at this thread from the android forums
http://androidforums.com/all-things-root-eris/53646-unwanted-apps.html
NOTE: you MUST have ROOT in order to remove those apps.
If the instructions in that thread about "adb" are too complicated for you, then go buy the Root Explorer app, navigate to the folders you were told to in the thread, click the "r/w" button at the top of the app, then long press on the files you are told to delete.
Deleting system apps is risky if you delete the wrong ones. As usual, you are responsible if anything happens.
As I see it, you must have root to modify system files on your ROM (anyone correct me if I'm wrong)
But I was able to use Titanium Back up (downloaded from the Android market, free) to see all installed programs and I successfully deleted Visual VM, Peep, and stock messages... I use the others...
now so far, my ROM that is installed [2.1 version .3] hasn't had any problems with the removal of these system programs, So I think it is a safe method.
I believe this is a good alternative to adb commands... since you know what you are deleting.
and of course, I am not responsible if you do happen to mess your phone up.
C:\Users\admin\Desktop>cd android-sdk-windows
C:\Users\admin\Desktop\android-sdk-windows>cd tools
C:\Users\admin\Desktop\android-sdk-windows\tools>adb shell
$ mount -0 rw,remoun /dev/block/mtdblock3 /system
mount -0 rw,remoun /dev/block/mtdblock3 /system
mount: invalid option -- '0'
BusyBox v1.15.0 (2009-08-25 15:17:43 BST) multi-call binary
Usage: mount [flags] DEVICE NODE [-o OPT,OPT]
Mount a filesystem. Filesystem autodetection requires /proc be mounted.
Options:
-a Mount all filesystems in fstab
-f Dry run
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification ti
me
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a directory to an additional location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing its flags
ro/rw Read-only/read-write mount
There are EVEN MORE flags that are specific to each filesystem
You'll have to see the written documentation for those filesystems
$ cd /system/app
cd /system/app
$ 1s
1s
1s: permission denied
$
this is what i get am i doing something wrong here
Type adb shell than su and tell me what happens.
binny1007 said:
Type adb shell than su and tell me what happens.[/QUOTE
never mind i got it to work i used different method i bought the titanium backup. show all the installed apps easy to uninstall it works great now my phone is running much faster thanks for all the help
Click to expand...
Click to collapse
FYI, you were typing the commands wrong.
Right after you do "adb shell" you'll need to type "su" and the $ prompt should change to a # prompt. Check your phone as well after typing "su" as you should see a popup asking for permission.
$ mount -0 rw,remoun /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
should be: mount -o rw,remoun /dev/block/mtdblock3 /system
The -o is the letter o, not a zero.
$ 1s
Click to expand...
Click to collapse
Should be: ls
That's the letter l (lowercase L), not a one.
grdlock, I believe there is a "t" missing in your post:
mount -o rw,remount /dev/block/mtdblock3 /system
Ahh, ya, you're right. I just copied/pasted what he wrote and didn't catch that.
ampinc said:
binny1007 said:
Type adb shell than su and tell me what happens.[/QUOTE
never mind i got it to work i used different method i bought the titanium backup. show all the installed apps easy to uninstall it works great now my phone is running much faster thanks for all the help
Click to expand...
Click to collapse
Glad to know it works for someone else as well
Click to expand...
Click to collapse
I just downloaded Titanium Backup and deleted the "worldclock.apk" and I have to say it's a nice app, (Titanium that is)
So far, from the VanillaDroid ROM, I've deleted the following with no ill effects:
Stocks
Weather ( I use WBug)
Visual Voicemail
Browser ( I use Dolphin)
Quickoffice
MMS
Talk
Mail
Deskclock
I would like to delete the following but am having some difficulty finding the correct "apk"
Camcorder (I think it's built into the camera?)
Call History
People Search
Settings (just the app in the drawer, another NAND before I do this I guess)
Voice Dialer
Voice Search
Voice Record
NaviPanel ***Anyone know if this will mess with Maps?***
FACEBOOK !!!! I deleted the "Facebook.apk" but the FB app is still in the drawer and it still works fine. If anyone could help me with deleting this one I would be forever greatful! Trying to delete it using Titanium, it says: "cannot find Facebook.apk" But it's still friggin there......argh!
Edit: Woohoo! Facebook is gone.
Titanium tells me it needs root acess and that's out of question. Then again, I'm on the lg ally and it might be different... idk. Any other suggestions?
Can Galaxy S users backup their bootup animations for me? I want to get rid of as much of the AT&T crap as possible.
They are as follows
Startup
/system/etc/PowerOn.wav
/system/media/bootsamsung.qmg
/system/media/bootsamsungloop.qmg
Thanks
here you go...
View attachment gt-i9000.zip
from GT-I9000;2.1-u1;JF3;2.6.29;ECLAIR
sorry for the delay, was testing other apps..
enjoy brother
Thanks! Going to try them out now
Just wanted to add that they work fine, now just to figure out how to flash a different boot image to get rid of the AT&T World Phone logo.
Why dont you flash with the GT-I9000 rom and say goodbye to At&t everything?
Sent from my GT-I9000 using XDA App
Didn't they free the brothers back in January 1865?
Hi,
How did you get these into the right folders?
What commands did you use?
Tried root explorer and su file manager and they won't paste ther files into system/etc or system/media.
adb gives a no access and can't use adb remount to push file.
So I am stuck.
Thanks
decepticon said:
Just wanted to add that they work fine, now just to figure out how to flash a different boot image to get rid of the AT&T World Phone logo.
Click to expand...
Click to collapse
KJPDX said:
Why dont you flash with the GT-I9000 rom and say goodbye to At&t everything?p
Click to expand...
Click to collapse
hm.i guess that would not be a good idea as they are not 100% the same. replacing the custom stuff is the easy and secure solution for the time being.
bestwebs said:
Hi,
How did you get these into the right folders?
What commands did you use?
Tried root explorer and su file manager and they won't paste ther files into system/etc or system/media.
adb gives a no access and can't use adb remount to push file.
So I am stuck.
Thanks
Click to expand...
Click to collapse
I used Root Explorer and copied them. You would have to mount the /system folder with RW permissions in ADB or just click the Mount RW button in Root Explorer before copying them over.
jodue said:
hm.i guess that would not be a good idea as they are not 100% the same. replacing the custom stuff is the easy and secure solution for the time being.
Click to expand...
Click to collapse
This is the reason why, the generic Galaxy S FW does not work with the Captivate.
Hi,
For some reason root explorer wouldn't paste these.
But I did figure out a way with adb.
I copied all 3 files to my sdcard 1st
These are the commands I used in case they are of help to anyone:
D:\>adb shell
$ su
su
# mount -o rw,remount -t rfs /dev/block/stl9
mount -o rw,remount -t rfs /dev/block/stl9 /s
# busybox cp /sdcard/PowerOn.wav /system/etc
busybox cp /sdcard/PowerOn.wav /system/etc
and
D:\>adb shell
$ su
su
# mount -o rw,remount -t rfs /dev/block/stl9 /system
mount -o rw,remount -t rfs /dev/block/stl9 /system
# busybox cp /sdcard/bootsamsungloop.qmg /system/med
busybox cp /sdcard/bootsamsungloop.qmg /system/media
# busybox cp /sdcard/bootsamsung.qmg /system/media
busybox cp /sdcard/bootsamsung.qmg /system/media
Thanks
decepticon said:
I used Root Explorer and copied them. You would have to mount the /system folder with RW permissions in ADB or just click the Mount RW button in Root Explorer before copying them over.
This is the reason why, the generic Galaxy S FW does not work with the Captivate.
Click to expand...
Click to collapse
emclondon said:
here you go...
View attachment 368161
from GT-I9000;2.1-u1;JF3;2.6.29;ECLAIR
sorry for the delay, was testing other apps..
enjoy brother
Click to expand...
Click to collapse
Thanks for posting this, exactly what I was looking for!
NOTE: This method has been somewhat superseded by JustAnotherCrowd's method in this thread:
http://forum.xda-developers.com/showthread.php?t=744655
It should still work, however, if you don't want to mess with Odin, but if you want to use ext4 and get the max speed AND stability, I recommend using JACs method.
There are two zip files attached. Consider them "Beginner" and "Advanced". You can only use one or the other, not both. No wipe is required for either, but you will want to clean and repair your ext partition if you plan on using one.
Beginner: If you have an SD card with an ext partition on it (no swap partition, just FAT/ext), ttabal has created a fantastic script to mount it on startup. This zip file runs that script at startup. Credit to ttabbal for the script.
IMPORTANT: You will need to install the latest version of busybox before installing this update or it will not work. You can find busybox on the market for free; download and install it and then open it and click "update busybox".
http://getyourboneon.com/vibranta2sd.zip
Advanced: Enables you to place a custom userinit.sh script in /data/local (make sure premissions are set to 755) and it will run on startup.
http://getyourboneon.com/enableuserinit.zip
An explanation of how this was done:
When looking through the init.rc, I realized that there was only one thing running as root that could safely be replaced; the boot logo player. So, all this does is replace the boot logo player with a script that calls userinit.sh from /data/local and then calls the (now renamed) bootlogo player for those of you who want that nifty startup screen
A super simple (and slightly dirty) hack but I figured it might come in handy for those of us who are impatient and would like to do our own tweaks.
Nice....
I'll be looking forward to this.
Edit:
Working great.
??
Can some one elaborate on what this does?:
BM1515 said:
Can some one elaborate on what this does?:
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=Userinit.sh
anomalous3 said:
I found a way to get a userinit.sh script working for the vibrant for those of us who would like to run anything at startup. Already got the proof of concept working, and am now busy packaging it into an easy script that will set everything up for you. Will update this post later tonight with the finalized script once it's done.
Click to expand...
Click to collapse
Nice work. What can you do on bootup on the vibrant? I havent looked at all the kernel settings.
oh, just stuff like mounting an ext partition or initializing the modules for the FM radio (assuming we can find them and the hardware's there).
anomalous3 said:
oh, just stuff like mounting an ext partition or initializing the modules for the FM radio (assuming we can find them and the hardware's there).
Click to expand...
Click to collapse
Yes the userinit can contain quite a few script functions and technically almost all of them that would be needed on a modifed rom.
E.G
Code:
insmod /system/lib/compcache/ramzswap.ko;
rzscontrol /dev/block/ramzswap0 -i -d 32768;
busybox swapon /dev/block/ramzswap0;
echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo 0 > /proc/sys/vm/page-cluster;
# Set "deadline" scheduler fifo batch to 1 for mtdblocks and mmc
for i in `ls -1 /sys/block/mtdblock*` /sys/block/mmcblk0
do
echo 1 > $i/queue/iosched/fifo_batch
done
busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sdcard/sd;
if [ "$?" = 0 ];
then
busybox chown 1000:1000 /system/sd;
busybox chmod 771 /system/sd;
# clean up any old symlinks, create data directories
for i in dalvik-cache data;
do
if [ -h /data/$i ];
then
rm /data/$i;
fi;
if [ ! -d /data/$i ];
then
mkdir /data/$i;
busybox chown 1000:1000 /data/$i;
busybox chmod 771 /data/$i;
fi;
done;
Updated. And to mount an ext partition you'd want to mount /dev/block/mmcblk1p2.
Got my ext mounted but haven't yet figured out how to get app data over to the external sd card without tons of force closes (I'm probably setting the permissions wrong).
anomalous3 said:
Updated. And to mount an ext partition you'd want to mount /dev/block/mmcblk1p2.
Got my ext mounted but haven't yet figured out how to get app data over to the external sd card without tons of force closes (I'm probably setting the permissions wrong).
Click to expand...
Click to collapse
Those were some examples not specifically for the Vibrant.
justanothercrowd said:
Those were some examples not specifically for the Vibrant.
Click to expand...
Click to collapse
I know I could tell by the echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
I was just sayin' though in case anyone was interested in making this work....too tired to mess with it anymore tonight.
anomalous3 said:
Updated. And to mount an ext partition you'd want to mount /dev/block/mmcblk1p2.
Got my ext mounted but haven't yet figured out how to get app data over to the external sd card without tons of force closes (I'm probably setting the permissions wrong).
Click to expand...
Click to collapse
I've been trying to get the ext partition to mount, but I keep getting errors from mount. This is just with "adb shell". I did "su", and have root. What command are you using? Does it only work from the userinit?
# mount /dev/block/mmcblk1p2 /system/sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -t auto /dev/block/mmcblk1p2 /system/sd
mount: No such device
# ls /dev/block/mmcblk1p2
/dev/block/mmcblk1p2
The device and mount directory do exist, so I'm a bit lost. I'll give it a go with the userinit hack and see if that gets things running.
EDIT: Nevermind, I forgot to do "busybox mount". grrrrr.. that works now.
EDIT2: Ummm... it mounts as a j4fs with a bunch of crap I've never seen on there. WTF?!? I didn't even know that filesystem existed.
maybe try
Code:
busybox mount -t ext3 /dev/block/mmcblk1p1 /system/sd
? I got it to mount and recognize the ext partition, my trouble was getting the data over to it. maybe a symlink isn't the best way to do it and I could try a bind mount.....
OK. I got it working, had to use mkfs.ext2 to re-format the ext partition. I have no idea what put that other crap there, but it wasn't me and formatting doesn't seem to have bothered anything.
Here's a rough draft of my userinit.sh. I have booted with it, and it seems to work fine. No warranty, obviously. It bind mounts /data/data to a directory on the ext partition, copying files if needed. It might do with some more cleanup and safety checking, but seems to work OK for me.
Speed wise, it seems to work pretty good.
Oh, you need to create the /system/sd directory yourself. I didn't add that in the script. remount rw and "mkdir /system/sd". A root file manager should be able to handle that as well, or add it to the script.
I've never had lag on my Vibrant so the lag fixes have always confused me a bit. Screwing with the phone is what its all about though.
well I'll be damned. It works. I wonder if we'll see an improvement from moving the dalvik-cache over too, seeing as how those are the actual executables for the applications.
[edit] It seems to have killed my mobile data connection.[/edit]
anomalous3 said:
well I'll be damned. It works. I wonder if we'll see an improvement from moving the dalvik-cache over too, seeing as how those are the actual executables for the applications.
Click to expand...
Click to collapse
Possibly. I haven't tried that yet. Maybe I'll toss it on and see. I did another version that moves the mount to /sd-ext like CM5. I'll add that in here, it automated, no need to make the mount point yourself. It feels a little more "standard" to have it there.
OK. For grins, I moved dalvik-cache as well. Here's the update, same mechanism. It feels like it might be a little faster, I'm not sure. I'll let everyone have a try at it and see what you think.
it works and data works too! Also seems noticeably quicker!
With your permission, I'd like to package this into an update.zip along with the userinit enabler (once you feel it's ready) so we can have a reliable way to get apps2sd working.
so with this userinit.sh we can apply the mimocan fix, not that i have noticed a hell lot of stalling but there is somewhat stalling after a while. only to make a great phone even better.
anomalous3 said:
it works and data works too! Also seems noticeably quicker!
With your permission, I'd like to package this into an update.zip along with the userinit enabler (once you feel it's ready) so we can have a reliable way to get apps2sd working.
Click to expand...
Click to collapse
just one question... why would we need a2sd? i remember when i had my mt3g and whenever i ran any sense rom or regular rom that a2sd slows it down significantly but when i stored everything on the phone it was way smoother and its not like we dont have the space..
I have busybox 1.6 on my captivate i see on www.busybox.net 1.17.3 is out. I have downloaded it from the site and its a tar file with a folder with a whole bunch of folders and files. How do you install this?
Are you familiar with the phrase, "if it isn't broken, don't fix it?"
I advise you to heed its warning.
But if you must proceed, a quick google search for "how to install busybox manually" brings up this very good result: http://www.droidforums.net/forum/droid-2-hacks/82573-busybox-manual-install-how-guide.html
Edit: By the way, love the avatar. Great album.
Yes i understand if its not broke don't try to fix it but i'm a OCD updater! Would there be any advantages of updating it? P.S. I saw Megadeth and Slayer a month ago they rocked!
Only advantages I can see are having a couple more bug fixes and maybe 4-5 new commands built in.
Download Busybox-1.17.2 HERE
Extract busybox to your SD Card
Make sure you are in PC Mode and Debugging is enabled in Applications options
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/busybox /system/xbin/
cd system/xbin
busybox --install /system/xbin/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
You can also use Root Explorer or whatever file browser you may use to copy busybox to your system/xbin folder. Some people use system/bin but I prefer xbin...just a habbit.
Click to expand...
Click to collapse
Ya, I read that and got really scared.
What is PC mode and where do you type these commands? (Vista user)
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Cruton502 said:
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
miztaken1312 said:
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
Click to expand...
Click to collapse
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Cruton502 said:
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Click to expand...
Click to collapse
I think you're seriously confused. The Captivate isn't a NAND locked phone. Generally when you root, busybox is installed. (I think. At least it always was for me.) You could also try installing Titanium Backup and have that install busybox for you.
Here are the App and Framework system files for 4.1.57 fully deodexed.
You must already have Root access in 4.1.57.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Remember to make a backup of your existing framework and app folders BEFORE you do this.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Again, backup your original system/framework and system/app files BEFORE you do this in case you want to revert back to an odexed system.
Here is the correction:
Put your phone in USB Mass Storage Device mode.
Copy the app and framework directory and their contents from the zip file to the root of your sdcard.
***Verify the copy was successful before you continue.***
Set USB mode back to None.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /dev/block/mmcblk0p12 /system
reboot
Thanks, you beat me to it!
lindsaytheflint said:
Thanks, you beat me to it!
Click to expand...
Click to collapse
I deodexed them last night, but wanted to run through some testing before I packaged them up.
Anyone feel like scripting this, go for it.
I must have done something wrong in shell... soft brick, certain it was my fault.
tl_bull said:
I must have done something wrong in shell... soft brick, certain it was my fault.
Click to expand...
Click to collapse
Not your fault... I found an error in my instructions.
cp /sdcard/frame/* /system/framework/
should be
cp /sdcard/framework/* /system/framework/
rjohnstone said:
Here are the App and Framework system files for 4.1.57 fully deodexed.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
Been running all day with these files with no issues.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Here is the correction.
Copy the app and framework directory to the root of your sdcard.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system
lpsi2000 said:
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Thx. Updated OP.
The mount commands I originally posted did work for me without any issue though.
Sent from my MB860 using XDA App
It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.
Ririal said:
It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.
Click to expand...
Click to collapse
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App
I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Edit:
Had to use usb port on the rear instead of the front when rooting.
zeyoner said:
I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Click to expand...
Click to collapse
Sounds like you don't have root access.
Do you see a $ or a # in your command prompt?
i have $ in my root access... i'm getting permission denied at when i type 'su' but im pretty sure i rooted it earlier today
edit fixed i wasnt rooted
rjohnstone said:
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah I looked it over again, should be fine.
EDIT: Nvm saw you updated.
I'm working on a new method to automate this, I'll post something when I have it working reliably.
looking for another way
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?
Very nice contribution!
Rad ryan said:
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?
Click to expand...
Click to collapse
This won't work without having root access first.
Sent from my MB860 using XDA App
I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.
Immix said:
I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.
Click to expand...
Click to collapse
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.
shawnbuck said:
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.
Click to expand...
Click to collapse
Thx for the tip.
I did use the stop command in my process and was able to prevent a reboot.
The process is so quick that I didn't see a single FC during the copy.
I think it should be mentioned in the OP that root is required.