Related
I found that [email protected]'s ROM had a good idea of adding WaveSecure to the system partition (preventing listing in the My Downloads part of market, and preventing uninstallation through normal means), but his version is slightly out of date now (latest version is 3.0.0.43)
As a result, I set about finding a means to install WaveSecure to ROM myself. Here are my findings for anyone interested in doing the same.
Install the latest version from the market (3.0.0.43 at this time). Now use adb pull to get it off the device onto your pc
Code:
adb pull /data/app/com.wsandroid.apk D:\com.wsandroid.apk
Now open Market back up from the menu, go to My Downloads, and choose Wavesecure Mobile Security Beta and uninstall it for just now (to get it off the data/A2SD location that normal apps are stored in) - thanks, my-space!
Then push the saved apk to the system partition after a remount (to make it read/write)
Code:
adb remount
Code:
adb push D:\com.wsandroid.apk /system/app/com.wsandroid.apk
Then set it all up as usual (will appear in apps list immediately)
and remount system as read only again
Code:
adb remount
And that seems to be it so far. Remember to change the D:\com.wsandroid.apk path to whatever you actually used.
Let me know if anyone finds any problems with this, but I've done it and, fingers crossed, it's worked OK for me.
Obviously, this is only for root users, and there are no guarantees for this.
Couple of questions that might need looked into -
- Do settings carry across after a wipe (as Paul claims Modaco's version does. I've never tried it so can't confirm)
- Is there any disadvantage to using this method? (I guess this is all Modaco's update.zip does, but I don't know)
you forgot to metion to uninstall wavesecure before it is pushed back into system....
my_space said:
you forgot to metion to uninstall wavesecure before it is pushed back into system....
Click to expand...
Click to collapse
Oops! Knew I'd forget something, as I always seem prone to do. Well spotted, and OP corrected.
Thanks
No worries I got a bit confused when i pushed it back onto the phone and was still in my downloads...
I've rooted my phone already but whenever i try to use the command adb remount I get "remount failed: operation not permitted". Suggestions?
I see more and more often, redundant threads.
What How-to will you post next time? How to change backlight settings?
You're pointlessly spamming the board.
I can't say i agree with the 'pointlessly spamming the board' comment, but i would have thought this would at least be better in the applications and themes subforum rather than in development.
Don't forget that an awful lot of android users (and more recently all HTC devices) are more and more 'newbs' and need stuff like this.
While this is good and provides info that people like that need (and myself cos i'm crap at adb and stuff like that so wouldn't have had a clue how to do this previously), maybe the development forum is not the best place for it....
I'm guessing one won't be notified via Market if there's an update available if you push an app to /system/app/, right?
usb0 said:
I'm guessing one won't be notified via Market if there's an update available if you push an app to /system/app/, right?
Click to expand...
Click to collapse
You won't be notified, correct
If anybody doesn't already know, WaveSecure have started hosting update.zip files. This means it's now easy to update your "baked-in" version of WaveSecure without much messing around.
https://www.wavesecure.com/installations/update.zip
Download the file, save it to your SD card, reboot into the recovery console and choose the option to apply an update.zip file.
Voila! Your version of WaveSecure will be updated to the very latest version
DJBenson said:
[...]
Click to expand...
Click to collapse
That's really awesome! Thanks for the tip!
Just a question of curiosity: If I push an app to /system/app/ and then issue the rm-command to remove its apk, won't there be lying a bunch of files associated with the program and with absolutely no function, since the app itself is removed? How do I know the name of these files and where they are located for removal?
I'm a bit confused by that question. My understanding (which may be incorrect but from what I've seen of the "guts of a ROM" appears to be the case) is that the applications reside in the apk files, they are not extracted. If you list the content of any of the app folders (/system/app, /data/app or /data/app-private) then all you get is a bunch of apk files (and some odex files). So when you 'push' an apk to the phone, that application is then "installed", when you rm/remove an application, you do so by removing the apk.
if you remove the apk you have left something in /data/dalvik-cache. wiping the dalvik-cache every now and then helps reclaiming that space, though it is not much.
the app settings and data are stored in /data/data, you could delete the files manually by checking their names (no idea if/what convention the names follow), imho not worth the trouble as it is only a few kb.
odex files aren't created if you don't do in a PITA process manually. don't worry about them, don't touch them, then you're good. odex files are only for system apps.
I bought a used phone and it had WaveSecure already installed. I couldn't find it in the applications list to uninstall, so I did a factory reset on the phone. The application was still there and it still didn't show up in the applications list.
I have the Superuser Permissions application, so someone must have rooted it.
Is there any way to uninstall this?
motomeup said:
I bought a used phone and it had WaveSecure already installed. I couldn't find it in the applications list to uninstall, so I did a factory reset on the phone. The application was still there and it still didn't show up in the applications list.
I have the Superuser Permissions application, so someone must have rooted it.
Is there any way to uninstall this?
Click to expand...
Click to collapse
""Just (re)flash a ROM................""
I just noticed that WaveSecure now points to this post for instructions to install as system application, and I am not sure that the update.zip maintained with them is up-to-date.
However, you can now select to download the .apk directly to your PC thus eliminating the first Market step in this guide.
strife242 said:
I just noticed that WaveSecure now points to this post for instructions to install as system application, and I am not sure that the update.zip maintained with them is up-to-date.
However, you can now select to download the .apk directly to your PC thus eliminating the first Market step in this guide.
Click to expand...
Click to collapse
I believe it is kept up to date, as VillainROM kitchen uses it as a source for the WaveSecure app (fetched each night to keep it up-to-date).
I've certainly never had any problems with it.
Excellent guide Pulser,... I should really reinstall Wavesecure now Im not using a MoDacO Custom ROM. Nice one bruv.
Found this to be helpful.
https://www.wavesecure.com/blog/how-to-make-wavesecure-hard-reset-proof.aspx
I just did a search in the Market fro 'wavesecure' and two things popped up WaveSecure and WaveSecure UninstallProtection Add-on which needs to be uninstalled before WaveSecure and if the add-on is uninstalled it is supposed to lock the phone. (all this is in the description I have yet to try)
Hi all,
I am not sure if this is the right place or not but worth a shot. I am swapping between quite a few roms at the moment and each time I do, I need to reinstall lots of applications from the market.
Now I know how to install an APK using ADB over USB when I have the package file but what I am ideally after is slightly different that that as I do not have the APK available.
What I would like is a way to install an application via command line from the market. That command line can be directly on the phone using a terminal or via ADB shell.
Is it possible at all to install an application from the market via a terminal?
Thanks in advance.
Read this
http://developer.android.com/reference/android/content/Intent.html
Also read about am command. You will have to open up the Vending.apk, see the intent and action required, pass the app name. I can't be more specific.
This is an example
Code:
#!/system/bin/sh
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/system/lib
am start -a android.intent.action.SEND -d "Hello World" -t "text/plain"
Hi,
I don't know if what you're after is possible, but you can:
1) leave it to google - with the newer versions of market when you first configure your google account the market starts installing the apps registered under that account
2) use a backup/restore app as mybackup Pro or titanium backup, which allow you to backup or restore all the apps with a single click
Bye,
Ildanish
Sent from my HTC Desire using XDA App
The reason I am looking for an alternative to googles backup within android is that when I am rolling from one ROM to another, this restore does not always work. A price exmaple is Sandvolds ICS ROM. Each time there is a new releast, the restore fails to restore - hence looking for an alternative.
I have previously used Titanium backup but not with this use case. Maybe I will give it a try and see how it works in this sense...
As an alternative, I think I could script something with "android.intent.action." It probably requrires some interaction still but it would get to a more automated install situation than I have now.
Thanks for the input guys, I will see what milage I can get from this.
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.
Edit: Please note this post does have a resolution at the end.
Did you ever have a tech quandry you just had to solve?
Last year I hid some apps in/from the app drawer of a stock, S-On, not unlocked or rooted, T-mobile HTC Wildfire S with the stock Sense 2.1 UI. I want to unhide them and can't find the info on how I hid them anywhere. They do show up in a different launcher, like LauncherPro. They're not disabled, I already checked that in adb in the Android SDK.
I can run them, either from Titanium Backup or Launcher Pro, and then from my recent apps drawer in Sense 2.1 after I've run them in one of the mentioned ways; but, I really want to get those icons back and do a CWM backup of my stock ROM before I start trying custom ROMs on this phone. I like Sense and want to be able to go back if I choose.
I'm rooted now thanks to the many articles and guides here. Unlocked at HTC Dev, and ran root.zip. Installed SuperUser, ROM_Manager, TitaniumBackup
I have spent a LOT of time recently and all day every day since Monday researching here and at Android Forums, the 2 defacto places for phone knowledge. I've also used Google, searched on Life Hacker, looked in all my browsers favs for articles, searched my computers for notes (I usually make a file in Notepad for things I do that I might not remember), checked magazines I read, and so on.
I don't know if I did something in adb, changed a manifest (too many to do that), or installed a launcher that left those apps hidden when it was deleted. I hid about a half dozen apps/icons.
There has to be an answer.
Sure would appreciate some help. I'm exhausted trying to find the tip/trick I followed to do this so I can undo it. If it will help. When I try to enable the Stocks package in adb I get a return of:
C:\>adb shell pm enable com.htc.android.Stock
[1] Killed pm enable com.ht...
Does that mean I killed the app, "Way back when"; or, maybe just the process is killed without invoking root (remember the phone wasn't rooted when I first did this)? If I do it this way invoking root, I get a diff result, but neither way shows the app (unlike freezing/unfreezing in the many apps like TB, etc.):
C:\>adb shell
$ su
su
# pm enable com.htc.android.Stock
pm enable com.htc.android.Stock
Package com.htc.android.Stock new state: enabled
BTW if I disable it disappears from LauncherPro and then enable and it reappears in Launcher Pro; but, nothing gets it to reappear in Sense except in the recent apps drawer after I open it in Launcher Pro or TB as mentioned in the above post.
The control has to be in a file somewhere. Do phones have an, "xxx.ini" file for apps like computers sometimes do?
Re: [Q] There must be an answer to show apps
MiCeltic said:
Sure would appreciate some help. I'm exhausted trying to find the tip/trick I followed to do this so I can undo it. If it will help. When I try to enable the Stocks package in adb I get a return of:
C:\>adb shell pm enable com.htc.android.Stock
[1] Killed pm enable com.ht...
Does that mean I killed the app, "Way back when"; or, maybe just the process is killed without invoking root (remember the phone wasn't rooted when I first did this)? If I do it this way invoking root, I get a diff result, but neither way shows the app (unlike freezing/unfreezing in the many apps like TB, etc.):
C:\>adb shell
$ su
su
# pm enable com.htc.android.Stock
pm enable com.htc.android.Stock
Package com.htc.android.Stock new state: enabled
BTW if I disable it disappears from LauncherPro and then enable and it reappears in Launcher Pro; but, nothing gets it to reappear in Sense except in the recent apps drawer after I open it in Launcher Pro or TB as mentioned in the above post.
The control has to be in a file somewhere. Do phones have an, "xxx.ini" file for apps like computers sometimes do?
Click to expand...
Click to collapse
What apps are you trying to show again? Since you have root you can try to use a root uninstaller app to make a back up of the app first, then reboot the phone. Then use the app to reinstall and then reboot to recovery and use fix permissions.
Feel free to make a nandroid back up first just incase you lose any data
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Thanks for the response heavy_metal_man. It's hard to tell everything. I missed what and the kind of apps, thanks. I am talking about system apps like, "Stocks" and, "Voice Recorder", and there's others. I did Fix permissions in ROM Manager before and it didn't fix anything. I have tried a lot of stuff and am getting flustered and tired, but not giving up! For the sake of knowledge, I really want to find out the what and how...not just use a workaround. I tried your suggestions with, "Voice Recorder"...backed up in Titanium Backup...uninstalled with Root Uninstaller...checked everything to be sure it was gone and then restarted...attempted a restore of, "App only" with TB and it just churned long enough to know it was hung (I did get a notice there was an update, but don't think that would interfere); so, I powered off and restarted. No changes; so, tried another restore of, "App + Data"...same thing it just churned...another restart and everthing was back to the way it was. VoiceRec in Settings>>Apps>>ManageApps, but not in the Sense app drawer. I then couldn't get ROM Manager to do anything when I selected Fix Permissions...couldn't get into TB, did the update, still couldn't get ROM Mgr or TB to do anything, and so did a battery pull restart...I did go into CWM, but just rebooted. Then everything was normal, meaning as before, and fixed Permissions in ROM Manger. I don't think it matters whether I fix in CWM, ROM Mgr, or ADB...they're all reading the same .xml files to set permissions. Anyway, No VoiceRec in the Apps Drawer.
So I'm back to square one. Any more ideas I'll be glad to try them. I don't think I used APKToolkit to do anything or that it would be in the apk's. Tomorrow I think I'll try to find something in the package xml's...just need to find the right package that would address them all. I've looked at a few, but just for change dates on all the files in the packages...all were 2009, and I'd have done this in 2012.
Thanks again...tomorrow is another day.
Re: [Q] There must be an answer to show apps
Hmm. For the sake of argument make a full backup and then factory reset from recovery, then reboot and go through the first setup nonsense. Are the apps back?
Also the sense launcher is called Rosie should that ring any bells.
If a factory reset doesn't fix this then you may have to flash a stock rom to sort it like
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
h_m_m,
I did a factory data reset myself before, which I believe is really just an erase of data, and not a real reset (like formatting and reinstalling an OS in a computer). Then of course there was the factory reset that occurred after unlocking and rooting. Neither of those changed anything. I have flashed a CWM recovery after rooting.
Are you saying, boot into recovery:
1. Factory Reset as
a. DO NOT wipe the factory data reset
b. Wipe cache and dalvik cache
c. Throw in a wipe of the batt stats too
then
d. Do the factory data reset and let all the caches rebuild as they will
or
2. Factory Reset as
a. Wipe factory data reset
b. Wipe cache and dalvik cache
c. Wipe batt stats
then
d. Backup and Restore>>Advance Restore>>Original ROM>>Restore system (not the data, cache or any of the other stuff there)
If number 2., then I wonder if that would put me back to OOB (Out Of Box), and if so, would I lose root, have T-mobile...yeah, I like T-mobile for some things - - blame it on Catherine Zeta-Jones time as spokesperson. As long as I have CWM recovery and have backed up from there I can't do anything that would ever leave the phone bricked; and, I can always unlock and root again if needed.
Either 1. or 2. I want to hold those in reserve because I do want to find out how I hide them. They act exactly as though they're disabled, i.e., The icon is gone, but I still get updates (Voice Recorder was updated just a week ago); however, they're only disabled in SenseUI. LauncherPro shows them all, and of course functionally...and remember once I run one of these apps, like Stocks, in LauncherPro, I can then switch to Sense and run it from my recent apps (long press on Home) or the pull down notifications area list of recents.
BTW, You were too gentlemanly to ask, but I clicked a couple, "Thanks" for you today. I was tired and forgot yesterday. We may not solve anything, but I'm enjoying/appreciate the conversaton/thread.
Even though I'm holding on those ideas above, let me know which/what you think of them please, in case I ultimately go that way. I did clear the data in Apps>>Manage for both of the HTC Senses and Rosie. I'll have to look at what's in Rosie though, maybe that holds the key!
As an aside, the first personal web page I made had, "Iron Man" as the background music!
Re: [Q] There must be an answer to show apps
MiCeltic said:
h_m_m,
I did a factory data reset myself before, which I believe is really just an erase of data, and not a real reset (like formatting and reinstalling an OS in a computer). Then of course there was the factory reset that occurred after unlocking and rooting. Neither of those changed anything. I have flashed a CWM recovery after rooting.
Are you saying, boot into recovery:
1. Factory Reset as
a. DO NOT wipe the factory data reset
b. Wipe cache and dalvik cache
c. Throw in a wipe of the batt stats too
then
d. Do the factory data reset and let all the caches rebuild as they will
or
2. Factory Reset as
a. Wipe factory data reset
b. Wipe cache and dalvik cache
c. Wipe batt stats
then
d. Backup and Restore>>Advance Restore>>Original ROM>>Restore system (not the data, cache or any of the other stuff there)
If number 2., then I wonder if that would put me back to OOB (Out Of Box), and if so, would I lose root, have T-mobile...yeah, I like T-mobile for some things - - blame it on Catherine Zeta-Jones time as spokesperson. As long as I have CWM recovery and have backed up from there I can't do anything that would ever leave the phone bricked; and, I can always unlock and root again if needed.
Either 1. or 2. I want to hold those in reserve because I do want to find out how I hide them. They act exactly as though they're disabled, i.e., The icon is gone, but I still get updates (Voice Recorder was updated just a week ago); however, they're only disabled in SenseUI. LauncherPro shows them all, and of course functionally...and remember once I run one of these apps, like Stocks, in LauncherPro, I can then switch to Sense and run it from my recent apps (long press on Home) or the pull down notifications area list of recents.
BTW, You were too gentlemanly to ask, but I clicked a couple, "Thanks" for you today. I was tired and forgot yesterday. We may not solve anything, but I'm enjoying/appreciate the conversaton/thread.
Even though I'm holding on those ideas above, let me know which/what you think of them please, in case I ultimately go that way. I did clear the data in Apps>>Manage for both of the HTC Senses and Rosie. I'll have to look at what's in Rosie though, maybe that holds the key!
As an aside, the first personal web page I made had, "Iron Man" as the background music!
Click to expand...
Click to collapse
Firstly thanks for the thanks , I love helping people out! Its how I get my kicks
Secondly as long as you have made a nandroid back up in your recovery you are pretty much covered for everything. If I was you I would go for option 2 and wipe the lot. Then let the phone fully boot up and go through the set up. If a full wipe fixes the issue then we at least have a solid starting point to find out what's happened after that little test then restore your back up regardless.
Notes: the factory reset will not remove root or any extra system apps you have installed.
As long as you have the back up done you can always go back to it, allowing you don't destroy the bootloader. But that is highly unlikely as you are still s-on
Also an option to help this might be to use the app titanium back up to back up all your apps data separately, then back up your contacts, SMS ect, and then do a fresh install of a stock rom. Once that is done you could restore your back ups manually and go from there
I must say though this is a very odd case indeed, I'm pretty stumped as to how you have managed this without root
Tapped out from my sexy nexus 7
Re: [Q] There must be an answer to show apps
I have been looking into this more and it turns out sense hides some system app icons by default. Such as the camcorder, as we already have the camera app. Can you post a list of the apps to cross reference them?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Sorry h_m_m, I didn't get an email notice of your reply on the 24th. Stocks and Voice Recorder are 2 definite ones. They don't show in Sense, but do in LP, and are discussed in the T-mobile HTC Wildfire S manual. I did notice in LP that there are some that I'm not sure I ever saw.
Re: your 2nd last post, I am 99% sure I did something with SDK, either in recovery or in the emulator...possibly debugging, that could be done without root!? I installed the SDK just short of one month after getting the phone. I really believe this was an article/tutorial by a programmer/developer that just walked me through. I felt OK using my computer skills in things like Visual Basic, SQL, and so on, but I was nervous because it was my 1st smartphone.
Anyway, in the last few days I've decompiled Rosie.apk to see if there was anything I could recognize or reason in the Manifest or Resources, but no clue there. I decompiled the Stock.apk from my WFS and one from a Hero to compare, again specific to the rosie/htc launcher, but nothing. I decompiled the htcSoundRecorder, no joy, Calculator (shows, but for comparison) - no joy. I have not done anything with the .odex files...maybe the tutorial I followed set something in those smali/java files, BUT, I don't see evidence on the computer I use for all this, of Eclipse or the JDK...only Java FX 2.1, but it's install coincides with the install of Google's Chrome browser, which uses it.
I believe this info is so obscure (except to ROM developers, I'm sure) because a lot of phones after Gingerbread got the menu option in the app drawer to hide icon shortcuts. So I'm going to keep this post in my favs and hope I get any email notifications if someone posts; and, search for articles now and then, but get back to living and leave this obsession behind...but not forgotten.
Hopefully I'll find something, come back and post it and even get a thanks for an interesting article and providing some obscure information!.
Oh, and I'll try option 2. from a couple posts ago before I take off flashing a bunch of ROMs, or after I delete stuff from this one and make a 2nd backup...like we rooted for! Clicked a couple more thanks too.
Re: [Q] There must be an answer to show apps
MiCeltic said:
..........
I believe this info is so obscure (except to ROM developers, I'm sure) because a lot of phones after Gingerbread got the menu option in the app drawer to hide icon shortcuts. So I'm going to keep this post in my favs and hope I get any email notifications if someone posts; and, search for articles now and then, but get back to living and leave this obsession behind...but not forgotten.
Click to expand...
Click to collapse
That's probably the best plan at this point sorry I couldn't help out more, but you have totally baffled me with this one just goes to show that the sdk can do far more than it lets on still, I hope one day you find that illusive tutorial and post it here
PS, gave you some thanks
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Hey h_m_m,
Thanks for the thanks!
I had time Sunday and I found some info and fixed them to show! I used search terms based on your statement that HTC hides some apps by default and found an article that referenced the, "/system/customize/mns/default.xml" file that contained a function, "applications_hide". So without getting into what I might do or might have done previously in the SDK, and since I was rooted, I just copied the file to my sdcard, attached to a computer and opened it in Notepad (needed to use the computer because it's well over 2000 lines in the file with no speed scrolling in es file explorer), changed (as one example):
<set name="plenty" max="7">
<item name="package">com.htc.android.Stock</item>
<item name="class">com.htc.android.Stock.StockWidget</item>
</set>
to
<!--<set name="plenty" max="7">
<item name="package">com.htc.android.Stock</item>
<item name="class">com.htc.android.Stock.StockWidget</item>
</set>-->
saved the file, mounted the file system using ES File Explorer and copied the file, then pasted it back in the, "/system/customize/mns/" folder. I commented the lines out so they wouldn't run and would still be there for history (instead of deleting the lines), and commented the code with a statement, <!--uncomment to hide the app's shortcut icon in the app drawer--> so that if I ever looked back I'd have info on it. I also did the same with the Sound Recorder, Voice Dialer, and WiFi (all at the same time as Stocks).
I did a factory reset and the shortcuts showed! This file, after all, sets the defaults. Well it didn't end there. I lost root. The su binary was still in it's folder(s) but Titanium Backup, ES File Explorer, and Super User wouldn't run...or rather wouldn't stop searching for root. It was like the su binary wasn't registered in the system; long story short, I re-flashed root.zip and all was right once more. The interesting thing is I had opened and abandoned this, "default.xml" file a couple times because it was so long and tedious to scroll through on the phone!
You can see a sample, "default.xml" for Gingerbread on code.google at http://code.google.com/p/warm-ginge...e/trunk/system/customize/MNS/default.xml?r=34 just stop the script if you get a pop-up. It's about 1/4 of the way down, or just do a find for, "applications_hide". There's only 2 things hid in that example file. ***Note that default is misspelled as defeault, but it seems to parse...it's in my phone's file that way too. I'd be cautious about opening that site on a phone browser, it seems to want to run on my computer when I open it.
What's the advantage of this? It could show apps or enable features that someone might like. This file sets all the defaults present OOB or after a factory reset, i.e., bookmarks, what I call sample app shortcuts and widgets on the screens, wallpaper, the 4 stocks in the stocks app, etc., etc., so those could be modified if desired as well. Proceed at own risk!
Clicking more thanks h_m_m! I don't know how long this would have taken without your feedback and input.
Re: [Q] There must be an answer to show apps
That is great news man I'm glad you got sorted and posted your findings here that's really interesting, and good to know
Tapped out from my sexy nexus 7