Database Users

[Q] Root Help myTouch 4G (SOLVED)

Hey there everyone. I have a myTouch and when I try and root using visionary it says that I am already rooted but if i go into the terminal emulator and I typer in su it says permission denied. I already wiped the os, cache, and sd. Please help
Thanks
macfan74318

Use the Manual method found here: http://forum.xda-developers.com/showthread.php?t=834225

But the problem is that I can not even get temp root. VISIONary says there is root but the terminal says permission denied when I try and get root access.

Try installing the superuser app from the market
Sent from my anti titanic

Thanks it worked perfectly.
Thanks
macfan74318

macfan74318 said:
Thanks it worked perfectly.
Thanks
macfan74318
Click to expand...
Click to collapse
Edit you post as solved.

thelamacmdr said:
Try installing the superuser app from the market
Sent from my anti titanic
Click to expand...
Click to collapse
macfan74318 said:
Thanks it worked perfectly.
Thanks
macfan74318
Click to expand...
Click to collapse
Seriously?! That's it? Ha!

What?
Why do you think that this is so funny. You have been their at one point and who knows someone else could have the problem and now they know what to do. Attitudes like this is what will lead to the downfall of the android developer community.

macfan74318 said:
Why do you think that this is so funny. You have been their at one point and who knows someone else could have the problem and now they know what to do. Attitudes like this is what will lead to the downfall of the android developer community.
Click to expand...
Click to collapse
No dude you got me wrong. I'm just amused that the problem is really solved that simply. It would never have occurred to me to try that. I've only just started playing with visionary on my phone about half an hour ago so I have virtually zero experience rooting the mt4g so far.
Was not talking **** but I totally appreciate your supportive attitude and I agree with your statements. I was a super-noob and am still pretty darn noobish. I actually enjoy helping where I can and I put links in my sig in case they come in handy for others.

Oh... Sorry for coming off so harsh.
Do you have any questions or need any help?
macfan74318

Since this is no longer development related, I am moving to General section

Okay. Sorry for being off topic. But if you need help please ask here.
Sent from my HTC Glacier using XDA App

macfan74318 said:
Oh... Sorry for coming off so harsh.
Do you have any questions or need any help?
macfan74318
Click to expand...
Click to collapse
No worries, your heart was in the right place. I think I'm ok for now. Going out of town this weekend so won't be able to play with this until probably tuesday night.
Also kinda waiting for CM6 to be available for our phones.

Yup Cyanogen Mod 6.1 will be amazing. They have already booted it but the status of the ROM is unknown

macfan74318 said:
Yup Cyanogen Mod 6.1 will be amazing. They have already booted it but the status of the ROM is unknown
Click to expand...
Click to collapse
Well it boots, but nothing works yet. Give them time.

Well kmobs says that "more will be released tonight". Maybe we will get a nightly build!

Can someone help me root my mt4g.i need wifi tethering.
Sent from my HTC Glacier using XDA App

How to root
First Question? Do you get and OTA Update (You can check by going to System -> About Phone -> Software Information. If you have gotten the update then under Android version it would say 2.2.1.
Next you need to follow this guide. http://forum.xda-developers.com/showthread.php?t=834225
What I did is I downloaded the program droid explorer (PC) (http://de.codeplex.com/) and it set up the whole adb system. All I did was to plug the phone in and copy the two files using Super Manager (Phone) and the ran the 2 commands minus the adb part of the command.
Download Visionary (http://android.modaco.com/content/t...350/10-nov-r12-test-visionary-one-click-root/) and then copy the apk file to your sd card.
Then mount your phone to your pc and copy the two files on to the root of your SD Card
Then open up super manager and go to settings and Enable ROOT Function, and show hidden files.
Then go the the copied files and cut them (Hi-light check box and hit the pair of scissors)
The keep navigating up one level until you cant go up anymore.
Then navigate to data
Then inside of data select local and paste the files there.
Then plug your phone in but dont mount it ( When you plug in it pull down the notification bar and select USB CONNECTION Change Type and change it to charge only.
The open Droid Explorer and it will recognize your phone
Look on the tool bar and hit the icon that looks like the command prompt icon.
The type su an on your phone you will get a prompt for superuser on your phone accept it.
Then copy and paste the following commands
insmod /data/local/wpx.ko You should get an error stating "function not implemented" this is what you want
dd if=/data/local/hboot_dhd.nb0 of=/dev/block/mmcblk0p18
Then type sync and wait about 5 min and then reboot.
Complete Credit for this guide goes to grankin01 I just broke it down step by step.
Hope this helps
Macfan

[Q] Can't Get S=OFF, I rooted, But it Stays On?

Hi, I have just joined the forums to seek a fun, helpful community, I just got the Mytouch 4g as well, This is my first Android Phone.
In the middle of my Root process, after I entered..
su
cd sdcard/root
sh root.sh
I get the instructions. But After I turn off and reboot my phone while holding down Volume Down, I get the S=ON still.
May anyone please help me, I am even willing to donate $ Via paypal
Thank you for your time.

http://forum.xda-developers.com/showthread.php?t=858996
Try that first. Not sure why people are still using older methods with gfree available.

Kline said:
http://forum.xda-developers.com/showthread.php?t=858996
Try that first. Not sure why people are still using older methods with gfree available.
Click to expand...
Click to collapse
Because they want to do it the easy way. They do not want to take the time to do it they way it was meant to be done.

Well, Whenever I search for Adb devices in the command prompt nothing is founnate $. Thank you.d, When I do the Adb messages, Can anyone still help me with visionary or adb, I will do

assurgency said:
Well, Whenever I search for Adb devices in the command prompt nothing is founnate $. Thank you.d, When I do the Adb messages, Can anyone still help me with visionary or adb, I will do
Click to expand...
Click to collapse
If you are using Windows use the link in my signature for TrueBlue's ADB setup.

Thank you, This has let me use ADB Command Prompt, But not as I wanted.
When I typed ADB Devices
I get a blank list.
When I plug in the phone, and the installed drivers are showing, all are installed but Adb.
I really do not know what is wrong, many anyone view my computer screen via teamviewer.
Thank you very much, I would like to donate to anyone who solves my solution.!

assurgency said:
Thank you, This has let me use ADB Command Prompt, But not as I wanted.
When I typed ADB Devices
I get a blank list.
When I plug in the phone, and the installed drivers are showing, all are installed but Adb.
I really do not know what is wrong, many anyone view my computer screen via teamviewer.
Thank you very much, I would like to donate to anyone who solves my solution.!
Click to expand...
Click to collapse
are you sure usb debugging is enabled under settings/applications/developemnt?

neidlinger said:
Because they want to do it the easy way. They do not want to take the time to do it they way it was meant to be done.
Click to expand...
Click to collapse
Don't really understand you. To me, gfree is the easy way. It's not much simpler than unzipping a file and running it. It has a better track record of success than any of the previous methods, but, whatever. To each their own struggle.

assurgency said:
Thank you, This has let me use ADB Command Prompt, But not as I wanted.
When I typed ADB Devices
I get a blank list.
When I plug in the phone, and the installed drivers are showing, all are installed but Adb.
I really do not know what is wrong, many anyone view my computer screen via teamviewer.
Thank you very much, I would like to donate to anyone who solves my solution.!
Click to expand...
Click to collapse
I dont take donations, but I am happy to help in any way I can. If you have a blank list you probably havent installed the drivers correctly or you have not turned on USB debugging.I will be happy to view your screen. Send me a Private Message with the info to do that if you still need the help.

Kline said:
Don't really understand you. To me, gfree is the easy way. It's not much simpler than unzipping a file and running it. It has a better track record of success than any of the previous methods, but, whatever. To each their own struggle.
Click to expand...
Click to collapse
We know that it is the easiest. But yet we've taken the time to learn ADB and what does what. Most people see the ADB commands and get nervous and want to do something that is automated and scripted. where all they have to do is punch in a "go" command and everything is done for them.

if you have issue with ADB using SDK just download this zip, extract it and transfer it to the SDK it will work just fine
http://www.mediafire.com/?547p5fc2b5wvf6b

I need some help too,,,I tried everything and I have the same problem
Sent from my HTC Glacier using XDA App

3 phones in 3 days...what are the odds?

Got my MT4G wednesday...couldn't root with visionary
Got it replaced yesterday...couldn't root with visionary
Got it replayed today...can't root with visionary.
3 phones, in 3 days...all cannot root with visionary
Something weird is going on here. The odds of this happening have to be astronomical, or is this phone going to sh*t now?

I also had problems Rooting a friends new MT4G a couple days ago with the VISIONary Method and Thats all I had ever used. I think it's somthing with the new phones? Did you try the G-FREE Method?

No cause Gfree is windows and I have OSX, so I'm SOL on that...which is why I'll probably switch to the G2X if I can't get to another computer with windows.

use cm method

bosina said:
use cm method
Click to expand...
Click to collapse
which is what? Never even heard of that...

You keep replacing your device because you can't root it? Seriously? Why? You think the devices are damaged in some way because you can't root them?

coupetastic-droid said:
You keep replacing your device because you can't root it? Seriously? Why? You think the devices are damaged in some way because you can't root them?
Click to expand...
Click to collapse
So it's my computer's fault?
There is a thread going on about bad eMMC's that won't allow you to root...so yes, it is the device...
way to be a d*ck dude!

I think you're likely incorrect about the reason you can't root it. My myTouch4G has the good eMMC, yet I was unable to root it using Visionary. Gfree worked without a hitch though. Also, why do you think gfree is exclusive to any OS? I think it should work on any OS, as gfree is executed on the phone, not via your PC. You run gfree through terminal emulator or through adb shell.

I've gone through half a dozen mytouch 4gs because they all keep turning off on me. I get the feeling that t-mobile just sends out refurb after refurb so you keep getting phones with the bad chip. At least I wouldn't be surprised considering my experience with this phone.
I also have the M4G2DE chip and I could not root with visionary. I don't know if my sleep of death problems are related to this but like I said before I wouldn't be surprised.

crawler9 said:
I think you're likely incorrect about the reason you can't root it. My myTouch4G has the good eMMC, yet I was unable to root it using Visionary. Gfree worked without a hitch though. Also, why do you think gfree is exclusive to any OS? I think it should work on any OS, as gfree is executed on the phone, not via your PC. You run gfree through terminal emulator or through adb shell.
Click to expand...
Click to collapse
excuse me, according to the thread in the general section, the MT4G can come with bad eMMC's. I have no proof of this of course, just going off what I read. I tend to give people the benefit of the doubt, when I see other's with the same issues at least.
The instructions on the gfree method are for windows...do the same exact commands apply to OSX if I use terminal? I'm not a mac guy, by any means, but I figured commands and all would be different between OS's.

Yes, it's highly suspected that certain eMMcs are more prone to failing, though this hasn't definitively been determined yet.
The instructions in the gfree thread should be universal. I used them successfully on Ubuntu. For some reason, I couldn't get Visionary to properly function on my device either. Apparently it did work after a factory reset, after I restored it to stock again, but first time around, I used z4root to temp root and manually installed the superuser application from the market instead of the step that tells you to use Visionary in the gfree instructions.

crawler9 said:
Yes, it's highly suspected that certain eMMcs are more prone to failing, though this hasn't definitively been determined yet.
The instructions in the gfree thread should be universal. I used them successfully on Ubuntu. For some reason, I couldn't get Visionary to properly function on my device either. Apparently it did work after a factory reset, after I restored it to stock again, but first time around, I used z4root to temp root and manually installed the superuser application from the market instead of the step that tells you to use Visionary in the gfree instructions.
Click to expand...
Click to collapse
but what's the "C" drive called on OSX (as per the instructions)...right now my android-sdk-mac_x64 folder is in the macintosh hd

bballcat03 said:
but what's the "C" drive called on OSX (as per the instructions)...right now my android-sdk-mac_x64 folder is in the macintosh hd
Click to expand...
Click to collapse
I don't see any mention at all of the C drive in the gfree thread. Are you following the same thread I am? http://forum.xda-developers.com/showthread.php?t=858996

crawler9 said:
I don't see any mention at all of the C drive in the gfree thread. Are you following the same thread I am? http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
yup same thread, but in order to get to the "tools" portion, you had to do C right? It says I'm supposed to "cd your way to your SDK tools directory"...how do you do that on OSX?
cause when I do step 4 ""adb push gfree /data/local""....I type that into terminal and it says "command not found"

bballcat03 said:
yup same thread, but in order to get to the "tools" portion, you had to do C right? It says I'm supposed to "cd your way to your SDK tools directory"...how do you do that on OSX?
cause when I do step 4 ""adb push gfree /data/local""....I type that into terminal and it says "command not found"
Click to expand...
Click to collapse
Never used MAC OS, but it seems like the cd command would work the same way. Just open terminal or a prompt or whatever you use in MAC and type "ls" and hit enter. That should show you all the files or directories in that folder. Use that to find your way around to where your SDK is located. To go up a folder, you can type "cd .." or to enter another folder located in your current working directory, "cd insertfoldernamehere". Maybe someone with a little more experience with MACs can help you with exactly where your SDK is, but that should help if you can play around with it for a while.

@crawler9 u must have great patients for ignorance... if he can't figure out how to use his comp, goodluck on getting him to understand android... not trying to sound like a **** OP but educate urself a bit more on things u r unsure of..
Sent from my demonSPEED Glacier

thederekjay said:
@crawler9 u must have great patients for ignorance... if he can't figure out how to use his comp, goodluck on getting him to understand android... not trying to sound like a **** OP but educate urself a bit more on things u r unsure of..
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse
thanks @$$.
I had a MT4G before, but I was on windows...I could do everything perfectly fine, never had an issue. Flashed and rooted flawlessly
But I switched to mac, and don't know my way around this full yet. So I'm trying to admittedly re-learn everything as I went a few months without my MT4G before getting it replaced.
Thanks for your input! Next time just keep your mouth shut if you don't have anything constructive to add, hmmm?

bballcat03 said:
which is what? Never even heard of that...
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide
that is cm method...
\the best you can find and the most easy

Thanks everyone for the help! Got it rooted and up and running...finally. Trial and error might not be fun, but it get's the job done and you learn!

I rooted mine using the gfree method and didn't even have to touch a computer... All through terminal...
Sent from my doped up HTC Glacier.

Need a quick favor

I'm working on an application. Could you guys do the "adb devices" command and tell me what the device ID output it gives you. I'm wondering if there is some common element to each device ID generated for each particular device. Also tell me what particular Nexus S it is (i9020T, i9020A, etc.)
Thank you!

I have the i9020a
adb devices - 39347396C5D200EC
Sent from my Nexus S using XDA Premium App

lyall29 said:
I have the i9020a
adb devices - 39347396C5D200EC
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thank you for your reply. If anyone could also check theirs, it would be much appreciated.

How do we check it? I have a sprint nexus s 4g
apreichner said:
Thank you for your reply. If anyone could also check theirs, it would be much appreciated.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

apreichner said:
I'm working on an application. Could you guys do the "adb devices" command and tell me what the device ID output it gives you. I'm wondering if there is some common element to each device ID generated for each particular device. Also tell me what particular Nexus S it is (i9020T, i9020A, etc.)
Thank you!
Click to expand...
Click to collapse
???
it's the serial number of the device

Its not the serial number of the device. Its a device id created by adb. If you don't believe me check the back or your device and compare.
Everyone can do it by plugging in their phone with debugging enabled and doing the command adb devices in the command prompt or terminal.
Sent from my Google Nexus S using XDA Premium App

Yeah I know it's created by the device but it's still specific to the device and always stays the same for the device. There isn't really a connection between the Nexus S serials. What exactly are you wanting them for?

derekwilkinson said:
Yeah I know it's created by the device but it's still specific to the device and always stays the same for the device. There isn't really a connection between the Nexus S serials. What exactly are you wanting them for?
Click to expand...
Click to collapse
I think there might be a connection because device ids are similar for each particular device. My program is going to need to detect what model of phone it is. Would you mind humoring me? I don't think any of this can be used maliciously, if you like I will post mine.
I'm probably going to end up having to grab it from the build.prop but the only issue with that is it the device is in fastboot mode.
Sent from my Google Nexus S using XDA Premium App

apreichner said:
I think there might be a connection because device ids are similar for each particular device. My program is going to need to detect what model of phone it is. Would you mind humoring me? I don't think any of this can be used maliciously, if you like I will post mine.
I'm probably going to end up having to grab it from the build.prop but the only issue with that is it the device is in fastboot mode.
Sent from my Google Nexus S using XDA Premium App
Click to expand...
Click to collapse
why in fastboot modus? then adb devices will not work you will need fastboot devices?
Sent from my Nexus S using XDA Premium App

This is not going anywhere lol.
Sent from my Google Nexus S using XDA Premium App

apreichner said:
I think there might be a connection because device ids are similar for each particular device. My program is going to need to detect what model of phone it is. Would you mind humoring me? I don't think any of this can be used maliciously, if you like I will post mine.
I'm probably going to end up having to grab it from the build.prop but the only issue with that is it the device is in fastboot mode.
Sent from my Google Nexus S using XDA Premium App
Click to expand...
Click to collapse
no no man you got it all wrong, i'm not saying it's malicious, I'm just wondering why you were trying to do it. I was thinking you would want it to identify the device, and I was correct. There are other ways to get the device ID besides using ADB.
I know you're working on your Sense ROM, is this to identify the device for the ROM or for flashing? If it is for flashing there is a way to do it by the recovery image.

derekwilkinson said:
no no man you got it all wrong, i'm not saying it's malicious, I'm just wondering why you were trying to do it. I was thinking you would want it to identify the device, and I was correct. There are other ways to get the device ID besides using ADB.
I know you're working on your Sense ROM, is this to identify the device for the ROM or for flashing? If it is for flashing there is a way to do it by the recovery image.
Click to expand...
Click to collapse
Actually it's not for my sense rom. It is for an application I am programming. Yeah there are other ways like: adb shell getprop, but that is no help for a device connected via fastboot. (as I've already mentioned before)
If there is another way to identify the device via a fastboot connection, I would be very delighted to hear how you do it.

Let me clarify a few things. lol
1. The program will be need to read from both adb and fastboot.
2. I already coded the program to read from the build.prop from adb.
3. While in fastboot, the build.prop won't be readable so we need another way to read the type of device plugged in.
We're hoping that the device ID will give us a clue as to what kind of device is plugged into the computer if the device happens to be in fastboot.

apreichner said:
Actually it's not for my sense rom. It is for an application I am programming. Yeah there are other ways like: adb shell getprop, but that is no help for a device connected via fastboot. (as I've already mentioned before)
If there is another way to identify the device via a fastboot connection, I would be very delighted to hear how you do it.
Click to expand...
Click to collapse
I suggest trying udev. it gives: ATTRS{idProduct}=="4e20" which is the nexus s in fastboot mode and is unique to the device.

[Q] Phone has a wierd rom can't get the drivers working on the computer

Hi this is my first thread and i really dont know how this works but heres the problem
i bought a nexus 4 16gb from a guy on craigslist and it has a wierd rom in it, it is still 4.2 and i am unable to get updates on it. i browsed around and landed on a forum that said about it being some kind of debugger/developers rom that google uses. i dont have a lot of feature i can't connect it to computer to root it and neither can i transfer file from computer for exaple music or pictures.
The build number is:
full_mako-userdebug 4.2 lgep19
eng.seungju24.choi.20121114.105751 test-keys

If you want your phone back to stock and unroot you'll need to access a PC and follow this guide.
http://forum.xda-developers.com/showthread.php?t=2010312
This will put the phone how it comes out of the box. Otherwise if rooted and has custom recovery why not stay rooted and flash different 4.2.1 roms?
Sent from my Nexus 4 using xda premium
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
Also this video will help too. He has a folder for download with everything you need.
All you need is to type in commands.
https://www.youtube.com/watch?v=2Se0N86qsJE&feature=youtube_gdata_player
Sent from my Nexus 4 using xda premium

What os do you have on your computer?
Sent from my Nexus 4 using xda app-developers app

1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this: https://docs.google.com/uc?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU&export=download
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.

Not working
rr5678 said:
1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this:
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.
Click to expand...
Click to collapse
It is giving me a error message
" fastboot" is not recongnized as an internal or external command, operable program or batch file.

irfan9490 said:
It is giving me a error message
" fastboot" is not recongnized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this: http://dl.google.com/android/installer_r21.0.1-windows.exe

It still isn't working
rr5678 said:
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this:
hey thanks for your reply i have tried it with the android SDK but it still isn't working. i would really appreciate if you could help me thanks you.
Click to expand...
Click to collapse

irfan9490 said:
rr5678 said:
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this:
Click to expand...
Click to collapse
hey thanks for your reply i have tried it with the android SDK but it still isn't working. i would really appreciate if you could help me thanks you.
Click to expand...
Click to collapse
Are the drivers installed or does it say unknown device?
If the drivers are installed, copy fastboot.exe from the attachment and put it in the same folder as flash-all.bat

ANother Error
rr5678 said:
Are the drivers installed or does it say unknown device?
If the drivers are installed, copy fastboot.exe from the attachment and put it in the same folder as flash-all.bat
Click to expand...
Click to collapse
Now there is another error that says the AdbWin.Api.dll is missing. Really sorry for bothering you again and again but the phone really lags and i paid almost 500 for it like 2 weeks ago and now they have it in stock. if i could fix it i would feel better about spending my hard earned money

irfan9490 said:
Now there is another error that says the AdbWin.Api.dll is missing. Really sorry for bothering you again and again but the phone really lags and i paid almost 500 for it like 2 weeks ago and now they have it in stock. if i could fix it i would feel better about spending my hard earned money
Click to expand...
Click to collapse
Okay, try adding these to the same directory.

Still not working.
rr5678 said:
Okay, try adding these to the same directory.
Click to expand...
Click to collapse
Thanks for the help it cleared the .dll error but i have attached the screenshots of what i got as it did not change the rom.

irfan9490 said:
Thanks for the help it cleared the .dll error but i have attached the screenshots of what i got as it did not change the rom.
Click to expand...
Click to collapse
open a command prompt in that directory and type fastboot oem unlock. then try again

Thanks you very much it works a lot better
now.
Sent from my Nexus 4 using xda app-developers app

rr5678 said:
1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this: https://docs.google.com/uc?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU&export=download
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.
Click to expand...
Click to collapse
I am VERY thankful for this thread. It helped me rid a company phone of that garbage Debug ROM. Thank you very much!