Ok fellas, my nook color has been out of commission for over 2 months. I can boot from sd but not from internal emmc.
Sam has been helpin me but it has been difficult due to him being in a different part of the world. From what i've been told my emmc is corrupt and my partitions need to be rebuilt or formatted.
I have tried the different fixes here and still i am stuck on the N screen.
I am trying to return my NC to stock form.
I will let Sam chime in also. I know there are a lot of talents on this forum and pretty sure this can be fixed.
Thanks everyone..
Sent from my SGH-T959 using XDA App
Hi,
As Wendell said, I've tried helping him with his corrupt emmc.
The problem is:
The emmc semms to be corrupt, or at least some sectors of it. Wendell cannot return it, because it boots to CWR. That's the strange part, though the disk seems totally corrupt, it still seems to be able to boot. I guess some sectors and still working. But I don't know of any way to find out which..
This is what I know so far:
The internal emmc generally returns I/O error when trying to use fdisk or parted.
But, somehow, depending on the bs and count, I can dd /dev/zero to it.
Even after having dd zeros to it, it still seems to boot to internal CWR. So, the dd isn't working. Still don't know why, or how to remedy to it.
If someone could give us a clue or two here, it would be very much appreciated. I must admit I'm really no HDD expert..
Thanks!!
Sam
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?
Any idea how the partition became corrupt? Did you dual-boot?
Partition became corrupt after flashing a couple of the very first OC kernels. Not sure if thats what caused it but wouldn't boot past N screen. Since then i have been trying to fix it by doing the several fixes to no avail and possibly damaging the emmc even more.
Sent from my SGH-T959 using XDA App
fprice02 said:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?
Click to expand...
Click to collapse
Please correct if I'm wrong but i think i need the stock recovery for this method. Unfortunately, the stock was replaced with CWR and now i cannot even get rid of CWR off the internal. If I could do it again, I would not place CWR on internal but rather run it off sd. I installed CWR via rom manager because the sd method was not yet available.
Try option number 3 in the thread I made in the general forum. the clockworkmod recover + stuck at " " screen. Flashing cwm via rom manager can cause corrupted /boot partition
Sent from my Vortex using Tapatalk
Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.
Excuse my ignorance, but will linux run off the sd card on the nook?
What about using something like GParted? Perhaps the USB bootable image on the sd card might work?
I know you are all trying to help. But please keep in mind that there aren't any obvious answers here. The emmc is corrupt. You can't flash anything to it.. and as I already stated, parted won't work either, it returns I/o error.
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
We need someone with hdd repairing experience. None of the answers found on existant threads will help Wendell..
Thank you.
Sam
Sent from my Desire HD using XDA App
samuelhalff said:
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
Click to expand...
Click to collapse
The boot may be from real hardware/non-eemc rom.
I know you said it's a emmc error - but have you tried to flash back to stock using CWM off of the SD with thecubed's MonsterRoot pack?
Yes
Sent from my SGH-T959 using XDA App
I'm sure you have tried this... but just in case...
Can you fdisk the partitions... then dd image img files to it?
I don't know if you will have any way of saving mmcblk0p2 and 3 to save your device specific information.
I believe sam has already tried
Sent from my SGH-T959 using XDA App
Here is what i would try.
First thing, get a cwm sd card setup that is bootable and has a decent amount of space so you can backup your emmc. The cwm sd card will allow us to adb in, but not worry about having any emmc partitions mounted (booting to a full android image would want at least the mmcblk0p2 partition mounted).
Make sure you have adb setup and working, so you can adb in once you've booted into cwm from the sd card. Make sure you know how to use adb pull and adb push to get files onto and off of the device easily.
Boot from the card, adb shell into the device. make sure when you are doing dd commands you are pulling from and writing to image files in a directory on the sd card, not on the emmc. you probably shouldn't even have any emmc partitions mounted at all.
Note: dd and bzip2 are both on the cwm 3.0.10 ramdisk, dunno about the earlier versions
I'd make a backup image of your emmc just in case things go from bad to worse:
Code:
dd if=/dev/mmcblk0 | bzip2 -9 > backup.img.bz2
This will take a while.
Now you'll need a MBR from someone with a stock partition table (i'm dual booting so mine probably won't work, otherwise i'd make one for you). Any volunteers?
Code:
dd if=/dev/mmcblk0 of=mbr.img bs=512 count=1
Once you have this file, just dump the image onto your emmc.
Code:
dd if=mbr.img of=/dev/mmcblk0
once you have a working partition table, you should be on your way to using the standard recovery techniques peppered throughout the forums.
btw, this won't fix any corruption in the extended partition table, that would take a little more effort (i'd have to read up on where/how that info is saved). Also obviously if it's a hardware problem rather than just corrupted data you have more problems than this will fix.
p.s. cwm loading witch a corrupt partiton table isn't that weird imho. the bootloader has barely over 400 bytes to load up the boot file and hand things off, it's probably not taking a close look at the partition map when it does this.
I know am probably being a stupid noob...have you tried the 8 failed boots?
Sent from my NookColor using Tapatalk
wendellc said:
Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.
Click to expand...
Click to collapse
Again..probably being a noob...are the file permissions set as ro? Mayhaps you need to change permissions?
Sent from my NookColor using Tapatalk
Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App
samuelhalff said:
Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Did you read my post? It is exactly telling you how to replace the first sector of the emmc. you can source it from /dev/zero with a bs=512 and a count=1 if you really wanna wipe the bootloader, but better would be just getting it working yeah? all our nooks have the same partition map (unless we are dual booting) and that map is stored on the first sector. My instruction tell how to pull the first sector with dd, and how to push it back on. notice i'm accessing the mmc directly? not the partitions? so unless his hardware is bad (or the extended partition is corrupt too) then my instructions will work. He just needs a copy of the first sector of a working nook. I'd put mine up but i'm not sure it would work, i have two extra partitions from stock. It probably wouldn't matter, but i'm not 100% sure on that, so i'd rather it be someone else that makes the image from a nook with a stock partition map (the contents of the partitions can be whatever, as long as they are all in the same place as stock).
Hi,
Thanks. Yes, I read your post. dd, for some reason, only works if I set bs to at least 1M. I don't have the NC, but maybe Wendell could confirm that.
Wendell: go to "adb shell" and type [dd if=/dev/zero of="/dev/block/mmcblk0" bs=512 count=1] without the [].
Please confirm that this returns an I/O error.
But for some reason, using 1M or greater as bs works, but the bootloader still isn't erased.. it still boots to CWR..
I'm pretty sure all the I/O error i've had mean that there's a hardware failure.. But that's my opinion, nothing more..
Thanks.
Related
I bricked my NC this morning, physical damaged, press power on button and there is no any response and I am sure battery is full.
I did following thing in recent two days, but I am not sure which one destroy it, maybe the combination.
1. flashed froyo in eMMC according below thread:
http://forum.xda-developers.com/showthread.php?t=922324
I failed in step 2 but firstly my NC can boot up and get in froyo, but is lag.
2. overclock NC to 1.1G, it works for near one day till brick, but I think this is the most possible reason finally break my NC.
3. I tried to flash HC last night but no success, after several tries, NC finally bricked.
Hope my experience can help others.
Flashing the eMMC incorrectly likely did it. The bootloader is likely messed up, nonexistent, etc now. Booting off an internal SD is often a much safer alternative and also allows a kind of dual booting. If you replace the NC, I'd recommend against writing the eMMC again until you're confident in what you're doing.
epakrat75 said:
If you replace the NC, I'd recommend against writing the eMMC again unless you're confident in what you're doing.
Click to expand...
Click to collapse
+1 x 10000000000
Be prepared to try and recover using bootable CWR on one uSD card and another uSD card with the stock image if you fail the eMMC writing process again.
awww man. I thought the NC was unbrickable. That sucks man.
xmr405o said:
awww man. I thought the NC was unbrickable. That sucks man.
Click to expand...
Click to collapse
And it's highly unlikely he actually bricked it. If he took the time to replace the partitions it'll be fine.
ctos said:
I bricked my NC this morning, physical damaged, press power on button and there is no any response and I am sure battery is full.
I did following thing in recent two days, but I am not sure which one destroy it, maybe the combination.
1. flashed froyo in eMMC according below thread:
http://forum.xda-developers.com/showthread.php?t=922324
I failed in step 2 but firstly my NC can boot up and get in froyo, but is lag.
2. overclock NC to 1.1G, it works for near one day till brick, but I think this is the most possible reason finally break my NC.
3. I tried to flash HC last night but no success, after several tries, NC finally bricked.
Hope my experience can help others.
Click to expand...
Click to collapse
Make yourself a nookie froyo uSD with CWR on it and flash back to stock
It's most certainly not bricked. Flash my repartition boot file.. no worries..
Sent from my HTC Desire using XDA App
khaytsus said:
And it's highly unlikely he actually bricked it. If he took the time to replace the partitions it'll be fine.
Click to expand...
Click to collapse
As khaytsus said there should be a way to bring it back to life. Take a break for a day or so then come back to it. That will clear your mind. Hope it works out.
I thought I had bricked my NC too. What I did was make a CWR sdcard put a stock rom on there and flashed it.
The nook is unbrickable, thanks to uSD's and ClockWork Recovery!
If you cant get your nook to boot at all try what I did:
Make a Clockwork uSD, if you don't have one.
place a copy of a stock Rom preferably 1.0.1 on the sdcard (you could find it in these forums)
Now to boot into clockwork, Stick the MicroSD in the Nook
Hold the power for about 30 seconds, If it dosen't boot don't worry.
release the power button and hold it down again.
This time it should boot into Clockwork.
Now just flash the rom and your all set!
Using this method, I recovered successfully several times today while experimenting. That is, until I tried
"Customized Nookie Froyo 0.5.9 flash to eMMC". Not exactly clear on "don't format SD from settings" I likely did such.
I've booted into CWR and tried flashing with stock 1.0.1 a few times now and my poor NC still wont boot without an SD card in it. Without a bootable card inserted, all I get is black screen.
MoreKJ said:
Using this method, I recovered successfully several times today while experimenting. That is, until I tried
"Customized Nookie Froyo 0.5.9 flash to eMMC". Not exactly clear on "don't format SD from settings" I likely did such.
I've booted into CWR and tried flashing with stock 1.0.1 a few times now and my poor NC still wont boot without an SD card in it. Without a bootable card inserted, all I get is black screen.
Click to expand...
Click to collapse
CWM Recovery SD Card and the stock system image dumps that are in the dev section will absolutely 100% clear you up. I promise.
I hosed my nook writing to the eMMC (granted, I did this 100% on purpose, lol) and just DDed the stock boot and system.img to their respective partitions to recover. Your nook is fine. It's not 100% unbrickable, but it's far from the "oops, flashed wrong HBOOT" that G1 owners had to deal with. Just keep a clear head.
Wow, sleeping on it actually helped. Here's explicit instructions on what i did to get this thing going again:
1 Downloaded nookie-froyo-5 bootables SDcard image from the devel forums and burned a card.
2 Downloaded and unzip boot.img (stock boot) from the dev forums and placed it onto the boot partition of the card (I did it from linux but its vFat and read/write-able from windows)
3 Booted nookie, no adb. Fired up term emulator and typed:
Code:
mount /dev/block/mmcblk1p1 /sdcard
dd if=/scard/boot.img of=/dev/block/mmcblk0p1
reboot
mmcblk1p1 is the boot partition of the card, 0p1 is the boot partition of the eMMC.
4 stock eMMC boot partition restored! But I never wanted stock, so...
5 Downloaded and burned the customized froyo 0.5.9 again
Booted CWM, formated /system and /data, left boot alone (afraid of touching boot now) and installed zip (which will overwrite boot it anyway).
Yaye! back to good. Now, how to format the SD card far, far away from the device....
If you had flashed my repartition boot with froyo zip..
Sent from my HTC Desire using XDA App
samuelhalff said:
If you had flashed my repartition boot with froyo zip..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Your repartition boot has been my key to experimenting this whole time! Its awesome, but for some reason, it wouldn't work after the "format card" situation...might be an ID10T error...it was 4am EST when i was doing this
Im having a issue with burning an actual uSDcard. i keep getting an error when i try to burn it regardless of what img it gives me this error.
dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Untitled 249.6 GB disk0s2
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *7.9 GB disk2
1: DOS_FAT_32 NO NAME 7.9 GB disk2s1
Timur-Dakhis-MacBook-Pro:~ rumitg2$ diskutil unmountDisk /dev/disk2
Unmount of all volumes on disk2 was successful
Timur-Dakhis-MacBook-Pro:~ rumitg2$ dd if=/Users/rumitg2/Desktop/Nook\ color/froyo-eMMC-0.2.img of=/dev/disk2 bs=1m
dd: /dev/disk2: Permission denied
Timur-Dakhis-MacBook-Pro:~ rumitg2$
i got it the first time but then it wouldnt boot
any ideas? ive tried dd ing it with SU and without
So I was going to try and change roms. And I couldn't boot into recovery, so I made a recovery bootable sd card. Me in my glorious thinking decided I would just use it to install the internal recovery and my rom.
Once the sdcard booted into recovery I did a system/data/cache wipe. then installed clockworkmod. It succeeded, so I went to the rom I had on my card. It failed. I said I know, I'll power down, take the sdcard put cm on it and try again. wrong.
Now I can't boot into recovery on either an sdcard or without and turning on the nook regularly flashes loading and goes to the page that says android with the flashing underscore.
so as far as I can tell I have no operating system, because I wiped system. and I'm not sure what is up with my recovery.
I'm looking at this page,
http://forum.xda-developers.com/showthread.php?t=914690
but I'm not sure how I would flash the zip if I can't boot into anything?
any ideas would be appreciated
constellanation said:
So I was going to try and change roms. And I couldn't boot into recovery, so I made a recovery bootable sd card. Me in my glorious thinking decided I would just use it to install the internal recovery and my rom.
Once the sdcard booted into recovery I did a system/data/cache wipe. then installed clockworkmod. It succeeded, so I went to the rom I had on my card. It failed. I said I know, I'll power down, take the sdcard put cm on it and try again. wrong.
Now I can't boot into recovery on either an sdcard or without and turning on the nook regularly flashes loading and goes to the page that says android with the flashing underscore.
so as far as I can tell I have no operating system, because I wiped system. and I'm not sure what is up with my recovery.
I'm looking at this page,
http://forum.xda-developers.com/showthread.php?t=914690
but I'm not sure how I would flash the zip if I can't boot into anything?
any ideas would be appreciated
Click to expand...
Click to collapse
Try Re-burning the Newest CWR to to your SD card, maybe your SD card has gotten corrupted
CWR 3.0.1.0 http://forum.xda-developers.com/showthread.php?t=971197
Also http://forum.xda-developers.com/showthread.php?t=949699
trying out your steps and I think I've realized the problem... but I can't figure out why it's doing what it's doing. I can't seem to correctly use dd to burn the image to the sdcard anymore... it worked the first 3 times I did with no problem. But now it's not working...
is there a certain format these cards need to be in? fat32, ext2/3/4?
constellanation said:
trying out your steps and I think I've realized the problem... but I can't figure out why it's doing what it's doing. I can't seem to correctly use dd to burn the image to the sdcard anymore... it worked the first 3 times I did with no problem. But now it's not working...
is there a certain format these cards need to be in? fat32, ext2/3/4?
Click to expand...
Click to collapse
what OS are you using? Linux? I don't know anything DD in Linux sorry.
I have been using Windows and Win32DiskImager
I think they are Fat32 images.
Maybe try Reseting the computer, and trying again.
Yeah it keeps writing phantom images to the directory that is supposed to be where my sdcard is located... and not on to the sdcard itself...
and yeah it's linux... I'm baffled... I think I will try a restart not only on my computer but on my day...
if any linux users have any advice on writing this image I'd appreciate... goodnight all I will try again tomorrow at some point
thanks for the help though!
constellanation said:
Yeah it keeps writing phantom images to the directory that is supposed to be where my sdcard is located... and not on to the sdcard itself...
and yeah it's linux... I'm baffled... I think I will try a restart not only on my computer but on my day...
if any linux users have any advice on writing this image I'd appreciate... goodnight all I will try again tomorrow at some point
thanks for the help though!
Click to expand...
Click to collapse
Make sure your Burning to the device directory and not the mount folder. (ie: /dev/sdc not /media/cardstick )
____________________________________________________
Sent from Nookie Froyo using Tapatalk
well that was what I was doing wrong writing the image. However the nook still won't boot from them...
It just goes to the dark screen that says android in light blue with a blinking cursor at the bottom left of the screen...
constellanation said:
well that was what I was doing wrong writing the image. However the nook still won't boot from them...
It just goes to the dark screen that says android in light blue with a blinking cursor at the bottom left of the screen...
Click to expand...
Click to collapse
well at least you boot Partition is intact, but sounds like you have no system or data partition.
Its very odd that the Nook wont boot off the SD card, it should look for that first in the boot Process, all i can think of is that your SD card is still not right.
I tried two different cards. The clockwork 4gb version and the 8gb version. Both looked right with the appropriate files. :/
So I don't think, though it's still a possibility, that it's the card itself
I think in the morning I'll try this http://forum.xda-developers.com/showthread.php?t=922870]
In combination with this http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151
Specifically the reverting to aosp part. To tired to deal with cli right now.
Edit: if that fails I may try this http://forum.xda-developers.com/showthread.php?t=914690
therealguppy said:
Try Re-burning the Newest CWR to to your SD card, maybe your SD card has gotten corrupted
CWR 3.0.1.0 http://forum.xda-developers.com/showthread.php?t=971197
Also http://forum.xda-developers.com/showthread.php?t=949699
Click to expand...
Click to collapse
Silly question as I haven't been able to find the info as of yet. Could you explain how we can go about burning the newest CWR ( ie 3.0.1.0 ) so we have a bootable sdcard running it ( 3.0.1.0) instead of the older 3.0.0.6 that all the burnable imgs are currently. I looked threw the thread and I don't see any instructions or talk about how to update a bootable sdcard. It only seems to discuss updating the recovery of the eMMC using ADB or the *.zip file that is linked. Any input,advice, or link would be greatly appreciated. Peace
I must say that the monster rootpack is amazing, and I am up and running
seriously when all else fails (or if you just want to cut down to it) http://forum.xda-developers.com/showthread.php?t=922870
anyway problem solved, running cm7 rc1 right now!
I bought the original Nook Color back in Nov. 2010. I went through all the methods back in the day, when guys first started rooting the Nook and all the problems we had back then ... side loading apps ... adhoc issues ... B&N updates ect ... we got CWM recoveries and finally we got fully working froyo's and Gingerbread's. Then CM7's and the Phiredrop's.
I been through it all. I ended up giving my Nook to my son, and he loved it. I got into Android Development Cell (ROMS). I Now got my Nook back from my son. It is working, but I have forgotten a lot about how to mod it .... mainly the partition tables, and how the bootloader runs. Does it look to the eMMC first ? or the SD-Card ? Can we flash from both locations ?
Anyways ... He has it setup weird now. It has a dual boot menu, I can boot into CM7 or CM9, But it is acting up and some stuff doesn't work. He also says it can boot into Stock 1.4.2 somehow *shrug*
I have done some searching here on xda but it is a lot of OLD posts and dead links.
Could you guys help me out with a few questions ?
01) I would like to wipe EVERYTHING from eMMC abd SD-Card and start over. I know I can format the uSD and also format the eMMC, but Can I flash a SD with a CWM image and then install Stock 1.4.2 on the eMMC. Do I even need to install stock first ? What is the best method for this ?
02) Will I need to nooter my nook again at this point if I do that ?
03) Can I run CWM on the SD and run a nandroid backup to that same SD if it is a large SD-Card ? I thought I could since the bootloader looks at uSD first (but I guess it looks at the boot partition huh ? ) my son says NO you can not run CWM and have a nandroid backup on that same SD. Yes or No ?
Bottom line is this is what I’m trying to do……
01a) I could care less about stock B&N.
02a) I just want a Nook that will dual boot into CM7 and / or CM9 preferably from my 16 GIG SD-Card but it really doesn’t matter, as long as I can install app’s to the external SD-Card.
03a) I want a way to backup the entire CM7 or CM9 via CWM to my SD-Card.
NOTE: I have a (1) 16 GIG SD-Card (1) 4 GIG SD-Card and (1) 8 GIG SD-Card.
If you could help me out with any info at all on any of this, please do so. I am mostly Android literate and I have a working ADB on my win7. I just have forgotten exactly how the nook operates at the lowest level, and how the newer CM's are flashed now after a clean format
Thank you for your time and help to any of my questions.
Peace
Thibor69 said:
the partition tables, and how the bootloader runs. Does it look to the eMMC first ? or the SD-Card ? Can we flash from both locations ?
Click to expand...
Click to collapse
Partition talbes and mount points
The Nook Color boots from uSD first... then eMMC if there is no bootable uSD in the card slot.
Thibor69 said:
I have done some searching here on xda but it is a lot of OLD posts and dead links.
Could you guys help me out with a few questions ?
Click to expand...
Click to collapse
Browsing the developer forum would be very beneficial... as there are constantly new posts... so almost all of this is covered in recent posts.
Thibor69 said:
01) I would like to wipe EVERYTHING from eMMC abd SD-Card and start over. I know I can format the uSD and also format the eMMC, but Can I flash a SD with a CWM image and then install Stock 1.4.2 on the eMMC. Do I even need to install stock first ? What is the best method for this ?
Click to expand...
Click to collapse
Create a new bootable CWM recovery uSD and place one of the files from here on it.
Boot into CWM and flash the file you downloaded.
Thibor69 said:
02) Will I need to nooter my nook again at this point if I do that ?
Click to expand...
Click to collapse
Only if you want stock to be rooted... not necessary if are going to flash a different ROM to eMMC or don't care about stock root access. If you choose to root stock.... use this thread
Thibor69 said:
03) Can I run CWM on the SD and run a nandroid backup to that same SD if it is a large SD-Card ? I thought I could since the bootloader looks at uSD first (but I guess it looks at the boot partition huh ? ) my son says NO you can not run CWM and have a nandroid backup on that same SD. Yes or No ?
Click to expand...
Click to collapse
Yes.... I do that frequently.. the thing is... the nandroid backup will be of the eMMC unless you use one of the modified CWM's designed for SD installs.
Additionally... if you are going to run that from a uSD with another ROM on it... you will certainly have to adjust the boot partition on the uSD to be large enough to hold the nandroid you are creating.
Thibor69 said:
Bottom line is this is what I’m trying to do……
01a) I could care less about stock B&N.
02a) I just want a Nook that will dual boot into CM7 and / or CM9 preferably from my 16 GIG SD-Card but it really doesn’t matter, as long as I can install app’s to the external SD-Card.
03a) I want a way to backup the entire CM7 or CM9 via CWM to my SD-Card.
NOTE: I have a (1) 16 GIG SD-Card (1) 4 GIG SD-Card and (1) 8 GIG SD-Card.
If you could help me out with any info at all on any of this, please do so. I am mostly Android literate and I have a working ADB on my win7. I just have forgotten exactly how the nook operates at the lowest level, and how the newer CM's are flashed now after a clean format
Thank you for your time and help to any of my questions.
Peace
Click to expand...
Click to collapse
DizzyDen said:
Create a new bootable CWM recovery uSD and place one of the files from here on it.
Boot into CWM and flash the file you downloaded.
Click to expand...
Click to collapse
So you are saying that I can do it in this order:
1) Format eMMC ( only boot partition right ? )
2) Format uSD ( resize boot partition to a larger size for backups )
3) Create bootable CWM uSB ( any particular one you recommend ? )
4) Put one of the stocks 1.4.x files on the uSB then flash it
5) Put CM7 or CM9 on uSB and flash it
Question: Do I need to flash stock 1.4.x even tho I dont want it ? or can I skip step #4 ?
Thanks
Thibor69 said:
So you are saying that I can do it in this order:
1) Format eMMC ( only boot partition right ? )
2) Format uSD ( resize boot partition to a larger size for backups )
3) Create bootable CWM uSB ( any particular one you recommend ? )
4) Put one of the stocks 1.4.x files on the uSB then flash it
5) Put CM7 or CM9 on uSB and flash it
Question: Do I need to flash stock 1.4.x even tho I dont want it ? or can I skip step #4 ?
Thanks
Click to expand...
Click to collapse
Item 1) highly NOT recommended. There is no point to format /boot.
Item 2) if "uSD" means the external microSD card, then, no, you don't need to format it since it will be done in step 3 of your list.
Item 3) Get the CwMR version 3.2.0.1. And call it "flashable CwMR uSD", not uSB.
Item 4) If you don't want stock, leave it out as no point to touch it.
Item 5) After done step 3 above, put CM7 OR CM9 in there, the CwMR uSD, and flash.
Strongly suggestion: before doing anything. Be sure you know what you trying to do or at least, pls let us know what you try to accomplish. For example, do you try to run CM7 or CM9? Do you want to run it from the external uSD card or from eMMC? Instructions are different.
votinh said:
Item 1) highly NOT recommended. There is no point to format /boot.
Item 2) if "uSD" means the external microSD card, then, no, you don't need to format it since it will be done in step 3 of your list.
Item 3) Get the CwMR version 3.2.0.1. And call it "flashable CwMR uSD", not uSB.
Item 4) If you don't want stock, leave it out as no point to touch it.
Item 5) After done step 3 above, put CM7 OR CM9 in there, the CwMR uSD, and flash.
Strongly suggestion: before doing anything. Be sure you know what you trying to do or at least, pls let us know what you try to accomplish. For example, do you try to run CM7 or CM9? Do you want to run it from the external uSD card or from eMMC? Instructions are different.
Click to expand...
Click to collapse
Hello -
Thank you for the update info. Glad I asked first. Thank you Dizzy for your help, you have been a big help to me in the past also. Votinh thank you for your reply. Looking back at what I wrote I see many mistakes in my process. Thanks for correcting them.
Now ... as to your question Votinh. What is it I am trying to do.
First off this is what I currently have. Nook is working, but not well and just a mess in general. Sometimes it locks up or just runs at a crawl. ( I have CPU oc'd to 1200 ) I have CM7 and CM9 but can't seem to boot into CM9 anymore at all. I also have CWM v3.2.0.1 installed on my external SD-Card with a nandroid backup.
I just want to erase it all and start over : )
I want my Nook to be able to Dual Boot into CM7 and CM9. I would like both CM9 and CM7 on my 16 GiG SD-Card, BUT if that is not easy or possible then I would like CM7 on internal and CM9 on external. I dont need stock.
If all else fails ... or just to complicated I could live with just CM9 (nightlies or stable) with all APPS installed to external SD. and forget about dual boot.
Again thank you .... and please ask me any more questions you might need to help clarify my goal.
Peace
Thibor69 said:
Hello -
Thank you for the update info. Glad I asked first. Thank you Dizzy for your help, you have been a big help to me in the past also. Votinh thank you for your reply. Looking back at what I wrote I see many mistakes in my process. Thanks for correcting them.
Now ... as to your question Votinh. What is it I am trying to do.
First off this is what I currently have. Nook is working, but not well and just a mess in general. Sometimes it locks up or just runs at a crawl. ( I have CPU oc'd to 1200 ) I have CM7 and CM9 but can't seem to boot into CM9 anymore at all. I also have CWM v3.2.0.1 installed on my external SD-Card with a nandroid backup.
I just want to erase it all and start over : )
I want my Nook to be able to Dual Boot into CM7 and CM9. I would like both CM9 and CM7 on my 16 GiG SD-Card, BUT if that is not easy or possible then I would like CM7 on internal and CM9 on external. I dont need stock.
If all else fails ... or just to complicated I could live with just CM9 (nightlies or stable) with all APPS installed to external SD. and forget about dual boot.
Again thank you .... and please ask me any more questions you might need to help clarify my goal.
Peace
Click to expand...
Click to collapse
So far, everything you've asked are doable, in fact, a lot of members currently having the same system you describe.
Firstly, "I would like both CM9 and CM7 on my 16 GiG SD-Card" is called "dual-boot, it is a true dual-boot.
Go thank "racks11479" for his tremendous work
Link: http://forum.xda-developers.com/showthread.php?t=1448186
Note: both CM7 AND CM9 are on the external uSD card.
Secondly, "then I would like CM7 on internal and CM9 on external."; since your wish is granted , this is just an option for you. Yes, you can easily install CM7 in eMMC (aka internal memory) and booting CM9 off uSD as you want.
For references:
Boot CM7/CM9 off uSD, thank verygreen.
Link: http://forum.xda-developers.com/showthread.php?t=1000957
---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------
Update from my last link
http://forum.xda-developers.com/showthread.php?t=1576879
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Wait a minute. Alan Moore doesn't live in Scottsdale!
Whatever. Swamp Thing is awesome. You can live wherever you want
mateorod said:
Wait a minute. Alan Moore doesn't live in Scottsdale!
Whatever. Swamp Thing is awesome. You can live wherever you want
Click to expand...
Click to collapse
Wow ... good call brother. Not many people know the face.
Peace
Thibor69 said:
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Click to expand...
Click to collapse
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Mr72 has good instructions for getting 7.2 up and running on eMMC, http://forum.xda-developers.com/showthread.php?t=1443292
You'll want to use his directions to load the image found in mrg666's thread here, http://forum.xda-developers.com/showthread.php?t=1344873
Dalingrins would be redundant as it is already part of this build. You *will* want to run the V6 script as it is well worth it.
Once you've got that going well you should have read around enough to be able to load CM9 nightlies on an SD card. You *do* have a Sandisk card, right?
Thibor69 said:
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Click to expand...
Click to collapse
In bold: sure, but what do you try to do? Format the internal so that you can install something else on it?
I currently have CM7.2-RC1 Kang running on eMMC, it is really good.
Booting off uSD is more like for experimental, play it for a while to see if we like it or not. For trying, I recommend using uSD.
I have not spent more time on CM9 since I don't see much of the benefit of it.
Also, MisRy covered pretty well there.
MISRy said:
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Mr72 has good instructions for getting 7.2 up and running on eMMC, http://forum.xda-developers.com/showthread.php?t=1443292
You'll want to use his directions to load the image found in mrg666's thread here, http://forum.xda-developers.com/showthread.php?t=1344873
Dalingrins would be redundant as it is already part of this build. You *will* want to run the V6 script as it is well worth it.
Once you've got that going well you should have read around enough to be able to load CM9 nightlies on an SD card. You *do* have a Sandisk card, right?
Click to expand...
Click to collapse
Thanks for the info Misry. I have many sd cards and have used them all will good results. My Sandisk is only 4 gig ... so it was not going to be my first choice. I also have a Class 4 8 Gig Kinston I was thinking of using. Or a Class 10 16 Gig Patriot, which I know people dont like, but it seems to work fine in my phones ....?
Magus-
The difference in the SD card class as far as speed comes down to the size of the information we want to write. The lower classes aren't very fast with the large hunks of info, but excel with the tiny byte exchange used in the ROM. As the speed of your system will really be affected by the slow I/O rates of something like a class 10, compromise on size before class. It may be counter intuitive, but people have given up on cyanogen in general only because they had the wrong sdcard. This is especially true if you have a dual boot and are running the ROM off of the sdcard itself.
Look at the "strange results or how I learned to love cm" or something thread. Google that with xda and nook and you'll find it. That has all the info you'd want and way more.
Do another book with Eddie Campbell and we'll call it square. You know you want to.
MISRy said:
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Click to expand...
Click to collapse
Well I was testing a homemade script and I believe I did in fact format eMMC and either scrambled the boot partition or deleted it also on emmc. No mater what I do I can not get eMMC to boot. I can boot cwm from SD-card, but nothing on eMMC.
Advice ?? please be as technical as needed. I do not have Linux right now, but I do have adb on win7 and 3 sd-cards
THanks
Well, let's see what we're working with...
$ su
# fdisk -l /dev/block/mmcblk0
Post the output of the above. It'll show what partitions are left (if any) and then we can take it from there. This can be a hassle indeed, and it will require some research as I have avoided doing this myself. I am hoping your ROM partition is still intact, at least.
Anybody else who can help, please do. I may not be able to respond as often as I would like.
I was gonna suggest 8+1 to see if we can get back to square one.
http://nookdevs.com/NookColor/RestoreToStock
He's gonna need a ROM partition for that to work.
For a long time, 8 failed boots would (as a last resort) result in a working Nook for just about every problem. But, as users are getting more experienced across the board, more advanced and dangerous stuff is being attempted.
When everything goes right, it can be pretty rewarding, but when it goes wrong...well, let's just say the solutions become a lot more advanced as well.
The output of the command will let us know which partitions are erased and if any are still intact. Considering the information we have so far, I am not hopeful. If the emmc was erased and formatted...well, we'll see.
Here's what has occoured:
over-wrote the following partitions with "0":
# 0p7 = /cache
# 0p1 = /boot
# 0p5 = /system
# 0p6 = /data
Then formatted 5-7 ext4. Flashing a ROM with a blank boot partition has been done on another device many times with no issues, for some odd reason this nook responded poorly and I believe the the boot.img never copied over to 0p1.
I am not sure what all he tried but I know he tried the flashable emmc fixer, which didnt' fix it. I am actually concerned that made it worse, but that's my opinion and I don't have my hands on the device. For what ever reason he couldn't get adb working with the device. I found this thread:
http://forum.xda-developers.com/showthread.php?t=919353
And since ADB wouldn't work, I wrote a script and created a flashable zip for him so it would perform the same operation, but it stopped saying bad zip. He tested it with 7zip and there were no errors, I checked my script and I see no errors in it and yes, I used a proper program for it as well, NotePad++. He's a bit frustrated and sending it to me. I am confident that if none of the things he tried didn't completely scramble the internal partitions that I can get it working. But if anyone has any idea as to why the script would fail, let me know.
Edit: And correct me if I am wrong, but it's the lack of a kernel which caused it to respond so badly. A similar thing happened on our phone but was due to powering off with a blank boot partition (not our noob moment but someone else's), but being that it's a tegra 2 system we have Nvflash and all is easily rectified. My theory is that there's something, most likely memory, which is loaded by the kernel and is required for a recovery to run.
He tried the 8 failed boot and it did bring up something which ended with an error about no boot partition, I'll try to get the picture he showed me later, I need to run off to work right now.
... Nevermind
Волк said:
For what ever reason he couldn't get adb working with the device.
And since ADB wouldn't work...
But if anyone has any idea as to why the script would fail, let me know.
Click to expand...
Click to collapse
First, why in heaven's name would you purposely want to write zeros on the boot partition?
Second, adb was not working because there was no kernel or ramdisk on the boot partition since you had him zero it out. Adb needs both.
If he was trying to flash your zip with CWM from a bootable SD card, then the zip needs to be properly signed before CWM will flash it. You can have CWM toggle off that check, but I doubt he did that. Hence the bad zip error.
Also if he has his CM7 SD card still working, he can repair the emmc partitions using the terminal emulator from CM7. All the adb type commands can be run from there.
The boot partition probably needs to be reformated to vfat before it can accept any files from a CWM restore.
OK to start I have CM7.1 on my eMMC works fine for many months. I want to install MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer ROM and it does not seem to work. Using CWM 3.2.0.1 flashing looks successful but when I reboot CM&.1 is still on the eMMC.
Tried doing a reset to default using EVRY technich suggested on these forums. No Go.
Using ADB I thought I would manually delete and push the system files over. I mount the system partition /dev/block/mmcblk0p5 and removed the existing files then pushed the new system files. But once I unmount and remount it reverts to the old files. The changes don't write dispite seeing the differences with an ls -al in ADB before the umount.
So I thought I would check the partitions and using fdisk via ADB. Deleted partitions 5, 6,7,8 and rebuilt them but when I write I get.
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
I also used the 1 - 5 - 6 - 7 - 8 fix and format zips with no joy.
I can boot to MIUI via SD but I want to put this on the eMMC.
Any ideas on how to fix this?
Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Edit: oh, you changed the version in your original post to 3.2.0.1. That version is ok.
leapinlar said:
Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Click to expand...
Click to collapse
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
Which matches the results I was seeing from adb.
rodneyshupe said:
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
Which matches the results I was seeing from adb.
Click to expand...
Click to collapse
When you boot to your SD version of your ROM, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip. They act like they have been written to, but when you come back, nothing has changed.
leapinlar said:
When you boot to your SD version, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip.
Click to expand...
Click to collapse
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?
rodneyshupe said:
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?
Click to expand...
Click to collapse
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard of anybody that this happened to their embedded chip. Sorry.
leapinlar said:
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard anybody that this happened to for their embedded chip. Sorry.
Click to expand...
Click to collapse
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?
rodneyshupe said:
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?
Click to expand...
Click to collapse
For my SD I tried everything. Images, formatting, partitioning, etc. Nothing could be written to the device.
You can make your own images of emmc by dding in reverse and write emmc partitions to your SD via adb. But if it is truly read only like my SD was, you will be able to write nothing back no matter what tool you use.
Yea I was hopping I could get an image of the entire working eMMC that included the partition tables and see if that worked in case the problem is related to a setting in the partition table.
My problem is almost similar to this , except the cause, and the seriousness
http://forum.xda-developers.com/showthread.php?t=2325101.
Could anyone report the rom problem to the official(i do not know how to access to them) and could the official give a solution? :crying:
If anyone could help me solve the problem, please tell the method step by step , i am not good at computer. If solving the problem need any files please post the downloading threads.Thanks.
I think the reason why I could not install the cm10.2 again maybe caused by load the internal memory too much. I saw someone said to install the cm would not format the data in the internal memory. When the memory is almost full , it won't install apps . Maybe it can not rewrite the rom. If so , how can i delete my personal data .?Now i can not boot the tablet , and even can not connect it to a PC. I am at a loss and very worried. I am out of USA , and it is almost impossible for me to return it to B&N to have it repaired. Could anyone here give some advice to repair it .
I asked verygreen , and he gave me an answer
There appears to be a bug in internal storage software used in Nook HDs that leads to internal storage dying under certain conditions, though the conditions are not exactly clear, but it also seems to do with a new feature added in Android 4.3
I disabled this feature on 8/15, though it's not yet clear if 8/15 nightly was built with that added or not.
The bug is not unique to Nooks too, Some Galaxy Note devices that use a very similar samsung-branded internal storage also have this problem.
But not gave the solution , could anyone solve this problem and give the solution step by step to me, thanks. i am just at a loss here
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Ogre6473 said:
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Click to expand...
Click to collapse
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
nookhdplus said:
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
Click to expand...
Click to collapse
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Same problem here.
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Now I can nearly confirm there is a fatal bug in the 8/15 rom , so many are affected by it .I recommand others not to update to the cm10.2 before the problem is solved and the official should offshelve it from the website and give a solution as quickly as possible.
talha970 said:
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Click to expand...
Click to collapse
BTW, which rom did you use when the problem occured ? Is it the 8/15 version?
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
verygreen said:
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
Click to expand...
Click to collapse
I would donate my totally bricked tablet to you but there is too much personal info in it.
Riddleric said:
I would donate my totally bricked tablet to you but there is too much personal info in it.
Click to expand...
Click to collapse
The info is likely not recoverable without some significant effort anyway, but I certainly can understand this decision too.
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Edit: BTW I never installed fstrim or anything like that. It probably was the 0813 version that initiated it but I wonder why it failed in 0815 when trim has been removed?
excalibar001 said:
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Click to expand...
Click to collapse
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Also failing that if you are just interested in warranty service, boot from my noemmc cwm, adb shell in and execute this:
dd if=/dev/zero of=/dev/block/mmcblk1p1
dd if=/dev/zero of=/dev/block/mmcblk1p2
this will make the cyanogen logo display go away and you'll just have black screen on boot.
verygreen said:
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Click to expand...
Click to collapse
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
excalibar001 said:
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
Click to expand...
Click to collapse
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Riddleric said:
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Click to expand...
Click to collapse
it does not really matter. "repair" is a codeword for "replace" these days, it's just they get your unit in and then send you one of their pile of repaired units, then see if they can fix yours and if they can, they add it to the refurbished pile to send to whoever send their stuff in next, or to sell through some side channel.
And of course I do recommend you to go the repair/replace route (unless you want to donate a broken unit to me for further research, of course ). Who knows, you might even win the emmc lottery and get emmc that is not buggy too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
excalibar001 said:
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
Click to expand...
Click to collapse
see if you can mount /cache:
in adb shell:
mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache
if that does not work, try reformatting it:
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
see if that succeeds.
then try rebooting again without sdcard and see if that helped.