ok so my girlfriend got a nook color for christmas this year and heard you can put honeycomb on it. i did it and all went well BUT she has no market and i have no idea how to use adb and her nook isnt even recognized. i tried the easy adb usb nook installer thing and it wont work. now i tried to format my sd card to use as a regular 4gb card and i only have 117 mb left!!!! i have no way to fix it and i just bought it today from walmart. it was only 10 bucks so no big loss but still its 4gb i couldve used. is there any home to reformat correctly to get it back or any way to completely uninstall android sdk and adb and the drivers and redo it over and can anyone help me as to making the market work if possible? i installed the honeycomb image to the sd card so i dont ruin her nook and i dont plan on flashing honeycomb to the actual nook. i need help asap so please anyone on the website help me!!!!!!
sneakysnake16 said:
ok so my girlfriend got a nook color for christmas this year and heard you can put honeycomb on it. i did it and all went well BUT she has no market and i have no idea how to use adb and her nook isnt even recognized. i tried the easy adb usb nook installer thing and it wont work. now i tried to format my sd card to use as a regular 4gb card and i only have 117 mb left!!!! i have no way to fix it and i just bought it today from walmart. it was only 10 bucks so no big loss but still its 4gb i couldve used. is there any home to reformat correctly to get it back or any way to completely uninstall android sdk and adb and the drivers and redo it over and can anyone help me as to making the market work if possible? i installed the honeycomb image to the sd card so i dont ruin her nook and i dont plan on flashing honeycomb to the actual nook. i need help asap so please anyone on the website help me!!!!!!
Click to expand...
Click to collapse
You should do some more research. Honeycomb on the nook is no bueno. You can use gingerbread with no problems. ICS is being updated daily, still some things not working. To format your micro sd card you can use SD Formatter from Sandisk. Try cm7 on your sd card. Works great. My girlfriend has very few problems, she is very happy.
Sent from my Xoom using Tapatalk
Oh ok thanks for the info I fixed the sd card.she will be happy to hear it might work cause I explained to her how annoying it was... Now do I have to flash anything to the nook itself? And is there any way to restore it in case it messes up? If possible id like it all done on the sd card and I could get an 8gb easy, and I could try for a 16 if necessary. Thank you for the quick reply too really helped
Sent from my SGH-T959 using XDA Premium App
Honeycomb in general is a no-no. The Honeycomb ROM you got was based off of SDK. Google never officially released the Honeycomb source code. As for your problem, I'd need more info. You could always wipe your SD and go to Wal-Mart, asking for a trade-in. If they plug it in, act dumb and say it came that way. Go with the latest CM7 nightly. CM9 is in a rapid change state at the moment, so unless you can build a ROM based off of source, I'd wait until CM9 becomes stable. For now, look into the ROM that would suit her. MIUI is well-supported and sort of resembles iOS. CM7 is strictly Android. Phiremod is nice but is officially unsupported because its developer decided to leave his Android life. Hopefully, someone else takes the reigns from him. My suggestion for you for now is either CM7 or MIUI.
I used to have a forum signature... then I took an arrow to the knee.
sneakysnake16 said:
Oh ok thanks for the info I fixed the sd card.she will be happy to hear it might work cause I explained to her how annoying it was... Now do I have to flash anything to the nook itself? And is there any way to restore it in case it messes up? If possible id like it all done on the sd card and I could get an 8gb easy, and I could try for a 16 if necessary. Thank you for the quick reply too really helped
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Personally I'd flash a ROM to the Nook. If you want to run CM7 completely off of SD, things get more complicated. For now, give her a ROM. If she likes the look of an iPod, go with MIUI. Otherwise, flash CM7 (the latest stable should do). Make a recovery after you flash and about once every week or so. I suggest getting an SD card for just recoveries. 2GB should do and when you need to delete old recoveries, just hook up to your computer, find the directory in your SD labeled "clockworkmod", open it, and delete the folders that hold the old recoveries. Most are named based on the date and time they were created.
I used to have a forum signature... then I took an arrow to the knee.
First, there is probably nothing wrong with your SD card as I think you have now found. When you make an install that is designed to run off the SD card the process partitions the card into various areas. Windows can only see the first partition which is the boot partition of 117 MB. Other partitions hold the system, data and "SD" areas and the Nook will see all of these and can mount the "SD" area as visible to the PC when connected by USB.
Various utilities are available to put the card back to a single full capacity partition. E.g. the HP utility or the Sandisk utility as mentioned.
I'd certainly follow the advice given on ROM selection. If you choose to use the CM7 type then the ROM build under the KANG MiRaGE thread is the best choice at the moment.
Although installing to emmc internal is nicer in many respects there are also lots of people here who have chosen to run on SD because they wanted to leave the Nook stock software unaltered. Providing you use a SanDisk card this will give good results, running fast and stable and does not alter the internal Nook software so you can just remove the card to get back to the standard Nook.
I started like this but then decided that I was never going to use the stock and eventually flashed into internal. For non-technical friends who want the CM7 experience on their Nook I normally use the SD card method as it then means they have an easy path back to a standard Nook.
If you want to run from the SD card then reformat your card back to full capacity, choose which ROM you want to use then follow the SD card install guide.
http://forum.xda-developers.com/showthread.php?t=1000957
Yea I used a sandisk card and I fixed mine thanks as for installing cm7 I would like it on the sd card becauae if she doesnt like it then idk how to return it to normal...
Sent from my SGH-T959 using XDA Premium App
bobtidey said:
http://forum.xda-developers.com/showthread.php?t=1000957
Click to expand...
Click to collapse
This ^^^. I have flashed cm7 to my gf's emmc, somehow, by accident in the past. I took it back to stock with the help of a thread in the dev section. Not a problem. It seems pretty hard to screw up her nook. She loves cm7 over stock. Actually, I used the cm7.2 kang. Runs really well on the sd card. If there is ever a problem, pull the sd card and start over. Always have current backups of apps/data. Good luck.
Sent from my Xoom using Tapatalk
ugh, I feel stupid, having the same issue with the sd card. Can someone gimme the link for the sd formatter? I tried the hp utility and it didnt change any thing. Thanx guys.
Actually, the stock B&N operating system has a nice SD card formatter. You just put in the SD card after turning on the Nook, go to Device Options from Settings, click on the SD card option, and you can format/wipe it from there.
Under Ubuntu, I use gparted.
For Windows, I don't know which one is the best, but when I had the same problem, I used MiniTool Partition Wizard
std5501 said:
ugh, I feel stupid, having the same issue with the sd card. Can someone gimme the link for the sd formatter? I tried the hp utility and it didnt change any thing. Thanx guys.
Click to expand...
Click to collapse
std5501 said:
ugh, I feel stupid, having the same issue with the sd card. Can someone gimme the link for the sd formatter? I tried the hp utility and it didnt change any thing. Thanx guys.
Click to expand...
Click to collapse
Use MiniTools Wizard
votinh said:
CM7 - nb230 on eMMC - Dalingrin's OC kernel 2.6.32.9 @ 1200MHz NOOKcolor
Click to expand...
Click to collapse
I can't help but notice you have it clocked to 1200MHz. No criticism, and it's purely your choice, but clocking to 1200MHz isn't actually... well, I guess the word is, "beneficial". Personally, I'm clocked to 1100MHz, and I'll tell you why. Clocking the Nook at 1200MHz makes it: 1) Overheat very easily, 2) Drain through battery like a b***ch, and 3) It has no noticeable increase in performance. I'm not the only one out there who has noticed this either. But I can't dictate you and make you change it. Just informing you that Dragons may be ahead of you. If you don't have any of those problems, then so be it. If I were to recommend my opinion for overclocking settings, I'd say 1100/1100 min/max set to interactive or interactiveX. It seems counter-intuitive, but I know of an article (for the life of me can't find the link, LeslieAnn posted the link in one of her replies to an LG Optimus V thread) where a developer did tests at different clocking settings. From his findings; overclocking is better than underclocking, minimum clock setting has a really miniscule effect on the idle power consumption, and setting min & max settings at the same step provides the most balanced power-performance ratio. Anyways, I'll look for the link and see if I can find it.
worldindo1 said:
I can't help but notice you have it clocked to 1200MHz. No criticism, and it's purely your choice, but clocking to 1200MHz isn't actually... well, I guess the word is, "beneficial". Personally, I'm clocked to 1100MHz, and I'll tell you why. Clocking the Nook at 1200MHz makes it: 1) Overheat very easily, 2) Drain through battery like a b***ch, and 3) It has no noticeable increase in performance. I'm not the only one out there who has noticed this either. But I can't dictate you and make you change it. Just informing you that Dragons may be ahead of you. If you don't have any of those problems, then so be it. If I were to recommend my opinion for overclocking settings, I'd say 1100/1100 min/max set to interactive or interactiveX. It seems counter-intuitive, but I know of an article (for the life of me can't find the link, LeslieAnn posted the link in one of her replies to an LG Optimus V thread) where a developer did tests at different clocking settings. From his findings; overclocking is better than underclocking, minimum clock setting has a really miniscule effect on the idle power consumption, and setting min & max settings at the same step provides the most balanced power-performance ratio. Anyways, I'll look for the link and see if I can find it.
Click to expand...
Click to collapse
You know what? I'm here to learn too so any new idea, new knowledge, ..... all are welcomed. Once again, thanks.
Just I thought that at one point, we, dev. concluded that 1200 is best, not 1100, not 1300. That's the reason why I set 1200. Personally I haven't set to anything else beside stock 800 and OC 1200.
Since you said so, I will set it to 1100 and see if any better.
Thanks again, m8
Just get a new sd card here for 8 bucks: http://www.dailysteals.com/
16 gb class 4.
Only good for today.
Go download EaseUS, the free trial. It helped me expand my 16gb sandisk to full capacity after I imaged the files I wanted. EaseUS got a great rating on CNET. I figured out what I needed to do without watching the tutorial video.
If only I could get my nook to actually boot now :/
The EaseUS tool works like a charm. Thanks for the info. I got my 16GB back now...
I messed up my 32GB Sandisk (4) sd card too. It crashed running CM7 (no idea why) and I tried to reformat it using mini as suggested and then reinstall CM7 on it. It would not reformat to FAT32! So, then I wiped it, which maybe was my mistake. Anyway, now I can see the card in mini but checking the properties I see that it's all f'd up. Basically I can't format it as anything, number of cylinders appears to have changed, etc, etc. I have no idea what I did to it! Obviously, my knowledge on this subject is limited. I've learned how to create partitions, define or extend them and so on but know very little about how these little buggers work.
Since it cost about $25 on sale I'd like to fix it, if possible. Anybody have any ideas about how to fix or where I can go to learn? Does this problem have to do with the master build? I see that option in mini but don't understand what it is!
Sorry for being so stupid. I bought a new 16GB card and successfully made a new CM7 sd and restored apps using TB and content from my PC (thank god I had the presence of mind to back that stuff up)! I sure would like the extra 16GB back though....no $$ in the budget for anything more than the 16GB I bought.
I know this is sort of wandering from the OP but since others were discussing f'd up cards (albeit more easily repaired) I thought it would be ok. Feel free administrator, to redirect me if I should start new thread in Q&A. I did surf there and ran a global search of the NT threads and this was the best of four pertinent threads I found.
Snooch
Sent from my Nook Tablet using xda app-developers app
But this is a nook color thread.
Everyone here uses burning software to put bootable NC images on the device and it fixes it. Not sure if such things exist on the NT. Best to search there.
Hi All
I've been using ICS since pretty much day one when i bought the phone.
I realized the USB transfer speed when I copy files is very low.
in my phone around 1.3MB/s and on another 1.9MB/s
both are incredibly slow.
Could you guys help me determine whether this is a problem only affecting my phones, or is something ICS related?
Seems to be ICS related, many threads saying the same problem. I'm getting a middle-ground speed personally on ICS.
If you want to transfer large files, you might prefer doing it via mounting the sdcard through recovery (assuming you have a custom one, don't think stock can do this).
It is Google who may completely solve this problem...
Harbb said:
Seems to be ICS related, many threads saying the same problem. I'm getting a middle-ground speed personally on ICS.
If you want to transfer large files, you might prefer doing it via mounting the sdcard through recovery (assuming you have a custom one, don't think stock can do this).
Click to expand...
Click to collapse
nope, GB has this problem too.
i opened a thread about this on the google support forums, but didnt get any helpful answers. nobody know how to solve this.
the transfer-rate just stays around 1.3 mb/s, tops (for me at least). this is painfully slow. i'm pretty sure google locks the speed somehow, for whatever reason.
on my n900 i get my usual 10-12 mb/s write speed, no matter if internal storage or microsd. why cant the nexus do this?
I wonder whether thee from devs are aware of this. Should be able to fix it.. how can we let them know?
I'm fairly certain the devs are aware of this. Maybe the CM team has something in mind here, i havn't tested sd speed on any CM9 ROM - or maybe they need some notification. It may not be a "bug" in the common sense, but possibly a series of underlying issues which increase the transfer rate. Maybe I'll test some things later to see if i can get a better idea on what is the cause.
For the record, I could get around 3-4MB/s on GB, i get around 2.5 - 3MB/s on ICS. In recovery i get closer to 4 - 4.5MB/s. The flash memory inside the Nexus S is quite slow write-wise, sadly. External SDCards rely entirely on the Class it is in, C2 will be very slow, C4 faster, up to C12 or whatever they have now which are happy to write Full HD video in real time.
got the same prob since beginning of the ics era ...
I was just messing around with the phone, unlocked bootloader, am about to install PACMAN rom to test it out to see if it's faster than stock one.. this because my phone became increasingly slow as I used it more. And I've only had it for 2-3 weeks..
I even rooted a week ago or something to remove all the bloatware to try and make it faster but didn't really notice too much diference..
Now while I was preparing for pacman (copying backup to pc and whatnot) I removed the SDcard and BAM... phone is back to it's original speed! which is really good...
If I had a lot of apps on the SDcard I'd understand it.. but I dont.
It's a class 4 microSD from Kodac, 8Gb. around 4.4 gb of music and respective cover images and not much else... what could justify that phone was so slugish with it mounted??
SrPintas said:
I was just messing around with the phone, unlocked bootloader, am about to install PACMAN rom to test it out to see if it's faster than stock one.. this because my phone became increasingly slow as I used it more. And I've only had it for 2-3 weeks..
I even rooted a week ago or something to remove all the bloatware to try and make it faster but didn't really notice too much diference..
Now while I was preparing for pacman (copying backup to pc and whatnot) I removed the SDcard and BAM... phone is back to it's original speed! which is really good...
If I had a lot of apps on the SDcard I'd understand it.. but I dont.
It's a class 4 microSD from Kodac, 8Gb. around 4.4 gb of music and respective cover images and not much else... what could justify that phone was so slugish with it mounted??
Click to expand...
Click to collapse
It may be that your phone was constantly scanning the SD card for media. Other than that I wouldn't know.
Sent from my XT907 using xda premium
Stock, unrooted, 16GB, original Nexus 7 (with plenty of free space 6GB), but over the past few updates it has slowed to a crawl. I have wiped the App's caches and cache partition (which help for a short while), but it is still painful to use.
It is running 4.4.4 at the moment, and am wondering if a full reset will actually help for the long term. I thought the whole idea of KK was to improve performance on less capable hardware. If that is really the case, something is horribly wrong on mine.
Note that I have no interest in rooting or flashing unless it is absolutely necessary.
My original Nexus 7 with 8gb has recently been horribly slower too. I am rooted and running the latest official release of CyanogenMod. I have over 1 gb free. I am guessing this problem is fairly basic or low level and that (hopefully) others are seeing it too so it can be fixed.
16 GB and it can get painfully slow, at times.
I uninstalled Facebook which made a world of difference, and now I can reboot when it crawls to get it back to decent speeds.
Yeah, rebooting it helps, but only for a short while. So none of you have recently done a factory reset?
Sent from my XT1095 using Tapatalk
Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Alex338 said:
Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Click to expand...
Click to collapse
That's so odd for someone on the bleeding edge to have issues. Give it time
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
dontbeweakvato said:
That's so odd for someone on the bleeding edge to have issues. Give it time
Click to expand...
Click to collapse
I'm impatient. They've had a whole day to work out the bugs
Pain-N-Panic said:
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Click to expand...
Click to collapse
Yeah Feb factory image was basically perfect for me. I don't use Bluetooth much so didn't have any of those issues. I had no issues flashing, but like I said I'm stock with no root, so no twrp to worry about. And yes we buy these phones to experiment!
Update: Had the phone completely freeze on me. First it lagged like crazy and wouldn't respond to touch, then screen went blank. Had to hold down power until finally it shut off. Seems to be fine after a reboot. I definitely never had anything like that happen since I got the phone. Hopefully it was some random one off bug!
quantumqweef said:
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
Yep I'm aware of all that. Like I said, not really a complaint, more of an observation.