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!
Related
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!
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!
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.
I bought the original Nook Color back in Nov. 2010. I went through all the methods back in the day, when guys first started rooting the Nook and all the problems we had back then ... side loading apps ... adhoc issues ... B&N updates ect ... we got CWM recoveries and finally we got fully working froyo's and Gingerbread's. Then CM7's and the Phiredrop's.
I been through it all. I ended up giving my Nook to my son, and he loved it. I got into Android Development Cell (ROMS). I Now got my Nook back from my son. It is working, but I have forgotten a lot about how to mod it .... mainly the partition tables, and how the bootloader runs. Does it look to the eMMC first ? or the SD-Card ? Can we flash from both locations ?
Anyways ... He has it setup weird now. It has a dual boot menu, I can boot into CM7 or CM9, But it is acting up and some stuff doesn't work. He also says it can boot into Stock 1.4.2 somehow *shrug*
I have done some searching here on xda but it is a lot of OLD posts and dead links.
Could you guys help me out with a few questions ?
01) I would like to wipe EVERYTHING from eMMC abd SD-Card and start over. I know I can format the uSD and also format the eMMC, but Can I flash a SD with a CWM image and then install Stock 1.4.2 on the eMMC. Do I even need to install stock first ? What is the best method for this ?
02) Will I need to nooter my nook again at this point if I do that ?
03) Can I run CWM on the SD and run a nandroid backup to that same SD if it is a large SD-Card ? I thought I could since the bootloader looks at uSD first (but I guess it looks at the boot partition huh ? ) my son says NO you can not run CWM and have a nandroid backup on that same SD. Yes or No ?
Bottom line is this is what I’m trying to do……
01a) I could care less about stock B&N.
02a) I just want a Nook that will dual boot into CM7 and / or CM9 preferably from my 16 GIG SD-Card but it really doesn’t matter, as long as I can install app’s to the external SD-Card.
03a) I want a way to backup the entire CM7 or CM9 via CWM to my SD-Card.
NOTE: I have a (1) 16 GIG SD-Card (1) 4 GIG SD-Card and (1) 8 GIG SD-Card.
If you could help me out with any info at all on any of this, please do so. I am mostly Android literate and I have a working ADB on my win7. I just have forgotten exactly how the nook operates at the lowest level, and how the newer CM's are flashed now after a clean format
Thank you for your time and help to any of my questions.
Peace
Thibor69 said:
the partition tables, and how the bootloader runs. Does it look to the eMMC first ? or the SD-Card ? Can we flash from both locations ?
Click to expand...
Click to collapse
Partition talbes and mount points
The Nook Color boots from uSD first... then eMMC if there is no bootable uSD in the card slot.
Thibor69 said:
I have done some searching here on xda but it is a lot of OLD posts and dead links.
Could you guys help me out with a few questions ?
Click to expand...
Click to collapse
Browsing the developer forum would be very beneficial... as there are constantly new posts... so almost all of this is covered in recent posts.
Thibor69 said:
01) I would like to wipe EVERYTHING from eMMC abd SD-Card and start over. I know I can format the uSD and also format the eMMC, but Can I flash a SD with a CWM image and then install Stock 1.4.2 on the eMMC. Do I even need to install stock first ? What is the best method for this ?
Click to expand...
Click to collapse
Create a new bootable CWM recovery uSD and place one of the files from here on it.
Boot into CWM and flash the file you downloaded.
Thibor69 said:
02) Will I need to nooter my nook again at this point if I do that ?
Click to expand...
Click to collapse
Only if you want stock to be rooted... not necessary if are going to flash a different ROM to eMMC or don't care about stock root access. If you choose to root stock.... use this thread
Thibor69 said:
03) Can I run CWM on the SD and run a nandroid backup to that same SD if it is a large SD-Card ? I thought I could since the bootloader looks at uSD first (but I guess it looks at the boot partition huh ? ) my son says NO you can not run CWM and have a nandroid backup on that same SD. Yes or No ?
Click to expand...
Click to collapse
Yes.... I do that frequently.. the thing is... the nandroid backup will be of the eMMC unless you use one of the modified CWM's designed for SD installs.
Additionally... if you are going to run that from a uSD with another ROM on it... you will certainly have to adjust the boot partition on the uSD to be large enough to hold the nandroid you are creating.
Thibor69 said:
Bottom line is this is what I’m trying to do……
01a) I could care less about stock B&N.
02a) I just want a Nook that will dual boot into CM7 and / or CM9 preferably from my 16 GIG SD-Card but it really doesn’t matter, as long as I can install app’s to the external SD-Card.
03a) I want a way to backup the entire CM7 or CM9 via CWM to my SD-Card.
NOTE: I have a (1) 16 GIG SD-Card (1) 4 GIG SD-Card and (1) 8 GIG SD-Card.
If you could help me out with any info at all on any of this, please do so. I am mostly Android literate and I have a working ADB on my win7. I just have forgotten exactly how the nook operates at the lowest level, and how the newer CM's are flashed now after a clean format
Thank you for your time and help to any of my questions.
Peace
Click to expand...
Click to collapse
DizzyDen said:
Create a new bootable CWM recovery uSD and place one of the files from here on it.
Boot into CWM and flash the file you downloaded.
Click to expand...
Click to collapse
So you are saying that I can do it in this order:
1) Format eMMC ( only boot partition right ? )
2) Format uSD ( resize boot partition to a larger size for backups )
3) Create bootable CWM uSB ( any particular one you recommend ? )
4) Put one of the stocks 1.4.x files on the uSB then flash it
5) Put CM7 or CM9 on uSB and flash it
Question: Do I need to flash stock 1.4.x even tho I dont want it ? or can I skip step #4 ?
Thanks
Thibor69 said:
So you are saying that I can do it in this order:
1) Format eMMC ( only boot partition right ? )
2) Format uSD ( resize boot partition to a larger size for backups )
3) Create bootable CWM uSB ( any particular one you recommend ? )
4) Put one of the stocks 1.4.x files on the uSB then flash it
5) Put CM7 or CM9 on uSB and flash it
Question: Do I need to flash stock 1.4.x even tho I dont want it ? or can I skip step #4 ?
Thanks
Click to expand...
Click to collapse
Item 1) highly NOT recommended. There is no point to format /boot.
Item 2) if "uSD" means the external microSD card, then, no, you don't need to format it since it will be done in step 3 of your list.
Item 3) Get the CwMR version 3.2.0.1. And call it "flashable CwMR uSD", not uSB.
Item 4) If you don't want stock, leave it out as no point to touch it.
Item 5) After done step 3 above, put CM7 OR CM9 in there, the CwMR uSD, and flash.
Strongly suggestion: before doing anything. Be sure you know what you trying to do or at least, pls let us know what you try to accomplish. For example, do you try to run CM7 or CM9? Do you want to run it from the external uSD card or from eMMC? Instructions are different.
votinh said:
Item 1) highly NOT recommended. There is no point to format /boot.
Item 2) if "uSD" means the external microSD card, then, no, you don't need to format it since it will be done in step 3 of your list.
Item 3) Get the CwMR version 3.2.0.1. And call it "flashable CwMR uSD", not uSB.
Item 4) If you don't want stock, leave it out as no point to touch it.
Item 5) After done step 3 above, put CM7 OR CM9 in there, the CwMR uSD, and flash.
Strongly suggestion: before doing anything. Be sure you know what you trying to do or at least, pls let us know what you try to accomplish. For example, do you try to run CM7 or CM9? Do you want to run it from the external uSD card or from eMMC? Instructions are different.
Click to expand...
Click to collapse
Hello -
Thank you for the update info. Glad I asked first. Thank you Dizzy for your help, you have been a big help to me in the past also. Votinh thank you for your reply. Looking back at what I wrote I see many mistakes in my process. Thanks for correcting them.
Now ... as to your question Votinh. What is it I am trying to do.
First off this is what I currently have. Nook is working, but not well and just a mess in general. Sometimes it locks up or just runs at a crawl. ( I have CPU oc'd to 1200 ) I have CM7 and CM9 but can't seem to boot into CM9 anymore at all. I also have CWM v3.2.0.1 installed on my external SD-Card with a nandroid backup.
I just want to erase it all and start over : )
I want my Nook to be able to Dual Boot into CM7 and CM9. I would like both CM9 and CM7 on my 16 GiG SD-Card, BUT if that is not easy or possible then I would like CM7 on internal and CM9 on external. I dont need stock.
If all else fails ... or just to complicated I could live with just CM9 (nightlies or stable) with all APPS installed to external SD. and forget about dual boot.
Again thank you .... and please ask me any more questions you might need to help clarify my goal.
Peace
Thibor69 said:
Hello -
Thank you for the update info. Glad I asked first. Thank you Dizzy for your help, you have been a big help to me in the past also. Votinh thank you for your reply. Looking back at what I wrote I see many mistakes in my process. Thanks for correcting them.
Now ... as to your question Votinh. What is it I am trying to do.
First off this is what I currently have. Nook is working, but not well and just a mess in general. Sometimes it locks up or just runs at a crawl. ( I have CPU oc'd to 1200 ) I have CM7 and CM9 but can't seem to boot into CM9 anymore at all. I also have CWM v3.2.0.1 installed on my external SD-Card with a nandroid backup.
I just want to erase it all and start over : )
I want my Nook to be able to Dual Boot into CM7 and CM9. I would like both CM9 and CM7 on my 16 GiG SD-Card, BUT if that is not easy or possible then I would like CM7 on internal and CM9 on external. I dont need stock.
If all else fails ... or just to complicated I could live with just CM9 (nightlies or stable) with all APPS installed to external SD. and forget about dual boot.
Again thank you .... and please ask me any more questions you might need to help clarify my goal.
Peace
Click to expand...
Click to collapse
So far, everything you've asked are doable, in fact, a lot of members currently having the same system you describe.
Firstly, "I would like both CM9 and CM7 on my 16 GiG SD-Card" is called "dual-boot, it is a true dual-boot.
Go thank "racks11479" for his tremendous work
Link: http://forum.xda-developers.com/showthread.php?t=1448186
Note: both CM7 AND CM9 are on the external uSD card.
Secondly, "then I would like CM7 on internal and CM9 on external."; since your wish is granted , this is just an option for you. Yes, you can easily install CM7 in eMMC (aka internal memory) and booting CM9 off uSD as you want.
For references:
Boot CM7/CM9 off uSD, thank verygreen.
Link: http://forum.xda-developers.com/showthread.php?t=1000957
---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------
Update from my last link
http://forum.xda-developers.com/showthread.php?t=1576879
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Wait a minute. Alan Moore doesn't live in Scottsdale!
Whatever. Swamp Thing is awesome. You can live wherever you want
mateorod said:
Wait a minute. Alan Moore doesn't live in Scottsdale!
Whatever. Swamp Thing is awesome. You can live wherever you want
Click to expand...
Click to collapse
Wow ... good call brother. Not many people know the face.
Peace
Thibor69 said:
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Click to expand...
Click to collapse
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Mr72 has good instructions for getting 7.2 up and running on eMMC, http://forum.xda-developers.com/showthread.php?t=1443292
You'll want to use his directions to load the image found in mrg666's thread here, http://forum.xda-developers.com/showthread.php?t=1344873
Dalingrins would be redundant as it is already part of this build. You *will* want to run the V6 script as it is well worth it.
Once you've got that going well you should have read around enough to be able to load CM9 nightlies on an SD card. You *do* have a Sandisk card, right?
Thibor69 said:
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Click to expand...
Click to collapse
In bold: sure, but what do you try to do? Format the internal so that you can install something else on it?
I currently have CM7.2-RC1 Kang running on eMMC, it is really good.
Booting off uSD is more like for experimental, play it for a while to see if we like it or not. For trying, I recommend using uSD.
I have not spent more time on CM9 since I don't see much of the benefit of it.
Also, MisRy covered pretty well there.
MISRy said:
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Mr72 has good instructions for getting 7.2 up and running on eMMC, http://forum.xda-developers.com/showthread.php?t=1443292
You'll want to use his directions to load the image found in mrg666's thread here, http://forum.xda-developers.com/showthread.php?t=1344873
Dalingrins would be redundant as it is already part of this build. You *will* want to run the V6 script as it is well worth it.
Once you've got that going well you should have read around enough to be able to load CM9 nightlies on an SD card. You *do* have a Sandisk card, right?
Click to expand...
Click to collapse
Thanks for the info Misry. I have many sd cards and have used them all will good results. My Sandisk is only 4 gig ... so it was not going to be my first choice. I also have a Class 4 8 Gig Kinston I was thinking of using. Or a Class 10 16 Gig Patriot, which I know people dont like, but it seems to work fine in my phones ....?
Magus-
The difference in the SD card class as far as speed comes down to the size of the information we want to write. The lower classes aren't very fast with the large hunks of info, but excel with the tiny byte exchange used in the ROM. As the speed of your system will really be affected by the slow I/O rates of something like a class 10, compromise on size before class. It may be counter intuitive, but people have given up on cyanogen in general only because they had the wrong sdcard. This is especially true if you have a dual boot and are running the ROM off of the sdcard itself.
Look at the "strange results or how I learned to love cm" or something thread. Google that with xda and nook and you'll find it. That has all the info you'd want and way more.
Do another book with Eddie Campbell and we'll call it square. You know you want to.
MISRy said:
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Click to expand...
Click to collapse
Well I was testing a homemade script and I believe I did in fact format eMMC and either scrambled the boot partition or deleted it also on emmc. No mater what I do I can not get eMMC to boot. I can boot cwm from SD-card, but nothing on eMMC.
Advice ?? please be as technical as needed. I do not have Linux right now, but I do have adb on win7 and 3 sd-cards
THanks
Well, let's see what we're working with...
$ su
# fdisk -l /dev/block/mmcblk0
Post the output of the above. It'll show what partitions are left (if any) and then we can take it from there. This can be a hassle indeed, and it will require some research as I have avoided doing this myself. I am hoping your ROM partition is still intact, at least.
Anybody else who can help, please do. I may not be able to respond as often as I would like.
I was gonna suggest 8+1 to see if we can get back to square one.
http://nookdevs.com/NookColor/RestoreToStock
He's gonna need a ROM partition for that to work.
For a long time, 8 failed boots would (as a last resort) result in a working Nook for just about every problem. But, as users are getting more experienced across the board, more advanced and dangerous stuff is being attempted.
When everything goes right, it can be pretty rewarding, but when it goes wrong...well, let's just say the solutions become a lot more advanced as well.
The output of the command will let us know which partitions are erased and if any are still intact. Considering the information we have so far, I am not hopeful. If the emmc was erased and formatted...well, we'll see.
Here's what has occoured:
over-wrote the following partitions with "0":
# 0p7 = /cache
# 0p1 = /boot
# 0p5 = /system
# 0p6 = /data
Then formatted 5-7 ext4. Flashing a ROM with a blank boot partition has been done on another device many times with no issues, for some odd reason this nook responded poorly and I believe the the boot.img never copied over to 0p1.
I am not sure what all he tried but I know he tried the flashable emmc fixer, which didnt' fix it. I am actually concerned that made it worse, but that's my opinion and I don't have my hands on the device. For what ever reason he couldn't get adb working with the device. I found this thread:
http://forum.xda-developers.com/showthread.php?t=919353
And since ADB wouldn't work, I wrote a script and created a flashable zip for him so it would perform the same operation, but it stopped saying bad zip. He tested it with 7zip and there were no errors, I checked my script and I see no errors in it and yes, I used a proper program for it as well, NotePad++. He's a bit frustrated and sending it to me. I am confident that if none of the things he tried didn't completely scramble the internal partitions that I can get it working. But if anyone has any idea as to why the script would fail, let me know.
Edit: And correct me if I am wrong, but it's the lack of a kernel which caused it to respond so badly. A similar thing happened on our phone but was due to powering off with a blank boot partition (not our noob moment but someone else's), but being that it's a tegra 2 system we have Nvflash and all is easily rectified. My theory is that there's something, most likely memory, which is loaded by the kernel and is required for a recovery to run.
He tried the 8 failed boot and it did bring up something which ended with an error about no boot partition, I'll try to get the picture he showed me later, I need to run off to work right now.
... Nevermind
Волк said:
For what ever reason he couldn't get adb working with the device.
And since ADB wouldn't work...
But if anyone has any idea as to why the script would fail, let me know.
Click to expand...
Click to collapse
First, why in heaven's name would you purposely want to write zeros on the boot partition?
Second, adb was not working because there was no kernel or ramdisk on the boot partition since you had him zero it out. Adb needs both.
If he was trying to flash your zip with CWM from a bootable SD card, then the zip needs to be properly signed before CWM will flash it. You can have CWM toggle off that check, but I doubt he did that. Hence the bad zip error.
Also if he has his CM7 SD card still working, he can repair the emmc partitions using the terminal emulator from CM7. All the adb type commands can be run from there.
The boot partition probably needs to be reformated to vfat before it can accept any files from a CWM restore.
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?