Related
Hello,
I only want to install some apps from the market (setcpu, market enabler and root explorer,...) that requiers root access.
So what do I have to do? Is it enough if I just unlock my bootloader with the tool on htcdev.com?
Which way of rooting my device would you recommend me?
I use an evo 3d gsm (eu version).
thx for the help
Honestly I go with the root posted here in xda, my friend rooted with the HTC method and has had some wierd stuff going on ( no roaming or 3g) I've had my phone rooted with the method given here on xda and haven't got any problems.
MettlerNikola said:
Hello,
I only want to install some apps from the market (setcpu, market enabler and root explorer,...) that requiers root access.
So what do I have to do? Is it enough if I just unlock my bootloader with the tool on htcdev.com?
Which way of rooting my device would you recommend me?
I use an evo 3d gsm (eu version).
thx for the help
Click to expand...
Click to collapse
The main limitation to modifying anything on our device is the internal memory write protection HTC has installed.
There is a temporary method, which will work on previous system software versions to get root acccess, traditional out of bounds exploit, fre3vo.
This will have to be run after each boot to get root access as it does not unlock the internal memory write protection, hence the term temporary root.
In order to unlock the internal memory write protection, so our modifications to the system persist past reboot, we have to run of two unlock methods, revolutionary or htc.
Personally, I ran revolutionary and will probably still continue to do so as it unlocks more of the internal memory more of the time.
If you're looking to follow the *official* route, you'll probably want to use the HTC method. This method is semi new and I haven't personally used it. I only speak from experienced gained through others posting their experiences. If I leave something out, I'm sure somebody will correct me.
The official htc dev method should unlock the write protection at least while in the bootloader and fastboot mode where you can flash a custom recovery and/or custom kernel. Once you have a custom recovery loaded, you can boot into recovery mode, where the internal memory write protection on the /system partition is disabled and make changes to the system, i.e. install an su binary or Superuser.apk (has its own su binary) to provide root access to Android applications.
After you've installed either the su binary, or the Superuser.apk, my application called Root Check is free in the android market and the advanced mode will provide all the details either confirming a proper installation or highlighting the area with issues.
I'm sure there is a guide around here .. I probably should have linked to it rather than write out the process ... lol
Hope that helps and best of luck!
Assuming you have the 1.5 HBoot? If so I dont really know anything about that...I wouldnt use HTCs method.
If you have an Hboot before 1.5 just use unrevolked.
S-Off does not mean you have root BTW it just means you can flash stuff. Once you have S-Off you have to flash super user to get root access.
I am using superSU, and I need temporary unroot to try and fix my issue with google Wallet.
However, I can't find the option called "Temporary Unroot"! I have searched XDA and also done a general google search. the feature is mentioned all over the place, but nowhere does anybody explain where it is or how to access it.
In SuperSU, under settings, I found the option to enable or disable "superuser", but that's all. Is that it? Confused.
You can use an app called ota root keeper I believe to do what you want.
leebo said:
I am using superSU, and I need temporary unroot to try and fix my issue with google Wallet.
However, I can't find the option called "Temporary Unroot"! I have searched XDA and also done a general google search. the feature is mentioned all over the place, but nowhere does anybody explain where it is or how to access it.
In SuperSU, under settings, I found the option to enable or disable "superuser", but that's all. Is that it? Confused.
Click to expand...
Click to collapse
Yes, that's it.
Thanks Captain.
Since my post I've seemed to have screwed up my Build.prop file and now it won't boot. I hope that $10 from Google Wallet will be worth it! Ha.
Yes, Disable SuperUser is the correct option within the app. If you have already opened Walletbthen you will need to disable then reboot. Now in terms of the OTA Updating and trying to OTA you can use SuperSU Pro and enable before OTA but disable BEFORE BackUp within Recovery
Brought To You By TapTalk 2 Via LTevo
EPayne123 said:
Yes[...] Now in terms of the OTA Updating and trying to OTA you can use SuperSU Pro and enable before OTA but disable BEFORE BackUp within Recovery
Click to expand...
Click to collapse
Thank you, I was looking for this exact thing !
But I don't understand the last part, about backupenavke what? why pro ? and how strong is recommended a backup for a simple Ota From 2.2 to 2.3
??
leebo said:
I am using superSU, and I need temporary unroot to try and fix my issue with google Wallet.
However, I can't find the option called "Temporary Unroot"! I have searched XDA and also done a general google search. the feature is mentioned all over the place, but nowhere does anybody explain where it is or how to access it.
In SuperSU, under settings, I found the option to enable or disable "superuser", but that's all. Is that it? Confused.
Click to expand...
Click to collapse
if you or anybody else coming across this thread is interested in the technical details around how this works, the process is very simple with some background knowledge.
there are two elements in play when an application, such as Google Wallet, or any other application attempts to verify whether or not the device has root access. It can directly attempt to issue the "su" command see if it gets returned elevated privileges, or it can look for the su binary to be specifically located in /system/bin or /system/xbin.
based on the methods used to determine root access, you can "temporarily" unroot by moving/renaming root access away from the standard location.
example:
adb shell
su
mount -o remount,rw /system /system
mv /system/bin/su /system/bin/backupsu
mount -o remount,ro /system /system
exit
now root access has been moved and android apps requiring root or searching for root access won't be able to locate it. when you want to restore root access, follow these steps based on the example above:
adb shell
backupsu
mount -o remount,rw /system /system
mv /system/bin/backup /system/bin/su
mount -o remount,ro /system /system
exit
these steps will moved the su binary back to the standard location. hope that helps provide some insight and detail to the process!
EPayne123 said:
Yes, Disable SuperUser is the correct option within the app. If you have already opened Walletbthen you will need to disable then reboot. Now in terms of the OTA Updating and trying to OTA you can use SuperSU Pro and enable before OTA but disable BEFORE BackUp within Recovery
Brought To You By TapTalk 2 Via LTevo
Click to expand...
Click to collapse
^^^
Doesn't work on N7100 with or without rebooting after unchecking the box.
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
hx4700 Killer said:
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
Click to expand...
Click to collapse
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
weakenfalls said:
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
Click to expand...
Click to collapse
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
hx4700 Killer said:
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
Click to expand...
Click to collapse
I get # in ADB but not using Terminal Emulator. What does this mean?
Restorer said:
I get # in ADB but not using Terminal Emulator. What does this mean?
Click to expand...
Click to collapse
Hmmm I will have to try in ADB and see what happens.
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
hx4700 Killer said:
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
Click to expand...
Click to collapse
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Restorer said:
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Click to expand...
Click to collapse
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
hx4700 Killer said:
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
Click to expand...
Click to collapse
I get:
"mount: Operation not permitted" .
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Sorry, just tried again and now stage 11 is working! But then when I try 12 I get:
"r.apk of=/system/app/Superuser.apk
/data/local/tmp/Superuser.apk:cannot open for read: No such file or directory
1:[email protected]:/#"
re root jellybean
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Whooo! Just got my root back. I hadn't realised there are a couple of typos in the guide there and I was copying and pasting the long lines!
Big thanks to hx4700 Killer for making me wonder I must be doing something wrong :laugh:.
tomtomxp said:
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
Click to expand...
Click to collapse
Well.. I believe that everyone who'd not consider unlocking their tablets before the JB update would not unlock after losing root just because of the warranty, probably not because they don't know how but because about half of the forumers don't think it's worth the risk considering the hardware instabilities like the green camera module, light bleed etc.
And since you've already flashed a custom recovery you've unlocked more than just root, why not try a custom ROM based on stock JB?
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
ToBe_HH said:
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
Click to expand...
Click to collapse
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
sangalaxy said:
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
Click to expand...
Click to collapse
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
I don't think you can root without any pc
If your phone has recovery just flash the root files :thumbup:
Sent from my Xperia Live with Walkman using xda app-developers app
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
Have you tried looking in /system/bin/su instead of /system/xbin/su
I've got a device and need either root or su for system app development, but want to do this in the least invasive way possbile. The twist... this is likely a pre-release device and came from HTC with S-OFF (HBOOT-1.01.0000).
With S-OFF (but no root) what are the options for getting root and/or SU installed?
pukebag said:
I've got a device and need either root or su for system app development, but want to do this in the least invasive way possbile. The twist... this is likely a pre-release device and came from HTC with S-OFF (HBOOT-1.01.0000).
With S-OFF (but no root) what are the options for getting root and/or SU installed?
Click to expand...
Click to collapse
Least invasive: Install superuser/su from adb, leaving stock recovery in place. LMGTFY: http://www.equisoforum.com/Thread-ADB-Shell-Pro-Root-method
Better route: Flash CWM or TWRP recovery to phone, then flash superuser/su package from recovery.
junkmail9 said:
Least invasive: Install superuser/su from adb, leaving stock recovery in place. LMGTFY: no_urls_from_noobs
Better route: Flash CWM or TWRP recovery to phone, then flash superuser/su package from recovery.
Click to expand...
Click to collapse
(please forgive if anything I have below is nonsense... I'm slowly building my understanding)
I don't believe the 1st method will work. I can't 'adb remount' because I don't have root on the device ('remount failed: Operation not permitted'). If remount worked I'd be good, because as you suggest I could push the su apk/permission/scripts to the device. I also tried remounting the /system partition as RW but no luck ('mount: Operation not permitted').
I'll try the 'traditional' CWM route. I just wasn't sure if having S-OFF opened up any other options for getting root, mounting /system as RW, or...
Thanks much.
pukebag said:
(please forgive if anything I have below is nonsense... I'm slowly building my understanding)
I don't believe the 1st method will work. I can't 'adb remount' because I don't have root on the device ('remount failed: Operation not permitted'). If remount worked I'd be good, because as you suggest I could push the su apk/permission/scripts to the device. I also tried remounting the /system partition as RW but no luck ('mount: Operation not permitted').
I'll try the 'traditional' CWM route. I just wasn't sure if having S-OFF opened up any other options for getting root, mounting /system as RW, or...
Thanks much.
Click to expand...
Click to collapse
I have always used the "Better Route". However, I was under the impression that s-off unlocked the partitions.
Out of curiosity, did you try the following command anyway: (adb push su /system/bin) ?
junkmail9 said:
I have always used the "Better Route". However, I was under the impression that s-off unlocked the partitions.
Out of curiosity, did you try the following command anyway: (adb push su /system/bin) ?
Click to expand...
Click to collapse
At least in this case /system is mounted RO:
- adb shell mount | grep system -> /dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
- adb push foobar.txt /system/bin -> 'failed to copy foobar.txt to /sytem/bin/foobar.txt : Read-only file system
This isn't a regular consumer device so it's at least a little funky. For example, it doesn't get OTA updates and is stuck with an old RUU (htc sense 4.0... ruu 1.31.605.1 (? not sure where exactly to get RUU version). It also has the 'normal' CID (VZW__001).
It might get a little interesting digging up workable bootloader and supercid method, now out-of-date for basically everyone else.
pukebag said:
At least in this case /system is mounted RO:
- adb shell mount | grep system -> /dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
- adb push foobar.txt /system/bin -> 'failed to copy foobar.txt to /sytem/bin/foobar.txt : Read-only file system
This isn't a regular consumer device so it's at least a little funky. For example, it doesn't get OTA updates and is stuck with an old RUU (htc sense 4.0... ruu 1.31.605.1 (? not sure where exactly to get RUU version). It also has the 'normal' CID (VZW__001).
It might get a little interesting digging up workable bootloader and supercid method, now out-of-date for basically everyone else.
Click to expand...
Click to collapse
If you're already S-OFF, you shouldn't need to do anything with supercid. Just put the phone into fastboot and flash a custom recovery - either CWM (link) or TWRP (link), depending on your preference. Follow the "manual installation" steps in the thread of your choice. I have been very happy with PhilZ's Touch CWM.
Also - first thing to do after installing the recovery is to make a nandroid backup of the (semi) pristine state of your phone.