Related
Does anyone know where I can find a copy of this? I've done a search and all I can find is one from the international version and that's based on the 2.3.1 build.
TIA
check here http://forum.xda-developers.com/showthread.php?t=1286432
daraj said:
check here http://forum.xda-developers.com/showthread.php?t=1286432
Click to expand...
Click to collapse
Nothing there about stock system dump.
BigBolo said:
Does anyone know where I can find a copy of this? I've done a search and all I can find is one from the international version and that's based on the 2.3.1 build.
TIA
Click to expand...
Click to collapse
Entropy512 started with a stock system dump that someone, (maybe Jivy26), made after installing a custom kernel. But I don't remember he ever posted a link to it. He may still have it hanging around, though. That's what he used to make his stock plus root package.
BigBolo said:
Nothing there about stock system dump.
Click to expand...
Click to collapse
Um, what do you think a flashable stock system image is? (Other than being a sparse ext4 image, if you want something loop-mountable use simg2img...)
Seriously - spend just a LITTLE more time reading before you post in a Development thread. This device has been out for only 2 weeks so it's not like the Dev forum has tons of threads.
There's also a dd-derived system dump in page 5 of codeworkx's CWM kernel thread. I used jivy26's tar dump, although I should probably do a consistency check against seattleboi1982's dump.
Entropy512 said:
Um, what do you think a flashable stock system image is? (Other than being a sparse ext4 image, if you want something loop-mountable use simg2img...)
Seriously - spend just a LITTLE more time reading before you post in a Development thread. This device has been out for only 2 weeks so it's not like the Dev forum has tons of threads.
There's also a dd-derived system dump in page 5 of codeworkx's CWM kernel thread. I used jivy26's tar dump, although I should probably do a consistency check against seattleboi1982's dump.
Click to expand...
Click to collapse
I'm actually looking for the system dump in a zip where I can extract it into folders. Not as a image. I want to basically get the media files. I did do a search in several forums trying to find it but came up with nothing.
Maybe I should of been more detailed and specific in my OP.
BigBolo said:
I'm actually looking for the system dump in a zip where I can extract it into folders. Not as a image. I want to basically get the media files. I did do a search in several forums trying to find it but came up with nothing.
Click to expand...
Click to collapse
Can't you just extract the stock system image?
eep2378 said:
Can't you just extract the stock system image?
Click to expand...
Click to collapse
I don't know how to do that...
Then you probably don't belong in android development (yet).
Use 7zip to extract the zip/tar/whatever.
In general, you're not supposed to put requests in Development. This should have been posted in General.
And a stock system dump IS an image dump. Zip files don't preserve permissions, and tar files only do if you prepared them carefully (good thing jivy26 did). The only way to be sure is to dd the partition.
If you want a nice easy to use zip, use paylyhoffman's stock deodexed CWM zip.
Entropy512 said:
In general, you're not supposed to put requests in Development. This should have been posted in General.
And a stock system dump IS an image dump. Zip files don't preserve permissions, and tar files only do if you prepared them carefully (good thing jivy26 did). The only way to be sure is to dd the partition.
If you want a nice easy to use zip, use paylyhoffman's stock deodexed CWM zip.
Click to expand...
Click to collapse
Thanks for clearing it up. My bad I thought this was the section to post requests like that.
Also folks before jumping on the guy, what he is asking for (at least with the .7z file posted) isn't as straightforward as everyone thinks.
If you first extract the 7z file, you'll get a PDA.tar file. Extract that and you'll get the kernel (zImage) and the lovely factoryfs.img.
Try extracting factoryfs.img with your favorite tools and see what happens.
Extracting the factoryfs.img is a real pain unless you are pretty hardcore -- in fact, there was another thread going on the in international SGS II forum with some pretty well known devs (who know their stuff) trying to figure out how to extract that bad boy.
So before everyone starts throwing rocks...you know the story.
Does this look easy to you?
http://forum.xda-developers.com/showthread.php?t=1054836 (relevant discussion starts around post #7)
and another solution (which also is not as simple as "right-click and extract")
http://forum.xda-developers.com/showthread.php?t=1081239
Now -- with that said, if one was really looking for an easy way to pull some media files from a ROM, you best bet would be to try and find a CWM flashable ROM (in a zip format) and do a regular extract on those, and you may find it much easier. They may not be stock, but if it's close, you may get lucky and find some of the stock media in them.
pinoymutt said:
Also folks before jumping on the guy, what he is asking for (at least with the .7z file posted) isn't as straightforward as everyone thinks.
If you first extract the 7z file, you'll get a PDA.tar file. Extract that and you'll get the kernel (zImage) and the lovely factoryfs.img.
Try extracting factoryfs.img with your favorite tools and see what happens.
Extracting the factoryfs.img is a real pain unless you are pretty hardcore -- in fact, there was another thread going on the in international SGS II forum with some pretty well known devs (who know their stuff) trying to figure out how to extract that bad boy.
So before everyone starts throwing rocks...you know the story.
Does this look easy to you?
http://forum.xda-developers.com/showthread.php?t=1054836 (relevant discussion starts around post #7)
and another solution (which also is not as simple as "right-click and extract")
http://forum.xda-developers.com/showthread.php?t=1081239
Now -- with that said, if one was really looking for an easy way to pull some media files from a ROM, you best bet would be to try and find a CWM flashable ROM (in a zip format) and do a regular extract on those, and you may find it much easier. They may not be stock, but if it's close, you may get lucky and find some of the stock media in them.
Click to expand...
Click to collapse
Thanks for clarifying that pinoymutt. Yea basically I know a lot of people don't like the finished charging notification but I don't mind it and I figured it's as simple as just placing the ogg file back in the ui folder. I'm on DG's Cog X2 and he had removed that.
BigBolo said:
Thanks for clarifying that pinoymutt. Yea basically I know a lot of people don't like the finished charging notification but I don't mind it and I figured it's as simple as just placing the ogg file back in the ui folder. I'm on DG's Cog X2 and he had removed that.
Click to expand...
Click to collapse
Doubt it's that simple. I removed the notification by modifying code. I would bet dg did the same.
**Disclaimer**
**I Take NO Responsibility in bricking your device**
For those of you who have a rooted device, ads suck, don't they?
Well here is the most up-to-date HOSTS file to help remove most ads (including ads in games/apps)
Needed:
Rooted Device
Root Explorer (Or another file manager that has /system/ directory access)
Attached hosts File
Step 1: Download and unpack hosts.zip
Step 2: Transfer hosts file to internal memory
Step 3: BACKUP Original hosts file (hosts.backup)
Step 4: Replace new hosts file from internal memory into directory /system/etc/
-Delete original (MAKE SURE THERE IS A BACKUP)
-Copy in new hosts
Step 5: Give full permissions to new hosts file
Step 6: Reboot
If there is any connectivity problems, replace the old hosts file
What this does:
Just like any other hosts file (on your PC), this tells the OS to route any website/ip that fall into a giant list of "ad" domains, to route back to 127.0.0.1 (you)... meaning, when an app/website asks for www.i_am_an_ad.com, instead of getting the ad, it gets a null response from yourself!
If you didn't understand the directions or what this is:
I DO NOT recommend customizing your Prime. I come from a Galaxy S, which you don't need balls to mess with, its nearly unbrickable.. this device..however is.. Do no attempt any messing with the /system/ folder without knowledge!
How does this differ than using an ad block app like Adfree?
Not trying to be a prick ... just curious.
Superguy said:
How does this differ than using an ad block app like Adfree?
Not trying to be a prick ... just curious.
Click to expand...
Click to collapse
no bloat. and can actually be incorporated into a ROM
also, this blocks ads at the source, i dont know how adfree blocks it, but i dont ever use ad-blocking programs, that means they the app can see your traffic..
ide rather some internal script doing the job it does with every bit of data in my phone than some external app.. we all should know about DOLPHIN logging user traffic...
Ad-away is the best app. It dies same thing, just installs a hosts file. Makes it in easy ui, and more noob proof. Also easier to update hosts file.
I like this way too, especially like you mentioned to be included in roms.
Sent from my Galaxy S2
There are multiple apps in the market that do exactly this...but easier.
RussianMenace said:
There are multiple apps in the market that do exactly this...but easier.
Click to expand...
Click to collapse
yes, but said aps, again, cannot be included in roms. this is mainly for custom roms.
personally, i would rather incorporate this into my roms before i flash, then download some app that does it
biggem001 said:
yes, but said aps, again, cannot be included in roms. this is mainly for custom roms.
personally, i would rather incorporate this into my roms before i flash, then download some app that does it
Click to expand...
Click to collapse
I'd rather use an app that updates the host file with the latest ad addresses as they become known rather replacing it manually. But that's just me
Charsher47 said:
I'd rather use an app that updates the host file with the latest ad addresses as they become known rather replacing it manually. But that's just me
Click to expand...
Click to collapse
again.. its for people making roms, mainly.
Ok, even if you bake it into a ROM, which is "what this is for" you would still have to manually update the host file to adapt to new Ad domains....yes?
I'm not trying to crap on your work here, just trying to understand the advantages this has over using a market app, which in itself can be baked into a ROM with developers permission.
yeah, but every release culd have it updated. I know most developers just don't put out one version of the rom and call it a day. Most update there roms at least 2-3 times a month if there is still a need for it.
doeboy1984 said:
yeah, but every release culd have it updated. I know most developers just don't put out one version of the rom and call it a day. Most update there roms at least 2-3 times a month if there is still a need for it.
Click to expand...
Click to collapse
agreed. this just reduces bullcrap 3rd party apps you don't need. roms are updated weekly at the latest, normally (at least in my galaxy s forum). throw in the host file every time and you are set. not some
biggem001 said:
**Disclaimer**
**I Take NO Responsibility in bricking your device**
For those of you who have a rooted device, ads suck, don't they?
Well here is the most up-to-date HOSTS file to help remove most ads (including ads in games/apps)
Needed:
Rooted Device
Root Explorer (Or another file manager that has /system/ directory access)
Attached hosts File
Step 1: Download and unpack hosts.zip
Step 2: Transfer hosts file to internal memory
Step 3: BACKUP Original hosts file (hosts.backup)
Step 4: Replace new hosts file from internal memory into directory /system/etc/
-Delete original (MAKE SURE THERE IS A BACKUP)
-Copy in new hosts
Step 5: Give full permissions to new hosts file
Step 6: Reboot
If there is any connectivity problems, replace the old hosts file
What this does:
Just like any other hosts file (on your PC), this tells the OS to route any website/ip that fall into a giant list of "ad" domains, to route back to 127.0.0.1 (you)... meaning, when an app/website asks for www.i_am_an_ad.com, instead of getting the ad, it gets a null response from yourself!
If you didn't understand the directions or what this is:
I DO NOT recommend customizing your Prime. I come from a Galaxy S, which you don't need balls to mess with, its nearly unbrickable.. this device..however is.. Do no attempt any messing with the /system/ folder without knowledge!
Click to expand...
Click to collapse
Well I thank you for your time and effort... I followed your directions and BAM my prime is adfree...
AdFree is one of the first root apps I downloaded. Just easier as a user and I love blocking ads!
Lock-N-Load said:
AdFree is one of the first root apps I downloaded. Just easier as a user and I love blocking ads!
Click to expand...
Click to collapse
Was just coming in here to say that. Way to beat me to it
Atleast upload a more recent one...
http://www.multiupload.com/SAQUI2FOBH
Lock-N-Load said:
AdFree is one of the first root apps I downloaded. Just easier as a user and I love blocking ads!
Click to expand...
Click to collapse
I use AdAway. There's an updated host almost every day.
Lock-N-Load said:
AdFree is one of the first root apps I downloaded. Just easier as a user and I love blocking ads!
Click to expand...
Click to collapse
Itaintrite said:
I use AdAway. There's an updated host almost every day.
Click to expand...
Click to collapse
yeah, they are great and everything, but that's just one more app you have to run in the background, taking up that much more system resources.
Swiftks said:
yeah, they are great and everything, but that's just one more app you have to run in the background, taking up that much more system resources.
Click to expand...
Click to collapse
i agree, when we start pushing roms out, it'll be much easier to just update the hosts files with the ROMS then installing that app every time you update the rom
biggem001 said:
i agree, when we start pushing roms out, it'll be much easier to just update the hosts files with the ROMS then installing that app every time you update the rom
Click to expand...
Click to collapse
I use adfree and I don't let it run in background and it still works, you only install app again if you update to different ROM, or you must swipe everything every time, but you have to install all of your apps again as well, install one more app won't make a dent to your finger, or you can use Titanium Backup
I'm surprised this hasn't been baked in CM7/8 or the upcoming CM9 yet.
Would be pretty easy to add it in the customize for most any ROM.
Sent from my DROID3 using Tapatalk
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.
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
johnwaynegacy said:
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
Click to expand...
Click to collapse
probably delete the OTA apk files in /system/app
con247 said:
probably delete the OTA apk files in /system/app
Click to expand...
Click to collapse
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
johnwaynegacy said:
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
Click to expand...
Click to collapse
I deleted those from my /system/app directory. The previous OTA did not ever come through my phone, so I think you'll be OK.
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
Good call!
instructions, pls?
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
i just did this on rezrom, thanks!
why is this file included with a custom rom?
michaelbsheldon said:
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
Click to expand...
Click to collapse
If for what ever reason you cant use root explorer and do have busybox (i think you need it) installed
It has been a really long time since I have used adb for anything, but this should work unless it denies you because system is mounted as read only.
adb shell
su
rm /filepath/file.apk
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
FabianaS said:
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
Click to expand...
Click to collapse
If you are stock unrooted, the best you can do is to say no if it asks. If for some reason it is a forced OTA, I don't think you can without staying in airplane mode.
Via Rezound using XDA Premium
Thanks, that is what I was wondering, if it asks or if it's forced? I don't remember how my past updates have been and for some reason I feel like they were forced!?!
This gets asked quite often so I decided to make a guide on how to do this. It's a very simple process and you will need something to either freeze the .apk or something to rename it. You will also need to be rooted.
Freezing:
Titanium Backup
Rom Toolbox
Renaming:
Root Explorer
ES File Explorer
The file you will be freezing/renaming is titled SDM.apk, it is located in the system/app directory. Navigate there and freeze/rename with your app of choice. If you're going the renaming route, rename it to sdm.apk.bak, or anything else you would like as long as you change the file extension. If anyone wants a different application added to list post here or PM me and I will add it. I just listed those because they're some of the popular ones and I have used all of them myself at one time or another.
Hi, is this process make stop any apps updates and update notitfications, because except title you didn't say anything about it?
blackfire74 said:
Hi, is this process make stop any apps updates and update notitfications, because except title you didn't say anything about it?
Click to expand...
Click to collapse
No this is for the ota updates
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free