[TIPS] NEW - Pre-rooted 1.1.0 update/disable 1.1 auto update (and keep root)

[brothertcoleman]

I'm pretty new ,how do I mount the sd card?

Thanks

 

[brothertcoleman]

Nook won't turn back on ,when I get it to come on I will try to look under mounts/partitions.

 

[barakisbrown]

Thanks for the tip of wiping data..youtube app now works.

 

[Will Shanklin]

I'm pretty new ,how do I mount the sd card?

Thanks

When you get back into clockwork, you can do it there under mounts/partitions. If you can't boot now, you'll probably need to refer to the restore to stock thread.

 

[brothertcoleman]

Had to hold power for 20 seconds per manual to get it back on .

I did the mount /unmount in the Nook option but still nothing .

Do I have backup my card on my PC then format card after I install ClockWORK mOD maybe?

 

[brothertcoleman]

I cant find under mounts/partitions but this is whats there;

 

[brothertcoleman]

Is this the right version ,this is my screen on the Nook?

http://i927.photobucket.com/albums/ad117/brothertcoleman/PIC_1629.jpg?t=1296340344

 

[Will Shanklin]

Is this the right version ,this is my screen on the Nook?

http://i927.photobucket.com/albums/ad117/brothertcoleman/PIC_1629.jpg?t=1296340344

Yeah, you have Clockwork installed.

If all you're trying to do is backup your current ROM, it sounds like it's giving you trouble - I'd just wipe and flash the updated ROM if that's what you're trying to do.

 

[brothertcoleman]

I am trying to get the update 1.1 to work like the first post, not really backup my current ROM.

I used the Partition SD Card in Clockwork to try to wipe and flash Nookie but still can't mount card even though the card works fine.

Thanks for all the help, I will just keep messing around with it and post when or if it works.

 

[eShawpm]

Has anyone addressed losing adhoc wifi with this update? I upgraded then restored1.0.1 to retain adhoc tether. Please advise.

DuBB

 

[soreal]

On rooted Nook Color (after the 1.1.0 update), whenever I try to install a non market apk, I get the "Installation of downloaded apks is not supported." (the checkbox is checked in nookcolor tools) When I try to side load an *.apk file using Root Explorer and then click on it, I get the same message.

Am i doing something wrong?

 

[brothertcoleman]

Okay I made some progress, I had to do this from the nookdevs.com then follow Wills
1st post.

After rooting using nooter, your SD card is left with a single 40mb partition on it. You'll want to fix this so that you can use the full capacity of your SD card again. The Nook Color can do this for you.

1.Power up your Nook Color *WITHOUT* the SD card inserted (Otherwise it will try to boot off of the SD card)
2.Press the button to pull up the context menu with device settings
3.Then go to device info
4.Then click on SD card
5.Click on 'umount sdcard'
6.Then click 'format sdcard'
The NC will repartition and format the card to it's full capacity.

I put the NookColor_v1.1.0 zip in the root of my sd card but when I go to
(5. Choose install zip from sdcard. Pick the file you downloaded.)
I cant find it but see everything else on the card now.

 

[Will Shanklin]

On rooted Nook Color (after the 1.1.0 update), whenever I try to install a non market apk, I get the "Installation of downloaded apks is not supported." (the checkbox is checked in nookcolor tools) When I try to side load an *.apk file using Root Explorer and then click on it, I get the same message.

Am i doing something wrong?

Open the included nookcolortools app, and select the option to allow non-market installs.

 

[soreal]

I did, the checkbox is checked in nookcolor tools

 

[jon b calderon]

where do you get the 1.0.1 update?

where do you get the 1.0.1 update? i can't find it anywhere, when i go to the links, they always re direct me to the barnes and noble page for the 1.1.0 update. :-\

 

[razorgaze]

woot! woot! finally, something that worked perfectly the first time! updated to 1.1.0 on my pre-rooted nookcolor.

the ONLY hesitation i had was with the instruction "reboot in CWR" - it's called reboot in recovery in the program. when you reboot, read prompts fully (selecting the zip file from sd card) then install nook file. you should come to a screen with a lot of 'no', scrolling down to the only 'yes'.

Don't panic when the file appears to hang seconds into to it - it will continue after about 3-5 minutes. once you get 'update successful' make sure to hit your power/sleep button to go back, where you then select (n button) reboot operating system or something to that effect.

good luck... it's easy if you follow the instructions AND it does work the first time.

raze

 

[brothertcoleman]

Finaly got it to work ,I had to redownload the zip file and it read on my Nook.

Thanks for all the help Will.

 

[ebarr727]

I couldn't fit NookColor... on my 8GB SDcard! Is that correct? Do I really need a bigger SDcard?

 

[AintSkerd]

:

UPDATE 01/28:
***SNIP,SNIP,SNIP***

2) (credit to khaytsus, whose post is here: Want to try to avoid 1.1.0 OTA? Modify build prop? - xda-developers)

In Root Explorer, go to system/build.prop, set system as r-w, and open the file in a text editor.

Change the following part:

ro.build.version.incremental=278
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1
ro.build.date=Thu Dec 16 14:27:20 PST 2010
ro.build.date.utc=1292538440

ro.build.description=1.0.1.278.int.enc.rrdp.s30428

# So let's use ARM, until we are totally conformatable with DSP Jpeg decoder.
# Setting limit to 2 Megs, as that seems to be the sweet spot
skia.jpeg_threshold=2000

...to the following:

ro.build.version.incremental=328
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1
ro.build.date=Fri Jan 21 18:45:35 PST 2011
ro.build.date.utc=1295664335

ro.build.description=1.1.0.328.int.enc.rrdp.s31975

# Setting limit to 1 Meg, as that seems to be the sweet spot
skia.jpeg_threshold=1024


Then reboot.

This could also be done by adb:

adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system

adb pull system/build.prop build.prop

(then make the above changes in a text editor on your computer, and save under the same name, then...)

adb push build.prop system/build.prop

adb reboot

This second method is basically tricking your Nook into thinking it already received the OTA. This is a new method suggested in the previous link. It shouldn't hurt anything, and it just might help.

Again, we'll see if the above procedures completely disable the firmware from automatically updating, but I'd say if you don't want the update, these procedures are WELL worth doing.
As time passes, please post your results in terms of whether you get an OTA or not after doing the tricks above.

I am 1.0.1 nootered. CWM installed. Being a fan of simplicity, I backed up in clockwork and tried the monsters zip to block ota. It looks like it modifies the prop build with a simple zip flash. On reboot it showed successful update (green N in status bar) and shows correctly in system. Note this is not the 1.1 update root, just a system edit. I am happy with 1.0.1 until something bigger and better comes along. (read as CM or HC port)

 

[DaveNagy]

Hi, gang.

I have a really basic question. I'm sure it's covered somewhere else in this forum, but explaining it somewhere here in this sticky (maybe even in the OP) might be useful to future newbies.

The short version of my question is: Why do we care if the new OTA update causes us to lose root? Why is that a big deal? Please explain the extent of the downside.

To expand, I don't own a Nook, but I'm thinking about picking one up this week. I do own a rooted and ROM'd Evo, so I'm not totally unfamiliar with concepts being discussed here. Certain Android hardware is pretty "locked down", and there's a constant fear that the next OTA update will lock things down even harder. Users are cautioned not to automatically take the OTA, but instead to wait for the community to check it out, and if necessary, remove any new "locks" and come up with a "root safe" version.

But everything I've read in the last few hours indicates that's it's absolutely trivial to root an NC. Does the 1.1.0 update break all currently known rooting methods? If yes, then that info probably belongs in the OP. If no, then why all the excitement?

(In other words, I'm just looking for the context behind this thread.)