Related
I know this has been asked before but I am kind of stuck I need to access my old data.img as it became corrupt however I have tried unyaffs.exe but it crashes I want to find out what my other options are.
Thanks,
yonu
You could try this program....ext2explore
data.img is not a yaffs image, it's an ext image. You'll need a linux box to edit it reliably.
thanks ext2 worked great I thougt I was suppose to be using the other one.
dumb question I found the files I needed but I can't seem to find the proper location on the phone to put them back they can from the root data in the img files so where should i put them back?
I found it was looking in the wrong place
Edit I was wrong
Sorry to be a pain I fouond it I broke down and used droid explorer to upload the files
ok stupid question as I went to run the program I was putting the databases for and found out that when i deleted and copied the files back over in droidexplorer it really isn't deleting the files. Anyone know of a fix?
Thanks
I'm a pretty experienced computer person. But I am a nube with the Nook Color I received for Christmas. I bought an 8 Gigabyte Cyanogen 7 chip on eBay. Ran the system from the SD chip so I can still go back to my Nook Color Barnes & Nobel system when I want or need to. Booted right up and I was good to go. Happy! Happy!
First what I've got: Cyanogen Mid 7.1.0 Rc1-encore.
Build GRJ22
Kernal 2.6.32.9
Android version is 2.3.4
Got Market up and running, connected on my WiFi network. Enabled Blue Tooth for an external keyboard. Downloaded Null Keyboard. Still monkeying around with that. Decided to try a little overclocking. Downloaded and installed Nook Tweaks. But it says I need to update my operating system. I've tried every step suggested for creating an updated SD chip. (I want to keep the 8 Gig SD chip so I can have that to fall back on if I screw up.) I've searched, read, and experimented. But I don't seem to be able to create my own SD Chip from scratch.
Bought two blank 16 Gigabyte San Disk Class 4 chips. I have a USB based card reader/writer running off a Windows XP laptop. I've got Win32 disk imager on the laptop. I've tried downloading an update to write to the new SD chips. But there are so many variations. It seems everybody and his brother has a variety that is the latest and greatest. I've searched all over the Nook forums for two weeks. Found lots of step by step instructions. The only problem is that many of these are several months old. So some of the systems they mention are now months old.
So, here are my questions:
1. I think what I need to download is CM7 7.2. But there are some later flavors that add numbers after the 2. Can anyone suggest the best CM7 system that will support the features of the Nook Tweaks App?
2. Is there anything I must do to the SD Chip before I use Win32 disk imager to write the system onto my 16 Gig SD chip? Example do I have to format it in the Nook, or does Win 32 disk imager do that when it writes the OS and files to the chip?
3. I'm assuming I'll have to reinstall some of my programs on this updated OS. I'm OK with that. I want something stable. Nightly builds seem like extra confusion. And are there versions by some particular developers that are better than others? Example: one sticky suggested CM7.2 by mrg666.
4. Can someone explain what Mount and Unmount means for my Nook chips? I can remove my SD Chip without Unmounting. But my understanding is that I should select Unmount before I do. Do I have to Mount it again when I place the SD chip for the upgrade? Since this will be an upgrade, I don't see how I can mount it. This is yet another area of my confusion.
I'm not stupid. But I am confused. And the terminology and acronyms so many of the experienced folks use here is confusing - at least to me. Any help will be greatly appreciated.
As long as I'm asking questions. While I was in the native Nook Color OS, it upgraded from version 1.3 to 1.4. Is there some way I can save the native Nook Color Barnes & Nobel Operating System and my books to a spare SD Chip?
Thanks in advance for any help!
Bach On
bachon said:
So, here are my questions:
1. I think what I need to download is CM7 7.2. But there are some later flavors that add numbers after the 2. Can anyone suggest the best CM7 system that will support the features of the Nook Tweaks App?
2. Is there anything I must do to the SD Chip before I use Win32 disk imager to write the system onto my 16 Gig SD chip? Example do I have to format it in the Nook, or does Win 32 disk imager do that when it writes the OS and files to the chip?
3. I'm assuming I'll have to reinstall some of my programs on this updated OS. I'm OK with that. I want something stable. Nightly builds seem like extra confusion. And are there versions by some particular developers that are better than others? Example: one sticky suggested CM7.2 by mrg666.
4. Can someone explain what Mount and Unmount means for my Nook chips? I can remove my SD Chip without Unmounting. But my understanding is that I should select Unmount before I do. Do I have to Mount it again when I place the SD chip for the upgrade? Since this will be an upgrade, I don't see how I can mount it. This is yet another area of my confusion.
I'm not stupid. But I am confused. And the terminology and acronyms so many of the experienced folks use here is confusing - at least to me. Any help will be greatly appreciated.
As long as I'm asking questions. While I was in the native Nook Color OS, it upgraded from version 1.3 to 1.4. Is there some way I can save the native Nook Color Barnes & Nobel Operating System and my books to a spare SD Chip?
Click to expand...
Click to collapse
1) I believe 7.1 RC has an older kernel (maybe even .29, can't remember) that won't allow all the features of the Nook Tweaks. I'd recommend upgrading to full release 7.1 which can be found if you search around.
2) You shouldn't have to do anything, but after you write the image, you may have to expand the partitions to give you full access to the storage space. i.e. writing a 2GB image leaves 14GB unallocated space you will not be able to access until you do.
3) I haven't tried other builds, but reading up on the threads (and usually the first post) can give you an idea of what works, what doesn't, what kind of problems are being run into by users.
4) Mounting/Unmounting is essentially allowing the system to use the drive/card. I think of it as the Windows Safely Remove USB device kind of thing. The system will automatically mount the SD card when you insert it. You can mount cards, partitions, etc. Though I don't think you can unmount a Sd card while running an OS off it.
bachon said:
I'm a pretty experienced computer person. But I am a nube with the Nook Color I received for Christmas. I bought an 8 Gigabyte Cyanogen 7 chip on eBay. Ran the system from the SD chip so I can still go back to my Nook Color Barnes & Nobel system when I want or need to. Booted right up and I was good to go. Happy! Happy!
First what I've got: Cyanogen Mid 7.1.0 Rc1-encore.
Build GRJ22
Kernal 2.6.32.9
Android version is 2.3.4
Got Market up and running, connected on my WiFi network. Enabled Blue Tooth for an external keyboard. Downloaded Null Keyboard. Still monkeying around with that. Decided to try a little overclocking. Downloaded and installed Nook Tweaks. But it says I need to update my operating system. I've tried every step suggested for creating an updated SD chip. (I want to keep the 8 Gig SD chip so I can have that to fall back on if I screw up.) I've searched, read, and experimented. But I don't seem to be able to create my own SD Chip from scratch.
Bought two blank 16 Gigabyte San Disk Class 4 chips. I have a USB based card reader/writer running off a Windows XP laptop. I've got Win32 disk imager on the laptop. I've tried downloading an update to write to the new SD chips. But there are so many variations. It seems everybody and his brother has a variety that is the latest and greatest. I've searched all over the Nook forums for two weeks. Found lots of step by step instructions. The only problem is that many of these are several months old. So some of the systems they mention are now months old.
So, here are my questions:
1. I think what I need to download is CM7 7.2. But there are some later flavors that add numbers after the 2. Can anyone suggest the best CM7 system that will support the features of the Nook Tweaks App?
2. Is there anything I must do to the SD Chip before I use Win32 disk imager to write the system onto my 16 Gig SD chip? Example do I have to format it in the Nook, or does Win 32 disk imager do that when it writes the OS and files to the chip?
3. I'm assuming I'll have to reinstall some of my programs on this updated OS. I'm OK with that. I want something stable. Nightly builds seem like extra confusion. And are there versions by some particular developers that are better than others? Example: one sticky suggested CM7.2 by mrg666.
4. Can someone explain what Mount and Unmount means for my Nook chips? I can remove my SD Chip without Unmounting. But my understanding is that I should select Unmount before I do. Do I have to Mount it again when I place the SD chip for the upgrade? Since this will be an upgrade, I don't see how I can mount it. This is yet another area of my confusion.
I'm not stupid. But I am confused. And the terminology and acronyms so many of the experienced folks use here is confusing - at least to me. Any help will be greatly appreciated.
As long as I'm asking questions. While I was in the native Nook Color OS, it upgraded from version 1.3 to 1.4. Is there some way I can save the native Nook Color Barnes & Nobel Operating System and my books to a spare SD Chip?
Thanks in advance for any help!
Bach On
Click to expand...
Click to collapse
1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB .
3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
Useful utilities are SDformatter from Sandisk site, Easeus Partition Manager, and Win32Diskimager.exe.
Hope this helps.
Leapinlar just posted an expanded Generic SD Image that does away with manually expanding the boot partition - I believe it's around 200mb... I just tried it and it works great! You can find it here: http://d01.megashares.com/index.php?d01=NcUqquQ
Please take time to thank Leapinlar (and Verygreen) - he worked hard on this!
Downloading it now. Many Thanks to you for the help!
If we're being honest, the only thing you did wrong is spend money on a pre-imaged sdcard. The people pumping those out are profiteers fleecing the underinformed, on the backs of the generous.
Nothing on you, the process can seem daunting, and the ready-to-run sdcards seem like an easier way. It just rankles me that people who had no hand in the work are always the ones selling these. Everything anybody could need is available for free right here.
Progress - but still some questions.
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
How can I (and others) know which ones are compatible with one another?
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
I can understand your feelings on this. But the truth is that I did not know how to do it. I agree that the information is here. But frankly, it is not in an easy to understand form. This is a huge website. And there is so much information that it is daunting to find the right steps.
I could probably fix my car when it has a problem. There are lots of resources on the Internet to tell me what to do. But I usually take it to a mechanic who is experienced at doing the needed repairs.
I wanted to know what the Android Operating system was like on my Nook Color. And I paid $18.00 for an 8 Gig Sani SD chip with the operating system. I was impressed enough with this operating system that I now want to know more. And I don't feel fleeced.
Maybe they are making a few bucks on the efforts of others. But they helped ease me into the process much quicker than I could have done it on my own. And now I am wanting to learn to do it myself. I only hope that I can help others as I learn.
Take care!
BO
bachon said:
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
How can I (and others) know which ones are compatible with one another?
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
Click to expand...
Click to collapse
You'll need to try again ! A couple observations:
1. Watch the process evolve on the screen of your Nook. You may see a clue as to why your build did not work.
2. use the Google Apps file from my earlier post,"gapps-gb-20110828-signed.zip"
available at the bottom of this page, http://wiki.cyanogenmod.com/index.php?title=Latest_Version .
3. If you don't have an CM ...zip file beginning with "update-" , you will be told , on the screen, that it is missing and must be renamed.
4. Most importantly, watch the screen as the process unfolds. It will be educational and if problems persist, may yield some clues to the problem.
Breaking this down for you and trying to answer/explain your questions:
bachon said:
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Click to expand...
Click to collapse
Generic-sdcard.... is a disk image file... it includes the script for partitioning the uSD (if needed), formatting the partitions, installing ROM and gapps.
bachon said:
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Click to expand...
Click to collapse
Correct... the sd image will have a single partition (root partition is labeled "boot") that is ~114 MB... ROMs are getting larger... resizing it now will save headache later.
bachon said:
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Click to expand...
Click to collapse
This rename is due to the installer/updater script looking for specific naming at the beginning of the filename (update-* or cm_encore_full*)... note the * is an OS wildcard meaning anything. After any ROMs have been installed, the installer/updater looks for a file named gapps-gb-* for processng.
bachon said:
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
Click to expand...
Click to collapse
There are various ROMs and variations of them, yes. Some name them differently to avoid confusion with standard "official" ROMs. It would be easier for uSD installers if the maintained the "update-" naming convention.
bachon said:
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Click to expand...
Click to collapse
Yes... copy/paste... do NOT extract (that's what the installer/updater does)
bachon said:
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Click to expand...
Click to collapse
See the answer above regarding what the installer/updater script expects for the naming.
bachon said:
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Click to expand...
Click to collapse
See above.
bachon said:
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
Click to expand...
Click to collapse
You do NOT need to rename gapps and it is NOT recommended you do so... the installer/updater will install any and all cm_full_* and update-* files... then process gapps. I personally recommend a 2 step process for this... install the ROM without gapps on the drive... then place gapps on the drive and boot into recovery again for the install of that... has just fixed issues in the past this way.
bachon said:
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Click to expand...
Click to collapse
the number is referencing the date, some are YYYYMMDD some are MMDDYYYY.
bachon said:
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
Click to expand...
Click to collapse
There is no gapps installer that enlarges the boot partition... they are referencing an updated uSD image file with a larger boot partition due to ICS builds... also note that ICS builds require different gapps than the CM7 variants and become even more confusing... for CM7 stick with the gapps that is on the CM7 wiki pages.
bachon said:
How can I (and others) know which ones are compatible with one another?
Click to expand...
Click to collapse
This gets daunting... answer above.
bachon said:
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
Click to expand...
Click to collapse
See answer above regarding naming conventions and recommendation pertaining one step install (with both files on SD) v. two step (ROM first then gapps seperately)
bachon said:
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Click to expand...
Click to collapse
Once the installer/updater installs a zip file... it deletes it... also note... the first boot after an install take a VERY LONG TIME
bachon said:
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
Click to expand...
Click to collapse
This would be very good to do... hopefully I have provided enough information to get you started.
Success.
I’m going to post this under my original post so nubes can find it more quickly. Many won’t take time to drill down into the thread. It would still be helpful of some of the experts would address some of the questions asked in this long winded report. [/B]
I discovered some mistakes in my understanding in the Question and Answer part of this LONG post. I’m going to try to correct it.
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Self Correction: NO. The Generic–sdcard-v1.3.img only creates the Boot/Root partition and writes the files needed to make the sdcard bootable in the Nook Color.
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Self Correction: there is a typo in the previous statement. The encore file should be renamed “update-cm-72-Mirage-0126012.zip”. I had an underscore symbol instead of a dash. I also had “encore” as the word after update. I believe it needs to begin with “update-cm”.
And one more thing. Some operating systems omit the .zip suffix on the filename. The Nook Color seems unable to recognize the archive without .ZIP at the end of the archive name.
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
Self Correction: Still not sure about the compatibility issues. But as with the other Zip archive, the archive name must be renamed to read “update-gapps-bg-20110828-signed zip”. (The quotes and final period are not used in the name.) Again, the .ZIP suffix must be on the end of the archive name.
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
How can I (and others) know which ones are compatible with one another?
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
Final Remarks on the post: after correcting the typos, the update took place and the Nook Color shut itself down.
There were then four Active Partitions on the sdcard. So one or more of the archives created the 3 extra partitions that weren’t there.
The Nook Color then booted up and I was allowed to setup Market, Wifi, etc. I will have to reinstall applications I had working before. No problem there.
BO
You got it - congrats!
If you want to try some of the CM9 nightlies (lots of fun on an extra card) - I've had good success by doing everything together... SP2, CM9 nightly and gapps together in one install and boot... and it does get you to Android Setup right off the bat!
see http://forum.xda-developers.com/showthread.php?t=1444943 for more info. Sam has also included the new expanded Generic SD image there.
Nobody has answered my question about compatibility between the encore zip and the gapps zip. Not sure, yet, which does what and if there are issues that must be understood in choosing these. I did get it done, but I want to be able to explain it to others.
Thanks for all the help, folks!
BO
Sam Adams said:
Leapinlar just posted an expanded Generic SD Image that does away with manually expanding the boot partition - I believe it's around 200mb... I just tried it and it works great! You can find it here: http://d01.megashares.com/index.php?d01=NcUqquQ
Please take time to thank Leapinlar (and Verygreen) - he worked hard on this!
Click to expand...
Click to collapse
I saw that posted in the ICS thread. Does it work for CM 7, as well? I can't see why not, but figured I'd ask. Thanks.
If I remember correctly I used it for making a CM7 card. Works fine because it's just for getting the card ready for whatever you're going to put on it and use.
I'm old though so my memory fails often. :what:
Sent from my NookColor running CM7.2-RC0 MiRaGe - KANG 02012012 using TapaTalk
bachon said:
Nobody has answered my question about compatibility between the encore zip and the gapps zip. Not sure, yet, which does what and if there are issues that must be understood in choosing these. I did get it done, but I want to be able to explain it to others.
Thanks for all the help, folks!
BO
Click to expand...
Click to collapse
You need to read my previous and long post in this thread answering your questions
bachon said:
Nobody has answered my question about compatibility between the encore zip and the gapps zip. Not sure, yet, which does what and if there are issues that must be understood in choosing these. I did get it done, but I want to be able to explain it to others.
Thanks for all the help, folks!
BO
Click to expand...
Click to collapse
There is no direct compatibility issue here other than getting a good base set appropriate for either CM7 or ICS/CM9.
The ROM is the ROM and will run quite happily without gapps. Think of it as your basic Windows OS.
Gapps is a set of Google applications. They are not part of the base OS but are quite important because they give you some basic applications like Calendars and eMail. Most important of all they give a Vending application which allows you to access the Google apps market. Once there you can load and update other apps including the Google apps themselves.
For CM7 you can start with the 20110828 labelled version.
To emphasise the independence of the ROM and the gapps many CM7 install instructions recommended installing the ROM first and getting it going and the wifi set up before even installing gapps.
For ICS/CM9 there are several versions available because they come pre-loaded with tablet/ICS versions of the Google apps which are more appropriate than than the CM7 ones. Quite a few of the alpha CM9 ROM builds point to a good starting gapps. For example, this link is to one of the popular ICS and includes a link to a decent starting gapps.
I did read your very informative post. I've started to prepare an introductory post for possible submission. I'd like to run this by you for your input, if you don't mind.
I'm going to provide you with an e-mail address: [email protected]
If you send a brief e-mail to that address then I send my draft. If you don't want to fool with it, no hard feelings.
Thanks!
BO
No problem at all... just send it to [email protected]
Can't get cm7 to boot from sd card
This is the closest thread I can find to my problem; please excuse me if some of my language is not accurate.
Wrote the generic-sdcard-v1.3ICS-large.img to a 16 gig sd card with win32diskimager.exe. . Copied cm-7.2.0-encore.zip and the gapps zip file to the sd card and renamed the cm file to update-cm-7.20encore.zip. Ejected the sd card, put into my nook. Nook booted from the card and successfully ran through the installation of the android system and gapps and shut down. Cannot successfully boot from the sd disk. It will show the cyanogen flash screen and "loading" and then go to a blank screen. It will sometimes go to the screen with the skateboarding robot with the arrow going around in a circle. I have tried the process many times and get the same result. I was successful once in getting the android system to boot and thought aha, finally there. Computer would not recognise the nook so played with that - and decided I need to reflash the sd card. No success since then - getting very frustrated.
Thanks for any help.
JPB
Need some help here:
I need to delete some of the backups I made with CWM recovery. I already have them backed up onto my PC, but need to delete them to make some room. For some reason I cant.
Ive tried root explorer, es file explorer, and my PC. Im unable to change the permissions of the files, and if you look at the pics I attached youll see they have some strange permissions, but I cant change them.
I am able to move the files anywhere else in the sd card folder, rename them, but no matter what I cant delete them. And when I try from my PC it shows them disappear, but they are actually still there.
If there is a way to format the sd card folder I will, but thats not an option in the settings, or CWM. Can someone please help me out here? This is really frustrating me. Thanks
No issues here when I delete backups using ROM Toolbox.
UnknownFearNG said:
No issues here when I delete backups using ROM Toolbox.
Click to expand...
Click to collapse
I tried through ROM Toolbox and still couldnt delete them.
Gam3r 4 Life said:
I tried through ROM Toolbox and still couldnt delete them.
Click to expand...
Click to collapse
Same, tried with multiple apps too.
I posted this in the other thread, but figured I would do so here in case other people needed the "fix".
Ok, so some good news and some bad news.
The good news is, I was able to put together a flashable zip that WILL DELETE the entire CWM backup directory from the sdcard. It is available here:
http://core.routed.com/CWM_Backup_Wipe.zip
You simply need to flash it via CWM. Easy peasy. I confirmed that the directory/files were all removed, AND the storage space is now available for other files (I checked df before and after).
The bad news is, before attempting to delete the directory, I first tried changing the permissions (recursively) to see if that was a better "fix" for this problem. Unfortunately, even with the directory 777 and the files 666, I still could not manually delete them through the system. Which means, whatever bug is causing this problem is much more severe than a file/directory permission thing.
In any case, until the CWM developer can figure out a way to fix this bug, at least we have a way to manually remove the backups and get our storage space back.
The script in the zip is very simple. It just does a recursive delete on /sdcard/clockworkmod/backup.
Enjoy!
phonic said:
I posted this in the other thread, but figured I would do so here in case other people needed the "fix".
Ok, so some good news and some bad news.
The good news is, I was able to put together a flashable zip that WILL DELETE the entire CWM backup directory from the sdcard. It is available here:
http://core.routed.com/CWM_Backup_Wipe.zip
You simply need to flash it via CWM. Easy peasy. I confirmed that the directory/files were all removed, AND the storage space is now available for other files (I checked df before and after).
The bad news is, before attempting to delete the directory, I first tried changing the permissions (recursively) to see if that was a better "fix" for this problem. Unfortunately, even with the directory 777 and the files 666, I still could not manually delete them through the system. Which means, whatever bug is causing this problem is much more severe than a file/directory permission thing.
In any case, until the CWM developer can figure out a way to fix this bug, at least we have a way to manually remove the backups and get our storage space back.
The script in the zip is very simple. It just does a recursive delete on /sdcard/clockworkmod/backup.
Enjoy!
Click to expand...
Click to collapse
Just saying thanks for this, I hope they figure a fix out soon. Flash worked perfectly, for some storage space back. :good:
Hey everyone, just wanted to share these flashable .zip's with any whom have been affected by the Encryption Unsuccessful Error. If you've been affected, then you certainly know how monotonous of a task it is to edit the vold.fstab every time you install a new ROM. Well, with the recent explosion of Jellybean ROMs, I realized just how annoying it can be. Jumping from ROM to ROM became a chore, and after finally deciding enough was enough, I put together these flashable .zips for all to enjoy. Now switching ROMs is a seamless task! Even with the EU error!
Simply download and flash the appropriate .zip, and it'll switch out your old vold.fstab with a modified one. This can be done directly after installing a new ROM. Links found below:
View attachment vold.fstab-fix-flashable-JB.zip
View attachment vold.fstab-fix-flashable-ICS.zip
Do you think these will work with Captivate? Thanks!
Yes it should work with captivate
Sent from my SGH-T959 using xda app-developers app
fb767 said:
Do you think these will work with Captivate? Thanks!
Click to expand...
Click to collapse
I can guarantee you, without a doubt, that both of the above flashables work for both the Vibrant and the Captivate.
I even double checked, just to be certain.
Sent from my SGH-T959
thumbs up
unbelieveable i have been trying a long time to fix this problem. excellent work really!
Awesome!!!
N00B_IN_N33D said:
Simply download and flash the appropriate .zip, and it'll switch out your old vold.fstab with a modified one. This can be done directly after installing a new ROM. Links found below:
View attachment 1782094
View attachment 1782095
Click to expand...
Click to collapse
Dude! You are my hero:laugh:!!! I have been, for 2 weeks, trying to set this tricky Vold.fstab file with no sucess, at all (after the internal SD crashed).
Your .zip worked perfectly on my CM10.. Now i`m back to mobile multimedia :good:
Next step is to fix my GPS Hardware (but it can wait)
N00B_IN_N33D said:
Hey everyone, just wanted to share these flashable .zip's with any whom have been affected by the Encryption Unsuccessful Error. If you've been affected, then you certainly know how monotonous of a task it is to edit the vold.fstab every time you install a new ROM. Well, with the recent explosion of Jellybean ROMs, I realized just how annoying it can be. Jumping from ROM to ROM became a chore, and after finally deciding enough was enough, I put together these flashable .zips for all to enjoy. Now switching ROMs is a seamless task! Even with the EU error!
Simply download and flash the appropriate .zip, and it'll switch out your old vold.fstab with a modified one. This can be done directly after installing a new ROM. Links found below:
View attachment 1782094
View attachment 1782095
Click to expand...
Click to collapse
I'm sorry, but this did not work for me. I have a Galaxy S3 which I rooted and flashed with cyanogenmod, nightly builds. So it had Jelly Bean on it. Last week suddenly it got hit with this encryption unsuccessful bug!
My phone is completely useless now, unless I can find some way to fix this.
I don't even know how to find out how the internal devices are named. However, in clockworkmod I saw this error:
mounting /dev/block/mmcblk0p12 on /data: I/O error
So apparantly the internal storage is on /dev/block/mmcblk0, with at least 12 partitions.
Is there any way to find out what the right device file names would be for the galaxy s3, for the external sdcard?
Is there someone who could prepare the right vold.fstab to put android on the external sdcard for the s3, and make a flashable zip file for it?
perpetualrabbit said:
I'm sorry, but this did not work for me. I have a Galaxy S3 which I rooted and flashed with cyanogenmod, nightly builds. So it had Jelly Bean on it. Last week suddenly it got hit with this encryption unsuccessful bug!
My phone is completely useless now, unless I can find some way to fix this.
I don't even know how to find out how the internal devices are named. However, in clockworkmod I saw this error:
mounting /dev/block/mmcblk0p12 on /data: I/O error
So apparantly the internal storage is on /dev/block/mmcblk0, with at least 12 partitions.
Is there any way to find out what the right device file names would be for the galaxy s3, for the external sdcard?
Is there someone who could prepare the right vold.fstab to put android on the external sdcard for the s3, and make a flashable zip file for it?
Click to expand...
Click to collapse
May be this will help.....
http://forum.xda-developers.com/showthread.php?t=2439367
Sent from my SGH-T999 using Tapatalk 2
N00B_IN_N33D said:
Hey everyone, just wanted to share these flashable .zip's with any whom have been affected by the Encryption Unsuccessful Error. If you've been affected, then you certainly know how monotonous of a task it is to edit the vold.fstab every time you install a new ROM. Well, with the recent explosion of Jellybean ROMs, I realized just how annoying it can be. Jumping from ROM to ROM became a chore, and after finally deciding enough was enough, I put together these flashable .zips for all to enjoy. Now switching ROMs is a seamless task! Even with the EU error!
Simply download and flash the appropriate .zip, and it'll switch out your old vold.fstab with a modified one. This can be done directly after installing a new ROM. Links found below:
View attachment 1782094
View attachment 1782095
Click to expand...
Click to collapse
what are the benifits are doing this?
we have to flash it frm recovery mode...right?
thanks a ton
Feiteng H9500 - vold.fstab !!!HELP!!!
Hi, I beg you for help!
I needed to replace my phone's internal SD card with external SD card, I did everything according to the instructions of the net. Through root explorer I found a file vold.fstab (system / etc / vold.fstab) and replaced it with a downloaded file vold.fstab. After rebooting everything should be ok, but unfortunately it was not - now I have only the phone memory. The original file I unfortunately accidentally backed up to the internal SD which I can not get I do not know what to do, without fixing this problem, the phone useless. I would very much appreciate if I'm with someone of you can help. Example, if a anyone have the same phone (Feiteng H9500) and could you send me the file vold.fstab. Thanks
help?
do you have a flashable vold.fstab for my kata fish tab 3> running jb 4.2
flashable via stock recovery. BADLY NEED IT! thank you!
View attachment 2701829
View attachment 2701830
View attachment 2701831
my phone is replica samsung gti-9190 and i deleted my vold.fstab and dont backup him. and now, my sdcard dont work. i need help. i paste some files and nothing... someone help!!!!!!!
Help !!!!
Hey can anybody modify my vold.fstab file for sd card swapping please. I have tried many times with many methods but unsuccessful my mobile is Panasonic T21.
Thanks in advance
help me creating flashable vold.fstab
plls make this flashable to my gingerbread phone. i use via stock recovery only
First off, HI ALL. Awesome community!! OK, so I am having the same can't write to SD issue as everyone else. I am rooted with TowelRoot and on KK 4.4.2. I have installed a few of the different "SD FIX" apps and upon looking at the platform.xml file the proper strings are there but I still cant write to or delete from EXT-SD. I have tried ES File Explorer and Root Explorer ( Donate vrs). Another thing that I noticed is that all the tutorials I have read say that there needs to be a space between the " /> at the end. My platform.xml doesnt have that, in fact, none of the strings have the space between the " and />. I tried to do it manually and got the massive force close of a lot of apps. Reverting back to the original didnt help. I had to do a factory reset. That stopped the FC issue but the paltform.xml file is the same with the added string and the nonexistant spaces. Any help would be greatly appreciated. Thanks in advance!!
what filesystem do you have on your card?
Either he has exFAT or FAT32. Can you tell us your exact device model? What ROM are you on?
Thanks for the reply. Model number is N900V and I'm on stock Rom rooted.
Considering that your platform.xml file is still stock, you might want to try this app: https://play.google.com/store/apps/details?id=nextapp.sdfix
This app will automatically detect whether you need the fix or not. If you do need it, it'll do it for you.
Gesendet von meinem SM-N9005 mit Tapatalk
I DL and ran app. Says not needed. Does anyone have the original file so I can start this process over? Or will that bork something? I'm a noob but I am a little tech savy. One anomaly that doesn't make sense to me is that in my xml file, none of the strings have a space between the " and />. Does that make a difference? I'm confused. lol
harmageddon4 said:
I DL and ran app. Says not needed. Does anyone have the original file so I can start this process over? Or will that bork something? I'm a noob but I am a little tech savy. One anomaly that doesn't make sense to me is that in my xml file, none of the strings have a space between the " and />. Does that make a difference? I'm confused. lol
Click to expand...
Click to collapse
Does it make a difference? ...make a backup of your platform.xml. Then put space in between " and >, save and reboot.
Sent from my SM-N9005 using Tapatalk
The whole xml is like that with no spaces. I originally used an SDFix app to do it. Never looked at it. It worked for a brief time then either I rebooted or something and it stopped. I added the space manually but noticed none of the strings had a space. Are they all supposed to have them or just to added/modified string? I did factory reset because I was getting the FC issue but that didn't reset the xml. Does anyone have the original so I can start the process over?
Try this. It already has the fix implemented. If everything else fails, you can still flash a stock rom and use the SD Fix app I posted before.
https://docs.google.com/file/d/0B9Yi7IW9DXQsdVF0aGl0Z3lJbGc/edit?usp=docslist_api
OK. I renamed the file to paltform.xml and renamed mine to bak. Moved it to the folder and did a reboot. So far so good, no FC. Upon using Root Explorer I still get the failed operation toast when trying to delete a file from EXT SD. If noone else has an idea I guess I will just have to flash a rom and try that. I'm going to del and reinstall Root Explorer and see if that does anything. I'll keep you posted. Thanks again for all the help.
OK so I dont know all what was messed up but here is what all I did. I went in to del the Root Explorer app and found that I had converted it to a sys app with TiBu. I undid that process, uninstall and reinstall. That didnt work, so I stuck SD in my puter and backed up files and then stuck card back into phone, robooted into recovery and did a wipe of the SD. Then I put a few test files back onto the card mounted by USB cable) and tried to make folder and del a diff file and it all seemed to work so all is good so far. As I am typing this I tried something else I couldnt do which was instll the XDA app. It kept saying something like it wouldnt write to the ext sd card. Well. I just installed it with no issues. Hooray!!!:laugh: So I dont really know what the issue was but it all seems to be going fine now. A BIG thank you to all that helped me in this. And Nitrous, I clicked the THANKS button on yours!! :good: