Related
Im running the latest stable version of CM with Amon Ra recovery. It runs great except for these three problems.
1. I use the Zeam Home Launcher and every time I reboot the system resets it back to the default launcher. I press home and choose Zeam launcher, but none of my widgets load.
2. Is there a way to keep Wifi on even when the screen is turned off. I know this was a setting on MIUI, however I cant find a setting for CM7. I would like it to stay on all the time.
3. I have the latest version of the Market. When I search for an app it displays the total number of matches found in the top right corner. However, when I scroll down the list it ends after about 20-30 apps even though there its showing hundreds of matches. I then do the same search online, see all the available apps, and know for certain that they are compatible and can install them from online.
I have done a factory reset twice and reinstalled everything, including ROM and Recovery.
Thanks for reading and any help you might be able to provide.
BioBot said:
Im running the latest stable version of CM with Amon Ra recovery. It runs great except for these three problems.
1. I use the Zeam Home Launcher and every time I reboot the system resets it back to the default launcher. I press home and choose Zeam launcher, but none of my widgets load.
2. Is there a way to keep Wifi on even when the screen is turned off. I know this was a setting on MIUI, however I cant find a setting for CM7. I would like it to stay on all the time.
3. I have the latest version of the Market. When I search for an app it displays the total number of matches found in the top right corner. However, when I scroll down the list it ends after about 20-30 apps even though there its showing hundreds of matches. I then do the same search online, see all the available apps, and know for certain that they are compatible and can install them from online.
I have done a factory reset twice and reinstalled everything, including ROM and Recovery.
Thanks for reading and any help you might be able to provide.
Click to expand...
Click to collapse
1. When you choose the zeam launcher, make sure you check the box that says 'set as default' set your widgets. They should stick now.
2. Settings > Wireless settings > Wifi Settings > Press Menu > Advanced > Wifi sleep policy: set to never
3. If you keep manually scrolling the rest of the results should show up.
One Down....
1. Zeam launcher has been set to default launcher every time. Tried again with no success.
2. FIXED. Thanks. Why in the world would they make you press "Menu" inside of a menu window ? Seems weird to me.
3. Scrolling changes nothing. How would you NOT scroll manually anyways ? Not trying to be rude, just sayin.
One down, two to go !
BioBot said:
1. Zeam launcher has been set to default launcher every time. Tried again with no success.
2. FIXED. Thanks. Why in the world would they make you press "Menu" inside of a menu window ? Seems weird to me.
3. Scrolling changes nothing. How would you NOT scroll manually anyways ? Not trying to be rude, just sayin.
One down, two to go !
Click to expand...
Click to collapse
1. IDK then, that's how it should work...try force stopping it then clearing the data
2. Huzzah
3. Well some people would just see the bottom, and not continue scrolling [seen it happen] try clearing the market cache and data.
Try uninstalling adw launcher
And search games on market. Does it really only show 20-30 games..?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Posted a video of what happens when i search something on the market.
http://www.youtube.com/watch?v=yLkQhVDhk-4
you can see that it says there are 4500 results, but i get no where near that many.
i cleared the cache and the data, rebooted and still nothing.
BioBot said:
Posted a video of what happens when i search something on the market.
http://www.youtube.com/watch?v=yLkQhVDhk-4
you can see that it says there are 4500 results, but i get no where near that many.
i cleared the cache and the data, rebooted and still nothing.
Click to expand...
Click to collapse
Have you tried installing a new market? [vending]
Download the latest CM7 gapps, extract the vending.apk [market], place it on your sd card, then install it.
I had the same problem with the Market, and I know others did too. Mine was only on occasion, but still obnoxious. So far the newest Market leaked from ICS (version 3.2.0) has fixed the problem for me. I couldn't install it over, I had to replace the apk in /system/app, set permissions (rw-r--r--) and reboot. Remove or rename any com.android.vending.apk you may have in /data/app, just in case. Backup your old Market in Titanium Backup or rename it so you can revert back if needed.
Link here: http://db.tt/pTvEmx4v
As for the launcher issue, I had similar problems when I was running CM7 way back on nightly 21 or something. Try updating to a newer version or downgrading to a previous version. Or you can try reflashing the rom over itself. You'll need to reinstall the new Market if you flash anything.
Sent from my Evo + MIUI using Tapatalk!
Launcher Issue
Notice: The stock launcher for CM is ADW Launcher. I'm not a big fan of it either so I've also replaced mine. Normally just installing a launcher from the market and selecting it as your default launcher (via the pop up window that displays when you have multiple launchers installed) is all it takes to make it a default. I normally wouldn't advocate changing your system apps. However, in your case it seems like the system just doesn't want to cooperate with you.
Here is how to do it.
1. Make sure ALL launchers are uninstalled. (except for ADW of course)
2. Download a root file explorer like ES File Explorer
3. Download Zeam Home Launcher's apk file to your SD card
4. Open ES File Explorer (or whatever root file manager you downloaded) and make sure your root folder is mounted (so that you can modify its contents instead of it being read only)
5. Copy Zeam Launcher apk from SD card to /System/App/
6. Delete the apk for ADW Launcher (the stock launcher) from /System/App/ (or you can just move it to your SD card in case you decide later that you want to use it again)
7. Reboot phone
8. Enjoy Zeam as your new PERMANENT stock launcher.
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Thanks roustabout! It works great and it was super easy to do! I just got done installing a bunch of apps from Amazon.
Update: I just posted a tutorial with a video for noobs on my blog.
One thing to note, I didn't do the reboot that you mention in between the 1 and 2 packages and everything worked fine. I just installed 2 right after 1 and haven't had any problems.
Thanks for this, rooted last night everything is as it should be, the only issue I've run into is that I can't seem to install the Kindle app. It's not in the amazon market place, I tried backing up the APK from another device via EStrong and transferring the apk to the microSD, and I get a parsing file error. Any tips?
I have not been able to get Tasker to install yet, either.
One thing which sometimes works where other approaches fail (if you have the .apk file) is to ssh into your device (I use quicksshd) and log in as root, then cd to the directory the APK was copied to and issue the command
pm install blah-blah.apk
I have not yet tried that with Tasker, but it may also help with the Kindle app? I did need to do it for one of the apps I use, although I can't recall which one.
Edit: the 3.1 kindle app Zydraka points out works for me as well.
By default, the Kindle app is pretty unusable, very slow page turns. But by using the gesture-enabled screen refresh hack, it's very useable. (I found that using the no gesture version led to lots of apps just ignoring the hack's presence. I think Renate has a way around that, but I haven't read up on it.)
http://forum.xda-developers.com/showthread.php?p=22800284#post22800284
I got Tasker to install, but needed first to copy in the Maps jar and xml (to framework and permissions respectively) reboot and install via ssh - it might have worked just to reboot.
Since others may want Tasker available, putting the maps.jar and maps.xml files into the tinynooter is trivial, and I'll probably get to it soon.
I found that the older version of the Kindle app works, version 3.1.0.30. There's a donwload for it at Android Freeware. http://www.freewarelovers.com/android/app/kindle
So, after this, will the glowlight work in all apps? I need to make sure that, moon+ reader and EZpdf will glow in the dark, before I purchase the new nook.
thanks.
The glowlight seems to work in all apps. I'm not clear on how exactly it's turned on and off; it might be possible to have an app that uses a long press on the N button for something else, and that might interfere, but so far it works fine in the launcher, in the Kindle reader, in fbreader, in Newsrob (that I know I've tested.) even if you had an app that was doing something funny with that long press, you ought to be able to turn it on from the settings menu that comes up on a short press.
Once the glowlight is on, it seems to stay on until your screen goes to sleep, regardless of what applications you may also be using.
This is part of why I didn't get into the boot environment at all in this approach - I knew from manual rooting that I didn't have to change out uRamdisk so I decided to leave it all alone.
Thanks for tinynoot! It's working well for me, and glowlight behaves normally.
roustabout said:
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Click to expand...
Click to collapse
You know, it should be nice if before using the packages other people create, for your own project, you asked them for permission to use them, if not, at least create your own scripts.....
Yes I'm refering to me.... thats not cool.
Anyway, the two step process is not necessary here, thats just for preventing some Gapps database corruption, you edited that code away allready and there are no Gapps installed, so add the code to correct the permissions on the first zip, and everything should work fine, no need to rm dalvik either if you arent modifying framework.jar, etc, it should also speed the first boot time.
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
roustabout said:
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
Click to expand...
Click to collapse
Don't worry, just stating that before creating a thread with others people work, you should ask them.
Everything is fine, It didn't even pass my mind the idea of reporting it, we are a small niche community, active members must be praised, so dont worry, and I encorage you to keep deving ^^, just that before using other peoples work and starting a thread with it, ask them for permission, no one is gonna deny it and it's the kind way of doing things .
I'm planning to get my hands on a Glow tonight, so over the weekend I should be able to get together a full Nooter for it.
tiny noot - also works for older NST
Just so folks know, I've confirmed that the tinynoot rooter also works on the NST running 1.1.2 firmware.
It will probably work on earlier firmware also, since it is not replacing uRamdisk or framework files.
Are Supermanager and the Busybox Updater supposed to work? Supermanager crashes back to home, and Busybox won't install.
Did you apply both files, and is there an sd card in your device? I just tested the busybox updater and was able to get it to update the installed busybox. It requires that you have an sdcard inserted to work - I remember being puzzled by that the first time I tried using it on a device.
supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Looking at logcat, yes, supermanager's crashing in the background quite a bit. It seems to be looking for things which are not available, for instance, a dialer, and erroring out when it can't find them.
roustabout said:
[...] supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Click to expand...
Click to collapse
Supermanager has always been a problem, at least for me, using TouchNooter. I believe it's intended to provide file manager capability, particularly for installing APKs on uSD. Once I get Market (Play Store) access, reinstalling supermanager fixes the problem. At that point, I don't need it anymore.
I've always had to work around this when rooting my Touch devices. I'd suggest a basic file manager be provided instead for Day 1.
I'm rooted with tinynoot. Recently I've been experiencing excessive battery drain. I'm eliminating apps I'd installed to if that helps. Wondering if anyone has experience with apps that are problematic in that regard? Dropbox? Amazon Appstore? Facebook? 1Mobile Market? I assume nothing that was provided by default with tinynoot. Thanks.
Hi Glowco,
I'd suggest installing task management apps to get a view of what is actually running (not all processes relate to an installed app icon that you can uninstall). I use Advanced Task Manager to view running apps, and Autorun Manager to control what processes start up at boot time.
Ian
Thanks, I'll keep that in mind. In the meantime, as an experiment I uninstalled several apps including Amazon Appstore, 1Mobile Market, FB, and Wireless ADB. Good result - my battery charge hasn't decreased in an hour and a half. If I decide I miss them I can try adding them back and use your method.
That's good news!
I'd suggest that Wireless ADB is not to blame, since it does not stay resident once it's closed and in any case does nothing until you click the big red button
Of the others, I have Amazon Marketplace installed and I don't experience any battery issues (I'm Glownooted not Tinynooted but don't think that's relevant in this discussion), but I can't speak for the other two apps. If I were paranoid (and I am! ) I would point at Facebook, since it's purpose is marketing and wants to follow your every move
Ian
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.
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.
Hi!
I bought a used HTC Desire. The person selling it had rooted the phone, installed a new ROM (miui, as far as I can tell, since there's at least the miui camera. He said he had wanted an ICS rom) and the phone is using the SD card for increasing its memory. Titanium Backup, LauncherPro, AC!D SoundMOD, Dolby Mobile, ES File Explorer, Firewall, Fancy Widgets, Pimp My Rom, QuickPic, SuperSU, two instances of Superuser, Task Manager and Theme Manager have been installed. LauncherPRO is used as the "desktop environment".
Some things from the "About Phone" dialogue:
Model number: HTC Desire
Android version: 4.0.4
Baseband version: 32.49.00.32U_5.11.05.27
Kernel version: 2.6.38.8-cayniarb-ics-stock-022612-00844-ge004de8
Build number marius.a v.2.5(Temporary version)
The problem is, reboots keep causing programs to disappear or get corrupt. There are several ways in which this happens:
* Some programs launch, but don't show anything. For example Firefox ends up showing only a white screen with some basic OS-wide UI elements visible.
* Most programs simply say "Unfortunately, <programname> has stopped", where <programname> of course varies according to program.
* Some programs launch for a while, but fall to the "unfortunately, <foo> has stopped" after a second or a minute.
* Some programs completely disappear, leaving at best a picture of a green robot on the home screen. Touching the picture with my finger, I get: "Could not launch the requested activity."
* There is one program still working flawlessly: Andropas, a PT route planner for my city and Maverick, a GPS/maps program.
Also the Play store is now broken, although it survived many earlier program mass deaths.
I've fixed Firefox several times by uninstalling it using ES File Explorer and then digging it from the Downloads folder (I've installed a beta from an .apk file) and installing it again.
A reboot doesn't always break programs: My previous two reboots left FF intact. I once rebooted choosing Reboot from the menu you get by pulling the panel on the upper side of the screen downwards and then choosing TOGGLES and once choosing Shutdown from the same menu, waiting for the phone to shut down and then starting it again.
I am therefore not completely sure if the problem is reboot-related, but it has by now only appeared when I've rebooted my phone.
For adjusting yourself: This is my first Android phone, but I would call myself generally tech savvy and am able to grasp new OSes very quickly. A power user for sure, but not a developer on any platform whatsoever.
So... Any idea of what I should fix in order to get the phone functioning correctly?
If I have to go for installing another ROM, is there something about using the SD Card as memory extension that I should take into account in order not to brick my phone?
You have an old version of the Marius.a ICS Rom, and it has bugs. You should flash the newest one.
If that doesn't solve it, then repartition your sd-card. Check the guide in my sig.
abaaaabbbb63 said:
You have an old version of the Marius.a ICS Rom, and it has bugs. You should flash the newest one.
If that doesn't solve it, then repartition your sd-card. Check the guide in my sig.
Click to expand...
Click to collapse
bugs, bugs. but that's an army of bugs
i guess the guy who sold it to you copy from one sdcard to another the content without setting permisions.
for sure he didn't kept his google account so... u can eighter reinstall rom or... go in recovery and choose factory setrings
Sent from my HTC Desire using xda app-developers app