yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] designgears:
Basic Rooting Instructions

Use Universal Root de la Vega to create a custom firmware (See Post #1)

Boot into bootloader mode

Open Odin or Heimdall and plug your USB cable into your computer and phone

Use Odin or Heimdall to flash the firmware created in step #1

Let your device fully boot after flashing has completed

Copy the contents of root_de_la_vega_sdcard.7z to the root of the internal storage

Reboot (very important!)

After fully booting delete the files from the internal storage that were added previously

Reboot (extremely important!)

Question & Answer

"Root de la Vega" What kind of name is that?

It's named after Ralph de la Vega, CEO of AT&T Mobility.

Can I flash custom recovery/kernel without tripping KNOX flags?

No.

Will this set a tripped KNOX flag 0x1 back to 0x0?

No.

Will root survive a factory reset?

Yes, it does.

Do I need to fully wipe my phone when rooting?

Not always, most cases it should be fine, but sometimes you get lots of forces closes, the only way to fix it is to flash your csc and let it wipe.

Can I unroot?

Yes, use SuperSU full unroot option or flash stock.

I am getting Force Closes after flashing, how can I fix it?

Make sure you are flashing the cache(csc) and system(ap) file!
[Galaxy Note 3 Original Android Development] raitospk:
May I know will factory reset trigger Knox 0*1 after the rooting?
[Galaxy Note 3 Original Android Development] robsnat:
[MENTION=2348906]designgears[/MENTION]

It means there is scope for rooting indian version running on exynos
[Galaxy Note 3 Original Android Development] itskapil:
This looks awesome!
[Galaxy Note 3 Original Android Development] gerald410:
Trying now on sprint MI5 wish me luck!
[Galaxy Note 3 Original Android Development] designgears:
No, the Exynos still doesn't have the required hooks.
[Galaxy Note 3 Original Android Development] gerald410:
How long does it take to complete the process? URDLV
[Galaxy Note 3 Original Android Development] designgears:
Shouldn't take more than a couple minutes... however, I was testing everything on an ssd.
[Galaxy Note 3 Original Android Development] gerald410:
I'm on one as well (SSD) Win 8. Doesn't seem to complete using full command. Stays on Hex Editing Image.......

Edit I put it at root of C drive now it's working Thx buddy!

---------- Post added at 01:39 AM ---------- Previous post was at 01:28 AM ----------

I did full and it produced a tar file and no corresponding csc file, don't I need a csc file as well?

Does the single file from the full command go in AP with csc left blank?
[Galaxy Note 3 Original Android Development] mouse100:
[MENTION=2348906]designgears[/MENTION] can I also update my 9005 with MJ3 to newer version without problem with this tool?

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Original Android Development] designgears:
The AP and the CSC are all in the one file it produced. Just drop it into the AP slot.

Just curious, what was the full path of the file when it wasn't working? I am thinking special characters in the parth might mess it up.

This simply creates the files I used to create by hand. That one thing that has changed, I don't take file requests anymore ;)
[Galaxy Note 3 Original Android Development] designgears:
Awesome! Looks like it works.. lol
[Galaxy Note 3 Original Android Development] gerald410:
Not only that i'm official as well, after using wanam exposed! It was always custom when I rooted on MI3 the Ota'ed to Mi5:)

You the man!
[Galaxy Note 3 Original Android Development] designgears:
That's good to hear! I wonder if that other one can be solved that way. Will have to look into it.
[Galaxy Note 3 Original Android Development] gerald410:
I wish you luck Gears thanks again.
[Galaxy Note 3 Original Android Development] rulala:
[MENTION=2348906]designgears[/MENTION]

Can you explain What is necessary hooks?

Because you say exynos doesn't have the required hooks.

BRI :

Build date: Wed, 16 Oct 2013 02:04:35 +0000

Product Code: BRI

PDA: N900ZSUBMJ2

MODEM: N900XXUBMI2

CSC: N900OZSBMJ2

When I upgrade to ZSBMJ2 , Download mode SHOW WARRANTY BIT.

It is Knox WARRANTY . Like 0x1 on N9005.

ZSBMJ2 PDA include a latest "Knox Bootloader" I think..

now exynos version is the same with S800 in download mode(Knox WARRANTY).
[Galaxy Note 3 Original Android Development] delanvital:
Sorry, of course. Many thanks. It worked with the addition of the also somewhere mentioned chmod +x on the .bat-file.

I am new to Samsung products, Odin etc., so had to catch up on some basics. To summarise, if anyone cares, I am on Win7 64 pro and I did as follows:

- Installed Cygwin64

- Started the Cygwin terminal

- cd'ed to proper drive and URDLV folder

- chmod +x URDLV.bat

- ./URDLV.bat full c:/URDLV/blahblah....tar.md5 (drag-n-dropped the path to the file)
[Galaxy Note 3 Original Android Development] jvrey:
Ooops wrong thread, please delete this post.
[Galaxy Note 3 Original Android Development] LIPA:
Change from Luxembourg to France and root at the same time

Hello,

Can someone tell me, today I have: AP XXUBMI7 et CSC LUXBMI3 .......

can I use XXUBMJ3_VEGA and XXBMJ3_CSC because there is no new firmware for Luxembourg (so I want to use VEGA for France)!

Is it a special risk to do that ?

Thanks
[Galaxy Note 3 Original Android Development] ocaldini:
you cannot alter systemui.apk file and its respective framework in order to allsharecast dongle works.
[Galaxy Note 3 Original Android Development] RavenY2K3:
I think if you haven't got the official boot loader from MJ3 you'll be ok. When I originally used one of the first rooted firmwares, my CSC changed to something else, but I managed to get back to what it should be without tripping the counter.

It was the MJ1 variants I was using at the time and It took a couple of flashes and wipes etc, but I managed it. So for you to want to change it,"I think" you should be OK, providing you haven't installed the official MJ3 firmware which includes the boot loader of doom! ;)
[Galaxy Note 3 Original Android Development] zroice:
Got a new vodafone branded Note 3 with MI6 or MI7.

How can I update and debrand to the latest rom version without updating the bootloader?
[Galaxy Note 3 Original Android Development] BlueChris:
Just follow the procedure m8 in OP post but the 1st think you need to do is to see in samfirmware if there is a newer version for your CSC. If not and you want to change CSC and debrand and you say then you risk the knox flag... at least is what i had understood so far with the overall RDLV methods.
[Galaxy Note 3 Original Android Development] zroice:
thanks for your reply, but I am asking about stock update BEFORE applying the root (and without bootloader)?

On my first N3 (which I sold now) I made the mistake to just download rom from sammobile / samfirmware and flash that to debrand, but that also updated the bootloader as I found out later. I want to avoid it this time =)
[Galaxy Note 3 Original Android Development] BlueChris:
Maybe URDLV is better for unbranding? I mean you download from Samfirmware the rom your phone has but the latest, you hexedit that with the method in OP post and the you pass it and after the csc for unbranding?

But I still don't know if your knox will be tripped, several people got that problem, just find the best possible steps for a successful rooting and unbranding.

I wanted today for example to pass the latest UK mj6 but I'm afraid because it's different csc and if I pass after my specific mj3 csc maybe I will trip knox.

Its tricky m8 but I believe a bit patience is the best friend.
[Galaxy Note 3 Original Android Development] zroice:
well the RDLV (and I think the URDLV too?) method has the problem with the risk of tripping knox since you can make errors with selecting the right files - there are several tools out there now which do work without touching odin to root (no flash required) - meaning they are alot safer for the knox warranty flag.

But before using those again, I'd just like to update my system to MJ8 because there are some changes.

I am not sure but I think I read somewhere that you can edit the tar file before flashing and delete the bootloader files so that they wont get flashed, but I need to know how to do this exactly please, and which files to delete.

Anyone?

---

would also be great if someone could explain the differences between the bootloaders (except no rdlv support)? Because even with old bootloader phone is in enforcing mode?
[Galaxy Note 3 Original Android Development] mjcollum:
Using the new vega script should delete the bootloader.

The Se enforcing is kernel related not bootloader and will stay in enforcing mode unless you flash a different kernel which would flip knox.
[Galaxy Note 3 Original Android Development] Luycks:
[MENTION=3160325]zroice[/MENTION] I'm on international (not-branded) SM-N9005, so I'm not sure if my statements below apply using a branded device. Anyhow:

The URDLV method produces an odin flashable tar file, that doesn't contain the newer bootloader. THAT is what you want, so you can still update to MJ8 AND be able to root keeping knox at 0x0.

If you update OTA or flash a stock rom MJ8 you will get the new bootloader. The new bootloader makes this URDLV method useless (doesn't work anymore), if I'm not mistaken it'll even trip your knox counter.
[Galaxy Note 3 Original Android Development] zroice:
thanks man, thats explains it good.

So on my "old" N3 which i just used stock rom from sammobile on, I could debrand with this stock MJ3 rom I still have here. The brandings and CSC are identical on the new one(at least the carrier and country is the same, so im assuming). Can I just use URDLV on this MJ3 rom file to debrand and root at the same time?

This rom did debrand my old note 3 without tripping knox - so its safe to use on the phone im sure (at least the stock one was, without the urdlv treatment)
[Galaxy Note 3 Original Android Development] Luycks:
[MENTION=3160325]zroice[/MENTION]

That's the point, I'm not sure about the debranding.

Let's say you're now on stock firmware (pre MJ3), so for example MJ1.

My route would be:

1. Download the international latest MJ3 for your country

2. Let the VEGA script produce a MJ3_vega (use option 'full')

3. Flash it

This will update your AP and CSC to MJ3. The modem will not

be upgraded.

4. Follow the instructions from post #1 for the sd-card files

part to root.

5. When up-and-running and rooted use Xposed and wanam to

change status custom to 'Samsung Official'

6. Go into download mode and check that status is 'Samsung

official' and 'knox 0x0'.

That's it, you should be on MJ3 now AND using the 'old' bootloader. This makes that you can apply this trick to the next official update again (as long as you download this update from sammobile and throw it through the URDLV script first and flashing the _vega result).

Again: because I'm on the international version of the device I'm not sure if you risk knox 0x1 by flashing the international CSC (debranding). So that's the risk you have to evaluate for yourself. Is it worth for you taking the risk?
[Galaxy Note 3 Original Android Development] zroice:
thanks, I just tried using URDLV on the rom i have here, but somehow it didnt went through. (extracting was finished instantly and hex editing was not doing anything it seems) - but I will get it to run im sure.

Why is the modem also left out in the RDLV? Is it just to make flashing faster or does this also affect knox and that sh*t?

Can I flash modem afterwards or does this mess up knox?
[Galaxy Note 3 Original Android Development] Luycks:
I flashed the modem afterwards (extracted the modem.bin from the downloaded MJ3 stock rom) and knox kept 0x0.

Question: what is your current firmware? I missed that part. If your phone came with MJ3 you already have the new bootloader and then the URDLV route will NOT work!
[Galaxy Note 3 Original Android Development] zroice:
VFUBMI7 - vodafone MI7... my other n3 also had that. I flashed over XXUBMJ3 and everything was cool. Trying to fix that one up with RDLV now.

What did you do with the modem to flash it alone? Put it in its own tar file, just putting the modem.bin in the phone thing in odin, or deleting all but the modem.bin from the stock rom and flashing that?

Final question for tonight ;P - MJ8 is not out for my region, can I still use it somehow?
[Galaxy Note 3 Original Android Development] Luycks:
So you flashed XXUBMJ3 STOCK rom over MI7? Then you're now on the 'new' 'evil' bootloader and rooting with Vegas wil not work...

For the modem: I extracted the modem.bin from the XXUBMJ3 stock rom (downloaded from sammobile) and flashed modem.bin with odin 3.9 in the CP slot AFTER I rooted and rebooted (see post #1).
[Galaxy Note 3 Original Android Development] mrpug:
Need help

Hi,

I'm Kind of new to this whole command prompt thing. and I look through the forum but I'm still somewhat confuse as I keep getting an error that it can't specify the location. I know im suppose to type/drag the full path of the URDLV full and the path of the file i got from sammobile. Can someone help me break down the step by step of what i have to do to create the odin file? I would really appreciate it.

Thank you
[Galaxy Note 3 Original Android Development] zroice:
I did that on my "old" note 3 - I had bought a second and sold the first. (because I messed up with the bootloader update and the screen of the first one had some brightness imperfections)

---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------

Shift+Rightclick the folder that the URDLV files are in and "open in command prompt".

Then type "URDLV full <full_patch_of_tar>".

Need to make sure you include drive and everything in the tar-path. (i first forgot that too and just tried to put the tar in the same directory and use it without path)
[Galaxy Note 3 Original Android Development] Luycks:
Ow okay haha... So the 'new' one is still at MI7, have the 'old' 'good' bootloader, and you will only flash a firmware upgrade thats modded with URDLV. Then you'll be fine... Strange that the URDLV script hangs on hex editing image... I don't know a solution for that. Hope I helped you a few steps... Good luck!

Just saw I missed more: you had a question about why [MENTION=2348906]designgears[/MENTION] left the modem part out of the produced tar. I have that same question too, obviously he identified some risks, but don't know which... Maybe he'll answer...
[Galaxy Note 3 Original Android Development] echaya:
Thanks a lot, buddy. It really helps!
[Galaxy Note 3 Original Android Development] mrpug:
ah thanks the Shift+Rightclick the folder did the trick :D

[/COLOR]

Shift+Rightclick the folder that the URDLV files are in and "open in command prompt".

Then type "URDLV full <full_patch_of_tar>".

Need to make sure you include drive and everything in the tar-path. (i first forgot that too and just tried to put the tar in the same directory and use it without path)[/QUOTE]

---------- Post added at 02:32 AM ---------- Previous post was at 01:59 AM ----------

I would also like to know if I want to do any future updates, would I have to do this again with the updates? will that trigger the knox? and lets say I do an update OTA cause I dont want the root anymore, will that trigger the knox?
[Galaxy Note 3 Original Android Development] ocaldini:
confirm?

Hi guys, I'm on windows 8.1 enterprise 64 bits using ssd.

After many attempts, I think I did it in the right way.

Put the rom.tar.md5 at root c:

Create a RDLV folder at root c:

Opened normal prompt (not the adm prompt, and I'm not the windows admnistrator).

command:

C:\universal_rdlv\URDLV csc c:\I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5

Then it was opened a explore window in "c:\universal_rdlv\output\I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME_CSC.tar.md5 (98mb)

Question, is that the file created in output folder that I have to flash in Odin?

Other question, what is the difference using "csc" or "full" command? Can I use either of them?

Thanks for the one who replies.
[Galaxy Note 3 Original Android Development] mjcollum:
I've been playing it safe and throwing it a full command.

Yes Flash the file from the output folder with odin.
[Galaxy Note 3 Original Android Development] zroice:
grmpf....

somehow the script does not work for me.

===============================================================================

This work is licensed under a Creative Commons
Attribution-NonCommercial-NoDerivs 3.0 United States License.

http://creativecommons.org/licenses/by-nc-nd/3.0/us

===============================================================================
Universal Root de la Vega v0.2 -- By DesignGears
Public Preview
===============================================================================

MODE: full
FILE TYPE: md5
FILENAME: N9005XXUBMJ3_N9005DBTBMJ3_N9005XXUBMJ2_HOME.tar.md5

Extracting Tar...
Hex Editing System Image...
Checking System Image Hook...
System Image Successfully Hooked
Creating Odin Flashable Tar...

/usr/bin/tar: value 4294967295 out of uid_t range 0..2097151
/usr/bin/tar: value 4294967295 out of uid_t range 0..2097151
/usr/bin/tar: Exiting with failure status due to previous errors
ODIN FILE: N9005XXUBMJ3_N9005DBTBMJ3_N9005XXUBMJ2_HOME_VEGA.tar

DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA

D:\Universal-RDLV>

---

One thing I noticed: When I open the N9005XXUBMJ3_N9005DBTBMJ3_N9005XXUBMJ2_HOME.tar.md5 file with 7zip, it does give me a "There is no correct record at the end of the archive"-Error. I've redownloaded the files and unzipping works alright, but the tar gives this errors - but this could be due to the appended md5 data I guess?

But any idea what causes the RDLV error above?
[Galaxy Note 3 Original Android Development] mjcollum:
Install cygwin

Then if you look up a couple post someone quoted what I needed to do on windows 8 anyway.
[Galaxy Note 3 Original Android Development] Luycks:
Again this error occurs on 64 bit systems... Search around page 13 of this forum to find my solution... Hope it helps!
[Galaxy Note 3 Original Android Development] zroice:
ohh didnt see that... thx! works now as it seems - creating the file at the moment.

...

Actually I'm a bit "scared" to flash this file before having the correct stock base on the phone. (i mean can I only flash cache.img and system.img without debranding first and installing the right modem for that firmware etc?)

I think this URDLV assumes you are using the rom version that you have installed on your device right now or? That would mean not really useful to debrand. I will download the unbranded MI7 and flash that, and then upgrade to MJ3 with root de la vega file.
[Galaxy Note 3 Original Android Development] mrpug:
anyone knows if I want to do any future updates, would I have to do this again with the updates? will that trigger the knox? and lets say I do an update OTA cause I dont want the root anymore, will that trigger the knox?

Thanks
[Galaxy Note 3 Original Android Development] ocaldini:
Originally Posted by ocaldini View Post

Hi guys, I'm on windows 8.1 enterprise 64 bits using ssd.

After many attempts, I think I did it in the right way.

Put the rom.tar.md5 at root c:

Create a RDLV folder at root c:

Opened normal prompt (not the adm prompt, and I'm not the windows admnistrator).

command:

C:\universal_rdlv\URDLV csc c:\I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar .md5

Then it was opened a explore window in "c:\universal_rdlv\output\I9505XXUEMJ5_I9505OXAEMJ 5_I9505XXUEMJ5_HOME_CSC.tar.md5 (98mb)

Question, is that the file created in output folder that I have to flash in Odin?

Other question, what is the difference using "csc" or "full" command? Can I use either of them?

Thanks for the one who replies.

Thanks for your reply.

I tried the same thing, now with the "full" command.

Original rom: I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5

full command: I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME_VEGA.tar.md5

csc command:I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME_CSC.tar.md5

So, I know "full" = AP+CSC, and CSC= only CSC.

But...in practice???

What is the difference between them? Doesn't it matter choosing either of them?

Can I flash either the "full" TAR or the "csc" TAR?

In practice, is there any difference?? Why are there those different ways??
[Galaxy Note 3 Original Android Development] goes_like_hell:
:crying: Someone here for de-la-vega to N9002 ? :crying:

goes like hell
[Galaxy Note 3 Original Android Development] akxak:
On my Note 10.1 2014, Wanam was not able to change the status, nevertheless, Allshare Cast Dongle works.
[Galaxy Note 3 Original Android Development] mrjasmin:
I after flashing Odin Faild

Hellp Please :( ?
[Galaxy Note 3 Original Android Development] mdfpido:
This method tripped my KNOX counter. :( I'm on the latest BTU FW.
[Galaxy Note 3 Original Android Development] geek78:
So, with the new bootloader ? :rolleyes:
[Galaxy Note 3 Original Android Development] mrjasmin:
hellp:crying:

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> N9005XXUBMJ3_N9005DBTBMJ3_N9005XXUBMJ2_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> sbl1.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003> aboot.mbn

<ID:0/003> rpm.mbn

<ID:0/003> tz.mbn

<ID:0/003> sdi.mbn

<ID:0/003> NON-HLOS.bin

<ID:0/003> boot.img

<ID:0/003> recovery.img

<ID:0/003> system.img.ext4

<ID:0/003> modem.bin

<ID:0/003> cache.img.ext4

<ID:0/003> hidden.img.ext4

<ID:0/003> FAIL! (Ext4)

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Frimware not boting:(