Database Develop

Unable to mount any more

Not sure when or what happened but I'm unable to mount now. I'm able to use adb and everything but unable to mount AT ALL via adb nor drop down on the notification bar. Any ideas? Yes i've searched and had other members try n figure out why.

imbonez9 said:
Not sure when or what happened but I'm unable to mount now. I'm able to use adb and everything but unable to mount AT ALL via adb nor drop down on the notification bar. Any ideas? Yes i've searched and had other members try n figure out why.
Click to expand...
Click to collapse
If you have Cyan's 1.4 recovery, reboot into recovery, go to console and type
Code:
ums_enable
if it doesnt work, its hardware problem. Make sure its in right, pull it out, blow out any dust, put it back in.
If it does, its something wrong with your ROM install. Make sure its not your computer OS either
you have given absolutely no information on your set-up and its hard to diagnose anything if we don't know what you have

i have
jacXhero1.2
vista 32bit.
My thing is i can use adb with no problems at all, will register every time.

if you can use adb then it shouldn't matter if you can mount the phone, just adb push stuff to your phone if you need it, or pull it. you said you couldn't mount via adb so i guess that means you did "adb shell sdutil ums enable" and you still have ums enabled in your settings?

My whole thing is i want to be able to mount so i can put things on my SD Card and take things off like: music,pictures,videos.

did you try flashing your ROM again? when did it start happening

Go to Settings>Applications>Development and disable USB debugging, you can now mount on your computer to access files. Reenable when done.

SolemnWishing said:
Go to Settings>Applications>Development and disable USB debugging, you can now mount on your computer to access files. Reenable when done.
Click to expand...
Click to collapse
No i still can't thank you though.

imbonez9 said:
No i still can't thank you though.
Click to expand...
Click to collapse
Did you try it with a different card?

you don't NEED to mount to put things on your SD card, you can just do
Code:
adb push \users\me\music\file.mp3 \sdcard\music\file.mp3
or do the same thing to pull from the sdcard, as long as the phone is reading the sdcard then you can push/pull through adb to/from the sdcard

adb commands nexus one-read only error

I have been trying for some time now,pushing files via adb commands onto nexus one but keep getting cannot copy file read only file error.I am fully rooted and unlocked.I have also reinstalled the android sdk but always get the same error when I push the image file.has anyone experienced this with their phone. I have a feeling its something to do with the SD card but can't be sure.any help would be appreciated. Thanks.
I know you must be thinking "Jedi"how can he can he call himself an androidjedi when he can't sort this simple problem (to some of you),but I must say even a Jedi needs to learn!

try adb remount before your command

Dunno if this will help but have tried changing the system to rw then try to push

Tried that no cigar

are you trying to push it into your sdcard or the phone system??
and remember the whole folder name has to be in the push so it woul have to look like
C:\Users\Android>ad push "C:\Users\Android\Downloads\Android\Nexus 1\Phone.apk" /sdcard/files
has to have full path of where you are pushing it from/too.. i have mine sdk setup to use adb in any directory as well why you dont see it in the sdk directory

@ilostchild
Thanks i will try that later today and let you know
As for pushing the file - i am trying to push it to the sd card - but i am not really sure as i am following instructions in the [HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012 thread in the forum
as i need to downgrade my Hboot from #17 to 12
are the commands different for pushing a file to the phone?

the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp

androidjedi said:
the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp
Click to expand...
Click to collapse
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come

ilostchild said:
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come
Click to expand...
Click to collapse
thanks for spending time on this-i am new to the android world so any help is welcome-however detailed or not
thanks will try that

ilostchild said:
Dunno if this will help but have tried changing the system to rw then try to push
Click to expand...
Click to collapse
how do i change the system to read write as i am still getting cannot copy file read only file error

androidjedi said:
how do i change the system to read write as i am still getting cannot copy file read only file error
Click to expand...
Click to collapse
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push

ilostchild said:
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push
Click to expand...
Click to collapse
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now

androidjedi said:
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now
Click to expand...
Click to collapse
Umm if you got that mesage you may have pushed it in right..

ilostchild said:
Umm if you got that mesage you may have pushed it in right..
Click to expand...
Click to collapse
does not seem to have worked for some reason as after flashing it should reboot in htc mode and then i would be able to flash a rom with the hboot12

May i ask what are you trying to push into your phone/sdcard?

ilostchild said:
May i ask what are you trying to push into your phone/sdcard?
Click to expand...
Click to collapse
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012

androidjedi said:
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012
Click to expand...
Click to collapse
managed to do it after just following the instructions and inoring what i thought was an error i managed to downgrade my happy days have a good weekend
will no doubt ask you for help another time cheers and thanks a lot

Welcome and congratz
Sent from my Nexus One using XDA App

[Q] how can i write /sdcard/update.zip in recovery mode

I was trying to update the status bar on my i9000m/JH2. I must have done something wrong when zipping, signing, or zipaligning the file. I was able to apply the update.zip without any errors through recovery mode. But when i rebooted, I was met with continuous force close windows. I had my original backed up and wanted to place that into /sdcard and then simply run it from recovery mode to 'undo' the damage i did.
/sdcard appears empty when I run abd to my phone while in recovery mode. If i attempt to push a file to it, i get 'permission denied'. Do i need to manually mount /sdcard in recovery mode to be able to overwrite /sdcard/update.zip (can this be done)?

*snip*
On sec...

nudge nudge

Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App

If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start

lgkahn said:
Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
I ended up reflashing shortly after it happened. I'll look into root explorers.

Daneshm90 said:
If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start
Click to expand...
Click to collapse
I was able to get adb running, but I didn't see /system when listing. Did i need to mount it?

onaquest said:
I was able to get adb running, but I didn't see /system when listing. Do i need to mount it?
Click to expand...
Click to collapse
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.

Daneshm90 said:
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.
Click to expand...
Click to collapse
One other detail is that the phone wasn't rooted At the time I thought that might have been preventing me from seein /system.
This is all educational for me, I was wondering what other options I had before reflashing. Thanks for all the input guys. I ended reflashing with Odin a few days ago.

About flash CMW V20A

Hello,
I had posted this in Frequently Asked Questions about the LG Optimus 4x HD but got no help so I post here for a last try.
Just followed all dexter's steps in this thread to flash CMW
http://forum.xda-developers.com/showthread.php?t=2180138
but I got stuck here. Tried to read 34 pages of the thread but still couldnt solve my problem
My LG was rooted and unlocked.
Any help? thanks
Ekio

The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/

AlderCass said:
The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/
Click to expand...
Click to collapse
Tried and still not such files and directory thx anyway

ekiong said:
Tried and still not such files and directory thx anyway
Click to expand...
Click to collapse
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...

Bogeyof said:
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...
Click to expand...
Click to collapse
Omg I already did
Look pics

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...

RuedasLocas said:
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...
Click to expand...
Click to collapse
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
---------- Post added at 06:48 PM ---------- Previous post was at 06:40 PM ----------
ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
Did you do it in recovery mode from the start? When I did it it was when the phone was just switched on normally into the main OS.

ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
Click to expand...
Click to collapse
Where the hell did you found that path /mnt/sdcard/....... ???

Tutorial CWM
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:

RuedasLocas said:
Where the hell did you found that path /mnt/sdcard/....... ???
Click to expand...
Click to collapse
It's in the system root for me, it's a symlink. Though it didn't work for me in the cat command, which is why I suggested using /storage/external_SD/ instead which did work for me. It looks like the OP has the files in the right places, and the hash in the command line screenshot implies that SU is working correctly, so I'm all out of ideas now.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
Click to expand...
Click to collapse
Little bit arrogant, we're all trying to help here, so I hope for your sake your way works for the OP

AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
Click to expand...
Click to collapse
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:
Click to expand...
Click to collapse
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.

ekiong said:
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.
Click to expand...
Click to collapse
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Dexter_nlb said:
......
GUIDE:
1. when you are running unlocked bootloader and is rooted goto step 2.
2. download attached zip files and extract content to internal sdcard location
3. use adb shell or terminal from market and execute the commands below
4. you are now running with native CWM recovery and unsecure boot, which enable adb root at boot instantly.
5. boot into recovery, by rebooting device and hold VOL-DOWN during bootup. (from power-off = keep holding vol-down during power on)
execute these 3 commands for recovery image install
Code:
su
cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
execute these 3 commands for unsecure boot image install
Code:
su
cat /mnt/sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
or see screenshot here
do this at your own risk, and do NOT try this on old 4.0.3, which is not with unlocked bootloader, and you are required to install KDZ again.
THANKS to:
skydev - for his continued effort in finding root and giving our device full freedom with boot/recovery.
Click to expand...
Click to collapse
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !

RuedasLocas said:
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !
Click to expand...
Click to collapse
Still no such file, I give up :angel:
Thx every one

ekiong said:
Still no such file, I give up :angel:
Thx every one
Click to expand...
Click to collapse
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."

RuedasLocas said:
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."
Click to expand...
Click to collapse
OH MY GOD I'm stupid, I copied files with ZERO byte.
sorry I used airdroid to copy them to my phone. But only their icons moved into my phone, not contents.
It works now THANKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS :laugh:
Close thread and my stupid problem :silly:

[ROOT][10-29-13]How to Manually Root the Nvidia Shield

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.