Alright, just got my hands on a system dump courtesy of loglud so I will be posting files (text files will include content that peaked my interest) here so me and other devs can see what we are able to toy with.
systemdump download link: http://dl.dropbox.com/u/15069134/SystemDump.zip
Current list:
/system/media/bnapps_icons\ <-- we can mod the app icons that come with the device so we can make it less-sucky.
/system/etc/bluetooth/blacklist.conf <-- referencing the bluetooth chip meaning we just have to find a way to activate it
/system/app/settings.apk <-- anyone think they can actually replace this with another gingerbread apk or decompile and discover if there is a custom intent? Warning: It does NOT work at all. I suggest against swapping the apk's out as it causes a force close.
/system/bin/bootanimation *Was told where it searches for bootanimations first so goto this thread for a new bootanimation: http://forum.xda-developers.com/showthread.php?t=1361735
Indirect said:
Alright, just got my hands on a system dump courtesy of loglud so I will be posting files (text files will include content that peaked my interest) here so me and other devs can see what we are able to toy with.
Current list:
/system/media/bnapps_icons\ <-- we can mod the app icons that come with the device so we can make it less-sucky.
/system/etc/bluetooth/blacklist.conf <-- referencing the bluetooth chip meaning we just have to find a way to activate it
/system/app/settings.apk <-- anyone think they can actually replace this with another gingerbread apk or decompile and discover if there is a custom intent?
Click to expand...
Click to collapse
Nice finds. Bluetooth will be intesting to test (about to do it right now).
As you know the Nook has a heavily modified framework, so I don't know if the stock settings app will work (but I'm about to find out and probably fark up my tablet).
Let me know how it goes anlog.
Indirect said:
/system/app/settings.apk <-- anyone think they can actually replace this with another gingerbread apk or decompile and discover if there is a custom intent?
Click to expand...
Click to collapse
Hmm . . . let me get a hold of it and I'll look at it tomorrow, I've already taken the rest of the week off (Diablo III beta key came in tonight).
You may not need to change out the settings.apk but just add another one to it.
I decided to hold off on swapping the settings.apk. Losing access to the real settings app with all of the Nook options might not be a good idea.
The main reason I wanted a full settings menu was to be able to get into the accounts sync settings, but I found an app to launch it.
Warning: It does NOT work at all. I suggest against swapping the apk's out as it causes a force close.
Indirect said:
A
/system/bin/bootanimation <-- It's not a .zip or anything, just a file...anyone know how we can edit this?
Click to expand...
Click to collapse
It's a binary file. This app executes bootanimation resources.
Example: on T-Mobile MyTouch 4G resources are in /system/customize//resource/htc_bootanimation.zip
You should search for bootanimation.zip and you can edit this archive
Indirect said:
Warning: It does NOT work at all. I suggest against swapping the apk's out as it causes a force close.
Click to expand...
Click to collapse
I read note, if you want edit system apps like Settings.apk you should sign them by personal keys only...
I was looking through and couldnt find a bootanimation.zip in the system so I'm checking the data folders now.
edit: What the hell, still can't find it.
Indirect said:
I was looking through and couldnt find a bootanimation.zip in the system so I'm checking the data folders now.
edit: What the hell, still can't find it.
Click to expand...
Click to collapse
I was using Absolite system to see if I could replace the bootanimation because I couldn't find it either. I did manage to make it go away and just had the splash screen. I'll look into this further today as well. I'm starting to get ideas as to which files you can and can't replace right now. Some will force an immediate reboot and get stuck in a boot loop. I also am trying to find what triggers and handles the home button menu, I am sure it is in the framework. I have framework.jar and services.jar decompiled and going through those as well. Reviewing logcats to see what I can track down. I have some other interesting stuff going as well
romified said:
I was using Absolite system to see if I could replace the bootanimation because I couldn't find it either.
Click to expand...
Click to collapse
Hmmm... Usually bootanimation is in /data/local/ or /system/media. May be it has different name?
/system/bin/bootanimation is the program that actually displays the bootanimation.
Normally it plays the contents of /system/media/bootanimation.zip, but it can also be hardcoded to play a fixed animation or designed to play a completely different format. (Such as on Samsung devices, where it only plays Samsung's QMG format until you replace the program.)
conundrum768 said:
I've already taken the rest of the week off (Diablo III beta key came in tonight).
Click to expand...
Click to collapse
conundrum768
Don't take this the wrong way, but I really hate you right now!
I tried getting in on the Diablo III beta, no luck!
Here is a file of some interest, it it looks to be encrypted because it would be of interest.
/system/recovery-from-boot.p
.p files are encrypted .m files. Not sure if anything exists out there to crack into that one, but I am sure it would tell some very interesting information and possibly allow hi-jacking the factory restore process?
Anyone familiar with .p files (pcode files) ?
---------- Post added at 12:20 PM ---------- Previous post was at 12:08 PM ----------
Also of interest are some .xem3 files under /system/lib/ducati
base_image_app_m3.xem3 --- 57 mb
base_image_sys_m3.xem3 --- 1.5 mb
I think could be system image files possibly from the little bit of research I have done. Due to the size of one of these (57 mb) and the name of the file, I was thinking maybe this is where the restore was getting it's base image from, but until I dig further I am not sure of that. The size of the file is what got my attention, much larger than other files in lib. That's half the size of CM7 in just one file.
Edit: These now look to be possibly drivers/firmware/images for Ducati and/or Pandaboard ? That's a large driver file....
The .p file is very much of interest I would think.
conundrum768 said:
Hmm . . . let me get a hold of it and I'll look at it tomorrow, I've already taken the rest of the week off (Diablo III beta key came in tonight).
Click to expand...
Click to collapse
It looks like the normal XML files are not controlling the layout and it is done through the smali files to get the custom actions and layout. A separate app to access development may be best for now, as we have been doing.
Unless someone edits the smali files of course, that's possible but will prove tedious and time consuming unless you have a lot of experience with these.
If you review the logcats from going into settings, you will see which smali files are involved.
I have almost a full system dump on an ftp so ill see about letting it be accessed.
Sent by breaking the sound barrier
Please upload full system dump from Nook Tablet
Please upload full system dump from Nook Tablet
How-to
1. Get root
2. Run terminal (enter su if symbol $ -> it will be changed to #)
3. Execute command mount
4. From list of partitions search for /system
Code:
Example: /dev/block/mmcblk0p27 /system ext4 ro,relatime
5. Dump it to sdcard with command dd
Code:
Example: dd if=/dev/block/mmcblk0p27 of=/sdcard/system.img
It dumps only system image not personal data...
I'll just upload a .zip to dropbox.
Is there a sanim.zip anywhere? If so, that's the bootani. If not, ill sink back to silence lol
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
I looked through and there are only a few .zip files but none of them actually contained a bootanimation. It really is annoying lol. This device is such a bastardized version of android, I can't wait to get past the bootloader. lol.
Related
It's not much, but I thought everyone should be able to theme their Legend
Requirements: WinZip(or any other zipping program), Android SDK, testsign, some graphics editor...
So what you need to start with is your framework files:
framework-res.apk, com.htc.resources.apk ... both are located in SYSTEM:framework/
These files are just renamed zip files, so rename them back to .zip and extract them (you can also edit them inside WINRAR or something, but it is more comfortable if you extract them)
In these, images are usually saved in res/drawable-mdpi or such, but you have to think here, allways modify all files from one resource
Now locate the images you want to edit but I only know how to edit .png files (.9.png files are for a different howto, probably not by me as I've never really mastered it)
Pick those you want to edit, and edit them (I'm not gonna tell you how here, I usually use photoshop to do that )
Once you have edited those images, it is recomended to optimize those png's (Firstly to make them smaller, but more importantly, most of the times the png's from Windows graphics editor didn't work for me...)
To optimize png's you can use:
OptiPNG: DOWNLOAD This one is drag'n'drop batch conversion capable...
Pngcrush: DOWNLOAD Command line utility, but it has more settings
...or something else, but I find these two the best
Once you have these optimized, copy and re-write them to folders you took them from to edit...
Now you need to zip these back, for framework files I was told it is usual to zip them as "store", but correct me someone if I'm wrong.
After you have zipped those, they will have to be re-signed. To do this, use testsign from code.google.com
Then run this in cmd line (or create a .bat file as I did, it's much easier):
Code:
java -classpath testsign.jar testsign [COLOR="DarkRed"]file.zip[/COLOR] [COLOR="DarkRed"]file-signed.zip[/COLOR]
Now that you have signed it, it is recomended to zipalign it:
(zipalign.exe is located in /tools in your SDK)
Run this in cmd line:
Code:
zipalign 4 [COLOR="DarkRed"]infile.zip[/COLOR] [COLOR="DarkRed"]outfile.zip[/COLOR]
(4 is alignment in bytes)
Now that you have aligned the .zip, rename it to the original name and then you just need to push it back to your phone:
Code:
adb shell mount /system
adb push [COLOR="DarkRed"]com.htc.resources.apk[/COLOR] /system/framework/[COLOR="DarkRed"]com.htc.resources.apk[/COLOR]
or
adb push [COLOR="DarkRed"]framework-res.apk[/COLOR] /system/framework/[COLOR="DarkRed"]framework-res.apk[/COLOR]
And you're done
I hope this helps someone! Enjoy!
note: This way you should be able to modify any apk I think
Is this the thing that has the potential to break the power menu in BlaY0's ROM, among other things?
Amongst other things...but this works on any ROM as long as you follow the guide I've succesfully ported my BattMod and Cryshop's navbar/lockscreen to B0.8 while doing these exact steps
Dr.Romca said:
Amongst other things...but this works on any ROM as long as you follow the guide I've succesfully ported my BattMod and Cryshop's navbar/lockscreen to B0.8 while doing these exact steps
Click to expand...
Click to collapse
can you post them?
stegg said:
can you post them?
Click to expand...
Click to collapse
Why? He gave you quite simple instructions on how to construct it yourself, so he wouldn't need to do that for every single release for any of you.
Sent from my HTC Legend
Right on I think it's simple enough...besides, I had to figure this all out myself...
It's nice when people use that round head sitting on their neck
BlaY0 said:
Why? He gave you quite simple instructions on how to construct it yourself, so he wouldn't need to do that for every single release for any of you.
Sent from my HTC Legend
Click to expand...
Click to collapse
you have some personality disorder, you'd better see someone specialised in mental health care
stegg said:
you have some personality disorder, you'd better see someone specialised in mental health care
Click to expand...
Click to collapse
I will do that as soon as you contribute at least one theme for three different roms and then supply new updates for every new release of those roms...
Sent from my HTC Legend
stegg said:
you have some personality disorder, you'd better see someone specialised in mental health care
Click to expand...
Click to collapse
Oh come on stegg, that was uncalled for I just think it's a better idea to share how I did it rather then do all the work for you. Hell it would be a full time job - making themes for everyone
...too bad there isn't a "what the hell?" button ...
Question ; are there any limitations to what you can port like different functioning slide bar / nav bar?
Sent from my HTC Legend using XDA Premium App
This howto only tells you how to replace png's inside those framework .apk packages. And you can change navbar as well, but you'd have to make it in the same shape as long as you don't want to decompile the apk...
Cool thanks, I'm giving this a go now
Sent from my HTC Legend using XDA Premium App
I guess my device has to be rooted to do this?
You are correct, sir
Damn...
I was wanting to know if anyone out there knows of a working Boot Screen Animation Changer for the A70/101IT that can successfully change the boot screen without crashing over and over?? It would also be even greater if anyone knows of one that also allows you to download new boot screens within the same app too!?
Lastly, if it really is possible to change the boot screen animation on the A101IT to something different... what is a good site that has them AND what file format ending (like .gif or whatever) should I look for? Also, are all custom boot screens for other Android devices (like Android cell phones) compatible with the A101IT?
spicy_puerto_rican said:
Lastly, if it really is possible to change the boot screen animation on the A101IT to something different... what is a good site that has them AND what file format ending (like .gif or whatever) should I look for? Also, are all custom boot screens for other Android devices (like Android cell phones) compatible with the A101IT?
Click to expand...
Click to collapse
Yes it's possible to change the boot screen animation. See here
And yes most boot screen animations from other devices will work.
http://lmgtfy.com/?q=android+boot+screen+animation
Awesome, thanks a ton! You rock! You're very helpful and informative! Much appreciated.
This is cool thanks. Will this work on the 70 as well . Also, Would you happen to know the dimensions for the images. I doubt that the bootanimations from a phone will have the right size images. If someone knows what size they need to be for the 101 and the 70 that would be some good info.
saprano614 said:
This is cool thanks. Will this work on the 70 as well . Also, Would you happen to know the dimensions for the images. I doubt that the bootanimations from a phone will have the right size images. If someone knows what size they need to be for the 101 and the 70 that would be some good info.
Click to expand...
Click to collapse
Any size smaller than the display size will work. I believe the images are automatically scaled down to fit the screen but not scaled up. Some tests need to be done to find a good size.
This may help http://androidforums.com/htc-droid-eris/56647-boot-animation-gallery.html
wdl1908 said:
Some tests need to be done to find a good size.
Click to expand...
Click to collapse
OK so this works great on the 70. I used 800x480 for the images and they fit perfect.
You 101 users should try 1024x600. this is the resolution of the 101 screen. that is how i came up with the size for my 70 so it should work.
I read somewhere on here the size of pics needed for the A101IT needs to be 1200x1024 for the best quality but i have yet to test those exact dimensions. When I read about it from somewhere in here like 3 other people all confirmed the 1200x1024 dimensions as well.
(It may be the same for the A70IT too but probably not due to the 70 and 101 size difference)?
As a side note, getting bach to the bootscreen animation, how would I go about applying a new bootscreen because I downloaded a new one and thought it would apply itself but didnt, any ideas?
spicy_puerto_rican said:
I read somewhere on here the size of pics needed for the A101IT needs to be 1200x1024 for the best quality but i have yet to test those exact dimensions. When I read about it from somewhere in here like 3 other people all confirmed the 1200x1024 dimensions as well.
(It may be the same for the A70IT too but probably not due to the 70 and 101 size difference)?
Click to expand...
Click to collapse
1200x1024 is the size of the wallpapers the max size of the boot animation should be 1024x600 for A101IT
spicy_puerto_rican said:
As a side note, getting bach to the bootscreen animation, how would I go about applying a new bootscreen because I downloaded a new one and thought it would apply itself but didnt, any ideas?
Click to expand...
Click to collapse
copy bootanimation.zip to /data/customization/
Ahhh, I see! Very much appreciated (wdl1908) for all your help! You know your $hit, thanks!
While searching around I found this site with a lot of boot screen animations http://cid-11d05b676a3170c4.office.live.com/browse.aspx/.Public/Android/bootanimations
Enjoy.
does anyone know if you can add sound to the animation? and if so how?
Here is the bootanimation i made for my 70.Just rename it to bootanimation.zip and paste in the /data/customization folder. (if that folder does not exist then just make it) I have more if you would like them let me know.
To Saprano614, WDL1908, or anyone else....
How do I apply a new custom boot screen animation??
I've tried numerous times putting new bootscreen animations in .zip folders in the /data/customization folder I had to create and I'm confused with how it's supposed to be applied?! Do I put it in the /data/customization folder and reboot... because I've done exactly that, time and time again but I still get nothing and it still loads the same boring factory bootscreen? Do I need to do something different or additional?? = ( Also, do I extract the bootscreen out of the zipped folder and put it in the /data/customization folder or just keep it zipped and copy there?
spicy_puerto_rican said:
To Saprano614, WDL1908, or anyone else....
How do I apply a new custom boot screen animation??
I've tried numerous times putting new bootscreen animations in .zip folders in the /data/customization folder I had to create and I'm confused with how it's supposed to be applied?! Do I put it in the /data/customization folder and reboot... because I've done exactly that, time and time again but I still get nothing and it still loads the same boring factory bootscreen? Do I need to do something different or additional?? = ( Also, do I extract the bootscreen out of the zipped folder and put it in the /data/customization folder or just keep it zipped and copy there?
Click to expand...
Click to collapse
you leave the zip as it is, but you have to edit a line and put a line in
/init.rc
first (in init.rc) undocument
Code:
# export ANDROID_BOOTLOGO 1
to
Code:
export ANDROID_BOOTLOGO 1
then, after this existing lines
Code:
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw
ioprio rt 4
insert ( or in the newer uruk versions, undocument) the lines
Code:
service bootanim /system/bin/bootanimation
user graphics
group system audio graphics
disabled
oneshot
this gives you the animation after message "switching to rootfs" till the homescreen appears
its also possible to remove the urukdroid logo, but therefore initramfs.cpio.gz has to be edited
(/etc/scripts/init_lib.sh in initramfs)
the second part of uruk animation is in
/system/bin/show_logo.sh
it also can be deactivated by editing the file (but do not delete it, because its used for other things too)
I use the app su file manager & terminal. Conect you tab to your pc paste the bootanimation.zip to the root of your sdcard. Then unplug the usb. Then with su file manager or another superuser permited file browser copy thr bootanimation.zip and then browse to the /data/customization folder. Make sure that it is in the correct /data folder. There is one on the sdcard and one on the device. if u use the file browser I do then hit back button till it asks if you want to exit but hit cancel. Then look for the Data file. That is the one you need. Then reboot. Again must be in the /data/customization folder not the /sdcard/data/customization folder.
woti23 said:
you leave the zip as it is, but you have to edit a line and put a line in
/init.rc
first (in init.rc) undocument
Code:
# export ANDROID_BOOTLOGO 1
to
Code:
export ANDROID_BOOTLOGO 1
then, after this existing lines
Code:
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw
ioprio rt 4
insert ( or in the newer uruk versions, undocument) the lines
Code:
service bootanim /system/bin/bootanimation
user graphics
group system audio graphics
disabled
oneshot
this gives you the animation after message "switching to rootfs" till the homescreen appears
its also possible to remove the urukdroid logo, but therefore initramfs.cpio.gz has to be edited
(/etc/scripts/init_lib.sh in initramfs)
the second part of uruk animation is in
/system/bin/show_logo.sh
it also can be deactivated by editing the file (but do not delete it, because its used for other things too)
Click to expand...
Click to collapse
Ok this is only needed if you are using uruk. If have rooted using churli's method then my above instructions are all yoi need.
saprano614 said:
I use the app su file manager & terminal. Conect you tab to your pc paste the bootanimation.zip to the root of your sdcard. Then unplug the usb. Then with su file manager or another superuser permited file browser copy thr bootanimation.zip and then browse to the /data/customization folder. Make sure that it is in the correct /data folder. There is one on the sdcard and one on the device. if u use the file browser I do then hit back button till it asks if you want to exit but hit cancel. Then look for the Data file. That is the one you need. Then reboot. Again must be in the /data/customization folder not the /sdcard/data/customization folder.
Click to expand...
Click to collapse
i followed these instrustions yet i still cant get the animation to work im new to all of this but i have done well with my evo lol it cooperates much better than this 101 does though lol please help.
you have root? make sure to copy the .zip file to the /data/customization folder. also it must be named bootanimation.
I did this as well but still no boot screen I'm wondering if the kernel I'm using doesn't support custom boot animations PR if that has anything to do with it at all
Sent from my PC36100 using XDA Premium App
dalton1091 said:
I did this as well but still no boot screen I'm wondering if the kernel I'm using doesn't support custom boot animations PR if that has anything to do with it at all
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
nothing to do with the kernel, you must edit the /init.rc and enable the bootanimation, as written above
Okay so I've spent about 2 days tweaking my stock deodexed Rom to my liking and It's super fast and responsive. Faster scrolling and speed hacks. Quadrants in the 2000s. And much more. How do I take this Rom and zip it so other people can flash it if they want?
Sent from my Beastly EVO.. And did I mention it has 3D?
youngpro83 said:
Okay so I've spent about 2 days tweaking my stock deodexed Rom to my liking and It's super fast and responsive. Faster scrolling and speed hacks. Quadrants in the 2000s. And much more. How do I take this Rom and zip it so other people can flash it if they want?
Sent from my Beastly EVO.. And did I mention it has 3D?
Click to expand...
Click to collapse
packaging up a ROM is fairly simple.
for a ROM .zip there are a few main components:
1) *required* /system directory (contains all your ROM files)
2) *required* META-INF/com/google/android/ with two files, updater-script and update-binary. updater-script file instructs the update-binary on how to process/install your ROM. the custom recovery will look for these two files and execute them.
3) *optional* a kernel in the .zip to be flashed
hope that helps! good luck on publishing your ROM!
joeykrim said:
packaging up a ROM is fairly simple.
for a ROM .zip there are a few main components:
1) *required* /system directory (contains all your ROM files)
2) *required* META-INF/com/google/android/ with two files, updater-script and update-binary. updater-script file instructs the update-binary on how to process/install your ROM. the custom recovery will look for these two files and execute them.
3) *optional* a kernel in the .zip to be flashed
hope that helps! good luck on publishing your ROM!
Click to expand...
Click to collapse
So could I just take a ROM and just change certain files and apps? And how do you make the Rom do cool stuff while flashing like spell your Rom name while it flashes? Sorry for all the questions but I appreciate ur help.
Sent from my Beastly EVO.. And did I mention it has 3D?
youngpro83 said:
So could I just take a ROM and just change certain files and apps? And how do you make the Rom do cool stuff while flashing like spell your Rom name while it flashes? Sorry for all the questions but I appreciate ur help.
Sent from my Beastly EVO.. And did I mention it has 3D?
Click to expand...
Click to collapse
Usually, at least from what I know...
The more In depth stuff is done with the ROM Kitchen through a computer!
youngpro83 said:
So could I just take a ROM and just change certain files and apps? And how do you make the Rom do cool stuff while flashing like spell your Rom name while it flashes? Sorry for all the questions but I appreciate ur help.
Sent from my Beastly EVO.. And did I mention it has 3D?
Click to expand...
Click to collapse
yes, you could take a ROM and only replace certain files / apps with the ones you've modified.
the ROM "cool stuff" while it flashes is all done in the updater-script file i mentioned in #2 of the required ROM files in my previous post above.
the ROM I maintan and publish for EVO 3D is 100% stock with root/su binary added, busybox and a bunch of linux arm developer binaries in /system/xbin.
my stock ROM would be a great base for you to start modifying and experimenting with!
1) swap out the apk/files in the .zip with the ones you've modified.
2) modify the updater-script file with your syntax
3) let us know how it goes!
[ROM] joeykrim-original-1.2.0 Odex *Stock Rooted 2.08.651.2* Aug 21st 2011
on windows, 7zip is a great GUI application for swap/editing files inside a .zip without having to extract the whole thing.
on linux, i'd just unzip the whole .zip to a directory and then swap out the files/edit the files in that directory, then zip up. also, i think ubuntu archive manager (default GUI for .zip files) lets you modify/edit files inside the .zip without having to extract the whole thing.
hope that helps!
joeykrim said:
yes, you could take a ROM and only replace certain files / apps with the ones you've modified.
the ROM "cool stuff" while it flashes is all done in the updater-script file i mentioned in #2 of the required ROM files in my previous post above.
the ROM I maintan and publish for EVO 3D is 100% stock with root/su binary added, busybox and a bunch of linux arm developer binaries in /system/xbin.
my stock ROM would be a great base for you to start modifying and experimenting with!
1) swap out the apk/files in the .zip with the ones you've modified.
2) modify the updater-script file with your syntax
3) let us know how it goes!
[ROM] joeykrim-original-1.2.0 Odex *Stock Rooted 2.08.651.2* Aug 21st 2011
on windows, 7zip is a great GUI application for swap/editing files inside a .zip without having to extract the whole thing.
on linux, i'd just unzip the whole .zip to a directory and then swap out the files/edit the files in that directory, then zip up. also, i think ubuntu archive manager (default GUI for .zip files) lets you modify/edit files inside the .zip without having to extract the whole thing.
hope that helps!
Click to expand...
Click to collapse
Thanks a lot. So ill experiment with ur base. What is syntax?
Sent from my Beastly EVO.. And did I mention it has 3D?
youngpro83 said:
Thanks a lot. So ill experiment with ur base. What is syntax?
Sent from my Beastly EVO.. And did I mention it has 3D?
Click to expand...
Click to collapse
fancy word i used in place of code/text. you can open the updater-script inside of the .zip file with a text editor. the updater-script file uses the edify scripting language.
there are a lot of guides on how to use edify and what each phrase means. google the terms, "edify android guide" and there should be a bunch of results. one of the results which looks fairly decent - Edify Script Syntax Explained
hope that helps! good luck!
youngpro83 said:
Okay so I've spent about 2 days tweaking my stock deodexed Rom to my liking and It's super fast and responsive. Faster scrolling and speed hacks. Quadrants in the 2000s. And much more. How do I take this Rom and zip it so other people can flash it if they want?
Sent from my Beastly EVO.. And did I mention it has 3D?
Click to expand...
Click to collapse
Cool man! Good luck! Hope to see ya on the dev page.
Sent from my SPH-P100 using xda premium
Alright so progress is being made and its going very well. Only things Im stuck on now is:
1. How do I add certain apps like astro or ES file explorer WITHOUT putting them into the system/apps folder??
2. How do I change the background at boot so that its not the colorful flares that Sprint has on there.
3. How do I remove the 3D apps game apk?
Once I have those figured out I think my ROM will be ready for the public.
youngpro83 said:
Alright so progress is being made and its going very well. Only things Im stuck on now is:
1. How do I add certain apps like astro or ES file explorer WITHOUT putting them into the system/apps folder??
2. How do I change the background at boot so that its not the colorful flares that Sprint has on there.
3. How do I remove the 3D apps game apk?
Once I have those figured out I think my ROM will be ready for the public.
Click to expand...
Click to collapse
1. android package manager monitors two locations for .apk files and will install them as soon as they appear in these two directories: /system/app and /data/app. if you want your rom to install .apk files to /data/app, you'll need to add the package_extract_dir command to your updater-script for /data and also create a data/app directory in the ROM zip file and put whatever apk files you want added in the data/app dir of the ROM zip file.
2. For Android boot animations the system looks in 3 locations in this order. 1) /data/local/bootanimation.zip, 2) /system/media/bootanimation.zip and 3) framework-res.apk . Since there are no bootanimation.zip files on our device, I'm assuming the sprint boot animation is stored in the framework-res.apk file. No worries, as placing any bootanimation file in either /data/local or /system/media will take priority over the Sprint animation in framework-res.apk.
3. 3D Games apk file is located here: /system/app/PGAWidget_HTCEvo3D_Sprint_v100.apk . Simply remove that apk file from /system/app inside the ROM .zip and it will not be loaded.
Let us know if you have any other questions. Hope that helps and good luck in the publishing!
joeykrim said:
1. android package manager monitors two locations for .apk files and will install them as soon as they appear in these two directories: /system/app and /data/app. if you want your rom to install .apk files to /data/app, you'll need to add the package_extract_dir command to your updater-script for /data and also create a data/app directory in the ROM zip file and put whatever apk files you want added in the data/app dir of the ROM zip file.
2. For Android boot animations the system looks in 3 locations in this order. 1) /data/local/bootanimation.zip, 2) /system/media/bootanimation.zip and 3) framework-res.apk . Since there are no bootanimation.zip files on our device, I'm assuming the sprint boot animation is stored in the framework-res.apk file. No worries, as placing any bootanimation file in either /data/local or /system/media will take priority over the Sprint animation in framework-res.apk.
3. 3D Games apk file is located here: /system/app/PGAWidget_HTCEvo3D_Sprint_v100.apk . Simply remove that apk file from /system/app inside the ROM .zip and it will not be loaded.
Let us know if you have any other questions. Hope that helps and good luck in the publishing!
Click to expand...
Click to collapse
Man you are the BOMB.COM!!!!
And for 2. I wasnt looking to replace the boot animation. I kinda like the Sprint one. I was trying to replace the actual wallpaper that the phone boots into. So at the home screen I can have my own wallpaper that I choose for my ROM.
Also for 1. Do I need to create a unmount script like the one for /system? Or do I just add the script you mentioned and that is it?
Thanks so much for your help man. I dont think I would have gotten this far without you!!
youngpro83 said:
Man you are the BOMB.COM!!!!
And for 2. I wasnt looking to replace the boot animation. I kinda like the Sprint one. I was trying to replace the actual wallpaper that the phone boots into. So at the home screen I can have my own wallpaper that I choose for my ROM.
Also for 1. Do I need to create a unmount script like the one for /system? Or do I just add the script you mentioned and that is it?
Thanks so much for your help man. I dont think I would have gotten this far without you!!
Click to expand...
Click to collapse
Oh, I misunderstood for 2. For the actual wallpaper .. I did a few quick google searches and haven't come up with anything super helpful. Based on this blog post Appears there are two possible locations for the default wallpaper images to be stored, either in the Launcher.apk or in /system/frameworks/framework.jar. Unfortunately, I'm not able to experiment on the device and search more thoroughly. If nobody posts back a better answer I'll look into this tonight.
1. Yea, it would be best practice to mount data, package extract dir /data and then unmount data. You should be able to copy the mount/unmount commands used for system and change the mount points to data and for the mount command change the device point for data .. off the top of my head I think its one number higher, but not positive. cat /proc/partitions to see the exact device mount point.
Hope that helps!
joeykrim said:
Oh, I misunderstood for 2. For the actual wallpaper .. I did a few quick google searches and haven't come up with anything super helpful. Based on this blog post Appears there are two possible locations for the default wallpaper images to be stored, either in the Launcher.apk or in /system/frameworks/framework.jar. Unfortunately, I'm not able to experiment on the device and search more thoroughly. If nobody posts back a better answer I'll look into this tonight.
1. Yea, it would be best practice to mount data, package extract dir /data and then unmount data. You should be able to copy the mount/unmount commands used for system and change the mount points to data and for the mount command change the device point for data .. off the top of my head I think its one number higher, but not positive. cat /proc/partitions to see the exact device mount point.
Hope that helps!
Click to expand...
Click to collapse
Helps a bunch!!! I will have to dig deeper because I tried flashing after creating those scripts and I got error 6 when trying to flash. Ill add the mount/unmount commands and see if that fixes it.
youngpro83 said:
Helps a bunch!!! I will have to dig deeper because I tried flashing after creating those scripts and I got error 6 when trying to flash. Ill add the mount/unmount commands and see if that fixes it.
Click to expand...
Click to collapse
To debug flashing errors while in the recovery, open adb shell and type:
Code:
cat /tmp/recovery.log
The recovery log has more details and usually the exact line of code where it failed. Feel free to paste this into pastebin and link up here, or paste into the thread and we can help troubleshoot.
Another step deeper into troubleshooting and debugging land of ROM development! Hope that helps!
Joeykrim, learned more from this thread then searching chefs central..
life64x said:
Joeykrim, learned more from this thread then searching chefs central..
Click to expand...
Click to collapse
I Agree... This Thread could be on its way to being a little STICKY, Lol!
Nah but Good Thread guys!
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
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.