Hoping for some help because I've ran into some really odd issues with SuperUser/root on my TF101.
I used the guide in the Dev Forum and flashed to Prime 1.4, everything was great and working well. I made a Nandroid of my base to fall back on.
ChainsDD updated SuperUser on 6/10 or 6/11 and I accepted the update from the market. When I launched SU, I was prompted to update the Binary, I granted SU root access and it said it completed. However, since then, no app that requires root has requested SU according to the log and Kernel Manager is telling me I don't have root.
If I open Terminal Emulator, it is automatically at a # rather than a $
In Root Explorer, tapping the Mount R/W button changes to R/O and I was able to successfully create and delete a test folder in /system
I need to get SuperUser functioning again, any thoughts or ideas?
What's a TF104 model device?
Um. you do know that # in terminal emulator indicates that the app currently has root access?
Open superuser, its being recognized as permanent root because you allowed it to have root access.
And its TF101 not TF104.
Sorry, misread the model...
I know the # means root that's why the title is kinda lost root...
I'm not getting any of the notifications that SuperUser granted access, like I used to. Also, Kernel Manager isn't being granted Root access when I launch it
I think the SuperUser binary update failed, I got the binary from goo-inside.me and flashed it from CWM. Then I cleared the SuperUser app data and launched it. I was again prompted to update the binary version. It failed and prompted me to to flash a zip that it downloaded to my SD card. That zip is a 0kb file.
Try downloading superuser from the market.
david279 said:
Try downloading superuser from the market.
Click to expand...
Click to collapse
Same results
Also, Superuser is now randomly Force Closing on launch.
Talked with ChainsDD, it's a problem with how he compiled Super User for honeycomb. Fix will be released tomorrow.
Sent from my gginggerfied EVO
Fixed binary has been posted to goo-inside.me
Sent from my gginggerfied EVO
Related
Hi all!
First off, I'm new to xda Developers so please excuse me if this is in the wrong forum! I thought I'd post information about a tool I wrote here which roots stock 4.0.3 leak on the A500, A501 and assumingly the A200 too. Its literally one click - just enable USB debugging. "ICS Root" also installs, optionally, FaceLock and Trebuchet (although FaceLock doesn't want to work. It lets you set it up though =P)
Since version 5.0.1 this also now works with the new 0.022.00 leak!
The full post is over at TegraOwners: http://forum.tegraowners.com/viewtopic.php?f=30&t=350
The only real system requirements are Windows (with .Net Framework 4) and an Iconia on the stock 4.0.3 leak. I hope somebody finds this useful its been tested by myself and a couple of TegraOwners users and it works well.
In terms of the technique used, it uses the great Jay Freeman's mempodroid exploit to gain root at which point it mounts /system rw and installs su, busybox and Superuser.apk so no real surprises there. Installing Trebuchet adds that apk to /system/app and installing FaceLock installs the apk to /system/app before installing the pittpatt folder to the flexrom (mounted as /system/vendor). I plan to open source it when all the requested features have been implemented and the code has been cleaned up.
Thanks!
~blackthund3r
EDIT 14/05/2012: ICS Root 7 is out enjoy!
Sent from my A500 using Tapatalk
cwm version?
why would it not work with cwm version?
With this tool does system remain writeable after rooting?
What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...
lowsum said:
What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...
Click to expand...
Click to collapse
If you are on the cwm with the HC boot loader it should work as Its Magic will be run..
if you are on the new boot loader as in the full non modded leak.. It will give you secure boot error ..
The new boot loader Blocks its magic.
Thanks
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!
JeanBubu said:
why would it not work with cwm version?
Click to expand...
Click to collapse
It would but the cwm one, afaik, is prerooted?
Sent from my A500 using Tapatalk
root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.
nifterific said:
root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.
Click to expand...
Click to collapse
That's storage cos terminal works for me and running su in an adb shell works great too.
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
# exit
[email protected]:/ $ su
#
Sent from my A500 using Tapatalk
SteamBishop said:
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!
Click to expand...
Click to collapse
You're welcome and I'm glad it worked!
Sent from my A500 using Tapatalk
After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.
SteamBishop said:
After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.
Click to expand...
Click to collapse
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
Sorry for offending you and whoever else it did. Thank you for pointing that script out in that post. My intent was to offer a second comment to your assessment..
nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk
New update out!!
blackthund3r said:
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Version 3 came out this morning
It features some bug fixes as well as a completely new remount menu which mounts /system rw properly on the fly. Tested with a busybox installer app
Enjoy!
Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.
paugustin said:
Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.
Click to expand...
Click to collapse
ah okay it appears a completely new leak has been released. It is possible that the mempodroid exploit has been patched up. I'm gonna look into it soon. I can't much tonight - I have school work. I'll see what can be done and what the differences between leaks are.
Sent from my A500 using Tapatalk
EDIT: mempodroid hasn't been patched See ICS Root v3.1
Hi blackthund3r
Thanks for the update 3.1 but could you please fix the problem on your hosting website? clicking on this file send to an error warning.
The other files can be downloaded though.
can someone post a mirror to the 3.1 version? current link is not working.
can somebody also confirm, if i root with this tool, i will be able to reinstall my clockworkmod recovery through 'acer recovery installer' and flash any other cwm rom? or do i have to downgrade to honeycomb 3.01, install iconiaroot for honeycomb and then acer recovery installer?
Gersma,
I'll be able to answer to your question as soon as I'll be able to download this tool and test it.
When apps that ask for root permissions are launched, it doesnt work, example: TI backup says that the device isnt rooted and i might have to check the SU binaries. My N7 was rooted before a update for Superuser was available, now something happen after i updated it. But i dont know what...
That's weird. After you updated your SU, did you go to SU to update its binaries?
i did that twice, and it did say to update binaries...so...
you might need SuperSu instead
What Android version are you running?
Droid_Boi86 said:
i did that twice, and it did say to update binaries...so...
Click to expand...
Click to collapse
I had similar problems with "lightly rooted" stock (4.2.1/JOP40D) using a slightly older version of Superuser. Some apps could get root and others could not. But things have been in flux recently; read on...
I poked around a little bit and it appeared that the 4.2 multi-user stuff was interfering with the way that older versions of (ChainsDD's) Superuser worked, and at that time (only a couple weeks ago) ChainsDD had not released a newer update - things were still in flux.
I switched over to SuperSU, and no problems since... but....
...for me, installation of SuperSU didn't go swimmingly. As I recall the SuperSU install instructions say something like "you need to already have root to install the SuperSU `su' binary". Makes sense as it needs to write it's 'su' binary into /system, which in turn means it needs to get root privilege from a pre-existing su/Superuser installation.
So it poses a chicken-and-egg problem if you have lost root completely which I somehow managed to do... wait, I remember now! I had left the old 'su' binary in place, but had manually uninstalled "Superuser" from /system before I attempted the SuperSU install. Doh!
If you have lost root... you can manually install SuperSU offline inside the recovery via adb & the command line, which means getting both the SuperSU.apk and the 'su' binary ahead of time.
You can get the .apk from the market. You can attempt an install - it will download the 'su' binary and (no kidding) place a copy of it in /data/data/eu.chainfire.supersu/files/superuser.png
If you haven't lost root completely inside the booted OS, I suggest mounting /system in "rw" mode prior to running the SuperSU install and startup.
It looks like I am back a version or two - I have superSU v 0.99
4d7abc0eb5898cdb81bc233dcd16e052 /system/app/SuperSU.apk
0034ec008416b1c3fa7010deb8a3a758 /system/xbin/su
-rwsr-sr-x 1 root root 91992 Jan 10 16:40 /system/xbin/su
note the setuid,setgid bits on /system/xbin/su. Also - no symlink from /system/bin/su to xbin/su.
OK, sorry for the long post. There have been new releases from both chainfire (SuperSU) and chainsDD (Superuser) quite recently. Since I haven't had any troubles since 10 January, I haven't been following it closely - YMMV.
cheers
So I did the "temp un-root" in Voodoo OTA Rootkeeper before updating to the new OTA build. The update was successful. I then went back to Voodoo and restored root access. It confirmed that I had root. I then went to SuperSU and it seemed to be working fine as well. TiBu also seemed to be working fine.
I then went to ES File Explorer, which I confirmed had been granted root access, and tried to rename the PowerOn.ogg file in order to stop the AT&T bootup sound. The rename did not work, but no error message. Out of curiosity I then tried to cut and paste that file up one directory and it told me it failed due to insufficient privileges. Does this mean something is wrong with my root?
It reminds me of a time on my Galaxy S3 when I did the exact same process with Voodoo and an OTA update...and everything seemed to be working fine...but when I was testing out the then newly released Carbon backup app, it failed to get proper root access every time until I finally just re-rooted the device.
I can't understand why I am having issues, but everything is reporting that I have proper root access. I even downloaded Root Checker and it confirmed my root access.
Any thoughts? Thanks!
The new es is a pain...you have to go to menu then tools then root explorer then mount r/w then check the rw side next to /system in order to write to anything in /system
Have to do it every time you start es
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I have just rooted my 4.4.4 Xt1028 using KingRoot v 4.5.0 it's not permanent and I can't get xposed to install because of the ro system, My main phone is an xt1028 that was unlocked with sunshine on 4.4.3. However sunshine doesn't support the 4.4.4 so Im at a loss on what to do next. Any suggestions?
Indeed, I've stumbled upon the same thing!
Root goes away after a reboot, but enough to run TitaniumBackup, or a few other apps that want root in order to read the file system.
This is identical to the prior PIE exploit that worked up to 4.4.2 I wonder if there is a way to package this stuff from KingRoot in order not to waste time running it so obviously after each reboot ...
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623
i got a 2013 Moto G Vzw prepaid that i got back when they were $24.95
been waiting to see if it can be rooted or unlocked to get CM installed or something
i turned it on today, tried the activation bypass and i was able to get into the OS
( pressing next, pull down noticication, then multitask and swype away)
(this device is on KK 4.4.4)
i was able to install and run kingroot 4.5.0 and it gave me some error, BUT it worked successfully anyways....
i can confirm root with titanium and terminal etc...
i have yet to restart it, but my purpose of this is to use it as a gopro remote, or playing ingress or some type of home automation
this should get my by until something else is found
The root is temporary whether or not you reboot. After a while, root stops working and sometimes makes your phone unstable. Everything may start to crash and you'd have to reboot your phone.
Teet1 said:
The root is temporary whether or not you reboot. After a while, root stops working and sometimes makes your phone unstable. Everything may start to crash and you'd have to reboot your phone.
Click to expand...
Click to collapse
This is true, I've seen it too.
What is interesting is that root checker claims that there is /system/xbin/su present by Kingroot. But /system is always read only. ES explorer appears to create files in /system, but if you quit and re-launch, there are no files there.
From shell, I tried to quickly replace KingRoot with SuperSu :
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
This did not work since in shell it claims that the file system is read only.
I wonder how Kingroot manages to maintain the illusion of /system/xbin/su for a while.
There could be a way to authorize SuperSu with Kingroot, and keep the temporary root all the way until a reboot.
I would be so happy to have xposed frameworks at least maybe busybox. my main phone is an xt1028 unlocked but my brothers was already on 4.4.4 that's why I'm so excited about this progress
bibikalka said:
This is true, I've seen it too.
What is interesting is that root checker claims that there is /system/xbin/su present by Kingroot. But /system is always read only. ES explorer appears to create files in /system, but if you quit and re-launch, there are no files there.
From shell, I tried to quickly replace KingRoot with SuperSu :
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
This did not work since in shell it claims that the file system is read only.
I wonder how Kingroot manages to maintain the illusion of /system/xbin/su for a while.
There could be a way to authorize SuperSu with Kingroot, and keep the temporary root all the way until a reboot.
Click to expand...
Click to collapse
If it manages to write into /system, perhaps we can exploit KingRoot to do some more in depth stuff?
Teet1 said:
If it manages to write into /system, perhaps we can exploit KingRoot to do some more in depth stuff?
Click to expand...
Click to collapse
It does not write into /system, it just fools the OS for a short while that somehow "su" was placed into /system/xbin . That's the strange thing about it!
bibikalka said:
It does not write into /system, it just fools the OS for a short while that somehow "su" was placed into /system/xbin . That's the strange thing about it!
Click to expand...
Click to collapse
I read it uses an exploit on the system to gain root or temproot. Maybe we can do the same?
As the title states, my device /system is mounted as R/O and cannot be switched. This ROM has a prebuilt rooted in it, but I tried using Root Explorer, ADB on PC, apps on Play Store, but no luck. So I was wondering if there is a work around with this.
Device:
Redmi Pro
MIUI 7.6.10 | Weekly Build
Android 6.0
Pre-rooted
What root "manager" are you using (SuperSU)? When you try to make a root operation, does the root manager pops up and asks you to grant root permissions? I think you don't have a root manager installed or working properly...
wizard8400 said:
What root "manager" are you using (SuperSU)? When you try to make a root operation, does the root manager pops up and asks you to grant root permissions? I think you don't have a root manager installed or working properly...
Click to expand...
Click to collapse
I'm using internal root, which is not using TWRP to flash SuperSU, and I can assure you that I have root installed.
http://imgur.com/f82RoiB
This app won't lie isn't it?