Related
This Nooter is officially supported by The Nooter Project for Nook Simple Touch​
I'm not adding certain things because I don't believe they should be available as part of a rooting kit designed to give users more control of their devices. Things such as additional readers or CPU Clocks are up to the user to install themselves and needlessly putting them in Nooter creates app bloat that a user may or may not want. You can always drop Apps you want into \nooter\data\app and they will install automatically when you root the device. This Nooter is designed with the sole purpose of opening up the possibilities of the device by giving users Root, Google Apps, and other Apps which make the device more usable as an android device than just an e-reader.
What it does:
Enables ADB via uRamdisk
Installs adbWireless
Installs Button Savior
Installs Amazon Marketplace
Installs su and Superuser.apk
Installs ADW + E-ink Friendly Theme
Installs Busybox & Busybox Installer/Uninstaller
Installs Gapps (Gmail, Market, Youtube, Others)
Installs NookColor Tools (To Enable Non-Market Installs)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
May 26, 2012 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch Glow
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Using the Nook Simple Touch can result in it becoming unusable (bricked).
You must have enough intelligence to follow instructions.
Let's get started:
Download CWM from here: http://forum.xda-developers.com/attachment.php?attachmentid=806435&d=1323121399
Download TouchNooter from here: glownooter-1-12-25.zip - Uploaded
Download eded333's beta5-1XWUMFTouch-PART-2-END from here: http://nooter.googlecode.com/files/beta5-1XWUMFTouch-PART-2-END.zip
Unzip CWM and you'll find an image file you will then need to write this to an SD Card.
Linux: Unzip and use dd if=cwmimagename.img of=/dev/sdcard
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
User "n" to select, Left Buttons to go up in the menu, Right Buttons to go down in the menu, Power Button to go back.
Install from zip
Choose zip from sdcard
glownooter-1-5-26.zip
Click Yes and let Complete
Remove SD Card and press Power Button to go back one to main menu
Click Reboot
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from ADW's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from ADW's App Drawer.
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
User "n" to select, Left Buttons to go up in the menu, Right Buttons to go down in the menu, Power Button to go back.
Install from zip
Choose zip from sdcard
beta5-1XWUMFTouch-PART-2-END.zip
Click Yes and let Complete
Remove SD Card and press Power Button to go back one to main menu
Click Reboot
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
mali100 - For porting CWM to Nook Simple Touch
eded333 - The second zip to fix Market Issues.
MrMuffin - For the original Market Hack that we're using.
If I'm using an app in TouchNooter and you would like Credit/Thanks, or to have it removed, please PM me, otherwise I might not see your requests
Currently Working On: Raspberry Pi Triple Boot System
It works!! Thank you thank you thank you thank you!
It works.
You couldn't have made me day any happier, Your hard work has given me a small tablet that I will use at work for keeping notes and recalling info. I'll be Joe cool with the info.
Thank you for all your hard work, I'll look in my couch and find something to donate.
Anyone experiencing problems accessing settings/screen to change the screesaver Folder?
Sent from my NOOK using xda premium
I have previously rooted using Roustabout's tinynoot. If I decide to do this Nooter, would I have to restore to stock first? (Haven't decided yet, pretty happy as is, but would like to know the options.)
Thanks,
Dude, nice job! Now to go buy a glowlight.
Hi,
Hmm, awesome =), just installed this on my Nook STR Glow.
Two questions
1. What's the best way to get Market searching enabled?
I've heard of installing SearchMarket - however, how do you do that? Do you just find the APK and install it manually?
2. Is it possible to install the Multitouch and NoRefresh patch from here?
http://forum.xda-developers.com/showthread.php?t=1568560
Or is the Glowlight version different enough that these won't work?
Cheers,
Victor
Anybody have trouble with getting the Opera Mini that comes with this to work? It doesn't even open for me. I installed Dolphin Mini and it seems to work ok but I'd like to get Opera working.
Multi-language root
This is great!
Is there a way to add menus and/or keyboard with another language?
xanadu1979 said:
Anybody have trouble with getting the Opera Mini that comes with this to work? It doesn't even open for me. I installed Dolphin Mini and it seems to work ok but I'd like to get Opera working.
Click to expand...
Click to collapse
Try opera mobile, not mini.
@glowco: I'm looking at GD's scripts and the tinynoot scripts right now.
It looks as if I used the same binary (despite the different name) for the
/system/app/Superuser piece (the file sizes and mod dates are identical.)
I used a different release of busybox, though. So the busybox my script installed would be overwritten by the glownoot busybox.
My advice is that if you want to get the google apps working, restore from a nonrooted backup and use this tool. I'm very likely to ignore my advice on my own device and see what happens, but today's not likely the day that's going to happen.
The line in glownooter that does the copy-in is:
package_extract_dir("system/xbin/", "/system/xbin/");
Unless the package_extract_dir command wipes a directory before copying in the file, you'd overwrite busybox at that step but leave the links to it. The links would probably continue to work but if there's an important difference between the two busyboxes, you might find it made trouble in a weird, random way long after you'd forgotten that you'd overlaid one root with another.
The busybox updater/manager might alleviate that issue - not sure what Ed's or GD's take on overlaying one root with another is.
Roustabout, thanks for your reply. I'm not rushing into anything, so if you do decide to try installing this over yours, let us know the results. (I tend to like the easier approach if it works okay.)
Maybe I should take this opportunity to ask an additional question: what will this root let me do that tinynoot didn't, other than run the Market? What additional apps would it allow me to run that would actually run well?
One app I have partially working on tinynoot is Jabiru, a jabber chat client. The basic chat connection works, but the Conference function crashes the session. I doubt this other root would make a difference in something like that?
Thanks.
I just did this and it works great. The only problem I have noticed is that when I am in gtalk and trying to chat I only see the top two rows of keys. Is anyone else getting this or know how to fix it?
Hi,
before to try rooting the nstglowlight, is it possible to make backup with noogie like the normal NST ?
Yes, you can and should boot from a noogie disk and make a whole-device backup before changing things up, just like with the NST.
Assuming that tinynoot used MinimalNooter as a basis for it's design (as is evident by the forum convo) then GlowNooter will run perfectly fine without any issues, however keep in mind that because the package names for files in GlowNooter in /data/app are likely to be different than those in tinynoot you'll end up with multiple copies of things like Amazon market, which doesn't actually affect performance, but can take up more space. So you have two options, the first is to do a fresh install onto a fresh NTG, or you can install this on top of tinynoot and go in and remove the excess files using Super Manager.
Aurtach said:
I just did this and it works great. The only problem I have noticed is that when I am in gtalk and trying to chat I only see the top two rows of keys. Is anyone else getting this or know how to fix it?
Click to expand...
Click to collapse
Using an alternative keyboard could fix it, the major issue is finding an alternative keyboard that is e-ink friendly. This tends to be broken in the app itself, because I have noticed the Google Voice app will do the same exact thing on nook devices.
glowco said:
Maybe I should take this opportunity to ask an additional question: what will this root let me do that tinynoot didn't, other than run the Market? What additional apps would it allow me to run that would actually run well?
One app I have partially working on tinynoot is Jabiru, a jabber chat client. The basic chat connection works, but the Conference function crashes the session. I doubt this other root would make a difference in something like that?
Thanks.
Click to expand...
Click to collapse
The difference between this and tinynoot IS the fact it has Market on it, you can actually go to google.com/play now and install apps to the device. Other than that there is no major difference.
Yeah, folks should understand what tinynoot grew out of: I wanted the smallest set of changes I could make to have a rooted NST usable by me. I almost didn't include the Amazon appstore, but then realized there were things I wanted from it and that it'd be more helpful to others if there was at least something
That's very bare-bones, because I don't use the NST for too much other than reading - I want an rss reader, a non-BN book reader and my contacts (via b-folders, rather than a google account,) and at that point I'm pretty much done. I often install what I want to a fresh device just using adb or pm from a commandline
Gabrial's trying to get the Google market working because so many folks really want it.
Also, I tested tinynoot against an NST last night and was able to root that using it, which is helpful to me.
That said, here are the files tinynoot copies in; it sounds as if the two rooting tools are compatible, which is helpful.
in system:
/system/xbin/busybox
/system/bin/su
/system/app/NookColorTools.apk
/system/app/com.noshufou.android.su.apk
and in /data/app:
ADW.Launcher_v1.3.6_Standalone.apk
Amazon_Appstore-2.1.0.apk
BusyBox_v7.3.apk
Button_Savior_v1.3.1.apk
NookTouchTools_v1.0-beta2.apk
Super_Manager_v2.6.0.apk
adbWireless_v1.4.1.apk
and that's that.
So I have a KF running twa_priv's CM10/sgt7 20121112 build. I was watching a movie on the Freedi Youtube downloader before a parade this morning with headphones. I pulled them out and turned the screen off because there were floats approaching. After the ~2 hour parade, I tried turning it on. It had gone to a(n?) SOD, so I just restarted it like I always do and held down the power button for 10 seconds. I turned it back on and let it run. About 3ish minutes later I look at it and it is still on the blue CM circle bootloader. I forced it off by another 10 sec hold on the power button, then went into TWRP (2.2.2.1) after it turned back on. I chose the fix errors under the advanced option, and also flashed the 20121119 build of the ROM that I had previously downloaded. I wiped cache/dalvik and restarted system. I waited for more than an hour on the CM boot screen before I forced off again. I then went back into TWRP, copied the log to SD, and chose the mount system. I had it connected to my computer, but it didn't show any connected devices, didn't alert me via autoplay choices (or whatever it's called), and when I restarted the adb server, my kindle didn't show up there either. Also, twice during TWRP the KF froze on me and had to force restart. I am sure a complete system wipe would work, but I would rather just have this fixed.
Any ideas?
EDIT------------------------------------------------------------------
And BTW, I have tried reseting the boot menu thingy from initial bootup using the power button which didn't work
Start fresh....save urself some headache
Sent from my SCH-R880 using xda app-developers app
guitarman2010 said:
Start fresh....save urself some headache
Click to expand...
Click to collapse
I know that is the easy alternative, but I have sideloaded so many apps, and have a whole bunch of changed ui options, I am really hoping that there is an alternative.
Maybe Thepooch has some words of wisdom? I think his (your) comments are really helpful, and actually seem to help.
No offense to anyone, especially guitarman2010.
jma9454 said:
I know that is the easy alternative, but I have sideloaded so many apps, and have a whole bunch of changed ui options, I am really hoping that there is an alternative.
Maybe Thepooch has some words of wisdom? I think his (your) comments are really helpful, and actually seem to help.
No offense to anyone, especially guitarman2010.
Click to expand...
Click to collapse
I know nothing compared to Thepooch lol.......I always keep backup apks on my Kindle because I flash different ROMs all the time
.....when you hit the walls of sanity, you have no-where to go.....
I use three different apps for backing up apk file the only downside is significant weight gain. Lots of people use titanium backup I do as well but really only for very little. I also use easy app manager and apk manager but often I`m stricken with considerable consumption of sdcard space so at this point I have scaled back to just using easy app manager for the majority. Things I really want to save I backup on my pc upload to Google drive and dropbox. Seems like overkill but time and time again I will get an update that is horrible and wish revert back to an older version and Google drive and dropbox are a mere download away without sucking away precious and limited kindle space. I don`t believe I know any more than anyone else I just do what is easy for me. I too flash Roms like crazy re-installing is and can be a weekly ritual depending on how smooth things are running. Guitarman2010 is right though A fresh install of your Rom is a very good idea. As for the adb issue there are minor device changes on jelly bean that can affect adb make sure you have the correct settings in developer options. In KFU delete this file and replace it http://db.tt/vXXeuL10 located in the kindle driver folder and reinstall the driver I have been making changes to it with ICS and jelly bean to keep adb working hope it helps.
I usually keep 2 or 3 ROMs handy on the Kindle SD ready to be flashed.......I never take off the Amazon update (6.3.1) just to be safe. My backup apk folder only has 205mb of usage and I use File Expert to make backups of the apks. I too also use the PC for even more backups and 4shared so I can easily transfer apps back and forth from the Kindle to a crappy low-end Samsung phone running Froyo. I'm getting off topic here so I'll shut-up lol
.....when you hit the walls of sanity, you have no-where to go.....
So I wiped cache, dalvik cache, factory reset. I didn't wipe SD card, cause i am hoping to get the files out eventually.Everything seemed fine, but I still can't connect it to the computer! I have it open to TWRP and selected mount, and same as before; no connected devices in device manager, no adb devices, and no autoplay window pops up to let me open files in the drive. I also had the 20121119 cm10/sgt7 in the sd card, so I flashed it, and rebooted, but I am still left at the CM logo. What can I do now? I replaced the file you said to in adb. I happen to have used Titanium Backup, too, a while back, so I have about 2/3 of my sideloaded apps.
Please help!
edit---
I was looking at other Q&A's to help and for help, and saw that Soupkit is recommended to a lot of people.
Would this help me?
OR could I do some sort of terminal commands inside the advanced section of TWRP?
Your kindle isn`t ruined and if your having mounting issues then Soupkit would work great. Before you do anything anything drastic I will take my laptop to work and help you fix your kindle.
Hi,
Like everyone else I have to say"Follow these instructions at your own risk" I do not take any responsibility for any thing that happens. It worked for me so it may work for you!
Trio 4.3 Internet Tablet M4302 Model Trio 4.3MID 4.0C by Mach Speed Technologies
I just picked this tablet up. I have successfully rooted it and have installed a working Play Store. I now have access to all my apps that I use on my Galaxy Note 10.1.
To root I used the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=1886460
Once I had root I wanted to get Google Play Store on the tab. I found a couple of places that had information concerning adding Play Store to other devices and kind of pieced the info together to come up with this solution.
1. Download gapps for ICS. http://goo.im/gapps/gapps-ics-20120429-signed.zip
2. Unzip file
3. Navigate to the " System/app " folder and find "phonesky.apk and setupwizard.apk"
(You will need to copy these two files to your tablet)
4. Once files are on tablet use something like "Root Explorer" to copy both to the "system/app" folder of the tablet.
(The folders will need to be mounted as "R/W" so they can be written to )
5. After the files are copied to the proper folder, you need to edit the permissions for both.
6. In "Root Explorer" long press on each file and choose "permissions"
7. Edit permissions to read "Owner: Read, Write" "Group: Read" "Others: Read"
8. Reboot and launch Play Store
Frys has this for $49...thinking I might need to order it as a music player for my 2 month old!
I used this method to get Google Play Store to work, But its not rooted. At least you can download the files.
http://nwteche.com/red7_blog/instal...-or-most-other-tablets-running-android-2-3-3/
works great thanks successfully rooted and installed google play on my trio stealth lite 4.3" internet tablet m4302 runing android 4.0.4 :victory:
Mine came rooted
Thank you for this post!
Just wanted to give a heads up for anyone who finds this thread through Google or whatever, like I did, that it's possible your device is already rooted.
I bought mine today from Big Lots - branded as a: Trio 4.3" Touch Screen Media Player for Android by Mach Speed Technologies - on the box (well blister plastic wrap thing that is Hades to open...). The instruction user's manual, however just calls it a Trio 4.3" Internet Tablet.
(Specs from the box.)
Android OS 4.0
4.3" Capacitive Touch Screen
4GB Internal Memory with Micro SD Slt (Up to 32GB)
Built-in WiFi
Speaker
Auto Rotate for Portrait & Landscape Viewing
1.2GHz Processor
Rechargable Li-on Battery
Anyway, I just wanted to say thank you, and let everyone know to check your device first. There may be better ways to check, but there are a couple of apps in the Amazon App Store called "Root Checker" - don't get the "My Root Checker" - it has crazy pop-up ads - I deleted it in seconds. But just check to see if your device is rooted. It could save you some time, and potential headaches.
Well, jsut confirming that this guide works. In the root post, I used the stadard root method...if you are like me and got this for a little one, they wanted apps. Of course I couldnt open until today...but it really works. I just dowloaded the root explorer apk (a quick google search worked) and installed it...i can upload a screen shot if necessary
chad78 said:
Thank you for this post!
it's possible your device is already rooted.
Click to expand...
Click to collapse
This. I picked up two of these devices and both were already rooted.
Dude, does anybody have the factory rom? I don't even have custom recovery but, I fukt up and tried to install cm9 and it says to reset the phone but, the touchscreen wont work. I dunno if I'm gonna be able to fix this or not. I've hard bricked a lot of android phones and still fixed em somehow so maybe I can. Any help?
C
Sent from my MB886 using xda premium
My Trio also had root access right out of the box. Followed the instructions right down to obtaining the "root explorer" apk. Worked like a charm, no issues at all. Now I just need to find a custom rom that will perform better than stock. Thanks for all the info.
Hulu Plus
Since this is the best thread for this tablet I've found. I wanted to ask if anyone has gotten Hulu to work? I have installed many different versions including the latest and all of them will play the ads just fine, but once it gets the episode it just sits there and buffers and buffers and buffers. Devices on the same WIFI have no issues. I am even talking with Hulu suppor about it and of course they are playing dumb about it and just giving me standard troubleshooting. Is this tablet blocked by Hulu somehow because it's chinese made? I don't get a region error, which I can force with proxies and such. I just get buffering and buffering and buffering. Any help would be much appreciated.
I need firmware or update.zip im stuck on boot screen.
This is strictly a kodi question if anyone can assist.
My living room install running latest 15 runs problem free. The bedroom, same version, starts with "error! failed to start common cache". This has happened in the past and I was able to fix it, but didn't feel like doing trial& error nor posting a log a the org so I just made a backup of my living room setup and restored it to bedroom.
BUT, I had some issues along the way
1. When I tried to restore the backup it gave a warning that this was a different version of kodi (No, It is not, I doubled checked to make sure. Both are 15 released on july 21st) I went ahead and restored it anyway.
2. Eventhough kodi has no obvious performance issues, restoring a backup from the working setup did not fix the "failed to start common cache" issue right after kodi boots up.
Can anyone explain how this is possible? And just an added detail--before I did the backup and restore I attempted to delete the "commoncache.db" file because it's worked in the past. But of course that did nothing. I'm not overly stressed out because kodi runs fine. I can watch videos as long as i want without any crashes and it's actually been buffer free from online and local sources. It's just an annoyance to see that error overtime. Thanks.
Common Cache Problem with me to using Kodi.
I am using 15.2 RC1 issue of Kodi. I have deleted the commoncache.db myself as well.
Does your copy not close properly? Does it seem to take forever to shut down like 30 seconds or so.
When browsers close they can delete cache files. I am wondering if there is a cleanup going on with Kodi closing.
If Kodi freezes on closing maybe there is an issue there. Kodi does not ever close well except when you first install it.
After a few add-ons and slow it goes from there on. Have you gotten any further with your problem. I need to solve
this annoying problem to. Thanks..
-------------------------------------------------------------------------------------------------------------------------------------------------
My living room install running latest 15 runs problem free. The bedroom, same version, starts with "error! failed to start common cache". This has happened in the past and I was able to fix it, but didn't feel like doing trial& error nor posting a log a the org so I just made a backup of my living room setup and restored it to bedroom.
BUT, I had some issues along the way
1. When I tried to restore the backup it gave a warning that this was a different version of kodi (No, It is not, I doubled checked to make sure. Both are 15 released on july 21st) I went ahead and restored it anyway.
2. Eventhough kodi has no obvious performance issues, restoring a backup from the working setup did not fix the "failed to start common cache" issue right after kodi boots up.
Can anyone explain how this is possible? And just an added detail--before I did the backup and restore I attempted to delete the "commoncache.db" file because it's worked in the past. But of course that did nothing. I'm not overly stressed out because kodi runs fine. I can watch videos as long as i want without any crashes and it's actually been buffer free from online and local sources. It's just an annoyance to see that error overtime. Thanks.[/QUOTE]
KLit75 said:
This is strictly a kodi question if anyone can assist.
My living room install running latest 15 runs problem free. The bedroom, same version, starts with "error! failed to start common cache". This has happened in the past and I was able to fix it, but didn't feel like doing trial& error nor posting a log a the org so I just made a backup of my living room setup and restored it to bedroom.
BUT, I had some issues along the way
1. When I tried to restore the backup it gave a warning that this was a different version of kodi (No, It is not, I doubled checked to make sure. Both are 15 released on july 21st) I went ahead and restored it anyway.
2. Eventhough kodi has no obvious performance issues, restoring a backup from the working setup did not fix the "failed to start common cache" issue right after kodi boots up.
Can anyone explain how this is possible? And just an added detail--before I did the backup and restore I attempted to delete the "commoncache.db" file because it's worked in the past. But of course that did nothing. I'm not overly stressed out because kodi runs fine. I can watch videos as long as i want without any crashes and it's actually been buffer free from online and local sources. It's just an annoyance to see that error overtime. Thanks.
Click to expand...
Click to collapse
Finally, I figured out a solution...
Settings>My add-ons>Services>Common plugin cache>Configure>turn off Auotstart with XBMC. Restart Kodi and that annoying error should be gone. Haven't noticed any ill-effects. I assume common plugin cache will be utilized, it just won't autostart with Kodi.
Hope this helps!
so you didn't fix the issue you just hid the messages
Had the same issue went to settings for commoncache and changed port from 59995 to 0 i believe port 0 is always open and hey presto no more problems with failed to start commoncache
Hi all, I have a problem.
Today I used my phone to play videogames using the Sixaxis Controller and the phone has rebooted. Now when I put my fingerprint, the device needs the password for security reasons but the keyboard not appears because the IME is set to PlayStation Joystick.
I can access to data folder using TWRP but I not know where is the file that set the input method.
I'm using a Motorola Z2 Play with Stock ROM, rooted (Android 8.0)
Any ideas?
Regards.
Well, finally I restored an old backup that I created, with this, works ok now, but anyway would be interesting know how to fix this problem manually. I'm very lucky by the backup, only updated all PlayStore apps, V4A, reinstalled Magisk and grant all root permitions and finally done. Wiping data it's terrible for me, a lot of apps, configs, files to edit, etc. It's hell.