Related
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app
Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk
Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.
i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot
re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app
Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.
cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2
I'm getting ready to root my phone and I just want to be sure of a couple of things. I think I found the correct 'how to' thread for rooting this phone using ioroot (there are a bunch out there), but i'm unsure of which version of ioroot to use. The thread talks about ioroot25, but the website for downloading has a newer version of ioroot available. The part where i'm a bit confused is that the latest version is a lot smaller in file size than version 25, something like 1.6mb vs. 7.3mb. I just want to be sure that the version from June 17th is the correct one to use despite being a lot smaller in size. Or should I still use ioroot25?
Also, i've read a lot of threads about display problems (a white line or soemthing) running an AOSP version of KitKat (which I was intending to do). Is this a kernel issue or a ROM issue? Are there certain AOSP KK ROMs or kernels I should avoid that have this problem?
Thanks for any info....
flyinjoe13 said:
I'm getting ready to root my phone and I just want to be sure of a couple of things. I think I found the correct 'how to' thread for rooting this phone using ioroot (there are a bunch out there), but i'm unsure of which version of ioroot to use. The thread talks about ioroot25, but the website for downloading has a newer version of ioroot available. The part where i'm a bit confused is that the latest version is a lot smaller in file size than version 25, something like 1.6mb vs. 7.3mb. I just want to be sure that the version from June 17th is the correct one to use despite being a lot smaller in size. Or should I still use ioroot25?
Also, i've read a lot of threads about display problems (a white line or soemthing) running an AOSP version of KitKat (which I was intending to do). Is this a kernel issue or a ROM issue? Are there certain AOSP KK ROMs or kernels I should avoid that have this problem?
Thanks for any info....
Click to expand...
Click to collapse
the latest ioroot is what you want to use, the reason it is smaller is because autoprime cleaned up a lot of not needed files which was actually update 25.1
yes there have been display problems which emerged with kitkat and it is related to the panel type of your phone after root use panel checker and if you have jdi panel you will need to flash a jdi kernel or you will have white lines issue but if you have lgd panel then there is nothing to worry about
XxZombiePikachu said:
the latest ioroot is what you want to use, the reason it is smaller is because autoprime cleaned up a lot of not needed files which was actually update 25.1
yes there have been display problems which emerged with kitkat and it is related to the panel type of your phone after root use panel checker and if you have jdi panel you will need to flash a jdi kernel or you will have white lines issue but if you have lgd panel then there is nothing to worry about
Click to expand...
Click to collapse
Great. Thanks for the info. I feel confident enough now to go ahead and root my phone.
Two more questions:
I went ahead and ran ioroot to root my phone and everything seems to have worked fine. I got root status under 'About Phone', was able to flash the TWRP recovery and was able to remove a bunch of the preloaded bloatware through file explorer so I know I am rooted. I noticed though that there is no Superuser app installed like i've gotten with past phones when I rooted. Am I supposed to install one from the Market or do I not need one anymore?
Also, can I uninstall the Autorec app after flashing TWRP or is it still needed?
flyinjoe13 said:
Two more questions:
I went ahead and ran ioroot to root my phone and everything seems to have worked fine. I got root status under 'About Phone', was able to flash the TWRP recovery and was able to remove a bunch of the preloaded bloatware through file explorer so I know I am rooted. I noticed though that there is no Superuser app installed like i've gotten with past phones when I rooted. Am I supposed to install one from the Market or do I not need one anymore?
Also, can I uninstall the Autorec app after flashing TWRP or is it still needed?
Click to expand...
Click to collapse
That is odd ioroot usually install supersu when rooting, well you can just grab it from play store which is advised so that way you can grant root only to apps you know need it(I have noticed a few games on play store who want root access and don't need it)
as for autorec, yes you can uninstall it since you already used it there is no need to keep it on phone
and don't forget to check your panel type if you haven't already
XxZombiePikachu said:
That is odd ioroot usually install supersu when rooting, well you can just grab it from play store which is advised so that way you can grant root only to apps you know need it(I have noticed a few games on play store who want root access and don't need it)
as for autorec, yes you can uninstall it since you already used it there is no need to keep it on phone
and don't forget to check your panel type if you haven't already
Click to expand...
Click to collapse
Thanks again for the answers. I will go ahead and get supersu and remove autorec. I did check the panel as you advised and it is an LG.
flyinjoe13 said:
Thanks again for the answers. I will go ahead and get supersu and remove autorec. I did check the panel as you advised and it is an LG.
Click to expand...
Click to collapse
if you mean lgd then that is awesome you shouldn't have any random display issues appeaaring
Just letting everyone know that is does work for this device as well. Not sure if it's been mentioned already or not. If so and it's old news, sorry but didn't see anything posted about here although I didn't look very hard either
On the latest 4.4.4 update. So far so good. Did it's thing in less than 5sec's. Root Check was good, Installed SU from the playstore, said something about the SU Binaries or something, rebooted and bam, that msg doesn't show up anymore and all looks to be good.
Thank you geohot!
Bricking and Boot Loops on Nexus 7 2013 WI-FI
Demmonnixx said:
Just letting everyone know that is does work for this device as well. Not sure if it's been mentioned already or not. If so and it's old news, sorry but didn't see anything posted about here although I didn't look very hard either
On the latest 4.4.4 update. So far so good. Did it's thing in less than 5sec's. Root Check was good, Installed SU from the playstore, said something about the SU Binaries or something, rebooted and bam, that msg doesn't show up anymore and all looks to be good.
Thank you geohot!
Click to expand...
Click to collapse
I actually have encountered problems on two separate Nexus 7 2013 editions both in less the a day of using towelroot. One tablet with a custom kernel bricked and the other tablet while rooted with towelroot is without a custom kernel and whenever encountering a force close will reboot itself and boot loop 20-30 times before eventually booting back into Android 4.4.4. I have no definitive 'proof' that towelroot is causing these errors but I find it all a little too coincidental. I hope your device fairs better then mine.
Not sure I see the point of towelroot on a N7, one just has to flash supersu in twrp.
Edit: I guess if you don't have a pc(really? in this day and age?) or don't wanna wipe? Meh, to each their own.
Captain_FSU said:
I actually have encountered problems on two separate Nexus 7 2013 editions both in less the a day of using towelroot. One tablet with a custom kernel bricked and the other tablet while rooted with towelroot is without a custom kernel and whenever encountering a force close will reboot itself and boot loop 20-30 times before eventually booting back into Android 4.4.4. I have no definitive 'proof' that towelroot is causing these errors but I find it all a little too coincidental. I hope your device fairs better then mine.
Click to expand...
Click to collapse
Haven't had a single issue so far. Did the towel root thing and then unlocked the boot loader then flashed clean ROM and this thing has been amazing so far on all aspects. I would start from scratch fresh and clean and see if that helps anything. Good luck but if u can give a step by step on what u did first through the last step and what version of towel root u used I might be able to help
mdamaged said:
Not sure I see the point of towelroot on a N7, one just has to flash supersu in twrp.
Edit: I guess if you don't have a pc(really? in this day and age?) or don't wanna wipe? Meh, to each their own.
Click to expand...
Click to collapse
1. My computer's a desktop and 100+ miles away
2. Don't want to wipe
I tried the latest towel root on Lollipop and it says "This device is not supported"
Hey guys,
This is almost certainly a stupid question but I would be grateful for any help. I have a Nexus 6p thats upgraded to the lastest Android O beta version of OPP2. I wanted to finally go around rooting it. I have enabled USB debugging, always allowed the PC's RSA fingerprint and checked allow OEM unlocking. Nothing else has been done before, I plan on following a step by step guide that will help me unlock bootloader, install custom recovery and root etc.
I tried googling and to my surprise I could not find any root guide for this version of Nexus 6p (maybe I am just blind?)
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Woah. Cheers mate! so i just need to plug my Nexus 6p in, execute the file and click on unlock bootloader? I assume i have to install super su after that and that will be it? :3 Sorry. I know i am asking stupid questions and you are obv a pro. Also the fact that my version is opp2.170420.019 makes no difference right?
chevycam94 said:
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Click to expand...
Click to collapse
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Allrighty then, ill take the plunge real soon! Thank you for all the help Any specific why I should go with TheFlash's build instead of this one: dl.twrp(dot)me/angler/? As far as I can see it only supports F2FS which I will probably not be using.
chevycam94 said:
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Click to expand...
Click to collapse
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
chevycam94 said:
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Click to expand...
Click to collapse
UsmanPirzada said:
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
Click to expand...
Click to collapse
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
chevycam94 said:
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Click to expand...
Click to collapse
UsmanPirzada said:
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
Click to expand...
Click to collapse
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
I flashed it to 7.1.1 N4F26T using NRT and now the it has severe lag and keeps freezing and screen isnt accepting touch commands. Since this is a fresh install I assume the RSA fingerprint and USB Debuugging option has been unchecked as well? I have downloaded the official stock image of 7.1.2. Can I apply it using recovery or something?
chevycam94 said:
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
Click to expand...
Click to collapse
Okay, flashed it to 7.1.2 using recovery. Everything seems fine now. Thank god. Helpful tip to any noob out there trying to root Android O Beta 2 on your nexus 6p: dont.
Is there any easy way to get root back? Do I just flash a previous version of SuperSU with flash fire? Thanks.
You have to re run the root file on your pc.
helllmonkey said:
Is there any easy way to get root back? Do I just flash a previous version of SuperSU with flash fire? Thanks.
Click to expand...
Click to collapse
Just need to run the root.bat file from your PC and you'll be good to go. That can be found in the thread on how to root your phone, install Xposed, etc.
Then make sure not to to update SU. There are a few workarounds to simply avoiding the update, but in general you don't want to take it. It will make you lose root every time you update.
nyr2k2 said:
Just need to run the root.bat file from your PC and you'll be good to go. That can be found in the thread on how to root your phone, install Xposed, etc.
Then make sure not to to update SU. There are a few workarounds to simply avoiding the update, but in general you don't want to take it. It will make you lose root every time you update.
Click to expand...
Click to collapse
Actually is there a way to stop it from popping up, asking me to Update SuperSU or not everytime when I press auto update for my other apps in the Google Play?
There were once or twice I mistakenly pressed yes when updating other apps (obviously when I was daydreaming or sleepwalking) and I will have to root it again.
cn2661 said:
Actually is there a way to stop it from popping up, asking me to Update SuperSU or not everytime when I press auto update for my other apps in the Google Play?
There were once or twice I mistakenly pressed yes when updating other apps (obviously when I was daydreaming or sleepwalking) and I will have to root it again.
Click to expand...
Click to collapse
If you long press the notification in the notification pull down, you can then turn off app notifications for it. That would stop the reminder and the constant # symbol from sitting in your tray. That's what I did. If you open the app itself it will still tell you the binary needs to be updated, but you can just ignore it. Basically you're running the 2.78 or whatever SU app and binary that installs when you run the root.bat but you have installed the latest version so you don't have to see it in the store. Supposedly the most recent version of the app itself "fixed" the problem of losing root just by installing the app but we can't install the binaries on our phone. So you can try updating it in the store--I'm on 2.82 with old binaries. There's still I suppose a chance you could lose root, but then again you just rerun the root.bat.
So all in all I'd recommend downloading the 2.82 update. Don't try to install the binaries. Hide the notifications. Then you're good to go. If you somehow lose root in the process then rerun the root.bat and look around here further. Someone had another workaround with a modified version of SuperSU, but I never tried that because my setup was fine and I was tired or screwing around, LOL.
This, again, is why I will not buy another phone unless I know it can have the BL unlocked. I want to use Magisk and have a custom recovery. Tinkering around on this thing and risking bricks when you then have to re-flash everything, it just sucks.
nyr2k2 said:
If you long press the notification in the notification pull down, you can then turn off app notifications for it. That would stop the reminder and the constant # symbol from sitting in your tray. That's what I did. If you open the app itself it will still tell you the binary needs to be updated, but you can just ignore it. Basically you're running the 2.78 or whatever SU app and binary that installs when you run the root.bat but you have installed the latest version so you don't have to see it in the store. Supposedly the most recent version of the app itself "fixed" the problem of losing root just by installing the app but we can't install the binaries on our phone. So you can try updating it in the store--I'm on 2.82 with old binaries. There's still I suppose a chance you could lose root, but then again you just rerun the root.bat.
So all in all I'd recommend downloading the 2.82 update. Don't try to install the binaries. Hide the notifications. Then you're good to go. If you somehow lose root in the process then rerun the root.bat and look around here further. Someone had another workaround with a modified version of SuperSU, but I never tried that because my setup was fine and I was tired or screwing around, LOL.
This, again, is why I will not buy another phone unless I know it can have the BL unlocked. I want to use Magisk and have a custom recovery. Tinkering around on this thing and risking bricks when you then have to re-flash everything, it just sucks.
Click to expand...
Click to collapse
Cheers mate, perfectly works,
by Updating the SuperSU app, Not updating the SU Binary and long-press notification to shut the notification off.
Peace to the Earth again.:good: