Related
something interesting happened to my NC last night. i was messing around with system apks, trying to get better access to the system settings. i copied Settings.apk and SettingsProvider.apk from the 2.1 emulator to /system/app the NC. they didn't work, so i replaced Settings.apk with the original, but forgot to replace SettingsProvider.apk. bonehead mistake. anyway, upon rebooting, the device was stuck in a bootloop. it would get to the white "Nook Color, by Barnes and Noble" boot animation, and just loop over and over. i tried the factory reset twice, but as i expected, it didn't help.
i decided to give up for the night, and left the NC plugged into AC power, bootlooping over and over, just to see if anything would happen. after about 30 minutes, i tried to shut it down by holding the power button. the screen went off, and i set it down. when i looked back a few seconds later, the NC was booting again. this time, it came to the screen shown in the attached photo. on the screen, it says "A new software update is being installed. This will take a few minutes."
the process finished, and the device booted up into a fresh, clean, non-rooted 1.0.0 installation! a real software update wasn't installed. it seems the device decided to reflash the original ROM on itself. can it be that the NC is smart enough to know when something is catastrophically wrong, and flash back to stock? either way, i'm happy to have my NC back in business
pokey and I were talking about this in another thread (though he's better at dissecting this stuff than I am). There's a counter for unsuccessful boot attempts, and after 8 it apparently flashes "factory.zip" from partition 3, which is a full clean factory dump.
This actually happened to me, sort of, two nights ago. I was messing around with system settings, but didn't change anything too important...or so I thought.
Shortly after, I was using my Nook, as it was working normally, and the initial setup screen popped up, said something about being unable to authorize my account, and then went ahead and factory reset itself,forcing me to have to re-root. Pretty annoying, and it was odd, since my Nook seemed to be working fine.
It may be worthwhile to make a modified factory.zip so devices wouldn't lose root, no?
I haven't yet encountered this problem, but it would suck to have to reformat my microSD card if this should happen.
tokyomonster said:
This actually happened to me, sort of, two nights ago. I was messing around with system settings, but didn't change anything too important...or so I thought.
Shortly after, I was using my Nook, as it was working normally, and the initial setup screen popped up, said something about being unable to authorize my account, and then went ahead and factory reset itself,forcing me to have to re-root. Pretty annoying, and it was odd, since my Nook seemed to be working fine.
Click to expand...
Click to collapse
Mine did this exact same thing too. I messed with the settings apks and then when I went back to the B&N home screen an error about not being able to authorize and the device needed to be reset. then it rebooted and performed a reinstall of 1.0.0
clockworx said:
pokey and I were talking about this in another thread (though he's better at dissecting this stuff than I am). There's a counter for unsuccessful boot attempts, and after 8 it apparently flashes "factory.zip" from partition 3, which is a full clean factory dump.
Click to expand...
Click to collapse
well there you have it. a nice feature, for the reckless
any idea where the counter is kept?
might there be some way to put factory.zip on the SD card, and force a flash? this would just be a parachute in case something gets too messed up for the failed boot counter to work.
This can be done manually too. Look on nookdevs.com for NookColor_UnRooting
Withfeeling said:
This can be done manually too. Look on nookdevs.com for NookColor_UnRooting
Click to expand...
Click to collapse
That isn't the same thing. It only fixes a few things (like Ramdisk, obviously), while this thread is referring to a complete clean /system.
clockworx said:
That isn't the same thing. It only fixes a few things (like Ramdisk, obviously), while this thread is referring to a complete clean /system.
Click to expand...
Click to collapse
actually, in a quiet, unassuming box at the bottom of the nookdevs unrooting page, it does describe a method to flash back to stock. apparently you hold volume down (minus) while powering on. it's easy to miss. i'll break that bit of information out into it's own page.
Ben74 said:
actually, in a quiet, unassuming box at the bottom of the nookdevs unrooting page, it does describe a method to flash back to stock. apparently you hold volume down (minus) while powering on. it's easy to miss. i'll break that bit of information out into it's own page.
Click to expand...
Click to collapse
nookdevs wiki updated:
http://www.nookdevs.com/Flash_back_to_clean_stock_ROM
Given this possibility, is there a way to backup a rooted NC so it would be easier to rebuild after an inadvertant flash.
Some of us noticed that "quiet, unassuming box".
blacter said:
Given this possibility, is there a way to backup a rooted NC so it would be easier to rebuild after an inadvertant flash.
Click to expand...
Click to collapse
This, built-in, mechanism seems like a pretty bullet-proof protection against bricking your Nook Color. The Nook Classic has a similar mechanism. I think it's a great idea and I wish all these new tablets had such a capability.
I'm loving the Nook Color but other things require the money right now so it's going back, for now.
I just did the Home+Power key combination and it did a reset. I re-registered the device to make sure Angry Bird and a few other things were gone and they are. I got a notice at the bottom of the home screen saying something about a software update and it just said I was currently on 1.0.0, I clicked it and it went away. But, in Settings and Device Info there is a Erase & Deregister Device option. When I click the option it says the following "This will remove all digital books and files, including side-loaded content, from this device. The titles you have purchased will remain in your B&N account." I find this interesting since it specifically mentions "side-loaded content" and I'm wondering if this also triggers the 'factory.zip' file and as a complete factory hard reset of files and all. I haven't seen it mentioned anywhere else so I thought it might be worth mentioning.
Cheers
I rooted my NC yesterday using the auto-nooter 2.12.25. Things seemed OK. I DLed some apps & used them. Got ADW launcher loaded and began setting it up for my preferences. The NC went most of the way through an update cycle even though I had already updated to version 1.0.1. However this time it never got to the green "n" and then it started cycling through the part where it comes up & writes "nook color", continues until the colors quit flashing & then starts back at "nook color".
None of the buttons seem to have any effect. I tried to follow the 'solution' entitled "NookColor Fix Boot Loops". I tried both the auto-nooter SD card and then when that didn't work, I tried the original manual nooter SD card.
Anyone have another idea to fix this. I'd really appreciate some help. A PM would be great or just answer here.
I had the same problem earilier today, I held down the power button until it did a complete reset (about 8 seconds of holding). It is working great since.
Thanks. I had already tried that, several times.
restore to factory and start again?
add http : // www to front of links with out the spaces i don't have the 8 post count needed to post links and
am not going to just reply needless info to 8 post to get rights to post links to help
don't get me wrong i believe it is a very good policy
unrooting
.nookdevs.com/NookColor_UnRooting
flashback to clean stock
.nookdevs.com/Flash_back_to_clean_stock_ROM
i have not tried any of these methods no need to but i do so much messing up
i guess eventually i will with that said this might be a long way around to your solution
read both carefully
Thanks, nookroot but this is not working.
Method 1 for unrooting - Holding those 3 keys together for over 30 seconds has no effect.
Method 2 for unrooting - I can't unroot with method 2 because the NC has to boot before I can go to settings.
Any other suggestions? In fact it seems that if it ever does power off, the only way to make it power on is to plug in its USB cord & this doesn't always work. When it does it just stats cycling. Sometimes it seems to just power up on its own and start cycling.
Whatever happened, since it's rooted I can't return it to B&N and I don't seem to be able to unroot it. Effectively I have bricked it even though many people say that's impossible.
Edit: something new just happened & I was able to go through the method 1 reset. It's booting now & looks like the B&N screen is coming up. I'm not sure how it happened. I'm going to leave it unrooted until I feel adventurous (or foolish) again.
P.S. Came back with version 1.0.0 SW.
HI All,
So, i have a brand new NC. I was eagerly looking forward to using it as a tablet.
So, here are the steps:
1. I open it, turn it on, register it on B&N, play around with it; power it all the way down. (never hooked it up to my PC).
2. I burn auto-nooter3.0 on to a microSD card (using http://forum.xda-developers.com/showthread.php?t=942424) as my gospel.
3. Place microSD card in NC; hook up to PC -- and, nothing.
It does absolutely nothing. it doesnt boot up, it doesnt do anyhing.
now I can't get it to turn on at all.
Thanks for your thoughts on what I should do next??
Have you taken the SD card out and tried powering it on?
I'm not sure exactly what went wrong, but I would re-read the auto nooter steps, and like said above remove your sd card and see what happens.
Also you need to read more of the forums and see the NC is extremely hard to brick...
and figure out the multiple ways to fix it. there are forums where you can post issues with the bricks and i'm not sure the dev forums is where you want to do that. Many devs may not have time to help you and those who are skilled in this area aren't searching here.
Sometimes it takes hitting the power button several times in a row before it responds.
Yes, took out the microSD card, and tried to power on--- and, nothing. it
Take your power cord and plug it in and press the power button repeatedly somewhat fast until you see the screen flicker, then stop.
I see you missed the first step. Charge it up. Try plugging it in for a while
Hold the power button down for 5-7 seconds until it resets
Sent from my NookColor using Tapatalk
When you plug the nook color into the computer IT WONT DO ANYTHING!!! WAIT FOR IT. Turn the sound up on your computer you'll hear it connecting, disconnecting, etc. Just be patient, jeez! Learn to carefully read.
Sent from my NookColor using Tapatalk
Autonooter 3.xxx.x is for B & N firmware 1.1 You said your NC was brand new... out of the box it could have 1.0.0 or 1.0.1 firmware as well--most likely it wasn't 1.1 If you turn it on and off enough times (theres a correct point at which to turn it off as it is still booting, then turn back on--repeat 8 times) it will trigger a self-repair back to stock. You can get the side-load update and instructions from 1.0.1 to 1.1 from B & N web site. Your NC is not a brick, it's just feeling lousy at the moment
You still broke?
I feel your pain
Try viewing these videos and following the directions EXACTLY. First go back to stock, re-register your NC with B&N, make sure your firmware is updated to 1.1.0 (this is important because autonooter 3.0 can only be used with that firmware), get a gmail account if you don't have one, then try to root again.
To go back to stock:
http://www.youtube.com/watch?v=U_gNvZGSJD4
Rooting with autonooter:
http://www.youtube.com/watch?v=MUoHALWvPts
Written directions here:
http://forum.xda-developers.com/showthread.php?t=942424
Good luck!
I've got an 896 Rogers Captivate that has been draining my sanity for hours now.
I managed to get it to download mode exactly ONCE out of ... literally eight hours of hold buttons, remove battery, replace battery, hold buttons, remove battery, etc etc.
I reached download mode by using the three button technique Volume Up + Volume Down + Power.
Once there I idiotically said "I can get here again.." and removed the battery.
I got this phone from a family member and managed to get it to download mode, but every other time I hold buttons (any buttons) it does exactly this:
If plugged into the computer it shows the loading daisy (which doesn't animate). I can hold any combination of the volume buttons and power button and it will flash black and return to the daisy.
If not plugged in, it shows the model number and 'Samsung'. Behavior is the same. Holding volume up, or down and the power button will flash black after eight seconds and then show the model and 'Samsung'.
I haven't tried Odin (although I've downloaded it and a rom thusly), a Jig, or any of the other brute force approaches to reaching download mode simply because I know that if I reached there once, I should be able to reach there again. Computers aren't sentient (although I swear this phone enjoys tormenting me).
Does any body have any insight to why I would be going through this?
Why won't it reach download mode again?
Just fyi: I have literally tried every button combination I can suss from the countless threads I've scoured and scanned.
Thanks in advance for any insight anyone can provide.
Just to make sure, as I didn't see it in the post, you did do v+/v- and insert the usb cord from a powered off state, right?
Also, check the captivate connection issues thread in my signature if you haven't already.
Different reaction
Hey thank you! Your list is handy!
I'm shocked I hadn't stumbled upon it already, or your signature for that matter..
Seriously can't understand how this is the first time I've seen it.
I've tried the [FROM A POWERED-DOWN STATE - BATTERY REMOVED] procedures but none of them got me into download mode.
Thanks all the same.
I'll try the battery charging list next.
Quick (and possibly stupid) question : Does it matter if it's an official Samsung USB cable?
As I noted in my initial post, I managed to get into download mode earlier today (little Android digging my grave with the same cable I've been struggling with for the past six hours.
Luck!
omigodomigodomigodomigodomigodomigod
okay, so I managed to get into d/l mode by plugging to power (outlet usb) and then applying three buttons.
So:
Battery Out
Plugged into USB
Battery In
Hold VolUp+VolDown+Power
Android man digging my grave showed up.
It should be noted that this same process was conducted several times against my PC upon which the technique worked several hours (and several hundred attempts, and half a season of StarTrek TNG) ago.
...now what (lol!)
I guess I'll fire up Kies and conduct a few more hours of scouring!
well you COULD go about flashing roms and kernels and modems to your hearts delight. But I would advise against that. I'd recommend first backing up EVERYTHING. Especially your /efs (you'll need to be rooted) folder if your considering flashing a rom. Once you do that you're free to flash. Just be sure to read the OP of the rom to make sure you meet the requirements for the rom or kernel, such as if you have the right boot loaders. As long as you read, you really can't go wrong with the captivate.
Sent from my SGH-I897 using XDA App
I'm not entirely sure how the phone reached this state but according to all the stuff I've read, if the phone is in this state it's recoverable using Kies.
However Kies doesn't seem to care that I've got this phone plugged in.
Frankly, there's nothing to back up, and if flashing out with Odin is the only way to establish a working Captivate then I suppose i've got some files to download.
Does anybody have any insight regarding Kies and getting it to play nice nice?
Do you have Samsung drivers installed?
Personally, I have only got Kies to work when the phone was actually on.
Sent from my SGH-I897 using XDA App
If your in download mode, I suggest just flashing back to stock using heimdal.
(I don't use odin 1-click stocks because my first attempt at using it corrupted my bootloaders. My phone would power on, go through the AT&T screen for hours. I also could not enter recovery or download using 6 different methods including a jig. I lost hope and accidentally left my phone on when I went to bed. I wake up next morning and it booted up. I used terminal emulator from the market and used the command Reboot Download. I worked, then I flashed back to stock using hiemdal. I am not completely sure why I shared this story but w.e )
Hi there!
I'm wondering if you guys can help me brainstorm, or at least get to the root of the problem. Alright, so to preface... I'm using an ATT Galaxy S Captivate [i897]
I was updating my version of MIUI from the miui.us version 2.3 to version 4.0 [ICS.] This worked fine, and I had backed up my data with TitaniumBackup. However, I made a mistake: I chose one of the backup all options, where it backed up all my system data and app data. Little did I know, restoring the system data would completely own my phone. So I did a restore, rebooted, and my Captivate sits at the boot animation indefinitely. It won't get past it.
Somewhere along the line, my download mode and recovery mode 3-button combo got borked. They no longer work [trust me, I've tried every one.] When I try to enter recovery by pressing and holding a number of volume and power button combinations, it goes straight to the boot animation after the AT&T screen. When I try to enter download mode by pressing and holding volume/power, battery in, cable in, and every other possible combination [including switching the cable to different ports on my computer,] I simply get a "stuck" circular loading icon which flickers every few seconds. When I let go, it shows me a grey battery icon with that stuck loading circle overlaid.
So, moving on, I decided to disassemble my phone and try to reset it by shorting the TP contact in the back against the SD card slot. I wish I could find the thread; it's supposed to reset the device. It definitely causes my captivate to reboot [while it was stuck in the boot animation] but it didn't fix the problem. So I decided to make my own jig.
I built it out of three 100k ohm resistors, was super careful not to contact the metal parts of them while I plugged it into my phone. I tried plugging the micro B cable in first, then touching the resistor leads to pins 4 and 5 on the back end of the USB jig, but to no avail. I tried slightly different resistances, but no go. I tried connecting every pin to every other pin just for the hell of it, and no luck there either.
I don't have a soldering gun, so J-tagging is not an option [before I just buy a new phone, anyway,] and I'd rather not buy a USB jig because I'm not convinced it'll work. I know there are a lot of factors, and everyone says to try it 400 times, but I tried it more than I have patience for already. There's got to be something else wrong.
I'm wondering if TitaniumBackup has the capability to mess up the boot loader? If I accidentally overwrote system files with older ones, why would that cause it to get stuck in a bootloop? And where did my download mode go?
If anyone has any ideas, please let me know! I've done a massive amount of research on this. And I found some pretty brilliant ideas along the way, but none of them seemed to work for me. I'm to the point where I literally can't find any more references to problems similar to mine, so I figured I'd ask you guys!
TL;DR: I think by [accidentally] restoring system files with TitaniumBackup from MIUI 2.3 to 4.0, I may have completely owned the boot loader. Can this happen? And is there any fix? I can't get into download or recovery with button combination, jigs, or short-circuiting my phone in fun new ways.
Thanks
The phone by itself is not capable of writing to the bootloader. I am at a loss for why it doesn't work. All I can say is keep trying.
Sent from a jelly bean
korockinout13 said:
The phone by itself is not capable of writing to the bootloader. I am at a loss for why it doesn't work. All I can say is keep trying.
Sent from a jelly bean
Click to expand...
Click to collapse
Well. It might just be the way you wrote it, but you said "I try to enter download mode by pressing and holding volume/power, battery in, cable in...".
The correct method is exactly this.
1. Pull your battery.
2. Hold down volume button.
3. Insert battery.
4. Plug in USB.
5. You should be in DL mode.
Give it a try even if you think you have done it before....