Database Develop

[Q] 8 interruptions doesn't work - install failed___UPDATE I am back to 1.1.0

My nook color is back to 1.1.0 now. I want to say thank you to all of you guys for helping me out. It was such a great experience here and I really appreciate it.
What happened is that Joja15 helped me to create the missing partitions, and then something miraculously happened during charging: it just booted all up to 1.1.0, which I had on emmc before it got stuck. I could never have done this on my own without the help. Thank you so much Joja !
Liz
This is how it was done after you have adb working:see the original thread here:
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(1) Connect Nook to PC
(2) Boot Nook into CWM off of uSD card.
(3) Verify ADB is connecting to nook by issuing the command:
adb devices
(4) If you see a serial number you are connected. Next go into adb shell by typing:
adb shell
(5) Before going any further we will want to back up your partitions 1-3 as they contain important unique information for your nook like the serial number. Make sure you 450mb of free space on your SD card.
(6) Issue the following command to backup your mmcblk0p1 boot partition to your SD card.
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1-boot.img
(7) Issue the following command to backup your mmcblk0p2 rom partition to your SD card.
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2-rom.img
(8) Issue the following command to backup your mmcblk0p3 factory partition to your SD card.
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3-factory.img
(9) Once your first three partitions are backed up in adb shell go into fdisk by typing:
fdisk /dev/block/mmcblk0
(10) Upon issuing the fdisk command you should see the following:
Command (m for help):
(11) Type m to get the help menu:
m
(12) You should see the following:
Command Action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
(13) We will use the above commands to recreate our partition table. First lets see what our current one looks like. Issue the print command by typing:
p
(14) You should see the following but probably will not because your partition table is screwed up what is listed below is what you will want to see once you have recreated your partitions:
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
/dev/block/mmcblk0p8 282 935 5253223+ c Win95 FAT32
A)
(15) We will need to first delete the partition #4 using the d command. Enter d and it should ask you which partition to delete. You will want to select or enter the mmcblk0p4 one or the #4 partition. I entered "4".
(16) Now that it is deleted we will want to create the #4 partition fresh. Issue the following command to create a partition:
n
When you enter the n command it will ask you questions like the start, the end, and the type of partition. Use the information in the print out above to enter the correct information. After you create a partition use the print command "p" to look at the partition layout and make sure that it matches the above for the new partition you created. If it does not delete the partition and create it again with different settings until it does. I tried this step several times before it was done in the correct way
(17) Use the n command to create partitions 5,6,7, and 8. Same as partition 4, it took me several times to get this done.
After that step I got a very similar layout as in step 14, but not exactly the same.
So I took the SD card out and planned to charge the NC. And that is when my nook color booted all up to rooted 1.1.0.
Hi, I am new here. Please talented people hear me out.
What happened to my NC is that I have it rooted by auto no, and CM7-ed, and it's been amazing. (Thanks to all of you guys!)
But one day, 2 days after RC4 I messed up somehow. Now my nook color won't boot right, it stuck at the n screen forever, if I don't hold the power button to power it off. I tried a lot of things here on this forum. Most of the time I get this error msg: can't mount /cache, can't format /system, install aborted......
So I removed CWR, then try to use the 8 interruptions plus the N+POWER key. It always give me the install failed msg after it started to install. I've tried to power it up after this and nothing changed. I have tried this for more than 10 times, crying now, any advice will be appreciated!

Launch cwr from SD, and use adb:
fdisk /dev/block/mmcblk0 -l
And print the output here.
Sent from my Desire HD using XDA App

ktan said:
So I removed CWR, then try to use the 8 interruptions plus the N+POWER key. It always give me the install failed msg after it started to install. I've tried to power it up after this and nothing changed. I have tried this for more than 10 times, crying now, any advice will be appreciated!
Click to expand...
Click to collapse
Do as Sam pointed out... however... the 8 failed reporting install failed is not a real uncommon item.
Even though you get the install failed message... power off by holding power button... holding "n" button... power on... keep holding "n" it should boot to factory clear... do the clear... then it will (probably) boot normally.
After that... there are things we can do to fix the 8 failed boots...

Thanks for the reply.
I will try this after work today then update here.
samuelhalff said:
Launch cwr from SD, and use adb:
fdisk /dev/block/mmcblk0 -l
And print the output here.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse

I did this power + "n", and did the factory clear. When it's done the NC automatically reboot, then it stuck at N as always
What is next then?
DizzyDen said:
Do as Sam pointed out... however... the 8 failed reporting install failed is not a real uncommon item.
Even though you get the install failed message... power off by holding power button... holding "n" button... power on... keep holding "n" it should boot to factory clear... do the clear... then it will (probably) boot normally.
After that... there are things we can do to fix the 8 failed boots...
Click to expand...
Click to collapse

I get this:
C:\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # fdisk /dev/block/mmcblk0 -l
fdisk /dev/block/mmcblk0 -l
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
~ #
samuelhalff said:
Launch cwr from SD, and use adb:
fdisk /dev/block/mmcblk0 -l
And print the output here.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse

If you have the cwr working from sd, just download the latest cm7 and place it on the sd card. Boot from the sd to cwr and choose install zip from sd card, install the cm7 zip you just downloaded.
Sent from my DROID2 using XDA App

If thats all you have on your emmc, then 4 partitions are missing.
Could someone help him rebuild the partitions using fdisk or parted, based on the stock layout? I don't have time right now.
Rebuilding of system, data, cache and media is needed.
What have you done to mess with partitions? Dual-boot?
See this thread for what you're supposed to print with fdisk: http://forum.xda-developers.com/showthread.php?t=942324
Sam
Sent from my Desire HD using XDA App

I've tried stuff here and there, after got stuck at n screen. Not dual-boot I think. Now I know what I have messed up
Thank you for the reply. I am going to study that thread.
And please, any help from you guys will be great.
samuelhalff said:
If thats all you have on your emmc, then 4 partitions are missing.
Could someone help him rebuild the partitions using fdisk or parted, based on the stock layout? I don't have time right now.
Rebuilding of system, data, cache and media is needed.
What have you done to mess with partitions? Dual-boot?
See this thread for what you're supposed to print with fdisk: http://forum.xda-developers.com/showthread.php?t=942324
Sam
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse

I've tried to install from zip file (stock). It just say install aborted. As you said, maybe i should try CM7 instead.
juvetch said:
If you have the cwr working from sd, just download the latest cm7 and place it on the sd card. Boot from the sd to cwr and choose install zip from sd card, install the cm7 zip you just downloaded.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse

How can you flash anything..? You don't have the appropriate partion layout..
You need to add the 4 missing partitions..
You should use parted (adb command). But if you have no clue and wish to use a GUI.. read the following, but I wont be held responsible for any damage..
If you choose to try, it's your responsibility all the way.. read the thread entirely before you attempt anything.
If you want repartition using a GUI on Linux, you can use a live cd:
For the following I would use gparted (linux disk utility). You can find a lot of info on Google if your not sure. Easiest is to use an Ubuntu.live CD and launch gparted.
- First with ADB:
- Boot with a bootable CWR. Once booted:
- then: echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
- The last command will mount your entire internal 8gb partition to your PC
Open Gparted:
- Select the 8GB drive (top right)
- you should see the4 existing partitions, with the extend at the end, on which you'll create the four missing partitions (system, data, cache and media, in that order)
- Unmount all partitions.
- Add the missing partitions starting with system, right after the extended partiton, find stock layout as an example and for partiton size references (from memory around 500 MB, then 900MB, then 350 and then 5GB, but find the exact size!)
- WARNING: every time you create a partition, make sure you choose round to cylinder and not MB, PLUS make sure you always leave a 1MB as preceding space, except for first partition (boot). If you don't follow this last recommendation, you'll end up with partitions writing over one another = corrupting partitions... Always leave a 1MB free space preceding.
- Finish by applying settings (nothing will be written to the disk before you apply). Then unmount the drive and reboot to cwr SD.
After that you can flash any rom to your nook to get it to boot again..
If you want to use command line partitioning, use fidsk/parted. Google it.
Again, if you attempt any of this, keep in mind you're playing around with the internal memory. IF anything goes wrong, you'll be left with sdcard booting only. But you'd really have to make a big mistake to get screwed.
And take time to check each step.. Instead of having to go through the process twice..
Sent from my NookColor using Tapatalk

Sam,
Thanks for all these input...
You are right. I am too stupid to see the truth I don't even have the right patition at this moment. I might go ahead start from parted. Need some serious reading before I screw up further more.

See this post in same thread Sam pointed earlier... it has a 7z copy of the partition 4 (mmcblk0p4) that will correct the other partition structures... then the 8 failed should work... it did on the one I was helping in that thread.
http://forum.xda-developers.com/showpost.php?p=12674635&postcount=18

I found my problem very similar to JoJa15.
When I check my recovery by this:
in adb mount mmcblk0p3 to /emmc and list its contents:
adb shell
mount /dev/block/mmcblk0p3 /emmc
ls /emmc
I found I have only two files:
ls /emmc
factory.zip lost+found rombackup.zip
~ #
This is different from what JoJa15 has. I did read on, but really hesitant to follow the posts after that before further guidance......I am afraid I will mess up with something again. So please tell me what to do next? I am so happy now, this seems to be going somewhere. Many many thanks!
DizzyDen said:
See this post in same thread Sam pointed earlier... it has a 7z copy of the partition 4 (mmcblk0p4) that will correct the other partition structures... then the 8 failed should work... it did on the one I was helping in that thread.
http://forum.xda-developers.com/showpost.php?p=12674635&postcount=18
Click to expand...
Click to collapse

ktan said:
I found my problem very similar to JoJa15.
When I check my recovery by this:
in adb mount mmcblk0p3 to /emmc and list its contents:
adb shell
mount /dev/block/mmcblk0p3 /emmc
ls /emmc
I found I have only two files:
ls /emmc
factory.zip lost+found rombackup.zip
~ #
This is different from what JoJa15 has. I did read on, but really hesitant to follow the posts after that before further guidance......I am afraid I will mess up with something again. So please tell me what to do next? I am so happy now, this seems to be going somewhere. Many many thanks!
Click to expand...
Click to collapse
Those are the only 2 files you should have on mmcblk0p3.
If you dd mmcblk0p4 file I provided in that thread... it will fix mmcblk0p5-8 and the 8 failed shoule work.... since the partitions will exist and be properly formatted.

Just be careful of you where you DD to. And make a DD image of 02 (rom) before you try anything..
Sent from my Desire HD using XDA App

samuelhalff said:
Just be careful of you where you DD to. And make a DD image of 02 (rom) before you try anything..
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'd also make DD image of 03.

Factory.zip is general and rom backup would be done with /rom..
But yeah, your never too careful..
Sent from my Desire HD using XDA App

I tried this
Code:
~ # dd if=/sdcard/mmcblk0p4-logical.img of=/dev/block/mmcblk0p4
dd if=/sdcard/mmcblk0p4-logical.img of=/dev/block/mmcblk0p4
dd: can't open '/sdcard/mmcblk0p4-logical.img': No such file or directory
~ #
I am definitely not doing this right.......
DizzyDen said:
Those are the only 2 files you should have on mmcblk0p3.
If you dd mmcblk0p4 file I provided in that thread... it will fix mmcblk0p5-8 and the 8 failed shoule work.... since the partitions will exist and be properly formatted.
Click to expand...
Click to collapse

Please bear with me coz I am really not familiar with adb.......
Could you please walk me through the steps right after this? Thanks a lot, I really appreciate it.
DizzyDen said:
Those are the only 2 files you should have on mmcblk0p3.
If you dd mmcblk0p4 file I provided in that thread... it will fix mmcblk0p5-8 and the 8 failed shoule work.... since the partitions will exist and be properly formatted.
Click to expand...
Click to collapse

[Q] 16GB in a single drive?

Hi.
I searched around but couldn't find anything on this.
Is there a way to merge internal storage and internal sd card into a single drive like i.e. nexus 7?
2GB is simply not enough space for my apps, and whenever i try to move apps to internal sd card most apps stop working properly, i.e. widgets and icons disappear.
I'm pretty sure regarding HW the 16GB is all the same flash, so there must be a way to merge this, no?
Thanks in advance.

Nope, you can't... unless you want to risk bricking your device through repartition. If you want more space for your apps then you can use Titanium Backup to make user apps into system apps. Or you could move the apps to preload.

I think you could do it with a modified pit file.
I am not going to do it for you, the risks are yours.
But if you succeed, there is a good chance that many will follow your foodsteps.
Edit: Here, have some fun.
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
This is as close as you are gonna get to a guide on how to re-partition your phone.
Make a backup of your efs partition.

Azeazezar said:
I think you could do it with a modified pit file.
I am not going to do it for you, the risks are yours.
But if you succeed, there is a good chance that many will follow your foodsteps.
Edit: Here, have some fun.
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
This is as close as you are gonna get to a guide on how to re-partition your phone.
Click to expand...
Click to collapse
Yeah, that's what I suggested... thing is that it is incredibly dangerous, the slightest mistake will perma-brick your device.

As long as he does not touch partition 1-6 there should not be a problem a pit-file flash would not fix, as far as i understand it.
I would recommend him to backup his efs partition before continuing, forgot to add that in my last post(yes i did go back to add it.).
It is not something i plan to do with my phone though. But best of luck to him.

Wow guys, stop scaring me. I'm way too noob to put myself into such dangerous areas..
If you want more space for your apps then you can use Titanium Backup to make user apps into system apps. Or you could move the apps to preload.
Click to expand...
Click to collapse
Pix, could you please explain me a little more about that, or give me some link?
How exactly will i win space making system apps, and what is moving the apps to preload?
Thanks.

Double post, please remove.

madz78 said:
Wow guys, stop scaring me. I'm way too noob to put myself into such dangerous areas..
Pix, could you please explain me a little more about that, or give me some link?
How exactly will i win space making system apps, and what is moving the apps to preload?
Thanks.
Click to expand...
Click to collapse
Sure, here is a link. SOME LINK
Apps installed on your system partition do not take up room on your data partition.
Preload is a partition i believe only used by samsung to update your device. Thus a nice place to store some apps. Not that i know anything about that, i flashed cyanogenmod the day i got my note.

You can move the apks from system to preload partition. Preload has about 500Mb of space and if you are using a stock rom then there will be some room left.
You can move apps using root Explorer. Once the apk is moved to preload, you will need to create a symlink for it in the system partition. Using root Explorer or using adb shell.

I'm using CM 10.2! Is it relevant?
I was using stock up until this monday, but fed up with constant low space warnings, unable to update chrome and move apps to internal sd partition, i flashed CM convinced that the ROM itself would merge the partition and that would be it.
But soon after i flashed CM ROM i noticed i still had both partitions and couldn't move many apps from internal memory to internal sd, the option was simply blacked out, and most i could move, simply stopped working properly..
Thanks.

madz78 said:
I'm using CM 10.2! Is it relevant?
I was using stock up until this monday, but fed up with constant low space warnings, unable to update chrome and move apps to internal sd partition, i flashed CM convinced that the ROM itself would merge the partition and that would be it.
But soon after i flashed CM ROM i noticed i still had both partitions and couldn't move many apps from internal memory to internal sd, the option was simply blacked out, and most i could move, simply stopped working properly..
Thanks.
Click to expand...
Click to collapse
I have not used cm 10.2 in a while. But i do not recall moving to sd failing.
Unless the app you are trying to move has widgets/live wallpaper.

Moving apps to SD work fine for the apps that are allowed. For others, Titanium back may help.. CM doesn't use preload partition and is wasted.

Will take a look at it.
If you don't mind me asking.. Could you explain in a noob friendly way, why is it so risky to merge partitions? I understand the risk i.e. of merging preload in stock ROM, but in a custom ROM i'm having a hard time understanding why can't i simply merge it to internal memory instead of moving apps to it..
It's hard to accept, knowing my device has the proper hardware to work as a nexus or most tablets, and that i need to do all these workarounds to simply enjoy the way it should have always been in the first place..
Thanks.

madz78 said:
Will take a look at it.
If you don't mind me asking.. Could you explain in a noob friendly way, why is it so risky to merge partitions? I understand the risk i.e. of merging preload in stock ROM, but in a custom ROM i'm having a hard time understanding why can't i simply merge it to internal memory instead of moving apps to it..
It's hard to accept, knowing my device has the proper hardware to work as a nexus or most tablets, and that i need to do all these workarounds to simply enjoy the way it should have always been in the first place..
Thanks.
Click to expand...
Click to collapse
Well, it is this way to avoid bigger problems.
Imagine what would happen if someone tries say cyanogenmod, then decides it is not for him.
He then tries to flash back but runs into trouble becouse his preload are not as touchwizz expects them to be.
Resulting in a lot of complaining.
Also, keeping the data partition separate from the sd card, allows you to reset your device to factory settings, without touching said sd card.
However, android has all the tools you expect on linux, to allow you to change partitions as you see fit. But if something goes wrong, there may not be a way to recover.
I have changed the partition sizes on my prs t1 and x10 mini pro, because i wanted to. Successfully, i might add.
But the lack of recovery options if something goes wrong, and compatibility with stock roms are 2 reasons to stay away from them.
And if you wanted to do it properly, i recommend this technique. It will require a custom kernel and recovery though. Start the compilers.
http://forum.xda-developers.com/showthread.php?t=1656794
Also, here is the partition table of a galaxy nexus. Note that it has a the same separation of data and sd-card.
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata

Thanks for all the enlightening. You make some very valid points. It's probably best to leave it alone.
One question, that partition table is for the galaxy nexus, not the galaxy note, right?
Thanks.

I see alot of wasted space in note partition table with a custom rom..
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS - do we need this? +893MB to merge datafs
10 1174MB 3322MB 2147MB ext4 DATAFS - this could be 3577MB, so much more..
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN - +537MB on datafs

FACTORYFS is where the ROM resides.

Sorry, my bad.

Well, i might have a solution for you actually.
How about mounting your internal SD card partition as data partition, and using your external SD card as SD card?

Azeazezar said:
Well, i might have a solution for you actually.
How about mounting your internal SD card partition as data partition, and using your external SD card as SD card?
Click to expand...
Click to collapse
Wow! That would be awesome!! :highfive:
2 questions instantly come to mind..
1 - How do I do it?
2 - If I format that 11.9GB partition to ext4 DATAFS, what will happen with the existing 2147MB ext4 DATAFS partition? Will it be discarded? merged? mounted as internal SD?
Thanks!! :victory:

Recover a dead emmc?

Hello guys, I am running Android off SdCard because my HD+ has a dead emmc, I recently discovered that I can read and write to it using root explorer, does that mean that there's a chance that I could somehow recover it?

mmk92 said:
Hello guys, I am running Android off SdCard because my HD+ has a dead emmc, I recently discovered that I can read and write to it using root explorer, does that mean that there's a chance that I could somehow recover it?
Click to expand...
Click to collapse
how can you access your emmc? the (emmc-less) rom that verygreen made used our sdcards as the emmc I think that what you are seeing is a portion of your sdcard not your emmc

Hello,
I've seen your other thread here at XDA, and I'm not trying to be offensive, but I think you maybe confused with EMMC, Pure SD install and the term "dead EMMC". Apologies I didn't reply to your other thread earlier; I did/do not have much time. Please note, I do not indent to be offensive at all, just trying to put facts together; to hopefully ease you to achieve your solution.
For starters, I don't think your EMMC is "dead"; else you would have a difficult time booting your tablet up (I'd be surprised if a Nook turned on with a dead EMMC), even if you're purely installed on an SD card. Personally what I think is going on, you stated in the other thread your friend gave you this Nook. Your friend thought he (assuming he's male) could install CyanogenMod on his Nook, but unfortunately he couldn't. Effectively, he thought he had "bricked" or damaged his Nook; at this point it was not working the way he intended, and couldn't boot into CyanogenMod. He turned to you for help, or you stepped in, as your more "technical" with this stuff. Of course, I could be wrong. You knew you wouldn't be able to fix this, but you could use an alternative way to boot CyanogenMod; using only a SD card.
Not bad idea, but I'm quite confident that your EMMC is not "dead" and that you can install CyanogenMod on your internal storage without a SD card being required for boot. Apologies if my assumptions contain mistakes, I only completed reading the thread after posting the above.
I was going to post some suggestions and write up some guides, but before I do, please may I ask a question? You said you're using Root Explorer? Where is this? On your stock ROM on internal/EMMC, on a CyanogenMod build on EMMC, or on Pure SD? If you're booting using purely a SD card, and have Root Explorer running, you can edit files because it's editing files on your SD card, not your EMMC (although it may say internal, a pure SD install "emulates" the internal storage).
Again, please reply with the answer(s). I'll do my best to assist. Also, just a quick note; it's not necessary to make two threads. You could have still used your earlier thread.

HiddenG said:
Hello,
I've seen your other thread here at XDA, and I'm not trying to be offensive, but I think you maybe confused with EMMC, Pure SD install and the term "dead EMMC". Apologies I didn't reply to your other thread earlier; I did/do not have much time. Please note, I do not indent to be offensive at all, just trying to put facts together; to hopefully ease you to achieve your solution.
For starters, I don't think your EMMC is "dead"; else you would have a difficult time booting your tablet up (I'd be surprised if a Nook turned on with a dead EMMC), even if you're purely installed on an SD card. Personally what I think is going on, you stated in the other thread your friend gave you this Nook. Your friend thought he (assuming he's male) could install CyanogenMod on his Nook, but unfortunately he couldn't. Effectively, he thought he had "bricked" or damaged his Nook; at this point it was not working the way he intended, and couldn't boot into CyanogenMod. He turned to you for help, or you stepped in, as your more "technical" with this stuff. Of course, I could be wrong. You knew you wouldn't be able to fix this, but you could use an alternative way to boot CyanogenMod; using only a SD card.
Not bad idea, but I'm quite confident that your EMMC is not "dead" and that you can install CyanogenMod on your internal storage without a SD card being required for boot. Apologies if my assumptions contain mistakes, I only completed reading the thread after posting the above.
I was going to post some suggestions and write up some guides, but before I do, please may I ask a question? You said you're using Root Explorer? Where is this? On your stock ROM on internal/EMMC, on a CyanogenMod build on EMMC, or on Pure SD? If you're booting using purely a SD card, and have Root Explorer running, you can edit files because it's editing files on your SD card, not your EMMC (although it may say internal, a pure SD install "emulates" the internal storage).
Again, please reply with the answer(s). I'll do my best to assist. Also, just a quick note; it's not necessary to make two threads. You could have still used your earlier thread.
Click to expand...
Click to collapse
I think you are quite wrong.The lagfix app bug actually does kill the emmc what hes using is an emmc-less rom that verygreen created for all the users who were affected by the emmc bug. This rom doesnot use the emmc at all it treats the sdcard as the emmc

Ahh, no problem. Thank you Talha, that cleared a few things for me. Haha, I've been missing from the latest developments on the Nook's.
Still, I hold my statement in this case, as the OP stated he can boot into EMMC recovery (source). So the EMMC is not dead.

Thank you guys for the replies!
I am accessing the emmcs through Root explorer on a nonemmc ROM, so I could be accessing the SD card itself, makes perfect sense.
But if i boot up my tablet without an sd card, it goes to the internal EMMC recovery, in that recovery I can access the SD card, but can't mount the emmc itself. (it says E: error can't mount /emmc/
This is weird because I've always though the recovery and ROM resie on the emmc.
Please pardon my ignorance guys.

mmk92 said:
Thank you guys for the replies!
I am accessing the emmcs through Root explorer on a nonemmc ROM, so I could be accessing the SD card itself, makes perfect sense.
But if i boot up my tablet without an sd card, it goes to the internal EMMC recovery, in that recovery I can access the SD card, but can't mount the emmc itself. (it says E: error can't mount /emmc/
This is weird because I've always though the recovery and ROM resie on the emmc.
Please pardon my ignorance guys.
Click to expand...
Click to collapse
No problem, haha. Is the recovery on your EMMC ClockWorkMod or TeamWin Recovery? If either of these, and you can boot into them; then may be I have a solution for you. Please let me know.
Also, have you tried flashing a ROM using your EMMC recovery? I'm pretty sure you have, and I'm assuming an error was presented? Let me know.

Without an sd card inside the Nook, it boots straight to CWM recovery. I tried flashing " cm-10.2-20131207-NIGHTLY-ovation.zip" first it gave me "E:Can't mount /cache/recovery/last_install E: failed to open last_install: no such directory or file" then it started running then it gave me a (status 0) error and then eventually aborting. I tried flashing the TWR, reports the same "last_install"errors like the ROM flash, then it finished really fast(around a second) reports a "Done..! Install from sdcard complete." but changes absolutely nothing (if i restart it goes back to CWM).

mmk92 said:
Without an sd card inside the Nook, it boots straight to CWM recovery. I tried flashing " cm-10.2-20131207-NIGHTLY-ovation.zip" first it gave me "E:Can't mount /cache/recovery/last_install E: failed to open last_install: no such directory or file" then it started running then it gave me a (status 0) error and then eventually aborting. I tried flashing the TWR, reports the same "last_install"errors like the ROM flash, then it finished really fast(around a second) reports a "Done..! Install from sdcard complete." but changes absolutely nothing (if i restart it goes back to CWM).
Click to expand...
Click to collapse
I think that your emmc is working but your partitions are broken

So there's hope? What do you guys suggest I do

mmk92 said:
So there's hope? What do you guys suggest I do
Click to expand...
Click to collapse
It is possible that your emmc is readable, but not writeable. I had an SD where that happened. It would act like it was writing and the PC would say successful, but when I ejected the SD and reinserted, it has not changed. Nothing I could do would revive the SD. I had to throw it away.
I suggest you use your noemmc ROM to explore emmc to see if you can change anything and have it stick after a reboot.
Sent from my BN NookHD+ using XDA Premium HD app

Bits in SD cards have a certain lifespan, I believe between 10k-100k read/writes until they become unwritable. Some generic/defective cards have much less. So in your case it could've been an old/cheap brand SD card that happened to die. Although the eMMC shares these drawbacks, it has a much longer lifespan, and I highly doubt this the issue for the emmc.

I attached to this post a dump of logs that I have collected from my Nook. I see a bunch of "unknown partition table" in there, so could that be the problem? Does that mean that a partition fix should solve my problem?(I've read about lots of devices revived from broken partition tables).
What if this is the issue for most people and not a dead eMMC chip? If this theory proves to be true maybe many nooks will be brought back from the dead.
It's times like these that I wish that I was more experienced with such low level stuff I barely know the terminology so again, please ignore my ignorance.

Sorry for the mult-posts, why did you leave meeh out to dry I am willing to try anything on my Nook if it has a chance to get back to life.

mmk92 said:
Sorry for the mult-posts, why did you leave meeh out to dry I am willing to try anything on my Nook if it has a chance to get back to life.
Click to expand...
Click to collapse
Is yours like this? http://forum.xda-developers.com/showthread.php?p=44842492&highlight=partition#post44842492
Sent from HD+ MAG2GA CM 10.2 from SD

I get no output for the command dmesg|grep mmc1 nor dmesg|grep mmcblk1
I do however get response from dmesg|mmcblk0
~ # dmesg|grep mmcblk1
dmesg|grep mmcblk1
~ # dmesg|grep mmcblk0
dmesg|grep mmcblk0
<6>[ 3.039337] mmcblk0: mmc0:0001 MAG2GA 14.5 GiB
<6>[ 3.039611] mmcblk0boot0: mmc0:0001 MAG2GA partition 1 2.00 MiB
<6>[ 3.039825] mmcblk0boot1: mmc0:0001 MAG2GA partition 2 2.00 MiB
<6>[ 3.040649] mmcblk0: unknown partition table
<6>[ 3.041839] mmcblk0boot1: unknown partition table
<6>[ 3.042846] mmcblk0boot0: unknown partition table
~ #
Click to expand...
Click to collapse

mmk92 said:
I get no output for the command dmesg|grep mmc1 nor dmesg|grep mmcblk1
I do however get response from dmesg|mmcblk0
Click to expand...
Click to collapse
The 1 applies when booted from the noemmc sdcard.
Here's another possibly helpful post http://forum.xda-developers.com/showthread.php?p=44887350
Sent from HD+ MAG2GA CM 10.2 from SD

~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ # mount .cache
mount .cache
mount: can't find .cache in /etc/fstab
~ # mount /cache
mount /cache
mount: mounting /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache fa
iled: No such file or directory
~ # mount /cache
mount /cache
mount: mounting /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache fa
iled: No such file or directory
~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ #
Click to expand...
Click to collapse
I get the "Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory" on every run.
Also tried flashing Stock from all recoveries, still no change

mmk92 said:
I get the "Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory" on every run.
Also tried flashing Stock from all recoveries, still no change
Click to expand...
Click to collapse
Here is a link for recreating the partition table http://forum.xda-developers.com/showthread.php?p=44620340&highlight=table#post44620340
Sent from HD+ MAG2GA CM 10.2 from SD

I got this interesting message when I executed print in parted.
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? yes
yes
yes
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 30535680s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 256s 511s 256s xloader
2 512s 1023s 512s bootloader
3 1024s 31743s 30720s recovery
4 32768s 65535s 32768s boot
5 65536s 163839s 98304s fat32 rom
6 163840s 262143s 98304s fat32 bootdata
7 262144s 1179647s 917504s ext4 factory
8 1179648s 2555903s 1376256s ext4 system
9 2555904s 3506175s 950272s ext4 cache
10 3506176s 30507007s 27000832s ext4 userdata
(parted)
Click to expand...
Click to collapse
Also the partitions seem intact, what do you suggest I do?

Need help mounting /system and /data from external SD. Internal SD is dead :/.

Hello,
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2

I see it's been a couple weeks with no update but if you're still stuck this may help. I had similar issues trying to flash zips from recovery. I kept getting the "can't mount" error message and what I figured out is that the access to CWM recovery via the update method I'd used was pretty much loaded up in cache, thus I couldn't mount . Getting back to total stock first may help. This is the basic rundown I performed to get my cappy back up ... currently on JB. Granted, I didn't go about reformatting drives as you did.
1. Flash I897UCKK4 with Odin (no root) for gingerbread stock rom
2. Download and install KK4root. Run Kk4 root "run" exe in the kk4_root folder. Corn kernel is installed with modded recovery system
3. From Corn kernel recovery click "root extras" to get su and busy box installed
Everything is pretty much dependent on using them in Windows and still active in download links if you do some searching.
Hope it helps!

Aimless Rambler said:
I see it's been a couple weeks with no update but if you're still stuck this may help. I had similar issues trying to flash zips from recovery. I kept getting the "can't mount" error message and what I figured out is that the access to CWM recovery via the update method I'd used was pretty much loaded up in cache, thus I couldn't mount . Getting back to total stock first may help. This is the basic rundown I performed to get my cappy back up ... currently on JB. Granted, I didn't go about reformatting drives as you did.
1. Flash I897UCKK4 with Odin (no root) for gingerbread stock rom
2. Download and install KK4root. Run Kk4 root "run" exe in the kk4_root folder. Corn kernel is installed with modded recovery system
3. From Corn kernel recovery click "root extras" to get su and busy box installed
Everything is pretty much dependent on using them in Windows and still active in download links if you do some searching.
Hope it helps!
Click to expand...
Click to collapse
Thanks for the reply; I constant checked this site for a week or so with no response, so I gave up. I would have been able to go with your method if my download mode worked. Basically, I cannot go into either download mode or fastboot. I tried to flash different kernels to try to enable it, but I kept running into error 0 even after I changed the binary. Any idea? Thanks.

[Q] Need help mounting /system and /data from external SD. Internal SD is dead :/

Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2

PMrjn83 said:
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
Click to expand...
Click to collapse
Have you looked over this guide ? or this ?

Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
Thanks. I'll try when I get home to my desktop. For some reason, my laptop does not recognize the phone through adb. It shows "SGH-i897" in device manager with an exclamation mark. And yes, I have tried quite a few drivers, etc... :/
I might need to try this...
http://forum.xda-developers.com/showthread.php?t=1761968

Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.

PMrjn83 said:
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
Click to expand...
Click to collapse
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.

gsstudios said:
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
Click to expand...
Click to collapse
Well, I tried. If it doesn't mount at all, how can you format?