Database Users

Brand new N9005 Root Question without tripping Knox flag

hi,
i got my n9005 (quad core, 32gb, sadly simlocked[provider]) today.
Yet i did not do anything to it, not even boot it.
I don't wanna screw anything up for later.
I want to make a complete backup of it and root it without tripping knox flag.
I read about auto root from chainfire but since that trips knox flag i cannot choose that.
Then I came across Root de la Vega from designgears and chainfire that does not trip knox flag
but as i understand it, it will not work on n9005 since i dont see my device being mentioned,
so what choice do i have now?
Can I power on the device now anyways just to ota or would that be bad (before a complete backup)?
Thanks

Please help me out here

You need to establish what firmware version you have first, take a look in the settings, what version off firmware do you have?

RavenY2K3 said:
You need to establish what firmware version you have first, take a look in the settings, what version off firmware do you have?
Click to expand...
Click to collapse
Austria (A1) 2013 September 4.3 N9005XXUBMI7 N9005VFGBMI1
Baseband N9005XXUBMI6
Even if i can root with URdlV 0.2, can i still remove provider simlock without tripping knox?
Somehow i get the impression i might be better off chainfireing it with autoroot after i flashed official unlocked german stock 4.3 over the current os. Triangleaway might come out in the next months so i can undo the knox trigger. Otherwise i might wait ages until i can use this phone...cos of the provider sim lock..
Thx

Do NOT update FW if you going to RDLV. MJ3 has new locked bootloader so you have to root first, then modify update FW.
Odinary carrier sim lock doesn't matter..
Read RDLV thread carefully again..
Sim lock has nothing to do with FW as long it's from same region and not special carrier locked bootloader
Sent from my SM-N9005 using Tapatalk

Ok, i will not update stock fw!
Why doesn't provider lock matter and what bootloader do i have? I read everyone writing mj3 blabla but where do u actually see what i got.
My stock fw was 4.3 when i got the phone and i never changed anything

cassinni said:
Ok, i will not update stock fw!
Why doesn't provider lock matter and what bootloader do i have? I read everyone writing mj3 blabla but where do u actually see what i got.
My stock fw was 4.3 when i got the phone and i never changed anything
Click to expand...
Click to collapse
Every Note 3 firmware is 4.3 until 4.4 kitkat arrives.
Find out your fw by settings/general/about phone, bottom line. If it has not .....MJ3, .....MJ6, ......MJ7 yet, your bootloader is not locked and you can RDLV.
If you're not gonna use the knox program, go for CF-autoroot instead.
Edit. Didn't see yor post above you said XXUBMI7. Do not update yet couse you have an early fw and can use RDLV
You clearly have some reading to do about firmwares and rooting etc..
Sent from my SM-N9005 using Tapatalk

Yea, its weird cos it says MI and nowhere mJ but everyone mentions it.
What about the provider lock?
Where can i read up on all that important info and esp. The No-No's?

cassinni said:
Yea, its weird cos it says MI and nowhere mJ but everyone mentions it.
What about the provider lock?
Where can i read up on all that important info and esp. The No-No's?
Click to expand...
Click to collapse
?? ...MI7 is your current fw. Newer update fw's: ....MJ3-7, you can download from sammobile.com and flash manually by software "Odin" later after if you wish to root.
If not rooted, you can get these updates OTA.
Read the RDLV thread to learn about that rooting method first. Search around in Note 3 forums for answers.
Sim-lock has nothing to do with this at all. You can not unlock sim by rooting.
You can remove sim lock if you buy special dial code at some web sites. You give them your IMEI and pay them for the unlocking code. Thats all I know about that.
Sent from my SM-N9005 using Tapatalk

[Q] Is there a way to root MJ7 without breaking Knox ?

Hi !
I made a mistake... I flashed my brand new Note 3 with the latest unbranded firmware from sammobile (N9005XXUDMJ7) with Odin. Flashing was successful and everything works fine. But I made it before I even read something about rooting that phone... Now I know that MJ7 is very hard to root without breaking Knox Is there a possibility to reverse it back to MJ3 ? Or maybe there is a way to root with flag 0x0 ?
If there is no way to do this I must wait until somone much smarter than me find the way...

FPPfan said:
Hi !
I made a mistake... I flashed my brand new Note 3 with the latest unbranded firmware from sammobile (N9005XXUDMJ7) with Odin. Flashing was successful and everything works fine. But I made it before I even read something about rooting that phone... Now I know that MJ7 is very hard to root without breaking Knox Is there a possibility to reverse it back to MJ3 ? Or maybe there is a way to root with flag 0x0 ?
If there is no way to do this I must wait until somone much smarter than me find the way...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2461929
have a look here but read all i think its knox free

Thx for fast reply ! But in post from your link is written that this method will break Knox and will void waranty... (flag to 0x1)... I'am looking/waiting for clear way to root my phone and set CSC code to my country (XEO)... (I live in Poland but bought phone from UK because it was 30% cheaper...)

[Q] Haven't ever been able to upgrade firmware on Note 3 since purchase - what's up?

Hola,
Got my Note 3 a while back, and I'm getting itchy firmware fingers!
Maybe I'm being stupid - but so far I haven't had any luck in 'automatically' finding updated firmwares - still sitting on the MHN one that was installed when I bought the phone back on November.
Am I doing anything wrong? Do I need to root to be able to update the firmware? KIES says I'm on the latest... Not a network locked phone - have used t-mob, orange and currently a 3 sim.
Halp!

Hup we go!
No updates have ever come through either OTA or KIES... why me!

pipohippo said:
Hup we go!
No updates have ever come through either OTA or KIES... why me!
Click to expand...
Click to collapse
mate why dont you update via pc odin then ? and you dont need root to upgrade via kies
here try this for guide
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
get your firmware from here
http://www.samfirmware.com/

pipohippo said:
Hup we go!
No updates have ever come through either OTA or KIES... why me!
Click to expand...
Click to collapse
Maybe you should post more details - for instance what version of Note 3 do you have (ideally you want to know the original code, something like N9005ZWE or N9005ZKEBTU, which identifies a N9005 for UK) and what firmware are you right now. And eventually what have you asked when originally asked about the country where you are (for the license agreement). If the combinations above get very weird you also need to know your effective CSC, but that could be a longer shot.

Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)

pipohippo said:
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
Click to expand...
Click to collapse
No my friend as I said before updating via odi n dsnt require root... great now you can just download 4.4.2 firmware for your note 3 and update
Sent from my SM-N900 using Tapatalk

pipohippo said:
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
Click to expand...
Click to collapse
N9005ZKEBTU seems to be be EU-British unlocked N9005 - I would assume that you also picked UK when asked about the license agreement.
N9005XXUBMHN is a very interesting version of the firmware that is not even listed here:
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=BTU#firmware
You seem to have a fairly recent firmware and for the moment there is no 4.4.2 version of the BTU sub-region.

I am guessing that the firmware is actually way old, so it's not listed! Assuming the firmwares are in alphabetical order!
MHx < MJx
All UK aye - good to know that the phone is actually unlocked though I'll have a look on SamMobile and grab a nice 4.3 firmware - not ready for KitKat yet!
xclub_101 said:
N9005ZKEBTU seems to be be EU-British unlocked N9005 - I would assume that you also picked UK when asked about the license agreement.
N9005XXUBMHN is a very interesting version of the firmware that is not even listed here:
-
You seem to have a fairly recent firmware and for the moment there is no 4.4.2 version of the BTU sub-region.
Click to expand...
Click to collapse

pipohippo said:
I am guessing that the firmware is actually way old, so it's not listed! Assuming the firmwares are in alphabetical order!
MHx < MJx
All UK aye - good to know that the phone is actually unlocked though I'll have a look on SamMobile and grab a nice 4.3 firmware - not ready for KitKat yet!
Click to expand...
Click to collapse
Hmm, for some reason I was thinking MK instead of MH, indeed your firmware is unusual! But please be aware that those old firmware versions are the only ones that can be safely rooted without triggering the knox warranty flag. Which reminds me - if you go to download mode do you see any reference to knox?

Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
I am guessing that is kind of good right?
final clarification - rooting has the possibility of triggering knox warranty shizzle, but just doing a 'standard' firmware update (even via odin) should keep things fine right?
xclub_101 said:
Hmm, for some reason I was thinking MK instead of MH, indeed your firmware is unusual! But please be aware that those old firmware versions are the only ones that can be safely rooted without triggering the knox warranty flag. Which reminds me - if you go to download mode do you see any reference to knox?
Click to expand...
Click to collapse

pipohippo said:
Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
I am guessing that is kind of good right?
final clarification - rooting has the possibility of triggering knox warranty shizzle, but just doing a 'standard' firmware update (even via odin) should keep things fine right?
Click to expand...
Click to collapse
Correct, standard Odin update WITH THE RIGHT FIRMWARE will be fine.
IMHO your absolute best path from this point would be something like this:
- save whatever you need to save to the cloud or eventually on the external microSD (just in case)
- disable reactivation lock; disable any updates and security updates in the current ROM; stop mobile data and WiFi; keep all updates off and all network off until the very last step of the entire procedure
- using normal Odin and download mode install oldest BTU firmware you can get - MI7 in the link I provided above; that update should go without any problem; reboot and check everything is OK (and stop again any network or update if re-enabled); this step is only needed in order to get you on the EXACT same path that the huge majority of the people around (including me) have used with URDLV; it might be possible to skip this and still have everything working 100% (and this is quite very likely but I have not tested it);
- using Universal Root de la Vega (URDLV) and the same MI7 from above you will generate a N9005XX____MI7_HOME_VEGA.tar.md5 file which then you will again write with normal Odin and in download mode; this will get you rooted on MI7 with knox 0x0 ; you can read more about this in the URDLV thread
- then using Mobile Odin Pro (NOT normal Odin / download mode) and the most recent 4.3 version available for BTU you can update to MJ7 or MK2 - while keeping root and knox 0x0!
Read for more details on the last step this thread:
http://forum.xda-developers.com/showthread.php?t=2522729
Also note that Mobile Odin Pro will also let you update to 4.4 and keep root and knox 0x0, so it is not a bad investment. Also note that at this point there is no other way to root with knox 0x0 once you got past a certain firmware, nor is it possible to go back before the version of your bootloader (so in other words the above procedure also would guarantee that you can get back to MI7 if for instance you do not like MK2, something you would never otherwise be able to do).
As my signature shows - MJ7 / MK2 are currently very solid versions (and if you are rooted you can get amazing battery life and performance) and I would strongly suggest avoiding any upgrade towards 4.4 in the immediate future.

[Q] Software Update for my S5 (SM-G900F)

Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.

gevensa said:
Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.
Click to expand...
Click to collapse
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.

gevensa said:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Click to expand...
Click to collapse
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).

Thanks for your answers.
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in Spain?
Sent from my SM-G900F using XDA Free mobile app

gee2012 said:
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
fffft said:
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).
Click to expand...
Click to collapse
Thanks for your answers!!
Sent from my SM-G900F using XDA
Free mobile app

gee2012 said:
...
You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
my stock firmware said:
Model: SM-G900F
Model name: GALAXY S5
Country: Czech Republic
Version: Android 4.4.2
Changelist: 1539356
Build date: Thu, 08 May 2014 03:44:41 +0000
Product Code: ETL
PDA: G900FXXU1ANE2
CSC: G900FETL1AND3
MODEM: G900FXXU1ANE2
Click to expand...
Click to collapse

born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
Where is your device from, if i may ask? Is it a Dutch device or imported?

I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.

born4trance said:
I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.
Click to expand...
Click to collapse
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?

gee2012 said:
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?
Click to expand...
Click to collapse
Everything flashes fine, until it encounters hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the mentioned file's filesize differed from the PHN .tar one.
Its a shame that there are so many differences amongst the same model.

born4trance said:
Correct > FAIL! (Size) @ hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the file in question differed from the one inside the PHN .tar
Click to expand...
Click to collapse
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.

gee2012 said:
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
Click to expand...
Click to collapse
I already quoted the firmware i (currently) have, a few posts back

born4trance said:
I already quoted the firmware i (currently) have, a few posts back
Click to expand...
Click to collapse
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.

gee2012 said:
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.
Click to expand...
Click to collapse
Perhaps it will work for you but not for me Í'm not sure if or when i'll flash another FW, i don't really want to lose/give up towelroot :angel:

gevensa said:
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in SpaIn?
Click to expand...
Click to collapse
An OTA update will check your CSC to see if the update should be applied to your system. If you change your CSC from AAA to BBB, you can't expect to receive OTA's for AAA any longer. If your intent in doing this is wanting to receive BBB updates, the CSC change will usually suffice. It's a carrier implementation though and a more conservative carrier could also do secondary checks such as matching the baseband CSC as well.
Also you shouldn't change a CSC unless you are confident that the BBB OTA is compatible with your current firmware.
.
---------- Post added at 11:06 PM ---------- Previous post was at 10:17 PM ----------
born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care aout Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
.

fffft said:
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care out Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
Click to expand...
Click to collapse
Wow.. and wow (+thanks )
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 (of the same model) that comes with a PHN firmware, and then flash the PHN firmware itself and retain 0x0

born4trance said:
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 that has a PHN firmware on it (and retain 0x0)
Click to expand...
Click to collapse
Flashing a custom recovery would increment Knox to 0x1. But it should remain 0x0 if you use the proper PIT corresponding to the new stock firmware. I haven't tested that (as I don't really care about Knox personally) but I don't see any logical reason that Knox would be concerned with that scenario, nor heard of any reports of it happening to anyone.
PHN.. is Netherlands? So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Theoretically the write could still fail on an aboot auth failure but I haven't seen any evidence that carriers are locking down their bootloaders that tightly and don't think that would be a likely impediment.
.

fffft said:
PHN.. is Netherands?
Click to expand...
Click to collapse
Correct: For non branded / SIM-lock free
fffft said:
So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Click to expand...
Click to collapse
I indeed own a SM-G900F and its also important to mention that the partition layout differs between 16GB/32GB models
Now to get ahold of the correct .pit (still looking)

[Q] Downgrading Galaxy Note 3 SM-N9005 from 4.4.2→4.3 without E-Fuse/Guarantee Loss

[Q] Downgrading Galaxy Note 3 SM-N9005 from 4.4.2→4.3 without E-Fuse/Guarantee Loss
Hello everybody.
Is there any way to downgrade the Galaxy Note 3 SM-N9005 from 4.4.2 to 4.3, without triggering the E-Fuse-Chip to short-circuit which causes feautre-loss and guarantee loss?
It's OK, if the Guarantee is just TEMPORAIRLY disabled, while the downgrade is in progress
But after the downgrade, the device should be like a new one.
I also don't want any damage on my device like lower processing power, guarantee loss, heat problems or compatibility problems.
Also, i've already backed all data up, so backup isn't really needed.
Please don't ask me, why i want to take this downgrade. KitKat has so many unknown software disadvantages, and compatibility problems and it's too bogus.
If you know, how to do this, but you don't think, that a downgrade is not needed, please post it yet.
Short Story
The Shop, where the Note 3 is bought from mentioned this device to have Android 4.3 Jelly Bean, but i was shocked/disappointed, after i saw KitKat.​
The KitKat-Wafer is quite tasty, but the Android-Operation-System is quite bitter.
I really appreciate any help you can provide.

Far as I know flashing an official binary will not trip your Knox. Don't know about KK to JB downgrades because the bootloader can not be flashing back to JB after KK has been applied.

AO7 said:
Far as I know flashing an official binary will not trip your Knox. Don't know about KK to JB downgrades because the bootloader can not be flashing back to JB after KK has been applied.
Click to expand...
Click to collapse
Thank you very much for answering.
So, i just have to start ODIN, and let's/here we go?

Right?
What i understand
So that means:
Download ODIN
Install ODIN
Download Firmware
Connect Note 3 to PC
[*]Let's go (Load Firmware on Note 3)
Will the downgrade be sucessfully?
No Guarantee Loss
[*]No eFuse-Trigger
No Feature Loss
No Other Problems
Temporaire guarantee loss is OK, if it can be restored.
But i don't want to Trigger the EFuse-Short Circuit.

Missing
Step 1 download and install Samsung/ Kies USB drivers .
Open Odin put relevant files in correct box.
Connect phone to PC
Make sure correct boxes ticked in Odin .
Hit start button
No Guarantee Loss >>> No not 100% possible .
Knox Triggered by custom rom / kernel/ recovery not by stock rom .
Really would not downgrade as i don't see you as understanding the basics .
Is your EFS folder backed up is question 1 as a downgrade may lose your IMEI .

Hannah Stern said:
What i understand
So that means:
Download ODIN
Install ODIN
Download Firmware
Connect Note 3 to PC
[*]Let's go (Load Firmware on Note 3)
Will the downgrade be sucessfully?
No Guarantee Loss
[*]No eFuse-Trigger
No Feature Loss
No Other Problems
Temporaire guarantee loss is OK, if it can be restored.
But i don't want to Trigger the EFuse-Short Circuit.
Click to expand...
Click to collapse
I'm gonna agree with the poster above Hannah. It looks like you don't really understand what you are doing.
Here's a very quick rundown:
1. Get the Samsung phone drivers
2. Get Odin 3.09
3. Get EFS professional and make several EFS backups of all partitions
4. If your phone is carrier branded only download stock firmware specifically for your carrier brand. Otherwise any region stock firmware should work. Do not use Hong Kong FW unless your phone is from HK. for safety, stick to firmware of your approximate geographical area to avoid possible issues with modems.
5. Read, read, and read as many threads on this forum as you can.
6. There are a bunch of steps after this which i won't all type out. Refer to point 5...

JJEgan said:
Missing
Step 1 download and install Samsung/ Kies USB drivers .
Open Odin put relevant files in correct box.
Connect phone to PC
Make sure correct boxes ticked in Odin .
Hit start button
No Guarantee Loss >>> No not 100% possible .
Knox Triggered by custom rom / kernel/ recovery not by stock rom .
Really would not downgrade as i don't see you as understanding the basics .
Is your EFS folder backed up is question 1 as a downgrade may lose your IMEI .
Click to expand...
Click to collapse
OK, Understood
AO7 said:
I'm gonna agree with the poster above Hannah. It looks like you don't really understand what you are doing.
Here's a very quick rundown:
1. Get the Samsung phone drivers
2. Get Odin 3.09
3. Get EFS professional and make several EFS backups of all partitions
4. If your phone is carrier branded only download stock firmware specifically for your carrier brand. Otherwise any region stock firmware should work. Do not use Hong Kong FW unless your phone is from HK. for safety, stick to firmware of your approximate geographical area to avoid possible issues with modems.
5. Read, read, and read as many threads on this forum as you can.
6. There are a bunch of steps after this which i won't all type out. Refer to point 5...
Click to expand...
Click to collapse
OK, Thanks very much.

I've got a German SM-N9005
What is the Newest Baseband Version with Android 4.3?
I think, it is:
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
Or is MK2 newer?

Hannah Stern said:
I've got a German SM-N9005
What is the Newest Baseband Version with Android 4.3?
I think, it is:
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
Or is MK2 newer?
Click to expand...
Click to collapse
Very basic Samsung FW decoder:
Device identifer - region code - FW identificator ( The lower the letter in the alphabet the newer the software)
N9005 - XXU - MJ7
This is the last 4.3 FW for DBT (Generic Germany)
http://samsung-updates.com/details/22095/Galaxy_Note_3_Snapdragon/SM-N9005/DBT/N9005XXUDMK2.html

AO7 said:
It looks like you don't really understand what you are doing.
Click to expand...
Click to collapse
That's why i was asking.
>>> But thank you very much for letting me know, which is the lastest 4.3-JB-Firmware for the Galaxy Note 3 and telling me, how Samsung's Firmware Codes work.
I owe you something for that great post...
The only problems are the upload sites:
Both pages Suck
UL.TO - Dead Link
RapidGator - Struggle to Download
But i managed it to download that file.
Thank you very much @AO7. The world needs more people like you.

Baseband is Modem and not always updated at the same time as firmware updated .

@JJEgan
 @AO7
I'm trapped.
Is there any way to
Root without triggering EFuse
or EFS-Backup without root?
Here's my thread about EFuse. (This text is the link itself)

Hannah Stern said:
@JJEgan
@AO7
I'm trapped.
Is there any way to
Root without triggering EFuse
or EFS-Backup without root?
Here's my thread about EFuse. (This text is the link itself)
Click to expand...
Click to collapse
I use EFS Backup Pro to backup my modem and EFS partitions but that requires root. TWRP also has the ability to backup the modem partition, but flashing a custom recovery will trigger knox 0x1.
I've tripped my knox over a year ago so I don't keep up with how to root the phone while keeping knox 0x0. A quick google gave me this post but I have not tried it myself.
If you manage to root your phone and keep it 0x0 than technically I imagine you can backup your EFS. The question is it's still worthwhile to go to all this trouble. The N9005 is approaching its' second birthday. In my personal case, since I don't care for extended warranties on electronics, my legal basic warranty already expired some time ago anyway.
there might be some obscure proprietary Samsung features that depend on Knox. But other than those, I see no real point in trying to keep your phone 0x0.

AO7 said:
I use EFS Backup Pro to backup my modem and EFS partitions but that requires root. TWRP also has the ability to backup the modem partition, but flashing a custom recovery will trigger knox 0x1.
I've tripped my knox over a year ago so I don't keep up with how to root the phone while keeping knox 0x0. A quick google gave me this post but I have not tried it myself.
If you manage to root your phone and keep it 0x0 than technically I imagine you can backup your EFS. The question is it's still worthwhile to go to all this trouble. The N9005 is approaching its' second birthday. In my personal case, since I don't care for extended warranties on electronics, my legal basic warranty already expired some time ago anyway.
there might be some obscure proprietary Samsung features that depend on Knox. But other than those, I see no real point in trying to keep your phone 0x0.
Click to expand...
Click to collapse
EFS backup always shows up an error while starting up. Then it closes itself.
EFS and EFuse...:crying:

does anyone here still have that jelly bean file?

pottylotty said:
does anyone here still have that jelly bean file?
Click to expand...
Click to collapse
What JB file ???