As you all are aware, the amazing developers at TeamWin were able to find a way to allow us to temporarily root our devices.
If you would like to play around with apps that use Superuser, then there are a few more things you would need to do.
WARNING - DO THIS AT YOUR OWN PERIL. I cannot provide extensive support. What i can provide is a way for applications that use Superuser such as Titanium Backup to recognize the root.
Since this is all temporary, you will only have access until the next time the device decides to clean house! Then, you will need to reboot, reroot, and rerun the script. This is only if you want to kind of fool around for a bit.
What you need:
Rooted with Fre3vo
Understand how to use ADB
Superuser.apk & Su
Titanium Backup
Busybox
fixsu.sh
1. adb push fixsu.sh /data/local/tmp
2. adb push su /data/local/tmp
3. adb push busybox /data/local/tmp
4. adb shell chmod 777 /data/local/tmp/fixsu.sh
5. adb shell chmod 777 /data/local/tmp/su
6. adb shell chmod 777 /data/local/tmp/busybox
7. Install Superuser.apk
8. Install Titanium Backup
9. adb shell
# cd /data/local/tmp
# ./fixsu.sh
--- It's okay to see this error ---
rm failed for /system/bin/su Read-only file system
Hopefully when you are all done, you can open up Superuser and TitaniumBackup and you will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Props to: Vampirefo for the shell script.
Lintrix said:
As you all are aware, the amazing developers at TeamWin were able to find a way to allow us to temporarily root our devices.
If you would like to play around with apps that use Superuser, then there are a few more things you would need to do.
WARNING - DO THIS AT YOUR OWN PERIL. I cannot provide extensive support. What i can provide is a way for applications that use Superuser such as Titanium Backup to recognize the root.
Since this is all temporary, you will only have access until the next time the device decides to clean house! Then, you will need to reboot, reroot, and rerun the script. This is only if you want to kind of fool around for a bit.
What you need:
Rooted with Fre3vo
Understand how to use ADB
Superuser.apk & Su
Titanium Backup
Busybox
fixsu.sh
1. adb push fixsu.sh /data/local/tmp
2. adb push su /data/local/tmp
3. adb push busybox /data/local/tmp
4. adb shell chmod 777 /data/local/tmp/fixsu.sh
5. adb shell chmod 777 /data/local/tmp/su
6. adb shell chmod 777 /data/local/tmp/busybox
7. Install Superuser.apk
8. Install Titanium Backup
9. adb shell
# cd /data/local/tmp
# ./fixsu.sh
--- You should not see any errors ---
Hopefully when you are all done, you can open up Superuser and TitaniumBackup and you will see something like this:
Click to expand...
Click to collapse
will try this after work
so where do we go to learn how to use ADB ?
SayWhat10 said:
so where do we go to learn how to use ADB ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=532719
Sent from my PC36100 using XDA App
Worked perfect! Thanks for the write up!
Much appreciated
SayWhat10 said:
so where do we go to learn how to use ADB ?
Click to expand...
Click to collapse
adb is really quite trivial. The main commands you need to worry about are push, which lets you upload a file to the phone, pull, which lets you download a file from the phone, and shell, which lets you send commands to the linux bash shell (or is it just sh? doesn't matter they're both very similar.) Adb push and pull work like this:
adb pull <source file on the phone>
adb push <source file on your pc> <destination directory on the phone>
So say for example you wanted to upload su to a writable location (in this case, /data/local/tmp,) you'd execute a command like this:
adb push su /data/local/tmp
adb shell with parameters after it will execute a shell command with that parameter. Or you can just do 'adb shell' and it'll bring up an interactive bash prompt where you can simply enter commands without having to type 'adb shell' at each line.
Now bash itself is a little more technical, but for the purposes of this, you only need to understand a few things: In linux, you need to flag a file with an executable permission attribute before you can execute it. This is what the 'chmod 777 <filename>' command does. So say you want to make su executable:
# chmod 777 su
And unless you set a PATH= environment variable (don't worry if you don't know what that is) you need to specify an absolute path to the executable in order to execute it. A simple dot (.) refers to the current directory. So if you are already in /data/local/tmp, you can say for example do this:
# ./su
Otherwise if you were in another directory, it would have to be:
# /data/local/tmp/su
As far as changing directories, bash is similar to DOS, aka windows command prompt. Just cd <directory name>. cd .. changes to one directory up in the heirarchy. Or you can specify an absolute path to switch to another directory without hopping through other ones first, e.g:
cd /data/local/tmp
Also noticed you can only use Root one time before it dies. Example: I tried to remove Amazon MP3 crapware and it removed but Superuser had to force close. Then no more exploit. Did I do something wrong or is that just the way it is for now?
Yes i know crapware comes back after reboot. Just sayin...
Yea I opened titanium backup once. Worked great when I tried to reopen it superuser force close. And TB couldn't find the root again.
Sent from my HTC Sensation 4G using XDA Premium App
any idea what the heck i'm doing wrong? i've been at this for a while now and it seems that i can't push files... i've tried everything i can think of and it keeps telling me that "adb: permission denied"
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tr0s>cd\
C:\Program Files (x86)\Android\android-sdk>cd\program files (x86)\android\androi
d-sdk\platform-tools
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ adb push fixsu.sh /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb: permission denied
$
Have you enable debug mode?
I was scratching my head until I revise debug mode is default to off.
yep.... i double checked that one
try this
adb kill-server
sudo adb start-server
adb push <file> <location on device>
the push may need a sudo as well. I can't remember if it did when I was having this problem. I don't think it does though
MichaelW2608 said:
adb kill-server
sudo adb start-server
adb push <file> <location on device>
the push may need a sudo as well. I can't remember if it did when I was having this problem. I don't think it does though
Click to expand...
Click to collapse
How do you push Fre3Vo to E3D? I've installed android sdk but I am unable to find my device at adb device. Did I do something wrong here? Please advise.
scrosler said:
Also noticed you can only use Root one time before it dies. Example: I tried to remove Amazon MP3 crapware and it removed but Superuser had to force close. Then no more exploit. Did I do something wrong or is that just the way it is for now?
Yes i know crapware comes back after reboot. Just sayin...
Click to expand...
Click to collapse
So we couldn't use this to remove any bloatware or say remove Swype and replace it with the new version of swype?
ok thank you guys i finally go it to give me root. i still can't get titanium backup to come up though..... it tells me that it's not rooted yet adb tells me otherwise. and i have superuser installed.
edit: so after about the 5th attempt it finally went through. so far it's working flawlessly and superuser isn't force closing. i've been able to delete some bloat and now i'm doing a full batch backup of the current system. i can't wait until full root access but this is definitely working for me now! xda rocks!
Scoop24 said:
Yea I opened titanium backup once. Worked great when I tried to reopen it superuser force close. And TB couldn't find the root again.
Sent from my HTC Sensation 4G using XDA Premium App
Click to expand...
Click to collapse
Superuser had a known problem and it crashed most of the times with the Incredible S , to solve this someone modified the superuser and it wouldn't crash anymore.
This is how we get the SU working on the Incredible S by then.
I am thinking a patched SU would do the trick . The patched SU has a version number of v9.9.9 or something like this.
A user madmaxx82 at the Incredible S forums knows very well about this issue and you guys can ask him for a patched SU version and then try again...
SU should work flawlessly after this patch.
Oohmahgaawwd.
Thank you!! I won't have to go back throw all my games I haven't beaten yet!
And tasker! My tasks!! Yay!
Sent from my PG86100 using Tapatalk
Ya so far my experience has been:
rooted the first time and busybox said i was rooted but superuser crashes and titanium says non-root (but adb says i'm rooted)
second time, i fixed the superuser problem by uninstalling then simply installing from Market...when it installed it said I should get the latest binary, i did, and it crashed zero times since then...the problem at that point was that superuser then allowed ITSELF, but busybox now said it WAS'NT rooted...and TB still no good.
SO: so far Superuser is 1 for 2, same with busybox, and TB is 0 for two.
I'll try again and see if I can just install superuser from market as a substitute for that step...or else maybe I can get the latest APK from market and then install vial adb just like your post says.
QUESTION: What's the point of the fixsu? that last step has given me weird responses every time (sometimes no reaction from adb, other times it seems to try to run busybox in every single /system folder....hmm)
OH, QUICK NOTE FOR NOOBS: OP's two steps that start "INSTALL..."...should read "adb install" .......or at least that's how it worked for me.
My experience is this.... Titanium works for restoringbut not really all that well for uninstalling, after rebooting I still have the icons and bs for all the stock sprint apps like telenav, amazon, and sprint tv. I also couldn't get root permissions for adfree either. I did notice that I had root until I hit kill all in atk so that seems to have something to do with it.
Sent from my PG86100 using XDA Premium App
Related
Hello everyone,
Its been great to have root on your X10 using the method posted here:
http://forum.xda-developers.com/showthread.php?t=711907
Well, this method works all right but I did some investigating of my own to audit the state of the system after its been rooted. Thanks to the discussions you may find here: http://forum.xda-developers.com/showthread.php?t=712178, the original developers soon chose to update the Rooting tutorial with some additional steps (See post #2 and #4 of the rooting thread). This is all good, because now you have the real power to act as a the *real* superuser i.e uid 0.
Most of the discussions that follow are only intended for users who are well versed with general *NIX security and concepts about user ids, permissions and other things. So please disregard this post if you have no ideas of these concepts.
Ok, so first things first. I basically followed the root tutorial as it is all the way upto step3 (or step3a as in my case). Remember, you essentially have a rooted phone right after step2, step3/3a just adds the updated baseband firmware, which has no effect whatsoever on the subsequent things that you do to your phone.
Well essentially, what I did do was install the "su" binary and the "Superuser.apk" following in the lines of step4v2 (post #2 in root thread). These are essential to give you control over your system as without them you are simply relying on a hacked "sh" binary which runs with elevated privileges. Here are the file permission masks for the "sh" binary which gets installed after the FOTA in step2:
Code:
# ls -l sh
ls -l sh
-rwsrwsrwx root root 86944 2010-06-28 18:08 sh
#
Wait!!! This is *not* quite ok. What this means is that any process can use this binary to gain super user privileges. This binary is setuid and setgid root!!!
Well you might say that... so is the case for "su":
Code:
# ls -l su
ls -l su
-rwsrwsrwx root root 22120 2010-06-28 08:08 su
#
But, this is different because its use is controlled by the Superuser Whitelist application that was installed with Superuser.apk.
This difference is crucial because if any non-privileged application and process forks and execs "su", the Superuser Whitelist app would immediately post a notification screen on the phone and provide options to allow or disallow.
With the "sh" binary installed on your phone as it is, you are basically inviting *any* application to be able to do anything it wants to your phone... and all this without your knowledge!!!
To test this theory, all you need to do is simply install one of the terminal emulators floating around the market or use the one provided in the rooting thread under the step4/app folder and launch it. It straight away, launches you into a root shell. Here is a screen shot of what you can do this way:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Remember, no warnings, no notifications and all this can be done by any app under the hood)
Here is what you can do to make your phone more secure.
Step1: Download an alternative shell or simply change the permissions on the "sh" binary:
Code:
# cd /system/bin
# chmod 755 sh
Step2: In case you downloaded an alternative shell like "bash" and copied it under your /system/bin folder, simply get rid of the original "sh" binary and create a symlink to the one you download, for ex: bash:
Code:
# cd /system/bin
# rm sh
# ln -s bash sh
(Note: the above steps assume that you have /system mounted as rw, if you don't know what that means, then you should not be reading this, sorry)
Remember, when installing any alternative shell make sure that its permission mode is set to 755 or lower. I recommend to *never* set the setuid and setgid bits on the shell!!!
Here is what I did personally:
Installed bash from here: http://forum.xda-developers.com/showthread.php?t=537827
Installed it under /system/bin *without* the setuid and setgid bits
Removed the "sh" binary
Created a symlink named "sh" to the binary "bash"
This way, whenever I launch "adb shell" or use any terminal emulator on my phone, I always get a un-privileged shell. To get root, simply fire "su".
PS: This information is not intended for casual users who have limited or no knowledge of UNIX or UNIX like sytems like Linux, Adrdoid SDK commands like adb or don't know their way around if faced with a command line!!!
PS: Another post with some steps to properly secure the system: http://forum.xda-developers.com/showthread.php?t=712945
lmao..
http://forum.xda-developers.com/showthread.php?t=712945
zephyrix said:
lmao..
http://forum.xda-developers.com/showthread.php?t=712945
Click to expand...
Click to collapse
lol, you must've done this while I was writing mine!!
Anyways, its good to have this info out and I do point out some concepts detailing *why* this is a problem.
Definitely.
Make sure people have installed a proper way to elevate to root before attempting to change sh to not setuid, or they may screw themselves over lol
Thanks for your guide! Much appreciated would be an understatement.
is there any other way of testing that as using tht method in ur given picture now says read only error does this mean i successfully secured my root?
bcool15 said:
is there any other way of testing that as using tht method in ur given picture now says read only error does this mean i successfully secured my root?
Click to expand...
Click to collapse
Oh... I think I forgot to show this, but essentially you need to get the system partition into read/write mode as well. So it will be one more command before the write is attempted:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
...
...
# echo "I can...
j4mm3r said:
Oh... I think I forgot to show this, but essentially you need to get the system partition into read/write mode as well. So it will be one more command before the write is attempted:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
...
...
# echo "I can...
Click to expand...
Click to collapse
thats the command which stoppped wrkin so i just redid whole rooting procedure with new v3 update does it still need securing?
bcool15 said:
thats the command which stoppped wrkin so i just redid whole rooting procedure with new v3 update does it still need securing?
Click to expand...
Click to collapse
Dont worry about the example shown in the screen shot. That is just to illustrate what a setuid "sh" binary can do to your system.
j4mm3r said:
Dont worry about the example shown in the screen shot. That is just to illustrate what a setuid "sh" binary can do to your system.
Click to expand...
Click to collapse
this securing procedure isnt working on my new root any suggestions?
please
Regards,
bcool15 said:
this securing procedure isnt working on my new root any suggestions?
please
Regards,
Click to expand...
Click to collapse
Exactly what procedure are you referring to? The post is just meant to be a set of guidelines of a vulnerability that existed on the phone after it was rooted using "the root procedure" at the time this was posted.
If you have a "sh" binary on your phone which is setuid and setgid, then you have this vulnerability. I haven't updated the post with results from any new root procedures that have been posted since, but I suspect even the newer methods posted so far in the "root thread" don't get rid of the compromised "sh" binary.
Please ignore if you don't know what setuid and setgid means.
All credits go to pulpoff2 for this! This is not by me, I am merely the messenger. Only thing I did was to ask pulpoff for the files and a tutorial With his permission I will share it with you.
This will provide you with a fresh and unmodified 2.1-system, exactly like you would do the official update - only exception is that it is rooted. So all the apps and games of the official firmware are available and nothing else. You can remove the crap (like the games or timescape for example) by yourself after doing the steps below.
UPDATE:
There is a newer ROM by propc you can use instead of this one. Look here:
http://forum.xda-developers.com/showthread.php?t=888427
-- NEW --
propc kindly provides us with a shellscript to automate the steps below. See here for the script and a short manual:
http://forum.xda-developers.com/showpost.php?p=10067921&postcount=120
If the script doesn't work for you or you prefer to do things the manual way, you may use the steps below.
Download these files:
x8-2.1rooted.img.yaffs.rar
and
ISO-8859-1__unyaffs-arm.rar
Also download the 2.1-firmware from here or here. Unpack it on your computer and delete the "system.sin".
Unpack "x8rooted.img", "busybox" and "unyaffs" to SDcard.
You need 1.6 with root on your phone. By the way, all the data on your phone will be lost after doing the following steps, so making a backup is advised.
Use "adb shell" to connect to your phone and become su:
Code:
su
Copy "busybox" and "unyaffs" to /data/local/tmp. (Pulpoff says you should copy to /sbin, but this requires remounting with busybox. I copied to /sbin, but I think /data/local/tmp should work just fine)
Code:
cd /data/local/tmp
cat /sdcard/busybox > busybox
cat /sdcard/unyaffs > unyaffs
chmod the files to make them executable:
Code:
chmod 755 busybox
chmod 755 unyaffs
EDIT: If you want to copy the files to /sbin (like pulpoff2 advises), you can do this OPTIONAL step:
EDIT2: It was confirmed that this is indeed not necessary!
Remount the root directory to make /sbin writable. Then copy the files over and change the working directory to /sbin:
Code:
[strike]
./busybox mount -o remount,rw /
./busybox cp -prf busybox /sbin/
./busybox cp -prf unyaffs /sbin/
cd /sbin[/strike]
Remount /system as writable:
Code:
mount -o remount,rw /dev/block/mtdblock0 /system
Switch to busybox shell:
Code:
./busybox sh
Remove /system (yes, really!). It's normal to get errors because of the "lost+found"-folders. Ignore the errors.
Code:
./busybox rm -r /system
Unpack pre-rooted image to system. It should output "end of image" if it finishes correctly.
Code:
./unyaffs /sdcard/x8rooted.img /system
Your phone won't boot anymore now and it will crash as soon as you try to use it - that's normal! Go to next step.
Just remove the battery and the usb-cable from the phone, then re-attach the battery. Flash 2.1-kernel (without system.sin !!) using the flasher-tool by Bin4ry. If the flasher gives you an error because of a missing "loader.sin" you can take this file from the 1.6-firmware. Refer to Bin4ry's thread to learn how to use his flasher and how to enter flash-mode on your phone.
The phone should now boot, although the first boot can take a little while. If you get into a boot-loop or you just see the white sony ericsson logo (not the green one after the animation) for several minutes, it probably didn't work and you have to start over again by flashing 1.6.
This was written as I remember how I did it by myself. It worked for me at first try! If it works for you, please click the thanks-button. It will make me feel better
After you have your nice rooted 2.1 you probably want to enable JIT for a nice performance boost.
But does it have root? Bad reading.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
a-k-t-w said:
But does it have root?
Click to expand...
Click to collapse
Absolutely. But no busybox. So if you plan to enable JIT, you have to copy busybox to /system/bin by yourself.
a-k-t-w said:
But does it have root? Bad reading.
Click to expand...
Click to collapse
of course it is rooted.
now we know what to do with unyaffs.
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
csengoi said:
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
Click to expand...
Click to collapse
1: There is no way to directly root a phone with 2.1. You need to go back to 1.6, root it and then follow the above steps.
2: I guess so. As far as I know the firmware is the same for all countries.
Works like a charm! I removed the /system folder contents one by one though, using the method from the previous thread. Anyway, the first time I tried, unyaffs exited before extracting all the files (maybe the phone ran out of memory?). I didn't notice it and went on to flash the phone, ending up stuck at the Sony Ericsson logo. So, make sure that unyaffs reports that it has reached the "end of image" before moving on to the next step!
Thanks!!
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
isaac12 said:
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
Click to expand...
Click to collapse
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
---dobule post--- sorry
trapacska said:
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
Click to expand...
Click to collapse
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
WARR10r said:
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
Click to expand...
Click to collapse
This has nothing to do with App2SD. Also the ROM gets loaded from internal flash, not from sdcard. The result is the same as with the official update, but with root.
If you want to have /data on sdcard, use the modified chargemon or neptun2's method.
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
try adding ./ before
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
You should still be in "/data/local/tmp" as the working directory (check with "pwd"-command). If you followed the steps correctly, you should have a working busybox-file in there. So just type "busybox sh". If it looks like it does nothing, it's all right
isaac12 said:
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
Click to expand...
Click to collapse
try to use another su. i rooted my x8 with superoneclick 1.5.0
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Sectoras said:
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Click to expand...
Click to collapse
That's way too long, something isn't right there. To start over again you have to flash back to 1.6.
Ok I had not realised the superuser permissions was not popping up on my phone that's sorted now. I get to number 8 again and it said permission denied
This script will run on Windows, Linux and Mac. No longer do you have to worry about having adb in your path, as i have included the binaries for all the operating systems.
The Linux and Mac script will automatically detect what O/S your using and use the correct binary.
You should be all set right out of the box, as long as you have the adb drivers installed for your device if you are in Windows. Linux/Mac users need not worry about the drivers.
COMING SOON.
overclocking capability and more
For Windows Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Make sure your drivers are installed.
Youtube Video from a user
http://www.youtube.com/watch?v=ZcWqeYQjjk0
older version of the script but same principal
4. Run Root.bat
5. Select your device
6. Hit #1
7. Profit!!!
Drivers For Windows:
Evo3D 32-bit Windows drivers:
Download HERE
Evo3D 64-bit Windows drivers:
Download HERE X64
For Linux/Mac Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Enter the directory.
4. Set the script permissions to allow it to execute.
Code:
chmod +x root
5. Plug in your device.
6. Run the script.
Code:
./root
7. Select your device.
8. Select #1
9. Profit!
Notes:
After the script starts all you have to do is choose option #1
The script remounts the file system R/W by itself. The other options are just there for convenience if you were to need to remount for hackery. sorry for the confusion.
All files are included including Fre3vo, su, busybox and superuser.apk
I get absolutely no superuser force closes with this. Titanium backup works perfectly. This is also the newest version of the superuser beta.
I have tested these scripts on my phone 10x each, 20 reboots if your counting If you are having problems REBOOT the phone to wipe all the changes you may have made with other scripts/errors.
Also if you install the Terminal Emulator from the market and type "su" you will get a superuser pop up to allow permissions and you will get a root prompt in the Terminal.
Let me know how it works for you.
Changelog:
v2.5
[Linux/Mac] Auto-detect Os
[Linux/Mac] Linux and Mac binaries now included so no more adb having to be in your PATH
v2.4
[Linux/Mac] Fix stupid error on my part in linux script
v2.3
[Linux/Mac]
[Windows]
Script Tweaks
New sticky temp root method (Installs to /vendor/bin/)
v2.2
[Linux/Mac]
[Windows]
HTC Sensation Support!
v2.1
[Linux/Mac] script tweaks
[Windows] rewrote script & added tools
v2.0
[Linux/Mac] rewrote script & added tools
[Windows] SORRY WINDOWS USERS NEW SCRIPT ISNT DONE FOR WINDOWS YET
v1.1
[Windows] Added Windows .bat
v1.0
[Linux/Mac] Initial Release
[Windows] Release SOON!
Download it here
http://dl.dropbox.com/u/11406774/Jeremy_Fre3vo2.5.zip
------Linux
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------Windows
Dam sweeeet
Can someone make one for a win XP setup
I plan on making a .bat soon but if someone that knows what they are doing wants to try to convert it over for me ill update the op. I use my only windows computer to watch netflix on my tv. LOL
Pew Pew
I got Linux but how do I run this one tho?
Sent From My "Desperate For Root" 3VO...
You Sir are Amazing. Thank You. (Moves my own script into trash =) )
Eagerly awaiting a .bat file for this.
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Stericson said:
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
Click to expand...
Click to collapse
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
**************
Your choices:
**************
(1) Set PATH variable for SDK platform-tools directory
(2) List devices found by adb
(3) Temp Root your Evo3d or Sensation with Fre3vo
(4) Install su, Superuser.apk and busybox
(5) Mount /system as R/W
(6) Mount /system as R/O
(7) Check mount points
(8) ADB Shell
(9) Exit
Type choice number: 4
********** su, Superuser.apk and busybox ***********
---------------------------------------------------------
Mounting /system as R/W
mount: Read-only file system
Done!!
---------------------------------------------------------
Installing su and busybox
failed to copy 'bin/su' to '/system/bin//su': Read-only file system
Unable to chmod /system/bin/su: Read-only file system
link failed File exists
failed to copy 'bin/busybox' to '/system/bin//busybox': Read-only file system
Unable to chmod /system/bin/busybox: Read-only file system
[1] Segmentation fault busybox --instal...
Done!!
---------------------------------------------------------
Installing Superuser
failed to copy 'apk/Superuser.apk' to '/system/app//Superuser.apk': Read-only fi
le system
Done!!
---------------------------------------------------------
Installing user and group
cannot create /system/etc/passwd: read-only file system
cannot create /system/etc/group: read-only file system
Unable to chmod /system/etc/passwd: No such file or directory
Unable to chmod /system/etc/group: No such file or directory
Done!!
---------------------------------------------------------
Complete, Press ENTER to return back to the main menu
Click to expand...
Click to collapse
Not sure what I'm doing wrong, copied all the folder elements into c:/android-sdk-windows/platform-tools, ran root.bat, pressed 3, waited until process finished, then pressed 4, installation says Okay. I see SU.apk installed on my phone but whenver I open up any rooted apps, it says cannot find root.
EDIT: this is through the windows version of the script.
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Stericson said:
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Click to expand...
Click to collapse
I'm retrying, let me test again after reboot.
fowenati said:
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Click to expand...
Click to collapse
here is the mac binary for adb.
what you have to do is copy it into the /usr/bin/ folder.
Code:
sudo cp adb /usr/bin/
you need to make sure you are in the directory that adb is in when you execute that.
spunks3 said:
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
Click to expand...
Click to collapse
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Stericson said:
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Click to expand...
Click to collapse
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
EDIT: root.bat is in c:/android-sdk-windows/, I cropped it out of the picture though.
SuperUser keeps crashing for me....that might be the problem...
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on super user, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
k2buckley said:
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on SU, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
Click to expand...
Click to collapse
Your welcome
it lasts me until reboot every time normally, im pretty sure the main problem with some other scripts are they are not setting the permissions right and not modifying the passwd and group files correctly.
no f/c on my end either
spunks3 said:
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
Click to expand...
Click to collapse
yea Stericson is right, looks like the batch file isn't auto mounting the /system as R/W.
gonna go take a look at it now
Overstew said:
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
Click to expand...
Click to collapse
interesting...your picture shows it cannot find /bin/fre3vo
either it cant find the folder, or it cant find the file....
Difference between Pre-OTA and Post-OTA: Pre-OTA means you did NOT accept the Over The Air system update. Post means you did
Click to expand...
Click to collapse
Well... I used all of the root tools and scripts... i always had a problem where no matter what only one program would get root. Then Titanium Backup wouldnt acquire root EVER...
Then I tried the new perma temp root and still nothing.
So i did what I do best and tweaked the .bat a bit and added automatic OC scripting. Only reason I am making this thread is to help those who could not fix FULL temp root. With this I was able to always run TiBu and SetCPU no probs. I achieved this by added the ./fixsu.sh into the /bat into /vendor/bin.
There is a point where it says you HAVE to wait ten seconds... You do. I do the whole root process with my screen off just to be safe. If it reboots your phone, it means the CPU was active while you tried to alter its settings.
Also, I went ahead and added the commands to push LKM right after ROOT, and made it scale up to my highest stable undervolted frequency. Note: you can change the settings within the .bat if you want higher/lower freqs+uV. [scpll_l_val=[B]32[/B] is the frequency step. 33 is 1.8GHz and 37 is 2.0GHz(good luck! haha). 37 IS the highest you can try. vdd_uv=1320000 is the voltage. If you try anything 1188000 or below you will be locked to stock clock settings. Stock voltage is 1188000, afterall....
Thanks to coolbho3000 for the LKM (and SetCPU of course, GO BUY IT FOR HIM, he deserves the $$$). And thanks to teamwin for the root... and thanks to
eugene373 for sharing about /vendor/bin.
This is probably what you wanna read
So much text for such an easy process. JUST run the .bat Press any key when it says... READ what it says afterwards [wait 10 seconds with no activity AND screen OFF]... Press a key to continue. Go to SetCPU and Overclock. This WILL make all your programs have permanent temporary root (if you reboot you must reroot!)
Update:Ok then. I went ahead and added another .bat file which is for people who DON'T want anything auto uninstalled (which is honestly just [email protected]@)
adb shell rm -r /system/app/slackerradio.apk
adb shell rm -r /system/app/TMOUS_Navigator.apk
adb shell rm -r /system/app/Transfer-pyramid-8.30.0.26-S30.apk
adb shell rm -r /system/app/Protips.apk
adb shell rm -r /system/app/Protips.odex
adb shell rm -r /system/app/IdleScreen_Stock.apk
adb shell rm -r /system/app/IdleScreen_Stock.odex
adb shell rm -r /system/app/HtcTipWidget.apk
adb shell rm -r /system/app/HtcTipWidget.odex
adb shell rm -r /system/app/com.htc.TrendsWidget.apk
adb shell rm -r /system/app/com.htc.TrendsWidget.odex
adb shell rm -r /system/app/com.mobitv.client.tmobiletvhd.apk
adb shell rm -r /system/app/FusionStockWidget.apk
adb shell rm -r /system/app/FusionStockWidget.odex
adb shell rm -r /system/app/Stock.apk
adb shell rm -r /system/app/Stock.odex
adb shell rm -r /system/app/slackerradio.apk
adb shell rm -r /system/app/TMOUS_Navigator.apk
adb shell rm -r /system/app/Transfer-pyramid-8.30.0.26-S30.apk
adb shell rm -r /system/app/Protips.apk
adb shell rm -r /system/app/Protips.odex
adb shell rm -r /system/app/IdleScreen_Stock.apk
adb shell rm -r /system/app/IdleScreen_Stock.odex
adb shell rm -r /system/app/HtcTipWidget.apk
adb shell rm -r /system/app/HtcTipWidget.odex
adb shell rm -r /system/app/com.htc.TrendsWidget.apk
adb shell rm -r /system/app/com.htc.TrendsWidget.odex
adb shell rm -r /system/app/com.mobitv.client.tmobiletvhd.apk
adb shell rm -r /system/app/FusionStockWidget.apk
adb shell rm -r /system/app/FusionStockWidget.odex
adb shell rm -r /system/app/Stock.apk
adb shell rm -r /system/app/Stock.odex
Also, updated the fixsu.sh to be overkill, it will send to both, /data AND /vendor. This is just for those picky phones. Won't have any negative effect on anyone.
Additionally, I found a TEMPSU.BAT in another thread and went ahead and overkilled that one on the pathing too. The tempsu.bat is for those who have issue with SuperUser and/or Force Closes in trying to reach it. First, Uninstall Superuser by using the default uninstaller (clear data first!). Reboot your phone. KEEP the screen OFF. Run the ROOT.bat. After its complete leave the screen off. Then run TEMPSU.BAT. Should be no problems anymore. I came from a LONG line of SuperUser FCs. I could only get one program at a time to get ROOT. Once I got it to work the right at last, it hasn't reappeared. So don't worry.
Click to expand...
Click to collapse
dhoshman said:
Please make a version that is mac compatible PLeeeeaase. At least a linux comp version.
Click to expand...
Click to collapse
View this guys' thread for linux
Get the updated zip on a lower post 1st page
============================================================
tuscani1821 said:
Can't seem to get root to work. When it installs oc it always resets too. I have the screen off like it says. Adb drivers are installed and I can root by other methods just not this one. Maybe the oc voltage is too high that's packed in the script?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I can think of 2 problems. Either you CPU is finicky and won't run on 1.7 (32), or you are pressing 'any key' in too quick of a succession. There will be one prompt for 'any key to continue', then it will pause again with text saying to wait, and THEN press a key again. If you are doing it right and know it, try changing the OC from 32 to 30 (and lower the voltage a bit also). If still doesn't work, do the RUU reflash method and start the script on a fresh install.
bballer71418 said:
On every root method I try I can't get my device to connect. I set up adb on my comp using the unlocker tutorial and it worked on my og evo. Any reason why I can't get adb to connect to ny 3VO?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
If you are using Win7 or Vista (same thing, really) @ 64bit, you have to remember that the drivers for ADB 64bit are not digitally signed. So you will have to press F8 key at your PC startup, then select 'Disable Driver Signature Enforcement. Be sure to go into the Device Manager and ensure you see 'ADB Android Interface' under 'Android Phones'. If you see a triangle with a yellow thing it means the driver is not properly loaded. This is the only thing that will keep ADB from recognizing your phone... That or you have USB Debugging disabled on your phone (Menu>Settings>Applications>Development.
ianoob said:
Been running for almost a day strait now. The only wierd thing is I keep getting the popup saying SetCPU has been granted SU permission every 30sec or so while the phone is in use :s
Edit, before I get flamed... I know I can tell SU not to warn me, but SetCPU has never done this to me except after reboots.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Yea I get it too. The problem is eMMC is making us lose the temp root. But thanks to the original founder, we can add and symlink to /vendor/bin and just have the system reapply the privileges.
fdavila17 said:
Guys which one I'm I suppose to download?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
POST-after OTA
PRE-Before OTA
IF you KNOW that you are doing it all right and are getting errors out the ying yang, read BELOW
ierv69 said:
Could you please tell me a link to download the ruu file..
I'm on 1.11.651.2
Click to expand...
Click to collapse
RUU_Shooter_Sprint_WWE_1.11.651.2_Radio_radio_0.97 .00.0518_NV_SPCS_1.15_release_193503_signed.exe
1.11
Click to expand...
Click to collapse
RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10. 0530_NV_NV_SPCS_1.16_release
Click to expand...
Click to collapse
First do the first RUU... Then go ahead and do the next one. Don't worry about any exploits that may be covered up, the kernel is the same and more than likely nothing else of value was touched... Since it wasn't noticed. Just do it. Then use the POST Ota zip.
worked now didnt it HAHAHAHAHAHAHA
I get a 'file is broken' error on adb.exe. I wouldn't care since I have adb already on my desktop and in my path, but it won't finish extracting files with that file dying. Not sure if it's just me or not.
This is on the pre-ota rar file.
smw6180 said:
I get a 'file is broken' error on adb.exe. I wouldn't care since I have adb already on my desktop and in my path, but it won't finish extracting files with that file dying. Not sure if it's just me or not.
This is on the pre-ota rar file.
Click to expand...
Click to collapse
yea... i see... everytime i upload it gets corrupted... joy...
UPDATE: Reuploaded and fixed... Checked it myself. Enjoy
Thanks for making overclocking dummy proof. I am tired and saw this post after seeing the overclock thread and thinking *that's too much for the morning*.
Good job.
Tilde88 said:
yea... i see... everytime i upload it gets corrupted... joy...
UPDATE: Reuploaded and fixed... Checked it myself. Enjoy
Click to expand...
Click to collapse
Yep, that fixed it. About to check it out. Thanks!
akiradavis said:
Thanks for making overclocking dummy proof. I am tired and saw this post after seeing the overclock thread and thinking *that's too much for the morning*.
Good job.
Click to expand...
Click to collapse
no problem man. Now that I have my phone basically with full Root privs, I dont need to restart anymore. But in the rare event that I HAVE to... It'll be 45 seconds to root and OC with nothing done.
i just wish i could do something about all the hostility in this forum...
i have tried this 2 times now.. the rooting process seems to go fine, but when the damn setCPU app tries to run, it says it cannot access root or whatever.. basically leaving me in setCPU safemode, where nothing can be done.. not sure whats goin on.. tried doing it the manual way before your .bat got uploaded and same stuff happened.. i know i have root cause i can see # in adb shell.. any suggestions.. its the latest SetCPU 2.2.4
EDIT: I think I finally got it.. for some reason, after reboots, superuser didnt uninstall.. so i uninstalled before i ran .bat and i opened titanium backup to check if it would request root from superuser and it did. i then opened setCPU and it requested superuser also.. was able to get it up to 1.8Ghz without shooting any commands. i had to do a autodetect though to get it to recognize correct cpu frequencies.. after that, i ran a full benchmark in Quadrant.. got a 2775!! W00t
Tilde88 said:
So much text for such an easy process. JUST run the .bat Press any key when it says... READ what it says afterwards [wait 10 seconds with no activity AND screen OFF]... Press a key to continue. Go to SetCPU and Overclock. This WILL make all your programs have permanent temporary root (if you reboot you must reroot!)
Click to expand...
Click to collapse
might want to alert people you put in some removal of stock apps - not a big deal cause i looked at your .bat first, but some people may not.
thanks for the script too!
worked first time. And Riggs, yeah, first thing I did was check the bat file and removed the remove lines.
First, thanks for this! Second, I'm not 100% sure, but I think the fixsu.sh file needs changed.. you are pushing busybox/su/etc to /vendor/bin, but fixsu.sh thinks they are still in /data/local/tmp.
If I'm wrong, ignore me... but it's throwing a number of errors that do not seem right..
Thanks again,
Scott
I had the same problem with Superuser. I had to uninstall it before this script would work.
And I wasn't crazy about the app removal lines either.. I removed them from my copy of the script.
Scott
Delvorak said:
First, thanks for this! Second, I'm not 100% sure, but I think the fixsu.sh file needs changed.. you are pushing busybox/su/etc to /vendor/bin, but fixsu.sh thinks they are still in /data/local/tmp.
If I'm wrong, ignore me... but it's throwing a number of errors that do not seem right..
Thanks again,
Scott
Click to expand...
Click to collapse
I noticed error when that part of process went thru in .bat also.. returned with error that no such file or directory exists... But last run of .bat though, went thru as far as setCPU n titanium backup..
:Sent from my EVO 3D:
Here are some screenies of setCPU n Quadrant score after running .bat n getting it OC'd.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:Sent from my EVO 3D:
Flawless! Can't thank you enough.
DDD-EVO
Does this wrk on a MAC
Sent from my PG86100 using XDA Premium App
drewski83 said:
Here are some screenies of setCPU n Quadrant score after running .bat n getting it OC'd.
:Sent from my EVO 3D:
Click to expand...
Click to collapse
Same here but no go with Titanium B, oh well.........
i ran the early version of fr3vo, then the one from yesterday (with /vendor/bin), then this one early morning. fr3vo and this script have given me titanium backup/msl reader working.
1728mhz good -- 2179 on quadrant.
edit: barnacle not working at all. i can see the ad-hoc network but im unable to connect/get an IP.
Best Permanent Temp Root so far... Thanks Bro!
Guys which one I'm I suppose to download?
Sent from my PG86100 using XDA Premium App
OC!!!
HI, Everything went fine, I have almost all my root apps working fine. But When I go to SetCPU thr freq is 1188 and the min I put it on 192000.. Cant make the max go more..Please help!!!!
Hey guys,
I know A LOT of the new users want to use mods and theme things now that they are newly rooted on ND7 4.4.2. So I was trying to think of a way to make it easier to do so, one being deodex. For us who are unlocked, we develop and theme mostly on deodex system's. So lets get to the guide.. This will make all your apps in system/app and system/priv-app Deodex, therefore you can theme them and head over to my Mods Thread and take advantage of them!
Prerequisites:
PC
Android SDK and/or ADB
USB cable
Patience
First make sure you have USB Debugging enabled on your device (Go into About Device in Settings, Find Build Number, Hit it 8 times until you unlock developer settings. Go into Developer Settings..Scroll down.. Enable USB debugging) Let make sure ADB is setup correctly and working.. Open a cmd prompt where you installed ADB (If SDK it should be C:\SDK\platform-tools\) type:
Code:
adb devices
Your return should look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it does NOT look like this you need to either enable USB debugging, Grant the PC access to the phone or look up some guides on getting ADB started.
So once we know ADB works, lets download the zip I provided with the apps. These are pulled straight from ND7 Stock tar and Deodex by me, there should be no issues. I want you to extract them to your PC. Now lets make some folders on your internal sdcard(Use a root explorer/file explorer):
Folder names:
deodex_app
deodex_priv-app
Once you made the folders go ahead and copy the apps in their correct directory. App goes in deodex_app and Priv-app goes into deodex_priv-app.
When this is finished its time to start the ADB commands..
So we should already have our device connected and adb working with the return device serial number. Lets execute some cmds. After each line hit ENTER:
Code:
adb shell
su ([COLOR="Red"]MAKE SURE YOU GRANT SU PERMISSON!![/COLOR])
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodex_priv-app/* /system/priv-app/
rm /system/priv-app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
**BE SURE TO PAY ATTENTION TO YOUR COMMANDS...SPELLING AND SPACES ETC..
Once rebooted your device should update all apps..You should be Deodex and ready to do whatever your heart desires!!
Happy Theming! Any ?'s just post and ask! Want to learn how to Theme??? Head to this THREAD!!
PS: You want frameworks as well? Do this:
Download this zip, extract it, make a folder on your sdcard: deodex_frame. Copy unzipped contents to that new folder. Start ADB:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_frame/* /system/framework/
rm /system/app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
Should update and be good to go! Enjoy!
@KennyG123 would mind making this sticky?? THANKS!
awesome, I've been using wanam xposed and love the outcome however there are still a few system ui errors. gonna try this and see what I get.
thanks
Sent from my SCH-I605 using Tapatalk
lacoursiere18 said:
Hey guys,
I know A LOT of the new users want to use mods and theme things now that they are newly rooted on ND7 4.4.2. So I was trying to think of a way to make it easier to do so, one being deodex. For us who are unlocked, we develop and theme mostly on deodex system's. So lets get to the guide.. This will make all your apps in system/app and system/priv-app Deodex, therefore you can theme them and head over to my Mods Thread and take advantage of them!
Prerequisites:
PC
Android SDK and/or ADB
USB cable
Patience
First make sure you have USB Debugging enabled on your device (Go into About Device in Settings, Find Build Number, Hit it 8 times until you unlock developer settings. Go into Developer Settings..Scroll down.. Enable USB debugging) Let make sure ADB is setup correctly and working.. Open a cmd prompt where you installed ADB (If SDK it should be C:\SDK\platform-tools\) type:
Code:
adb devices
Your return should look something like this:
View attachment 2945524
If it does NOT look like this you need to either enable USB debugging, Grant the PC access to the phone or look up some guides on getting ADB started.
So once we know ADB works, lets download the zip I provided with the apps. These are pulled straight from ND7 Stock tar and Deodex by me, there should be no issues. I want you to extract them to your PC. Now lets make some folders on your internal sdcard(Use a root explorer/file explorer):
Folder names:
deodex_app
deodex_priv-app
Once you made the folders go ahead and copy the apps in their correct directory. App goes in deodex_app and Priv-app goes into deodex_priv-app.
When this is finished its time to start the ADB commands..
So we should already have our device connected and adb working with the return device serial number. Lets execute some cmds. After each line hit ENTER:
Code:
adb shell
su ([COLOR="Red"]MAKE SURE YOU GRANT SU PERMISSON!![/COLOR])
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodex_priv-app/* /system/priv-app/
rm /system/priv-app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
**BE SURE TO PAY ATTENTION TO YOUR COMMANDS...SPELLING AND SPACES ETC..
Once rebooted your device should update all apps..You should be Deodex and ready to do whatever your heart desires!!
Happy Theming! Any ?'s just post and ask! Want to learn how to Theme??? Head to this THREAD!!
PS: You want frameworks as well? Do this:
Download this zip, extract it, make a folder on your sdcard: deodex_frame. Copy unzipped contents to that new folder. Start ADB:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_frame/* /system/framework/
rm /system/app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
Should update and be good to go! Enjoy!
@KennyG123 would mind making this sticky?? THANKS!
Click to expand...
Click to collapse
So do you copy the the contents of deodex_app/app to deodex_app on the phone or do you copy the app folder itself to the phone
sergeptx said:
So do you copy the the contents of deodex_app/app to deodex_app on the phone or do you copy the app folder itself to the phone
Click to expand...
Click to collapse
Unzip it and there should be a /app and /priv-app folder.. Make a folders called deodex_app and deodex_priv-app on your sdcard.. open those folders and copy the contents(the actual apps) inside of those folders
lacoursiere18 said:
Unzip it and there should be a /app and /priv-app folder.. Make a folders called deodex_app and deodex_priv-app on your sdcard.. open those folders and copy the contents(the actual apps) inside of those folders
Click to expand...
Click to collapse
Thanks.... gonna try it
Could you just copy and paste using a root explorer as well
Sent from my SCH-I605 using XDA Free mobile app
dillonorden said:
Could you just copy and paste using a root explorer as well
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Nope..
Don't know what I did wrong but I'm stuck at the verizon boot logo...
Only thing I did different was created folders on internal storage on pc instead of using root browser on phone.
Nice write up lacoursiere18, worked like a charm. :good: thanks for the deodexed files
got the apps and priv-apps deodexed fine but, when I get to the part for framework the copy goes fine but when I do rm /system/app/*.odex it fails and says no .odex found. Should it be rm /system/framework/*.odex ??? Seems to have worked, don't see any odex files. Thanks for the write up!