Where is our v1.4? - Nook Color General

Hey guys with the release of the Nook Tablet and the price reduction of our brethren color, where is our 1.4 rom update? I assume the NT is already running it as well as any new NC. Should we be concerned the 1.4 update may lock up our bootloaders like the NT is?

Its not out for the NC yet. Reports said December.

Your signature indicated you're running CM7.1, why care about the 1.4, which is probably Gingerbread 2.3.5?

I am but I've considered dual-booting stock firmware alongside, especially with the newly added features of 1.4 . Aside from that I just like to play with roms, I didnt have 1.3 on my device for more than 72hours before I stuck cm7.1 on it.

Don't jump on v1.4 too fast...
It could have locked down the device to where dual boot & CM7 are not usable...

BKKKevin said:
Don't jump on v1.4 too fast...
It could have locked down the device to where dual boot & CM7 are not usable...
Click to expand...
Click to collapse
It's more likely to make unicorns fart rainbows than do that, but okay...

That there is funny...LOL!

BKKKevin said:
Don't jump on v1.4 too fast...
It could have locked down the device to where dual boot & CM7 are not usable...
Click to expand...
Click to collapse
If it does lock it down, can it still be unlocked to original status?
Sent from my NOOKcolor Android eReader Tablet

gsutton said:
If it does lock it down, can it still be unlocked to original status?
Sent from my NOOKcolor Android eReader Tablet
Click to expand...
Click to collapse
If you still have the stock ROM installed I would assume you could still do a factory reset and then avoid any OTA updates.

BKKKevin said:
Don't jump on v1.4 too fast...
It could have locked down the device to where dual boot & CM7 are not usable...
Click to expand...
Click to collapse
That isn't likely. The board attempts to boot the first partition of sd or emmc (if its vfat). It loads MLO then u-boot.bin. They "could" lock down either with an update, but you could simply boot sdcard and replace the ones in /boot with non-locked versions. You don't have much to worry about with this device.

d0nk` said:
That isn't likely. The board attempts to boot the first partition of sd or emmc (if its vfat). It loads MLO then u-boot.bin. They "could" lock down either with an update, but you could simply boot sdcard and replace the ones in /boot with non-locked versions. You don't have much to worry about with this device.
Click to expand...
Click to collapse
What if they updated the bootloader to stop it from looking for the SD card first. The nook tablet doesntsearch for SD card first does it?
Sent from my NookColor using xda premium

psychoace said:
What if they updated the bootloader to stop it from looking for the SD card first. The nook tablet doesntsearch for SD card first does it?
Click to expand...
Click to collapse
The Tablet does check the SD card first, however it's checking for a signed boot image there just like on the internal memory. The only signed image you could possibly run at this time is one copied from the internal memory, but the mount points in that image point right back to the partitions on the internal memory so it wouldn't look like you've done anything differently.
From what I gather, SD boot is in important part of B&N's service setup for these devices as it allows an in-store employee without tons of Android tech support training to stick in a special SD card and boot straight into reformatting tools, etc no matter how badly someone messed up their software.
Can you even flash a bootloader on these devices? My only experience with devices where you could flash something lower level than recovery is my HTC phone and it's hboot but that device is setup very differently than these tablets

Related

how to flash a new room to an already rooted phone?

Hi
I have flashed my G1 T-mobile following the the one-click process in here! i have now root access. The ROM is CyanogenMod-3.9.11.2
After all that i bought a trascend SDcard 8GB class 6, formatted about 600MB to EXT4 using gparted on a live cd, winxp and my G1.
The first thing i noticed is that the phone is slower to load up. it stays about 35secs on the G1 logo and then move to android for a total of about 1min to be ready.
Second thing my free space on internal memory went from 38MB to 68MB, i believe somehow the phone moved the cache on the sdcard...if i install new programs they get installed on the phone memory as far as i understand...however i could be wrong on this. i never started the phone without sdcard since, I'm not sure if this could damage the phone in some way.
I would like to have some feedback on this (the slow boot and memory thing) if someone has experienced a similar situation.
I'm thinking to flash my phone again and move to a stable version of Cyanogen so that i can use app2Sd and Cyanogen updater!!
- how can i flash a new room, considering that i have the latest radio but not HARDspl. (as far as i understand the oneclick method doesn't change the SPL)
I was looking at using again the small oneclick software and flash the Cyanogen 4.0 this time, would that make sense since i have already root access on the phone?
thank you for the help
kirk
update
After installing and unistalling few softwares i found out that all programs are actually on the SDcard however the Mobile uses still the internal memory for the cache. This doesn't bother me for now since i still have about 68MB free. Basically if you install CyanogenMod and you don't have a partitioned SDcard all software get installed on the internal memory however as soon as you put in an partioned card all programs get transfered automatically after the first boot. At least this is what happen to me. Somehow i got what i wanted and because of this i don't need to flash my phone anymore... maybe I'll flash it again when android 2 is out, if i don't have to change spl, image recovery or anythingelse too risky
I used the 1-click method as well, and I just download the latest cyanogen rom, rename it to update, boot into cm-recovery and apply the update.
One more thing, the latest versions of Cyanogen's rom have auto apps2sd built into the rom. It will automatically move all apps to the sd card as long as you have an ext2/ext3/ext4 partition on your sd card.
Your still going to have the same boot time. It's still going to take awhile to boot, just because you have a custom rom doesn't mean it will boot faster. And to load a new rom either rename to update.zip and update or if you have the newest recovery then you can just flash whatever rom without renaming because you can flash any .zip file.
In reading your post I think you said you wanted to use the small 1 click software to download cm4.0 You are done rooting your phone you no longer need to use the 1 click software.
Just copy new rom (cm4.0.4) to sd card
unplug phone from computer
turn off phone
boot into recovery (home and power at the same time)
flash new rom
when you use one root, it flashes cm-recovery 1.4 so there is no need to rename, just put on the root of your sd and flash from recovery
supremeteam256 said:
Your still going to have the same boot time. It's still going to take awhile to boot, just because you have a custom rom doesn't mean it will boot faster. And to load a new rom either rename to update.zip and update or if you have the newest recovery then you can just flash whatever rom without renaming because you can flash any .zip file.
Click to expand...
Click to collapse
Are you aware of any reason for the slow boot after partition of the sdcard??
is it the stock 1GB sdcard?
Cause it has to read from the sd during boot up and it has to run the script for the apps2sd
Fingerlickin said:
is it the stock 1GB sdcard?
Click to expand...
Click to collapse
no is a transcend 8GB class 6.
gridlock32404 said:
Cause it has to read from the sd during boot up and it has to run the script for the apps2sd
Click to expand...
Click to collapse
As far as i know i'm not using app2sd yet. I partitioned my SDcard ONLY after i flashed my phone. however like i said i think the phone is somehow using the ext4 partition for something.
You reckon this would be a normal boot time i mean it takes between 50secs and 1.05 min to be ready. Phone is stable as far as i can tell.
I myself am not concerned with the boot time, the ext4 is another filesystem that it has to read and recongize, you basicly have a little mini computer in your hands so how long does your pc take to load up, there are many files and system checks that it has to go through starting up not to mention all the settings and components it has to turn on
Bottom line, if you want something to boot up quickly than get a basic phone because there is a very good way to speed up a mini computer to do the same
gridlock32404 said:
I myself am not concerned with the boot time, the ext4 is another filesystem that it has to read and recongize, you basicly have a little mini computer in your hands so how long does your pc take to load up, there are many files and system checks that it has to go through starting up not to mention all the settings and components it has to turn on
Bottom line, if you want something to boot up quickly than get a basic phone because there is a very good way to speed up a mini computer to do the same
Click to expand...
Click to collapse
Well i'm aware of all this and i'm not concerned too much about the boot time. I'm only trying to gather information and learn a bit more from other ppl experiences. I come from windows mobile and android OS is all new world for me.
have you a similar configuration to my G1? Do you run app2sd? is yor boot time similar to mine??
maybeoneday said:
Just copy new rom (cm4.0.4) to sd card
unplug phone from computer
turn off phone
boot into recovery (home and power at the same time)
flash new rom
Click to expand...
Click to collapse
Just a quick question for future reference...
do i need to put Cyanogen recovery image on the root of the sd card when i boot into recovery mode?
thank you
Kirk
Why did you root your phone? You have no desire to search to even do one of the most well documented things to your phone in these forums. What you need to do is take a DREAIMG.nbh file and put it in the root of your sdcard (or in no folders), then open up terminal emulator and type su then reboot bootloader once that happens wait for it to flash that image. Then you will have the most pimping room on your phone. Also you have amazing boot times. Everything you want.
david1171 said:
Why did you root your phone? You have no desire to search to even do one of the most well documented things to your phone in these forums. What you need to do is take a DREAIMG.nbh file and put it in the root of your sdcard (or in no folders), then open up terminal emulator and type su then reboot bootloader once that happens wait for it to flash that image. Then you will have the most pimping room on your phone. Also you have amazing boot times. Everything you want.
Click to expand...
Click to collapse
Hi David
I had specific reason to root 2 different G1 and this is not to play with it or try a new ROM or even experiment new things. I may change my ROM again when a major relase is out (i.e. Android 2 if it has something that i need)
Going back to reflashing the phone.
You now suggest me to use DREAIMG.nbh which is actually mentioned on the guide "hoe to downgrade-root-flash your phone" here
....am I missing something here?? thank you for taking the time to reply anyway.
..I have read quite a bit on this forum and i decided to use the one-click method (because is the quickest and safiest one). I thought reflashing should be as easy. go in safe mode wipe and reflash it. Anyway for my nature i tend to ask/investigate one thing before go and actually do it. My questions are:
- if i press home power right now, considering that i have nothing on my sdcard would it take me to the safemode screen?
- Consequently do i need to have Cyanogen image revovery together with the ROM on my sd card in order to flash a new version of CyanogenMod?
Thank you
Kirk
you can boot into recovery at any time by pressing home and power when the phone is powered down. it will go into recovery no matter what is on the sdcard.
Also the recovery image you have on your phone does not determine what rom you can flash.
wow... i am at a loss for words...... do you even know why you did any of the things you did? did you even read the release notes for cyan's rom's? ALL OF THE ANSWERS TO YOUR QUESTIONS ARE THERE...
if you have an ext partition on your sd card....it WILL AUTOMATICALLY be used for apps2sd with 80%-90% of the ROM's out there today... ITS IN ALL OF THE ROMS' CHANGE LOGS/RELEASE NOTES
I had specific reason to root 2 different G1 and this is not to play with it or try a new ROM or even experiment new things. I may change my ROM again when a major relase is out (i.e. Android 2 if it has something that i need)
Click to expand...
Click to collapse
if you didnt root to try a new rom or experiment with new things, your better off with the stock firmware...which is why david suggested you flash DREAIMG.nbh
go in safe mode wipe and reflash it
Click to expand...
Click to collapse
going into safemode wont flash anything.... i suggest you search and find out what exactly safemode is, especially since there was a thread only a few threads below yours detailing it.
All you need to flash a new ROM is the rom on your sd card and a working recovery, as well as anything that the ROM your installing has required which are noted in the changelog/release notes....
nothing else is needed on your SD card, except maybe specific partitioning, which will be noted in the ROM's requirements.
I try to help out here as much as i can when i have time (most of my posts are in Q&A helping out people) but it seems as though no one even bothers to look at the actual forums anymore. They just create an account, create a thread, bug people till a simple question is answered, and disappear forever.....
I came to this site simply to get roms, but i stayed because there was so much to learn and i created an account to help out people as well...i did all of my major modifications without asking any questions....all the questions are already answered somewhere...
i understand its hard to go through all the clutter, but it is starting to look as if no one even cares anymore
@B-man007 i am starting to feel like you do, i had my phone rooted and all that good stuff at least a month before i made an account just to download something uploaded to the forum. I wish i could see how many post i have in a ceratin forum bc i imagine at least 450 or 500 of them would be in this one helping people. Its getting to the point where i no longer care to help people and i thought i had a lot of patience. I porbably do but people are sinking to new lows with the questions they ask...
I think I have maybe 5 posts in dev, most of my posts are q&a and general, but then again half of those posts are from hijacking threads. I just got tired of answering the same questions over and over and over
gridlock32404 said:
I think I have maybe 5 posts in dev, most of my posts are q&a and general, but then again half of those posts are from hijacking threads. I just got tired of answering the same questions over and over and over
Click to expand...
Click to collapse
u hijack the hell outa threads. there should some type of entrance exam for xda. like do u know how to search, can u read do u have a brain. i mean god i actually helped a guy who couldnt open the terminal

Nook ver 1.2 and 1.3 can't upgrade after downgrade

When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
It says there is no storage because you are not on 1.2 or above. Just update manually through BN.
---------------------------------
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
It says there is no storage because you are not on 1.2 or above. Just update manually through BN.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. My problem is now that when I connect the Nook to the computer (linux Ubuntu), two drives show up both named B&N eReader. Neither can be opened. I suspect it's due to the fact that it shows no storage. How do I go about upgrading through B&N?
Maybe I have to use Windows? The 1.2 version before I started tinkering was recognised by Ubuntu Linux. Any help so I don't get murdered by my 9 year old for breaking her Nook is appreciated.
So are you on 1.2 now? Try making a bootable clockwork card and flashing this.
http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
So are you on 1.2 now? Try making a bootable clockwork card and flashing this.
http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
No I'm not on 1.2. I used to be but after "bricking" it and bringing it back I now have 1.0.1. I also have a bootable clockwork sd card. My question was how to get to 1.2 or 1.3 and you answered it by the link. Than you very much. I love you guys
loveubuntu said:
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
Click to expand...
Click to collapse
It would help us more if we knew what you did/tried to do when messing it up... was it one of the "restore nook to stock" cwr images you used?
Try using the 8 failed boot attempts.... if you haven't messed up your recovery partition it should restore you to the version that was originally installed on your NC.
To help troubleshoot and fix it is really helpful to tell us what happened... you could also try using the cwr restore to stock 1.2 or the cwr update to 1.2 or 1.3 files.
DizzyDen said:
It would help us more if we knew what you did/tried to do when messing it up... was it one of the "restore nook to stock" cwr images you used?
Try using the 8 failed boot attempts.... if you haven't messed up your recovery partition it should restore you to the version that was originally installed on your NC.
To help troubleshoot and fix it is really helpful to tell us what happened... you could also try using the cwr restore to stock 1.2 or the cwr update to 1.2 or 1.3 files.
Click to expand...
Click to collapse
Thanks for your reply DizzyDen. As I mentioned in the post before yours, I think I'm all OK now. I had made a bootable CM7 sd card to have stock/CM7 (without and with SD) but somehow had CWR installed on the emmc.
Then trying to upgrade to 1.3 from their website, I was not allowed. So what I had to do was to make a bootable CWR sd card, boot from the sd card and remove the CWR from emmc (used a flashable zip found on forums) and then flash a 1.0.1 image. Then I used the 1.2 update from the above link to update to 1.2 and then used the 1.3 from B&N website to upgrade to 1.3. Now I'm where I want to be but thinking about rooting again It's too much excitement but didn't have to be.
I think I must have tried to flash CWR recovery with the ROM Manager app when I had the CM7 bootable sd card in that caused all these problems. It's nice to have the bootable CWR though.
loveubuntu said:
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
Click to expand...
Click to collapse
You can get you Nook back to the factory 1.2 by following procedure the it described near the end of the first post at
http://forum.xda-developers.com/showthread.php?t=1054027
Look for the "Complete Wipe" heading.
BASIC! said:
You can get you Nook back to the factory 1.2 by following procedure the it described near the end of the first post at
http://forum.xda-developers.com/showthread.php?t=1054027
Look for the "Complete Wipe" heading.
Click to expand...
Click to collapse
thanks, i wonder why this isn't included in the guide sticky thread. Also, is there a simpler way to complete wipe than the 8 reboot sequence? a script?
loveubuntu said:
thanks, i wonder why this isn't included in the guide sticky thread. Also, is there a simpler way to complete wipe than the 8 reboot sequence? a script?
Click to expand...
Click to collapse
Here's a BootCnt file and a dos batch file that will make it a LOT easier for ya if you have adb running...
DizzyDen said:
Here's a BootCnt file and a dos batch file that will make it a LOT easier for ya if you have adb running...
Click to expand...
Click to collapse
Thank you. I have adb and will give it a whirl later. I'm still stcuk with trying to have a working ROM on the nook. The Phiremod7.1 which is based on CM7 seems to be working fine now but I can't get any CM7 nightlys to show any soft keys at the bottom, hence no back or notification bars. I'm going to try a stable one to see if that maybe the problem. Funny that I was able to run the nightlies when I was off of SD.
Also while I have your ear, , I'm a bit confused about this wiping and rooting business with the nook. I'd appreciate any help for me to understand it a litlle better. Excuse my ignorance.
Why can't a complete wipe be performed when booted from a CWM sd card? In the numerous phones I have rooted the sequence is easy: root, install custom recovery, nandroid back up, wipe data/system/cache/dalvik and then install a new rom. In the nook,, I still get residual from the last rom (my wifi settings, wallpaper, B&N registration info) unless I do the 8 reboot sequence. What does the 8 reboot wipe that we can't wipe any other way? What does emmc format accomplish then?
Also, how is it that I can install a rom through an SD card without ever rooting the nook?
TIA
loveubuntu said:
Thank you. I have adb and will give it a whirl later. I'm still stcuk with trying to have a working ROM on the nook. The Phiremod7.1 which is based on CM7 seems to be working fine now but I can't get any CM7 nightlys to show any soft keys at the bottom, hence no back or notification bars. I'm going to try a stable one to see if that maybe the problem. Funny that I was able to run the nightlies when I was off of SD.
Also while I have your ear, , I'm a bit confused about this wiping and rooting business with the nook. I'd appreciate any help for me to understand it a litlle better. Excuse my ignorance.
Why can't a complete wipe be performed when booted from a CWM sd card? In the numerous phones I have rooted the sequence is easy: root, install custom recovery, nandroid back up, wipe data/system/cache/dalvik and then install a new rom. In the nook,, I still get residual from the last rom (my wifi settings, wallpaper, B&N registration info) unless I do the 8 reboot sequence. What does the 8 reboot wipe that we can't wipe any other way? What does emmc format accomplish then?
Also, how is it that I can install a rom through an SD card without ever rooting the nook?
TIA
Click to expand...
Click to collapse
I have only recently noticed the remnant effect of previous data... I suspect it has something to do with B&N's newest software effecting the ability to wipe the partitions... perhaps formatting the partitions first would assist.
The 8 failed boots completely re-initializes the Nook with the factory backup data stored on mmcblk0p3... there is the complete rom and device specific backup stored in zip files there.
You can install a ROM by booting off the SD because B&N set our nooks up to boot from SD first... so when you do nothing from the Internal storage is loaded upon boot... so its not in use and can easily be manipulated.

CM 7.2 release candidate

http://www.cyanogenmod.com/blog/cyanogenmod-7-2-0-rc1-is-upon-us
It’s been a long time in the making, but it’s finally here: CyanogenMod 7.2, the latest version based on Android 2.3(.7), has reached the release candidate stage!
We’ve been delaying it for too long, mostly because new devices kept being submitted to us, and now we feel that at 69 70 devices, CM7.2 is more than ready for everybody to enjoy
7.2 adds a couple of backported features and fixes from Android 4 (ICS), over 20 new devices when compared to 7.1, and even some new features to boot (be sure to check out the new predictive contact search in the phone dialer!). We’ve also fixed some bugs along the way. Some of them device-specific, others that affected everybody, and one in particular that’s been plaguing Android for a long time: the mysteriously vanishing SD-card ringtones are no more! You can check the full list of noteworthy changes at the CHANGELOG.
As usual, you can submit bug reports on these builds: if you find anything broken in your device while running CM7.2-RC1, (as downloaded from our mirrors or ROM Manager! Please do not submit reports if your build came from elsewhere), be sure to submit a report through http://code.google.com/p/cyanogenmod/issues/ , so that we can fix it in time for the final 7.2 release.
from Cyanogenmod Blog
What are the significant differences between this official CM7.2 and the unofficial CM7.2 KANG that we have been using in the last couples of months?
Excuse a noob, but is this file good for SD as well as emmc installs?
thanks
Assuming you have already got a flavor of cm7 installed on an SD card you can copy the update file to the boot partition (I did it from my PC with a card reader), then insert the card in your NC and either access your boot menu and select Reboot Recovery or boot normally and then Reboot with the Recovery option. The files unpack and the penguin is displayed. The unit shuts off and you have to restart (seems to take forever with the android boot animation but wait it out) and all should be well.
Sent from my NookColor using Tapatalk 2 Beta-2
votinh said:
What are the significant differences between this official CM7.2 and the unofficial CM7.2 KANG that we have been using in the last couples of months?
Click to expand...
Click to collapse
KANG 03042012, the latest, *has* CM7.2RC1 so the differences are detailed in that thread but boil down to mr666's enhancements.
For instance, I get the impression from your sig that you run Dalingrin's as a separate update. Dalingrin's has been a part of M-K,(one of the above mentioned enhancements), for a while now.
MISRy said:
KANG 03042012, the latest, *has* CM7.2RC1 so the differences are detailed in that thread but boil down to mr666's enhancements.
For instance, I get the impression from your sig that you run Dalingrin's as a separate update. Dalingrin's has been a part of M-K,(one of the above mentioned enhancements), for a while now.
Click to expand...
Click to collapse
Phrrrrrrr??? What???
Forgive me but what are you talking about?
votinh said:
Phrrrrrrr??? What???
Forgive me but what are you talking about?
Click to expand...
Click to collapse
Glad you said it, so I didn't have to show my ignorance
I was happy to see that 7.2 fixed the magazine stacking in the Nook App. I have the official and the M-K running on different NCs and they're running great!
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Sherip said:
The unit shuts off and you have to restart (seems to take forever with the android boot animation but wait it out)
Click to expand...
Click to collapse
I tried to update but I can't even get to the boot animation. It shows CM is loading, flash of light, then goes black. Time for a fresh install I guess.
bp_ said:
I tried to update but I can't even get to the boot animation. It shows CM is loading, flash of light, then goes black. Time for a fresh install I guess.
Click to expand...
Click to collapse
Took awhile even to get to the animation, you may have given up too soon.
I like the update, have noticed improved battery life, nice colors and screen transitions. I have twice had a glitch where it wouldn't wake up after sleeping (twice in the last few days). Hope that doesn't persist.
Sent from my NookColor using Tapatalk 2 Beta-2
libertus77 said:
I was happy to see that 7.2 fixed the magazine stacking in the Nook App. I have the official and the M-K running on different NCs and they're running great!
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Actually it didn't. It's that Nook for Android released a brand new version that fixed the magazine issue. A week prior the older version still stacked all the magazines on top of each other on my 7.2 build.
How do you know if you have the latest version of the Nook app? Download some comic books, it's the first version that supports Nook Comics.
SeaFractor said:
Actually it didn't. It's that Nook for Android released a brand new version that fixed the magazine issue. A week prior the older version still stacked all the magazines on top of each other on my 7.2 build.
Click to expand...
Click to collapse
Hmm. But is the newer version not stacking on 7.1 either? I'm curious, but not enough to flash back to test, I don't think. I just had a friend switch to 7.2. A few days ago specifically because of the stacking, so that would be a good coincidental timing. Anyone still on 7.1 that can check?
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
libertus77 said:
Hmm. But is the newer version not stacking on 7.1 either? I'm curious, but not enough to flash back to test, I don't think. I just had a friend switch to 7.2. A few days ago specifically because of the stacking, so that would be a good coincidental timing. Anyone still on 7.1 that can check?
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I had rotated out of 7.1 awhile back and I use B&N app everyday. When they provided the new update for the app, that is when my magazines stacked correctly. The update was actually made for the tablet and the version of the new update is: 3.1.0.19.ANDTBL (and tablet). I updated when it came out and it fixed it immediately. I would think it would still work correctly on 7.1, but like you, do not want to mess with a good think.
Okay, curiosity was bugging me. I tested, and yep, no stacking on 7.1 either, guess it was a B&N fix. 7.2 is good in any case.
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
I did a new install to SD card with the CM7.2RC Most things work as should. Biggest issue is that after some point, the unit will not accept a charge. I plug the cable in (NC Cable/charger) and the light on the cable goes straight to green. Leaving it plugged in for awhile doesn't change the amount of charge (actually is discharging per normal use). After a power off and re-boot, all works as normal. Not sure what the trigger is that causes the Nook Color to not take a charge, but it is not locked up, all programs work normally. It will take a charge and discharge-lets say over a few days, then at some point will not allow a charge. Battery % meter seems to be accurate; tracking appropriately.
I also have a Nightly (#75 I think) SD card that I use, as well as stock Rooted 1.1 on EMMC, and neither have this issue, device is fine electronically.
Any ideas?
Thanks, Mark
Are you sure it's not the cable? They have a bad habit of going south on us.
CM7.0.3 to CM7.2 non rooted on SD card
Hello,
I'm a noob here and found that I should ask questions here on the general forum and not the developers forum.
I have very recently created a sd card non rooted using CM7.0.3 encore and have kernel version 2.6.29-omap1 and its Android version 2.3.3.
I want to keep the ability to return to B&N mode from internal memory to keep my warranty from B&N in check.
I have had issues with using the Google Market app and don't see a lot of apps that I would normally see on my Droid Bionic...like Facebook and others. I have hacked around that issue by finding apps and manually installing them as a work around which is fine for now.
A couple of questions?
By going to a nightly version...can I still remain non-rooted and keep emmc stock and intact with B&N Color flash and boot from my sd card?
will this fix my Google Market issues and have more applications that I can see?
Will I be able to just drag the new CM7.2 ??version code to my /boot directory on my sd card and go into recovery mode to boot it in?
Does this new CM7.2 ??? get put in a particular partition or just under the /boot directory?
Will this wipe out my apps or any data on my sd card?
Will this CM7.2 ??? version support USB host mode for a USB webcam for Skype?
Apparently, this opens another can of worms in that I need to provide USB power from an external hub and I need some kind of Nook Tweaks app to adjust settings?
Can someone explain this?
I have searched these forums and I must say spent a lot of time and nothing seems to be in one place or current on pre-requisites.
Should I get a second sd card to practice on so I don't wipe out my bootable CM7.0.3 version
Any help here would be GREAT!
Thanks in advance!
BB
I'm in a similarsituation as BeaconBob. The following applies to me as well.
BeaconBob said:
... using CM7.0.3 encore and have kernel version 2.6.29-omap1 and its Android version 2.3.3.
A couple of questions?
Will I be able to just drag the new CM7.2 ??version code to my /boot directory on my sd card and go into recovery mode to boot it in?
Does this new CM7.2 ??? get put in a particular partition or just under the /boot directory?
Will this wipe out my apps or any data on my sd card?
Should I get a second sd card to practice on so I don't wipe out my bootable CM7.0.3 version
Any help here would be GREAT!
BB
Click to expand...
Click to collapse
I set up my 8GB card months ago and have forgotten all the details of flashing a ROM. Thanks for any suggestons/help.
Make sure your screen density is set to 180. Clear market cache and data, reboot, and try again.
If you don't want to spring for a new Sandisk class 4 card -- I have five now ) -- just use your Win32Disk Imager to write an image file of your current setup to your computer and go blithely on experimenting like crazy. You will always have an image file to write back to your freshly formatted sd card to take a giant leap backward. But I'd bet you'll never even use it. It's too much fun going forward.
And it never hurts to have a zipped backup of the Titanium BU files available to upload and restore at various stages.
Currently running a racks triple boot, the latest Kang cm7, a dualboot miui/stock, and somewhere I could swear I had an old 253m from back in january. Just so my NC flap doesn't break, I'm good...

[Q] Stuck at Cyanoboot screen

Hello I've had a Nook HD+ working since August beautifully, I thought to get one for my sister and picked one up over the weekend.
Today I decided make it like mine, ie take off the B&N interface and try for a most vanilla like jelly Bean.
These are the instructions I followed last time....
"1. Download leapinlar's NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip
2. Extract the zip above and burn the img to a 4GB or larger microSD card
3. After burning, copy cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip and gapps-20130301-jb-signed.zip back to the microSD card
4. Place the microSD card back to the Nook HD+ and boot it
5. Do a backup for the stock ROM
6. After backup is done, do data wipe/factory reset
7. Flash the cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip and gapps-20130301-jb-signed.zip"
I made a mistake this time around, I used cm-10.2-20131031-UNOFFICIAL-ovation-sdcard.zip by accident instead of the EMMC version. Now when I power the unit on, with no SD card it keep rebooting at the Nook screen. With a now corrected SD card it gets stuck at the cyanoboot screen, it dims after a minute but then still just stuck there.
How do I go about fixing this? Thank you in Advance....
Ok so I rebuilt the SD card and it looks like it's kinda back to normal. I did a wipe and then wrote....
cwm-recovery-ovation-3.zip
cm-10.2-20131031-UNOFFICIAL-ovation-emmc.zip
gapps-jb-20130301-signed.zip
Rebooted and now it gets stuck at that spinning logo, the logo never goes to the correct aspect ration. Screw it I'm done for today.
Tomorrow I'll try doing a restore to factory defaults and try the same steps again, if it should fail again, then I'll restore, wipe, and try the exact same files I used on mine. Unless someone has a better guide/method to use....
Any insight would be appreciated. Thank you!
You need to get back to pure stock so that everything can be done over. Go to my HD/HD+ CWM thread linked in my signature and use your already burned CWM SD to flash a plain stock ROM from item 6. Also do a factory wipe with it.
Then start over, but use the dummies guide for CM10.1.
Edit: I did not see your second post when I wrote this. But I think the advice still holds.
Sent from my BN NookHD+ using XDA Premium HD app
OK go tit all settle! I used your stock image, booted up to normal, then went back, wiped, and did the usual files. The latest file cm-10.2-20131031-UNOFFICIAL-ovation-emmc Gave me keyboard errors, so I went back to the old file I used previously on mine, cm-10.1-20130615-UNOFFICIAL-ovation-emmc, and everything seems perfect.
Thank you for your help! You are a man among men!
leapinlar said:
You need to get back to pure stock so that everything can be done over. Go to my HD/HD+ CWM thread linked in my signature and use your already burned CWM SD to flash a plain stock ROM from item 6. Also do a factory wipe with it.
Then start over, but use the dummies guide for CM10.1.
Edit: I did not see your second post when I wrote this. But I think the advice still holds.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I'm trying to follow your method of going back to stock on emmc, but I can't get my nook into recovery. I have re-made my SD card multiple times and the times my HD+ boots off the sd card (mine is one of those thats hit or miss), it will stay stuck on the Cyanoboot screen. If I can't get into recovery somehow, I'm hosed. Any ideas? I want to avoid having to bring it in for 1 year warranty replacement.
cabbieBot said:
I'm trying to follow your method of going back to stock on emmc, but I can't get my nook into recovery. I have re-made my SD card multiple times and the times my HD+ boots off the sd card (mine is one of those thats hit or miss), it will stay stuck on the Cyanoboot screen. If I can't get into recovery somehow, I'm hosed. Any ideas? I want to avoid having to bring it in for 1 year warranty replacement.
Click to expand...
Click to collapse
Sounds similar to my situation. Can't get the tab into recovery.
chr0 said:
Sounds similar to my situation. Can't get the tab into recovery.
Click to expand...
Click to collapse
i find it hard to believe we are both just screwed. Maybe I'll try and find a different sd card and give that a try. Ugh. This is most bogus.
Hello everybody,
I have even worse problem with cyanoboot - I've bought used NOOK HD+ after someone tried to install cyanogenmod on it, and except holding cyanoboot at screen with an SD card (that I've prepared accordingly leapinlar's page), it has next issues:
1) there is absolutely no response, when I try to turn it on without an SD card;
2) when the SD was untouched by me, it had some other cyanoboot installed on it but with this version nothing in the cyanoboot menu worked: there was a menu and errors in the console every time I've done everything. But, at least, it loaded.
And I have no SD card bigger than 1 GB.
And, question ahead - is it some easy way to figure out whether my B&N is bricked?
Regards
cabbieBot said:
i find it hard to believe we are both just screwed. Maybe I'll try and find a different sd card and give that a try. Ugh. This is most bogus.
Click to expand...
Click to collapse
Good luck to you, sir.
Do you mean you are going to try another SD card by making it bootable with CWM? Or are you going to try verygreen's no-emmc build and run your tab directly off the SD? Because I have tried more than a few SD cards for the former to no effect.
chr0 said:
Good luck to you, sir.
Do you mean you are going to try another SD card by making it bootable with CWM? Or are you going to try verygreen's no-emmc build and run your tab directly off the SD? Because I have tried more than a few SD cards for the former to no effect.
Click to expand...
Click to collapse
I cried uncle and got it swapped out for a refurb. Hope you find a fix, this problem is a little nightmare, first time I've never been able to save a device.
cabbieBot said:
I cried uncle and got it swapped out for a refurb. Hope you find a fix, this problem is a little nightmare, first time I've never been able to save a device.
Click to expand...
Click to collapse
Glad you got it exchanged. Nook, after the drop in prices has been extremely good value for money.
I'm in Afghanistan, so an exchange is not happening until my next R&R. I'll probably be able to save enough for a Note 10.1 or Nexus 10 atleast by then.

Start HD+ with custom rom from SD without rooting device?

Hi there,
I have a HD+ and am very happy with it (perfect price/value ratio!).
I mainly use it for movies and to read.
So basically I am good with the regular OS.
On the other hand it sometimes seems to be a bit slow.
So I thought I evaluate the options running it on a different OS.
I am a bit scared flashing the device (installing a completely new ROM), as I tried to do that with a cell phone and trashed the device.
I thought it might be possible to start the device from SD without even loading the regular BN OS.
I don't mind leaving an SD card in there for like forever and always boot from there.
Is such thing possible?
Not to flash the device but still use a custom ROM?
If so, does anyone have a link to a tutorial?
Thanks a lot!
Matt
Yes, it is done all the time. It depends on which CM version you want. Look through the dev forum. If you want the latest, try this:
http://forum.xda-developers.com/showthread.php?p=48808658
Sent from my SCH-i705 using XDA Premium HD app
Thanks for the quick reply.
Do I lose any kind of performance, when I boot a ROM from the SD card (assuming I have a high speed card, so the SD card is not the limiting factor)?
I mean is the BN OS still running in the background?
How do I start the ROM from the SD card?
Thanks again,
Matt
EDIT: I think I got it.
Gotta figure out how to read the device though.
Will do that on the weekend using this:
http://forum.xda-developers.com/showthread.php?t=2062613
Thanks
Mattes_01 said:
Thanks for the quick reply.
Do I lose any kind of performance, when I boot a ROM from the SD card (assuming I have a high speed card
...
Click to expand...
Click to collapse
High-speed cards don't necessarily yield best performance for running ROM -- see http://forum.xda-developers.com/showthread.php?t=1005633.
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for pointers/tips on how to create SD-based ROM cards for HD+.

Categories

Resources