SU request hangs after root attempt - Galaxy Note 10.1 Q&A, Help & Troubleshooting

Hello world,
I try to make something useful out of my Samsung Galaxy Note 10.1 (GT-n8020), so I've started with reinitializing the device with kies, which got me a fresh android kitkat 4.4.2 rom (build: KOT49H.N8020XXUDNI2). After that, I wanted to flash supersu, of course - I've used chainfires cf-autoroot (CF-Auto-Root-p4notelte-p4noteltexx-gtn8020.zip - cant post links, sorry)
I've also flashed philz recovery which works quite well, over odin.
The problem for now is, I cant use the super user binary:
1. The binary was successfully flashed via odin on the device, like the supersu apk. Opening the app just displays a missing su binary, any other app which requires root cant locate or call the file...
2. The following permissions are set on the su file
[email protected]:/ $ ls -la /system/xbin/su
-rwsr-sr-x root root 96144 2015-09-15 14:44 su
3. I've enabled usb debugging because people like to use magic even if this has nothing to do with the main problem
4. I've tried to execute su via adb shell, but it just hangs.
So if anyone could help, I'd be pretty happy - if not, I'm going to throw this f*ck!ng piece of plastic into the woods.

Alright, using N8020-CWM-6.0.2.8-Darkman.tar.md5 as recovery and CF-Auto-Root-p4notelte-p4noteltexx-gtn8020.tar.md5 as root finally worked.

Related

need help rooting flipside

i have a motorola flipside with 2.2.2 installed. somehow it lost its root and will not reroot z4root keeps shuting down and giving some odd error saying The application z4root (process com.z4mod.z4root) has stopped unexpectedly. Please try again and leaves only the option to force close the app. i left gingerbreak running all night and when i woke up it was still running not getting anywhere theyed superoneclick it will not finish im getting very fustrated with this phone i even went as far as asuming somthing on the phone went bad and flashed it to a stock att rom and still cannot get the root to finish and apply. is there some way i can mannualy root this phone? also yes usb debuging is on allow unknown aps to install is enabled
anyone please this dam phone is practicaly useless without a root to me id rather be using my stupid windows 7 phone at this rate because at least it had my ringtones and allowed me to use a different backround image than stock att ones.
---------- Post added at 02:09 PM ---------- Previous post was at 01:47 PM ----------
ok i have come accross this but i am a little lost at the steps
wiki.rootzwiki.com/index.php/Motorola_Flipside
it says to download 3 files psneuter busybox and super user unzip the downloads into the same folder. then it says to open a terminal and change to the folder i dont understand this what am i suposed to to? it then says i need android sdk installed and working witch i do i installed it for android screencast. then it says adb devices but does not say how im suposed to enter this command. after that im fairly sure its from the cmd entering the commands shown on that link. can anyone tell me how to get throgh the first few steps please?
copyed from link
Manual Root
[edit] Download
psneuter: Download
Superuser: Download
busybox: Download
Unzip the downloaded files into the same folder
Open a terminal and change to the folder.
You need the android SDK and ADB working. To make sure type:
adb devices
if your device lists, then you are ready to go!
[edit] Gain Root
Run the following commands:
adb push psneuter /data/local/temp/psneuter
adb shell
chmod 755 /data/local/temp/psneuter
./data/local/temp/psneuter
ADB should hang, wait a little while and then type:
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
Type:
exit
adb push busybox /data/local/temp/busybox
adb shell
chmod 755 /data/local/temp/busybox
./data/local/temp/busybox mount -o rw,remount /system
The last command should return nothing
update i learned how to do the procedure and finished sucesfully however the phone is still not rooted. i did reboot the phone after it seems faster now but not rooted.i downloaded the root checker app and scaned the phone it emailed me a log and here is that log
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your MB508 device by Root Checker version 3.7 from joeykrim in the Android Market
is it even posible to root this phone?
i guess im not allowed to be helped or somthing.
i have a procedure here that i had to build up from 2 seperate write ups. i had to use this one http://androidforums.com/droid-all-...oid-without-rsd-lite-up-including-frg83d.html along with this one together http://wiki.rootzwiki.com/index.php/Motorola_Flipside to get it to root properly.
here is what i did. u will need the downloads from both links for this to work i beleive. follow the steps from the second link to gain root once u get to where the number simbole is shown in the command line u need to switch to the instructions in link 1 and start at step 13 and follow to the end. this works to root your flipside when nothing els will work at least for me it did none of the apps that are suposed to root for you worked for me.
thank you me for having to figure this out on my own have fun
Problem rooting
I rooted my Flipside at its stock state and it worked fine. And then I upgraded my software to 2.2.2 Froyo and lost the root so now I am trying to reinstall z4root and re-root the phone but z4root now doesn't work. It gets successfully installed but when I hit PERMANENT ROOT it just stays in that window with the turning wheel and gets stuck there. It doesn't completely root. I've tried the hard reset by pulling the battery, and hitting the back key and forced closing it and then trying it again. Nothing works! HELP!
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
jovanphilip said:
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
Click to expand...
Click to collapse
Really? I thought the only upgrade I can do to it is from stock to Froyo. How'd you do that? I'm sorry. I am totally untechie. :/

[Q] Titanium Backup not working on my ROOTED One S

Hi,
Today I've unlocked, flashed Paul's CWM recovery, and then rooted my HTC One S.
I've installed SU and Busybox but Titanium Backup still says it couldn't get root privileges. What am I doing wrong?
reupugi
try to update the binarys in SU
if that fails re flash the root.zip file
happened to me yesterday
Thanx for the quick answer.
When I try to update the su binarys it fails saying it "failed to find currently installed su binery...
What does that mean?
uninstall and reinstall the SU app
or reflash the root file as this is supposed to install SU on your device
Well, last night I spent hours trying to uninstall and reinstall su. I've also flashed Paul's root twice but still no luck.. I've tried to install busybox with two different apps but still no luck... Is there any way to roll back everything and start over?
you need to flash the su through cwm. then you can update the app's. You can not just download a app and think that it will root the phone. Look at step 3.
http://forum.xda-developers.com/showpost.php?p=24478083&postcount=1
So I encountered a similar problem (https://github.com/ChainsDD/Superuser/issues/46).
Edit: Of-course it'd make more sense to confirm if this could be the problem first...
Code:
$ adb pull /system/framework/framework.odex
$ strings framework.odex | grep HtcIntentFlag
@test_code: getHtcIntentFlag:
@test_code: setHtcIntentFlag:
addHtcIntentFlag
getHtcIntentFlag
setHtcIntentFlag
I patched the su binary in accordance with the change I observed in the framework and that works for me.
Could the OP please try the following su binary:-
* http://revolutionary.io/one-s/su (md5sum: 83fdeaef210225d7361e6c8eb63bae96)
This will need to pushed from recovery, something like (after ensuring /system is mounted):-
Code:
$ adb push su /system/bin/su
$ adb shell chown root /system/bin/su
$ adb shell chgrp root /system/bin/su
$ adb shell chmod 6755 /system/bin/su
(You can obviously push to xbin/ if you have the appropriate symlink set-up in bin/, etc...etc...)
zylith said:
you need to flash the su through cwm. then you can update the app's. You can not just download a app and think that it will root the phone. Look at step 3.
http://forum.xda-developers.com/showpost.php?p=24478083&postcount=1
Click to expand...
Click to collapse
I've flashed su through Paul's cwm, following steps 1,2 and 3. I did have a problem entering bootloader through shutting sown - power+vol down. For some reason that didn't work, numerous times, so I got into the bootloader through terminal (mac) and command prompt (win 7).

[Q] Mysterious Superuser/root problem

Ok, so this is the problem:
I have a TF101, rooted since 3.2. I have been able to do OTA updates without problems so far, keeping my root with OTA Rootkeeper.
Last week, I tried figuring out how to automatically mount cifs-shares through Tasker. Whatever I tried, the share would not mount through Tasker. It mounted without problems through command line in Terminal Emulator.
Eventually, i narrowed it down to a root acces problem in Tasker, or the Locale Execute plugin, or the secure settings plugin. I noticed that neither of those had ever asked for SU-acces and there were no logs of it in the Superuser app. When downloading other root-needing apps (e.g. rootchecker), I had the same problem: whenever a new app would normally ask for root acces, instead of the usual Superuser-prompt, the app stalled for a few seconds and then gave an error message or just plain nothing. There was no log of this in the superuser app.
When setting the superuser app to 'always grant root', the situation stayed the same: new apps didn't get root, older apps still had root without problems.
While searching for similar occurences on the internet, I saw a suggestion somewhere to clear the cache and data for the superuser app, so I did.
Now superuser still doesn't prompt and NONE of my apps have root. Apparently even the superuser app itself has no root acces anymore, since it fails to get root acces when updating the su-binary.
My guess was that completely removing su and the superuser app and subsequently re-rooting the whole thing would fix this.
I tried unrooting/rerooting through various methods (Brk, Vipermod, this one, and the new Wolf's thingy), but to no avail.
Brk tells me eveything worked fine, but changes nothing, except it gave me an even older version of the su-binary.
Vipermod hangs on "daemon started succesfully" but apparently does nothing even after 10 minutes.
The Asus Backup Utility method changed absolutely nothing
The Wolf's method looked promising, but installing the "Superuser-3.0.7-efghi-signed.zip" failed. (maybe because I did this from CWM recovery instead of his recoveryblob recovery? Dunno.)
So far I can't seem to remove root, as OTA Rootkeeper assures me the superuser app is installed and the device is rooted, even if the root acces is not granted to it (or any other app).
Any ideas?
Update: tried installing SuperSU from CWM recovery to replace Superuser app, but it gave the same 'installation aborted' message. Is this because CWM has no root acces also?
update2: I have root acces through adb shell apparently. I looked here and here for a way to replace the superuser app. I managed to remount /system, delete Superuser.apk and push the Superuser.apk and su from "Superuser-3.0.7-efghi-signed.zip" onto the device.
No apparent change, not even in the su binary version number reported by Superuser app.
I downloaded the standalone su-binary from here too, and replaced /system/bin/su with that one, too, but after reboot the Superuser app still indicated su binary version 2.3.2-efgh.
I don't know exactly when this problem started, but it could have been caused by the recent update from 9.2.1.17 to 9.2.1.21? Is it possible to revert to the previous version? If so, how? Would I lose data/apps?
Type the following in terminal:
ls -l /system/*/su
My guess is that you have two binaries and one or both of them is not superuser with permission rwsr.xr.x
Ensuring CWM working properly, you just try do backup using CWM then, if it worked then it's has nothing to do with being root access problem. And flashing wolf's root zip via CWM is all it takes to regain root after the 9.2.1.21 update.
Mine was similar root access messed after flashing the 9.2.1.21 update. Tried rectified this by copying su from system/bin to system/xbin but still nothing, but my CWM work though and use it to flash wolf's root zip to correct the su missing in the system. Now it work great..
Sent from my awesome rooted Defy: 2.3.6
@gee one
ls -l /system/*/su gives me this:
-rw-rw-rw- root root 22364 2008-02-29 02:33 su
-rwsr-sr-x root shell 26324 2008-02-29 03:33 su
So you're on to sth. Top one is located in /system/bin, lower one is in /system/xbin.
Now what do I do with this? Copy one over the other? chmod? chown?
@farsight73
As said in the OP, I tried flashing wolf's root zip in CWM, but got an error and it aborted. I did the following:
put zip on removable sd
reboot to CWM
choose update from zip
select the right zip
confirm
I also tried this with /system mounted, but same result.
I don't have acces to pc now, I will try more tonight.a
[SOLVED]
Thanks for the replies, you got me in the right direction in that I was replacing the wrong su in the wrong way.
Since Brk Toolkit managed to get me an older su, I thought it could as well give me the right one second time.
I replaced the su and superuser.apk in the /adb folder of the Brk rootkit with the one from wolf's root zip, and then used Brk Toolkit to install su and superuser.
Upon reboot, the problem was solved.
Thanks a bunch!
For future reference, I think you could just elevate to the superuser by typing in terminal "/system/xbin/su" Then you could fix system/bin/su with "chmod 06775/system/bin/su"
Then " exit" should drop you to a normal shell, and "su" will promote you in the usual way.
The issue here is that xbin and bin are both in your path, and bin is probably first, so the non-super version is "found" first. "echo $PATH" will reveal your path variable.
sent from my transformer
gee one said:
For future reference, I think you could just elevate to the superuser by typing in terminal "/system/xbin/su" Then you could fix system/bin/su with "chmod 06775/system/bin/su"
Then " exit" should drop you to a normal shell, and "su" will promote you in the usual way.
The issue here is that xbin and bin are both in your path, and bin is probably first, so the non-super version is "found" first. "echo $PATH" will reveal your path variable.
sent from my transformer
Click to expand...
Click to collapse
HEY MY FRIED I HAVE EXACTLY THE SAME PROBLEM
chmod 06775 /system/bin/su results"unable to chmod /system/bin/su: readonly filesystem "
echo $PATH RESULTS /system/bin/su: /system/Xbin/su
COULD U HELP ME WITH ZIS MY FRIEND
10Q
From adb or the terminal, type in "/system/xbin/su" to elevate to the superuser. Then mount system to read-write and delete the /system/bin/su version. Remount system as read only.
This will work if you have two versions of su and one of them is not really super.
sent while running with scissors

[Q] Loaded Clockworkmod Superuser Update - Lost Root - Note N7000

Hi All.
Sorry about the noob question, I am not a developer at all, and the only reason I rooted my Galaxy Note N7000 was so that I can update the ROM to the newest version of KitKat once the ROM is stable.
The problem is that last week I flashed the PhilZ-cwm6-XXLT4-OXA-4.93.6-signed file to the phone and it rooted successfully (Superclean asked for root access, I allowed it, and it appeared in the log of Superuser)
The problem happened last night when there was an OTA update for superuser, it said Su Binary needs updating, and I hit yes. I then lost root access as per Titanium backup.
I did a search and someone suggested removing and reloading the original superuser APK but that did nothing.
It seems the binary update pooched the root. Anyone successful in getting it back, or knowing how to?
Anyone can help on this?
It appears from the comments in Google Play that many people that were prompted to update the binary from superuser were left without root.
I lost root access on apps once.
All I did was:
1. re-install "superuser" from Google Play.
2. when opening "superuser" app, it asked to update the SU Binary.. and I allowed it to do so through recovery (TWRP/CWM). (I use CWM).
3. the phone will restart into recovery mode automatically, updating the SU Binary, then phone will restart again back into the OS.
This is all it took for myself to gain SU access again.
This should work if the ROM you're using truly does allow SU access.
OTHERWISE.
You could get the latest Super User.zip for your phone, and run it yourself through TWRP/CWM.
Hope this helps, or at least leads you to an answer.
new su binary is the culprit
Hello,
I too lost root after the su update - Superuser would not prompt any more, and all requests are denied after a timeout. Tried deleting Superuser data, deinstalling and reinstalling Superuser, same with some of the apps, but no avail. Then I noticed that sometimes after reboot /system/xbin/su worked when in android debug bridge shell, so I could get root. Then I replaced the su binary with a copy (in my case of OTA rootkeeper), and all started to work again.
Steps to replace:
1. become root in ADB shell using existing su binary
2. remounting system rw
3. bring replacement su to a ext-fs-partition of your device (needed for setuid)
4. make sure file permissions are set to 06755 (-rwsr-sr-x)
5. exit root
6. become root with newly copied su binary
7. replace defect su with new su
8. remount system ro
Hope koush will stop delivering this defect su soon ... I did mail him already ...

[Resolved] [Q] Help needed rooting G Pro! T_T

*Since this problem can happen to other LG devices, I'm writing here.
-Summarized Question for Busy XDAers-
1.Installed su binary and busybox through Android System Recovery 3e.
2.Can get root access from LG Recovery mode, half access on ordinary boot+adb shell, Permission denied on terminal emulator app. SuperSu not working, and 'root' is granting permission every 5 minutes.
3.HELP PLEASE!
-Full Question-
Maybe it can be a real noobish question, but I need help rooting my G Pro.
LG started Kitkat update a week ago, and G Pro also got Kitkat update.
I tried to root my device using old methods, and new methods for other G devices, but none of them worked.
So! I tried making one for me, using Android System Recovery 3e(maybe it could be a problem?)
I booted my device to recovery using
Code:
'adb reboot recovery'
and sideloaded zip file containing su binary and busybox.
Of course I signed it with testkey, so I could get SuperSu, su binary, and busybox installed on my system.
But, after rebooting my device, I felt something went wrong.
I typed
Code:
'su'
command on terminal enulator, and got
Code:
'Permission Denied'
error.
Assuming it's related to permission and owner of su binary, I tried
Code:
ls -al /system/bin/su
.
Here's the result:
Code:
[email protected]:/ $ su
Permission denied
1|[email protected]:/ $ ls -al /system/bin/su
-rwsr-sr-x root root 85096 2008-08-01 21:00 su
It seems...nothing's wrong!
So I tried with adb, and got # without asking Superuser app.
But I couldn't mount system, as well as other commands require root access.
I removed SuperSu and downloaded Superuser by ChainsDD, but that didn't work.
Instead, I could see on log that 'root' was granting permission every 5 minutes.
Not knowing what the problem is, I rebooted device to LG recovery(diffrent from Android Recovery 3e).
I could access adb from there, and got root access and removed some garbage apps.
Then, it means su binary and busybox is working.
What is the problem??? Please help!
EDIT:It was binary version problem lol

Categories

Resources