Root [Avail] How To Root/UnRoot (Full Guide) (Update 3/5)

[anthony062991]

I have the same exact problem. "Connection problem or invalid MMI code." I have reset my phone to factory condition twice, and I still get this error. I really really want to root this phone to get the crapware off and free up some space. I really hope somebody knows how to get around this error code.

If anybody having this issue figures it out please post on here.

What happens when you move on from there? Do you get any other errors? Try dong the rest of the steps and see if root works?

 

[LuckyHermit]

What happens when you move on from there? Do you get any other errors? Try dong the rest of the steps and see if root works?

Ha! Smart man! I kept getting the error message and just assumed it was failing. I checked to see if it is rooted and it is! I'm happy now. Thanks for the help!

 

[chrismbrunner]

Don't hit send. It should work fine entering just the code. And it doesn't seem to be a permanent root. If you wipe data, you have to do it again.

 

[crshocks]

this is so sad but i don't see my device listed when i first getting into CMD. what am i doing wrong?

 

[crshocks]

I got it! thanks so much for the guide!

 

[fluid]

Okay, I am not sure what the deal is here, but I have tried several things before I finally resorted to posting here.

I got this phone yesterday, I would like to root it for the purpose of getting Avast! Antitheft (and several other things I would like to run at boot without being able to be cancelled or skipped).

Anyway, I followed the directions in this thread to a tee.

When I try and use ADB to list devices, I get the following results:

c:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached


c:\Program Files (x86)\Android\android-sdk\platform-tools>

I have tried both your ADB.zip file, and downloading the actual android platform sdk (which is what I used in the quoted text above). Both versions of ADB to not see a phone attached to the machine. I cannot seem to get the platform sdk USB drivers to install as the phone is not listed in the computers device manager.

What am I missing here? Thanks much!

 

[fluid]

Solved my problem by forcing reinstall of the drivers from the device. Thanks anyway though! Looking forward to getting this done.

 

[Kma4444]

Solved my problem by forcing reinstall of the drivers from the device. Thanks anyway though! Looking forward to getting this done.

Hey Fluid, how did you reinstall the drivers? I am a newb to this and go to the point where I was going to push the SU to the phone and didn't have the SU in the right place on my computer. I then had to go and move the SU and when I tried to do that step I got an error code. I then tried to start over and now ADB shows no devices, so obviously I lost something that it needs to see the phone.

Any guidance would be appreciated.

 

[Kma4444]

And also in doing what I have done so far, I have rendered the phone mute. Not a sound will it make so I killed a driver of some kind I suppose.

 

[fluid]

Hey Fluid, how did you reinstall the drivers? I am a newb to this and go to the point where I was going to push the SU to the phone and didn't have the SU in the right place on my computer. I then had to go and move the SU and when I tried to do that step I got an error code. I then tried to start over and now ADB shows no devices, so obviously I lost something that it needs to see the phone.

Any guidance would be appreciated.

Well, when I say I forced the drivers to reinstall that may not have been the correct wording. I uninstalled the drivers from my machine in Add/Remove Programs (Programs and Features in Windows 7). They are listed as ZTE Handset USB Driver.

After that reconnect the phone and it should work fine. I also had to install the Android SDK instead of using the ADB.zip file above. Even still, the ADB.zip version does not see my phone, but the Google Android SDK version does.

Here is output from both:

C:\ADB>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

C:\ADB>

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
P736T device

C:\Program Files (x86)\Android\android-sdk\platform-tools>

I just posted that to prove that it doesn't work quite right with my phone/computer for whatever reason. I don't really care to be honest, I just think its odd. Maybe Anthony can fill us in on that. Wow that is weird, my name is Anthony too. I feel like I am talking to myself. lol.

And also in doing what I have done so far, I have rendered the phone mute. Not a sound will it make so I killed a driver of some kind I suppose.

I have run into this before with my phone, and read a lot of posts from people elsewhere saying the same thing (on rooted and non-rooted phones of different makes). I have even seen issues like this arise on non-android phones believe it or not. Best solution I have ever found for this is to just remove the battery, wait a minute, and pop it back in and reboot.

When I rooted this ZTE handset, it also went mute (including telephone calls which sucked the first time I got one).

Also ensure that the phone is not in "silent mode" (it probably is not, but check anyway).

When you do get to a point that you are going to try again, FOLLOW THE INSTRUCTIONS IN THIS THREAD AND ANY OTHER THREAD LIKE IT TO A TEE. Doing this stuff voids your phones warranty FLAT-OUT, and you definitely don't want to monkey around with a new phone that has no warranty.

Needless to say, I am rooted, and running Anthony's one.one. I like the Go Launcher, but I am not sure I like it more than adw.launcher...guess I am a minimalist. Gonna give it some time, maybe purchase the Go Launcher EX and see if that helps me get into it more.

FREAKING THANK YOU ANTHONY. You have made this phone a LOT better, not that it was bad to begin with... it just got a lot better because of your work. I cannot wait for one.two

 

[Kma4444]

Thanks Fluid, I did manage to get it all working again, though I'm sure my method was a tad, well, barbaric. I did a T card reboot and just returned the phone to factory defaults. Not a big deal other than losing a few apps and such. I've only had the thing a couple weeks so it wasn't a huge deal. At least now I have an SD card setup that I can drop in and reset it if I screw up again.

I'm sure most of my problems are because I am completely new to doing this. Some of the minutia that is completely obvious to folks who have done these before are lost on me. Just want to get it all figured out and working without making the phone rubbish.

I like the challenge just wish some of it was more clear to me. I'll get there.

Thanks again

 

[Kma4444]

Well, I got it rooted, not too much trouble. Funny thing, when I got to the reboot step, when it turned back on it was again mute. Like you said yours was, no speaker, no sounds at all. Root check says I'm rooted but sound is gone. I tried leaving the battery out for a while and maybe I will try that some more.

I'd hate to have to unroot it again since it seems to be alright other than being useless as a phone. Pretty funny really.

Thanks again

 

[Kma4444]

OK, so happy to say, it now speaks again. Here's a confession from a rookie, noob, new B!!! I stopped after I pushed the su command. I thought the rest of the directions were in case the push command didn't work. After I looked at it a few times and looked at how the command list should look, it was obvious. So any other beginners out there, the command list continues after the push line. Not very bright on my part to be honest. The sound came back on reboot after doing the rest of the root sequence.

Now to figure out how to get rid of the AT&T stuff I don't want.

Thanks for your patience in watching me fumble around. Told you I'd get it, now I'm like graduated from 1st grade, I'm educated!!!!

 

[fluid]

OK, so happy to say, it now speaks again. Here's a confession from a rookie, noob, new B!!! I stopped after I pushed the su command. I thought the rest of the directions were in case the push command didn't work. After I looked at it a few times and looked at how the command list should look, it was obvious. So any other beginners out there, the command list continues after the push line. Not very bright on my part to be honest. The sound came back on reboot after doing the rest of the root sequence.

Now to figure out how to get rid of the AT&T stuff I don't want.

Thanks for your patience in watching me fumble around. Told you I'd get it, now I'm like graduated from 1st grade, I'm educated!!!!

if you can afford to replace the phone if you manage to murder it then i would push for the next step. it isn't hard, but just like everyone else suggesting you modify something, i am not responsible if it bricks your phone, or kills your pets.

the thread that i have found in this forum that lists everything that is "safe" to remove is here:

http://androidforums.com/avail-all-things-root/483369-apps-safe-remove-do-not-remove-email-apk.html

i personally suggest changing the recovery rom with clockwork mod, and that thread can be found here:

http://androidforums.com/avail-all-...0-stock-recovery-working-dl-links-2-11-a.html

stick the clockwork mod zip, and the stock recovery zip on the root of the sdcard for convenience of having both, but i dont ever see myself leaving clockwork mod now that it is installed and working

there is 1 custom mod out for this phone once you get it rooted, and honestly from what i can tell MOST of the things I am mentioning (if not all of them) were done by the same person. this mod overclocks the phone a bit as needed to make things a bit more responsive, and removes all of the "bloat" that comes on these phones. it changes the stock launcher out for GO Launcher EX, and gets rid of a lot of stock functionality (that is all replaced by the apps mentioned in the thread, just get them when you get the install done)

the only thing im missing out of it is the calendar, but i will buy the one mentioned in the thread, its under $3, and looks freaking amazing

http://androidforums.com/avail-all-...-one-two-overclock-working-update-2-23-a.html

currently the only download for that mod i could find is one.one, even though the thread says it is one.two. i believe that one.two will come soon (i hope)

again, these phones are really inexpensive, and pretty good to learn the ins-and-outs of droids (and linux for that matter if you get into terminal use at all), so if you can afford to replace the phone, do not be afraid to try things.

 

[Kma4444]

I really appreciate the help and suggestions. I already did the clockwork recovery, that went fine and using Titanium Backup I have been able to remove a lot of the useless AT&T stuff. I got this phone to use with Straight Talk and picked it because it was cheap enough that if it didn't work out or I rendered it useless, I could give it the old float check and if it sank, I was alright with that.

I will look into the mod and give it a try, sounds like the goods!

Thanks again and hopefully I at least gave you guys a little something to laugh about.

 

[Motorhead1991]

I was able to root my avail by just dialing thr write mount dev code then updating the binary on superuser. It worked for some reason...

 

[Karroon]

Edit:
Got it to work, had to get cmd to run as administrator, and Win 7 likes to hide it

 

[Natetd26]

When I get to this part:

adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"

it says permission denied!! Any help I would be very greatful!!

 

[Thrive]

It should be similar to what I have. I have windows 7 and ubuntu installed on two different laptops. You need to have android sdk installed in your pc. Download all the files from here and put it into your tools folder from the sdk. Then cd ./path/to/adnroid/sdk/tools/ mine looks like this: cd ~/android-sdk-linux_x86/platform-tools . Then try to type ./adb devies and you should see your device listed. You should be able to run the commands to root from there. I hope this helps.

So, I got Android SDK installed, with Eclipse and such. Got adb running. I didn't see the Avail SDK package, so I just downloaded everything they had. Went to search for my phone and got:

~/SDK/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached 
????????????    no permissions

No idea where to go from here. Working on Ubuntu 11.10 now, BTW. Decided I needed a dual-boot.

 

[anthony062991]

So, I got Android SDK installed, with Eclipse and such. Got adb running. I didn't see the Avail SDK package, so I just downloaded everything they had. Went to search for my phone and got:

~/SDK/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached 
????????????    no permissions

No idea where to go from here. Working on Ubuntu 11.10 now, BTW. Decided I needed a dual-boot.

Look at this guide. It will tell you how to fix that issue. It is really easy. I tried with both ubuntu and mint and both works great.
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10 - Now with Ubuntu 11.10 ! - xda-developers

Edit:
You do not need Linux in order to use these commands. You can use windows and it will work just fine.

 

[rkalajian]

I'm having an issue trying to root this damn phone, and was wondering if anyone knew the solution. When I dial *983*7668# and wait, nothing happens. If I click the send button I then get the "Connection problem or invalid MMI code" message. Either way, I can't continue on with the process. I get "cannot create /data/local.prop: permission denied"

 

[anthony062991]

I'm having an issue trying to root this damn phone, and was wondering if anyone knew the solution. When I dial *983*7668# and wait, nothing happens. If I click the send button I then get the "Connection problem or invalid MMI code" message. Either way, I can't continue on with the process. I get "cannot create /data/local.prop: permission denied"

Have you tried to reboot or just pull out the battery and start from the top again? If that doesn't work try using the T-Card Upgrading tool I posted in the other thread. Update the device and then try rooting again.

 

[rkalajian]

Have you tried to reboot or just pull out the battery and start from the top again? If that doesn't work try using the T-Card Upgrading tool I posted in the other thread. Update the device and then try rooting again.

Damn. The T-Card upgrade did the trick. I was able to start the process over again, and am rooted!

 

[Thrive]

So, I don't think my phone's showing up properly. lsusb gives me:

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0461:4de7 Primax Electronics, Ltd 
Bus 001 Device 015: ID 19d2:1354 ONDA Communication S.p.A.

I imagine that the one at the bottom is the phone, because it's the only one that goes away when I unplug the phone from the USB port. So I wrote my 99-android.rules as such:

SUBSYSTEM=="usb", ATTRS{idVendor}==19d2:1354, SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"

Restarted udev as per the instructions, and my output for ./adb devices is still:

# ./adb devices
List of devices attached 
????????????    no permissions

Wat do? I'm about to smash this goddamn thing against a wall.

 

[anthony062991]

So, I don't think my phone's showing up properly. lsusb gives me:

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0461:4de7 Primax Electronics, Ltd 
Bus 001 Device 015: ID 19d2:1354 ONDA Communication S.p.A.

I imagine that the one at the bottom is the phone, because it's the only one that goes away when I unplug the phone from the USB port. So I wrote my 99-android.rules as such:

SUBSYSTEM=="usb", ATTRS{idVendor}==19d2:1354, SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"

Restarted udev as per the instructions, and my output for ./adb devices is still:

# ./adb devices
List of devices attached 
????????????    no permissions

Wat do? I'm about to smash this goddamn thing against a wall.

Yes it is the last one there.
Try this:
./adb kill-server
sudo ./adb start-server
./adb devices