What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Latest Update

Andriod and Forum Newbie

This is my first post since I’ve been a long time Sprint Blackberry user but recently switched to a Droid Pro with Verizon. As of 4/14, (I’m not sure what system version it was on) in order to prevent bloat from running I was able to root using z4Root 1.3.1. I then installed System App Remover 4.12 to “disable” system bloat rather than uninstalling it. I feel that this works better than Titanium or Bloat Freezer.

On 4/17 prior to doing a user initiated OTA update to 2.26.60.XT610, I “re-enabled” the system bloat, and z4 un-rooted. The update worked fine but messed up my corporate sync contact links. I was able to recreate my corporate sync account and play with one of the contacts until all the rest of the contact links corrected itself. Again, I was able to z4Root and “disable” bloat after the 2.26.60 update.

On 4/22 around 2:00AM this morning upon receiving notice of a server OTA 3.8.7.XT610 push, I once again re-enabled bloat and z4 un-rooted prior to updating. The update went fine with no sound or corporate sync problems with Exchange but z4 root no longer works just kicking me out of the app after selecting a root option.

Therefore, I tried the aRoot method mentioned in this thread. As a last resort, I had to install the Motorola ADB drivers on my PC for it to work. USB Debugging is turned on and it doesn’t seem to matter if I’m in “USB Mass Storage” or "Charge Only" modes since I tried both. aRoot runs fine, installs Superuser, and reboots the phone but System App Remover 4.12 doesn’t see the phone as being rooted. If I run Superuser, it says there is an update but fails to install creating an empty zip file on the SD card. Fortunately, the aRoot un-root works as expected. Am I missing a step or does someone know of another way to fully root 3.8.7.XT610 successfully?

BTW, z4Root 1.3.1 doesn’t work on a Samsung Galaxy Tab SCH-1800 running Baseband version S:1800.0.3V.DL21, Kernel version 2.6.32.9 either. Does anyone have success rooting this tablet?
 
I've tried a few times now and my phone tells me update failed upon reboot. I'm not sure what I've done to my phone to do this. I even tried un-freezing everything and moving all my apps to internal memory and still the update fails. Not sure what to do at this point.

Mine told me the update failed, but I turned the phone off and back on and it didn't say the update failed again. The operating system shows to be the new one, so I'm assuming it's working.
 
I'm still running 2.26 even after a hard boot. So mine failed. I have a copy of the zip so I can force an update via CWR but several others here at work seem to be having exchange errors now with their phones. Since it looks like I can't do an OTA update i'll wait until next week to see what happens with them before forcing the update.
 
Battery Issues

I just updated to 3.8.7 this morning, I see a lot of people saying their battery lives are extended, mine however, barely lasted 4 hours today. I never did have exchange activesync issues and I have 3 exchange accounts synced to this phone. The phone actually gets warm now as if it's constantly running some high performance program. When I go into battery manager the big user is ".com.motorola.service.ma(something but it cuts off after that)" at 35%. The android system is next at 23%. Anyone else experience your battery draining much faster?
 
I just updated to 3.8.7 this morning, I see a lot of people saying their battery lives are extended, mine however, barely lasted 4 hours today. I never did have exchange activesync issues and I have 3 exchange accounts synced to this phone. The phone actually gets warm now as if it's constantly running some high performance program. When I go into battery manager the big user is ".com.motorola.service.ma(something but it cuts off after that)" at 35%. The android system is next at 23%. Anyone else experience your battery draining much faster?

Not this time around, but a similar phenomenon used to happen to my OG Droid whenever I got an OTA update. A factory reset fixed it then... maybe you want to try the same? I am assuming you've already restarted/pulled the battery.
 
My update a couple of hours ago failed. Not sure if it has anything to do with Clockwork Recovery that I have on my phone.

Sent from my drUid PRO using DroidForums
 
My update a couple of hours ago failed. Not sure if it has anything to do with Clockwork Recovery that I have on my phone.

Sent from my drUid PRO using DroidForums

If you're rooted and have deleted or moved any of the stock apps, your updates will usually fail. Best way I've found to update is put back the apps and unroot.
 
I just updated to 3.8.7 this morning, I see a lot of people saying their battery lives are extended, mine however, barely lasted 4 hours today. I never did have exchange activesync issues and I have 3 exchange accounts synced to this phone. The phone actually gets warm now as if it's constantly running some high performance program. When I go into battery manager the big user is ".com.motorola.service.ma(something but it cuts off after that)" at 35%. The android system is next at 23%. Anyone else experience your battery draining much faster?

Not this time around, but a similar phenomenon used to happen to my OG Droid whenever I got an OTA update. A factory reset fixed it then... maybe you want to try the same? I am assuming you've already restarted/pulled the battery.


Yeah I pulled the battery, didn't change anything, I'll go ahead and do the factory reset and see if that resolves it.
 
Just Unzipit/unrar and you will find inside it a batch called aroot.bat for rootingand unroot.bat for unrooting

This is not working for me. The CMD runs, but the phone never reboots. What am I doing wrong?
Settings - Applications - Development - Check Allow USB Debugging.

I had the same issue until I realized I'd turned off USB Debugging. After that, it worked for me first try with my phone connected in "Charge Only" mode. You can select this by pulling down the status bar and tapping the USB item when it's plugged in.

Still no luck. I've done everything exactly as instructed, but the phone doesn't reboot. I've extracted the files to my desktop and clicked on aroot.bat from my desktop. The phone has usb debugging enabled and the cmd prompt runs, but the phone won't reboot. The phone is connected in charge only mode as well. Can someone tell me what I'm doing wrong?
 
This is not working for me. The CMD runs, but the phone never reboots. What am I doing wrong?
Settings - Applications - Development - Check Allow USB Debugging.

I had the same issue until I realized I'd turned off USB Debugging. After that, it worked for me first try with my phone connected in "Charge Only" mode. You can select this by pulling down the status bar and tapping the USB item when it's plugged in.

Still no luck. I've done everything exactly as instructed, but the phone doesn't reboot. I've extracted the files to my desktop and clicked on aroot.bat from my desktop. The phone has usb debugging enabled and the cmd prompt runs, but the phone won't reboot. The phone is connected in charge only mode as well. Can someone tell me what I'm doing wrong?

I had the same issue until I updated to the latest Motorola USB drivers found here:

USB and PC Charging Drivers - Motorola Mobility, Inc. USA

After installing those, aRoot worked on the first try.
 
Settings - Applications - Development - Check Allow USB Debugging.

I had the same issue until I realized I'd turned off USB Debugging. After that, it worked for me first try with my phone connected in "Charge Only" mode. You can select this by pulling down the status bar and tapping the USB item when it's plugged in.

Still no luck. I've done everything exactly as instructed, but the phone doesn't reboot. I've extracted the files to my desktop and clicked on aroot.bat from my desktop. The phone has usb debugging enabled and the cmd prompt runs, but the phone won't reboot. The phone is connected in charge only mode as well. Can someone tell me what I'm doing wrong?

I had the same issue until I updated to the latest Motorola USB drivers found here:

USB and PC Charging Drivers - Motorola Mobility, Inc. USA

After installing those, aRoot worked on the first try.

I appreciate that, but I've already installed these drivers... I did that last night when I couldn't get aroot to work.
 
I've tried a few times now and my phone tells me update failed upon reboot. I'm not sure what I've done to my phone to do this. I even tried un-freezing everything and moving all my apps to internal memory and still the update fails. Not sure what to do at this point.

Are you still rooted? I believe the issue may be if you still have Clockwork Recovery on your phone....some people have said that their rooted phone was able to install the update, but most have not been able to...

I unrooted prior to the update coming out and followed the following steps to unroot completely:


If you decide to unroot you should "unfreeze" any bloatware apps that you froze....
  • then uninstall the Droid 2 Bootstrapper....
  • then use Root explorer to go to system/bin and:
    • delete file named "hijack"
    • delete file named "logwrapper"
    • rename file named "logwrapper.bin" to "logwrapper"
  • then use Z4Root to "unroot" by using uroot button
 
I just updated to 3.8.7 this morning, I see a lot of people saying their battery lives are extended, mine however, barely lasted 4 hours today. I never did have exchange activesync issues and I have 3 exchange accounts synced to this phone. The phone actually gets warm now as if it's constantly running some high performance program. When I go into battery manager the big user is ".com.motorola.service.ma(something but it cuts off after that)" at 35%. The android system is next at 23%. Anyone else experience your battery draining much faster?

Not this time around, but a similar phenomenon used to happen to my OG Droid whenever I got an OTA update. A factory reset fixed it then... maybe you want to try the same? I am assuming you've already restarted/pulled the battery.


Yeah I pulled the battery, didn't change anything, I'll go ahead and do the factory reset and see if that resolves it.


Yeah that did the job, installing back all my apps now, but so far the .com.motorola.service.main is staying at only about 8%, with the android system at 3%
 
Back
Top