yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] mapl.ph:
Post your *#1234# here. You don't need any video. Try reading the steps again. If your CSC is not on the list. You'll have to make a request and wait.
[Galaxy Note 3 Original Android Development] tsabrakar:
I tried to root again with correct files and I've got a message: Set Warranty Bit : system (in yellow colour)

Is it normal? Phone should reboot.

Edit

Problem solved. This time I've used Odin3 v3.09 from Root_de_la_Vega.zip.

Thank you designegears. Thanks to you my phone is finally rooted.

Officially o2 UK version of SM-N9005 Note3 has been ROOTED. :D

Edit2

Knox Warranty has been void. 0x1

All I did is factory reset and I've put back my sd card
[Galaxy Note 3 Original Android Development] Yungfu:
I rooted my phone using the old root de la vega method, the one without using csc, should i redo it again? Will I run into problems in the future? Its a 9005 open/unbranded phone. Im pretty sure its not the original csc anymore, since its showing oxx. I wasnt able to check the old one but im assuming it should be olb, as im in the Philippines.

I dont have any problems tho and knox is 0x0 still
[Galaxy Note 3 Original Android Development] Andrewtst:
Finally successful update to latest UK firmware - KNOX remain 0x0 (My Note 3 original is Malaysia)

Cautions:

BUT.... after I do Root de la Vega root - KNOX Warranty Void had trigger to 0x1 !!! :confused:

Haizz... Possible Samsung already fixed it under this new firmware???... :eek: or the KNOX really base on country specific? :mad:
[Galaxy Note 3 Original Android Development] medicus07:
What was your approach? Did you unroot your phone and then flash official firmware before update with new root-de-la-vega firmware BMJ3?
[Galaxy Note 3 Original Android Development] Andrewtst:
Here the step I do when updating to UK latest firmware.

I didn't unroot it 1st, but I don't think that is a matter, as after update to UK firmware, the root is gone and I check the KNOX it still remain 0x0

Remove all customization that required root.

Update to UK N9005XXUBMJ3, download from SamMobile. (The root is not there anymore after the updates)

Check KNOX, remain 0x0

Update to Vega AP-N9005XXUBMJ3 + CSC-N9005OXABMJ3 and following the same root procedures.

Check KNOX, trigger to 0x1 already.

I do success root in my local Malaysia firmware N9005XXUBMJ1 previously and the KNOX remain 0x0
[Galaxy Note 3 Original Android Development] spiralz:
shooting in the dark here but could this be that you were flashing an AP / CSC on a different region note 3? as in you were using a firmware from a different region and the note 3 as it wasnt region unlocked then trip the fuse?

just an idea :confused:
[Galaxy Note 3 Original Android Development] Andrewtst:
I am not shooting and didn't blame anyone here.

I just post here for

precautions to anyone plan use different region firmware & root

.

During flashing the different region firmware, the KNOX remain 0x0.

It get trigger to 0x1 only either after vega installation complete or after proceed with root.

After change my Malaysia firmware to UK firmware. KNOX still 0x0

After use Vega + correct CSC and root, KNOX change to 0x1
[Galaxy Note 3 Original Android Development] tsabrakar:
It looks like same happened to me.

But my phone is UK and I applied (AP) N9005XXUBMJ3 and (CSC) N9005OXABMJ3_CSC
[Galaxy Note 3 Original Android Development] Andrewtst:
Then maybe the new N9005XXUBMJ3 bootloader had change and preventing this method already. :eek:
[Galaxy Note 3 Original Android Development] spiralz:
hey sorry :)

i meant that i was making a guess, not saying you are at fault at all or that you are blaming anyone. i meant I was shooting in the dark not you just an idea no offence meant
[Galaxy Note 3 Original Android Development] Andrewtst:
Is ok. :) :good:
[Galaxy Note 3 Original Android Development] htc6500uk:
Maybe the OP should flag this Knox problem very clearly as this whole thread seems to be about getting root without setting Knox to void 0x1

If you find my post useful, a click on the 'thanks' is appreciated.
[Galaxy Note 3 Original Android Development] tsabrakar:
It will be good if someone from UK will root his device.

We made few mistakes on the beginning and this may be the reason why KNOX counter set itself 0x1 after.

Mine was really weird.

I flashed stock.

Reboot

KNOX 0x0

Then AP and CSC

Reboot

KNOX 0x0

Then I copied root files

Reboot

KNOX 0x0

Gained root and deleted "root_de_la_vega.sh" and "root_files" (folder)

Reboot

KNOX 0x0

I did Factory Reset and I've put back my SD card

Reboot

KNOX 0x1

Root still there
[Galaxy Note 3 Original Android Development] Andrewtst:
I didn't factory reset, it is 0x1 after root, that time my SD card still haven't put in yet.
[Galaxy Note 3 Original Android Development] tsabrakar:
It looks like factory reset causes the problem. But we need confirmation.
[Galaxy Note 3 Original Android Development] designgears:
I don't even see anything for N9005XXUBMI5, only N9005XXUBMI7

Get me the full details with the instructions at the top of post #2

I would say you are right. When you go into recovery the files from the CSC are reapplied. Something probably doesn't match up, but still works because of the previously botched upgrade which changed what the phone was expecting. So what you can flash and what firmware it expects are now different.

------------------------

Just a note after [MENTION=4352894]tsabrakar[/MENTION]s KNOX flag trip, DO NOT mix and match AP and CSC, you do so at your own risk!
[Galaxy Note 3 Original Android Development] BlueChris:
Thx m8 I did it with no problem.
[Galaxy Note 3 Original Android Development] spiralz:
I am from uk will try this method later tonight.
[Galaxy Note 3 Original Android Development] BlueChris:
I matched everything to j1 here but now is there a risk if I do factory reset? This what you are saying?
[Galaxy Note 3 Original Android Development] geek78:
all must match your original situation : country and brand
[Galaxy Note 3 Original Android Development] mormegil:
I overwrote my CSC using the first version of Vega root and managed to revert back to where I was initially. Unrooted using SuperSU before doing so. Then re-rooted with correct AP/CSC combo and I still have 0x0. Running XXUBMJ1 AP though. Something has changed in MJ3 perhaps.
[Galaxy Note 3 Original Android Development] Andrewtst:
Agree on this, something had change in MJ3. Previously I mixed with others CSC and not get trigger.

This time I even use match CSC but get trigger.
[Galaxy Note 3 Original Android Development] mapl.ph:
Have you tried to do a factory reset?
[Galaxy Note 3 Original Android Development] mormegil:
Yes. I did a factory reset from recovery after regaining root.
[Galaxy Note 3 Original Android Development] medicus07:
Just an idea...

XXUBMJ3 firmware is just released in UK...

Yet, there is no official firmware update released for non-UK countries (in Germany [DBT] I´m still on XXUBMJ1... so if you have a non-matching CSC and flash XXUBMJ3 AP, then you get the flag 0x1...

In my case I checked my details in dialpad with *#1234# and got AP, CS and CSC... XXUBMJ1 and DBT. Then I used the "old" XXUBMJ1 firmware and not the new one XXUBMJ3 and correct CSC DBT. No problems so far...
[Galaxy Note 3 Original Android Development] mormegil:
Let's just stick to whatever stock version that is released for our regions and be safe I guess.
[Galaxy Note 3 Original Android Development] cherylbaker:
I know you have the mi3 for sprint womder If you are going to do mi 5?

http://swappa.com/listing/ZZV485/view

note 2 for sale
[Galaxy Note 3 Original Android Development] mjcollum:
The problem at the moment is samsung hasn't posted a full mi5 official build.

From my Note 3 using Tapatalk
[Galaxy Note 3 Original Android Development] drreality:
many thanks

:D:D:D

GUYS THE DEVICE IS WORKING

thank you for all of the support and help on hourly bases

I am humbled by the help that I received from the kindest developer in the forum and the best man in here

DESIGNGEARS and DJEMBEY

I have flashed the CSC file FAQs and I am up and running

As I promised, my small contribution to this community

Confirmation number: 17J55808M91710006.

I wish you both all the best
[Galaxy Note 3 Original Android Development] nintendolinky:
if i change the csc be changed by flashing it in Odin and then using the app from the playstore, will this raise the knox flag, it uses root, i just want to debrand the phone and have stock uk updates.
[Galaxy Note 3 Original Android Development] spiralz:
uk device warranty void 0x1

Well i tried it didnt work for me

My device is a uk device

originally on the latest MJ3 AP & CSC

I followed to post instructions to the letter using the exact same AP & CSC as i currently had

all seemed to go fine, however knox flagged after second reboot

I have root but it did not protect from the knox flag.... :crying:

be warned people from UK.

still thanks very much to the OP for his efforts.

just hope my phone doesn't need a return :eek:

a least i can start falshing roms now! :laugh:
[Galaxy Note 3 Original Android Development] RavenY2K3:
Well, I've just been messing around trying to get mine back on the correct csc, it took a couple of reboots, but I didn't use any 3rd party tools to do it.
[Galaxy Note 3 Original Android Development] Yungfu:
How did you do it?
[Galaxy Note 3 Original Android Development] seavers11:
I install the first version come out from the MJ1 firmware with included CSC. Later i see the CSC is not the right i need DBT for Germany. Everything is working flawless for me switched all to german in settings. But when an update is coming is it possible to flash this update with the CSC for Germany?

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Original Android Development] tsabrakar:
I did OTA update when i receive my phone. This may be the problem.

It changed my AP and CSC. Maybe someone who didn't do OTA will be able to root.

But I wouldn't recommend it.
[Galaxy Note 3 Original Android Development] RavenY2K3:
In full:

Mine was originally a BTU device, after flashing one of the first ROMs in testing, it changed to CYO.

I tried, just flashing the correct CSC, which wiped the device (I knew it would do this) fired the phone up but was still coming up with the Cypriot text, I rebooted into recovery and the multi CSC still displayed CYO, I then wiped and rebooted, still the same.

I then turned to the official firmware, flashed and booted into recovery, it still showed CYO, I let it power up to the setup screen, rebooted into recovery did a wipe, let it boot up again and this time the text was in English, I checked recovery and it was back to being BTU.

After that, I reflashed the rootable firmware and CSC. All the files I used, official and the Vega, were of the same version, MJ1.

I've chosen to stay away from the very latest, as others have reported it tripping the counter.

Edit: I must also add, if you were to change it using the CSC changer, it will wipe your device, it's just what happens when you change the CSC regardless of the method.

I chose to do it this way coz, although I don't think it would have tripped the counter... I just didn't want to risk it.
[Galaxy Note 3 Original Android Development] mjcollum:
in regards to sprint. OTA update from mi3 to mi5.

it appears the su binary is still present in the folder.

however root checker shows no root.

supersu shows-

there is no SU binary installed, and superSU cannot install it.This is a problem!

if you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!

all my wanam xposed tweaks are still applied though.(this is probably normal i guess)

system status now shows custom again.

knox still 0x0.

thanks for any insight in advance.
[Galaxy Note 3 Original Android Development] designgears:
Drop the sdcard files in and reboot, bet it will root it.
[Galaxy Note 3 Original Android Development] gerald410:
I'm hoping, if thats the case i'll go for it:)
[Galaxy Note 3 Original Android Development] mjcollum:
you sir are a genius!

i was going to try that but didn't figure it would be that simple.

VICTORY!!

can confirm sprint mi3 vega root

fake status with xposed

get update

drop files on card

reboot

remove files

reboot

ROOT!!!!! knox 0x0 mi5!
[Galaxy Note 3 Original Android Development] designgears:
Awesome sauce! Looked at the OTA zip, it didn't touch the file that handled that :)
[Galaxy Note 3 Original Android Development] gerald410:
Going for it now!:)
[Galaxy Note 3 Original Android Development] mjcollum:
good luck! let us know.

worked great for me but always like outside confirmation.

for everyone else:

I've kept another thread going with progress/testing this on the sprint version.

SPRINT users may want to check out>>>

http://xdaforums.com/showthread.php?p=46529443#post46529443

nothing fancy mostly just the steps i took to get mi5 root with knox 0x0.

and answers some of the questions you'd have to search through this whole thread for.
[Galaxy Note 3 Original Android Development] RippeR37:
I see that i9505 files are up, have any1 tested them here? Does they work without tripping KNOX flag?

Btw. [MENTION=2348906]designgears[/MENTION] nice job! ;)
[Galaxy Note 3 Original Android Development] RavenY2K3:
[MENTION=2348906]designgears[/MENTION]

I have had an hypotheses, this evening I've been pratting (messing for those not in the UK ;) ) around, trying to and successfully getting back to my original CSC.

Now, on the first boot, where you're supposed to copy the files to the root of the SD card, ready to reboot again, it downloaded the latest OTA ready to apply it. What do you reckon the chances are of it applying the OTA, mid way through the root process and still proceeding to do it's thing and actually root, as at that point nothing has been modified, to the OTA's eyes at least?

Please do tell me to shut up and go home if this sounds too ludicrous, the only thing stopping me trying it, was the fact people have had issues with this very latest update from Sammy, triggering this wretched counter.
[Galaxy Note 3 Original Android Development] designgears:
Tested and verified working :)
[Galaxy Note 3 Original Android Development] gerald410:
Knox still intact after downgrading to MI3 rooted used xposed to set official and Ota'ed back to MI5!

only thing left to do is reinstal Vegas and reboot:)

Sprint I haz root! Knox intact MI5 thx guys!
[Galaxy Note 3 Original Android Development] stari4ek:
After flashing original N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5 (from sammobile) got knox 0x1.
[Galaxy Note 3 Original Android Development] RippeR37:
Superb! Currently on my MH8 with BTU CSC (afaik) from OTA updates with 0x0, (still 4.2.2) but as soon as there will be official 4.3 for my CSC i'm updating and i hope u will continue your support for that model :) (s4 international i mean)

Maybe you should start thread there? Where people could ask and tell their opinions and worries about method etc or just post some tips for newbies? ;) I'm so glad someone was able to make that work, i was missing root so badly for couple weeks!
[Galaxy Note 3 Original Android Development] RavenY2K3:
Was your CSC the same as the one in the firmware before you flashed?
[Galaxy Note 3 Original Android Development] stari4ek:
it was a bit complex way of CSC:

TPLBMI1 -> OXABMJ1 (0x0)

OXABMJ1 -> OXABMJ1(vega). Failed to flash. soft-brick (0x0)

soft-brick -> none (same firmware from 1st step but without cache.img/hidden.img. system shows no CSC. (0x0)

none -> OXABMJ1 (same firmware from 1st step). 0x1 =(
[Galaxy Note 3 Original Android Development] RavenY2K3:
Perhaps it needed that initial full boot for it to kick in the CSC, check what I did a couple of posts back. It's damn unfortunate you've triggered the counter though. :(
[Galaxy Note 3 Original Android Development] stari4ek:
don't think so. cause it shows warning in yellow ("Set warranty Bit: cache") when you flash firmware from odin. It shows during cache.img upload which is totally legal, cause it from stock firmware (got from sammobile)

probably it compares smth. from cache installed and cache it's going to flash, and if it doesn't match - it raises flag.

anyway. now I'm free to do with phone what I'd like to do, without thinking about 0x0 =)
[Galaxy Note 3 Original Android Development] audioph1le:
Why? I flashed with this reactivation lock on. Everythink works fine.
[Galaxy Note 3 Original Android Development] RavenY2K3:
What I meant was, it wasn't until I'd fully booted from one of my many reboots (and possibly one of the wipes) into it, before the CSC I actually wanted, was actually applied, i checked the recovery every time I flashed anything.

If you never got that far, maybe when you flashed it , it was still registering the previous CSC.

Only a theory and only going by what I experienced, but alas you are correct, you've gone past the point of no return, so ya can do what the bloody hell ya like now lol.
[Galaxy Note 3 Original Android Development] Luycks:
If I understood correctly the reactivation lock will cause the phone to force you to login with your samsung account after flashing. This is going to be a problem if you didn't flash the right CSC file along, this CAN cause the samsung keyboard to crash. And it'll be difficult to enter your Samsung-account credentials without a keyboard...

I haven't been in this situation, but maybe this suggestion helps for the ones who are stuck: IF you can access the notification bar in that screen maybe you can toggle on bluetooth and connect a bluetooth keyboard to the Note 3? Maybe it helps so you can use that input device to get to the playstore and download an alternate keyboard for the time being...
[Galaxy Note 3 Original Android Development] raitospk:
Can I unroot?

Yes, use SuperSU full unroot option or flash stock.

will this action trip the knox warranty ?
[Galaxy Note 3 Original Android Development] mshagg:
Just wanted to confirm that XSA CSC (unbranded Australian stock) doesnt wipe any content from the phone.

Thanks dev, great to have a safe way to access root :good:
[Galaxy Note 3 Original Android Development] tarantula78:
I flashed and everything is working great but why does gallery tell me "unfortunately gallery has stopped working"every time? i have flashed the correct rom and the correct CSC a number of times and seperately too.
[Galaxy Note 3 Original Android Development] keifer77:
Rooted successfully, Knox at 0x0 (N900W8). Do any apps such as Cerberus trip Knox?
[Galaxy Note 3 Original Android Development] cherylbaker:
Oh and the roms being posted are mi5 but not official so they won't work. . I see..

http://swappa.com/listing/ZZV485/view

note 2 for sale

---------- Post added at 02:49 AM ---------- Previous post was at 02:45 AM ----------

Any chance that if you are on mi5 you can just use the mi3 root files?

http://swappa.com/listing/ZZV485/view

note 2 for sale
[Galaxy Note 3 Original Android Development] cjvail13:
Works Great. Thanks for everything.
[Galaxy Note 3 Original Android Development] mjcollum:
I wouldn't risk it. Follow the known working route and do the downgrade to mi3. Then vega root. Xposed to system status official. Get ota. Drop root files on SD again reboot delete reboot. Viola mi5 root knox 0x0.

From my Note 3 using Tapatalk
[Galaxy Note 3 Original Android Development] sc2ascend:
Edit: I see what you mean about post #2, thank you for pointing it out.
[Galaxy Note 3 Original Android Development] cyphol:
Read post#2 for instruction. > Dial *#1234#
[Galaxy Note 3 Original Android Development] Girn:
I got a software update but it's failing to install. Does this root have something to do with it? My counters at zero and I don't have any recovery installed
[Galaxy Note 3 Original Android Development] wilsons618:
I have the Canadian (Bell) version and just received a notification that an update is available but I haven't downloaded yet. Not sure if I should since I've also rooted using instructions from this thread. :confused:
[Galaxy Note 3 Original Android Development] Girn:
Nothing will happen if you try it, I have a wind phone. It will just say failed.

Try it and lemme know if it works for you
[Galaxy Note 3 Original Android Development] nicholaschum:
I'm not gonna risk installing it. There are reports that Samsung are patching this exploit through the new updates somehow, causing you to get a 0x1 flag if you try to re-root.
[Galaxy Note 3 Original Android Development] wilsons618:
My thoughts exactly. Root is more valuable to me than some minor improvements.

(I'm not too used to these OTA stuff because I've used a custom rom for each of my previous devices lol.)
[Galaxy Note 3 Original Android Development] nicholaschum:
I guess Root is extremely important to me too, because I got rid of that dreaded 480 DPI on this phone, and also made it look more unique.

But some minor bugs like as I heard from a user, his power button SEEMED a bit more responsive, but he will report back.

If this is the last firmware that is KNOX-Free, I'm just going to disable OTA all together.
[Galaxy Note 3 Original Android Development] Girn:
Pmd you
[Galaxy Note 3 Original Android Development] nicholaschum:
Pm'd you back :)
[Galaxy Note 3 Original Android Development] vader9000:
Enviado do meu SM-N9005 utilizando Tapatalk
[Galaxy Note 3 Original Android Development] nicholaschum:
Anyways, Designgears, can we get you to check out the new firmware for N900W8 please, and upload, that is, if you can grab ahold of the firmware:

AP: N900W8VLUBMJ1

CSC: N900W8OYABMJ1

And we need a brave Canadian patriot willing to try rooting using this method on this new firmware, for the Note 3 citizens of the country!
[Galaxy Note 3 Original Android Development] nickzan:
Yes please. If anyone knows if We can retain root or re root after update our would be very much appreciated
[Galaxy Note 3 Original Android Development] Kur0saki:
I downloaded viper4mod, and root says now su binary not installed, you need to root manually, the strange part is that i havent had any update.

I have dropped the files again on the sd card and done the process again, but no change.

ANy ideas?
[Galaxy Note 3 Original Android Development] nicholaschum:
I am not sure, there is a possibility that MJ1 is the original MJ1 that samsung released, which should be the last working reported firmware to be able to be rooted using this method. Once you hit MJ3, you will have a high risk of tripping the counter as reported on pages 108 onwards.

Even though my girlfriend's name starts with a J, I think I don't like the letter J right now, so I might stay where I (haha see what I did there?) work.

Don't take my word on this, but if MJ1 is the last working firmware, then lucky us, but if Samsung took this long to release it, it could be sneaky :/
[Galaxy Note 3 Original Android Development] seavers11:
I flashed the MJ1 and rooted sucessfull. The only problem is I flashed the wrong CSC I need the DBTBMJ1 and flashed the XOOBMJ1 is it dangerous to flash only the right CSC?

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Original Android Development] Bishopandme:
Good news...:cowboy:

B
[Galaxy Note 3 Original Android Development] maxnik1:
My Note 3:

AP: N9005XXUBMJ1

CSC: N9005VVTBMI2

I don't find the CSC in the list. The device was bought in Bulgaria.

Is it possible to use different CSC or do I have to wait main to be added, eventually?
[Galaxy Note 3 Original Android Development] fethi2:
why did you remove exynos mate ?

i was going to flash your root :(

Mod Edit

No need to quote the whole of the first post
[Galaxy Note 3 Original Android Development] RavenY2K3:
Shouldn't be an issue just flashing the CSC alone, I was doing it yesterday evening with no ill affect.
[Galaxy Note 3 Original Android Development] seavers11:
When flash new CSC root is still there ? Get I a fullwipe?

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Original Android Development] RavenY2K3:
If you're already rooted it'll stay rooted, and yes it will wipe your device so back up what you need.