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

[Q] Stuck booting into Download mode

Okay, so as far as I am able to find... This problem is pretty unique...
I'm running Cognition 4.5.3 with no software issues. I have had this problem since Cog 3...
Most people have trouble getting their phone to boot into download mode, but NOT ME!
My phone randomly (I can find absolutely no cause or trigger and I'm not really a novice at Android) will shut itself off. Now normally I would not have an issue with this, but when I go to turn the phone on... it boots straight to download mode, and no key combo or anything will avoid it. So I have been testing this out and I can reboot the phone from the enhanced power menu, I can boot into Recovery from enhanced power menu... But when the phone shuts off or when I shut it down, the ONLY way that I can get it to power on correctly, is to plug the phone in and wait for it to show that the phone is charging. Then I can power it on normally...
Now, this issue arose the same time that my phone began to refuse to be recognised when plugged into a computer via USB... and at times the USB debugging and USB connected notifications will remain in the notification bar until I reboot the phone...
Naturally, my first instinct was to try and restore to stock... But since no computer will recognize my phone (even with fresh drivers installed) I cannot use odin to flash to stock.
So to summarize my problems:
1. My phone will not be recognized by a computer. (USB device not recognized)
2. My phone randomly shuts itself off. (Not a big deal, I can live with that)
3. My phone ONLY boots into download mode unless plugged into the charger (Incredibly frustrating when I am not at home or I don't have my car charger)
4. USB debugging and USB connected notifications stick around until phone is rebooted. (Using enhanced power menu. Again, I can live with this minor annoyance)

have you tried reflashing that rom...or trying another?
it could be the random shutdown issue that some cappys have paired with a failing usb port.
try changing roms.

studacris said:
have you tried reflashing that rom...or trying another?
it could be the random shutdown issue that some cappys have paired with a failing usb port.
try changing roms.
Click to expand...
Click to collapse
Hehe... I tried a different rom for two weeks and had similar and/or more problems...
Reflashing doesn't help either.
I've tried my best to troubleshoot this on my own, so I'm not shutting down your attempt to help. Just letting you know I have tried it.
I hadn't heard about a failing USB port problem... I'll read up on it.
Thanks for your help!

Atleast you dont have to worry about soft bricks if it auto boots into download mode

d34thp1ng said:
Atleast you dont have to worry about soft bricks if it auto boots into download mode
Click to expand...
Click to collapse
Actually I do...because USB still won't interface...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

like i said could be a short or something in the usb port...or somewhere in the hardware. if you experience this problem across different software then it has to be a physical defect someplace. cause if it were software related it would fix once you flashed something different...
you can try for a warranty replacement, that requires a little loose morals. you will have to do something to cause it not to boot, or only boot to the at&t screen otherwise they will have proof of root and/or custom rom and void your warranty. once thats accomplished mention some crap about kies failing and they should replace it.

studacris said:
like i said could be a short or something in the usb port...or somewhere in the hardware. if you experience this problem across different software then it has to be a physical defect someplace. cause if it were software related it would fix once you flashed something different...
you can try for a warranty replacement, that requires a little loose morals. you will have to do something to cause it not to boot, or only boot to the at&t screen otherwise they will have proof of root and/or custom rom and void your warranty. once thats accomplished mention some crap about kies failing and they should replace it.
Click to expand...
Click to collapse
Hmmm... a few months back my original USB/Charging cable broke and for a couple of days I was forced to use a generic MicroUSB cable to charge my phone... Could that have cause a short/damage to the port?
My phone does not have warranty as I bought it refurbished. :'(
(Plus my morals aren't that loose.)

Had a similar issue, eventually determined that it was a short in this usb port and did a warranty return. (Only when plugged in could I turn on, etc.)
If that isn't an option for you, you could try flashing CM. For some reason, the cyanogenmod build won't let the phone charge when off. ( Automatically powers back up once the juice flows.)
I flashed a nightly and somehow, magically, my phone would power back up normally ( but wouldn't turn off, unless plugged in without power. So strange!)
Even more weird? I flashed back to stock and the new powering and rebooting stuck. The short wasn't fixed, my phone simply seemed to reverse the problem.
Plus, you would be using cm.
Sent from my SGH-I897 using XDA App

tbrass said:
Had a similar issue, eventually determined that it was a short in this usb port and did a warranty return. (Only when plugged in could I turn on, etc.)
If that isn't an option for you, you could try flashing CM. For some reason, the cyanogenmod build won't let the phone charge when off. ( Automatically powers back up once the juice flows.)
I flashed a nightly and somehow, magically, my phone would power back up normally ( but wouldn't turn off, unless plugged in without power. So strange!)
Even more weird? I flashed back to stock and the new powering and rebooting stuck. The short wasn't fixed, my phone simply seemed to reverse the problem.
Plus, you would be using cm.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks! You guys have pretty much answered my questions...
I don't want to leave my nice DG Rom though.
Since I have determined that it is a hardware problem... I think I'm just going to live with it for a few more weeks until I can afford to go ahead and buy the newer build of the Cappy... (Might even wait until the SGSII comes out.)

You should be able to get warranty replacement, just make sure the device is in a stock condition when you take it in!

tbrass said:
You should be able to get warranty replacement, just make sure the device is in a stock condition when you take it in!
Click to expand...
Click to collapse
Even though I purchased the device as a refurbished device?
The only problem is that I can't Odin back to stock...

Cease1 said:
Even though I purchased the device as a refurbished device?
The only problem is that I can't Odin back to stock...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=995143&highlight=safely+to+stock
this will get you to stock then look in forums for how to change boot animation change that to stock boot logo and your good to go i did read some were you could do boot img all on phone i belive. i cant find thats up to u

Okay so I called them and let them know what the phone was doing and they tried to send me to samsung to have them repair the phone...

I now hold in my hands a shiny new 1102 build Cappy... Took it to my local device service center and explained the random shutdowns and the booting into download mode and they replaced it no questions asked!
Now to get Cog 5b2 on here.

[Q] Stuck in a boot loop, cannot access recovery

Alright I am stuck. I've spent three days searching all the forums I can find, trying everything I find, and none of it has worked.
I was running the Decrap ROM on my phone no problem up until the OTA update started coming through. It failed the couple of times it tried to install. Then the Revolt ROM 1.0 came out. Made a backup, and flashed that one over the Decrap ROM, no problems. Revolt 1.1 is released, I flashed back to stock, then flashed 1.1 over it. It was running fine for a few days, except for two FC on the phone. Then I got a call from my girlfriend, tried to answer it, and the phone FC but was still ringing. I tried opening the dialer to call back, and it kept force closing. I rebooted the phone, and my real problems started.
The phone now goes through this process...Vibrate > LG splash screen > blank screen > Vibrate > LG splash screen > blank > repeat.
The only way to make it stop is taking the battery out. Every time I plug it into the wall or computer (with or without a battery) the process starts automatically. I cannot get into any sort of recovery no matter how long I hold the volume and power keys. I tried taking the battery out, SIM card, and SD card. I plugged it into the wall with and without a battery, let it charge overnight, no luck. I tried the SDK method with fast boot but I cannot get my computer to recognize the device because it keeps trying to restart itself.
The only thing I have not tried is the LGNPST method because I read of problems people were having even after recovering their phone, and I figured that if the SDK method would not work because my computer did not recognize the device neither would this.
Does anyone have any other suggestions? Or am I going to have to bite the bullet and pay for a replacement?
Thanks!

Sent you a pm
Sent from my VS910 4G using XDA Premium App

I have not had the exact problem you do, I can get the phone to charge. But I have also had repeated problems with not being able to boot my Revolution. This has happened consistently no matter which ROM I've used. I've factory reset and tried Decrap and Revolt both. I can reboot my phone fine, but if I ever turn it off overnight, I go back to a blank screen after boot in the morning.
It seems a number of non-root users have this problem. You might be able to go in for a replacement, see:
https://www.youtube.com/watch?v=IOGM__SQB6Y
I'm not sure if having a low battery contributes to the problem, but I do know that Clockwork works better with a full battery.
Have you tried plugging it in without the SIM and SD card?

Charging without Battery
http://forum.xda-developers.com/showthread.php?t=1211935&highlight=can't+boot+to+clockwork
Well, this morning, I ended up in exactly your positions, despite having a full battery.
I tried the suggestion of plugging the phone in without the battery and letting the bottom lights flash on and off about five times. Then I put the battery back in and it booted to the charger.
still can't get to Clockwork though, if you find a solution, please post.
Update: I ended up getting back to Clockwork. Can't say exactly what did it, but what seemed to work was:
1. Charging the battery fully overnight
2. Removing the battery and holding the power button down for 30 seconds
3. Leaving the battery out for some time, about an hour I guess
4. With the battery still removed, plugging the phone in and allowing the bottom lights to flash about 10 times
5. Replacing the battery, holding down the power button and volume down.
After a full day of not being able to get into Clockwork, I was able to get in and do a factory reset.

Returning Revolution to Verizon
FYI, I took my rooted, non bootable phone into a Verizon store, and they ordered a replacement. Didn't try anything special and they didn't ask about or look for rooting on the phone.

I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?

nesterbation said:
I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?
Click to expand...
Click to collapse
Try pulling battery, put battery back in, press and hold volume up, press and hold power button, hold both thru the lg screen. Hopefully it will boot into a download mode that is recognized in lgnpst.
Sent from my VS910 4G using xda premium

Didn't seem to do anything different. Still prompting for those USB modem drivers.

nesterbation said:
Didn't seem to do anything different. Still prompting for those USB modem drivers.
Click to expand...
Click to collapse
You are downgrading correct? If so the drivers you downloaded from the downgrade instructions delete those. Go to LGs website download those drivers and then retry again. That's what I did yesterday when it wouldn't recognize my phone in the program. Let me know if it works.
I've Revolted have you?

When this happened to me I contacted Verizon about the issue. Apparently I was not the first person this had happened to. I found on a couple of other forums that non root users had the same problem. Sounds like it may be an issue with the phone in general.
Sent from my VS910 4G using xda premium

Fix my Brick Captivate

Please i need help with my samsung captivate, i've gone through various post and thread in all forum pertaining 2 soft brick or hard brick. But i don't what i can call my own because all i get when i try booting the device in various mode is white display at times with several colour doting display or fading display with several color, whenever i try boot in download mode it displays the white with several colour and at my computer i get gadget driver installation succesful then d phone power off and on which i hear disconnection n connection sound from my pc. so it keep repeat d same thing. pls help how can i fix this. i need genuine solution.... thks

What were you doing before it bricked? ie. Were you flashing something, using it to hammer nails, or mixed it up for soap in the shower?
Sent from my cm_tenderloin using xda premium

-SGA- said:
What were you doing before it bricked? ie. Were you flashing something, using it to hammer nails, or mixed it up for soap in the shower?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
I wanted to install cm-9-20120804-NIGHTLY-captivatemtd on the device. Actual the installation was successful then when i was trying to restore my backup. it now stoped in d process of installing boot sector. after which remove the battery to start again. that was when it started showing that. actuall when i press power to on it doesn't respond but it only show the display when i plug my charger or usb to computer.

I had exactly the same problem. Use a program called one-click unbrick, that will get your phone back into download mode. After that you can use odin to restore stock. Watch out though, I was very happy when this all worked and I booted into stock only to find out that restarting the phone would brick my phone even worse than it was before. Now the computer wont even pick it up at all and it is stuck in a white at&t bootloop screen when I turn it on. When it is plugged in, all I get is a grey battery that isnt charging and it will not go into download mode. I don't know what I did wrong so I cant tell you how to prevent this problem so just be careful.

A jig would likely be your best option to force your phone in download mode.
If you haven't tried it already, try flashing a stock rom using Heimdall. I've had much better luck using that program than Odin with my own phone.

droyd666 said:
I had exactly the same problem. Use a program called one-click unbrick, that will get your phone back into download mode. After that you can use odin to restore stock. Watch out though, I was very happy when this all worked and I booted into stock only to find out that restarting the phone would brick my phone even worse than it was before. Now the computer wont even pick it up at all and it is stuck in a white at&t bootloop screen when I turn it on. When it is plugged in, all I get is a grey battery that isnt charging and it will not go into download mode. I don't know what I did wrong so I cant tell you how to prevent this problem so just be careful.
Click to expand...
Click to collapse
droy... The problem you're describing is exactly what happened to the first cappy I had, fortunately for me, I did it within a week of getting the phone.... I took it to an AT&T service center *aaack*, they were nice enough to tell me that there was nothing they could do and that I should be able to get it sent back in. Fortunately for me, it was right around the time when the 2.3.5 stock update came out and there were a few other people that were having somewhat similar problems. To try and fix it, I tried the jig, which I constructed myself only, ran the meter tests and found out that it didn't work after trying 3 different ones. I sent it back and got another, fortunately, I haven't ran into the issue again, so I think it may just be some kind of fault on the board given that I've never read of anyone else until now running into the problem

Thanks youall, gr8 help

Note 4 Reboot Problem with Weird Temporary Solution

I'll try to make this short.....
I am using N910T3. Phone was charging in car while using (stop by roadside). Out of sudden it shutdown and went into reboot loop and the phone is extremely hot. I took the battery out for soft reset and try to turn on again. Phone will freeze at different screen (Lock Screen, Home Page, Samsung Logo, Powered by Android) and give two separate vibration before reboot.
I thought it is battery problem so I bought a new battery to try, but still the same problem. So I went on to backup all file before I perform hard reset. While doing that, I find out the phone can be use for longer before reboot if it was stay off for a long time. So I have this crazy idea: put it in a fridge. Surprisingly it works! The phone will not reboot anymore and I can manage to backup all file before doing anything else. Also, the phone will not charge if you plug in right after a few reboot.
Then, along with the fridge method, I perform factory reset through normal android setting. Now it will just stuck at powered by android screen while in reboot loop. I then try to flash with Odin, multiple times. Flash by Odin is complete, phone restart, then it freeze and reboot, at different screen (Installing system update, Erasing, powered by android).
Out of frustration I try with the fridge method to flash, and IT WORKS AGAIN!!!. The phone can now boot to welcome screen where you first setup your phone. However, it will then freeze again and reboot while doing so.
There was only this one time, where I left the phone off for a day after flash with a previous stock ROM, turn it on and skip as much setup as I can, finally reach the homepage screen, then will stay on without any reboot issue. I thought I finally fix it. I then power off the phone, put in my Sim Card and SD Card, power it on, then again, reboot issue appear.
I tried flash with latest stock ROM, previous stock ROM (one updates away), flash any stock ROM with pit file. I sometimes will get error code on device after flash (can't remember the exact error). I also cannot boot into recovery mode without flashing a twrp. Sometimes if success, I will get straight to Lock Screen without going through the phone welcome setup process. But again, none of these I tried can solve the reboot loop.
I may went too far and mix up all steps to the phone. Does anyone have any idea how to fix this? Or is my phone, as I believe, has a faulty motherboard that cause the reboot loop? Thanks in advance for reading through my problem!

Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.

oscarmaldonado said:
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
Click to expand...
Click to collapse
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.

jackgan said:
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
Click to expand...
Click to collapse
Try a firmware flash before newsest. Then take the ota

anyone know if a 910t3 mother board will fit in a 910t frame? Asking cuz I wanna switch them out.