Database Develop

trying to delete apks off ext3

ok so im trying to get rid of some apk that r no longer on my g1 they r just on my ext 3. i went into terminal and tried 2 sets of sripts. the 1st one was:
su
cd /system/sd
ls app
rm pk blah blah
basically when i ran this i got no such file in directory message. so i searched and tried this next:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /ststem
it said: device or resource busy
can anyone help? im on cm 3.6.8.1 with ext3. i dont have my pc with ubuntu on it it crashed.

do rm *.apk to remove all of them

alritewhadeva said:
do rm *.apk to remove all of them
Click to expand...
Click to collapse
yea i know that command but im just trying to get rid of one not all

pistol4413 said:
yea i know that command but im just trying to get rid of one not all
Click to expand...
Click to collapse
its case sensitive remember that..ur typing it wrong. not a mounting issue

su
cd /system/sd/app
ls
rm *APPNAMEASLISTEDABOVE*

Jonno12345 said:
su
cd /system/sd/app
ls
rm *APPNAMEASLISTEDABOVE*
Click to expand...
Click to collapse
Umm I tried that. I said I tried it in the 1st post. And I'm 100 percent sure I typed it right I wrote down the name on a seprate peice of paper and checking it twice.

In your first post, you're listing all the applications in the app folder, but then trying to remove them from the /system/sd folder. You need to cd into the app folder, then do the rm command, or do rm ./app/*APP NAME*
Atleast try following my steps before concluding they are not right .

Ok tried it ur way and same results:
Su
Cd /system/sd
Ls app
Rm com.bg.smsbk.apk
Rm: can not remove 'com.bg.smsbk.apk' No such file or directory
And like I said I tried this 1st b4 I posted, and I checked the spelling

You're missing a VERY important part of my instructions
su
*********** cd /system/sd/app **************
That /app part isn't for show, that is necessary.
Then use ls, not ls app
Follow my instructions to the letter, and you'll find a much better success rate .
Even better, tell me the name of the app and I can tell you exactly what to type

Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs

pistol4413 said:
Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs
Click to expand...
Click to collapse
try going into the recovery console
<enter>
mount /system
rm /system/sd/app/xxxxxxxxxx.apk
reboot
if you can't get anything else to work then download root explorer and delete the .apk using it.

pistol4413 said:
Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs
Click to expand...
Click to collapse
What he's saying is that when you type rm blah, you are trying to remove something from /system/sd/ when you need to be removing it from /system/sd/app therefore, you need to cd /system/sd/app to have the plain vanilla rm, otherwise, you need to rm app/blah.
I hate typing in the full names so what I do, is take a specific part of the apk filename that no other file has i.e.
If i was trying to delete com.flargh.apk, I would type
cd /system/sd/
ls app
rm app/*flargh* <- these asterisks are necessary, they are wildcards (just if you didn't know, I didn't want to clarify with another post down the line)
This way, its harder to mess up as you only need to type in a small portion of the actual filename.

h.nocturna said:
I hate typing in the full names so what I do, is take a specific part of the apk filename that no other file has i.e.
If i was trying to delete com.flargh.apk, I would type
cd /system/sd/
ls app
rm app/*flargh* <- these asterisks are necessary, they are wildcards (just if you didn't know, I didn't want to clarify with another post down the line)
This way, its harder to mess up as you only need to type in a small portion of the actual filename.
Click to expand...
Click to collapse
Great tip. I love it. Makes things so much simpler. Works like a charm.

@OP, your initial problem is that you were trying to do this from terminal, which is impossible if you are on apps2sd because the ext3 partition is in use whenever the phone is booted normally. therefore, you MUST reboot into recovery to mess with your ext3 partition in ANY WAY.
-BMFC

pistol4413 said:
Lol I truer ur commands didn't work same result. And by the way cd/system/sd/app is the same as this:
Cd /system/sd
Ls app
My command involve a few extra sets but either way they r the same as urs
Click to expand...
Click to collapse
This is not the same thing at all, this is:
cd /system/sd
You're now in the /system/sd folder
ls app
You're listing everything in the /system/sd/app folder
rm *app*
You're still in the /system/sd folder, so it's trying to remove the file from there, NOT the app folder you listed. My method would put you in the correct folder. You can use your method, but before the rm command, type 'cd app', that would work, but it adds unnecessary steps.

help with user.conf

can someone give me a tutorial on how to update the user.conf..i have looked at the compcache threads and linux swap but im not getting it...i want to be able to update it through terminal emulator and do i have to do nething to the userinit.sh if i change the user.conf...because numerous configs i have done for swappiness and linux swap...etc, have shown no difference..can somone give me a walkthrough...thanks so much..sry if i have a lot of questions just want to make myself more knowledgeable so i can hopefully return the favor to somone else one day

i do not know if you can edit it through the terminal sorry. i do know that you do not have to change the userinit.sh if you change user.conf, also i do know that you can open it up with PSPad (thats what i use) on a computer edit it there and push it back to phone and reboot. sorry i couldn't answer all of your questions

well i have had no problems editing it...its just putting it back nd making sure it works..now i have no problem using adb if u know of a tutorial to use it on mac...or know how to use it on mac

when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command

david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
delete this post; see below...

david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
this applies to tools and location of user.conf on cyanogen's roms ->
-transfer it to the root of your sdcard from your pc or mac to the g1.
-unmount sdcard from dropdown on the g1
-open up terminal on the g1
type and hit enter afterwards: cp /sdcard/user.conf /system/sd
type and hit enter afterwards: dos2unix /system/sd/user.conf
type and hit enter afterwards: chmod 664 /system/sd/user.conf
type and hit enter afterwards: exit
reboot

see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them

bonkasnucca said:
see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them
Click to expand...
Click to collapse
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works

david1171 said:
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works
Click to expand...
Click to collapse
775 = rwx-rwx-rx. conf file does not need executable in u-g nor x in o groups.
664 = rw-rw-r
if it is in /system/bin do this:
open up terminal
dos2unix /sdcard/user.conf
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/user.conf /system/bin
chmod 664 /system/bin/user.conf
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
reboot

[ROOTING] The M7 Exploit + Newbie Guide

To be honest, I'm a nice guy, but when threads get filled with utter "OMG, How do I root?" posts, I get pissed off. I don't mean to backseat moderate or anything, I just really get fed up sometimes. Hence, I've broken out the hardcore side of myself, and I present:
Coburn's (mostly) failproof rootmeplz kthxbai tutorial, featuring the awesome m7 exploit.
YOU CANNOT USE THIS ROOT GUIDE TO INSTALL ANDROID 2.0.x/2.1/2.x AT THIS MOMENT IN TIME. PLEASE DO NOT ASK IF YOU CAN INSTALL ANDROID 2.x USING ROOT, AT THIS STAGE IT'S A BIG FAT NO! THANK YOU FOR YOUR ATTENTION!!
Alright.
Easy to understand, plain english guide
Download the ZIP file attached to this post. Extract the files to a safe location - perhaps C:\Tattoo ?
Now, you'll need adb for windows. You can get it from my website's server here: ADB for windows.
Make sure your device is in USB Debug Mode (Settings > Applications > Development). This is ESSENTIAL!
Extract all the files in the adb4win zip file to your C:\Tattoo folder.
Now, go to Command Prompt. In XP, it's under System Tools in Accessories. In Vista/7, it'll be under accessories.
Do the following at the command line:
C:\Users\Coburn> cd C:\Tattoo
This will change your working directory from C:\Users\Coburn (or silimar) to C:\Tattoo .
Now, at the command line, do this:
C:\Tattoo> adb-windows shell "mkdir /data/local/bin" (with the quotes!).
This makes a directory on the Tattoo under /data/local, called bin. If you get a error (like mkdir failed, file/folder exists), this is fine! Don't sweat it.
Now, run this command:
C:\Tattoo> adb-windows push m7 /data/local/bin/m7
...and wait until finish.
Run this:
C:\Tattoo> adb-windows shell "cd /data/local/bin && chmod 755 ./m7" (with the quotes!)
This allows you to run the sucker.
Now, the fun part. Run this:
C:\Tattoo> adb-windows shell
This will dump you at a "$" shell. do the following:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
...lotsa text will flow down your screen. This is normal. Sometimes the exploit causes adb to freeze up, I don't know. I think it may be due to the exploit. It worked on my mac fine though...
Soon, you'll be greeted with this:
#
This is the root prompt! If you get stuff like this:
# usage: reboot ...
usage: reboot ....
usage: reboot ...
Just keep your cool, press enter and the # will say "Boo" again. This is due the exploit spawning reboots to gain the shell.
Then, do these commands from this thread's first post:
-bm- and the hax0rs crew said:
You did it, you should be root now!
Let's set some variables:
Code:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
[...] check if ur root:
Code:
id
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
When you get this:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
[... lotsa pasta ...]
#
You can do anything then! Look at /system, /data, etc etc. You're broken free, my friend, and you'll forever be free. Until you press that exit button. you didn't. You didn't press that exit button? lolwut u did? Grrrrrrr!!!
EDIT: Added Guide to remount partitions. It's below.
Now you need to install su. Exit your root shell (via CTRL+C) (NO, Coburn, are you serious? ME LOSE ROOT SHELL?! ) and download this su.zip and extract it to C:\Tattoo. DO NOT EXIT THE COMMAND PROMPT WINDOW.
Meanwhile, back at the ranch, in your command prompt window, do this:
C:\Tattoo> adb-windows push su /data/local/bin/su
Then break out a shell...
C:\Tattoo> adb-windows shell
at the $ prompt, enter:
$ chmod 755 /data/local/bin/su
$ cd /data/local/bin/
..run the exploit again via "while 'true' ; do ./m7 ; done" to get root again then enter ...
# chown root.root /data/local/bin/su
# chmod 4755 /data/local/bin/su
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system (This line allows you to play around with files on the system partition!)
After that, you can exit out of the root shell, and try a normal shell and this:
$ /data/local/bin/su
...which should make you get a nice # prompt. (Sometimes it doesn't, for me it got su: permission denied, wtf?)
(End SU Part of guide)
Tested on Windows 7. Also works on a phone terminal emulator too!
Keep your cool peeps - I do this for fun, I'm not a fulltime android dev. I am an addict though.
Happy rootin my friends.
Cheers,
Tattoo Hacker Coburn.
Greets fly out to the geeks that hacked it originally - without you, I'd have got a nexus one.
Thanks for marsdroid for correcting an error. Kudos to you, bro!
"ANDROID - It's a virus. In a Good Way. Once it's in your system, you can't get rid of it."

You should also add the "su" part in order to get root easier after the first time. Otherwise you have to do the exploit every time you want #

You could also add an explanation on how to remount the partitions without nosuid, so that a suid su can work.

mainfram3 said:
You could also add an explanation on how to remount the partitions without nosuid, so that a suid su can work.
Click to expand...
Click to collapse
Noted. Will do.
LordGiotto said:
You should also add the "su" part in order to get root easier after the first time. Otherwise you have to do the exploit every time you want #
Click to expand...
Click to collapse
Heh, yeah. Might add that up too.

Coburn64.
Thanks Man.
Nice Thread.

Thank you Coburn

svprm said:
Coburn64.
Thanks Man.
Nice Thread.
Click to expand...
Click to collapse
Thanks bro for your thanks.

I'm very glad you did that work, I'm kind of busy but I will update my statusposting and link to your HowTo!
Thats great community work.
[ROOTING] The M7 Exploit + Newbie Guide
Easy to understand, plain english guide
Click to expand...
Click to collapse
I apologize for my english, it's not my native language and I tried my best. ;-)
Keep up your work!
-bm-

-bm- said:
I'm very glad you did that work, I'm kind of busy but I will update my statusposting and link to your HowTo!
Thats great community work.
I apologize for my english, it's not my native language and I tried my best. ;-)
Keep up your work!
-bm-
Click to expand...
Click to collapse
You're welcome. I actually wanted this thread to help your thread, I wanted to spawn a m7 exploit thread to keep the original thread (which is based on the classic m6 exploit) clean of "How do I root with m7" and such.
Keep up the good work too, bm!

Thanks Coburn, so m6 is useless..
adb shell rm /data/local/bin/m6?

thx for the work , and corrections ! deleted the ealyer post

?
When i get # , and type:
# chown root.root /data/local/bin/su
i get :
chown root.root /data/local/bin/su
chown: not found
#
What i'm doing wrong /??

liderzre said:
When i get # , and type:
# chown root.root /data/local/bin/su
i get :
chown root.root /data/local/bin/su
chown: not found
#
What i'm doing wrong /??
Click to expand...
Click to collapse
type
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin

rooted
Ty. Guide is not 100% for noobs. (ME).

Problem copying files to system partition after successfull rooting
Hi
The device was rooted successfully (from the first time using m7)
But I have very strange problem.
I try to update some files in the /system (updating fonts in /system/fonts).
I successfully run following command to remount system with rw permissions
/system/bin/mount -o rw,remount /dev/block/mtdblock3 /system
But when I try to copy files to /system/fonts I get "not enough memory" error.
If I run "df" command it shows that /system has 14% free before write attempt
But if I run "df" command after the write attempt I see that there is no free space.
It looks like there is some protection mechanism that prevents copying files to /system partition.
Does any one has an idea how to solve it?
Thanks

ronyrad said:
Hi
The device was rooted successfully (from the first time using m7)
But I have very strange problem.
I try to update some files in the /system (updating fonts in /system/fonts).
I successfully run following command to remount system with rw permissions
/system/bin/mount -o rw,remount /dev/block/mtdblock3 /system
But when I try to copy files to /system/fonts I get "not enough memory" error.
If I run "df" command it shows that /system has 14% free before write attempt
But if I run "df" command after the write attempt I see that there is no free space.
It looks like there is some protection mechanism that prevents copying files to /system partition.
Does any one has an idea how to solve it?
Thanks
Click to expand...
Click to collapse
The problem is well known an jet we have got no explanation. It looks like an additional security system build in by HTC. That is what also prevents us from flashing Custom ROMS at the moment. Development goes on here: http://forum.xda-developers.com/showthread.php?t=631540&page=18 but there is no solution or explanation until now.
-bm-

Could it be that it seems to be that the driver (yaffs) is possibly trying to copy /system into memory, and then reflash the partition all at once (to prevent NAND/NOR tear and wear)?

this guide is in error and will for sure not work ...
you should post probberly ...specially now when things is working....
there is no reason do do a NONSENCE guide .....
thx for the work thoe
Click to expand...
Click to collapse
Excuse me, but it was tested working. I do not post false or misleading information, so please don't accuse me of posting something that won't work. It does work. If you have troubles, you're not following it correctly. Start again and work one step at a time.

Coburn64 said:
Excuse me, but it was tested working. I do not post false or misleading information, so please don't accuse me of posting something that won't work. It does work. If you have troubles, you're not following it correctly. Start again and work one step at a time.
Click to expand...
Click to collapse
don't worry for such baseless allegations coburn.... u r doing a great job. keep up this good work bro.... thanks a lot for this wonderful presentation...
waiting for ur custom ROM.....

Coburn64 u are missing a ; in the 2. while
and i dont expect the newbies to sit back and wait for the "BUUH"..
but im sure someone will....
thx again
EDIT Coburn64 fixed it

[FIXED] Remount failed: operation not permitted

Ok, I'm not a total noob. I've been trying to return to 1.5 as cleanly as possible, but now I'm having an error when trying to remount my phone.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
This is what I did:
Flashed the 1.5 RUU that Flipz has had out for months. No errors
Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
updated my profile
updated my PRL (which is now 65000??)
rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"
Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.
Anyone else have this issue? I searched the forum but I came up empty.

Try adb remount before adb shell. I'm pretty sure anythig with adb should be ran at just the command prompt.
Someone feel free to correct me if I'm wrong.

right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#

Yeah the wording got me. I was hoping it was as simple as that for you tho. Defiantly Strange. Believe me I've had plenty of those moments where hours would have been saved if someone could have just said "no your just doing it wrong".
Maybe try rerunning the RUU and start from scratch the PRI fix should hold thru the RUU but if it did affect something else running the RUU again may correct it.

I RUU'd about 4 times so far on two different laptops, one with XP and one with Win7, running both versions of the HTC Sync drivers.
Something is definitely different. I'm thinking of doing the PRI fix again to see if that helps. The PRL being 65000 instead of the normal 60664 is another anomaly I'm curious about.

looks as if the 65000 PRL is a new one. I can't confirm (not with Sprint) but there is a thread over in General talking about it.
http://forum.xda-developers.com/showthread.php?t=684873

YEAH! I fixed it....well....actually Flipz fixed it for me. I created a custom ROM in the kitchen and flashed it. Now the remount miraculously works. I'm back to being happy...though I don't know why. Its not like I was using root for anything

Nextelian said:
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Click to expand...
Click to collapse
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?

mrsato said:
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
Click to expand...
Click to collapse
I found something that help me and you. it properly works!!
I can't spell out instructions for the above mentioned suggestion, since I
don't know which file editor comes on the shipped device, but I have an
alternative solution.From the SDK's tools directory, run adb shell. In the
prompt run the following:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
and eventually you should restore the original directory permissions by:
# chmod 755 /system (Or any subdirectory you modified permissions to)
Hope this helps,
Yoav
Click to expand...
Click to collapse

still no Read/Write on /system
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.

mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
I'm not at my computer but I think the command is off... check to make sure its exactly how it should be... maybe the coma after the rw
Sent from my HERO200 using XDA App

mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
Just cd to your tools directory and adb remount

huedawg said:
Just cd to your tools directory and adb remount
Click to expand...
Click to collapse
Is there a solution for this?
I have a rooted HTC Desire.
When I type adb remount I get permission denied.
When I type adb shell and then su , i get permission denied!
This was a stock 2.2 rooted with unrevoked 3.
Any idea?
[edit]
i noticed root permissions pop-up on the phone and allowed so su worked.
[/edit]

Hi,
I have a Desire with stock froyo rooted with unrevocked 3 too and cannot use adb remount:
D:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
D:\android-sdk-windows\tools>adb shell
$ remount
remount
remount: permission denied
$
Click to expand...
Click to collapse
I have allowed ADB via the Super user app popup.
Any idea?
EDIT: I have set S-OFF using AlphaRev's recovery fastboot and I am now able to remount in rw (well no access denied anymore)
still missing some access as I fail to remove the Google Maps app (want to use Brut maps only)

ghost_boy1412 said:
I found something that help me and you. it properly works!!
Click to expand...
Click to collapse
This worked perfectly! Thank you!

Good freakin lord why the heck did you feel the need to bump this thread thats almost a year old just to say that!!!!!!!! I rarly shout like this, but this crap is starting to drive me crazy!!!!!!!!!!!!
Grrrrrrrrrrrrrrr

same thing for me. i get permission denied

DannyMichel said:
same thing for me. i get permission denied
Click to expand...
Click to collapse
thank you for letting us all know, and in such detail, and with new valuable information no less
/me shakes fists in rage.

Post deleted.

Don't mean to bring up this dead thread but a more simple solution would be this
adb shell
$ su
# busybox mount -o remount,rw /system (or another desired directory)
# chmod 777 (or another desired permission set) /system (or another desired directory)
# exit
$ exit

[HOW-TO] Manually Deodex Any ROM On The Atrix

First off I take no credit for any of these instructions!! I did not make them and they were found at another area of the forum, I just thought since I used them to deodex my OLYEM_U4_2.2.3 that they may be of use to someone.
P.S. For step 5 there was no guava.odex, so if nothing show's up don't worry about; and I also changed the mount codes for step 10, these were out of my experience and just made things quicker.
You must be rooted!
Get xUltimate here.
Process:
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
9. Put the phone in PC mode
10. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
Credits:
Rainabba and Mike919: For initially working with me to get a white clock, and later deodex.
toxman: For testing, and being a huge risk taker.
teenfaces: For letting me use his services.jar
And especially Xeudoxus: For letting me a guinea pig, for xUltimate, and answering my questions. And also for the making the xUltimate tool. It defiantly makes thing easier.

I get a virus warning Trojan when I downloaded the file, anyone else get this. I'm using Norton Antivirus.
Update:
The developers notes this on the OP. Figured what the hell and went ahead and tried it out. But when i press 3 i get "java" is not recognized and an internal or external command operable or batch file. So in english this means? I need Java SDK installed?
Update2:
I installed Java. And now everything seems to be working.

No virus However I got the java error, just downloaded java and problem sorted and now I'm deodexed Thanks for posting the information, really useful!

hexxor93 said:
No virus However I got the java error, just downloaded java and problem sorted and now I'm deodexed Thanks for posting the information, really useful!
Click to expand...
Click to collapse
No problem. Glad it worked.

Got the Java error. I already had it installed so I uninstalled and reinstalled to no avail. Can you guys be more specific as to which you downloaded? I have win 7 64 bit so I did the bottom option here: http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
Did anyone choose differently? I'll try 32 bit as I wait for a response.

omni_angel7 said:
Got the Java error. I already had it installed so I uninstalled and reinstalled to no avail. Can you guys be more specific as to which you downloaded? I have win 7 64 bit so I did the bottom option here: http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
Did anyone choose differently? I'll try 32 bit as I wait for a response.
Click to expand...
Click to collapse
http://www.java.com/en/download/ That's all nothing special just normal java

hexxor93 said:
http://www.java.com/en/download/ That's all nothing special just normal java
Click to expand...
Click to collapse
What the... That worked >.< Thanks man

omni_angel7 said:
What the... That worked >.< Thanks man
Click to expand...
Click to collapse
xD Glad it did. Random huh lol

hexxor93 said:
xD Glad it did. Random huh lol
Click to expand...
Click to collapse
Has anyone deodexed 2.3.4 build 4.5.91 yet? Can you confirm if this works?
TIA.
EDIT - Just went ahead and did it and it works well. The process is well documented by the OP.

i just tried this, gettin error any ideas ?this is what i did...
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\ADB>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
# su
su
# stop
stop
# mount -o rw,remount /system/ /system/
mount -o rw,remount /system/ /system/
# cp /sdcard/done_app/* /system/app/
cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
cp /sdcard/done_frame/* /system/framework/
cp: /system/framework/services.jar: No such file or directory
cp: /system/framework/sqlite-jdbc.jar: No space left on device
cp: /system/framework/svc.jar: No space left on device
# rm /system/app/*.odex
rm /system/app/*.odex
# rm /system/framework/*.odex
rm /system/framework/*.odex
# mount -o ro,remount /system/ /system/
mount -o ro,remount /system/ /system/
# reboot
reboot
C:\ADB>

simplesid242002 said:
i just tried this, gettin error any ideas ?this is what i did...
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\ADB>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
# su
su
# stop
stop
# mount -o rw,remount /system/ /system/
mount -o rw,remount /system/ /system/
# cp /sdcard/done_app/* /system/app/
cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
cp /sdcard/done_frame/* /system/framework/
cp: /system/framework/services.jar: No such file or directory
cp: /system/framework/sqlite-jdbc.jar: No space left on device
cp: /system/framework/svc.jar: No space left on device
# rm /system/app/*.odex
rm /system/app/*.odex
# rm /system/framework/*.odex
rm /system/framework/*.odex
# mount -o ro,remount /system/ /system/
mount -o ro,remount /system/ /system/
# reboot
reboot
C:\ADB>
Click to expand...
Click to collapse
I ran into that as well... I treated it as if I ran out of space, so I reran the copy command: cp /sdcard/done_frame/* /system/framework/ . With the odex files gone it ran without issue.
But it looks like you copied and pasted the entire block. I did it line by line and only rebooted at the end (after my second attempt to copy those files).

Can it deodex official 2.3.4?
Sent from my MB860 using XDA App

Javi97100 said:
Can it deodex official 2.3.4?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes it can.

how do I know if i am dedoexed after doing all the steps?

and i keep getting error when trying to flash blur music.apk

i am at the adb shell step. When i get to typing: mount -o rw,remount /system/ /system/ it gives me a permission denied. What am i doing wrong?

and1baller said:
i am at the adb shell step. When i get to typing: mount -o rw,remount /system/ /system/ it gives me a permission denied. What am i doing wrong?
Click to expand...
Click to collapse
are you rooted?
did you enter "su"?
does the prompt appear as "#"?

yes i am rooted and i did type SU. But i don't see a # sign. All i see is a $ sign.

and1baller said:
yes i am rooted and i did type SU. But i don't see a # sign. All i see is a $ sign.
Click to expand...
Click to collapse
Then you are not in as root. When you type "su" do you check the phone screen to see if it is asking for you to grant permissions?

i checked the screen when typing su but it doesn't ask me to give permission. I am in usb debugging and the usb connection is set as none.