Related
About:
This tool is meant to easily compare the contents of two rom archives and allow easy manipulation by copying files from one rom to another and removing files from a rom archive. The idea is to specify two rom archives which have the same structure, usually something like the following:
[data]
[META-INF]
[sdcard]
[system]
flash_image
modem.bin
zImage
I made it because I would like to know which files/apks might have been removed from one rom compared to another, which isn't always clear from the descriptions. But then thought other people might find it usefull as well, so here it is
It's written in java, just extract the zip and run through run.bat (windows only) or the .jar file.
Update, version 2 added
Ok, I tested it today and seems to work fine... Was able to reflash a rom modded with this tool (file from another rom added, other files removed).
For now it just allows transferring of files between roms and removal of files from a rom archive.
How it works:
1. Load the rom-archives (zip only) using the browse buttons. If one file is selected all contents are simply listed, in case 2 files are supported only the extra files per rom are listed.
You can filter on .apk/.odex files only by using the checkbox and pressing 'Scan'.
2. By using the 'Copy >>' and '<< Copy' buttons you can copy files between roms, these entries will be colored GREEN in the respective table views.
3. By using the 'Remove files' buttons you can remove files from the roms, these entries will be colored RED in the respective table views.
4. Save the rom by pressing the proper 'Save Changes' button and specifying the name of the .zip it has to be saved to.
A progressbar will show the progress and you'll get a message telling you when it's done. It's not the fastest but it does the job. The resulting zip can then be flashed through clockworkmod (at least the one I tested it with could ).
THere are prolly some bugs when you move files back and forth and delete files in between and adding them again, etc... I just tested it with moving a few files from one rom to another and deleting a few form the target rom. This worked fine, but please let me know about bugs and issues.
Update, version 2.1 added
Allrighty, I included the data from the spreadsheet found here:
http://forum.xda-developers.com/showthread.php?t=1069924
To display information about the selected apk's in the table. This gives you a quick overview about what an apk does and whether or not you can and want to remove it. It's displayed in a little text area below the table.
I also changed it so that by default one 'view' is shown, once a first archive is selected the option to select a second one is enabled by displaying the proper buttons. Only after a second file is specified the complete view is shown (two tables, etc).
That's it again for now
Use it at your onwn risk!
Thanks this is very helpful tool.
Would love to see this further developed...two thumbs up!
Sent from my GT-I9100 using Tapatalk
Subscrived to this topic in a hope to see development on it
Sent from my GT-I9100 using xda premium
Woooww, this tool is awesome, how about adding feature like u can copy one or more file from one archive to another one so we can not only remove but also add
I hope u will improve this app further in the future!
Sent from my GT-I9100 using Tapatalk
Thanks for the comments people, good idea about moving apk's to one and another as well indeed To be continued (and always open for suggestions!)
Also updated main post, but...
I rewrote it to allow removal of files and copying of files between two rom packages, I haven't been able to test it myself yet (finished it just now and really need to catch some sleep) but will try to do so tomorrow... However, if anyone else wants to give it a shot as well please let me know and I'll send it (tomorrow evening or monday prolly). I will not put it up before it has been tested and it is about 2:30am here so time to go to sleep. If I get a chance to test and upload tomorrow I'll do so...
Will try to check this topic tomorrow again but can't promise... Busy day.
Clever tool. Will definitely watch this develop
Gr8 work pal. Please continue your development. Is really a handy tool.
Updated 1st post with new version and some instuctions/clarifications
wow. missing that tool.
And another update, added ifnormation display about the apk's using the spreadsheet from this source:
http://forum.xda-developers.com/showthread.php?t=1069924
and changed the UI a bit to make it a bit simpler...
ps. Thinking about adding a feature where you can add seperate apk's/files... Would have to think about how to add that without rewriting too much.
Hey guys. So I made this hack for my old epic, then my GSII, now I'm posting it here since I know I DEFINITELY wanted unrestricted hulu access on such a nice tablet, without the extra price/"not available for devices" BS of Hulu+. This should also work for any other sites that restrict mobile devices. This hack simply changes 3 characters in the flash library file from AND to WIN, and copies my modded file over the stock/updated adobe file upon each boot.
For those who wish to learn more the original post can be found here: http://forum.xda-developers.com/showthread.php?t=114215
New install instructions
Flash via CWM OR follow the instructions above, but you must locate the files within the zip sub folders. They are in the folders they should be in if you were to unzip to the device root. You may also copy and paste with root explorer if you prefer that to ADB (I do). Just make sure you get the file permissions right (they should match other files in the same folder).
NOTE: If you have adfree or another adblock, you'll see a message to disable it, you don't need to disable it (they just want you to watch their commercials), just wait the 30 seconds or whatever it is and that black message counts as your commercial, and your show will play
Once we get a few custom kernels out there with init.d support we won't need script manager (init.d support just means it will run all scripts in the folder /system/etc/init.d) making the process a bit cleaner but for now this works. I also have a cwm flashable version but we'll have to wait a bit longer for that. For now let's just be happy Jcase got us root Enjoy!
EDIT: Updated for ICS AND JELLYBEAN and flash version 11.1.115.12 (8/9/2012) (latest..for now) LATEST VERSION IS BUILT TO BE EASIER/MORE RELIABLE FOR SOME USERS
TESTED: Confirmed on Galaxy SII on CMX. Turns out Jelly Bean (and maybe ICS) have changed the order on boot so that init.d runs BEFORE flash overwrites our hack on each boot. In other words, the flash APK is re-unpacked in its non-hacked form by adobeflashplayer on each boot somewhere after the boot animation and probably just before the homescreen is displayed. The init.d scripts we run are unfortunately run at the VERY beginning, while the OEM logo is still displayed (BEFORE the boot animation). Because of this, script manager is currently absolutely required until I can find another "entry point" to run these scripts
It is this unfortuante order that requires using script manager to run the script "on boot" later in the process.
Be sure BUSYBOX is installed or GTFO
It IS typically included in most custom roms, but still, MAKE SURE.
HOWTO Video (without using the adb method above though it still works just fine) thanks to jjdevega if you need it here http://youtu.be/rXTdIyMP_Xs
OLD install instructions below for those without CWM:
So here goes.
1. Update flash via the market to the latest version
2. Download & unzip the 2 files linked below to be pushed to /data/flash
3. adb shell mkdir /data/flash
4. adb push S98fixflash /data/flash
5. adb push libflashplayer.so /data/flash
5.5 (almost forgot) Install Busybox from the market, let it run, grant su, and have it install the latest busybox for you
6. Install Script Manager from the market
7. Open Script Manager and be sure to select to give it root access
8. Browse to /data/flash in Script Manager, select S98fixflash and select root and boot options (thus making it run on each boot, with root permissions)
9. Reboot (Press + hold power, power off)
10. Open Browser, open settings, advanced, user agent string, desktop
Thanks OP for the mod!!!
Now that we have root can anyone try vgeezy's hacked apk and see if it works? this method should allow hulu.com and is much more noob friendly.
http://forum.xda-developers.com/showthread.php?p=20598069#post20598069
Great mod already instaled it
Wysłane z mojego Transformer Prime TF201 za pomocą Tapatalk
For those saying they got this to work, how were they able to get a root adb shell on their comp to make this work? Although rooted with vipermods tool, I cannot get a root adb shell through windows, and my understanding is that it takes a modified boot-img for that to happen.
Is there a way to make this mod work from a terminal on the tablet? Thanks!
Edit: Tried opening the prime's internal storage up through windows, going to android/data and creating a 'flash' folder and moving the two files into it. Then going through script manager and setting the script to run as root at boot.
Didnt work.
However using ES to move the files to system/data/flash and setting to run at boot from there seems to have worked.
Any help?
---------- Post added at 09:05 PM ---------- Previous post was at 08:43 PM ----------
Also, is it just me or does ScriptManager constantly force close for anyone else?
mikek9 said:
For those saying they got this to work, how were they able to get a root adb shell on their comp to make this work? Although rooted with vipermods tool, I cannot get a root adb shell through windows, and my understanding is that it takes a modified boot-img for that to happen.
Is there a way to make this mod work from a terminal on the tablet? Thanks!
Edit: Tried opening the prime's internal storage up through windows, going to android/data and creating a 'flash' folder and moving the two files into it. Then going through script manager and setting the script to run as root at boot.
Didnt work.
Any help?
---------- Post added at 09:05 PM ---------- Previous post was at 08:43 PM ----------
Also, is it just me or does ScriptManager constantly force close for anyone else?
Click to expand...
Click to collapse
Connectbot can replace adb. Also, you don't need to use adb at all, you can use root explorer to place the files in the correct locations, it's just easier to write a step-by-step that way. Also, if you rooted, you could try running from that same folder as you will have the adb tool within the "one click root" folder you most likely used (or normal platform tools if you used jcase's step-by-step).
Script Manager doesn't have issues for me, it's very popular software and well made. Maybe try uninstalling/reinstalling? If not, clear cache/data for script manager and try again? Not sure...
EDIT: If you don't HAVE root, and try to OBTAIN root while running script manager, it will force close I believe. Make SURE you have root, use adfree or titanium backup to confirm maybe...
2nd Edit: Also, don't use usb transfer, that just puts it in the 'internal sd' folder. Use root explorer and back all the way out to the root directory first.
I tried this and couldn't seem to get it to work. However, for anyone looking for a quick way to watch hulu in a browser, download "flash video browser" from the market. It is $0.99 I believe and no additional tinkering is needed.
Sent from my Transformer Prime TF201 using xda premium
Moving to Themes/Apps as it is related to a Theme or an App.
jerdog said:
Moving to Themes/Apps as it is related to a Theme or an App.
Click to expand...
Click to collapse
Works for me, wasn't quite sure which. Thanks!
Worked like a charm. I just used Root explorer to make the data/flash folder. Had problems with script manager fcs but cleared data and cache from the manage applications and then it worked just fine.
Sent from my Transformer Prime TF201 using xda premium
not working after the ics update. redid the mod and used script manager post-update but not working. Used dolphin browser with uA set to desktop.
i get a blue lego block with a ? mark in the center of where the video should be.
Sent from my Transformer Prime TF201 using xda premium
Not sure about dolphin, i uploaded new files for ics (though the old ones do work). Make sure in the stock browser you check request desktop site in the menu button. Works for me.
ok trie dthe updated files. NOW WORKS PERFECTLY!!!!!!!!!!! thanks so much. also i recommend ics+ browser bc it lets u keep desktop user agent permanent.
Sent from my Transformer Prime TF201 using xda premium
For those those that don't have root and/or don't wish to mess with root/existing Flash installation an alternative is to buy/use Flash Video Browser. Works great on the Prime and was recently updated with ICS compatibility. Works great with Hulu.
Those who did this, did it affect your ability to upgrade to ICS? I'd like to try, but don't want to miss out on future OTAs.
chinly43 said:
Those who did this, did it affect your ability to upgrade to ICS? I'd like to try, but don't want to miss out on future OTAs.
Click to expand...
Click to collapse
No has nothing to do with ota. i had the mod before when i was on hc, upgraded fine to ics, redid the mod and i was good to go.
Sent from my Transformer Prime TF201 using xda premium
Thanks - I was curious, since removing built-in apps prevented the OTA I thought this might too.
ravizzle said:
No has nothing to do with ota. i had the mod before when i was on hc, upgraded fine to ics, redid the mod and i was good to go.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Any clue why the User Agent String option might be missing from Settings>Advanced?
It's odd, because when I first got the TP I hunted for it, but couldn't find it--but then stumbled across someone mentioning it online, and lo-and-behold it had appeared for some reason.
Now that I'm trying to use this hack, it's missing again. Any ideas?
I usually just press menu -> Request desktop site.
Hulu works great with this mod in desktop mode. That add message threw me off, thanks for the warning, video started 30sec later.
thanks, worked perfectly with root explorer
Found a working package for the Touchpad:
http://dl.dropbox.com/u/33540509/cwmpolafficea500.zip
It works for me on ICS Alpha0.5.
Flash it in recovery and you're good to go.
This package is not my work nor am I responsible for it not working on yours or doing any harm.
Hope it works on yours too.
Sent from my GT-P7510 using xda premium
Thanks. I will try it out. They really should bring it to the market, they'd make way more money than through OEM s
Works great so far, but have to say that each time you flash a new build (today Dalingrin released A0.6) you have to flash this file again.
Recommended is to place the file in your cminstall folder (I assume most have set a specific folder for all their flash files) and flash it each time you flash the new build & gapps etc.
I just installed the app and copyed the lib and apk files using Root Explorer and set the R/W to the same as everything else. If you just install the apk it will launch but force close when you try to create a new document.
I have been using OfficeSuite Pro 5 and liking it in the past. It was the only Office Suite that supported a tablet UI on CM7
been looking for this. thanks.
spunker88 said:
I just installed the app and copyed the lib and apk files using Root Explorer and set the R/W to the same as everything else. If you just install the apk it will launch but force close when you try to create a new document.
I have been using OfficeSuite Pro 5 and liking it in the past. It was the only Office Suite that supported a tablet UI on CM7
Click to expand...
Click to collapse
What do you mean? For me it worked out-of-the-box.
Even create and edit of documents.
Polaris Office - cannot edit
Hi all,
I have installed this package using the rootexplorer method.
It works well on my HP Touchpad, Dual boot with AOKP.
But I cannot edit the documents, I can create new and save. But there is no option to edit. It is like this package is designed for android devices with a menu button. i.e. open file , menu, edit....
Does anyone know a workaround or, have an ICS compatible package that displays the menu button?
Thanks.
Enable Copy & Paste on the Nook Tablet
Background
The lack of copy & paste functionality on the Nook Tablet is one of the most annoying "features" of the B&N firmware and it affects not just geeks like me but also the average user. This thread and this thread are two of many, many threads complaining about the missing copy & paste. This thread proposes a "fix" by combining the Hacker's Keyboard and Swype, but is still really lame.
The method I will describe here solves the problem by replacing /system/framework/framework.jar which contains the code for Android widgets like text fields. I have merged into the stock /syste/framework/framework.jar the code responsible for copy & paste from the Android source code.
Instructions
Video walkthrough: http://www.youtube.com/watch?v=7V70a3FYbt4
0. Before you proceed, know that THIS IS EXPERIMENTAL SOFTWARE THAT PROBABLY VOIDS YOUR WARRANTY AND MAY PERMANENTLY OR TEMPORARILY BRICK YOUR TABLET. Even though it worked for me, it may not work for you, and worse, it is quite possible that it could cause your tablet to boot-loop or die. I AM NOT RESPONSIBLE FOR ANY POSSIBLE DAMAGES TO YOUR TABLET / ANYTHING ELSE CAUSED BY THIS METHOD. BY USING IT YOU AGREE TO ASSUME ALL RESPONSIBILITY FOR YOUR ACTIONS.
1. Your tablet needs to be rooted for this to work. If you have not rooted it yet, search this forum for instructions.
2. Since we will be copying files to /system, you will need to install ES File Explorer or Root Explorer or whatever other app that allows you to do that.
3. Download the file that corresponds to your OS version from below:
1.4.2 (16GB/8GB): http://www.mediafire.com/?5pf2aegq02194lq MD5: ef35d35daffd0d9574f48a43ccc4b58c1.4.0 (16GB): http://www.mediafire.com/?es6gd31wzr7yk8a MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
The 1.4.0 version has been reported to cause boot loops for some people, while it has worked for others. You have been warned.If you're on a different OS version, post the file /system/framework/framework.jar form your tablet and I will make a package for it.
4. Extract file contents to microSD card, and insert microSD card into the tablet.
5. Using ES File Explorer / Root Explorer, copy the extracted file framework.jar.new to the directory /system/framework/. (If you're using ES File Explorer, make sure "Up to Root", "Root Explorer", and "Mount File System" are checked in settings.)
6. Copy the extracted file uim-sysfs to /system/bin/.
7. Go to /system/bin/, and change the permissions of the file uim-sysfs to executable. (If using ES File Explorer, long press -> Properties -> Change -> Check everything under "execute".)
8. Power off tablet and power on again. The tablet should take much longer to boot this time than normally, so no need to worry. When the tablet boots up, you will most likely see lots of force close dialogs. This is normal.
9. Wait one minute. You could be stuck in a boot loop if you don't wait.
10. Power off tablet and power on yet again. This time it should also take much longer to boot; the boot times will return to normal after several reboots.
11. Profit.
Force close issues
The first time you run some (read most) apps after applying this hack would likely result in force closes. While annoying, there is no way to get around it due to how the Dalvik VM caches references to /system/framework/framework.jar. In addition, every time you install new apps or update apps, you will have to reboot the machine before those apps are usable; you will get a force close when you try to use those apps until you reboot.
The solution is simply to reboot your tablet each time you get a force close error from an app that worked fine before this hack. The force close error for that particular app should go away following a reboot. If you get a force close from another app after that, just reboot again.
How it works
The information below is for people interested in understanding how this stuff works. If you just wanted to enable copy and paste on your tablet, you can stop reading.
This hack is based on the exploit explained at http://forum.xda-developers.com/showthread.php?t=1534518. The uim-sysfs script in the attached file saves the stock /system/framework/framework.jar, copies over my modified framework.jar.new, and restarts the zygote process. After the zygote process has loaded my framework.jar.new, the uim-sysfs script restores the stock /system/framework/framework.jar so that /init will not bail on the next boot.
To enable copy & paste in /system/framework/framework.jar, I decompiled the stock implementation and merged in related code from AOSP. The two classes I changed are android.widget.TextView and android.widget.EditText. For android.widget.EditText, I simply used the AOSP implementation because the only difference between the two was in the enabling of copy & paste. I manually merged android.widget.TextView because there appears to be B&N enhancements in it in addition to disabling copy & paste.
The exact steps I took as well as a diff of my modifications are documented in post #12.
Disclaimer
Again, this is experimental software. That it worked for me does not mean it will work for you, or that it won't brick your tablet. I am not responsible for any possible damages resulting from using this method.
Here i post framework.jar from stock 1.4.0 rooted
~ Veronica
lavero.burgos said:
Here i post framework.jar from stock 1.4.0 rooted
Click to expand...
Click to collapse
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
16gb Nootlet with 1.4.0 rom, rooted, OTA blocked yada yada.
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
Lots of FC, the last persistent one was the launcher (ADW ipaidforthis version)
Powered off and on again after waiting way longer than 1 minute.
Second boot forever at "read forever" screen so far.
If it comes back to life I'll try the 1.4.0 version & let you know.
[Edited to add}
... time passes ...
Any way out of the "ADWLauncherEX" force-close loop? Does Android have a "safe mode" boot option like Windows? (sorry)
No, I haven't installed CWM recovery yet. Remind me to do that if this thing ever gets over its mental breakdown.
jichuan89 said:
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
Click to expand...
Click to collapse
Thanks can't test right now 'cause im finishing another project and then i have to test the tun.ko module for CM9 busy bee .
~ Veronica
cellhead said:
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
...
Second boot forever at "read forever" screen so far.
Click to expand...
Click to collapse
Thanks for mentioning this. Will add to instructions.
cellhead said:
Any way out of the "ADWLauncherEX" force-close loop?
Click to expand...
Click to collapse
Getting FC's is normal - as the instructions state you probably have to reboot a number of times before all FC's disappear. Any luck so far? If not, please let me know and I will post a recovery SD card image that will allow you to undo this hack.
Also - as I said clearly in the instructions (Compatibility section), before you try this out on your 16GB, you should post your /system/framework/framework.jar so I can verify that this works on the 16GB. I don't have the 16GB tablet so I don't know if this works on it at all. Anyone?
Thanks. You may want to feature the version info prominently in the OP. I got my issue solved in a roundabout way when it finally went into a boot loop and triggered the factory reset. That got me back to 1.4.0 unrooted, and without the FC problems. Reran indirect's rooting script and I'm back to some semblance of normality.
Ain't complaining, I took on the risk of trying your copy/paste fix and went on an unplanned adventure. Such is life as a RL software tester ;-)
I'll wait and see how things shake out. You're onto something good here, so once it's a little safer for the normals to apply it, I'll give another go.
For the record, 16g Nook tablet, rooted via indirect, OTA blocked, v1.4.0
cellhead said:
You may want to feature the version info prominently in the OP.
Click to expand...
Click to collapse
You're right...really sorry about that.
On the other hand, did you try the files in the original post, or did you use the files for 1.4.0 I posted in the 3rd post?
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Sent from my BNTV250 using xda premium
cellhead said:
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Click to expand...
Click to collapse
The files in the original post are modified from 1.4.2 and would most certainly not have worked on 1.4.0...I should have made that clearer. Sorry.
The files in the 3rd post though are modified from 1.4.0 (thanks to lavero.burgos) and should work for you. Any chance you could test them out?
--- EDIT ---
Also - I've made a bootable SD card that will remove this hack and fix the tablet even if something goes wrong and you cannot boot into the system to remove the files directly. I can post it if someone needs it.
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
pfalcon said:
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
Click to expand...
Click to collapse
Thanks for the link! I went and downloaded the update archive and extracted it, and can confirm that the /system/framework/framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2., which confirms my hypothesis in posts #11 and #14 in http://forum.xda-developers.com/showthread.php?t=1517513&page=2. The bizarre thing is that if you unzip the files they produce the exact same content; it looks like they differ only in some sort of signature. But this means that my framework.jar will work on both the 8GB and 16GB on 1.4.2. So thanks again for the link!
pfalcon said:
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
Click to expand...
Click to collapse
What I did was this. You need zip, unzip and a tool called apktool. I'm assuming the framework.jar from the Nook is called ~/framework.jar.nook and the framework.jar from vanilla Android (AOSP) is ~/framework.jar.aosp.
1. Extract framework.jar into a directory z:
Code:
$ unzip framework.jar -d z
2. Use apktool to disassemble framework.jar.nook:
Code:
$ apktool d ~/framework.jar.nook
3. Disassemble framework.jar from AOSP.
Code:
$ apktool d ~/framework.jar.aosp
4. Compare and modify framework.jar.nook.out/smali/android/widget/{TextView,EditText}.smali against framework.jar.aosp.out/smali/android/widget/{TextView,EditText}.smali. My diff file can be downloaded here. Apply diff with
Code:
$ cd framework.jar.nook.out; patch -Np1 < jichuan89_nook_text_hack.diff; cd ..
5. Recompile Nook's framework.jar:
Code:
$ apktool b framework.jar.nook.out
6. Repackage modified Nook's framework.jar into ~/framework.jar.new
Code:
$ cp framework.jar.nook.out/build/apk/classes.dex z/classes.dex
$ cd z; zip -r ~/framework.jar.new META-INF classes.dex preloaded-classes; cd ..
framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2
Click to expand...
Click to collapse
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b. Anyway, good news that contents were the same in your case too. It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
What I did was this.
Click to expand...
Click to collapse
Thanks for the instructions and the diff! I with that all hacks posted on the forum came in such form ;-)
pfalcon said:
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b.
Click to expand...
Click to collapse
Nice - thanks for confirming this. That's really helpful to know.
pfalcon said:
It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
Click to expand...
Click to collapse
Right - it would make economic sense for B&N to make the software on the two tablet models to be as close as possible. I do hope they'll make their and our lives easier by just using the same version of the same damn files in the next update for the two models, as you said.
Sent from my Nook Tablet using XDA
I can make CWM flashable zip with original framework.jar for the ones having troubles until is fully tested. Tomorrow i'll jump back to stock 1.4.0 to test this hack and report back.
~ Veronica
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
CRE said:
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
Click to expand...
Click to collapse
No - this is for the stock firmware. CWM should have copy & paste already because it doesn't use B & N's framework.jar.
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
CRE said:
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
Click to expand...
Click to collapse
No. If there were requirements I would have put them in the instructions. It doesn't matter how you boot.
Sent from my Nook Tablet using XDA
Thank you. I guess I'll repartition first then get this out of the way too.
problems:
1. trackballwake
I execute this command through adb shell/terminal, reboot, didn't work, finally I found that curcial-oj.idc became empty. Then I used root explorer to edit this file but always empty. I quit, and reflash rom with fix permission. Set the value by text edit.
2. Music&Gallery can not recognise files
Apollo and Google Music Player can not recognise the media files in sdcard, gallery either. Sdcard was partitioned by CWK 5, ext 2G,swap 0mb or 32mb(try several times). I even use fix permission. But these didn't work. BTW, CM10 can recognise the correct size in "setting -> storage" but apollo shows empty list.
root explorer -> into music dir-> open a .mp3 file
-- use apollo -> show error
-- use google music player-> play it normal.but this player cannot scan files in sdcard either.
Then I found that. If I transfer files by USB storage mass. The .mp3 files cannot be fount. So I try assistant programs like 'wandoujia' (-- wandoujia.com can download this ,which can transfer files through ftp protocal) ,and the media files show up.
list:
1) format sdcard or partition. didn't work.
2) fix permission. didn't work
3) double wipe and reflash the rom. didn't work
4) use other assistant program. work but transfer very slow
3.setting -> storage -> [menu -> usb connections] : other types can crash the setting.
spent much time in p2. other feathers had no time to try.
by WinSuk--------
1. Make sure you are on the 1.02 bootloader (included in the Froyo RUU) & S-OFF.
2. Try deleting the Android/data/com.cooliris.media folder. If you have too many mp3s in one folder, that can cause it too
--------
1. It's already 1.02 and S-OFF. I try again this noon and trackballwake work. Maybe it's because the permission.
2. There's no such folder. But perhaps can workaround in this way: Flash CM9, open Apollo and Galery3D, then flash CM10 without double wipe after they reload the resources.
I had restore the files through wandoujia and have no time to try this way. Someone who has this problem could do sth like that. And I hope WinSuk can find out the reason. It seems so many people who use Android 4.1 have this problem.
dcshallot said:
by WinSuk--------
1. Make sure you are on the 1.02 bootloader (included in the Froyo RUU) & S-OFF.
2. Try deleting the Android/data/com.cooliris.media folder. If you have too many mp3s in one folder, that can cause it too
--------
1. It's already 1.02 and S-OFF. I try again this noon and trackballwake work. Maybe it's because the permission.
2. There's no such folder. But perhaps can workaround in this way: Flash CM9, open Apollo and Galery3D, then flash CM10 without double wipe after they reload the resources.
I had restore the files through wandoujia and have no time to try this way. Someone who has this problem could do sth like that. And I hope WinSuk can find out the reason. It seems so many people who use Android 4.1 have this problem.
Click to expand...
Click to collapse
i'm not sure what is causing the issue, but i can say that i did this:
- full wipe of caches, /system/, /data/, /sd-ext/, etc. (but not normal SD partition)
- install winsuk CM10 alpha 4 from clockworkmod
- boot into CM10, reboot into recovery
- install winsuk's small gapps
- boot into CM10
and everything seemed to work great. apollo reads my MP3s fine (i have a fair amount, maybe 800+ in one folder?), etc. they are in /sdcard/media/Music/ i believe.
and since i can't post on the dev forums just yet, just wanted to say a big thank you to winsuk and munjeni!
Blade2187 said:
i'm not sure what is causing the issue, but i can say that i did this:
- full wipe of caches, /system/, /data/, /sd-ext/, etc. (but not normal SD partition)
- install winsuk CM10 alpha 4 from clockworkmod
- boot into CM10, reboot into recovery
- install winsuk's small gapps
- boot into CM10
and everything seemed to work great. apollo reads my MP3s fine (i have a fair amount, maybe 800+ in one folder?), etc. they are in /sdcard/media/Music/ i believe.
and since i can't post on the dev forums just yet, just wanted to say a big thank you to winsuk and munjeni!
Click to expand...
Click to collapse
I've tried this way. It didn't work -.-
And I found something just now. The folder /storage should be set permission 666 or sth to allow apps for full accessing. Now I do set 666 and clear Apollo&Google Music Player datas and restart both apps. Then they found out the MP3s~~~
BTW. There's another problem. I'm chinese, and it cannot use chinese names' pinyin spelling to locate the contacts in dial pannel. Then I found a Contacts.apk and ext.jar to replace the files under /system/app/ & /system/framework/ , finally resolve that.
View attachment Contacts.apk
View attachment ext.jar