Titanium BAckup not opened after root - Intercept General

I have Samsung Intercept from Sprint with Android 2.1, locked. Tried to root it with SuperOneClick 2.3.3. It seems device is rooted (it is not failed during the rooting, and Root Checker shows phone is rooted). SuperUser was installed.
su in /system/xbin
remounting system with read only access
I used simple Root and not Shell Root. I installed Titanium Backup but was unable to start it. I've got the following error:
Could not acquire root privileges. This app will not work. Verify rom is rooted. Attempt was made using /system/xbin/su command.
In Titanium: Root access failed.
So, it seems I'm able to install non-market app but unable to run it, because SU failed to recognize it.
How to root this phone in a right way? Should I unroot it and make Shell Root? Will this unlocked the bootloader? Would this affect the wifi and other phone functions? If the system was mounted with read access only how to get write access rights?
Thank you for your suggestions

I was able to apply temporary root by InterceptRoot software. Unfortunately, permanent root on my device doesn't work.

Related

Root Explorer and Busybox woes, help?

So, I'm rooted. S=OFF, I get su access in Terminal, and I have the latest busybox installed in /system/bin. But, after a reboot of the device I can only get R/W access to certain parts of the directory structure - /system is unfortunately not one of them.
Now, here's the weird part: When I start the app Busybox Installer (downloaded from the market), the app searches for busybox installations and tells me I have the latest in /system/bin (this I already know). Once I have started this Installer without doing anything else, I can gain full R/W access to /system.
So, there seems to be some sort of strange busybox issue and how it relates to system R/W access. Is the latest busybox incompatible with this stock ROM?
Root explorer issues
I am also having the same issue I can not get R/W access in the system folder. I have been trying to re-map the Genius button. I am able to remove "bloatware" by using Titanium backup. I definitely have permanent root on the phone, so I am confused by this issue. I have been searching and have not seen other similar complaints. I tried the busybox from the above post but still am not able to R/W access.
You need the latest version of root explorer. Will solve the issue.
Sent from my HTC Glacier

Busybody caused me to lose root

Ive successfully rooted my kindle(twice), verified through root checker, but when I downloaded busybox( stericson) and double checked for root I get and error message. I did not know this was the original issue the first time. I ended up unrooting and rerooting. The second time the first thing I did after initial root check was to install busybox and this is how I know that is the issue. The main reason I need it is so I can use ad-hoc switcher to tether. I tried other versions of busybox installer but they wouldn't download. I'm looking for an alternative to unrooting and rerooting, but I will if I have to. Also, a busybox installer that works and doesn't unroot my kindle would be nice. The error is as follows:
Superuser Application status: ...installed.
System file
properties for root access: alternative location check command: ls-l/shin/su:
Result: /shin/suermissions restricted and denied access
Standard location
check command: ls-l/system/bin/su:
Result: lrwxrwxrwx root root 2011-12-29 8:52
Su->/system/bin/busybox
Analysis : file:/system/bin/busybox
Alternative location
check command: ls-l system/shin/suck:no such file or directory
Analysis: file /system/chin
Adb shell default User:
Adb shell setting for standard access, stored in default.prop, is configured as: shell(non root) User -to.secure=1
(I did try to access these files to see if I could alter them and it would not let me into them.)
And thanks to all the great help and guides that have helped me root my devices.
Sent from my Kindle Fire using xda premium
read this thread:
http://forum.xda-developers.com/showthread.php?t=1359600
at the end there are all nessesary things for a successful thetering including download sources
good luck !
I will try to download busybox differently next time but that doesn't change the fact that my device is now not showing that im not rooted and I don't know how to undo what busybox did to my settings. Do I need to unroot and reroot or is there an easier fix.
Sent from my Kindle Fire using xda premium
the question is how did you root ? temporary or permanent ?
i recommend the KFU for such stuff - it makes it a lot easier
if you'r rooted permanently with superuser then everything should be ok
as you suggested i would try to unroot and root permanent with KFU
then you can decide to uninstall your busybox version or not and try an other version
I rooted permanent via kfu. Will unroot and reroot again and see if I can make it work this tome. Thanks.
Sent from my Kindle Fire using xda premium

[Q] How can i get ADB ROOT? i want to know rageagainstthecage's working principle

hi,guys!
as this title says i found a tool named "rageagainstthecage",but i want to know how dose it work.Can anyone help me ? thanks
try superoneclick
Are you using Linux to grant root access on your Defy?
I rooted mine yestarday and I was a little confused on how to make it, I have same file as you as I read. rageagainstthecage is the exploit that will you grant root privileges. The instructions for linux are here [1]. I replaced 'exploit.bin' with 'rageagainstthecage' or you can use the one provided in that post 'psneuter', the proccess is simple
1. Copy files to phone using adb (I used /data/local/tmp as directory in the phone): su, busybox, Superuser.apk and exploit (exploit name, let's say: rageagainstthecage)
2. Make the exploit executable and execute it
3. Give permissions to the commands su and busybox
4. There you go
All the credits for the autor of the post on IBM forum
I hope this help you with your question
[1]
PHP:
www_ibm_com/developerworks/mydeveloperworks/blogs/coolwinding/entry/how_to_root_defy_on_linux1
jianbangguo said:
try superoneclick
Click to expand...
Click to collapse
Dose the superoneclick use "rageagainstthecage" to grant adb root access? i just want to know "rageagainstthecage", how dose it work? can you help me? thanks
cristianpark said:
Are you using Linux to grant root access on your Defy?
I rooted mine yestarday and I was a little confused on how to make it, I have same file as you as I read. rageagainstthecage is the exploit that will you grant root privileges. The instructions for linux are here [1]. I replaced 'exploit.bin' with 'rageagainstthecage' or you can use the one provided in that post 'psneuter', the proccess is simple
1. Copy files to phone using adb (I used /data/local/tmp as directory in the phone): su, busybox, Superuser.apk and exploit (exploit name, let's say: rageagainstthecage)
2. Make the exploit executable and execute it
3. Give permissions to the commands su and busybox
4. There you go
All the credits for the autor of the post on IBM forum
I hope this help you with your question
[1]
PHP:
www_ibm_com/developerworks/mydeveloperworks/blogs/coolwinding/entry/how_to_root_defy_on_linux1
Click to expand...
Click to collapse
pardon my poor english,I just want to know how dose it work, for example : rageagainstthecage's Working principle,not how to use "rageagainstthecage" to grant root access,thank you !!
The principle of how it works is very simple, the rageinthecage exploit just forks proccesses until the proccessor hits the max, then the system will kill the olders apps, because you are using adb and running psneuter, the system will kill the adb shell, and here is the magic, when you restart the adb shell it start with root rights, to prevent that, inmediatly adb starts, the system calls setuid function, but because the proccesses list is full, the explot prevents the setuid call, allowing you to maintain the root rights, and in that point, you push Superuser.apk to allow the root access to the apps, changin before the permissions to the su binary allowing you to call that binary with a less rights user, that is the idea beyond the exploit!, wish that help you!
Sorry for the bad english
LeonardoJegigzem said:
The principle of how it works is very simple, the rageinthecage exploit just forks proccesses until the proccessor hits the max, then the system will kill the olders apps, because you are using adb and running psneuter, the system will kill the adb shell, and here is the magic, when you restart the adb shell it start with root rights, to prevent that, inmediatly adb starts, the system calls setuid function, but because the proccesses list is full, the explot prevents the setuid call, allowing you to maintain the root rights, and in that point, you push Superuser.apk to allow the root access to the apps, changin before the permissions to the su binary allowing you to call that binary with a less rights user, that is the idea beyond the exploit!, wish that help you!
Sorry for the bad english
Click to expand...
Click to collapse
Great info, thanks for sharing this with us I was wondering the same

[Q] Fix rooting

Hi,
I have a Chineese device without otg port, so I cannot connect to adb. I want to root the device. I just discovered the su binary exists in the /system/xbin. I would manually fix the root if it is possible, but I can't run the su.
The error I get while running the su binary:
uid 10076 not allowed to su
1. Is there any chance to manually fix the root, and if so what step shall I take?
2. What does is exactly mean when there is a su binary in the system/xbin folder if can't do anything whit that?

how to allow root for apps?

I have a nvidia shield tv with full android 6.
adb root and and adb remount is working, so I have root access on shell level.
Also I have /system/xbin/su which goes into root if I do not use "adb root".
But root for apps does not work. No app gets root access, RootChecker says "no".
I installed Superuser.apk but this did not help.
What is missing?
I see that this:
java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Caused by: java.io.IOException: Permission denied
I saw that RootChecker tells me "SELinux enforcing", is this the problem?
I do not want to download any ready-made root miracle and flash the whole device.
Since I have adb root, I can adb push everything.
Just flash su.zip and all will be fine.
I don't need SuperSU. I want to root my device i.e. that apps can execute su.
I have /system/xbin/su but it seems that apps cannot use it.
SuperSU is required to give root access to apps, even with full Android. You will need to flash the zip file from TWRP recovery.
How does SuperSU work?
As far as I understand, there is a /system/xbin/su which is called by apps wanting root access.
This su binary then starts the app to verify access. Right?
Not sure, but I think that su is just for adb and maybe system apps.
On my system I have "adb root" access. But apps do not have root access, I do not have supersu or su.

Categories

Resources