Related
Hi, i have ShubCrafts android rom from early august currently on my HD2 and i want to change over to darkstone HD2Froyo V2.1.
I wanted to know if i backed up my apps using titanium backup will it keep all my data from the apps? furthermore can i backup my personal information - sms, contacts, and then restore them in darkstone's rom without any problems.
lastly on the root of my sdcard i have several folders from android apps, Grooveshark, Kindle, Espn score center etc and i wanted to know if i should reformat my sdcard and then place a single android folder on there with the darkstone files, or can i just rename/delete the shubCraft android folder and then just replace it with darkstone's and then run android.
oh one last thing, i wanted to ask how do i go about adding a 1GB data image, i will be trying to use this file - 1GB data.img v1.1 for DarkStone's Froyo v1! - and hopefully it is compatible. Will i just have to boot android for the first time let it create the data image and then replace it with the 1GB file i have downloaded, directly in android or boot back to winmo and then copy/paste it into the android folder.
So sorry for the multitude of questions being asked, any help appreciated.
Arigato Gozaimasu
I am also interested to see if this can be done. I just got a larger MicroSD card and I don't want to have to start from scratch.
Have you tried posting in the shubcraft build thread?
can anyone help us.... please
Hmmm. well I used this guide:
http://forum.xda-developers.com/showthread.php?t=741383
However make sure you read mstrk242 post on the 2nd page:
mstrk242 said:
I think some of the confusion on the linux side is resize2fs -p (size) is for block size not bytes. So 512000 is actually 2gb. If you do 256000 it worked for me my data.img was 4 block size. If you are using the build I am (mattc 1.4rc) this will work. I suggest copying the data.img to your hd and doing it there so you cant mess up the original. I also found that my build doesnt seem to like a bigger file than 1gb, but its the only one ive tested this on.
Click to expand...
Click to collapse
Only problem with this method is that you need linux (you could just use a live cd) and you kinda need to know how to start/use the terminal (which is a bit like cmd/command prompt on windows). But I've found this guide quite straight forward.
hey is anyone able to help, please i would greatly appreciate any answers to my problems.
thank you
ichigo786 said:
Hi, i have ShubCrafts android rom from early august currently on my HD2 and i want to change over to darkstone HD2Froyo V2.1.
I wanted to know if i backed up my apps using titanium backup will it keep all my data from the apps? furthermore can i backup my personal information - sms, contacts, and then restore them in darkstone's rom without any problems.
lastly on the root of my sdcard i have several folders from android apps, Grooveshark, Kindle, Espn score center etc and i wanted to know if i should reformat my sdcard and then place a single android folder on there with the darkstone files, or can i just rename/delete the shubCraft android folder and then just replace it with darkstone's and then run android.
oh one last thing, i wanted to ask how do i go about adding a 1GB data image, i will be trying to use this file - 1GB data.img v1.1 for DarkStone's Froyo v1! - and hopefully it is compatible. Will i just have to boot android for the first time let it create the data image and then replace it with the 1GB file i have downloaded, directly in android or boot back to winmo and then copy/paste it into the android folder.
So sorry for the multitude of questions being asked, any help appreciated.
Arigato Gozaimasu
Click to expand...
Click to collapse
Hi,
I have frequently switched between shubcraft and Froyostone so might be able to help. I use Titanium back up.
1. Backup your current build using titanium backup (free on android market)
2. Download and extract your new build. What I also do is download the apk files (from www.freewarelovers.com) of a file manager such as Estrongs as well as Titanium backup and copy them into the 'AndroidApps' folder contained within the new build to be installed. This way they install on first boot and avoids me having to connect to market for their installation.
3. Go to your SD card and remove all your current native android files and folders. Leave folders that belong to your installed apps such as grooveshack, espn etc.
4. Copy your new build onto your SD card and boot.
5. After 1st boot, reboot again by pressing the power button.
6. Work though initial android set up
7. Go to settings>applications> tap 'unknown sources' > ok
8. Open your installed titanium back up. Tap 'backup/restore', Press windows hardkey button, select 'batch'. Scroll down on the list and tap 'restore missing apps + data'.
9. After installation, reboot device
10. Enjoy!!
NB: Froyostone v2. comes with 1GB data already!
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
Hey guys.
First of all, sorry if this has been asked before. I googled a lot and searched here and couldn't find this particular problem.
My Nexus 4 is running stock 4.2. Unlocked bootloader, rooted and running ClockworkMod 6.0.1.9. Everything worked perfectly. My only problem right now is, after making a nandroid backup, I cannot see the clockworkmod folder anywhere on the phone when browsing either in windows or with ES File Explorer. I think by now I looked everywhere. Everything else in this regard seems to work fine, I can copy files, the other folders are all correct etc. I can also see and delete/restore the backup in CWM recovery. All I want is to see the folder to get it off the phone. Any ideas?
Thanks in advance.
You can find it in mnt/shell/emulated it is protected so you will need a file explorer that can give you root access. I use ES File Explorer.
Found it. Thank you very much.
Its also in /data/media/clockworkmod for whatever reason, hope this gets fixed soon.
Is there any way to copy those CWM backup folders to your computer? I tried to use Root Explorer to move the backup folders to the main sdcard/0 folder but I still cannot see it when I move the file Am I doing something wrong or is it not possible to move it to the sdcard/0?
Yeah I'm also still not too sure how to get it off the phone easily.
Chill4xed said:
Yeah I'm also still not too sure how to get it off the phone easily.
Click to expand...
Click to collapse
easiest way would probably be to just use the toolkit, unless you're opposed to such things.
Is this why ROM manager can't delte my backups? It seems them but I get an error saying "there was an error deleting your backup"
Edit: new update fixes this issue with ROM manager
man we need to get it move to a pc. i'd like to save some space since its our phone have maximum 12.9gb at our disposal.
btw, i tried Root Browser Lite to move it on sdcard area... operation failed
I had the same problem. My internal SD card just kept getting fuller and fuller with ClockwordMod. And, when I tried to copy the files from /mnt/shell/emulated/clockwork to my comp, and copy them back to the SD card to try and Restore, I ended up with corrupted files.
So, rather than fight it, I decided to wait until Clockwordmod recovery got its storage/mount point issues straightened out, and moved to the TWRP side of things. That has been seamless (once I got used to it).
I hope that they soon figure out the Clockwordmod issues; I liked having ROM Manager installed on past phones.
Btw, as an aside that is a little related, why, pray tell, are there so many mount points for the SD card? It's just weird.
just navigate the clockwordmod folder in your phone and copy it to the root of the internal memory.. connect the phone via usb into the computer and copy it
BY FAR, the easiest way is:
Chill4xed said:
My Nexus 4 is running stock 4.2. Unlocked bootloader, rooted and running ClockworkMod 6.0.1.9. Everything worked perfectly. My only problem right now is, after making a nandroid backup, I cannot see the clockworkmod folder anywhere on the phone when browsing either in windows or with ES File Explorer. I think by now I looked everywhere. Everything else in this regard seems to work fine, I can copy files, the other folders are all correct etc. I can also see and delete/restore the backup in CWM recovery. All I want is to see the folder to get it off the phone. Any ideas?
Click to expand...
Click to collapse
BY FAR the easiest way: in ROM Manager, Manage and Restore Backups>Download Backups>Open your desktop browser on the address informed by ROM Manager to download your backup.
Thanks to everyone, going to the directories works and the rom manager app is aware of the new cwm backup folder.
Hi. How to change roms in NativeSD Multiboot? When I change rom it says I have to reboot, I reboot and I still see the first rom :/ Why? What should I do?
which version of native SD Multiboot do you have & how many naiveSD Roms installed?
when you press switch rom, choose the next ROM > reboot is on the upper left corner of ver 10
I have apk version 9.0, CLK 1.5.1.6 (from kokotas) and 2 roms installed (both NativeSD). I do have reboot option in menu, but it only reboots active rom...
All right, got it. Just had to flash sboot. I've thought I have to flash it once ever so it adds sboot, but I have to flash it with each rom...
EDIT
No, still the same, I had thought if it booted after install then it works, but switching doesn't work...
Anyone knows?
Are you sure you have your NativeSD set up correctly in the boot loader (I'm using MAGLDR, so I can't say how this is done for CLK)?
You should have the "AD SD Dir" (the directory that the boot loader will boot from) set to "NativeSD", and not some subdirectory in there.
Apologies if this is irrelevant for CLK; as said, I'm not very familiar with that bootloader.
I know what is wrong. But I don't know why. When I press switch rom, new rom's initrd.gz and zimage goes to NativeSD folder on SDCard. Then app tries to flash sboot, but it doesn't manage. I have to flash it manually, and it works then.
Connect your hd2 to pc .. navigate to native sd folder..
You should see rom folders and ..two files zimage init.gz (kind of something i dnt remember the exact name)
Now which ever rom you want to select.. navigate to the folder..copy the two files (init.gz and zimage) and replace it in the main native sd folder .. simple and reboot.. yhis is manual changing of native sd rom
Sent from my HTC One X with Beats Audio using Tapatalk 2
luciferps said:
Connect your hd2 to pc .. navigate to native sd folder..
You should see rom folders and ..two files zimage init.gz (kind of something i dnt remember the exact name)
Now which ever rom you want to select.. navigate to the folder..copy the two files (init.gz and zimage) and replace it in the main native sd folder .. simple and reboot.. yhis is manual changing of native sd rom
Sent from my HTC One X with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
You have forgotten about flashing sboot_v2.zip after that
I didnt flash anything after that lol
Sent from my HTC One X with Beats Audio using Tapatalk 2
So, I noticed that apparently I was running low on space on my 16GB model and was wondering what the reason for that might be since I haven't put that many files on my phone.
Found out that my Nexus writes every file i put on it twice, one in /storage/emulated/0 and one in /storage/emulated/legacy.
After a little google searchI found out that this seems to be caused by the multiple user feature of 4.2 and apparently the old clockworkmod recovery that I was running.
Question is: how do I get it back to write in only one directory (I suppose /0 is supposed to be the main one?)
Running latest TWRP now, btw...
Apfelschale said:
So, I noticed that apparently I was running low on space on my 16GB model and was wondering what the reason for that might be since I haven't put that many files on my phone.
Found out that my Nexus writes every file i put on it twice, one in /storage/emulated/0 and one in /storage/emulated/legacy.
After a little google searchI found out that this seems to be caused by the multiple user feature of 4.2 and apparently the old clockworkmod recovery that I was running.
Question is: how do I get it back to write in only one directory (I suppose /0 is supposed to be the main one?)
Running latest TWRP now, btw...
Click to expand...
Click to collapse
I believe those 2 paths that you mentioned point to a single physical location. I don't remember which one but one of them is just a virtual path. So your files are not written twice.
To find out what's using up your space, use an app like DiskUsage. More often than not, it's files in your Download folder, your Nandroid backups, and/or other recovery flashable zips.
Ah, I see. You're right, the clockwork backups took all the space. Thanks