Hi..!! Everyone I tried everything, I was going to unlock and root my xoom but I got stuck at this step:
7. fastboot flash boot rootboot.img
I get this error: "can't load rootboot.img"
I run fastboot reboot command and works, after reboots I try adb devices and my xoom shows but if I run adb remount I get this error:
"remount failed: Operation no permitted"
I tried everything search everywhere, update everything and NADA, I'm on a Windows 7 64bit.
Thanks and I hope somebody can direct me to the right path..
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
diablo2224 said:
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
I get stuck on step 7 of this guide below, so I think I never get to the point of getting root, but if I'm doing something wrong and I have to run some other commands please let me know.
1. Download the Motorola Xoom Root Zip file and unzip it. Download
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
And thanks for making some time to reply, I try to get some help on other threads with no response.
dumb question: is rootboot.img in the same directory as everything else?
It sounds to me like your flashboot can't find it.
That's a good point from the poster above. I had trouble at the start with this and the SDK tools folder because I never messed with the adb shell too often because there never really has been a need for me to do so up until I got the Xoom.
OP... like this reply says above me, I am agreeing to as well. It looks like it might not be finding your rootboot. Make sure all root files are located in the very root of the SDK tools folder, and make sure all root files are not inside a folder. If they are please drag them into the tools folder and slap them all in there. It looks like a mess but it works. Do the same type of thing if you plan on flashing an overclock kernel. Always make sure that all files are NOT in folders when flashing something like this, and that they are always placed in the very root of the tools folder located within the SDK folder. Hope this helps.
About my above post... woops. I wasn't paying attention totally. It was late. I was thinking about when you are trying to install an overclock kernel and run into this problem that says that you cannot remount in adb. It does have to do with root access though.
Thank you very much guys I found what was my problem, I was running ADB straight from CMD window without navigating to my tool folder and always worked so I thought running step 7 will work, but NO I had to cd c:.....bla bla navigate to tool folder and do step 7.
Now I'm happily Rooted thanks again for your time guys, now to set up again my beautiful screens.
I'm having that problem where i'm trying to flash Tiamat Kernel on my Xoom and when i get to the remount i'm getting - remount failed: Operation not permitted . When you say grant root access again you talking about pointing it to the platform folder ?.
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
jase33 said:
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
jawonder said:
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
Click to expand...
Click to collapse
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
lokko21 said:
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Yes i'm trying to flash a kernel but at the remount step it's telling that : remount failed : operation is not permitted .
Related
Ive just ordered a desire z and have been reading a bit on the uber root method.....
What i want to know is can I use a file manager to install the visinary.apk and then the terminal emulator from the phone to run all the adb commands?
Reason i ask is cos A) ADB freaks me out....just the install instructions make my head spin and B) i havent got any space on my even if i wanted to install it....
Im aware that you need to install the gscript to /data/local but can this be done just by dropping it into the relevant place rather than pushing it using ADB?
and assuming I can?
Which bits of the commands do i run ? looking at the following.....
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
do i just pick this up from the point of SU?
oh and errr if ive completely got the wrong end of the stick then please say.....id sooner look stupid than have a £420 brick
cheers peeps
Yes, if you want you can copy the gfree program to your SD card via some other method, and then pick up the instructions from the su onwards.
An alternative is to run the "rage" method of rooting, but if you don't like adb (it's a lot easier than it might look) then maybe that's not for you.
steviewevie said:
Yes, if you want you can copy the gfree program to your SD card via some other method, and then pick up the instructions from the su onwards.
An alternative is to run the "rage" method of rooting, but if you don't like adb (it's a lot easier than it might look) then maybe that's not for you.
Click to expand...
Click to collapse
TBH its not the ADB commands that i struggle with its the setup of ADB itself.....ADB, SDK, HBOOT drivers, issues with windows 7 etc....
Im happy running the commands and sort of understand what im asking my phone to do so if i can get by without ADB i will try
Thanks for clarifying though
rtorbs said:
TBH its not the ADB commands that i struggle with its the setup of ADB itself.....ADB, SDK, HBOOT drivers, issues with windows 7 etc....
Im happy running the commands and sort of understand what im asking my phone to do so if i can get by without ADB i will try
Thanks for clarifying though
Click to expand...
Click to collapse
I suggest you to read the Easy root / flashing tutorial and FAQ post located at android development subforum
And regarding ADB, if you daownload qpop's "uber root" package, everything required is inside the zip, even ADB is inside
i used gtrab's guide...
super easy and no adb necessary.
http://forum.xda-developers.com/showthread.php?t=835777
bradleymor said:
i used gtrab's guide...
super easy and no adb necessary.
http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
Things evolve quicky, problem with this guide is hBoot step was very risky, and it was sort of a "false" S-OFF
The newer method is easyer, safer, and doesn't require manually flashing hBoot
The guide has been reestructurated accordingly
gtrab said:
I suggest you to read the Easy root / flashing tutorial and FAQ post located at android development subforum
And regarding ADB, if you daownload qpop's "uber root" package, everything required is inside the zip, even ADB is inside
Click to expand...
Click to collapse
I've already read them pal, that's why im here...I was just clarifying that I could use the terminal emulator rather than adb.....I'm pretty sure what i need to do now so its cool
Cheers peeps
Sent from my HTC Hero using XDA App
rtorbs said:
I've already read them pal, that's why im here...I was just clarifying that I could use the terminal emulator rather than adb.....I'm pretty sure what i need to do now so its cool
Cheers peeps
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
The reason the guide is all ADB is that its much easier to get right with adb...seriously there's no install needed, just open up a command prompt in windows seven (or use the packaged cmd.bat from my zip) and follow instructions. No install needed, no complexities, no messing around with a very limited terminal clone.
But yea, as long as you get the gfree file onto your phone it should be ok
qpop said:
The reason the guide is all ADB is that its much easier to get right with adb...seriously there's no install needed, just open up a command prompt in windows seven (or use the packaged cmd.bat from my zip) and follow instructions. No install needed, no complexities, no messing around with a very limited terminal clone.
But yea, as long as you get the gfree file onto your phone it should be ok
Click to expand...
Click to collapse
Ok cool....sounds a bit more promising....will give it a bash....at least I know I now have a plan b with the term emulator if I have problms
Cheers
Sent from my HTC Hero using XDA App
As someone who had never even heard of ADB and is on his first Android phone..believe me when I tell you that all these different instructions and methods made my head spin! What I ended up doing was (can't remember which "method" it was called) just downloading the VISIONary program onto my SD card, and then running it right from the phone to achieve my ROOT. Once I was rooted, I used the UBERROOT method for S-OFF. I simply downloaded the ADB program (and whatever else it was that came with it)..let it go thru it's updates and made sure the computer recognized my phone (by making sure drivers were installed). Plug your phone into the computer..open up the gfree program you downloaded...and inside there is two main programs..and exe and the cmd. I ran the exe, then simply opened up the cmd program..entered the necessary commands..and viola! It really was simple once I finished it.
I am having a bit of difficulty rooting my g2. I am not sure if its related to my os or not but i can not get it to work.
I have followed this and tried it all kinds of different ways.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/[/url]
I can get to my run command after doing all of that and it shows my serial number after typing adb devices but after that i can't enter any info in the sdk run command promt.
I have not been able to gain temp root yet because it won't let me enter the commands. I went to try to re-install java/sdk manager yet again and now it says java is not in the right path.
Any help?
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
martonikaj said:
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
Click to expand...
Click to collapse
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
901-Memphis said:
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
Click to expand...
Click to collapse
Yep let me grab a link for you (theres actually a video tutorial I wanna try and find). But basically instead of using ADB to push the files to the correct location, you just have to manually put the files in the right locations on the SDcard, which is where ADB pushes them anyways.
K so I followed this method: http://www.youtube.com/watch?v=tU9zn_BEth4
The files he refers to are in this thread: http://forum.xda-developers.com/showthread.php?t=833965
Now different people have had different issues with this. I personally had some issues where it tells you to run #sync, because my perm root wouldn't stick properly after reboot. If this doesn't work properly, I'm sure someone can help you with your drivers to get ADB working.
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
If you got the adb devices command to work you are actually in good shape. You are supposed to enter all of the commands from what you are calling the "run command" prompt anyway (the one you used for adb devices).
martonikaj said:
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
Click to expand...
Click to collapse
Unfortunately this won't work (if you don't want to use ADB, Visionary must be used to get temp root). ADB is needed in order to push the files directly to the phone. If you try copying the files to the SD card first, you won't have the correct permissions to copy the files to the phone in Terminal. You are also not allowed to execute programs directly from the SD card (mounted as noexec), so you can't try to obtain temp root from there. If you want to use the gfree method of rooting without using ADB, I made a guide using Visionary for the temp root here: http://forum.xda-developers.com/showthread.php?t=928160.
But the OP actually has ADB working, so he should be able to use any of the guides.
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Uploaded with ImageShack.us
901-Memphis said:
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Click to expand...
Click to collapse
You are supposed to be using the regular command prompt (I think you referred to it as the "run command prompt" earlier). It is the prompt in which you successfully ran the "adb devices" command. That is the only prompt you need to use.
Do i enter commands 1 at a time or all at once?
901-Memphis said:
Do i enter commands 1 at a time or all at once?
Click to expand...
Click to collapse
First off, Yes you enter each line as you see it.
Second just to make sure you are in the right area to enter these commands, to get to command prompt you can either search for it from the start menu or hold the "windows button + R".
That opens your run command from there type in "cmd" and that opens command prompt.
Next make sure your current directory is the one you installed adb into. To get to that you can type "cd C:/...... whatever folder you installed it to."
To make sure my adb is working I usually type "adb devices" and see if my phone shows up.
Good luck
Glad to see someone else from the good ole 901 around here =)
Sent from my HTC Vision using XDA App
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
901-Memphis said:
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
Click to expand...
Click to collapse
try pushing the file to that folder again
Re-Tried everything at least 3 times, including pushing the files that didn't go.
I give up Ive spent so much time on this only to have it fail at the most unlikely times.
Will wait for another method to root come available
You could try downloading and installing Droid Explorer. It installs adb and fastboot files in its install folder.
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
ianmcquinn said:
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
Click to expand...
Click to collapse
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
901-Memphis said:
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
Click to expand...
Click to collapse
You are supposed to do that command from your computer. (The instructions state "On the computer, open terminal and type the following commands".) Here, terminal means the command prompt that you've been running all of you other ADB commands from.
If you wanted to run the command from terminal on your phone, you would just type "chmod 777 /data/local/gfree".
You don't need ADB for G2s.
trance2315 said:
You don't need ADB for G2s.
Click to expand...
Click to collapse
Can someone link me a better guide for my G2 so that i can try this 1 more time ?
Maybe a link to the top choices for versions of android to run once i get it rooted?
Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks
thepaperescape said:
Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks
Click to expand...
Click to collapse
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
How ever their are much easier methods. This being one of them. Makes sure to go to page two.
neidlinger said:
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
Click to expand...
Click to collapse
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.
thepaperescape said:
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.
Click to expand...
Click to collapse
okay.
I've seen alot of people try this method and very little come out okay.
you need SU access to push objects to the phone. The phone is seeing it as a foreign object and is wanting to prevent it from being pushed. The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.
Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
SU was actually Switch User but Super User is used ATM due to the confusion it created to the newbies a decade ago who didn't understand how permission base structure on *nix worked. Which always required chmod and whole rwx thing even made it more confusing so they preallocated it with [email protected] with UiD:0 as default permission.
Now what I like to know is why are you using that howto? As neidlinger stated just run VISIONary+ to get TempROOT and then do root.sh to obtain PermROOT. If you need to unlock the CiD just call TMo and get the code free as no need to risk it. But if you still want Radio S=OFF then just do the simple gfree step and you will have it.
You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?
UsrBkp said:
Now what I like to know is why are you using that howto?
Click to expand...
Click to collapse
Well for one, I chose that guide because my goal is to install cyanogen and that is found directly off their site regarding my phone. My expectation is that a group of developers so renowned for their contributions should be able to correctly explain how to get to the point of install. Still I know it's a wiki, and things are constantly changing (generally faster than the wiki). For instance, I did notice that the wiki was incorrect about the location of the google usb drivers post download. I assume that is due to the newer version of the sdk i installed. And the jdk r25 is pretty new and I believe that to be one of the other things causing me problems, but I don't know for sure.
neidlinger said:
The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.
Click to expand...
Click to collapse
I tried doing this for those two files (su and superuser) that are supposed to be pushed onto the sd root and i thought it worked. cmd allowed me to push the other three files into /data/... no problem. chmod to 0755 even seemed to work (it neither explicitly approved or denied). but then when I got to step 8, terminal on the phone said i did not have access to run that command.
shuka325 said:
You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?
Click to expand...
Click to collapse
That's what I figured based off of the guide (since it's a guide on GETTING TO temproot, but what do I know... i'm supernoob. I've attached an image to see if you can see ANYTHING wrong with what I'm trying to do.
Thanks for everything guys!
I would give up that guide and use VISIONary to gain Temp Root & Root.sh to obtain perm Root. Then install the latest rom manager and make sure CWM sticks. Then you can flash CM7, or any other ROM for that matter.
Is there any guide you all think stands above the rest?!?!
thepaperescape said:
Is there any guide you all think stands above the rest?!?!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=13989736&postcount=6
Ok..
I cleared delvik cache.. battery and decided to try out a new kernel.. now it hangs..
Now I only have an 8 gig.. I guess i cleared out the backup to save space because as I went to look for it, it was gone. Now I cant get any roms on the phone to reflash.. and i deleted the ROMs on there...
How do I get a rom on the phone to reflash it. Any help would be greatly appreciated.
Thanks
Chris
Bump
Can anybody help with this? Basically is there a way to get files on the phone in recovery mode?
I'm sort of new... I see the side load but not sure how to use it. Says load the files on once activated but not sure how the relates to the computer. Or where I put the commands to do it. Thanks.
Chris
Sent from my SGH-I747 using xda app-developers app
You are running a custom recovery right?
You can use adb to push files when booted into a custom recovery.
The command used would be
Code:
adb push nameofzip /storage/emulated/0
To read more on adb check out efrants sicky http://forum.xda-developers.com/showthread.php?t=2010338 adb commands are about half way down on the OP.
When u say custom recovery do u mean CWM? I do have that... and my computer registers the phone when I plug it in. But nothing pops up. I don't think USB debugging is on...
I'll check out the link.
Sent from my SGH-I747 using xda app-developers app
Yep, that is a custom recovery. If you have questions post them here. I'll be around for a little while.
I think I am so close.
I got the adb and fastboot files, and upon checking devices in fastboot, it does say that my device is connected.
But I cant get the adb driver to put the files on my phone.
Im using "adb push -d C:\android1\cm-10.1-20121214-NIGHTLY-mako.zip
And it says device not found?
Sorry for the questions, but thank you for the help.
Chris
(and im in the directory where the adb file is located)
(Once I get this resolved... im always gonna have one backup on my phone)
wizshaw said:
I think I am so close.
I got the adb and fastboot files, and upon checking devices in fastboot, it does say that my device is connected.
But I cant get the adb driver to put the files on my phone.
Im using "adb push -d C:\android1\cm-10.1-20121214-NIGHTLY-mako.zip
And it says device not found?
Sorry for the questions, but thank you for the help.
Chris
(and im in the directory where the adb file is located)
(Once I get this resolved... im always gonna have one backup on my phone)
Click to expand...
Click to collapse
Ok. The best way is to open the command prompt from the folder in which you have adb. The easy way to do that is hold down shift and right click. Then choose open window here.
Next, once you are booted into recovery type
Code:
adb devcies
If it returns a number then proceed to push the file. (Its easy to make a typo so change the file to something easy like cm10.zip)
So you would type
Code:
adb push cm10.zip /storage/emulated/0
I erased everything the other day by mistake and total noobishness Lol. I just used wugs tool kit to flash the stock image back. Might be useful if struggling with adb etc.
Sent from my Nexus 4
slymobi said:
I erased everything the other day by mistake and total noobishness Lol. I just used wugs tool kit to flash the stock image back. Might be useful if struggling with adb etc.
Sent from my Nexus 4
Click to expand...
Click to collapse
What is anyone going to learn by using a toolkit?! I commend the OP for putting in the time to learn how to use adb. So in the future if they were to run into a problem they would know how to easily fix it.
Sent from my Nexus 4
I got it guys.
I realized that fastboot and adb only get activated in their respective UI's... And i refined my CMD commands a bit after a little more reading.
Problem solved. And i learned more about the android platform in the process. Time well spent.
I want to formally thank you guys. This is why this community is great.
Chris
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