This always confuses and creates a lot of anguish and anger and rage.. i've had to redo the plaster on the apartment walls seven times and replace 4 LCD screens from my violent outbursts as a result of this.
This it it:
EMMC and SD.
EMMC, sure, easy, simple - install, get rom manager, use TWRP as a tool for flashing and updating roms.
SD, single and dual-bootable, not so easy. Error messages. Update failures. Screams, tears, coffee-shop outbursts resulting in numerous police calls and once to a mental ward facility.
Question:
How do I manage between the two. I eff up the EMMC trying to update the SD, and so on. They don't make it easy, unless I'm just for some reason blindsided by this.
Rundown:
TWRP 2.2 with its touchscreen feature, love it. Cool, stylish, features, yeah. Easy got that on my EMMC.
So question question, is there anyway to get TWRP installed on my SD, or any type of usable interface that doesn't muck up and just flash something if it has update-*.zip in it standalone without gui functionality. It's annoying, and I've had numerous problems with it breaking down and having to reinstall everything or go deep into it and fix a broken sector to get it working.
There has to be a fix for this, no?
Myself (and those around me as a result of this) would greatly appreciate any input.
Thanks
echoedge said:
This always confuses and creates a lot of anguish and anger and rage.. i've had to redo the plaster on the apartment walls seven times and replace 4 LCD screens from my violent outbursts as a result of this.
This it it:
EMMC and SD.
EMMC, sure, easy, simple - install, get rom manager, use TWRP as a tool for flashing and updating roms.
SD, single and dual-bootable, not so easy. Error messages. Update failures. Screams, tears, coffee-shop outbursts resulting in numerous police calls and once to a mental ward facility.
Question:
How do I manage between the two. I eff up the EMMC trying to update the SD, and so on. They don't make it easy, unless I'm just for some reason blindsided by this.
Rundown:
TWRP 2.2 with its touchscreen feature, love it. Cool, stylish, features, yeah. Easy got that on my EMMC.
So question question, is there anyway to get TWRP installed on my SD, or any type of usable interface that doesn't muck up and just flash something if it has update-*.zip in it standalone without gui functionality. It's annoying, and I've had numerous problems with it breaking down and having to reinstall everything or go deep into it and fix a broken sector to get it working.
There has to be a fix for this, no?
Myself (and those around me as a result of this) would greatly appreciate any input.
Thanks
Click to expand...
Click to collapse
I'm not really sure what you are asking. No kind of recovery program (either CWM or TWRP) can flash roms to the verygreen SD setup (what you called single boot). They have to be installed using the copy to boot partition method. And on Racks' dual boot SD you have to use his specially modified version of CWM to flash roms there. And the roms to be flashed there have to be specially modified before flashing too.
If you try to flash any unmodified rom zip with either TWRP or CWM it will always get put on emmc. That's what the roms are hard coded to do. It makes no difference whether the recovery is on emmc or SD, it will always install the rom to emmc.
Also remember, even if you somehow get TWRP installed on your SD, whatever you tell it to do, it does it to emmc. If you say wipe system, it wipes emmc system, not SD system, and same with other functions in TWRP. The same is true using an unmodified version of CWM.
I have heard that eyeballer may be working on a modified version of TWRP that may do things to SD, but I don't think he has released it.
Look on my tips thread linked in my signature for an explanation for the difference between flashing to emmc and installing on SD. There is also an explanation of the difference between the two types of SD installations.
Related
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!
I've been tooling around with Sammy devices forever, and know my N1 pretty well EXCEPT for the whole "X-Y-Z" to flash a Sense rom. Is there a step-by-step written in layman's terms to safely try out some of these ports? Most instructions seem a bit ambiguous (I know, most N1 owners have been around since it dropped, thus no need to beat instructions to death) and I would love try some Sense-loving.
I have been around and around the Dev section here, but there seem to only be bits and pieces left in one thread or another...Forgive me in advance as Sammy and MotoGoogle are pretty easy to **** around on.
The procedure is the same for Sense/AOSP
Just read OP page and last 20 pages of thread for specific rom flashing instructions
Wiki on this Forum has a lot of how to's
But, if already rooted, just make sure you have bu's of phone and sdcard and partition card as suggested on rom OP page
Wipe ALL including system a couple times thru recovery before flashing new rom
What about the 'partitioning sd thing' I keep seeing, but no real explaination?
There are no complete easy step by step guides on everything
The wiki's are good to root, but don't cover partitioning
Most of us had to fumble through it with lots of research and googling
Are you rooted and which recovery are you using. I use Amon_Ra
http://dl.dropbox.com/u/28338566/AmonRa 2.2.1.mht
As far as partitioning I use sdformatter to format sdcard outside of phone
http://dl.dropbox.com/u/28338566/SDFormatter 2.0.mht
I set full erase and size adjustment to ON in sdformatter options
Back up card to pc first as well as backing up phone, if rooted do a nandroid back up and get apps like Titanium BackUp for app mgt from the market. Learn to use it before flashing roms. Terminal Emulator will be needed too. If using Terminal you will need this zip placed on the root of your sdcard to flash things like recoveries and kernels/hboots. Haven't done this stuff for awhile so bu, study, research and proceed at your own risk--
http://dl.dropbox.com/u/28338566/flash_image Terminal
Once you format card, put it back in phone and boot into recovery. Once there you will have a partition sdcard option. You need to follow prompts to partition to 1.5gb and 0 swap. Depending on your recovery as in Amon or Clockwork process will vary, but result the same. If Amon, you will partition as ext2 first, then go back and partition from ext2 to ext3. All these prompts are there.
If using Amon you will need Temasek's Extreme Wipe to format System--Amon doesn't have this option yet
http://dl.dropbox.com/u/28338566/Extreme-wipe.zip
If you don't wipe System with Data/Caches etc--some garbage will still be left behind when flashing between roms and can cause problems. I wipe all 3X
Don't know best Sense to try anymore, haven't flashed one for awhile. Maybe RCADS, think it has a2sd included and you don't need to flash other zips to run it. May still have glitches. First boot may take 15 minutes. If it continues to hang, pull battery. Some phones with lots of bad boot sectors don't handle these roms well--
I would read thru all of them and study up before just flashing one
Good Luck
Ken
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.
Hello everyone,
I have tried very hard not to post here for help, reading quite a few of the posted forums topics related to my issue.
I have tried this:
http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_Tab_(CDMA):_Full_Update_Guide
I have used the stable CM9 and even the latest daily (as of today) of CM10.
the issue is after I install, the window just gets stuck at the logo. CM10 seems stuck on the circular logo, looping over and over. However, with CM9, it always gives me an error "Encryption Unsucessful". i've read if i click the button "reset data", it messes up the cache. I have also seen that it then proceeds to give me an error, saying it cannot mount the /cache/(4-5 directories about recovery and logs).
I even have asked for help in the #gtab channel and had tons of help from "Insanity".
thank god for this, I've been able to go back to stock:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
I am at a point where I'm not sure what to do or what to test.
i started with cwm-5.0.2.7-p1c
and tried cm-9.1.0-p1c, cm-10-20121109-NIGHTLY-p1c, and cm-10-20121111-NIGHTLY-p1c
after installing cm9 and cm10, i do notice that cwm gets updated from 5 to 6 (i believe it was 6, i know it was a higher version and the font color was light/neon blue)
I have tried doing these steps on Windows 7 and on Mac OSX 10.8.2
Any help would be appreciated.
any help would be appreciated.
That sounds like the internal storage has been damaged. If it's indeed a hardware error, it can't be repaired by software, the chip or the motherboard would need to be replaced. A workaround would be to use external storage (an SD card) as internal storage. Recent CM10 nightlies can do this by partitioning the card, putting a file called activate_data_on_sdcard on it, and installing the CM10 nightly from recovery.
ableeker said:
That sounds like the internal storage has been damaged. If it's indeed a hardware error, it can't be repaired by software, the chip or the motherboard would need to be replaced. A workaround would be to use external storage (an SD card) as internal storage. Recent CM10 nightlies can do this by partitioning the card, putting a file called activate_data_on_sdcard on it, and installing the CM10 nightly from recovery.
Click to expand...
Click to collapse
thanks ableeker,
is there a way i can verify that the storage was damaged?
also, I'm able to restore and put EF17 on it with Odin, essentially reverting it, and it runs fine. wouldn't it run bad if the internal card was damaged?
the same problem (Encryption Unsuccessful) was faced in CM9 (search for that and you will find many), and thought to have been resolved in CM10, but apparently not. (also reported by other users)
It could lead to permanent internal storage damage.
I think while you still have good one, stick to the stock rom or any rom up to gingerbread.
I think it mostly affect p1c users, but if I am not mistaken I read one or two p1 users too, but it could be due to different cause.
priyana said:
the same problem (Encryption Unsuccessful) was faced in CM9 (search for that and you will find many), and thought to have been resolved in CM10, but apparently not. (also reported by other users)
It could lead to permanent internal storage damage.
I think while you still have good one, stick to the stock rom or any rom up to gingerbread.
I think it mostly affect p1c users, but if I am not mistaken I read one or two p1 users too, but it could be due to different cause.
Click to expand...
Click to collapse
agreed.
I've had enough trying to upgrade it. thanks all for your help! I'm over this.
THANK YOU IN ADVANCE FOR ANY HELP! I'm dead new with android and just got a Nook HD+ 32gb (groupon deal $130)
anyway, I've done a ton of reading on here and watched a bunch of youtube vids- i don't know if people use overlapping terminology that means the same things or what.. and also seems like theres a lot of opinions in the forums.
I want basically the full android experience and root access- like i said, never used any android, but i like toying around with these things. BUT i also really want a fully stable platform- don't want constant crashing or it reseting on me.
questions i have-
1)the CWM is the "program" (don't know the correct terminology) that basically gives me the access to back up and install new roms, root, etc? TWRP does the same thing- but i understand you don't use that?
2)If i have a BRAND NEW nook HD+ do i need to back it up before messing with it OR are the "stock rom" zips you provided just that?
2) with the SD card image, do i need to put a specific image on the specified sd card. i.e. 4gb SD gets a 4gb image? or is the image universal to whatever size SD card i get?
2a) What problems am i going to run into using my mac to make the SD card, if any? what program do i need to use?
4) when you back up through CWM where does it save it? to the SD card?
4a) this is where i was confused about the image, reading into some of the posts it led me to think the image file took up the entirety of the
SD card.
4b)So in the future i could just boot from the SD card and would have the option to flash the stock rom back on the HD+ if desired? and/or
go back to CM?
5) what is DUALBOOTING? and NANDROID? how do they tie into CWM and CM10. very confused about this.
6) any disadvantage to flashing the EMMC vs booting from SD card every time? I THINK i want to flash the emmc, i don't want to be tied to booting from the SD card everytime- if I'm understanding that correctly.
7)what is this "trim" lag problem? couldn't really figure out what people were talking about.
thanks a ton for any help you can give me- I'm sure you receive a lot of questions!
-Sonny
santinod15 said:
THANK YOU IN ADVANCE FOR ANY HELP! I'm dead new with android and just got a Nook HD+ 32gb (groupon deal $130)
anyway, I've done a ton of reading on here and watched a bunch of youtube vids- i don't know if people use overlapping terminology that means the same things or what.. and also seems like theres a lot of opinions in the forums.
I want basically the full android experience and root access- like i said, never used any android, but i like toying around with these things. BUT i also really want a fully stable platform- don't want constant crashing or it reseting on me.
questions i have-
1)the CWM is the "program" (don't know the correct terminology) that basically gives me the access to back up and install new roms, root, etc? TWRP does the same thing- but i understand you don't use that?
Click to expand...
Click to collapse
CWM (ClockworkMod) is a recovery program that allows you to do just what you said. TWRP is also a recovery, but uses the touch screen instead of hardware keys to control it.
2)If i have a BRAND NEW nook HD+ do i need to back it up before messing with it OR are the "stock rom" zips you provided just that?
Click to expand...
Click to collapse
You can either use the CWM backup tool to return your device to stock (including any data you have already created, like registration) or the plain stock zips I have will also return you to stock, but the way it was when you got it new before registering.
3) with the SD card image, do i need to put a specific image on the specified sd card. i.e. 4gb SD gets a 4gb image? or is the image universal to whatever size SD card i get?
3a) What problems am i going to run into using my mac to make the SD card, if any? what program do i need to use?
Click to expand...
Click to collapse
Since you have a Mac, the best way to do it is the new procedure without burning an image. Since I don't have a Mac, I don't know the exact programs to use. I think SDFormatter comes in a Mac version. And I know there are lots of mac partitioning programs to set the first partition active. And using the procedure does use all of the SD, so it is best to use a relatively small one, 2-4GB.
4) when you back up through CWM where does it save it? to the SD card?
4a) this is where i was confused about the image, reading into some of the posts it led me to think the image file took up the entirety of the
SD card.
4b)So in the future i could just boot from the SD card and would have the option to flash the stock rom back on the HD+ if desired? and/or
go back to CM?
Click to expand...
Click to collapse
It saves it either to the SD card or internal memory, you choose.
Yes it uses all of the SD if you use the new procedure. But you need that if you choose to backup to SD. A backup takes about 1.5GB.
And yes, save the SD for future use, like restoring backups or installing new ROMs.
5) what is DUALBOOTING? and NANDROID? how do they tie into CWM and CM10. very confused about this.
Click to expand...
Click to collapse
Dual booting means having one operating system on internal memory (also called emmc for Embedded MultiMedia Card) and one installed to a bootable SD. Most people that dual boot have stock on internal and CM on SD. They are separate and independent from each other.
Nandroid just means internal memory. So a nandroid backup means backing up whatever you have on internal memory.
6) any disadvantage to flashing the EMMC vs booting from SD card every time? I THINK i want to flash the emmc, i don't want to be tied to booting from the SD card everytime- if I'm understanding that correctly.
Click to expand...
Click to collapse
The only advantage to booting to CM on SD is it leaves internal memory untouched for warranty reasons. The disadvantage is it runs slower and is less stable.
7)what is this "trim" lag problem? couldn't really figure out what people were talking about.
Click to expand...
Click to collapse
LAG is a complex issue to explain. If you are used to hard drives getting fragmented and slowing down your system, LAG is similar but a different mechanism with solid state flash drives. TRIM is a process to undo what causes LAG. But some of the solid state chips in these devices have a bug and when TRIM is run, it bricks the chip, making it unusable.
thanks a ton for any help you can give me- I'm sure you receive a lot of questions!
-Sonny
Click to expand...
Click to collapse
leapinlar said:
CWM (ClockworkMod) is a recovery program that allows you to do just what you said. TWRP is also a recovery, but uses the touch screen instead of hardware keys to control it.
You can either use the CWM backup tool to return your device to stock (including any data you have already created, like registration) or the plain stock zips I have will also return you to stock, but the way it was when you got it new before registering.
Since you have a Mac, the best way to do it is the new procedure without burning an image. Since I don't have a Mac, I don't know the exact programs to use. I think SDFormatter comes in a Mac version. And I know there are lots of mac partitioning programs to set the first partition active. And using the procedure does use all of the SD, so it is best to use a relatively small one, 2-4GB.
It saves it either to the SD card or internal memory, you choose.
Yes it uses all of the SD if you use the new procedure. But you need that if you choose to backup to SD. A backup takes about 1.5GB.
And yes, save the SD for future use, like restoring backups or installing new ROMs.
Dual booting means having one operating system on internal memory (also called emmc for Embedded MultiMedia Card) and one installed to a bootable SD. Most people that dual boot have stock on internal and CM on SD. They are separate and independent from each other.
Nandroid just means internal memory. So a nandroid backup means backing up whatever you have on internal memory.
The only advantage to booting to CM on SD is it leaves internal memory untouched for warranty reasons. The disadvantage is it runs slower and is less stable.
LAG is a complex issue to explain. If you are used to hard drives getting fragmented and slowing down your system, LAG is similar but a different mechanism with solid state flash drives. TRIM is a process to undo what causes LAG. But some of the solid state chips in these devices have a bug and when TRIM is run, it bricks the chip, making it unusable.
Click to expand...
Click to collapse
THANK YOU.. so much answered for me