I have a Droid RAZR and I'm on Verizon, and when I try to send a text that's over 2x160 characters to another Verizon phone, it usually doesn't send. In the message details, my phone says "Received", but the other person doesn't get the text. This has been happening for a while, but it's only gotten bad recently - before, I would have to reach 5x160 characters in order for it not to send. Texts sent to non-Verizon phones seem to send fine. To try to get around it, I set my SMS app (I use GoSMS) to always split up my messages. What happens now is that some of the messages in the batch don't go through, regardless of the number of messages. I would ideally like to not need to have my phone set to split my messages automatically, and be sure that long messages are going through. How can I do this?

I have a Verizon Motorola Razr HD Maxx, running the latest firmware (182.46.15.XT926). My phone was dropped and the screen shattered about 6 months ago. The Razr was powered off and left alone while I switched to an older phone until I could find the time and money to get a screen replacement. Having just done so, my phone is now in mostly working order. I can browse on 4G and make/receive test messages and calls. However, the date/time on the phone are completely inaccurate. It is currently reporting the date as 3/15/2015, and the time as 6:52 as of the time of this post (while it is 10:56 AM EST, 5/21/2015 in reality). Manually attempting to change the time does not work - After modifying the time and selecting done, the change does not persist. I do not appear to be the only one with this problem - others have reported it online (see [here](http://forums.androidcentral.com/android-4-4-kitkat/394439-razr-hd-time-date-won-t-update-can-t-connect-google.html) and [here](https://forums.motorola.com/posts/2b9452ac6b) for example), but no solutions have been posted which worked. I am curious if anyone here has input as to a solution. This is a huge impediment for me, since many apps rely on the time and any SSL cert checking will fail due to the incorrect date, preventing access to Google Play.

I am trying to pull data off a Droid Razr XT912 with a broken digitizer and screen from last summer which has been under pattern lock since then. I purchased a Micro-to-HDMI cable, which successfully displays the phone's unlock screen on my TV. I also purchased a Mini-to-USB cord so I could enter the pattern on the screen with a USB mouse. The phone, however, is not recognizing the mouse, regardless of whether it is wired or wireless. Interestingly, plugging the Mini-to-USB into my XT907 which I got to replace the old phone makes the mouse boot right up, even though that phone has its own pattern lock. I'm completely lost as to why the newer model cannot recognize the device when the older one can. My only guesses are as follows: 1. The operating platform has been updated since last year to support the USB mouse connection. The XT907, having been in operation until April 2014, would have received the update while the XT912 was locked with no SIM since August 2013. 2. The phone does not support a simultaneous connection to the HDMI (via Micro) and the USB Mouse (via Mini). 3. The phone does not supply adequate power to the mouse. Any thoughts on how I might solve this riddle? If #3 is the culprit, does anyone know which adapter do I need to supply external power to a USB mouse in "on-the-go" mode? Last, is this a fool's errand and should I just ante up for a new digitizer? Thank you in advance!

My Razr (Stock ROM 4.0) is very very hot. After some research I found com.android.providers.downloads is responsible, since it's using about 60% of CPU. I have tried killing it, and it respawns, however what I found to work (for two hours) is clearing the cache and data of the process, and killing it, however something is triggering again. P.S. I'm not downloading anything, and all my apps are updated (so Play Store is not trying to download updates). If I freeze this process, the Gmail app crashes.

I've tried everything that I can think of to try and root my Razr Droid Maxx HD Verizon phone, running 4.4.2. Towel root, sunshine and I can't even remember all of the others I tried. Nothing works!

A couple of days ago, I got an error on my phone (Motorola Razr HD xt925) saying that it cannot load the home screen. So, I restarted it in order to resolve the issue. However, it didn't reboot and since then it has been stuck in the Motorola logo. * I tried to do recovery or factory reset, but all the options lead to the same Motorola logo with no luck. * The only option that is working is **AP Fastboot**. I managed to unlock the bootloader by getting an unlock code from Motorola's website and using the **mfastboot** command. So I assume that the fastboot command is working since it detects the devices; however, I couldn't make ADB command to work since it give the error: 'device not found'. * Anyway, the second step is to flash the phone. According to this question , I should be able to do that. However, when I am running the command fastboot flash partition gpt.bin, I am getting the following result: (bootloader) Variable not supported! target max-download-size: 30MB sending 'partition' (32 KB)... OKAY [ 0.022s] writing 'partition'... FAILED (remote failure) finished. total time: 0.154s I have been searching for days to solve this problem, but nothing yet! I don't know which part I am doing wrong.

How do I root my Motorola Droid Razr?

I have an old droid RAZR Maxx (4.1.2) that I decided I want to root, but I want to make a backup first just in case. I've followed instructions from this site: How To Create a Full Android Phone or Tablet Backup Without Rooting or Unlocking Your Device My command was this: adb backup -apk -shared -all -f c:\backup.ab The resulting backup.ab file on the C: drive was only 41 bytes and, when opened in a hex editor, appears to only be the header of the backup file. I'm wondering what I'm doing wrong here, I've googled but can't find anything that helps. Any suggestions? Edit: This is not a duplicate of the suggested a topic linked by beeshyams. That topic explains why the user couldn't back up one *single* app's files, I'm trying to back up everything. I don't care if I don't get SMS included in that backup because it's an old phone, I'm not using it to text, but there are other apps and settings that *should* back up without issue.

I'm using OS Monitor to look at CPU usage because I've noticed a drastic performance decrease lately. The app shows that system/xbin/sh is consuming anywhere from 10% to 70% of the CPU. This happens constantly, the process never stops appearing at the top of the list. I have a two questions: 1. What is system/xbin/sh? 2. What could be causing it to utilize so much of the CPU? 3. Is there a way to track which apps make calls to system/xbin/sh? More Info: - Android version: 4.1.2 - Phone: Motorola DROID RAZR MAXX HD - ROM: Droid Nexesque v3.8 (AOSP-based ROM) (through safestrap) - Rooted: yes - not running any anti-virus or the like adb shell top output: PID PR CPU% S #THR VSS RSS PCY UID Name 6214 0 97% R 1 182528K 92452K root /system/xbin/sh ... 6211 0 0% S 1 1428K 448K root /system/xbin/sh 6212 0 0% S 1 53500K 52596K root /system/xbin/sh ... adb shell ps output: USER PID PPID VSIZE RSS WCHAN PC NAME root 1 0 544 404 ffffffff 00000000 S /init ... root 6211 1 1428 448 ffffffff 00000000 S /system/xbin/sh root 6212 6211 53500 52596 ffffffff 00000000 S /system/xbin/sh root 6214 6212 293976 214156 ffffffff 00000000 R /system/xbin/sh ... cat /proc//cmdline output: "level 1" process: /system/xbin/sh /system/bin/debuggerd "level 2" process: /system/xbin/sh /system/etc/init.d.loader "level 3" process: /system/xbin/sh /system/etc/init.d.loader /system/etc/init.d.loader contents: #!/system/xbin/sh ############# ############# ############# # init.d.loader by puppet13th@xda # Version 0.7 19 June 2012 # to run script in background append .bgrun to script name # example : "myscript.bgrun" # ############# ############# ############# logfile=/data/init.d.loader.log loglength=65536 bgrunsign='.bgrun' if [ -f $logfile ] then log=cat $logfile currentloglength=length "$log" if [ $currentloglength -gt $loglength ] then rm -f $logfile fi fi echo " * date * init.d.loader start . . .">>$logfile echo " ">>$logfile if [ ! -d /system/etc/init.d ] then echo " creating init.d folder . . .">>$logfile mount -o remount rw /system >>$logfile 2>>$logfile if [ -f /system/etc/init.d ] then rm -f /system/etc/init.d >>$logfile 2>>$logfile fi mkdir /system/etc/init.d >>$logfile 2>>$logfile mount -o remount ro /system >>$logfile 2>>$logfile fi echo " ">>$logfile echo " i : running init.d scripts . . .">>$logfile for script in /system/etc/init.d/* do if [ -x $script ] then bgrun=grep $bgrunsign $script>/dev/null if [ $? = 0 ] then echo " - running $script in background . . .">>$logfile /system/xbin/sh $script & >>$logfile 2>>$logfile else echo " - running $script . . .">>$logfile /system/xbin/sh $script>>$logfile 2>>$logfile fi fi done echo " ">>$logfile echo " * date * init.d.loader end . . .">>$logfile echo " ">>$logfile /system/bin/debuggerd contents: #!/system/xbin/sh #init.d.loader /system/etc/init.d.loader /system/bin/debuggerd.bin Checking /data/local for things other tools might have left to "plug into init": There are four empty folders and a file named RootToolsMounts. /data/local/RootToolsMounts contents: rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /acct cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 /dev/block/platform/msm_sdcc.1/by-name/userdataorig /datamedia ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/userdataorig /ss ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc,discard 0 0 /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/pds /pds ext3 rw,nosuid,noexec,relatime,barrier=0,data=writeback 0 0 /dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 /dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 Looking at /data/init.d.loader.log (~50 MB file), it is running the init.d scripts approximately every 10 seconds. I'm not too familiar with the underlying components of Android, so I'm not sure if this is a lot or not. The two scripts in /system/etc/init.d./ are init.d.loader.test and minfree. /data/init.d.loader.log contents: The log file is filled with these entries repeating every 10-12 seconds ... * Sun Feb 23 18:46:09 CST 2014 * init.d.loader start... i: running init.d scripts... - running /system/etc/init.d/init.d.loader.test... - running /system/etc/init.d/minfree... * Sun Feb 23 18:46:09 CST 2014 * init.d.loader end... * Sun Feb 23 18:46:20 CST 2014 * init.d.loader start... i: running init.d scripts... - running /system/etc/init.d/init.d.loader.test... - running /system/etc/init.d/minfree... * Sun Feb 23 18:46:20 CST 2014 * init.d.loader end... ... init.d.loader.test contents: #!/system/xbin/sh # init.d.loader tester # check /data/init.d.loader.test echo init.d.loader test >/data/init.d.loader.test minfree contents: #!/system/xbin/sh echo "2469,4938,6584,33756,36971,40186" > /sys/module/lowmemorykiller/parameters/minfree

I'm currently in possession of a Droid Razr M that may be "soft-bricked". It's bootscreen won't progress beyond the red Motorola logo. I can't turn it off unless I do it via soft rebooting, in which case it just reboots and gets stuck at the logo again. I've already done a hard (factory) reset, which I assume succeeded. The device never had its bootloader unlocked, nor was it rooted. It did receive all available OS updates available for it (it only went up to some version of KitKat). This is also not a developer edition. At this point, what I want to know is: can the device have its bootloader unlocked or be rooted in any way? If not, is there anything I can do to restore this device to some kind of working order? I'm unsure as to where I would get appropriate stock images for the device (it had a Verizon-customized Android installed on it), so I was planning on flashing something like LineageOS. If there is nothing I can do for the device at this point, I'd like to know so I can avoid wasting time on it. Thanks for any assistance in advance.

I have a Droid Razr Maxx HD that just got an OTA update to KitKat. I am wondering if there is a way to remove the camera icon from the lock screen and disable the right-to-left swipe to enable the camera. I've looked and haven't seen any settings for this... if one even exists.

I have a Droid RAZR and the stock messaging app just keeps loading forever and Handcent SMS crashes when I access it. I have tried to leave it be and let it load but nothing happens. I would use SMS Backup & Restore (or another backup app) like I have in the past but since the messages don’t load the progress bar just says “NaN 0/0″ and does nothing. This is the only thing preventing me from doing a factory reset/clear data since I have lots of messages on this baby that I need to keep. I'm not sure if the messages have already been deleted, but if they were, wouldn't the apps work? This is just one of my many problems I've been running into with ICS.

I have Motorola Droid razr smart phone in which i got a virus called 'factory test' I have factory reset my phone and used antivirus for it but isn't removing from my phone what should be done to remove it completely?

I'm trying to root my Motorola Droid RAZR HD running Android 4.4.2, and I can't find any working instructions anywhere for how to root it. I've looked over the XDA Developer forums, but many results assume that the phone is already rooted. I've made sure that all Motorola drivers are updated on my computer, as well as having developer mode unlocked on the phone. I've tried following the XDA thread here: , and when I run the run.bat file, the console either gets stuck on "Waiting for device" or "daemon started successfully", after which nothing happens. I've left both results running for >30min, with no results. Is there something I'm doing wrong here with this guide, or is there a better/simpler way to root the phone? Also, do I need to factory reset my phone prior to rooting for best results, or can rooting be performed on a used phone? I have checked the rooting index, and the Droid RAZR HD isn't indexed. EDIT: I have been informed by Tamoghna Chowdhury that the above link is for Android 4.0 ICS, not 4.4.2 KitKat.

I'm having trouble with date and time on my Droid Razr M running Android 4.4.2. Every time my phone shuts off it goes back to 1970 and I can't get on the internet or any of my apps.

My Droid Razr XT910 was constantly booting and after a forced reboot still hangs here. As a next step I wiped out the data via the boot menu, i.e. a factory reset. But the phone still hangs with the boot logo. My phone is stock, not rooted. I let it constantly load over night, until the battery finished. Two days ago I tried the factory reset, but it didn't result in showing the home screen. I did several factory resets just to check. Is there any way to let the phone boot again? Thanks for your help.

I have a Droid Razr XT912 which was bricked but now recovered after some effort followed from XDA. Now I'm trying to install a new custom ROM to my device with Safestrap, but it's giving me a message about failure on every action, such as failed to create backup, failed on wipe and failed to install. (Click image to enlarge) " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> Can anybody tell me what should I do?

I bought a Motorola Razr i in the web but It turns out that the phone has an unlock pattern and now I can't contact the seller. I have read some tutorials of the web talking about the "Hard Reset" which consist in something like this: http://www.smartmobilephonesolutions.com/content/how-to-hard-reset-an-android-phone When I try to do it I never see the Menu that I souposed to. I really dont know If im doing well the process so I need someone to help me with specific instrucions of how to do this or with another solution. Thanks.

I'm looking forward to install new CM 10.1.3 to my Razr MAXX (XT910), but I see some bug reports about this version. I want to give it a try, but - is there a way to go back to the stock ROM if I don't like it? By "go back" I mean restoring it's original state, no "unlocked" icons. Currently I have 982.124.14.XT910.Retail.en.FR (Android 4.1.2).

Whenever I download the Facebook app for my Android phone (Motorola Razr D3) it shows up normal for the first time but then changes to a strange interface and then stays that way. (Click picture for larger variant) I've tried deleting it and then downloading it again and again but it keeps changing back, what is this? What should I do?