I bought a used Nook Color this spring on ebay, already rooted. It is JellyBean 4.1.2, CM10-20121216-UNOFFICIAL, ParanoidAndroid 2.99. It had Goo Manager, but not TWRP that I could tell.
It's always gone into boot loops, when I asked the seller he said use Goo Manager to look for an update. There has never been an update found. I tried installing TWRP through Goo Manager today, but it tells me no recoveries found. May have managed to install from the computer's Play Store, haven't been able to check yet because it is still looping. (Does not look like it downloaded, many updates were ahead of it.)
The past few weeks it has spent more time rebooting than working. Cyanoboot loads, but the little jellybean guy just glows and the eyes move around on the beans. Sometimes it will load after awhile, sometimes it takes hours. I have it charging the whole time, but it does not charge while it is looping. Once it finally loads and I unlock it, it shows a popup that Process Service isn't responding. If I hit wait, it will load.
The NC did not come with a charger, I bought a non-OEM charger on Amazon that was listed as NC-compatible. It seems to work fine, although doesn't quite keep up when watching video or anything screen-intensive. I normally leave the NC plugged in when I am home, when it comes out of the looping it is usually in the 90 plus percent range. I tried leaving it unplugged overnight while looping once, it ran down fairly low but recharged fully after finally loading.
For a week or two before the constant looping started, two other issues appeared. When I woke it up in the morning, it would not be connected to wifi. The icon is just an outline, and when I check under settings it says scanning for wifi networks. If I reboot, it connects fine.
The second problem is the SD card keeps unmounting. Generally I will get a popup from Evernote that the SD card has changed. Most of the time if I go into settings > storage I can see that the card is unmounted and tell it to mount. Sometimes it says it is mounted, so then I reboot. Today I noticed the internal card was also showing as unmounted. I was able to mount both, at least until the NC rebooted itself again. I'm using a SanDisk Ultra (Class 10) 32 GB card.
It finally loaded, but looks like no wifi again. Battery is at 92 percent. It did finally manually connect after telling me avoided due to poor connection (about 5 feet tops away from the modem).
Would re-rooting or flashing a new ROM work, or is something else wrong? Why can't Goo Manager find any updates?
Thanks for any help!
I used that ROM for a while, it had some issues, but for the most part I enjoyed it. The SD I mounting issue can usually be solved by formatting it with your computer, and the bootloops can be fixed by reinstalling the ROM. Make a twrp sd card. (There's a thread in here somewhere) and reinstall it, or install other roms if you decide you don't like this one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also, goo manager simply doesn't work with the pa 2.99 rom. Don't know why.
Mineturtle33 said:
I used that ROM for a while, it had some issues, but for the most part I enjoyed it. The SD I mounting issue can usually be solved by formatting it with your computer, and the bootloops can be fixed by reinstalling the ROM. Make a twrp sd card. (There's a thread in here somewhere) and reinstall it, or install other roms if you decide you don't like this one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also, goo manager simply doesn't work with the pa 2.99 rom. Don't know why.
Click to expand...
Click to collapse
I can't find any recoveries, finally managed to install ClockworkMod's ROM Manager and it says both ClockworkMod and TWRP recoveries are there somewhere. SD card was unmounted again and while remounting it went into a bootloop again
Off to look for the twrp card thread, thanks!
Related
Since I'm kind of a newbie, this isn't so much a HowTo as it is a HowIDidIt. Follow at your own risk...
I had to send in my Atrix for a warranty replacement because the WiFi inexplicably died. Kept saying "error" and wouldn't connect anywhere. Very annoying.
I used Motorola's software update tool on a windows box to flash to the .141 update, which removed the "unlocked" bit. Somehow, though, it dorked up the OS to the point where the status bar was disappearing, phone wouldn't auto switch to incoming calls, etc. Also very annoying. So when the replacement phone came, and I put my SIM card and SD card in, it had the same issues with that. Basically it was barely usable.
Using my linux box, I booted the phone into RSD mode and used sudo ./sbf_flash to flash the 4547-fix-try2.sbf file onto the phone, which allowed me to reboot the phone into fastboot mode and use sudo ./moto-fastboot oem unlock the phone. At that point, I got stuck with the "Failed to boot" business. See http://forum.xda-developers.com/showthread.php?t=1528729.
Then I realized I needed some sort of recovery app installed, and didn't have one, so I found this guy's work http://forum.xda-developers.com/showthread.php?t=1204500 and used moto-fastboot to flash the recovery program into the recovery partition.
Next I needed a ROM to install, and I took the http://forum.xda-developers.com/showthread.php?t=1528729 poster's recommendation to use Neutrino. Downloaded the zip, pulled the SD card out of the phone and stuck the zip on it, put the SD card back into the phone and booted the phone into recovery mode. Then I chose install from SD card, and installed the zip.
After install it gave me a slight scare when it didn't get past the opening motorola screen without rebooting itself, but that must have been part of the process cause it worked fine after that and booted into Neutrino. Which, I'd like to add, is pretty nice. I added a bunch of the add-ons that I use (various syncs, google stuff, and the alarm clock) by downloading them, putting the zips on the SD card by USB, and installing through booting the phone into recovery mode as with installing the ROM itself.
Now I have a usable phone again, yay!
Did the same thing yesterday when I bought a used Atrix to replace my out of warranty atrix's wifi radio. Even reloaded my cwm backup
xandr115 said:
Did the same thing yesterday when I bought a used Atrix to replace my out of warranty atrix's wifi radio. Even reloaded my cwm backup
Click to expand...
Click to collapse
So do you think it was a hardware issue and not a software issue? I could never get a solid answer on that in reading online. Some folks swore up and down that it was not hardware, but I couldn't see how my CM7 suddenly just broke for no apparent reason. I don't THINK I added any funky apps. Maybe I got a virus somewhere?
Last week, following Leapinlar's updated directions, began putting latest nightly cm on the ol' nook. Thought it was okay, but then, on reboot, it just sticks on rotating "Cyanogen Mod" screen (which I take is a boot loop). I waited a long time, maybe 30 minutes, still spinning. That began my frustrating journey. Here's the deal:
Latest nightly cm, 121212 gapps. Same deal. Loads on initial boot, then it powers itself off. Next boot, android keyboard failure, sometimes trebuchet failure. But I have (bearing in mind I have gone through these steps maybe 20 times) seen some success in getting past the keyboard issues and managed to get logged into the play store. Then, on the subsequent boot, spinning splash screen forever. Try again.
Try different gapps files. Sometims I hit one that seems to be digested fairly well, sometimes pretty much all the apps begin failing on the initial cm boot (after the load boot). No matter what, still, on the second cm boot, spinning splash screen.
Try to load gapps again, maybe a different version. I do this through holding the n and going to recovery, which reinstalls the gapps (or some other file). In this case, it seems to inflate all the apps okay, then goes to a "starting apps" screen, and it sticks *there.*
I rolled back to the latest stable version, 7.2 I believe, and got it running just fine on that; ran it for a week with no glitch whatsoever. But it's not the same! I really want this thing to run the latest and greatest!
So this weekend I am back to attempting the latest nightly and I am just getting skunked. It either loops the cm splash on second cm boot (which is the first boot after I set up account, etc), or it, in the case of trying to "after install" a new gapps file, sticks at the "starting apps" screen. Oh yeah, if it does that and I do hard reboot, I stick at the cm splash spinner again. Help!
Maybe a new sd card? (but it did load 7.2 okay). Maybe factory reset to the internal? I have done the cwm alt recovery and cleaned out the caches. I have cleared the data from the android keyboard.
For SD card cm10 installation (use Sandisk class 4 or 6)
Here is LeapinLar's thread to get you started http://forum.xda-developers.com/show....php?t=1941858
Get the latest CM10 nightly here http://get.cm/?device=encore
Make sure to use Gapps 20121011. Newer version will not work.
Here are the steps involved to make a bootable sd card:
Unzip the ...Rev5.zip
Use program Win32diskimager.exe to write the above unzipped image to SD card
Copy latest Cm10 nightly to sdcard (do not unzip)
Copy gapps 20121011 to SD card (do not unzip)
Safely eject SD card from computer
Turn off Nook Color
Insert SD card you created above
Turn on Nook color
Watch the Cm10 splash screen come to life.
wilco
Thank you for the response! Will run out and get a new card. will report later this P.M.
nailed it! It was the card!
Got the new class 4 micro sd card. Followed the instructions, again. Install different this time, with not a single error. On boot, it asked for google info, smoothly, all seemed right. Reboot success! Smooth as silk!. Play Store, the whole deal, perfect! YAY!
THANK YOU XDA-DEVS!
BTW, went to Office Depot for the card. Their website says 13.99 for a 4 gig card; on the shelf it was listed as 17.99. At the register I say, "Your web site has this for 13.99." So the dude does a price override on his terminal (he chose "match competitor's price" then "Office Depot website") and I got it for the lower price!
Hi all
A while ago my trusty nook started to behave erractically and then wouldn't boot at all. I removed the battery, reattached it and still no boot. Before I threw it out I left it for a few days and for some reason it started to boot again BUT it had problems so I flushed all the memory locations, reset it back to CM7 factory defaults and reloaded. All seemed to be well for about a month THEN this week I got the phantom key strokes issue and some erratic behaviour. Today it really started to go wrong, here are the symtoms:
1 100% battery all well and function fine
2 85% battery ( about 15 minutes into a streaming vid) noise on the audio
3 81% play bar on stream started to flash on and off though fingers no where near it
4 80% screen flash then shut down.
5 boot only to seemingly frozen CM7 android logo no looping arrow.
6 can't boot to recovery
7 took out sg card freezes at CM7 logo.
So is this really the end of my old buddy? I have pretty much tried everything.
thanks
Charge for 3/4 hours while turned off completely with stock charger.
Create a clockworkmod recovery sd card. (not twrp since you have touchscreen issues)
Boot into cwm and wipe everything but system and boot. (Battery stats, cache, data, etc)
Reboot.
Charge for another hour.
Profit.
---------- Post added at 10:28 AM ---------- Previous post was at 10:25 AM ----------
If that doesn't work, look in leapinlar's tips thread, and use his format tools to format everything, then boot into cwm from the sd card, and install the latest cm7 stable, GAPPS, etc.
Mineturtle33 said:
Charge for 3/4 hours while turned off completely with stock charger.
Create a clockworkmod recovery sd card. (not twrp since you have touchscreen issues)
Boot into cwm and wipe everything but system and boot. (Battery stats, cache, data, etc)
Reboot.
Charge for another hour.
Profit.
---------- Post added at 10:28 AM ---------- Previous post was at 10:25 AM ----------
If that doesn't work, look in leapinlar's tips thread, and use his format tools to format everything, then boot into cwm from the sd card, and install the latest cm7 stable, GAPPS, etc.
Click to expand...
Click to collapse
thanks for you great advice BUT had already done all of the above before I posted. Rebuilt it from scratch ala leapinlar's tips ( really useful) no luck. Just read a book until the power dropped below 65% then erratic behaviour starts. Was reading using coolreader, first the pages start to turn without any touch. Then menus pop up and icons get pushed. I just shut it down and will power it back up to 100%. Cleaned the screen completely. So pretty sure this is a power issue as it happens at 65% and below. Above that it's perfect.
Replace the battery. That's all I can say. That or get a replacement if you can fake unbroken warranty.
Mineturtle33 said:
Replace the battery. That's all I can say. That or get a replacement if you can fake unbroken warranty.
Click to expand...
Click to collapse
thanks for trying but I'll just keep it for parts. Still would be interested in finding out why low battery makes the phantom key presses appear.
I upgraded my phone to the 2/10/2014 Nightly and it was running ok for a day or so. Then when I went to check my email I started getting massive app and system crashing. I was constantly getting com.google.process.gapps along with apps themselves FC.
I have been running the same version of Gapps on the phone since the beginning, and have installed a bunch of CM 11 nightlies before this. I have CWM 6.0.4.4 for a recovery. I always wipe cache and Dalvik when I do a nightly. The Gapps version I was using was gapps-kk-20140105
Here is where the weird starts. All the partitions are read only, or so it appears. If I wipe user data in CWM the phone reboots to my old profile. If I try to flash a newer nightly, it installs ok but the phone boots to the 2/10 version. If I try to install a different recovery it installs ok but will reboot to CWM.
I can successfully push an image through Matt's utility (1.20 and 1.30), I can push a image through RSD, I can push an image through HouseofMoto. The images actually successfully transfer but the phone reboots to the 2/10 rom. Their appears to be no way for me to regain write access. I can't re-root the phone through Matt's utility because when the phone boots it establishes a USB media connection but never gets into ADB mode(shows device offline). I've tried toggling the setting on and off and it doesn't make a difference.
Also, when the phone boots, I can access my external SD card along with the internal but I can't read or write to it etiher. If I take the card out I can transfer files to it through my PC's SD card slot(with an adapter) and put it back in..but whatever is going on is locking out write access to everything on the phone.
I have even tried flashing through fastboot using dos commands, and the flashes appear successful but the phone reboots to it's old config every time. I have "bricked" stuff before, but this is the first time I am at a total dead end for a fix....and this time I didn't really do anything! lol
I also tried various USB cables/ports/PC's, same result.
bayankee said:
I upgraded my phone to the 2/10/2014 Nightly and it was running ok for a day or so. Then when I went to check my email I started getting massive app and system crashing. I was constantly getting com.google.process.gapps along with apps themselves FC.
I have been running the same version of Gapps on the phone since the beginning, and have installed a bunch of CM 11 nightlies before this. I have CWM 6.0.4.4 for a recovery. I always wipe cache and Dalvik when I do a nightly. The Gapps version I was using was gapps-kk-20140105
Here is where the weird starts. All the partitions are read only, or so it appears. If I wipe user data in CWM the phone reboots to my old profile. If I try to flash a newer nightly, it installs ok but the phone boots to the 2/10 version. If I try to install a different recovery it installs ok but will reboot to CWM.
I can successfully push an image through Matt's utility (1.20 and 1.30), I can push a image through RSD, I can push an image through HouseofMoto. The images actually successfully transfer but the phone reboots to the 2/10 rom. Their appears to be no way for me to regain write access. I can't re-root the phone through Matt's utility because when the phone boots it establishes a USB media connection but never gets into ADB mode(shows device offline). I've tried toggling the setting on and off and it doesn't make a difference.
Also, when the phone boots, I can access my external SD card along with the internal but I can't read or write to it etiher. If I take the card out I can transfer files to it through my PC's SD card slot(with an adapter) and put it back in..but whatever is going on is locking out write access to everything on the phone.
I have even tried flashing through fastboot using dos commands, and the flashes appear successful but the phone reboots to it's old config every time. I have "bricked" stuff before, but this is the first time I am at a total dead end for a fix....and this time I didn't really do anything! lol
I also tried various USB cables/ports/PC's, same result.
Click to expand...
Click to collapse
This has happened to others in various degrees. 907 & 926. Here might be your only hope. http://forum.xda-developers.com/showthread.php?t=2551113
Your's seems to be a bad case. I think all had to do with cm11 though.
Read what jcase replied to me here http://forum.xda-developers.com/showpost.php?p=47745733&postcount=2
---------- Post added at 07:39 AM ---------- Previous post was at 07:37 AM ----------
He also said the wpnomo should work on other droids
---------- Post added at 07:42 AM ---------- Previous post was at 07:39 AM ----------
Your recovery has been cwm only? Never twrp? I have never seen the issue associated with cwmr.
Read this op it may help too.
http://forum.xda-developers.com/showpost.php?p=45598679&postcount=1
Thanks for the reply, I will give the utility a shot when I get home. ADB is flaky because processes keep crashing, hopefully I can maintain it long enough to run this utility. I was able to get it past the initial ADB connection but it's failing on check updates since I am behind a corporate firewall and use a proxy.
bayankee said:
Thanks for the reply, I will give the utility a shot when I get home. ADB is flaky because processes keep crashing, hopefully I can maintain it long enough to run this utility. I was able to get it past the initial ADB connection but it's failing on check updates since I am behind a corporate firewall and use a proxy.
Click to expand...
Click to collapse
Which client needs to check for ud?
I went and installed a snapshot of CM11 to my nook color like an idiot, forgetting that it was a freaking snapshot and those are unstable. It worked fine, but when I powered it off.... It won't power on, I don't think it's off, but the screen won't even flash. Tried plugging it in, fully charged at the moment..... Read somewhere else on here that it can mean corrupted boot files - my microSD almost definitely doesn't have corrupted boot files because they worked just fine before and I did nothing that could corrupt them, yet it won't boot with or without the microSD in. Anyone know how to fix this?
Right now I'm trying something that has worked with a Motorola Xoom that I once overloaded the processor of - fully charging it, giving it a few days unplugged, and trying again to power it on.
Anything quicker than this that might help, if possible without requiring me to format my microSD?
Also, FYIs: Nook is long since rooted, had Cyanogenmod 10.1.2 running just fine but wanted an upgrade to 11. Stupid me didn't wait for the nightly to finish downloading and figured I'd try the snapshot, which may have killed it.
Same Problem So Far Nothing Working...
:crying:
just_magikkal said:
I went and installed a snapshot of CM11 to my nook color like an idiot, forgetting that it was a freaking snapshot and those are unstable. It worked fine, but when I powered it off.... It won't power on, I don't think it's off, but the screen won't even flash. Tried plugging it in, fully charged at the moment..... Read somewhere else on here that it can mean corrupted boot files - my microSD almost definitely doesn't have corrupted boot files because they worked just fine before and I did nothing that could corrupt them, yet it won't boot with or without the microSD in. Anyone know how to fix this?
Right now I'm trying something that has worked with a Motorola Xoom that I once overloaded the processor of - fully charging it, giving it a few days unplugged, and trying again to power it on.
Anything quicker than this that might help, if possible without requiring me to format my microSD?
Also, FYIs: Nook is long since rooted, had Cyanogenmod 10.1.2 running just fine but wanted an upgrade to 11. Stupid me didn't wait for the nightly to finish downloading and figured I'd try the snapshot, which may have killed it.
Click to expand...
Click to collapse
---------- Post added at 08:39 PM ---------- Previous post was at 08:24 PM ----------
I G
Dj-kream said:
:crying:
Click to expand...
Click to collapse
I actually waited a few days and then it worked again... Forgot to post here and say so xD my problem fixed itself c: