After rooting via Indirect's method, many sub-menus are not readable due to the text being the same color. Has anyone found a standalone fix for this? (I noticed snowball mod addresses it but am already rooted).
there is a partial fix available, but as of now it isn't practical to implement.
btw, there is a discussion about this later down the board. I can't link to it right now. I asked the same question, and I was told to use search instead of the answer and a link to the discussion. I wanted to let you know better than I was told what was going on about this issue.
From what I understand this is a non-trivial problem to solve.
The snowball root method has the fix for this, but its injected while in the root process, but i have read that the framework-res.apk provided in the snowball-mod.zip contains the fix (replaced files) and apparently by just replacing this .apk to your existing system/framework/framework-res.apk it should do the job. However i haven't found someone that has tested this yet and i dont have my nook yet so if you want to give it a try DO IT AT YOUR OWN RISK. Dont worry if it doesn't work you may get bootlops or FC's nothing major and by doing the "magic card" method for go back to stock you be fine again.
I will attach the framework-res.apk if someone wants to give it a try and please report back the results.
*NOTE: You need to uncompress first and inside you will find the .apk
Path: system/framework/
1. Copy the .apk to your sdcard
2. Using a file explorer (eg. root explorer, es file explorer) navigate to your sdcard find the .apk you just copied and copy it
3. Go back and navigate to system/framework/
4. rename the existing framework-res.apk to framework-res.apk.bak
5. immediately hit paste
6. reboot
7. report back
Veronica
lavero.burgos said:
The snowball root method has the fix for this, but its injected while in the root process, but i have read that the framework-res.apk provided in the snowball-mod.zip contains the fix (replaced files) and apparently by just replacing this .apk to your existing system/framework/framework-res.apk it should do the job. However i haven't found someone that has tested this yet and i dont have my nook yet so if you want to give it a try DO IT AT YOUR OWN RISK. Dont worry if it doesn't work you may get bootlops or FC's nothing major and by doing the "magic card" method for go back to stock you be fine again.
I will attach the framework-res.apk if someone wants to give it a try and please report back the results.
*NOTE: You need to uncompress first and inside you will find the .apk
Path: system/framework/
1. Copy the .apk to your sdcard
2. Using a file explorer (eg. root explorer, es file explorer) navigate to your sdcard find the .apk you just copied and copy it
3. Go back and navigate to system/framework/
4. rename the existing framework-res.apk to framework-res.apk.bak
5. immediately hit paste
6. reboot
7. report back
Veronica
Click to expand...
Click to collapse
i can confirm that this works. the only thing you would need to double check before replacing the framework-res.apk is to check the permissions and make sure they are correct because once you replace the apk, the NT auto reboots and if you did the process correctly it will boot up normally, otherwise you will be stuck in an infinite boot loop...
The fix did not work for me I made sure the permissions were the same but my go launcher settings are still white on white
Montisaquadeis said:
The fix did not work for me I made sure the permissions were the same but my go launcher settings are still white on white
Click to expand...
Click to collapse
If you got the snowball bootanimation then the framework-res.apk applied just fine.
However, as I may have mentioned above, but have certainly mentioned elsewhere: the white-on-white fix in snowball-mod is a stop-gap for one specific set of menus (and could even cause black-on-black for those menus!)
We cannot fix all white-on-white, and black-on-black problems without entirely retheming just about everything in the framework-res.apk, which involves the backgrounds and the texts.
As noted above: "this is a non-trivial solution".
Does the snowball animation say hack by Barnes & Noble?
Edit Looks like the modified framework-res.apk file is what is causing the nook not to charge while its on as my nook has stopped charging when its on which sucks as I use the nook constantly through out the day.
Well, if you want to just spill the beans like that... yes.
Just wanted to make sure it had taken as I havent payed any attention the boot animation in the past
Related
Discontinued. The latest versions of all previously supported ROMs have this functionality built in.
This gives you an over-scroll glow when you reach the end of a list.
I really hope you knew that before clicking on this thread.
Example if you don't know what I'm talking about
It's just a modified framework.jar with modified files allowing the over-scroll to work and the correct glow images assigned to it. Theming is very easy, just colorize the over-scroll glow pngs in framework-res.apk. The default is orange.
What I want to do with this thread is sort of have a place where you can find the over-scroll enabling mod for every popular ROM for our phones. If you think I should support a ROM that I currently don't, then please post in the forums because I read every post! Ask to put a ROM on the wishlist. Upload the ROM's framework-res.apk and framework.jar files and I'll work on it when I'm not busy with school.
Currently, the wish list is:
Stock KH7
[Update on 10/15/11] UnNamed v1.0.1 compatible files uploaded. Give them a try. Honorable mention to quarlow
Installation:
BACK UP YOUR OLD FRAMEWORK.JAR
Because I'll just laugh at you if you complain that your phone won't boot up.
>>>ADB:
Code:
Extract the CWM package to get the framework.jar
adb remount
adb shell
su
cd /system/framework/
cp framework.jar framework.jar.backup
exit
exit
adb push framework.jar /system/framework/
adb reboot
>>>ROOT EXPLORER:
Extract the CWM package to get the framework.jar
Okay, now you can theoretically do this, but why would you want to? You'll get lots of crashes and might mess something important up.
Go to: /system/framework/ and rename framework.jar to something else. Go back to where-ever you saved my modified framework.jar and copy it over to /system/framework/ and change the permissions of the new framework.jar to match the old one. I'm pretty sure it's rw-r--r--, but don't quote me on that. + Restart your phone.
Simba501 has a more indepth tutorial on how to install this mod through Root Explorer here
>>>RECOVERY (preferred):
Flash the one specific to the ROM you're running
Whatever method you choose, know that it will take a stupidly long time for your phone to boot-up. Don't worry though, it'll be worth the wait.
Yoderk created some cool themes for the over-scroll glow for Cognition Beta-4 which you can find HERE.
UnNamed 1.0.1 works with 1.0.2 and 1.0.3 as well.
Also, please remember to say THANKS if I helped you!
cwm please!!
<3
diabolicalangle said:
cwm please!!
<3
Click to expand...
Click to collapse
It's there if you REALLY need it. I haven't tested it and to be honest, it's been a very very long time since I made my last CWM compatible file. Maybe it works though, try it out. If not, then use one of the other methods.
Fine work sir! Works well on Cog Beta 4.
yoderk said:
Fine work sir! Works well on Cog Beta 4.
Click to expand...
Click to collapse
That's awesome! Someone test it on stock w/ root, because if it works there, I'll be amazed.
Confirming that the cwm flashable zip works on cog beta 3!
Working fine here. I'm technically on Beta 1, but I've manually added the components I wanted from each Beta update because there were things I didn't want.
I have a suggestion. I don't know why everyone repeats that method for using root explorer. That's a terrible way to do it. I always use root explorer to manually replace my files and have never experienced any issues. Here is the correct way to use root explorer for manually replacing modded files:
1. Navigate to the file that you plan to replace (in this case, system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. In this case, the permissions are RW-R-R, which in root explorer, means that the first two boxes on the first line are checked and only the first box on the next two lines are checked.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and that the permissions also match what it is replacing.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
Cwm file worked great on cog beta 4. Thnkz!!
Sent from my SAMSUNG-SGH-I777 Cognition
Simba501 said:
Working fine here. I'm technically on Beta 1, but I've manually added the components I wanted from each Beta update because there were things I didn't want.
I have a suggestion. I don't know why everyone repeats that method for using root explorer. That's a terrible way to do it. I always use root explorer to manually replace my files and have never experienced any issues. Here is the correct way to use root explorer for manually replacing modded files:
...
No force closes, no problems .
Click to expand...
Click to collapse
Thanks! I added your tutorial to the OP.
Well if your like me and hate orange! Then here are two framework-res.apk with a blue and green overscroll color. Just rename them to framework-res.apk and overwrite the original file in system/framework.
Do not forget to back up original file! I claim no responsibility to problems.
Very subtle but a very nice touch...kudos...came zip worked great!!!
Sent from my SAMSUNG-SGH-I777 using XDA App
stock with root, i've got nothing. tried root explorer method and cwm
Does this still have the problem of not changing the Contacts or other Samsung apps?
illathanyours said:
stock with root, i've got nothing. tried root explorer method and cwm
Click to expand...
Click to collapse
Alright this may be Cog4 only... if you want, upload your framework.jar and framework-res.apk and I'll mod it for you and let me know if that works.
MikeyMike01 said:
Does this still have the problem of not changing the Contacts or other Samsung apps?
Click to expand...
Click to collapse
Yes. Those need the tw-framework to be modified and I haven't taken a look at those yet since I'm trying out Perception for a couple of days and that already has it coded in? But it isn't a problem per-say, it's just how Samsung decided to code those specific apps and there isn't a way to implement them in 2.3.4 without breaking the slide left to call, slide right to message, feature. 2.3.5 Roms have that built in on Samsung apps.
Problem probably isn't the best word.
Thanks for answering though. I always wanted the overscroll but having mixed bothered me.
Sent from my SGH-i777
shishir95 said:
Alright this may be Cog4 only... if you want, upload your framework.jar and framework-res.apk and I'll mod it for you and let me know if that works.
Well it's not that pressing of an issue, but maybe I'll send it to you later but right now I'm Dealing with insane iPhone customers, makes me want to hang myself... If 2.3.5 is gonna be coming sometime soon I wouldn't care about the wait.
Anyone know about 2.3.5 ota eta?
Sent from illaphone.
Click to expand...
Click to collapse
illathanyours said:
shishir95 said:
Alright this may be Cog4 only... if you want, upload your framework.jar and framework-res.apk and I'll mod it for you and let me know if that works.
Well it's not that pressing of an issue, but maybe I'll send it to you later but right now I'm Dealing with insane iPhone customers, makes me want to hang myself... If 2.3.5 is gonna be coming sometime soon I wouldn't care about the wait.
Anyone know about 2.3.5 ota eta?
Sent from illaphone.
Click to expand...
Click to collapse
There's a leaked 2.3.5 ROM for the i777 but personally I'm using designgear's Perception which is a port of a i9100 ROM and it works perfectly. I'd recommend the latter since leaked ROMs tend to have problems.
Click to expand...
Click to collapse
could you modify the framework.jar for UnNamed v1.0.1 - First ever well documented and open source stock derived rom? It has the extended power menu and if I overwrite the framework.jar using this it will break that extended power menu. Much thanks for getting the overscroll glow!!
Skyler2Dope said:
could you modify the framework.jar for UnNamed v1.0.1 - First ever well documented and open source stock derived rom? It has the extended power menu and if I overwrite the framework.jar using this it will break that extended power menu. Much thanks for getting the overscroll glow!!
Click to expand...
Click to collapse
I'll give it a try if there's enough demand for it.
shishir95 said:
I'll give it a try if there's enough demand for it.
Click to expand...
Click to collapse
+1 here
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
Hey Guys,
I have been attempting to mod my framework-res.apk to try and add a percent battery icon (unsuccessfuly so far). Here is my issue, after finding that my modded framework file isnt working properly, I go to try and restore the original. After restoring the original I still get tons of FC's and the only way to get things back to normal is to restore my backup from CWM.
The method I am using to replace my framework-res.apk is to use a root explorer (ES File Manager) to copy the file to /system/ then from there I modify the permissions and then move the file to the framework folder, overwriting the existing file. After this, I reboot the phone.
My question is, why is my original framework-res.apk file causing force closes? It is starting to make me think that even my modded files are ok, but that the issue is arising in the manual transfer.
Sorry if the answer is posted elsewhere, I googled and was only finding issues with the apk not being compiled correctly, but that shouldnt be an issue with the original apk.
*EDIT* I figured it out. It appears it was because Jkay Deluxe was installed. I decided to reflash the rom and try with a fresh copy of the framework-res.apk and everything appears to be working now.
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.
Took me hours of reading to figure out something extremely simple. But, hopefully this will save some of the smart people here from having to expend energy belittliing retarded noobs like me.
When I flashed to SHOstock's ICS 2.2.6 I missed the droid animation he had with his GB 1.9.4. So I went searching on how to change it back.
It's pretty simple. All you have to do is.....
1. Get a file explorer with root access. I use ES File Explorer
2. Download any of the custom ROMs in GSII Development
3. Unzip the ROM, open System>media folder. Find the bootanimation zip file and copy that to a folder of your choice on your phone.
4. On your phone, open your file explorer and allow it root folder read/write access
5. Navigate to System>media folder and backup the original bootanimation zip, in case you ever want to replace it.
6. Navigate back to where you put the custom bootanimation zip and copy and replace that zip into the media folder on your phone.
You're done.
If there was audio to the bootanimation it's the same copy and paste process. The .wav file should be located in System>etc. It's named "PowerOn". Once you move that over you may have to change the file permissions to RW--R--R.
To change permissions in ES File Explorer you long press the icon. It'll pull up an "Operations" drop down. Scroll to "Properties". Click "Change". Then make sure User: read/write is checked. Group: read. Other: read Then click ok.
If the sound doesn't work you may have to rename the PowerOn.wav to "PowerOn.ogg"
I'll try and answer any questions you may have but keep in mind i've only had this phone for less than two weeks. I've been lurking and studying on XDA for even less. But i'll do my best.
Remember, before asking questions, searching/reading the forums is your best option. I'm still a total novice but because of this wonderful place i've managed to root my phone, installed several different kernels and themes and flashed two different ROMS
You can also put the bootanimation.zip file in data/local. This way you will preserve your stock bootanimation file.
Sent from my SGH-I777
Hey I'm not sure if this is recommended but I didn't see any instructions specifically for disabling the bootsound. I did find the location of it in this post so I just removed it and my phone stopped making noises when it boot up. I'll report back if any weird issues start happening.
JohnnyKushi said:
Hey I'm not sure if this is recommended but I didn't see any instructions specifically for disabling the bootsound. I did find the location of it in this post so I just removed it and my phone stopped making noises when it boot up. I'll report back if any weird issues start happening.
Click to expand...
Click to collapse
Should be ok. Because if the animation didn't have sound to begin with the .wav file wouldn't be there.
Props to chetan_mohanty for the bootanimations.
Most of the links to the ba's are down but the MassEffect one is still active.
MassEffect - http://depositfiles.com/files/f461b8tt3
Video:-
http://www.youtube.com/watch?v=-W2jWIHSODw
You can thank him here or see his other animations.....
http://forum.xda-developers.com/showpost.php?p=20673303&postcount=1