Related
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Do a factory reset, install the update, then use the new autonooter.
how to do a factory reset? thanks, I am a newbie to this area!
Not sure how much I can help-
Just how "bricked" is it?
A truly bricked device will do nothing. It will not start or do anything whatsoever.
A machine that is thoroughly HOSED may get stuck in a boot loop, or try to start and fail every time you press the power button.
When I forced the update manually it took a few minutes to take and reboot; how long ago did it do the update?
Have you tried connecting with adb yet?
Have you tried booting it with a nooter or auto-nooter sd card yet?
http://nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC
Instructions for manually updating.
Here is my situation:
Around 9:30, my NC started updated itself, it reboot in about 15 minutes, and takes a very long time get to the "nook color" screen, then took another 10 minutes letting me select "home or zeam", after that, it has no response.
I tried to reboot, it got up to the "Nook Color" welcome screen, no further response!
I tried to factory reset, not working through adb, it did appear on the adb devices command!
Do a factory reset and start over.
I ran into a similar problem, but here is what happened to me:
1. I reset the device to factory settings.
2. I rebooted the nook 8 times, stopping the boot process. This took my NC back to factory version and no rooting at all.
3. Installed NC update 1.01 per B&N instructions.
4. Used AutoNooter (latest version for 1.01). AutoNooter rebooted the device as it is supposed to.
5. After AutoNooter reboot, I installed Astro File Manager and then after that the NC stopped responding to screen touch.
6. I held the power button to shut the device down. Strangely, the screen shut off and it appeared to be shut down, but I think it did not truly shut down.
7. I could not turn the NC back on. I tried to reset to factory settings 2-3 times and no response.
8. I plugged in my NC as if to charge, and it went through the boot process.
and it has worked just fine since then. To be honest it kind of scared me, because I love this thing to death, but I remained calm and kept at it and it was not bricked. I guess what I'm trying to say is that before you post here that the new update bricks the NC, you should be absolutely sure it is bricked and not just frozen like mine was.
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Brick, like you can't do anything at all anymore, might as well lay it on papers, use it as a door stop and pour cement to build a house?
That's what bricked means... If you still can access it via ADB, run recovery, etc.. it is far from "BRICKED"...
-CC
Hello,
My Nook is completely rooted. I wanted to start from a clean slate. During the wiping and upgrading to 1.0.1 I was prompted to go through the setup which it did. The root happened successfully, however when I look at the device info ==> About your Nook it is currently showing the "Owner" as unavailable. I tried the erase and degregister my nook but it comes up with an error Deregister device failed with error: User Not registered (e_not_registered) Reset device was not attempted. Also, I'm unable to ADB into my nook after I flashed the update for some reason. Any idea would be appreciated, thanks.
The three finger data reset will take you back to the Register screen. Just be very sure you are using the correct login info.
Sent from my Droid using Tapatalk
Which three keys are used, or are you referring to rebooting it 8 times? thanks!
takef0cusin said:
Which three keys are used, or are you referring to rebooting it 8 times? thanks!
Click to expand...
Click to collapse
I was having similar issue as well getting the E_NOT_REGISTERED error. That was the result of trying to upgrade the NookColor firmware to 1.0.1 without deregister the unit first.
The problem was eventually solved after poking around the "NookColor Tools" after rooting. Select that NookColor Tools, then select "Development", then "Deregister & Erase Device". Try one of the option to see which one works for you. The Deregister Only option doesn't work for me, but Master Clear Only worked and after reboot it let me register again and this time I got access back to the Nook Shop.
However it seems there is something wrong with the root as I can't connect to Gmail anymore. Perhaps I need to properly deregister it again before I do any upgrade....
Hope this help.
I too have been having trouble registering my NC to my bn account since i unboxed it. I tried using the method above and ran master reset now my NC won't boot any more...
It seems completely unresponsive :/ Ideas?
EDIT: Removed SD card and it booted up. Cant get past the LogicPD Screen, going to try select "quick setup" this time...
Boots ok, though still getting deregister device failed message :-(
So I selected the other option at boot and got the normal setup screen YAY! when through and selected my wifi etc and hit continue with setup only to be greeted by the familiar error "sorry we're having trouble setting up your nookcolor. Please shutdown the device and try again. it says "BAD1221" at the bottom in grey letters....error code?
So frustrating
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
jbright44 said:
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
Click to expand...
Click to collapse
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
wvcachi said:
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
Click to expand...
Click to collapse
Yes I did. It's doing all of this with the SD card out.
jbright44 said:
Yes I did. It's doing all of this with the SD card out.
Click to expand...
Click to collapse
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
wvcachi said:
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
Click to expand...
Click to collapse
Edit. That fixed it. Thanks. Man do I feel stupid. I thought the 8x reset and the 3 button method were the same. Apparently not. I'll try this again a little smarter hopefully this time.
Thank you for this thread. I thought I just bricked my 2 hour old nook. I stupidly restarted it after root with the nooter card still plugged in. Then I couldn't figure out why it was taking so long for the screen to turn on, so I kept pressing the button and then holding it. Then I realized the card was still in. Took the card out and tried to boot it, but it hung at the 'n' screen. The 8 interrupted boot method saved me from my stupidity though. Thanks.
Same here - left the card in...
8x reset and then a home and power reset cleared me up. Then update back to 1.1 and autonooter 3 again.
Loving it ever since.
hey
im having the same problem i did the factory reset to and nothing
wats the 3 count and wat else can i do
So what to do when factory restores and stock installs fail?!
OK... reviving this thread since it's my exact problem but I've been unable to find resolution. I've been searching everywhere for what to do next but nothing seems to be working.
I'm helping my buddy get his nook working. He said he was updating to 1.4 and when he rebooted it, it froze on the n screen. He plugged it back into his Win 7 machine to try the update again and it wouldn't mount as a USB device.
After a bunch of reading and fiddling, he built an SD card with ClockworkMod and installed in on an SD card. Or so he thought... he hadn't made it bootable. Over the phone, I walked him through restoring the image to his card and then it booted.
CWM comes back with a pile of errors. Specifically,
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When trying to format /data and /system, we also get errors.
We've downloaded various factory restore zips and tried installing them but they install (successfully according to CWM) and we reboot only to get stuck at the dreaded n screen again. We've done the 8 boot interrupt restore and get and error to call support (nobody answers this week) and done the regular power/+/n restore and it completes but leaves us again on the n screen.
Can anyone tell me the significance of these errors in CWM? It's the only thing different from all the tutorials and video walkthroughs we've followed and although we've seen these errors in other posts, there's never been a good explanation of them and how to resolve them if necessary.
Also, what is the latest version of CWM for the Nook Color and where do I find it? Is there an official site for CWM? Seems like people are just linking to older versions and sources all over the place with no common "go to the CWM site and get latest build of CWM." The latest I've found is 3.2.0.1 in a post back in August 2011.
Thanks in advance! Hoping this gets us over this hump and helps anyone else in the in the same situation.
moose
Solved it...
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
I'm also getting the E: Can't mount / errors.
Will try this when I get home.
Also i'm just realizing now that i am using an older CWR v3.0.0.5, so that might be my issue also.
links
Mooseroo Could you please post links used to fix this issue
Try using this version of CWR. Just remember you can always choose a recovery image smaller than or the same as your SD card but not larger.
http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
this is not working. same issue with nook 1.4.1 and CM7...hangs at "N" or goes black with CM7
Have you check the MD5 of all your files to make sure you have good downloads? It is frequently a skipped step but one of the easiest and first things you need to check.
Mooseroo - where are you?
mooseroo said:
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
Click to expand...
Click to collapse
Just found this thread and I have the same issue - can you post the links you reference? Please?
tmccully said:
Just found this thread and I have the same issue - can you post the links you reference? Please?
Click to expand...
Click to collapse
I think he's talking about my files in this post.
I need some serious help, I guess. I couldn't even tell you what happened.
**NOTE: I have to post the youtube titles the to tutorials I used since I'm new. I can't post the links.***
Anyway, I am new to nook. I tried to get cute and root it (and thought I was doing so with the MicroSD method) but it wasn't the way I wanted to do so.
I followed this guys tutorial [SEARCH YOUTUBE FOR How to Install CyanogenMod 7 on the Nook Color (PC Version)] to install CyanogenMod 7 on the Nook Color.
Here I am everything's going along fine, and then he gets to the part where he says "take out the SD card and reboot..." and I'm going "WHAAAT?!" I didn't want to root my nook, but create a start up image on my MicroSD card so it wouldn't come to this situation...
Anyway, I did what he said because I'd gone too far as it was. When I tried to reboot, the CyanogenMod 7 screen just stuck loading and loading. I rebooted NUMEROUS times, and nothing... so I repeated all his steps again, and nothing.
I tried to format the cache, data and system. That worked fine... but I think at one point I accidentally chose "wipe data/factory reset" and "wipe cache partition."
I tried using his reversal method here [SEARCH YOUTUBE FOR How to Unroot / Restore / Unbrick the Nook Color (PC Version)] to get my NC back to normal, but upon following these steps, found myself with an error when trying to format the data.
The error reads, "Formatting /data... Error formatting /data!"
Does ANYONE have any idea what I did, and how I can reverse it?
I can pay a couple of bucks to whoever helps me out to show you that I am dead serious about this.
I am a newb, so I'd need some detailed instructions.
I have two MicroSD cards that I can use, one 2GB and one 16GB.
Please help!!!
Email me at [email protected]... please due let me know if you have Skype or Yahoo. I prefer a live chat.
PLEASE... God bless you.
I apologize. I think I posted this in the wrong section.
Firstly, don't panic, no need to. If the first time doesn't work out, try a couple more times.
Secondly, we're here to help so relax and try to tackle your issue slowly.
Now, be sure to tell us what you intend to do NOW (at this stage of your NC)?
a. returning to the original stock ROM or
b. installing and running CM7 from internal memory (aka. eMMC) or
c. booting CM7 off uSD card
If the answer is either a or b, then first step, try getting the ClockworkMod Recovery (CwM R) version 3.2.0.1.
If you want to go back to stock on a NC you can ALWAYS do so(unless you screwed with your partitions which I doubt you did) by doing this simple thing:
-Power it off.
-Now turn on.
-While it's booting up hold down both POWER and N buttons.This will power your nook off no matter what every time, it's built right into the device. Great for getting out of bootloops.
-Do this EIGHT TIMES.
Your Nook was designed to be nearly "UnBrickable". After 8 failed boots it will always restore it's factory settings. So unless you've tried this and it did not work, then no, your Nook is not ruined. Obviously you don't wanna have an SD card in there while doing this, or you will probably get AIDS.
Landara said:
If you want to go back to stock on a NC you can ALWAYS do so(unless you screwed with your partitions which I doubt you did) by doing this simple thing:
-Power it off.
-Now turn on.
-While it's booting up hold down both POWER and N buttons.This will power your nook off no matter what every time, it's built right into the device. Great for getting out of bootloops.
-Do this EIGHT TIMES.
Your Nook was designed to be nearly "UnBrickable". After 8 failed boots it will always restore it's factory settings. So unless you've tried this and it did not work, then no, your Nook is not ruined. Obviously you don't wanna have an SD card in there while doing this, or you will probably get AIDS.
Click to expand...
Click to collapse
you can also do it by holding down "Power" "N button" and "Up volume" at same time and it will do a factory reset
leapinlar: Ask the question on the forum. I don't like using PMs.
Recently the update allowing google play store somehow bypassed the anti-update thing on my nook, so now I can use play store on the nook home, but the update removed my root but kept the android system home.. It uses a lot of ram, which i'd rather have free to play games or other resource heavy apps on.
I know I have to get my nook to start unsuccessfully 8 times, but I don't know how I go about doing that, can I get some help?
flipperz said:
leapinlar: Ask the question on the forum. I don't like using PMs.
Recently the update allowing google play store somehow bypassed the anti-update thing on my nook, so now I can use play store on the nook home, but the update removed my root but kept the android system home.. It uses a lot of ram, which i'd rather have free to play games or other resource heavy apps on.
I know I have to get my nook to start unsuccessfully 8 times, but I don't know how I go about doing that, can I get some help?
Click to expand...
Click to collapse
If you want to do it the easy way, just interrupt the boot by turning it completely off (hold power button for a few seconds) while booting eight times in a row. It will take you back to some version of stock, usually 2.0.0 or 2.0.4 then upgrade again to 2.1.0 when you register again.
Sent from my Nook HD+ running CM10.1 on emmc.
Another way
leapinlar said:
... just interrupt the boot by turning it completely off (hold power button for a few seconds) while booting eight times in a row. It will take you back to some version of stock, ...
Click to expand...
Click to collapse
After my HD+ locked up when I created a "Guest" ("child") profile and I had to do the 8-reboot process, after upgrading to B&N v2.1.0, I experimented with alternate button combinations at power-on. If I held the "n" button when pressing "power", I got a prompt that allowed me to do a factory reset.
Whether that is part of a later B&N recovery module, I can't say.
DeanGibson said:
After my HD+ locked up when I created a "Guest" ("child") profile and I had to do the 8-reboot process, after upgrading to B&N v2.1.0, I experimented with alternate button combinations at power-on. If I held the "n" button when pressing "power", I got a prompt that allowed me to do a factory reset.
Whether that is part of a later B&N recovery module, I can't say.
Click to expand...
Click to collapse
That factory reset just wipes data, it does not reinstall the ROM. He probably needs to reinstall the ROM since some of the broken symlinks may still be in /system.
Power + n takes you to stock recovery, which, without other parameters being passed to it, asks if you want to factory reset.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
That factory reset just wipes data, it does not reinstall the ROM. He probably needs to reinstall the ROM since some of the broken symlinks may still be in /system.
Power + n takes you to stock recovery, which, without other parameters being passed to it, asks if you want to factory reset.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the help!
I'd like to return my Nook HD+ to stock, too. It has a Cyanogen mod that precedes that startup, and I think that's getting in the way of the 'eight reset' mechanism for a total factory reset to stock software.
Is there a bootloader, system, and gapps zip that I could just flash from an external SD card that would do the job? Seems like there was, at one time, but it's getting very difficult to find them. Any ideas for a quick factory reset (not a wipe, but a complete reset to original OS?).
[email protected] said:
I'd like to return my Nook HD+ to stock, too. It has a Cyanogen mod that precedes that startup, and I think that's getting in the way of the 'eight reset' mechanism for a total factory reset to stock software.
Is there a bootloader, system, and gapps zip that I could just flash from an external SD card that would do the job? Seems like there was, at one time, but it's getting very difficult to find them. Any ideas for a quick factory reset (not a wipe, but a complete reset to original OS?).
Click to expand...
Click to collapse
Go to my HD/HD+ CWM thread linked in my signature and flash the plain stock zip from item 6 there and follow that with a factory reset by CWM.
And it was not the cyanoboot that prevents the 8 reset, it is because when you originally installed CM you also replaced the stock recovery on internal memory with CWM. Stock recovery is needed for the 8 reset to work.
Sent from my BN NookHD+ using XDA Premium HD app
Thanks, that worked. I also tried the rooted version of stock, but it has a problem: "Unfortunately, Home has Stopped". Is there a workaround to this?
[email protected] said:
Thanks, that worked. I also tried the rooted version of stock, but it has a problem: "Unfortunately, Home has Stopped". Is there a workaround to this?
Click to expand...
Click to collapse
Don't use that version, I should remove it. If you want to root, do it per the thread with universal root rev 3.
Sent from my SCH-i705 using XDA Premium HD app
Hi there,
I have a device that is also candidate for unrooting to stock. The thing is that I have tried both CWM and TWRP on bootable SD to try and fix the situation tith the apropriate zips but unfortunately none of them can mount sd ot any internal memory for me to reset.
Maybe I should also add that the device is charging without turning on except if there is a proper bootable sd inserted.
I presume a rescue bootable SD of OEM type could bring the device back to life.
I`ll apreciate any help.
ValentinD said:
Hi there,
I have a device that is also candidate for unrooting to stock. The thing is that I have tried both CWM and TWRP on bootable SD to try and fix the situation tith the apropriate zips but unfortunately none of them can mount sd ot any internal memory for me to reset.
Maybe I should also add that the device is charging without turning on except if there is a proper bootable sd inserted.
I presume a rescue bootable SD of OEM type could bring the device back to life.
I`ll apreciate any help.
Click to expand...
Click to collapse
When you say a candidate for stock, why? Is there something else wrong with it? I am just trying to see if it is bricked.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
When you say a candidate for stock, why? Is there something else wrong with it? I am just trying to see if it is bricked.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Maybe Bricked is the situation. The device is charging (the green light is present when plugged to the charger or USB ) but the power button can no longer start any visible boot process on the screen.
The story of the device is nearly the following:
I was using the device for a long time rooted with installed CM updating even with over night builds from time to time.
Once I had a problem booting properly after update but easily booted to TWRP and restored the previouse update.
A week ago the same situation occured, after an update procedure I left the device plugged to the wall charger and on the morning it was stuck on the CYANOGEN universal boot logo. No way found to boot to recovery found.
I figured the recovery has gone bad. Started to prepare bootable SD to try and fox the mess somehow, but could not do the corect procedure of preparing a good bootable SD many times. The only time I successfuly booted CWM recovery from SD I tried to install a zip with CWM recovery and as far as I remember at that time the bootable recovery was able to mount another SD wile it was booted on the device and the zip installed with success according to the software. Sadly after a restart the device was as is, stuck on the bootloader logo.
After 2-3 times successfuly booting both CWM and TWRP recoveries from prepared SD card, doing nothing at all that can alter the device, just tried to see how to mount any usable memory, the device stopped visualy booting without an SD.
Thank you for the reply, hope you can add some wisdome to the happy end
ValentinD said:
Maybe Bricked is the situation. The device is charging (the green light is present when plugged to the charger or USB ) but the power button can no longer start any visible boot process on the screen.
The story of the device is nearly the following:
I was using the device for a long time rooted with installed CM updating even with over night builds from time to time.
Once I had a problem booting properly after update but easily booted to TWRP and restored the previouse update.
A week ago the same situation occured, after an update procedure I left the device plugged to the wall charger and on the morning it was stuck on the CYANOGEN universal boot logo. No way found to boot to recovery found.
I figured the recovery has gone bad. Started to prepare bootable SD to try and fox the mess somehow, but could not do the corect procedure of preparing a good bootable SD many times. The only time I successfuly booted CWM recovery from SD I tried to install a zip with CWM recovery and as far as I remember at that time the bootable recovery was able to mount another SD wile it was booted on the device and the zip installed with success according to the software. Sadly after a restart the device was as is, stuck on the bootloader logo.
After 2-3 times successfully booting both CWM and TWRP recoveries from prepared SD card, doing nothing at all that can alter the device, just tried to see how to mount any usable memory, the device stopped visualy booting without an SD.
Thank you for the reply, hope you can add some wisdom to the happy end
Click to expand...
Click to collapse
It sounds like it is bricked. If recovery said it installed successfully and it still will not boot normally, it is usually what that means. By bricking, I mean internal memory has become read only and nothing can successfully be written to it even if it said it was successful. Your probable only option is to use a noemmc version of SD CM. Search the dev forum for that term.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
It sounds like it is bricked. If recovery said it installed successfully and it still will not boot normally, it is usually what that means. By bricking, I mean internal memory has become read only and nothing can successfully be written to it even if it said it was successful. Your probable only option is to use a noemmc version of SD CM. Search the dev forum for that term.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Apart from the the. Is that a BN at a point of too much geting on or it has to deal with the overal life of surge protection meh a chip?
ValentinD said:
Apart from the the. Is that a BN at a point of too much geting on or it has to deal with the overal life of surge protection meh a chip?
Click to expand...
Click to collapse
No, it is probably from running CM11. That has a history of bricking devices with the faulty emmc chip due to applying trim automatically.
Sent from my BN NookHD+ using XDA Premium HD app