My phone dead so I put it on the charger and then turn on my phone. But instead of booting up normally I got and Android guy and underneath of it saying downloading do not turn off target and then I have in the upper left hand corner---
could not do normal boot
DDI: MMC_read failed
ODIN MODE (HIGH SPEED)
Product name: sm-n910a
Current binary: samsung official
system status: custom
reactivation lock: off
knox warranty void: 0x0
Qualcomm secureboot: enable (csb)
Rp swrey: s1, t2, r1, a2, please
Secure download: enable
Udc start.
Never rooted.
Any ideas to fix.
Thanks
I have the exact same problem. It turns on sometimes...sometimes it just goes to this screen and sometimes I need to leave the battery out for half an hour as I get no response at all when hitting the power button. Majorly frustrating. Once I even got the same android screen but this time it was going on about kernel stuff? No idea. When it does turn on it will work fine for...say an hour then if I go back and try to unlock it will be majority sluggish. .turn on Bluetooth, oh God. ..freezes then kicks into life carrying out every button operation I pushed trying to get it to respond whilst it was frozen. Touch wizard fails and gives me stop report etc. Open an app and it will randomly lag like crazy. It is soooo anoying I am close to throwing the thing against the wall. I have never cuztomised my rom or whatever..just a standard note 4. I can't use the Samsung warranty as day one of my 24month contract I stupidly dropped it and have thee smallest cracking around the area of the forward facing camera. That was exactly 1 year ago and it has performed perfectly until now. So i know it's a software problem but I guarantee samsung will blame this. What the hell is going on...
Note4 AT&T Problems - Freeze,Reboot,BootLoop,NotTurnOn,Downloading...
I had same problem for 3 months now with my AT&T Note 4 SM-N910A ....
Freeze, Lag, Black screen, Reboots by itself, Stuck In boot loop, Stuck at ODIN "Downloading... Do not turn off target!!" screen with the message "ddi : mmc_read failed", cannot turn on the phone with power button, Touchwiz stopped message, System UI Stopped .message.....
Problems started with ATT OTA (over-the-air) update failed 3 months ago. After all standard fix attempts failed (clear cache, factory reset, uninstall programs, boot to safe mode), I reflashed to stock ATT ROM (5.0.1) with ODIN, then was able to install ATT OTA update to 5.1.1. (2 step process since 2 updates are needed - ATT tech support had to set something to download and install intermediate update first, then install the 2nd update - Cannot go directly from 5.0.1 to 5.1.1 with straight AT&T OTA update). Still same problem...
After all attempts failed, ATT tech support sent me to Samsung Service Kiosk at Best Buy., and Kiosk people sent me to Samsung Service Center. Samsung Service Center said this is ATT update problem. Samsung Service Center person told me that until ATT release a fix for the update, Samsung cannot do anything. He said that he attempted previously on another customer's phone to re-flash the firmware and the phone got bricked.
I tried factory reset, clear the cache, re-flashed to stock firmware and update to current ATT OTA update, start the phone in SAFE mode, remove SIM card, remove SD memory card, I tried uninstalling programs. None of these attempts solved the problem.
At one point I suspected volume key or power button hardware issue, but it is not the case. Even with phone not being touched and without the protective case, and without backcover, sitting by itself on the desk, the phone exhibits these problems.
My conclustion is the problem is one of the following: (1) System SW and/or AT&T update has bugs, (2) Hardware issue - memory chip, motherboard, or buttons. In either case, I cannot fix.
Only solution for now seems to be to take out the battery, wait few seconds (not too quick), then put the battery back in, and most of the time the phone boots ok. Then after a while the problems start again, and I have to take out the battery again.
Related
I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
....
FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.
I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.
I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.
Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.
So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.
That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.
I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....
I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]
Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.
I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?
after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone
I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.
I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!
Hello everyone,
My phone is NOT rooted. Earlier today it was stuck on the Samsung Screeen when I turned my phone on. I then used the power, camera, volume down button combo to bring me into recovery mode. Now everytime my phone turns on it stays in recovery mode. I can scroll up and down on my choices but there is not a key that I can press that will select a choice. Any ideas for how I can get my phone to work?
Screen I am stuckl on reads: "android system recovery <3e>
enter: OK key, Select : Vol UP/ Vol Down
reboot system now
apply update from SD cared
Wipe Data/factory reset
wipe cache partition
then theres an exclimation mark in a triangle with the android dude below that
#manual Mode#
If you don't care about existing app data, Odin would be a great choice. Either Odin-ing in a custom recovery or a fresh stock system would get you out of the situation.
Sent from Samsung Captivate Glide @ CM10.1.2
Sounds like you tried to do something and the phone didn't like it, hence you boot back into recovery on it's own.
Use Odin and reflash stock.
Much Thanks
Thank you very much for the responses, for some reason I was under the impression that your phone had to be rooted in order to use odin, much thanks!
I do not care about my personal files getting lost, but just out of pure curiosity, roughly, how would one accomplish that?
I'm try out odin now!
Back to my old problem! Any ideas?
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
apugslovesxda said:
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
Click to expand...
Click to collapse
Well, first boot of flashing any custom or stock rom takes a bit to fully boot. If you're stuck at the Samsung or Galaxy S screens, then you should reflash. If you have tried that and still having the same issue, then try a few more times. I've read posts of people having constant boot loops on flashes and they finally got one flash to properly stick after many tries.
So odined again and again, this time my phone eventually did turn on but it literally took 30 mins. When it did turn on I had no network connection nor could I use my touchscreen, it eventually shut off. I'ma go get robbed at the sprint store in a bit lol.
End Thread
End Thread- I got a Samsung Galaxy Note 3. My god- this phone is amazing. Kinda bull**** that I got nothing for my old phone with full insurance when it seems like it was a hardware failure!
Can't wait to play with this beast of a phone tomorrow!
Hey all...and to answer the number one question, yes I did do A TON of searches already to find a solution...PLEASE HELP if you have the knowledge
Phone Model: Galaxy S III (SPH-L710) Sprint 16gb
Firmware/ROM: All stock and never tried ANY customization
Problem: I think the problem happened when the phone auto updated to 4.3. Now when the phone tries to boot it just boots to the second Samsung "Samsung Galaxy S III" screen, reboots and then will get to the same screen and just sits there. One time I even let it sit there for 30 minutes just to see if it needed the ridiculous amount of time. When I try to get the phone into recovery mode (Volume UP/Home key/then the Power key) it will boot and on the first Samsung "Samsung" screen, in the top left corner in small print, it shows "booting recovery...". Then it will just go strait to the second Samsung screen then keeps rebooting twice before it will just stop on the second Samsung screen again. When I try to get the phone into ODIN mode (Volume DOWN/Home key/then the Power key) it will boot asking me if I'm sure and to press Volume UP to continue. Once I press Volume UP, to continue, I get to ODIN mode. In the top left corner it shows...
ODIN MODE
Product Name: SPH-710
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
(all grayed out) Qualcomm Secureboot: ENABLE
Then in the middle of the screen is the little Android guy. Below that it shows, "Downloading..." "Do not turn off target!!". And it just sits there doing nothing else.
I'm pretty sure I have done everything I could possible do to get it working again. From what I understand there may be other things I can do. Worse case scenario, if I must, I would be willing to loose everything on the phone and start over from scratch, if that's even possible.
There has to be some VERY smart people on here that can help me. This is my wife's phone and we don't have an upgrade until May...PLEASE HELP. Thanks all!!!
ONE MORE THING...almost forgot: We've never had the need to ever change anything on the phone so UBS debug was never turned on. Please tell me this isn't going to be a problem.
Sounds to me like the zip your phone downloaded to update to 4.3 was bad and now your system and recovery images are broke.
There isn't a MK3 tar you can flash via ODIN right now, you're probably best served taking it to a Sprint store to have them flash it.
You'd only be taking a risk trying to ODIN 4.1.2 (MD4) to your phone at this point. If the 4.3 bootloader made it on, then trying that will totally brick your phone to the point that they have to replace it.
Safest bet is Sprint store because you can get into Download mode, they should be able to get it working for you. I hope, good luck!
EDIT: there is a tar file for ODIN now
@romeoh posted this in the [STOCK] 4.3 and up Discussion Thread (NOT CM or AOSP) thread
Finally a .tar file is available to download on sammobile website.
http://www.sammobile.com/firmwares/
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
there was an ota update a bit ago, 4.3...um, is it under warranty or does she have insurance, if so, go to the sprint techs and have them look at it, if not, what you can do/try for it is to completely flash the 4.3 ota update again using odin and download mode...you can do this by clicking on the 2nd link in my signature and see what happens, fixed my phone like this after 4.3 and myself messed it up lol and it's the exact same thing the sprint techs would do for it if you brought it in
so there's your options man...good luck, any questions just post up but the guide is very simple and straight fwd to follow and I provided all that is needed in my download bundle from my dropbox account
edit...if you can't boot up to enable the usb debugging mode, it should still work but it's recommended to do but again, shouldn't really matter, as long as it boots into download mode you should be ready to go
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
This isn't an uncommon problem with the S3. I just recently went through this. In my case, and in many other cases, it's a faulty motherboard. Nothing you can do to fix it other than get Sprint to replace the handset.
For me, if I left it completely off for a long time, when I turned it back in it was stable for a couple of hours. Not sure if it was a coincidence, happened a couple of times that way.
My girlfriend was using her tablet the other day to do a card swipe transaction at work. Suddenly Mid-transaction the tablet crashed and wouldn't turn on. I took it home and plugged it in. I finally got it to turn on into stock recovery mode however it had the Android icon laying down with his front panel open and a red exclamation point with "No Command" underneath. I proceeded to do a factory reset which succeeded however right before it reboot the "No Command" underneath the Android icon switched to "Error". The system rebooted, and initialized the first on procedures (connect to wifi, sign in to google, sign in to samsung, etc..) however it wont stay on for more than about 15 minutes without shutting off completely, or restarting itself and going into boot-loop. It wasn't holding a charge either so i replaced the battery but the all the symptoms remain except for not holding a charge. One other thing that it does... sometimes a triangle shaped part of the screen will blink black, or the screen will flicker back and forth from the home screen to the settings screen if i go into settings. Occasionally, buttons like "Submit" and "Cancel" (On the wifi password entry) will glitch out.
I was thinking of rooting it, installing custom recovery and a custom rom to see if it would fix it but thought i would ask what you all thought first.
62 views and no replies? Nobody else has experienced the No Command error? I replaced the battery.... the tablet was fine for a couple of days and now it just shut itself off again...
I never had any of these problems. If you're near a Best Buy try going in and talking to their Samsung rep. Our local ones here is SLC have a rep in every store that works specifically with Samsung. Good luck. Thats frusterating.
Epic Nightmare said:
My girlfriend was using her tablet the other day to do a card swipe transaction at work. Suddenly Mid-transaction the tablet crashed and wouldn't turn on. I took it home and plugged it in. I finally got it to turn on into stock recovery mode however it had the Android icon laying down with his front panel open and a red exclamation point with "No Command" underneath. I proceeded to do a factory reset which succeeded however right before it reboot the "No Command" underneath the Android icon switched to "Error". The system rebooted, and initialized the first on procedures (connect to wifi, sign in to google, sign in to samsung, etc..) however it wont stay on for more than about 15 minutes without shutting off completely, or restarting itself and going into boot-loop. It wasn't holding a charge either so i replaced the battery but the all the symptoms remain except for not holding a charge. One other thing that it does... sometimes a triangle shaped part of the screen will blink black, or the screen will flicker back and forth from the home screen to the settings screen if i go into settings. Occasionally, buttons like "Submit" and "Cancel" (On the wifi password entry) will glitch out.
I was thinking of rooting it, installing custom recovery and a custom rom to see if it would fix it but thought i would ask what you all thought first.
Click to expand...
Click to collapse
Android will corrupt itself if improperly shut down. Especially with battery drain, that is why there are warnings not to let the tablet run bellow a certain percentage.
Download Odin 3.07 if your android is below 4.4.2, if not Download 3.09
I prefer UK firmwares as they are more robust than US.
To go into firmware upload, you can hold the volume down while powering up and volume up once more to be in upload mode. Then connect to your pc. If you do not have drivers installed Odin will not work. Either install Kies and allow drivers to install or download them from Samsungs site.
Once you perform the update you should have a normally running device.
If you never updated to 4.4.2... stay away from it too many issues over what it is. You can root 4.2.2 and tweak its performance easier than dealing with 4.4.2's reboot and multitasking lag issues. Some say they are fixed with a factory reset after updating, but they still remain, just not as problematic.
As of right now the tablet is bricked. The screen wont turn on, it wont even respond to being charged. I took the back off of it to make sure all of the hardware was connected and replaced the battery. Now its a brick
Sent from my SM-P900 using XDA Free mobile app
gooberdude said:
Android will corrupt itself if improperly shut down. Especially with battery drain, that is why there are warnings not to let the tablet run bellow a certain percentage.
Download Odin 3.07 if your android is below 4.4.2, if not Download 3.09
I prefer UK firmwares as they are more robust than US.
To go into firmware upload, you can hold the volume down while powering up and volume up once more to be in upload mode. Then connect to your pc. If you do not have drivers installed Odin will not work. Either install Kies and allow drivers to install or download them from Samsungs site.
Once you perform the update you should have a normally running device.
If you never updated to 4.4.2... stay away from it too many issues over what it is. You can root 4.2.2 and tweak its performance easier than dealing with 4.4.2's reboot and multitasking lag issues. Some say they are fixed with a factory reset after updating, but they still remain, just not as problematic.
Click to expand...
Click to collapse
In case I do get download mode working where would i get these UK official roms from? Are they for the wi-fi version?
1st thing... Search for battery disconnect note 8.0. A few have done a reset of the battery and power on issues. It is a lot easier than an Apple tablet.
Below is the 4.2.2 UK version for the WiFi only GT-N5110.
http://www.samsungis.com/download/BTU-N5110XXCMK1
If you are able to flash... I recommend safe root and install exposed framework and wanam exposed to disable DVFS and add some custom features.
If you have 4.4.2 already, you wil need to flash 4.4.2.
http://www.samsungis.com/download/BTU-N5110XXDNE1