Database Users

Reactivation Lock not working after root

hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/

jgfernog said:
hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
Click to expand...
Click to collapse
Same here , when Im rooting doesnt show anything , and the smartphone turns on without showing the red android that suppose to show

jgfernog said:
hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
Click to expand...
Click to collapse
Same here, maybe installing xposed and putting a request for a module? although s health and private mode don't work on my note 4 either (xposed running)

UnboundDemon said:
Same here, maybe installing xposed and putting a request for a module? although s health and private mode don't work on my note 4 either (xposed running)
Click to expand...
Click to collapse
this is a kernel related, I think. Everybody says that it still working on Snapdragon's Note 4, but here at Exynos, you can't activate it.

jgfernog said:
this is a kernel related, I think. Everybody says that it still working on Snapdragon's Note 4, but here at Exynos, you can't activate it.
Click to expand...
Click to collapse
I dont think it is that, I have a friend with the same model that us, and the activation works on his phone :s

So, guys, have anyone solved this problem?
I also have rooted Note 4 and neither "Remote controls" nor "reactivation lock" can I activate...

reactivetion lock not working
I also encountered a similar case but only used through l launch , give me one new idea when it dies in it :good:

Guys, has anybody solved this problem?

Here I am, rooted GS5 with MM fw, before root it worked, as it did with lollipop and kitkat.
After root it doesn't turn on anymore, I reflashed stock recovery too. I guess it's related to knox 0x1, with rooted knox 0x0 kitkat and lollipop I could enable it.
Or maybe it's kernel related, so systemless root with stock kernel could be the solution

Good news, after reflashing a stock firmware I could enable RL back. So it's not knox related but root related. Tomorrow I'll try with systemless root

Joker87 said:
Good news, after reflashing a stock firmware I could enable RL back. So it's not knox related but root related. Tomorrow I'll try with systemless root
Click to expand...
Click to collapse
I think what is needed it to copy your stock recovery from an official touchwiz rom and flash it. You will need a tar.gz converter to flash it via odin. Sometime ago I tried it where your root remains but you have a stock recovery. I believe all those Samsung security features like Reactivation Lock relies on a stock recovery and not a custom like ( TWRP/CWM)

chaundb said:
I think what is needed it to copy your stock recovery from an official touchwiz rom and flash it. You will need a tar.gz converter to flash it via odin. Sometime ago I tried it where your root remains but you have a stock recovery. I believe all those Samsung security features like Reactivation Lock relies on a stock recovery and not a custom like ( TWRP/CWM)
Click to expand...
Click to collapse
I reflashed stock recovery but still no luck. It's root related, or better kernel related, as someone posted above. I'm on systemless root and it shows "warranty bit kernel" message at boot. With rooted lollipop and stock kernel/recovery it worked

Joker87 said:
I reflashed stock recovery but still no luck. It's root related, or better kernel related, as someone posted above. I'm on systemless root and it shows "warranty bit kernel" message at boot. With rooted lollipop and stock kernel/recovery it worked
Click to expand...
Click to collapse
Really, so how can I do the same on Marshmallow. Where can I obtain a systemless root method for my SM-N910H Note 4 ???

chaundb said:
Really, so how can I do the same on Marshmallow. Where can I obtain a systemless root method for my SM-N910H Note 4 ???
Click to expand...
Click to collapse
Just flash supersu beta via twrp
You must have stock boot.img, I suggest reflashing the entire stock firmware if you did some modifications

Joker87 said:
Just flash supersu beta via twrp
You must have stock boot.img, I suggest reflashing the entire stock firmware if you did some modifications
Click to expand...
Click to collapse
Look...i am currently rooted. I have twrp 3.0 and i flashed super su beta. I dont have any modified or special kernels of that sort...just root. So are you telling me all i need to do is flash the original touchwiz boot.img from the marshmallow rom file ( i will have to go convert it to a Tar file) ???.... And that will give me the ability to stay rooted and be able to use reactivation lock again ???

chaundb said:
Look...i am currently rooted. I have twrp 3.0 and i flashed super su beta. I dont have any modified or special kernels of that sort...just root. So are you telling me all i need to do is flash the original touchwiz boot.img from the marshmallow rom file ( i will have to go convert it to a Tar file) ???.... And that will give me the ability to stay rooted and be able to use reactivation lock again ???
Click to expand...
Click to collapse
Nope... rl doesn't work with any root method

Joker87 said:
Nope... rl doesn't work with any root method
Click to expand...
Click to collapse
Ok..thats what i thought.......its best we stay without it then. Or go back completely stock and unrooted to use the feature.

Hello, seen there is no new news about this.. Has anyone got around this?
Can we root and activate the reactivation lock now?
Thanks

Galaxy Note Pro 12.2 5.1.1 OTA P907AUCU1BOH3.ZIP

People were asking for the OTA Zip so here it is.
....You are using this at your own risk I am not responsible if you ruin your tablet.
This is my first REAL contribution to the forum so if I've done something wrong please let me know and I will correct it.
I was able to flash this using the stock recovery.
If you flash the update and want root back or just don't like the update this is completely reversible.
If you are rooted you will need to flash back to stock firmware before you can flash this update. Plenty of threads here that will walk you through how to go back to stock.
If you are still on firmware P907AUCU1AND7 you will need to upgrade to P907AUCU1ANK2 before P907AUCU1BOH3.
This is the link to P907AUCU1ANK2 KitKat OTA update.
https://mega.nz/#!INw0lbDC!2uvFS6gBxq51YK8ghi3_yI0YFEazObe7-lPOJHGDr68
This is the link to P907AUCU1BOH3 5.1.1 Lollipop OTA update.
https://mega.nz/#!JYYmASyR!wKCXQr-2iS1Yk4P-MOiil1hg04ZltGdTjfVBBqCoKIc
I suggest putting the updates on your SD Card.
Boot into recovery. Restart the tablet holding the volume up as it restarts.
Go to apply update from external storage and select the update zip.
Let it do its thing and you will be updated.
Perhaps some kind soul out there will find a way to add root to this update then I would be a happy guy.

eazyg said:
People were asking for the OTA Zip so here it is.
....You are using this at your own risk I am not responsible if you ruin your tablet.
This is my first REAL contribution to the forum so if I've done something wrong please let me know and I will correct it.
I was able to flash this using the stock recovery.
If you flash the update and want root back or just don't like the update this is completely reversible.
If you are rooted you will need to flash back to stock firmware before you can flash this update. Plenty of threads here that will walk you through how to go back to stock.
If you are still on firmware P907AUCU1AND7 you will need to upgrade to P907AUCU1ANK2 before P907AUCU1BOH3.
This is the link to P907AUCU1ANK2 KitKat OTA update.
https://mega.nz/#!INw0lbDC!2uvFS6gBxq51YK8ghi3_yI0YFEazObe7-lPOJHGDr68
This is the link to P907AUCU1BOH3 5.1.1 Lollipop OTA update.
https://mega.nz/#!JYYmASyR!wKCXQr-2iS1Yk4P-MOiil1hg04ZltGdTjfVBBqCoKIc
I suggest putting the updates on your SD Card.
Boot into recovery. Restart the tablet holding the volume up as it restarts.
Go to apply update from external storage and select the update zip.
Let it do its thing and you will be updated.
Perhaps some kind soul out there will find a way to add root to this update then I would be a happy guy.
Click to expand...
Click to collapse
Thank you a lot !!!!

Well it worked, yay, thank you so much for making a zip file, you are awesome!!...Now we just have to figure out how to root this sucker
Sent from my SAMSUNG-SM-P907A using XDA Premium HD app

I'm still on 4.4.2 can I use this to update?

dont work here, the P907AUCU1ANK2 work fine, but the P907AUCU1BOH3 gimme this type of errors:
E: Error in tmp sideload package.zip
status 7
and
E unknow volume for path sdcard1
any idea?

I had same error except it referenced unnecessary files or the like just before the error.
I was rooted before last 4.4.2 update. It installed ANK update fine(no more root possible though) but 5.1.1 failed.
I reinstalled 4.4.2 rooted it AGAIN and changed CSC files back to ATT(I was messing with changing region so could install Europe version through ODIN), only one file had not been overwritten by re-install.
Unrooted completely and Then installed ANK AND 5.1.1 updates and it took that time. After initial 4.4.2 system Odin flash it factory reset this time. I had reinstalled 4.4.2 numerous times(ODIN) without this happening before.
When I updated my 2nd tablet it was never rooted but a few things were dorked by Previous owner so I factory reset it first. It came with ANK already installed so just updated to 5.1.1 with no issues.
I believe being rooted and installing the ANK update then 5.1.1 dorked something up.
I think I would unroot fully then try if still doesn't work do a factory reset then install.
Sent from my SAMSUNG-SM-P907A using XDA Free mobile app

You must be fully stock and not rooted. It will not install if you are rooted.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Thanks!
I used ODIN to go back to stock and remove root, http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/post54879249#post54879249
Then without booting into stock and signing in, I installed both zips in recovery mode. Took a little bit longer than normal loading the AT&T splashscreen for the first time but it's working great!

I'm constantly facing a reboot \ crash loop the minute I get on 5.1.1 (stock, knox 0x0). Even went so far as to completely re-stock via KIES, and OTA ANK2...then finally 5.1.1. No luck.
I've repeated it various ways and combinations, multiple times without success. reboots either immediately after splash or within 2 - 3 mins after boot. No issues on AND7 or ANK2. Any ideas?

I'm not familiar with ATT, whether they lock their bootloaders or not, but whatever the case is... you may never be able to root again (if they do) or wait an unusually long time (if they started to with 5.1.1 like with some newer devices)
needless to say, a rom can be modded to include root a lot easier than giving you a new way to flash the rom

OP can you please change your thread name I am happy reading 5.1.1 for note pro 12.2 and then disappointed every time I read the build number couse it's for at&t
Gesendet von meinem SM-N910F mit Tapatalk

Thanks, it works great without BSOD after update to Lollipop

LegendSmoker said:
OP can you please change your thread name I am happy reading 5.1.1 for note pro 12.2 and then disappointed every time I read the build number couse it's for at&t
Gesendet von meinem SM-N910F mit Tapatalk
Click to expand...
Click to collapse
The title mentioned P907A which is AT&T model., P905V is for Verizon.
You should know the Note Pro wifi only is SM-P900 which 5.0.2 is the latest version. Only the Tab Pro SM-T900 Wifi gets to 5.1.1

The fact that 907 is in the zip file name may escape some people though. Typically titles are a little more descriptive when it comes to distribution so I can understand the reason for the rename request.
Sent from my SM-P900 using Tapatalk

Beut said:
The title mentioned P907A which is AT&T model., P905V is for Verizon.
You should know the Note Pro wifi only is SM-P900 which 5.0.2 is the latest version. Only the Tab Pro SM-T900 Wifi gets to 5.1.1
Click to expand...
Click to collapse
I know about different versions but it would be easier to understand when you would write At& t note pro getting 5.1.1 and not note pro and then the hint for model in the end of thread title in build nr... don't understand me wrong when I open the thread on Tapatalk with my note 4 I only see :
Note pro 12.2 finally getting 5.1.1 ( the build nr in the title is hide in ...).
anyway I know p900 is wifi and exynos while p905 LTE and snapdragon. Same for tab pro
and there are 5.1.1 builds out for both tab pro's t900 and t905.
Gesendet von meinem SM-N920C mit Tapatalk

Thank You, soooooo much!!!
Your instructions are extremely clear.
You have every thing in one place.
You don't use jargon only a few prevledged souls know.
Your a perfect contributor.
Thank you again.

I'm also getting (Status 7) error and cant get round it for some reason
my device was rooted which seemed to make the first update go on without any error but the second one isn't installing. when I put it back to stock to tried both updates without root in the first place they failed. so im going to try put it back to stock then root then install first update, which seemed to help my problem of blue screen but I didn't only use it for a short while.
any help?

When I try reboot into recovery mode to install the zip it goes into the files within the zip. I have no idea what to do.

Updates don't work for me
I'm having some trouble using these updates. When I try to apply either one through the recovery, I get two messages:
footer is wrong
signature verification is wrong
I've got an AT&T SM-P907a that has never been rooted and is pure stock. It had been up to the ANK2 firmware, so I tried your BOH3 package and got these messages. I ended up using ODIN to return back to the original stock version, but I can't use either of your packages now.
To add to the confusion, I can't update using ANY standard, official method. Kies 3 says there are no firmware updates available, even when I went back to AND7 stock and the OTA check for updates function says the same thing.
Is there an ODIN package somewhere for BOH3 that I could just use?
Thanks!

I updated at least 8 of SM-P907A from Kitkat to Lollipop via this way. Most would go smoothly but one I got stuck at the second update due to error.
I flashed the firmware of ND7 downloaded from sammobile, then proceeded to update via SD card, it worked without problem.
Try it, flash back the original firmware via Odin, then update via SD card. A fresh and clean stock ROM will make the update easier.

How to root samsung note 4 SM-N910C on android 6.0.1?

Recently I used odin to flash Russian marshmallow on my note 4 SM-N910C. I also flashed TWRP successfully.
I tried the usual rooting method with cf-autoroot but I got into bootloops. also I tried flashing the spacex kernel but the device didn't start up at all.
Now that I tried everything I know, is there any method to root it?
I had to go back to 5.1.1 and wait for rooting method for 6.0.1.
Any help will be appreciated.

Flash the SuperSU zip from TWRP? Do that.

vampokin said:
Recently I used odin to flash Russian marshmallow on my note 4 SM-N910C. I also flashed TWRP successfully.
I tried the usual rooting method with cf-autoroot but I got into bootloops. also I tried flashing the spacex kernel but the device didn't start up at all.
Now that I tried everything I know, is there any method to root it?
I had to go back to 5.1.1 and wait for rooting method for 6.0.1.
Any help will be appreciated.
Click to expand...
Click to collapse
Flash (for Root) this SuperUser zip via TWRP 3.0+ for stock MM 6.0.1 (N910C)..
ChainFire (the Dev. for Root) requests to link to his files, but cannot, for the life of me, find where I downloaded it from, so here is my personal copy..please donate to ChainFire if you can, for all his hard efforts..
I'm on the "Polish" version here in USA..works flawlessly..
Here >> https://drive.google.com/file/d/0Bzr_08QESKW4WjRzaUcwNlVOMVU/view?usp=drivesdk
SM-N910C Gold Note 4 (MM 6.0.1)

Thanks a lot it works though a little buggy

vampokin said:
Thanks a lot it works though a little buggy
Click to expand...
Click to collapse
"buggy"..lol..runs flawless on my device, but..every device/user is a bit different..glad you got it working..
SM-N910C Gold Note 4 (MM 6.0.1)

NWKENT said:
"buggy"..lol..runs flawless on my device, but..every device/user is a bit different..glad you got it working..
SM-N910C Gold Note 4 (MM 6.0.1)
Click to expand...
Click to collapse
Is this the link?
https://download.chainfire.eu/559/CF-Root
from whichever device is closest to hand

NWKENT said:
Flash (for Root) this SuperUser zip via TWRP 3.0+ for stock MM 6.0.1 (N910C)..
ChainFire (the Dev. for Root) requests to link to his files, but cannot, for the life of me, find where I downloaded it from, so here is my personal copy..please donate to ChainFire if you can, for all his hard efforts..
I'm on the "Polish" version here in USA..works flawlessly..
Here >> https://drive.google.com/file/d/0Bzr_08QESKW4WjRzaUcwNlVOMVU/view?usp=drivesdk
SM-N910C Gold Note 4 (MM 6.0.1)
Click to expand...
Click to collapse
Hate to ask this random question here, but I'm currently downloading the Polish xeo mm files to flash in odin. I have found the twrp 3.0.2 tar on Google. Is that compatible with MM universally after 3.0? Or is there a different 3.0.2 for LP and MM?
Sent from my SM-N920C using XDA-Developers mobile app

carnivalrejectq said:
Hate to ask this random question here, but I'm currently downloading the Polish xeo mm files to flash in odin. I have found the twrp 3.0.2 tar on Google. Is that compatible with MM universally after 3.0? Or is there a different 3.0.2 for LP and MM?
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
Is this the version?
https://dl.twrp.me/treltexx/
The latest version of TWRP is compatible with MarshMallow.
from whichever device is closest to hand

baltics said:
Is this the version?
https://dl.twrp.me/treltexx/
The latest version of TWRP is compatible with MarshMallow.
from whichever device is closest to hand
Click to expand...
Click to collapse
Yes that's it. I have a strange issue though. If i flash MM manuall from the poland version......i can get that twrp to work.....if i take the OTA to MM from the poland Lollipop..... Then that twrp wont work......the reason this is an issue is because the OTA MM is faster and more fluid on my device than the odin tar......why idk. This is a strange case lol.
Sent from my 6045O using XDA-Developers mobile app

carnivalrejectq said:
Yes that's it. I have a strange issue though. If i flash MM manuall from the poland version......i can get that twrp to work.....if i take the OTA to MM from the poland Lollipop..... Then that twrp wont work......the reason this is an issue is because the OTA MM is faster and more fluid on my device than the odin tar......why idk. This is a strange case lol.
Sent from my 6045O using XDA-Developers mobile app
Click to expand...
Click to collapse
CF (N910c) did work for me, but after few days mysteriously stopped working. No SU binary could be found and therefore no root . Then i decided to root again but unsuccessfully. CF does what is supposed to do and after a phone reboots no root, so i tried this way and it worked: Flashed TWRP tar from odin, than flashed superSU zip from twrp. phone rebooted 2-3 times (this is normal) then when it booted, still did not work until i rebooted it once more manually and screen "android is upgrading" appeared for a few sec. After that everything works as is supposed to.
I have found this video on YouTube (Spanish but it contains download links in video description) and detailed explanation how to do it.

Dryfit said:
CF (N910c) did work for me, but after few days mysteriously stopped working. No SU binary could be found and therefore no root . Then i decided to root again but unsuccessfully. CF does what is supposed to do and after a phone reboots no root, so i tried this way and it worked: Flashed TWRP tar from odin, than flashed superSU zip from twrp. phone rebooted 2-3 times (this is normal) then when it booted, still did not work until i rebooted it once more manually and screen "android is upgrading" appeared for a few sec. After that everything works as is supposed to.
I have found this video on YouTube (Spanish but it contains download links in video description) and detailed explanation how to do it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2897428
Sent from my GT-I9300 using XDA-Developers mobile app

baltics said:
http://forum.xda-developers.com/showthread.php?t=2897428
Sent from my GT-I9300 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes i tried this first http://forum.xda-developers.com/show....php?t=2897428
and it worked. After few days root acess somehow dissapeared. And i was not able to root again using cf root. I flash cf root, phone reboots, flash su binaries and reboots again. When it boots up again no root access. (Stock Android 6.0.1) Then i tried method i mentioned in a previous post and it worked.

Galaxy Tab S2 (T817T) Marshmallow Update

I found this on T-Mobile's site stating the update would be available starting today. https://support.t-mobile.com/docs/DOC-23647 Don't have my tablet to confirm. Has anyone with this tab checked for the update to confirm?

Milly7 said:
I found this on T-Mobile's site stating the update would be available starting today. https://support.t-mobile.com/docs/DOC-23647 Don't have my tablet to confirm. Has anyone with this tab checked for the update to confirm?
Click to expand...
Click to collapse
Dowloading now, 1.02 gigs...

eric_mac said:
Dowloading now, 1.02 gigs...
Click to expand...
Click to collapse
Installing...

Thanks for confirming. I stumbled on the link just trying to see if I could find some eta on the update.

Just updated. Now time to root.

I saw this on T-Mobile's site a couple of days ago, but I'm on the fence about updating. I updated my Note 4 (910T) when MM came out and I'm used to it, but they removed the ability to alter the quick settings toggles (Samsung disabled system ui tuner) so you can no longer add hidden features like mobile data or VPN. While I can grudgingly live without it on the Note 4, I find it too handy to do without on the 817T. Unless someone finds a way around this, I'm staying put for the time being.

Just updated my T817T to MM.. thanks for the info. Updated and rooted as well with supersu 2.74

kingwicked said:
Just updated my T817T to MM.. thanks for the info. Updated and rooted as well with supersu 2.74
Click to expand...
Click to collapse
How did you root your T817T with MM? Did you already have TWRP and it was retained with the update and you just flashed SuperSu?

I flashed twrp 3.0.0.2 for t810 it works for marshmallow and then I flashed super su 2.74.
It was not retained after update. I flashed it via Odin again

kingwicked said:
I flashed twrp 3.0.0.2 for t810 it works for marshmallow and then I flashed super su 2.74.
It was not retained after update. I flashed it via Odin again
Click to expand...
Click to collapse
I had issues with xposed and the machine becoming unresponsive. Had to reinstall and root. Works fine without xposed.

hgill2412 said:
I had issues with xposed and the machine becoming unresponsive. Had to reinstall and root. Works fine without xposed.
Click to expand...
Click to collapse
I have no issues with xposed .works perfect for me with wanam's xposed V86 for MM

Success!
Since I had installed TWRP and rooted, I could not update to MM. I re-flashed back to stock 5.1.1 with Odin and then was able to update to MM.
After the update I flashed the T815 TWRP with Odin (make sure you don't auto-reboot and boot into TWRP right after flashing to make it stick). Then I flashed the SuperSu 2.76 ZIP from TWRP.
So I now have a stock rooted 6.0.1 ROM. Everything seems to work fine for me. I can use LTE and even enable the mobile hotspot.

Viper4Android on Marshmallow 6.0.1 N910C ?

Hi,
does anyone know how to install viper4android into SM-N910C 6.0.1 Stock *properly*?
I have root, busybox, ViPER4Android-supolicy zip installed and it starts ok but after a song or two it goes back to Processing: NO.

Hi,
Try with a custom kernel. A permissive one. I know it might be a painful but it's a way that works.
Good luck.
Sent from my Note 4 using XDA Labs

0-W4lly said:
Hi,
Try with a custom kernel. A permissive one. I know it might be a painful but it's a way that works.
Click to expand...
Click to collapse
Thanks, but the ViPER4Android-supolicy zip took care of selinux
Also, if anyone's interested I've finally managed to make it work permanently. You need to remove the deep buffer stuff from audio_policy.conf (placed at system/etc) with a root explorer, AND remove/uninstall/disable SoundAlive in system apps.

Could use some help guys. Trying to get viper/ARISE running on a note edge (sprint). I've done everything to meet every prereq. I have root. I have busybox. I have permissive SELinux. I've done all the build.prop and audio_policy.conf edits. I've flashed a billion different zips. Nothing's working. Viper says the driver is installed and processing correctly, but none of the sound coming out of the speakers or headphones is actually viper-processed sound. I'm on Marshmallow (6.0.1) and running Emotion Kernel. Any help is appreciated. Thanks