Related
So i've been searching for a couple days now, but can't seem to find a straight answer.
If i root my note 12.2, will it trip Knox to 0x1, or will knox only trip if i flash a custom rom?
I don't care too much for modding and such, just interested in rooting to remove blaotware. From what i've been seeing though, it looks like knox will trip just by rooting. However i'v seen others say it only tripped after installing custom roms. Maybe im just getting my references mixed up though.
AANNDD if rooting will trip knox, any idea if it will ever be possible to root without buggin knox? I have the note3 and was able to root and keep 0x0. I know they are very different when it comes to kernels, but maybe one day?
o0pyroguy0o said:
So i've been searching for a couple days now, but can't seem to find a straight answer.
If i root my note 12.2, will it trip Knox to 0x1, or will knox only trip if i flash a custom rom?
I don't care too much for modding and such, just interested in rooting to remove blaotware. From what i've been seeing though, it looks like knox will trip just by rooting. However i'v seen others say it only tripped after installing custom roms. Maybe im just getting my references mixed up though.
AANNDD if rooting will trip knox, any idea if it will ever be possible to root without buggin knox? I have the note3 and was able to root and keep 0x0. I know they are very different when it comes to kernels, but maybe one day?
Click to expand...
Click to collapse
I tripped knox trying to install TWRP... I know this doesn't exactly answer your question.
o0pyroguy0o said:
So i've been searching for a couple days now, but can't seem to find a straight answer.
If i root my note 12.2, will it trip Knox to 0x1, or will knox only trip if i flash a custom rom?
I don't care too much for modding and such, just interested in rooting to remove blaotware. From what i've been seeing though, it looks like knox will trip just by rooting. However i'v seen others say it only tripped after installing custom roms. Maybe im just getting my references mixed up though.
AANNDD if rooting will trip knox, any idea if it will ever be possible to root without buggin knox? I have the note3 and was able to root and keep 0x0. I know they are very different when it comes to kernels, but maybe one day?
Click to expand...
Click to collapse
I have root, stock recovery, stock firmware, never installed anything custom and KNOX is tripped. AFAIK, no way to achieve root without tripping KNOX, but so worth it to root. I have Exposed installed with Wanam and have my tablet set to Custom instead of Modified so I still get updates. I also have a Note 3 rooted on 4.4.2 without tripping KNOX.
It's not possible to root / flash custom ROMs or recoveries without tripping KNOX. At last for now.
And a bit off topic:
Note 3 was different since @designgears found way (URDLV) to root without triggering KNOX.. But it didn't took very long for Samsung to release a patch for that and downgrading is also impossible. So if you updated your phone via Kies or OTA when that exploit were patched, you got "bootloader of doom" and no way root without triggering KNOX flag (and since downgrading is impossible, you can't go back to "rootable" version). And I'm talking now about international Snapdragon version (since my Note 3 and NP 12.2 are international versions)
One day . . perhaps. .
I'm now on my second Note Pro having lost the first to an act of stupidity. This time around I've purchased a square trade warranty with accidental damage coverage for 2-years and as with the first I'll be rooting this tablet as well (gave it a week to settle in so that I'm sure that there's no hardware issues).
Here's my take on KNOX; Unless there were applications that I relied on that are checking on KNOX or evidence of root to stop me from using them I'm not going to worry myself at all about it. If I'm going to be sending in my device for repair it's going to be for a hardware issue NOT a software one because if I have the knowledge to be doing things like rooting and installing custom recoveries then I should be able to solve my own software issues (most likely through a factory reset if need be). Warranty coverage for hardware defect shouldn't be influenced by software.
wow, thanks for the fast replies guy!
So another quick question. (since muzzy mentioned breaking)
Lets say i root my note, knox trips 0x1, and in 3 months my volume rocker stops working (hardware problem). With other devices, i would call customer support, we troubleshoot for a bit, they decide to send me a new device (refurbished most likely) and i send my broken one to them since im still in warranty time wise. If they receive my note 12 and knox says 0x1, what do they do? Since my warranty is technically void, could they charge me for the tablet they sent me?
i think i just answered my own question as im thinking about it more.
SO knox is specifically SOFTWARE, if something hardware wise go amiss, my warranty is still good?
Root that bad boy. Get the files you need to root here:
http://forum.xda-developers.com/showthread.php?p=50492301
and when you encounter problems, go to this thread for answers:
http://forum.xda-developers.com/showthread.php?t=2710004&page=3
Russbad said:
Root that bad boy. Get the files you need to root here:
http://forum.xda-developers.com/showthread.php?p=50492301
and when you encounter problems, go to this thread for answers:
http://forum.xda-developers.com/showthread.php?t=2710004&page=3
Click to expand...
Click to collapse
awesome! I'll get this done as soon as im home then. Thanks for the quick responses everyone!
I installed CF auto root via Odin and it tripped the knox flag.
Bummer =(
oh well, as long as hardware wise, the warranty is fine, i guess its no big deal. Like muzzy said, anything software wise, i can fix. And if rooting trips KNOX and only void software warranty, i don't care too much about that.
Russbad said:
Root that bad boy. Get the files you need to root here:
http://forum.xda-developers.com/showthread.php?p=50492301
and when you encounter problems, go to this thread for answers:
http://forum.xda-developers.com/showthread.php?t=2710004&page=3
Click to expand...
Click to collapse
Unfortunately this won't work for the P905V (Verizon Variant). I've tried, since it said LTE but it's not for the Verizon LTE version. Still waiting for Root so I can at least install Xposed. I bought my device outright and couldn't care less about tripping KNOX.
I bought my device outright and couldn't care less about tripping KNOX
Click to expand...
Click to collapse
The only crappy part is if you get an actual hardware failure it sucks that they invalidate your entire warranty.
KNOX Warranty has nothing to do with the hardware warranty. The Knox warranty flag is there to make sure a device has never been tampered with in a way that could compromise their Knox services. Period.
Sent from my SM-P900 using Tapatalk
dodo99x said:
KNOX Warranty has nothing to do with the hardware warranty.
Click to expand...
Click to collapse
Well that's a relief.
dodo99x said:
KNOX Warranty has nothing to do with the hardware warranty. The Knox warranty flag is there to make sure a device has never been tampered with in a way that could compromise their Knox services. Period.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Those Knox services were the first thing I froze then deleted after root
Huh... im failing at the cache. Those recovery images have sure come in handy. Any tips?
Ive used odin 3.07/3.09 and CF-Auto-Root-v1awifi-v1awifixx-smp900? Im seeing a bunch of people getting stuck on the cache.img.
EDIT * USB debugging is on btw
EDIT* Got it! I unplugged ALL my other usb devices and changed the port i was using... stupid fix, but it worked.
Goodbye knox and all you other battery sucking memory hogging pieces of bloatware!
Thanks for you great help and suggestions! Greatly appreciated =D
Once the flag is tripped you can't even install Knox anymore
Sent from my SM-P900 using Tapatalk
o0pyroguy0o said:
Huh... im failing at the cache. Those recovery images have sure come in handy. Any tips?
Ive used odin 3.07/3.09 and CF-Auto-Root-v1awifi-v1awifixx-smp900? Im seeing a bunch of people getting stuck on the cache.img.
EDIT * USB debugging is on btw
EDIT* Got it! I unplugged ALL my other usb devices and changed the port i was using... stupid fix, but it worked.
Goodbye knox and all you other battery sucking memory hogging pieces of bloatware!
Thanks for you great help and suggestions! Greatly appreciated =D
Click to expand...
Click to collapse
Congrats to you, glad you worked it out! Enjoy your rooted tablet!
dodo99x said:
Once the flag is tripped you can't even install Knox anymore
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I REALLY don't care for knox anyways. Basically what i did right after rooting was open TB and uninstall everything that started with K and ended with NOX... removed a totall of 48 other programs too. Running smooth with no errors =D
Couldn't be happier.... well i could be happier if i could actually transfer files from my computer to my tablet... that would be nice. Good thing i have a card reader right?
o0pyroguy0o said:
I REALLY don't care for knox anyways. Basically what i did right after rooting was open TB and uninstall everything that started with K and ended with NOX... removed a totall of 48 other programs too. Running smooth with no errors =D
Couldn't be happier.... well i could be happier if i could actually transfer files from my computer to my tablet... that would be nice. Good thing i have a card reader right?
Click to expand...
Click to collapse
Hey, can you post your list of programs you uninstalled? I would love to take a look at it and compare it to the other threads about this, but I don't think anyone posted that many. I'm trying to improve my battery life, right now the screen takes the most and exchange service the next most.
On KNOX, I can't find anything at all that I would ever use it for so it didn't matter to me. Seems like Samsung could make it so that they could still have KNOX but allow us to root all the same. They even talk about CF root in their literature not installing a rootkit so they are not worried about it like other rooting methods that don't trip the KNOX circuit and DO instal a rootkit.
I sold my p905 a while back, going to get a p900 however, the biggest factor is able to delete files on the sd card. I know I have to root it, however, from what I read there's issues and you can no longer root it?.
rirawin said:
I sold my p905 a while back, going to get a p900 however, the biggest factor is able to delete files on the sd card. I know I have to root it, however, from what I read there's issues and you can no longer root it?.
Click to expand...
Click to collapse
Use Odin to Flash TWRP then use TWRP to Flash Super SU.
nrage23 said:
Use Odin to Flash TWRP then use TWRP to Flash Super SU.
Click to expand...
Click to collapse
Thanks, so no issues with rooting with latest firmware?.
http://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
This guide?, been ages since I rooted.
rirawin said:
http://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
This guide?, been ages since I rooted.
Click to expand...
Click to collapse
I love how that guide says all variants and then makes no mention of the P907. I would love to be able to use a custom recovery. Unless the P907 falls under the LTE moniker even though the model number is different?
Yes, TWRP works with P900
I went through this a week ago (with some help) and once I figured out how to get TWRP 2.8 to flash using Odin the process of rooting and installing a custom rom was easy. There is a thread a little lower on this forum that goes through the process.
Keith
do you have the link please.
What happens if I wish to unroot?
rirawin said:
do you have the link please.
What happens if I wish to unroot?
Click to expand...
Click to collapse
I can't post a link but the thread is in this forum. I have not unrooted but there are several threads that mention going back to stock.
Please can someone link me to an up to date method to root?
I understand towelroot only works for p905 and p900/
okay
rirawin said:
Please can someone link me to an up to date method to root?
I understand towelroot only works for p905 and p900/
Click to expand...
Click to collapse
I do not have enough posts to link an email. About three weeks ago I had the same question. The thread is in this forum on page 3, 5 or so messages down. I am the op, stedmakr. Gastrom answered the thread, provided a link and helped me root the p900 and install his rom (its excellent). Sorry I can't post links. Page 3 of this forum.
Keith
http://forum.xda-developers.com/gal...reliable-root-method-p900-build-bnk1-t2986600
I still don't quite understand, I just like to root to get sd card fix
Since there's this thread... How about KNOX? Is there a way to root P900 without tripping KNOX flag? I don't care about KNOX software itself, but since here in Poland warranty problems are left to the decision of the service, it is quite important for me not to give them opportunity to refuse a repair (if something happens, which - I hope - never will).
Wytaptalkowane na notatniku
Peri Noid said:
Since there's this thread... How about KNOX? Is there a way to root P900 without tripping KNOX flag? I don't care about KNOX software itself, but since here in Poland warranty problems are left to the decision of the service, it is quite important for me not to give them opportunity to refuse a repair (if something happens, which - I hope - never will).
Wytaptalkowane na notatniku
Click to expand...
Click to collapse
Nope, no way to avoid Knox trip.
Sent from my SM-P900 using Tapatalk
can anyone confirm please, is this the method to root:
https://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
So after I done that, I update su user and then I install sdfix is that right?.
anyone please?
Are you having problems or just too afraid to try it?
Not sure if you realize this but one of the reasons people aren't answering you is because those of us who have rooted do so and never look back. I wish I could tell you for sure that it will work with the current version of the firmware but I cant . . I rooted 8 months ago and haven't looked back. I cant speak for others but I'm not about to flash stock and go through the whole thing again just to update an old thread so I suspect that this is part of the reason that there's no updated guide. For devices that get a ton of development things are different but this niche device doesn't have a flurry of development activity surrounding it so . . .
One thing I can say is that it is my experience that if CF Autoroot fails the worst thing you're left with is a tripped knox and the stock rom without root. I say this because I was one of the unlucky ones who had to struggle through multiple attempts to get CF Autoroot to work. Eventually it did but during that time I had multiple shots at it and each time I was able to at least recover to the point of getting stock OS and recovery working again.
I see no reason why you can't achieve root on a SM-P900. If you can't do it with CF Autoroot then just download one of Gatsrom's images of stock rooted, flash TWRP using Odin (with auto reboot option disabled), boot into TWRP and do a full wipe and flash Gatsrom's image. You'll lose your setup and apps but you'll get root.
muzzy996 said:
Are you having problems or just too afraid to try it?
Not sure if you realize this but one of the reasons people aren't answering you is because those of us who have rooted do so and never look back. I wish I could tell you for sure that it will work with the current version of the firmware but I cant . . I rooted 8 months ago and haven't looked back. I cant speak for others but I'm not about to flash stock and go through the whole thing again just to update an old thread so I suspect that this is part of the reason that there's no updated guide. For devices that get a ton of development things are different but this niche device doesn't have a flurry of development activity surrounding it so . . .
One thing I can say is that it is my experience that if CF Autoroot fails the worst thing you're left with is a tripped knox and the stock rom without root. I say this because I was one of the unlucky ones who had to struggle through multiple attempts to get CF Autoroot to work. Eventually it did but during that time I had multiple shots at it and each time I was able to at least recover to the point of getting stock OS and recovery working again.
I see no reason why you can't achieve root on a SM-P900. If you can't do it with CF Autoroot then just download one of Gatsrom's images of stock rooted, flash TWRP using Odin (with auto reboot option disabled), boot into TWRP and do a full wipe and flash Gatsrom's image. You'll lose your setup and apps but you'll get root.
Click to expand...
Click to collapse
Well said mate! Well said.
If someone's gonna root their tablet, especially one of this caliber & price point. Then they should know how to recover it back to stock on their own. Concerning the tripping of Knox, who cares! Samsung won't turn down a hardware issue covered under warranty just because you decided to load another ROM. That topic has been discussed to death in another thread. If your going to root this thing, then root it and live on! LoL ?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Android.Ninja said:
Samsung won't turn down a hardware issue covered under warranty just because you decided to load another ROM.
Click to expand...
Click to collapse
Not here in Poland...
I see a lot of similar questions, but am getting yes and no answers.
Background+Rant: after spending yesterday bashing my head against knox, i managed to get my new sm-g900p from oem 5.0 back to stock 4.4.2, towel-rooted successfully (keeping 0x0). Good, but not enough. without a real recovery to make a backup, samsung is actually putting me at more risk than ever at turning my phone into a brick (security my ***). plus the slow/ugly stock rom hurts my head after seeing what Android should be. They act like making a rewarding process dangerous is going to stop this entire community! Anyway enough ranting from a non-dev.
what i need to know is since i have NOT sent knox into lockdown mode(0x1), can i get knox out of the Bootloader? from what i understand, you can disable the knox apps using superSU, titanium, or a command prompt, but this will not effect the flash counter (not eliminating the risk of permanent 0x1). we flash bootloaders all the time with our recoveries, firmwares, and roms. If knox has not activated (ie blocking root, apps, etc) how is this bootloader different?
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html seems hopeful as it involves extracting the firmware to linux, removing the knox code, repacking and reflashing. sounds like something even i could do, but would feel more comfortable downloading from a real developer.
Hopes and thoughts to go along with my disappointment and concerns?
3rdsurfer said:
I see a lot of similar questions, but am getting yes and no answers.
Background+Rant: after spending yesterday bashing my head against knox, i managed to get my new sm-g900p from oem 5.0 back to stock 4.4.2, towel-rooted successfully (keeping 0x0). Good, but not enough. without a real recovery to make a backup, samsung is actually putting me at more risk than ever at turning my phone into a brick (security my ***). plus the slow/ugly stock rom hurts my head after seeing what Android should be. They act like making a rewarding process dangerous is going to stop this entire community! Anyway enough ranting from a non-dev.
what i need to know is since i have NOT sent knox into lockdown mode(0x1), can i get knox out of the Bootloader? from what i understand, you can disable the knox apps using superSU, titanium, or a command prompt, but this will not effect the flash counter (not eliminating the risk of permanent 0x1). we flash bootloaders all the time with our recoveries, firmwares, and roms. If knox has not activated (ie blocking root, apps, etc) how is this bootloader different?
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html seems hopeful as it involves extracting the firmware to linux, removing the knox code, repacking and reflashing. sounds like something even i could do, but would feel more comfortable downloading from a real developer.
Hopes and thoughts to go along with my disappointment and concerns?
Click to expand...
Click to collapse
I did a little reading on the xda thread that links to but other than it being done just because it can, I don't see the real usefulness in the exercise of removing knox from a stock bootloader.
As you already pointed out, getting anywhere with a stock rom is pretty much pointless without two things:
1. Root
2. Custom Recovery
First of all, lets face it, there is only so much you can do with a stock odexed rom. Secondly, I personally dont understand the need to keep the knox bit untripped. Even if you remove knox from the bootloader, once custom recovery is installed, I'm pretty sure you're going to trip the bit anyway.
He even states so in the thread here:
http://forum.xda-developers.com/showpost.php?p=51828541&postcount=102
---------- Post added at 02:25 PM ---------- Previous post was at 02:17 PM ----------
And FYI, no one to my knowledge has ever hard bricked a Sprint Galaxy S5 phone. The only real issue at the moment is once you flash the OD3 Lollipop firmware or newer (currently OF6 I think) or take the OTA update, flashing any firmware older than OD3 is blocked.
Hi,
Bassically I'm just trying to get my phone to be unrooted to pass SafetyNet (Android Pay, Pokemon Go, and others) but have some system modications (adaway and removed boot sounds mainly).
What I did do is flash stock odin firmware (PG1), then twrp, supersu, and make my changes. Then if I just unroot with supersu it still fails SafetyNet. If I unroot and tell SuperSU to restore boot.img then I get a bootloop. Probably due to TWRP still being there and not stock Recovery? So I thought maybe from there I can just flash boot and recovery via odin but that didn't seem to work either. Is it possible to take the stock firmware and flash whatever I need except system? Or not possible to alter system and go back to stock boot/recovery?
Thanks!
I don't play but here's a link for info
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
greco2003 said:
I don't play but here's a link for info
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Click to expand...
Click to collapse
That no longer works to pass SafetyNet. Last couple weeks there have been a couple of root/xposed solutions only for Google to changes SafetyNet and detect it. So I was thinking of just getting rid of root but hopefully keeping the couple system mods I like...
Not much help in here. Anyone know of a way to have a modified system but no root (or recovery if I don't need twrp)? Mainly I'd just like to update my hosts file and remove the stupid reboot "ding".
My hope was to modify system via twrp/supersu and then flash recovery/boot to get it back to stock but there must be some sort of check because that just causes dm-verity failed notification in stock recovery. I can unroot via the SuperSU app but unrooting and telling it to restore stock boot.img causes loop. Unroot and tell it to leave boot.img lets my phone work but still doesn't pass safetynet checks.
All this work makes me miss my HTC phones. They seemed so much easier to manipulate.
This guy's solution lets me have a stock system with some system modifications. So now I have what I wanted, passing Safety Net, removed boot sound and applied adaway hosts file!
http://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
@henderjr i found this. Would this work under you're criteria needed??
https://theunlockr.com/2015/09/26/how-to-unroot-the-samsung-galaxy-note-5-t-mobile-sprint-versions/
Im thinking of doing this also.
I know yur post is pretty old bug i just got my note recently but i had no idea there was such a lack in development for sprint version. If u did end up accomplishing unroot with eneabled security, let me know. Thanks
Abu Nazir said:
@henderjr i found this. Would this work under you're criteria needed??
https://theunlockr.com/2015/09/26/how-to-unroot-the-samsung-galaxy-note-5-t-mobile-sprint-versions/
Im thinking of doing this also.
I know yur post is pretty old bug i just got my note recently but i had no idea there was such a lack in development for sprint version. If u did end up accomplishing unroot with eneabled security, let me know. Thanks
Click to expand...
Click to collapse
That will unroot it but you'll also lose all system modifications so it'll be stock again. I wanted adaway hosts file and a couple other system mods. What I posted above did work for me but about six weeks ago I exchanged my Note 5 for a new one (camera died on the old one) and haven't rooted. I enjoy using Samsung Pay so I haven't tripped Knox yet.
henderjr said:
That will unroot it but you'll also lose all system modifications so it'll be stock again. I wanted adaway hosts file and a couple other system mods. What I posted above did work for me but about six weeks ago I exchanged my Note 5 for a new one (camera died on the old one) and haven't rooted. I enjoy using Samsung Pay so I haven't tripped Knox yet.
Click to expand...
Click to collapse
Oh ok. Yep gotcha. Sorry i forgot u said that. Ive been reading so much on these forums in the past couple days im getting myself confused on what ive read and havent. Ok tho thanks alot. Really appreciate the reply tho on these dead forums. Lol. Thanks again
So I have a Sprint Galaxy S6. Until last week, I was running Android 5.1. I actively avoided upgrading to 6.0.1 because things are getting more difficult with the use of certain programs and with rooting and all that.
Something important required me to TRY upgrading to Android 6, hoping this might solve my problem. It didn't. The problem has since fixed itself (much to my confusion), but now I'm stuck with Android 6. And by upgrading I lost my custom recovery and root. I now find out that downgrading is quite a task and multiple sources say don't do it under any circumstances.
I'm (probably) fine with keeping Android 6.0 if I could just figure out how to root my phone (preferably easily). Tried PingPongRoot which is what I had previously, also tried King Root and Kingo Root and nothing worked. They all failed. PPR even put me in a catch-22 whereby I couldn't root until I got SuperSU working, but SuperSU wouldn't work because the binary wasn't installed and required root to do so. So I needed root to make SuperSU work and needed SuperSU to work in order to root. Fail.
So I got CF-Auto-Root. I figured easy, right? Then I get something I've never seen before: "Custom Binary Blocked by FRP Lock." This was not on my phone before I updated. Flashing with Odin failed instantly. Phone still works, but I'm back to square one. Looked up how to fix this problem and found that, this too, could mess me up. I'm locked out of Titanium Backup until I root and I don't want to go ruining my phone without a backup of all of my apps, for which I need TB.
1) How do I root my Galaxy S6 SM-G920P Android 6.0.1 easily? Relatively easily?
2) Is there a safe way to get rid of the FRP Lock so that I can root?
3) If rooting Android 6 is going to be dangerous, is downgrading back to Android 5 possible? Is this equally, if not more, dangerous?
I did NOT know what a pain this would be going to Android 6. I'm totally frazzled right now and out of ideas. Any help would be appreciated.
hamstrman said:
So I have a Sprint Galaxy S6. Until last week, I was running Android 5.1. I actively avoided upgrading to 6.0.1 because things are getting more difficult with the use of certain programs and with rooting and all that.
Something important required me to TRY upgrading to Android 6, hoping this might solve my problem. It didn't. The problem has since fixed itself (much to my confusion), but now I'm stuck with Android 6. And by upgrading I lost my custom recovery and root. I now find out that downgrading is quite a task and multiple sources say don't do it under any circumstances.
I'm (probably) fine with keeping Android 6.0 if I could just figure out how to root my phone (preferably easily). Tried PingPongRoot which is what I had previously, also tried King Root and Kingo Root and nothing worked. They all failed. PPR even put me in a catch-22 whereby I couldn't root until I got SuperSU working, but SuperSU wouldn't work because the binary wasn't installed and required root to do so. So I needed root to make SuperSU work and needed SuperSU to work in order to root. Fail.
So I got CF-Auto-Root. I figured easy, right? Then I get something I've never seen before: "Custom Binary Blocked by FRP Lock." This was not on my phone before I updated. Flashing with Odin failed instantly. Phone still works, but I'm back to square one. Looked up how to fix this problem and found that, this too, could mess me up. I'm locked out of Titanium Backup until I root and I don't want to go ruining my phone without a backup of all of my apps, for which I need TB.
1) How do I root my Galaxy S6 SM-G920P Android 6.0.1 easily? Relatively easily?
2) Is there a safe way to get rid of the FRP Lock so that I can root?
3) If rooting Android 6 is going to be dangerous, is downgrading back to Android 5 possible? Is this equally, if not more, dangerous?
I did NOT know what a pain this would be going to Android 6. I'm totally frazzled right now and out of ideas. Any help would be appreciated.
Click to expand...
Click to collapse
Rooting is fairly straightforward with cf-autoroot, you're main problem here is frp (factory reset protection) which is a Google security feature, you need to remove this or bypass this 1st before doing anything. I've seen a few articles and guides on Google, but as I don't have this issue I cannot say if they work or not but at a glance they do not seem very difficult. But once you get past the frp lock you can go ahead and root. If you are on a newer marshmallow bootloader then downgrading to lollipop is pretty much impossible
sofir786 said:
Rooting is fairly straightforward with cf-autoroot, you're main problem here is frp (factory reset protection) which is a Google security feature, you need to remove this or bypass this 1st before doing anything. I've seen a few articles and guides on Google, but as I don't have this issue I cannot say if they work or not but at a glance they do not seem very difficult. But once you get past the frp lock you can go ahead and root. If you are on a newer marshmallow bootloader then downgrading to lollipop is pretty much impossible
Click to expand...
Click to collapse
Thanks. I looked it up myself. Requires something called "Find my mobile," a setting under "Lock Screen and Security." I don't have that.
Samsung's website says if you don't see it, then your device is not supported. Kill me now!
I completely screwed myself by updating. If anyone else knows a way to do this with my... limitations, I would love to hear about it.
hamstrman said:
Thanks. I looked it up myself. Requires something called "Find my mobile," a setting under "Lock Screen and Security." I don't have that.
Samsung's website says if you don't see it, then your device is not supported. Kill me now!
I completely screwed myself by updating. If anyone else knows a way to do this with my... limitations, I would love to hear about it.
Click to expand...
Click to collapse
Have you had a look at method 1 on the below page?
https://www.google.ie/amp/s/www.pro...tory-reset-protection-on-samsung-devices/amp/
sofir786 said:
Have you had a look at method 1 on the below page?
https://www.google.ie/amp/s/www.pro...tory-reset-protection-on-samsung-devices/amp/
Click to expand...
Click to collapse
Method 1 being... factory reset? I'm hoping to keep my phone in tact.
I did find something stupidly simple that someone just happened to off hand comment on in an old thread. Apparently there's a switch in the settings to disable OEM protections. I didn't think it would work but it really was that easy.
Was able to root successfully using CF, but then doing a SuperSU full unroot caused a bootloop. I have to figure out the proper way to root for my needs now.
Thanks for the suggestion, though!