July 3rd, 2012, 09:39 PM
Thread Author (OP)
Join Date: Dec 2011
Device(s): Huawei Ascend 2
Carrier: Not Provided
Thanked 9 Times in 6 Posts
How to root with Muve 2.3.5/2.3.6 - READ HERE
Since rooting is such a problem on the Muve update, I decided to make this thread. I already posted this in the other thread, but people don't seem to want to read through the thread to see if it's already been resolved.
This will work regardless of whether or not 2.3.5 or 2.3.6 was preinstalled. It will also work in the original 2.3.3 (pre-Muve) Stock ROM, provided you want to install CWM Recovery (not necessary for 2.3.3 users, just use the original rooting thread). This has already been confirmed by several users (and not just at this forum). I even did it several times myself just to make sure it works. (I'm not sure if any US Cellular users have tested it, but I know for fact it works for Cricket users on the Ascend 2 M865)
To navigate in recovery for the following steps, use the volume buttons to move up and down. Both the Menu button and Power button can be used to select/confirm stuff. The back button can be used as a shortcut to take you back one menu.
- Download the rooting zip. You should end up with an update.zip file in the location your browser saves stuff to.
- Place the zip on the root (top level) of your phone's SD card. It should look similar to E:\update.zip on Windows or /mnt/sdb1/update.zip on Linux and Mac.
- Install ClockWorkMod Recovery. Instructions at ClockWorkmod Recovery - PlayfulDroidz Wiki . The fastboot method is easiest for most users. If it hangs during install via fastboot, make sure you are running the install script as an administrative user. (Linux and Mac call this user root, though running via sudo is also valid)
- Boot into recovery (with phone off, hold Volume Up + Power until the menu appears, about 10 seconds).
- Go to the Advanced menu.
- Wipe Dalvik Cache, confirm.
- Fix Permissions.
- Go back to main menu.
- Wipe Cache, confirm.
- Apply update from zip, confirm.
- Reboot (it will take a little longer because it needs to rebuild the Dalvik Cache, but will return to normal afterward).
- Check to see if the Superuser app is installed. If not, try again.
Once again, this should work, and has been confirmed by several users.
Last edited by Pikidalto; July 15th, 2012 at 05:11 PM.