Related
I decided to go back to stock when the new Jellybean finally rolled out.
So I wiped the phone. and put the factory boot.img back in and used the 4.0.4 RUU. (updated OTA after reboot)
Then I unlocked the Bootloader and put TWRP 2.5.0.0 on it.
Then I rebooted and downloaded SuperSU and Busybox from the Play store
I tried updated the Binary and it failed. So I flashed the UPDATE Super SU.zip
rebooted and was able to update the Binary. But everytime I try to update the busybox it says "it looks like the installation of BusyBox was not successful"
and when I delete Tmobile bloatware using TB (which promted and is granted Superuser permissions). The Phone will randomly reboot and when it restarts all the applications I just deleted are back.
What am I missing?
Like this:
usaff22 said:
Same as this problem, many people have asked a similar question before:
http://forum.xda-developers.com/showthread.php?t=2067495
Edit:
And these:
http://forum.xda-developers.com/showthread.php?p=39138367
http://forum.xda-developers.com/showthread.php?t=2190194
Click to expand...
Click to collapse
usaff22 said:
Like this:
Click to expand...
Click to collapse
Thanks.
I just didnt know what "keywords" to search for that.
I've been having issues with all new root apps being auto-denied (namely goomanager) by superuser. I tried factory reset but unfortunately it kept root. SuperSU said I needed to update binary, but I have no idea how to do that, so I thought unrooting and re-rooting would be easier. Any advice?
mgoblueno1 said:
I've been having issues with all new root apps being auto-denied (namely goomanager) by superuser. I tried factory reset but unfortunately it kept root. SuperSU said I needed to update binary, but I have no idea how to do that, so I thought unrooting and re-rooting would be easier. Any advice?
Click to expand...
Click to collapse
Just follow the the instructions superuser gives to update the binary. That is what is causing your half root issues.
sbdags said:
Just follow the the instructions superuser gives to update the binary. That is what is causing your half root issues.
Click to expand...
Click to collapse
Alright, I rerooted with motochopper and updated using supersu, but goomanager still get "No recoveries were found for your device", even after I verified it had root access. Do I have to do the complicated method, or is there something else I can try?
mgoblueno1 said:
Alright, I rerooted with motochopper and updated using supersu, but goomanager still get "No recoveries were found for your device", even after I verified it had root access. Do I have to do the complicated method, or is there something else I can try?
Click to expand...
Click to collapse
You have to be unlocked to use the goo manager method.
sbdags said:
You have to be unlocked to use the goo manager method.
Click to expand...
Click to collapse
I am unlocked via asus unlock tool. And I get the message on the boot up screen that says I'm unlocked
mgoblueno1 said:
I am unlocked via asus unlock tool. And I get the message on the boot up screen that says I'm unlocked
Click to expand...
Click to collapse
Somehow GooManager doesn't seem to work on our tablets - don't know why but I read the same scenario more than twice: http://forum.xda-developers.com/showthread.php?t=2524661
Use the fastboot method to install TWRP or the "MinimalADB fastboot Tool"
Yes goo manager has stopped support for installing twrp. I suspect too many people bricked as it can flash the wrong one. Only method now is fast boot from PC which is the best method.
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
Have you verify that your phone successfully rooted? Check it with root checker from the market.
ShapesBlue said:
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Have you got a link? I'm looking but not finding.
nook2hd said:
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.
Click to expand...
Click to collapse
I did have my phone rooted prior to the OTA. I've been rooting my phones for years, but have never messed with adb shell. I read your post before posting this question but it is kind of greek to me. I've always used the usual run this, run that, Odin this, CWM that type approaches. My SuperSU binary won't update because it can't disable KNOX.
buhohitr said:
Have you verify that your phone successfully rooted? Check it with root checker from the market.
Click to expand...
Click to collapse
I already used root checker to verify the phone did not root successfully.
voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
I have the zip file. I downloaded it awhile ago. It's dated from October.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
---------- Post added at 01:44 PM ---------- Previous post was at 01:32 PM ----------
voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
Best bet is his thread here on xda. He has a flashable zip
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.
buhohitr said:
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.
Click to expand...
Click to collapse
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.
voigts said:
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.
Click to expand...
Click to collapse
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.
buhohitr said:
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.
Click to expand...
Click to collapse
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?
voigts said:
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?
Click to expand...
Click to collapse
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.
buhohitr said:
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.
Click to expand...
Click to collapse
Makes sense. I get the concept. Thank you very much for your help. I Googled over and over and couldn't come up with an answer.
Using Saferoot with Knox disable
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I had tried the saferoot and it failed several times, until i installed kies 3 here's how finally was able to root my SCH-R530u Us cellular phone with JB 4.3:
downloaded saferoot & unzipped, then installed kies 3 & run it (make sure your phone is detected ok in kies) after kies opens & your phone is recognized open saferoot and run it. wait for the phone to restart, then go to play store and download supesu and install it or update it, then open supersu & it should ask to install binary. that should do it! Hope this helps:victory:
voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
can you please tell me how did you manage to disable knox because i have the same exact problem tnx
LYwaa said:
can you please tell me how did you manage to disable knox because i have the same exact problem tnx
Click to expand...
Click to collapse
I'd try to help but I know hardly anything about Knox. Try sending a PM to the person
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I'm having issues with my OPO root. I unlocked my bootloader, flashed TWRP and rooted by installing SuperSU through a zip. All was good and root was working yesterday.
I haven't done any Android updates, but my root is gone! If I open the SuperSU app it does this (see screenshot in attachments)
I tried reflashing the zip through TWRP but the same happens after rebooting.
Any ideas?
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Reinstall busybox.
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Sent from N5 or OPO
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Why on earth did you uninstall Busybox in the first place?
Sent from my Evita
Same problem here.
My OpO was rooted and after uninstalling busybox i have the same issue.
Superuser says no su binaries
i tried flashing again an again. Flash works fine but always the same message no su binaries ..
Busybox was stuck on loading data, that's why i uninstall it .
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
wacky.ddw said:
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
Click to expand...
Click to collapse
Don't restore system data when switching ROMs.
Sent via Bacon
timmaaa said:
Don't restore system data when switching ROMs.
Sent via Bacon
Click to expand...
Click to collapse
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
You guys are totally out of a clue.
First: why do you uninstall busybox? Read twice, flash once. If you knew what busybox is for you probably would avoid such errors. Don't tweak your devices if you're not savvy of what you're doing or xda forum will always be cluttered by such threads.
Second: System options backed up can screw up your phone if they do not apply to the ROM just installed causing various problems if not bootloops. DO NOT RESTORE EM. NO WAY.
Hope this helps.
PS: Install busybox from play store to solve the issue.
wacky.ddw said:
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
Click to expand...
Click to collapse
Read what you just wrote and tell me again that you don't want to restore system data.
Sent via Bacon
DuckMcQUack said:
PS: Install busybox from play store to solve the issue.
Click to expand...
Click to collapse
It don't works, install ok but Busybox crash when i open it
ahytes said:
It don't works, install ok but Busybox crash when i open it
Click to expand...
Click to collapse
Personally i would just clean flash again from the start...
Inviato dal mio One utilizzando Tapatalk
Hi, I have the same problem.
I tried to reflash SuperSU, but not working.
BusyBox was uninstalled from my pocket :crying:
What should I do ?
See post right above yours.
Transmitted via Bacon
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Brigitte-Bedo said:
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Click to expand...
Click to collapse
I have this same problem as OP. Ok well since the app keeps crashing on startup, flashing a zip seems like a good idea. Where did you find this zip file?
Same Problem
I lrooted my opo and flashed Sabermods Cm Lollipop and am also getting the same notification, any root needed apps are telling me the phone isnt rooted?? I also tried installing this busybox but wont work cause the phone is coming up as unrooted?
Has anyone a straight answer for this dilemma that doesnt include a full wipe/flash rom again...?
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------
mindblizzard said:
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
Click to expand...
Click to collapse
Had this problem to, try to uninstall supersu etc. Flash latest su and problem fixed, im on slimLP rom
Ok, I can't seem to get back root either. I had root and was running ParanoidAndroid. I wiped clean, flashed Cyanogen 12 nightly, flashed Gapps, wiped cache/dalvik. Everything rebooted into Lollipop fine, but I've lost root and can't seem to figure out how to re-root. I flashed the most recent SuperSU (2.46) via TWRP with no luck. Keeps saying I need to re-root first. Any ideas?
This afternoon I applied OTA 3.1 to my Shield Tablet, and reinstalled CWM and flashed supersu. My tablet booted correctly but I don't have root. If I open the SuperSU app, I get "there is no SU binary installed and SuperSU cannot install it. This is a problem!" anyone know how to fix this?
Thanks
I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.
Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk
sixstringedmatt said:
Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.
Aventura5 said:
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.
Click to expand...
Click to collapse
I'm having the same problem.
Im also with the same problem, on 3.0 i used kingroot, but with 3.1 doesnt work also.
Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.
King root 4.5 works to root easily
Got it rooted again
I finally got it rooted again.
1) Put supersu.zip on to sd card.
2) Flashed TWRP with ADB fastboot.
3) Rebooted into recovery.
4) Flashed supersu.zip from the sd card.
5) Rebooted
After that it was finally rooted again. Hope this helps anybody else who has this problem.
Unfortunately though since I got my tablet when it first came out I have a recalled one. This will be my 4th RMA. LOL
danjull said:
Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.
Click to expand...
Click to collapse
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
EDIT: This worked and now CWM sticks, but i still get the SU binary not installed error.
Aventura5 said:
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
Click to expand...
Click to collapse
No. It restores stock recovery on first reboot.
Kingroot worked for me guys
What I don't understand is how the zip can install the SuperSU app as a system app, but not install the SU binary. Is it possible to manually copy the Su binary to my device? I have root access in recovery mode.
Dose anyone have any idea why this happens?
It works now with the new version of supersu
Is there a guide for rooting the shield from 3.0 and up? Thanks.
tecnoworld said:
Is there a guide for rooting the shield from 3.0 and up? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.
tecnoworld said:
That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.
Click to expand...
Click to collapse
It dose say for 2.0, but it should work on everything. This is the "real" way, other methods are hacks that work only on certain versions. I prefer this method, it gives you the most insurance against damage, but you could always just use kingo root. Also, versions 2.x and 3.x are both lollipop.
Aventura5 said:
I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.
Click to expand...
Click to collapse
Just out of curiosity, doesn't fastboot boot (image of recovery) just boot into the recovery and not flash it?
From previous experience, to reflash recovery you need something like flash_image or a way to write the image on the recovery partition... Correct me if I'm wrong...