[Q] HELP with EMMC and CWM! anyone? - Nook Color General

Sorry if this isn't in the right place, but i'm hoping it's something simple. I finally decided to take the plunge and try HC on emmc. I have all the right files, and an using the same method to format/write that i used to run off sd. I have tried 5 different cards from (patriot/sandisk/wintec/) various sizes and speeds also. I have also tried re-dl-ing the cwm images, and the hc zip bootable zip. HERE'S WHAT HAPPENS, every time...CWM installs fine, The first 3 things I do are "format system", "format data", and "format boot", in that order, and then choose zip from sd card, (making sure none of above are mounted)...Update goes fine, tells me all is good. After I take out sd and repower, blackscreen. Every time. Help? I did notice that when CWM starts, it seems to automatically have mounted cache...Is that correct? What am I missing? I'm going crazy trying to figure this out.

Not 100% sure...
I'm not 100% sure, but I do not think you need to format boot. I made the mistake of formatting boot, and guess what? It stopped booting and took me ages (literally hours and hours trying to piece it all together again).
Finally got it back to stock, now running Froyo 0.6.7 (even though my market doesn't work... it says that it is starting to download... but nothing!!!). Anyhow, at least it can boot though...
So for the time being, I am getting the apks online. But I would say, give it a shot... format data and system, and leave the boot alone. See how that works out.

Related

[Q] HC emmc install hangs

I've gone thru the paces numerous times, even rolled a rooted install back to a full install of 1.0.1 and reapplied the HC v.4 (following all instructions carefully). I don't have any problems with the file extraction and get the Done message. However, when I reboot the nook it gives me a Loading screen then flickers a few times and then an ANDROID_ (flashing curson) and hangs. I've gotten this far every time I've tried to apply the zip. Once in awhile it will flash between the Loading and ANDROID_ screens a few times but ultimately I end up with ANDROID on my screen and nothing else.
Any ideas or direction I can move in? I'm anxious to try this out but prefer to run it from internal memory instead of an SD card...
There does seem to be one disparity between the instructions and the actual application of them, there doesn't appear to be a way to unmount /boot that I recall, only format it.
Make sure data and system have been formatted without issues before flashing the zip.
If that doesn't work, you might have a system partition size issue. Download shad0wf0x's stock image and dd it to your mmcblk0p5 partition (see specific thread). Then try flashing zip after having formatted both data and system.
Sent from my HTC Desire using XDA App
During the formats I haven't gotten any error messages, just a simple Done. when the format of each completes. I do hang when boot is done but a hard reboot, per the instructions, allows me to continue from there and I making sure /system and /data aren't mounted.
I'll give this a shot and let you know how it works out.
Thanks.
That didn't seem to do the trick. The last time I did this I started from a complete reinstall of 1.0.1 with an image I got from this thread.
http://forum.xda-developers.com/archive/index.php/t-914690.html
I'm able to boot into the stock install without difficulty, register the nook, setup my gmail association and then root. If I had a corrupted systems directory would I be able to do all those things?

I could really use some help, *UPDATE* Thanks XDA....

I don't know where to turn. I started a thread about my effed up nook but it got deleted (my fault) I'm completely at my wits end here. I had NookFroyo .68 working just fine on mine but like an IDIOT I thought it would be neat to try out CM7. Big mistake would not get past the animated N screen no matter what. I got the SD version of the Customized Nook Froyo to boot up but its very slow and stuff doesn't work. How do I get a ROM back on the eMMC? Some one suggested I get CWR and a ROM on the card and flash it via CWR off the card onto the eMMC. How exactly do I do this? I CANNOT get the winimage method to work no matter what I do and I don't know WHAT I'm doing wrong. Everytime I direct winimage to the place I've downloaded an image to, theres nothing there....
I thought I ALMOST had it a few minutes ago. I can get the CWR to come up and I flashed the flashable eMMC NF. I got my hopes up as it started to boot BUT OF COURSE NOT - went into a boot loop, constantly doing the N screen over and over. WTF.
I'm desperate here. I'm at the point where I'm willing to pay someone a small fee to help me get this sorted out. I'm going to keep on trying....
on win image, when you go to select the file. you must change the file types it see's to everything. that will let you see the .img file you downloaded.
We are talking about Win32disk imager right? It only gives the *img selection.
KDOG2020 said:
We are talking about Win32disk imager right? It only gives the *img selection.
Click to expand...
Click to collapse
click the arrow and hit ALL FILES
I AM clicking the arrow, there is ONLY *img....
I've heard of an 8 boot reset. How does that work?
I'm reading the "Recovery" thread. Should I do the "repartiion" zip file? I'm starting to think that maybe the problem...
EDIT: Tried the Repartion.zip. No change. Still continously reboots.
I just tried the Nook restore file and it still gets hung up on a different N screen (the Nook symbol). What in the HECK! It wont' go into CWR anymore, says there isn't any room on the card. AN 8GB CARD!!!! I put the card back in the computer and it says its only 115MB! WHAT THE HELL IS GOING ON HERE.
EDIT X2: LOOKS LIKE I GOT IT BACK TO STOCK. WHEW! Now I can start over! Tomorrow after I rest a bit. LOL
KDOG2020 said:
I just tried the Nook restore file and it still gets hung up on a different N screen (the Nook symbol). What in the HECK! It wont' go into CWR anymore, says there isn't any room on the card. AN 8GB CARD!!!! I put the card back in the computer and it says its only 115MB! WHAT THE HELL IS GOING ON HERE.
EDIT X2: LOOKS LIKE I GOT IT BACK TO STOCK. WHEW! Now I can start over! Tomorrow after I rest a bit. LOL
Click to expand...
Click to collapse
This will allow you to get the card back to showing 8gb:
http://www.sdcard.org/consumers/formatter_3/
Hi,
I found this post (in developers/cm7 users thread) very useful for installing
CM7:
http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151
It is a little dated (weeks) but very detailed and should hopefully still all work fine.
Some more general information on:
http://nookdevs.com/Portal:NookColor
I find that I never have enough uSD cards to use - so make sure that
you have several spare. The emmc Androids are still in general expecting
an external SD card for storing data such as ebooks etc. and CWM will
backup to the external cards too.
CM7 and Froyo use different disk format types for various partitions, don't know,
but that may be part of your problem?
Your PC won't normally read some of the linux partitions on the SD card
either - hence only 115MB showing. This is the boot partition, formatted with
FAT32 (a PC related format) In general you don't need to reformat this partition,
just update or change some of the files. (Some of the names of formats used include:
FAT32, EXT3 and EXT4)
CM7/17 and CM7/19 Have both been very stable and easy to use for me. I switched
to CM7 from Froyo 6.8 a week or so ago.
Good luck, the Color Nook is a fun device!
Peter
Thanks all I appreciate the help. I used some HP utility to take care of the cards, worked great.
Ok I've got a NF .68 up and running. Titanium backup worked beautifully. SetCPU is running it at 1.1 interactive..... HOWEVER!....
I flashed it with a another version of the CWM flashable .68 NF that I had previously. I tried to reflash the other version and it went to install then stated "Installation aborted". I tried twice and got the same thing. I guess its no big deal since their the same version just this one thats on there had some more tweaks hence the title "Customized".
My question is why did it do that? My guess I was supposed to format or clear the data/system/caches' in CWR. Is that right? If so, which ones precisly do I clear or format before flashing a new ROM? I'm starting to think thats' what happened when I tried to load CM7 (Yes I had CWR 3010) and go me all borked to begin with....
And if someone would like to answer a quick question. What this EXT4 stuff and how does it pertain to flashing ROMs? Thanks guys... Your advice got me back up and running!
KDOG2020 said:
Ok I've got a NF .68 up and running. Titanium backup worked beautifully. SetCPU is running it at 1.1 interactive..... HOWEVER!....
I flashed it with a another version of the CWM flashable .68 NF that I had previously. I tried to reflash the other version and it went to install then stated "Installation aborted". I tried twice and got the same thing. I guess its no big deal since their the same version just this one thats on there had some more tweaks hence the title "Customized".
My question is why did it do that? My guess I was supposed to format or clear the data/system/caches' in CWR. Is that right? If so, which ones precisly do I clear or format before flashing a new ROM? I'm starting to think thats' what happened when I tried to load CM7 (Yes I had CWR 3010) and go me all borked to begin with....
And if someone would like to answer a quick question. What this EXT4 stuff and how does it pertain to flashing ROMs? Thanks guys... Your advice got me back up and running!
Click to expand...
Click to collapse
Always format /system, /data, and /cache. Whatever you do DO NOT format /boot.
As to why you may have had an issue on trying the other ROM. My guess is it has to do with what version of CWR you had been using and wha twas on the device prior to flashing it. I've found if you make say a nandroid backup using 3.0.0.6 or earlier, and are currently using CWR 3.0.1.0 they don't mix well. And I think it has to do with the fact the older CWR version only supported ext3, and the newer one has ext3 and ext4 support. So once you install a ROM using CWR 3.0.1.0 that uses ext4, and then you try to go back to a ROM that is ext3 it just doens't work out like planned.
That all said I not longer flash CWR to eMMC, and I have a bootable sdcard running 3.0.1.0 with all my current and old backup files. Make life much much easier IMO seeing as you can always boot to an sdcard, and all backups are in the correct format and will Restore just fine.
Thanks for the info! I'm sure that will make trying to upgrade to CM7 actually work! LOL!
But first can someone explain to me what this EXT3/4 stuff is?
Different filesystems for Linux/Android. Wikipedia has pages for each if you want google them and get too much info
Too much info? No thanks! As you can see I can barely handle the info I'm getting now!

Need some serious help...

Alright here's my whole story...
Was running Froyo 6.8 flashed to internal memory. Was going to update to latest Phiremod. Booted into clock recovery and formatted system and data. Then went to install the Phiremod zip and it wouldn't work. I forget what it said now because i've been trying so many things. Either way wouldn't go more than a line or two before saying it couldn't install. Now after reboot it won't go past the blue android line in the upper left corner. I can still get into clockwork but now it says it can't mount sd card. Someone please help. I knew I should have left it alone...
Well as long as the hardware itself is ok there should be no need to worry. I wish I had enough experience to help you through this but Im afraid at this point it would be like the blind leading the blind. So just relax and be patient and im sure someone will be able to help get you going again.
jrob9583 said:
Alright here's my whole story...
Was running Froyo 6.8 flashed to internal memory. Was going to update to latest Phiremod. Booted into clock recovery and formatted system and data. Then went to install the Phiremod zip and it wouldn't work. I forget what it said now because i've been trying so many things. Either way wouldn't go more than a line or two before saying it couldn't install. Now after reboot it won't go past the blue android line in the upper left corner. I can still get into clockwork but now it says it can't mount sd card. Someone please help. I knew I should have left it alone...
Click to expand...
Click to collapse
Try flashing it again this time also formatting cache and MAKE SURE NOT TO FORMAT /BOOT! Also make sure none of the partitions are mounted. If that doesnt work write down the darn error msg.. oh also redownload phiremod and compair it against the md5
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
I've had a few instances where the sd card just stopped talking to the nook. Usually just taking it out and reseating it seemed to help. Could be this is the issue with not mounting, either that or the card just needs to be reburned with an image. I would start with just popping it out and back in, and if this doesn't work relfash the image to the card. If I'm not mistaken Phiremod is based on CM7, and you need an EXT4 aware CWR. Make sure you have the right version for what you are installing.

[Q] CM9, Encryption, and Locked SD Card

So I installed CM9 on my TouchPad, Alpha 0.6. It's been running fine for close to two weeks. I went to turn it on after it had been sitting and charging (it was at no lower than 60% when I hooked it up), and it wouldn't turn on. I tried all combinations of holding down the various buttons nothing worked. Then, out of the blue, while trying to figure out that problem, it held down power and it turned on.
So it started booting into ICS, but instead of the home screen, it said that the encryption failed or something, and that I had to do a factory reset. I booted into CWM, and tried everything, including re-installing from zip, installing Alpha 2 from the zip, wiping the SD card, doing a factory reset...everything. Every time, I go back into the SD card and all the folders are still there. That's making me think that the SD card was locked by ICS somehow, and now isn't letting go, and as such, nothing can wipe the system.
Any ideas for a fix to this? I love CM9 on the TouchPad, but...this sucks.
Wow, nothing, eh? I've tried everything I can think of; the tablet is getting stuck at 12% when I try to run WebOS Doctor (and yes, I've tried every "stuck at 12%" trick I could find), and in general, it appears that writing to any part of the device is locked. I guess I'm going to warranty return it back to HP, unless anyone can think of something brilliant.
Can you boot to webos, maybe if you take the sd card out? If you can, do a full secure factory reset. Also try formatting the sd card (backup your files to your PC). You should try with another sd card also . If these don't work I guess HP warranty is the way to go. Take the sd card out before you send it back. Good luck.
Thanks for replying.
Yeah, I can boot into WebOS, but any changes I make there don't keep (i.e. if I install an app and reboot, it's gone when I get back). There isn't actually an SD card in the TouchPad, the internal memory just gets partitioned and made into an "SD Card", so that's out.
Probably just going to have to send it back...
Duhh! I knew about the sd card and the TP, I was thinking about my cell phone.
Try calling HP's butler service. I've been lucky, the guy I talked to was knowledgeable, but I've read that you can get someone who's useless.

[FIX] Data wipe error or Can't mount /dev/block/mmcblk0p1

Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (www.goo-inside.me/gapps/gapps-ics-20120317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get...e-cm-9-20120520-NIGHTLY-vibrantmtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/showthread.php?t=1447303
...and to think that I've "lost" a Vibrant about a year ago because such tecniques had not developed yet (back then we had no CM and the modding scene was all about samsung roms).
If that works, "thanks" on behalf of all those which are in the position that I was in. If only I still had the phone, I would had probably made it working one way or another
Yea luckily for me the phone's internal died about 3 days ago.
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
ferhanmm said:
Hmm... oddly enough the internal started working again.
Click to expand...
Click to collapse
Good news about this. You are back full and completely. Can you please go to this thread and read the OP and post your findings in it?
The error came up from a phone that was boot looping that was running stock kb5 with the "stock + voodoo kb5" kernel.
I tried flashing stock jfd then ics in attempts to fix the unmountable internal SD data. After that I did receive the encryption bug but only with the initial fix that I applied. But after the second fix I applied the internal was surprisingly brought back to life so I haven't had to deal with the encryption issues yet and I hope never again lol.
Regardless, I'll run those adb commands for you and post them when I see her again. Which should be soon.
ferhanmm said:
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
Click to expand...
Click to collapse
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
McBang2023 said:
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
Click to expand...
Click to collapse
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
ferhanmm said:
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
Click to expand...
Click to collapse
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
McBang2023 said:
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
Click to expand...
Click to collapse
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
ferhanmm said:
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
Click to expand...
Click to collapse
absolutely. and thanks again
Bump for interest of knowing if anyone else recovered internal memory after doing these steps
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
accordex said:
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
Click to expand...
Click to collapse
If you can access your internal sd after flashing stock jfd, then yes your phones storage is fine.
If you flashed eugenes jk2, check storage if it lists as unavailable then yes its messed up.
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
McBang2023 said:
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
Click to expand...
Click to collapse
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
fishman0919 said:
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
Click to expand...
Click to collapse
i would be willing to try it....but the link is broken. so no valid download.
EDIT: i found a workaround. downloading and flashing now. i will post results later.
EDIT 2: after flashing, the phone does similar to if i flashed stock jfd. the only difference is it will restart after showing the vibrant splash scfeen back to the splash screen. on stock, it completely shuts down.
anybody ever try something like this with samsung tab sph-100..?
or think i could try this? what would i need to change?
I received this tab from someone over ebay and have never once been able to get past samsung boot screen.
I have the same errors in recovery mode, have tried a lot in odin but i came to believe from other xda members that there must be some internal memory / nand chip damage.
I just got an sd card in hopes i could try something with sd card.
Is this what i'm looking for?
mind, I've never worked with android before this.. noob status still.
sender said he never had any issues with it before sending, hoping to take his word for it, i think i can return it if nothing ends up working, but he's caught in hurricane at the moment, so i am willing to work on it a few more days.
wonder if somehow magnets thru shipping could have done something?
I doubt magnets messed anything up. My suggestion is go to the section here in xda for your device and ask your question there. I would also find out if the previous owner had a custom ROM?, if so which ROM. Is it rooted and does it have a custom recovery?
All will be important info to find a fix.
Sent from my SGH-T959 using xda premium
Basically what I need is to use this mod to boot my experimental builds on the external sd w/t wiping my main ROM (which would be installed to my phone). Is that possible?
So that whatever happens I could always boot back to stock (what I will have installed in my phone), with some minor tweaking through adb shell of course. It sounds doable, ain't it?

Categories

Resources