(n8000) Stuck at Samsung Logo, possible fix

Search This thread

AdroidZ

Member
Mar 27, 2018
12
0
Steps to do the recovery
1. Download odin and extract
2. Download drivers and install.
3. Run Odin, place the following files
- click the PIT button, select the note10.pit.
- click the CSC, and select the previously extracted efs.rar..it should be efs.tar now
- click on AP, for custom recovery, such as philz.. or official rom..up to you.
4. Tick the following menus in Odin
- Re-Partition (optional, some users said no need to tick this would do as well)
- Phone bootloader update
- Phone EFS clear
5. Place your n8000 in download mode, and connect via USB.
6. Click on START button.. and hopefully success.
7. Once finishes, reboot into recovery mode (those who flash rom via Odin can skip this), and install the rom zip file.

Everything should be fine now and your n8000 should able to start properly... that's how I managed to "resurrect" my n8000 tho... hope these helps... mine was n8000 16GB, 3G/Wifi version

I have left my GT-N8000 to completely discharge while on holiday and as a result, it gets stuck on SAMSUNG logo when trying to turn it on ....

So I am now trying your method, but:
- in AP field of Odin3 v3.09 I am unable to insert any files from the provided "philz_touch_6.48.4-n8000.zip" file that contains "recovery.img" and" META-INF" DIRectory with more files inside,
yes some people suggest to insert I9300_Repair_efs.tar\I9300_Repair_efs.tar.md5 file, but should this field contain "PDA (CODE)" that refers to the build version of the software/firmware?

- and the CSC should be the consumer software customisation and is specific to geographical region and carriers. It should contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider, etc?

Reason I am asking this is my Windows 7 Pro 64bit PC does not detect the phone, if I try to install/re-install Samsung USB drivers , so I have tried on my Debian Jessie 64bit with Heimdall and the phone gets detected as "GT-I9100 Phone [Galaxy S II]" in Download mode, so not sure if I should be concern that different model is displayed:
Code:
sudo lsusb
Bus 002 Device 006: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)

Running detect, detects the tablet:
Code:
sudo heimdall detect --verbose --stdout-errors --usb-log-level debug
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.001274] [000058a8] libusb: debug [libusb_get_device_list]
[ 0.001317] [000058a8] libusb: debug [discovered_devs_append] need to increase capacity
[ 0.001337] [000058a8] libusb: debug [libusb_get_device_descriptor]
[ 0.001346] [000058a8] libusb: debug [libusb_get_device_descriptor]
[ 0.001352] [000058a8] libusb: debug [libusb_get_device_descriptor]
[ 0.001357] [000058a8] libusb: debug [libusb_get_device_descriptor]
[ 0.001363] [000058a8] libusb: debug [libusb_get_device_descriptor]
[ 0.001369] [000058a8] libusb: debug [libusb_get_device_descriptor]
[ 0.001375] [000058a8] libusb: debug [libusb_get_device_descriptor]
[ 0.001380] [000058a8] libusb: debug [libusb_get_device_descriptor]
Device detected
[ 0.001400] [000058a8] libusb: debug [libusb_exit]
[ 0.001407] [000058a8] libusb: debug [libusb_exit] destroying default context

And getting the partition information of the device will output this:
sudo heimdall download-pit --no-reboot --output mydevice.pit
sudo heimdall print-pit --no-reboot --file mydevice.pit

Code:
~/GT-N8000$ sudo heimdall print-pit --no-reboot --file GT-N8000.pit
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Entry Count: 16
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 20302
Unknown 4: 17748
Unknown 5: 12337
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename:


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: note10.pit
FOTA Filename:


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 1638400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1818624
Partition Block Count: 2867200
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4685824
Partition Block Count: 1024000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 5709824
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5726208
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained


So my plan is to use Heimdall, but the settings looks quite complex and I do not want to get the tablet to non-repairable state.

Anyone over here who is familiar with using Heimdal?

Yes, I have looked at the wiki page https://forum.xda-developers.com/wiki/Heimdall but there is so many options see below:

Code:
sudo heimdall flash --pit mydevice.pit
--ABOOT aboot.mbn \
--BOOT boot.img \
--CACHE cache.img.ext4 \
--MODEM NON-HLOS.bin \
--RECOVERY recovery.img \
--RPM rpm.mbn \
--SBL2 sbl2.mbn \
--SBL3 sbl3.mbn \
--SYSTEM system.img.ext4 \
--TZ tz.mbn
;

I have just found the original box hoping to be able to find additional information, but there is only IMEI and BAR CODE from John Lewis store on it
The tables had original firmware on it I think it was 4.4.2 and no root, UK version purchased from John Lewis.
 
Last edited:

AdroidZ

Member
Mar 27, 2018
12
0
I have now tried on my Windows 7 Pro 64bit PC connecting my GT-I9195 in "download mode" and with the Samsung USB drivers from
samsungusbdriver.com/download/samsung-driver-v1-5-63-0
the device has been detected with Odin3 3.09, but when I plugged in the GT-N8000 in download mode, I get msg. "USB Device Not Recognized"
even if I connect and disconnect it several times ......

So it looks like for me its only Heimdall in Linux as the device does not want to talk to Windows PC ..
 

AdroidZ

Member
Mar 27, 2018
12
0
So I have tried running the FrontEnd sudo heimdall-frontend

And use provided files in the "Flash" TAB:
PIT note10.pit (Note10_PIT.zip)
Partition (Files)
recovery.img - RECOVERY Partioin ID 6 (philz_touch_6.48.4-n8000.zip)
efs.img - EFS Partition ID 3 from (i9300_repair_efs.tar.rar)

But without success, I can Print PIT details from the device
Code:
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "SAMSUNG"
           Product: "Gadget Serial"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 021B
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 83
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 02
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Entry Count: 16
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 20302
Unknown 4: 17748
Unknown 5: 12337
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename: 


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename: 


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: note10.pit
FOTA Filename: 


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename: 


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename: 


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename: 


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename: 


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename: 


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename: 


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename: 


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename: 


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 1638400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename: 


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1818624
Partition Block Count: 2867200
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename: 


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4685824
Partition Block Count: 1024000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename: 


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 5709824
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename: 


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5726208
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained

Ending session...
Releasing device interface...



But when I press Start, I would get this message:

Beginning session...
ERROR: libusb error 0 whilst receiving packet. Retrying...
ERROR: libusb error 0 whilst receiving packet. Retrying...
ERROR: libusb error 0 whilst receiving packet. Retrying...
ERROR: libusb error 0 whilst receiving packet. Retrying...
ERROR: libusb error 0 whilst receiving packet.
Releasing device interface...

And after this, I am unable to read the PIT from device with the same error ....
untill I turn of the tablet and go back into "download mode"
 

AdroidZ

Member
Mar 27, 2018
12
0
I have tried on Debian 9 4.14.0-0.bpo.3-amd64 with slightly different error msg., I was able to retrieve the PIT file again,
but then come "ERROR: libusb error -7 whilst receiving packet. Retrying..."


Code:
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "SAMSUNG"
           Product: "Gadget Serial"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 021B
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 83
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 02
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Beginning session...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
Releasing device interface...
 

[email protected]

New member
Oct 13, 2016
4
0
That is not how the forum works .
You have a problem post a question in Q&A .
Ok, so i need all files for my n8000, pit file, efs.rar.
And rom, because im trying to install everything using odin and its come out message failed, and i dont now what is wrong.
I do same as you telling from begining
 

JJEgan

Senior Member
Oct 24, 2010
30,246
5,879
How to is in Post One.
As are all links and they work /

Or
Pit Search forum
Firmware files are on sammobile or updato .com

EFS is a file you save from your phone .
 
Last edited:

mukkino78

Member
May 8, 2018
5
0
n8000 - logo samsung loop

i need help from you industry experts i can not resurrect my gt-n8000 ever samsung logo in loop. It goes only in download mode. Does this method work? BUT the recovery philz is in zip format and is not accepted by odin which only receives files in .tar format
 

mukkino78

Member
May 8, 2018
5
0
Give me alwayes FAIL with odin

<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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 
Last edited:

PuffItGoes

New member
Jul 28, 2016
4
0
Did not resolve my problem

The method and files did not help in my case. But is someone able to pin down my issue and what I should do?
I used the file from sammobile. My Device is from germany (DBT), a N8000 16GB 3G Version.

Odin-Screenshot: https://ibb.co/fvZ5xrp

Message Box:
Code:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<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)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    I'm having this problem past few days, tried all the links in the Q/A section, dev.. all links were dead.. and managed to found solutions for this problem.

    Basically, the tab will stuck on "Samsung" logo and looping for eternity... tried to reflash the rom, wipe system and everything via odin.. will results the same thing...and I thought I'm gonna say good bye forever for my note 10.1 (n8000)...or send for repair (which samsung quoted me ~ $158 for the "board replacement"... but until I found how to get it alive... actually I've no idea what causing my n8000 stuck in the first place..

    After a whole day "intensive" searching and everything.. almost all files links in xda were dead.. and finally I found out all the files and solutions..

    What you'll need
    > Odin 3.xx, can get from samfirmware website
    http://www.sammobile.com/firmwares/download/30977/N8000XXUDNE5_N8000OLBDNE3_XME/
    > Samsung drivers
    http://forum.xda-developers.com/showthread.php?t=961956
    > note 10.pit and efs (extract the efs.rar after download, yes it's i9300 but can be used)
    > n8000 rom, can get from http://www.sammobile.com/ or development section. I prefer flashable rom in recovery such as android revolution HD, and place it in microsd.
    > Philztouch CWM

    (files as attached)

    Steps to do the recovery
    1. Download odin and extract
    2. Download drivers and install.
    3. Run Odin, place the following files
    - click the PIT button, select the note10.pit.
    - click the CSC, and select the previously extracted efs.rar..it should be efs.tar now
    - click on AP, for custom recovery, such as philz.. or official rom..up to you.
    4. Tick the following menus in Odin
    - Re-Partition (optional, some users said no need to tick this would do as well)
    - Phone bootloader update
    - Phone EFS clear
    5. Place your n8000 in download mode, and connect via USB.
    6. Click on START button.. and hopefully success.
    7. Once finishes, reboot into recovery mode (those who flash rom via Odin can skip this), and install the rom zip file.

    Everything should be fine now and your n8000 should able to start properly... that's how I managed to "resurrect" my n8000 tho... hope these helps... mine was n8000 16GB, 3G/Wifi version
    1
    Hello, i have also this issue with the galaxy note 10.1 gt-n8020, its stucks on samsung logo and doesnt go any further...i dont have a custom firmware neither the tablet its rooted, i tried with odin having the original firmware but when i press start, after the msg "Start write to NAND" i get a FAIL and ends there. Even with the method mentioned here, still i get the FAIL msg...any Info on this on what might be the cause and maybe a possible fix?Can this be also hardware related malfunction?I cant go into recovery mode, only download mode works...
    1
    Yes, that md5 was used.....

    I've went completely by procedure described in first post, with exception of i9300_repair_efs change as mentioned. For that part, I've used latest Odin downloaded from Samsung web, and for bootloader, I've used Odin 3.05, just to be sure, since there is a button with "Bootloader" written on it :)
    1
    Sorry but I didn't get it clear!!:confused:
    Did you use i9300_repair_efs.tar for AP and left CSC empty?
    Did you flash a stock rom or a recovery after that?
    Did you Ticked Re-Partition ,Phone bootloader update ,Phone EFS clear ,F.Reset Time or Auto Reboot?
    please provide the right steps you've used one by one.:(

    Used i9300_repair_efs.tar for both CSC and AP, after that installed android revolution.
    Can't remember everything that was ticked, but was going step by step according to guide in the first post, with i9300_repair_efs.tar change.
    1
    Sammobile is official.
    Flash firmware reboot then flash custom recovery .The flash custom rom.
    First back up your EFS .

    Sent from my SM-N930F using XDA-Developers Legacy app