Hey guys, this isn't my area of expertise once it comes to this device, so my nook color just shut off while i was reading a book, and as i tried to charge it, it went to erasing the data, reinstalling firmware, and did it for an uncountable amount of times after it tries to boot, but boot loops, and repeats. Does anyone know how to fix this? I have searched around and heard things such as a bad boot cnt file, but idk what the true problem is.
iKoolkid said:
Hey guys, this isn't my area of expertise once it comes to this device, so my nook color just shut off while i was reading a book, and as i tried to charge it, it went to erasing the data, reinstalling firmware, and did it for an uncountable amount of times after it tries to boot, but boot loops, and repeats. Does anyone know how to fix this? I have searched around and heard things such as a bad boot cnt file, but idk what the true problem is.
Click to expand...
Click to collapse
Somehow your ROM has gotten corrupted and it is trying to repair itself. If it does try to boot 8 times in a row, it will try to reset itself.
I suggest you go to my NC Tips thread linked in my signature and read item A12. You may have to eventually go to my NC partition repair thread also linked in my signature.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Somehow your ROM has gotten corrupted and it is trying to repair itself. If it does try to boot 8 times in a row, it will try to reset itself.
I suggest you go to my NC Tips thread linked in my signature and read item A12. You may have to eventually go to my NC partition repair thread also linked in my signature.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I've been searching up, but haven't tried the method i found, will doing said steps here work with repairing the bootcnt file?
EDIT: I believe i forgot to mention it only can boot up with a power source even though the battery, i believe, is charged
Related
I tried the Apps2SD 2 App on the market today. It hung then finally said error, check this guide online, which I didn't write down the link for. Restarted and now I'm in a boot loop. I tried to say forget it and installed the brand new JACHero2.2F ROM. Still boot loop
I have tried to "Wipe" which I don't really understand. What does it mean exactly? It says it was completed but my G1 is still boot looping.
I was on JF 1.41
Please please please give me some insight. I really don't understand why I can't get it back to a place where it'll boot.
bump bump bump
I actually had a similar issue with apps2sd- It crashed on me then I got stuck in a boot loop
I don't recall the exact details as its been a while, but I believe I formatted my card back to scratch and then re-applied an update. Different images wouldnt work for me until I re-did the card for whatever reason. Never found out exactly what the cause was but I attempted to get as close to a 'new' flash as I could and it worked.
Don't suppose anyone else had a similar issue and knows what happened?
HachiMatt said:
I tried the Apps2SD 2 App on the market today. It hung then finally said error, check this guide online, which I didn't write down the link for. Restarted and now I'm in a boot loop. I tried to say forget it and installed the brand new JACHero2.2F ROM. Still boot loop
I have tried to "Wipe" which I don't really understand. What does it mean exactly? It says it was completed but my G1 is still boot looping.
I was on JF 1.41
Please please please give me some insight. I really don't understand why I can't get it back to a place where it'll boot.
Click to expand...
Click to collapse
just restart call-HOME-end then hold end(power) and home then ALT-L ALT-W ALT-s and your done
So, I'm drunk with my friends, and I turn on my G1 for the millionth time in the last two days... and it turns on!!
Somehow it is working. I can only assume it is because I reformated my memory card and re-updated a million times.
The strange thing is that it is redownloading some apps. Dunno what's going on yet. I am going to apply the JFHero ROM soon.
Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Don't get too upset. You can still boot from SD. At worst, you may have to (re)install some firmware. If you want the B&N firmware, you can reinstall B&N 1.3 and update, or stay at 1.3 if you prefer.
It's hard to totally brick a NC.
Take a look at the restoring to stock section of the guide in my sig
Sent from space
Listen to the two people above this post. They are right. It is nearly impossible to completely brick it. Trust me I've tried.:what:
Seems no matter what I do to it, short of kick boxing it, I've always been able to start from a brand new running nook. Just by reading many posts and the great help from everyone on this forum, who have usually, "been there, done that.", folks.
I'm sure this will work out and everything will be fine, but then you'll be able to help someone else too.
Sent from my GT-P7510 using Tapatalk
i just use this command "fdisk /dev/block/mmcblk0 -l"
i think it was to see the partitions and they dissapeared just chek the image ;(
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
bobtidey said:
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
Click to expand...
Click to collapse
Nope... you can see he's looking at /dev/block/mmcblk0... that is internal.
Need to find the thread about the nook color partitions and create partitions 5-8 then dd the images to them.
i already fixed ! its working again
i can´t believe,
i was thinking about doing a tutorial in how to soft unbrick your nook, i´m not an expert but is a lot of people with the same problem as mine
basically when i enter in recovery receive errors in logs and he dont let me mount or format any of mine partitions(except boot and sdcard), a lot of people are having the same issues and i was thinking about doing a tutorial in how to do it.
should i do it??
thanks everybody
More tutorials are always good. One thing to remember though, is that if someone is looking for a tutorial that means they are usually starting with a small knowledge base. You not only need to be clear, you need to be right.
All I am saying is an underinformed/incorrect tutorial is worse than no tutorial at all. The information is out there, but can be hard to find. If you know your stuff, and have a place to present it where it doesn't already exist, then sure, people will benifit from your knowledge.
Just a guess, but problems mounting within CWM tend to come from old and/or incompatible versions of Clockwork. Is that where you had your problem? I definitely wished that had been stressed on the tutorial I first followed. Would have saved me untold hours of pointless reflashing.
you are right but in my case and i think that is the same of a lot of people (who follow this tutorial http://www.youtube.com/watch?v=szlGSBtWbKY) i tried about 7 to eight diferent versions of clockworkmod and including change of sdcard, i also tried DD the images of the boot and system, when nothing of this works we start get in panic, with no necessity because its only a partition problem, i fixed my 4 partition and he started working
Yeah, I can see where you are coming from. I followed an older tutorial as well, and never saw anything to indicate the link to the CWM image might be outdated.
For sure, that info should be wider spread.
Good luck on your video (?)
hackerse7en said:
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Click to expand...
Click to collapse
I am not sure where to ask for help. I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install, I power off forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. Am I bricked my nook?? please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stacked at the cw recovery screen. Help...
I see that there are other posts on this same subject and I have looked through them to try and fix my problem but I haven't found a proper solution yet. I rooted my NC (1.4.3) cm7 and it worked alright after that but apps weren't available for the version so I attempted an update then reboot. I powered down and pulled the micro sd then powered up and it gets to "Read Forever" then goes black. I have tried cm10 with manual nooter in order to try and re-do the partition on the device but it won't do anything once I put the card in and try to boot. I have had to dis-assemble it so that I can pull the battery and get it to power down completely. I have tried a factory reset boot, sd card boot with auto nooter, manual nooter, cm7, cm10, and other options on the sd card, I have also tried to boot directly from internal memory. I have tried the process of plugging it into the computer through the usb cable. I have charged the battery completely so that isn't a problem.
I have read that it is virtually impossible to brick this thing but I think I might have succeeded....any input on what I can try next would be helpful...
Fatguy86 said:
I see that there are other posts on this same subject and I have looked through them to try and fix my problem but I haven't found a proper solution yet. I rooted my NC (1.4.3) cm7 and it worked alright after that but apps weren't available for the version so I attempted an update then reboot. I powered down and pulled the micro sd then powered up and it gets to "Read Forever" then goes black. I have tried cm10 with manual nooter in order to try and re-do the partition on the device but it won't do anything once I put the card in and try to boot. I have had to dis-assemble it so that I can pull the battery and get it to power down completely. I have tried a factory reset boot, sd card boot with auto nooter, manual nooter, cm7, cm10, and other options on the sd card, I have also tried to boot directly from internal memory. I have tried the process of plugging it into the computer through the usb cable. I have charged the battery completely so that isn't a problem.
I have read that it is virtually impossible to brick this thing but I think I might have succeeded....any input on what I can try next would be helpful...
Click to expand...
Click to collapse
A good place to start with boot problems is here http://forum.xda-developers.com/showthread.php?t=949699
You should also probably read at least the first two post in this thread http://forum.xda-developers.com/showthread.php?t=1621301
You need to do a better job of describing your situation if you want help: how your NC was set up; exactly what you did that created the problem; what you want to end up with. At a guess, I will assume the you were running rooted stock on EMMC and CM7 on SD, decided to update CM7 to CM10, but used directions for updating CM that was installed to EMMC. I am not an expert on this, but sort of remember Leapinlar posting advice for someone (or maybe a few (?dozen?) someones) with this problem, you might want to search for those threads. If not, you have probably corrupted your boot records, recovery and/or possibly some partitions. Check out this thread by Leapinlar for help http://forum.xda-developers.com/showthread.php?t=1759558
If you decide to install CM on EMMC, see this thread http://forum.xda-developers.com/showthread.php?t=1030227
To install stock BN firmware to EMMC, see this thread http://forum.xda-developers.com/showthread.php?t=931720
To install CM on SD, see this http://forum.xda-developers.com/showthread.php?t=1941858
Good luck and don't forget to hit the thanks button in the posts you use
webyrd said:
A good place to start with boot problems is here http://forum.xda-developers.com/showthread.php?t=949699
You should also probably read at least the first two post in this thread http://forum.xda-developers.com/showthread.php?t=1621301
You need to do a better job of describing your situation if you want help: how your NC was set up; exactly what you did that created the problem; what you want to end up with
Good luck and don't forget to hit the thanks button in the posts you use
Click to expand...
Click to collapse
Here are the exact steps that I took to get to where I am:
I rooted the stock EMMC with the manual nooter to be able to get the Google Play Market, that worked well and I had access but the Android version was so old that I couldn't install the apps that I was after.
I then attempted to flash the EMMC to CM7, all status came up as pass and I rebooted. when it came up after the reboot all I got was the "Read Forever" screen.
since then I have read many different posts and tried to boot from the SD...that doesn't work, the screen just stays black
I have tried to boot to CWM to repair or rebuild the EMMC...same outcome
once I remove the SD all I get to is the "Read Forever" screen...
I have read and tried all the steps listed in every post you listed but they all have the same outcome
I have attached a pic of what the screen looks like when it tries to boot.
Fatguy86 said:
Here are the exact steps that I took to get to where I am:
I rooted the stock EMMC with the manual nooter to be able to get the Google Play Market, that worked well and I had access but the Android version was so old that I couldn't install the apps that I was after.
I then attempted to flash the EMMC to CM7, all status came up as pass and I rebooted. when it came up after the reboot all I got was the "Read Forever" screen.
since then I have read many different posts and tried to boot from the SD...that doesn't work, the screen just stays black
I have tried to boot to CWM to repair or rebuild the EMMC...same outcome
once I remove the SD all I get to is the "Read Forever" screen...
I have read and tried all the steps listed in every post you listed but they all have the same outcome
I have attached a pic of what the screen looks like when it tries to boot.
Click to expand...
Click to collapse
Hopefully someone more knowlegeable will look in, this is above my level. The fact that the Read Forever still displays shows that CM did not install correctly, if it's a newer version. You might want to try posting your problem in the same thread that you got the install instructions from.
I've spent hours at this now, and Im kind of wondering if my Nook Color is damaged in a way that it allows CWM to think it's written an image to the EMMC but it is actually failing to write anything.
I still have cyanoboot on the device, it still goes into Cyanogenmod boot screen and sits there indefinitely OR it reboots a couple times and gets stuck loading infinitely.
This is AFTER I have tried imaging it back to stock, CM 11, formatting it's partitions with the images on this site and various other things.
So either there is something common in all these tasks Im just blindly missing each time I try this and read/watch another tutorial that doesn't work out for me.....or something is wrong with my the Nook Color.
Can't even do the 8 failed reboots thing Im ASSUMING because the cyanoboot thing is there catching all the failed attempts.
Hadn't used the Nook Color in awhile because my wireless router died and it was kinda pointless to try to use it...now got a nice new router and the damn Nook is making me want to strangle it. So it was in some state other than stock, and I really don't remember if I was trying something new or if it worked fine when the router died at this point. I am just trying to get it to some point where it boots into some kinda of OS so I got some kind of baseline to start from at this point.
So ideas? I can get more specific if need be on what exactly I tried if it seems relevant, but I pretty much pulled the images and guides off the various posts referenced all over the net back to this forum. Hoping I missed something, going to be rather upset if this device is essentially dead since I haven't used it a whole lot since purchase..
First off, make sure you really have a Nook Color and not a Nook Tablet. The Color has a black bezel and the Tablet is silver. If it is a Tablet, the files on this forum will not work.
If you really have a Color, you need to explain more the steps you have taken to try to revive it before we can help.
Sent from my BN NookHD+ using XDA Premium HD app
It's a Nook Color, I've actually rooted and put it back to stock over a year ago. But even the methods I used then will not remove the Cyanoboot or whatever version of CM it's trying to boot into that never goes anywhere.
I've tried
http://forum.xda-developers.com/showthread.php?t=1759558
To see if it's a partition problem AFTER I tried to rewrite the boot/etc to stock and CM 11 with no luck.
Even went to Youtube to make sure I Was getting the proper screens and responses from the device.
https://www.youtube.com/watch?v=vUEoFPApfeQ To try to restore it.
https://www.youtube.com/watch?v=pj_DGZaKwBw To try to put a different version of CWM on it.
Used this link for GApps http://wiki.cyanogenmod.org/w/Gapps, I tried the "small" version along side CM 11
Tried using http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148 to try to restore it to a Nook Color rom.
Tried following http://forum.xda-developers.com/showthread.php?t=2653483 Which is a collection of help postings on the Nook Color....havent had any luck with anything on there.
http://download.cyanogenmod.org/?device=encore&type=snapshot is where I got my images for the Nook Color Cyanogenmod. I used M12, with no results.
And while Im posting all the stuff I used.... I had http://forum.xda-developers.com/showpost.php?p=50438799&postcount=4 opened if I ever got it to boot into CM to use for further issues....maybe it'll help someone else.
And I can't tell you what order I did them all in at this point because I tried and retried different things. And I still have cyanobootloader coming up, if I select EMMC recovery it goes to what looks like a barnes and noble original screen to me and says "Install failed". If I let it do the standard EMMC bootup it just loads forever.
I HAVE NOT tried to load a bootable SD with the OS, etc on it because I was trying to get the device to work properly on the EMMC first. But if that is something that needs to be done to fix it, I can do that if you point me in the right direction. I'll even try to use ADB on it if I can get some kind of guide to it...most of the ones I found were no longer valid /missing links and other things with just a few random command lines but no images or anything to use and I didn't want to risk screwing the device up even more.
Thanks.
The reason you see "install failed" when trying to go to internal recovery is because you still have stock recovery installed on internal memory.
And after you did the partition repair and you want to install CM11, you must upgrade your recovery to v6045 or newer before flashing the CM11 zip.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
The reason you see "install failed" when trying to go to internal recovery is because you still have stock recovery installed on internal memory.
And after you did the partition repair and you want to install CM11, you must upgrade your recovery to v6045 or newer before flashing the CM11 zip.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Is this referring to the CWM version on the SD card, EMMC or both? I used some of the premade images for booting and they were all older versions of CWM.
I believe I attempted to use "cwm-6.0.5.0-encore-emmc+sd.zip" when I attempted to install CM11. If it wasn't that one it was "cwm-6.0.4.7-encore-signed.zip". It was CM11 Snapshot M12 with gapps-kk-20140105 since it's smaller than 20140606. It did the blue text scrolling install of both, autodetecting gapps and installing it. Then removed both from the SD card when I did it. I didn't catch any errors.
I have not been able to get the Nook Color to enter the CWM version on the EMMC to verify it's version number....but this may be because Cyanoboot is catching it or Im doing something wrong.
If I were going to describe this problem on a PC, I'd say it was pointed at a corrupted boot device and ignoring the one you're trying to use in it's place.
Xaxl said:
Is this referring to the CWM version on the SD card, EMMC or both? I used some of the premade images for booting and they were all older versions of CWM.
I believe I attempted to use "cwm-6.0.5.0-encore-emmc+sd.zip" when I attempted to install CM11. If it wasn't that one it was "cwm-6.0.4.7-encore-signed.zip". It was CM11 Snapshot M12 with gapps-kk-20140105 since it's smaller than 20140606. It did the blue text scrolling install of both, autodetecting gapps and installing it. Then removed both from the SD card when I did it. I didn't catch any errors.
I have not been able to get the Nook Color to enter the CWM version on the EMMC to verify it's version number....but this may be because Cyanoboot is catching it or Im doing something wrong.
If I were going to describe this problem on a PC, I'd say it was pointed at a corrupted boot device and ignoring the one you're trying to use in it's place.
Click to expand...
Click to collapse
Blue text scrolling means you are trying to install to SD, not emmc.
What are you trying to install, emmc or SD? If trying for SD, you are using files made for emmc.
If you want to go back to stock, go to my NC tips thread linked in my signature and use an older version of CWM to flash the stock zip from item A15 there.
Sent from my BN NookHD+ using XDA Premium HD app
Really Im just trying to get what's on it, replaced with something that is functional so I can tell when Im doing something right or wrong.
I will attempt to do this again and try to document it a little better. I would like the EMMC to be functional at the very least no matter what version it ends up being... I will attempt stock again from your guide which I thought I did right the other night but Ill try it again.
OK.
Using:
NookColor-emmc-format-partitions-5-6-7-8.zip
TWRP-2.1.8-bootable-SD-encore.zip
nookcolor_1_4_3.signed.zip
I imaged the TWRP img onto an SD, copied both zips onto it.
Put it in the Nook Color, powered on and I saw the cyanoboot, then it loaded into TWRP.
From the install menu I installed the format partitions zip. It ran without errors. I wiped the cache/dalvik.
Then went back into the install menu and ran the nookcolor_1_4_3signed.zip. I see this:
-- Install /sdcard/nookcolor_1_4_3_signed.zip ...
Finding update package. . .
Opening update package. . .
Installing update . . .
E: Error in /tmp/sideload/package.zip
(Status 0)
*Verifying filesystems ...
* Verifying partition sizes...
Error flashing zip '/sdcard/nookcolor_1_4_3_signed.zip'
I will try it with another microSD card just incase it's defective.......and then see if trying another signed nookcolor might work from the guide.
Tried a different micro sd and used signed version 1.4.1 stock.
Did same steps. It errors, but as soon as it errors, it's like the TWRP resets real fast and gets the blue boot screen, flickers a couple times then rolls back and away to show the buttons again...takes 30 seconds or so.
Xaxl said:
Tried a different micro sd and used signed version 1.4.1 stock.
Did same steps. It errors, but as soon as it errors, it's like the TWRP resets real fast and gets the blue boot screen, flickers a couple times then rolls back and away to show the buttons again...takes 30 seconds or so.
Click to expand...
Click to collapse
Try it using the CWM instead of TWRP.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Try it using the CWM instead of TWRP.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Ok... I'm using CWM 6.0.1.2 from your guide. Format partitions zip and 1.4.3 stock signed that I used prior.
I just got done flashing the format and then stock to the nook color and no errors are reported untill...
I just finished writing Nookcolor_1_4_3_signed.zip...
Finding update packing
opening update package
installing update
boot files...
Install from sdcard complete.
And here's the first errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I don't know if they mean anything, but something similar popped up in other attempts. I am rebooting device now to see what happens.
Going to EMMC 01 in top left of Cyanoboot screen....blank screen...waiting.
Cyanomod rotating load screen comes up. And if it holds true, it'll do this until the battery dies.
I don't think the stuff is being written to the EMMC. Which...maybe it's damaged or maybe there's some kind of lock out in place preventing it that needs turned off?
If I can get it running off an SD I'll be happy at this point...perhaps it'll be easier to tell if the EMMC is screwed up then.. If you are out of ideas or think it's damaged. Only reasons I can think of since it's been sitting for a couple months is was kind of near a speaker and I know magnets can damage HDs but really strong magnets can fry phones and stuff....so might have gotten the EMMC in some weird way.
Or some sort of power surge got it when I had it plugged in before I stopped using it.
Did you try my partition repair zips from my partition repair thread linked in my signature?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Did you try my partition repair zips from my partition repair thread linked in my signature?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yes I tried 1-4-5-6-7-8 and the separate 2 one. But if you want me to try again I can.....any specific version of CWM you want me to use?
Xaxl said:
Yes I tried 1-4-5-6-7-8 and the separate 2 one. But if you want me to try again I can.....any specific version of CWM you want me to use?
Click to expand...
Click to collapse
I've always liked the v5504. If the repairs do not work, something is wrong with the NC.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
I've always liked the v5504. If the repairs do not work, something is wrong with the NC.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I figured.......I'll try it a little later and see if any luck with the repair partition zips..but I doubt it.
Meanwhile, I should probably get you to point me to some SD images to see if I can get it to boot up into CM something and work successfully off the SD card.
I'm hoping I can find a way to fix the EMMC once Im able to successfully boot the device....or even with ADB. I dunno. Pisses me off since I never used the Nook excessively and took pains to keep it safe.
Oh and I saw people asking for specific partition repair files (like unique to their device), does that sound like a possibility here?
Xaxl said:
I figured.......I'll try it a little later and see if any luck with the repair partition zips..but I doubt it.
Meanwhile, I should probably get you to point me to some SD images to see if I can get it to boot up into CM something and work successfully off the SD card.
I'm hoping I can find a way to fix the EMMC once Im able to successfully boot the device....or even with ADB. I dunno. Pisses me off since I never used the Nook excessively and took pains to keep it safe.
Oh and I saw people asking for specific partition repair files (like unique to their device), does that sound like a possibility here?
Click to expand...
Click to collapse
Go to my NC SD installation instruction thread linked in my signature to install CM to SD. I recommend CM10.1.3 from the CM site.
You can also put stock on SD. See my NC Tips thread, item B11 in the second post there.
Sent from my BN NookHD+ using XDA Premium HD app
So using 5504 of CWM with your partition repairs did nothing...still has cyanoboot and infinite load screen.
Working on SD installation now base on your recommendations.
Is there something you can think of that could be done from the SD boot to diagnose the EMMC more? It doesn't seem like there's really anything coming up on google even remotely similar to my issue.
And I've done this once with a much larger SD card but it had kind of **** transfer speeds so it might be defective... So Im repeating it as I type this.
Generic-sdcard-v1.3......rev8c.zip is what I used to image the card.
Then I used CM-11-20141112-SNAPSHOT-M12-encore.zip
and gapps-kk-20140606-signed.zip
The device ran through all the blue text and turned itself off. Loaded up with Cyanoboot going to SD01 and then it would blank screen for awhile and reboot...and repeat itself.
Now this one just error with not enough space on google apps, but Im going to see if the thing will even attempt to boot up.
Then Ill try your recommended version of CM...I already had all these images and was just hoping to see some results after all this.
OK. Some kind of success....
I actually got it to boot up using your rev8c, CM 10.1.3 and gapps-jb-20130301
BUT it gives TONS of popup errors....I was able to get through the setups somewhat. But once it's at the desktop...
I see
Unfortunately, Email has stopped. ----- Press OK then I get
Unfortunately, Trebuchet has stopped. --- Press OK, back to email.
I can kind of get into the settings and stuff, but with the continuous errors popping up it's hard to do anything productive.
So I'm going to let it sit and see if you have any input on that. I find it weird that it loaded with this version...but not the other.
As soon as I got it connected to the wireless network, a couple errors popped up, screen flashed and it went back to the cyanogenmod loading screen WITHOUT rebooting.
I don't even know what information would be useful at this point, lol.