yashsingh1/xdaforums huggingface dataset:
[Nook Color Q&A, Help & Troubleshooting] bachon:
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
[Nook Color Q&A, Help & Troubleshooting] biohazrd51:
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.
[Nook Color Q&A, Help & Troubleshooting] brentb636:
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.

:)
[Nook Color Q&A, Help & Troubleshooting] Sam Adams:
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!
[Nook Color Q&A, Help & Troubleshooting] bachon:
Downloading it now. Many Thanks to you for the help!
[Nook Color Q&A, Help & Troubleshooting] mateorod:
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.
[Nook Color Q&A, Help & Troubleshooting] bachon:
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
[Nook Color Q&A, Help & Troubleshooting] brentb636:
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.
[Nook Color Q&A, Help & Troubleshooting] DizzyDen:
Breaking this down for you and trying to answer/explain your questions:

Generic-sdcard.... is a disk image file... it includes the script for partitioning the uSD (if needed), formatting the partitions, installing ROM and gapps.

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.

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.

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.

Yes... copy/paste... do NOT extract (that's what the installer/updater does)

See the answer above regarding what the installer/updater script expects for the naming.

See above.

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.

the number is referencing the date, some are YYYYMMDD some are MMDDYYYY.

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.

This gets daunting... answer above.

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)

Once the installer/updater installs a zip file... it deletes it... also note... the first boot after an install take a VERY LONG TIME

This would be very good to do... hopefully I have provided enough information to get you started.
[Nook Color Q&A, Help & Troubleshooting] Sam Adams:
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://xdaforums.com/showthread.php?t=1444943 for more info. Sam has also included the new expanded Generic SD image there.
[Nook Color Q&A, Help & Troubleshooting] bachon:
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
[Nook Color Q&A, Help & Troubleshooting] smarcin:
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.
[Nook Color Q&A, Help & Troubleshooting] Benzoman:
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:
[Nook Color Q&A, Help & Troubleshooting] DizzyDen:
You need to read my previous and long post in this thread answering your questions ;)
[Nook Color Q&A, Help & Troubleshooting] bobtidey:
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.
[Nook Color Q&A, Help & Troubleshooting] bachon:
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: bach_on@hotmail.com

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
[Nook Color Q&A, Help & Troubleshooting] DizzyDen:
No problem at all... just send it to dizzyden@gmail.com
[Nook Color Q&A, Help & Troubleshooting] peerpaulandmary:
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
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
First, I recommend you go to my tips thread linked in my signature. Read section B on the second post. I would also recommend getting the latest generic-SD... image file linked there.

It sounds like you may not have a good SD card. You need to use a SanDisk class 4 card if possible. Other cards cannot handle the small file read/write speeds required by running a ROM from it. So it becomes very unreliable. The fact that you got it to boot once makes me believe that the downloaded ROM is ok.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Q&A, Help & Troubleshooting] peerpaulandmary:
>>>>

Thanks for the prompt reply. I had already read your tips, and my sometimes technically challenged mind :) hadn't picked up anything that seemed relevant to my issue. Anyway, the card is a sandisk 16gig class 10 card, new at the start of my futile exercise. To make a long story short, I had already decided that something about the card might be an issue, so I bought a new 8 gig sandisk card while I was out today, and it worked like a charm. I am still puzzled, but, hey, it works now. Any suggestions how to get the nook to show up on win 7 computer? I followed instructions on getting adb interface working, but it still shows the two drives as needing to be inserted.

Once again, thanks.

JPB
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
After those two empty drives show up on your PC, go to the nook and open your notification area. There is an option to connect. Do it. And make sure to have USB debugging turned off. (Unless you were wanting ADB access, which you did not really say. If that's what you meant, then turn it on.)

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Q&A, Help & Troubleshooting] peerpaulandmary:
Thanks a bunch - I think I am finally up and running - maybe at a snail's pace, but running, never the less.

JPB
[Nook Color Q&A, Help & Troubleshooting] irisclara:
The reason everything is so slow is that your sd card isn't a class 4. The class 10 cards are considerably slower at running an operating system than the class 4 cards.
[Asus  Eee Pad Transformer Prime] bscotth:
Update February 3:

Tried the GPS test again today and I went from 0 satellites before the RMA to now having 7 satellites. Attached is a screen shot of such.

Good job Asus.

Update February 2:

Received my prime last night and played with it for most of the evening. No problems on honeycomb, updated to ICS and still had no problems. There was no information on exactly what they did to repair like I had hoped but all is good.

GPS is slightly better (1 satellite vs. 0 satellites before) but in my opinion,

this isn't a GPS device and I don't plan on using it like one.

So in a TL;DR version: If you plan on RMA'ing, it worked effectively for me but the whole process took about a month.

Original post:

Hello everyone,

I just wanted to take the time to keep you all up to date on how the RMA side of the prime tech support is going for me and possibly others.

I sent my prime to Texas on the 5th (It's been quite a while.. I miss it.) A week later it was received by the repair facility (the 12th). The support status website then said "Waiting" for about 18 days then finally it said "Ready for shipping" and the "memo" section said I received a new serial number.

I'm guessing the support staff did extensive hardware replacement or simply gave me a new prime. I hope some sort of repair report/record is included whenever I get my prime back.

Original complaint was absolutely zero GPS and slight backlight bleed.

I attached a screenshot of the repair status screen.

I'll update this post when I get it back and disclose whether or not the complaints have been fixed or if there are any new problems. ;) Hopefully this helps anyone trying to decide whether to RMA their unit or not.
[Asus  Eee Pad Transformer Prime] 1SiK1500:
intresting. Please keep us posted on the updates. let us know what is fixed!
[Asus  Eee Pad Transformer Prime] kerryking1:
mine says Waiting-[WB5] Wait for Repair\Test\Aging
[Asus  Eee Pad Transformer Prime] Pubnum:
<troll>

Wait, you returned this because of no-GPS and slight backlight bleed...Really? You must have known GPS wasn't working

Even the IPAD 2s have backlight bleed...

</troll>

None the less, good luck, curious how the RMA is going to go.
[Asus  Eee Pad Transformer Prime] Jonasmyst:
I am going through my own trials with them. I bought my Prime on the 20th and and received it on the 21st. On the 24th I was at school and opened the tablet (I have the TF201 Dock) and there was a single pristine crack in the screen. Tablet has no abrasions or dents so it is obvious it was not dropped and I am a bit over protective of a new device for the first few months. I think I just got a bad piece of glass, that or the dock is not designed very well. But since the basic design of the Prime dock is the same as the original Transformer I find that hard to believe.

So they received the tablet in TX Friday. Sat in Waiting yesterday. Today it showed they wanted to confirm repair OOW. I called and asked them ??? and they said it was "expertly analyzed" and found to be customer induced damage. I stayed calm and responded with "the table has been treated like it was priceless. The screen cracked when I closed the tablet while in the ASUS made dock. There are no indications of droppage on the tablet and I find it unacceptable to charge the customer for the repair of what is most likely a manufacturing defect."

Now I am waiting 24-48 to hear from a supervisor. Now if I had dropped the tablet I would be like, ok I screwed up. But I did not. And I did buy ADC insurance from Square so I can get it fixed for free, but I am not going to have them fix something I believe is a manufacturing defect. Guess we will see what ASUS customer support is really made of in the next 24-48 hours. Hate having the tablet for 2 days then spending 2 weeks without it. It's like a big tease! lol
[Asus  Eee Pad Transformer Prime] kaijura:
Sounds really weird to be cracking on its own. You'd need to be in very high heat or below/near freezing temps to induce it by nature.

Did someone damage it without you looking? BB gun, threw something, etc. Things can't suddenly crack outta nowhere, but this is pure conjecture of course.

First in the line of a major manufacturing defect?
[Asus  Eee Pad Transformer Prime] kerryking1:
my touch screen wasnt working and usb didnt work
[Asus  Eee Pad Transformer Prime] Jonasmyst:
I wish someone had hit it or I dropped it, I could have just sent it in for Accident repair but I have to try ASUS first because SquareTrade says it is a manufacturing defect if I did not drop the tablet.

Basically I took the tablet, in the dock and closed it. Placed is in a padded neoprene sleeve. Set the tablet and the sleeve on the passenger seat next to me (where it did not move and I hit no pot holes or anything crazy). Drove from work to school. Picked up the tablet and took it inside. Took it out of the sleeve and opened it. BAM crack. Could barely see it from the front on view. I think I just got a bad piece of glass. I have owned the Evo 4G and I own the Evo 3D and a Kindle Fire. All gorilla glass and I have had no problems (granted smaller screens). I attached 2 pics of the crack. (Yes I know there is a sword in one :D)
[Asus  Eee Pad Transformer Prime] markimar:
Clearly looks like a defective screen. Don't see any indication of impact to me. They should repair it.
[Asus  Eee Pad Transformer Prime] Blairware:
It would take a lot of force to induce that

I would guess that a serous amount of flex in the tablet would be required to have that happen. Gorilla Glass however is often misunderstood as break resistant when it actually breaks quite easily. It is hardened glass that is SCRATCH resistant, and not even all that scratch resistant. My daughter scratched the screen on one of my phones with a cheap ring, and she wasn't mishandling it at all, just playing a game. have seen rants about Gorilla Glass breaking on phone placed in their back pants pocket, which is so stupid I can't imagine what they were thinking.

Your glass may indeed have been stressed by the bezel, and assembly, and could easily have been defective, when you consider how many Prime Asus was cranking out in December. If it was stressed in it's frame, and you went out in the cold it could have contributed to its failure. You said you opened it at school. This is important: How did you transport it? In a sleeve/case or just Dock/Tablet in backpack? My thinking is it was stressed, and only took some additional flex or twist to have it snap.

Stand your guns, and just mention ONCE that there are no dents marks or abrasions on the tablet casing. Just calmly (as possible, I know how infuriating CSRs can be) ask for a supervisor, explain that the dock was attached the whole time, and no "accidents" "drops" or anything else occurred. MOST IMPORTANT: Ask : What exactly is the "expert analysis" that was done? Was the glass measure at multiple points with a digital micrometer? What evidence do THEY have to suggest customer induced damage?