Database Users

Galaxy S4 Stock Firmware Quick Download Links [Mediafire, Dropbox or others]

I have the Galaxy S4 (GT-I9500). As such I am interested in getting the stock firmware for my device. However, all I get are download links to the hotfiles posted on Samfirmware.com and samsung-updates.com. As we all know, the Hotfile download links are usually very slow. I use a slow connection so this makes it even worse. Could someone be having a download link of the stock ROM somewhere that is not a hotfile?

Seriously dude ! i want a non-hotfile link too i'm stuck with my old firmware

I'm still looking for it. If you find it be sure to share the details on this thread.
asad007 said:
Seriously dude ! i want a non-hotfile link too i'm stuck with my old firmware
Click to expand...
Click to collapse

i just found This link
but it's not the latest firmware

Thanks a bunch mate. It may not be the latest but at least its something. Keep sharing
asad007 said:
i just found This link
but it's not the latest firmware
Click to expand...
Click to collapse

Stock S4 ROM - NOT hotifle
Hey,
Won't believe how long I've spent doing this.
I'm trying to unroot my S4 (XFA)
But now I'll just take any stock ROM.
Preferably a 4.2.2
Every single link to a ROM is hotfile....
Anybody got something for me?
---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------
echenze said:
I have the Galaxy S4 (GT-I9500). As such I am interested in getting the stock firmware for my device. However, all I get are download links to the hotfiles posted on Samfirmware.com and samsung-updates.com. As we all know, the Hotfile download links are usually very slow. I use a slow connection so this makes it even worse. Could someone be having a download link of the stock ROM somewhere that is not a hotfile?
Click to expand...
Click to collapse
I'm exactly in the same position.... I cannot find a stock ROM anywhere.
Were you successful. How did you do it?

Hi @Bigmozzarella please check out this group on Facebook It was very helpful throughout my stay with the Galaxy S4 (I have since upgraded to the Note 3). There are fast download download links to stock firmware thanks to one @stanley08. Check it out.

got it! - sorted!
echenze said:
I'm still looking for it. If you find it be sure to share the details on this thread.
Click to expand...
Click to collapse
OK - got it! :good:
Found it on SamMobile.
I had to join (just like one joins this forum) - there's paid membership and free membership.
Free means downloads are slower (but not that rubbish you get on all the rapidgator terafile, etc networks. I'ts just a download wihtout makign you wait 30sec, and with no restrictions like (you must wait another hour)
I went to firmware - firmware database.
There you can enter the fields, phone, model, region, etc... and I got my original 4.2.2 - as released by my mobile SP
I'm now on official, official.
4.2.2 came out before Knox - so just don't know if I have a flash count or not - don't know where / how to check - but at least no Warranty void bit yet.

Bigmozzarella said:
4.2.2 came out before Knox - so just don't know if I have a flash count or not - don't know where / how to check - but at least no Warranty void bit yet.
Click to expand...
Click to collapse
@Bigmozzarella why settle for 4.2.2 when there's even KitKat out for the S4? 4.2.2 did not have the Knox counter. It is after all the Android version the S4 launched with. The Knox counter was introduced in Android 4.3. When you upgrade to 4.3 you're likely to get a new bootloader which will come with the Knox counter reading something like this : 0x0 Warranty bit: 0 when untripped and the warranty bit becomes 1 once tripped. Rooting, flashing a custom kernel, recovery or ROM will lead to that. There are ways of flashing Android 4.3 and retaining your old bootloader so as to avoid Knox. The same is the case with KitKat (not too sure, just checked for Note 3 only). You can check the S4 threads, there's a lot of such info. How to check Knox counter? Boot into your device download mode, you'll see it.

Sorted now thanks
echenze said:
@Bigmozzarella why settle for 4.2.2 when there's even KitKat out for the S4? 4.2.2 did not have the Knox counter. It is after all the Android version the S4 launched with. The Knox counter was introduced in Android 4.3. When you upgrade to 4.3 you're likely to get a new bootloader which will come with the Knox counter reading something like this : 0x0 Warranty bit: 0 when untripped and the warranty bit becomes 1 once tripped. Rooting, flashing a custom kernel, recovery or ROM will lead to that. There are ways of flashing Android 4.3 and retaining your old bootloader so as to avoid Knox. The same is the case with KitKat (not too sure, just checked for Note 3 only). You can check the S4 threads, there's a lot of such info. How to check Knox counter? Boot into your device download mode, you'll see it.
Click to expand...
Click to collapse
Cheers, thanks. I sorted it out.
I had a rooted phone with a custom 4.3.
Unrooted, and flashed 4.2.2 - making it stock like the phone came out.
From there I use the usual Samsung updates up to KitKat. (with all the bloatware....and their updates )
So, I'm on the latest firmware, it's the stock Rom, No warantee bit void, and no custom Rom count.
My phone has that irritating screen issue when it flickers the S-view for no reason, and I want to take it in under warrantee - which I can do.

[Q] New to note 3 & samsung

hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you

linx1287 said:
hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you
Click to expand...
Click to collapse
Samsung issue a 24month warranty on the Note 3 (maybe country specific?) -
If KNOX isn't an issue for you and you do not mind tripping it, the CF-Auto is the way to go.
RDLV is complicated if you're lazy, but it does preserve KNOX status depending on your bootloader version, put in #*1234# into your dial pad and post the results. We can know if you can use RDLV.
However, if you want to flash a Custom ROM, then you will need a custom recovery, which will trip your KNOX (can't be done without) - on the Android dev section and Orginal Android dev section (in this sub forum) are some Custom ROMs and the instructions on how to do so.
I have used X-Note, Crash and am currently using AllianceROM, but there are a few others.
Just be careful with custom kernels until you're pretty confident cause you can bootloop and ruin your EFS quite easily (it is fixable 99% of the time tho, script is on here also)
EDIT : All you need is here pretty much

thank you for your reply & these are the stats
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005EVRDMJ4
also RDLV is way too complicated for me & besides i do plan to install a custom recovery so i think that defeats the point ....since you seem to have tripped knox, there hasnt been any kind of system issue i hope? this whole knox business gave me cold feet when i read about it...but so far as i can see..its just a flash counter.... could you tell me the tools i need to get started with? i already downloaded the usb drivers & odin 3.09..is there anything else i should need?
p.s. i was reading about "before or later MJ7 4" whatever...& i was wondering which of these was it refering to? ap? thank you

Once you trip the knox counter it makes no difference to the phone except not being able to use knox containers, and of course the warranty which you know. -- if you have the drivers and odin. Go grab cf-autoroot, run it thru odin and voila all done, similar for twrp or Cwm which ever you choose as your custom recovery (I use twrp) flash in odin and that's it all set.
Just make sure and I can't stress this enough, that you flash the right ROM for the N9005, and N900 doesn't work. - avoid doing restores with twrp for now also when you do a back up, some issues have arose recently and not sure of they're resolved or not yet.
Have fun man, just read everything about the ROM etc before you flash the odd one has FC's or NFC issues
Sent from my SM-N9005 using XDA Premium 4 mobile app

ok so backing up & restoring with recovery is, for the time being, a no no? yes i will make sure to see if the roms are made for n9005 only....i will probably start off with omega roms as they are the 1st choice i had when i started modding the s3 ....thank you soo much mate for all the info...1 last thing to clear up is i am reading on developers talking about MJ or MK or whatever it is....are they talking about the build number i find in Settings/About??

1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?

linx1287 said:
1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?
Click to expand...
Click to collapse
Yeah yours is unbranded, only thing that may/will apply to you is region lock (which unless you're leaving the country your purchased your phone in isn't an issue at the start.
Although I see your CSC is EVR (if I recall correctly that is EE UK's firmware on board)
EDIT: Yes MK/ML are build numbers

no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?

linx1287 said:
no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?
Click to expand...
Click to collapse
Yup can go forwards. EVR (EE aka Orange/T-Mobile) have unlocked phones so yeah you won't have region lock. Which means yours is unbranded but carrier unbranded.
As for firmware, it depends on what region you are using? And what country you are in (you could use BTU (also UK, unbranded but EVR is ok also) - You are **now I say this depending on your country/region** OK on MJ7 or MK2 IF you upgrade since you're using a UK based ROM/CSC your network obviously supports it. However battery life is better on lower than MJ6. So it's your choice really.
Most custom ROMs are MK2 or ML2 atm I think, - Not sure if any upgrade your bootloader to MJ7 (if they do, you can't roll back any lower currently)

i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue

linx1287 said:
i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue
Click to expand...
Click to collapse
As long as your bootloader doesn't go to MJ7 - that firmware is OK, If your bootloader updates ( I think it may with the custom ROM) you can't roll back to MJ6, you can go to MJ7 or MK2 via BTU which will work for you since EVR works.

the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2

linx1287 said:
the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2
Click to expand...
Click to collapse
You can drop back as far as MJ7 ( I have at least when I've returned to stock due to mess ups) my build is MK2 atm
the bootloader only goes to MJ7 (last I checked, If it has changed then mine still lets me roll to MJ7)

csc seems a very complicated mess...GOD when did the mod friendly samsung go this crazy? the s3 was the most fun thing to mod...now this feels more complicated then Sony's!! :'( since my csc is EVR...is it possible to put BTU? i saw someone post this but didnt get any replies... http://www.usofttech.com/t128991.html
OH CRAP you said this BTU already...sorry my bad.... just trying to absorb all this

1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated

linx1287 said:
1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated
Click to expand...
Click to collapse
You can CF root straight away, - since you're triggering KNOX anyway it won't affect you. Then on with custom recovery etc, just keep MJ7 as your stock back up on your PC just incase. and IF you run into any issues with EFS (bootloops/no signal/wifi/baseband etc) use THIS It has saved me and quite a few others.
EDIT: And no problem man, glad to help, we all start somewhere with new devices

mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin

linx1287 said:
mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin
Click to expand...
Click to collapse
I use 3.07 personally - and flash using PDA -- Use the one with CF root if you're unsure

the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?

linx1287 said:
the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?
Click to expand...
Click to collapse
TWRP has issues *sometimes* there's a few posts about it around, I personally have had no problems and use TWRP fine, but I mentioned it because what works for one, doesn't always for another.
As for EFS backup, keep it just incase -- IT seems Android can rebuild the EFS again with that fire script. -- It's handy though, gotten a few out of the crapper including myself

[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] 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 ???

Can I downgrade my S5 from Lollipop 5.1.1 to Kitkat?

So I had to finally use my warranty for my S5 with Tmobile. I have the replacement but it came with Lollipop 5.1.1 and not Kitkat. I've started using Lollipop and it's a nightmare. I absolutely hate it and many of my apps are incompatible. I am a bit new to this but am well aware Samsung has pretty lousy performance with S5 and lollipop.
Knowing this, is there an efficient and safe way to downgrade without tripping knox? I did some googling but find more information on 5.0 Lollipop than 5.1.1. I'm surprised S5's got that update.

you can with no problem ( right now no one have problem with imei )

popmpopm said:
you can with no problem ( right now no one have problem with imei )
Click to expand...
Click to collapse
Thanks for the reply. What is the best way to get started reading up on that? I am a bit new to the rooting scene etc. I don't want anyone to spoonfeed me an answer--just kind of a general "where can I get started" thing so I can understand what firmware I need etc.

1. Go to sammobile website and click Firmware button.
2. Enter your device model in the search box
3. Select your country and the android version you want (in your case select 4.4.2)
4. Click Download button to download the firmware (you need to register to be able to download, don't worry it's free).
5. Download Odin and use it to flash the firmware you've downloaded (Google how to use it if you don't know how).
By the way, your phone doesn't need to be rooted to do all this. In the contrary, if it is already rooted, it will lose the root after doing these steps.
Hope that helps