Database Develop

Boot loop

And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk

I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.

Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.

Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.

What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App

Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?

sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)

Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?

Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.

Cal you never mentioned if you cleared the user data... Did you?

Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)

cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.

Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?

I ran into the same problem, trying the same solution - any luck the second time?

JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...

confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks

My Bionic has lost its marbles

Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.

lemonoid said:
Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
Click to expand...
Click to collapse
after the FXZ did you do a factory reset or did you just reboot?

Just reboot. That's what I've always done, I've FXZ'd it three times. I don't even know how to do a factory reset after I FXZ it.

lemonoid said:
Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
Click to expand...
Click to collapse
I would probably do the FXZ one more time and if the problem persists, then I think you know it's a hardware issue - warranty at that point.
Good luck and let us know how it turns out.

lemonoid said:
Just reboot. That's what I've always done, I've FXZ'd it three times. I don't even know how to do a factory reset after I FXZ it.
Click to expand...
Click to collapse
Do a fxz and then boot into recovery and do a factory reset. Then report back! good luck!
Fyi a fxz doesn't wipe data like previous sbfs from Droid x and other moto phones
Sent from my DROID BIONIC using XDA Premium App

^^^Everything they said.
Also, stop using Advanced Task Killer.

mistawolfe said:
Also, stop using Advanced Task Killer.
Click to expand...
Click to collapse
Yeah, task killers are the devil for root users.

Yeah I usually have ATK disabled, but last time I did my Titanium Restore I forgot that it was in one of my profiles, I was doing some mods/tweaks to some apps and that was in my tweaker profile. But anyways on to the issue at hand, I did go into recovery and do a factory reset and it fixed it. I didn't FXZ again, I figured if a factory reset should do the trick, and it did since I had already FXZd.

lemonoid said:
Yeah I usually have ATK disabled, but last time I did my Titanium Restore I forgot that it was in one of my profiles, I was doing some mods/tweaks to some apps and that was in my tweaker profile. But anyways on to the issue at hand, I did go into recovery and do a factory reset and it fixed it. I didn't FXZ again, I figured if a factory reset should do the trick, and it did since I had already FXZd.
Click to expand...
Click to collapse
I would just uninstall it and never use it again. ATK that is...
Sent from my DROID BIONIC using xda premium

I would just like to commend you for not immediately going to Verizon for a warranty replacement. It is people who replace before researching the cause of their problems that cause us to be presented with these phones with locked bootloaders. So, again, kudos on asking questions and figuring it out without replacing the phone. If only everyone would follow suit.
Sent from my DROID BIONIC using xda premium

I can't stand not being able to fix something that is broken, especially when i broke it and even more so when its an Android device. People who take the easy way out just show me that they don't like to learn. ever since my Eris i have been trying to fit in time to learning more about Android, programming and software development. Warranty replacement would void my commitment to learning. So thanks for the kudos bro. Just wish that more people got enjoyment from learning.
Sent from my DROID BIONIC using xda premium

lemonoid said:
I can't stand not being able to fix something that is broken, especially when i broke it and even more so when its an Android device. People who take the easy way out just show me that they don't like to learn. ever since my Eris i have been trying to fit in time to learning more about Android, programming and software development. Warranty replacement would void my commitment to learning. So thanks for the kudos bro. Just wish that more people got enjoyment from learning.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
THIS... omfg this is exactly how I feel. :-D

[Q] Bionic constantly rebooting after ICS OTA update

Hey everyone I'm new to this forum. After I updated my bionic to ICS last week I have had nothing but problems. The phone constantly reboots itself. It might stay on for 5 seconds or 3 hours. I was wondering if there is anyway to go back to Gingerbread or a way to install a rom that will work. Any help would be greatly appreciated.

There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.

Sir_Eagle said:
There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.
Click to expand...
Click to collapse
I have reset it 3 times. Still reboots all the time. I tried taking out the microSD card doesn't help either.

I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.

stevendbrady said:
I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.
Click to expand...
Click to collapse
I should be getting a new battery in the mail tomorrow. I will let you know what happens. Thanks for the help.

Ha, it's been a month, but did it work? Or did you get it working otherwise?

I experience the same issue.
I RSD Lite and FZX my phone back to stock and it seems to work for another 5 days or so. I've tried to nandroid a backup when it's good then restore it when it goes nutty but that doesn't help. I've flashed the FZX image, then used Safestrap to flash a CM-based ROM in Slot1, but when the stock goes TU, so does the other.... and vice versa.
I haven't tried batteries.

I just got this phone in the mail yesterday off of e**y and it has been rebooting all the time too. Not consistently though but enough to make it aggravating. I just got it rooted and somehow was able to get safestrap3 on it. Went into the twrp recovery and wiped cache and dalvik and rebooted from there. So far ok but it has only been about 10 minutes since I did that. I have already done 3 factory resets and even wiped cache in stock recovery. I used my X2 to record the craziness of this phone doing it's own thing but with the guy above talking about the battery maybe being faulty I might have to try that because the phone has at 0% when I got it and I don't know how long it was dead for. Does not being charged for a long time ruin a battery?

[Q] Did I do the unthinkable? *BRICKED* After 2 days ownership.

Have checked as many threads and post as possible - And I think I have royally screwed up. Problem is My HTC Google Nexus One will only vibrate continuously until either the battery or power is pulled. I did root the phone, and installed Clockwork Mod recovery making a full back up of the factory image. This was as far as I got in my quest to upgrade the OS to something more modern.
The phone worked for a day and a half after rooting, and worked fine after installing ROM Manager. But i kept getting prompted to upgrade from 2.1 Eclair to 2.3.6 Gingerbread. So I tried to run that upgrade and it failed with a triangle with exclamation mark. I rebooted and thought nothing of it. Later I installed Snapchat, and an hour after that the phone wouldn't respond to accessing 'settings' or any other system folder. So I had to pull battery. Tried to reboot and it stalled at the starting animation and that was the last action I saw from both the screen or otherwise.
So although I read there is a risk to rooting your phone, I figured it went smoothly as the phone functioned well for a day and a half.
Anyone have any thoughts on this? I read if you can't get to any of the 3 boot screens then you're bricked. I just can't understand how it happened so easily?

[Q] Power-On Lag/Freezeing

So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)

I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.

wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).