Related
Stock Android currently doesn't support Sanskrit/Hindi (Devnagri lipi Character Set). I see Square boxes like ☐ instead of characters अ आ इ ई उ ऊ on Unicode or UTF8 compliant Hindi websites. Even Google Hindi website doesnt open properly through my HTC Hero's stock Android 1.5 browser or any other browser like Dolphin, etc.
Has anyone figured out how to support Non-English fonts like Devnagri lipi (Sanskrit/Hindi) fonts in Android OS? I want to change my default font to see Devnagri numerals: ०,१,२,३,४,५,६,७,८,९ instead of Roman numerals: 0,1,2,3,4,5,6,7,8,9. I want my clock to use Devnagri numerals instead of Roman numerals.
Can someone please help?
prateekandroid said:
Stock Android currently doesn't support Sanskrit/Hindi (Devnagri lipi Character Set). I see Square boxes like ☐ instead of characters अ आ इ ई उ ऊ on Unicode or UTF8 compliant Hindi websites. Even Google Hindi website doesnt open properly through my HTC Hero's stock Android 1.5 browser or any other browser like Dolphin, etc.
Has anyone figured out how to support Non-English fonts like Devnagri lipi (Sanskrit/Hindi) fonts in Android OS? I want to change my default font to see Devnagri numerals: ०,१,२,३,४,५,६,७,८,९ instead of Roman numerals: 0,1,2,3,4,5,6,7,8,9. I want my clock to use Devnagri numerals instead of Roman numerals.
Can someone please help?
Click to expand...
Click to collapse
The problem is obviously with the font and Android being unable to recognize it -- which leaves me to believe that the fonts you're trying to use are UNI-CODE and actually should be TTF (True Type Face). However, I would try different variants of the font you're looking for. I did some searching and this is what I've found (below). I don't know what characters I'm supposed to look for, but the site I found seemed somewhat helpful and apparently they might have the fonts you're looking for. If so, you need to push the font files you find to your /system/fonts/ folder of your phone -- but HAVE to rename the the font files. One needs to be called DroidSans and the other DroidSans-Bold -- Case sensitive for both.
If you'd like -- I can make an update.zip file for you instead. All you would need to do however it tell me which font you are considering and either upload the font here or give me a link where I can download and package it. Hope that helps.
Just remember that IF and when you find the font file you need, that it has an .ttf extension -- which is where I think your problem is.
http://www.wazu.jp/gallery/Fonts_Devanagari.html
Click to expand...
Click to collapse
pseudoremora said:
The problem is obviously with the font and Android being unable to recognize it -- which leaves me to believe that the fonts you're trying to use are UNI-CODE and actually should be TTF (True Type Face). However, I would try different variants of the font you're looking for. I did some searching and this is what I've found (below). I don't know what characters I'm supposed to look for, but the site I found seemed somewhat helpful and apparently they might have the fonts you're looking for. If so, you need to push the font files you find to your /system/fonts/ folder of your phone -- but HAVE to rename the the font files. One needs to be called DroidSans and the other DroidSans-Bold -- Case sensitive for both.
If you'd like -- I can make an update.zip file for you instead. All you would need to do however it tell me which font you are considering and either upload the font here or give me a link where I can download and package it. Hope that helps.
Just remember that IF and when you find the font file you need, that it has an .ttf extension -- which is where I think your problem is.
Click to expand...
Click to collapse
Thank you for a prompt reply. The website you suggested is very helpful and I think Mangal or Arial Unicode MS are the best bet. It took me a while to find these fonts, sorry for a little late response.
Unfortunately, I could only find Mangal.ttf (201 KB) & ArialUni.ttf (22 MB) but not their respective "-Bold.ttf" fonts as you mentioned.
I can use Mangal.ttf in MS Office 2007 to write in Sanskrit/Hindi and it lets me format the text (bold, italics, resize, etc.).
Would it be enough to push this one font? Since Mangal-Bold.ttf is not available specifically.
Also, does pushing a font to ADB means that it overwrites the new font over the existing font in Android? Since we'll be renaming new font to already existing DroidSans.ttf. Or does it merge the two fonts?
I have attached Mangal.ttf (in a zip) to this post since that has a smaller size (201 KB) than ArialUni.ttf (22 MB). Would really appreciate if you could please create an Update.zip with proper files?
Thanks for your help!
prateekandroid said:
Thank you for a prompt reply. The website you suggested is very helpful and I think Mangal or Arial Unicode MS are the best bet. It took me a while to find these fonts, sorry for a little late response.
Unfortunately, I could only find Mangal.ttf (201 KB) & ArialUni.ttf (22 MB) but not their respective "-Bold.ttf" fonts as you mentioned.
I can use Mangal.ttf in MS Office 2007 to write in Sanskrit/Hindi and it lets me format the text (bold, italics, resize, etc.).
Would it be enough to push this one font? Since Mangal-Bold.ttf is not available specifically.
Also, does pushing a font to ADB means that it overwrites the new font over the existing font in Android? Since we'll be renaming new font to already existing DroidSans.ttf. Or does it merge the two fonts?
I have attached Mangal.ttf (in a zip) to this post since that has a smaller size (201 KB) than ArialUni.ttf (22 MB). Would really appreciate if you could please create an Update.zip with proper files?
Thanks for your help!
Click to expand...
Click to collapse
It's fine that you only found the regular font without it's bold counterpart. What can be done is that we'll use Mangal.ttf twice and rename it Droid-Sans.ttf as well as Droid-Sans-Bold.ttf. The system will accept it, though if you can find a font with both the regular and bold files, that would be nice.
Also, when you adb push the new renamed fonts into the /system/font folder -- they will indeed overwrite the previous fonts that were there. They will NOT be merged.
In anycase, I've created an update.zip file for you to flash. Tell me what happens.
pseudoremora said:
It's fine that you only found the regular font without it's bold counterpart. What can be done is that we'll use Mangal.ttf twice and rename it Droid-Sans.ttf as well as Droid-Sans-Bold.ttf. The system will accept it, though if you can find a font with both the regular and bold files, that would be nice.
Also, when you adb push the new renamed fonts into the /system/font folder -- they will indeed overwrite the previous fonts that were there. They will NOT be merged.
In anycase, I've created an update.zip file for you to flash. Tell me what happens.
Click to expand...
Click to collapse
Thank you for the file pseudoremora. Really appreciate it.
So if these new fonts will overwrite the previous fonts, I hope I don't loose my current stock fonts & style. Just for knowledge purposes; Did you manually merge "Mangal" font into stock fonts?
As far as I know, I would need to root my phone for flashing this file. I have never done it before. But I found steps for it on Unlockr (don't know if I can mention other websites on this forum). I am mentioning the steps below for other people's references, assuming these haven't changed:
Code:
1. Download the following file and then unzip it.
AsRoot2
2. Take the unzipped file and save it into the Tools folder of your AndroidSDK.
3. Plug your phone in via USB and do NOT mount the SD card.
4. Open the Command Prompt and type the following (hitting enter at the end of every line):
cd\
cd AndroidSDK\Tools\
adb devices
And make sure your phone’s serial number pops up (if not setup ADB & USB drivers).
5. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
6. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
Although, I don't know how to unroot the phone after rooting it.
pseudoremora, I have been searching for steps on how to flash a file like "Mangal_font-signed.zip". But since "flash" is such a term that most search results are for Adobe Flash. Do you know any place with step by step instructions to do it for Sprint HTC Hero?
Also, if these fonts don't work. How do I go back to stock condition? Do I need to take some backup?
Thanks for your help.
prateekandroid said:
Thank you for the file pseudoremora. Really appreciate it.
So if these new fonts will overwrite the previous fonts, I hope I don't loose my current stock fonts & style. Just for knowledge purposes; Did you manually merge "Mangal" font into stock fonts?
Click to expand...
Click to collapse
You should have rooted first before thinking about anything else, but that's alright. Also, I did NOT "merge" the fonts... you can't do that. I overwrote the previous font with the Mangal one. Even if you flash a new font, getting the stock font back on is just as easy as adding a different one.
prateekandroid said:
pseudoremora, I have been searching for steps on how to flash a file like "Mangal_font-signed.zip". But since "flash" is such a term that most search results are for Adobe Flash. Do you know any place with step by step instructions to do it for Sprint HTC Hero?
Thanks for your help.
Click to expand...
Click to collapse
Before we go any further, its imperative that you root your phone and understand the in's and out's of flashing, using command prompt, and the installing recovery image. Also, you do own a CDMA Hero, for the Sprint network, correct?
All of the information you are trying to find can be found right HERE on XDA. The link will provide step-by-step guides that will walk you through everything you are trying to learn. I would advise reading them, following the steps the best you can, and then asking questions when you get stuck.
I can give the answers, however... with anything new, it's always best to let ones own curiosity invoke the learning process. Myself and others here are more than knowledgeable to help you any way, but even a beginner is capable of rooting there own phone.
prateekandroid said:
Also, if these fonts don't work. How do I go back to stock condition? Do I need to take some backup?
Click to expand...
Click to collapse
Upon rooting your phone and installing a recovery image, you will have the option to backup your phone and ALL its data. Secondly, if for some reason, you do in fact mess up and get to a point where you would like to start from the beginning (Go back to Stock), there is also an application for that.
So, for the time being -- don't worry about backing up your phone or even going back to stock, you need to focus on rooting your phone, installing a recovery image, making your first Nandroid backup, and then hopefully installing your first user created ROM.
As always, I'm here to help. Oh, one more thing... before you ask me, try to search the CDMA Hero threads, you'll more than likely find your answer. Otherwise, you can ask.
pseudoremora said:
You should have rooted first before thinking about anything else, but that's alright. Also, I did NOT "merge" the fonts... you can't do that. I overwrote the previous font with the Mangal one. Even if you flash a new font, getting the stock font back on is just as easy as adding a different one.
Before we go any further, its imperative that you root your phone and understand the in's and out's of flashing, using command prompt, and the installing recovery image. Also, you do own a CDMA Hero, for the Sprint network, correct?
So, for the time being -- don't worry about backing up your phone or even going back to stock, you need to focus on rooting your phone, installing a recovery image, making your first Nandroid backup, and then hopefully installing your first user created ROM.
As always, I'm here to help. Oh, one more thing... before you ask me, try to search the CDMA Hero threads, you'll more than likely find your answer. Otherwise, you can ask.
Click to expand...
Click to collapse
Thanks pseudoremora. Will do.
In case of an issue, I may have to bug you again.
PS: Yes, I do have CDMA Sprint HTC Hero with Google written on its back cover
prateekandroid said:
Thanks pseudoremora. Will do.
In case of an issue, I may have to bug you again.
PS: Yes, I do have CDMA Sprint HTC Hero with Google written on its back cover
Click to expand...
Click to collapse
Hope my last post didn't come as asshole-ish. That wasn't my intention. I'm just trying to get you in the mindset to always think about searching for the answer(s), before I step in and give them to you.
Also, you're not bugging me at all, I'm more than happy to help.
Good luck!
pseudoremora said:
Hope my last post didn't come as asshole-ish. That wasn't my intention. I'm just trying to get you in the mindset to always think about searching for the answer(s), before I step in and give them to you.
Also, you're not bugging me at all, I'm more than happy to help.
Good luck!
Click to expand...
Click to collapse
Na dude. You're fine.
So I am now rooted, recovered (v1.6.2), nandroid backed up (stock v1.5) & running DC v2.07.2. I flashed Mangal.zip. Good news is that I can now read Devnagri on Dolphin bowser. Glyphs are messed up. So instead of शिवाय it is showing शविाय. But its Ok, at least its readable. Better than ☐☐☐☐☐.
However, the bad news is that English characters are all bigger & spacier than normal. It looks so weird. Will attach a screenshot tomorrow.
prateekandroid said:
Na dude. You're fine.
So I am now rooted, recovered (v1.6.2), nandroid backed up (stock v1.5) & running DC v2.07.2. I flashed Mangal.zip. Good news is that I can now read Devnagri on Dolphin bowser. Glyphs are messed up. So instead of शिवाय it is showing शविाय. But its Ok, at least its readable. Better than ☐☐☐☐☐.
However, the bad news is that English characters are all bigger & spacier than normal. It looks so weird. Will attach a screenshot tomorrow.
Click to expand...
Click to collapse
Excellent! Seriously, that's amazing that you were able to accomplish everything I stated without having me helping you (not that I wouldn't have), but I'm sure you know that you get a great feeling once you accomplish each one of those things (I know I did when I first did it).
Again, great job!
pseudoremora said:
Excellent! Seriously, that's amazing that you were able to accomplish everything I stated without having me helping you (not that I wouldn't have), but I'm sure you know that you get a great feeling once you accomplish each one of those things (I know I did when I first did it).
Again, great job!
Click to expand...
Click to collapse
Dude, I am sorry for being MIA. I have been trying for a few days the merged font that I created using FontLab but it makes English characters so bloated that two lines start overlapping each other. For eg. if you are looking at a specific contact in people App, "Call mobile" text overlaps the cell number right below it.
Wats weird is that FontLab doesn't bloat Devnagri characters but only English characters. I dont know FontLab very well so dont know how to stop it from scaling.
I had to revert to stock font. S**ks!
Do you have any suggestion of some way to merge Stock font with Mangal font?
prateekandroid said:
Dude, I am sorry for being MIA. I have been trying for a few days the merged font that I created using FontLab but it makes English characters so bloated that two lines start overlapping each other. For eg. if you are looking at a specific contact in people App, "Call mobile" text overlaps the cell number right below it.
Wats weird is that FontLab doesn't bloat Devnagri characters but only English characters. I dont know FontLab very well so dont know how to stop it from scaling.
I had to revert to stock font. S**ks!
Do you have any suggestion of some way to merge Stock font with Mangal font?
Click to expand...
Click to collapse
I've never had to merge any fonts; but then again I've only had to read English.
I've never worked with Fontlab, so I'm not sure where to even begin. The reason however I think you keep having problems is because maybe the phone isn't understanding how to handle the merged font... so the Devnagri characters are okay, but the English ones aren't scaled correctly because they were merged or merged incorrectly? Again, I don't know, those are just my ideas.
I hate to say it... but it looks like you're either have to bare with it, choose one font or the other, or what I would do is contact HTC and see if they have native font or any font that they could recommend. I'm all out of ideas, so I don't know what to tell you. Sorry.
Try this
http://forum.xda-developers.com/showthread.php?t=798380
Replace only Fallback font. Do not touch DroidSans.ttf
Hope it helps
But there are issues in having hindi support in this way.
There is Samsung Galaxy phones with perfect hindi support in 2.1 and 2.2 versions of Android. Is there any way to get the Language pack or Hindi IMI from them. And have heard Android 2.3 has bulit-in Hindi language support. But I don't know how to install it.
Opera mini can read hindi font
Opera mini can read hindi font
click here
pseudoremora said:
The problem is obviously with the font and Android being unable to recognize it -- which leaves me to believe that the fonts you're trying to use are UNI-CODE and actually should be TTF (True Type Face). However, I would try different variants of the font you're looking for. I did some searching and this is what I've found (below). I don't know what characters I'm supposed to look for, but the site I found seemed somewhat helpful and apparently they might have the fonts you're looking for. If so, you need to push the font files you find to your /system/fonts/ folder of your phone -- but HAVE to rename the the font files. One needs to be called DroidSans and the other DroidSans-Bold -- Case sensitive for both.
If you'd like -- I can make an update.zip file for you instead. All you would need to do however it tell me which font you are considering and either upload the font here or give me a link where I can download and package it. Hope that helps.
Just remember that IF and when you find the font file you need, that it has an .ttf extension -- which is where I think your problem is.
Click to expand...
Click to collapse
Problem is most of the world has now moved to the unicode fornts from google transliteration which has become defacto standard due to ease of use. If that helps. Any help would really be very useful.
Hi,
I live in China and got an already rooted legend from a super friendly little shop in the neighbourhood here, but it came with a horrendous goapk.com rom which severely locked down my ability to install anything from the market - instead, it tried to force me into this relatively useless Chinese goMarket thing. So, waiting patiently, I finally installed the MoDaCo custom ROM last week and everything is running sweetly.
Only now I find I actually miss a couple of the customisations the Chinese ROM had on it. In particular, the htc_cime was very useful to me because it supported handwriting input - the Google Pinyin IME is less useful to Chinese noobs like me who can't read the sound of the characters and need to input the handwriting.
I have had a http://forum.xda-developers.com/showthread.php?p=7276627 rummage around these threads and found lots of htc_cime packages, none of which work on Legend under Froyo. Does anybody have a solution? The apk's that do install die immediately when I try to input text, and I don't know what to do with the zip files available on that site - I can extract them, but then it says "Application not installed" without any further help.
Cheers and thanks! Maybe the IME will turn up when 2.2 finally comes out for stock Legends, which will surely happen any minute now
So, a few hundred reads and no replies. Seems like a difficult issue, and obviously not many people are interested in using Chinese handwriting. Should I post this on the development thread? Can anyone at least give some advice on how to install these .zip distribution packages? I know how to install a .apk using the file manager, is some other app necessary to install the .zips?
strophy said:
So, a few hundred reads and no replies. Seems like a difficult issue, and obviously not many people are interested in using Chinese handwriting. Should I post this on the development thread? Can anyone at least give some advice on how to install these .zip distribution packages? I know how to install a .apk using the file manager, is some other app necessary to install the .zips?
Click to expand...
Click to collapse
I just downloaded the .zip file from your link and it had the .apk file inside it and another zip (?).
A zip file is a zip file, they are not android specific, have been around at least 20 years now, it is a compressed file, windows or whatever os you use should be able to open it no problems and then just extract/copy the apk inside to your phones sd card and install it, you also need to open the other zip file INSIDE the zip file (yay recursion) and extract/copy the folder to your sd card as well.
I didn't install it myself as I am still on éclair.
It may be that ZIP files are not Android specific, but to install one you should flash it with ROM Manager or from Clockworkmod Recovery. I don't know if extracting the zip and installing the .apk is working like that. The reason for doing this is mainly because some files cannot be written or replaced when phone is in normal use. From that link I saw it is a signed package (by the name) and it should be installed via ROM Manager or recovery
Hi again,
I tried unzipping the .apk file and installing it, but also no luck. I am fairly sure the .apk installer references the "zi" folder ("zi" means character in Chinese), as that folder seems to contain a lot of files describing the metrics and probably recognition of each character as you write it. Still no luck though.
Using the ROM manager to install packages seems a bit like overkill though - if the Google IME can be installed as an apk without rebooting, surely any IME can be installed like that?
I might ask htc about this when the official 2.2 FOTA comes out, if I claim I had it before and it wasn't in the update they might just send me an .apk that will sort this out once and for all. No big hopes on that one though.
Cheers,
Leon
can anyone help me how to make nand file when i have sd file cuz i cannot install from my sd card i need to install directly
thanks
I am not sure that I understand what is your exact problem. But if I'm right and you can not install rom from SD card and want to install it directly from computer, maybe you should try to use DAF versions ?
adecostres said:
I am not sure that I understand what is your exact problem. But if I'm right and you can not install rom from SD card and want to install it directly from computer, maybe you should try to use DAF versions ?
Click to expand...
Click to collapse
yes but there is only one daf version and i want to know how to convert the sd version to daf version
That's not very easy. You'd have to edit the intrid.gz and and zImage and other things to make it work. More effort than it's worth. What ROM you looking for? Is it a .zip SD card file or and Android folder type?
daniel.nano said:
yes but there is only one daf version and i want to know how to convert the sd version to daf version
Click to expand...
Click to collapse
To the point - the fact you're asking this question leads me to believe you're not skilled enough to know how to perform all of the changes this would require.
My suggestion is you forget about the SD version and make the move to the NAND Android instead.
The DAF version is a way for Windows to put Android on your phone through the built-in bootloader onto the NAND chip on your phone. SD android is a completely different structure and you'll never find an "SD DAF" Android.
could you perhaps extract the system folder from the CWM zip, then use mkyaffs2image to build a system.img and drop that in place of the original system.img from the DFT version? (and teh same with the boot folder boot.img too, i would assume)
Or is that make believe?
dkl_uk said:
My suggestion is you forget about the SD version and make the move to the NAND Android instead.
Click to expand...
Click to collapse
daniel.nano said:
can anyone help me how to make nand file when i have sd file cuz i cannot install from my sd card i need to install directly
thanks
Click to expand...
Click to collapse
To the point - the fact you're giving that answer leads me to believe you're not skilled enough to know how to read the whole question befor,,,,,,,,,,,,,,,,
hehe, sorry, couldnt resist.
samsamuel said:
could you perhaps extract the system folder from the CWM zip, then use mkyaffs2image to build a system.img and drop that in place of the original system.img from the DFT version? (and teh same with the boot folder boot.img too, i would assume)
Or is that make believe?
Click to expand...
Click to collapse
Extracting the system folder from CWM zip wont work. Its because during the zip installation the updater script is beeing called and it creates a lot of symlinks. So, if you just extract and convert, you will miss the whole bunch of symlinks (and permissions, etc..)
samsamuel said:
To the point - the fact you're giving that answer leads me to believe you're not skilled enough to know how to read the whole question befor,,,,,,,,,,,,,,,,
hehe, sorry, couldnt resist.
Click to expand...
Click to collapse
Really?
Never heard of DAF then?
We're limited to either SD or CWM install, are we?
dkl_uk said:
Really?
Never heard of DAF then?
We're limited to either SD or CWM install, are we?
Click to expand...
Click to collapse
Heh, dig deeper.
The op is limited to usb only so yea, in this case we are limited to daf only, and he finds there isn't as wide range of daf roms, hence the perfectly reasonable question.
which part of the original post can't you understand?
greg17477 said:
Extracting the system folder from CWM zip wont work. Its because during the zip installation the updater script is beeing called and it creates a lot of symlinks. So, if you just extract and convert, you will miss the whole bunch of symlinks (and permissions, etc..)
Click to expand...
Click to collapse
Ah I thought maybe something like that, but figured I'd ask anyway, for myself if nothing else.
samsamuel said:
Heh, dig deeper.
The op is limited to usb only so yea, in this case we are limited to daf only, and he finds there isn't as wide range of daf roms, hence the perfectly reasonable question.
which part of the original post can't you understand?
Click to expand...
Click to collapse
I'll assume your lack of English skills is the reason you've totally mis-understood every single thing i've written in this thread.
If I've missunderstood, it can only mean that even though it didn't sound like it, you do agree with me, in which case appology accepted, lets say no more about it.
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
Is there any way to change (that is, add to) the fonts in the reader itself? I've read that it's only possible to change the system font? Are there any updates on this?
Not sure if any has tried FontInstaller on the Nook or not. It's a rooted Android device, so I would think in theory at least, it would word.. Someone correct me if I am wrong please?
Yes, I can confirm that it is possible to replace the fonts on the rooted nook, that is provided that you want to keep using the stock reader. On other readers, cool reader for example, you can just install additional fonts and they would be able to use those new ones.
zecoj said:
Yes, I can confirm that it is possible to replace the fonts on the rooted nook, that is provided that you want to keep using the stock reader. On other readers, cool reader for example, you can just install additional fonts and they would be able to use those new ones.
Click to expand...
Click to collapse
Could you explain how to do it? My device is rooted. I just prefer to use the default reader because some of the newspapers are encrypted and I prefer to read it right after I download it, rather than transfer it to my computer, decrypt it, and send it back to my reader.
xdadooder said:
Could you explain how to do it?
Click to expand...
Click to collapse
From memory:
/system/fonts contains all "stock" fonts, you'll need to find out which files are of the font in the original reader
Pick a font you don't like (Malabar, for example). See in /system/fonts, these are the files of interest: Malabar.ttf, Malabar-Bold.ttf, Malabar-BoldItalic.ttf, Malabar-Italic.ttf. Back up these first.
Get a new font of your choosing (Gentium Book Basic, for example -- because I just LOVE this font), rename all the files to be exactly like Malabar's ones. Pay attention to Bold, BoldItalic, etc.
Overwrite the original files with the renamed one.
Make sure permissions are correct (644)
Reboot and choose Malabar as your preferred font in the reader.
IndyRoadie said:
Not sure if any has tried FontInstaller on the Nook or not. It's a rooted Android device, so I would think in theory at least, it would word.. Someone correct me if I am wrong please?
Click to expand...
Click to collapse
Just realized FontInstaller probably would only work on the Rooted part, not the stock Nook part, my bad..
zecoj said:
Yes, I can confirm that it is possible to replace the fonts on the rooted nook, that is provided that you want to keep using the stock reader. On other readers, cool reader for example, you can just install additional fonts and they would be able to use those new ones.
Click to expand...
Click to collapse
zecoj said:
From memory:
/system/fonts contains all "stock" fonts, you'll need to find out which files are of the font in the original reader
Pick a font you don't like (Malabar, for example). See in /system/fonts, these are the files of interest: Malabar.ttf, Malabar-Bold.ttf, Malabar-BoldItalic.ttf, Malabar-Italic.ttf. Back up these first.
Get a new font of your choosing (Gentium Book Basic, for example -- because I just LOVE this font), rename all the files to be exactly like Malabar's ones. Pay attention to Bold, BoldItalic, etc.
Overwrite the original files with the renamed one.
Make sure permissions are correct (644)
Reboot and choose Malabar as your preferred font in the reader.
Click to expand...
Click to collapse
Thanks. Will try that.
If that works, wondering if it would help with the Kindle app?
zecoj said:
From memory:
/system/fonts contains all "stock" fonts, you'll need to find out which files are of the font in the original reader
Pick a font you don't like (Malabar, for example). See in /system/fonts, these are the files of interest: Malabar.ttf, Malabar-Bold.ttf, Malabar-BoldItalic.ttf, Malabar-Italic.ttf. Back up these first.
Get a new font of your choosing (Gentium Book Basic, for example -- because I just LOVE this font), rename all the files to be exactly like Malabar's ones. Pay attention to Bold, BoldItalic, etc.
Overwrite the original files with the renamed one.
Make sure permissions are correct (644)
Reboot and choose Malabar as your preferred font in the reader.
Click to expand...
Click to collapse
I can't mount the system\fonts folder as read/write in root explorer. Any idea how to get around this? I was able to read and copy the fonts to backup before, so I don't know what's wrong
WARNING: Don't try to replace system fonts. I replaced my system fonts and now my nook is stuck in a boot loop. I think the nook is very particular about what is in the file system.
I tried to do a factory reset, and now I can't register the device because the keyboard no longer appears when I try to connect to a network to enter the password. Something is seriously wrong with the root file system.
xdadooder said:
WARNING: Don't try to replace system fonts. I replaced my system fonts and now my nook is stuck in a boot loop. I think the nook is very particular about what is in the file system.
I tried to do a factory reset, and now I can't register the device because the keyboard no longer appears when I try to connect to a network to enter the password. Something is seriously wrong with the root file system.
Click to expand...
Click to collapse
Were you trying to replace "helvetica neue" by any chance?
You can try this to format /system as well for a full stock restore: http://forum.xda-developers.com/showthread.php?t=1475613
zecoj said:
Were you trying to replace "helvetica neue" by any chance?
You can try this to format /system as well for a full stock restore: http://forum.xda-developers.com/showthread.php?t=1475613
Click to expand...
Click to collapse
No, I was trying to replace trebuchet. I did the 6 power off system restore to stock and I'm fine now.