yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Gibbage:
I have 1.2 with MN, and I DONT want the auto-update to 1.3 (till things are fixed). Is there a way to prevent the auto update? As simple as possible please!
[Nook Color Android Development] doncaruana:
You figure out what's simple to you, but look here.

I think the database or build.prop either one will work.
[Nook Color Android Development] Gibbage:
The thing is, all 3 solutions require some sort of terminal access to type in commands. I dont know how to get into this terminal.
[Nook Color Android Development] doncaruana:
For llewelyn and gabrial - how did you guys eventually solve the issue with the cache/null problem with the market?
[Nook Color Android Development] RegLinUsr:
I edit the build.prop via the

Root Explorer

app... doesn't get much simpler than that. Create backup of original build.prop prior to editing.
[Nook Color Android Development] dtbrewer:
As I mentioned in another thread I like the method in this link which gives an easier to follow method for the sqlite editing version of the update block. It worked for me for 2 months after the 1.1 to 1.2 update came out. It works directly from the Nook, no terminal access needed, but requires you to purchase the apps Root Explorer and SQLite Editor.

http://xdaforums.com/showthread.php?t=946969
[Nook Color Android Development] fpga_guy:
The SQLite method can be done without ADB. Also there is a legitimate free version of SQLite editor. See http://xdaforums.com/showpost.php?p=11038175&postcount=23 for the link.

The SQLite basically set the OTA (on the air) update from "auto" to "manual".
[Nook Color Android Development] GMPOWER:
You’re trying to make a 1.3 update rom right? The null is fixed with the script that is located in the MN package under /tmp/scripts/database

#!/sbin/sh
(
HOME=/tmp /tmp/sqlite3 /data/data/com.android.providers.downloads/databases/downloads.db << EOF

BEGIN EXCLUSIVE TRANSACTION;

CREATE TEMPORARY TABLE temp_downloads(_id INTEGER PRIMARY KEY AUTOINCREMENT,uri TEXT, method INTEGER, entity TEXT, no_integrity BOOLEAN, hint TEXT, otaupdate BOOLEAN, _data TEXT, mimetype TEXT, destination INTEGER, license_bytes TEXT, no_system BOOLEAN, visibility INTEGER, control INTEGER, status INTEGER, numfailed INTEGER, lastmod BIGINT, notificationpackage TEXT, notificationclass TEXT, notificationextras TEXT, cookiedata TEXT, useragent TEXT, referer TEXT, total_bytes INTEGER, current_bytes INTEGER, etag TEXT, uid INTEGER, otheruid INTEGER, title TEXT, description TEXT, scanned BOOLEAN, bn_environment TEXT, bn_category TEXT, bn_device_token TEXT, bn_acc_token TEXT, bn_item_id BIGINT, relative_path TEXT default '', install_status INTEGER);

INSERT INTO temp_downloads SELECT * FROM downloads;

DROP TABLE downloads;

CREATE TABLE downloads(_id INTEGER PRIMARY KEY AUTOINCREMENT,uri TEXT, method INTEGER, entity TEXT, no_integrity BOOLEAN, hint TEXT, otaupdate BOOLEAN, _data TEXT, mimetype TEXT, destination INTEGER, license_bytes TEXT, no_system BOOLEAN, visibility INTEGER, control INTEGER, status INTEGER, numfailed INTEGER, lastmod BIGINT, notificationpackage TEXT, notificationclass TEXT, notificationextras TEXT, cookiedata TEXT, useragent TEXT, referer TEXT, total_bytes INTEGER, current_bytes INTEGER, etag TEXT, uid INTEGER, otheruid INTEGER, title TEXT, description TEXT, scanned BOOLEAN, bn_environment TEXT, bn_category TEXT, bn_device_token TEXT, bn_acc_token TEXT, bn_item_id BIGINT, relative_path TEXT default '', install_status INTEGER);

INSERT INTO downloads SELECT * FROM temp_downloads;

DROP TABLE temp_downloads;

UPDATE downloads SET relative_path = '' WHERE relative_path IS NULL;

END TRANSACTION;

VACUUM;

EOF
) || exit 1

The problem that you are going to run into is that the database file is not generated until first boot. Just putting the script into your install package will not write the changes because the file has not been created yet. If you want to make it a one step all in one install, you will have to manually go and edit the correct section of code for the changes.
[Nook Color Android Development] doncaruana:
Thanks gmpower. You led me down the exact same conclusion I had come to. I saw the script change but couldn't figure out how that would work since it seems to come later.

Do you know what triggers the change exactly? I mean first boot after what? I was actually experimenting with getting rid of the format in the 1.3 update and so then it doesn't mess with the system/app directory (ie leaves market and gapps in place). Because I'm seeing the problem in going from rooted 1.2 to 1.3.
[Nook Color Android Development] GMPOWER:
When the new DownloadProvider.apk from 1.3 is installed to /system/app, on the first boot it will then install itself to /data/data/com.android.providers.downloads and creates the downloads.db inside of that folder. I will have to go back through my notes to see if I still have the steps to manually apply the null fix into the system file.

The formatting of the /system/app folder is not really much of a problem because you can just include the gapps into the update rom. When people want a non wiping update rom, what they are really asking for is that you don’t format the /data/app and /data/data folders. The /data/app holds their apps apk file, and the /data/data folder holds their app and system app data. The problem that you start to run into without formatting the /data/data folder is that the old 1.2 system app data might not work correctly with the new 1.3 app data added to it. You can also start to run into UID errors, because the system is going to give all apps a new UID.
[Nook Color Android Development] doncaruana:
Thanks man - that explains a lot. The 'no format' I built seems to work okay except for the download problem. What I was gunning for was kind of a one-shot deal to 'upgrade' from 1.2 to 1.3 without losing root. I have that, but the download issue happens, since it takes place after the update. So, absent some sort of a fix, it'll just have to be a two-step process I guess. Also need an updated kernel, but once dalingrin updates his, I'll just incorporate it.

thanks again!
[Nook Color Android Development] doncaruana:
Back to bug you folks again...

So...how exactly do you get past the "Could not verify APK signature" issue? I was thinking that the same set of gapps, etc on 1.3 should still work, right?

I'm sure I'm missing something quite simple, but if anyone has a suggestion...
[Nook Color Android Development] DizzyDen:
You choose to install zip...NOT update.

Always remember...

YCGIYWG

(You Can't Get... If You Won't Give)
[Nook Color Android Development] doncaruana:
You mean in CWM, right? That's what I did - install zip from sd card.
[Nook Color Android Development] DizzyDen:
You might want to disable signature checking then.

Always remember...

YCGIYWG

(You Can't Get... If You Won't Give)
[Nook Color Android Development] doncaruana:
Sorry I wasn't clear...I have no problems installing the files. But, once on the nook, when I try to download or update a market app, I get the "Could not verify APK signature" problem as the root of "Download Unsuccessful" (I see this from looking at logcat).

Now, at some point in the original MN, they solved that problem, but I'm wondering how, since I'm basically just trying to get the same stuff to work on 1.3.
[Nook Color Android Development] doncaruana:
Okay, my deeply knowledgeable developer friends...

Can someone explain to me why this works?

Going from 1.2 to 1.3, I couldn't get anything to work. But if you apply 4-5-18 first and THEN apply 4-6-16, everything works!

Makes no sense to me at all...anyone?
[Nook Color Android Development] GabrialDestruir:
Does ANYONE know why applying 5-18 before 6-16 would fix issues with root on 1.3?
[Nook Color Android Development] GabrialDestruir:
We didn't, we tested a bunch of different sets of Gapps, and we eventually came up with, or some came up with the set currently used in 6.16, they should work in 1.3 without anymore issues than existed in 1.2
[Nook Color Android Development] doncaruana:
I guess that goes back to my previous post then. Very bizarre. Apparently some reported that 6-16 applied to a fresh 1.3 (ie straight stock, no previous rooting) would work okay, but I restored a couple of dozen backups trying to get 6.16 to work over top of a previously MN nook with the 1.2 update and it just would not work. Can't even tell you how many combinations I tried. Very bizarre...
[Nook Color Android Development] mojonba:
Hey guys,

My NC autoupdated to 1.3 and lost root. I followed instructions in the first post to restore root by running MN 4.5 first and then MN 4.6. Market showed up login screen but does not load. Repeated MN steps but market still does not load. Any ideas?

Thanks
[Nook Color Android Development] bmar08:
if i am running a version of Phiermod from the SD card right now.. the OP says to download MN and then run it from CWR basically and it will open up and root the NC, can i use the same CWR i use thats on the SD card i use to update the SD version of android so the stock version is rooted and keep the sd version saved on the card or should i follow the steps to create a fresh sd with CWR on it to do this?

reason why im asking is because im wanting to start running it on the EMMC and not thru the sd card because ive heard it runs much better that way...
[Nook Color Android Development] explorer-10:
whats the change from 1.2 to 1.3 do, aside from the b&n changes[or root-wise]?
[Nook Color Android Development] Windsor1959:
I'll share my experience with you, not only for any advice you can offer, but also in the hope that some little piece of info I share might help someone else.

I flashed 4.6.16 over B&N 1.3 yesterday, before I saw the 5.18 possibility. At first, everything seemed to work, including Market and Gmail. I restored my other apps with TB. Then I rebooted. Once I unlocked my Nook, I saw the green Nook symbol in the lower left of the status bar. Gmail and Google Maps would load no longer. I can still install apps through Amazon appstore, and I can sideload apps and install them. Market still opens, and I still have good app visibility. But, when I try to download or update an app, once the app downloads I get the "package file is invalid" error. Fixing permissions in Rom Manager did not fix the problem. Do I need to start over again (flash 1.2, update to 1.3, then apply 5.18 and 6.16), or can I fix my Market problem some other way?

I sideloaded Gmail 2.3.5, and it works fine. I tried sideloading a newer Market, but it behaves the same way.

Thanks in advance for your help!
[Nook Color Android Development] bretzke:
I had BN 1.2 + Dal's OC kernel with MN working fine most of the summer. 1.3 was pushed last week and I lost root, but Amazon store still worked and I could DL/install from that, but Market, GMail and many apps were gone.

I did the instructions in OP to MN 1.3. I did not clear all out/restore to stock, just pushed MN 4.5.18 then 4.6.16 and then Dal's OC kernel as listed. Now it won't complete a boot. Just stays on the NC animated boot screen, repeating for ever. It last 2 hours before the battery gave up. It never reboots through 'Read Forever' or anything else, just the boot animation.

Any thoughts? The only option I see is to restore to clean 1.2. Any sense in restoring the 1.2 stock kernel? I would hate to kill my \data but see no real choice.

Thanks.
[Nook Color Android Development] sym1:
Can anyone tell me if this new method of applying both MNs solves the problem of apps2sd on 1.3, or does it still corrupt the app?

I have had this problem while on v1.2 using MN 4.6.16, and it persists after ota 1.3 and reapplying MN 4.6.16 (not a clean install, just the way the ota left it). Everything else seems to work fairly smooth, with the exception of Beautiful Widgets, which seems to switch clock formats on it's own.

TIA
[Nook Color Android Development] doncaruana:
Did you boot up after applying 4.5.18?

You could try doing that again and see if you can boot. I know every time I change the kernel, it stays on the color nook animation for a scary long time.

I would try each one and boot up in between.
[Nook Color Android Development] doncaruana:
build.prop sed error

Just as an FYI, the sed that is supposed to change the build.prop was never fixed for MN 4.6.16. If you don't change it, your nook will have a fingerprint of zoom2 when you're all done, which is what it would have had originally if you never fixed it the first time. Depending on what it was before the B&N 1.3 update, that could affect market visibility and other things.

If you want to know what it's supposed to be or how to change it, look at this post.

I compiled an updated MN 4.6.16 that has the build.prop fix plus includes a script to do the OTA block, which GD has a fundamental objection to. My version is here if anyone is interested, but it doesn't do anything magical besides the above and doesn't operate any differently than the original MN 4.6.16.
[Nook Color Android Development] bretzke:
I didn't that's probably what screwed me up. Wiped and rebuilt. I got 1.3 and rooted with the OP. Installed Dal's OC (the newest one marked 090111) and the eternal boot stall returned. Again, not a boot loop as in it goes back to Reading Forever each time, just loops the boot animation, freezing half way through, then restarting the boot animation. Left if on for 45 minutes on this loop (just to make sure) and decided to start the wipe process again :mad:

Don have you gotten Dal's OC to work on the MN 1.3? I know his thread says it should work no matter the userspace, but not seeing that on my NC.

Thanks for your help.
[Nook Color Android Development] fpga_guy:
Dalingren's OC kernel works fine on BN1.3 rooted. My NC flies and I can read magazines on NC for free (with paid print subscription). See how I did it:

http://xdaforums.com/showpost.php?p=17264793&postcount=9
[Nook Color Android Development] bretzke:
I followed that upgrade path too. After installing Dal's OC, the boot cycle started, and I never booted good again. I had his older version on MN 1.2 all summer and it worked fine.

Dave
[Nook Color Android Development] fpga_guy:
Which OC kernel are you using? Also, I fixed permissions after MN4.6.16 before install the OC kernel.
[Nook Color Android Development] bretzke:
It's the most current one I see:

update-Froyo1.2-dalingrin-OC-emmc-090111

That said, I'm thinking I have a bad MicroSD I'm installing these updates etc. from. Not sure yet, but that's what I'm hoping for at the moment.

Let you know in a few minutes.

Dave
[Nook Color Android Development] doncaruana:
That's the right version and, yeah, it's been working fine for me. I'd definitely check your files and your sd card.
[Nook Color Android Development] Tool Belt:
Problems....Help please?

Rooted 1.2 with 4.4.28 and other than Market needing several attempts to download things all was well.

1.3 arrived last night. Installed 4.5.18 off flashable card. Reboot....fail....reboot again.

Unable to sign in to market. Sometimes get as far as beginning to enter username.....then or before then Nook reboots itself.

Install 4.6.16. Reboot, fail...reboot. Run fix permissions. Reboots itself after a bit (is that normal?). Unable to sign into market as before, Nook reboots. Now it is rebooting to lock screen, sitting there for a minute or so and rebooting again...and again.

Any ideas please?

Thank you.
[Nook Color Android Development] doncaruana:
None of that is normal. I have no idea what it could be other than a bad load or bad card, but I'm far from an expert.
[Nook Color Android Development] lexluthor:
My nook was on 1.2 with MN 4.6.16 and it auto-updated to 1.3.

I want to understand the process to re-root / working marking.

I create a CWM card and put both MN 4.5.18 and MN 4.6.16 on it?

I then flash MN 4.5.18 and then immediately MN 4.6.16 or do I reboot into the OS after MN 4.5.18 and then do MN 4.6.16?

Where do I do fix permissions? That's something that's something that I run with the nook booted up or is that something in CWM?

Also, please confirm that indeed the process for people who are in the situation I indicated above.
[Nook Color Android Development] doncaruana:
You reboot in between applying versions of MN. I created this thread and instructions for exactly your situation. Just for clarity, both the OP in this thread and mine state you run fix permissions from rom manager.

Please note that you can use my modified zip or the original one here at your discretion. The differences are described in that post.
[Nook Color Android Development] lexluthor:
I headed over there am having a problem. I posted the issue at the end of that thread.

Thanks.
[Nook Color Android Development] Tool Belt:
Did a complete wipe, looks like everything is ok.
[Nook Color Android Development] marckusdavis:
Thanks doncaruana! This worked great for me!! I posted my results in your other thread.
[Nook Color Android Development] KuDaH:
Live Wallpapers

Rooted Nook B&N 1.3 with 4.6.16a

Live wallpapers working...

Cannot select it from normal menu...

Used Nook settings / App Settings / Home / Set Wallpaper

choose Live Wallpapers tab....

Currently had a live wallpaper installed but could not get it to work through marketplace application.

Currently using "Jumpgate Live wallpaper "flying Android in space"

Looks like a live wallpaper download will not show in the list untill the nook is rebooted.

Thanks for a great root!

No issues so far.
[Nook Color Android Development] ahmo97:
thank you. it work again
[Nook Color Android Development] w8wca:
1.3.0, MN and Dolphin HD Browser

I took my NC back to stock (8 interupted power up's) and deregister and erase.

Updated to 1.2.0 then 1.3.0 (1.3.0 did not take from my orig.).

Then ran ManualNooter-4-5-18.zip first (no fix permissions, but I booted to it though then power off)

Then ran ManualNooter-4-6-16.zip. - Fix permissions

I did the market fix as had fairly limited market (Well for what I wanted to d/l anyway).

I cannot find Dolphin HD Browser in the market. and appbrain will not install it

(Using fast web installer - it comes up with the install button but it does nothing when I tap it)

Seems like a build.prop problem?

lines probably important from it:

ro.product.model=NOOKcolor

ro.product.brand=nook

ro.product.name=zoom2

ro.product.overall.name=NOOKcolor

ro.product.device=zoom2

ro.product.board=zoom2

Any advice?
[Nook Color Android Development] doncaruana:
Yes - look here.
[Nook Color Android Development] w8wca:
I tried - Just doing the one line mod (used sed to change build.propp's ro.build.fingerprint) - it did not help.

Then I ran your MN and it did not work either.

build.prop = attached as .txt
[Nook Color Android Development] doncaruana:
So, the build.prop changes took effect (i can see that), but they aren't improving your market issue. Go through the market visibility fix now in the OP for this thread and see if that helps at all.
[Nook Color Android Development] w8wca:
Thanks that reminded me to also try to fix permissions again between the 2 I now have Market back.
[Nook Color Android Development] theseus9t6:
I followed the instructions in this thread here and voila! I have an updated 1.3 nook rooted and I didn't loose a program and Market works great.

The only thing I had to do was remove CWM recovery so that I could flash the update to begin the process. To do that, follow this thread.

Thanks to everyone here who are working hard to keep us up and running!
[Nook Color Android Development] gsutton:
Concerning the "update-Froyo1.2-dalingrin-OC-emmc-090111" or especially the "update-Froyo1.2-dalingrin-OC-emmc-063011" ROM, if I flash the ROM with my manualnootered rooted stock 1.2 Nook Color, is there any way to replace it with the original ROM if I decide to? I am guessing that I would have to backup my ROM and then restore it. Any comments are welcomed, and thanks for all of the great work you all do for us.
[Nook Color Android Development] w8wca:
When you say replace the orig ROM - if you mean take you ManualNootered 1.2.0 back to stock 1.2.0 yes you can there are instructions here to restore a Rooted NC to stock, and if you want to just take the kernel back you can also do that.

http://xdaforums.com/showthread.php?t=1050520

http://xdaforums.com/showthread.php?t=914690

This post has a .zip you can download to restore the stock kernel:

http://xdaforums.com/showthread.php?t=925451
[Nook Color Android Development] gsutton:
Thanks for the reply. I should have said "kernel" instead of "ROM". Sorry for the confusion.

Sent from my NookColor eReader Tablet
[Nook Color Android Development] RETIEF:
B&N market not working

Ok. I have root since 1.1 and did the revert back to 1.2 then updated and ran the manual nooters by the instructions. I no longer can use the "shop" app for BN stuff like their market, or buy magazines, etc. Seems like a lot of wasted time to do the update if I don't get any of the advantages of the update. So what did I do wrong?

Thanks.
[Nook Color Android Development] lexluthor:
I have another Nook Color that I had previously rooted using MN 4.6.16 which received the 1.3 update OTA (it's still on 1.3 unlike a poster above).

I've flashed 4.5.18 and 4.6.16a many times already, sometimes with a reboot in between, sometimes not, sometimes opening market in between, sometimes not. I've run fix permissions after the 4.6.16a update as well. Prior to booting up after 4.6.16a, I did put back in my normal SD card.

No matter what I do though, Market closes as soon as I open it.

If I clear market data, the first time it opens, it does ask me to accept the terms, then closes.

If I go to gtalk, I am logged in.

I also tried to update to the 3.1.3 market, but that says application not installed when I try.

Any ideas?
[Nook Color Android Development] fpga_guy:
BN shop works for me. Just download an issue of a magazine. Worst case is to do a fresh restore to BN1.2 and start over...
[Nook Color Android Development] bretzke:
This happened to me because (I think) I accidently tried to start up market after the 4.6.16a MN install but before the Fix Permissions via ROM Manager. GMail and Talk still worked but Market wouldn't. I bit my lip and reflashed start to finish, doing it in order this time and all is well now.

Perhaps you can pull the vending.apk from the MN zip file and put it in /system/app/, run Fix Permissions and see if that fixes it?

Good luck.

Dave
[Nook Color Android Development] lexluthor:
Success!

I had file expert installed so I navigated to system/app and looked at the permissions for vending.apk.

The first row was all checked, 2nd row just the top and 3rd row none.

I checked all 9 boxes and market now opens without closing.

In addition, I was also able to install the 3.1.3 market over the top without error.

I rebooted and everything still looks good.

I did run fix permissions plenty of times in this process. What does/should that set market permissions too? Maybe someone can figure out why that step isn't working right.

Hope this helps others!
[Nook Color Android Development] Fekish:
I have tried the same thing but with no success. When I open the market it stays open for 10 seconds and then just shuts down...
[Nook Color Android Development] Fekish:
OK everything works perfect now...

What I had to do was uninstall market from Titanium and then install it again!

By the way anyone knows how to install copy paste function as it newer android versions?
[Nook Color Android Development] bountyhunter644:
Is this a one time fix or something that needs done periodically? Just rotted a 1.3 nook for sister and not sure if she is technical enough to do this herself...
[Nook Color Android Development] Fekish:
hello,

Suddenly today after a restart i cannot go into my Nook. It is stuck on the Nook multicolored sign. I dont know what to do now...

The only thing i changed before this was to change permission for installing the market...

Any ideas what to do?

Thanks in advance!