Related
So now my DVP has learned a new trick. I was driving home and noticed the power was off. Could've sworn it had plenty of battery, so I went to power it on.
Now it just sits there and power cycles...all the time. Tried yanking the battery, replacing it, and charging it plugged into the wall...still sits and power cycles.
Between this and the whole SD debacle, I'm getting pretty pissed off at this phone.
Have you replaced the SD Card? Could the power button be sticking?
Yes - the SD card was replaced. Several times actually, and all replacements worked fine (reset + card swap, then power on) for a week...then this suddenly started occurring.
Someone at the MS store blamed it on that, which I guess is okay, but seriously - if that is the case, then Dell needs to put a legitimate "this will void your warranty" sticker on there rather than some black bar that *supposedly* shows "void" once you peel it off, even though nobody in the store could actually read what the hell it said.
I have had something like that happen with my phone as well. I have not replaced the MicroSD card but maybe 4 or 5 times this last week the phone has seemingly been off or off in space when I try and turn it on from "sleep". All the times this has happened I had to pull the battery. Once it did the same thing again right away but most of the time it goes back to normal.
I thought it was one of the apps that might be causing some issues so I have removed it and will see if this stops.
gshocker said:
I have had something like that happen with my phone as well. I have not replaced the MicroSD card but maybe 4 or 5 times this last week the phone has seemingly been off or off in space when I try and turn it on from "sleep". All the times this has happened I had to pull the battery. Once it did the same thing again right away but most of the time it goes back to normal.
I thought it was one of the apps that might be causing some issues so I have removed it and will see if this stops.
Click to expand...
Click to collapse
What SD cards are you guys using? I have had a Sandisk 32gb Class 2 in since Friday morning and no issues so far (crosses fingers).
I used a Kingston C4 32GB - worked fine aside from the slow Zune sync, same with the Patriot C4 16GB. The one that worked properly was a Wintec 16GB C10 card - until the power cycling occurred. I replaced the stock card and it still did the same thing. I would expect if it was *really* a card issue, it would've booted but displayed an error, as it does if you just replace the card without doing a reset.
After some more testing it seems this happens when I am pretty sure it has to do with some Marketplace app bug. When I search in the marketplace it seems to happen. Phone will go to sleep and then not come back. I end up having to pull the battery to get it back. Hopefully this will get fixed in an update.
My recommendation is to use the phone for a few weeks *before* swapping out cards. In this case, no one knows if it's a hardware issue, software, or something about the MicroSD card.
Keep it stock. See if it's fine that way. If so, then swap out cards. If it starts to act up, then you likely have your culprit.
My $.02
yipcanjo said:
My recommendation is to use the phone for a few weeks *before* swapping out cards. In this case, no one knows if it's a hardware issue, software, or something about the MicroSD card.
Keep it stock. See if it's fine that way. If so, then swap out cards. If it starts to act up, then you likely have your culprit.
My $.02
Click to expand...
Click to collapse
agreed. saves time when using process of elimination.
hello!
my nook likes to tap all by itself, sometimes in different places but generally in the center of the screen. i just bought it on onesaleaday.com a few days ago and had plans to upgrade to the latest cm7 nightly. my questions are:
1. is the tapping problem one that will go away when i boot my nook from an external microsd, running cm7?
2. since im under warranty for a year, is there are reason i should consider fixing the problem and/or returning my nook prior to putting cm7 on it?
3. if i do run cm7 from an external microsd card, will my nook always be stock and unmodified when i remove the card, thereby allowing me to make warranty claims on hardware if need be?
and on a related note, i bought a microsdhc card prior to hearing about how sandisk is the best. i bought this one: Transcend 32 GB Class 4 microSDHC . i may be able to return it for a sandisk.
4. does anyone have specific experience running this card or know as to its functioning on the nook?
5. if i have problems running cm7 on this card, is it easy to use the internal card on the nook for cm7, and then use the external one for my music collection? obviously this would void my warranty.
thank you!
sorry, i know some of these could be answerable by searching in depth, but i couldnt find anything particular to the tapping problem i have.
Do you have sweaty hands?
If the screen gets at all moist, it will get false touches. If that occurs, switch the screen off then on again, it should reset it.
If/when you root it, and the issue is still there, run nook recalibrator to recalibrate the display. Worked for me
Sent from my NookColor using Tapatalk
whatismouse said:
hello!
my nook likes to tap all by itself, sometimes in different places but generally in the center of the screen. i just bought it on onesaleaday.com a few days ago and had plans to upgrade to the latest cm7 nightly. my questions are:
1. is the tapping problem one that will go away when i boot my nook from an external microsd, running cm7?
2. since im under warranty for a year, is there are reason i should consider fixing the problem and/or returning my nook prior to putting cm7 on it?
3. if i do run cm7 from an external microsd card, will my nook always be stock and unmodified when i remove the card, thereby allowing me to make warranty claims on hardware if need be?
and on a related note, i bought a microsdhc card prior to hearing about how sandisk is the best. i bought this one: Transcend 32 GB Class 4 microSDHC . i may be able to return it for a sandisk.
4. does anyone have specific experience running this card or know as to its functioning on the nook?
5. if i have problems running cm7 on this card, is it easy to use the internal card on the nook for cm7, and then use the external one for my music collection? obviously this would void my warranty.
thank you!
sorry, i know some of these could be answerable by searching in depth, but i couldnt find anything particular to the tapping problem i have.
Click to expand...
Click to collapse
I've heard that the phantom taps have been related to when the NC is plugged in. I know I experienced a few when I first got mine, but I haven't in a long time.
Does this only happen when you have the NC plugged in. Also, have you given the screen a good clean to make sure all dirt, grim, oil, etc are off of it (I know at least once that was my problem).
There is no reason not to try CM7 on it before claiming any warranty. As far as where you want to run it from, that is entirely up to you and what you feel comfortable with. Running it off eMMC is not a big deal since the NC boots off SD card first you can always revert back to stock B&N OS on it.
There are a lot of tutorials on how the roms and such for the device, just dig around.
Phantom taps seem to only happen on my NC when it is plugged into the wall charger, but doesn't seem to happen at all while hooked up to the computer. Random zoom in and out and highlighting of words from a single touch. Sometimes my finger can be 2" away from the screen and it sets off the touch sensor.
Thanks everyone. I think it must have been a dirty screen because i havent had any problems today after cleaning. The browser on froyo is still terrible, it just wont respond to my scrolls or taps sometimes but if i turn off the screen and back on it always works again. All of the tapping problems i was having was with the nook unplugged.
It seems my HD+ left me yesterday morning.
I was just copying some data from the SD-Card to emmc (running CM10). I left the device alone for about five minutes and when I came back, the screen would not turn on.
My battery was around 50 percent, so that should not be the problem.
Since then I tried various methods to bring the Nook back to life:
- I plugged it into the power device and waited (around five hours).
- I pressed the power button with all imaginable combinations of other buttons (from short to about 30 seconds)
- I even put the HD+ in the fridge, as suggested in this thread: http://forum.xda-developers.com/showthread.php?t=1599753
The result is always the same: Nothing happens when I press any key.
The only exception is the green light that comes on, when I connect it to the charger: this light goes out when I press the power switch for more than around ten seconds. When I press the switch again it comes back on.
Is there anything else I could do? Can I somehoe try to ADB into the Nook in this state?
Its a little annoying for me, as I imported the little fellow to germany (bough on Ebay UK) and I do not have a receipt or anything. So I think I won't be able to return it to BN...
Thanks in advance for any hint!
Bert Randolph said:
It seems my HD+ left me yesterday morning.
I was just copying some data from the SD-Card to emmc (running CM10). I left the device alone for about five minutes and when I came back, the screen would not turn on.
My battery was around 50 percent, so that should not be the problem.
Since then I tried various methods to bring the Nook back to life:
- I plugged it into the power device and waited (around five hours).
- I pressed the power button with all imaginable combinations of other buttons (from short to about 30 seconds)
- I even put the HD+ in the fridge, as suggested in this thread: http://forum.xda-developers.com/showthread.php?t=1599753
The result is always the same: Nothing happens when I press any key.
The only exception is the green light that comes on, when I connect it to the charger: this light goes out when I press the power switch for more than around ten seconds. When I press the switch again it comes back on.
Is there anything else I could do? Can I somehoe try to ADB into the Nook in this state?
Its a little annoying for me, as I imported the little fellow to germany (bough on Ebay UK) and I do not have a receipt or anything. So I think I won't be able to return it to BN...
Thanks in advance for any hint!
Click to expand...
Click to collapse
Take your CM10 card out. Press power for a while. Let go and momentarily Pres power again. It should boot to stock. Then you can resume booting to and using CM10.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
Take your CM10 card out. Press power for a while. Let go and momentarily Pres power again. It should boot to stock. Then you can resume booting to and using CM10.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
I already tried that, with sd-card and without.
Just gave it another go and it still does not work (also tried with and without power)...
Bert Randolph said:
I already tried that, with sd-card and without.
Just gave it another go and it still does not work (also tried with and without power)...
Click to expand...
Click to collapse
Wow, only suggestion I have is plug it in, press power button null green light goes out, push it again, then just leave it plugged in over night...Good luck, out works for me. Take the sd out to
Sent from my BNTV600 using xda app-developers app
dbh369 said:
Wow, only suggestion I have is plug it in, press power button null green light goes out, push it again, then just leave it plugged in over night...Good luck, out works for me. Take the sd out to
Sent from my BNTV600 using xda app-developers app
Click to expand...
Click to collapse
I also tried this already, but left it plugged in only for an hour or so. Will try again tonight.
Thanks!
dbh369 said:
Wow, only suggestion I have is plug it in, press power button null green light goes out, push it again, then just leave it plugged in over night...Good luck, out works for me. Take the sd out to
Sent from my BNTV600 using xda app-developers app
Click to expand...
Click to collapse
Well, this didn't work out either. The green light was still on in the morning and the unit wn't turn on.
I guess, if nobody comea up with a plan B, I will have to try my luck with the customer support.
Bert Randolph said:
Well, this didn't work out either. The green light was still on in the morning and the unit wn't turn on.
I guess, if nobody comea up with a plan B, I will have to try my luck with the customer support.
Click to expand...
Click to collapse
Good luck, post here if you get an answer from them...sounds like this might be an issue with Nooks...
dbh369 said:
Good luck, post here if you get an answer from them...sounds like this might be an issue with Nooks...
Click to expand...
Click to collapse
Will do.
But does anybody else really have a bricked unit? I don't remember reading anything about Hd+s that couldn't be revieved.
I have the exact same problem.as you. Also when I plug the HD+ into my pc it mounts for 1 second then disconnects.
Hopefully we can fix the problem.
oI say chaged it over night to make sure it's fully chage first, try to atleast make sure charge indicator is green and not amber. Then try various buttons combination like power+home while pluging in charge cable. You can try like a router 30:30:30, meaning holding 30 sec with cable on and continue holding while unplug the cable for 30psec then plug cable back in while still holding for another 30sec.
someone0 said:
oI say chaged it over night to make sure it's fully chage first, try to atleast make sure charge indicator is green and not amber. Then try various buttons combination like power+home while pluging in charge cable. You can try like a router 30:30:30, meaning holding 30 sec with cable on and continue holding while unplug the cable for 30psec then plug cable back in while still holding for another 30sec.
Click to expand...
Click to collapse
I tried all these suggestions (and looked rather silly doing so, as some combinations are quite difficult to press while plugging the power in ). Well, nothing worked.
Thanks anyway!
rain22 said:
I have the exact same problem.as you. Also when I plug the HD+ into my pc it mounts for 1 second then disconnects.
Hopefully we can fix the problem.
Click to expand...
Click to collapse
Mine is not recognized at all by the computer.
The fact that yours is seen suggests that there is still some system running on your nook. I would think that maybe it is in some kind of loop or so, as described in this thread: http://forum.xda-developers.com/showthread.php?t=1599753. You could try to completely drain the battery and than plug it in again.
Good luck!
Bert Randolph said:
I was just copying some data from the SD-Card to emmc (running CM10).
Click to expand...
Click to collapse
This might result (for some unknown reason) in your internal emmc card being corrupted (or dead). And maybe also your microsd card is now not bootable.
Did you try to prepare new bootable microsd card with CM10?
Even if your internal emmc died completely there is still a chance it could boot from microSD. Not sure about specific OMAP4470 configuration in Nook HD+ but in general OMAP chips have a boot ROM inside CPU which tries to boot in specific order from SD/MMC interfaces, NAND flash and maybe also USB and serial.
So maybe there is bigger chance to boot from microSD than internal eMMC.
Bert Randolph said:
The only exception is the green light that comes on, when I connect it to the charger: this light goes out when I press the power switch for more than around ten seconds. When I press the switch again it comes back on.
Click to expand...
Click to collapse
So it looks like there is still some difference between OFF and ON state so it is not hopeless.
First thing is that, that you have warranty if you bought it over Ebay UK (if seller was EU user). EU laws marks that you can return it directly to seller or importer (retailer). On UK Nook official retailers are shown here.
But anyway, if you dont plan go with return/warranty way, then ... honestly, its not hard open Nook HD+ and detach battery. Only thing what you later need is 3M two sided 3mm tape (you can find it on ebay. example). If i have time on work tomorrow i make disassemble guide if someone interested. We opened one for knowledge.
fanoush said:
This might result (for some unknown reason) in your internal emmc card being corrupted (or dead). And maybe also your microsd card is now not bootable.
Did you try to prepare new bootable microsd card with CM10?
Even if your internal emmc died completely there is still a chance it could boot from microSD. Not sure about specific OMAP4470 configuration in Nook HD+ but in general OMAP chips have a boot ROM inside CPU which tries to boot in specific order from SD/MMC interfaces, NAND flash and maybe also USB and serial.
So maybe there is bigger chance to boot from microSD than internal eMMC.
So it looks like there is still some difference between OFF and ON state so it is not hopeless.
Click to expand...
Click to collapse
Thanks for this quite interesting idea.
I still had the old 4 GB SD-card that I used at the beginning. I put this back into the HD+, but this did not solve the problems. Still no reaction apart from the green light going out after around 10 seconds of pressing power...
datas0ft said:
First thing is that, that you have warranty if you bought it over Ebay UK (if seller was EU user). EU laws marks that you can return it directly to seller or importer (retailer). On UK Nook official retailers are shown here.
But anyway, if you dont plan go with return/warranty way, then ... honestly, its not hard open Nook HD+ and detach battery. Only thing what you later need is 3M two sided 3mm tape (you can find it on ebay. example). If i have time on work tomorrow i make disassemble guide if someone interested. We opened one for knowledge.
Click to expand...
Click to collapse
Thanks for the info on UK warranty. I called Nook support yesterday and they are now sorting things out (basically they have to know where the devicecame from). Will call again today.
Concerning the instructions on how to open the nook, this is of course very welcome!
In case the warranty does not kick in I will have to do something and this will almost certainly include opening the Nook's case!
Bert Randolph said:
I still had the old 4 GB SD-card that I used at the beginning. I put this back into the HD+, but this did not solve the problems.
Click to expand...
Click to collapse
What I meant is (just to be sure) to take different sd card and start from scratch - unpack CWM image and try to boot it. Because you mentioned you copied stuff from sd to emmc at that time so in case some random glitch happened both cards (sd and internal emmc) could be corrupted. But I agree the chance is low.
fanoush said:
What I meant is (just to be sure) to take different sd card and start from scratch - unpack CWM image and try to boot it. Because you mentioned you copied stuff from sd to emmc at that time so in case some random glitch happened both cards (sd and internal emmc) could be corrupted. But I agree the chance is low.
Click to expand...
Click to collapse
Yes, I used a 32 GB card when it happend. The 4 GB I had lying around with an older CM10 snapshot on it. So this card was definately okay, but the nook didn't come to life...
Bert Randolph said:
Thanks for the info on UK warranty. I called Nook support yesterday and they are now sorting things out (basically they have to know where the devicecame from). Will call again today.
Concerning the instructions on how to open the nook, this is of course very welcome!
In case the warranty does not kick in I will have to do something and this will almost certainly include opening the Nook's case!
Click to expand...
Click to collapse
How with your warranty?
datas0ft said:
How with your warranty?
Click to expand...
Click to collapse
Well, nook customer service confirms that I have warranty on the device.
But they insist that I call them to discuss the details - the thing is they only have a 0800 - number that cannot be reached from outside the UK.
So I cannot call them and when I try to explaint this via email and suggest other solutions, they answer "We think it is best you contact us by phone...".
At the moment I don't know what I can do. Maybe I just put the device on Ebay UK again, telling the whole story. A buyer from UK should easily be able to get a replacement.
Did you have time to write something about the procedure of opening the case?
Thanks!
(BLACK SCREEN OF DEATH)
OK, I have a dead Nook on my hands - non-responsive completely. A coworker of mine bought one of those CM7 cards off of Ebay and it worked fine, but had some connection issues, so I suggested he make a move to PA. Of course, I was the one that was going to do this, so I installed CWR to the EMMC, rebooted, hit N, and booted to EMMC recovery no problem.
Here's where things got stupid:
In recovery, I attempted to install PA without removing the sd card and used the internal SD Card to grab the image. Yeah, I know... Browbeating not necessary... It was taking too long and appeared stuck, and then suddenly the unit just appeared to power down. That was it. No more recovery, the card no longer worked, NOTHING!
Hooked it up to my PC and for a second or two when you hook it up, you can see in the device manager, the Motorola device pops up (I own a Motorola phone, so I assume the drivers are kicking in), and then it goes away. Long press power, do it again, same results. Still no screen, no nothing.
So I figure the 16GB CM7 card (Sandisk SDHC) still has to be useful for creating a recovery card, right? After all, whoever created it originally was able to stuff a bootloader on there, right?
So here's what I tried in terms of tools:
win32diskimager .1 r15
win32diskimager .7
WinImage 8.5
with these, I have tried the following images:
16gb_clockwork-3.0.2.8.img
generic-sdcard-v1.3.img
TWRP-2.1.8-bootable-SD.img
And I used MiniTool Partition Wizard to remove the partitions after each attempt and reformat back to its full 16GB.
The only time a burn was unsuccessful was on the 16GB clockwork with Win32DiskImager - it gave an error stating it couldn't find sectors at 99%. I tried an 8GB image too, but while it burned successfully, no dice.
Alright, so here we are, me at the end of my wits, you reading this tale of woe, and a coworker without a functioning device. The device has charged all night. I owned an NC for years and was mod-happy during that time, and although I had BSOD, I was able to fix it easily. This is a 1 year old BNRV200 (pretty sure they didn't switch up the models).
Help? Advice? WT%#$%^?
EDIT: ADB does not recognize the device when connected.
Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.
majorpay said:
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.
Click to expand...
Click to collapse
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
reply
majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou
majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
dajmaa said:
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou
Click to expand...
Click to collapse
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.
SHOOTEMUP2.0 said:
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.
Click to expand...
Click to collapse
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.
majorpay said:
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.
Click to expand...
Click to collapse
Story of my life. always a Dollar Short and a Day Late. Well in this case a couple years late.
leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.
majorpay said:
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.
Click to expand...
Click to collapse
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.
Scratch that...
I found the files, but now I have an entirely different issue.
My copy of Win32DiskImager back then was very size specific, and although I have a copy of the 16gb_clockwork file I used back then, I can't burn it because Win32DI says the card isn't the right size..
Ugh... I'll keep you all posted.
majorpay said:
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.
Click to expand...
Click to collapse
It is possible that it is a hardware failure of the SD slot. Have you tried cleaning it? The booting to SD is built into the OMAP chip and is not effected by what you have in emmc. It automatically looks at the SD slot first to see if a bootable SD is there. But it looks for specific features of the SD found there to be sure it is bootable. If it is not bootable, it tries the emmc boot partition and if valid boot files are not there, it won't turn on.
Sent from my Nook HD+ running CM10.1 on emmc.
Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.
majorpay said:
Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.
Click to expand...
Click to collapse
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Bit the bullet and grabbed my dads. It's confirmed, the SD card I recently burned works - CWR booted right up. Now for the stock cable test.
Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.
I'm done...
I'm beat. Cable turned green again, and no dice. This Nook is headed for the scrap pile (unless I get a wild hair and tear it apart to re-solder some joints).
majorpay said:
Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.
Click to expand...
Click to collapse
I went back to your OP and re-read. It is very common for an installation to screw up and lock up, leaving the boot partition borked. But usually the user can boot to a bootable CWM and re-flash and it repairs it. Ordinarily I would say that the slot could have been messed up for a long time too, since a lot of users have CWM on emmc and would not know it until they needed a bootable card. But in your case the slot was working right up till after you put CWM on emmc. And your using internal memory to flash the zip from and leaving the SD in the slot is usually of no consequence. But it is remotely possible since you left the SD in and the software was running amouk, that it did something to the SD and the slot, like overcurrents or some such nonsense. I still think the not booting from SD is a slot hardware issue since your card boots on other devices and the booting code is in chip firmware.
Sent from my Nook HD+ running CM10.1 on emmc.
Well, first off let me say I've been researching this issue for about 6 hours, and I've read several hundred posts across dozens upon dozens of threads so, I'll just say I've got a dead NC and I'm wondering if it's truly dead considering how much I keep seeing "it's practically unbrickable..." (which I've heard before on other devices).
Was working fine with 1.4.3 when I got it yesterday (boy that firmware was damned slow, good lord), then I worked out how to get CM7.2 on it and that worked fine for a bit, then I figured I'd give CM10.2 a shot and that worked fine (albeit slow which is seemingly just how the NC is), then even the latest snapshot M7 build of CM11 and even that worked somewhat (constant FC's of gapps, etc, known problems I suppose - yes I did use CWM 6.0.4.8 to install it).
So I did some more research yesterday and found out about MiRaGe CM7.2 being hailed as the best performing ROM for the NC and figured ok this could be just the ticket.
To get CM11 installed I used a Sandisk Class 4 8GB card, the 1gb_clockwork-3.2.0.1-eyeballer image, the snapshot M7 build of CM11, the most current gapps for KitKat (20140606) and then CWM 6.0.4.8, data/factory reset, reboot, worked fine until I decided to get MiRaGe CM7.2 on it.
To install MiRaGe CM7.2, I used the same SD card (the Sandisk), only placed the MiRaGe zip and the gapps-gb-20110828-signed.zip file on the card. Booted the NC to the recovery (CWM 6.0.4.8) and then inserted the SD card, chose to install zip from SD card, browsed for the MiRaGe zip and then started the install - it got to roughly 80% or so and then just hung there for several minutes, then the NC powered itself off and back on again, getting to the Cyanoboot screen, then a flash, then nothing but the display and backlight were obviously on.
Ok, not good, so then I held the power button till it shut off, ejected the card, started it up again, went into CWM 6.0.4.8 again (it was installed to the eMMC), put the SD card back in, factory wipe/etc, install zip, same thing: hung at 80% for a minute or so, then an NC reboot.
It did that twice, and after the third time when I shut it off thinking ok I'll just try the plain old vanilla CM7.2, I pulled the SD card out, put it in the laptop, copied over the CM7.2 zip, popped out the card, back in the NC (but not inserted since I needed to get Cyanoboot up to hold N to get recovery.
That's when the NC wouldn't power back up. Dead, nothing, no response of any kind. Plugged in the charger (factory charger and cable), got the typical colored light (orange or amber or whatever the hell color it is) - before I started this process the NC was 95% for battery, it wasn't plugged in during the attempts to get MiRaGe CM7.2 on it, however.
But even so, no response whatsoever. I held power for 15 seconds or so, pushed in the SD card to try and boot from that, same thing: no response of any kind whatsoever. Popped the card out completely, then decided to try Power+N (nothing), Power for 30 seconds, then let go, power for 5, no go, nothing.
Decided to plug the NC into the computer direct using the factory cable, no response of any kind - the computer is not recognizing anything whatsoever (I know some folks report they get a hardware detection of the OMAP device, I'm not that lucky). Unplug it, hold power for 15 seconds, let it go, wait 10 seconds, plug in the USB cable, still no response, no sound, no activity, no backlight, nada, zip, zilch, zero, null and void, "It's dead, Jim..."
But, I kept trying, using 2 other SD cards I have (a 1GB Sandisk and a 2GB Sandisk), same results: totally dead nothing.
Decided to make this post just for the hell of it but I'm fairly confident that it truly is totally toasted dead. I've tried different CWM bootable images from leapinlar and others, still nothing, no response of any kind, no activity.
I kinda figured that it's truly totally absolutely dead when I plugged it into the laptop and it wasn't detected at all. Holding Power+N while plugging it in (a trick of sheer physical ambidexterity, I assure you) has no effect. Not sure what I may have done, maybe the eMMC is just totally hosed - but then again, it won't boot from SD card either. I've read many posts that say if the boot partition on the eMMC is hosed, it's a dead device but then someone else will say that doesn't matter 'cause you can just put in an SD card (which has boot priority) and it'll fire up but that's not happening with mine.
Went from working device to brick, and I don't know how unless something just totally died in the process that shouldn't have. Oh well, I only paid $25 for it from someone that just didn't use it anymore. Did require a 45 minute charge to get it to wake up yesterday when I got it - previous owner said it had been in a drawer for like 9 months, hadn't been touched at all and I figured it was cheap and would give me something to do.
I know it's dead but, there's always some hope... right?
How you got to your problem was using that 6048 to try to flash mirage. You must use a version of CWM older than 6045 for it to successfully flash older zips. It now sounds like your battery is depleted. That is why you do not get the OMAP thing. Many have successfully revived their devices by dismantling and temporarily disconnecting the battery. I recommend trying that. Then it may boot to one of my older bootable CWM SDs.
Sent from my SCH-i705 using XDA Premium HD app
Well I'll be damned... IT'S ALIVE!!! (MUAHAHA--errr... you get the point).
Lifted up the back panel enough to disconnect the battery for a few minutes (don't have a Torx T-5 around here it seems, now I have reason to get one), and sure enough as soon as I reconnected it the NC sprang back to life, so that's pretty awesome. Thanks, I had thought of doing that earlier and figured it might not make that much of a difference, apparently that was a mistake that has now been corrected.
Pushed MiRaGe CM7.2 + Gapps to the device, and I have to agree with everything that's been said so far: right from the gitgo it's fast, faster than anything else I've put on here so far and I suppose given the age of the device, this is pretty much the best it's ever going to be capable of.
I wish KitKat could get a nice clean rebuild leaving out a lot of the cruft for a nice lean install on the NC, some aspects of that version of Android are very cool and the fact that it's designed from the ground up to work better with older hardware aka "limited resource devices" with low internal RAM would sure make it seem like just what the NC really needs.
Oh well, at least it's functional again, thanks for the suggestion, leapinlar, as always your assistance is greatly appreciated.