(OUTDATED) All-in-One, ROOT + manual OTA + Enable Unknown Source+ GAPPS

[leapinlar]

Began the rooting process last night. Best I can tell, with a new device, there's no way to prevent the automatic update, as it happens before there is the opportunity to enable ADB. I neglected to look closely at the version that got automatically installed--turns out it was 2.0.5

Went through verygreen's process first, then was trying to run CM10 from sd card. No luck--simply would not boot at all from sd card. Tried 3 different cards, multiple times reformatting the cards with the hp usb utility and writing the image file with win32diskimager. No success.

Went back, did the factory reset, both from the settings menu (settings-device information-erase & deregister device) as well as by holding the n key while powering up.

Then tried someone0's all-in-one method; parts of it worked, but anything that required su did not.

Went through the reset process then attempted to reroot several times, to no avail.

Wondering if I can reset or reflash the device back to 2.0, 2.0.2, or 2.0.4, then root and install the OTA block.

Or perhaps I'll get lucky and someone with greater technical skills than I will figure out how to root 2.0.5.

Suggestions would be appreciated.

Many thanks to verygreen, someone0, LeapinLar, and others for all the work they've done.



Nook HD 16G
win7 build 7601
sd cards Samsung 8 gb, Ridata 16 gb, Kingston 16 gb (all have worked fine in my Nook Color and Nook Tablet)

The reason the card would not boot is because you have an HD. The SD CM10 does not work on the HD, only the HD+.

 

[someone0]

Went back, did the factory reset, both from the settings menu (settings-device information-erase & deregister device) as well as by holding the n key while powering up.

Since you already not have root and on 2.0.5 why not try to manually fail boot 8 time and let it do a full factory reset first then try skip OOBE? To for a fail boot, you first power the nook off, then hit the power button, and when it's trying to boot, hold on to the power button, and I think about 10sec after it will force poweroff. You timing have to be quite good and make sure it's getting a success boot. You basically have to do that at least 8 times. IDK about you guys, but when I first got my Nook it was at 2.0.0, and I accidentally upgrade to 2.0.2 after the full reset it went back to 2.0.0

 

[pumpal]

I'm still confused - if the OTA update was set to "manual" by the 'allinone.sh' script, why mine updated alone then ? .. I am pretty sure I saw the expected value after the Sqlite portion of the script...

Also, is it possible for those updates to reflash the boot loader too, preventing it from booting from SD? Right now it is still booting and I am going to stick to the CM10 image for now, until there is more clarity on that subject ..


New to Android, experienced with Linux - I am thinking - if the 'su' binary was made root:root in the /data/su directory, it would be possible to re-gain root using it now, unfortunately that directory is still there, but su inside it is shell:shell - maybe it's a good idea to add a chmod to allinone.sh script.. ?


P.S> B&N note - B&N, the only reason I bought this device was because of the rooting and CM10 abilities, and I am sure I am not the only one .. so think about that while you kill your otherwise not-flawless device's capabilities that make it interesting for us. I will be returning it if I am stuck with your limited OS!

 

[jasonwho]

first is there a way to revert back to 2.0.04 of you never did the cwm method? I too did the allinone install and thought OTA was disabled I guess it did not work. I tried to run it again on 2.0.05 and of course it wont work gives the SU others have reported. I did this when typing in the su command put data/su/su in where typically su is in the script. Its not 100% it will as if your root. The it is not working on changeing the databases see this cmd attempt: (bold is the change in the command i ran from the script which i did manually instead of using the bat.)

C:\adb>adb shell /data/su/su -c /data/su/settings.sh
Error: unable to open database "/data/data/com.android.providers.settings/databa
ses/settings.db": unable to open database file
show new install non-market apps setting
Error: unable to open database "/data/data/com.android.providers.settings/databa
ses/settings.db": unable to open database file
Error: unable to open database "/data/data/com.bn.devicemanager/databases/device
manager.db": unable to open database file

If you see 'install_non_market_apps|1' above
then you have allow install Non-Market apps.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
show new Nook OTA update setting
Error: unable to open database "/data/data/com.bn.devicemanager/databases/device
manager.db": unable to open database file

If you see 'com.bn.device.fota.mode|fota operation mode|fota|manual' above
then you have set Nook OTA update to manual.

C:\adb>

So its not working to change databases. and I followed the script each step as i did the commands in CMD manually.

Now I was able to get Google play to load again by using /data/su/su in the script, it did report errors and following the allinone script before again putting in /data/su/su instead of su in the su commands I was even able to download and install a game from google play.

This hopefully help out those who got hit with the 2.0.05 upgrade like I did and needed to get google play back, also make sure you have your launcher to get to google play.

 

[pumpal]

As I said, the 'su' binary in the /data/su is not owned by root, it's shell:shell, so I don't think you can use it to gain root.

 

[jasonwho]

No it dont seem using su gains root anymore, but using it in a command that requires su and doing the workaround I did in the allinone script it did error but allowed google play to load and gave access to laod apps. Hopefully someone can figure out how to gain full root and SU use again.

 

[smartypantsdotcom]

Reset to 2.0!

Since you already not have root and on 2.0.5 why not try to manually fail boot 8 time and let it do a full factory reset first then try skip OOBE? To for a fail boot, you first power the nook off, then hit the power button, and when it's trying to boot, hold on to the power button, and I think about 10sec after it will force poweroff. You timing have to be quite good and make sure it's getting a success boot. You basically have to do that at least 8 times. IDK about you guys, but when I first got my Nook it was at 2.0.0, and I accidentally upgrade to 2.0.2 after the full reset it went back to 2.0.0

Thanks, that worked to reset it back to 2.0.
In the meantime I've read through the threads more closely and learned how to bypass the OOBE 'out of box experience' so that the automatic update dies not happen and i can enable adb.

Tomorrow i will retry someone0's all in one and report back.

 

[dbrons]

I spent all morning getting adb working and recognizing my Nook hd+. I was concerned about the update so I did a reset but it went right to update, so then I did do the interrupt 8 times trick and got back to 2004 from 2005. I think that was because I had downloaded and installed 2004 myself.

Anyway I got it and used the info here to bypass OOTB. I wasn't sure how to run allinone though. I tried through a command prompt but there was a lot of "adb not a valid command" in the verbiage so I tried executing it with adb and not sure if that was right.

I am listed as "Test" on the nook, I have no browser or any evidence that the root worked,

Adb does see my nook hd+ . thanks for any help
Dave

 

[pumpal]

I tried through a command prompt but there was a lot of "adb not a valid command" in the verbiage so I tried executing it with adb and not sure if that was right.

Not sure I correctly understand what you did, but it sounds adb is not in the system path. Open a cmd and type 'adb' to see if that's true. If it is unable to find it, simply copy all the needed files to the folder where adb is, open a cmd and navigate to that folder (cd ... ) and then run allinone.bat from there. To verify it worked, at the end do 'adb shell', then check that /system/bin/su exists and you are able to execute something like 'su -c whoami' which would return 'root' as a result. To see the PlayStore, go to the "Apps" screen and then while holding the volumeUP button, long press and swipe a little the "Apps" sign at the top of the screen - the 'Extras' screen should open with PlayStore in it, then use it to install another app launcher that will always see all.


I reverted mine to 2.0.2 using the '8 failed boot approach', and now I am trying to think of something that would allow to regain root after 2.0.5 hits. As I mentioned, I am new to Android and just now I have found that /data is (of course) mounted with 'nosuexec' ... so having a 06755 0.0 'su' in /data/su/ doesn't help as I initially hoped .

 

[dbrons]

Not sure I correctly understand what you did, but it sounds adb is not in the system path. Open a cmd and type 'adb' to see if that's true. If it is unable to find it, simply copy all the needed files to the folder where adb is, open a cmd and navigate to that folder (cd ... ) and then run allinone.bat from there. To verify it worked, at the end do 'adb shell', then check that /system/bin/su exists and you are able to execute something like 'su -c whoami' which would return 'root' as a result. To see the PlayStore, go to the "Apps" screen and then while holding the volumeUP button, long press and swipe a little the "Apps" sign at the top of the screen - the 'Extras' screen should open with PlayStore in it, then use it to install another app launcher that will always see all.


I reverted mine to 2.0.2 using the '8 failed boot approach', and now I am trying to think of something that would allow to regain root after 2.0.5 hits. As I mentioned, I am new to Android and just now I have found that /data is (of course) mounted with 'nosuexec' ... so having a 06755 0.0 'su' in /data/su/ doesn't help as I initially hoped .

Thanks I'm getting somewhere now. I had the files in with adb, just ran the command wrong. But really the problem was the driver wasn't holding for some reason, adb couldn't see my HD+ again, so I reinstalled the drivers, then immediately rad command as you suggested and it did work, and restarted my device, but right now it seems hung up on "uploading files to block OTA and allow sources". The previous section, cleaning up install files ended with "device not found".

But anyway, I'm getting there, thanks. As to the update, I bypassed OOTB.
Dave

Added For some reason adb can see my HD+, then it loses it. I reinstalled the drivers when I realized adb was no longer showing my device, got it working again, but partway through the batch, at the second restart, adb stopped working.. I got adb going again and when the allinone install seemed to be failing at the same place I cycled between PTP and MTP and the install completed.
Unfortunately, I now have lost adb again and fixing it and running adb shell yields error protol fault- no status.

 

[pumpal]

For some reason adb can see my HD+, then it loses it.

Well, I think you are experiencing the same thing as me. As nobody else mentioned it, I thought it must be my setup, but it's probably not.

As I couldn't make adb drivers to install on W8, I installed Debian on a VirtualBox VM and worked from inside it. I connected nook to the virtual machine using the USB capabilities of VBox.

What I observed though is very similar to what you have - nook connects, then after about 5-6 seconds it disconnects and reconnects again with slightly different usb ID. This thing brakes the script and it can only partially execute.

Anyway, what I did and suggest you to do is - I slightly changed the allinone script. I removed all occurrences of "wait-for-device" from the command lines (just this string) and after each 'adb reboot' I added a line that will wait for a key press. I used the Linux script and added 'read -n 1 -s' but for the Windows script it would just be a 'pause' . So what I suggest you to do - do that change, then move to the nook and do a "deregister device and reset" to undo all partial changes the script possibly did so far, then skip OOB again and enable debugging (ADB), then return back to PC and run the script again. After each reboot, when nook comes back on, in a separate cmd window make sure the device is permanently accessible (wait for that reconnect and make sure you can see it with adb devices and can connect to it with adb shell) and then go back to the window you ran the allinone.bat from and press a key so it continues with the next step. That way it should complete without any errors. Hope that gives you a helpful idea.

Greets.

 

[dbrons]

Thanks a lot. I kinda thought Windows 8 might have something to do with it. I did do another reset and I was going to try on a Windows xp computer I just pulled out of the closet

If I can't get that going I'll try as you suggested. I don't know really how to edit a bat file but I'll look it up. thanks again
Dave

Well, I think you are experiencing the same thing as me. As nobody else mentioned it, I thought it must be my setup, but it's probably not.

As I couldn't make adb drivers to install on W8, I installed Debian on a VirtualBox VM and worked from inside it. I connected nook to the virtual machine using the USB capabilities of VBox.

What I observed though is very similar to what you have - nook connects, then after about 5-6 seconds it disconnects and reconnects again with slightly different usb ID. This thing brakes the script and it can only partially execute.

Anyway, what I did and suggest you to do is - I slightly changed the allinone script. I removed all occurrences of "wait-for-device" from the command lines (just this string) and after each 'adb reboot' I added a line that will wait for a key press. I used the Linux script and added 'read -n 1 -s' but for the Windows script it would just be a 'pause' . So what I suggest you to do - do that change, then move to the nook and do a "deregister device and reset" to undo all partial changes the script possibly did so far, then skip OOB again and enable debugging (ADB), then return back to PC and run the script again. After each reboot, when nook comes back on, in a separate cmd window make sure the device is permanently accessible (wait for that reconnect and make sure you can see it with adb devices and can connect to it with adb shell) and then go back to the window you ran the allinone.bat from and press a key so it continues with the next step. That way it should complete without any errors. Hope that gives you a helpful idea.

Greets.

[

 

[Databit42]

8 boot loop,enable ADB before OOBE

I bought a nook for my wife and wanted to put Kindle reader on it and it has been an adventure.
I have learned alot and some of it I was not able to find here.
When I started out I thought I could just install from a browser, but of course not.
So I learned here how to hack it and install the APK except I could not get the device to recognize under android and once I did it would not show up under ADB devices. A lot of deleting and refreshing later I got it recognized but now trying to run AllInOne I am getting that SU is failing. So I found that people are skipping the OOBE. But I have not been able to do that on the HD. The push right button and swipe top left to right did not do anything. I found the factory menu by pushing Volume Up and touching the bottom right corner. But I did not see a way to turn off OOBE. If you do volume down though and touch bottom left corner it allows you to enable ADB. So before OOBE was able to start, I turned on ADB and pushed AllInOne and it succeeded.
After I finished, I allowed the OOBE to run and it ran the critical updates and upgraded to 2.0.5.
Once in, I loaded the Extras in apps by going to Apps and holding the up volume and pressing on the title bar. Then launched Google appstore. I found and downloaded Kindle reader and it allowed me to install and run it.

 

[Nuor60]

As I couldn't make adb drivers to install on W8 ...

My experience was that I could get driver to work on both w7 and w8 but on w7 the USB connection was somewhat unstable while on w8 everything was smooth with no issues.

 

[mzjc]

I bought a nook for my wife and wanted to put Kindle reader on it and it has been an adventure.
After I finished, I allowed the OOBE to run and it ran the critical updates and upgraded to 2.0.5.
Once in, I loaded the Extras in apps by going to Apps and holding the up volume and pressing on the title bar. Then launched Google appstore. I found and downloaded Kindle reader and it allowed me to install and run it.

Are you still rooted after it updated to 2.0.5?

I would love to be able to just side load Google Play and have it work, but read it wouldn't unless rooted!

 

[someone0]

Are you still rooted after it updated to 2.0.5?

I would love to be able to just side load Google Play and have it work, but read it wouldn't unless rooted!

There is a new root for 2.0.5 now, check out leapinlar thread in the developer forum.

 

[leapinlar]

Are you still rooted after it updated to 2.0.5?

I would love to be able to just side load Google Play and have it work, but read it wouldn't unless rooted!

You need root to install from ADB. But if you flash my gapps zip with my CWM as described in my thread in the dev section, you don't need root. It runs fine without root.

Sent from my Nook HD+ Running CM10 on SD

 

[dysan911]

You need root to install from ADB. But if you flash my gapps zip with my CWM as described in my thread in the dev section, you don't need root. It runs fine without root.

Sent from my Nook HD+ Running CM10 on SD

Which only works on HD+ right leap? I bought my wife a Nook HD and am trying to root it. There's a lot of confusion between the methods of the HD+ vs HD, then compounded by the 2.05 update. My wifes Nook HD does have 2.0.5 If I can get ADB to work can I just run that allinone script?

 

[someone0]

Nope, there will never be a root mod for 2.0.5 through ADB. It's not possible ATM. HD people just have to sit tight until you have CWM for that. The only other way to gain root is to restore it back to original firmware and then be on skip OOBE and then use all-in-one mod.

 

[Trance-M]

So I didn't totally turn off my allinone hd+ since the 2.0.5 update came out, but it updated anyways I just noticed. Only thing I noticed was the counter went to 100% really fast when waking up my hd+. Didn't even think it was updating, just found out. Well, the tv app I got from a SII now works. Play store also does, but root will be gone I guess. Stiill haven't turned it off, must check ADB tomorrow. Maybe keep it a while like thiis as long as I don't need root access.