Database Info

my phone is not flashing via odin also

first i have reboot the phone and install the creed 3.5 via stock recovery and then the phone is only showing the creed text on display till 15-20 min.then i install the original anroid 2.3.6 with odin but phone is not working and now phone is not going in recovery mode its only going in the downloading mode .And i try by multi file os 2.3.6 from odin but it also not working is only go to download mod but nothing happen.
i also try to select all the debug options in odin but now it shows this error -
Uploaded with ImageShack.us
in odin, it stuck at
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> APBOOT_S5670XWKTI_CL1006640_REV01_user_low_true.tar.md5 is valid.
<OSM> CODE_S5670XWKTI_CL1006640_REV01_user_low_true.tar.md5 is valid.
<OSM> MODEM_S5670XWKT6_CL1006640_REV01.tar.md5 is valid.
<OSM> GT-S5670-csc-DBTKT1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..

Done with ODIN "ops" file and one package option.
but i need to know what was the error in above SS?

It seems u r using old odin version (seeing from screenshot ie 3) use latest versn 4.8 n one more thing if its stuck at setup conn der mgt be prblm wid ur usb port chnge it n check if dat works..

Reinstall FROYO
Please flash FROYO (four package) installation. download from samfirmware and flash with the lastest ODIN from samfirmware. Check the guide on that site. Place all the files in proper links and flash it. Reboot the system. then flash Gingerbread.

it's okay you have to flash froyo 1st =D

ya flash multipackage froyo first

i had same problem try to flash phone via 4 pakage mode rather than the one package mode .... go to samfirmware nd download a firmware nd place all the four files in it in proper places nd flash ... chck out the guide to flashing in samfirmware.com..
Sent from my GT-S5670 using XDA

[Q] P3100 only booting to Stock Recovery & not CWM?

Unlocking GT-P3100 Bootloader - Help Needed
Hi All,
I was able to load the CWM recovery image through ODIN, below is the trace of the image download through ODIN:
=================================
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> recovery.img
<ID:0/021> NAND Write Start!!
<ID:0/021> RQT_CLOSE !!
<ID:0/021> RES OK !!
<ID:0/021> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/021> Removed!!
===============================
However, when I go to recovery menu , I'm not seeing CWM menu & only seeing "Android System Recovery (3e)".
A friend of mine suggested my boot loader needs to be unlocked.
Reading google it seems when we switch to download mode & connect to USB on PC, using ADB command "fastboot oem unlock" it should be done.
But the command is < Waiting for a device > , I can see "adb devices" reporting valid entries when in download mode.
Any suggestions....how to get CWM working ?
My Build # IML74K.P3100DDALE1
ICS 4.0.3
Want to get it rooted to install Chainfire3D to play some games with this Tablet.
Please help!

I was just messing around with wrong recovery image....
Grab this one http://imnuts.net/JxMIGa ( 9.4MB ) used ODIN 1.85 works 100%
My Flash count is now 5.
Got CWM Recovery installed OK & SuperUser app is now showing as well.
Time to install Chainfire3D on this GT-P3100 & enjoy some quality gaming
Confirmed 100% working.

How did you root it
Sent from my GT-P3100 using Tapatalk 2

[S5301][GUIDE]how to root the Galaxy Pocket Plus S5301

Hi Evryone.
Until somebody will release CWM Recovery or any root method for the galaxy pocket plus, I managed to create a pre-rooted firmware.
This firmware base on the last build for S5301, is a full firmware exactly like the original, except the root.
after flash you will see the SuperSU app in the app drawer.
flashing this firmware do not doing wipe data. you will not lose anything.
also, this flash not increase your download binary count.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
base on - XXAMC1.
PDA - S5301XXAMC1
PHONE- S5301XXMC1
CSC- S5301SERAMB1
Android version: 4.04
Download
https://mega.co.nz/#!qQ8B2BxZ!fhAggBRAzvsPzYejncA_Zlbkf-9r6UhPGU1BBYlbHqw
Installation instructions
install samsung usb drivers from here.
Download the 7z file above and extract it (with winrar or 7z) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in pda.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
Enjoy
If you want to thank me for this work, you can do this by donating.. :good:

thank you very much
I'll try it but does it has Arabic language ??

I don't remember, but i think it does.

Don't work to me, apear modem error and stop odim
Here Odim check
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5301XXAMC1_S5301SERAMB1_S5301XXMC1_HOME_ROOTED.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> BcmCP.img.md5
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

dragaoheremita said:
Here Odim check
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5301XXAMC1_S5301SERAMB1_S5301XXMC1_HOME_ROOTED.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> BcmCP.img.md5
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Confirm that Kies is not running.

panda00 said:
Confirm that Kies is not running.
Click to expand...
Click to collapse
Kies is ok, im put back my phone with odin 3.07, and recovery.

Can anyone help me pls?
Is there any custom rom or if i root the phone can i disable that fuction?
http://forum.xda-developers.com/showthread.php?p=44391342#post44391342http://forum.xda-developers.com/showpost.php?p=44391342&postcount=1

avicohh said:
Hi Evryone.
Until somebody will release CWM Recovery or any root method for the galaxy pocket plus, I managed to create a pre-rooted firmware.
This firmware base on the last build for S5301, is a full firmware exactly like the original, except the root.
after flash you will see the SuperSU app in the app drawer.
flashing this firmware do not doing wipe data. you will not lose anything.
also, this flash not increase your download binary count.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
base on - XXAMC1.
PDA - S5301XXAMC1
PHONE- S5301XXMC1
CSC- S5301SERAMB1
Android version: 4.04
Download
https://mega.co.nz/#!qQ8B2BxZ!fhAggBRAzvsPzYejncA_Zlbkf-9r6UhPGU1BBYlbHqw
Installation instructions
install samsung usb drivers from here.
Download the 7z file above and extract it (with winrar or 7z) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in pda.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
Enjoy
If you want to thank me for this work, you can do this by donating.. :good:
Click to expand...
Click to collapse
Dear @avicohh
Can i return back to my stock rom? If yes then how???
reply plzzzz

Yes.
Just flash stock rom.
Sent from my Nexus 5 using Tapatalk

SM-G930F bricked and can't load stock ROM

I am trying to flash a stock ROM onto my SM-G930F using Odin3 v3.10.7 . I am in the United Kindom and the phone is H3G. I have tried 3 different ROMS from sammobile but none will flash onto the device. I can now only get into download mode.
On the device it says
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWREV: B:1 K:0 S:0
None of the text on the phone changes whilst flashing.
The log on Odin is:
<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> 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> 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> 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/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> 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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I have also tried using the "Firmware and initialization" tool in Samsung Kies 3 but get the error "failed to upgrade firmware due to an unexpected error".
Any help would be greatly appreciated.

Tried different usb cable? (Especially try the one that came with your phone)
Tried a different USB port? (no hub in between)
Tried different drivers?
Tried different computer?
edit: maybe this works: http://androidforums.com/threads/resolved-soft-bricked-cant-flash-with-odin.473420/

LowLatency said:
Firstly, I know this is posted under S7 Edge but couldn't find a Q&A topic for the S7.
I am trying to flash a stock ROM onto my SM-G930F using Odin3 v3.10.7 . I am in the United Kindom and the phone is H3G. I have tried 3 different ROMS from sammobile but none will flash onto the device. I can now only get into download mode.
On the device it says
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWREV: B:1 K:0 S:0
None of the text on the phone changes whilst flashing.
The log on Odin is:
<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> 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> 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> 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/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> 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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I have also tried using the "Firmware and initialization" tool in Samsung Kies 3 but get the error "failed to upgrade firmware due to an unexpected error".
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi mate
Did you unlock your bootloader? , try it with a newer Odin
check this thread , there are step by step instructions
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431

MAX 404 said:
Hi mate
Did you unlock your bootloader? , try it with a newer Odin
check this thread , there are step by step instructions
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
Click to expand...
Click to collapse
How do I unlcok the bootloader? Is this by turning on developer options? I couldn't access the settings so was unable to do this if so.

LowLatency said:
How do I unlcok the bootloader? Is this by turning on developer options? I couldn't access the settings so was unable to do this if so.
Click to expand...
Click to collapse
Unlocking the bootloader is when you go into your SETTINGS/ABOUT DEVICE and tap the build number until you get a message that you have unlocked the developer options. You then back out of ABOUT DEVICE and enter DEVELOPER OPTIONS and enable OEM UNLOCK. Did you do any of that?

I think this may be progress. My phone now boots into Recovery where at the top it says:
Android Recovery
MMB29K.G930FXXU1APC8
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1APC8
user/release-keys
I think this is showing a ROM that I flashed onto it in an attempt to fix the problem but it didn't work.
Then has all the options for recovery.
At the bottom it says
Supported API: 3
dm-verity verification failed...
E:failed to mount /system (Invalid argument)
I have tried a few different ROMS that I have on my computer through Odin v3.11.1 (I believe the newest version) but to no avail.
As you can probably tell, I'm not 100% sure what I am doing but have worked out that it is the main file that goes under AP in Odin that is the problem.
I am about to try the upgrade tool in Kies now I can get into recovery mode and see if that works.

kettir said:
Unlocking the bootloader is when you go into your SETTINGS/ABOUT DEVICE and tap the build number until you get a message that you have unlocked the developer options. You then back out of ABOUT DEVICE and enter DEVELOPER OPTIONS and enable OEM UNLOCK. Did you do any of that?
Click to expand...
Click to collapse
I hadn't done this no, because the phone bricked whilst I was updating it through Kies. After the update failed I couldn't get back into the phone at all other than "download mode" so this wasn't an option.

Update!
My phone still won't update through Kies. I'm still getting the same error message

LowLatency said:
I think this may be progress. My phone now boots into Recovery where at the top it says:
Android Recovery
MMB29K.G930FXXU1APC8
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1APC8
user/release-keys
I think this is showing a ROM that I flashed onto it in an attempt to fix the problem but it didn't work.
Then has all the options for recovery.
At the bottom it says
Supported API: 3
dm-verity verification failed...
E:failed to mount /system (Invalid argument)
I have tried a few different ROMS that I have on my computer through Odin v3.11.1 (I believe the newest version) but to no avail.
As you can probably tell, I'm not 100% sure what I am doing but have worked out that it is the main file that goes under AP in Odin that is the problem.
I am about to try the upgrade tool in Kies now I can get into recovery mode and see if that works.
Click to expand...
Click to collapse
Hi mate
First of all "OEM unlock" is not necessary to odin flash a stock rom...please forget i said it
The issue seem that is caused by dm-verity verification failed , same symptoms .. keeps device in boot loop ( Samsung Logo) , not sure yet what the solution is i seem lots of threads about it on S6 and Note 5
Check this thread:
http://forum.xda-developers.com/showpost.php?p=66605862&postcount=48
@CuBz90 with a S7 had the same problem and mention it did not work........maybe he can help out
In the same thread they suggested this..you could try it ..just in case
http://forum.xda-developers.com/showpost.php?p=67217747&postcount=52
Only thing i got for now......

With frp lock on and drm error. There is no way around it at the moment.
Sent from my SM-G935F using Tapatalk

CuBz90 said:
With frp lock on and drm error. There is no way around it at the moment.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks for replying mate
Bad news indeed......in your case you had knox bit tripped off?
I see that twrp recovery
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Has a
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
I know it means to trip knox , but i wonder if it would help

MAX 404 said:
Thanks for replying mate
Bad news indeed......in your case you had knox bit tripped off?
I see that twrp recovery
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Has a
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
I know it means to trip knox , but i wonder if it would help
Click to expand...
Click to collapse
No because with frp on you cannot flash twrp
Sent from my SM-G935F using Tapatalk

CuBz90 said:
With frp lock on and drm error. There is no way around it at the moment.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
How annoying, hopefully somebody finds a fix soon

LowLatency said:
How annoying, hopefully somebody finds a fix soon
Click to expand...
Click to collapse
Just one thing I noticed in your posts, you refer to Kies 3 if you are trying to do it with Kies 3 this isn't compatible with the S7, if you don't need it uninstall it and install Samsung Smart Switch, this will install the correct drivers for the S7, you may be able to get the Initialization and Recovery process to work then.
The problem with Odin is if you don't have USB Debugging enabled it wont work, also you system status says Custom this can prevent Smart Switch from working as well but give it a try you have nothing to lose

I have the same problem.
What damages drk?

ag4751 said:
Just one thing I noticed in your posts, you refer to Kies 3 if you are trying to do it with Kies 3 this isn't compatible with the S7, if you don't need it uninstall it and install Samsung Smart Switch, this will install the correct drivers for the S7, you may be able to get the Initialization and Recovery process to work then.
The problem with Odin is if you don't have USB Debugging enabled it wont work, also you system status says Custom this can prevent Smart Switch from working as well but give it a try you have nothing to lose
Click to expand...
Click to collapse
Still no luck using Smart Switch, I get the same error message as with Kies.
As you say, it was worth a try, so thanks!

Anyone have a fix for this? I ran into the same thing. Mistakenly (like an idiot) reset all of my settings before using Flashfire to flash an OTA update. The result is the same as the OP. Tried using Odin to flash stock, running into failures and the same dm-verification problem.

bump

I semi bricked mine not long ago I just put it in download mode plugged it in to my win 10 laptop and flashed twrp with ordinary then flashed stock rom
Sent from my SM-G930F using Tapatalk

I cannot flash anithing. All tries ended up in a fail. (Complete write operation fail).
Looks like the samsung protection blocked the Boot.

Gt-n8000 stuck on samsung 10.1 screen

Try flash via odin show fail..ALREADY VIEW ALOT YOURTUBE AND XDA..NOT FIX.. PRESS POWER + VOL BUTTON CAN'T ENTER RECOVER MODE. OR EMMC CHIP SPOIL? THANK
Pls help.

One use the report button and ask a mod to move the post to the correct section .Q&A
Try flash via odin show fail
What fail .
What are you flashing ??

JJEgan said:
One use the report button and ask a mod to move the post to the correct section .Q&A
Try flash via odin show fail
What fail .
What are you flashing ??
Click to expand...
Click to collapse
Because keep stuck on samsung logo. Can't go into recovery mode too. Suspect firmware corrupt. Fail show at 1st pic there Sboot.bin. So try re-flash stock rom, one of my htc problem like this after flash phone work as normal.
Some say this due to EMMC chip issue.
Pls help.

Try flashing a full firmware .
Full as in a single file

JJEgan said:
Try flashing a full firmware .
Full as in a single file
Click to expand...
Click to collapse
All already try. The pic 'FAIL" red color show in odin is single file(full firmware).
This case similar like my other HTC keep reboot in logo, htc after flash work as normal.
Alot of people facing same issue too, search around forum still unable to fix. Probably emmc.

Usual for Emmc fail is Odin fails at Nand write.
Sent from my SM-N930F using XDA-Developers Legacy app

JJEgan said:
Usual for Emmc fail is Odin fails at Nand write.
Sent from my SM-N930F using XDA- Legacy app
Click to expand...
Click to collapse
This note already problem quite some time, before that show the error below, at NAND Write start, so is EMMC problem, need replace the chip?
Also the battery charging bar not running, previously when charge will show the battery bar running.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDPB1_N8000LUXDPB1_N8000XXUDNH1_HOME.tar.md 5 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..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

This note already problem quite some time, before that show the error below, at NAND Write start, so is EMMC problem, need replace the chip?
Probably but ask a service centre .

Enter in download mode and try to flash any recovery cwm, twrp or philz with odin. See if now you're able to boot into recovery mode.
Enviado do meu GT-I9301I através de Tapatalk

skyx1128 said:
Try flash via odin show fail..ALREADY VIEW ALOT YOURTUBE AND XDA..NOT FIX.. PRESS POWER + VOL BUTTON CAN'T ENTER RECOVER MODE. OR EMMC CHIP SPOIL? THANK
Pls help.
Click to expand...
Click to collapse
I have the same problem but mine shows a error at system.img.
View attachment 5290635
And When I power it through the adaptor it shows the charging symbol and then it turns off. (As shown in the above image).
This happen when it ran out of charge for a day since then its been stuck with this logo. (As shown above).

Wrong firmware sys.img.
Wrong size PIT file .

JJEgan said:
Wrong firmware sys.img.
Wrong size PIT file .
Click to expand...
Click to collapse
I appreciate your help but I am new to all this and if you can explain things in detail would be helpful.
I have worked on xiaomi phones before but they use adb & fastboot to flash things, so I am a beginner for the flashing of samsung devices.
I downloaded the files from samobile and one more from other source and they are for the correct model as well.
This log is of the file download from the other source and was a single file.
Odin Log:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 1764 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> system.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
This log is of the file download from samobile with four different files.
Odin Log:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 1765 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In a post similar to this, someone mentioned that device stuck on logo could be due to a corrupted kernel.

Firmware is tied to the 16 or 32 Gb memory , check yours first.

JJEgan said:
Firmware is tied to the 16 or 32 Gb memory , check yours first.
Click to expand...
Click to collapse
Mine is the 16GB model and the firmware is also correct.

Probable
Flash stock but still custom rom
Hi folks , I installed cyanogenmod rom to my Samsung Galaxy Note 10.1 (GT-N8005) a year ago. It stuck on boot animation. Then I flash stock rom via odin , it passed. But still stuck on cyanogenmod boot animation. Can anyone help ? How can I...
forum.xda-developers.com

JJEgan said:
Probable
Flash stock but still custom rom
Hi folks , I installed cyanogenmod rom to my Samsung Galaxy Note 10.1 (GT-N8005) a year ago. It stuck on boot animation. Then I flash stock rom via odin , it passed. But still stuck on cyanogenmod boot animation. Can anyone help ? How can I...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help but I already checked this link and many others but the conclusion was when the error occurs at "NAND write" step then the emmc chip was probably damaged but mine stops at a different step. And also if I replace the emmc wouldn't I lose the data?

[RECOVERY][OFFICIAL] TWRP 3.6.0_9 [N8000 N8010 N8020]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
try flashing this twrp recovery, note use odin 3.10.5, note disable auto reboot, in options, after sucess reboot recovery, click flash, and see how big the internal storage is. If no sucess flashing twrp recovery or internal storage = 0MB your emmc is fried, else you device still has life.
If your device still has life install this custom android(LineageOS is just the UI name, it is stable android)(follow the steps)(ask @html6405 for questions, I can only help you to here)
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com