Related
So, many of us are waiting patiently of a new ROM for our Alpines, courtesy of aeroflyluby and cottula, but a few people keep bugging them about release dates.
So, here is something for you. It is a linux kernel for the Alpine.
To use it you mus have a
1) Alpine (Obviously)
2) A 512mb or larger SD card (Not SDHC!)
3) Windows Computer
4) An SD card reader (You can't use the Alpine as an SD card reader for this sorry)
If you have all these then follow these instructions.
1) Download the Zip file from http://www.mediafire.com/?m7klbqdkzf4y3w6
2) Extract it to your desktop
3) Find the linux folder and copy the contents to the Storage on your Alpine
4) Open up ghost32 on your computer
5) (NOTE: If it says anything about compatibility, ignore it and carry on.) Click on local and then Disk. Then click on the 699linux.GHO file. Then click on your SD card. (Usually the smallest one) Wait for it to complete
6) Make sure that your alpine is fully charged and ALL IMPORTANT DATA IS BACKED UP.
7) Put the SD card into the Alpine and Navigate to STORAGE - NOT STORAGE CARD on the alpine.
8)Open haret.exe. It it asks for a startup.txt, make sure startup.txt is present. If here is a button ha says run or similar, click it!
9) Wait for linux to boot and Enjoy!
NOTE: I am not responsible for any damage this may cause to either he alpine or the computer used.
I cant test this at the moment as my battery is broken, if anyone can tell me what the correct voltage for the battery is it would be appreciated.
I didn't make this, just found it on bbsfans.net (I think)
btyre said:
So, many of us are waiting patiently of a new ROM for our Alpines, courtesy of aeroflyluby and cottula, but a few people keep bugging them about release dates.
So, here is something for you. It is a linux kernel for the Alpine.
To use it you mus have a
1) Alpine (Obviously)
2) A 512mb or larger SD card (Not SDHC!)
3) Windows Computer
4) An SD card reader (You can't use the Alpine as an SD card reader for this sorry)
If you have all these then follow these instructions.
1) Download the Zip file from http://www.mediafire.com/?m7klbqdkzf4y3w6
2) Extract it to your desktop
3) Find the linux folder and copy the contents to the Storage on your Alpine
4) Open up ghost32 on your computer
5) (NOTE: If it says anything about compatibility, ignore it and carry on.) Click on local and then Disk. Then click on the 699linux.GHO file. Then click on your SD card. (Usually the smallest one) Wait for it to complete
6) Make sure that your alpine is fully charged and ALL IMPORTANT DATA IS BACKED UP.
7) Put the SD card into the Alpine and Navigate to STORAGE - NOT STORAGE CARD on the alpine.
8)Open haret.exe. It it asks for a startup.txt, make sure startup.txt is present. If here is a button ha says run or similar, click it!
9) Wait for linux to boot and Enjoy!
NOTE: I am not responsible for any damage this may cause to either he alpine or the computer used.
I cant test this at the moment as my battery is broken, if anyone can tell me what the correct voltage for the battery is it would be appreciated.
Click to expand...
Click to collapse
It's nice, I ran it too.
I think having linux side-by-side to operate on ext2 partitions is really good think, especially for Android.
(btw, android runs really similar, but there is another ways (initrd))
Yeah, I know about initrd but this is the old style, less user friendly but less hassle to make. I think the idea of using a Ghost patch so it's easier is nice oo.
btyre said:
Yeah, I know about initrd but this is the old style, less user friendly but less hassle to make. I think the idea of using a Ghost patch so it's easier is nice oo.
Click to expand...
Click to collapse
But you can forget about manual modifying..
Ext2 driver for windows works okay, but sometimes it really corrupts files or all disk too.
Isn't it quite hard to manually modify using the initgrd? I don't know as I've only read about it.
With the .GHO meathod you can use the Ghosexp to modify the .GHO file then flash it again.
Personally I think it's a draw.
NOTE: If you use this, please post. A few screens would be nice too. I would post some, but my battery is dead. If you know where to get one then please tell me by PM, or just post. Thanks
if we're talking about things that would keep yo busy until release of anything new we should appreciate this useful app for PPC2003, pLock.
It provides you lockscreen known from WM5, with ablitity of automatic locking and hardware buttons unlocking.
To configure it after installation, go into Today options and after checking pLock tap on Settings/option (don't remeber, alpine under hard development)
Download from attachment, enjoy (it's not mine)
I've got an error like this when run ghost32
error when create partitions from ghost.
I'can attach my screen shot here
Help Please
I am absolutely pulling my hair out here. I have 3 16GB sd cards - 2 16gb ridata class 6, and one patriot class 4.
No matter what I do, I cannot get any of them to work with Froyo. ONLY my 16gb cards fail - I have various other 4 and 8gb cards floating around that work 100% fine.
With this image, I can boot the first time, run the makepart.sh command (which gives a "too many cylinders on disk error), and reboot fine again. When I go to finish formatting the SD card partition using formatpart.sh, it completes the process but never reboots - it just gets stuck on the Android... text in the bottom corner of the screen.
http://forum.xda-developers.com/showthread.php?t=922324
With these images, both 6.6 and 5.9, I can boot initially just fine but the sd card is only seen as 884mb. When I expand the partition to take up the rest of the free space (about 14gb) using EASEUS partition manager, I can boot fine next time but get literally hundreds of force closes to the point where I can't do anything. I've tried everything - creating new partitions as both logical and primary, resizing existing partitions, formatting from terminal and windows 7 x64, etc, etc.
http://forum.xda-developers.com/showthread.php?t=883175
So I've had it. If someone can make me a flashable and bootable SD card image (preferably 6.6, but 5.9 works too) that simply works with the 16GB cards (so I can actually utilize the extra space) and includes the below I will paypal them $125.
-Google Apps
-Market
-Camera and Voice apps removed
-Dropbox added
-Mount/System added (if the app does not take up the full screen force close it once)
-Nook Reader
-Phone and TelephonyProvider removed
-SetupWizard renamed (Can't get it to work. Go into Setting>Accounts & sync to add gmail account after your wireless has been setup)
-Flash installed and updated
-Default Launcher removed
-Zeam added
-Button Savior
-Angry Birds
-Astro File Manager
-Gingerbread keyboard
I basically want a version of the customized Nookie, but with Angry birds, astro, and button savior instead of softkeys (I can't stand softkeys).
To clarify, it only has to work with 16GB cards to get the $125. If it can work with 4 and/or 8GB size cards too, I'll add another $50.
Thanks for looking.
$500 if someone can de-expand my snookie "wife" from 16GB to 2GB and isolate her to sit in her fixed emcc and cook me up some gingerbread. lol. and yes i have used the search function already.
Edit: I did my own research and came to this, I did not create it but I read that some people are using it on 16gb SD cards and it works perfectly. So I decided to put it here.
Updated 2/6 new version! Pandora, YouTube, MP3's all play now. Flash might work w/o choppiness now too(?) - let us know.
Installing Nookie Froyo custom Android 2.2 ROM to boot off of an SD card:
The first thing you're going to need is a micro-SD card:
*at least 2GB in size
*at least 4GB is recommended, in order to have several GB's of storage on the SD Card partition (what Android reads as actual SD card storage)
*Class 6 or 10 is preferred
*Class 4 may be fine, 2 will likely be slow
Be aware that some companies claim to be offering a higher-class card than they really are (as there's no independent third-party that monitors the Class specification). So researching the brand you're considering is recommended.
You'll also need an SD card reader
If you have an Android phone, you may also be able to use it by placing the SD in your phone, selecting Mount as USB Drive on your phone, and proceeding from there.
First, download the latest version of Nookie
Unzip the .gz file (Winrar, 7zip, etc. Should work for that) so that you have an .img file that you're working with.
If you're on a PC, you're going to want to get a program called Win32DiskImager.
If you're on a Mac or Linux machine, you'll want dd.
Connect the SD card to your computer.
For PC Users:
open Win32DiskImager, select (using the button with the dots) the image file for Nookie that you downloaded, then select the drive of your SD Card (be very careful you're choosing your SD Card drive and not another!), then choose Write Image. *After a few minutes, you're all done!
For Mac Users (instructions credit nookdevs.com)
Open a terminal window.
Find which drive the sd card is mapped to: type in the terminal this:
diskutil list
Be very careful to identify the SD card and not your hard disk. Be VERY careful.
Now unmount that drive typing this:
diskutil unmountDisk /dev/disk#
(My computer is was disk2 replace # with your number.)
The computer should say:*Unmount of all volumes on disk was successful
dd if=NameOfNookieFroYoImage of=/dev/disk# bs=1m
Again, replace # with the number of your card. Everything needed should copy right over to the card.
RUNNING NOOKIE:
Simply insert your Nookie Froyo SD card into your nook and power on. As long as your SD card is in your NOOKcolor when you power it on or reboot, it will boot into Nookie Froyo. Everything that would normally be on an Android phone or tablet's internal memory (plus what would normally be on an SD card) is all going to be on your SD (this is why we recommended a card of 4GB or more).
One of the first things you'll notice is that there aren't any Google apps installed. You'll need to do this yourself (I would have loved to include them, but there are legalities, yadda yadda...).
ADB Installation of Google Apps:
1. You'll need to have adb (Android Debug Bridge) installed on your computer. This link explains in relatively easy terms how to get this going . . .http://forum.xda-developers.com/showthread.php?t=502010
Basically, you'll want to install the Android SDK and become familiar with the location of the directory it was installed in.
If you want to make it easy, move the 'Tools' directory (inside the SDK directory) onto c:/ . . . (or whatever your main hard drive's letter is) then, to get there, you'll simply type cd c:/tools
2. Having installed the SDK for adb access to your nook, now download the google apps files, and unzip the file so that it extracts the folder called 'system' into the 'Tools' directory in the SDK folder you downloaded.
3. Now you'll open a command prompt in Windows (start menu>run>type 'cmd') and navigate to the correct folder (cd [folder directory's path]). On Mac, this would be done via Terminal.
4. Now, with your NOOKcolor connected to your computer's USB port, type the following (of course, hit enter after each line):
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push [here, enter the path to your SDK tools folder]\system system/
adb reboot
5. Now your NC will reboot. When it boots, you'll have Market, Gmail, Google Maps, and many more Google apps.
* If you're getting a "device not found" error when running adb, first, reboot your Nook and your computer and see if it changes.
If that fails, download and unzip this file, open install.exe, and follow the on-screen prompts (this will install drivers so your computer will recognize the nook).
If that doesn't work, try opening the Super User app on your nook and then issuing the commands.
If that still doesn't work, refer to the steps in this thread, repeating if necessary.
One of the first things to do:
Before you start, one of the most important things to remember with the current version of nookie is to turn the screen off/on (do this each time you boot your nook). There's some serious touchscreen lag by default, and this is the very simple solution to make it go away. Nothing fancy, just put the screen to sleep for a sec, and when you turn it back on, it'll be plenty responsive.
Click to expand...
Click to collapse
Here is a comment a user posted regarding the 16gb SD cards
I bought a class 10 16GB from Wintek, a brand I've never heard of and not only was the card unbearably slow -- so massive lag a points, it ended up corrupting itself... Anyways, I put in a 16 GB class 4 Kingston I have and not only is it faster than the supposed class 10 -- rarely any lag, I've not had any problems.
Click to expand...
Click to collapse
Source: (all credit for creating the rom)
Android Central
Edit 2: Since you also wanted to delete any signs of cell phone options, use this theme.
http://forum.xda-developers.com/showthread.php?t=944278
Hope this helps
So... since someone did end up "fixing" your problem, although not directly in response to your thread, are they going to get a nice surprise?
Chirp....Chirp....Chirp....Chirp...
(Just Kiding)
"computerpro", have you looked to see if the FAT is FAT16 or FAT32? Pretty sure a 14G FAT16 isn't going to fly.
khaytsus said:
"computerpro", have you looked to see if the FAT is FAT16 or FAT32? Pretty sure a 14G FAT16 isn't going to fly.
Click to expand...
Click to collapse
It's Fat32. I'll try that solution posted above when I get home from class, but brian said he is working on an update that should work with all cards and it should be out today. What's weird is that I can even boot with a 10GB partition with 4gb unallocated space. IT's just once I get up in the 12-14gb partition size range when things start corrupting themselves. And again, what's weird is that this happens across different brand and class cards. They are not defective. I am convinced it has something to do with the too many cylinder error I get while running makepart.sh
We shall see!
Need to have better/clearer instructions on the win32diskimager software to write autonooter to sdcard. Things I did:
1. 16gb microsd card in laptop via sd card adapter.
2. dl autonooter 3.0, unzaipped in seperate folder on desktop(124,627kb size img file)
3. dl win32diskimager-RELEASE0.2-r23-win32, unzipped
4. double click Win32DiskImager.exe under the unzipped folder
5. I select the aformentioned autonooter img file and the program automatically selects my sdcard, in my case g:
6. I click "write"
7. I get a Confirm overwrite message "Writing to a physical device can corrupt the device. Are you sure you want to continue?" I click Yes.
8. Write Error message appears- Not enough space on disk.
wha???
I am confident that I am doing something wrong in the whole windiskimager process, as the process was never explained very well. For example, when you go to the page to dl the win32diskimager there are 4 files 2 win32 files and 2 source files. One each for a .2 release and a .1 release. ok...wtf? what do I use? how do I use them etc etc etc.
It just seems to me that this particular step in the process could stand a little more clarification/simplification. just saying.
Thanks.
I had the exact same issue, someone told me that it might have something to do with using a built in SD card reader to your laptop, like I was using. He said that he tried that and an external reader with win32diskimager, and that the external usb reader worked fine.
I was able to work around this by using the method that involved WinImage instead of win32diskimager...I don't have the instructions on me at the moment but if you look around you may be able to find them.
rohit275 said:
I had the exact same issue, someone told me that it might have something to do with using a built in SD card reader to your laptop, like I was using. He said that he tried that and an external reader with win32diskimager, and that the external usb reader worked fine.
I was able to work around this by using the method that involved WinImage instead of win32diskimager...I don't have the instructions on me at the moment but if you look around you may be able to find them.
Click to expand...
Click to collapse
Actually you might just want to have both. I've the same thing happen with WinImage and had to use Win32DiskImager. As long as I don't run into both having the error, I'm good
Folks, I am trying to root my NC for the first time. I am following the instructions found here:
http://forum.xda-developers.com/showthread.php?t=942424.
I cannot get WinImage to write to the disk. I downloaded auto-nooter-3.0.0. It is about 125 Meg when unzipped. I open Winimage just fine, and point to the .img file. When I try to do the "Restore Virtual Hard Disk Image", it asks me for a VHD file. I checked all the folders I installed, and cannot find a .vhd file anywhere.
I did point it back to the image file and it says it cannot write it because the file is in use...
I also tried the alternate windows application, Win32ImageWriter. No good. It errors out as well. Gives me an undocumented error code: error 8.
There must be something wrong with my setup, but I cannot figure out what it is. I have a brand new MicroSD card, 8GB. The card is visible in windows explorer and it shows empty...
Any help would be appreciated.
Jim
Error 8 means you have to run win32imagewriter as administrator.
Using Win Image 32
Jim,
EDIT: use whatever version of Clockwork Mod that is recommended for the purposes that you are trying accomplish. The one I listed below may not work with what ever you are doing.
I had similar issues when I started to use it, also.
The following is info from another post I made on installing a rom to the Nook. Formatting the XD card with SD Formatter 3.0, and then using version 0.1 of Win Image seemed to be the answer.
A) Download the following software to your PC/MAC for formatting your XD card. This is the best one that I have found.
SD Formatter 3.0 for SD/SDHC/SDXC:
- Format your XD card. This step is very important to correctly write the EXT4 compatible bootable SD recovery.
B) You will need “Image Writer for Windows”
- I found that the “0.1 (truckstop) release” worked the best. The newer version seemed to always have some problem.
- Paste the unzipped folder to you C:\ directory. Put the EXT4 compatible bootable SD recovery file in the same folder. This will help prevent issues. This software is originally intended for a Linux environment and thank you to the developer for making it compatible with Windows.
- Make sure that the chosen device is your XD card. It automatically selects the correct one, but you never know. Go to “my computer” in windows and check to see what Letter has been assigned.
- Choose the EXT4 compatible bootable SD recovery file from Image writer directory.
- Click the “write” button. This will take a few minutes to finish.
- Now you can copy misc files to the flash drive. It is ready to boot your Nook into Clockwork Mod Recovery.
They don't trust me yet on this site, so I cannot post links to other sites. The required links are in my original post: http://forum.xda-developers.com/showthread.php?t=997764
Let me know it this helps.
SUBCAN
Solved: cannot write SD image
solved...
Thanks to both Subcan and n1bsbri for the replies. The one that put me on the right track was N1's statement that I had to run as admin. I was running as admin, but obviously I did not have write permission. I then just tried to write something to the card using dumb old windows explorer and found that the card was write protected.
I am embarrased to admit it took me hours to find a post that highlighted the fact that on some microSD adapters you had to tape (yes, good old Scotch Tape) over the switch to get it writeable. I did that, wrote the card, and the NC booted right up.
I cannot begin to tell you how many bad words it took me to figure that out...
Thanks to both of you for your replies. I am very new at this and I know I will have more questions... thanks for getting me over the hump!
Jim
I keep seeing SD card rooting questions. I'm providing a link to some guides that describe in gory detail how to get CM7 up and running on an SD card (for both MAC OSX and PC). These guides are built off of verygreen's size-agnostic SD card thread and he deserves any and all credit. All that I (DrAstro) and DrWho have done is expound on the easy-to-follow steps that he provides from the perspective of trying to teach someone who is only mildly computer literate.
http://clubnook.com/forum/showthread.php?953-Rooting-Instructions
If this helps, go to verygreen's SIZE AGNOSTIC card thread and give him thanks.
I've just copied and pasted directly from Clubnook in case people don't want to link over there. If this is useful for you, comment and I'll keep it updated. If not, just let it fall into the ether...
CM7 - SD Card - Mac Version
INSTALLING CM7 (CyanogenMod 7/Android 2.3) ONTO A MICROSD CARD FOR USE WITH NOOK COLOR
Thanks to DrAstro for the following instructions:
I used the instructions from verygreen (who deserves any and all credit):
http://forum.xda-developers.com/show....php?t=1000957
I did nothing other than follow exactly what he said to do and was up and running with full android market access in about 10 minutes (with a 5 minute nap in the middle!). It was literally that easy. I’ve just expanded, in gory detail, on the basic.
Basically, what you are doing here is taking a microSD card, making it so that the nook color can boot from it, putting a new OS on that card (CM7) and then adding the android market. At the end, you will be able to run a more tablet-like experience from your microSD card without doing anything to the internal software that BN put on there. Here are steps, with heavy borrowing from verygreen’s guide. Hopefully you will read and understand what you are doing, so that you can pick and choose which OS zip you want to use.
NOTE: These are mac specific instructions, as that’s what I used!
1) Downloaded the following files and put them on your desktop:
generic-sdcard-v1.2.1.img.gz
(http://nook.handhelds.ru/sdimage/gen...-v1.2.1.img.gz) - This file makes your SD card bootable. This is probably the “hardest” part of the process as you have to “burn” this image to the card, not just “drag and drop”
update-cm-7.1.0-RCO-encore-2.6.32-beta3.1.zip
(http://coachz.inetpro.org/~dalingrin...32-beta3.1.zip) – This is the latest beta version of CM7 that was available at the time I did this! There may be some instability, but they fixed the battery issues with this release so the tradeoff is worth it.
Or get the latest stable version update-cm-7.0.2-encore.zip
(http://tinyurl.com/3vyanhh)
gapps-gb-20110307-signed.zip
(http://wiki.cyanogenmod.com/index.ph...Latest_Version) – This was the latest google apps version that was available when I did this. It will give you access to the android market!
2) Get any microSD card that you don't mind trashing the data on. There a LOTS of options out there, but I would HIGHLY SUGGEST getting a SANDISK, CLASS 4, 8 GB or 16 GB card. It is by far the most likely card to work well for you.
Also get a reader for your microSD card. I got one that plugs into my USB port and lets me see my microSD card on my desktop.
3) The first step is to install the .img file to the microSD card. First, you need to double click it on your desktop and let mac osx unzip it for you. It should do this nicely and your resultant file will be:
generic-sdcard-v1.2.1.img (i.e. the .gz at the end will go away)
To install the .img onto the microsd card, put the micro sd card into your card reader. It should pop up on your desktop as a disk. Mine was called “no name”.
To write the image (called burning the .img file to), you need to do the following:
-Find which drive the sd card is mapped to. To do this on mac, you can use the terminal:
how to open the terminal:
a) Go up to the magnifying glass in the top right of your mac.
b) Click on it and search for the word “terminal”. The first thing it finds should be a little black box with the word Terminal.
c) Click on that and a window should open on your desktop. That window should say something like Terminal – bash – 80x24 in the top line and then have a bunch of words, maybe something about Last login: and finally a line that ends in a dollar sign $. Here’s where you will type in your commands.)
Inside of that terminal, after the dollar sign ($) first, type:
cd Desktop
That will take you to your desktop. If you now type
ls
This should show you a list of all the files and folders on your desktop. All the terminal does is let you work with files using text commands rather than a nice graphical interface (i.e. clicking on windows and stuff)
Now that you know a couple basics on “terminals” type this:
diskutil list
This lists all the spaces on your computer where things are stored. You need to unmount the microSD card that you just plugged in. This will allow you to erase the card and put what you want on it. You need to look at this list and figure out which drive# is your microSD card. To the far right, you will see the disk size. Your microSD card should be around that same size as what you bought (for example, I’m using an 8GB card and found the disk that was around 7.5 GB).
Once you know the right disk (mine was disk1, yours may be different) unmount that drive by typing this:
diskutil unmountDisk /dev/disk<#>
(to be explicit, my drive was disk1 so I typed: diskutil unmountDisk /dev/disk1)
It should say: Unmount of all volumes on disk<#> was successful
Next type:
dd if=generic-sdcard-v1.1.img of=/dev/disk1
Everything needed should copy right over to the card. It took my laptop 140 s.
Now unmount the microSD card, but NOT the same way as what you just did. How? Remember when you connected the microSD card and a folder popped up on your desktop? Right click on that and select “unmount”. Note, it might be the case that the folder was renamed “boot”. If that’s the case, that is the folder to unmount.
After the microSD card disappears from your desktop, remove your microSD card from the laptop and plug it back in. The folder named “boot” should pop up on your desktop. Now the easy part.
Drag and drop the file:
update-cm-7.1.0-RCO-encore-2.6.32-beta3.1.zip or update-cm-7.0.2-encore.zip
Into the “boot” folder. Now right click on the “boot” folder and unmount.
Take out the microSD card and put it into the nook color. Turn the nook color on and it will boot. A little penguin might pop up followed by lots of techie looking things flashing on your screen. That’s fine. Keep an eye open and when its done, the screen will go blank. It should turn itself off, but probably won’t reboot. You need to hold down the power button for around 8 seconds to turn it back on. It will reboot into CM7.
(note: This is updated from prior CM7 installations (i.e. these instructions are specific to installing the CM7 beta). If your unhappy with the performance of the beta, you can install a CM7 version that’s labeled as “stable”. The stable versions occasionally need to be turned off manually (i.e. by holding down the power button for 8 seconds)).
You’re almost there. You should have a homescreen with a few icons. Find the one labeled “settings”. Open this up, go to Wireless & networks, and connect to your wireless network. Now CM7 is ready to go online and you can turn off the nook color and install the Android Market.
You need to turn off the nook color. Take out the microSD card and connect it to your computer again. This time, two folders will pop up. One called “boot” and one called “sdcard” or something similar
This time, drag and drop:
gapps-gb-20110307-signed.zip
into the boot folder. Now comes the second hardest part, booting into recovery. The process depends on the version you are installing.
If you are installing the beta version I reference above then put the microSD card into the nook color and boot into CM7. Once you’re in CM7, hold the power button until a menu pops up and choose to “reboot”. Choose to reboot into “recovery” and you should be all set.
If you’re installing one of the “stable” versions, put the microSD card into the nook color and boot to Recovery Mode. In order to do this hold the nook N key and press and hold the power button for ~5-6 seconds. It may take a couple of tries. The screen may turn off a couple times. You may boot into CM7 a couple times. Eventually, with luck on your side, you will successfully boot into “recovery mode” and google apps will be installed. Once you manage to boot into recovery the screen will flash up lots of techie text, similar to when you started CM7. It should go blank when this is done. At this point you can turn it off by holding power for around 8 seconds. Turn it back on, follow the screen instructions and you should be good to go with an android tablet with the full android market, all running from your microSD card!
Setup Wizard stuck?
I actually got this working on the first try a couple weeks ago and it was fantastic!
I was able to play netflix and flash for the first time, and now my dad wants me to do his nook the same way. He has a 16GB sd card though, and the original instructions didn't work on >8gb cards. I can't just image his SD card to my SD card because I couldn't get my google account to de-register etc, so I started from scratch with my card and planned to image to his before configuring any user accounts.
I'm having repeated trouble with my retry attempt though
Basic CM7 install with the generic-sdcard-v1.2.1 and update-cm-7.1.0-RC0-encore-2.6.32-beta3.1 (the ones recommended as of today in the instructions)
I set up wireless access, shut down, and backed up my card at this point.
Copy the current 20110307 gapps to the boot partition, eject, put it back in the nook, boot into recover (I've gotten good at this), it installs, shut down. Back up my card again as I figure this is where I'll want to start the other card.
Back to the Nook, boot up, get past the CyanogenMod scateboard screen, and it goes to "Setup Wizard". This should be for setting up the Google Apps Marketplace account I think, except it's completely black except for grey bar across the top with "Setup Wizard" on it, and the bar across the bottom with menu/back/search/battery indicator etc (these do nothing).
I can press power button and get only two options: shut down the tablet or reboot the tablet. I can rotate the nook and the UI changes orientation. Nothing else does anything as far as I can tell.
Anyone else seen this problem? I've searched, and even tried to post to the dev thread, but I can't due to low post count.
Help! (and thanks in advance!)
*.gz img file not recognizable & not zipped
Hi. I rooted my Nook with Autonooter and love using it. YouTube and all work fine, but I would like to redo with CM7. I have all that I need, except I'm caught with the img file this time round. It has an extension .gz. Win32DiskImager does not recognize it. Some sites say that it needs to be unzipped, but it's not zipped. I hate being stuck before even beginning. I hope that you can explain why I'm having this trouble. TY!
The .gz file is just a compressed .img file.
There are a number of Windows apps that can de-comress the file, for example: 7-Zip
Martyn
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
I saw this suggested: "I did a full format (not quick) and used WinImage to write the SD card instead. Works every time since then," by TL Jester here. I"m just curious why there always seems to be a roadblock.
sGooss said:
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
Click to expand...
Click to collapse
I had this same problem, i discovered that it created a partition on the sd card... I had easeus partition master home edition, which i used to resixe the partition and you can see your full 16GB then.
sGooss said:
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
Click to expand...
Click to collapse
I had an error message like this too. It turns out it was because I was trying to use the internal card reader in my laptop. I bought an external USB card reader, and it worked fine with the same card.
Originally Posted by sGooss View Post
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
babyfine24 said:
I had this same problem, i discovered that it created a partition on the sd card... I had easeus partition master home edition, which i used to resixe the partition and you can see your full 16GB then.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ditto, same problem, same solution. When you write the image to the card it seems to create a default boot partition of 117mg. When I tried to put both the rom and gapps in the boot partition after writing the image, I got that message (but not every time). So I made the boot partition bigger before adding rom and gapps, using Easus. I increased it to 150mg or so, that was plenty.
One time image+rom+gapps barely fit in the boot partition, and while installing I got an error that said not enough space in disc. I redid it, making the partition bigger, and it worked. I think the installation process may temporarily use some of that boot partition space.