Database Users

Note 3 is "not supported" by Kies 3

EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.

If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005

ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.

Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?

bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.

Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).

Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.

Possible not a genuine Note 3?

This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..

Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.

Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.

Flashed Rom zip. Note 3 back to health.

shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2

shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked

R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.

If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.

Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?

I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?

I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...

Bootloader version after URDLV + firmware or modem downgrade

Hey
Something I don't understand.
It is always written to check *#1234# to get the bootloader version.
On my side, If I do that I get :
AP : MK2
CP : MJ7
CSC : MK3
What I don't understand is that I am rooted since MI7.
I was branded Orange - used URDLV rooting method to MI7 - URDLV to MJ3 (november) and URDLV to MK2 (last week)
without tripping knox
As I am not satisfied of MK2 (due to very strange location update from time to time), I'd like to go back to MJ3.
But all comments I read are all saying this is not possible (which might be true anyway). But all posts are always based on the *#1234# result....
I understood that URDLV was not changing the bootloader (I didn't flash the famous aboot.mbn).
So now after using URDLV method, should I understand that I got the new bootloader somehow ?
My concern is really only on this location that is sending me all around the world regularly and I think this is linked to the modem. So the idea was to downgrade the modem but can't find any experience on that. It seems modems are now linked to particular firmwares. So I wondered if I could go back to MJ3.
Some screenshots seem showing Modile Odin Pro displaying the bootloader version... but don't feel like buying an app just to get this information once and never use it...
Ahhhhhh I miss my Note 2 The only missing feature on it was the S-Pen not being able to use the "menu" and "back" button (which I already missed on the Notes1 )
Cheers

GalaxHe said:
Hey
Something I don't understand.
It is always written to check *#1234# to get the bootloader version.
...
Click to expand...
Click to collapse
No, a slightly better way to get the bootloader version is:
Code:
adb shell getprop ro.boot.bootloader
But even this one can be fooled.
Downgrading the modem is a different thing and on Note3 can be tricky.

I might be missing something here, but you used Vega to do all the upgrades. That means you still have the original bootloader - why can't you simply use the MJ3 ROM process with RDLV again to flash a root version of MJ3?
I'd back up the data then do factory reset and act as if you're doing the original RDLV again.
Do you think there would be a problem with that?

xclub_101 said:
No, a slightly better way to get the bootloader version is:
Code:
adb shell getprop ro.boot.bootloader
But even this one can be fooled.
Downgrading the modem is a different thing and on Note3 can be tricky.
Click to expand...
Click to collapse
I get an error "device not found" with this command on a terminal
What do you think about with "tricky" with the modem downgrade ?

Journyman16 said:
I might be missing something here, but you used Vega to do all the upgrades. That means you still have the original bootloader
Click to expand...
Click to collapse
I agree... but to verify this, lots of post tell to do a *#1234# - which does not return any information about MI7 (I am not supposed to have the mj3 bootloader).
Haven't found threads of people having done a downgrade using "regular" Odin...

hummm I am not supposed to type the 'adb shell' but only 'getprop ro.boot.bootloader' when using terminal on the phone........
so yes I am still on MI7
N9005XXUBMI7

No downgrade possible
Well... now I know it's not possible to downgrade !
On Odin's side :
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ1VEGA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> modem.bin
<ID:0/012> rpm.mbn
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Errors in download mode on the phone screen :
When downgrading to URDLV MI7 / MJ1 / MJ3
SW REV CHECK FAIL : [rpm]Fused 2 > Binary 1
When downgrading to stock MI7
SW REV CHECK FAIL : [sbl]Fused 2 > Binary 1
I had to reflash the firmware I had previously (so MK2 URDLV) to be be able to use the phone back. I was stuck on download mode - no more recovery and default boot was saying the phone need urgent recovery through Kies - which was not usefull either as it's not able to do anything when you never used the software before...
Anyway, I might give it a try tomorrow to downgrade the modem only - see if that's possible.
btw, my knox is still 0x0

To complete this thread, I tried to downgrade the modem.bin + non-hlos.bin from MJ7 (provided with MK2 firmware) to versions I had on my PC :
MJ3
MJ1
MI7
with no luck.
Phone boots but there is no network service anymore.
I downloaded MJ4 branded to my provider and was able to flash the modem + non-hlos.bin and have that work. Unfortunatelly, it hasn't change my issue of bad location being detected. Seems this could be coming from somewhere else...
Need to try if downgrading to MJ3 works or not now that the modem is not mj7 anymore.

stuck note3
GalaxHe said:
To complete this thread, I tried to downgrade the modem.bin + non-hlos.bin from MJ7 (provided with MK2 firmware) to versions I had on my PC :
MJ3
MJ1
MI7
with no luck.
Phone boots but there is no network service anymore.
I downloaded MJ4 branded to my provider and was able to flash the modem + non-hlos.bin and have that work. Unfortunatelly, it hasn't change my issue of bad location being detected. Seems this could be coming from somewhere else...
Need to try if downgrading to MJ3 works or not now that the modem is not mj7 anymore.
Click to expand...
Click to collapse
i downloaded the 4.4.2 rom poland and flash it on hongkong one but flash was refused and stuck on boot menu,
any ideas please.

ahmekh said:
i downloaded the 4.4.2 rom poland and flash it on hongkong one but flash was refused and stuck on boot menu,
any ideas please.
Click to expand...
Click to collapse
I don't understand the link with this thread... it's about downgrading and not about upgrading.

Reflash the HK one that you had. I had similar results trying to flash an Australian version - not sure why. Instead of going back to MI7 I flashed HK MK1 version using the RDLV method - now on MK1, rooted, Knox on 0x0.
Will work on getting to Aust CSC later when I have had the phone more than 2 weeks and willing to risk warranty.

How do i do the RDLV method
Sent from my GT-I9300 using XDA Premium 4 mobile app

ahmekh said:
How do i do the RDLV method
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/showthread.php?t=2498850 and have a read through. Galaxhe posted a clear explanation of how to do it in (I think) post 1127, but do some reading of the thread as well so you understand what is going on.

[Q] Soft brick at&t note 3?

Hi
I have AT&T Note 3 , sim unlock from carrier, successful kingo root 0x0 Knox (startup splash screen says Custom Unlock)
So, I was hopped up on percocets because of my recent surgery and i decided i was in conscious enough mind to tackle getting AWS unlock. I wasn't.
I was reading about chainfire regionaway app, so i went to the app store and downloaded the first chainfire app that popped up - 3D. so now i am stuck in the note 3 splash screen. yes i know i should have read it more carefully, etc. but i just wasn't all there at the time. Please help me save this $500 brick!
I've been reading these methods:
http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/
i can get the phone recognized in ODIN, but the secure check fail: cache occurs
http://forum.xda-developers.com/showthread.php?t=2567133
i can't download any of these files...
http://forum.xda-developers.com/showthread.php?t=2507403
tried this but didn't work.
i'm really not making any headway... any help would be much appreciated.
side note:
can i send this in for warranty? Since AT&T just release the kitkat update can i claim that i tried to update and it failed?
current binary: samsung official
system status: custom (not official)
Knox lock 0x0
Knox warranty void 0x0
EDIT: After doing the ODIN fail - it is stuck in ODIN mode and says "firmware upgrade encountered an issue. Please select recory mode in Kies & try again."
Can not enter download mode. But still connects in ODIN
thanks!

Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?

kenny1991 said:
Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?
Click to expand...
Click to collapse
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood

firstsx said:
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood
Click to expand...
Click to collapse
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
I don't know. But flashing kitkat may tripe Knox i don't know atnt models. If you don't want to flash then return it.

kenny1991 said:
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
Click to expand...
Click to collapse
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1

firstsx said:
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware. http://www.sammobile.com/firmwares/3/?download=25106
You know how to flash?

kenny1991 said:
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware.
You know how to flash?
Click to expand...
Click to collapse
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
but when i run it, it fails and says this on my phone
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1

firstsx said:
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
Click to expand...
Click to collapse
hm. Still no recovery mode?
Past your Odin log so someone can see why it fails.

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Need pit file?

kenny1991 said:
Need pit file?
Click to expand...
Click to collapse
sammobile doesn't say anything about pit file?
i only used the AP file from there
i have HLTE__USA_ATT_32G_pit file even when i use that PIT file with the AP file it still gives me the same fail error...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

firstsx said:
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T

toastido said:
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit

firstsx said:
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps

Markudsc said:
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Click to expand...
Click to collapse
can i use this method
http://forum.xda-developers.com/showthread.php?t=2559715
it seems pretty much the same, except yours includes updating to kitkat.
if i do kitkat, can i still keep root?
will this trip knox?

Ok i did this method
http://forum.xda-developers.com/showthread.php?t=2559715
i re-downloaded all the files because the files i had just wouldn't work in ODIN or anything. so based your advice i just downloaded new files.
ODIN flash was successful
then i did the rest of the steps successfully! and i am back!

Problem while flashing 5.0 Lollipop

So my Note 3 (europe) is unlocked and I downloaded the file from sammobile (N9005XXUGBOB6_N9005H3GGBOB1_N9005XXUGBOA2_HOME) but when I tried to flash it with Odin (I tried both 3.09 and 3.10 v.) when it's just about to finish it reads:
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And now I'm stuck at this screen which says that I need to connect my phone to Kies to enter recovery mode, which I've also tried, however Kies does not recognize my phone at this point.
I really don't know what to do, I've read a few topics here and there and some of them suggested I should flash with both the md5 and the pit file. I'm not sure if I should do this because I've also read that I could hard-brick my phone...
Anyway, I would really appreciate if anyone could tell me what to do now and if there's a way to return to 4.4.2 or, ultimately, to update to 5.0.
Thanks!

danhale said:
So my Note 3 (europe) is unlocked and I downloaded the file from sammobile (N9005XXUGBOB6_N9005H3GGBOB1_N9005XXUGBOA2_HOME) but when I tried to flash it with Odin (I tried both 3.09 and 3.10 v.) when it's just about to finish it reads:
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And now I'm stuck at this screen which says that I need to connect my phone to Kies to enter recovery mode, which I've also tried, however Kies does not recognize my phone at this point.
I really don't know what to do, I've read a few topics here and there and some of them suggested I should flash with both the md5 and the pit file. I'm not sure if I should do this because I've also read that I could hard-brick my phone...
Anyway, I would really appreciate if anyone could tell me what to do now and if there's a way to return to 4.4.2 or, ultimately, to update to 5.0.
Thanks!
Click to expand...
Click to collapse
Flash one stock firmware unbranded (like for example the Poland one: HERE).

I'm thinking of manual updating Europe note 3 lte
Hello, did that suggested solution worked for you? I'm thinking of flashing mine UK(BTU) Note 3 with software, made for BALTIC region (SEB). will it work? (I live in Lithuania, BALTIC received lollipop a month ago, while UK version is still on KITKAT). Waiting for the answer.

Mindaugas92 said:
Hello, did that suggested solution worked for you? I'm thinking of flashing mine UK(BTU) Note 3 with software, made for BALTIC region (SEB). will it work? (I live in Lithuania, BALTIC received lollipop a month ago, while UK version is still on KITKAT). Waiting for the answer.
Click to expand...
Click to collapse
Yes, it should.

Will I get updates from KIES after doing that?

Mindaugas92 said:
Will I get updates from KIES after doing that?
Click to expand...
Click to collapse
Nope. You will have to reflash android 5.0 (UK BTU) when will be out for receive OTA or KIES updates.

Stuck at Odin mode ? Please help

Hi,
I wanted to reinstall the stock rom via odin and i was trying to put it to odin mode but I didn't know my Pda csc so I decided to reboot it before flashing to make sure I got the correct firmware but now it won't reboot and it's stuck at odin mode despite removing the battery and inserting it again .

Is the phone an i337 or i337m?

audit13 said:
Is the phone an i337 or i337m?
Click to expand...
Click to collapse
IT's i337 and it has the letters UD in the same line and it's from AT&T btw and I checked sammobile website and I think there are two firmware to download but I don't know which one
Thanks for your reply.I could have replied earlier but I didn't get the notification

In download mode, do you see anything about knox or warranty bit?
Id this the stock ROM you tried to flash: http://www.sammobile.com/firmwares/database/SGH-I337/ ?

audit13 said:
In download mode, do you see anything about knox or warranty bit?
Id this the stock ROM you tried to flash: http://www.sammobile.com/firmwares/database/SGH-I337/ ?
Click to expand...
Click to collapse
the knox count is :0
and I didn't even try to flash.I was seeing if i can put it into download mode and then I went to download the firmware and then found out there are two of them so when I tried rebooting to check which one I need from the system info , it got stuck.

Looks like neither of the firmware files from sammobile.com will work as your phone is running at least a 4.3 bootloader as indicated by the presence of the "Knox" in download mode. Your bootloader may be locked as well.
You can't boot into recovery either?

audit13 said:
Looks like neither of the firmware files from sammobile.com will work as your phone is running at least a 4.3 bootloader as indicated by the presence of the "Knox" in download mode. Your bootloader may be locked as well.
You can't boot into recovery either?
Click to expand...
Click to collapse
No I can't

Okay, this may help: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642

audit13 said:
Okay, this may help: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Click to expand...
Click to collapse
Ok I will try and let you know.I am currently trying to restore with kies

If kies doesn't work, try smart switch.

audit13 said:
If kies doesn't work, try smart switch.
Click to expand...
Click to collapse
I am getting the same error from kies and odin which is sw rev check fail : fused :5 ,binary :1
and this is odin's log :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I might try the files in the guide but I don't know which bootloader I have

The rom can't be flashed because the rom you are flashing has a bootloader that is older than the bootloader on the phone. This is evidenced by the failed to flash the aboot.mbn file.
Where did you get the rom file?

audit13 said:
The rom can't be flashed because the rom you are flashing has a bootloader that is older than the bootloader on the phone. This is evidenced by the failed to flash the aboot.mbn file.
Where did you get the rom file?
Click to expand...
Click to collapse
I have just checked and I think kies was downloading the one with the mdl bootloader and I think it's the same one I tried flashing with odin.The first one from this link http://www.sammobile.com/firmwares/database/SGH-I337/
Thanks again

Looks like kies will not restore the phone. You'll have to flash a newer rom using Odin. Check out the link I posted earlier.

audit13 said:
Looks like kies will not restore the phone. You'll have to flash a newer rom using Odin. Check out the link I posted earlier.
Click to expand...
Click to collapse
It only has 2 firmwares and I already tried 1 and the second has a different bootloader.
Edit: If you mean the guide,then it is stated at the end that I shouldn't use it with MDL

http://forum.xda-developers.com/showpost.php?p=65534997&postcount=8

If your phone has the mdl bootloader, the mdl sammobile.comm firmware should work. If the mdl firmware can't be flashed to the phone, this tells me the phone is not running an mdl bootloader.
Yes, the guide should not be used if the bootloader is mdl but this may not be the case with your phone as there is a reference to "knox" in download mode.

audit13 said:
If your phone has the mdl bootloader, the mdl sammobile.comm firmware should work. If the mdl firmware can't be flashed to the phone, this tells me the phone is not running an mdl bootloader.
Yes, the guide should not be used if the bootloader is mdl but this may not be the case with your phone as there is a reference to "knox" in download mode.
Click to expand...
Click to collapse
I don't know what's wrong but kies and smartswitch are downloading the one with the mdl bootloader

It's probably picking the mdl because that is the only full rom available for the i337. Any updates beyond 4.2 were only released as ota updates. You will have no choice but to flash in accordance with a locked bootloader.

audit13 said:
It's probably picking the mdl because that is the only full rom available for the i337. Any updates beyond 4.2 were only released as ota updates. You will have no choice but to flash in accordance with a locked bootloader.
Click to expand...
Click to collapse
There is also the one with the mdb and I tried it too but I didn't work.I didn't understand the second sentence? Should I follow the guide and install one of the firmwares ? Which one do you recommend ? or are they the same ?