Database Develop

[Q] Galaxy Note bricked? No. Problem solved.

This is the situation:
Windows XP 32bit
Galaxy Note with LA4
Odin V1.85
KIES latest version
Latest Android SDK
I tried today to downgrade to a directly rootable stock ROM. It failed?
My Note stucks on the bootscreen.
I can put the Note in the downloadmode. When I start Odin, I see a yellow box under ID:COM with 0:[COM7], so my computer sees the Note. I want to flash the rootable stock ROM as described in many threads, especially following Dr. Ketans Guide
But it fails, it stucks at Initialzation..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
I tried the LA4 stock ROM, same problem.
After this I have putted the Note in recovery mode and this is what I see:
"E:failed to mount /sdcard (Unknown error: 0)"
"E:install_application_for_customer:Can't mount /sdcard"
" your storage not prepared yet. please use UI menu for format and reboot actions."
"copy application failed"
In the recovery mode I tried Factory reset and Wipe cache...no effect.
Since 4pm I have tried many things, read threads and posts, but nothing has solved my problem. By the way I have not seen a problem as described above no where. Is there a genius who can solve this/my problem?
Or is my Note bricked?

The only thing i can see is that it can't mount the SD. Other than that, i don't know. And you know i had my own problems yesterday, so i'm not in the position to know what might be wrong. But one thing is sure, it's not bricked since you can enter download mode.
I know it's frustrating, but you'll have to wait for somebody that knows some things about Odin. I used it myself for the first time yesterday since the Note is my first Samsung device.
Sent from my iPad GT-N7000 using xda premium

see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps

I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)

Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
As you can read I did trie data factory reset, after flash with Odin it didn't work. Thanks for your help.

gee2012 said:
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps
Click to expand...
Click to collapse
As you can read I can't ENABLE USB DEBUGGING, because I can't start my Note up normally. Thanks for your help.

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Thanks, but no effect.

dr.ketan said:
I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)
Click to expand...
Click to collapse
With the pit-file it showed PASS!:
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/006> Added!!
At my screen the following:
Firmware upgrade encountered an isseu.
Please select recovery mode in Kies & try again
If I open Kies to select recevory mode it asks for a recovery code. I tried some codes like 0000,1234 and others, but no good...
Then, I entered the download mode of the Note and tried a flash with KK9 (one file) it shows PASS:
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan

Note not bricked.
Problem solved.

And the problem was?
Sent from my GT-N7000 using xda premium

Read my first post...

got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_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> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks

Caesarea038 said:
With the pit-file it showed PASS!:
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan
Click to expand...
Click to collapse
Really glad to hear.
It is really painful when some one say bricked lovely device.
its ok now, congratulation.
it is advisable once you format internal SD card. Not in hurry, but at least before next update.
Sent from my GT-N7000 using xda premium

shaharda said:
got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
...........................
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks
Click to expand...
Click to collapse
Can you tell me exactly the problem and what you did step by step?

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Today I figured something out:
If you encounter problems with rooting/flashing try another or original USB cable, maybe a different USB port....
My problem as described in my first post was a combination of a fail USB cable and a software problem.

thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).

now the battary won't charge. need to send it to the Lab.
thanks anyway. (i'll as them what they did)

shaharda said:
thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).
Click to expand...
Click to collapse
Can you enter DOWNLOAD MODE?

[HELP] - upgrade gone wrong?

hi all,
i was on KL3, rooted, then KIES kept bothering me so i thought i'd upgrade to the new LA3 i think....
then the thing crashed and now all i get is the Firmware upgrade encounted an issue. PLease recovery mode in Kies and try again.
problem is, i cant get it to go into recovery mode?!??!?! (volume up, power?)
nothng works, KIes cant detect it, and cant upgrade anything, i am a total noob, and can only get into ODin mode..
HELP please?!?!?
what do i need to do, please step by step, what to download, what to press and whether i need to get a micro sd to install some firmware?
thankyou - urgent help needed!

First of all, relax
You said you can get into "Odin Mode"? I suppose that's download mode. Just go to this thread and everything is explained here. No need to worry
http://forum.xda-developers.com/showthread.php?t=1424997
Just flash another firmware (why not the latest) and everything will be just fine.
P.S. Once rooted, you should probably stay away from stock upgrades...
Press thanks if it helped

Recovery : vol up + home + power
If you get into recovery just wipe cache n wipe data
If error still there
Go to download :
vol dwn + home + power
Reflash new rom
Sent from my GT-N7000 using xda premium

this is all i get and gets stuck???
i chose this one: N7000XXLC1---------2.3.6-------2012 March----------N7000OXXLB3-----------France------------------------------------Download
went to bed for 2 hours and it didnt move...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXXLB3_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img

confirm you have close antivirus if running
Dont put ROM file too deep, better keep on Root folder e.g. C:/Folder/***.tar.md5
Dont use USB extension, attach USB cable direct to slot on PC, try using different slot (preferably back side PC)
N dont forget to put device in download mode.

Thankyou Dr.Ketan and eug3n91
worked after i switched to the onboard USB.
i guess thats probably why Kies failed too....
this site is fantastic, been a lurker for a while, but never needed to post until today and its proven to be very succesful with both of you helping out so quick.
cant thankyou enough!

Dr.Ketan I am facing the same problem and did exactly the same but this is all i get
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.bin
<ID:0/015> cache.img
<ID:0/015> factoryfs.img

same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893

ow1166 said:
same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893
Click to expand...
Click to collapse
I'm afraid this has to do with corrupted memory partitions. It's what devs called 'superbricks' if I'm not mistaking...
You could try a ROM with a PIT file, hoping that would repartition any bad sectors.
Again, I could be mistaken. Try to read some other threads around here. A lot of.others have also encountered this problem

khok3893 said:
<ID:0/015> factoryfs.img
Click to expand...
Click to collapse
When you stuck at factoryfs.img = system partition corrupted

I tried with PIT file (Q1_20110914_16GB.pit) and ICS LYP Rom and it stucks on "NAND WRITE START" that comes after "factoryfs.img" I even uses "re-partition" in Odin. Nothing works.....

[SOLVED] Can't install for latest CWM recovery and CM

Hello all, I'm new.
Last night, I've already flashed to ClockworkMod recovery (5.8.1.8) after following the instruction from wiki, then I formatted all for data, cache, preload and sdcard (except emmc), and then also I tried to download latest version of ClockworkMod recovery and CyanogenMod stable or nightly builds for her Samsung Galaxy Note (GT-N7000) phone.
The biggest problem before I tried to install for stable or latest nightly builds of CyanogenMod, but it doesn't work due for asserting failure (the console log shows 'assert failed: getprop("ro.product.device") == "galaxynote"') as in status 7 of error.
And then, I can't install for latest ClockworkMod recovery while freezes and the message says "Replacing stock recovery with ClockworkMod recovery".
I need to teach for how to install, but could you please help me?
(Note: Sorry for bad English, but I could not understand anymore.)

You can't install recovery directly.. You need to use a custom kernel like Philz or Speedmod. Then you can go about cleaning and wiping.

nokiamodeln91 said:
You can install recovery directly.. You need to use a custom kernel like Philz or Speedmod. Then you can go about cleaning and wiping.
Click to expand...
Click to collapse
I've already cleaned and wiped for her's phone, and then I tried to install for latest Philz' CWM recovery, but what happens... it doesn't work.
So here is the recovery console log.
Code:
This package is for 'galaxynote,n7000,N7000,GT-N700' devices; this is a ''.
E: Error in /emmc/philz_touch_6.07.9-n7000.zip
(Status 7)
Installation aborted.

GrandChaos9000 said:
I've already cleaned and wiped for her's phone, and then I tried to install for latest Philz' CWM recovery, but what happens... it doesn't work.
So here is the recovery console log.
Code:
This package is for 'galaxynote,n7000,N7000,GT-N700' devices; this is a ''.
E: Error in /emmc/philz_touch_6.07.9-n7000.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I meant to say you CANT install recovery directly.
If that does not work then use Philz kernel that's is a tar.md5 file and use Odin to flash on PDA.

Flash philz ((kernel)) from this thread:
http://forum.xda-developers.com/showthread.php?t=1901191
Then you're good to go.

nokiamodeln91 said:
I meant to say you CANT install recovery directly.
If that does not work then use Philz kernel that's is a tar.md5 file and use Odin to flash on PDA.
Click to expand...
Click to collapse
I switched to Windows 7 after boot selection (I have a triple boot with my Debian-based distro, Ubuntu and Windows 7), running/downloading older to latest Odin3, power on to download mode, and then connect into my computer, but it won't appear in the yellow box of USB ID COM after installed/replaced the drivers from zadlg.

Anyone?

GrandChaos9000 said:
Anyone?
Click to expand...
Click to collapse
try installing driver from here.. Once installed connect the phone in normal power on mode and then let windows install the drivers...

nokiamodeln91 said:
Once installed connect the phone in normal power on mode and then let windows install the drivers...
Click to expand...
Click to collapse
Okay... but now what?

GrandChaos9000 said:
Okay... but now what?
Click to expand...
Click to collapse
Then boot into download mode and flash Philz kernel from there... Philz tar.md5 file selected in PDA and phone in download mode.

nokiamodeln91 said:
Philz tar.md5 file selected in PDA and phone in download mode.
Click to expand...
Click to collapse
Is it both all in PDA and phone before installing?

GrandChaos9000 said:
Is it both all in PDA and phone before installing?
Click to expand...
Click to collapse
It is just in PDA, he is saying to put the phone in download mode by pressing volume down+power+home button to be able to do that.

PDA and phone won't install due in the red box of failure, so here is my log.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-n7000.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: I've removed anti-virus and Kies (except for mobile drivers), but it failed again.

Anyone how to resolve this?

It seems you keep flashing PhilZ recovery. Don't do that. You need to flash PhilZ kernel which inlude recovery in it. Download from here latest one.
http://forum.xda-developers.com/showthread.php?p=31911620
Sent from my GT-N7000 using Tapatalk 2

U come from where? Gingerbread/ics/jb n what baseband u use
Phone status
Gingerbread
Ics
Jb?
Baseband?
Make sure philz kernel is compatible u device
GrandChaos9000 said:
PDA and phone won't install due in the red box of failure, so here is my log.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-n7000.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

AMUK0110 said:
Phone status
Gingerbread
ICS
JB?
Baseband?
Click to expand...
Click to collapse
Uhm... Jelly Bean 4.1 Stock with apps in Germany about her phone.

U baseband?
Etc
GrandChaos9000 said:
Uhm... Jelly Bean 4.1 Stock with apps in Germany about her phone.
Click to expand...
Click to collapse

AMUK0110 said:
Your baseband?
Click to expand...
Click to collapse
N7000XXLSA in baseband version I guess...

And finally, I installed Philz CWM recovery (Version 5.15.0 - CWM base version 6.0.3.7) and it works for XXLTA-ATL baseband instead.
So here is my another log.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.15.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)

Samsung GT-N8020 bricked ???

Hello everyone,
I got the old tablet of my gf, because it crashed and now it does not reboot. Samsung says it would cost 200$ to repair it, so she bought a new one.
GT-N8020 (T-Mobile Germany)
1. When I turn on the tablet -->I get a crashed screen. (just grey) Same when I hold VolumeUP +Power
2. When I press Volume down + Power --> I get into Odin Mode and it says Downloading... --> nothing happens from then on.
(Odin Mode, Custom Binary Download: No, Current Binary: Samsung Official, System Status: Custom)
3. Now I installed Odin on my Windows PC, Downloaded the Firmware and also a pitfile from the forum. I connected my tablet and it was accepted by Odin. So I loaded the PDA and Pit. Without Pit it says Fail! There is no PIT partition. With .pit file it says:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020XXUDNI2_N8020DTMDNJ1_N8020XXUDNJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried Odin 3.09 and Odin 1.7.
I tried it with and without Re-partition checkbox
I tried pit file for N8020 and 8000
Is there any option I have left ?!?
Would be nice if anyone has some tips for me!
Thanks in advance!
Jan

Hey bro install cwm recovery or TWRP through Odin then load any compatible rom through recovery mode.
Sent from my SM-J500F using XDA Forums

Xtereme Developer said:
Hey bro install cwm recovery or TWRP through Odin then load any compatible rom through recovery mode.
Sent from my SM-J500F using XDA Forums
Click to expand...
Click to collapse
Thanks for the answer. But when I tried "fastboot flash recovery recovery.img" its waiting for the device all the time. All drivers etc. installed.
Any further help for me?

Last opition visit service centre pay some $ and get ur gadget repared

Unable to flash rom after failed update on Kies

Hey guys I am was going from rooted 4.4 to 5.1.1 and running the dynamic kat rom...I downgraded to stock 4.4 and attempted to update through Kies...well the update hung at 87% for a long time and eventually failed, I got the "system encounted a firmware issue " error and was unable to restart...Kies will not recognize my note no matter how many times I flash the drivers and Odin always fails no matter the version I try to flash...Even SmartSwitch says "device failed to recognize", and I cannot flash twrp either (I even tried flashing PIT files which failed as well) (I still get a "comm4" connection in odin)
(4.4/5.0.1) <ID:0/004> Added!!
<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..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn

Had a similar issue too. Do an emergency recovery from kies. it will download latest stock firmware restore.

Kies cannot see my phone and I get odin error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABO when I try to flash ANY rom

m33android said:
Kies cannot see my phone and I get odin error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABO when I try to flash ANY rom
Click to expand...
Click to collapse
Have you tried a full internal wipe from recovery?
maybe retry 4.4.4 through ODIN and then moving forward?
up to date on modem/bootloader?
also, sometimes flashing in ODIN just fails for no apparent reason. when it does, you must unplug the phone, reboot the phone and enter bootloader mode again every time.