Hello guys,
This device was my grandpa's gaming device (Candy Crush) so it has a emotional value.
What do I have:
Hardware:
> GT-N8010 Brazilian version (ZTO)
What is in it:
> Any alpha version of Lineage*
> CWM Recovery v6.0.1.1
* I don't remember what version of Lineage is (but I think it's 14.1 ) because I flashed it a few years ago when rom development for this device was almost dead, and this one I found was an alpha version, but it worked until a beautiful day, when bootloops occured and Unsuccessful Encryption screen showed its face.
The Reset Tablet button on Encryption Screen does nothing.
I'm able to boot on Recovery mode but I can't mount /data, /cache, etc.
I'm able to mount /system but I can't format it due to error.
Code:
Formatting /system...
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
Error formatting /system
I can't mount SDCARD or access it over PC connection.
What have I done so far:
Tried multiple flashes over Odin, using diferent versions of Odin (from 3.04 to the latest build);
More than one PC/USB Ports/Cables;
I also bought a new docker port but I still waiting to be delivered;
What I've tried to flash:
> Brazilian (ZTO) Stock ROM Kies Home type (Single File)
> Recovery Firmwares (Multiple files type BL+AP+CSC file)
> Pit file
> Some TWRP versions as well CWM 6.0.3.0
> Re-partition
All the times I tried I had succeed 1 / failed 0 / PASS! results in Odin, but when I boot the device it's the same.
Some times it bootloops on Lineage bootloader, some others on Unsuccessful Encryption screen.
So no changes at all.
Also, the loading bar appears on the device when Odin is flashing system.img.
Status on Download mode (Even after "successful flash"):
ODIN MODE
PRODUCT NAME:GT-N8010
CUSTOM BINARY DOWNLOAD: no
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
For example:
>> Multiple FIles Flash Odin 3.14 BL+AP+CSC
Code:
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1789 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
>> Single File Flash Odin 3.07 KIES HOME
Code:
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> sboot.bin
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I appreciate any new Ideas, have a nice day you all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mandatti said:
Hello guys,
This device was my grandpa's gaming device (Candy Crush) so it has a emotional value.
What do I have:
Hardware:
> GT-N8010 Brazilian version (ZTO)
What is in it:
> Any alpha version of Lineage*
> CWM Recovery v6.0.1.1
* I don't remember what version of Lineage is (but I think it's 14.1 ) because I flashed it a few years ago when rom development for this device was almost dead, and this one I found was an alpha version, but it worked until a beautiful day, when bootloops occured and Unsuccessful Encryption screen showed its face.
The Reset Tablet button on Encryption Screen does nothing.
I'm able to boot on Recovery mode but I can't mount /data, /cache, etc.
I'm able to mount /system but I can't format it due to error.
Code:
Formatting /system...
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
Error formatting /system
I can't mount SDCARD or access it over PC connection.
What have I done so far:
Tried multiple flashes over Odin, using diferent versions of Odin (from 3.04 to the latest build);
More than one PC/USB Ports/Cables;
I also bought a new docker port but I still waiting to be delivered;
What I've tried to flash:
> Brazilian (ZTO) Stock ROM Kies Home type (Single File)
> Recovery Firmwares (Multiple files type BL+AP+CSC file)
> Pit file
> Some TWRP versions as well CWM 6.0.3.0
> Re-partition
All the times I tried I had succeed 1 / failed 0 / PASS! results in Odin, but when I boot the device it's the same.
Some times it bootloops on Lineage bootloader, some others on Unsuccessful Encryption screen.
So no changes at all.
Also, the loading bar appears on the device when Odin is flashing system.img.
Status on Download mode (Even after "successful flash"):
ODIN MODE
PRODUCT NAME:GT-N8010
CUSTOM BINARY DOWNLOAD: no
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
For example:
>> Multiple FIles Flash Odin 3.14 BL+AP+CSC
Code:
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1789 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
>> Single File Flash Odin 3.07 KIES HOME
Code:
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> sboot.bin
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I appreciate any new Ideas, have a nice day you all.
View attachment 5741025
View attachment 5741027
Click to expand...
Click to collapse
I'm really sorry to tell you that your eMMC is locked.
If the devices stay's at the same state after flashing...
In this case the eMMC needs to get replaced, I've done this about 200 times on this tablet, the eMMC itself is not too expensive, IDK if a repair shop does this in your country, we are still doing it.
You also could buy a used mainboard or a used device, but consider that this eMMC is also used and will die someday.
html6405 said:
I'm really sorry to tell you that your eMMC is locked.
If the devices stay's at the same state after flashing...
In this case the eMMC needs to get replaced, I've done this abouht 200 times on this tablet, the eMMC itself is not too expensive, IDK if a repair shop does this in your country, we are still doing it.
You also could buy a used mainboard or a used device, but consider that this eMMC is also used and will die someday.
Click to expand...
Click to collapse
I'm curious why would the eMMC suddenly lock itself?
joseph15two said:
I'm curious why would the eMMC suddenly lock itself?
Click to expand...
Click to collapse
Thats the common EOL behaviour of the klmag2ge4a-a002 eMMC firmware,
you can read it in the data sheet.
It could be that it detected that it were running out of reserve blocks.
html6405 said:
Thats the common EOL behaviour of the klmag2ge4a-a002 eMMC firmware,
you can read it in the data sheet.
It could be that it detected that it were running out of reserve blocks.
Click to expand...
Click to collapse
Oh that's interesting. Thanks for the info!
html6405 said:
I'm really sorry to tell you that your eMMC is locked.
If the devices stay's at the same state after flashing...
In this case the eMMC needs to get replaced, I've done this about 200 times on this tablet, the eMMC itself is not too expensive, IDK if a repair shop does this in your country, we are still doing it.
You also could buy a used mainboard or a used device, but consider that this eMMC is also used and will die someday.
Click to expand...
Click to collapse
got this error with my tablet a long time ago, flashed stock and then lineageos 16 and all is ok
Fixes do vary but dead EMMC been on the forum since month one .
w_tapper said:
got this error with my tablet a long time ago, flashed stock and then lineageos 16 and all is ok
Click to expand...
Click to collapse
I don't believe that you've read the previous post carefully.
He's flashing the stock ROM and still LineageOS boot's up,
this show's for 100% that the eMMC is locked and read only.
In such a case a fake flashing is nearly always possible, but doesn't change anything on the device.
You really have to replace the eMMC like here:
Samsung Galaxy Note 10.1 eMMC replacement | Hier bekommt ein Samsung Galaxy Note 10.1 eine neue eMMC (intern verbauter Speicher), den Vorbereitungsprozess haben wir nicht gefilmt. (eMMC ablöten,... | By Mobile Hard & Software Solutions - Facebook
Hier bekommt ein Samsung Galaxy Note 10.1 eine neue eMMC (intern verbauter Speicher), den Vorbereitungsprozess haben wir nicht gefilmt. (eMMC ablöten,...
fb.watch
html6405 said:
I'm really sorry to tell you that your eMMC is locked.
If the devices stay's at the same state after flashing...
In this case the eMMC needs to get replaced, I've done this about 200 times on this tablet, the eMMC itself is not too expensive, IDK if a repair shop does this in your country, we are still doing it.
You also could buy a used mainboard or a used device, but consider that this eMMC is also used and will die someday.
Click to expand...
Click to collapse
Thank you!
That's what I was suspicious about...
Sad, I'll try to find a eMMC and try to replace it.
I'll post any updates if I have them.
EDIT: Do you have maybe where I can find a eMMC?
A link would be usefull.
I'm based on Germany.
mandatti said:
I'm based on Germany.
Click to expand...
Click to collapse
Thats great, then I could send you a pre-programmed eMMC from Austria, just contact me via PM.
html6405 said:
Thats great, then I could send you a pre-programmed eMMC from Austria, just contact me via PM.
Click to expand...
Click to collapse
Sent. (Y)
Related
Thanks to Atntpt that opened my mind. I've unpacked .Tar odin package of 5.1.1 and flashed something like modem,boot and recovery (adding .tar in the file names before flash them) one per time, then a custom kernel and last twrp, and the phone stops to reboot. Samsung Switch done the rest of the work. Hi guys, please help me, i'm working no stop on my phone from yesterday without a solution. Yesterday i've tryed to flash mm(Coming from noblerom installed without tripping knox with modified bootloader of 5.0) from the post in general. Flash of mm has fail with an error of a bootloader. then i've tryed to flash latest stock rom(not of my country), and gave me an error in flashing hidden.img, i've tryed to flash in odin, seems fine and phone boots but have no charge. attacched to charger the phone boots and shut down after 5 seconds.
Both recovery and download mode, works
in official recovery and twrp can't mount system
in official says
failed to mount '/system (invalid argument
If you know something about, please help me.
Log of odin flash
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
after hidden fails flash custom kernel via odin.. i should boot normaly..(will tip KNOX!!) that was the reason i tiped knok was unable to bypass that situation
Atntpt said:
after hidden fails flash custom kernel via odin.. i should boot normaly..(will tip KNOX!!) that was the reason i tiped knok was unable to bypass that situation
Click to expand...
Click to collapse
can you send me a link?
I'm glad I could help
Hello all,
My tablet note 10.1 N8000 (3G, Wi-Fi, 16 GB) suddenly got stuck in bootloop. I was not trying to flash anything when it did so, nor did I flashed anything recently before the bootloop (although it seemed to constantly freeze before the bootloop when trying to switch between my two whatsapp accounts that I have using Titanium Backup which allows creating more than one account in all apps).
I did however root the device when I bought it in 2012 and it was the only time I did so, and I still have USB debugging mode on.
The device would bootloop in the first Samsung logo most of the time, but on rare occasions it would move to the second animated logo and get stuck repeating the animation forever.
I can only access Odin Download mode, but cannot access recovery mode (when I try to do so, it shows the first Samsung logo, then attempts to go into recovery but only shows a lit black screen then reboots).
Here are the steps I did (might help some of you, but unfortunately didn't help me):
1) I tried flashing a custom recovery (CMW, Philz touch, TWRP, and stock recovery) through Odin (Odin 3 version v3.10.6):
- Put the .tar file in AP slot then put device in download mode (power key + volume down), then plug device into my computer.
- Check only auto restart and F. time reset.
- Here's what it says after flashing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
2) I tried flashing stock rom through Odin:
(Roms I tried: N8000XXCMF1, N8000XXUDOF1, N8000XWALG7, N8000XXCMA2, N8000XXUDOF1)
- I put the .tar.md5 file in AP and follow same steps above, here's what Odin says after flashing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
3) I tried following the post here:
http://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923
I followed everything until the part where I have to access recovery (because I could not access recovery still to flash rom from recovery). Here's what it says in Odin after it's done:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300_Repair_efs.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> efs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But again it did not work even though it always says "PASS"! And I also tried flashing stock rom after trying this method through Odin, shows success but still stuck in bootloop.
I don't know what else to try really. I will not take it to support to fix it, either I fix it myself or use it as a cutting board.
If anyone has any ideas please reply. I'm sure there are more things to try.
EDIT:
- Is there a way to clear cache without accessing recovery (since I can't access it)? Lots of people say it worked after clearing cache.
- Is Nand erase all an option? I wish someone would explain it in details instead of telling me not to do it without saying exactly why.
- Could the problem be in hardware? How can I know if so?
NaND ERASE WILL KILL THE PRODUCT .
JJEgan said:
NaND ERASE WILL KILL THE PRODUCT .
Click to expand...
Click to collapse
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/
No help?
RHAddict said:
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/
Click to expand...
Click to collapse
Odin is a tool that we are able to borrow .
You could try recovery via KIES .
RHAddict said:
No help?
Click to expand...
Click to collapse
HI RHAddict,
It happened to my Note GT-N8000, if a Hardware failure. If you send to SAMSUNG service center it will cost u around US$ 200 for motherboard replacement. But i manage to find a mobile service center, the technician said it only 1 of the chip in motherboard out of service. I got my tablet fixed just US$ 50-60. Now is working as is it before.
TQ
My Samsung 8010 has just gone exactly the same way. Cannot enter recovery mode, just get a blank lit screen for a second then goes back into a reboot cycle and never gets past the Samsung logo. Did you get anywhere with fixing it, or have you given up? Was thinking of taking mine to a service centre, but probably not worth it?
Followed all tutorials and did some specific research but failed.
I downloaded the gt-s7582 official firmware, drivers, and all were successfully installed and flashed but still encountered firmware upgrade error.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> BcmCP.img
<ID:0/003> dt-blob
<ID:0/003> cache.img
<ID:0/003> system.img
<ID:0/003> hidden.img
<ID:0/003> param.lfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
Please..
Hello,
Are you certain that you have the correct firmware for your model number, carrier and region?
Try finding a copy of the PIT file for your model, maybe someone else with your device can help you with that.
Was/is USB debugging turned on in developer options?
Can you boot to stock recovery and factory reset and wipe cache partition, then flash the stock firmware via Odin.
Does your device have a locked bootloader? If so then you'll have to flash the same stock firmware the device had before the issues or a newer firmware, flashing an older version than what you already had probably won't work.
same problem with my device
So I'm trying to reset my phone(regular S8 but hoping if someone else had the same issue the fix might be the same) as a bad rom flash caused some sort of issue and couldn't get back into twrp "official binaries only"
Find latest firmware for my csc (which was july) doesnt work, I thought it might have been a BL issue as I had the august patch through a custom rom, found a different csc which was from august, and I get the same error
I also no longer get the official binaries only, just a bootloop of "An error has occurred while updating....use emergency recovery function in smart switch" which I also tried, no luck, but I can still get into download mode
Using most recent odin, official cable, updated usb firmware and such and am running as admin. Have tried different ports too, but it always fails at same step
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5716 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone also says SW REV CHECK FAIL (Bootloader) Device 5, Binary: 4 after failed ODIN install
Any Ideas? Thanks
ACardAttack said:
So I'm trying to reset my phone(regular S8 but hoping if someone else had the same issue the fix might be the same) as a bad rom flash caused some sort of issue and couldn't get back into twrp "official binaries only"
Find latest firmware for my csc (which was july) doesnt work, I thought it might have been a BL issue as I had the august patch through a custom rom, found a different csc which was from august, and I get the same error
I also no longer get the official binaries only, just a bootloop of "An error has occurred while updating....use emergency recovery function in smart switch" which I also tried, no luck, but I can still get into download mode
Using most recent odin, official cable, updated usb firmware and such and am running as admin. Have tried different ports too, but it always fails at same step
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5716 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone also says SW REV CHECK FAIL (Bootloader) Device 5, Binary: 4 after failed ODIN install
Any Ideas? Thanks
Click to expand...
Click to collapse
You are trying to downgrade from bootloader 5 to 4 (see here Device 5, Binary: 4 )which it wont let you. download firmware with bootloader 5
Here's what I did from start
Installed TWRP
installed lineage 17.1 with gapps and magisk
Removed everything and installed pixel experience 10 herolte
Volte was not working in both
So I downloaded the stock firmware (latest) according to my model - G930FD INS and tried to flash it through odin as per steps
But
The log gets stuck on 'SYSTEM.IMG' and after a while fails to flash the phone.
I just want to get my stock firmware back so I can start my calls and msgs.
Please help.
I didn't used anything different just clean flashed my phone.
I have the latest firmware for stock
log file
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4077 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Solved
As the problem was, while flashing with Odin it wasn't showing any error and was only giving out output as Fail, turns out it was a port problem, I changed my USB port and cable and it worked fine. My friend also gave me advice to try it on another laptop because this happens sometimes and sometimes it works.
So if your log is something similar to what I have posted try downloading the latest Odin and changing ports or PCs, if nothing then create an id here and start a thread somebody will help you out for sure.
Peace