Nook HD+ 2.0.4 update silently corrupts sdcard data

[someone0]

Well, I'm not entirely sure if that's correct. At least if you are willing to play with the wifi router. I mean shouldn't authorization only take a few packet and it's tiny in size compare to say downloading update. So, I would say it's entirely possible to put restrict the speed of the wifi on the nook at least initially until you did manual OTA mod. So, if you are willing to play around, I guess you can restrict the speed down to like a few KB/s or maybe drop the packet a lot. Unless the update take place prior to login? IDK, I haven't don't that since the first time I boot my nook.

 

[verygreen]

I found out that when you interrupt the initial download of update (at registration time) by powering off the Nook (as soon as you get the downloading bar, press and hold power + home buttons, having not super fast link so that download takes more than 10 seconds is a big plus), then next time you turn it on and continue registration, it does not see the update anymore. The about tab shows "downloading" progress bar that's stuck in place basically for hours.
I imagine it will retry eventually, but nothing you cannot solve with a quick firewall rule or two.

 

[leapinlar]

Well, if you are talking about extreme measures, there are lots of ways to do it. I did it. One way is to power off when it gets to the first screen. Use verygreen's first CWM card to boot to. Use adb to mount both interior system and data. Symlink build.prop to data. Then put the 2.0.4 build.prop in data and boot again. Then when it checks for version it is fooled into thinking you have 2.0.4 and does not update. That's not how I did it, so there are other ways.

Edit: 12/21/12 - I did this procedure with my second HD+ unit. It worked great. But I used my own CWM that I modified for internal memory. I wiped /system and /data (leaving /data/media alone) then flashed factory.zip (2.0.0) from partition 7, mounted /data and/system with CWM and connected to ADB. Used ADB to add the build.prop from 2.0.4 to /data and deleted the 2.0.0 build.prop from /system. Then symlinked the 2.0.4 build.prop in/data to /system. Rebooted, update checked and thought I was on 2.0.4 so did not update. Registered and proceeded to all-in-one root and do gapps etc.

Sent from my Nook HD+ Running CM10 on SD

 

[Zaben]

I'm trying to parse this into practical terms: are you saying these errors occur when writing from a PC to /ext_sdcard over MTP, or only when writing to /ext_sdcard from the HD+ itself (i.e. downloading from a browser or copying files w/ a file manager)?

I've written quite a bit of data to a 64GB SD over MTP with no panick reboots and I've accessed some of those files quite heavily and not found any corrupted. In fact, I started using the HD+ for this purpose because the only card reader I had handy was failing with large tranfers (otherwise I would avoid MTP). I don't know that I've ever written to /ext_sdcard from the HD+ itself, though--all app data lands internally on /sdcard, and I mostly load media over USB, so for all intents and purposes the card could be read-only.

Out of curiosity, what kind of file transfers were you attempting when you got these errors (what kind of files/jobs from where to where)?

I have the same experience as you. 64GB Sandisk card with several transfers from PC to my HD, I don't see any file corruption related messages so far.

 

[someone0]

Anyone know if this bug still existin 2.0.5, or B&N only release 2.0.5. to screw us up by removing root.

 

[lkmiller]

Anyone know if this bug still existin 2.0.5, or B&N only release 2.0.5. to screw us up by removing root.

Apparently it still exists:

http://forum.xda-developers.com/showpost.php?p=35909269&postcount=259

 

[someone0]

I guess that means people should stick with version 2.0.0-2.0.2

 

[cattywh]

Good to know that.