How To Root


An Android mb526


Access MB526's rear end




The documents contained here are to be used at your own risk.

Motorola Smartphone

How to Remove a Pesky Account WITHOUT doing a factory reset!!

I rooted my Android Smartphone a motorola MB526. I had to do this because I needed to remove a mail account that was no longer relevant. When I went to remove the account my phone complained that other applications were attached and it went onto inform me that to do this I would need to do a factory reset first. Major bummer, this would mean losing all the changes I had made to my phone, losing all my contacts and photos, videos, apps along the way. It would be like reinstalling your operating system on a laptop.


I searched the internet and found a neat site that had instructions and the required bits and pieces to root the phone. By rooting my phone, I mean obtaining superuser privileges to the Android operating system, which is really just a minix or mini unix operating system. By obtaining superuser privileges I was able to delete the annoying email account (which was constantly trying to connect and couldn't because the owners had removed it) without doing a factory reset and without losing any changes I had made to the phone up to that moment.


So I figured there may be others out there that could do with this intel.


The website I found was great, but it missed a few important pieces to the puzzle which I'll include here.


There are other nice things about gaining root access to your phones operating system as well as really dangerous things too.



Steps To Root MB526

  1. Export your contacts as a csv file so you can import later if something goes wrong when you delete that annoying email account.
  2. Download the necessary software to enable you to access MB526 Android operating system. I have version 2.3. The software is ADB.exe and runs in Windows operating system. You'll be using this to access the MB526 connected to a PC or laptop's USB port.
  3. Connect the MB526 to the USB port of the computer running Windows 7 or XP operating system (I used Windows 7) should recognise the MB526 and install the necessary drivers automatically.
  4. Run the following commands. The site I used had a batch file called "Click to root your DROID 3.bat", but I found that his didn't work for me because one of the commands didn't work. Mainly because I had already tried Gingerbreak, which is also supposed to magically root your phone but it failed for me.
Files You need to root MB526 and Delete an Email Account
Unzip these files in a new directory on the computer hard drive that the smartphone will be connected to. I created a directory c:\tmp\droid3-root-mb526-for-xp and put my unzipped files there.
Files are:
Superuser.apk 192kb
adb.exe 566kb
AdbWinApi.dll 94kb
AdbWinUsbApi.dll 60kb
busybox 1824kb
su 26kb
sqlite3.exe 460kb used to delete the account
sqlite3_analyzer.exe 1285kb used to analyse accounts database.
Compressed Archive in ZIP Format 2.2 MB

Commands to Execute to Enable Root Access to Android

These commands will consist of a command and explanation, and expected response. So you will know if something failed. At this point the phone has connected successfully to your USB port and connection has been successfully been established using the Moto Phone Portal, mine is The files needed have been downloaded and unzipped.

  1. Start shell i.e. run cmd.exe
  2. Change directory to the location of the unzipped files. e.g. cd c:\tmp\droid3-root-mb526-for-xp
  3. adb wait-for-device  - See if the android debug bridge software can connect to the MB526 phone connected to the USB port.
  4. adb kill-server   - Kill any hanging adb servers. Precautionary step. I found this step was not necessary.
  5. adb shell rm /data/local/12m.bak  - Remove this backup file from the phone if it exists. Will respond with an error message if it doesn't exist. This can be ignored.
  6. adb shell mv /data/local/12m /data/local/12m.bak - Backup the 12m directory by copying it to 12m.bak.
  7. adb shell ln -s /data /data/local/12m  - Create a pointer 12m to point to /data.
  8. adb reboot   - Restart the phones operating system so those changes take affect. The phone will restart. Wait till is has restarted completely and reconnected with the host computer before continuing.
  9. adb wait-for-device  - Make sure we can connect.
  10. adb shell rm /data/local/12m  - remove the pointer file created in step 7.
  11. adb shell mv /data/local/12m.bak /data/local/12m  - Restore 12m from backup created in step 6.
  12. adb shell rm /data/local.prop.bak  - remove any existing prop.bak file. Ignore errors that say no such file exists.
  13. adb shell mv /data/local.prop /data/local.prop.bak  - remove and backup the current props file.
  14. adb shell echo "ro.sys.atvc_allow_netmon_usb=0" ^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_netmon_ih=0" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_res_core=0" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_res_panic=0" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_all_adb=1" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_all_core=0" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_efem=0" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_bp_log=0" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_ap_mot_log=0" ^>^> /data/local.prop
    adb shell echo "ro.sys.atvc_allow_gki_log=0" ^>^> /data/local.prop 
    - Creates new local.prop file with entries detailed in between the quotes.
  15. adb reboot  - Restart the phones Android operating system so the new props file can take affect.
  16. adb wait-for-device - wait and make sure we can again connect to the phone after the reboot
  17. adb remount - mount sdcard
  18. adb push busybox /system/xbin/busybox  - copy busybox software from the pc to the phone
  19. adb push su /system/xbin/su   - copy su to the phone
  20. adb push Superuser.apk /system/app/Superuser.apk - copy Superuser android package to the phone
  21. adb shell chmod 4755 /system/xbin/su - change permissions so su can run
  22. adb shell chmod 755 /system/xbin/busybox - similarly for busybox
  23. adb shell chown system.system /data  - ensure data is owned by system user
  24. adb kill-server


You should now be able to run adb shell and get a # prompt that confirms you are the superuser.



How To Remove a Pesky Account WITHOUT doing a Factory Reset

Accounts.db is an SQLITE database and can be copied to a PC from your phone. This has the account configs and will have the account you want to remove.


Use SQLITE3.exe in the download kit to access account.db

Use delete sql command to delete the account you don't want.

Backup account.db first before you do this.


delete from accounts where Name='vodophone....';




Now simply overwrite the accounts.db with the one you just edited.


To find accounts.db you can do a search through your phone by using the windows explorer connection via



or use adb shell

then change directory to root '/'

issue an ls command.

This will list all the directories and files on your phone.

Copy it to a text file i.e.

ls > files.txt

then edit the file and search for accounts.db


You also should backup data.db this has all your phone contacts. This is also an SQLITE3 db.


Well that's about it.


If you need to ask me any questions feel free. or


Email me here

Note: Please fill out the fields marked with an asterisk.