I tried to root my sch-i535 4.3 I had MTP click and usb debugging click...and it failed in odin...I have an image and link of what I was using to root the phone below and this is what the phone gave me in download mode...how can I fix this problem?
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
eddieleed said:
I tried to root my sch-i535 4.3 I had MTP click and usb debugging click...and it failed in odin...I have an image and link of what I was using to root the phone below and this is what the phone gave me in download mode...how can I fix this problem?
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
If you spend the time looking through the countless 4.3 ota threads, you would see that you can't root from 4.3 that way... safestrap is it and trying to Odin root will probably brick your device...
Check twice, flash once...
Sent from my SCH-I535 using xda premium
Do you have info on it???
Do you have info on how to do it with Safestrap?
Macrodroid said:
If you spend the time looking through the countless 4.3 ota threads, you would see that you can't root from 4.3 that way... safestrap is it and trying to Odin root will probably brick your device...
Check twice, flash once...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Dadiekane said:
Do you have info on how to do it with Safestrap?
Click to expand...
Click to collapse
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
landshark68 said:
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
I'll look into this as well...I'll keep faith that thier is a root out there or will b out there.
works
landshark68 said:
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
thanks for the link..it worked...I am rooted on my Verizon 4.3 galaxy s3...can I install recovery (cwm or twrp)?
eddieleed said:
thanks for the link..it worked...I am rooted on my Verizon 4.3 galaxy s3...can I install recovery (cwm or twrp)?
Click to expand...
Click to collapse
No, you can only root.
landshark68 said:
No, you can only root.
Click to expand...
Click to collapse
That's what I have been reading. Ill be waiting for a custom recovery...thank you for your and comments. :good:
can any one help I safe rooted my sch-i535 verizon jellybean 4.3 ..added titanium back and pressed something wrong in titanium back up that soft brick my phone so now all it says is "unauthorized software take to you local verizon dealer" i've tried everything Ive read on this site and then some,still boots to yellow screen of death.this is not the first phone i've rooted been playing with modifying phones since the V3M came out.yes it was updated by OTA 4.3..everything in Odin fails, the knot counter is tripped but i don't buy my phones from Verizon anyway, tried hard reset still nothing.I can get into down load mode (power,vol down/home)and reset mode(power, vol up/home)Kies says unauthorized software .anything would be helpful.......deadcat
Saferoot working in s3 verizon
Sent from my SCH-I535 using xda app-developers app
deadcatsrule said:
can any one help I safe rooted my sch-i535 verizon jellybean 4.3 ..added titanium back and pressed something wrong in titanium back up that soft brick my phone so now all it says is "unauthorized software take to you local verizon dealer" i've tried everything Ive read on this site and then some,still boots to yellow screen of death.this is not the first phone i've rooted been playing with modifying phones since the V3M came out.yes it was updated by OTA 4.3..everything in Odin fails, the knot counter is tripped but i don't buy my phones from Verizon anyway, tried hard reset still nothing.I can get into down load mode (power,vol down/home)and reset mode(power, vol up/home)Kies says unauthorized software .anything would be helpful.......deadcat
Click to expand...
Click to collapse
As long as you can get to download mode, you can flash the stock 4.3 image back. When you start TB, pay attention. Do not restore ANY system apps and do not allow it to change the phone ID.
Sent from my SCH-I535 using xda app-developers app
5ft24 said:
As long as you can get to download mode, you can flash the stock 4.3 image back. When you start TB, pay attention. Do not restore ANY system apps and do not allow it to change the phone ID.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I backd up my phone with TB and have it saved on my laptop but dont know what file to try to flash and I can not find a good stock 4.3 image that i can get to flash back to the phone.from what im reading the boot loader is locked keeping me from flashing anything .I've picked up another S3 to use for now so I can try to undo what ever i did wrong
deadcatsrule said:
I backd up my phone with TB and have it saved on my laptop but dont know what file to try to flash and I can not find a good stock 4.3 image that i can get to flash back to the phone.from what im reading the boot loader is locked keeping me from flashing anything .I've picked up another S3 to use for now so I can try to undo what ever i did wrong
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2589314
post one is to download the official firmware 4.3
post 2 is how to fix and if you follow the link after you redirected there're more info how to recover your phone depended on how bad it is, but if you still get into download mode you should be ok.
buhohitr said:
Try this http://forum.xda-developers.com/showthread.php?t=2589314
post one is to download the official firmware 4.3
post 2 is how to fix and if you follow the link after you redirected there're more info how to recover your phone depended on how bad it is, but if you still get into download mode you should be ok.
Click to expand...
Click to collapse
UPDATE!! the link and info you posted for me fixed my phone first try..THANKS
Help, using Saferoot to root OTA 4.3, but Supersu binary update failed
Followed all the steps of Saferoot, everything else seems ok except SuperSU failed to update su binary.
The weird thing is that steps after SuperSU update (disabling KNOX and installing busybox) seem ok, and while SuperSU's popup window asking for SU binary needs to be updated, I can see in the grayed out back showing ADB Shell as the only apps gained root access.
More detail on SuperSU binary update, I chose update su normal way (instead CWM/TWRP) and next popup will report "Installation failed. Please reboot and try again." I tried many reboots and results were all the same.
From Terminal emulator, su -v command shows su is at version 3.1.1 (that's the latest already). If I cancel binary update, SuperSU app will exit too. I tried to install superuser app and use it to update su binary as someone suggested, it will fail in gaining root access.
Any way to overcome this issue and gain root on this OTA 4.3? Please help.
Phone Info:
Device Name: SCH-I535
Baseband Version: I535VRUCML1
Build Number: JSS15J.I535VRUCML1
Hardware Version: I535.10
nook2hd said:
Followed all the steps of Saferoot, everything else seems ok except SuperSU failed to update su binary.
The weird thing is that steps after SuperSU update (disabling KNOX and installing busybox) seem ok, and while SuperSU's popup window asking for SU binary needs to be updated, I can see in the grayed out back showing ADB Shell as the only apps gained root access.
More detail on SuperSU binary update, I chose update su normal way (instead CWM/TWRP) and next popup will report "Installation failed. Please reboot and try again." I tried many reboots and results were all the same.
From Terminal emulator, su -v command shows su is at version 3.1.1 (that's the latest already). If I cancel binary update, SuperSU app will exit too. I tried to install superuser app and use it to update su binary as someone suggested, it will fail in gaining root access.
Any way to overcome this issue and gain root on this OTA 4.3? Please help.
Phone Info:
Device Name: SCH-I535
Baseband Version: I535VRUCML1
Build Number: JSS15J.I535VRUCML1
Hardware Version: I535.10
Click to expand...
Click to collapse
In super su options do the clean up for market reinstall. Then download supersu from the market. It may not be worded like that but you will see what I mean. And make sure you uninstall superuser if you haven't already.
Still the same
ThePagel said:
In super su options do the clean up for market reinstall. Then download supersu from the market. It may not be worded like that but you will see what I mean. And make sure you uninstall superuser if you haven't already.
Click to expand...
Click to collapse
I cannot get into SuperSU options (or settings as in the snapshots). Neither Cancel nor Continue to the binary update popup will not stop me into SuperSU app.
Unistalled superuser, force stopped SuperSU and cleared data, then reinstalled SuperSU from play store. However, when open SuperSU, still asks for su binary update and fail.
Any other ways to get this to work?
nook2hd said:
Unistalled superuser, force stopped SuperSU and cleared data, then reinstalled SuperSU from play store. However, when open SuperSU, still asks for su binary update and fail.
Any other ways to get this to work?
Click to expand...
Click to collapse
Did you do the cleanup option in supersu?
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
Labeled reinstall under supersu settings.
ThePagel said:
Did you do the cleanup option in supersu?
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
Labeled reinstall under supersu settings.
Click to expand...
Click to collapse
I cannot get into SuperSu settings when there are popup windows, and when popup is gone, SuperSU app exits with it somehow. Is there a way to bypass those popups and allow me to click on the settings?
nook2hd said:
I cannot get into SuperSu settings when there are popup windows, and when popup is gone, SuperSU app exits with it somehow. Is there a way to bypass those popups and allow me to click on the settings?
Click to expand...
Click to collapse
I have no clue. If you can't find a solution you could always factory reset and start over.
Related
Hey does anyone know if OTA rootkeeper can preserve root through a facory reset? I want to downgrade to .30, root, upgrade to JB, then factory reset. I know it will preserve through OTA, but i want to know if it is possible to preserve root through full reset, with OTA rootkeeper or any other methods.
lucius.zen said:
Hey does anyone know if OTA rootkeeper can preserve root through a facory reset? I want to downgrade to .30, root, upgrade to JB, then factory reset. I know it will preserve through OTA, but i want to know if it is possible to preserve root through full reset, with OTA rootkeeper or any other methods.
Click to expand...
Click to collapse
Yes, it should keep root after you did a factory reset. Make sure you download and installed superSU, once download open up superuser and and superSU. In supersu put a check for preserve root in settings(if you have the paid version), if you don't open up superuser and put a check to preserve root. Then Open up OTA root keeper, make sure you save root by click "Temp unroot". Now turn off your device and boot into "wipe data" execute it. Once your device boot up, re download superuser, open it, then download and install OTA root keeper, open up then click restore. You should have root back.
Have you tried? Did it work?
MarkAndroid said:
Have you tried? Did it work?
Click to expand...
Click to collapse
I have tried this 3 times while I'm on JB, then one more time with factory reset 3 times consecutively and I still able to preserve root. Then again, still there are some odds out there, nothing is 100% with tf700.
buhohitr said:
... open up superuser and put a check to preserve root.
Click to expand...
Click to collapse
I don't see anywhere in SuperSU to check preserve root. Am I missing something?
atgmartin said:
I don't see anywhere in SuperSU to check preserve root. Am I missing something?
Click to expand...
Click to collapse
You need a paid version to have the option. It's gray out on the free version.
Hey all,
been trying to get help on this in other threads as well but not som much luck.
1- From ICS 9.4.5.30 I rooted using DebugFS, which installed superuser
2- Then installed RootKeeper, click on Protect Root, then click on Temp Un-Root
3- Upgraded to JB 10.4.4.16 through SD card
4- Open RootKeeper but no Restore button is there.
I have unlocked bootloaders and no wipe data anywhere in this process.
Will installing SuperSU before upgrading to JB change anything at all? What am I doing wrong?
nadram said:
Hey all,
been trying to get help on this in other threads as well but not som much luck.
1- From ICS 9.4.5.30 I rooted using DebugFS, which installed superuser
2- Then installed RootKeeper, click on Protect Root, then click on Temp Un-Root
3- Upgraded to JB 10.4.4.16 through SD card
4- Open RootKeeper but no Restore button is there.
I have unlocked bootloaders and no wipe data anywhere in this process.
Will installing SuperSU before upgrading to JB change anything at all? What am I doing wrong?
Click to expand...
Click to collapse
After you rooted, make sure you open superuser, then dowload superSU, open the app also, then download the OTA root keeper then click protect root,(all the boxes should have a check), click on Temp Un-Rood, now do the upgrade.(you must update through OTA or use incremental dlpkgfile to update, a full package will wipe everything).
buhohitr said:
After you rooted, make sure you open superuser, then dowload superSU, open the app also, then download the OTA root keeper then click protect root,(all the boxes should have a check), click on Temp Un-Rood, now do the upgrade.(you must update through OTA or use incremental dlpkgfile to update, a full package will wipe everything).
Click to expand...
Click to collapse
aaaaaarrrrrrrrrrrrrrrrrrrrghghghhgghhg
dlpkgfile...... didn't know about that :'(
Thanks bro, i'll give it a shot
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
Fine. I just wanted to try out CleanRom.
F that.
Too complicated and not worth another minute of my time.
I'll stick to stock.
nadram said:
aaaaaarrrrrrrrrrrrrrrrrrrrghghghhgghhg
dlpkgfile...... didn't know about that :'(
Thanks bro, i'll give it a shot
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
Fine. I just wanted to try out CleanRom.
F that.
Too complicated and not worth another minute of my time.
I'll stick to stock.
Click to expand...
Click to collapse
Since you already unlock it's a shame that you're not runing custom rom. If you already on JB, you can do it this way, download Android sdk to your computer and install it. During the install process, you need to pick the package to install, pick 2 packages that named with android. The sDK is installed in this directory on your computer,c:\android-sdk\platform-tools, in this directory theire is a command called fastboot.exe. Download recovery image file from here http://www.mediafire.com/?ju5p2p9adpuus2k and put this file "recovery.img" to the same folder as fastboot.exe (c:\android-sdk\platform-tools), Now let begin:
1. connect your device to your PC with usb cable
2. boot your device into fastboot mode (select the USB icon)
3. On your pc open cmd (command prompt) and navigate to this directory; c:\android-sdk\platform-tools
4 type :
fastboot -i 0x0B05 flash recovery recovery.img
once done type
fastboot -i 0x0B05 reboot
That's it. You should install sdk because it's a very useful tool, and since you already unlocked, it such as waist if you not runing custom rom. You are going to fall back in love with your device when you're running custom rom. Go for it bro.
buhohitr said:
I have tried this 3 times while I'm on JB, then one more time with factory reset 3 times consecutively and I still able to preserve root. Then again, still there are some odds out there, nothing is 100% with tf700.
Click to expand...
Click to collapse
With superuser do not have this option (check preserve root) but after the OTA update I was able to restore the root.
Do you even restoring to factory data I am able to replace the root with Rootkeeper?
I'm not sure what you did that's different from me, but I used Voodoo Rootkeeper and worked fine. I don't have SuperSU installed.
I'm thinking you didn't save your root properly when you went to protect root.
lovekeiiy said:
I'm not sure what you did that's different from me, but I used Voodoo Rootkeeper and worked fine. I don't have SuperSU installed.
I'm thinking you didn't save your root properly when you went to protect root.
Click to expand...
Click to collapse
SuperSU is the latest and all developers are going to use this app going forward. SuperSU is more reliable. Superuser is old and will slowly phase out.
buhohitr said:
Since you already unlock it's a shame that you're not runing custom rom. If you already on JB, you can do it this way, download Android sdk to your computer and install it. During the install process, you need to pick the package to install, pick 2 packages that named with android. The sDK is installed in this directory on your computer,c:\android-sdk\platform-tools, in this directory theire is a command called fastboot.exe. Download recovery image file from here http://www.mediafire.com/?ju5p2p9adpuus2k and put this file "recovery.img" to the same folder as fastboot.exe (c:\android-sdk\platform-tools), Now let begin:
1. connect your device to your PC with usb cable
2. boot your device into fastboot mode (select the USB icon)
3. On your pc open cmd (command prompt) and navigate to this directory; c:\android-sdk\platform-tools
4 type :
fastboot -i 0x0B05 flash recovery recovery.img
once done type
fastboot -i 0x0B05 reboot
That's it. You should install sdk because it's a very useful tool, and since you already unlocked, it such as waist if you not runing custom rom. You are going to fall back in love with your device when you're running custom rom. Go for it bro.
Click to expand...
Click to collapse
So if I understand, this will install a "custom" recovery mode from which i can flash CleanRom?
You're right about falling back in love with it. I own a Galaxy S and an S3, and I don't know if there's any device easier to modify then the Galaxy series. They're awesome and so much fun.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
nadram said:
So if I understand, this will install a "custom" recovery mode from which i can flash CleanRom?
You're right about falling back in love with it. I own a Galaxy S and an S3, and I don't know if there's any device easier to modify then the Galaxy series. They're awesome and so much fun.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
That's correct.
lovekeiiy said:
I'm not sure what you did that's different from me, but I used Voodoo Rootkeeper and worked fine. I don't have SuperSU installed.
I'm thinking you didn't save your root properly when you went to protect root.
Click to expand...
Click to collapse
I got the courage and I restored to the factory settings my TF700
Reinstalled superuser and rootkeeper and I regained root privileges!
WOW!
buhohitr said:
That's correct.
Click to expand...
Click to collapse
Alright
I did it
And it worked
Thanks a million!
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
gstoliby said:
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
Click to expand...
Click to collapse
try disabling signature verification in your recovery
chromium96 said:
try disabling signature verification in your recovery
Click to expand...
Click to collapse
I can't even figure out how to do that!
gstoliby said:
I can't even figure out how to do that!
Click to expand...
Click to collapse
Which recovery are you using? In clockwordmod the option is located in the advacned menu
chromium96 said:
Which recovery are you using? In clockwordmod the option is located in the advacned menu
Click to expand...
Click to collapse
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
gstoliby said:
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
Click to expand...
Click to collapse
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
chromium96 said:
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
Click to expand...
Click to collapse
I'll have to give it a try when I get to my personal computer.
Hello XDA members
i have a big problem, when i want to open SuperSU a box popup saying that you must update SU binary then it asks what kind of method do you want to update "Normal" or "TWRP/CWM", when i choose "Normal" it failed to update, when i choose "TWRP/CWM" it reboots into recovery, i don't know what to do. Any one can help please.
Thanks.
Superuser.apk
hbforce said:
Hello XDA members
i have a big problem, when i want to open SuperSU a box popup saying that you must update SU binary then it asks what kind of method do you want to update "Normal" or "TWRP/CWM", when i choose "Normal" it failed to update, when i choose "TWRP/CWM" it reboots into recovery, i don't know what to do. Any one can help please.
Thanks.
Click to expand...
Click to collapse
I think it's much better if you install Superuser.apk rather than SuperSU.apk, you can find it here http://androidsu.com/superuser/
Download its files (superuser and su-binary) that appropriate to your device and then flash it via Recovery (CWM/TWRP).
im having the same problem, i will install superuser but how do i uninstall SuperSU ?
You must install supersu by recovery. Search for supersu on xda and download de latest version in zip version. Install it with e recovery and enjoy it.
Sent from my HTC One S using XDA Premium 4 mobile app
hbforce said:
when i want to open SuperSU a box popup saying that you must update SU binary then it asks what kind of method do you want to update "Normal" or "TWRP/CWM", when i choose "Normal" it failed to update, when i choose "TWRP/CWM" it reboots into recovery, i don't know what to do.
Click to expand...
Click to collapse
Try to use the recovery method several times. It will probably work after some tries. Also, did you update superSU from the market? Do this first.
Try to install SuperUSER.zip via recovery.
It will root your phone and It will install Superuser apk.
I had the same issue and now, superuser works fine <3
Sent from my HTC One S using xda app-developers app
xQubee5o3 said:
Try to install SuperUSER.zip via recovery.
It will root your phone and It will install Superuser apk.
I had the same issue and now, superuser works fine <3
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I have SuperSU and I also have the problem with the binary update failing. Can you please tell me how to install supersu via recovery? How to install anything via recovery?
Thanks, I am good at administrating windows PCs, but android is a totally new field to me...
jantinak said:
I have SuperSU and I also have the problem with the binary update failing. Can you please tell me how to install supersu via recovery? How to install anything via recovery?
Thanks, I am good at administrating windows PCs, but android is a totally new field to me...
Click to expand...
Click to collapse
SuperSU flashable zip can be found here.
Hi - I didn't have a problem finding the zip - that is easy. I don't know how to flash these things "via recovery" or whatever that means...
I found some guides which say how to flash zips through recovery CWM / TWRP, but as I dug deeper, these things require root to function properly, but that is the thing - I don't have the root, since I cannot update the SU binary library, see?
Also - when I tried to get to the recovery mode by pressing the buttons as it was stated in the guide, I got into some mode, but I got only an image of phone and cable connected to it, which was crossed by red lines. And no menu, nothing... it seemed, that the phone should be connected to the PC, but the guide didn't say anything about connecting phone to PC before entering recovery mode.
Could you help me solve this issue with binary thing from ground up?
Thanks
jantinak said:
Hi - I didn't have a problem finding the zip - that is easy. I don't know how to flash these things "via recovery" or whatever that means...
I found some guides which say how to flash zips through recovery CWM / TWRP, but as I dug deeper, these things require root to function properly, but that is the thing - I don't have the root, since I cannot update the SU binary library, see?
Also - when I tried to get to the recovery mode by pressing the buttons as it was stated in the guide, I got into some mode, but I got only an image of phone and cable connected to it, which was crossed by red lines. And no menu, nothing... it seemed, that the phone should be connected to the PC, but the guide didn't say anything about connecting phone to PC before entering recovery mode.
Could you help me solve this issue with binary thing from ground up?
Thanks
Click to expand...
Click to collapse
1. Unlock your bootloader via HTCdev.com
2. flash a custom recovery via fastboot (This toolkit will help you --> LINK
3. flash superuser
LS.xD said:
1. Unlock your bootloader via HTCdev.com
2. flash a custom recovery via fastboot (This toolkit will help you --> LINK
3. flash superuser
Click to expand...
Click to collapse
I have LG P880, not HTC phone...
Just how do I go about flashing it? It seems the only way to boot into recovery mode is to have root access which I don't have because Supersu needs an update. It's all a tiring cycle.
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
Can someone please help me in the process of unrooting and removing cmw recovery mod. I know from previous experience i can remove root, using supersu and click full unroot. Problem i am mainly having is what do I do to remove the CMW recovery mod. I have downloaded the factory image of the shield tablet, i just dont know how to go about it. Im very tech savy but im fairly new to android rooting.
S197Mike said:
Can someone please help me in the process of unrooting and removing cmw recovery mod. I know from previous experience i can remove root, using supersu and click full unroot. Problem i am mainly having is what do I do to remove the CMW recovery mod. I have downloaded the factory image of the shield tablet, i just dont know how to go about it. Im very tech savy but im fairly new to android rooting.
Click to expand...
Click to collapse
Extract all files from Nvidia's "recovery" file. Then copy the stock recovery.img. Fastboot flash recovery recovery.img
Stock recovery.img attached. Fastboot flash.
How did you unroot?
I know that some Samsung devices, like the Note 8, require a full Odin of the stock ROM as unroot with SuperUser won't do anything.
lanwarrior said:
How did you unroot?
I know that some Samsung devices, like the Note 8, require a full Odin of the stock ROM as unroot with SuperUser won't do anything.
Click to expand...
Click to collapse
SuperSU has a full unroot option. Works on Shield tab.
cam30era said:
SuperSU has a full unroot option. Works on Shield tab.
Click to expand...
Click to collapse
Thanks for the confirmation.
FYI, when I had my Note 8.0, doing the full unroot via SuperSU did not remove all the necessary file. Update no longer received, so I had to Odin the stock ROM.
lanwarrior said:
Thanks for the confirmation.
FYI, when I had my Note 8.0, doing the full unroot via SuperSU did not remove all the necessary file. Update no longer received, so I had to Odin the stock ROM.
Click to expand...
Click to collapse
FWIW: I flashed the stock recovery, then used SuperSU "unroot", and was able to successfully install the 1.1 OTA. I can't confirm that SuperSu unroot removes every trace of root, but it's good enough to accept OTA updates.
cam30era said:
FWIW: I flashed the stock recovery, then used SuperSU "unroot", and was able to successfully install the 1.1 OTA. I can't confirm that SuperSu unroot removes every trace of root, but it's good enough to accept OTA updates.
Click to expand...
Click to collapse
Thanks that is really good to know!
I just did a reset on my phone, install SuperSU, encrypt the tablet, reboot and checked if root is still there (it is).
Now I am trying to unroot by selecting "Full Unroot" in SuperSU, but I got stuck in the "Uninstalling, please wait..." message.
Is this normal?
EDIT: I had to uninstall SuperSU, reinstall from Google Play, update the binary, reboot and then the Full Unroot works. I think it does, because I use "root checker" and it said no root.