Database Users

[Help] Tablet randomly freezes! Bad hardware?!

Last week my tablet froze at 5am (the screen was on and the clock stuck).
Since then, it randomly freezes (and sometimes reboots) -- hard lock.
I've tried wiping, new ROMs, etc. The freezes even occur in clockwork recovery.
Am I out of luck?

If it freezes both in normal mode and even in recovery, I would say you're out of luck.

requist said:
If it freezes both in normal mode and even in recovery, I would say you're out of luck.
Click to expand...
Click to collapse
I just logcat'd a few lockups, no clues whatsoever
Time to wipe and trash.

In recovery the tab is in a known state, freshly booted, no user programs, different states or options. If it is freezing in this mode it means either the loaded image is incorrect or the handling of this image is incorrect. The handling would mean a hardware error because other tabs with exact the same image and options work normally. An error of the image would be possible without hardware error but very unlikely since loading a different image (normal mode) gives the same problems.
I would guess a problem with either sd or normal ram. No clue what a repair would cost but is it already past guarantee? (Else I would try to recover to stock rom and bring it back to the store..)

[Q] NFC error puzzle. USB debug not an option

Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!

Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.

notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).

Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris

flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.

[Q] SAM+CWM bootloop nightmare (& my mom-in-law will kill me!)

UPDATE: Problem solved! Subsequent attempts at Odin flashing succeeded. So...Nevermind!
Hello XDA sages!
I'm an avid Android user and I like to mess around, but I have no genuine technical skills or training and it's now bitten me pretty hard. I just got engaged and I was trying to clean out my phone and gift it to my new mother-in-law...with disastrous consequences. So this is my SOS to this incredible community! (Please note, I have searched many other Note 2 bootloop threads but I've seen nothing describing my situation and their solutions have not helped. Though I do apologize if I've missed something!
My current situation:
* Upon restart, the phone (Note 2 GT-N7100, unlocked) is stuck in a terrible bootloop, where the "Samsung Galaxy NoteII GT-N7100" logo appears for 6 seconds, and is then replaced by the Clockwok mod recovery logo (not recovery mode screen, just the hat+geer+orange arrow logo in the center, with "ClockworkMod Recovery v6.0.4.3" in small letters at the bottom). That logo lasts for about 1 second and then it goes black for 1 second, then repeats with the Samsung logo. And so on.
* Many other threads have suggesting entering recovery mode by holding power + home + volume up. This only causes the Samsung logo to refresh every few seconds (i.e. it eliminates the Clockwork mod logo interlude but does nothing else)
* Down+power+home does stop the loop and change to the custom OS download option screen. Pressing volume up then does enter the "Downloading..." screen with the picture of the green Android. (pressing volume up restarts the phone and the loop begins again).
* I've tried loading a stock firmware package onto the device in this mode with Odin v.3.0.9 (obtained via this post) but it doesn't recognize my device. I'm guessing this is because USB debugging was not turned on before the crash.
How I got here:
* I first rooted and flashed a custom rom several months ago using the Cynogen Mod custom installer. I installed the only "stable" release for the N7100 (here.)
* About 1 month ago I used the Rom Manager app and CWM to flash OmniRom, from a zip file on my external SD card. Just before the crash happened last night, I successfully completed an OTA to the latest OmniRom nightly.
* As mentioned, I was preparing the phone to be gifted to my new mother-in-law, and wanted to clean it out. I started by booting into recovery mode (from the Rom Manager app) and then initiating a factory reset.
* Upon rebooting, I noticed that somehow a bunch of my data was still hiding on the phone. Photos and videos and some songs were mysteriously still present, and the storage analysis in settings showed only about 6 gigs were free out of 16. A subsequent Factory Reset did nothing to change this. (All other aspects appeared to be working perfectly, however, as far as returning to a clean install of a fresh copy of OmniRom Android 4.4.2 -- no account data was preset, all my apps were gone and all the stock apps were in the default folders, etc.)
* I booted into Recovery Mode and initiated a "Media Data wipe" (I think that's what it was called) in an attempt to clear out the stubborn media files that weren't being erased.
* I then initiated a "data wipe" (which appeared to just be one level of storage hierarchy above the media data wipe I had just completed).
* I'm pretty sure I also separately initiated a "cache wipe". (But not a "Dalvik Cache" wipe that I have seen referenced on other threads, as I don't believe I saw a reference to that within the recovery mode interface).
* After these wipes I restarted, and all appeared to be fine. The stubborn media data was wiped clean. Finally, after logging back into my Google account to use the App Store to download Rom Manager one last time, (and I honestly can't quite remember why I needed to that) I wanted to complete the process with one more factory reset to eliminate my account data before handing over the phone. This time, I initiated the reset from within the settings menu of the phone in normal operational mode. (This was the first of the various factory wipes I've mentioned that I initiated this way -- all the other factory resets were initiated from within recovery mode).
* I think this is when the current loop started. But to be embarrassingly honest, I had the phone face down and didn't look at it after initiating that final factory restart until I subsequently popped out the battery in order to remove the SIM card. I think the factory reset was complete by that time, but I'm not sure. (In other words, I might have interrupted the factory reset by removing the battery before it was complete).
* After that point this evil loop began.
* To my amateurish eye, the two leading contenders for how I did this are a) the "media wipe" or "data wipe" which I completed before the penultimate restart (although the phone did boot and operate just fine after those were completed, or b) the final factory reset which I may have interrupted by removing the battery.
Three other notes which may or may not be relevant:
* Every time I did a factory reset or data wipe and then went to restart the phone from within the recovery mode, a warning screen came on saying that something might have messed up root access and asked me if I wanted to fix. I always said that I did,
* I had selected TWRP recovery in the Rom Manager app on the advice of the Omnirom site, and I think I saw a reference to TWRP on the recovery mode screen, but I had previously installed ClockWorkMod Recovery and thought maybe that was still active in a way it shouldn't be. (I can't remember what those indications were exactly, but I think it might have just been seeing the logo in the recovery page). But the presence of the ClockWorkMod Recovery logo in my evil boot loop makes me think this may be relevant.
* Before my first factory reset I had made a full backup copy of the current Rom (omnirom) onto my external SD card, which is still in the phone.
I would be eternally grateful for any help, tips, references or suggestions! My fate is in your hands!!
Many thanks,
- Your overeager n00b

Try simple things first. Reinstall kies so you know drivers isnt corupted and then flash stock rom with odin. And also try to switch usb cable and if that doesnt work switch to another pc. Try that and well go on.
Edit: i see you solved it gj.

Do not touch somebody else's phone if they are going to kill you when something goes bad

Next time better think twice

Brandzel said:
UPDATE: Problem solved! Subsequent attempts at Odin flashing succeeded. So...Nevermind!
Click to expand...
Click to collapse
Nice to hear you solved it You flashed stock, i guess?
By the way, I recommend changing the tag to [SOLVED] :good:

Help! Galaxy S5 recovery bootlooping after shutdown during factory reset!

Greetings members of XDA! I'm new to posting here, although I drop in here sometimes to look at ROMs.
Recently, after having the contacts under my screen cleaned (due to a ghost input problem which doesn't seem to be related to this, the cleaning didn't really fix the ghost inputs anyway), I factory reset my Galaxy S5 through the regular backup/reset settings. However, part of the way through the reset, my phone shut off. I don't know whether the battery lost contact for a split second, or if it just crashed, but it started booting again straight away - except this time it booted into the recovery of its own accord, without me holding down any other buttons. The recovery (TWRP) just bootloops, and the "TeamWin" screen just flashes constantly. Removing the battery is now the only way to turn the phone off, and whenever I turn it on or charge it, it boots into the recovery and the recovery just bootloops. Although the regular ROM is not accessible (it just goes to the recovery), Download Mode can be accessed normally.
I had a look at my catlog (thankfully I had USB debugging enabled before this fiasco), but it only offered me this after starting the daemon:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
I also used ADB to pull /tmp/recovery.log, here's the pastebin code: U89RQTkZ (I can't post the link itself, but this is the code for it after pastebin's URL)
The pastebin above is just one repeat of the attempt to boot inside the bootloop - the log itself is comprised of many subsequent attempts to boot, with identical results in the log. (I know the log says the date is 2014, that's probably because I had aeroplane mode on before I did the reset.)
So, can anyone help me fix this? I am inclined to try reflashing my recovery (TWRP again since my most recent nandroid backup is in that format), but I want to know if anyone here has a better idea before I start doing potentially irreversible damage to my phone.
Thanks in advance!

CakeWithoutEggs said:
Greetings members of XDA! I'm new to posting here, although I drop in here sometimes to look at ROMs.
Recently, after having the contacts under my screen cleaned (due to a ghost input problem which doesn't seem to be related to this, the cleaning didn't really fix the ghost inputs anyway), I factory reset my Galaxy S5 through the regular backup/reset settings. However, part of the way through the reset, my phone shut off. I don't know whether the battery lost contact for a split second, or if it just crashed, but it started booting again straight away - except this time it booted into the recovery of its own accord, without me holding down any other buttons. The recovery (TWRP) just bootloops, and the "TeamWin" screen just flashes constantly. Removing the battery is now the only way to turn the phone off, and whenever I turn it on or charge it, it boots into the recovery and the recovery just bootloops. Although the regular ROM is not accessible (it just goes to the recovery), Download Mode can be accessed normally.
I had a look at my catlog (thankfully I had USB debugging enabled before this fiasco), but it only offered me this after starting the daemon:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
I also used ADB to pull /tmp/recovery.log, here's the pastebin code: U89RQTkZ (I can't post the link itself, but this is the code for it after pastebin's URL)
The pastebin above is just one repeat of the attempt to boot inside the bootloop - the log itself is comprised of many subsequent attempts to boot, with identical results in the log. (I know the log says the date is 2014, that's probably because I had aeroplane mode on before I did the reset.)
So, can anyone help me fix this? I am inclined to try reflashing my recovery (TWRP again since my most recent nandroid backup is in that format), but I want to know if anyone here has a better idea before I start doing potentially irreversible damage to my phone.
Thanks in advance!
Click to expand...
Click to collapse
Flashing your recovery won't damage your phone in anyways. The best method I can recommend is to flash your phone's stock rom using odin. Usually flashing stock is helpful after soft breaks and bootloops. Flash stock and then you can install twrp and restore your backups. And about those ghost inputs. Sometimes with phone being charged with a non-standard cable those ghost inputs will happen. And if your phone gets wet this issue will show up. Try using another charger and cable and see if they happen again or not.

Stuck in "Deleting all Data..." Loop

I think I've brought this upon myself - probably had a "delete all data after X incorrect password tried" set up, then my phone was in my sweaty pocket and the buttons pressed randomly...
Here's what happens when I turn the phone on
1) Normal boot into Android
2) Immediately a popup is visible "Deleting all data..."
3) Lockscreen is visible behind the popup but not accessible
4) Unable to take any step except reboot phone because I can't provide my PIN
5) Things start up as normal in the background, apps load, notifications come in, etc
6) Phone abruptly reboots into a blue screen that reads "Erasing..."
7) Phone reboots into recovery
8) I can then reboot the phone into Android again, go back to 1) above
Here's what I recall of how I've set up my phone
- Rooted via engineering boot image
- No custom bootloader
I don't think any data is actually deleted which is strange... everything that happens behind the "Deleting all data..." popup leads me to believe it's not successfully deleting (at least most) data.
Is there any way I can get out of this loop? Or possible backup all my phone data and restore it after I've reflashed the phone?
Any advice greatly appreciated, thanks

ninegoodthings said:
I think I've brought this upon myself - probably had a "delete all data after X incorrect password tried" set up, then my phone was in my sweaty pocket and the buttons pressed randomly...
Here's what happens when I turn the phone on
1) Normal boot into Android
2) Immediately a popup is visible "Deleting all data..."
3) Lockscreen is visible behind the popup but not accessible
4) Unable to take any step except reboot phone because I can't provide my PIN
5) Things start up as normal in the background, apps load, notifications come in, etc
6) Phone abruptly reboots into a blue screen that reads "Erasing..."
7) Phone reboots into recovery
8) I can then reboot the phone into Android again, go back to 1) above
Here's what I recall of how I've set up my phone
- Rooted via engineering boot image
- No custom bootloader
I don't think any data is actually deleted which is strange... everything that happens behind the "Deleting all data..." popup leads me to believe it's not successfully deleting (at least most) data.
Is there any way I can get out of this loop? Or possible backup all my phone data and restore it after I've reflashed the phone?
Any advice greatly appreciated, thanks
Click to expand...
Click to collapse
Wipe all except sd in twrp recovery
Restore with stock rom or use twrp backup

to recovery^
ninegoodthings said:
I think I've brought this upon myself - probably had a "delete all data after X incorrect password tried" set up, then my phone was in my sweaty pocket and the buttons pressed randomly...
Here's what happens when I turn the phone on
1) Normal boot into Android
2) Immediately a popup is visible "Deleting all data..."
3) Lockscreen is visible behind the popup but not accessible
4) Unable to take any step except reboot phone because I can't provide my PIN
5) Things start up as normal in the background, apps load, notifications come in, etc
6) Phone abruptly reboots into a blue screen that reads "Erasing..."
7) Phone reboots into recovery
8) I can then reboot the phone into Android again, go back to 1) above
Here's what I recall of how I've set up my phone
- Rooted via engineering boot image
- No custom bootloader
I don't think any data is actually deleted which is strange... everything that happens behind the "Deleting all data..." popup leads me to believe it's not successfully deleting (at least most) data.
Is there any way I can get out of this loop? Or possible backup all my phone data and restore it after I've reflashed the phone?
Any advice greatly appreciated, thanks
Click to expand...
Click to collapse
i was having the same problem when rooting my phone .Go to recovery , immediately keep pressing vol up & down ,u r in recovery. do a full wipe data settle the problem

My Galaxy Note 9 is also stuck in deleting all data due to wrong passcode entered too many times, yet my situation is slightly different.
-The phone is powered on.
-Unable to power off (must enter pin to turn off phone)
-It has a popup "Deleting all data..."
-Lockscreen is visible behind the popup but not accessible
-Unable to take any step because I can't provide my PIN
My phone is not rooted. Its normal and I am not all that tech savvy.
-Is it safe to pull the battery?