yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] zroice:
OK here the foolproof/safe (hopefully) method to debrand, update and root while keeping knox 0x0, bootloader old and system updated.

1.) Get the stock unbranded rom with the same version as currently installed rom. (so if you have uk branded phone with MI7 software, get the unbranded UK software with the same version - MI7)

2.) Get the latest stock unbranded rom from your phones country. (same country as the old firmware you downloaded in step 1)

3.) Flash the unbranded stock with the same version as your current rom to set up an "unbranded base". (by choosing the exact same rom version, the risk of tripping knox while debranding should be 0, as long as you dont mix regions or countries etc.)

4.) Use URDLV to create a "full" rooted rom from the LATEST version of the stock rom of your phones country you downloaded earlier.

5.) Flash it.

6.) (optional) extract modem.bin from the tar of the latest rom, and flash it by putting it in the "phone" or "cp" slot in odin.

7.) Load the zip contents on your device.

8) Profit.

---

To update in future:

1.) Get the latest rom available for your phones country.

2.) Make it vega.

3.) Flash

4.) Flash the modem.bin if you want.

------

One big "problem" that came up to my mind with this method of aquiring root that RDLV uses: (creating a "hook" to run stuff with root rights).

Malware developers or evil people in general could simply put a root_de_la_vega.sh on your phone and hope that the phone has the hooks, and then could bypass all security when the phone reboots, without even requiring root itself. (just needs rights to write to the sd..)

[MENTION=2348906]designgears[/MENTION] Is there a way to disable the hook again once the phone is rooted? or does it get deactivated once the root is done? If not, please elaborate a bit on how this could be fixed?

and second question [MENTION=2348906]designgears[/MENTION]: At which userlevel does the root_de_la_vega.sh run? Root or system? Is that script still dependent on what SELinux allows, or could you theoretically do stuff that SELinux would normally not allow? If so, this could maybe be our chance to actually run certain things in full system root (without beeing restricted by SELinux) - at least on reboots. (to edit certain files that are usually protected for example, to deactivate some SELinux functions etc. we need to be able to run "setenforce 0" to disable the enforcing - but root is not allowed to do it inside android)
[Galaxy Note 3 Original Android Development] geek78:
Delete the line in /system/bin/ss-presetup.sh
[Galaxy Note 3 Original Android Development] zroice:
ahh thanks ill have a look into it. Any clue at what rights that file runs? (that would also answer my 2nd question: would we be able to do stuff that selinux normally does not allow with it?)

Is there any point in this at all? I mean is there possibly a way to get selinux permissive or is it just not possible with the stock kernel? (need to get this damn phone to run "setenforce 0" as system user somehow...if that is even enough..)
[Galaxy Note 3 Original Android Development] wocko1:
Would this root method work on the Chinese Galaxy Note 3 Duos SM-9002? I know it also has a Snapdragon CPU. I hope to install Google Play, without upsetting Knox.
[Galaxy Note 3 Original Android Development] BlueChris:
This procedure is great as long that you are one of the 1st N3 owners that don't have MJ3 from original, from Ota, from Kies or after a repair from a service center. If you are on full official mj3 or later you risk high for tripping knox.

Anyone tested URDLV on latest mj6?
[Galaxy Note 3 Original Android Development] zroice:
f*ck YEAAAA!

idk what caused it yet, but it seems I got (nearly) full root now! I mean full in the way, that I can even access the SELinux directories and edit permissions there or files (at least some).

On my other phone where I messed up the bootloader and used kingoroot (because RDLV didnt work) I couldnt do this. Reboot from terminal also works etc. but SELinux is currently still enforcing.

I can even use "setenforce 0" without getting permission denied, but it does not turn of the selinux. What I couldnt do was to execute the following file: /sys/fs/selinux/disable - got permission denied again. But I could make the "policy" file writable - so maybe we can alter policy and keep selinux enforcing but "harmless"?

What I did different and what could possibly cause this change (against my old phone with new bootloader and kingoapp root):

1.) old bootloader still

2.) I changed the su and superuser.apk files in the root_files folder to the latest version (1.65 instead of 1.45)

3.) additional magic that RDLV uses?
[Galaxy Note 3 Original Android Development] RavenY2K3:
Currently downloading it now, will let the thread know unless someone beats me to it.
[Galaxy Note 3 Original Android Development] Luycks:
I will keep following your progress, interesting!
[Galaxy Note 3 Original Android Development] zroice:
How about you guys? Can you "reboot" in terminal? And/or enter the /sys/fs/selinux folder and view files there?

If not and youre rooted with RDLV that would mean that the new Superuser helped.

If you can, then it's the old vs new bootloader that brings the difference.

--

I will try all my root apps and see if there is anything not working - (like the reboot which didnt work before, or browsing /data/data with solid explorer) - because if everything is working then we can really just forget about the selinux I think. (in terms of messing up our modification capabilities)

Just setting everything up... will report back later. (would be cool if you guys would say if you got any of the described permission / root problems or if everything is working? So we can maybe figure out together what causes the problems with selinux permission denied stuff.
[Galaxy Note 3 Original Android Development] bottad:
Worked flawlessly

Hey all,

Worked for me no problem. No data loss or anything and everything is working normally. Only thing changed is custom status.

On Bell Mobility in Canada.

Thanks gears!

Aaron
[Galaxy Note 3 Original Android Development] TheWizzard2203:
I downloaded the RDLV for my european Note 3. According to *#1234# i needed those two files -> AP: N9005XXUBMJ3_VEGA.tar.md5 and CSC: N9005OXXBMJ3_CSC.tar.md5. RDLV works like a charm but what I notice is that the GPS detects false values since then. While I live in the Eastern part of The Netherlands it sometimes tells me that the phone thinks I'm somewhere in India or Iran. I notice this through my weather widget (transparant weather clock), but also through the standard weather widget from Samsung. Does anyone has a clue what could be the cause of this and more important, how can this be fixed?
[Galaxy Note 3 Original Android Development] encho:
Would this still work if I want to rebrand it to generic European version, not the country specific one?

---------- Post added at 11:07 AM ---------- Previous post was at 11:04 AM ----------

Anyone knows is there any changelog from Samsung? What's the real benefit of going from MIx to MJx? Does new bootloader bring anything new, apart from preventing users to root?
[Galaxy Note 3 Original Android Development] RavenY2K3:
Successfully created MJ6.

Not had chance to flash it yet, but my system successfully created a modified firmware from the latest MJ6 version using URDLV, not gonna get chance to flash until I get home from work.
[Galaxy Note 3 Original Android Development] berju:
Thanks, do you think it's possible to update a note to other phone country firmware most recent. For exemple i'm french and last FW is MJ3 can i update to MJ6 ?

Thanks.
[Galaxy Note 3 Original Android Development] zroice:
didnt try new firmware yet and to be honest I wouldnt recommend as you flash csc as well by upgrading and that could trip knox or make the phone unusable - maybe someone else was brave to try and can report.

---

New infos to the "SELinux = enforcing" problem:

Most root apps seem to work. It seems it depends on the app itself - with solid explorer I can now delete system apps without any errors after remounting system (I can also use solid to mount system rw directly, and dont have to use the "trick" to do it through terminal first. But at the same time, I cannot deinstall system apps with Titanium (cannot locate the path it says).

Tried to edit settings.db with sqlite3 editor but that didnt work as well. (this is most likely related to selinux and not a problem with the app since i could still edit many other databases with it, although: I could restore android_id with Titanium, and this android id is set inside this settings db - so Titanium could edit it somehow... really weird because Titanium couldnt deinstall system apps, but now it can edit the settings db?!

I can even edit init.rc and build.prop, default.prop etc. In the "default.prop" there lies all the SELinux crap if you look at it. There SELinux is set to enforcing and some other stuff.

So I edited default.prop and build.prop to turn off selinux - but after reboot the default.prop gets overwritten and the values in the build.prop regarding selinux just get ignored. I guess the kernel uses a default.prop or creates one from its own image to make sure selinux stays enabled. So we would have to find a way to turn that off somehow without reflashing the kernel... if possible at all..

--

What I do not really understand is that I can run "setenforce 0" as root now without problems (thats the command for temporary turning off the enforcing mode) but it does not actually do anything =(

One other thing that might be also an approach to keep knox 0x0 while actually using a custom kernel:

I read about knox and checked the apps etc. and there is this "SysScope" and "TIMA" thing that, as far as I understand handle the "checking" of the device's at runtime to detect alteration. Odin flashing also triggers the integrity check as far as I understand... So maybe there is a way to disable the integrity check at runtime by disabling syscope/tima and then flashing / overwriting the kernel without odin. (like mobileodin?)

Just speculating as I dont know the inners of this stuff and are no actual developer.
[Galaxy Note 3 Original Android Development] ZeAuReLiEn:
I did the update you plan.

Results : WIFI broken, camera broken and battery drain related to the camera issue.

Rolled back in MJ3 fixed the issue for me.

First informations suggests that this issue only happens when using Root de la Vega, I know guys who performed the same upgrade but with CF-ROOT and no problem encountered
[Galaxy Note 3 Original Android Development] alucine:
RavenY2K3, good news with MJ6 rom ?
[Galaxy Note 3 Original Android Development] berju:
Thanks for reply, i read a french forum and the guy done this update. I read more about the problem and comeback to say.
[Galaxy Note 3 Original Android Development] RavenY2K3:
Yep, working and rooted... however! I think it needs the modem that comes with that firmware because I'm unable to turn on Wifi the the modem that comes with MJ3.

---------- Post added at 08:28 PM ---------- Previous post was at 08:17 PM ----------

Update: Flashed the corresponding modem and it still does NOT work. I'm sure I've read somewhere in the past that some modems won't work without the correct boot loader so perhaps this is why.

Maybe someone with more knowledge can support or dismiss this theory though.
[Galaxy Note 3 Original Android Development] ZeAuReLiEn:
I guess you also face camera issue and a battery drain related to the camera.

So far only solution found was for me to revert to MJ3 (I never updated to the radio associated with MJ6)

Take care, I found a guy that briked its Note 3 by reverting back to MJ3 (flashing official MJ1 didn't help either after that). He now has a "unknown baseband" issue and the phone freezes/reboot all the time
[Galaxy Note 3 Original Android Development] RavenY2K3:
Got back to MJ3 no problems, I used the version I made with URDLV as opposed to the official file. Also kept the MJ6 modem, which is working just fine with MJ3. We'll see if it adds any power saving benefits over the previous version.
[Galaxy Note 3 Original Android Development] nex7er:
So those with MJ3 OTA (new bootloader) will never get root without tripping KNOX? Is nobody working on this?

I OTA'd to MJ3 with the new bootloader. :/ NEE version.
[Galaxy Note 3 Original Android Development] antt00:
Does MJ6 comes with a new kernel? Have you tried also flashing the boot.img (kernel) as it should also be removed when creating urdlv
[Galaxy Note 3 Original Android Development] Jack Barrett:
Flashed MJ6 hexed over MJ6. No baseband/wifi problems, however my KNOX now is 0x1.

Cheers
[Galaxy Note 3 Original Android Development] engas:
Korean variant N900S MJ5 (SKT) also tripped to 0x1...
[Galaxy Note 3 Original Android Development] teknowiz23:
every time i attempt to dial *#1234# i get the message "USSD code running", and then "unable to process request". anyone else run into this? know a fix or workaround for identifying ap/csc?
[Galaxy Note 3 Original Android Development] BlueChris:
Type the *#1234# to the default dialer m8
[Galaxy Note 3 Original Android Development] teknowiz23:
this is my screen as i attempt to enter *#1234# into the default dialer. and it doesn't do it automatically after # like it did on my att note 3 sm-n900a. with sm-900t that i am using now.. i have to hit the call button to even get these messages.
[Galaxy Note 3 Original Android Development] ocaldini:
Are you sure your KNOX was 0x0 on original MJ6?

Did you use root de la vega before MJ6? You know have to unroot before flashing another original/new rom, otherwise knox 0x1 for sure!

---------- Post added at 03:47 AM ---------- Previous post was at 03:43 AM ----------

Man, TB you fix with TB fixer, it is on playstore!

---------- Post added at 03:55 AM ---------- Previous post was at 03:47 AM ----------

May you please tell me the DIFFERENCE between "csc" or "full" in practice?? Why those two options?? Can I choose either?

I've made I9505 ZTO MJ6 succesfully, both csc and full files.
[Galaxy Note 3 Original Android Development] BlueChris:
I'm with mj3 and mj4 modem (from mj6) and I was fine but I noticed that I cannot record video only photos, anyone things is modem related? And if I roll back to mj2 I risk anything knox related?
[Galaxy Note 3 Original Android Development] alucine:
Is possible to downgrade MJ6 to MJ3 without odin problems ?
[Galaxy Note 3 Original Android Development] RavenY2K3:
I did, but I stayed well away from the official files. I downgraded using the MJ3 I created using URDLV.
[Galaxy Note 3 Original Android Development] ZeAuReLiEn:
An advise, if you don't have a good reason (something broken after reverting from MJ6 to MJ3) to rollback the modem (if you updated it to MJ4) don't perform the modem rollback operation.
[Galaxy Note 3 Original Android Development] Jack Barrett:
MJ3 --> root with kingo app --> update to official MJ6 --> lost root --> flashed hexed MJ6 --> 0x1
[Galaxy Note 3 Original Android Development] geek78:
What are the problems with the modem downgrade?
[Galaxy Note 3 Original Android Development] geek78:
Maybe we need to flash modem and boot from mj6 also. But I don't know if flashing stock boot from mj6 won't trigger knox flag... And if we flash boot from mj6 it will be difficult to downgrade.
[Galaxy Note 3 Original Android Development] BlueChris:
I agree with the problems...

I have N9005XXUBMJ3 in my phone and i took the Mj4 modem (N9005XXUDMJ4) which is in the MJ6 UK and passed it to phone . All was fine until i noticed that the camera wasnt able to record videos.. was able to take photos fine though... Ok i said no worries i will roll back modem and i tried... BUT no matter what modem i tried (mj1 or mj2 basically) it didnt passed to the phone ... and phone was booting in a crazy situation without radios etc and crashing... i passed again the mj6 modem and is working now with the flaw of not been able to record video. I will leave like this till the MJ6 firmware appears here for greece and i will try to hex it and pass it... if the problem still continues i dont know what i can do... maybe an emergency restore to MJ3 from Kies will solve the problem but im not really sure now if this will trip my knox or something..

M8 you are as me now but i have troubles in only one thing if you read above... can you check if you are able to record video?
[Galaxy Note 3 Original Android Development] Chalao:
Confirmed working!

I just upgraded from J1 to J3 (see pics below) and can confirm that everything works as intended. I never took the OTA/Kies update to J3 but downloaded it from Sammobile as explained by OP in #1.

J1 was already rooted with previous version of RDLV but root was lost after the upgrade. I flashed the full URDLV-file (in my case N9005XXUBMJ3_N9005ATOBMJ3_N9005XXUBMJ2_HOME_VEGA.tar.md5) in the Odin AP-slot. Actually I am still on the J1 modem as I don´t care at this moment given that there don´t seem to be any major differences compared to J2 and some guys seem to have quite some problems with modem upgrades).

Anyways, I didn´t do a factory reset at any time (no FCs so far), survival mode in SuperSU was on, you need to update Xposed framework as app_processes aren´t active and also grant SU access again to root apps such as Wanam, Titanium etc.

So my data were'nt wiped (as I didn't change the CSC), frozen apps with Titanium remained as well as the region unlock did, I got official system status thanks to Wanam and:

==> Knox still 0x0 :victory:

Before:

After:

PS: Regarding future firmware updates, get them on Sammobile (don't OTA them) and proceed as explained in #1 and #2 in this thread. At least you cannot accidentally update firmware via Kies as it is not supported anymore once you did URDLV :p
[Galaxy Note 3 Original Android Development] RavenY2K3:
Yeah, looks like I've got the same issue. I'm gonna see if I get any grief downgrading the modern later, if that fails... well I'll cross that bridge if it comes to it.
[Galaxy Note 3 Original Android Development] BlueChris:
Guys can someone with MJ6 upload somewhere the camera app of MJ6 please? its the

com.sec.android.app.camera the file name..

i just wanna test if the problem will disapear and the reason that video capturing that doesnt work in myne is something that has to do of an update in camera app from mj3 to mj6 that is related to mj4 modem...

thx

P.S. I can receive also titanium backup file of camera apk :)
[Galaxy Note 3 Original Android Development] RavenY2K3:
BINGO!

Flash your HEXED MJ6 file, the MJ6 modem and NON-HLOS.mbn

Just stay away from flashing any full firmware files. I tried downgrading everything and just got into a world of reboots, I flashed all sorts except aboot.mbn.

Just to confirm, I am rooted and Knox counter is in tact ;)
[Galaxy Note 3 Original Android Development] geek78:
I was on MJ3 rooted by URDLV and with knox trigger at 0 (old bootloader). I have just flashed stock Modem and stock boot from MJ3 and knox trigger is still at 0. So for me this is the good way to follow with MJ6. As soon as I will have mj6 downloaded I will try. Maybe this night..
[Galaxy Note 3 Original Android Development] BlueChris:
Im confused a bit ... atm my country specific is this

PDA: N9005XXUBMJ3

CSC: N9005OXXBMJ3

MODEM: N9005XXUBMJ2

I am Hexed with the above and i just changed the modem and i got

PDA: N9005XXUBMJ3

CSC: N9005OXXBMJ3

MODEM: N9005XXUDMJ4

The modem gave me the trouble with the camera... so i think i cannot full update to MJ6 fully because its different CSC... am i wrong? thats why im thinking to w8 for MJ6 for my region... if i understood something wrong pls tell me
[Galaxy Note 3 Original Android Development] RavenY2K3:
In the official firmware tar, you will see a file called NON-HLOS.mbn, you need to flash this and the modem as well. This will fix the camera being broke.
[Galaxy Note 3 Original Android Development] nex7er:
Alright, so I jumped in knowing full well that I would get 0x1 with MJ3 OTA that I installed, but I'm still 0x0! Thing is though, there is no superuser app? I downloaded SuperSu from the playstore and it said there was no SU binary. About Device does have the new MJ3 version, though (was: NEE, now: XXU).
[Galaxy Note 3 Original Android Development] BlueChris:
Aha now I got you m8 thx, This mbn file I flash it in AP slot?
[Galaxy Note 3 Original Android Development] RavenY2K3:
Now I've got a bit more time to update, I'll let you know what happened and what I did to fix it.

I went from hexed MJ3 to hexed MJ6. When doing this, the WiFi and video recording was unusable. Flashing the corresponding modem got the WiFi working but recording still wouldn't work. I tried to downgrade, which I did successfully but, got reboot after reboot despite wiping etc.

So back up to MJ6 I went, I then decided to flash everything in the MJ6 official file EXCEPT aboot.mbn, and NON-HLOS still didn't work.

Then I flashed the latter and everything was back to normal again.

Rooted and Knox counter still in tact at 0x0.

Now the key thing here is, that I still have the boot loader from MJ1, and ONLY flashed URDLV created firmware. Everyone who jumped the gun, found it not working and flashed the official firmware, shot themselves in the foot.

To summarise, it looks like you can't go back from MJ6, but as long as you flash the URDLV created firmware, then flash NON-HLOS.mbn and modem.mbn, you will be rooted, maintain your boot loader and Knox counter and have camera, Wi-Fi etc fully functional.
[Galaxy Note 3 Original Android Development] nex7er:
How do you get the SU binary installed? It flashes just fine, but superuser will not install. I placed the two files in the root sdcard folder (like it says in the OP), then I reboot, wait a bit, remove the files, reboot again and nothing. No root. :(

EDIT ADD: Apparently, CSC command did not take. URDLV just past by extremely quickly (no errors however), but with the full command it took a while. And voila. Will report 0x0 or 0x1. Stock MJ3 OTA. 99% sure I'll get 0x1
[Galaxy Note 3 Original Android Development] BlueChris:
M8 it worked thx you are a life savior thx.
[Galaxy Note 3 Original Android Development] LouisChow:
I'm the dummy for rooting, I'm just use the Kies to upgrade to MJ8, If I use the URDLV to create a ROM and flrash it again using Odin, is that mean I can get root. Does anyone success with MJ8 version ?

Country: Hong Kong

Product Code: TGY

PDA: N9005ZHUDMJ8

CSC: N9005ZZHDMJ8

MODEM: N9005ZHUDMJ4
[Galaxy Note 3 Original Android Development] poyin:
That's what i want to know too. Hope that somebody could help us.

And I got some errors using the universal root on creating the files from stock rom...
[Galaxy Note 3 Original Android Development] BlueChris:
What errors? Can you paste some info here? If you get a file 11kb after the process is finished then roll back some pages and you will find what you need to do, you need to use cigwin
[Galaxy Note 3 Original Android Development] geek78:
Good news : I am on MJ6 rooted by URDLV and all is working : wifi, camera, reboot .. and Knox at 0 and status at Official with wanam xposed !

I was on MJ3 rooted by URDLV (so i have still the old bootoader) and I made a tar with :

- system hex edited by URDLV

- boot, modem, cache, Hidden and NON-HLOS from stock MJ6

Last point : I have a XEF unit and XEF is part of the stock CSC ;)
[Galaxy Note 3 Original Android Development] berju:
Hello, good news. Could you explain a bit more ?

I just have my note 3 and it's on MI7 branded orange, i would like remove orange to have stock rom.

I've read i have to first install same FW but not branded, if i install MI7 without orange knox and official are steal there ?

After what's the way ? Install MI7 URDLV, after MJ3 URDLV and finally MJ6 ?

Thanks
[Galaxy Note 3 Original Android Development] RavenY2K3:
Providing you use URDLV firmware, you can miss out MJ3 all together, just make sure you flash NON-HLOS.mbn and modem for MJ6.
[Galaxy Note 3 Original Android Development] berju:
I flash MJ6 URDLV directly on my branded MI7 orange FW ?