N8000 hangs on Samsung logo

[filbert42]

Hi Folks,

My Note 10.1 3G (N8000) suddenly rebooted itself (I heard the reboot sound) and is now stuck on the Samsung logo - the one that comes after the initial logo with the 10.1 in the text. I want to do a factory reset. One problem is that I can't turn it off. Pressing the power button does nothing. Holding it down for 10 seconds or so restarts the device.
I think I am on Android 4.n of some sort but I have no way of checking.

Google tells me that, from device switched off, to press power and down volume. But, when I do this (during the power off/recycle process I mentioned) I get to a screen that says:
"warning! a custom OS can cause critical problems in phone and install applications. If you want to download a custom OS press volume up key. otherwise press volume down to continue"

I don't get a factory reset option. Volume up just goes back to the logo hang situation. Volume down gets to a screen that is waiting for a custom ROM download.

Any thoughts on how I do a factory reset?

Thanks

 

[B. Diddy]

First, to force a shutdown (if it's currently on), press and hold Power and Vol Down for about 10-15 seconds.

Then, from a powered-off state, follow these steps to boot into Recovery Mode, where you can either wipe the cache partition or do a factory reset: https://support.t-mobile.com/docs/DOC-14245

 

[filbert42]

Thanks for that. I did manage to to a shutdown but that power+vol down didn't work until I had the USB cable connected plugged into my laptop. Thanks for the tip.
However, I have tried numerous times to get the power+vol up switch on to work but it always ends up with the logo screen - I mean the one with just the one word, not the initial one with the Note 10.1 bit as well. If I keep holding the power button past the 10.1 logo, it reboots.
If I use power+vol down, I get to the custom OS upload screen.

Any more ideas?

Thanks

 

[B. Diddy]

Hmm. Try this instead. I thought the Note 10.1 2014 would have the same procedure as the original Note 10.1, but apparently not: Wipe Cache Partition - Samsung Galaxy Note 10.1 | Verizon Wireless

 

[filbert42]

Sorry, didn't make it clear. Mine is the original (2012?) version and it doesn't have a home key.

I wonder if I should just use the download option and try to install something like CyanogenMod?

Thanks for your support

 

[B. Diddy]

Man, I wish Samsung would've made up their minds back then about whether to keep the Home button or not!

Ok, try this: SAMSUNG N8000 Galaxy Note 10.1 3G - How to Hard Reset my phone - HardReset.info

 

[filbert42]

No. Nothing I do seems to work. I seem to have a choice between the download screen and hanging at the second Samsung logo.

I'm currently looking at using Odin to upload either the standard firmware or a CyanogenMod OS. AS my main machine's now a Mac, I need to dig out my old Windows laptop. I have tried via a Parallels VM but it won't see the tablet.

Thanks for your suggestions

 

[B. Diddy]

Does Kies detect it? If not, I hope you have success with Odin. http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html

 

[filbert42]

Thanks for all your help. - I dug out my Thinkpad Windows laptop to make things a standard as possible.
So far, no luck. Kies hangs on "connecting". I've tried a couple of version of Odin and a couple of methods with no luck.
With Odin v3 11.1 and something called High on Android CWM recovery, I just get a 'fail' message.


<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


With a stock firmware from Sammobile, it hangs for several minutes at 'setup connection' and then fails with a serial port error.
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)


Guess I'll try disconnecting the battery as a last resort, otherwise it looks like it's totally useless

 

[filbert42]

Well, disconnecting the battery didn't work - didn't really hold out much hope.

I then sent it to a repair shop that claimed to specialise in Samsung devices but they can't fix it either.

I guess it's bricked - unless anyone has any ideas of anything else to try?

 

[ssss37373]

hey did you find a solution ? my My Note 10.1 has the same problem and i don’t know what to do