[Q] GT-8013 16gig wifi only, stuck on logo screen and wont go into recovery mode - Galaxy Note 10.1 Q&A, Help & Troubleshooting

I have done hours of searches and can't find the answer to my problem. Hopefully someone here can help.
My GT-N8013 is stuck in the Samsung Galaxy Note 10.1 logo screen. I can't even turn it off without it bringing this screen right back up. It only goes dead when I unplug it and let the battery run out of juice.
I can get it to restart into Odin Download mode, but not into the recovery mode. I can install roms and CWM and stock roms using both Kies and desktop Odin3, and I get "pass" status with no errors, most the time, when I do rom update, but I can't get to the restore screen with the power + volume up button, then releasing the power button and holding down the volume up button only. It just stays on the Logo screen.
I hold down the power + Volume down button and it will restart into the Warning screen that allows me to hit the volume down to go to the download screen or volume up to cancel and restart. Both the volume up and down buttons work for this action so I'm sure the buttons are working okay.
I thought maybe the battery wasn't charging right and that was preventing it from going into recovery mode, but I can charge it for a while and unplug it and the screen will stay on the logo screen for a long time, so I think the battery is okey.
Samsung just said I should send it in, but it is out of warranty and I don't want to put much more money into this devices since it is old and a new version is out now, but I hate to think a great device like this that worked so well for so long is now going to be worthless because I can't figure out how to fix it. Hardware seams to be working fine and just a few days ago, the software was working fine. I'm so confused.
Leading up to these events, I had it turned off for a few weeks because I was traveling and going on airplanes and never ended up using it on the trips so it remained turned off. When I turned it back on, there was a OTA system update that I wasn't sure what it did. Didn't appear to do anything noticeable. Still worked normal. Then a few days later I did a personal data wipe because I was going to sell it and get the new Note 10.1. I went through the new setup process without problems, everything was fine. I sold it to a guy and a day later he contacts me and says it isn't working properly and I've been dealing with this ever since. It didn't appear to have any physical damage and the custom binary download count was at "No" so I don't think he tried to load any custom roms. I don't think this guy is tech savvy enough to do anything but plug it in and use it normal, so I don't suspect foul play.
Any help would be greatly appreciated. Thanks.

Check this
http://forum.xda-developers.com/showthread.php?t=2477626
Sent from my GT-N8013 using Tapatalk HD

I have the exact same symptoms. (No recovery mode / stuck on boot screen even after fresh stock rom installed). Out of the blue after working fine the day before.
Anyone know:
a) of anything further that I can try to resurrect this
b) if I might still have any joy getting warranty service from the shop I bought it from in the UK / Samsung if they send it back to them. I have more than a year left on the 2-year warranty they provided, and have only ever run/attempted to run stock. However as I have been out of the UK my custom binary count has increased to 7 as I have tried to reinstall Stock Roms myself to fix the problem. (However OS version still shows as Samsung Official, not custom)
Thanks so much if anyone can help me

Custom binary 7 = warranty void .
I would try flashing Philz recovery tar through Odin and try recovery mode .

Related

[Q] Transformer Dead?

Hi, a few days ago I bought the tablet, and the keyboard dock station.
Yesterday, I had it on stand by (or sleep mode, don´t know the difference) with the keyboard and then I wanted to use it but it seems dead. I charged it all the night, but it doesn´t starts.
It doesn´t show the asus´s logo.
I'm desperate.
Thanks in advance, Nico.
Same problem here
I ran into the same problem about a week and a half ago. Was using it a bunch with the keyboard and then I couldn't turn it on again. I was able to get it to come when it was off the keyboard by plugging in the power cable. However, when it was on I couldn't get the shut down dialog to come up, holding the power button in would only cause the screen to black out.
I e-mailed ASUS and they suggested I reset it back to factory. Still had the problem. It is currently in repair status at their RMA facility.
My first guess was that it was software related, since other android devices seem to have similar problems, for time to time. However, on a couple of occasions if I pressed the power button in a certain way the unit would turn on or I could get the shut down dialog to show up. I could never get the button to work consistantly, so I sent it in.
For folks who are interested: The tablet was non-rooted or ROM'd. Had 3.1 and the keyboard was running the software update that came with 3.1. The tablet was 40 series based on the serial number. It had been working fine for about a month.
Henry
I've seen this lots on Tegra devices.
Solution: NVFlash another custom recovery.
This even happened to me. During a bad flash that locked up, I pulled the battery and it wouldn't even power on. Nothing. No Bootlogo or anything.
NVFlash mode would still register the device when connected. So I NVFlashed between Stock and Clockwork Mod back and forth (this on my LG G2x)... trying to boot it up in between flashes...
Eventually it booted up and I was able to get into Recovery, where I did a factory reset and flashed a known good rom. All has been well since.
How can I reset it?
I have to try the most possible things to repair it, becouse it isn´t simple to me to send it to RMA, becouse I´m from Uruguay.
I can to power it on! The battery looks in 81%.
What you recommend to do now? Quickly please!,
I do not know how long you'll be able to take on.
How can i reboot it or dont know?
Android Version 3.01
*Edit: Just actualized to 3.1
Hold the power button for 15 seconds until the screen goes off then power it up normally and see if it'll come on. I was thinking maybe it's the Sleep of death bug...

Constant boot loop - can't even get download mode

I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
That almost sounds like some sort of power issue. Have you left it sit turned off until the battery was full?
Yes, I left it overnight and it just keeps flashing the battery screen and then resets. I also have an external charger and used it to charge the battery, so it's not an issue with the battery actually being empty.
Have you been able to get the phone into download mode previously?
Have you have dealt with a boot loop and performed an Odin recovery previously? If not, remember it can take a few tries to get download mode to pop up.
If you can't get Odin to go, you might try flashing with Kies.
I am wondering if your phone met with some kind of disaster when you weren't around (trauma or liquid).
anyone747 said:
I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
Click to expand...
Click to collapse
This sounds almost exactly like the problem I had with my Sidekick. In my case, it turned out to be a bad battery and a loose ribbon cable on the motherboard. I'd check those two things.
This happened to me as well, and the three-button method to get into download mode wasn't working. For some odd reason, for me to get into download mode all I have to do is hold down the power button + track pad, and it goes right into download mode... Maybe slightly different model?
Try that - power button + trackpad
Bootloops.
Not a guaranteed fix by any means but for troubleshooting purposes you may want to consider making a USB JIG. It will most definitely help you figure out just how serious the problem is and if it IS software related with a way to get it working again you will need the JIG anyway so its worth a shot. If nothing else you learn a new skill and you're the proud owner of an incredibly useful tool that you can say you made yourself. good luck!
I know this post is kind of old, but it just happened to me last week (same circumstance, a rooted phone, but stock). I ended up just pulling the battery out and pressing the power button a couple times to hopefully drian it and letting it sit for 15 minutes, and then I put the battery back in and it worked again. I now have another rom flashed on it, I hate stock.
I know this forum is ancient, but I'm working on an E-Bay phone with this exact issue. I found the following thread the most useful and informative on the problem:
http://forum.xda-developers.com/showthread.php?t=1996709
Hopefully this helps other.
what i did was hold the power volume and button between the menu n back with the left hand YES HOLD IT UNTILL THE PIT IS UPLOADED. then u can let go then slide in the vattery with the right.while checking off the flash bootloarders on the heimdall with it fixing my phone XD
I had this happen, I dissassembled the phone, and used an alcohol pad to clean the power button area, and manipulated the button a lot, let it dry, reassembled...it still bootlooped.
BELOW IS RISKY BUT WORKED FOR ME
So while the back cover was off (exposing the cicuit board but everything still connected) I inserted the battery and watched it boot loop...during this, I used a flathead screw driver to "short" the power button pins...this let it boot fully, and it has been fine since.
i smacked the phones power button a few times and it worked

phone wont even turn on... WTF

how do all.... nexus s I9023
i have just purchased a some what lovely google nexus s I9023
working fine for an hour or so...
i had a little pop up asking me to update...
i thought OK... sure why not...
having done so phone worked fine for an additional 20 mins...
then phone froze... i took the battery out and started it up again...
it froze on GOOGLE screen...
iv trawled every forum possible since this has happened...
now the PHONE WILL NOT EVEN TURN ON...
the phone is completely stock no mods or addon's to it!
im at the end of my tether.. SOME ONE PLEASE HELP!!!!!!!!
Hold volume up + power after reinserting the battery and putting it on charge. Do you enter bootloader mode? And what happens if you click recovery?
done the hold volume up and press power...
still no joy unresponsive!!
when it does work after 50 attempts of taking the battery out and putting it back in and doing volume and power
it turns on.. scroll to recovery.. it turns off google screen pops on...
then a Green android lying on his back appears with its stomach open showing white blocks and a explanation mark above it!
IM PUZZLED!!!!!
it then resets it self going back to being unresponsive!!
HELP!!!!
Give this a shot.
Also, could it be a power button issue? And that android screen is the splash for stock recovery. You have to press vol. up + power again to get past it, beyond this you can do a factory reset and similar magic. However you likely don't want this, and on the screen where you chose to enter recovery, you'll likely want to use fastboot to unlock the phone (which will wipe all personal data) and then flash a stock ROM again. At this point i would advise lots and lots of reading.
If it's less than a year old, i would be calling samsung though. If it is a new phone i would definitely do this first. Do not unlock unless you have no chance of going through warranty. Will need to know the exact status of the phone for best advice here.

[Q] My tablet seems to be bricked?

Hello people!
First of all; thank you very much for your time and effort in developing ROMS for all of my android devices. Keep up the good work :good:
Now, I just bought the galaxy tab 2 10.1 Wifi (p5110) a month ago. Naturally I didn't like the bloatware Samsung shipped with their default ROM.
So I started flashing some custom ROM's. All went flawless until yesterday.
I guess it's my own fault, but here's my situation:
Yesterday, in order to install the Zap Blaster rom, I installed TWRP.
Here is where i think it went wrong:
I Wiped the /system partition and then rebooted the device. Naturally it wouldn't boot up anymore. But I wasn't able to shutdown the device anymore and enter the Recovery (or so I may thought).
My next action was to drain the battery, in order to completely shutdown the device. But now it only shows a battery with a loading indicator.
I charged the device for 8 hours but it still only shows the battery with the loading indicator. This screen appears when I connect the tablet to a power source. I can then "hard"-shutdown the device, by pressing the power button for 10 secs.
Otherwise it isn't responding at all.
When I connect the device to my computer, it shows up as a omap4430 device, but it quickly disappears. Only to show the device again, and so on.
Can I save my tablet? Or do I need to send it to the Customer Service and pay for my "sins"?
Like to hear from you, and thanks in advance for your time!
Greetings!
P.S: Sorry if my English isn't that good, I did my best effort!
P.P.S: I know my tablet isn't complety bricked, but I didn't know any other word for it.
I just got done with that same problem, you. Can actually still power off your device from the battery logo.
Then you will have to hold the power and volume down to get into download mode and flash the stock rom using odin for windows or heimdall for Linux/mac.
If that dosent work then let me know i have another solution to ypur problem. I just meed to know if u can get into the download mode or not
Sent from my MB865 using xda app-developers app
Hope i can help
jarrin92 said:
Hello people!
First of all; thank you very much for your time and effort in developing ROMS for all of my android devices. Keep up the good work :good:
Now, I just bought the galaxy tab 2 10.1 Wifi (p5110) a month ago. Naturally I didn't like the bloatware Samsung shipped with their default ROM.
So I started flashing some custom ROM's. All went flawless until yesterday.
I guess it's my own fault, but here's my situation:
Yesterday, in order to install the Zap Blaster rom, I installed TWRP.
Here is where i think it went wrong:
I Wiped the /system partition and then rebooted the device. Naturally it wouldn't boot up anymore. But I wasn't able to shutdown the device anymore and enter the Recovery (or so I may thought).
My next action was to drain the battery, in order to completely shutdown the device. But now it only shows a battery with a loading indicator.
I charged the device for 8 hours but it still only shows the battery with the loading indicator. This screen appears when I connect the tablet to a power source. I can then "hard"-shutdown the device, by pressing the power button for 10 secs.
Otherwise it isn't responding at all.
When I connect the device to my computer, it shows up as a omap4430 device, but it quickly disappears. Only to show the device again, and so on.
Can I save my tablet? Or do I need to send it to the Customer Service and pay for my "sins"?
Like to hear from you, and thanks in advance for your time!
Greetings!
P.S: Sorry if my English isn't that good, I did my best effort!
P.P.S: I know my tablet isn't complety bricked, but I didn't know any other word for it.
Click to expand...
Click to collapse
Whatever you do dont send it in quite yet. Try holding the power and volume down button and wait till the samsung logo comes up. keep holding them until the samsung logo a second time. If you can get into recovery mode i will be able to guide u from there. If that doesnt work i have one other idea too

Exynos S8+ flashed TWRP now wont boot

Hi, decided today to bite the bullet and finally root my S8+, however wish I didnt!
Flashed it with the correct version of ODIN an the correct version of TWRP, process went through ok and the phone re booted, however it stuck on the samsung splash screen.
It was stuck for about an hour so I powered it down (think it was the volume down and power button for 7 seconds). this turned the phone off but now it wont turn back on again. I have tried recovery mode etc but nothing. Connecting the charger doesnt light up the led either.
Phone is not recognised if connected to a pc either (including ADB)
Is this a total brick ?
Cheers
Ok spoke with samsung, they will replace the mainboard under warranty
I don't think it was a total brick, sometimes takes a few minutes of holding the 3 key to get to a reboot into download mode when TWRP is mux'ed. There are a few other key combos that can sometimes work as well. It is kinda scary, however, my experience with these phones is that they are pretty durable. Seems to take a lot to really brick'em.
If you installed TWRP correctly, you need to have your phone completely off. Then press and hold the Up, Bixby, and Power button. As soon as you see the Samsung S8+ logo, release the power button. This'll boot you into recovery.
Thanks guys but the phone was totally bricked. No key combi action would work phone wouldn't turn on or charge. Took it to a samsung service centre yesterday and they replaced the mainboard under warranty for me. Interestingly as I was handing over my phone they went through the terms and conditions and said that software modification would mean that the phone would not be covered.(I didn't say anything about what I had attempted).
I am on the Samsung beta program for Oreo, so I wonder if the bootloader was the issue
Just so you know, if they do get it operational and find you have altered the software/kernel/recovery then you can expect a call to let you know how much it will cost to fix...
Just an FYI...

Categories

Resources