I currently have RC33 w/ apps on SD card. If I installed a theme or converted to the RC33 Lite version, will that corrupt my phone?
creid2352 said:
I currently have RC33 w/ apps on SD card. If I installed a theme or converted to the RC33 Lite version, will that corrupt my phone?
Click to expand...
Click to collapse
RC33 Lite i believe will delete your link to the SD .. to accomplish the Lite version simply delete the media files on from the phone .. as for the themes .. you're on your own .. there are plenty of themes people have used that cause no problems .. but you may come across one that doesn't work properly
*Note: lite versions are only required if you're going to use a theme, on JF RC33 V1.41 and up
JFvMOD by LucidREM
-Seems to be the most popular version right now.
-Same as JF RC33 V1.42 except for a few added files to make APPS to SD really easy for everyone.
-Themes will not work on this unless you manually make it a "lite" version following the steps below
JF RC33 V1.42
-This version really only introduced a bug fix so Android Debug Bridge (adb) would work in recovery mode.
*A wipe shouldn't be necessary when updating to this version.*
* JF RC33 V1.42 (lite)
Same as the JF RC33 v1.41 (lite) version but has the bug fix of rc1.42
you can manually make your own lite version of the firmware by typing these commands
in the terminal emulator.
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp -rf /system/media /sdcard
rm -rf /system/media
shouldn't it be
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp -a /system/media /sdcard
rm -rf /system/media
ln -s /sdcard/media /system/media
Nitro212 said:
shouldn't it be
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp -a /system/media /sdcard
rm -rf /system/media
ln -s /sdcard/media /system/media
Click to expand...
Click to collapse
no need for the "ln -s" because the phone recognizes media on the /sdcard .. also the "cp -a" is not needed as the FAT32 does not recognize any permission settings from the files .. so you only need your method if you were to do something like moving it to EXT2:
#ln -s /system/sd/media /system/media
would then be necessary since the system does not automatically recognize the EXT2 partition
I have a question, i am going thru themes for competition and ran into one that is a full rc33 update. Is there any way to flash this without screwing up apps to sd? Can i put apps back to memory, flash, then reflash when im done and run copy.sh app script again, anyone?
Rinja said:
JFvMOD by LucidREM
-Seems to be the most popular version right now.
-Same as JF RC33 V1.42 except for a few added files to make APPS to SD really easy for everyone.
-Themes will not work on this unless you manually make it a "lite" version following the steps below
Click to expand...
Click to collapse
Im currently running Lucid's JFvMod and a comp theme on dxtop. Works flawlessly and have all the stock notifications .... Thanks Lucid!
Related
There is an update for Terminal Emulator in the market I am wondering how you can uninstall it from JF 1.41 RC33 in order to get the update
you can use in terminal
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
rm /system/app/com.android.term.apk
or navigate to system/app
rm com.android.term.apk
It will close the terminal right away for obvious reasons and then you can load the one from the market.
Just tested it and it works and doesn't seem to have any adverse affects. Mine is still working
I dont see any difference in the app to me looks the same no changes that I can tell.
savethechicken said:
you can use in terminal
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
and the navigate to system/app or you can you use
rm system/app/com.android.term.apk
It will close the terminal right away for obvious reasons and then you can load the one from the market.
Just tested it and it works and doesn't seem to have any adverse affects. Mine is still working
I dont see any difference in the app to me looks the same no changes that I can tell.
Click to expand...
Click to collapse
I keep getting permission denied
are you type su first before mounting the image to get full superuser access.
The only difference we have if your signature is right is that im running the 1.41 RC33 but i was able to remove any apks i wanted this same way when i was on RC30
Yeah I typed su and got the superuser going... Maybe I am just oo much of a noob at this I am running the new JF RC33 update too
make sure that you are not typing anything in quotes "quotes just to show spaces" this is where i had the most problems when i started using this code
su
mount "space" -o "space" rw,remount "space" -t "space" yaffs2 "space" /dev/block/mtdblock03 "space" /system
then the long way
cd system
cd app
rm com.android.term.apk
that might help
Sweet I got it working thanks a million
Is there any reason why the new version is better than the one we have already?
not a problem.
I personally dont see any difference in it but everything still seems to be working
Alright, I've been posting this all over trying to help people figure out how to do this and figured it's time to make a dedicated thread. If at any point you get an error DON'T PROCEED. See if I referenced the error you're getting and, if so, do what I suggested. If not, post your error here and I'll try to get back to you ASAP.
NOTE: This can now also be done through my appstoSD app posted on this forum!!!! It will do everything for you.
This tutorial assumes you have:
A: A micro-sd card with 2 partitions, the first must be FAT32 and the second must be ext2.
B: Your phone must have one of the apps-to-sd ROM's installed.
C: Busybox installed into the /system/xbin directory. For steps on this please reference Darkrift's thread.
Before we start, let's make sure your phone is set up to handle this. Open up the terminal emulator app(available in the market) and type:
Code:
su
busybox df -h
If /system/sd doesn't appear, something is wrong. Either your sd card isn't partitioned correctly or your phone has a ROM that doesn't have apps to sd enabled. If /system/sd does show up then you're set and can start the tutorial
NOTE: Moving the cache is highly unstable and works for some people but not for most. I don't recommend trying unless you have a good idea of how to get your phone back to a usable state if it starts boot looping.
Now, for the first step you need to copy all the apps over to the sd card. To do this type(still in the terminal emulator)(The third and fourth lines are for cache to sd only):
Code:
busybox cp -a /data/app /system/sd/
busybox cp -a /data/app-private /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
exit
exit
Once the terminal emulator app closes, power off your phone. Then, turn it on in recovery mode by holding down the home button and then pressing the power button. Continue holding the home button until the "T-Mobile G1" icon goes away and a menu comes up. Then press Alt-x to go to recovery terminal. Press enter and a prompt should come up with a "#". Now type(If you only want your apps on your sd card and not the caches, skip steps 6-9)
Code:
mount data
rm -rf /data/app
ln -s /system/sd/app /data/app
rm -rf /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -rf /data/data
ln -s /system/sd/data /data/data
rm -rf /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
reboot
And... you're all set! Your phone might take a while at the android screen since it has to populate the apps tray. If it lasts >5-10 minutes then something likely went wrong. Make sure you did all the steps correctly and if you did try the steps in the recovery terminal section of this tutorial again. If it still doesn't work, post here and we'll try to get it sorted out. That aside, enjoy having your apps on SD card and the permanent 72-73MB available!
EDIT: forgot the app-private directory. Thanks, LucidREM!!!
Maximus is the man.
[email protected] said:
Now, for the first step you need to copy all the apps over to the sd card. To do this type(still in the terminal emulator)(The second and third lines are for cache to sd only):
Code:
busybox cp -a /data/app /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
exit
exit
Once the terminal emulator app closes, power off your phone. Then, turn it on in recovery mode by holding down the home button and then pressing the power button. Continue holding the home button until the "T-Mobile G1" icon goes away and a menu comes up. Then press Alt-x to go to recovery terminal. Press enter and a prompt should come up with a "#". Now type(If you only want your apps on your sd card and not the caches, skip steps 4-7)
Code:
mount data
rm -rf /data/app
ln -s /system/sd/app /data/app
rm -rf /data/data
ln -s /system/sd/data /data/data
rm -rf /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
reboot
Click to expand...
Click to collapse
i see a missing step here .. what about /data/app-private
LucidREM said:
i see a missing step here .. what about /data/app-private
Click to expand...
Click to collapse
RIGHT! I keep forgetting that one cause that folder pisses me off and I move all the apps there to the normal app folder lol. Will fix in 5, 4, 3...
EDIT: 2,1,0
cp: cannot stat '/data/davlik-cache': no such file or directory
whats up?
NEVERMIND. i need to go back to spelling class.
I'm sure its been asked and answered but I'll ask again! I understand it can take quite a few minutes to boot but is this every time you reboot or just the first time?
Thanks
DynaMight said:
I'm sure its been asked and answered but I'll ask again! I understand it can take quite a few minutes to boot but is this every time you reboot or just the first time?
Thanks
Click to expand...
Click to collapse
just the first time. its moving all the apps and cache from phone to sd card during that first reboot.
won't that slow down the phone even more?
the first time takes much longer. Subsequent reboots are of normal duration, comparable to the standard build.
Smokuevo said:
won't that slow down the phone even more?
Click to expand...
Click to collapse
if you use a class six sdcard, the apps will load faster. i believe that class 6 flash media is faster than the phones flash.
stogchris81 said:
if you use a class six sdcard, the apps will load faster. i believe that class 6 flash media is faster than the phones flash.
Click to expand...
Click to collapse
Pushing (writing) a 2MB file through adp push seems a bit faster to the SDCARD compared to the internal memory.
-> rough average for SDCARD : 1200 KB/s
-> rough average for system storage : 1000 KB/s
Regarding pulling (reading), internal seems faster :
-> rough average for SDCARD : 1247 KB/s
-> rough average for system storage : 1250 KB/s
These tests are everything but serious.. This is using the famous SanDisk 8GB Mobile Ultra (class 6).
To conclude I'd say that speed is almost the same, sometimes a bit faster for SDCARD.
i have one question
i tried to read through the thread but it was waay to large and long
if u do install apps to the sd card
when u install a newer rom on it does that mean the apps are automatically installed once again? i would like to do this because haykuro's roms are released once a week and i dont like reinstalling apps over and over again...
bigballa said:
i have one question
i tried to read through the thread but it was waay to large and long
if u do install apps to the sd card
when u install a newer rom on it does that mean the apps are automatically installed once again? i would like to do this because haykuro's roms are released once a week and i dont like reinstalling apps over and over again...
Click to expand...
Click to collapse
Unfortunately the answer is "sorta". The apps will still be on your sd card in the same places you put them. BUT all the symlinks will be gone so it'll look like they all dissapeared. You'll have to repeat the recovery terminal part of the tutorial, but all the stuff before it will be unnecessary.
i keep getting /system/sd/app is not a directory but when i run mkdir /system/sd/app it says that the file already exists.
the one time i got adb to work i did the steps through it to get apps to sd but the i had to wipe my phone. do i have to do the steps in the first post or recreate the symlinks?
wizern23 said:
i keep getting /system/sd/app is not a directory but when i run mkdir /system/sd/app it says that the file already exists.
the one time i got adb to work i did the steps through it to get apps to sd but the i had to wipe my phone. do i have to do the steps in the first post or recreate the symlinks?
Click to expand...
Click to collapse
In terminal emulator do this:
Code:
su
cd /system/sd
ls -l[CODE]
And put what it says on the line with "app" in it here. If it says "app ->" and has something after the arrow(my guess would be /data/app) then you put the symlink the wrong way. Make sure you do ln -s /system/sd/app /data/app, not the other way around. Let me know what your results are
[email protected] said:
In terminal emulator do this:
Code:
su
cd /system/sd
ls -l[CODE]
And put what it says on the line with "app" in it here. If it says "app ->" and has something after the arrow(my guess would be /data/app) then you put the symlink the wrong way. Make sure you do ln -s /system/sd/app /data/app, not the other way around. Let me know what your results are[/QUOTE]
huh? can you repeat that because i didnt understand what you were saying
im at the first step anyway. and thats when it says /system/sd/app is not a directory. my other question is is do i have to use
rm -rf /data/app
rm -rf /data/dalvik-cache
rm -rf /data/app-private
to re-establish the symlinks or did the steps through adb i used get erased when i wiped it.
Click to expand...
Click to collapse
[email protected] said:
In terminal emulator do this:
Code:
su
cd /system/sd
ls -l[CODE]
And put what it says on the line with "app" in it here. If it says "app ->" and has something after the arrow(my guess would be /data/app) then you put the symlink the wrong way. Make sure you do ln -s /system/sd/app /data/app, not the other way around. Let me know what your results are[/QUOTE]
i had the same problem. it said /system/sd/app is not a directory even though it already existed. when i used your code above this was my result:
drwx----- root root 2009-04-12 20:11 lost+found
-rw-r--r-- system system 29303 2009-04-11 11:56 app
Click to expand...
Click to collapse
wizern23 said:
huh? can you repeat that because i didnt understand what you were saying
im at the first step anyway. and thats when it says /system/sd/app is not a directory. my other question is is do i have to use
rm -rf /data/app
rm -rf /data/dalvik-cache
rm -rf /data/app-private
to re-establish the symlinks or did the steps through adb i used get erased when i wiped it.
Click to expand...
Click to collapse
Umm I wouldn't proceed cause if /system/sd/app isn't a directory then you're gonna have lots of problems. I need to know what it says after you type
Code:
su
cd /system/sd/
ln -s
Specifically, there'll be a line of output that has the word "app" towards/at the end. I need to know what's in that line. If the line doesn't start with a 'd' then app isn't a directory and something happened and you need to remove /system/sd/app by typing this in the terminal emulator:
Code:
su
busybox rm -rf /system/sd/app
and then restart the process from the beginning.
it says that /system/sd/app is not a directory but when i do mkdir /system/sd/app it says the file already exists.
the line with app in it says
-rw-r--r-- system system 29303 2009-04-14 17:27 app.
okay removing that made it work.
[edit] Thank you so much. it finally worked. i now have 73mb free on the phone.
glad I could help. On a side note Apps to SD app is now live
The script does a one time copy of the apps from /system/sd to /data for mytouch phones (since we don't need a2sd!). After that, a2sd is just disabled
Attachment: Update zip (takes about 20sec lol)
Pastebin: http://pastebin.com/d108b98f8
Rough info:
Cyanogen & Twisted A2SD modded for Hero (by Maxisma)
Remodified for CM 4.2+ by Wes Garner
This finds out if it is running on Magic or G1 and decides if A2SD is used or not
Mounts EXT for Magic and G1
Or you could just delete your ext2 partition...
but then no userinit
Didn't work for me. I have CM 4.2.5, downloaded mt3g-noa2sd-signed.zip and flashed it in recovery. Then when I rebooted I got to the CM bootscreen, after a few seconds the screen went black. I let it load for 45-60 minutes (watching tv) but nothing happened. Tried to flash again and the same thing.
ls -l in /data showed app and app-private was still linked to sd. I removed the links, made the directories and copied over the data from sd. Then it worked.
Kaptur said:
Didn't work for me. I have CM 4.2.5, downloaded mt3g-noa2sd-signed.zip and flashed it in recovery. Then when I rebooted I got to the CM bootscreen, after a few seconds the screen went black. I let it load for 45-60 minutes (watching tv) but nothing happened. Tried to flash again and the same thing.
ls -l in /data showed app and app-private was still linked to sd. I removed the links, made the directories and copied over the data from sd. Then it worked.
Click to expand...
Click to collapse
I'm having the same issue here, after flashing, I get Cyanogen boot screen and then it moves to black and sits there - since there's no way it's taking that long to copy the data, I'm guessing this script is broken as of 4.2.5.
From CyanogenMod Wiki http://wiki.cyanogenmod.com/index.php/Removing_Apps2SD
Removing Apps2SD
From CyanogenMod Wiki
Jump to: navigation, search
You'll probably have to re-install any paid apps (app-private) but normal apps should run fine after this.
For Terminal Emulator
Code:
su
mount -o rw,remount /system
Then proceed to the ADB instructions from after 'adb shell'
ADB Instructions
Code:
adb remount
adb shell
Code:
rm /data/app
mkdir /data/app
cp /system/sd/app/* /data/app/
rm /data/app-private
mkdir /data/app-private
cp -r /system/sd/app-private/* /data/app-private
rm /data/dalvik-cache
mkdir /data/dalvik-cache
reboot recovery
In Recovery Mode console, you will have to delete the ext partition:
Code:
parted /dev/block/mmcblk0
rm 2
quit
Note: If you had a 3rd partition for swap it will now be partition 2. Adjust your userinit.sh accordingly.
After rebooting, you can confirm that it worked by running:
ls -l /system
From Terminal Emulator (no need to remount/su) and you should see 'app' and 'app-private' as directories (and not app -> /system/sd/app).
Click to expand...
Click to collapse
yea oops, forgot to delete old symlinks on it
It doesn´t work for me...
I´m trying to disable A2sd because of my partition layout (Swap+Fat32) on my HTC Magic 32B but nothing happens after applying the update. My phone it just keeps in the bootloop forever....
*****THIS IS FOR 2.1 ONLY*****
*****YOU MUST BE ROOTED*****
This will theme well over 90% of everything you see that has to do with the android os and blur if its still there.
Download my files here http://www.megaupload.com/?d=59KOD7MS
By downloading this you agree to take full responsibility for the actions you are about to preform.
Original files if needed http://www.megaupload.com/?d=0RNAMSQ3
If you have kousch's recovery installed, make a back up, if not use root explorer and make a back up of the following file.
/system/framework/blur-res.apk
download the other original system files here
Sorry no MM method only terminal emulator, so you have to suffer through typing about 10 lines of commands....
Unzip the entire contents onto your sdcard
open terminal emulator
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Services.jar /system/framework
cp /sdcard/framework-res.apk /system/framework
your phone will auto reboot. If you havent already applied a changed services or framework the boot animation will take a long time. If it by chance freezes, or does the boot sound but never shows the screen do a battery pull.
Once your phone reboots you will see a new lock screen and dark status bar with white font, if this is not the case you need to redo the steps above.
If you have root explorer, long press on the /system folder choose permissions. Make note of what permissions are set, grant everything permission for now. Change this back when your done. Failure to do so may cause an apk to not apply.
If you prefer you can reboot after each line command by simply typing reboot and hitting enter, just to make sure it boots clean, but its really not needed.
Put capitol letters when seen!!!! failure will cause duplicate applications!!!
Dont apply anything blur you deleted and dont want on your phone.
In terminal emulator
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/BlurPhone.apk /system/app
cp /sdcard/BlurCalendar.apk /system/app
cp /sdcard/BlurContacts.apk /system/app
cp /sdcard/BlurHome.apk /system/app
cp /sdcard/Browser.apk /system/app
cp /sdcard/Gallery3D.apk /system/app
cp /sdcard/Music.apk /system/app
cp /sdcard/Settings.apk /system/app
this one goes to new directory so pay attention, dont get type happy
cp /sdcard/blur-res.apk /system/framework
now type reboot and hit enter
phone may or may not have an extended boot.
If you use handcent and want it themed, uninstall your old one
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/com.handcent.nextsms.apk /system/app
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Enjoy
Credit to
Me
prodigy
skyraider
tparker76
Teenfaces
stewart1champ
quadjacks
hacku
RinTinTigger
Taypotts
moto
htc
928droid
fabulous
I learned a lot from looking at how everyone else themed to get ideas for mine.
all images came from google searches. Then edited as needed.
reserved for me
please wait... an operator will be with you shortly...
Whens the download going to be up?
Ok. Now that i reverted to stock i can't get my themed google maps to install.... sucks. Also my themed launcher pro keeps my registation code. So if i release that its stealing. I will work on these two tonight and see what i can do.
Either way, a dl will be posted in the morning.
Sorry
Sent via your mom and tapatalk
Maybe try re-signing it then install via adb install command as per the the autosign.bat method in my other post.
ignorant question. Can i install this using Rom manager?
No sir. But you have rom manager and haven't switched to 2.2?
sent by your mom on tapatalk
Yep but I used sbf switched back to 2.1......2.2 had a few bugs that drove me crazy
Sent from my DROIDX using Tapatalk
running this theme
Ok backup made through rom mamnger. So im currently running rooted 2.1. Ive download the files and they are upzip on the root of the SD..can i simply type the codes in termnal emulator app on the phone and this should work?
catalystsupreme2 said:
Ok backup made through rom mamnger. So im currently running rooted 2.1. Ive download the files and they are upzip on the root of the SD..can i simply type the codes in termnal emulator app on the phone and this should work?
Click to expand...
Click to collapse
yup just follow the codes in the OP, you can omit what ever you dont want.
bad4u6669 said:
yup just follow the codes in the OP, you can omit what ever you dont want.
Click to expand...
Click to collapse
Big thanks for the help..everything worked flawlessly..very beautiful theme
catalystsupreme2 said:
Big thanks for the help..everything worked flawlessly..very beautiful theme
Click to expand...
Click to collapse
any time, head over to my 2.2 thread for a few upgrades, they still work for users on 2.1
FINALLY MY WIFI CAME BACK !!!
SO I THINK U SHOULD DEODEX UR ROM FOR MORE SPACE AND FLUIDITY
{I COULD NOT CREATE BATCH FILE AS OUR BOOT IMAGE DOES NOT SUPPORT TRUE ADB ROOT AS ITS DEV EDITION}(ANY IDEAS FROM DEVS IS WELCOME)
AGAIN SAYING NOT FOR ATT
OKAY FIRST THANX TO dsixda/Android-Kitchen FOR HELPING TO DEODEX THE ROM
NOW STEPS ::::::
-1.install a third party launcher (like apex for safety purpose)
0.MAKE A BACKUP OF UR SYSTEM (I HOPE U R USING BMM !!!)
1.DOWNLOAD THE APP AND FRAMEWORK FOLDER FROM LINK GIVEN BELOW
2.PUT BOTH THE FOLDERS ON SDCARD AS WELL AS INTERNAL MEMORY (DONNO WHICH IS USED !!)
3.OPEN THE """4.0.4ROOT BY CRC""" FOLDER U DOWNLOADED WHILE ROOTING OR ANY FOLDER WHICH CONTAINS ADB
3.5}NOW HOLDING SHIFT CLICK OPEN COMMAND WINDOW HERE
4.NOW CONNECT PHONE IN MTP MODE WITH DEBUGGING ON
5.TYPE THE FOLLOWING CODE AND U R DONE (WELL IT WILL SLIGHTLY MAKE U FEEL LIKE A TEMPORARY DEV HAAHAH)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodexedapp/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodexedframe/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
note ::
1.its o not zero
2.when u enter su the $ sign will change to # it means u gained root access
3.i dont remember but after pressing su look at ur phone if supersu notification for root access comes allow it if it is there
4.i am not sure or the stock launcher it may fc so firs install a third party launcher for safety purpose
*links ::::
apps::
https://app.sugarsync.com/iris/wf/D8443834_63525726_687588
framework::::
https://www.sugarsync.com/pf/D8443834_63525726_688199
pls hit thanx bros it motivates me !!!!!!!
make an acc on sugarsync the next famous storage systemm it will help u as well as me
What is MTP mode?
brianmoyano said:
What is MTP mode?
Click to expand...
Click to collapse
When ya connect the phone to PC, it will show 3 different modes. Like USB mass storage and stuff. One of em is MTP. pull down the notification bar, you will get those options (when connected of course)
Sent from my muffin LIFE! Under maintenance.!
Good. Thanks for sharing this!
I already Deodexed and zipaligined my rom using this tutorial to achieve the same.
brianmoyano said:
What is MTP mode?
Click to expand...
Click to collapse
Media Transfer Protocol. Gives you access to your SD Card and phone storage without unmounting them from phone so your SD Card is also available through phone as well as on PC. If you access any file on your phone, it will first copy it to PC and then open it which makes it slower. But its good enough for transferring pics and music and basically MEDIA TRANSFER as the name says..
answersamir said:
Code:
adb shell
su
stop
mount -o rw, remount /system/ /system/
cp /sdcard/deodexedapp/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodexedframe/* /system/framework/
rm /system/framework/*.odex
mount -o ro, remount /system/ /system/
reboot
Click to expand...
Click to collapse
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
shubham412302 said:
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
Click to expand...
Click to collapse
On extremely close observations I found out that both are same :sly:
Buddy order doesn't matter
Sent from my ME865 using xda app-developers app
can you upload an alternate link for 'apps' ...download is not completing...it is stopping after 140mb....
poorna said:
can you upload an alternate link for 'apps' ...download is not completing...it is stopping after 140mb....
Click to expand...
Click to collapse
Thats the full size of zipped apps...
But it has all apps
Sent from my jb atrix 2
shubham412302 said:
Thats the full size of zipped apps...
But it has all apps
Sent from my jb atrix 2
Click to expand...
Click to collapse
when i try to extract it ,i get a message invalid file ...the actual size is 185mb ...twice i downloaded. in the 1st attempt i was able to download 146mb...in the 2nd attempt i was able to download 140mb....
poorna said:
when i try to extract it ,i get a message invalid file ...the actual size is 185mb ...twice i downloaded. in the 1st attempt i was able to download 146mb...in the 2nd attempt i was able to download 140mb....
Click to expand...
Click to collapse
Match this with your d/l file.
146 MB (153,457,466 bytes)
CRC: 7FC9D73F
shubham412302 said:
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
Click to expand...
Click to collapse
the phone is not booting... after i type stop and press enter ,the screen turns off,then when i type mount -o rw,remount /system/ /system/ and press enter i get the same line and then i get the # symbol again..then when type rm /system/app/*.odex and press enter i get the same line and then i get the # symbol again ,same thing for the next rm line...but when i type cp /sdcard/deodexedapp/* /system/app/ and press enter i get the same line again and there is no # symbol,the same thing happens to the following lines ....when i typed reboot and press enter the same line(reboot) appears and the phone is not rebooting...i removed the battery and tried to boot the phone is not booting...i downloaded both the links (apps and framework) and extracted them and copied both(deodexedapp and deodexedframe) to internal phone storage and sd card ....what might be the problem here?
poorna said:
the phone is not booting... after i type stop and press enter ,the screen turns off,then when i type mount -o rw,remount /system/ /system/ and press enter i get the same line and then i get the # symbol again..then when type rm /system/app/*.odex and press enter i get the same line and then i get the # symbol again ,same thing for the next rm line...but when i type cp /sdcard/deodexedapp/* /system/app/ and press enter i get the same line again and there is no # symbol,the same thing happens to the following lines ....when i typed reboot and press enter the same line(reboot) appears and the phone is not rebooting...i removed the battery and tried to boot the phone is not booting...i downloaded both the links (apps and framework) and extracted them and copied both(deodexedapp and deodexedframe) to internal phone storage and sd card ....what might be the problem here?
Click to expand...
Click to collapse
Wait for a while....
Until you get the [email protected] again you must not do any thing because the previous step is not done.....
Be patient.
The step copy system apps take 5 minutes...
And there is a space here before remount
mount -o rw, remount /system/ /system/
Sent from my jb atrix 2
What are the advantages of deodexing the stock rom?
I came across this thread and it gave me curiosity to find-out the stuff which I wanted to read for long time. Odex and deodex..
The only advantage I came across of deodexing was posibility of theme modifications.
Some thread on XDA and google said that with odex rom (1) boot will be faster.
With deodexing, they said (1) it will take up more data space (2) theoritically deodexing will slow some performance and (3) longer boot times because of big dalvik cache...
Please can you tell me exactly where I am wrong?
Sent from my jb atrix 2
Download unsuccessful
Download is not starting...it says it has started but nothing is getting downloaded have tried a lot.... any alternate link pls:silly:
hello , it´s only for jelly bean?