Related
Hey had a question no one on other posts responded to me about. I have debian running on my phones, apps on my SD, Running JF 1.51 US with EXT2 since not too much needed on EXT3. But been seeing people making 3 partitions on the SD card. Fat32, EXT2, and Linux-Swap. Was wondering if anyone could fill me in more about if this is worth doing?
Also side question.. any real way to backup my ext2 to Windows XP or so to change out the SD card.. Call me impatient but I wanna use my class 6.. heh.. At work for another 5 hours.. otherwise I would just use Ubuntu at home like I did my 1st upgrade. I know a couple apps that moved it to the Fat32 portion of the SD card, but not sure if thats stable/advised. Think I should just wait till Im home to do it proper or is there a safe upgrade way now?
Also what size is everyone using as a standard EXT2 size on a 4GB anyways? I had mine set to 1 GB, is that too large? I just didnt want the G1 to run out of space.
Ok well finally sat down and upgraded it. So got everything setup and ready. However according to the posts I am reading.. I need a certain ROM build only?
So am I correct in assuming on JF 1.51 US I can not mount a linux-swap partition? Am I stuck using swapper? Can someone fill me in? Reading other posts atm but so far seems its all being used with 2 ROM sets which I dont plan on upgrading to. Only thing I see to try is this post http://forum.xda-developers.com/showthread.php?t=532188&highlight=linux-swap but if anyone has more info using JF let me know please.
Edit: Found my answer, http://forum.xda-developers.com/showpost.php?p=4070702&postcount=102 New test build which adds support for linux-swap partitions. While It may take a lil longer before it starts up unlike a init script on start up. Least this does auto do the job on boot and so far its working. The great solution for JF roms. =D
Ok, I've been reading the forum until my eyes are popping out. I can not find my situation. So please forgive but I've been searching.
Bought a NC for my daughter for the purpose of Rooting it using the SD method. I followed the routine install last Monday:
1. Using WinImage, I burned the Size-agnostic SD Card image on the SDcard (Transcend 8GB Class 6 SDHC) using my HTC Incredible as my card reader.
2. Downloaded cm_encore_full-131.zip and moved it to the card.
3. Installed the SD card and bam! Everything was working and I was happy as hell!
4. I went through the process and got gapps-gb-20110307-signed.zip installed and I was working away downloading apps and stuff.
5. Downloaded update-CM7-dalingrin-OC-sd-063011.zip and got that loaded and our NC was flying high. And since we have the right kernel, downloaded Nook Tweaks and we can use a case with a USB keyboard with no issues playing Angrybirds and everything. LOVING IT!
I was happy as hell cause I wanted to be done in my limited time before tomorrow because my daughter is staying with my mom and this will give her something to do.
THEN today after powering it off. I powered it back on again and the following happened:
1. It appears to attempt boot from the SD card.
2. The green Cyannogen logo comes up and under it it says "loading..."
3. However, instead of the Android on the surfboard coming up like before, it will boot up to the stock Android with the N splash screen first then to the stock interface???
I tried several times powering it on and off to see if it was just a glitch but it still did it. Soooo, I redid the whole process again. But once I tried to boot from the SD card with CM7 loaded, the same thing happens. Green logo, loading..., then back to the NC stock OS.
I tried downloading the image a few times to make sure it wasn't corrupt and reburned the img on the SD card, tried booting it again and still the same results. (I did this whole process at least 5 times!)
Sorry for the long read but I am frustrated and disappointed that i will have to tell my girl that it's not working like it was earlier. Can someone give me any advice to try? Or what can I possibly doing wrong? I'm beyond my skill sets at this point. The only thing that I can find on the forum is that it maybe the Transcend SD card but it worked find for three days. Can it really suck that bad after 3 days? I only have tomorrow to work it during the day so If I have to I'll go to Costco and get a Scandisk over there as some have mentioned, I will. But if there is something someone can tell me to try, please let me know.
Thanks in advance!
You are probably on the right track with getting a new SD card. One of two things happened: the SD card failed during the initial "burn-in" period or the Nook's reader slot did. The card is thebmore likely point of failure.
If the problem persists with a new card, get your Nook back to B&N for warranty replacement. Just don't let them have your SD cards an you won't lose all your work
P.S. Yes, ANYthing electronic can "suck that bad after just 3 days". If an electronic component is going to fail, it will either be DOA (and even cursory quality control will catch it) or it will fail shortly after being placed in regular service (burn-in). If it survives the first 60 to 100 hours of use, it will PROBABLY last for years.
Thanks DiDGR8!
I hear you on the electronic part. I was also really tired when I posted. I guess I just didn't want to believe that the card was the issue or rather could be the issue specially when I can read the card from my phone and read it from the NC in the stock interface. It had to be something I did or forgot to do. But I've seen stranger things happen. LOL Things can break.
As soon as I can, I will run out and get a new (Scandisk) card and I hope that it resolves the issue. I hope it is not the NC's reader slot because I hate going through the "returning process" plus we have to leave tonight.
I'll post my results as soon as I can today.
I often not to believe the uSD card itself is the problem but I guess this time, I believe it.
I have the same card as yours (Transcend 8GB class 6), testing random read/write small block and the result were about 0.08 (meaning bad). Sure enough, running CM7 off it last few days then I got ton of FC errors. I now then boot CM7 from eMMC and use the card as an external storage, the card still gives me some problems.
Try Sandisk and keep yours fingers crossed.
Well at least I'm not alone. Thanks votinh!
I wanted to avoid running it from eMMC so that if i wanted to I can do the warranty thing.
Well, I got me a Scandisk 4Gb Class 4 this morning in addition to a card reader/writer to eliminate my phone as a card reader.
Followed the steps and still the same thing. However, I did noticed this time some I/O errors come up during the installation process.
So, I let it go to stock so i can test my phoness SD card (Scandisk 2GB) and it worked just fine. So, I'm really stumped now.
I'm going to try flashing it again a couple of more times. I can go to B&N and tell them it is not working but if i show them it does work reading my phone's SD card. unless i just push them for an exchange.
OK, tried the the latest stable and now the Driod comes up and it is in a loop. I abandoned that all together. Need to stay focused.
So, I went through the process again using #133 on my Scandisk 4GB and tried to boot with it. Same results again Green logo, loading..., then back to the NC stock OS.
However, this time I was able to take a pic of the screen so I can copy what I saw when I saw I/O errors during the installation. So at one point I got:
end_request: I/O error, dev mmcblkl, sector, <insert number>: this flashed down the screen quite a bit
also
JB2: DetectedIO errors while flushing file data on mmcblk1p2-8
Ok so I went back to the Transcend card and did #132 but using my new reader. This time it seem to install clean. When I powered it back up, this time str8 to the "Read Forever" splash screen and back to stock. Weird.
So, I redid the 4GB card again and got the I/O errors again same thing the "Read Forever" splash screen and agian back to stock. It's like it's telling me to go F*** myself.
At this point, I'm thinking its the NC reader reading off the card itself. I tried 2 brand new cards, dif brand, dif reader/writers, multiple downloads of the img and installers...I don't know what to say. I should just root it to eMMC but if i'm having trouble with the SD method and I go eMMC and that messes up I won't be able to return it on Warrenty. What am I doing wrong? Can anyone give me anything else, I'm desperate and ready to fling it out the window. LOL
LOL I love the way I'm bumping my own thread here.
So, I went to B&N and got me a new replacement NC without any hassles.
I ran through the routine from scratch with CM7 #133 (which I believe has the OC kernel in it) on my new Scandisk 4GB Class 4 without the gapps.zip just to take it one step at a time.
I powered it on and prayed to the CM7 gods. I see the same I/O errors on the install and I also saw chown: cannot access '/tmp/backuptool.sh' : No such file or directory which I've seen before as well. However, this time the droid came up refreshing itself in a continuous loop. Like when I tried the stable version earlier. I did this twice and the same results.
At this point I'm thinking it maybe the WinImage. I'm using Winimage V 8.50? So, I downloaded Win32disk imager to give it a try and using my phone as the reader again because that was the last known combo. Again, the same errors. Then the Logo, loading…, this time blank screen…crickets…
I’m out of ideas…I had a clean install once on Monday worked fine until yesterday and I can’t do a damn thing.
Different SD cards, 2 brand new NCs, different readers, multiple downloads of image, installer, etc. Two dif imagers as well…Someone please tell me you are missing a step or doing something working because this does not make any sense… Booting in recovery mode maybe?
The only idea I have is a longshot. When you were getting the looping bootanimation (the blue Andy on a skateboard), or the "crickets"; how long did you wait before aborting the boot?
I have seen it take a LOT longer in those steps than I ever remembered (or thought reasonable). I'm talking 5 or 10 minutes.
It has something to do with recreating internal partitions and the dalvik cache (IIRC). It's been so long since I booted off the SD card, I'm not really sure what is supposed to happen that way.
Sorry that I can't offer more than "just let the first boot take all the time it wants".
It's all good. I understand.
So, Truth be told I think the first time with the "stable" image I let it go for 3 rotations before I said jumped ship. As I type now, I tried going back to #128 and it's doing it again. Andy has done skated across it at least 20 times...21... I'll let it run for a bit since you say that while I research the recovering to stock in emmc in case I decide to chuck it up and go emmc. This is driving me crazy. I would guess that emmc maybe more stable than running it from an SDcard.
You have got to be s***ing me. So I staied persistant and used my 8GB Transcend card again. This time it installed clean (I was taking pictures so I can read the damn thing) and booted clean. WEIRD!!!
I'm going to see if I can get my Scandisk to do the same.
I have seen mention that using the latest winimage is not a good idea, something about it not working right.
Version 8.1 is the usual recommendation.
I have been using the dualboot image racks11479 put together, and i've burned it with winimage a handful of times without issue, but always used winimage 8.1
Not sure if that's your issue, as i've never forayed into the realm of recent nightlies, but it could be a contributing factor.
Win32Disk Imager works perfect for me, even on win7 x64 and winimage would write, but the disk wouldn't boot.
Short story: Was running the latest (as of Dec. 4-5) ICS ROM(s) - the ones with the SD card bug - and my SD card appears to be shot.
Long story:
-----
I had been using the various betas of the ICS ROMs since I noticed Tytung's first Alpha was out and the ROMs had been improving rapidly. I guess when the headphones issue was fixed it caused problems with reading the SD Card which was documented and seems to be well known.
The constant SD messages didn't bother me much, but eventually I noticed launch icons missing and went to the Market to re-download one of the apps I use (I've been flashing so much, I wasn't sure which apps I didn't bother restoring). The Market app tells me I need a SD Card to install apps, so I just figured it's just the instability of the sd card mount for this latest batch of ROMs and I'll flash an older ROM off my SD card when I get the chance. I also noticed the messages started saying I inserted a blank SD Card but I brushed it off (couldn't look into it at the time).
I get home and find out Clockwork refuses to mount my card which means I can't easily wipe and install something else, so I switch to USB storage mode in CWM to simply transfer a ROM from my PC and my PC only sees ~30mb of my 16GB SD! I initially thought it was just some corruption but I tried all sorts of format and partitioning programs and nothing recognizes more than 30mb of space and none have even been able to format that little space that's showing.
I've been Googling for a while and came up with nothing I haven't already tried so I finally decided to post here. Is there any hope for my SD card? Being the holiday season and for once I've got most of my Christmas shopping done early, I'd rather not waste the little money I have left to run out and buy another SD card right away if it's not necessary.
-----
Does anyone have any ideas how I could fix this? I'd greatly appreciate it because I now stuck with WM6.5 and realize how much I didn't miss it for the past year
This is also a heads up for testers to be sure to upgrade their ROM ASAP (or at least to the kernel that fixes this) if they're on a ICS ROM with an SD card bug. I'm not complaining - I know this is a part of testing early builds (please ignore my sorry post count; I've been flashing for quite a while) - but there's no reason for others to go through this issue if it can be helped.
Have you tried EaseUS?
Sent from my LG-VM670 using Tapatalk
Yes,
Try Easus Partition Manager and/or MiniTool Partition Manager.
They can help but you will have to format your SD card I think.
Good luck!
I had the same problem. I plugged my card into a USB reader after it working error free, it then said it needed to be formatted and was only showing 30mb. After formatting repeatedly it still doesn't read. I haven't retired any positioning software but i think the card may just be done with.
Sent from my HD2 using XDA App
probably you'll need a replacement.
have you tried the SD formatter? there's like a 0.000001% chance it will work in your case, but why not try it?
Hey everyone, this is my first post here. I just did my first cm7 root, via sd card image, and everything went fine except that I didn't partition it correctly, since it says ive only got like...32mb left on my 4gb sd card.
Is it too late to go back and complete that step? Or will it wipe everything and i'll have to start from scratch. I hope that's not the case, but I've only got room for one app -__-
Im not even sure this question makes sense...that's how much of a noob I am with this stuff.
If anyone can give me some advice, i'd greatly appreciate it!
Oh, also...no preloaded android market? How do I go about getting that?
Us the Mini Tool Resize function to increase the 31MB to include the unallocated memory.
How are you judging you only have 32MB space left?
If you have installed CM7 onto the SD card rather than internal then putting the card back into the PC will only show the boot partition which is small (normally around 114MB) but the rest of the card will be available for apps downloading.
As it sounds like you haven't got far with loading apps etc I would recommend actually repeating the install process from the beginning using the guide here as it is very quick to do.
http://forum.xda-developers.com/showthread.php?t=1000957
The VeryGreen installer will automatically partition the card for you appropriately and for a 4GB card will leave you with about 1GB for downloaded apps and over 2GB of space for media.
To get the market you need to flash the gapps package referred to in the guide.
For the base ROM I would actually use the KANG MiRaGe ROM as this has all the latest fixes in. Just make sure the zip is renamed to start with update-cm- before putting it on the VeryGreen card for the install.
Thanks guys! I'm going to go ahead and follow your advice bobtidey.
Much appreciated
I have a nice step by step in my signature (mainly because people kept having trouble with WinImage).
Hi,
I just bought a nook color. I'm trying to install nightly cm9 on it. i have been reading and i have some questions .. please help i don't wanna turn my new nook into paperweight lol. I understand i need to make a bootable sd card with CWR on it. i understand there are newer version CWR out there now but I am only able to find 4gb version of 3.0.2.8. Will that cause a problem ? Do i have to use 4gb version CWR? I can find 1gb CWM 3.2.0.1 ( i have a 4g micro sd card ). About wiping, i know with android phones you always wipe before you flash roms but i have been reading, posts suggest to wipe cach and dalvik AFTER flashing cm and gapps. Is that the correct order to wipe? [GUIDE] Install CM7 or CM9(!) + Clockworkmod to EMMC - ALL NOOKS! (Updated:1/16/12) - xda-developers This post don't even mention wiping dalvik. So what exactly should i wipe and in what order? Also in that post it says after you flash, without rebooting you are to remove sd card and format it on a computer... since its a bootable CRW, the nook color doesnt even have the recovery on it , will removing the sd just cause it to crush ? Please help ~ Thank you.
Best advice is to go to the "development forum" and read the CM9/ICS nightly thread.Everything you need is in the first post.I would suggest you test your SD card with CrystalDiskMark 3.0(free program,google it up)first to see if it is suitable for a ROM install.
See the SD card strange thread in this forum first.
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Thanks and what is the "telephony permission fix" ?
bobtidey said:
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Click to expand...
Click to collapse
Found the telephony fix thanks
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
I already have cm7 on my phone , hopefully its not gonna be the same thing lol . i was hoping to put cm9 on there so it will entertain me for a while but if its really that buggy mb i will consider just running on cm7.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
Thanks. I already have bobzhome 7.2 on my phone. The reason why i wanna cm* on my nook is because i don't read(i read enough for school XD ) haha so the nook factory rom will be kinda pointless for me. Also just booting from sd and flashing roms seem really straight forward to me so that's why i want to flash cm* on internal memory. As im not that knowledgeble about nook colors, running on a bootable rom still seem complicated for me but i sure will think about it .
brentb636 said:
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
Click to expand...
Click to collapse
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
optimusv45 said:
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
Click to expand...
Click to collapse
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
just making sure since im not very knowledge about nook colors. i rather ask more than do something stupid on my device and cause myself problems.
Benzoman said:
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
No problem. Just noticed it was in a separate thread already.
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Dual booting SD
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
I posted what a/v already. its kaspersky internet security. i guess i never look into running off SD. I don't read much so i just don't need nook color stock ROM, i guess that's also part of why i wanna run on internal memory. oh and i bought a refurbished nook color from BNs website and it came defective. part of the screen didn't work. To those who wanna buy it from them i suggest to buy from a retail store so u don't have to pay shipping and waste time I think all they did was a factory restore on a return and sell it again for 149.
TL2000 said:
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Click to expand...
Click to collapse
Im gonna buy a new nook color and i read that newer ones have different hardware. newer hardware aren't supported by CM7. I guess I'll have to try a nightly CM9 build.
The1Power said:
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
Click to expand...
Click to collapse
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I just bought my nook color Dec. 30th, 2011 and I have ran cm7 as well as cm9. Like the others are saying, set up cm7 off of a SD card until you learn what you are doing then consider moving to the emmc.
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I believe that is CM9, not 7 that was having issues with the new nook color touch screen drivers.
Here's a post about it:http://forum.xda-developers.com/showthread.php?p=21333209&highlight=touchscreen#post21333209
Looks like it may already be fixed: http://forum.xda-developers.com/showthread.php?p=21353661&highlight=touchscreen#post21353661