MobileRead Forums - View Single Post

taosaur · 12-17-2011, 04:26 PM

I'm updating this thread because it was one of the few relevant google results I got when trying and having trouble rooting a newer-hardware Nook First Edition purchased used as a Xmas gift. To answer the title question, yes, after numerous attempts and several hours invested, I've succeeded in rooting firmware 1.7 via the web exploit.

I recommend anyone trying this method read the talk page that jhempel linked in the OP. I could probably have saved myself 2-3 hours if I'd followed the suggestion there to copy the connect-and-push commands to the clipboard with new line commands included. Presumably it's what the .bat file is intended to do, but I had no luck using the .bat file.

Stopping partway through this process (having run ratc.bin but not successfully pushed init.rc), I came back to it today to find my Nook unstable, the browser crashing immediately after opening so that I could not attempt the web exploit. The Nook wouldn't seem to fully factory reset from settings, and triggering "factory fallback" restore (power off Nook, then hold the power button for 12 seconds after the screen flashes, 6-7 times in a row) didn't work the first time, either. I thought I was screwed.

The watchwords for dealing with this device, though, seem to be "try, try again." After going through the 7-failed boots six times and seeming to succeed (getting the "update installing screen") three times, it finally stuck and my Nook reverted to firmware 1.4.3.

Actually rooting once I was registered and updated again took less than 30 minutes. I would say it took on average about a dozen tries to trigger adbd via the web exploit, and I did it at least half a dozen times these past two days. You really have to put on your Zen hat and be prepared to do everything over-and-over to get through this procedure. I kept a text file open with the relevant console commands handy for copying to the clipboard.

Hopefully this post will save the next person some headaches. Just keep in mind that just about every step of this process is a toss of the dice; if it doesn't work, just do it again.

12-17-2011, 04:26 PM	#13
taosaur intelligent posterior Posts: 1,562 Karma: 21295618 Join Date: Mar 2009 Location: Ohiopolis Device: Kindle Paperwhite 2, Samsung S8, Lenovo Tab 3 Pro	I'm updating this thread because it was one of the few relevant google results I got when trying and having trouble rooting a newer-hardware Nook First Edition purchased used as a Xmas gift. To answer the title question, yes, after numerous attempts and several hours invested, I've succeeded in rooting firmware 1.7 via the web exploit. I recommend anyone trying this method read the talk page that jhempel linked in the OP. I could probably have saved myself 2-3 hours if I'd followed the suggestion there to copy the connect-and-push commands to the clipboard with new line commands included. Presumably it's what the .bat file is intended to do, but I had no luck using the .bat file. Stopping partway through this process (having run ratc.bin but not successfully pushed init.rc), I came back to it today to find my Nook unstable, the browser crashing immediately after opening so that I could not attempt the web exploit. The Nook wouldn't seem to fully factory reset from settings, and triggering "factory fallback" restore (power off Nook, then hold the power button for 12 seconds after the screen flashes, 6-7 times in a row) didn't work the first time, either. I thought I was screwed. The watchwords for dealing with this device, though, seem to be "try, try again." After going through the 7-failed boots six times and seeming to succeed (getting the "update installing screen") three times, it finally stuck and my Nook reverted to firmware 1.4.3. Actually rooting once I was registered and updated again took less than 30 minutes. I would say it took on average about a dozen tries to trigger adbd via the web exploit, and I did it at least half a dozen times these past two days. You really have to put on your Zen hat and be prepared to do everything over-and-over to get through this procedure. I kept a text file open with the relevant console commands handy for copying to the clipboard. Hopefully this post will save the next person some headaches. Just keep in mind that just about every step of this process is a toss of the dice; if it doesn't work, just do it again.