Related
I owe much credit to toastcfh, none of this would be possibly without his work on originally rooting the EVO.
Getting Root & Recovery Mode
(My version, dumbed down even more)
You have three options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support
3) Unrevoked Root Patch - No system access in recovery (can't remove sprint apps, etc)
To get a rooted stock ROM, you have to start with Toasts, instructions below; you can find details after.
If you want the Unrevoked Root patch, install a file browser on your EVO and install this.
1. Copy this to the root folder of the SD card, you can do this by syncing the Evo as a disc and just copying in windows.
2. Shut off the Evo, and hold the "volume down" button while powering it on until you see a white screen. Every question it asks, just answer yes. DO NOT UNPLUG, let it finish at all costs, no matter how long it takes.
3. Rename the file you copied to the SD card. (to avoid accidental re-flash and save it for later)
4. Download this and unzip to anywhere of you liking on your desktop. Run the setup, if it asks to accept and install a bunch of stuff, hit cancel, you wont be needing most of it. Select available packages and it will show a repository url, the actual url is irrelevant and will be google's be default...we want to expand the list and select SDK Platform 2.1. Accept an install the selection.
What you just did is installed the Android SDK which includes adb, a shell connector for your phone that we need to operate in recovery mode.
5. Hold the Windows key and press "R", type CMD in the run box. (Run the task with Administrative privileges if there is an option)
Type "cd " in the CMD window, do not forget the trailing space, it is important and DO NOT HIT ENTER yet.
Now, with that CMD windows open, go to the folder you installed the android sdk. There will be a "tools" folder, drag the tools folder into the cmd window.
Press enter, this will set your working directory to the tools folder.
6. If you have not installed drivers for your Evo, there is a folder that comes of the sd card called "HTC-Sync", run the setup in there and it will install sufficient drivers automatically.
After drivers are setup sync the phone using the HTC Sync mode, this will ensure we can control the phone using adb.
Go to your CMD window and type "adb reboot recovery", you will see your phone reboot...it will show a red warning icon on the screen afterwards, this is perfectly normal and good to see such.
7. Your phone should not be in recovery mode, but the filesystem will be offline. Download this to setup the shell for us before we can mount the filesystem. Run "recovery-windows.bat", if you are using Vista or Win7, make to sure right click the file and "Run as Administrator"...you will see another CMD window popup and do some work, just leave it open. You should now have the shell setup in Recovery Mode on your Evo.
8. Go back to your original CMD window we setup, type "adb shell" and hit enter, this will set all commands to work right on the phone. You should see a line with just "#", that is what we want.
Now type "mount /dev/block/mtdblock4 /system" and hit enter.
You should now have your Evo in recovery mode with a shell setup and filesystem mounted. This is where we can begin making changes.
Now that this has all been setup, you may want to go back after making some changes.
Repeat steps 5-8 to re-enter recovery mode with the filesystem mounted.
If you want to continue and do the stock update, check here.
Basically, copy that file to the SD and do steps 5-7.
Then use the onscreen (on the EVO Recovery Mode) to "Flash from ZIP" and select the rooted stock rom update.
WARNING: You must clear user data if the update creates issue, you will know right away.
so this is a third way of rooting, if i used a different way how do i get rid of it and use yours, i'm so tired and confused.
Post Removed to maintain consistancy, see 1st post in thread.
root rom and activesync?
I'm a complete noob here but: By using this method do I still retain the ability to run ActiveSync/Exchange support? (Didn't think this was in the SDK Platform 2.1)
What about Sense?
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Good noob friendly guide, kinda tldr, but what I did readlooked good!
Change ur title
Neotelos_com;
[B said:
You have two options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support[/B]
....
Click to expand...
Click to collapse
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
adeyo said:
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
Click to expand...
Click to collapse
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
johnsongrantr said:
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Change ur title
Click to expand...
Click to collapse
I have plans for adding in tweaks, which will be delayed a bit...
Sorry for any inconvenience.
Neotelos_com said:
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
Click to expand...
Click to collapse
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Click to expand...
Click to collapse
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Neotelos_com said:
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Click to expand...
Click to collapse
Well thats all kinds of dumb..
I give it a week and there will be something better working.
Nice write up. The only problem is, I don't have the sync software on my sd card because the best buy employee knew about the evo's sd card problem and formatted it, erasing everything on the card. I checked htc's site and they had the drivers for download, but it keeps giving me an error saying it's not compatible. I'm using windows 7 64bit. Any ideas guys?
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Click to expand...
Click to collapse
you CAN remove apps like that, using toast's custom recovery. if you do your shell, and mount, in recovery, using adb, you can go to /system/app and rm whatever you want (be careful not to remove anything important, probably wise to pull whatever first, in case you need to push it back)
i had problems when i did an rm on a file, but that is because apparently i forgot to rm it's info in /data/data too. word to the wise
HTC Sync Torrent
http://thepiratebay.org/torrent/5609530
PLEASE SEED AFTER DOWNLOAD!
New android user here!
So to me it seems like all three have something they're not able to do. Seems best to wait for a root release that your able to take full advantage of, right?
I'm a former WM flasher , I need to learn android still. I want the free hot spot/tethering, more battery life as I need 2 batteries to make it through the day -.- (I kill apps constantly, 4g turned on rarely,ect, ect)
Any feedback is appreciated,
Sean
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
kingcliff00 said:
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
Click to expand...
Click to collapse
Try going to Settings -> Applications on the evo and enable usb debugging...if that5 gives you adb access that's all you need
confirmed working with unrevoked root method. It can tether 3G or 4G, depends on how you connected to the Sprint network. 3G was 0.80Mbps DL, 4G was 2.63Mbps DL.
Before using unrevoked root method, I had applied the sdcard patch already. so it doesn't matter if you applied the sdcard patch or not (OTA updated).
You really shouldn't kill tasks. Just cycle the battery a couple of times and turn your antennas off and on when u need them. Especially if u are in spotty 3g coverage. There already one or two official write ups that say task killing is bad I use to do it and got forceloses and errors all the time. Its not about how many tasks you have running I.e. memory, items about cpu and antenna signal that kills you're battery I'll find the link if I can. My battery life is pretty good and I'm a heavy user.
Sent from my PC36100 using Tapatalk
i cannot get recovery bat file to work. I am at the red exclamation point screen on my evo and i run the bat file as amdmin. it pops up for a second then closes and nothing happens.
Edit: NVM I figured it out. on to the next step.
Hi,
I posted a question in forum about how to connect my A500 tablet to an Ad-hoc networking but after I did some search in the forum I found some steps to solve the issue and it is starting from rooting the device and finalizing by modifying a file in the following path:
sdcard/system/bin/wpa_supplicant
The problem is I can't rename the file (wpa_supplicant) also I can't copy the modified (wpa_supplicant) to the system/bin folder and a message appearing told that this file is "read only" and can not be modified or edited. Note that I used Root Explorer and Root Browser to explore the systems folders.
Please any one can help??
You can't do this because your device is not rooted !
Use Root explorer don't give all super user privilege to your device
my device did not open what shall i do??
As the guy answered, you have to be rooted in order to do that.
Im not sure if you can root tablets, I have never had any interest in this direction because I dont have money to buy one.
But if you can you click on Root explorer, then click mount r/w , go to system/apps.
If it is mounting r/o you can delete system apps, I did that to my SGSII and my battery life lasts much longer.
You also have access to the files that created the applications, the ones you create in Eclipse.If you are a developer , you would know what I'm talkin about.
I dont know any other ways of doing this if you are not rooted and I'm almost sure its not possible, but good luck still.
Im not sure if you can root tablets,
Click to expand...
Click to collapse
You can root tablets, even the a500 as tough as it is to do so. I am running FlexReaper ROM on my Iconia a500 right now. It's flippin' awesome !
As far as editing the system files, the O.P. may need to actually mount the drive as r/w.
In ES File Explorer there is an option to actually mount the file system as 'writable'......(which will be rejected if the device is not rooted).
Do you see any similar option in the file explorer apps you are using ? If so, try to enable it. Just browsing 'up to root' is not enough......at least for ES.
I would use a root check type of app to verify you are up to a 'true root'.
As for custom ROM's the Iconia a500 tab requires flashing with a custom unlocked bootloader and custom recovery image like cwm, then installing/flashing the new custom or stock OTA ROM and any desired app/system packs if needed. The Iconia a500 is pretty tricky, but possible.
If you do go the way of custom ROM's, I HIGHLY recommend the FlexReaper RF-1_rv3 Custom ICS 4.0.3 ROM for users running the Acer Iconia a500 tablet.
Super smooth, and the only custom ROM that doesn't start with a funny snow screen when initially booting up. A couple other ROM's I tried would 'snow' like a bad hardware compatibility issue or something. Flexreaper seems like it is the perfect ROM for the a500, at least for me.
many thanks for all help;
I used an app to check if my A500 is root and it is called "Root Checker" and told me that my device is rooted and I have root access but when I used Root Explorer or Root Browser apps I found there is a button to switch from (r/o) to (r/w) but when i bushed it never changed to (r/w) by the way I used a software to root the A500 from my laptop this software called ( ICS ROOT 2) if this software is not rooting so can anyone tell me about the right way to root my A500 device which it is working on ICS system bcoz really I confused!!
ahmedalbidhany said:
many thanks for all help;
I used an app to check if my A500 is root and it is called "Root Checker" and told me that my device is rooted and I have root access but when I used Root Explorer or Root Browser apps I found there is a button to switch from (r/o) to (r/w) but when i bushed it never changed to (r/w) by the way I used a software to root the A500 from my laptop this software called ( ICS ROOT 2) if this software is not rooting so can anyone tell me about the right way to root my A500 device which it is working on ICS system bcoz really I confused!!
Click to expand...
Click to collapse
I actually used the same method so I am unsure as to what is going on here.
Will read back thru my research and see if I can figure something out. I am still new to this rooting/flashing thing, so I don't want to mislead you. I'd rather find my methods in tangible text online, rather than relying on my fuzzy memory.
I am not sure if this will help, but if you boot into recovery, check if there is an option to fix permissions. Run it then reboot normally.
Should be under the Advanced header.
IMOP,your Root explorer manybe havent get the right from super user.
Or,there is a problem with the root app.
My A500 rooted with the method instead of official Recovery.
@ Valkillmore : thank you for your support I'll try this method and comeback again and post the results
Root + SSH + remount
Here's how I do it.
1) Root your device.. lots of tips on this in the forums and the process depends on your specific phone model.
2) Install SU super user access.
3) SSHDroid - Install from market and allow root access (via SU)
4) Turn on SSHDroid and login to it via an SSH client from your computer (see putty for windows, Linux, Unix , and MAC should have it already).
> ssh [email protected] (for example)
5) remount the system drive (it is typically mounted as read-only
> mount -o remount,rw /system
Then you can go ahead and modify files under /system folder. Note: when you reboot, /system will be mounted normally (read-only).
i had the same issue
i had astro file manager, it doesnt have complete root access.
downlaod efs explorer
go to settings
allow "up to root" click allow when super user dialog box pops up
select "mount" right under "up to root"
then go to efs explorer main manu press the "up" tap
navigate to wherever you want. bne carefull with what you change.
i was changing the APN settings on my evo
I know how to root devices but whenever someone ask me what is rooting i am not able to explain it :-\ anyone got idea about how to explain rooting
Sent from my GT-I9100 using xda premium
ankur.co.in said:
I know how to root devices but whenever someone ask me what is rooting i am not able to explain it :-\ anyone got idea about how to explain rooting
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Rooting is opening the operating system to be alerted.
Sent from my Rooted Gameboy
Rooting allows you to run special applications like SuperUser, SetCPU. Allows you to flash custom kernels and ROMs like cyanogen mod. Also you free up memory that extra apps use.. In easy language, you get full access to everything..
Sent from my GT-I9300 using xda premium
If you want the most complete, hands-on way to control what your phone is capable of...it's best to root it. Rooting gives you access to manipulate your phone in a way that carriers try to keep you from doing.
Sent from my SGSIII running some "Goodness" 4.0 (Team Nocturnal) using xda app-developers app
Allow you to backup & access apps/info/data etc that no root phone cant.
ankur.co.in said:
I know how to root devices but whenever someone ask me what is rooting i am not able to explain it :-\ anyone got idea about how to explain rooting
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Rooting is the act of gaining superuser access(root permissions) to the root(main files) of the device's operating systems, letting apps run at kernel level. Rooting allows for overclocking, however, in Jelly Bean, root is not required to overclock. Overclocking is the most frequently used root application. Root also lets you change system files.
Here is rooting for all you noobs
Basically every linux system has an administrator capable of making changes to the computer and access all the files that make the system up. On Mobile phones however, this is locked down for security/warranty reasons etc.
This is a great start, we know that the admin (root) access is there, we are just locked down from using it. So the point of rooting is not to install Super User, it is to trick the system into giving us adb shell as root and therefore allowing us to mount the /system partition as Read/Write (instead of read only).
That is what allows us to change the value of ro.secure in the kernel, which sets the flag that allows us a root shell, instead of a regular (non-privileged) shell. Then we push the SU binary and SU app to the system, which gives us choice as to what apps are allowed su rights and what is not. In other words, we don't need the SU app to obtain root access. It is just for data protection.
It sounds so simple, but it is not. Since the /system partitions cannot be mounted as read/write by default, and ro.secure=1, we cannot have a root shell and therefore not able to change ro.secure=0. Therefore, it is secure.
In order to gain the root shell we have to find an exploit that will trick the system. We use an exploit (hack, vulnerability) to trick the android OS into giving us a root shell in adb. For example on of them (in simple terms is...)
1. We kill adbd ***(this is the parent) It spawns a shell (adb) based on its rights*** keep this in mind.
2. When it adbd starts up, it must run as root. When its done, it will set its id back to a non root user
3. The program (SuperOneClick for ex) races adbd by spawning a process that tries to change its id at the same time (slightly first).
4. Since we are busy changing the id of our fake process, the kernel wont be able to change adbd since it is busy and therefore adbd continues to run as root.
5. Now we can spawn a root shell, because the root rights are passed from adbd to the shell, which is now root.
6. Sucess! Now lets set everything up!
This has been answered about as well as it can. For future reference, please try searching before posting as extremely basic questions like this do not warrant creating a thread. Closed.
Have a question about the mount settings in my recovery. I know that target box means it is mounted/RW and untagged is unmounted/Ro. But my /system partition keeps getting set to Ro and when i need to flash things it needs to be on RW. Is that bc my device is Samsung and thereforth has protected bootloader set? I'v been reading trough script files and think i can adjust some of them so they mount as RW instead of Ro. I know that /system is set to RO bc of safe against accidental alteration/removement. But it would be much easier to flash or install updates/programs/apps/etc that way. Hope anyone can give some advice for me.
P.S. i use the ROM Toolbox Lite Scripter bc it has a lot standard scripts already and changing them is easy. And u can just copy that script into an Terminal Emulgator thats rooted and then run it to alter/install it so u can read back whats been changed?
A. Nieveen said:
Have a question about the mount settings in my recovery. I know that target box means it is mounted/RW and untagged is unmounted/Ro. But my /system partition keeps getting set to Ro and when i need to flash things it needs to be on RW. Is that bc my device is Samsung and thereforth has protected bootloader set? I'v been reading trough script files and think i can adjust some of them so they mount as RW instead of Ro. I know that /system is set to RO bc of safe against accidental alteration/removement. But it would be much easier to flash or install updates/programs/apps/etc that way. Hope anyone can give some advice for me.
P.S. i use the ROM Toolbox Lite Scripter bc it has a lot standard scripts already and changing them is easy. And u can just copy that script into an Terminal Emulgator thats rooted and then run it to alter/install it so u can read back whats been changed
Click to expand...
Click to collapse
Usually, the ROM updater script will mount/unmount system. I do not know if that is the case here.
Currently running a OnePlus 8T + 5G with unlocked/TWRP bootloader which is not rooted, since neither of the two methods want to work on my specific version (KB2007; unlocked former T-Mobile).
Anyway, I'm trying to switch to another ROM but I'm wondering how best to backup/restore all of my apps. Loved using Titanium Backup way back in the day, but am I still correct in assuming that it doesn't work correctly without root access? If so, are there any non-root methods of backing up all or most of my apps along with their current configurations/etc to restore into the new ROM once it's installed? Obviously, most ROMs will support doing it through Google Play, but then it takes forever to log back in to each app, set it all back up, etc. If I've been missing some basic way of restoring all the apps with their configurations intact, please feel free to smack me upside the head with the answer =)
And my apologies in advance if I'm misusing any of the terminology. Before this phone, it has been at least five years since I even tried rooting/unlocking/etc, so I'm a bit rusty.
In the world of computers an app belongs to person who installed it, app's data are owned by the app itself.
Hence it should be obvious that only an user with elevated rights ( AKA Superuser or Root ) can perform a backup and/or restore.
Take note that a temporary root is enough to do the jobs.
Got it. So, in other words, figure out how to root the phone despite the troubles I've been having trying to do so. Unless there's some sort of temporary root privs available that I've never heard of?
To get a temporary root all you have to do is to add to Android OS the binary called SU
Example
Code:
adb push <LOCATION-OF-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
what then allows you to run Android shell commands when elevated rights are needed
Example
Code:
adb devices
adb shell "/data/local/tmp/su -c '<SHELL-COMMAND-HERE>'"
Am I correct in assuming that SU is the same as "switch/substitute user" in *nix? Does that mean I can run TB from the ADB shell, assuming I include the correct command line arguments? Something along the lines of doing a SUDO in *nix before running something that requires admin access or whatever.
I know this might be quite different from what you're looking for maybe?
In the future if you get a rooted rom, I use something called Migrate from the play store, it requires root and just copies all your data into a bunch of twrp flashable zip files.
Play Store
silentrawr said:
Am I correct in assuming that SU is the same as "switch/substitute user" in *nix? Does that mean I can run TB from the ADB shell, assuming I include the correct command line arguments? Something along the lines of doing a SUDO in *nix before running something that requires admin access or whatever.
Click to expand...
Click to collapse
SU in root context usually means super user, as a user with all privileges, but it's the same thing as super user, so yes.
Hello Everyone,
I too am interested in a backup solution for my Android smartphone.
I would happily root or temporarily root, but despite having a computer background that dates back to Unix, I am an Android novice and do not know how to perform these operations which to most people here seem elementary.
Could someone please point me to an easy to understand primer on either temporary root or permanent root.
I would be very appreciative and I am sure that there are other readers of this post who would benefit as well.
Thank you.
AndroidNewbie9000 said:
Could someone please point me to an easy to understand primer on either temporary root or permanent root.
I would be very appreciative and I am sure that there are other readers of this post who would benefit as well.
Thank you.
Click to expand...
Click to collapse
The thing is, that the "official" way to root a device nowadays usually includes a wipe of all user data. You basically have to decide that you want to do full backups before you use an app. This is a security measure so that an attacker cannot use the official way to e.g. access app-internal data on a stolen phone, like secret tokens of 2FA-apps. In order to backup existing app-internal data you either need to use the per-app-backup that the creators of that app did hopefully include or hope that the allowed to do adb backup. That can be used without root, but depending on your Android, apps either need to allow this explicitly or at least not explicitly disallow that in their manifest file.
In principle you can use exploits for non-official rooting to backup existing data that is blocked from adb backup - but this is only an option if you do not have the latest security updates in place and an exploit is publicly available.