A couple weeks ago I bought a Nook Color on ebay. The first thing I did was turn it on and let it fully charge overnight. I noticed that it was in normal condition, but didn't bother going past the intro screen since an off the shelf Nook Color was not what I was interested in anyway.
The next day I flashed phiremod 6.2 on it with no problems (I have done this process successfully to two other Nook Color's by the way). I am able to connect to my wifi, setup my google account, and open the market. Life is good so far. Then I notice in ROM Manager that there is a phiremod 6.3 version out. I try to download phiremod 6.3 from ROM Manager for an entire day with no luck. The download just kept stalling on me. No problem I'll just download phiremod 6.3 onto my sdcard and flash it through clockwork recovery as normal (performing a full wipe first of course).
Then boot loop for no reason I can tell. Just a boot loop at "Touch the future of reading" with no way to get into recovery without restarting it with the sdcard.
So I put the sdcard back in and wipe and reflash phiremod 6.3 with the same results. Then I wipe and reflash phiremod 6.2...boot loop again. I repeat this process until my eyes start to bleed.
At this point I'm thinking, "There's no reason this should be happening. I wish I could just go back in time and start over." That's when I find this link: http://forum.xda-developers.com/showthread.php?t=914690
Ok, I'll just restore everything back to stock. No clockwork, no phiremod, just Barnes and Noble software just like the day it was born. So I go down the road of restoring the device to stock and instead of bootlooping at "Touch the future of Reading" it bootloops at the "N" screen. I'm running out of ideas so I perform the 8x method, get the OTA install, and still bootlooping at the "N" screen. Oh yeah, and "power + n" wont take it into recovery of any kind.
Now that it seems that I've failed to restore the device to stock, I try to flash phiremod 6.3 again because this is really my end goal anyway. This time it is a success. I connect to my wifi. The device says I am connected and the wifi signal is strong, but I can't establish a reliable data connection with google, or open the market, or browse the web. I turn the wifi off and on, I tell it to forget my connection and add it again, but nothing seems to work until a day later when it suddenly establishes a connection.
So everything seemed like it might be ok at this point except strange things started happening with the device. Power + n doesn't take it into recovery, and never did at any time it has been in my possession. When I try to go into recovery from ROM Manager after flashing CWR I go into a bootloop. This is even after updating Rom Manager and doing things like rebooting after flashing CWR. Wifi always says it's strong and connected but any app with internet access is often times painfully slow to the point of being unusable or at least impractical. Downloading a single app from the market is like pulling teeth, and I regularly get the "retry or cancel" popup over and over again. Sometimes when I tell it to reboot or shut off, I get the "rebooting" or "shutting off" message and it just grinds away endlessly.
The device is currently in a bootloop after just telling it to reboot (normal reboot not reboot into recovery), and I know how to pop in my sdcard with CWR and get out of it. However, my problem is that this is a gift for my sister, and I just cant seem to get this device into a normal working state that I can give to her.
I know that there are plenty of threads answering all of the little problems I have outlined here, but none have resolved them for me nor have I found a single thread that deals with a whole host of problems like this device seems to have.
Thank you for your patience in reading this.
Try restoring to stock 1.2:
http://forum.xda-developers.com/showthread.php?t=1050520
It can't hurt at this point, and it may get you fixed.
Thanks for the reply.
No dice. I tried both of those files. I made sure to format the system and data before flashing each time, and I'm still stuck at the "n" screen.
Alright so here's what I just did:
1) Format system
2) Format data
3) Flash B&N v1.1 "old" 1GB "/data", 5+GB "/media" partitioning zip from:
http://forum.xda-developers.com/showthread.php?t=1094371
4) Reboot
5) Flash Stock 1.2 update.zip from:
http://forum.xda-developers.com/showthread.php?t=1050520
6) Unmount sdcard
7) Reboot
8)Still stuck at the "n" screen.
The story so far:
I was forgetting to do the 8 reboots after repartitioning and flashing stock apparently.
I performed the 8 reboots, and my Nook did a factory reset and OTA update. Now it boots into stock v1.1.0. I see the pretty lady, there's a video, I get to accept a B&N agreement, I connect to either of my wireless connections, but after I enter my account name and password it always says "Error sorry we're having trouble setting up your Nookcolor. Please shutdown the device and try again...." It gives me a number to call so I do. After a long bewildering conversation with tech support, I'm told that my device was once registered to someone else (which I already suspected having purchased it on ebay). I'm told that in order to fix the problem they are going remove the old account from the device, and that when I restart it in an hour I will be one with the Nookcolor universe. It has been many hours, and I am still getting same error message.
Should I continue down this path with customer service (who are failing to inspire me), take it into the Barnes and Noble store this weekend (I don't have a receipt but it at least it boots into stock now), or just go ahead and load phiremod 6.3 (which is my end goal, but I want to make sure I don't take one step forward and then two steps back now that I've gotten this far)?
"Device Info" only has "back," "power off," and "reset."
I just tried holding the "power + n" for 10 seconds as demonstrated here Nook blocked after downloading latest software - Barnes & Noble Book Clubs. This guys seems very happy that this solution worked for him. I don't know why it wont work for me seeing as I have the exact same problem.
Barnes and Noble tech support came through and reset my device. It appears that I have a stock 1.1 Nook Color and all is well. I am even connected and able to browse the internet. Does this mean I am ready to start flashing new ROMs onto it, or should I do more testing while it is still stock?
So I made a nandroid backup of the stock system with no problem. Then I flashed phiremod v7 test. Everything was going well until I went to ROM manager, flashed CWR, and tried to make a backup. It went into a bootloop so I put in my sdcard with CWR. Immediately it started putting my backup on that card. I rebooted it through CWR, but it still went into a bootloop. I then did a factory reset, full wipe, and flashed phiremod 6.3... still bootlooping away. This is one of the problems I was having before I started this thread. The CWR on my sdcard is ClockworkMod Recovery v3.0.0.6.
Sorry to read that you're having so much trouble. FWIW I'm having one hell of a time using Phiremod on my NC, too. I've found solace with CM7 nightlies and the latest Dalingrin kernel.
CWR 3.0.0.6 is very outdated at this point. I use CWR 3.2.0.8 on my recovery SD. I think it was V3.0.0.6 that had problems formatting the data partition, but I could be wrong.
Hope you get it sorted out.
Thanks for the support. Do you know where I could find the latest versions of Clockwork?
There's a typo in my post above. The current version is 3.2.0.1
I read about it and got the files from androidforums.com, although I'd be surprised if they weren't on this forum, too.
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR, and now it is endlessly scrolling through the CWR menu on its own. The log at the bottom says "ClockworkMod Recovery v3.2.0.0," then "Back menu button enabled," then "Back menu button disabled," then "Back menu button enabled," and seems to be continuing like that without end. After powering off, removing the sdcard, and holding the power + n buttons for about 8 seconds, the screen shows the cyanogenmod logo and says "booting into recovery" but does nothing. I've repeated this entire process several times while holding the power + n buttons for varying times and it still doesn't actually boot into recovery.
Wulfie6 said:
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR
Click to expand...
Click to collapse
This is the problem. The nook color is the encore not the bravo. You have the wrong recovery image. Its a good thing its unusable...you might fubar your device if you were actually able to use that recovery.
Sent from my Phiremod Nook Color using XDA Premium App
I created a new boot disk with CWR 3.02.8 and successfully flashed Phiremod 6.3 and CM7 nightly 107. I was still essentially unable to use the internet on both of these ROMs even though my wifi connection said it was good. I did not try using my phone as a hotspot with these versions.
I'm on CM7 108 at the moment. I'm still getting sporadic internet access even though my wi-fi is pretty good (usually just shy of full bars). I connected to my phones wi-fi hotspot which produces full bars on the Nook with good internet results. This isn't practical though because I can't always have my phone creating a wi-fi hotspot. Doesn't this seem odd that my Nook is only internet reliable when it's connected to an excellent wifi connection, but functionally wont work when it's on a good wifi connection?
Also when I go into ROM Manager and try to flash the current version of CWR, it pulls up the "confirm phone model" (when it is actually connecting to the internet) but as soon I put my finger on the menu to scroll through, it selects the first one I touch. This is one of the problems I was having before on all ROMs.
So I just went into ROM Manager, flashed the latest version, then tried to make a backup through ROM Manager, and now I'm in a boot loop again except this is the kind of bootloop where I can't get it to turn off. It just sits there with the cyanogenmod logo saying "Loading..." When I hold the power down, it turns off and then comes right back on. When I hold power + n, it does the same thing but instead of saying "Loading..." it says "Booting into recovery..." I don't understand why this time it's different. If I take out the card that's in there now and put in my bootable SD card while it's in the boot loop, will it fry my cards?
Wulfie6 said:
S When I hold the power down, it turns off and then comes right back on.
Click to expand...
Click to collapse
sounds like it's plugged in
TheAmazingDave said:
sounds like it's plugged in
Click to expand...
Click to collapse
It's not plugged in.
Return to stock 1.2 - Stuck at n screen fix.
After you flash the 1.2 image with a clockwork recovery sd boot card, and are stuck at the n screen, you will need to restart and have the Nook software reset to default.
1. Hold Power+n for 8 seconds, release n, then power (it may take a couple of tries to get it right).
2. At the "Factory Reset" screen, confirm your intention to reset to defaults (press "home" n).
3. At the "Are you sure?" screen, confirm again (press "home" n).
It will then go to a "Clearing data..." screen and reboot to the stock nook software.
This procedure will reset your device to stock 1.2, just as it was when it shipped.
I second what JoeInternet says. You NEED to be on stock B&N 1.2 to be able to run the latest CM7 builds and ANY .32 Dalingrin kernels or it will not work.
Quick thought... The first thing that should have been done is an ATO 'deregister' to get that nook's ID dis-associated with the original BN account.
Greetings members of XDA! I'm new to posting here, although I drop in here sometimes to look at ROMs.
Recently, after having the contacts under my screen cleaned (due to a ghost input problem which doesn't seem to be related to this, the cleaning didn't really fix the ghost inputs anyway), I factory reset my Galaxy S5 through the regular backup/reset settings. However, part of the way through the reset, my phone shut off. I don't know whether the battery lost contact for a split second, or if it just crashed, but it started booting again straight away - except this time it booted into the recovery of its own accord, without me holding down any other buttons. The recovery (TWRP) just bootloops, and the "TeamWin" screen just flashes constantly. Removing the battery is now the only way to turn the phone off, and whenever I turn it on or charge it, it boots into the recovery and the recovery just bootloops. Although the regular ROM is not accessible (it just goes to the recovery), Download Mode can be accessed normally.
I had a look at my catlog (thankfully I had USB debugging enabled before this fiasco), but it only offered me this after starting the daemon:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
I also used ADB to pull /tmp/recovery.log, here's the pastebin code: U89RQTkZ (I can't post the link itself, but this is the code for it after pastebin's URL)
The pastebin above is just one repeat of the attempt to boot inside the bootloop - the log itself is comprised of many subsequent attempts to boot, with identical results in the log. (I know the log says the date is 2014, that's probably because I had aeroplane mode on before I did the reset.)
So, can anyone help me fix this? I am inclined to try reflashing my recovery (TWRP again since my most recent nandroid backup is in that format), but I want to know if anyone here has a better idea before I start doing potentially irreversible damage to my phone.
Thanks in advance!
CakeWithoutEggs said:
Greetings members of XDA! I'm new to posting here, although I drop in here sometimes to look at ROMs.
Recently, after having the contacts under my screen cleaned (due to a ghost input problem which doesn't seem to be related to this, the cleaning didn't really fix the ghost inputs anyway), I factory reset my Galaxy S5 through the regular backup/reset settings. However, part of the way through the reset, my phone shut off. I don't know whether the battery lost contact for a split second, or if it just crashed, but it started booting again straight away - except this time it booted into the recovery of its own accord, without me holding down any other buttons. The recovery (TWRP) just bootloops, and the "TeamWin" screen just flashes constantly. Removing the battery is now the only way to turn the phone off, and whenever I turn it on or charge it, it boots into the recovery and the recovery just bootloops. Although the regular ROM is not accessible (it just goes to the recovery), Download Mode can be accessed normally.
I had a look at my catlog (thankfully I had USB debugging enabled before this fiasco), but it only offered me this after starting the daemon:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
I also used ADB to pull /tmp/recovery.log, here's the pastebin code: U89RQTkZ (I can't post the link itself, but this is the code for it after pastebin's URL)
The pastebin above is just one repeat of the attempt to boot inside the bootloop - the log itself is comprised of many subsequent attempts to boot, with identical results in the log. (I know the log says the date is 2014, that's probably because I had aeroplane mode on before I did the reset.)
So, can anyone help me fix this? I am inclined to try reflashing my recovery (TWRP again since my most recent nandroid backup is in that format), but I want to know if anyone here has a better idea before I start doing potentially irreversible damage to my phone.
Thanks in advance!
Click to expand...
Click to collapse
Flashing your recovery won't damage your phone in anyways. The best method I can recommend is to flash your phone's stock rom using odin. Usually flashing stock is helpful after soft breaks and bootloops. Flash stock and then you can install twrp and restore your backups. And about those ghost inputs. Sometimes with phone being charged with a non-standard cable those ghost inputs will happen. And if your phone gets wet this issue will show up. Try using another charger and cable and see if they happen again or not.
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.
Hi Everyone -
Last night when I went to sleep I left my PH-1 plugged in and charging, and when I woke up this morning the phone had frozen with a black screen and status light still blinking. I restarted the phone and end up at a screen with "Cannot Load Android System. Your data may be corrupt". The boot cycle goes "Powered by Android" --> circles to square dot rotation --> restarts to "Powered by Android" --> to screen mentioned before with corruption. I have options to "Try Again" or "Factory Reset" and have selected "Try Again" about 20 times now with no luck.
Some pertinent facts:
Running latest official OS from Essential
Bootloader unlocked
Phone is encrypted
When I flashed the latest official OS about a year ago I used TWRP, but forgot to re-install TWRP after the flash
I am able to get to the Bootloader --> "Recovery" --> "No Action Screen" and then get to the actual recovery from there; I am now kicking myself for not reinstalling TWRP. My options on the recovery screen are "apply update from ADB option", "mount /system", or "Factory Data Reset" (as well as review logs and some other tests).
Most of the data on the phone is backed up, however there are still some items not backed up that I'd like to attempt to retrieve.
My Question - What are my options to try and salvage the data off the phone provided it is encrypted? I've seen some references to using ADB update to re-flash the original OS (I assume this is a dirty flash) but not wipe the data and my data would still be there after the install. I've seen references for that approach but not confident enough to know if it would apply for my case. In example, would this work even with the encryption? Alternatively, I expect I could reinstall TWRP via ADB update and try to work something out from there.
Thank you in advance for reading this! I appreciate any and all insight or recommendations of an approach to take. As you can see, I'm clearly a novice who has followed some tutorials, but definitely not advanced enough to have strong knowledge of all of Android's innards. Thanks again.
Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.
neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery ModeRebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD CardYou may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe ModeThis problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery ModeWhen you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.
At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.
The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)