Related
This little gem of a phone is a tough little thing to custom install apps on, but that didn't stop the Coburn from being able to get busybox installed.
Therefore, introducing Busybox for your HTC Click/Tattoo!
FOLLOW THIS TUTORIAL CAREFULLY. This guide may brick or NOT brick your Tattoo (most likely the latter), however I cannot assure you that it's 100% fail proof. I have installed it successfully. IN OTHER WORDS: THIS IS NOT FOR THE FAINT HEARTED! IF YOU DO NOT KNOW WHAT 'FLASH','ADB' OR 'HACK' MEANS, PLEASE DO NOT CONTINUE.
Requirements:
1 HTC Tattoo (The Victim)
1 MS Windows Powered Computer (I used Win7 64Bit)
1 HTC Tattoo -> USB Cable (Included with phone... Well, it was in the box).
Download the package attached to this post. Extract all files to a directory like C:\BUSYCLICK . (Actually, please extract them there).
Installation
Connect your Tattoo to your phone, make sure USB Debugging is enabled (Settings -> Applications -> Development) and sit back. Windows should say "New Hardware! OMG!" and ask "What is this piece of tech?" (aka New Hardware Install Wizard). On XP, allow to search Windows Update. On Vista/7, I'm going to have to get back to you on that. The installed driver will be like "HTC Dream blah blah blah ADB Interface" or something. Odd why it says it's a HTC Dream...
Anyway, go to the folder where you extracted the files, and run the Installation.bat file. It's the one that says "Installation" With the cogs icon.
You'll get a DOS Prompt and some text, PAY ATTENTION! My installer will hold your hand and explain what's happening. Should any errors occur, you may be out of space on your Tattoo's internal memory or something. If you do get errors, please post them here! I'll try to fix them for you guys and girls.
Post-install tasks
When complete, run the TestBusybox.bat script in the same folder where you extracted the BusyBox files, and you should get some output. If not, busybox failed to install... Let me know what the error is and I'll try to fix it.
Notes:
You can use the busybox commands in /data/local/bin from "adb shell" or a terminal emulator on the phone itself... /data/local/bin/sh DOES NOT work from adb shell, I don't know why. It will work using a terminal emulator. Try "/data/local/bin/free" and such for some memory read outs, etc, etc.
Feel free to love/like/hate/kill/shoot my work, you can expect to see ROMs and the like in the near future as I love hacking devices.
Cheers,
Coburn64
Ok busybox installed normally...
Do i have root acces with busybox now? I dont see su...
C:\Busybox>adb shell /data/local/busybox ls /data
ls: can't open '/data': Permission denied
I do see /data/local and under tho... including ../bin and ../rights but dont see any use of it...
Coburn Hi, this is a step closer to being root
can be root in busybox?
chmod command does?
thx
Code:
benno.id.au/blog/2007/11/14/android-busybox
chmod command is useless without su...If only su worked
Installed and worked fine, can run busybox but:
it runs with shell privileges
setting setuid bit doesn't solve, because I can chown to root
Do I miss something?
Thanks Really appreciate your work!
Do you have to install the new RUU Click HTC WWE 1.63.405.1 WWE test signed NoDriver first?
coolbits said:
Code:
benno.id.au/blog/2007/11/14/android-busybox
chmod command is useless without su...If only su worked
Click to expand...
Click to collapse
I know friend!
I asked the chmod without adb, or if they could use the chmod as root from the busibox console
leon1984 said:
I know friend!
I asked the chmod without adb, or if they could use the chmod as root from the busibox console
Click to expand...
Click to collapse
All this does is allows you to run more commands from the shell in Android, whereas the standard shell doesn't have many commands built-in. Could be used in conjuction with a root hack.
One step more, but nothing to do with root
I'm starting to believe that Click will never have a root method working because its underused compared with other android devices
MiSSigNNo said:
One step more, but nothing to do with root
I'm starting to believe that Click will never have a root method working because its underused compared with other android devices
Click to expand...
Click to collapse
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
What's the new root vulnerability? Is it something that was just discovered?
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
Ok, where to find more info about this? :S
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
I was able to install Busybox on my phone successfully. But the problem is I don't know what it's for. Would anyone be kind enough to post a link or a tutorial for this? Thanks.
sheik_yerbouti said:
I was able to install Busybox on my phone successfully. But the problem is I don't know what it's for. Would anyone be kind enough to post a link or a tutorial for this? Thanks.
Click to expand...
Click to collapse
Busybox just allows you to use more features at the adb shell command line. So, yeah. Heh.
You lost me at 'adb shell command line'. Is that some command line provided by the Android SDK?
sheik_yerbouti said:
You lost me at 'adb shell command line'. Is that some command line provided by the Android SDK?
Click to expand...
Click to collapse
Sorry if I lost you. Let me sum it up: It's a 'feature pack' for Android Developers, which could be used in conjunction with rooting tools.
Coburn64 said:
What's the new root vulnerability? Is it something that was just discovered?
Click to expand...
Click to collapse
zenthought.org/content/file/android-root-2009-08-16-source
This is linked in the other thread...
ivendor said:
zenthought.org/content/file/android-root-2009-08-16-source
This is linked in the other thread...
Click to expand...
Click to collapse
That code is old, and apparently won't work. It won't compile either, Paul from Modaco tried it and it just spat the dummy and gave a make error.
Coburn64 said:
That code is old, and apparently won't work. It won't compile either, Paul from Modaco tried it and it just spat the dummy and gave a make error.
Click to expand...
Click to collapse
That's the code for the old asroot exploit (used in the Hero IIRC). It's been patched in August/09 so it won't affect the kernel in stock Tattoos.
Yeah, that's what I was getting at - the exploit is too old.
We need to either:
1) Get a S-OFF bootloader
2) Find another working root exploit
3) Dig around in the test ROM and extract the SU binary out of that sucker and put it in /data/local on the working ROM.
I think I can do the latter.
I didn't really know where to put this question, but since it involves my Nexus One I put it here. I put Ubuntu 10.04 on a old Compaq V2000 laptop that I resurrected from the dead, and it's running beautifully. I spend more time on my Ubuntu machine then my new Toshiba/w/ W7. Anyway I need things working like I have on my Toshiba. I set up ADB after getting bits and pieces of information here and there, I just could never get fastboot to work for my N1, except when I'm in fastboot and I plug in my usb it changes from fastboot to fastboot usb, so it's recognized in fastboot, well sorta. But, when I run fastboot devices the terminal just hangs on >>waiting for device<<. Now I have another problem, adb works just fine, but yesterday I used it and where the number of your devices appears is blank now, no number shows up, but I can still run commands. I've done just about everything and I'm at a loss here. Some real help here, no snide remarks, and no [email protected], I need dev help or someone familiar with Ubuntu 10.04, or if you've had this problem lend some help. Once again I already have adb setup, but my number isn't showing anymore, and I need fastboot working, and yes I gave it executable permissions, I exported my path, I created my android rules, I edited my .bashrc file. Thanks much in advance. Long Live Linux!!!!!!
I'm good, found a executable script that solved my problem.
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Read Read Read!!!!!!!!!!
evilkorn said:
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Click to expand...
Click to collapse
I said in my post that I used a executable script, I mean thats all you should need to know. I read about it somewhere, that's all I needed to know, and I found it on my own. They have nuff post on how to setup your adb, but none are 100%, so you have to take bits and pieces from them, and kinda wing it from there. I don't sudo adb on my system, sudo adb =can't be found. It would be senseles to have to type sudo every time you wanted to run adb, I have my to autostart as root as soon as I run adb. If someone needed help all they have to do is ask. Since this post I've had to re-install ubuntu 3 times and I've gotten my adb & fastboot working with the same method I used the first time. I have my adb setup where I can push and pull from any directory, so I don't fill up my tools directory with too many files, and so I don't have to move files, I can just push & pull to & from anywhere.
Perhaps you can share the script you found?
Dude, chill out. The guides are fine and 100%. I don't need to know ****, I know how to setup adb. How the hell is someone going to find that script when you didn't link it.
First, you have to tell sudo where to look for adb, you obviously didn't link it init.d or some other way to tell the software what to do with adb. You have to do 'sudo /home/name/sdk/tools'.
google query: somewhere executable script ubuntu adb
rm -r -f /
Hope this helps
prettyboy85712 said:
Perhaps you can share the script you found?
Click to expand...
Click to collapse
Here's the links, the script isn't mine to give, and I think that would be against the rules. Go to the first link to get the installer, and the next one to get the fastboot exe. I would follow the instructions in the second link. Once you finish that, run the adb script, If nothing pops out of the script when it starts to run , run it again, or try running (in terminal) command. If you need detailed instructions PM me, it's a little process, you have to edit some files.
http://www.droidforums.net/forum/hacking-help/38186-linux-sdk-adb-autoinstaller-script.html
http://forum.xda-developers.com/showthread.php?t=537508
Good for you.
First of all, Linux and OS X come with sqlite3 by default. Windows users will need to download the executable. With that said, here is how you can enable sideloading the old-fashioned way.
Code:
[[email protected] ~]$ adb shell
$ su
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /data/data/com.android.providers.settings/databases/settings.db.bak
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard
# exit
$ exit
[[email protected] ~]$ adb pull /sdcard/settings.db
sqlite3 settings.db
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|0
sqlite> UPDATE secure SET value=1 WHERE name="install_non_market_apps";
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|1
sqlite> .quit
[[email protected] ~]$ adb push settings.db /sdcard/
[[email protected] ~]$ adb shell
$ su
# busybox cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# exit
$ exit
[[email protected] ~]$ adb reboot
You should be all set.
thank god for super one click
Script?
Sent from my MB860 using XDA Premium App
lsxrx7 said:
thank god for super one click
Click to expand...
Click to collapse
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.
I think this work on only rooted devices. If that case we have one already which will root it and also side load apps.
You got the phone gdanko?! Cool
I'll do it this way for kicks when I get my phone lol
gdanko said:
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.
Click to expand...
Click to collapse
Yes, it's always great to know how things work.
But it looks like SuperOneClick is not just confined to Windows.
It is compatible with:
Windows Vista
Windows 7
Ubuntu Hardy (8.04 LTS)
Ubuntu Jaunty (9.04)
Ubuntu Karmic (9.10)
Ubuntu Lucid (10.04 LTS)
Ubuntu Maverick (10.10)
Debian Lenny (5.0)
Debian Squeeze (testing)
Debian Sid (unstable)
Debian Experimental
SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.
Can anyone do this a little more nood friendly? And/or does this require root?
phro321 said:
Can anyone do this a little more nood friendly? And/or does this require root?
Click to expand...
Click to collapse
Yeah, you basically want to get out of this thread and head here:
http://forum.xda-developers.com/showthread.php?t=960336
Follow briefmobile's tutorial. And yes, it requires root.
If I am not mistaken gdanko doesnt use any of those operating systems. He uses a mac...
Maybe his old school ways will help uncover some mysterious portal into the Atrix that will allow cracking the bootloader...
I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!
__redfox__ said:
I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!
Click to expand...
Click to collapse
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.
__redfox__ said:
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.
Click to expand...
Click to collapse
Follow this to add the check box: http://forum.xda-developers.com/showthread.php?t=972760
agentdr8 said:
SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.
Click to expand...
Click to collapse
Fails on Ubuntu 64. And installing mono and a host of other things for something so trivial is pointless.
Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..
marlasinger said:
Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..
Click to expand...
Click to collapse
Hey How did you root your 1.57?
Spoofy said:
Hey How did you root your 1.57?
Click to expand...
Click to collapse
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.
Ririal said:
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.
Click to expand...
Click to collapse
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
EDIT #2: I just found [HOWTO] Easy Root 1.5.7 using GingerBreak which popped up on the 23rd. WOHOOO, no need to downgrade and risk Wifi issues.
Spoofy said:
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
Click to expand...
Click to collapse
It has nothing to do with respect, and I don't have an attitude. Relax, guy.
All the information is readily available, all you need to do is look for it. There's several threads on the first page of the development forum (which you found as you're posting in it) that contain the information you need. One of the threads is even clearly labeled: "[HOWTO] Easy Root 1.5.7 using GingerBreak"
So sorry, I get a little short with people who ask questions that are already answered. Don't take it personally. Here's the breakdown:
There's currently 2 methods of root, one is GladRoot, which requires you to downgrade first. The other is GingerBreak, which formats your phone data. Pick your poison.
hi all. i'm new in android and i dont like that,
many person can install ubuntu 12.04 on TouchPad. but i cant.
how can help me for installing that ( doual Boot).
in android os.after entring this command:
Code:
cp 4GBPartition.sh /tmp
that say:
Code:
/tmp - Not a directory.
i have tmp in root directory but i cant access into that.
Code:
-rw-rw-rw- root root 1824 DATE TIME tmp
after entering this command:
Code:
ls -d */
i cant see tmp in list and i cant create that
i have this problem now:
Code:
/system/bin/sh: cd /tmp - Not a directory
1) Boot on Webos
2) Install preware (many docs on google)
3) open xecutah, then xterm
4) cd /media/internal
5) cp 4GBPartition.sh /tmp
6) cd /tmp
7) sh /tmp/4GBPartition.sh
Click to expand...
Click to collapse
Be carefull... This PORT of Ubuntu isn't for beginners... It's not like your desktop PC, many thing don't work..
Mystikal57 said:
Be carefull... This PORT of Ubuntu isn't for beginners... It's not like your desktop PC, many thing don't work..
Click to expand...
Click to collapse
then can i use keaybord usb and mouse usb?
can i install libreo office - firefox?
tux-world said:
then can i use keaybord usb and mouse usb?
can i install libreo office - firefox?
Click to expand...
Click to collapse
OK I'm not trying to be rude here but you started a new thread that is a little misleading in the title to ask for help that you already asked about in the other thread? This is not a novice install... The instructions are clear, if you can't get it installed by following the clear guide... You may not want to install this. Sorry Devs but when you take your time to make CLEAR guides for us... yet people can't follow instructions then spam.It irritates me.
kicker22004 said:
OK I'm not trying to be rude here but you started a new thread that is a little misleading in the title to ask for help that you already asked about in the other thread? This is not a novice install... The instructions are clear, if you can't get it installed by following the clear guide... You may not want to install this. Sorry Devs but when you take your time to make CLEAR guides for us... yet people can't follow instructions then spam.It irritates me.
Click to expand...
Click to collapse
The instructions may be clear, but are almost always only available in English. XDA is international and judging from his sentences, English is probably not his primary language.
It bothers me too when people create pointless threads (esp with misleading titles). I try to imagine myself on a non-English forum, desperate for help. Even with Google translate, I doubt I could make sense of their rules or "clear" guides.
エイトリックス から 送ります
in install progress that ask you must press 0 or 1, after downloading and install kernel of ubuntu , what key must be pressed?
i dont see any line like umount. i see data lose :|
message is this:
Code:
Repartition to create ext3 volume for Ubuntu.
umount: can't umount /media/internal:Invalid argument
Did the pervious line say somthing about not being able umount /media/internal? if so, press 1, otherwise press 0.
DO NOT PRESS 0 IF DID SAY SOMTHING; THIS CAN LEAD TO DATA LOSS! If it did say somthing,reboot and try again.
after reboot i see this line. external memory may be data loss?
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.