Related
There are users here in Canada with Note 3's that have "Custom" in "Current Bianary" and "System Status".
This information has not been posted, I have NO idea why. I am guessing these people could care less about us (the people still in the dark).
I have only just obtained a Note 3 (Week ago) and I am trying to figure this stuff out.
We have a special Note 3 in our N900W8's. Apparently we can:
- Downgrade from 4.4.2 to 4.3 via Odin 3.09 without tripping Knox (not sure if this requires the Mexican bootloader first or if we can do it with our Canadian bootloaders)
- Keep Knox at 0x0 with Custom Everything else. From what I see, our bootloaders are unlocked allowing us to flash our phones in Odin with multiple files (not 1 file mode as this contains a bootloader) as long as we dont include the bootloader (theory from what I have seen, and read a few times, no confirmation).
However I can not get an answer out of anyone who knows anything. I cannot just blindly flash and see if Knox is tripped, I'll only get one shot. Not worth it IMO.
Can anyone chime in on this? Is it acceptable to call members out? I know exactly who the 2 people are that have Custom everything and Knox at 0x0. 2 Torontonians, younger guys, doesn't seem like they want to talk though. Can I call them in here, is that acceptable behavior? Never done that before. Hehe.
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
I PM'd you but yeah, I'm Knox 0x0 on X-Note 12 right now. Sorry about that, wasn't home.
kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
That link notes that installing a custom recovery will trip knox. Could you please verify what you did to install custom recovery and still maintain knox 0x0? Will be very interested in your follow-up.
kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !
bingbinghaha said:
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !
Click to expand...
Click to collapse
Actually, I would be interested too. Any chance of posting the procedue instead of PM to multiple users? If not, please PM me as well
I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.
kiru said:
I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.
Click to expand...
Click to collapse
Second that.
---------- Post added at 12:55 AM ---------- Previous post was at 12:38 AM ----------
Okay here. https://www.youtube.com/watch?v=Tks73wZH3qg&list=UU2FLZg9YNAr4YAd0VEDDKGQ
You have to pause to see it at the beginning, and in hindsight, I probably have should of started in CWM, then booted into recovery, but whatever.
Set it to HD and pause it at the beginning, you can see my Knox 0x0. Then watch the video and I boot into the ROM, then back into CWM, all in one cut.
Cheers.
Same here
Knox 0x0 here, after a few good reasons to trip it
Android newcomer here.
I have a Bell Canada SM-N900W8, and it came with 4.3. Rooted 4.3 with Kingo (noob style) and that was just perfect to start out. Then the OTA came out. I unrooted the device, reseted with Kies 3 update to 4.4.2 and then Kingo wasn't working anymore of course.
At that point I decided I didn't care about tripping knox and installed TWRP to start trying roms... Tried like 2-3 1+gb complete packed roms (bootloops, probably cauz im a noob) then I wiped from TWRP, restored my OTA backup, flashed with CF-Auto-Root international version (canadian is another bootloop) and then flashed a CivZ kernel +stock-modification rom that I now simply keep clean with Titanium Backup and some apps y'all know about.
Some more info :
My version is VLUCNB7
My current kernel [email protected]
My current SE state is Permissive
Again, Knox is 0x0. Even after bootloops of custom crap that was crashing and I'm custom-rom, custom-kernel.
Two facts to finish that off
1) That's weird
2) I'm a lucky *****
Have a great day
What if I want to use a custom 4.3 ROM (just to get BT Tethering) without tripping KNOX?
The guides seems to push you to install the 4.4 ROMs.
I have the Bell version of N900W8.
Started at MI5, rooted de la vega, then wanted to upgrade to 4.4.2.
Used polishpats way of upgrading with the leaked 4.4.2, flashed all the AP,CSC,CP,PIT, then installed TWRP and autorooted, both with Odin 3.09 - no knox trip
Wanted to try X-note, installed it using TWRP, and no knox trip
Upgraded the kernel using TWRP, no knox trip
Did not like X-note, wanted to go back to 4.4.2, and reflashed it - no knox trip
Downgraded back to 4.3, no knox trip
upgraded to offical 4.4.2, no knox trip
rooted via chainfire and odin - no knox trip
now sitting at rooted 4.4.2 with 0x0 still
Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.
klau1 said:
Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.
Click to expand...
Click to collapse
Hello,
My friend has just the same phone as me, he bought it a few weeks before me, and he used his own techniques and got 0x1 knox tripped, so I just can't warn you enough : not all N900W8 are "untrippable"
...but...I didn't trip mine and I'm not alone.
Without more information you can't just say canadian w8's are untrippable, cauz they are.
Well, are older the better?
I got mine the first week it came out.
klau1 said:
Well, are older the better?
I got mine the first week it came out.
Click to expand...
Click to collapse
I doubt it.
Will look into this. I am positive all N900W8's are the same.
Surely your friend missed something or did something improperly to trip Knox.
Taking this all in. Thanks for the posts guys!
@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?
klau1 said:
@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?
Click to expand...
Click to collapse
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.
nexxusty said:
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.
Click to expand...
Click to collapse
Flashed CF-Auto-Root, flashed TWRP 2.6.3.0, 0x0 still!
Now for the info on my phone.
I have done as follows.
Phone came with 4.3 stock --> Root De La Vega --> Flashed 4.4.2 Stock (Rogers) with Odin 3.09 --> CF Auto-Root --> TWRP 2.6.3.0 = Rooted 4.4.2 with TWRP 2.6.3.0 Recovery and Knox @ 0x0.
I'm not stopping here. Will flash everything DrawntoLife has.
Appreciated my man. Thanks again! Easy to Follow Step By Step Tutorial **WILL** be written tonight after I am done at a LAN I am already late for figuring this out.
Talk soon everyone! Happy flashing!
did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.
klau1 said:
did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.
Click to expand...
Click to collapse
When I updated to 4.4.2? I did, but I was not sure if that would trip Knox so I left it in the package.
It's irrelevant now anyway, the bootloader in 4.4.2 Rogers is the one I am on now and allowing me to do all this still.
I suggest you update to it. Use the package labeled "N900W8VLUCNB7_N900W8OYACNB7_RWC". That is 4.4.2 for a Rogers Note 3.
I can safely assume you can flash this at any point and be fine. Even if you are already on a hacked 4.4.2 or something. There would be no issue updating the bootloader to the same version, would just overwrite it.
Hi,
I am using samsung galaxy S5 SM-G900R7, i am able to root this phone then started trying flashing of custom boot.img contating custom zImage. ODIN is showing successful flashing , but when i am restarting its always going in download mode with error message "couldn't do normal boot" . In download mode there is a line "QUALOCM SECUREBOOT : ENABLE". I doubt this is beacuse of locked bootloader.
I want to know is it really beacuse of locked bootloader?
I downloaded kernel for my phone model from samsung official website mentioned below and built in same way they have given instruction, so i ahve less doubt on custom zImage.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
if yes then i have second question is it unlockable or not, i am not getting any unlocking method for samsung galaxy S5. whatever info i am getting regarding unlocking is upto galaxy S3 but not helpful for galaxy S5. PLease help me to come to a final conclusion on flashing custom zImage to phone.
arvind3023 said:
Hi,
I am using samsung galaxy S5 SM-G900R7, i am able to root this phone then started trying flashing of custom boot.img contating custom zImage. ODIN is showing successful flashing , but when i am restarting its always going in download mode with error message "couldn't do normal boot" . In download mode there is a line "QUALOCM SECUREBOOT : ENABLE". I doubt this is beacuse of locked bootloader.
I want to know is it really beacuse of locked bootloader?
I downloaded kernel for my phone model from samsung official website mentioned below and built in same way they have given instruction, so i ahve less doubt on custom zImage.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
if yes then i have second question is it unlockable or not, i am not getting any unlocking method for samsung galaxy S5. whatever info i am getting regarding unlocking is upto galaxy S3 but not helpful for galaxy S5. PLease help me to come to a final conclusion on flashing custom zImage to phone.
Click to expand...
Click to collapse
As far as I'm aware most Samsung devices if not all have unlocked bootloaders, as for a soloution I haven't seen anything really but some say you need to re-flash stock then try from scrath or make a backup after reflashing stock and a custom recovery then format and restore to get it working.
TechMinerUK said:
As far as I'm aware most Samsung devices if not all have unlocked bootloaders, as for a soloution I haven't seen anything really but some say you need to re-flash stock then try from scrath or make a backup after reflashing stock and a custom recovery then format and restore to get it working.
Click to expand...
Click to collapse
Thanks a lot for your reply,
I searched regarding this and i found latest samsungs are coming with KNOX security in which SECUREBOOT is there, which doesn't allow phone to boot with any boot image if chacksum value doesn't match. so i feel even if bootloader is not locked here but same thng KNOX security is doing. Help me if you have any idea how to disable it in samsung galaxy S5. Getting way how to disable in previous series but not finding method how to do for galaxy S5.
arvind3023 said:
Thanks a lot for your reply,
I searched regarding this and i found latest samsungs are coming with KNOX security in which SECUREBOOT is there, which doesn't allow phone to boot with any boot image if chacksum value doesn't match. so i feel even if bootloader is not locked here but same thng KNOX security is doing. Help me if you have any idea how to disable it in samsung galaxy S5. Getting way how to disable in previous series but not finding method how to do for galaxy S5.
Click to expand...
Click to collapse
Looks like getting rid of KNOX is a difficult task but not impossible: http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
TechMinerUK said:
Looks like getting rid of KNOX is a difficult task but not impossible: http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
Click to expand...
Click to collapse
Thanks for your reply,
I think your post brought me closer to soltution. Tommorw i have to try this. The only problem now i have that i am not getting firmware for my phone model SM-900R7, I am getting firmware for model number SM-900R6 which is very close to this not not exactly for SM-900R7. I have to search more to get it, i hope i will be able to find it.
Thanks again for your valuable post.
arvind3023 said:
Thanks for your reply,
I think your post brought me closer to soltution. Tommorw i have to try this. The only problem now i have that i am not getting firmware for my phone model SM-900R7, I am getting firmware for model number SM-900R6 which is very close to this not not exactly for SM-900R7. I have to search more to get it, i hope i will be able to find it.
Thanks again for your valuable post.
Click to expand...
Click to collapse
No problem, good luck with removing KNOX
TechMinerUK said:
No problem, good luck with removing KNOX
Click to expand...
Click to collapse
Hi,
Yesterday night you posted a link, that link was good but still my requirement is different.Yesterday i was not able to go through whole link you provided to me, today i was reading the whole article. its looks like they are trying to save warrany of phone even after flashing custom ROM. They are deleting bootloader contents of flashing ROM, even i will flash custom ROM with deleted bootloader contents, In phone bootloader will remain same with KNOX SECUREBOOT feature. My target is to flash with KNOX disabled bootloader so it will not stop booting with custom zImage.
TechMinerUK said:
No problem, good luck with removing KNOX
Click to expand...
Click to collapse
Actaully that link was removing KNOX from firmware which you are going to flash not from phone if you have already KNOX is there. That is for if your mobile is not having KNOX and you dont want KNOX when you are going to flash with recent updated firmware so you can delete KNOX contents from firmware and can flash.
arvind3023 said:
Actaully that link was removing KNOX from firmware which you are going to flash not from phone if you have already KNOX is there. That is for if your mobile is not having KNOX and you dont want KNOX when you are going to flash with recent updated firmware so you can delete KNOX contents from firmware and can flash.
Click to expand...
Click to collapse
Hmm, it appears it not possible due to it having a locked bootloader/KNOX not being removable
http://forum.xda-developers.com/verizon-galaxy-s5/help/g900r7-problem-t2877527
TechMinerUK said:
Hmm, it appears it not possible due to it having a locked bootloader/KNOX not being removable
http://forum.xda-developers.com/verizon-galaxy-s5/help/g900r7-problem-t2877527
Click to expand...
Click to collapse
Thats my problem is i am not getting concrete answer either some good link or something official from samsung to come to conclusion of NO, searching searching trying this and that with a hope that its possible.
arvind3023 said:
Thats my problem is i am not getting concrete answer either some good link or something official from samsung to come to conclusion of NO, searching searching trying this and that with a hope that its possible.
Click to expand...
Click to collapse
I would pressume their will be some method of doing it and if it's not released yet it will be soon...
I guess it's just best to bide time and wait untill a concrete method has been developed
Hi,my galaxy s6 is on version 5.1.1 with the G920FXXU2BOGG firmware and I want to root it but don't know the right method.I know that there is already a method on how to root galaxy s6 on 5.1.1 but does it support my firmware?because it is made to root the first 5.1.1 firmware or it supports all galaxy s6 5.1.1 firmwares?
hlm19 said:
Hi,my galaxy s6 is on version 5.1.1 with the G920FXXU2BOGG firmware and I want to root it but don't know the right method.I know that there is already a method on how to root galaxy s6 on 5.1.1 but does it support my firmware?because it is made to root the first 5.1.1 firmware or it supports all galaxy s6 5.1.1 firmwares?
Click to expand...
Click to collapse
Only way to get root on 5.1.1 thus far is by flashing TWRP recovery.
If you are an amateur to this sort of thing I would highly suggest not to do that.
It will void your warranty permanently by tripping KNOX which can't be "un-tripped"
May I ask why you think you need/want root?
I want to root my galaxy s6 as I see some good custom roms and want to try them.I've had some android phones before like the galaxy note 4,galaxy note 3,htc one m8 and galaxy nexus and rooted them.Just curious on how to root my gs6 with the XXU2BOGG firmware.Does the 5.1.1 root method supports my firmware?
hlm19 said:
I wan't to root my galaxy s6 as I see some good custom roms and want to try them.I've had some android phones before like the galaxy note 4,galaxy note 3,htc one m8 and galaxy nexus and rooted them.Just curious on how to root my gs6 with the XXU2BOGG firmware.Does the 5.1.1 root method supports my firmware?
Click to expand...
Click to collapse
Okay then, as long as you aware of the risks..
Rooting isn't device dependent, it's just software. It's supported on any firmware as long as you have TWRP installed. It just installs SuperSU for you into the system files.
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
Pretty sure TWRP is supported on all models of S6/Edge, they all share the same hardware as each other.
Just flash it with Odin version 3.10.6.
Grab it here ZeroFLTE represents all S6 models except Sprint model which require their own special one (no idea why)
You then follow the Odin install method, making sure you're using 3.10.6. Otherwise more than likely will not work.
After installation of TWRP and then booting into TWRP you will be faced with the "SuperSU is not installed, would you like to install it?"
.. And done.
Er, actually I think that appears when when you go to restart via TWRP menu
But yeah.. best of luck, don't blame me if your phone explodes into a fire ball that goes nuclear and destroys the world.. Or simply bricks it
Edit: Wait are you talking about the Chainfire root method? If you are you may as well not even consider that if you're planning on custom firmware installs.. TWRP is your best bet because it isn't device/firmware specific like CF. And you need TWRP for firmware installs anyway..
Stevles said:
Okay then, as long as you aware of the risks..
Rooting isn't device dependent, it's just software. It's supported on any firmware as long as you have TWRP installed. It just installs SuperSU for you into the system files.
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
Pretty sure TWRP is supported on all models of S6/Edge, they all share the same hardware as each other.
Just flash it with Odin version 3.10.6.
Grab it here ZeroFLTE represents all S6 models except Sprint model which require their own special one (no idea why)
You then follow the Odin install method, making sure you're using 3.10.6. Otherwise more than likely will not work.
After installation of TWRP and then booting into TWRP you will be faced with the "SuperSU is not installed, would you like to install it?"
.. And done.
Er, actually I think that appears when when you go to restart via TWRP menu
But yeah.. best of luck, don't blame me if your phone explodes into a fire ball that goes nuclear and destroys the world.. Or simply bricks it
Edit: Wait are you talking about the Chainfire root method? If you are you may as well not even consider that if you're planning on custom firmware installs.. TWRP is your best bet because it isn't device/firmware specific like CF. And you need TWRP for firmware installs anyway..
Click to expand...
Click to collapse
Thanks mate!So twrp now supports 5.1.1?
Welcome! TWRP has supported 5.1.1 since the latest version: 2.8.7.1. Change log is in the second post here. Take care and have fun
Stevles said:
Welcome! TWRP has supported 5.1.1 since the latest version: 2.8.7.1. Change log is in the second post here. Take care and have fun
Click to expand...
Click to collapse
Thanks again!But I thought the only way to root the gs6 with 5.1.1 is by using the unikernel something?as 5.1.1 is different than 5.0.2.
hlm19 said:
Thanks again!But I thought the only way to root the gs6 with 5.1.1 is by using the unikernel something?as 5.1.1 is different than 5.0.2.
Click to expand...
Click to collapse
Not sure about that.. Perhaps install unikernal first just to be sure
Okay so go to the last page or two of the TWRP thread and start reading
Stevles said:
Not sure about that.. Perhaps install unikernal first just to be sure
Click to expand...
Click to collapse
Yeah,just checked and have to flash unikernel first and then the twrp via odin.If I root using this twrp method,it supports my 5.1.1 firmware right?Sorry for lots of asking.
hlm19 said:
Yeah,just checked and have to flash unikernel first and then the twrp via odin.If I root using this twrp method,it supports my 5.1.1 firmware right?Sorry for lots of asking.
Click to expand...
Click to collapse
Assuming it doesn't boot loop with unikernel (all reports say it's fine) then yeah you won't have any dramas with root via TWRP.. Like I said it's just software, the boot loop comes from Samsung being slippery Gypsies and modifying their kernels to basically stop people from modifying system partitions. Hence the need for a custom kernel to bypass that crap. You'll be fine
Stevles said:
Assuming it doesn't boot loop with unikernel (all reports say it's fine) then yeah you won't have any dramas with root via TWRP.. Like I said it's just software, the boot loop comes from Samsung being slippery Gypsies and modifying their kernels to basically stop people from modifying system partitions. Hence the need for a custom kernel to bypass that crap. You'll be fine
Click to expand...
Click to collapse
Yeah,and if I need to unroot it,I do just flash the official firmware via odin?
hlm19 said:
Yeah,and if I need to unroot it,I do just flash the official firmware via odin?
Click to expand...
Click to collapse
Sorry for delayed response.. Yes flashing a firmware tar. md5 will reset the system partition back to full stock and replace the recovery, kernel, modem etc.
Just download one corresponding to your device ie.. SM-G92XX where the first X is either a 5 or 0 and the second is the country or region the phone was intended for. I keep the latest firmware for my device and country (not carrier because it has too much bloatware) around at all times to undo any screw ups and start again
Stevles said:
Sorry for delayed response.. Yes flashing a firmware tar. md5 will reset the system partition back to full stock and replace the recovery, kernel, modem etc.
Just download one corresponding to your device ie.. SM-G92XX where the first X is either a 5 or 0 and the second is the country or region the phone was intended for. I keep the latest firmware for my device and country (not carrier because it has too much bloatware) around at all times to undo any screw ups and start again
Click to expand...
Click to collapse
Thanks for the help!Will try it
Try this:
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
roydok said:
Try this:
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Click to expand...
Click to collapse
I think he may have already actually, thanks for your input. It was certainly mentioned earlier but now there's a link which is always nice
What does tripping KNOX do? I like and would like to continue using the Tap & Pay feature from my bank. Is KNOX separate from the secure element the bank uses?
Other than providing a separate environment for work, what else does KNOX provide?
I want to root my S6 but I know nothing about rooting and such. I've tried towelroot, kingroot and pingpong but none of them seem to support my device.
It's model nr SM-G920F and the build number is MMB29K.G20FXXS3DPD3. I'd like to root it without triggering knox if possible, if it's not tell me what not to do as to avoid bricking it.
It's 6.0.1 Marshmallow
Sorry if this noobish of me to ask but I can't find any tuts with which I feel secure rooting, thanks!
eye_lf said:
I want to root my S6 but I know nothing about rooting and such. I've tried towelroot, kingroot and pingpong but none of them seem to support my device.
It's model nr SM-G920F and the build number is MMB29K.G20FXXS3DPD3. I'd like to root it without triggering knox if possible, if it's not tell me what not to do as to avoid bricking it.
It's 6.0.1 Marshmallow
Sorry if this noobish of me to ask but I can't find any tuts with which I feel secure rooting, thanks!
Click to expand...
Click to collapse
You cant root without tripping knox cf auto root is your only choice i believe
xstokerx said:
You cant root without tripping knox cf auto root is your only choice i believe
Click to expand...
Click to collapse
This will still trip knox right? At least that what their website says.
Jhayzt said:
This will still trip knox right? At least that what their website says.
Click to expand...
Click to collapse
Yep
xstokerx said:
You cant root without tripping knox cf auto root is your only choice i believe
Click to expand...
Click to collapse
I think CF auto root also doesn't support my device
eye_lf said:
I think CF auto root also doesn't support my device
Click to expand...
Click to collapse
Yes it does. I rooted it yesterday. But be careful with TWRP,
"recovery is not seandroid enforcing" may appear on boot, and u may experience a bootloop.
Keep a stock official rom in your pc, in case u want to recover. Use Odin
bigkusi said:
Yes it does. I rooted it yesterday. But be careful with TWRP,
"recovery is not seandroid enforcing" may appear on boot, and u may experience a bootloop.
Keep a stock official rom in your pc, in case u want to recover. Use Odin
Click to expand...
Click to collapse
Would you mind adding me on skype, I'm still having trouble understanding this
I am ready to root my device and check out all the custom ROMS/creations that the greats around here have created. BUT - I saw there was a list of incompatible devices, however it is a dead link and I can not see the bad devices when I click the link. Here are my device specs
Code:
model
samsung-sm-n915a
version
6.0.1
kernal
3.10.10-8932341
build
mmb29m.n915aucu2dph5
Am I safe to root? And if yes, can someone point me to a good download of the factory image, just in case I screw the pooch on something? I can't find a good download for that either.
Thanks in advance everyone.
And if it is not listed in any of the jargon above, this is an ATT USA device. Also, here is one of the dead links http://autoroot.chainfire.eu/
Does this method work, or will I brick my device attempting it?
http://trueandroid.com/en/how-to-root-samsung-galaxy-note-edge-sm-n915a-att-without-pc/
King Root doesn't work on 6.0.1. I'm having the same problem
I rooted my n915f few days back wasnt an issue even tho I couldn't find the cf auto root for my build in the list. You should be fine using odin.
SubhanFLX said:
I rooted my n915f few days back wasnt an issue even tho I couldn't find the cf auto root for my build in the list. You should be fine using odin.
Click to expand...
Click to collapse
OP was asking about N915A not F
Don't Attempt Root
Do not try that method. I guarantee it will brick your phone. Bootloader on AT&T version is locked and will not be getting an unlock method ever.
If you already did it and bricked.. look for the Marshmallow OTA files for restore via Odin specific to the AT&T version you have. I bricked my note 4 AT&T attempting root and recovered via Odin and stock firmware files. And i know i did this to a note 4 all att Samsung notes of the same generation have the same locked bootloader ='ing no root ever ?
jo15765 said:
I am ready to root my device and check out all the custom ROMS/creations that the greats around here have created. BUT - I saw there was a list of incompatible devices, however it is a dead link and I can not see the bad devices when I click the link. Here are my device specs
Code:
model
samsung-sm-n915a
version
6.0.1
kernal
3.10.10-8932341
build
mmb29m.n915aucu2dph5
Am I safe to root? And if yes, can someone point me to a good download of the factory image, just in case I screw the pooch on something? I can't find a good download for that either.
Thanks in advance everyone.
And if it is not listed in any of the jargon above, this is an ATT USA device. Also, here is one of the dead links http://autoroot.chainfire.eu/
Does this method work, or will I brick my device attempting it?
http://trueandroid.com/en/how-to-root-samsung-galaxy-note-edge-sm-n915a-att-without-pc/
Click to expand...
Click to collapse