Database Users

Frak! Fat fingered permaroot - root is now an unknown user

Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.

vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.

Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!

just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on

vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.

mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.

Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...

Please post questions in Q&A section.

just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.

Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App

Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark

Rooted Then Updated Then Lost Root??

I recently rooted my atrix with superoneclick then i accidently updated then i belive i still had my root until i went to install a 3d theme then my phone crashed and wouldnt get past the at&t screen so i had to erase everything now on my phone i still have "super user" in my app draw but i cannot side load apps did i lose my root? what do i have to do to sideload apps again ? and i guess re root my phone
Yes i am a newb i am comming from IOS and an iPhone 4 please dont flame

If you updated, you mean 4.1.57, this is what I did to re-root when I lost mine after updating and SuperOneClick wouldn't work.
http://forum.xda-developers.com/showthread.php?t=1013931

Ok so i read that so basically i have to flash my phone back to default then root again?

Yeap, that's exactly what I did, but in that same thread, I think someone else outlined using aRoot to go over SuperOneClick.
Originally Posted by donbar85
I'm pretty new to Android (two weeks now), and want to ensure I don't end up with a bricked device, so I apologize for the 'noob' question here. I rooted with SuperOneClick. Has anyone else used this script successfully with that root method, or will it only be successful with aRoot?
Also, if I need aRoot, can I run it over top SuperOneClick, or would it be best to unroot, run aRoot (or let the script root) and then run the script?
I appreciate all the hard work I've seen done in these forums and appreciate any help anyone can offer.
---
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
----
Originally Posted by DJQ1212
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
Thank you both. I believe I will try running aRoot over my SuperOneClick root and then try out the script. Thanks again!
Click to expand...
Click to collapse

Yup the aRoot script is used in the GladiAtrix and possibly the GingerBlur rom as well. Either way. SOC is crap, not meant for atrix anyway. aRoot was written specifically for the Atrix. If you want to update to 4.1.57 read through the retain root thread over in atrix development.

after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?

sam_t610 said:
after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?
Click to expand...
Click to collapse
This has been explained many times. updating kills root, even though you still have superuser installed. to retain root you need to use the script in the development section when updating from 1.26 to 1.57. flash back to 1.26 and try again.

[Q] unable to get su when attempting root

I am trying to root my phone and am running into trouble early. I have watched the videos & followed instructions. Somehow I am either missing something or my phone is jacked somehow.
I made sure it's not in fast boot, USB debugging & unknown sources are on. I have tried visionary r14 & r11. I have also tried multiple factory resets.
OK, I use visionary with set system r/w after root checked. I go from there to Term. Emulator & when I type su it shows "unknown user root" without the quotes. I've tried to continue but it gives me other errors and S is always on when I check.
I've searched Google & the forums and haven't found much that's been able to help me.
If anyone has seen this I would appreciate the help. Thanks!

Visionary (r11 & r14) are only temp root tools. You must use one of the two methods (both are in my signature) to turn s-off. As long as your s-on you will not be able to permaroot your phone.
Once you turn off the phone, and turn it back on you've lost Root Access. and that's why it's given you that error. If you pull the battery wait about 30 seconds, put the battery back in. Then temp root you should see a "superuser" icon appear. Once you see that try your SU command from terminal emulator. The other thing you can try is setting up your ADB (link in signature). Navigate to the c:/adb folder then typing in ADB shell. You should see a $ sign appear. Type SU from the Command Prompt and it should ask you to approve the SU access on the phone. once you've gained temp SU access you can proceed with one of the two methods i've got posted to finish turning s-off.

It's the temp root I'm getting stuck at. I do get the superuser icon after I do the temp root. I go directly to emulator and type in su and that is when it tells me "unknown user root". I will try the ADB method when I get home from work if nothing else is figured out before that.

Same deal for me. Not sure if my MT4G is a newer model or what. I've literally done EVERY set of instructions and youtube videos on rooting and keep getting stuck at the same place. Typing su into terminal emulator and getting unknown user root. I have reset my phone, taken the battery out for five minutes and re-inserted it. I have tried both visionary 11 and 14 versions and clicked temp root. Once the temp root process completes and comes back to visionary+ I go straight to terminal emulator, type in su and get unknown user root. Unlike dbharr I DO NOT get a superuser icon after temprooting with visionary. It's not like i'm fudging up any part of the process here. I'm stuck at like step 2 of the rooting process. Any ideas anyone?
Software version is 2.2.1

You may have a newer chip set and may only be able to root with s-off by using the gfree route. It was the only thing that worked for me.
In my situation I had visionary installed, root folder in the root of my sd card, and followed the unlockr method for root access.
I temprooted and checked temp root on boot and rw one too.
I ran terminal emulator, typed in the commands and the process ran and looked like a success.
I powered my phone down and boot into hboot and s-on showed up.
I tried the same process and factory reset between tries.
I then found out there was another way to get perm root with s-off using a similar process.
I factory reset and placed visionary apk and gfree folder on the root of my sd card.
I went on the android market and installed root explorer (there plenty others you can use it only need to be able to access your root) and also terminal emulator.
I installed visionary and temp rooted (using same temproot method from unlockr.com) my phone I downloaded the gfree file and extracted it on my cpu then moved it to the root of my sdcard.
Then using your root explorer go into gfree folder and copy the file called "gfree" and only this file.
The go into the root of the phone and your going to paste that into the local folder in /data/local/
From there you type in a few commands in terminal emulator. It will run thru a process then power down.
Boot into hboot and verify it shows s-off
If so reboot phone. When your phone boots up visionary should have temp rooted your phone.
If so Open up visionary and uncheck temproot on boot and click attempt perm root. Your phone will reboot and you have perm root. Verify by typing su in terminal emulator and then if you get # your good to go.
If you dont get s-off try factory reset and repeat process, you should be able to find the instructions if you search gfree and it should come up but if im not mistaken its a stickie on the developement forum
Hope this helps!
HTC Glacier
Perm-rooted S-off

If root.sh method is not working, use gfree + visionary method. Worked for me as a charm.

People, please bother to read before answering questions. Marking below the important part of the question that everyone is missing:
corollatercel said:
Same deal for me. Not sure if my MT4G is a newer model or what. I've literally done EVERY set of instructions and youtube videos on rooting and keep getting stuck at the same place. Typing su into terminal emulator and getting unknown user root. I have reset my phone, taken the battery out for five minutes and re-inserted it. I have tried both visionary 11 and 14 versions and clicked temp root. Once the temp root process completes and comes back to visionary+ I go straight to terminal emulator, type in su and get unknown user root. Unlike dbharr I DO NOT get a superuser icon after temprooting with visionary. It's not like i'm fudging up any part of the process here. I'm stuck at like step 2 of the rooting process. Any ideas anyone?
Software version is 2.2.1
Click to expand...
Click to collapse
To corollatercel:
If Visionary doesn't temp-root your phone, you could attempt it using SuperOneClick (google it) from PC, using rageagainstthecage or psneuter method. Just substitute the steps for temp-root using Visionary to temp-root using SuperOneClick.

Jack_R1 said:
People, please bother to read before answering questions. Marking below the important part of the question that everyone is missing:
To corollatercel:
If Visionary doesn't temp-root your phone, you could attempt it using SuperOneClick (google it) from PC, using rageagainstthecage or psneuter method. Just substitute the steps for temp-root using Visionary to temp-root using SuperOneClick.
Click to expand...
Click to collapse
Thanks, this is the answer I was looking for. An alternate method of temprooting. I will try this and post results. Thanks Jack.

Ok you guys may think i'm kidding but I tried both methods outlined
Here:
SuperOneClick trying both psnueter AND gingerbreak options
http://forum.xda-developers.com/showthread.php?t=803682
And
Here:
RageagainsttheCage
http://forum.xda-developers.com/showthread.php?t=792016
and even after superoneclick says its rooted AND says says success when it asks if I want to test root by sending su command, whenever I go into terminal Emulator and type in su I get permission denied or unknown user root whenever I tried su through adb shell through Dos on my machine. I dunno what is it with my device. I did all of this after fresh factory resets just so you all know. I dunno my MT4G must have a newer chipset that's not vulnerable to the current exploits is all I can say. I've follow these instructions to the letter more than twice each time factory resetting just to make sure things are fresh. Still no dice.

I never did get mine working. I did get a warranty replacement & had it rooted within 10 minutes of being out of the box. That makes me think it was something with the phone. Best of luck to others with the same problem.

dbharr said:
I never did get mine working. I did get a warranty replacement & had it rooted within 10 minutes of being out of the box. That makes me think it was something with the phone. Best of luck to others with the same problem.
Click to expand...
Click to collapse
Yeah unfortunately am not in that same position. It sucks. Guess i'm stuck with it for the moment. Only reason I really wanted to root and upgrade was so I could download netflix. I went from the G2 to the MT4G and had NO idea it was just compatible with certain devices. I've tried different versions of the netflix app on here too but they all require you to have root. Hopefully they make the app compatible soon.

Here's an update everyone. I was FINALLY able to get everything working. I had to use a tool called Z4root to gain temproot. You can imagine my relief AND also frustration after I installed z4root and things just started running just the way it was supposed to. I gained temp root in a matter of minutes and after doing so I was able to use the gfree method to perform all other functions that are a part of the rooting process. And for the record ALL other tools did not work for me:
- Both versions of visionary + 11 and 14
- SuperOneClick using psnueter AND rageagainstthecage exploits
Just thought I'd share. Thanks a lot guys. I had already put my mytouch on cl for sale or trade for a G2 because I thought my device could not be rooted or anything. until about 1 o clock in the morning I got it workin...ha.

Thats sweet man im glad you got it done, only difference I was avle to use visionary
Sent from my HTC Glacier using XDA App

Been gone for a few weeks..

Playin w/ roms on my new Rezound... Anyways I noticed the wife's KF got updated to 6.2.2 and FFF/twrp got axed.. Came back lookin for an updated way to get it back quickly. From my last 30 mins or so of reading it would seem the KFU and burritoroot are like fragmented now or something. I tried KFU for twrp and it failed- then I saw there was a burritoroot v3 but it doesn't install a recovery. Just wondering if there's any automated way to get it all done again or if I'm gonna have to keep searchin for links to recoveries etc. If so, no biggie- but if there's an easy way to get twrp back obviously I'll go that route. If there's a thread on it- I must just be missing it- granted I've had a few tonight.

I rooted my 6.2.2 kindle with burritoroot3 and then used KFU to flash TWRP recovery. Make sure you have the updated run.bat found in the KFU thread before trying to flash TWRP

Yep- I found the post from stevenmirabito seconds after posting this damn thread and I've already got twrp back on.. Sorry for the wasted thread.. Still kinda wondering why BR3 hasn't been worked into a new version of KFU but I'm sure if I was really interested enough there's prob some threads on that too- hopefully no drama. Anyways- thanks BluesHawk for responding to my question.
One more thing- I'm assuming it's ok to remove the old burritoroot? Got two icons now

Once you got the burritoroot you may as well uninstall unless your sentimental :_
done and done!

Well- I didn't do perm root- so that I could keep the streaming vid working. I fig'd I'd keep it around though for temp root/unroot

Hag77 said:
Well- I didn't do perm root- so that I could keep the streaming vid working. I fig'd I'd keep it around though for temp root/unroot
Click to expand...
Click to collapse
Unnecessary... Just perm root it and be done with it.
Use OTA Rootkeeper and you will be able to view your Amazon Videos.

Oh ok cool- like I said I've been gone for a while.. Pretty sure last time I was active on these forums OTA RK was a no go for prime video.

It has been the only method that I've ever seen.
o Using OTA rootkeeper use Unroot
o Go to settings -> Applications
o find Amazon Video and force close it
Now run Amazon Video again and it will work. You can even go back and root using OTR Rootkeeper and it will still work until your reboot your device.
This works on the Stock roms... CM7 and ICS doesn't

Cool thx for the info.. Last time (6.2.1) I did perm root, installed market and other apps, FFF&twrp, then unrooted (had to manual delete su files on the device)- so OTA-RK sounds easier. Unfortunately, this is my wife's fire- so I don't get to have that much fun with it. She's way into the amazon ecosystem and likes the stock rom.. So unless ICS final just kicks complete ass- I'll prob have to buy my own to play w/ those roms.. Not even sure why I ended up putting twrp back on it really- I just can't help myself!

krelvinaz said:
It has been the only method that I've ever seen.
o Using OTA rootkeeper use Unroot
o Go to settings -> Applications
o find Amazon Video and force close it
Now run Amazon Video again and it will work. You can even go back and root using OTR Rootkeeper and it will still work until your reboot your device.
This works on the Stock roms... CM7 and ICS doesn't
Click to expand...
Click to collapse
If on CM7, you can leave rooted, use the browser to view Amazon video if you set the user agent to Linux desktop, and that works.

[Q] Need Help - GooManager Error and other question's

Hey Guys,
I recently bought a Nexus 7 from ebay. The guy I bought it from had put Paranoid Android 3 on it. I am cimplete noob and do not know how to root or flash.
I just did something which I dont know how to correct.
GooManager kept telling me there was an update which when tapped on, would bring me to the .zip file i was supposed to dl.
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh

Josh5321 said:
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Click to expand...
Click to collapse
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.

Pirateghost said:
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Click to expand...
Click to collapse
but in the past when I would click on the update notification it brought me straight to the download file. now it just brings me to the goomanager main screen.

reboot the device and try again. or you can go in and clear out all data and cache for goomanager in your settings/apps/goomanager page

I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.

Josh5321 said:
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Click to expand...
Click to collapse
open the NEXUS 7 ORIGINAL DEVELOPMENT FORUMS and download yourself, or open GOOMANAGER and BROWSE COMPATIBLE ROMS...

I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.

TyneBridges said:
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
Click to expand...
Click to collapse
Hi, TyneBridges...
Well, I've never used GooManager myself... but the apps description on PlayStore certainly suggests you do need to be rooted to be use it.
You're a long way from the Motorola Xoom forums (wherever they may be)... but try, from PlayStore, running some app that requires root... like Titanium backup, or perhaps better, Android Terminal emulator (by Jack Palevich)... run it, and type...
Code:
su
If you're NOT rooted, you should see something like this...
Code:
$su
su: not found
$
-------------------------------------------------------
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
If you have some root SU binary installed, then Chainfire's SuperSU app should detect it... and either replace it, or update it.
Anyway... just some thoughts.
I really have no idea what other technical issues/problems there might be rooting a Motorola Xoom. And so you should hunt out the XDA forum for your specific device for more information... I'd be very surprised if there wasn't one.
Good luck.
Rgrds,
Ged.

GedBlake said:
Hi, TyneBridges...
...
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
...
Click to expand...
Click to collapse
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John

TyneBridges said:
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
Click to expand...
Click to collapse
Hi, again John...
I'm afraid I'm a bit out of my depth with the Motorola Xoom... I know absolutely nothing about it. Sorry.
Here's where you should really be asking...
http://forum.xda-developers.com/motorola-xoom
...if anybody can solve your problem, then that's where you're likely to find them.
----------------------------------------------
If you can install a Custom Recovery like TWRP or CWM on your device, then it **SHOULD** (theoretically) just be a case of flashing Chainfire's UPDATE-SuperSU-v1.94, via that Custom Recovery.
On Nexus devices, you use FASTBOOT to flash a Custom Recovery.... on Samsung Devices, you need something called Odin to do likewise.
Once you have a Custom Recovery installed, rooting should be a piece of cake.
Problem is, I have absolutely no idea how to get such a Custom Recovery installed on a Xoom.
Do a bit of research... XDA is a vast repository of considerably more knowledgeable people than myself... and somebody is likely to know something.
Good luck.
Rgrds,
Ged.