5 Replies Latest reply on Jul 9, 2011 12:15 PM by DeanGibson

    DNS issues that affect other devices with 1.2 upgrade

      It's been weeks. I see many others on the forums still having this problem but can find no reasonable fix -- or a sign of one coming.

       

      There are two Nook Color users in my home. One of them "forgets repeatedly" that since the 1.2 upgrade, our other devices, i.e. computer and internet TV, lose connectivity (DNS Access) if the WiFi on the Nook Color is used. I have to disable the WiFi on the Nook, reset the router and devices everyday.

       

      As someone who works in IT, this is a programming issue and should be corrected without novice users jumping through hoops. It's absurd to think we should get a different router from our ISPs, and ISPs shouldn't be fielding so many unecessary technical assistance calls that are not caused by their service.

       

      Fix it. At the very least, distribute a downgrade program that doesn't destroy user content and prevents the auto-upgrade that re-creates the problem.

       

       

        • Re: DNS issues that affect other devices with 1.2 upgrade
          Just a hunch, but maybe your router's LAN IP address range is too small?  so maybe your subnet is oversubscribed by the time your nook color attempts to connect?
          Maybe you could also reserve a local IP address for your color nooks.
          or you need a firmware update?

          edmannix wrote:

          There are two Nook Color users in my home. One of them "forgets repeatedly" that since the 1.2 upgrade, our other devices, i.e. computer and internet TV, lose connectivity (DNS Access) if the WiFi on the Nook Color is used. I have to disable the WiFi on the Nook, reset the router and devices everyday.

           


           

          • Re: DNS issues that affect other devices with 1.2 upgrade
            roustabout

            @edmannix:  a downgrade is possible.  Since the downgrade involves setting up a CWR boot disk to start with, you could

            - make the CWR disk

            - install the current manual nooter to it *and* get a copy of the Ham and Cheese APK installer, which for me has been an absolute requirement to get Titanium to run properly

            - root

            - install Titanium and backup

            - put the 1.0.1 downgrade/restore to stock zipfile on your NC

            - run it, and immediately follow it with the prerooted 1.1 update (seriously, you can just daisy chain those two, no need to restart between them)

            - on boot, skip the out of box experience and do not reregister

             

            A rooted 1.1 device is immune from the OTA update. 

             

            If you decide to go this routeI would recommend after you do the 1.1/root applying either monster root pack or the 3.0 Autonooter, as the sideloadable root that I have is not complete. 

             

            Once rooted in 1.1 reinstall Titanium.  You should be able to restore from your 1.2 backup your apps and library settings.  (I have not tried it in the 1.2 > 1.1 direction, but this works in the 1.1 > 1.2 direction.)

             

            If Titanium complains about non-market apps, it might well be worth trying to flash in the unsigned APK installer.  It was written for 1.2, but if it will load on 1.1, that would probably do the trick. 

             

            If you're able to restore yourself from the Titanium backup, on reboot your device should now be correctly registered, able to use wifi as 1.1 devices were, and contain your books.

             

            If the titanium restore can't restore apps in 1.1, it may still be able to restore data.  (Probably can, actually, but as I say, the testing I remember clearly has been in preserving material going 1.1 to 1.2, where the system settings can be restored even though some system apps can not.  IE:  my browser bookmarks were restored;  the 1.2 browser vetoes any attempt to restore in the old browser app from 1.1) 

             

            The reason to skip the registration with BN is to avoid creating a new registration token.  It took me a while to figure out why my NC was being remote reset after a backup was restored, but I finally realized that a registered device has a local crypto token that's presented to BN.  The token is generated during registration if it's absent.  If your copy and their copy disagree, their software assumes your device is screwed up and resets it.  A freshly installed NC doesn't have the token, but it can be restored from a backup. 

             

            What I can't tell you is exactly what element of the backup contains the token.  I've been trying to push over as many system settings as possible, since no one's paying me to validate these processes :smileyhappy: 

             

            This weekend I'm in the process of putting together some "your nook's not bricked" documentation that (hopefully) will give people pointers to a number of these things - there's a lot of overlap in things people want to try with 1.2 in particular.

             

            I have not used bookshelves, so I can't guarantee that, either. 

             

            It's something.  It's free, and it doesn't take too long to do (probably an evening if you haven't assembled the tools before.) 

             

            I agree - BN needs to be working on getting a much easier free backup utility into the shop, like yesterday.  Not just because they're good people and know there's local content, but because the reset devices a couple of weeks ago. 

             

            I've asked the new community liason to try to let us know more of what happened, what's being done to prevent a re-run, and for status on either making a backup utility available or tying the shelf data to our device accounts, as well as our "what books do we own" data.