yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] stanzlavos:
Hi

Just to know... anything happening on the exynos front ? :)

When can the SM-N900 users rejoice ? :D
[Galaxy Note 3 Original Android Development] Bagpuss:
From reading the thread, it appears that N9005XXUBMJ3 brings along a new bootloader, which breaks the current RDLV method.

Currently, my Note 3 has:

AP: N9005XXUBMJ2

CP: N9005XXUBMJ2

CSC: N9005OXABMJ1

If I download the N9005XXUBMJ3 and N9005OXABMJ1 from here, then I am assuming that this is the 'safe' way to update and root.

Am I correct? Will this mean that Knox should not be tripped?

Just want to be certain, before I go ahead. Any help would be much appreciated.
[Galaxy Note 3 Original Android Development] GODSPD:
I have to ask again but there seems to be a lot of different methods and firmwares mentioned in this thread and to be honest I have no idea what to do now, can someone kindly answer the following for me:

1) Can I update the firmware after rooting or should it be done before?

2) Once rooted the status will changed to modified, if needed how do I revert it back to official?

3) Which is the latest current firmware that I may use AND does not contain a locked bootloader?

4) MJ3 seems to be the most talked about firmware, should I flash the stock MJ3 via ODIN or can I use the pre rooted and flash that via odin instead?

All I want to do is update to the latest and safest firmware without locking the bootloader, and have my device rooted, can someone please help me with these simple questions???
[Galaxy Note 3 Original Android Development] Bagpuss:
1) I think you should update before rooting, from what I can make out. However, you should not use either OTA or stock ODIN firmware for BMJ3.

2) The Xposed framework (available on XDA) and Wanam (in Play Store) are required for this, but Wanam doesn't appear to work on BMJ3 firmware.

3) Certainly, the N9005XXUBMJ3 firmware appears to bring with it a new, locked bootloader.

4) You definitely don't want to flash a stock MJ3, as this will update the bootloader, and a Knox 0x1 will be the result if you try to root.

From what I can make out, the N9005XXUBMJ3 from designgears (available in first post in this thread) has been modified to remove the new bootloader update.

It should therefore be safe to update your device as part of the rooting process with this firmware. You just need to make sure that your AP and CSC match.

e.g. if you are currently on AP: N9005XXUBMJ2 and CSC: N9005OXABMJ1, it's okay to flash AP: N9005XXUBMJ3 but you must match that with the correct CSC.

In my case, it appears that the CSC changes when updating to N9005XXUBMJ3, so rather than use a CSC of N9005OXABMJ1, I need to use N9005OXABMJ3.

I suspect the same might be the case for you, so be careful with this.

I'm going to give this a try on my unbranded UK N9005 in the next few minutes. I'll report back when I'm done.
[Galaxy Note 3 Original Android Development] programatix:
Just to be certain, you placed the root files in the Internal SD, not the External SD, right?
[Galaxy Note 3 Original Android Development] michael1982t:
Support for the Chinese version SM-N9006 ?

Which one of you fine gentlemen in here can help me out? Perhaps the fine developers of this root tool can help?

Does this method work for SM-N9006? If so what will it take to make a solution for us with this phone? Willing to donate.

Got the Chinese version SM-N9006:

BASEBAND: N9006ZCUBMI3

BUILD: JSS15J.N9006ZCUBMJ3

Dear developer, imagine if you can get us a solution, you would be supercool.

ALOT of people in China have this version of the phone.
[Galaxy Note 3 Original Android Development] Bagpuss:
I've just successfully upgraded and rooted by using AP: N9005XXUBMJ3 (from 1st post in this thread) and CSC: N9005OXABMJ3 (also from this thread).

Just checked Knox flag, and it's all good (0x0).

Interestingly, my Note has not shown the padlock on the boot screen to show that I'm rooted. Is that normal?

I've rebooted 5 or 6 times, and still not sign.

What steps should I take next?

The update did not reset or lose any of my data, but I've read that I should perhaps do a factory reset now? Is that sensible?

I'm not seeing any force closes, so am thinking I should be okay.

I was considering doing the following:

1) Installed Xposed and Wanam to mark firmware as stock (not sure if this works on BMJ3).

2) Install Titanium Backup and freeze various apps for updates etc. (any tips on which ones to freeze?)

Anything else I should consider?

Are future OTAs now likely to be safe? I'm thinking not, and that I should rely on newer, patched firmwares from here.
[Galaxy Note 3 Original Android Development] ibis69:
Hi, for information i'm still knox 0x0 and samsung device status official after doing this :

* Initial rom (french, operator branded)

AP: N9005XXUBMI7

CP: N9005XXUBMI6

CSC: N9005BOGBMI3

* First Upgrade with 0din 3.04 to AP N9005XXUBMJ3 with a [MENTION=4398524]DjeMBeY[/MENTION] rom ( http://xdaforums.com/showpost.php?p=46434032&postcount=326) (not available anymore)

Result after upgrade

AP : N9005XXUBMJ3

CP: N9005XXUBMJ2

CSC : N9005OXABMJ1

no wipe

Knox 0x0

root working

device status unnoficial

installed Wanam Xposed to make device status official

Then today

Applied only CSC N9005OXXBMJ3 from #2 post with odin 3.04

Result after upgrade

AP : N9005XXUBMJ3

CP: N9005XXUBMJ2

CSC : N9005OXXBMJ3

Changing CSC wiped sdcard (this is normal)

Still knox 0x0

Device Status unnoficial

Installed CSC Changer to change my CSC code from BOG ( french operator) to XEF ( generic french)

Rebooted in recovery to apply new csc (xef) --> working

Still knox 0x0

Reinstalled Wanam Xposed to make device status official --> working

So i was able to update CSC and change CSC code with CSC changer without making knox 0x1 with AP BMJ3 already installed
[Galaxy Note 3 Original Android Development] hallydamaster:
If there is no signs og FC you should be fine and factory reset shouldn't be any concern of yours.

Regarding the pad lock I have no idea? Do you mean pattern lock? Just set it again? If you are unsure that you rooted then try root checker in play store.

Did you just upgrade using the Root de la Vega AP and CSC? You didn't upgrade beforehand?
[Galaxy Note 3 Original Android Development] Seraphim401:
Rooting worked,but it tripped the Knox counter.

Whatever at least now I can install cwm,do a nandroid backup and remove all that Samsung crap from MY phone:cool:
[Galaxy Note 3 Original Android Development] mouse100:
I rooted my previous MJ1 with root de la vega, applied wanam to reset system status to official and it worked fine.

Then I bought supersu pro and activated survival mode. I updated to OTA MJ3 and now system status remains custom also with wanam. I posted on wanam thread and Dev said that he won't support this feature on next updates.

So since I don't want to lose ota and warranty, could someone suggest me the best way to return stock without increasing Knox counter please?

- Should I flash MJ3 with odin or MJ1?

- Should I unroot with supersu option and then factory reset?

- Should I re flash official fw with kies 3?

Please help :(

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Original Android Development] magicxp:
Wanam has been updated today :) Version 2.2.0 :D
[Galaxy Note 3 Original Android Development] mouse100:
System status remains custom also with 2.2.0

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Original Android Development] sanac698:
Other AP/CSC

Hi,

My AP is N9005VJUBMI7 and CSC is N9005ZVVBMI7... any chance to you include these files? i previously buy the SuperSU Premium, how i can help your good work again? (sorry for my bad english...)

Thanks
[Galaxy Note 3 Original Android Development] magicxp:
Did you install Xposed Framework and aktivated Wanam?
[Galaxy Note 3 Original Android Development] mouse100:
Yes of course. But I just solved the problem. I tried to clear Syscope data and now system returned to official :D

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Original Android Development] benhouli:
if what u say is true

this is my info now

ap: N9005XXUBMJ1

cp: N9005XXUBMJ1

csc:N9005XXUBMJ1

rooted with de la vega knox 0x0

if i will do the ota to N9005XXUBMJ3 with super su on survivel mode it will not trip the knox ?

and one more question please... where is that option clear Syscope data ?

thanks
[Galaxy Note 3 Original Android Development] mouse100:
Yes but I can't assure you this. For me worked fine.

After survival mode on supersu I updated with ota.

Then you should go on settings -> application manager -> all.

Then you have to locate a system app called Syscope, here tap force close and clear data.

You must have xposed framework with wanam with fake status checked ;)

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Original Android Development] benhouli:
thanks for your answer....

and of course i have xposed framework with wanam

bacuase i already rooted with de la vega and did the ota to MJ1 and fake with wanam xposed....

thanks , i think i will try that later after i will charge my battery , i have just 3% battery now :fingers-crossed:
[Galaxy Note 3 Original Android Development] hidea:
Hey [MENTION=3605033]nicholaschum[/MENTION], what's STOCK RWC? Is that the _VEGA files (along with the CSC files) posted by the OP?

Edit:

Oh wait. I got it, Rogers Wireless Canada.

Did you unroot from MI5, prior to wiping in stock recovery (twice)?
[Galaxy Note 3 Original Android Development] Bagpuss:
I simply meant the open padlock symbol on the initial splash screen when the Note is booting. For some, I believe that this is displayed when the firmware detects a custom software is running.

In any event, I've installed the latest version of the Xposed framework (v21_77db90) and v2.2 of Wanam Xposed. I've set the 'Fake system status' back to 'official' and all seems good. If I run a software update check, it works fine, and reports that there are currently no updates for my software. I believe this would fail, if the 'custom' status was still set.

I've also had to freeze the Knox applicatios, as I was getting prevention warnings.

I seem to remember reading that I could also freeze two other applications, in order to prevent OTA update notifications. I've tried searching for this, but can't seem to find the information. If anyone could give me a pointer, I'd appreciate it.

The other question is whether OTA updates are now safe for me. I don't want to inadvertently update the bootloader. Anyone got any thoughts on this?
[Galaxy Note 3 Original Android Development] dantxx:
Did they find a way to do this root de lá Vega in the galaxy note 3 from Tim Brasil?

AP = n9005vjubmi7

Csc = n9005ztmbmi7
[Galaxy Note 3 Original Android Development] GODSPD:
My current firmware stats are:

AP: N9005XXUBMI7

CP: N9005XXUBMI6

SCS: N9005TPLBMI1 - (T-Mobile Poland )

From what I gathered MJ3 is the latest, but I am fine choosing a older firmware which will keep my bootloader unlocked and allow me to install xposed framework ect... So I understand MJ1/MJ2 is fine?

I am trying to get this done without tripping the knox counter, but if it trips I seriously wont care, my S4 is on 0x1 and couldn't care less lol

in another thread there are pre rooted stock roms, why not just use these instead? Or they trip the knox counter?

Based on my currently mentioned firmware stats what should I download and flash ?
[Galaxy Note 3 Original Android Development] Luycks:
Here's your pointer mate, look at the attachment, you have to freeze the two software-update (in the screenshot they are at the bottom of the page) apps in Titanium and you will not get notified again when OTA updates are available.
[Galaxy Note 3 Original Android Development] Elin28:
Second confirm it works. Download the RWC Rogers file, and just wipe the rom in stock android recovery (never unroot), and flash the RWC stock files (only once, not twice), follow the OP procedures and then root it with MJ1.
[Galaxy Note 3 Original Android Development] jetv1r:
this is my version

AP: N9005XXUBMI7

CP: N9005XXUBMI6

CSC: N9005METBMI2

this from meteor ireland...

i cant find the CSC in your files....

thank you...
[Galaxy Note 3 Original Android Development] hidea:
Let me clarify a few things

1) If I'm on MI5; reboot into stock Samsung Recovery; wipe.

2) Download the appropriate firmware for my phone (since I've got a Telus phone, then I assume I've got to grab the appropriate Telus firmware from SamMobile?). I'm a bit unclear on this step; which version of the firmware do I grab? The originating firmware I'm from (which is MI5) or the firmware I'm upgrading to? (MJ1)

3) Flash the Telus firmware using ODIN.

4) Follow procedure, which includes grabbing the correct CSC and AP files relevant to MJ1

5) ????

6) PROFIT!
[Galaxy Note 3 Original Android Development] designgears:
What is your CSC?
[Galaxy Note 3 Original Android Development] GODSPD:
I wish someone could let us know, i am waiting a few days to root but haven't received any replies to clarify a few steps,

My current firmware stats are:

AP: N9005XXUBMI7

CP: N9005XXUBMI6

SCS: N9005TPLBMI1 - (T-Mobile Poland )

From what I gathered MJ3 is the latest, but I am fine choosing a older firmware which will keep my bootloader unlocked and allow me to install xposed framework ect... So I understand MJ1/MJ2 is fine?

in another thread there are pre rooted stock roms, why not just use these instead? Or they trip the knox counter?

Based on my currently mentioned firmware stats what should I download and flash ?
[Galaxy Note 3 Original Android Development] designgears:
Which steps aren't clear?
[Galaxy Note 3 Original Android Development] GODSPD:
AP: N9005XXUBMI7

CP: N9005XXUBMI6

SCS: N9005TPLBMI1 - (T-Mobile Poland)

If i wish to upgrade prior to rooting which firmware is safe for me to upgrade via Odin? And which wont lock my bootloader or trip knox...?

Once i upgrade i follow the instructions on the first page, that's all clear, but all i want to know is what can i upgrade to now (and from where or which files should i use? The ones on the first page or stock samsung files?

I plan to install xposed framework etc, so which firmware is good for this? And i gather i use the same . Tar file during the root process and update?

Thanks in advance!
[Galaxy Note 3 Original Android Development] Elin28:
Yes, basically you need to grab the official Telus MJ1 firmware... Then grab the MJ1 AP and CSC and follow the procedure.. Not sure if you need to install twice but I did once and work perfectly..

Good luck and my knox is 0x0 after the steps... You should feel happy about it..
[Galaxy Note 3 Original Android Development] jetv1r:
hi designgears do you have any info regarding my CSC
[Galaxy Note 3 Original Android Development] 00_MACKIE_00:
Excellent.... Nice OP!!!

Rooted Sprint Galaxy Note3
[Galaxy Note 3 Original Android Development] tatsu666:
Can't find a CSC file for "N900W8OYABMI5" yet.
[Galaxy Note 3 Original Android Development] dantxx:
Well did someone already find those ones?
[Galaxy Note 3 Original Android Development] di08s:
Root AP:N9005XXUBMJ3 and CSC:N9005OXABMJ3 without problem ..... Knox 0x0

After install Titanium BackUp freeze Knox , because don't use anyway,

Today I check again and the Knox is now tripped 0x1 and kernel is still 0x0, I don't understand what happened .

Don't do nothing just install TB ........

May can by because I freeze the Knox ??
[Galaxy Note 3 Original Android Development] designgears:
Added to the todo list

Pretty sure they are checking system integrity now. You can still root, but they added stuff to void the warranty.
[Galaxy Note 3 Original Android Development] di08s:
I'm stay root and everything is OK just now have Knox 0x1 which I can't do nothing about this. ...

Just wanna warning you guys may freeze the Knox is not good idea...
[Galaxy Note 3 Original Android Development] sharary:
hi,

i can't find my ap and csc version in the list

my phone is N9005 with stock unlocked brazilian

my ap version is : AP_N9005VJUBMJ1

my csc version is : CSC_N9005ZTOBMJ1
[Galaxy Note 3 Original Android Development] designgears:
Added to my todo list
[Galaxy Note 3 Original Android Development] mapl.ph:
I have KNOX frozen by TB for about two weeks now, still at 0x0. Maybe you have Samsung AUTO-UPDATE turned ON? Or you installed something else on your phone.
[Galaxy Note 3 Original Android Development] designgears:
Files are up!

N9005TIMBMI3 - [MENTION=5493520]joe666it[/MENTION]

N900W8UBUBMJ1 - @deivy48

N900W8UWABMI4

N9005VJUBMI7 - [MENTION=1578418]sanac698[/MENTION]

N9005ZVVBMI7

N9006ZCUBMJ3 - [MENTION=3341088]michael1982t[/MENTION]

N9006CHNBMJ3

N9005VJUBMJ1 - [MENTION=3502759]sharary[/MENTION]

N9005ZTOBMJ1

N9005METBMI2 - [MENTION=2746668]jetv1r[/MENTION]
[Galaxy Note 3 Original Android Development] di08s:
After root disable update and install just TB and basic apps from Play store don't do nothing else for thet reason don't have idea what happen. I'm not new on android know what I'm doing. .. But some time how you know s...t happen :) and we can't do nothing about this. .
[Galaxy Note 3 Original Android Development] benhouli:
ok

after i was on

AP :N9005XXUBMJ1

CP : N9005XXUBMJ1

CSC :N9005XXUBMJ1

already rooted with de la vega

i set super su on survivel mode and did the OTA

now i

AP :N9005XXUBMJ3

CP : N9005XXUBMJ2

CSC :N9005XXUBMJ3

knox still on 0x0

i force stop syscope and clear data

and recheck the fake on wanam xposed but still system is custom....

any suggestions?
[Galaxy Note 3 Original Android Development] mouse100:
Have you root explorer or busy box installed?

I don't know why it worked for me but before these steps I was for sure on custom status!

Try also to tap on Update/Install on xposed framework, then reboot, then fake system on wanam and reboot.

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Original Android Development] hussam1988:
Knox frozen 0x0 also
[Galaxy Note 3 Original Android Development] benhouli:
i read your commet on wanam xposed theard

no root explorer or busy box installed

and did try update/install on xposed framework reboot and fake system and reboot

still custom
[Galaxy Note 3 Original Android Development] nickzan:
What happened to the AP and CSC files for?

AP: N900W8VLUBMI5

CSC: N900W8OYABMI5

They were there a few days ago when thesmokingandroid posted a how to root video with these versions yet now they're missing?
[Galaxy Note 3 Original Android Development] mjcollum:
Knew you'd be looking for them so they got removed.

From my Note 3 using Tapatalk
[Galaxy Note 3 Original Android Development] nickzan:
duplicate post - delete
[Galaxy Note 3 Original Android Development] BlueChris:
[MENTION=2974278]mouse100[/MENTION] m8 I'm with mj1 and I want to go to mj3, when you say about syscope which of the 2 files I found with titanium I need to froze?
[Galaxy Note 3 Original Android Development] mouse100:
You have to froze nothing.

You should locate Syscope app in android settings -> app manager -> all.

But it seems that this method not worked for other people. For me yes but I don't know why..

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Original Android Development] designgears:
Strange, CSC is there, but the AP is missing... adding it again.

edit:

[MENTION=5075615]nickzan[/MENTION]

Its back!
[Galaxy Note 3 Original Android Development] BlueChris:
[MENTION=2348906]designgears[/MENTION] m8 sorry for asking if its dumb but atm i am with RDLV and

AP : N9005XXUBMJ1

CP: N9005XXUBMJ1

CSC:N9005OXXBMJ1

to go to

AP:N9005XXUBMJ3

CP:N9005XXUBMJ2

CSC:N9005OXXBMJ3

i put the AP

N9005XXUBMJ3_VEGA.tar.md5

and after the csc

N9005OXXBMJ3_CSC.tar.md5

am i correct?

also i am unable to find a file for the modem but i suppose the AP file will change my modem to MJ2 correctly?

in what point then i clean the cache of this program?
[Galaxy Note 3 Original Android Development] nickzan:
Thanks for adding the AP, unfortunately I still don't see the CSC file. I did a search of *5_CSC and the only thing that appears is the mj5 one
[Galaxy Note 3 Original Android Development] GODSPD:
AP: N9005XXUBMI7

CP: N9005XXUBMI6

SCS: N9005TPLBMI1 - (T-Mobile PL)

PLEASE - I wish to upgrade prior to rooting which firmware is safe for me to upgrade via Odin? And which wont lock my bootloader or trip knox...?
[Galaxy Note 3 Original Android Development] nickzan:
Screenshot below.
[Galaxy Note 3 Original Android Development] Snake-Plissken:
Guys I want to root too. I Ann still concerned and confused with all the comments here. I(guess) don't really care about Knox tripped.

My main concern is to get system status official. To use Samsung video hub and all the streaming features.

I also want to be able to stay on basic Samsung firmware and no custom Rom.

Can I achieve that if I tripped Knox? I mean can I get system status official with Knox tripped?

If Knox is tripped, can you still use the Knox feature (software) on your phone?

Sent from my SM-N9005
[Galaxy Note 3 Original Android Development] Bagpuss:
From what I can see, you are already running the latest firmware that's available for your device.

If you check sammobile.com, then the latest firmware for T-Mobile is:

AP: N9005XXUBMI7

CP: N9005XXUBMI6

SCS: N9005TPLBMI1

This is what you've already got, so I don't think there is any updating to be done for your particular device. If you try and change the firmware away from what you've got, there is a high chance of tripping the Knox flag.

So far, I've only seen mention of new bootloader firmware in the BMJ3 firmwares, so I think you are okay at the moment.

There is an AP and CSC file for your firmware in the first post of the RDLV thread, so I would simply suggest using them, and following the rooting procedure. This should get you root without tripping the knox flag. With regards to the Xposed framework and Wanam, I've only read reports of this not working with BMJ3 firmware. You should be okay with your firmware version. I should say that I'm on N9005XXUBMJ3 firmware, and it's working fine for me, so I don't think it affects everyone.
[Galaxy Note 3 Original Android Development] GODSPD:
Thanks, I will try the T-Mobile firmware in the meantime, I am 99% this method will work, I will report back once I finish :)
[Galaxy Note 3 Original Android Development] Bagpuss:
Now that I've sucessfully rooted, I was wondering about freezing another application on the phone.

There is an 'Auto update security' option, which is described as 'Automatically check for changes to the security policy and download any updates to provide security and service'.

From googling around, it seems that this is related to Knox security policies, so I was wondering if it would be sensible to also freeze the app that does this. I've currently just unset the toggle. What do folks think?

From what I can see the responsible process is called:

Security policy update SPD_v1_1308_5_3

These policy updates seemed to cause issues for S4 owners for a while, prior to the rollout of Knox enabled firmware.
[Galaxy Note 3 Original Android Development] GODSPD:
Root went fine, KNOX is still at 0x0, but wasn't the process supposed to wipe my internal storage? everything is still there...
[Galaxy Note 3 Original Android Development] Bagpuss:
My internal storage wasn't wiped, either. If you suffer a lot of force closes after rooting, then you might need to erase your internal storage, but otherwise, you should be okay.
[Galaxy Note 3 Original Android Development] BlueChris:
Can someone who was succesfull in updating from mj1 to mj3 create a new thread in general with the steps he did? the thread became total confusing really.. i also ask questions and noone answers.. at least with that thread we the rest who had stick in MJ1 will see a succesfull steps and we take or not the risk.

Thx
[Galaxy Note 3 Original Android Development] benhouli:
i did it

my phone was on mj1 already rooted with de la vega and knox 0x0

i checked super su pro to survivel mode option

and did the OTA

now i am mj3

knox stil 0x0 but system is custom and wanam xposed didn't fix it , then i wating for updates from wanam now
[Galaxy Note 3 Original Android Development] mouse100:
I hope he'll fix this on next update. But it seems that he doesn't want to support this feature on next releases..

Galaxy Note 3 | SM-9005 | Tapatalk