Thinking about rooting the tfp for the first time. What's the best way from .28?
Currently this is the only way to root .28 if you haven't rooted before. http://forum.xda-developers.com/showthread.php?t=1706588
Sent from my ADR6425LVW using XDA Premium.
I have had great success with that tool. I was on .21 rooted, but OTArootkeeper didnt keep root (derp) so I rooted with Debugfs, just do what it says on the tool and make sure you have the drivers and you're away.
It also adds the Superuser app
Worked for me But....
SteveG12543 said:
Currently this is the only way to root .28 if you haven't rooted before. http://forum.xda-developers.com/showthread.php?t=1706588
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
The root method worked like a charm on my TFP .28
I used root checker and it confirmed that I have root access.
However, most of my root apps are not working and say that they have no root access, despite allowing them using Superuser app.
Could it be with the error I got on step two (Check Attached.)
Manar Aleryani said:
The root method worked like a charm on my TFP .28
I used root checker and it confirmed that I have root access.
However, most of my root apps are not working and say that they have no root access, despite allowing them using Superuser app.
Could it be with the error I got on step two (Check Attached.)
Click to expand...
Click to collapse
im not sure about others
but im having a real hard time reading what it says, could you type out what it says in your cmd?
also did super user get installed onto your prime? if so open it and make sure you have the latest binary on there~
yeah i can barely read it lol
lil-devil said:
im not sure about others
but im having a real hard time reading what it says, could you type out what it says in your cmd?
also did super user get installed onto your prime? if so open it and make sure you have the latest binary on there~
Click to expand...
Click to collapse
Here is what it says,
Step 2 - Rooting...
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: Allocate inode: 1431
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Yes SuperUser was installed
After a second thought, I think I forgot to check if the binary is up to date.
My TFP is not near by. I will check it when I go home.
A million thanks if it turns out to be the problem.
Manar Aleryani said:
Here is what it says,
Step 2 - Rooting...
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: Allocate inode: 1431
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Yes SuperUser was installed
After a second thought, I think I forgot to check if the binary is up to date.
My TFP is not near by. I will check it when I go home.
A million thanks if it turns out to be the problem.
Click to expand...
Click to collapse
yeah thats usually the problem
when i first started mine i went omgwtfbbq at it too xDD
let us know if thats the problem or not!
lil-devil said:
yeah thats usually the problem
when i first started mine i went omgwtfbbq at it too xDD
let us know if thats the problem or not!
Click to expand...
Click to collapse
I tried to update the binary and this is what I get (Check Attached.)
Same problem. Still most root apps not working
Personally, I was able to get the debugfs batch file to work properly, but it took some doing.
My .28 TF Prime wouldn't reboot fast enough for the batch file to work right, so I ended up messing around with the batch file a bit to get it to work.
Even still, the second reboot was too slow and it failed to install superuser. However, I just downloaded SU from the Play Store and it worked fine.
I would recommend running the debugfs batch file again and see if that might fix the issue since your SU binary is already up to date.
Manar Aleryani said:
I tried to update the binary and this is what I get (Check Attached.)
Same problem. Still most root apps not working
Click to expand...
Click to collapse
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Hello, when i try to use this tool on my TFP .28, it just sticks at
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
Just use straight commands, dont use a script/toolkit, if you dont know how to tweak or dont understand it
Sent from my i9250
Gipjoe said:
Hello, when i try to use this tool on my TFP .28, it just sticks at
Click to expand...
Click to collapse
Make sure you have ADB and the drivers installed.
---------- Post added at 09:12 AM ---------- Previous post was at 09:08 AM ----------
lil-devil said:
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Click to expand...
Click to collapse
Titanum backup is actually one of the apps that work.
I'm having problems with other root apps.
And yes; they do ask for root access and I grant them.
I will try to use Super SU. But will I have to disable the original SuperUser app? And how?
lil-devil said:
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Click to expand...
Click to collapse
I tried downloading Super SU. It changed nothing but ruining my original super user app. Now the app allows all root apps without prompt and I can't use the Super SU because it's Super slow
Related
I recently won this developer tablet and I can't seem to get on-device root access. It came with su binaries installed. (very old ones but I updated it) It also has an unsecured kernel because ADB always runs as root. However I installed superuser and it can't get root access and when other apps attempt root access something seems to be denying access before the superuser prompt is even able to come up. Just curious if anyone has any ideas??
JBO1018 said:
I recently won this developer tablet and I can't seem to get on-device root access. It came with su binaries installed. (very old ones but I updated it) It also has an unsecured kernel because ADB always runs as root. However I installed superuser and it can't get root access and when other apps attempt root access something seems to be denying access before the superuser prompt is even able to come up. Just curious if anyone has any ideas??
Click to expand...
Click to collapse
This may seem like a stupid suggestion but I suppose you could try uninstalling the superuser app and use Chainfire's Super SU app to see if that might make any difference.
Tried that too lol. I was even able to go into old su app and toggle permission for super su to allowed and it still said fail when it tried to update binary. Thanks for the suggestion though. It seems to me the problem is that the chown and chmod commands are not sticking on the su binary. They appear to work but the actual ownership and permissions of the file don't change. Even when I do adb remount first.
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
JBO1018 said:
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
Click to expand...
Click to collapse
One way to get your games to work would be try side loading the Modern Combat 3 and Nova 3 APK's onto the device and installing them manually that way. Another way if that doesn't work is you could try modifying your build.prop and changing your product id to match the galaxy nexus that way the play store will think your on a galaxy nexus and it should say that the games are compatible then.
JBO1018 said:
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
Click to expand...
Click to collapse
I know this is an older post but I'm at the same point where I can't figure out how to allow superuser access. I'm using the 8064 for research and I need the root access but can't seem to figure out how to update the SU. Any tips?
mcforan said:
I know this is an older post but I'm at the same point where I can't figure out how to allow superuser access. I'm using the 8064 for research and I need the root access but can't seem to figure out how to update the SU. Any tips?
Click to expand...
Click to collapse
Do you have the Superuser.apk app installed along with the SU binary in the correct place /system/bin as mentioned by JBO1018? If you already had working root access before on the device and just need to update the SU binary you can open the Superuser app, then go under the info tab and tap on the SU binary version number this should then check for updates and then ask you if you want to install any found updates.
shimp208 said:
Do you have the Superuser.apk app installed along with the SU binary in the correct place /system/bin as mentioned by JBO1018? If you already had working root access before on the device and just need to update the SU binary you can open the Superuser app, then go under the info tab and tap on the SU binary version number this should then check for updates and then ask you if you want to install any found updates.
Click to expand...
Click to collapse
I have both the Superuser.apk and SU binary in the right place. Each time I open up an app that needs root access a toast message pops saying that the app has been denied Superuser permissions. I tried restarting both apps but its not working.
mcforan said:
I have both the Superuser.apk and SU binary in the right place. Each time I open up an app that needs root access a toast message pops saying that the app has been denied Superuser permissions. I tried restarting both apps but its not working.
Click to expand...
Click to collapse
Try going into the Superuser app and under settings and then security the default behavior is set to prompt not deny.
Sent from my SCH-I535 using xda premium
join have a tablet TIR 8960 is preloaded with windows rt, tablet says about the problems of the system,
Hello
To be honest im beginning to wonder why I even bothered rooting my S3 seems to cause more hassle than its worth.
The only reason I rooted it was so that I can use the Vodooo Sim Unlocker App on my handset. I bought it on ebay and rooted the phone and used Vodoo to unlock the network lock all worked fine for a while until last week when I was on holiday I got an OTA update ...so I installed it since then when I start my mobile its asking for the Sim network pin code.
I am trying to get Three to provide this but they say the previous owner (off ebay)has to approve this or they cant do it.
I think that the root access on my mobile is fooked so I downloade dan app called Root Checker Pro results are below:
===========================================================
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.91 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root shell 91980 2008-08-01 13:00 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
===========================================
I have tried to re-root my device by using the same method that worked the first time i.e http://reviews.cnet.co.uk/mobile-phones/how-to-root-your-samsung-galaxy-s3-50008588/ but this does not work now any tips what I can do?
Get your info/rooting methods from xda only, everyone else in the world is stupid.
Flash cf-root and stop blaming root for user error, tbh your post was a case of tl;dr but from what I've experienced its user error 99.9% of the time.
Sent from my GT-I9300 using xda premium
Like I said It was working fine before the OTA update so that was my fault for downloading the upgrade...right ok thanks for your help...
slinkydonkey said:
Like I said It was working fine before the OTA update so that was my fault for downloading the upgrade...right ok thanks for your help...
Click to expand...
Click to collapse
Obviously the OTA broke root access, that's what happens.
Use Odin to flash cf-root 6.4 and Bob's your uncle.
Sent from my GT-I9300 using xda premium
nodstuff said:
Obviously the OTA broke root access, that's what happens.
Use Odin to flash cf-root 6.4 and Bob's your uncle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ok ill try it again tonight I was going to ask you to send me a link the the official XDA developers way of doing it but might be a bit tricky on a mobile so ill take a look around but im sure ive already tried this but ill try again tonight thanks
im assuming i cant just use? http://forum.xda-developers.com/showthread.php?t=1703488
If you couldn't be arsed learning what you are doing and why, and also learning so that you never get stuck in a situation like this again then work away with the toolkit.
Personally I think its the wrong way to do it.
Find the cf-root thread and do it that way if you want to learn how to do something.
Sent from my GT-I9300 using xda premium
nodstuff said:
If you couldn't be arsed learning what you are doing and why, and also learning so that you never get stuck in a situation like this again then work away with the toolkit.
Personally I think its the wrong way to do it.
Find the cf-root thread and do it that way if you want to learn how to do something.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
ok ill search it out but to be honest I have enough learning IT at work
slinkydonkey said:
ok ill search it out but to be honest I have enough learning IT at work
Click to expand...
Click to collapse
Well, if you want something easy to use and doesnt require learning then get an iphone Or dont mod your gs3.
If you only rooted to unlock wouldnt it have just made more sense (and less hassle if you don't know what you're doing) just to buy an unlock code for 10 bucks and be done than trying to dive in the deep end without knowing how to doggy paddle to accomplish the same thing?
plus with odin it couldnt be anymore simple especially for an IT guy.
get odin
get the cf root tar
boot the phone in download mode
point odin to the tar file and flash
it's pretty darn simple actually
graffixnyc said:
Well, if you want something easy to use and doesnt require learning then get an iphone Or dont mod your gs3.
If you only rooted to unlock wouldnt it have just made more sense (and less hassle if you don't know what you're doing) just to buy an unlock code for 10 bucks and be done than trying to dive in the deep end without knowing how to doggy paddle to accomplish the same thing?
plus with odin it couldnt be anymore simple especially for an IT guy.
get odin
get the cf root tar
boot the phone in download mode
point odin to the tar file and flash
it's pretty darn simple actually
Click to expand...
Click to collapse
Your right to a point I should of just bought an unlocked S3 off ebay thats my fault ..I had tried the odin method yesterday it didnt work then but today it has so im happy now ive run Vodooo and my mobile is working again. I use the S3 for my small business and partiuclar apps like Barclays app does not work on Rooted phones so maybe I should of get an iphone haha but im not that stupid .. :laugh:
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
hx4700 Killer said:
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
Click to expand...
Click to collapse
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
weakenfalls said:
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
Click to expand...
Click to collapse
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
hx4700 Killer said:
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
Click to expand...
Click to collapse
I get # in ADB but not using Terminal Emulator. What does this mean?
Restorer said:
I get # in ADB but not using Terminal Emulator. What does this mean?
Click to expand...
Click to collapse
Hmmm I will have to try in ADB and see what happens.
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
hx4700 Killer said:
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
Click to expand...
Click to collapse
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Restorer said:
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Click to expand...
Click to collapse
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
hx4700 Killer said:
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
Click to expand...
Click to collapse
I get:
"mount: Operation not permitted" .
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Sorry, just tried again and now stage 11 is working! But then when I try 12 I get:
"r.apk of=/system/app/Superuser.apk
/data/local/tmp/Superuser.apk:cannot open for read: No such file or directory
1:[email protected]:/#"
re root jellybean
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Whooo! Just got my root back. I hadn't realised there are a couple of typos in the guide there and I was copying and pasting the long lines!
Big thanks to hx4700 Killer for making me wonder I must be doing something wrong :laugh:.
tomtomxp said:
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
Click to expand...
Click to collapse
Well.. I believe that everyone who'd not consider unlocking their tablets before the JB update would not unlock after losing root just because of the warranty, probably not because they don't know how but because about half of the forumers don't think it's worth the risk considering the hardware instabilities like the green camera module, light bleed etc.
And since you've already flashed a custom recovery you've unlocked more than just root, why not try a custom ROM based on stock JB?
Update 9/14/2013
A better solution has been released, please update using it.
http://forum.xda-developers.com/showthread.php?p=45598648
Warning: Don't attempt to use this on a device that isn't Motorola.
Lets break this sub forum open with a good one.
See: http://www.androidpolice.com/2013/09/12/exclusive-how-to-root-moto-x-ultra-mini-and-maxx/ for the story
Bounty payouts or donations can be paypaled to [email protected], or use the donate button to the left. If its for the bounty, please reply below with confirmation number or pm me.
These files are not to be mirrored elsewhere, no included in other packages. Its simple already, no need to repackage it.
Same APK should work for Maxx, Ultra and Mini. If it does not, I just need to rebuild it and need someone to test, it will work.
adb install -r <filename>
Run MotoRoot app
Press Setup
Install Supersu app
Phone will reboot, and you will be rooted as soon as device is fully booted.
Limitations:
Uninstalling the app will disable root until reinstalled
supersu is not able to update su yet, this will be fixed in an update shortly.
su is maintained in a ext4 img at /data/xbin.img and mounted over /system/xbin at BOOT_COMPLETE.
su is not available for the first few seconds of boot, im working on this.
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Unroot:
Two choices, factory reset, or press the unroot menu option in the app.
Problems:
Run into a problem? try hittung unroot then re-rooting
Credits:
We use two vulns in this app, first being 9695860 to gain system user, then a symlink attack of mine to get root from system.
xIndirect (nick) for assisting me from start to finish
Whoever originally found bug 9695860
Saurik for his description of 9695860
Ryan Welton for his 9695860 tool
Dave Kover for yet another kick butt icon
and Anthony Fox/Droid-Hive for great help with getting the device to me today
Very much appreciated.
PayPal transaction ID 4GK69936510343543.
Ignore everything I said, I will send my donation thank you
jcase said:
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Click to expand...
Click to collapse
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
jcase said:
su is not available for the first few seconds of boot, im working on this.
Click to expand...
Click to collapse
and dose this mean files cant be pushed with adb as a work around?
Confirmation number: 3FS7579230091290J
Thanks!!
Confirmation 17R58863KC726802C , I didn't pledge on the bounty thread.
Yes!
Worked like a charm!
Been waiting for this since day one. You are a god sir.
TheWhiteChallenger said:
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
and dose this mean files cant be pushed with adb as a work around?
Click to expand...
Click to collapse
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Thanks man!
Sent from my XT1080 using XDA Premium 4 mobile app
got adfree working, but you have to do it QUICKLY. remount /system as rw, then immediately press the update button on the adfree app. the changes will remain until reboot, but I hardly ever reboot
busybox mount -o remount,rw /system;
Thanks...didn't expect to have root so soon. Confirmation 7PD1555899342392B - pledged over on the Droid Ultra bounty page
Droid Mini Confirmed! Thank you!
Sent from my XT1030 using xda app-developers app
jcase said:
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Click to expand...
Click to collapse
ok kool, i dont mean to sound ungrateful thats just mainly what i use root for is fiddling with stuff of the system folder, so i was just wondering if i was permanently screwed of if was something that is atleast being working on, thanks again ill be sending my donation as soon as i remember my paypal pw, lol
Should USB Debugging be enabled?
is the "Transaction ID" the confirmation number?
Thanks! 8JG23957NE2435454
Posted from http://forum.xda-developers.com/showthread.php?t=2431005
Confirmation number: 4JK07192689429602
Thanks!
So this has to be installed by adb? What if in my haste and excitement, I "accidentally" installed it without ADB? I noticed I can't uninstall it. However, when I do Root Checker, it shows I'm rooted but I can't install SU it says "Installation Failed!"
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
I'm getting the exact same thing, if you push cancel it just closes the app.
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
Just don't open SuperSU once it's installed. Reboot one more time and you'll get regular prompts from SuperSU to allow permissions as apps request root.
Hello,
I rooted my 8.9" and lose root after i installed busybox. Right now, i cannot install SU binary. I tried factory reset, unroot, and reroot without any success. Is there a way i can install SU binary manually?
Thanks.
anyone???
It appears that I will have to live with it.
Thanks.
auky said:
It appears that I will have to live with it.
Thanks.
Click to expand...
Click to collapse
I don't know what or how you did what you did. You won't get many answers without providing specific examples.
I for one have NEVER heard of ANYONE losing root from BusyBox, but everyone I know, including myself, uses BusyBox Pro v. 10.5 currently. Most of the people I know also use SuperSU from Chainfire. Generically saying tha some busybox installation messed with some generic root or SU installation/binary, really does not give anyone much to go on.
You can apply the root exploit again. There is no issue with that, or you can use adb to copy the su binary over, set permissions & ownership & the cp it to the correct directory.
At any rate, there are too many possibilities & possible solutions depending on what you did & how you did it.
GSLEON3 said:
I don't know what or how you did what you did. You won't get many answers without providing specific examples.
I for one have NEVER heard of ANYONE losing root from BusyBox, but everyone I know, including myself, uses BusyBox Pro v. 10.5 currently. Most of the people I know also use SuperSU from Chainfire. Generically saying tha some busybox installation messed with some generic root or SU installation/binary, really does not give anyone much to go on.
You can apply the root exploit again. There is no issue with that, or you can use adb to copy the su binary over, set permissions & ownership & the cp it to the correct directory.
At any rate, there are too many possibilities & possible solutions depending on what you did & how you did it.
Click to expand...
Click to collapse
Hi GSLEON3,
You have given me hope. Thank you for the respond. I rooted my HDX 8.9 with no issue. Without knowing if I have busybox, I downloaded and installed the attached busybox apk. After that, I lose root. When I open SuperSU, I was asked to install SU binary, but when I click "Normal", the SU binary installation will fail. I tried unrooting and rerooting (with Bin4ry method as well as manual) without any success. Error messages such as "must be SUID to work properly" when I tried unroot and reroot. Guess i lose write ability. I will really appreciate it if you can tell me how to adb to copy SU binary or help me get root back.
Thanks.