Dial *983*7668# on your phone. This does a few things, it mounts /system as writable on boot, and creates the loglast1.tar.gz.
Wait about 10 seconds, then continue.
I guess some people are running into an issue when tryping in the code:
Originally Posted by rockyj Hello when i enter the number *983*7668# into my phone I get the message "Connection problem or invalid MMI code." This is after the initial messages... Is this a problem or is this known to happen? Help would be GREATLY appreciated! Thanks!
type it in and if you get that error msg then ignore it and move onto the next step anyways!
Heads up at the end, When Unrooting, Dont drag the whole stockapps folder in and click replace. It will delete something important momentarily, and make the phone unusable. GREAT.
Heads up at the end, When Unrooting, Dont drag the whole stockapps folder in and click replace. It will delete something important momentarily, and make the phone unusable. GREAT.
Sorry, its for people who forgot to back up one and or several of there apps. i just put the whole system/app folder there. Maybe I will update all att apps. one at a time so people dont get confused with the whole folder.
Sorry, it is vary important that USB Debugging and unknown sources are always on while rooted.
I'm new to Android (and smartphones) and have some questions with rooting...
First off, with your statement here, do you mean USB Debugging... must be turned on at all times after you root or just when you root? I just want to be clear on that. If the former, what happens if you should accidentally turn USB Debugging... off?
You posted the other thread on apps that can safely be removed. The biggest downfall to my phone is currently Facebook, Twitter, and a few other large stock apps that I will never use and are hogging up space. Do you actually delete the files or will it give you an option to uninstall the apps after root?
There are a few stock apps that I do want to keep, but they are taking up space on the internal memory. Along with that, it seems that my most used of my downloaded apps (Winamp, iHeart Radio, a MS Office app, and other large apps) installed on the internal memory and I can not move them to the SD card. Will I be able to move the stock apps that I want to keep to SD and will I be able to move some of the downloaded apps I mentioned to the SD and still have functionality with them and the phone? I don't have the understanding on why many of the apps install to the internal memory and can't be moved with the phone in stock form.
I am now stuck at about 5mb available on the internal memory, but I really want to keep all the apps I've downloaded and can't move to the SD card because I will use them every day (just installed the Office app for viewing and editing Excel files today hoping it would allow to move to SD and the 15mb it is took up all the rest of my free space on internal memory.) I'm scared about the rooting thing, but desperately need the space on the internal memory back as there are yet more apps that I really want but can't get because of lack of space.
I know absolutely nothing about the custom ROMs I keep seeing info about and don't want to do anything like that right now, but I really just want to be able to get stuff off the internal memory and stored onto the SD card.
I'm new to Android (and smartphones) and have some questions with rooting...
First off, with your statement here, do you mean USB Debugging... must be turned on at all times after you root or just when you root? I just want to be clear on that. If the former, what happens if you should accidentally turn USB Debugging... off?.
USB Debugging is intended for development purposes only. It pulls data between your pc and phone and phone to pc. Some rooted apps are required for you to enable usb debugging like gingerbreak for example. You need to enable this for the app to run commands to the phone to unroot the device. It is fine if usb debugging is turned off, but some rooted apps may not work properly and or can cause your phone to be bricked. Here is how to enable it: Press HOME > MENU, and then tap Settings > Applications > Development and make sure there is a check.
Quote:
Originally Posted by mrodgers
You posted the other thread on apps that can safely be removed. The biggest downfall to my phone is currently Facebook, Twitter, and a few other large stock apps that I will never use and are hogging up space. Do you actually delete the files or will it give you an option to uninstall the apps after root?
You will have to manually delete the apps one by one once rooted.
Quote:
Originally Posted by mrodgers
There are a few stock apps that I do want to keep, but they are taking up space on the internal memory. Along with that, it seems that my most used of my downloaded apps (Winamp, iHeart Radio, a MS Office app, and other large apps) installed on the internal memory and I can not move them to the SD card. Will I be able to move the stock apps that I want to keep to SD and will I be able to move some of the downloaded apps I mentioned to the SD and still have functionality with them and the phone? I don't have the understanding on why many of the apps install to the internal memory and can't be moved with the phone in stock form.
I am now stuck at about 5mb available on the internal memory, but I really want to keep all the apps I've downloaded and can't move to the SD card because I will use them every day (just installed the Office app for viewing and editing Excel files today hoping it would allow to move to SD and the 15mb it is took up all the rest of my free space on internal memory.) I'm scared about the rooting thing, but desperately need the space on the internal memory back as there are yet more apps that I really want but can't get because of lack of space.
The stock apps that come with the phone can not be moved to the SD card at all. EDIT: You can delete maps, gmail, and youtube. Reinstall from the market. Then you can download an app called Titanium Backup . This will allow any apps you downloaded to force them to install to the SDcard once your phone is rooted. At this moment I have 89.39MB freed up in the internal storage.
Quote:
Originally Posted by mrodgers
I know absolutely nothing about the custom ROMs I keep seeing info about and don't want to do anything like that right now, but I really just want to be able to get stuff off the internal memory and stored onto the SD card.
There is no custom ROMs out for this device at the moment. If you want to move apps to your SDcard. My advice for you is to just root your phone. Just folow the steps above and you should be fine.
Last edited by anthony062991; January 19th, 2012 at 11:48 AM.
I dial the number, next step, then reboot the phone. At this step...
adb push su /system/xbin/su
I get an error saying, cannot stat 'su': No such file or directory
I downloaded the su file and put it in the adb folder. Any reason why? Can I start over?
According to the app "Root Access Basic", I have root access. What does the "SU" file do as I couldn't go on from that point above?
1a. You need the su file for superuser app in the market. Superusers is an app required for root users to manage system and rooted apps to work properly. You can Start from the top and redo the commands until everything works. It gave me errors my first few times. I kept retrying and it finally went through.
1b. adb push su /system/xbin/
try going to the next step if it goes through.
1c. you can manually put the su file into /system/xbin/ with Es File Explorer if it lets you and just try moving on to the next step.
If 1a doesn't work you can try 1b. If that does't work try 1c. One of these steps should get you in the right direction.
1a. You need the su file for superuser app in the market. Superusers is an app required for root users to manage system and rooted apps to work properly. You can Start from the top and redo the commands until everything works. It gave me errors my first few times. I kept retrying and it finally went through.
1b. adb push su /system/xbin/
try going to the next step if it goes through.
1c. you can manually put the su file into /system/xbin/ with Es File Explorer if it lets you and just try moving on to the next step.
If 1a doesn't work you can try 1b. If that does't work try 1c. One of these steps should get you in the right direction.
SUCCESS!!! I had a lot of difficulty with this also. Here was my workaround:
1. Download Explorer v1.0 from Speed Software (this allows you to view and edit the root file system, including hidden files, which the default and many 3rd party file managers refused to show)
2. Move the the su file previously downloaded to your PC, to your phone's external micro SD card via SD adapter inserted into your PC.
3. Pull the micro SD out of your PC and put back into your phone.
4. Open Explorer app. If necessary, create directory /system/xbin/
Then, copy and paste the su file to that directory.
Ok so I downloaded adp, but I have no idea how to use it. How do input commands? How do I even bring up the command prompts? Help would be greatly appreciated...
When I try using "adb push" it says SU doesn't exist. ES file manager wont let me put it in, nor will Explorer by Speed Software. Says that it can't send it to a read only directory. What am I doing wrong? This is my first time rooting a device, first android phone (had it for a few months).
EDIT: Nevermind, got it figured out. Forgot to reboot after entering the number.
Last edited by Wuverul; January 30th, 2012 at 08:24 PM.
I was wondering if you may have a guide to doing this on Linux? I'm running OpenSUSE. Thanks in advance for the reply!
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.
Last edited by anthony062991; February 1st, 2012 at 10:21 AM.
Hello when i enter the number *983*7668# into my phone I get the message "Connection problem or invalid MMI code." This is after the initial messages... Is this a problem or is this known to happen? Help would be GREATLY appreciated! Thanks!
Hello when i enter the number *983*7668# into my phone I get the message "Connection problem or invalid MMI code." This is after the initial messages... Is this a problem or is this known to happen? Help would be GREATLY appreciated! Thanks!
I am not sure about this problem. Maybe try taking out your battery and put it back in. Then start from the top again.
If that does not work then try a master reset from the settings. This will delete everything and your phone will come back on like it is brand new. Then try from the top. Other wise I have no idea? I hope this helps.
Hello when i enter the number *983*7668# into my phone I get the message "Connection problem or invalid MMI code." This is after the initial messages... Is this a problem or is this known to happen? Help would be GREATLY appreciated! Thanks!
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.
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?
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!
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:
Quote:
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
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.
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.
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:
Quote:
Originally Posted by ADB.zip Version
C:\ADB>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\ADB>
Quote:
Originally Posted by Android-SDK version
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
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.
Quote:
Originally Posted by 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.
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
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.
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.
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!!!!
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:
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
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.
The Following User Says Thank You to fluid For This Useful Post:
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.
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:
Code:
~/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.
Last edited by Thrive; April 2nd, 2012 at 03:07 AM.
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:
Code:
~/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.
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"
Last edited by rkalajian; April 2nd, 2012 at 01:29 PM.
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.
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!
So, I don't think my phone's showing up properly. lsusb gives me:
Code:
# 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:
So, I don't think my phone's showing up properly. lsusb gives me:
Code:
# 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:
1Likes
How To Root/UnRoot (Full Guide) (Update 3/5)
This should be added to the all things root 
Entering the number
