Database Users

[Q] Nook stuck in reset loop

I have a rooted, but otherwise stock nook that I was having trouble installing apps from the amazon appstore on. I was trying to find some settings to fix this when all of a sudden it said something about an "authorization error" and reset. When it came back up, it was resetting data and I had to go through all the setup again. When I get to the point where I set up my account, I get the message "Sorry, we're having touble setting up your NOOK. Please shutdown sthe device and try again". Every time I reset it goes back to the same thing. Can I do something to fix this, or do I need to go throught the "restore to stock" and start over?

This happened to me and is the reason that i was driven to install CM7 to emmc.
It was a while ago, but i think i was able to fix this using the debug bridge. I would have to say that restoring to stock is probably your best option, especially if you don't have a recovery rom.

Ok, it's been a while since I've had a chance to look at this (and since the pad works with my CM7 boot card it's not been a priority). I have this to restore to stock: http://nookcolorrooting.com/RestoretoStock.aspx, but when I get to the 2nd step booting with the n key held in doesn't seem to do anything....it just boots up as normal. Is there some trick in how long to hold the button down?

Are you continuing to hold power + n while it's booting?

I've tried it several different ways, including holding the n button down until it has completely booted up.
I did find some instructions for using the clockwork mod recovery to flash the original files and am in the process of working through that.

[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] S4 won't turn on after encryption

Hi guys,
The [email protected] app asked me to encrypt the device in order to use company e-mail and VPN. I hit "Encrypt my device" and a different than the usual Android logo appeared but the device turned off. I started it again and tried once more time but now using "Fas encryption" option. Device displays the same logo and turned off.
I just thought encryption didn't work but then I tried to boot up again and now it asks for the password, I type it, it shows that Android logo and turns off again.
Do somebody know what to do in this case?
It's ok to lose the data since I have nothing special stored.
Thank you in advance!
Update: after a few attempts I managed to wipe the entire device from Recovery.

viva_zidane said:
Hi guys,
The [email protected] app asked me to encrypt the device in order to use company e-mail and VPN. I hit "Encrypt my device" and a different than the usual Android logo appeared but the device turned off. I started it again and tried once more time but now using "Fas encryption" option. Device displays the same logo and turned off.
I just thought encryption didn't work but then I tried to boot up again and now it asks for the password, I type it, it shows that Android logo and turns off again.
Do somebody know what to do in this case?
It's ok to lose the data since I have nothing special stored.
Thank you in advance!
Update: after a few attempts I managed to wipe the entire device from Recovery.
Click to expand...
Click to collapse
I get the same now, anyone have a fix?

Have you tried flashing a stock ROM via Odin and performing a factory wipe before booting the newly-installed ROM for the first time?

audit13 said:
Have you tried flashing a stock ROM via Odin and performing a factory wipe before booting the newly-installed ROM for the first time?
Click to expand...
Click to collapse
the phone was rooted and everything worked so i dont think that is the issue

Stuck in BootLoop and Factory Wiping doesn't actually wipe anything

Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.

same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.

I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?

eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.

Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911

Constant restarts

Hello
Since this morning my Note 3 has died. I went to turn it on and it did not go beyond the initial Samsung boot screen.
I have already tried almost everything:
- Enter in recovery mode and make wipe dalvik and cache
- Enter in recovery mode and make wipe factory reset
- Install a new ROM for Odin
When Odin finishes, he gives me the PASS in green as all correct. I start the phone, enter the initial configuration screens, let me put the language, wifi, Google account but when the automatic configuration of the applications starts, it restarts and loops in trying to boot, but does not pass the Samsung logo.
I tried to install the ROM again, in case there had been any problems during the installation (despite giving the PASS in green), but it does not work.
The only thing I can think of is to put another type of ROM of those in which the option Re-Partition is marked, which I think is more exhaustive, but I'm not clear what kind of ROMs those are.
I would appreciate any help with the ROMs with Re-Partition, or any other suggestion that you could give me, to see if I can resuscitate it.

Are you performing a factory reset after flashing a stock ROM with Odin and before the phone boots the stock ROM for the first time?

but when the automatic configuration of the applications starts, it restarts
Reads as an app or something is the problem .

Thank you very much for your responses. After searching a lot, I found a ROM of 4 files + PIT. After installing it, the phone works correctly.