[Q] Blocking carrier updates? - General Questions and Answers

I see some threads that are exactly what I want, but they are for the Nook and things don't look to match up well enough for me to use those instructions.
I have an Epic4G (GalaxyS) on Sprint, and have recently flashed with Legendary ROM 2.2. Now I'm getting constant update alerts to download the new firmware update from Sprint. At this point, it's already downloaded the update so I need to find where it is and get rid of that file as well.
I've read about the editing the devicemanager.db file, but I am not finding that file in the /data tree. I also read the build.prop thread, but it looks like they want you to grab a pre-built build.prop that's obviously for the nook.
Any help or direction would be greatly appreciated!

NOOOOO update
takendal said:
I see some threads that are exactly what I want, but they are for the Nook and things don't look to match up well enough for me to use those instructions.
I have an Epic4G (GalaxyS) on Sprint, and have recently flashed with Legendary ROM 2.2. Now I'm getting constant update alerts to download the new firmware update from Sprint. At this point, it's already downloaded the update so I need to find where it is and get rid of that file as well.
I've read about the editing the devicemanager.db file, but I am not finding that file in the /data tree. I also read the build.prop thread, but it looks like they want you to grab a pre-built build.prop that's obviously for the nook.
Any help or direction would be greatly appreciated!
Click to expand...
Click to collapse
Try to delete ota apk that is the one asking about the update and delete the file usin root explorer in system/ app
Hope work for you :highfive: remmember to thanks :laugh:

Related

[ROM] Rooted stock 1.47.651.1

Edit: I was looking for a zipped, rooted version of 1.47.651.1 and didn't find it, so I made one and posted it. Turns out I had just missed caulkin's post, so my post is now pretty pointless. If a mod wants to delete the thread, that is fine. I apologize for clogging things up, I was intending to provide a resource to make things easier for other people.
Here is caulkins: http://forum.xda-developers.com/showthread.php?t=712695
#######################################################
I haven't seen a rooted stock of the latest OTA ROM (1.47.651.1) so I made one. I added superuser, busy box, and left everything else the same. I'll probably add a deodexed version and stripped version soon.
odex-1.47.651.1
I'm pretty new to the Android world, but I think no one had put this up yet because it is pretty easy to do, but a pain to upload. Let me know if there are any issues, but in my testing it has been fine, market works, etc. Also, if this is out there, let me know, or delete the thread, but the only post I saw with this had a dead link.
This is just the images from whitslacks expanded into the more familiar zip package like most of the cooked roms are distributed. If you are running whitslacks this would be no different.
Thanks to:
dsixda for the kitchen
whitslack for the one shot image I pulled this out of
community in general
So u rooted the evo with the update?
Sent from my PC36100 using Tapatalk
laydros said:
I haven't seen a rooted stock of the latest OTA ROM (1.47.651.1) so I made one. I added superuser, busy box, and left everything else the same. I'll probably add a deodexed version and stripped version soon.
odex-1.47.651.1
I'm pretty new to the Android world, but I think no one had put this up yet because it is pretty easy to do, but a pain to upload. Let me know if there are any issues, but in my testing it has been fine, market works, etc. Also, if this is out there, let me know, or delete the thread, but the only post I saw with this had a dead link.
Thanks to:
dsixda for the kitchen
whitslack for the one shot image I pulled this out of
community in general
Click to expand...
Click to collapse
Here is whitslacks rooted 1.47 ROM:
http://forum.xda-developers.com/showthread.php?t=715915
Works perfectly, I haven't had any issues with it and I flashed it about 3-4 days ago.
vballboarder said:
Here is whitslacks rooted 1.47 ROM:
http://forum.xda-developers.com/showthread.php?t=715915
Works perfectly, I haven't had any issues with it and I flashed it about 3-4 days ago.
Click to expand...
Click to collapse
Yes, this is actually based on whitslack's. His work may be more useful, but his is a full package that replaces everything (radio, recovery, etc), and requires another flash to root.
This is just a standard rom that can be installed via clockwork or RA and doesn't change any of the other pieces.
More than anything it may be a building block for other roms, especially once I get a deodexed version up.
Caulkin also has a rooted stock Rom as well odex and deodexed in this forum. He was the first to put it out like the day the ota was released
xxbabiboi228xx said:
Caulkin also has a rooted stock Rom as well odex and deodexed in this forum
Click to expand...
Click to collapse
You are right. I looked quite a bit for this, but it didn't get a lot of posts in the last few days so it hasn't been in the top often.
laydros said:
Yes, this is actually based on whitslack's. His work may be more useful, but his is a full package that replaces everything (radio, recovery, etc), and requires another flash to root.
This is just a standard rom that can be installed via clockwork or RA and doesn't change any of the other pieces.
More than anything it may be a building block for other roms, especially once I get a deodexed version up.
Click to expand...
Click to collapse
Okay, I've spent quite a bit of time trying to figure this whole root thing out and I've got a pretty good handle on rooting and flashing ROM, but can't find what's the deal with odexed versus de-odexed? I imagine there's a different thread with this info and a little off topic from the original intent of this thread. If anyone has a link, I'd appreciate it.
Now that I've already done whitslacks 1.47 rooted rom, I should be fine with that, correct? What you're doing here doesn't necessarily apply if one has already done whitslacks and is happy with it?
Thanks, still learning this stuff.
vballboarder said:
Okay, I've spent quite a bit of time trying to figure this whole root thing out and I've got a pretty good handle on rooting and flashing ROM, but can't find what's the deal with odexed versus de-odexed? I imagine there's a different thread with this info and a little off topic from the original intent of this thread. If anyone has a link, I'd appreciate it.
Now that I've already done whitslacks 1.47 rooted rom, I should be fine with that, correct? What you're doing here doesn't necessarily apply if one has already done whitslacks and is happy with it?
Thanks, still learning this stuff.
Click to expand...
Click to collapse
I'm quite new and may have some of this wrong, but I think I'm close:
When a developer makes an application file, it is an apk. The apk is actually a zip file with information inside on how to install, name of the file, and resources used in the application, like pictures used for buttons. If the file is not odexed, then there is also a .dex file contained which has the actual program code used by the virtual machine. If a file is odexed then there is a separate file with the same name as the apk, but has the extension .odex. This is done by htc to the system files to make things (arguably) a little faster.
Dev's then deodex the files to put the odex file back into the apk as a .dex file, if this is desired. The reason for this is so that they can be changed later to do something like theming.
Yes, this is the same as whitslack's. If you wanted a de-odexed ROM you could now grab the one caulkin posted and flash it.
laydros said:
I'm quite new and may have some of this wrong, but I think I'm close:
When a developer makes an application file, it is an apk. The apk is actually a zip file with information inside on how to install, name of the file, and resources used in the application, like pictures used for buttons. If the file is not odexed, then there is also a .dex file contained which has the actual program code used by the virtual machine. If a file is odexed then there is a separate file with the same name as the apk, but has the extension .odex. This is done by htc to the system files to make things (arguably) a little faster.
Dev's then deodex the files to put the odex file back into the apk as a .dex file, if this is desired. The reason for this is so that they can be changed later to do something like theming.
Yes, this is the same as whitslack's. If you wanted a de-odexed ROM you could now grab the one caulkin posted and flash it.
Click to expand...
Click to collapse
Thanks, been wondering wtf deodex'd, etc meant.
laydros said:
I'm quite new and may have some of this wrong, but I think I'm close:
When a developer makes an application file, it is an apk. The apk is actually a zip file with information inside on how to install, name of the file, and resources used in the application, like pictures used for buttons. If the file is not odexed, then there is also a .dex file contained which has the actual program code used by the virtual machine. If a file is odexed then there is a separate file with the same name as the apk, but has the extension .odex. This is done by htc to the system files to make things (arguably) a little faster.
Dev's then deodex the files to put the odex file back into the apk as a .dex file, if this is desired. The reason for this is so that they can be changed later to do something like theming.
Yes, this is the same as whitslack's. If you wanted a de-odexed ROM you could now grab the one caulkin posted and flash it.
Click to expand...
Click to collapse
So, essentially caulkin's rom is deodexed, whitslacks is not? Which means, whitslacks rom is exactly like a non-rooted 1.47 ota but with root permissions, while caulkins is exactly like whitslacks, but with the ability to change some files around later.
Like I said, I'm still learning, and it appears whitslacks is sufficient for me since I don't even know what files I could manipulate with caulkins (or your) version nor how to do it even if I wanted to.
Thanks again, learning a little more every day. I've spent about 5 full days on this forum. slowly but surely, right?
Pretty cool

Custom clockworkmod compatible update.zip

Hello, I would like to create my own update.zip that would be compatible with clockwork mod. I have several files in several locations that I manually copy over after new installs like multicolored bash nano iwconfig iwlist etc. And I think it would be much easier to create a installable package for that, I also delete a number of built I. Apps like tweeter amazon etc. And I have seen the scripts inside oyhers update.zip's that I could add the bash commands to remove those things as well.unfortunately I know nothing about what clockworkmod wants and I see binarys inside these zips dont know if those are customized for each zip or the same in all of them, I dont know what files or information is absolutely required. The best possible solution is if I had a blank update.zip that held all of the required files settings and all I needed to do was add my files and asd a few lines to a preexisting script to remove sum stock apps.thinking back I might have seen a file containing all the files names and md5 chucksums for each as well which if necessary I can do. Is there something like this available for download sumwhere? If not ajy resources to learn the required information and find the required binarys.thank you in advance.
Sent from my Droid using Tapatalk
Hi,
I've been trying to learn the same thing. I'm curious if you found anything useful since posting this.
Of course, if I find anything, i'll post back here too.
Thanks.
Same problem here
Good to hear someone with same problems. I want to create a generic ROM for myself and I want to use ClockworkMod to help flash it instead of using fastboot.
Well, I have found no documentation about what ClockworkMod may need for a zip file.
But I guess it could be possible to just replace them with your own by downloading an existing zip file created by someone else.
I'll try it to see if that works or not. Of course, a documentation would be better.
I regularly flash a new CM7 Nightly as they are released and I have to manually modify some things each time a new rom is flashed. I change screen density and add a notification ringtone that CM7 does not have. I wanted to automate that. Since I have to reflash the Google Apps each time anyway, I thought why not modify the gapps zip to include my changes. After searching the web I found a little info about how to do it. I just modify the zip on my computer using WinRar, copy the file to my device and re-sign the package using signapktic which is free on the market. Then flash using CWM. It worked great. No more manual adjustments. There are some instructions here which helped me:
http://forum.cyanogenmod.com/topic/15030-moving-apps-to-system/
I been getting into the kitchen
http://forum.xda-developers.com/showthread.php?t=633246
So far i`ve managed to integrate a few apps , ringtone should be easy
next the fonts from utmost rom
thanks to the kitchen, Im now running at script kiddie level

[Q] help making .zip to flash wpa_supplicant

Good evening dev community, I'm trying to create a flashable .zip that will replace the wpa_supplicant file with one that can connect to Ad-hoc networks. Replacing the file is actually really easy to do but I want to make a flashable .zip for others who don't want to mess with root explorer or ADB.
I have taken a .zip that works for the CWM 2.x for my phone but that won't flash on the xoom because CWM 3.x doesn't support the amend language so I converted it using amend2edify by nubecoder and I was so excited when it seemed to work but it will look like it's flashing and not actually do anything.
I was wondering it someone who knows more than me might want to lend a hand.
Please take a look and see if you can see anything wrong with my updater-script
Here is what I have so far. (see attachment)
Disclaimer: I got bored with not getting anywhere so I changed some of the display text so it's goofy so try to ignore that.
You shouldn't need to be afraid to flash it, it's harmless... that's the problem.
But as always you do so at your own risk.
Bump?
Sent from my Xoom using Tapatalk
Take a look at this thread. There is a link to a generic update script that works on the xoom. Just put your file in the right folder / subfolder and you should be good to go.
http://forum.xda-developers.com/showthread.php?t=1041205
I'll take a look at it. Thanks.
Sent from my Xoom using Tapatalk
Thanks for the help. It's exactly what I needed. I put a thank you in my new thread on this http://forum.xda-developers.com/showthread.php?t=1106130.
Do you know where I can get the wpa_supplicant file that will work with my Toshiba Thrive Tablet running Android Stock ROM 3.1? Thanks!

[Q]Using UOT Kitchen

I'm trying to use this and for the life of me no matter what I do it always puts out an error when trying to create the zip file. Any suggestions or ideas? I thought I tried uploading the right files and settings but I've done it four times now and to no avail.
Ddot196 said:
I'm trying to use this and for the life of me no matter what I do it always puts out an error when trying to create the zip file. Any suggestions or ideas? I thought I tried uploading the right files and settings but I've done it four times now and to no avail.
Click to expand...
Click to collapse
You will probably get flamed for not posting this in Themes and Apps or some other section as this is not development.
I used UOT today and had no issues for Infused v2.0.
I apologize. Perhaps you can PM me exactly what you are selecting when on the file upload page. I've tried every combination it seems. Maybe my files do not like some of the mods I have made, I don't know.
Move this thread if need be, don't want to piss anyone off.
The developers are very sensitive to posting things in that section that aren't development related. I found that out the hard way myself!
Anyway, all I wanted was a circle battery mod so I selected the one I wanted on the battery mod tab, clicked preview to see what it looked like then went to the tab to upload the 2 system files for gingerbread from my phone (framework-res.apk and systemui.apk). Submitted that and that was all I did. Didn't select anything else.
Thanks man. Yea I finally figured it out.... I was uploading files that were read only because I did not change the mount when I copied them from root explorer to sd card to my phone.
Sent from my rooted infuse flashed with infused!

[Q] How to create a Google Apps flashable zip from the stock ROM ?

From CM Gapps page it says
It is possible to perform a "backup" of the Google Apps on your device and then "restore" them, but this does take additional steps which are not covered here.
Click to expand...
Click to collapse
I'd like to know how can I do this.
I've searched all across the forum but had no luck. It looks like some kind of trade secret.
I know that it's not just a matter of pulling the apk files. Because I can see that the zip has .apk, .jars, .so, configuration and certificate files.
I'm guessing this is done by extracting the files from a system.img.
But how is this done?
Is there some script available to build a gapps zip from a system.img file?
Another thing is that my OnePlus phone doesn't has an official LP update yet (although CM12 and their gapps work fine) so I suspect this would have to be done using the stock ROM of another device, maybe a Nexus. Is this correct?
Any help is appreciated.
Thanks

Categories

Resources