G355HN flash problems with odin - Samsung Galaxy Core

G355HN flash problems with odin - Samsung Galaxy Core

Hello everyone,
My old phone starting to do some weird things: on power on, it doesn't respond. If I put it in charge, it reboots continuosly, by vibrating and showing the Samsung logo for a fraction of second. I don't know why.
I'm able to put it in download mode, but if I try to flash a stock rom, odin doesn't works.
I downloaded this rom from sammobile: G355HNXXU0AQA1_G355HNITV0AQA1_G355HNXXU0AQA1_HOME Italy Android 4.4.2
Putted into Odin 3.13 in the section AP, I tried to flash but the message was "There is no PIT Partition". Options enabled: "AutoReboot, F.ResetTime".
Second attempt: Options enabled: "AutoReboot, F.ResetTime and Re - Partition", same firmware. Result: operation failed.
Third attempt: changed the cable and the firmware, with: G355HNXXS0APH1_G355HNITV0APF1_G355HNXXU0APE1_HOME
It doesn't works. My log is:
<ID:0/005> 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/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1105 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
No pit file used during the procedure, only the firmware as AP.
Any help?
Thanks in advance

UP! Please, nobody?

Same problem
My odin do the same!!! Please help

Related

[Q] Stuck on SGS3 logo screen. Flashing fails.

UPDATE: I switched USB ports and it seems that it's now flashing...standby
UPDATE 2: All fixed.
Unhide for original post:
I think I need a bit of help. So last night busybox updated to the latest version (from the app). Now today when I go to start up my phone it starts up, but stays on the Galaxy S3 logo. I can boot into CWM recovery and download mode just fine. So I was attempting to flash (via Odin) back to stock so I could start fresh. I was following the advice from here: http://forum.xda-developers.com/showthread.php?t=1840030. And the bootchains flashed fine, but the root66.tar keeps failing.
This is the log I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_I535VRBMA2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am I doing wrong?
Also I was running a older build of SynergyROM if that's of any use.

[help] n8020 restarted alone & freez at logo & ODIN failed!!

oh my god!
what is happened?
it was at my side on the bed, not under usage. it did a restart .. alone .. and could not enter the system. it freez at logo!
i tried:
- to wipe, but could not help.
- get the last backup with cmw, but could not help.
- flash tle stock recovery with odin, but gone fail.
- flash a fresh stock room with odin, but gone fail.
- flash pit file with odin, but gone fail.
it can enter download and recovery modes.
what was happened?
i am not beginner and could help many people with much of problems, but .. this thing is totally new for me.
who can help please? i can not still without my note. i use it all the time, specially now where i am in a new country and city
so .... heeeeeeeeeeeeeeeeeelllllllllp
-------------- 1st update
wenn i try to flash stock recovery:
Code:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020-Stock-Recovery.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> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and wenn i try to flash stock rom 4.4.2:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020XXUDNE4_N8020VFGDNE1_N8020BUDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
-------------- 2nd update
I tried everything, but nothing could work.
At the end I tried to restore with the advance setting, because when I resore my CWM-backup, it stop at mount /system and can not do that. So, I did:
- restore boot --> work
- restore cach -- > don't work
- restore data -- > don't work, rebooted alone
- restore system -- > don't work

What is the ODIN fail message ??

JJEgan said:
What is the ODIN fail message ??
Click to expand...
Click to collapse
wenn i try to flash stock recovery:
Code:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020-Stock-Recovery.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> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and wenn i try to flash stock rom 4.4.2:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020XXUDNE4_N8020VFGDNE1_N8020BUDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)

is there maybe any methode mith ADB or any tool?

I tried everything, but nothing could work.
At the end I tried to restore with the advance setting, because when I resore my CWM-backup, it stop at mount /system and can not do that. So, I did:
- restore boot --> work
- restore cach -- > don't work
- restore data -- > don't work, rebooted alone
- restore system -- > don't work

Can't open the serial(COM) port
Google suggests USB cable problem or KIES? USB drivers .
http://forum.xda-developers.com/showthread.php?t=1622790
https://www.google.co.uk/search?q=a...source=hp&gfe_rd=cr&ei=zkMFVp7fCaux0wW8nKLoCw

but i work with other devices, also with this device before this problem

i deinstalled Kies and the driver, reinstaller the driver and tried again, but it is the same

no help
where to sell it as bricked of defect?

dercncplaner said:
no help
where to sell it as bricked of defect?
Click to expand...
Click to collapse
EBay and describe the problem .

Samsung Tab GT-N8010 Rom doesn't Install, PIT issue, Flashing Screen, do not turn ON
I have Samsung Tab GT-N8010
When I try to turn on, its screen flashing White for half second and then Black and Continuosly till the Battery End.
I try to Install ROM 4.4.2 with ODIN 3.10.7 and get this error
<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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried different PIT files including 3 different N8010.pit and 8013.pit and 8020.pit
but the issue remaining same
I read all the google search including Russian websites at-least but I couldn't find the issue
I have original cable

Solution
I know now the problem and the solution.
The problem: The flash memory on the mainboard is defect. This was the answer of Samsung Support Office.
The solution: The mainboard have to be replaced.
I am now in Turkey and here there is no N8020, but just a bad version (N8005) !!!
So, Samsung could not repair it for me. But I found everything I need for the repair on ifixit, also the board, B´but I could not collect the money for that, so maybe I wait or sell it. Here in turkey no one want to buy it because the phones here have to be registered and this costs much of money. hmm

Failed Root Resulting in Problems. Please Help.

So I went to root the phone and I did so with CF Auto Root. I went into Super Su and decided it was not what I was looking for. I was hoping for more of a GUI TWRP system and decided to unroot and factory restore the phone. I'm stressed to the point where i have no memory of how the phone got screwed up at this point. Here is what I do know.
When I power the device on normally it is frozen at the Samsung Galaxy S6 boot page and at the top it says KERNEL REV CHECK FAIL DEVICE 3 BINARY 2. Is this because I have the wrong firmware on the device? Is there any way I can get the bootloader, the firmware and everything else and just restore everything at once? Samsung Smart Switch fails to recover the device and I would absolutely love to do an emergency recovery, but it keeps asking for a code from a previous computer and I have no idea what it's talking about.
Any help would be appreciated.

jblevins1991 said:
So I went to root the phone and I did so with CF Auto Root. I went into Super Su and decided it was not what I was looking for. I was hoping for more of a GUI TWRP system and decided to unroot and factory restore the phone. I'm stressed to the point where i have no memory of how the phone got screwed up at this point. Here is what I do know.
When I power the device on normally it is frozen at the Samsung Galaxy S6 boot page and at the top it says KERNEL REV CHECK FAIL DEVICE 3 BINARY 2. Is this because I have the wrong firmware on the device? Is there any way I can get the bootloader, the firmware and everything else and just restore everything at once? Samsung Smart Switch fails to recover the device and I would absolutely love to do an emergency recovery, but it keeps asking for a code from a previous computer and I have no idea what it's talking about.
Any help would be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
There you go..

brenner650 said:
https://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
There you go..
Click to expand...
Click to collapse
I have already done this. It failed. I need help getting into Emergency Recovery. This is just Recovery.

jblevins1991 said:
I have already done this. It failed. I need help getting into Emergency Recovery. This is just Recovery.
Click to expand...
Click to collapse
Is your device SM-G920F?

forumber2 said:
Is your device SM-G920F?
Click to expand...
Click to collapse
It's the sm-g920t.

jblevins1991 said:
It's the sm-g920t.
Click to expand...
Click to collapse
So, your phone should be T-Mobile.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920T
Region: TMB (write XAR here if your phone is not T-Mobile variant)
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Downlaod" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.

forumber2 said:
So, your phone should be T-Mobile.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920T
Region: TMB (write XAR here if your phone is not T-Mobile variant)
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Downlaod" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
Click to expand...
Click to collapse
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> 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/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
This is the log when I tried your solution. Any ideas?

jblevins1991 said:
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> 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/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
This is the log when I tried your solution. Any ideas?
Click to expand...
Click to collapse
Try with another usb cable, another usb port or another PC.

I bought an official samsung charger and fixed it. I think the old charger was disconnecting during the smart switch initialization process.
Any way to fix knox?

S6 Stuck at Logo Screen, flashed new ROM twice with no change

Hello,
A bit of back story first - yesterday, my mother's Galaxy S6 (SM-G920F) suddenly rebooted to the device's logo screen ( the "Samsung Galaxy S6....powered by android" one) and it's been stuck there since. There had been no "tinkering" so to say with the device; debugging was disabled, the bootloader had not been tampered with at all, and all the updates were done through the official android route. The last major update was around a month ago, to Nougat from MM, after which I cleared the cache. The latest update was about 10 days ago, a minor Nougat one, but the cache had not been wiped.
Now down to business. The phone does not turn off at all. Holding the power button and the volume down just reboots it to the same screen. That being such, I cannot access recovery mode. I can however access Download Mode which makes be believe that all hope is not lost.
Using Odin, I attempted to flash a stock ROM, which for this model was Android v5.1.1, and now I understand why that wouldn't work. At this point instead of the logo screen, it showed a blue screen saying something along the lines of "An error has occurred while updating your phone, please use Smart Switch emergency recovery". I had tried to connect to smart switch before but it wouldn't recognize the device. I was saving initialization as a last resort.
I then flashed the most recent MM ROM for this model (which I found on sammmobile) using Odin, having read it was possible to still downgrade, and believing that perhaps Nougat was causing this problem. And it was successful, except the phone now returned to the logo screen. Again, with the same problems as before. And I still couldn't wipe the data and cache because I still couldn't access recovery mode.
Finally I connected the phone to Smart Switch and chose to initialize it. After going through all the steps, and downloading the files, it said it was successful but the phone is still stuck at the damn logo screen. I can still access download mode for what it's worth but I haven't a clue now as to what I should do next.
Any help or suggestions would be greatly appreciated. Thanks.

Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: PHN
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this Odin (even if you have another one);
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfirm) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.

no luck
forumber2 said:
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
...
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.
Click to expand...
Click to collapse
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> 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> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.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)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
(also I'm running Odin with only "Auto Reboot" and "F.Reset Time" ticked, don't know if that will help)

rayofmoonshine said:
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> 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> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.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)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
Click to expand...
Click to collapse
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.

forumber2 said:
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.
Click to expand...
Click to collapse
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?

rayofmoonshine said:
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?
Click to expand...
Click to collapse
Replacing motherboard will not help You unless You have a way to program EFS and IMEI information to it.

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

Database Info

welcome