[Galaxy Note 10.1 Q&A, Help & Troubleshooting] RHAddict:
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:

<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:

<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://xdaforums.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:

<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?