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
Related
I went to update to use autonooter 3.0.0 with nook 1.1.0 software. I went through the process of installing the autonooter 3 and it booted up with the Android splash screen but it kept replaying the android sequence (spelling android) and it would keep restarting sometimes not getting through the entire spelling of android.
I went to reset to factory defaults and now it constantly reboots after "installing a new software update is being installed..." completes. Autonooter no longer boots it justs sits blank forever.
Please help!
hmmm...
Autonooter seemed to work for me. I just had to make sure that I was on stock 1.1 and it worked.
Try to obtain another microSD card. A 1GB will work just fine for the Autonook img.
Also, I would download another copy of the image. What you are going through seems to be a bad image either burned to the microSD or from the source.
Just my 2 cents.
I am sure that it works but for some reason I seem to be in some exception case and I need input how to get out of this mode. My nook is essentially bricked right now.
Have you tried to restore to stock using these instructions?
http://nookdevs.com/Flash_back_to_clean_stock_ROM
I could not get the 8 times failed boot to happen, no matter what the nook boot always happens, I could not get ADB to recognize the device to for the failed boot, I tried the new SD card and image. I give up. I bought it from BN last week so I will just exchange it. thanks for the help.
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
To all of you stuck in this boot loop use my guide posted here to return to stock.
It even includes the link to decadences pre-rooted 1.1 so you can use that instead of flashing back to stock 1.0 or 1.0.1. Good luck and have fun!
Note: Make sure to format /data /system and probably /boot if you are going to flash one of these. Its always best to start from a clean build.
Try the CWR bootable SD...?
quickwitt said:
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
Click to expand...
Click to collapse
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
I used winimage to write the 1.1 image here to an sd card
http://forum.xda-developers.com/showthread.php?t=945838
Put the sd card in the Nook and rebooted. It booted into CWR, I followed the onscreen instructions and now I'm back to stock 1.1.
Reflashed Nooter 3.0.
Back in business.
hvuong2 said:
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
Click to expand...
Click to collapse
I think the "pulling off the shelves" is a myth but I purchased my nook the 1st week of January. I've loaded every version of Autonooter as well as Froyo and Honeycomb without incident until now. I'm sure I screwed something up in the process or just had a bad write to the sd. I'm pleased that you can't really brick this great little tablet.
I know, its not truly bricked. But as of right now it'll only power up if connected to USB power source and will only boot as far as landscape Android text with a blinking underscore. Part of why I didn't get it fixed last night was my unwillingness to leave and aquire a larger micro SD card. I'll be leaving work in a couple hours to go get some stuff to get this thing working again (its 2 days old) heres the recovery plan:
Aquire 4GB + MSD card
Flash a stock 1.1 ROM (the one thats pre-rooted here)
Install (sideload) that stock joint
Read that Elephant book that comes with the Nook because its working again
From there I'm a little confused. Can I flash Clockwork to a MSD and then use that to flash CM7? Or am I oversimplifying here?
From my trial and error the only thing I have gotten to "un-brick" is to boot into monsters pack then switch cards (i used the 128mb version and it removed the rest of the space on my 2gig card) then format cache and system in the mount section of clockwork. then head to install zip and installed a complete restore to 1.0.1. when thats done I head to BN site and got the side load to 1.1.whatever and let it do its thing. From there your up to date and just like new and can then try and "re-brick" it. Ive had mine for less than a week and done this a few times now cause I am never satisfied.........
The nook is never bricked unless it has a hardware failure. One of the great things about the nook is that it has a very early hook in the boot sequence that checks for presence of a bootable SD card. Creating a bootable SD card is easy. Follow the thread which instructs how to make a CWM bootable SD card. You need to choose between the EXT3 or EXT4 version depending on which ROM you will flash. CM7 requires EXT4 version of CWM. If you try to use the wrong CWM version you will get the outcome that you just observed, stuck at android text. If you want to flash the stock 1.1 rom, then you'll need the CWM EXT3 version.
I had the exact same issue. I used this:
The internal CWR workaround is ugly to say the least. So if you NC should refuse to boot or bootloops, which I hope won't, flash this boot repair that I'm adding just in case. Just flash it, no need for formatting.. Use a bootable CWR SD Card.
HCext4-boot-repair flashable zip: http://www.multiupload.com/LN64D4RXEY
6.8 MB
cf963da4043d91d7f4bf8f784cd02d95 HCext4-boot-repair.zip
from the HC v4 on eMMC thread and it solved the issue and I have since flashed just about everything available with success, including dual boot ROMs. I am using a 1gb card.
Calla969 said:
I had the exact same issue. I used this:
The internal CWR workaround is ugly to say the least. So if you NC should refuse to boot or bootloops, which I hope won't, flash this boot repair that I'm adding just in case. Just flash it, no need for formatting.. Use a bootable CWR SD Card.
HCext4-boot-repair flashable zip: http://www.multiupload.com/LN64D4RXEY
6.8 MB
cf963da4043d91d7f4bf8f784cd02d95 HCext4-boot-repair.zip
from the HC v4 on eMMC thread and it solved the issue and I have since flashed just about everything available with success, including dual boot ROMs. I am using a 1gb card.
Click to expand...
Click to collapse
I'll try this and see if I can get it booted. Thanks.
nswenson said:
The nook is never bricked unless it has a hardware failure. One of the great things about the nook is that it has a very early hook in the boot sequence that checks for presence of a bootable SD card. Creating a bootable SD card is easy. Follow the thread which instructs how to make a CWM bootable SD card. You need to choose between the EXT3 or EXT4 version depending on which ROM you will flash. CM7 requires EXT4 version of CWM. If you try to use the wrong CWM version you will get the outcome that you just observed, stuck at android text. If you want to flash the stock 1.1 rom, then you'll need the CWM EXT3 version.
Click to expand...
Click to collapse
That makes things much clearer for me. I knew CM7 required EXT4, but was unaware that the CWM flashed MSD would be properly formatted and couldent be bothered to boot in Linux to do it. Blame lack of sleep. Thanks!
My Boot will not boot no matter what I do. I encountered this issue after flashing to phiremod v4, which worked beautifully until I decided to free up some storage space on my SD card and format it through the Nook. The next time I tried to boot, I got the dreaded black screen.
I've burned Clockwork Recovery (4gb v .7) onto the SD card and copied the Nook Color V1.1.0_r2 rom (found here http://forum.xda-developers.com/showthread.php?t=932145). From there, I formatted the data, system, and cache, then installed the rom from the SD card. Everything went through smoothly, until I rebooted the Nook (with the SD card out). Nothing happens! The Nook simply will not reboot without the SD card inserted. Even if it boots (with the SD card) it just sends me back to Clockwork Recovery.
I also tried recovering the Nook through ADB (using the steps found here http://mrm3.net/2011/01/24/113/). I install everything, but I cannot locate the ADB device in the device manager. I've even used the .bat file to auto installs ADB, but it is still not found in the device manager.
I've read that it is nearly impossible to brick a Nook, but I'm not sure what else to try. I'm a Android noob, so please bear with me. TIA!
Fairly certain I read about a bug with formatting the SD card on the NC, that it would format the internal memory instead. I would imagine you will need to flash a new image to the internal memory (should be stock image floating around here somewhere).
No worries, you are most likely NOT bricked. There are hundreds of posts about people thinking they bricked their device.
First thing is first, IF YOU READ THE POST IT SPECIFICALLY STATES DO NOT FORMAT THE SDCARD USING THE NOOK AS IT WIPES THE /BOOT
My suggestion to you is do some research on XDA there are PLENTY of posts about "unbricking" your device.
I have only seen 1 nook be bricked, and it was hardly bricked because it could be booted from an SDCard.
Try following the instructions here to return back to the stock OS:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Reneg4d3 said:
No worries, you are most likely NOT bricked. There are hundreds of posts about people thinking they bricked their device.
First thing is first, IF YOU READ THE POST IT SPECIFICALLY STATES DO NOT FORMAT THE SDCARD USING THE NOOK AS IT WIPES THE /BOOT
My suggestion to you is do some research on XDA there are PLENTY of posts about "unbricking" your device.
I have only seen 1 nook be bricked, and it was hardly bricked because it could be booted from an SDCard.
Try following the instructions here to return back to the stock OS:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Click to expand...
Click to collapse
Yeah, I realize that was a big no no. I am unable to perform any of the steps in the link you provided because my nook doesn't even reach the 'Welcome to the future of reading' screen. Also, I can't try method 2 because ADP is not working properly.
I should mention that I also tried samuelhalff's first method to no avail. Any other ideas?
So you CAN boot from an SDCard correct? Only way to boot again is to flash the boot file...
Reneg4d3 said:
So you CAN boot from an SDCard correct? Only way to boot again is to flash the boot file...
Click to expand...
Click to collapse
Yes, I can boot (to Clockwork Recovery) if the SD card is inserted and the power cord is inserted and I hold the power button for 10 seconds. If I install a rom from the SD card, doesn't it flash the boot file? If not, how do I flash the boot file?
I know you said you tried Sams method, I would re-read how to flash his boot repartition file found on his froyo on emmc thread
thadeus_d3 said:
Yes, I can boot (to Clockwork Recovery) if the SD card is inserted and the power cord is inserted and I hold the power button for 10 seconds. If I install a rom from the SD card, doesn't it flash the boot file? If not, how do I flash the boot file?
Click to expand...
Click to collapse
Here's the link to the boot file. I did the same thing not long ago (formatted SD from within CM7) and I fixed it by flashing this file to repartition the boot.
It's the last link in the OP of this thread (repartition-boot-with-stock.zip):
http://forum.xda-developers.com/showthread.php?t=914690
If that doesn't work, he has a couple of restore to stock methods in that thread as well.
C Dippa said:
Here's the link to the boot file. I did the same thing not long ago (formatted SD from within CM7) and I fixed it by flashing this file to repartition the boot.
It's the last link in the OP of this thread (repartition-boot-with-stock.zip):
http://forum.xda-developers.com/showthread.php?t=914690
If that doesn't work, he has a couple of restore to stock methods in that thread as well.
Click to expand...
Click to collapse
YES! This did it! I missed this link somehow. Many thanks to all that helped.
Ok, now I'm stuck on the screen that says "Contains Reader Mobile technology by Adobe Systems Incorporated". Did this happen to you C Dippa? I'm going to try a reset and see if that helps.
thadeus_d3 said:
Ok, now I'm stuck on the screen that says "Contains Reader Mobile technology by Adobe Systems Incorporated". Did this happen to you C Dippa? I'm going to try a reset and see if that helps.
Click to expand...
Click to collapse
Nope...it just booted up, may have taken a little longer.
Any luck with it?
Yeah, I had to do the 8 failed boot attempts to bypass that screen, then re-root. Now, I'm all set! Phiremod is installed again.
Glad to have helped! Happy nooting!
Sent from my Droid using Tapatalk
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!
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.