[Q] my n8000 dead - Galaxy Note 10.1 Q&A, Help & Troubleshooting

hi
my n8000 locked and after i reboot screen was only many lines.
i tried to flash it but i can just go to odin mode.
no cwm mode.
no samsung screen.
just downloading screen and odin mode.
when i tried to flash official rom for my country it failed on sboot.bin.
in odin mode it said:
ODIN MODE
PRODUCT NAME: GT-N8000
CUSTOM BINARY DOWNLOAD: Yes ( 7 counts )
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
i am waiting for your syggestion for solve this prob.

Suggest stock rom flash via Odin and report where Odin fails .
Download a new stock rom as existing may be corrupt .
Fails at Nand Write you need a new motherboard .

JJEgan said:
Suggest stock rom flash via Odin and report where Odin fails .
Download a new stock rom as existing may be corrupt .
Fails at Nand Write you need a new motherboard .
Click to expand...
Click to collapse
i did stock rom flash via odin but it fails at sboot.bin

Related

need help about odin

i am trying to flash stock rom {pda file }with odin but odin show fail msg .

samsung galaxy note 10.1 N8010 has a screen full of white lines can acess odin mode

good morning/evening,
I have a samsung galaxy note 10.1 GT-N8010. I left it for charging and the screen went completely white lines and does not respond but can access odin mode only.Tried flashing stock rom but it says pit partition failed, tried various other methods in odin but of no use. can acess odin mode only. in odin mode it shows the following:
Product name:
custom binary download:no
system status : Custom
but it was in stock rom only
it says pit partition failed
What are you flashing ???
JJEgan said:
it says pit partition failed
What are you flashing ???
Click to expand...
Click to collapse
i was charging it and the screen went completely blank with completely white but i could get into odin mode so i tried flashing the samsung official firmware from smmobiles. Some forums and threads say it could be a damage in emmc chipset in motherboard causing pit damage and corrupt the software.is there any method i can fix it please help me.
in odin mode it does not show product name. i cannot get into recovery.
:crying:
thankyou

Stuck at Startup image after flash stock rom via Odin

When i want to flash back my old Samsung S7 Stock ROM via Odin after it said PASSED and then it stuck on Startup image
Unknow Predator said:
When i want to flash back my old Samsung S7 Stock ROM via Odin after it said PASSED and then it stuck on Startup image
Click to expand...
Click to collapse
Hi
What firmware you flashed , describe steps ... the more details the better
Flash again , download firmware again check MD5 , copy and paste Odin logs in case it fails again

Secure Download fail:(Bootloader) SM-G920F

Hi again.. i am trying to flash 7.0 rom with odin but it fails. It doesnt even start the flashing process. I just get an FAIL! mesage. In download mode it shows secure download fail: bootloader.
Here are some details about my phone can someonw please find me a firmware version that will work.
AP G920FXXU5DPL4 (6.0.1)
CP G90FXXU5DPL4
CSC G920FDDX5DPL1
Any solutions?
Download lastest Firmware from sammobile for G920F and flash normally. probably the one you're trying to flash it's old

Galaxy Note N8000 stuck on samsung logo after update. Everything stock never rooted.

Hello,
My N8000 was updating today and it got stuck at the samsung logo agter the "Galaxy note 10.1" screen. I am unable to access recovery mode; only download mode. I have been looking for hours for a solution but can't find any. I have tried to flash a stock ROM from sammobile not working (odin always fails) , tried flashing both custom and stock recoveries but odin keeps failing. I installed the toolkit but inorder to flash roms and stuff i need usb debugging to be enabled, and it is not. Is there a way to enable it while on bootloop?
Thanks,
Where does Odin fail ??
JJEgan said:
Where does Odin fail ??
Click to expand...
Click to collapse
When flashing stock recovery, it fails at recovery.img, flashing rom at boot.img
Suggests wrong files used .
Or possible damaged NAND .

Categories

Resources