yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] cook:
As stated by previous comment (that included reference to EU directive so why not read it? here is the link http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31999L0044:fr:HTML sorry in french but easy to find in anther language) refusing waranty in Europe only because Knox is 1 is perfectly NOT legal.

Refuse waranty need to prove you are the source of the the damage. So claim for repair for hardware issue like button dead and obviously have nothing to do with software cannot be refused.

You can modify your device all the way you want and the waranty still apply until your modification are the source of the trouble and this apply from everything from phone to your home including your car.

Example your car. You can change the paint colour and the sound system and still be able to claim waranty on engine problem but not, obviously, if your paint cause rust or if your sound system cause a short-circuit.

We don't care about the "no everything" policy of the seller. If a seller want sell in Europe he must comply to european rules. Jurist have a sentence to qualify these kind of policies "reputed not writen" means seller can write it, if he want, it's not forbidden to write that kind of false things as long as at the end the magic sentence is there "in any case your legal right apply depending of your residence country" but have no legal effect.

More, for french (I'm french) you are covered by law 1641 to 1648 from civil code. You are more covered by that than any commercial waranty (1st reason is there is no time limit). Link is here : http://www.legifrance.gouv.fr/affic...Texte=LEGITEXT000006070721&dateTexte=20140420

Usually in France just write "1641" in a letter to a customer service is enough to solve problems. Only one time (was a car manufacturer for a 5 year old car) customer service refuse. I go to justice. I win. (no time limit, the 2 years delay start not when you buy but when the failure appears, you have maximum 2 years to claim for waranty eventually in justice after you discover the failure.)

So please don't fool consumers about their legal right because it's like you say in your country.

Original post clearly says EU.
[Galaxy Note 3 Original Android Development] paulopais:
I think the same.. they have to prove the software was the cause of the problem.
[Galaxy Note 3 Original Android Development] sauron82:
I'm confused: Are you agreeing with me because you think the same? Because proving software is the cause of the problem is exactly the opposite of my point.

Has there been a court case in the EU about this specific thing? Has someone brought Samsung (or the store) to court for refusing to warrany a device with Knox void status? Electronics warranties are simple: if you modify your device in any way then the warranty is void. Changing your car's paint colour is like changing the case on your phone. Of course that doesn't void the warranty. But if you play around under the hood at all, then the warranty is void. Same with electronics. You can cosmetically modify the device (change what it looks like physically, like a case or a screen protector), but you can't do anything else. Until someone successfully sues over this, I can't/won't believe any different. Electronics warranties have always been like that. When you buy a DVD player it has that sticker that says warranty void if seal is broken. The fact that that sticker seal is broken doesn't necessarily mean that you opened up the DVD player and modified it, but it does mean the warranty is void. It's that simple. Knox just gives them a way to conclusively prove that we modified the device in some way, like that sticker seal on DVD players.

It comes down to this: You modified your device knowing that doing so would void the warranty, and then you complain when they won't honour the warranty. Rooting voids warranty. Period. That's how it's always been. If my phone needs service, I don't expect free service, since I knowingly voided my warranty.

Let's make an easy comparison: Will Apple warranty a jailbroken iPhone? No. Doesn't matter what's broken/not working; if it's jailbroken, no warranty.
[Galaxy Note 3 Original Android Development] paulopais:
Ok .. it's my last Samsung device. Vpn doesn't work .. too slow .. and o can't get root with warranty.
[Galaxy Note 3 Original Android Development] Alfablos:
Then the whole sticker thing is wrong:

I cause the issue, I pay.

You cause the issue, you pay.

No matter what.
[Galaxy Note 3 Original Android Development] hyogman:
rooting note 3 from telcel

I just wanna say that yesterday, after following the tutorial on first post, step-by-step, I got root access... at the cost of triggering knox.
[Galaxy Note 3 Original Android Development] sauron82:
That's how I feel too. I wish I could say, "I only changed the software. But the hardware headphone jack isn't working; that's not my fault." Unfortunately, that's not the way it works. When you buy something, you implicitly agree to the terms of sale. Things like that warranty sticker on DVD players (and lots of other electronics) are part of the terms of sale. How many of us have actually read every word on the little warranty card that comes with a DVD player, sound system or tv? I haven't, but nobody needs to tell me that Panasonic will warranty my tv, as long as I don't modify it for more brightness, deeper blacks and a faster framerate. A warranty is an agreement between manufacturer and buyer: they agree to provide reasonable service (repairing any problems caused by defects in either the design or manufacture, usually limited by a timeframe) on the product that they manufactured, provided you agree not to modify it from the original design (because those are the designs they're working with). That's why Samsung says to update using Kies or OTA and not Odin; telling you to use only fewer (two instead of three) methods streamlines the troubleshooting process for them, and both methods are designed by Samsung (I'm not sure if Odin was designed by them, and even if it was, there are so many more things to you can screw up using Odin than in Kies or OTA). If you want complete coverage for your device, get insurance. I said defects instead of flaws because if every device has that same problem, it's harder to get them to fix it. I give you the iPhone antenna "You're holding it wrong" as an example; that's a flawed design in the first place, not a glitch in the process, which would (should?) be covered under warranty.

Here's a perfect example of software modification affecting hardware: In CM11, which is the rom I choose to use on my phone, NFC is only working on the international N9005 version of the phone; it's not working on other models (I have a Canadian N900W8). Can I now, under warranty (with Knox 0x0 and device status=official), go to the retailer/manufacturer and say that there's a problem with my phone, NFC doesn't work, and I want them to fix it? No I can't. That's why Knox status voids hardware warranty. I know that all I have to do to get NFC working is to go back to a stock-based rom, but that's beside the point. I know that all I have to do put it back to out-of-the-box condition is to flash the original image from sammobile.com, and probably so do most of the techs at the repair centres. But once you modify it in any way, the warranty is void. I might break that sticker with the intention of opening up my DVD player, and even if I open it and just look and don't do anything, or if I change my mind and don't even open it, as long as that sticker's broken the warranty is void. It's not the way I want it, but that's the way it is. Maybe it's different with Developer Edition devices, which are marketed to users like us, I don't know; we don't have those here in Canada unfortunately.
[Galaxy Note 3 Original Android Development] Alfablos:
Ok, here's an example:

I flash a custom kernel and then I overclock my CPU (or GPU), temperature-based security systems don't work (but "that's ok") and the phone shuts down never to power on ever again. Samsung CAN see (the storage component is intact) from I don't know which file that I DID change the clock speed and tell me "I'm sorry buddy, you break, you pay". Samsung has the possibility to differentiate what's on me and what's on It! I shouldn't have to pay for a malfunctioning display just because I flashed a ROM which doesn't reserve half of the available RAM to apps I don't even need (my benefit, over a non-optimized memory handling).
[Galaxy Note 3 Original Android Development] ajster1989:
How about we focus on Root De La Vega and start another another thread titled KNOX Debate. At this put the thread is way of topic.

Sent from another Galaxy... Note 3
[Galaxy Note 3 Original Android Development] Frank Westlake:
Please repeat this and tell us which Android version and whether it was purchased that way or upgraded. This is so that all the information is in one message.

Frank
[Galaxy Note 3 Original Android Development] orlandson:
Great idea!
[Galaxy Note 3 Original Android Development] hyogman:
rooting note 3 from telcel

This is my info, posted in many oportunities and have confirmed by many people here that it would be safe to use URDLV. I bought with that firmware.
[Galaxy Note 3 Original Android Development] CZ Eddie:
Dangit!

Wait, what?

Does your utility root the TMO N5 if it's running 4.4.2, or not?

I'm confused because the first quote & second quote are conflicting, unless I'm just reading it wrong?
[Galaxy Note 3 Original Android Development] toastido:
He means it's still possible to root, but the available methods will trip knox. URDLV will not work, but other methods will (such as CF-Auto-Root).

Sent from my leanKernel 2.4 powered stock 4.4.2 SM-N900T
[Galaxy Note 3 Original Android Development] ajster1989:
I dont see a conflict, No 4.4.2 rom will work, straight to the point.

Sent from another Galaxy... Note 3
[Galaxy Note 3 Original Android Development] CZ Eddie:
Thanks for explaining it, toastido. That helps a lot. :good:
[Galaxy Note 3 Original Android Development] montersgps:
Root without tripping KNOX

May i know after i root this will tripping KNOX for my Note 3 or not?
[Galaxy Note 3 Original Android Development] DrPhant0m:
My assumption is this: (may be lost on those not familiar with VBA)

IF (You have an Exynos-powered Note 3) THEN

---This root method will not work. Qualcomm only.

---EXIT THREAD

END IF

IF ( Your phone is running Kit Kat ) THEN

---You are out of luck with URDLV... try a different root method

EXIT THREAD

ELSEIF ( Your phone is running Jelly Bean ) THEN

---SELECT CASE firmware version

---------CASE MJ4, MJ7, MK1, MK2 or higher 'Newer JB firmware revisions

---------------you can still root (with URDLV), but you will (most likely) trip KNOX!

---------CASE Else 'Earlier/Initial JB firmware revisions

---------------Try using URDLV with relative confidence, but no guarantees.

---END SELECT

ELSE

---If you're not on JB or KK, then you don't have a Note 3

---EXIT THREAD

END IF

***I tried using the [ INDENT ] formatting option, but it put everything into gray boxes... and spaces weren't working either... so I went with dashes instead

In my case (Verizon)... there are no KitKat releases. The latest one is MJ7 (I believe). I rooted my MI9 (initial fw release) successfully with the ORIGINAL (not universal) root de la vega method, with knox = 0x0.

When (if?) Verizon releases a KitKat update... regardless of what the firmware code is... I am 99.9999% sure URDLV will not work. Being that URDLV is readily available... it would be foolish to think that Verizon's software engineers will not patch for it, and then try the RDLV methods to make sure the patch works. That .0001% is just a glimmer of hope that they build the update on 4.4.3 instead of 4.4.2... and they flub something up and leave a loophole... but it will likely take some new or revised method to achieve root if that's the case.
[Galaxy Note 3 Original Android Development] mtbsoft.:
Could someone please confirm one thing for me, *#1234# gives me...

AP: N9005XXUDMJ7

CP: N9005XXUDMJ7

CSC: N9005VAUDMJ2

I presume that the MJ7 (AP and CP) takes precedence over the MJ2 (CSC) and therefore I will trigger knox if I use URDLV, my phone is on 4.3.

Thanks
[Galaxy Note 3 Original Android Development] CZ Eddie:
Hahah, thanks for putting the argument into SQL for for me. Much easier to understand. hahah :) :good:
[Galaxy Note 3 Original Android Development] ajster1989:
They should require this lol

Sent from another Galaxy... Note 3
[Galaxy Note 3 Original Android Development] Frank Westlake:
That does clear it up!

Frank
[Galaxy Note 3 Original Android Development] mtbsoft.:
Reading back through this thread, there seems to be a considerable number of readers who are unsure of the relationship between the AP, CP and CSC version number (myself included). Could someone please either point us to a definition or write one here.

Given my own version numbers (above) I'm inclined to think I can use URDLV but only using the CSC path but would really appreciate someone giving me a definitive explanation.
[Galaxy Note 3 Original Android Development] ajster1989:
When I was on MJ7 I just used Kingo, it was a 10 second root.

Sent from another Galaxy... Note 3
[Galaxy Note 3 Original Android Development] mtbsoft.:
Ah, but there's the rub... were all three of your versions MJ7 - AP, CP and/or CSC?

Given that Kingo appears to have some safeguards before the critical steps, I might try it but the informations about the AP/CP/CSC is still thin on the ground in this thread.

BTW were you on 4.3 and are you still? Your phone isn't a 9005 and your sig. shows it unrooted!?!
[Galaxy Note 3 Original Android Development] BlueChris:
I had mj1 with 1st RDLV method and

1. I downloaded the mj3 EUR from Samfirmware

2. i passed it throw URDLV and gave me a Vega file

3. with odin I passed it to phone.

4. I inserted the Root files of designgears to SD card and reboot

5. I delete the Root files and reboot again

6. I passed the mj2 modem with odin

7. I opened xposed clicked install framework and reboot.

That was it, I haven't lost or wiped anything, my status is official and when I reinstalled xposed all my wanam settings stayed after a reboot.

It worked to me without doing nothing, it was working in mj1 and after update to mj3 the setting stayed. I also have all share cast dongle and this was my main concern that I was delayed the update till I saw some people here successfully going to mj3 and be official and I took the risk and worked fine.
[Galaxy Note 3 Original Android Development] jamice4u:
Okay I was able to get back to official and the update took now my rom and firmware is at N900PVPUBMJ4. Next mission getting official root. I thank the original post because I was starting to lose hope of updating my phone back to official.
[Galaxy Note 3 Original Android Development] mjcollum:
Be careful on sprint mj4. Appears the bootloader changed. You are able to get root on mj4 with knox 0x0. But starting to look like unable to downgrade back to mi5. As there is no mj4 tar. If you mess something up you may have to flash twrp to recover your phone which will flip knox.
[Galaxy Note 3 Original Android Development] power_tennis:
I have the MJ4. Should I not try to root. I'm coming from the Evo forums and this thread is a totally different language for me LOL. I've read all the pages and I'm good at (following explicit) instructions, but I'm afraid I would be in trouble if I got stuck anywhere.
[Galaxy Note 3 Original Android Development] hosamomr:
thanks

Thanks

Excellent work

Steps were applied on my phone n9005 Preview [KNOX 0x0 Root]

& thanks to wanam for official
[Galaxy Note 3 Original Android Development] mjcollum:
If you already have mj4 the worst that will happen would be you could trip knox. If you want to try downgrading to mi5 and doing the knox safe root it may or may not work. It let me once now seems not to want to. If you don't care about knox things get way essier. Worst case would be you'd have to trip knox to get back to mj4. Help is available if you need it.
[Galaxy Note 3 Original Android Development] dadymon53:
Can someone please make a video tutorial using this root method?
[Galaxy Note 3 Original Android Development] cherylbaker:
Except that appears to only work for you.

Sent from my SM-N900P using Xparent Purple Tapatalk 2
[Galaxy Note 3 Original Android Development] mjcollum:
:) I've seen a few success stories. But seems quite a few people are having issues as well.

We'll get this solved eventually.

Wish I could hold one that wasn't working in my hand.

Anybody around austin having issues and want a hand ?
[Galaxy Note 3 Original Android Development] akxak:
Many thanks to the developers, it worked also for my brand new Note 10.1 2014 LTE (SP-605). I needed my Win 7/32 laptop, under Win 7/64, I got the uid_t error with tar already mentioned in this thread.
[Galaxy Note 3 Original Android Development] power_tennis:
OK. Thanks for the info. I'm not too concerned about the Knox. This is gonna be my handset for quite a while!
[Galaxy Note 3 Original Android Development] mjcollum:
Also on sprint at least it seems better to run the vega files on mi5. Do not use the sd card files. Get the ota then run the sd files.
[Galaxy Note 3 Original Android Development] LeoCFZ:
I can't seem to get rid of the prevention information notification! Yes, I have read the Q&A and I have ran the script through the terminal emulator. And, I have froze all of the knox apps in Titanium Backup. And I have tried the knox disable app by Viper Boy. But the notifications still pop up.

Can anyone please help me get rid of the notice?
[Galaxy Note 3 Original Android Development] mjcollum:
Try using wanam xposed.

Under security settings

Disable knox notifications.

See if that does it.
[Galaxy Note 3 Original Android Development] LeoCFZ:
Thanks! The Wanam Xposed was the key that disabled the notifications. :)
[Galaxy Note 3 Original Android Development] BlueChris:
Guys anyone knows a way to make a cwm backup to odin tar file?

I ask this because with this method we dont have CWM or TWRP right? BUT nandroid backup works fine (in my eyes at least) and creates the files that CWM needs. So if i am able to make this files to a .tar.md5 i will be able to have normal backups that they can pass to phone with ODIN.

I dont know if what im thinking is doable or it will trip knox or anything but in my mind its doable.

Can anyone help?
[Galaxy Note 3 Original Android Development] alucine:
Thanks BlueChris for your guide, is very easy to follow.

I have MJ1 root de la vega, with frozen system apps, also uninstall evernote and similiar apps.

If i flash new MJ3, what append with application frozen or uninstall ?

Before to flash MJ3 is better factory reset o not ?

Thanks in advance.
[Galaxy Note 3 Original Android Development] BlueChris:
D know I never did factory reset in this device, I constantly updating :)

As for the frozen apps I think they stay frozen, after all the only time you are unrooted is in the 1st boot where you pass the Vega files
[Galaxy Note 3 Original Android Development] delanvital:
I grabbed the proper file from SamMobile, then tried full and csc, but both return errors. This is the error with CSC (full is similar):

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

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: csc
FILE TYPE: md5
FILENAME: P605XXUBMJ9_P605OXABMJ1_P605XXUBMJ4_HOME.tar.md5

Extracting Tar...
Creating Odin Flashable Tar...

/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: P605XXUBMJ9_P605OXABMJ1_P605XXUBMJ4_HOME_CSC.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

C:\URDLV>

Perhaps someone could give me a clue as to what I am doing wrong?

Edit: I am using this to root the Note 10.1 2014 edition, after reading other posts on XDA, that it works and is Knox 0x0.
[Galaxy Note 3 Original Android Development] Luycks:
It looks like u r using a 64 bits windows system. Search one of my earlier posts in this thread to find out how to deal with that...
[Galaxy Note 3 Original Android Development] ajster1989:
I'm on an N900T. I was all 3 MJ7 and rooted with kingo, Then upgraded with Mobile Odin to keep root and knox.

Thanks for pointing out I need to update my sig! [emoji106]

Sent from another Galaxy... Note 3
[Galaxy Note 3 Original Android Development] DrPhant0m:
I'm on the Verizon Note 3... so, yeah... I don't have a Kit Kat release yet. I rooted with the original Root De La Vega, and I'm still on the original firmware, MI9.

When Verizon does put out a Kit Kat release... will the Mobile Odin method work for me? Will I have to update my firmware and root with another method before taking the KitKat update? I know it's speculation for now, until it actually comes out, and someone is able to try it.

I've wanted to avoid Kingo for the same reason that I'll probably end up using it... no one knows how it works - including Verizon's software engineers. They've surely patched URDLV completely in the 4.4.x release.
[Galaxy Note 3 Original Android Development] msasm09:
Can I safley toot this 4.3 without void warranty nor knox
[Galaxy Note 3 Original Android Development] ajster1989:
Kingo and Vroot install an old (very old) camera application that allows them to gain temp root and install the su files via adb.

Sent from another Galaxy... Note 3
[Galaxy Note 3 Original Android Development] DrPhant0m:
If that's an exhaustive recount of what is done... why is there a big deal made over it, and why hasn't it been patched?
[Galaxy Note 3 Original Android Development] ajster1989:
I think it was in 4.4.2, cause it doesn't work...

Sent from another Galaxy... Note 3