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?
Related
Hello,
My brother and I both have d2gs. I changed/removed apps in the system/apps folder as a result I was unable to upgrade to 2.4.3. My brother hasn't changed anything or rooted. If I copy his folder and overwrite my directory will I be able to update? (His phone is already updated)
Thx
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
leobg said:
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
Click to expand...
Click to collapse
Yea I didn't think it would be that easy haha
leobg said:
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
Click to expand...
Click to collapse
Yea I didn't think it would be that easy haha
leobg said:
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
Click to expand...
Click to collapse
I think Vexorg might mean the system/apps folder, which he or she modified to disable bloatware. It seems that removing apps from that folder makes the update fail. One should rename the apps instead to disable (e.g. CityID.apk -> CityID.apk.bak) so the original state can be recovered when updating.
Correct me if I'm wrong, but in that case copying the brother's system/apps should work fine. I've read that you can download the same APKs online to recover them, so I would imagine using the brother's directory contents should be fine as well.
adridge said:
I think Vexorg might mean the system/apps folder, which he or she modified to disable bloatware. It seems that removing apps from that folder makes the update fail. One should rename the apps instead to disable (e.g. CityID.apk -> CityID.apk.bak) so the original state can be recovered when updating.
Correct me if I'm wrong, but in that case copying the brother's system/apps should work fine. I've read that you can download the same APKs online to recover them, so I would imagine using the brother's directory contents should be fine as well.
Click to expand...
Click to collapse
Yup that's exactly what I meant, can anyone confirrm?
Hello,
i would like flash CWM on my TF101G so i can flash a rom. I have it rootet with ViperMod but what´s the next? I have testet nvflash but it´s fail. My serialnumber begins with BA0. What can i do?
With my Galaxy S2 that´s all so easy and with the Transformer so difficult
Sorry for my bad english, i´m from germany.
Not difficult at all, everything is there jsut have to do a little research.
RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
Thank you for your help but i can not install this apk it´s parsingerror
silence84 said:
Thank you for your help but i can not install this apk it´s parsingerror
Click to expand...
Click to collapse
try re downloading it or make sure that you are rooted
Titanium Backup says i have root. Loaded again but same error. I have Android 3.0.1 on the Tablet could be this the reason?
silence84 said:
Titanium Backup says i have root. Loaded again but same error. I have Android 3.0.1 on the Tablet could be this the reason?
Click to expand...
Click to collapse
Yeah, update to the latest firmware. It should work after that.
Try OTA Root Keeper (it might save your root so you don't have to root again).
IF not just update, run ViperMod again and install RecoveryInstaller
I can not flash the update. I put the Update on the SD, the system dedects also the update but after the restart the update breaks and the system restart again.
I desperate slowly
Did you extract the file you download to get to the zip file inside? You also have to rename that extracted file. I cant recall exactly what it need to be rename to but I'll check soon as i get near a PC
baseballfanz said:
Did you extract the file you download to get to the zip file inside? You also have to rename that extracted file. I cant recall exactly what it need to be rename to but I'll check soon as i get near a PC
Click to expand...
Click to collapse
"EP101_SDUPDATE.zip" i think this is what you have to rename the file
edit: Tips from Baseballfanz For those not able to get it working, a few things to check.
1-Make sure you actually extract the WW_epad-user-8.6.x.x.zip within the zip. Inside the file you download is an Asus folder, inside that is an Update folder, inside that is the WW_epad-user-8.6.x.x.zip file you'll be working with.
2-When renaming, if your PC is set to "hide known extension", you'll not see the .zip so if you type in .zip you'll get filename.zip.zip The file manager on the TF should show you the extension
3-Make sure it's on the root of the sd card and not within any folder.
4-Check spelling of files WW_epad-user-8.6.x.x.zip EP101_SDUPATED.zip
5-Micro sd card is in FAT32 format. Try a different card or format again (after saving your stuffs)
6-File manager on the TF sdcard is internal and Removable/MicroSD is the external sd card.
THESE ARE TIPS FROM BASEBALLFANZ POST SOMEWHERE ELSE ONLY I X'ED OUT THE FIRMWARE NUMBER TO DENOTE THE NEWEST FIRMWARE.... HOPE YOU DNT MIND
Thank you very mutch for your help. I have the last update installed 8.6.6.23 but i can this not rooted. ViperMod no longer works.
YYYEEEEAAAAHH
I have root with nachoroot. CWM is already on it. Many thanks again!
That's good to hear.
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.
This is my first time rooting my phone (tried rooting an o+ phone but couldn't unlock the bootloader) and I want to know how to my get phone's firmware. I tried using the Samsung Firmware Downloader but it won't accept my model and region.
I've tried using SuperSu to root but Root Checker says root access wasn't properly installed. What do I do now? Can I download a different firmware from a different site and is it safe? Does showing my pda code safe?
Edit: Forgot to mention I've already flashed TWRP.
Excuse me but what is your region and model number
tech-mаn said:
Excuse me but what is your region and model number
Click to expand...
Click to collapse
Never mind, I manage to download the firmware and root my phone thanks to Samsung Downloader. I wasn't able to download it at first because I keep using XXU (the one I saw in *#1234#, samsung firmware) as my region but it was actually XTC (I checked Software information in the About Phone).
Ok
if twrp is installed
root the phone with magisk
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
Maybe it'll work
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
first root your device
then use mt manager to access build.prop file
i tested this in my sm-t585 with lineage os custom rom
alireza9082 said:
then use mt manager to access build.prop file
Click to expand...
Click to collapse
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
MasterKwonKaichi said:
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
Click to expand...
Click to collapse
as i said
use mt manager to save changes in build.prop
Since our system is F2FS you can't modify system it stays RO you can make a magisk module yourself to modify build prop also don't use supersu rooting is very easy just flash twrp then flash magisk. I'm making a custom rom which I'm hoping to release soon that's ext4 but I'm limited by time and the recent events from where I live so I can't give a ETA