Related
I am using the PRS complete rooting guide. And when it tells me to type cat /sdcard/su > su, i am getting this error message - cat: can't open '/sdcard/su': No such file or directory.
Can anyone help with this?
Do you have su on your sdcard?
use unrevoked. one click root
just use the one click method by unrevoleved its easier
Su is not on the SD card. The sd card is a brand new PNY card. I have Su in the sdk/tools folder.
Then obviously, that command will not work. Use the unrevoked method if you are unsure what these commands do/how they work. Less headache on your end.
where is it located?
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
This is what it's asking me to do.
From PRS Complete Rooting Guide
Now type the following commands to make it persistent through reboot
Code:
adb shell
su
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su /* IF YOU GET AN ERROR HERE DO rm /system/xbin/su THEN REDO */
chmod 06755 su
k_flan said:
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
Click to expand...
Click to collapse
I don't know what that guide does, but it doesn't seem right --- it'll mess up the privs, that's why the old root was written as an update-payload.
It's redirected I/O since you can't copy across filesystem boundaries -- ie /sdcard to a different mountpoint.
So if I reboot my phone now, do you think I'll lose root and have to start over?
csills said:
So if I reboot my phone now, do you think I'll lose root and have to start over?
Click to expand...
Click to collapse
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to http://unrevoked.com/ and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
askwhy said:
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
Click to expand...
Click to collapse
AND - if you appreciate unREVoked's work - please donate. They do amazing work and they do it all for free! We're the lucky ones to have such [email protected] developers out there who do this kind of stuff so that we don't have to figure out the exact second to push in our SD cards, push files to the SD card, and then push them to the phone at exactly the right time...... just download, run, and you're done.
Just use the unrevoked 3 you will save plenty of pain and struggle
unrevoked3 worked! Thanks for the help guys.
No problem were glad to be of assistance
I have busybox 1.6 on my captivate i see on www.busybox.net 1.17.3 is out. I have downloaded it from the site and its a tar file with a folder with a whole bunch of folders and files. How do you install this?
Are you familiar with the phrase, "if it isn't broken, don't fix it?"
I advise you to heed its warning.
But if you must proceed, a quick google search for "how to install busybox manually" brings up this very good result: http://www.droidforums.net/forum/droid-2-hacks/82573-busybox-manual-install-how-guide.html
Edit: By the way, love the avatar. Great album.
Yes i understand if its not broke don't try to fix it but i'm a OCD updater! Would there be any advantages of updating it? P.S. I saw Megadeth and Slayer a month ago they rocked!
Only advantages I can see are having a couple more bug fixes and maybe 4-5 new commands built in.
Download Busybox-1.17.2 HERE
Extract busybox to your SD Card
Make sure you are in PC Mode and Debugging is enabled in Applications options
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/busybox /system/xbin/
cd system/xbin
busybox --install /system/xbin/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
You can also use Root Explorer or whatever file browser you may use to copy busybox to your system/xbin folder. Some people use system/bin but I prefer xbin...just a habbit.
Click to expand...
Click to collapse
Ya, I read that and got really scared.
What is PC mode and where do you type these commands? (Vista user)
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Cruton502 said:
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
miztaken1312 said:
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
Click to expand...
Click to collapse
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Cruton502 said:
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Click to expand...
Click to collapse
I think you're seriously confused. The Captivate isn't a NAND locked phone. Generally when you root, busybox is installed. (I think. At least it always was for me.) You could also try installing Titanium Backup and have that install busybox for you.
HTML:
The new update blocks the current ways of attaining root for the device. However, if you have root before you update, it is possible to retain this during the upgrade.
Script is online!
A newer version is available here:
http://forum.xda-developers.com/showthread.php?p=12540398#post12540398
Yeah... I'll just wait for you
Thanks for this! been holding out on the update ever since I found out you lose root during the beta testings
if this works i guess it's time to get my desktop back up and running so i can flash back and use this. damn power supplies dying on me.
ill wait for ur auto script
will this b possible btw neone?
Flash the 1.5.7 sbf -> run gblur custom rom -> run the root scrip
No Gingerblur needs root to push its files, also if you need a host I can host
Scripts are online!
Run beforeupdate.bat, update, then run afterupdate.bat.
Haven't tried it yet but wanted to say thanks and great work!
--EDIT -- BELIEVE THIS IS FIXED--
you didn't package the bin folder with psneuter.. :X
In reference to "adb.exe push movesu.sh /data/local/tmp > NUL 2>&1"
movesu.sh is now backup.sh, yes?
Also busybox "mv /system/xbin/su /system/bin/frozenfish" clobbers the copy from system/bin, if there is a difference, i thought it was generally a symlink to /system/bin.
Other than that, good idea in renaming the binary file, I probably won't use frozenfish in case Motorola targets that now..
Sounds sweet! If I already updated can I flash back to old then re root? Then run script then update?
Sent from my MB860 using XDA App
Update: Yes You Can ! just finished..
Whoops - I based it from adeo without making the proper changes. Corrected one should be live in a few minutes.
all good take your time..
so far the only corrections were the movesu.sh in beforeupdate.bat
and the missing /bin folder :X .. well technically you just need psneuter in there.. and just change the /bin/psneuter.. to /psneuter saves you time lol
The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.
curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work
"movesu.sh" is called but doesn't exist.
shawnbuck said:
The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.
Click to expand...
Click to collapse
Do you have the su that does not require Superuser.apk installed?
Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.
I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu
dLo GSR said:
curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work
Click to expand...
Click to collapse
Root here is a normal root, anything you could do before you'll be able to continue doing.
eval- said:
I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu
Click to expand...
Click to collapse
Thats right - I corrected that and added a new version.
OrangesOfCourse said:
Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.
Click to expand...
Click to collapse
Exactly right. I'll clarify the directions in the OP.
lpsi2000 said:
Do you have the su that does not require Superuser.apk installed?
Click to expand...
Click to collapse
This doesn't come bundled with a copy of su, it uses the one already installed in the system.
will this work on flash sbf?
I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
Click to expand...
Click to collapse
3. Then, type and press enter:
su
Click to expand...
Click to collapse
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
Click to expand...
Click to collapse
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!
Will try and report if it works or not
Sent from my MB860 using XDA App
Well I know I shouldn't say it here...
But is the HKTW rom blurred or blurless?
Different kind of blur but its still blur
Sent from my MB860 using XDA App
Do you mean Blur 4.5?
I don't know what its called lol
Sent from my MB860 using XDA App
Trying it out now. Will report back.
And this has Blur on it. It's not a custom ROM.
Anyone else experiencing issues getting their phone recognize by adb
Sent from my Atrix 4g Ubl 2.3.4
su is throwing me a permission denied
http://pastebin.com/brXVEYDb
i guess i didn't phrase the instruction clearly. sorry. just edited first post.. reread everything and try again.
had to run it a few times.. but it worked! thx!
Works! 10char
reserved *10chars
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
having the same issue with SU
Are there any other alternatives to root currently?
jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
Can you be more specifically on those files? Where to download and how exactly did you go about running those files?
Do I need the SDK for rooting it?
THIS WORKS ON WINDOWS, OSX, AND LINUX
once you type in adb shell then type dosu instead of su and see if that helps
I get an error at the last part when I put it in cmd
Whenever I type in 'su', I get permission denied - and dosu doesn't work either.
Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.
Does anyone if the root stop you from updating the device like GS4?
Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.
Finally success root my shield
oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?
Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.