Hi, I've always liked to modify ROM ZIPs by just opening them, and then deleting the stuff I had no interest in (say, for example, DownloadProviderUi.apk), and doing that has always worked just fine after installing it (talking about Eclair and Froyo).
However, since the release of GB/ICS based ROMs, if I go as far as to modify just one file - even simply replacing the bootanimation.zip contained within the ROM ZIP, after it has been installed and rebooted, there's no lockscreen (deactivating and activating it again does nothing) and the HOME button doesn't work - it acknowledges that it's being pressed, but it simply doesn't do anything at all (return and recent do) - trying to change its default behaviour has no effect at all. As far as I'm aware, the problem spans across multiple (all I have tested) GB/ICS ROMs and a few different and completely unrelated (different brand) Android devices.
Also, installing those same ZIPs without making any modifications keeps any issues from ever happening.
I'm aware that they can be removed using ADB after it has been installed, using Root Explorer to mount /system as RW and deleting them manually, using Titanium Backup to freeze or remove, etc...
I'm mostly interested in having some light shed on the above issue. -Why- do those ROMs always fail if the ZIP file is modified in any way? Is there no way around it?
Thanks for taking the time to read
EDIT: Just in case, I've already tried searching for information regarding these problems, and other than unanswered to and very scarce comments, I've been unable to find anything revealing in any way - I'd appreciate if someone could point me in the right direction if there's something I've missed.
Are you signing your apks before trying to install them?
The APKs..? I'm guessing you meant the ZIP - if so, no. I could give that a try later and see how it goes...
No, I meant apks, but only because I've had an experience nearly exactly like the one you're describing and it was from trying to package the rom with an unsigned apk.
Ah. Well, I guess if I tried adding an APK it'd happen as well - my issue is I want to edit the updater-script (extract, edit with notepad++, throw it back in...) and/or remove APKs (for example, I have no interest in /system/app/DownloadProviderUi.apk). Like, fire up winrar or 7zip (tried with both), browse to the file, delete, then copy it over the to device and install the ROM - the bug always shows up.
Uncompressing the entire ROM, modifying away and then creating a new ZIP makes no difference, either...
EDIT: No dice - I've taken Hashcode's latest ROM, just for reference:
Untouched ZIP works flawlessly.
Modified unsigned ZIP doesn't have a lockscreen and the Home button doesn't respond when pressed (though it acknowledges being pressed).
Modified signed ZIP does exactly the same as the unsigned one.
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.
I have a brand new Ouya, running completely stock - not rooted or anything - and have sideloaded some emulators (YongZH stuff mostly) onto my Ouya. The ones I have tried work fine - with the exception of Gensoid 2.4.3 (the apk that I got from SlideME before YongZH pulled everything except N64oid)
If I go to a file browser, and install the apk and open it from the install screen, it opens fine. If I open a Sega Genesis .bin file using Gensoid, it opens fine. If I try to open it from the launcher - it closes as soon as it pops up.
Even deleting app data doesn't fix this.
I have done a factory reset, and reinstalled my apk files - still have the issue. Since the emulator runs fine, I can not figure it out, and think I may have a bad RAM sector, or it may be an issue with the Ouya launcher. Since the emulator does run, though, and I reinstalled the APK files in a different order, so I highly doubt it is stored in the same place in RAM, I can not figure out why it won't open.
Is anyone else having this issue? What could it be, and is there a fix?
hello all, I have a few problems with the process of sideloading google play onto my ouya, i am not a skilled android user but i am familiar w/ them and am a good reader/listener but i havent seen this issue anywhere so i hope someone here would be willing to help me out.
my goal was to sideload google play apk on my ouya. I successfully rooted it, installed the xposed framework and used ADB to push the ps4ouya_script contents onto my system.
it worked, but not fully. some of the files were successfully transferred but 2 technically did not. they show up, but are broken.
com.android.vending.apk and com.google.android.gms.apk are showing up as 0kb in system/app and I cant remove them. everything i try (overwriting via file managers, command line, re-pushing) all have no effect.
what can i do?
i have read and followed multiple guides here and on ouya forum to no avail. i'm sure i messed something up but i am at a loss as to what it is.
After further reading it sounds like ouya toolbox might help me with the removal of the broken system apps and this mod might be useful for a reinstall: http://forum.xda-developers.com/showthread.php?t=2359390
I'll try it and report back, but if anyone has any thoughts/insight I'd be grateful.
EDIT
Ok problem solved, Mod Collection For Ouya [link above] was able to [properly] install google play and it corrected the problems I had. If youre new to all this I highly recommend using it as its idiot proof. well, it helped me
Now for some MC4 action!
I didn't really see a post based on general experience everyone's having, mainly just different issues installing and what not. I'm also having a few issues that I didn't find much about and I'm hoping someone else ran into this and solved it.
I love the ROM so far. It's way better than stock IMO. I love having access to the play store without anything additional and the CM11 feel is awesome. The controller works fine on CM11 navigating, opening apps, etc. The trackpad isn't the best experience for scrolling and switching between pages, but it's there if you need it. XBMC works awesome. I'm running Kodi and have no complaints at all. I downloaded Quick Boot (Reboot) from the play store and it works perfect. Reboots, powers off, and boots me into recovery. I'm running SNES9x and NES EMU and both work great. The default controller template for Ouya didn't work, I had to remap the keys. I have PS one and PSP emulators installed but haven't tried them yet.
Issues:
-I'm unable to set a static IP for the ethernet connection. It's not listed in settings. Not sure if this is something I can set via SSH, but I'm unable to get in with the root password for the Ouya. I know I can set a reservation on my router to keep the same IP but I wanted to see if I could set it on the Ouya.
-I can't get my PS3 controller paired. It doesn't even work hard wired. I am aware of the steps on pairing and it did work fine on the stock rom, but it's supposed to work when you first plug it in as well. I've tried sixaxis to set the master but that didn't work either.
-CWM backup. I can backup without any issue in CWM but I was looking for the backup on the SD card so I could copy it to my machine for a backup but couldn't find it using ES explorer or Root explorer. The path in CWM shows \SDCARD\Clockworkrecovery\backup but the backup folder does not exist. However in advanced restore in CWM it shows the backup.
One last thing. I couldn't find a step by step in reverting back to stock. I have found the zips to flash but 'm not sure if I can just flash the stock fw and reboot or if there is something else required. I didn't want to test until I could figure out how to copy the CM11 backup from the device.
Appreciate everyone's input and look forward to hearing your experience as well!