Dear All,
I have recently rooted a sidekick 4g (t-mobile) using SuperOneClick and today, I have a OTA update, which I've postponded until tomorrow...
After further research I found away to rename a file from .zip to .bak to stop further updates, but I'm still getting the notification..
So more research I saw other options for other phone about changing the build.prop file, but all the research doesn't match the info I've got on my SD card... (as I copied the file from the system folder to SD, the plugged the SD into my pc)
Can anybody help, what parts of the build.prop info would be needed for advice on changing it to other figures? I could provide it all, but I didn't want to copy and paste a big text file here.
Thanks in advance for the help and support.
Regards
If you
Code:
pm disable com.wssyncmldm
as root, you'll stop receiving notifications about firmware updates. This might or might not break TMO contacts backup, or maybe that was due to the com.wssnps package I disabled at the same time.
I know nothing about build.prop or what the update agent might actually be using to sense the version.
just go into system/apps and delete wssyncmldm.apk
Thank you both for the replies, I will do that later on tonight.
Related
So I have a Samsung Galaxy Europa I5500L (Running 2.2 android)
Im wanting to remove my carrier name from the pulldown bar and the lock screen.
I have successfully pulled framework-res.apk using adb into my pc.
I then edited it, and changed a few things to do with eri.xml (carrier name), and saved it.
However, I cant get adb to 'push' the framework back into the phone, even with su permissions, even with usb debugging on, and yes its rooted, and yes the adb connection works fine normally
SO I came to the conclusion that I could use root explorer to put the framework file back into my phones system.
This is way Im going to do it is this.. copy the modified framework-res.apk it to my SD card, then inside my phone copy the file across to the phones system area using the root explorer app (making sure that the system is R/W). Im thinking this will obviously replace the existing framework-res.apk
However, Is this safe? Ive read about people doing it before but it doesn't seem right to replace a system file whilst the phone is up and running
Can I have some clarification whether or not this will be fine or not?
Thanks...
bump
any response would be welcomed , im really stuck here!
Your phone might not boot afterwards, so unless you have a custom recovery dont do that.
Sent from my T-Mobile myTouch 3G using XDA App
I uninstalled AT&T Address Book (through Titanium Backup) and expected to be able to restore it in the event of catastrophic failure...was wrong. I then attempted to replace contacts.apk with one without AT&T Address Book and that broke EVERYTHING...did factory reset...even worse. I managed to get Contacts.apk back to normal but I still have the "AAB Initializing error when ever I click on my address book...
Anyone know how I can restore my ...
ALRIGHTY...all I need now is the name of the ATT_AddressBook.apk, and I should be back in business...
Go to this thread the apk is like 4 posts down!!!
HERE
and i would appreciate it if you could help me...
we are trying to get some development going for the LG thrill 4g...
so if you could plz copy the flash_image file in the system/bin folder on your device and post it on this thread please!!!
thankyou your help is appreciated!!!
I can help you out, but I'm in the /system/bin folder right now and don't see the file your talking about.
I'm using root explorer BTW and have r/w control...
Closest thing is "flash_renderer_test" then "frame buffer_test". The file you speak of should be right around there, but its not..
sorry for posting new thread but I don't know where to ask...can anybody please tell me tge new update 4.5.269 and someting3..is it the new version of gingerbread,is it safe to update..please tell me...
The new update is 4.5.629. It goes from Gingerbread 2.3.3 to Gingerbread 2.3.4, so a slight update. There are a few bug fixes, but it has a number of undesirable things.
1) 4.5.629 is currently not rootable
2) You cannot simply return to an earlier version via SBF.
You can overcome the first by using Voodoo Rootkeeper or similar to root on your current version, back up root with Rootkeeper and then update.
Recently, a method was found for this release to unbrick phones damaged by attempts to SBF or from bad ROMs: http://rootzwiki.com/topic/23207-how-to-sbf-unbricking-root-d2g-629 This also allows users who did upgrade to 4.5.629 to return to the previous version, root there and then upgrade again.
So it is sort of safe, but not ideal. The changelog is here, decide if the bug fixes are important enough for the added inconvenience
http://support.verizonwireless.com/pdf/system_update/droid_2_global.pdf
ok...thank u very much +1..I prefer not to update for now,and by mistake ,i select yes button in the update prompt,and its in the pull down bar,stucked and is ready to start downloading as soon as I connect to wi-fi,how will I cancel the download
You can block the update by renaming these files (e.g., append ".bak" to each filename):
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
Since these are in /system, renaming them requires root privileges and a root-enabled file manager (such as Root Browser Lite, available in the Google Play store).
ok..thanks,will do that,but after doing that,will I be able ro manually update it,or all the updates have been blocked???
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
jabberwockish said:
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
Click to expand...
Click to collapse
okok..thanks man +1
edit : i got this 'failed to rename file' error ..what should I do??
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
jabberwockish said:
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
Click to expand...
Click to collapse
the app that u suggested me,root browser lite and my phone was rooted and also have been granted superuser's permissions..
You didn't remount /system in Read/Write mode.
Gasai Yuno said:
You didn't remount /system in Read/Write mode.
Click to expand...
Click to collapse
please tell me how to do that
Root Explorer has a button for that.
“adb remount” when connected to a PC with USB debugging enabled will do that as well.
It's also possible to do from the terminal emulator, however I don't remember the exact command.
i can't find that button,by long pressing the file/folder or what?
It looks like this app defaults to RW once it gets superuser permission (GY was referring to Root Explorer, a different app). How about copying a system file, does that work?
I have decided to stick with 4.1.2 and am currently rooted with an unlocked bootloader.
Is there a way to keep the phone from constantly checking software status and giving me the notification to upgrade (install now or install later screen)?
I went ahead and downloaded and had it "install now", knowing it was going to fail, in hopes it would stop checking after failing initially. No go as it keeps going to the install selection screen after a certain period.
I am assuming there is probably something I could "freeze" in TiBu to stop the phone from constantly checking software status, but am not sure which one and if freezing it will violate the law of "unintended consequences" (ie if that app is critical in other phone operations).
Just want to get rid of the "reset" I have to do every time I get the notification.
Thanks!
paulsoncpa said:
I have decided to stick with 4.1.2 and am currently rooted with an unlocked bootloader.
Is there a way to keep the phone from constantly checking software status and giving me the notification to upgrade (install now or install later screen)?
I went ahead and downloaded and had it "install now", knowing it was going to fail, in hopes it would stop checking after failing initially. No go as it keeps going to the install selection screen after a certain period.
I am assuming there is probably something I could "freeze" in TiBu to stop the phone from constantly checking software status, but am not sure which one and if freezing it will violate the law of "unintended consequences" (ie if that app is critical in other phone operations).
Just want to get rid of the "reset" I have to do every time I get the notification.
Thanks!
Click to expand...
Click to collapse
STOP OTA UPDATE NOTIFICATION
If the OTA already downloaded, delete it here /cache/fota
To disable the OTA:
Rename or freeze the apps with Titanium backup:
otacerts.zip located in /etc/security - rename to otacerts.zip.bak
Rename fwupdate.odex, fwupdate.apk located in /system/app
and freeze SDM1.0 located in /system/app
Trouble locating the directories/files to rename.
Thanks buhohitr for your quick response.
freeze SDM1.0 located in /system/app
Click to expand...
Click to collapse
I was able to locate this and freeze it in Titanium, however, I was unable to locate the other files on Titanium or directory locations you specified when browsing through the phone's file manager or through my computer (connected to the phone.)
I also could not locate the /cache/fota directory to delete the software download. In the phone's file directory, I did make sure all options were selected (to show hidden directories). What am I missing?
Rename fwupdate.odex, fwupdate.apk located in /system/app
Click to expand...
Click to collapse
Just to be clear, once I locate this file, I just change the extention from "odex" to "apk"?
Thanks
just realized I need a root explorer app.
buhohitr said:
STOP OTA UPDATE NOTIFICATION
If the OTA already downloaded, delete it here /cache/fota
To disable the OTA:
Rename or freeze the apps with Titanium backup:
otacerts.zip located in /etc/security - rename to otacerts.zip.bak
Rename fwupdate.odex, fwupdate.apk located in /system/app
and freeze SDM1.0 located in /system/app
Click to expand...
Click to collapse
Disregard my previous post on the fwupdate.odex/.apk files. Realized I needed to add .bak to all the files you specified.
All steps completed and thank you for your assistance! Just needed to get the rootexplorer to locate the directories. (one note, I am pretty sure the update package did get downloaded, however I did not see a file in the "fota" directory.) Not too concerned as all other steps completed.
paulsoncpa said:
Thanks buhohitr for your quick response.
I was able to locate this and freeze it in Titanium, however, I was unable to locate the other files on Titanium or directory locations you specified when browsing through the phone's file manager or through my computer (connected to the phone.)
I also could not locate the /cache/fota directory to delete the software download. In the phone's file directory, I did make sure all options were selected (to show hidden directories). What am I missing?
Just to be clear, once I locate this file, I just change the extention from "odex" to "apk"?
Thanks
Click to expand...
Click to collapse
TB only can see SDM1.0, if the OTA did not download to your phone you won't see anything under /cache/fota so this is normal. The rest you need to use some root browser app like root explorer or ES file explore to find them and just rename by adding a .bak at the end, example: otacerts.zip, fwupgrade.odex,fwupgrade.apk rename them to otacerts.zip.bak, fwupgrade.odex.bak,fwupgrade.apk.bak.
buhohitr said:
if the OTA did not download to your phone you won't see anything under /cache/fota so this is normal.
Click to expand...
Click to collapse
I know it did download, but wondering if it automatically got "trashed" once the install failed. Although, when the "install now" notification came up, it went to recovery for the install instead of initiating a download. No big deal since I got all other steps taken care of.
thanks again for your assistance.
paulsoncpa said:
I know it did download, but wondering if it automatically got "trashed" once the install failed. Although, when the "install now" notification came up, it went to recovery for the install instead of initiating a download. No big deal since I got all other steps taken care of.
thanks again for your assistance.
Click to expand...
Click to collapse
Yes, it got trashed when it failed!
Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.
TheJokah said:
Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.
Click to expand...
Click to collapse
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.
ajent said:
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.
Click to expand...
Click to collapse
I'm having the same issue with upgrading 10G. maybe there is a way in the ota Package
EDIT:
I found this link http://forum.xda-developers.com/showthread.php?t=2699123 to force an update using the dlpkgfile from ota. I wonder if it could work for G4 also??
@TheJokah @ajent. Don't need to be rooted. Root Browser will be able to view the directory without root permissions. (I use it all the time to browse system partitions and files on unrooted devices). You can do a lot with Root Browser without root. You just can't make changes.
When the fota is available you will find it in /cache/fota
I have captured several OTAs for various devices this way...
EDIT: Make sure to copy the file after it downloads and before restart, otherwise the file will be deleted before you get it.
That is good info, thanks.
I'm pretty convinced flashfire installing the xposed zip does something that isn't reverted when flashing the unrooted system image. I used my limited knowledge to look at that xposed zip and it seems like only modifications are made to /system so it should be removed when flashing back unrooted image. I really don't know, but hope somebody can figure it out lol.