Database Users

[Q] Unable to ADB Remount XOOM...!!

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 .

Mac compatibility

Hello, I am just curious if anyone knows of updates that will allow mac compatibility for rooting and bootloader unlocks. I know a lot of this is new, but I do not own a windows computer and I am not able to find a way to root my phone with my macbook.
I appreciate any help.
edit: I am also still running 4.1.52 and cannot get my phone to update... I thought there was a more current software available? Everytime I go into my phone to "update" is says my device is up to date.

bump it up!

In terms of rooting, can you not use gingerbreak? It's an apk so it doesn't matter if you're on a Mac. You just need to get it onto your phone somehow.
I'm also on a Mac, and for most things, I use the OS X version of adb and redo any windows batch scripts to bash style. There aren't too many mods that use actual windows execs, except rsd lite.
Otherwise you'll need bootcamp / virtualbox and a copy of windows...
Sent from my MB860 using XDA Premium App

You can do absolutely everything on Mac. I'm almost sure someone post a guide about fastboot, sbf_flash on a mac/linux
Enviado desde mi MB860 usando Tapatalk

Just run VMware Fusion & run a windows emulation..
Sent from my MB860 using XDA Premium App

I've done everything (except flash radio) on mac. There are binaries available for mac for "moto-fastboot", "adb (google SDK)" and "sbf_flash". Just search the forums. All commands will be through the terminal and will be the same as linux version
moto-fastboot: http://forum.xda-developers.com/showthread.php?t=1138092
sbf_flash is here: http://blog.opticaldelusion.org/2011/04/universal-binaries-running-same.html#more
and there's a version of adb in gingerbreak.apk if you don't want to install adb with the android sdk.

I dont know what that means... haha! Hopefully superoneclick works for the atrix eventually.
thank you for the responses.

I did everything in a virtual machine. No problems.
Sent from my MB860 using XDA Premium App

Ok im guessing this is a better place than any. anyone know how to get fastboot to work on mac? im tired of barrowing PCs lol I can adb,get it start up but everytime i go into the flash commands i get command not found. anyone know why?

joshyy_rey said:
Ok im guessing this is a better place than any. anyone know how to get fastboot to work on mac? im tired of barrowing PCs lol I can adb,get it start up but everytime i go into the flash commands i get command not found. anyone know why?
Click to expand...
Click to collapse
Add the directory where fastboot and adb are to the $PATH variable in ~/.profile
Also you can add it temporarily with the command set $PATH=$PATH:/path/to/adb
Edit: detailed instructions.
In your home folder create a folder, let's call it android_tools
Copy adb, moto-fastboot, etc to it.
Open terminal
type nano .profile
add in the file the next line:
export PATH=$PATH:~/android_tools;
press ctrl+x, then y to save the file and quit from nano
close Terminal
Open Terminal then type adb or moto-fastboot or whatever is inside android_tools and this command should be recognized.
if it fails, maybe you need to set exec permissions to the commands, open terminal, type cd ~/android_tools, then type chmod +x *
Hope this help
Enviado desde mi MB860 usando Tapatalk

ADB/SDK?!?!?!

ok, just got a new laptop because the old one died and im trying to get adb working on it...i spend multiple hours trying to get it to work, can someone please point me to a guide that works with windows 7 ultimate...i have followed many and then go to command prompt and type adb and it basically says that it doesnt recognize the command...sorry for the noob question, i had it before, i tried multiple guides and im still adb-less
Sent from my Transformer TF101 using XDA Premium App

Are you in the same directory you installed all your sdk stuff?

keroppilee said:
Are you in the same directory you installed all your sdk stuff?
Click to expand...
Click to collapse
+1
cd C:\wherever\your\sdk\is\located\

Lets start off with a simple question: do you have the sdk installed?
If you wish to use ADB first you have to run it from the directory that it is via the command prompt (start -> run -> type cmd). The easiest way to get it to work by just typing adb at the command prompt it by putting adb.exe in c:\windows.
Sorry if anything is slightly off, I use the Linux version of ADB.

Good post
http://forum.xda-developers.com/showthread.php?t=1071584&highlight=adb

Please help: How do u put files on the SD with CWM?.

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

Rooting On Macbook Pro

I am getting things set up to root my Nexus 6p using a Macbook Pro. I have Android Studio installed & I see the platform-tools folder like the tutorial says. But my phone isn't showing up as a device on my Macbook nor is the terminal command "adb devices" showing it.
Has anyone successfully rooted their Nexus 6p using a Macbook Pro?
Thanks!!

Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237

lyall29 said:
Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Totally agree! I used this to get a handle on ADB/fastboot and have been good ever since. Which version of OSX are you using, OP? I followed the above guide and use manual command on OSX 10.10.5. I have heard there are some issues on 10.11 though.
Sent from my Nexus 5X using Tapatalk

I used ruby (built in with osx) inside the terminal to install homebrew. Then install android-platform-tools using homebrew. This installs fastboot and adb, AND adds these programs to PATH so you can use adb or fastboot command no matter which folder the terminal has open. Hope this helps!
EDIT:
Link providing steps for how to do this:
http://macappstore.org/android-platform-tools/

Yes I have rooted my 6p using macbook pro. You have to CD to platform-tools and make the command ./adb devices
That was my problem. Adb wasn't even recognized unless I did ./ before the adb command

andrewnelson23 said:
Yes I have rooted my 6p using macbook pro. You have to CD to platform-tools and make the command ./adb devices
That was my problem. Adb wasn't even recognized unless I did ./ before the adb command
Click to expand...
Click to collapse
That means your search path was not set up.
Even executables in ./ not found? Path really messed up.
BTW : I only use a Mac so I've rooted everything from Samsung to LG and now Nexus on my Macs.

lyall29 said:
Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
WOW!!! Thanks!!! I just posted in the when did you root thread that I haven't seen a tutorial on rooting with a mac!!! I did a search and it didn't show up in the results. I figured people assume that if you have a Mac you also have an iPhone! Thanks for posting this tutorial!!!

mikespe said:
WOW!!! Thanks!!! I just posted in the when did you root thread that I haven't seen a tutorial on rooting with a mac!!! I did a search and it didn't show up in the results. I figured people assume that if you have a Mac you also have an iPhone! Thanks for posting this tutorial!!!
Click to expand...
Click to collapse
I don't make that assumption.
I have been using Macs exclusively for 15+ years.
I have never owned an iPhone. I like MacOS because it's got BSD Unix under the hood.
I had a NeXT before that.

Here is the easiest way to install adb/fastboot on a Mac, also installs it correctly in your PATH.
Also if you are running El Capitan, see this.

I have been using Fedora Linux to root my devices and as long as the path is setup you do not need the "./" but once you are booted into fastboot, even with proper path, you need the ./fasboot (Don't ask me why, haven't figured it out). You may also have to execute fastboot as
sudo ./fastboot

dratsablive said:
I have been using Fedora Linux to root my devices and as long as the path is setup you do not need the "./" but once you are booted into fastboot, even with proper path, you need the ./fasboot (Don't ask me why, haven't figured it out). You may also have to execute fastboot as
sudo ./fastboot
Click to expand...
Click to collapse
If you use the link at the top, the ./ isn't required any longer, not sure why.

Everyone thank you so much for all the information. I have been a Windows guy all my life. I bought this macbook about a year ago and I'm still learning. Windows I can go into the registry and tweak almost anything....Mac I fee like a rookie. As I mentioned earlier I think I will use my Surface Pro 3 this weekend to root the phone. This way I won't have to worry about doing anything wrong or get frustrated!

jawmail said:
If you use the link at the top, the ./ isn't required any longer, not sure why.
Click to expand...
Click to collapse
The issue is that I need to use sudo to execute the command fastboot. Since it's sudo it doesn't have the proper path, hence the need to add the ./