Droid Razr Gsm Patch
Droid Razr Gsm
When essentially the same device is released on both GSM and CDMA carriers, development on one can be stronger than development on the other despite the fact that.
This is a patch to fully enable the GSM on CDMA Global phones. The Global Phones are phones with CDMA and GSM modems but that are usually configured to primarly work on CDMA network and at least to be able to call on GSM network. The patch is working on every Stock Rom, on every AOSP Rom and on every Android version. If you are successfully using this patch please comment the thread with your phone model.
Hi everyone, I was hoping that I might be able to get a bit of help here. I think I have a bit of a doozie of a problem. For me it is a doozie anyway, as I'm a bit unfamiliar with with android o/s and have patchy tech knowledge at the best of times.
Motorola Droid Razr Gsm
I have some giant gaping holes where someone with my level of experience (a bit above beginner, but hardly advanced) should understand things better. Anyway, I have a rooted XT910. I bought it rooted, and haven't really played with it much apart from appreciating the fact that I can disable bloatware. I have been unable to update to JB via the OTA updates since they were rolled out, but hadn't really taken the time to look into why. Pulling out the logfile for the last attempted OTA update, I get the following (sorry for posting the full thing, I just don't want to have missed anything). Installation aborted. Looking at /system/bin/ there is a /system/bin/logwrapper.bak along with the logwrapper file.
The modification date on both files is from before I got the phone. If logwrapper has an incorrect sha1sum, I presume that means it's been corrupted or changed and that's what's interrupting the update? I also presume that logwrapper.bak is a backup of the original logwrapper file (pre-corruption). Is logwrapper the problem, or is there something higher up in the logfile that I'm missing that's kicking me out of the updater?. If I rename logwrapper to logwrapper.broken and rename logwrapper.bak to logwrapper, might this fix the problem? Might this cause more problems?.
Alternately, is there somewhere I can get a clean version of logwrapper to replace my corrupted version?. If logwrapper is corrupted, does this mean that umpteen other things are likely to be corrupted as well? I'm loathe to do a factory reset if I can avoid it and would rather fix it this way if possible. Finally, I have copied the OTA update file so I don't have to re-download it for the twentieth time, if I whack it and the crc file back in /cache/recovery will that shortcut me have to re-re-re-download the OTA, or can I only manually update by factory resetting? Any help would be massively, massively appreciated.
I had a search of the forums and didn't find anything. Verifying current system. File '/system/bin/logwrapper' doesn't have any of expected sha1 sums; checking cache failed to stat '/cache/saved.file': No such file or directory failed to load cache file script aborted: assert failed: applypatchcheck('/system/bin/logwrapper', '23d23abf573e78e4bfe692fedf631ad1faa3179e', '4a63fec78956def045b442910a754fa640db8f5a') assert failed: applypatchcheck('/system/bin/logwrapper', '23d23abf573e78e4bfe692fedf631ad1faa3179e', '4a63fec78956def045b442910a754fa640db8f5a') E:Error in /cache/BlurVersion.672.180.41.XT910.Retail.en.EU.zip (Status 7). Click to expand.That ^^^ is classic 'Status 7' error stuff.
You do likely need to 'fix' (replace/update) that file before the OTA will allowed to be installed, but you'd be best advised to have a Nandroid backup handy just in case your current system doesn't like it (I don't have your device so I don't know the impact of restoring a file that somehow got out-of-sync-although, I seem to remember the replacement of the logwrapper file being used on the Droid X for installing CWM for the bootstrapper-don't know if the same mechanism is used for the RAZR Maxx). I wouldn't imagine that your logwrapper is corrupt or that other files are either. It may be that the rooting method or something else root-related on your device changed this file? Anyway, you can also use my OTA Verifier app to scan your system for other files that might also not be in-sync and/or other issues that it can find.
I've not pulled files from system images for Moto devices before, but if you can point me to a system.img file for your phone's currently installed version, I might be able to help you out. I hope that helps!