Is anyone else in the same boat as me, where they updated prior to instructions reading to move SU to xbin????
I have the SU in my app drawer, I have loaded setcpu and other root programs like barnacle, but I CANNOT for the life of me get the other half of the root apps to work because it says I DO NOT have SU permissions.... like Root Explorer for example.
I wouldn't mind sbf'n it back to 2.1 and then back to 2.2 again at all, just not quite sure what to do.... an ideas?
I was in the same boat as you after upgrading to 2.2 even though I thought I did the xbin step correct, guess not.
Anyways, the only way I fixed it was to completely flash my phone, I didn't mind doing this because it's always nice to start with a fresh install.
This guide was the best for me, simple and includes all necessary links.
http://forum.xda-developers.com/showthread.php?t=758907
Make sure you have busybox installed. There is an appliaction in the market that will download it..
Sent from my DROIDX using XDA App
If you didnt move su to xbin, you will HAVE to sbf your x and redo everything to get 2.2 with root. Thats what happened to me.
I did this also...half root and stuff. I used astro to install the su apk off my sd card. I didn't have the ninja guy in my app drawer though. But could run set cpu. Not root explorer. I just again installed the su apk from sd. And it showed up in my app drawer. And I was able to install root explorer. Just my 2's
Sent from my DROIDX using XDA App
A fix without adb
To anyone that has run into this problem I have a solution. This is for everyone that missed the step on keeping your root access. If you have su in xbin and still won't work this will work for you.
(Open terminal emulator) type the following:
/system/xbin/su
Then you should see a #
Run "mount -o rw,remount /dev/block/system /system"
Run "mv /system/bin/su /system/bin/su.bak"
Run "cd /system/xbin/"
Run "cp su ../bin/"
Then you should have your root access again!
and one more thing, don't type the word run or put the " " in this code
Same thing happened to me as well, I SBF'd back the first run and did everything EXCEPT the moving su to xbin, and well.... I had to do it all over again, took a bit of time, but now root works again.
Chris
So on my Epic 4G, I preferred to do the manual root process of using the rageagainstthecage-arm5.bin exploit and then setting up the permanent root by putting some joeykrim scripts in place (joeykrim-root.sh, jksu, and playlogo alterations). This worked perfectly for me on stock.
So I downloaded the Froyo EB13 update.zip from Samsung today and went to install it. First time failed because it wanted to patch playlogo, but I had the root version in place. So I put the original back in place (un-rooting the phone, I think), and ran the update again and it worked fine. Didn't lose any of my apps.
So I go to re-root it using my old files, and I can't get it working now. The rageagainstthecage-arm5.bin exploit still works fine, but when I put the joeykrim files in place, I don't get su back when I reboot the device. When I go to the adb shell and type su, it reports that su is not found.
c:\Android_root>adb shell
$ su
su
su: not found
Did something change where the joeykrim su replacement doesn't work anymore? Is there another manual root process? I prefer to do it manually if possible.
Thanks!
I prefer to do it manually if possible.
Click to expand...
Click to collapse
why (just curious)?
I feel like I'm more in control of whats going on when I do it manual. Also, at one point I heard there is a higher potential to run into problems when doing a one click process.
Hi
I have rooted my Fire with zergRush and confirmed with adb shell
Code:
# id
uid=0 gid=0
but after rebooting the Fire it seems to have gone as the prompt returned to $
Is this usual?
I'm on a MAC and the Fire is 6.2. I can root again but obviously it would be good if it remained after a reboot.
Any help would be much appreciated
edit: but now I'm not so sure.. SU from adb shell returns 'not found' and when running a terminal app I have on the Fire the prompt is $ and SU returns 'permission denied'.
I'm not really one who should answer this as I'll not really up on the different exploits used for rooting but...
My understanding was that zergRush got you a temporary root which was enough to enable you to remount /system as RW which then let's you install su and busybox and the superuser.apk which then gives you permanent root.
Sent from my Kindle Fire using Tapatalk
Like bsoplinger said,
zergRush is the exploit most are using to gain root, and then while having root allow you to install tools which survive the reboot cycle to continue to provide root from that point on.
Busybox, su and superuser are those tools.
Thanks very much, certainly gives me more to go on although I'm a bit confused as to when I should be installing tools using adb and when I should be using a file manager. Probably neither and I have the wrong end of the stick no probs.. on on
edit: I think I've got it... can't thank you enough your advice has saved me hours I'm sure but I will wait till the morning. I'd rather brick it with a fresh head than the one on my shoulders now.
This did not go exactly as I had planned but it ended up ok anyway and I learned some.
I am using a rooted stock rom. First, my idea was to prevent the auto update to 6.3. Second, I wanted to see if it was possible to somehow preserve root so that I wouldn't have to re-root after the update, because I am not really thrilled by the idea of installing a new boot loader and so on; I would prefer to make the minimum modifications necessary to do what I need.
The first goal appeared to be well-served by using droidwall. I used whitelist mode and blocked everything that I couldn't tell had an obvious need to access the net. I posted more detail here. From the time the update started going out until today when I had time to actually try my update, I did not receive the update automatically. So that appeared to work.
Next, my idea was to simply make a copy of /system/xbin/su to a place that wouldn't get overwritten by the update.
# mkdir /data/lunchmeat
# cat /system/xbin/su > /data/lunchmeat/salami
# chmod 6755 /data/lunchmeat/salami
The idea being that since it's still setuid root, I'd be able to execute it and become root after the update. (I just picked a silly name in case something looked for su and blew it away).
So, I turned off wifi, disabled droidwall, manually updated (copied the updates into kindleupdates and so on) and after it rebooted, I opened the terminal app and tried to execute my salami binary. I got permission denied, and the superuser app said that superuser permission was denied on the terminal app. Hmmm....
Couldn't figure out why it was behaving that way so I thought I'd try adb root, and whadya know, I had a root shell.
remounted /system read-write, copied su back into /system/xbin, renamed /system/bin/check_rooted to /system/bin/check_rootedx, created an empty executable /system/bin/check_rooted, and rebooted...
...and everything is (rooted) as it was before. I re-enabled droidwall. google play seems to be working.
Why did 'adb root' work for me after the update? That might be a good question to answer, since it could make the re-rooting process much simpler for people! 2 or 3 commands and you're done.
edit: ohhhhh, stupid me! /data is mounted nosuid. / seems to get blown away on every reboot, so even if I remount it read/write and put su there, it gets lost.
And, also, I just remembered that I did what jcase said in this post which is what allowed me to keep adb root working.
So, so far this idea is going nowhere.
EDIT:
Go here to root your Tegra Note 7: https://github.com/linux-shield/shield-root/blob/master/README.md (thanks to CampGareth for finding the link).
I have tested this, it works with no bloatware, only installs SuperSu.
---------
Hey guys, I got my new Tegra Note 7 last night and I've been trying to get it rooted, but I keep running into trouble.
First of all, I DO NOT want to use some shady Chinese software that installs a bunch of bloat on both my tablet and PC just to get SuperSu going, I've tried that method and had to reset the tablet to get rid of all the crap it installs (and it didn't even seem to root anyway).
Now I'm trying the manual method from here: http://pan.baidu.com/wap/link?uk=3073396937&shareid=3129426036&third=0
Which, again, is Chinese but at least I can see what it's doing since I'm issuing ADB commands, and supposedly it has worked for others on this forum.
Now, I get to step 3 on the included PDF which says to boot an insecure bootloader image with "fastboot boot tegranote_insecure_boot.img", I do this and the tablet screen flashes a few times and reboots to android.
I get to the next step which says to open an adb shell, and do "/sbin/rootsh +p" to get a temp root shell, and this is where I get stuck. Instead of getting a root shell I get the message "/system/bin/sh: /sbin/rootsh: not found". Does anyone have suggestions?
By the way we really need a Tegra Note 7 subforum here at XDA, if the mods could add it that would be great.
dark42 said:
Hey guys, I got my new Tegra Note 7 last night and I've been trying to get it rooted, but I keep running into trouble.
First of all, I DO NOT want to use some shady Chinese software that installs a bunch of bloat on both my tablet and PC just to get SuperSu going, I've tried that method and had to reset the tablet to get rid of all the crap it installs (and it didn't even seem to root anyway).
Now I'm trying the manual method from here: http://pan.baidu.com/wap/link?uk=3073396937&shareid=3129426036&third=0
Which, again, is Chinese but at least I can see what it's doing since I'm issuing ADB commands, and supposedly it has worked for others on this forum.
Now, I get to step 3 on the included PDF which says to boot an insecure bootloader image with "fastboot boot tegranote_insecure_boot.img", I do this and the tablet screen flashes a few times and reboots to android.
I get to the next step which says to open an adb shell, and do "/sbin/rootsh +p" to get a temp root shell, and this is where I get stuck. Instead of getting a root shell I get the message "/system/bin/sh: /sbin/rootsh: not found". Does anyone have suggestions?
By the way we really need a Tegra Note 7 subforum here at XDA, if the mods could add it that would be great.
Click to expand...
Click to collapse
I would recommend the following procedure:
1. Download the root_tool_v2.zip attached to this post
2. Unzip the contents the root_tool_v2.zip to a directory
3. Run the following commands from your ADB and Fastboot directory:
Code:
adb reboot bootloader
fastboot boot tegranote_insecure_v2.img
4. Once your device finishes booting the insecure boot.img (Your device's screen will blink several times and then boot into Android) run the following commands:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o remount,ro /dev/block/mmcblk0p5 /system
exit
adb reboot
5. You should now have Superuser installed and have root access.
What I did was I modified the boot.img provided to be insecure and use an insecure adbd binary to allow a root shell when booted from which can then be used to setup Superuser and su binary access. Let me know how this goes for you and if you have any questions .
Wow, thanks for the help! Unfortunately your attachment seems to be corrupt, I can't decompress the archive. I'm using 7-zip btw. The forum says your attachment is 7.19MB but when downloaded it's only 160KB.
If you can re-upload it I will give it a go.
a reup of the file would be much appreciated! :good:
PS
i have a batch file to expedite the process.
dark42 said:
Wow, thanks for the help! Unfortunately your attachment seems to be corrupt, I can't decompress the archive. I'm using 7-zip btw. The forum says your attachment is 7.19MB but when downloaded it's only 160KB.
If you can re-upload it I will give it a go.
Click to expand...
Click to collapse
dergezero said:
a reup of the file would be much appreciated! :good:
PS
i have a batch file to expedite the process.
Click to expand...
Click to collapse
Re-uploaded the file for you guys let me know how it goes for you .
Awesome your new package downloaded fine.
However I'm still not getting root, I got to step 4 and when I open an adb shell I don't have permissions to do the next command.
The exact error message:
[email protected]:/ mount -o remount,rw /dev/block/mmcblk0p5 /system
mount -o remount,rw /dev/block/mmcblk0p5 /system
mount: Operation not permitted
So I guess the insecure boot image didn't work right. I should mention that I am using the latest Tegra Note firmware, I don't know if that makes a difference though. Any ideas?
Thanks for your help so far.
do you guys have a copy of the drivers for the tablet? mine only seems to work for storage.
update: got drivers working.
dergezero said:
do you guys have a copy of the drivers for the tablet? mine only seems to work for storage.
update: got drivers working.
Click to expand...
Click to collapse
I used Universal Naked Driver 0.73, I just manually installed the driver for the Nvidia Shield, thinking it would work, and it does!
Does shimp208's root image work for you, dergezero?
dark42 said:
I used Universal Naked Driver 0.73, I just manually installed the driver for the Nvidia Shield, thinking it would work, and it does!
Does shimp208's root image work for you, dergezero?
Click to expand...
Click to collapse
no, it just reboots. neither is working. im going to see if any one can give us a dump of their img that already works to be rooted. i tried that Chinese method and its really annoying and i dont get root on any computer i try it on.
Hey guys I am in the process of creating a new boot image that uses a different method for gaining root access and will upload that once I finish it.
shimp208 said:
Hey guys I am in the process of creating a new boot image that uses a different method for gaining root access and will upload that once I finish it.
Click to expand...
Click to collapse
:good: Awesome man, good luck! Eager to try it when you post it! :fingers-crossed:
dark42 said:
:good: Awesome man, good luck! Eager to try it when you post it! :fingers-crossed:
Click to expand...
Click to collapse
I agree, with the amount of malware that is in the chinese root tools, it makes me nervous to use the one the OP posted.
Brew
I wonder if someone would be able to port Clockworkmod Recovery to the TN7 eventually. The bootloader on this device is factory unlocked so it should be simple enough. Unfortunately I'm not a good enough programmer to get this done.
If we had Clockworkmod then rooting would be as easy as flashing the SuperSU .zip from the SD.
I have updated my original post with the rooting instructions to include a new insecure boot method follow the same instructions as before just use the new boot.img I uploaded to that post. Credit to teknoraver for the insecure adbd binary.
shimp208 said:
I have updated my original post with the rooting instructions to include a new insecure boot method follow the same instructions as before just use the new boot.img I uploaded to that post. Credit to teknoraver for the insecure adbd binary.
Click to expand...
Click to collapse
I tried your V2 image, still getting permission errors when doing "mount -o remount,rw /dev/block/mmcblk0p5 /system", what am I doing wrong?
dark42 said:
I tried your V2 image, still getting permission errors when doing "mount -o remount,rw /dev/block/mmcblk0p5 /system", what am I doing wrong?
Click to expand...
Click to collapse
When you boot the image and then type ADB shell do you get a root shell ([email protected]:/ #) or just a regular shell ([email protected]:/ $)?
Amazing
Nice to see you working on a different method of root... I am sorry to those who feel that the method I posted is getting negative reviews just wanted to throw something out there for people... however, I do feel much better with Shrimp208 working on a better root method I really wish we could get a forum going..
I used the Chinese root tool and all seems fine on my Tegra note
Sent from my TegraNote-P1640 using Tapatalk
shimp208 said:
When you boot the image and then type ADB shell do you get a root shell ([email protected]:/ #) or just a regular shell ([email protected]:/ $)?
Click to expand...
Click to collapse
Just a regular shell with $. Doesn't look like I get temp root permissions after running the tegranote_insecure_v2.img.
If it matters, I'm on the latest Stock ROM (4.2.2/JDQ39.13155_268.1942) and I'm using Universal Naked Driver 0.73 for the Shield, which works with this device. Maybe I need to use a different driver?
Toyeboy said:
I used the Chinese root tool and all seems fine on my Tegra note
Sent from my TegraNote-P1640 using Tapatalk
Click to expand...
Click to collapse
yeah it works but you dont really know what was installed on ur phone or on your pc. 3 apps are installed on your phone and a few reg changes on ur pc can be detrimental. and its all bloatware