yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] anpho:
I just bought my note3 second hand and unfortunately it has the mj4 CSC and mj7 AP so this means that if I root it will trip knox right? and there is no way of rooting without tripping knox right?

The thing I want to ask is if we have some kind of evidence that indeed the warranty is void and SAMSUNG will refuse to repair the phone under warranty. I know in theory it's void but did anyone went to samsung for a repair and SAMSUNG denied to repair it under warranty or is it just a (most probable) guess that they will deny to repair it under warranty if knox is tripped? And also is it true that the service and repair centers that samsung cooperates with don't really care to check about the tripped knox and repair it under warranty nevertheless? and even in some cases reset the counter? Sorry if it's offtopic but I am just trying to sum up all the facts so I can decide if I should root the phone or not. Any clarification about this is most welcome :)
[Galaxy Note 3 Original Android Development] About20ninj45:
Hate to be redundant but...

I was wondering if i could root without tripping knox using this method. Im on AP: PUBMI5 CSC: PTBMI5. Any information is greatly appreciated and yes i have searched all 130 pages :) :)
[Galaxy Note 3 Original Android Development] chrisgriner:
Hey Journyman,

You are correct, I did not do the extraction step. That was not described or detailed in the OP's directions and I guess I never saw GalaxHe's post. I did go back and read his post and that process is significantly different than the OP's directions. More detailed for sure, but some completely new steps as well. Wish I would have know about that before I moved forward, just for trying's sake.

Nevertheless, I did root with the updated firmware, following the directions in the OP and all is well. Promptly installed SafeStrap and trying out JellyBeans Rom.

I upgraded my base phone to MJE with the most recent download from SamMobile. After that, following the directions in the OP worked perfectly. SafeStrap was as easy as installing an APK and KNOX is still all 0x0.

Thanks to all!
[Galaxy Note 3 Original Android Development] BlueChris:
I will get bootloops m8 since I will be in old bootloader with urdlv and 4.4.2 needs it's own bootloader, I don't do it till a dev find a way to bypass this, I don't wanna loose the ability to roll back to 4.3 roms.

Στάλθηκε από το SM-N9005 μου χρησιμοποιώντας Tapatalk
[Galaxy Note 3 Original Android Development] Killberty:
Okay, didnt really understand that ;)

Android user for 4 months, but i learn cuick due to guys like u :b

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] radicalisto:
He means you need to upgrade the BL to try on 4.4.2 and you cannot roll back to 4.3 once upgraded - which renders URDLV useless beyond 4.3.
[Galaxy Note 3 Original Android Development] GaresTaylan:
How do I move the files to the root of the internal storage? I can't move them with root explorer because I need root to mount as r/w. I can't copy them there with mobile go either.
[Galaxy Note 3 Original Android Development] Journyman16:
At the point you need to copy them over, you should be in the phone OS and have it connected to your PC. Use Windows File Manager to open the phone and copy the files in to the internal card.

If you can't see anything but the phone connection in the folders list, unlock the phone and you will see Phone and SDCard as 'folders'

Then reboot the phone, wait for it to be in the OS and then repeat the above to delete the file and the root_files folder. :D

Then reboot once more.
[Galaxy Note 3 Original Android Development] GaresTaylan:
Nevermind
[Galaxy Note 3 Original Android Development] JGKUMAR1976:
shall i use this on n7100 4.3 rom

pls assist
[Galaxy Note 3 Original Android Development] GaresTaylan:
No idea what Im doing wrong. I got my CSC. I downloaded N900VVRUBMJE_N900VVZWMJE.

I have cygwin installed. I have Universal-RDLV_v05 on my desktop. I open cygwin and cd to that folder. I then run ./URDLV.sh full (Path To My MJE tar.md5) inside of cygwin.

When I do this it extracts the firmware, says its hooking system image, verifies system hook, finds system hook and then creates an odin flash able tar. The creation pieces takes about 15 seconds and a new tar is in my output folder. I then put the phone into download mode and use odin to AP that tar.md5 file. Odin gets all the way to the end and then it fails. If I reboot the phone its corrupt and I have to odin the regular MJE to get back up and running.

What am I doing wrong? I don't get any errors that indicate that Im having issues when it is creating the tar. And the regular tar I have before going through this mess is fine as I can Odin it ok before running the script. Verizon Note 3.

*EDIT*

I want to add that I have followed the steps in post 1127 exactly, using the firmware for my phone, and it still failed at the end. http://xdaforums.com/showpost.php?p=49047469&postcount=1127

So now I am really stuck. I don't get it.
[Galaxy Note 3 Original Android Development] Journyman16:
Are you replacing the system and cache .img.ext4 files?

Also you have a Verizon - while it looks similar in specs, there is a reason why there is a Verizon Note 3 forum and an International N9005 forum.

---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------

Um... NO. This is developed for N9005 phones. The other Notes have different root methods. Easier ones probably. They don't have to avoid Knox triggers. Go to the N7100 forums and look for how to root your phone.

---------- Post added at 09:18 PM ---------- Previous post was at 09:00 PM ----------

If you have read the whole thread and do not know the answer, I would suggest you do NOT try rooting with RDLV or any other process. Learn some more first.

It is quite clear, from post #1 on, what the answer is to your question. If you are not sure what those labels mean, again, do some more reading and learn what you need to know.

It will do you no good if someone here says 'yes' or 'no' and you go off and run into a problem. YOU need to know what YOU are doing. When you come back to ask what went wrong, at the least you need to know what it is we need to know to answer you.
[Galaxy Note 3 Original Android Development] poida97:
Hi GalaxHe, appreciate you taking the time to write the detailed tutorial for the process. Would you kindly help me to understand why the following sections are not part of designgears OP?

Thanks!

and

cheers,

Anthony
[Galaxy Note 3 Original Android Development] GalaxHe:
Hello anthony

These are non mandatory steps. You could root and stay on the same level/version of the current installed firmware without upgrading to a higher one.

If you upgrade, it is bettet to put the other files althought even this is not mandatory as well...

Anyway, the op provides steps which are clear enough for some but not the others. This is why i added these steps.

Cheers

Envoyé de mon SM-N9005 en utilisant Tapatalk
[Galaxy Note 3 Original Android Development] poida97:
Wow, thanks for the quick response. I'm on MI7 and happy to stay with that now, so I'll just go ahead and flash the N9005XXUBMI7_N9005TELBMI2_N9005XXUBMI6_HOME_VEGA.tar file as generated by designgear's script.

Thank you!
[Galaxy Note 3 Original Android Development] verifunny:
You can use MobileOdin Pro 3.85 to flash the VEGA file and skip the repackage steps which GalexHe wrote. You use those steps only if you flash using desktop Odin.
[Galaxy Note 3 Original Android Development] poida97:
Well, with all your help I was successful without tripping knox. I used desktop Odin 3.09 and the original Vega file. Tested with Root Explorer. I'm happy!

One last very noob question - SuperSU prompts me with an offer to disable Knox... is this advisable? Can it be enabled again if an application needs it?

Cheers
[Galaxy Note 3 Original Android Development] About20ninj45:
Thank you for your reply, but unfortunately, I am only confused because it doesnt mention my software. The reason why i asked because the whole process seems like we are editing the firmware file and using that as a replacement for the firmware on the device.
[Galaxy Note 3 Original Android Development] GaresTaylan:
Thanks, I get that, but the thread on the verizon for URDLV forwards to this thread. I hoped for some help here.

And yes, as mentioned above, I performed all of the steps in post 1127 which included removing of those files, extracting new ones, replacing them, repackaging those files into a tar, etc.
[Galaxy Note 3 Original Android Development] roger321974:
OK i give up with new Bootloaders (4.3 and 4.4.2) to root knox 0x0. i think there is no chance. samsung locked clever his software and GOD can't break this. thx for dev activity here, but all can give up.
[Galaxy Note 3 Original Android Development] GalaxHe:
I choosed to disabled it using the SuperSu prompt/popup.

No defect since that ;)

Knox is supposed to be an Enterprise tool mainly.

---------- Post added at 06:50 PM ---------- Previous post was at 06:46 PM ----------

Why should all give up?

They have been already able to by-pass the thingy a first time (before mj3). I see no reason for them not to succeeed another time. Maybe you are simply to hurry.... And kitkat is new and is a TEST release. No urge to go on it.
[Galaxy Note 3 Original Android Development] GaresTaylan:
To expand on my last post - I decided to redownload the tar file from sammobile and start the whole process over again. I still get the fail when pushing the created tar file in Odin so I started following GalaxHE's post again.

This time I get all the way to this part:

ComputerName /cygdrive/c/temp/MK2_stock

$ tar -H ustar -c boot.img modem.bin rpm.mbn system.img.ext4 cache.img.ext4 NON-HLOS.bin sbl1.mbn tz.mbn hidden.img.ext4 recovery.img sdi.mbn > MK2VEGA.tar

In my case, I named the files MJE_stock. I run the above script in cygwin and get this error:

/cygdrive/c/temp/MJE_stock

$ tar -H ustar -c boot.img modem.bin rpm.mbn system.img.ext4 cache.img.ext4 NON-HLOS.bin sbl1.mbn tz.mbn hidden.img.ext4 recovery.img sdi.mbn > MJEVEGA.tar

tar: hidden.img.ext4: Cannot stat: No such file or directory

tar: Exiting with failure status due to previous errors

This file does NOT exist on my MJE_stock folder. I never touched it in any way. I just went back to the original MJE file I downloaded from sammobile, extracted it down again, and there is no hidden.img.ext4 file anywhere to be seen.

What is this file and how important is it? the MJE from sammobile restores my phone fine, even though that file isnt in it.

*EDIT*

I packaged the file by taking the piece regarding that hidden file out. Worse case I repackage. Went through the remaining steps and pushed the file with Odin and once again it fails. Same place each time.

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

<ID:0/005> FAIL! (Auth)

<ID:0/005>

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

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note 3 Original Android Development] neov:
Hi,

I just rooted my Note 10.1 2014 P605. I've read that russian MJ9 combined with URDLV doesn't trip knox, but unfortunately it does. Everything is fine, except Knox 0x1... :(
[Galaxy Note 3 Original Android Development] Journyman16:
YOu are on MI5 from your post. The PUB is the region code. MJ comes after MI so you should be fine to root using RDLV. I might have sounded harsh but if you don't understand the difference in the file names, I figured the chances were good you wouldn't understand the rest of the process. So I suggested you need to learn more, including stopping your device getting OTA's until you work out if/why you wish to root your phone.

---------- Post added at 11:41 AM ---------- Previous post was at 11:37 AM ----------

I kept getting the system.img.ext4 error when i was trying to run an Aussie ROM over my Hong Kong ROM. I figured (from a post I read while trying to work out WTF?) the system partitions are constructed differently. Not wanting to risk things so early on (my phone is still less than 3 weeks old) I simply downloaded an updated HK version (MK1) and ran that through the RDLV process instead - worked perfectly first time.
[Galaxy Note 3 Original Android Development] GalaxHe:
What error do you have on your phone screen ? Most likely, the current release which is installed on your phone doesn't accept the MJE release. Anyway, I don't know about MJE, I guess that's not for N9005 phones.
[Galaxy Note 3 Original Android Development] whatisthezmatrix:
Is there a reason why this statement doesn't just state "MJ4, MK1" or higher? Is there anything special about MJ5 MJ6?
[Galaxy Note 3 Original Android Development] About20ninj45:
No worries ..

Naw not really, i have thick skin so i didnt take your comment as being "harsh" lol I had already stopped the updates since day one of owning the phone, so i followed galaxhe's post to a T. I encountered some errors but I successfully rooted my device and all is well!.
[Galaxy Note 3 Original Android Development] antique_sonic:
I read so many post here includes the OP.

I understand that OP stated if on MJ7 or something like newer release firmware, knox will trip to 0x1.

I have kept on searching on this thread... I am on MJ7 N9005, anyway to root this firmware without tripping knox with de la vega?

Thanks!

Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.6 OC
[Galaxy Note 3 Original Android Development] About20ninj45:
Nope

Im afraid not...

There is a post asking the same question by stargazer_vit, as killiberty put it, in short, you have a patched bootloader and it will not work.
[Galaxy Note 3 Original Android Development] antique_sonic:
So... I guess I only have 2 choices.

1. Don't root to keep warranty

2. Root with tripping knox.

:(:banghead:

Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.6 OC
[Galaxy Note 3 Original Android Development] About20ninj45:
hmmm

Do you have insurance on your phone?

If so through who?
[Galaxy Note 3 Original Android Development] antique_sonic:
What insurance? Since when we put our phone under insurance?

Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.6 OC
[Galaxy Note 3 Original Android Development] About20ninj45:
Most of the time, if you buy a device new and depending on your country/ provider, they have an option for insurance for the device. If thats the case and you have insurance via your provider, i wouldnt worry about it to much and root away. :) imho...

Just noticed your in singapore, if you purchased your device new, I think you have a 1 year manufacturers warranty. Sorry for the confusion.
[Galaxy Note 3 Original Android Development] antique_sonic:
Hehehe. Yep mate. No insurance here. Just manufacturer warranty. :)

Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.6 OC
[Galaxy Note 3 Original Android Development] Alfablos:
Hi guys, some time ago I posted a very important question but got no reply: I was running BMI4 and succesfully rooted with URDLV. Then I updated to MJ7 THROUGH Mobile Odin Pro (3.85), as I was told this app wouldn't update the bootloader. Now I find myself with

AP: DMJ7

CP: DMJ7

CSC: DMJ4

Am I screwed? I mean, has my bootloader been updated someway?If so, where did I go wrong?

Can I downgrade to BMI4? Or, can I root again, if needed, without tripping knox?

Please, let me know.

Thanks guys!

P.S.: Any news about knox? Are we closer to be able to install whatever we want (including custom recoveries) on our Note 3?
[Galaxy Note 3 Original Android Development] Killberty:
No you are not screwed at all.

If your knox is 0x0 and u r rooted all is okay.

You can find out your bootloader version by

Getprop ro.bootloader

In any terminal emulator

Should be n9005....bmi5

No news, some custom rom work via MOP but no custom recvoveries with 0x0 so far.

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] Alfablos:
Bootloader is BMI7, which should be ok, am I right?

I really hope this whole situation will end, at last, with a tool to reset knox :P

Thanks anyway
[Galaxy Note 3 Original Android Development] Killberty:
Yup, mine is mi7 too :D

I hope so too.

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] msbearbr:
The post is a bit confuse.. This method still working?

I have one J6 device. If do that i will lose my warranty? My system status go to custom with knox 0x0?
[Galaxy Note 3 Original Android Development] GalaxHe:
no one said warranty is lost... no one actually knows how samsung centers work with this knox status.

There are different kind of posts. Some people actually sent their phones with a knox 0x1 and was repaired + status set back to 0x0. Which may not be the case for the center you would be "attached" to.

You can ask Samsung about what happens if your knox status is 0x1 and post the feedback.

The method is working. It is clear enough I think. If you are below MJ3, knox will not change. If you are MJ3, there is a risk for it to change. If you are above MJ3, it will change.
[Galaxy Note 3 Original Android Development] gsc_hd2:
N9008VZMUBML2 - SM-[B]N9008V[/B] (China mobile 4G LTE)

Hi. Anyone know if the variant "N9008VZMUBML2"- SM-N9008V (China mobile 4G LTE) can be used with this? Any info on KNOX 0x0 rooting for that ?
[Galaxy Note 3 Original Android Development] Killberty:
It will trip knox.

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] gsc_hd2:
Thanks for the quick reply. Its so annoying. All i need is to recover app data for wechat which i have on ttn bkp. Need 2 chats for proof in a legal letter. Lost my new Note 3 9008v after 2 days, and that had my backup se card from my HTC One... Now i have the ttn bkp, but cant restore on my newly bought Note3 9008v. Tried looking for a way to export ttn to helium, but dont think that exists...
[Galaxy Note 3 Original Android Development] mrej201:
will this work with att note 3

which file do i download

do i download sm n900a

plz help
[Galaxy Note 3 Original Android Development] Sleestax:
I want to be sure I completely understand this bit from post #2 before I decide whether to use DLV or the chainfire easy root.

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

No."

So if I intend to flash a kernel/ROM after gaining root, it's going to trip KNOX anyway? If so, I'll probably just use the chainfire root since it's fewer steps. Also, has anyone had the misfortune of having to use their insurance to replace a phone yet? If so, did a tripped KNOX matter? It seems like it only voids the manufacturer warrantee, but I would bet the carrier insurance is written to allow them to deny coverage if you have "tampered" with the phone.
[Galaxy Note 3 Original Android Development] vinokirk:
So.... Whats so bad about using Kingo to root then?

Im on MJ6.
[Galaxy Note 3 Original Android Development] Killberty:
They were stealing your IMEI and sending it to chinese servers.

They have removed this, but my trust is broken.

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] totalny:
@up read kingo app webside...now dont send Your IMEI but they too can't break Secirity Knox

Wysłane z mojego SM-N9005 przy użyciu Tapatalka
[Galaxy Note 3 Original Android Development] jabbathewocket:
Please stop spreading these rumors that imply Knox Warranty bit can be reset by anyone.. it cannot.. if your device comes out of service with the bit reset it means you have a new mainboard in your case (or a completely different phone) efuses *cannot* be reset they are in hardware .. http://www.free60.org/Fusesets has more information on how they work as implemented on the Xbox 360...

There is minuscule chance that the hardware has multiple efuses and samsung can install a new bootloader that looks for these other efuses (essentially pointing the bootloader at a different address of an efuse that is not blow) .. However the chances of this being out there.. are slim to none given the reason for the Knox bit existing in the first place.. not to mention the managing of perhaps hundreds of different bootloaders .. (assuming a modest amount of space in the efuse bitfield..

Granted they could be using something else in hardware to point the bootloader at a specific fuse, that they can flash to the device without maintaining many different bootloaders.. But this is suspicious as well as it would be a HUGE vulnerability and largely negate Knox as a secure corporate environment in terms of hardware trustability.
[Galaxy Note 3 Original Android Development] teslax:
N9005 - xxudmj7

Hi guys,

can I root my N9005 (AP: XXUDMJ7, CSC: OXXDMJ4) with this Root- tool and with any KitKat Rom?

Thanks
[Galaxy Note 3 Original Android Development] Xproplayer:
Need a little help, tried to root SM-N900V on verizon with 4.3 and latest OTA update. Downloaded the SM-n900v file under the "stock firmware download" the one that was 2gb. Put my phone into download mode and loaded said file into odin 3.09, click on start and it errored out and put my phone into usb firmware failed mode, flashed a stock firmware through kies 3 so that's fine but still need root. I can provide my build version if needed. Here is my ODIN output:

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

USB Debugging on

USB connection mode: MTP

Android version: 4.3

Baseband version: N900VVRUBMJE

Build number: JSS15J.N900VVRUBMJE

Any advice?
[Galaxy Note 3 Original Android Development] Killberty:
Failed on aboot which is bootloader.

You are trying to downgrade your bootloader.

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] Xproplayer:
Ahh thank you, anything I can do right now to fix or am I waiting for something to be released? I don't care about warranty flag or factory resetting my phone, just want root asap.
[Galaxy Note 3 Original Android Development] Killberty:
Then u might just want to use cf-autoroot

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] Xproplayer:
I don't see a download for Verizon note 3, could you direct link me to the file or point me the right way
[Galaxy Note 3 Original Android Development] Killberty:
Www.sammobile.com/firmwares

Type in n900vxxx

While xxx u get from ×#1234# in the csc part

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app
[Galaxy Note 3 Original Android Development] Xproplayer:
*#1234# doesn't work for me
[Galaxy Note 3 Original Android Development] Xproplayer:
Does the baseband version count here, there's one on that site for mje which is verizons version that I have. I just load that into cf auto and do start in Odin?