[NST]MinimalTouch 1.1beta5 (+Index to manual rooting)

[xd4d3v]

Hi All.

I managed to get my nook simple touch rooted with no problems.
but i was struggling to get the gapps step to work.

I first started youtube and entered my account and then went to gmail.
I refreshed a few times, but later gmail stopped working alltogether and would close after running. no prompt no FC just flashed the screen and went back. same as youtube and market.

I did the fix here http://forum.xda-developers.com/showpost.php?p=19441352&postcount=33
and managed to get market and gmail to work.

However, I still have two problems.

1) Youtube doesnt start at all, just flashes and goes back to the previous screen
2) market searches don't work.

Any idea how to fix these?

 

[digixmax]

...
However, I still have two problems.
...
2) market searches don't work.
Any idea how to fix these?

See this post.

 

[klausef]

The reason you need to be able to use the YouTube app is to log in and thus attach your device to a Google account. If YouTube fails for some reason or another, you can still do the same through the GMail or Google Calendar apps by adding an account through 'settings.'

 

[xd4d3v]

The reason you need to be able to use the YouTube app is to log in and thus attach your device to a Google account. If YouTube fails for some reason or another, you can still do the same through the GMail or Google Calendar apps by adding an account through 'settings.'

Thanks guys.
Youtube doesnt really matter, not that we can watch it. just curious.
PS: workaround working great

 

[MTKnife]

I've searched all through the Nook Development forums to try to find out why I can't get ADB to work, but didn't find anything....

I rooted my Nook with Beta 5 some time ago; I'm not sure if I ever used ADB. Today, I tried to access the Nook Shop, and got a connection error. Oddly enough, I've never bought a B&N ebook before today, and so I don't know if I've always had this problem, but to fix it I did a factory reset, then upgraded to 1.1.2, and that fixed it. I then re-rooted with Beta 5, and the shop problem stayed fixed (except that the "Shop" button still doesn't work--but there are other ways to get into the Shop).

I thought that, while I was reinstalling everything, I might try a new kernel. For that I need ADB (yes, I could use Noogie, but once ADB started giving me trouble, it became a matter of principle). I can't get ADB to work. The modified uRamdisk for Beta 5 should include both wireless and USB ADB support. I can get the Windows drivers to install properly, and Windows to recognize the Nook as an ADB device, but I can't get ADB.EXE to list it among the connected devices.

I also can't get ADB wireless to work. For a while, I forgot I had to run ADB Wireless, but when I do run it, and press the big button, it just hangs after the SU permissions toast is displayed, until I get the Wait/Force Close prompt. If I do force close it, when I bring up the app again, all I get is a blank screen, until I reboot the device--but the button still doesn't work.

Oh, and yes, I do have USB Debugging enabled in the Development settings.

 

[Renate]

ADB over WiFi and ADB over USB are mutually exclusive.
They are controlled by service.adb.tcp.port

Have you done all the steps for getting ADB over USB to work?
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB

 

[MTKnife]

ADB over WiFi and ADB over USB are mutually exclusive.
They are controlled by service.adb.tcp.port

I realize I can't do both at the same time, but doesn't Beta 5 include support for both? I'm using the adbWireless included in the FullTouch package. The uRamdisk file has been modified, so at least one of them should enabled.

Have you done all the steps for getting ADB over USB to work?
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB

I used a package that includes an already-edited inf file (I can't find at the moment where I downloaded it, but the name of the downloaded file is "Nook_Touch_USB_ADB_Drivers.zip"--I just checked, and yes, it includes the required modifications to the inf). In any case, a problem with the USB drivers wouldn't explain my inability to get adbWireless to work, before I even get to the PC to try to connect.

EDIT: Since the first post doesn't explicitly state whether beta5 supports USB, Wi-fi, or both, I thought I'd compare the uRamdisk that was installed with one of the ones found here: http://forum.xda-developers.com/showthread.php?t=1337653. However, it's apparently not possible to download these files without either installing a download manager (no thanks--I pick my own download managers) or signing a petition (no thanks--the idea of a petition is you sign it voluntarily, not because of coercion). A Google search failed to find any mirrors that didn't require a sign-in.

 

[digixmax]

I realize I can't do both at the same time, but doesn't Beta 5 include support for both?
...

Beta5 supports both but you have to choose one or the other by picking one of two options for its PART-1-START sub-package: either beta5-2 XUFullTouch-PART-1-START or beta5-2 XWFullTouch-PART-1-START.

I wanted wireless, so I chose beta5-2 XWFullTouch-PART-1-START, and the ADB Wireless Widget (from the Google Playstore) fires up the connection like a charm.

 

[MTKnife]

Beta5 supports both but you have to choose one or the other by picking one of two options for its PART-1-START sub-package: either beta5-2 XUFullTouch-PART-1-START or beta5-2 XWFullTouch-PART-1-START.

I wanted wireless, so I chose beta5-2 XWFullTouch-PART-1-START, and the ADB Wireless Widget (from the Google Playstore) fires up the connection like a charm.

Oh, I see now--I had downloaded some time ago, and forgot about the choice; looking back at it, I didn't read carefully, and thought that the two "start" packages were the Minimal and Full. It turns out I have the XU, so I should be able to use ADB through USB, but that's still not working. At least I know why the wireless doesn't work. Any ideas what the problem with the USB might be?

 

[MTKnife]

OK, I found the source of the driver package again. It's the thread here: http://forum.xda-developers.com/showthread.php?t=1125094&highlight=usb. I just noticed something strange, though: when I follow the instructions and update the driver for the USB Mass Storage Device, I can no longer see the drive (in other words, I don't get two devices, just one)--and that's true even if I have "USB Debugging" unchecked on the Nook. More strangely still, even if I uninstall the ADB Interface, reconnect the Nook, and let it auto-install as a USB Mass Storage Device, I have access only to the SD card; the internal storage shows up as a drive, but the drive isn't accessible.

EDIT: Just to be sure, I manually edited the generic ADB USB driver, and the results are identical, including the fact that neither drive any longer shows up.

 

[MTKnife]

Got it working now--I went back to the beginning and did a factory reset again. I think the problem may have been trying to do the manual upgrade to 1.1.2 after a factory reset, which I did because I didn't realize that the Nook would still be on 1.1.2 after a factory reset now.

Anyway, thanks for the help.

 

[eded333]

Bye

I've been absent for quite some time as you may have noticed. I won't be updating my work on the NST any more.
If anyone wants to continue updating it or reusing it they are welcome.
Real life dosn't leave me any time to play with this any more and I just sold my Nook.
Thanks and good luck to the community.