Related
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
EDIT: SOLVED!
So, I'm waiting for my Nexus one to come in the mail, and I think to myself, "Why not give rooting the slide another go?"
Worked second try. How's that for random....
So, here's how I made it work...Dunno if it was 'luck of the draw', but here ya go anyways...Hope it helps someone!
1. Instead of turning off the phone normally, I rebooted straight into recovery, with the phone being on first.
Code:
./adb reboot recovery
2. While rebooting, MANUALLY search for devices as soon as you can type it in, repeating rapidly (This made the difference for me).
Code:
./adb devices
3. You should catch the device in offline mode right before the recovery screen. Unplug device for 5 seconds or so, then plug it back in.
Code:
./adb devices
List of devices attached
HT05MPS02279 recovery
4. You should see your device in recovery, then you're good to go. If not try again.
How to you get the loop to stop? I have to quit Terminal app to stop it.
Click to expand...
Click to collapse
No, simply hit <control> c from inside the Terminal app to break out of the shell script.
Any other things to know?
Click to expand...
Click to collapse
Not really, it may take you several tries to get this as it did for people using M$ Winblows. I tried it about 20 - 30 times on XP and never was successful. After switching to my mac, I got root on the 5th try!
My suggestion is to follow Eugene's guide, it worked great for me! If you have problems, post them here and myself or others will try to help you.
Good luck!
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
So I set up my camera to record myself rooting my phone using OSX and a couple friends walked into the room. I got distracted explaining what it was I was doing and didn't make the how to. If I have free time tomorrow afternoon I can make a how to vid. My girlfriend just got her slide yesterday and I believe she wants me to root it.
it's exactly the same doing it in Mac OSX as doing it in Windows except you don't have to worry about drivers. Make sure you get android SDK for Mac OSX and that you put it somewhere that is in your PATH variable.
But if you feel more comfortable doing it from Bootcamp Windows partition -- by all means do that.
Don't boot camp it... lol
I'll be posting a Mac OSX version of Eugene's Root Method shortly.
sk8rbebop, Fordude, stangri, Thanks for the quick replies! Wasn't expecting anything so soon!
I think I have tried to press CMD+C to stop the script, must have been my problem. lol.
@stangri What do you mean by PATH variable? I have the Android SDK installed in my home folder...
@sk8rbebop That's pretty funny . I'm going to have a go at it right now, I'll edit this post with my results.
edit: I don't know if this is right, but I stop the script when I see the device in offline mode. But when I unplug device, re-plug and run ./adb devices nothing shows up. The same happens if I don't unplug.
edit2: Still nothing. adb never recognizes device after I stop the loop.
I threw up a guide. Hope it helps.
Don't shut off the loop until something displays under the devices.
Re: Question: How to root MyTouch Slide using OSX?
When u connect the slide to your mac and type "adb devices", do you see your phone listed? Crucial first step before moving on.
To make things a little easier for me, I put the sdk tools folder in my path so I could issue adb commands in any directory I want to.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
@sk8rbebop Read the guide and i'm still stuck at the loop. I'm having the same issues as earlier, the device will show for a little bit but right before the recovery screen shows, it dissapears. I was stopping the script once I saw the device, before it "dissapeared". Stopping the script after it dissapears does the same...
BTW, I've noticed that I need to start the adb daemon before I run the loop in order for it to even see the device in the loop. Odd.
@Fordude Yes, if I run ./adb devices when the phone is on I get my serial number and it says "device".
edit: I found that I am running an out of date SDK revision, so I am updating to the newest (revision 6), lets see if that makes any difference...
edit 2: No dice. Lame. Oh well I guess...Try try again. My mac seems to be determined not to let this happen
update: So, I'm getting a nexus. Thanks all for your help, happy hacking!
SOLVED
post removed
Hi, I've googled and searched the forum for this and can't find anything that works for the Desire HD.
The phone comes with an option to use the PC's internet connection through the usb interface. When I enable this on the phone the usb0 interface pops up on the computer. I've tried various bridging and natting alternatives, but everything ends up with the phone complaining that htc sync isn't set up right. I've tried askimng HTC what the phone expects but they just say that they don't support Linux. Grrr!
Anybody succeeded in getting this working or can say exactly what the phone expects to see on the pc side?
I thought it was the other way around (PC using the phone's connection) ?
Edit: Link.
Both are possible. PC using phone's connection is called "Tethering" and Phone using PC's connection is called "Internet passthrough".
There are recipes for foolong a "Nexus One" into reversing the tethering solution so that it connects to the internet through the PC, but the HD seems to have blocked this.
We have a Wifi-Free home, so this really is the only way of connecting the phone to the internet without using valuable 3G data traffic.
Apologies, I didn't know.
I took a look around, maybe you've tried this already but here it is (scroll down to post #53). Good luck!
Thanks. Looks promising. From Post #53 it looks as if I should be able to do this from adb, although earlier posts in the thread mention busybox and root, neither of which I have on the phone. Have in any case not used adb to connect before so may ask for help here if I can't find out how to do it.
Thanks very much for the suggestion.
For root you can search for the app "Visionary" in the market, I'm not sure if it installs busybox too though (but you can find that in the market as well).
Also make sure you have USB Debugging enabled in the settings.
You're most probably going to need the ADB drivers as well, but i think they're shipped with HTC Sync. Anyone correct me if I'm wrong.
Thanks, now have adb access (with root . Next problem is that my linux box always assigns an APIPA (zeroconf) address to the usb interface. Can't remove it or specify a static IP for the next connection.
Unfortunately I can't help you or suggest anything else for the time being. I'll be switching to Archlinux tonight (for the 150th time) and will hopefully have my device within this week. So if you don't figure it out by then, I'll give it a shot.
I think it can be done quite easily using the Firestarter application. Too busy playing Black Ops to confirm that the method I have in mind works but I will try it out later and if I'm right I will post a how to.
I'd be very interested to hear how you get on phunkycow. The APIPA problem seems to be debian sid related. On my wife's Ubuntu laptop I can configure both interfaces and ping between the phone and the pc. Didn't have time to figure out routing and dns.
I now have this working on Ubuntu. Debian still gives me a zeroconf address on the pc's usb interface.
Next problem is that to script this as suggested in post #53 I think I need a different su or sudo on the phone as sudo and su -c both give me permission denied.
Any other ways of running remote commands as root using adb?
Working perfectly on Ubuntu when I run through the commands interactively. Next job is to script it. The only possible caveat is that I seem to have to run the adb commands as root, however a quick test indicates that this is probably doable just by piping each adb shell command to su.
Will post back with the findings and the script (when I'm happy with it).
Piping to su doesn't work unfortunately, so I need to think again.
Any tips on scripting adb shell commands to run as root?
Another problem (after setting this up interactively) is that only some apps even attempt to connect to the internet this way.
Web browser shows error about not being able to connect first time, but then connects anyway. Ditto Google earth.
Phone update refuses to connect and asks for wifi or mobile network to be turned on.
Skype can't sign in.
I'm wondering whether some apps look for a particular property to be set and refuse to connect if it's not there??
A hot candidate might be [init.svc.netsharing_pass]???
Any comments?
Hi,
I installed bash and su from su-2.3.2.1-ef-signed.zip, which I moved to /system/bin
which su shows that that's what's being used.
I was hoping that this would give me the possibility to run su with switches (ie su -c "command"), and only use adb to invoke a script on the phone with the rest of the commands. Unfortunately fails on both counts :-(
Does anyone know of other su utilities out there that are more like the Linux version?
Cheers!
The answer seems to be gscript.
Phone side commands can be scripted to run on the phone, requires manually finding and running the script from the phone's UI.
Now if there were a way to invoke it through adb ... !
hi Learnincurve,
can you please briefly post, what you did to use the internet-passthrough? i cant figure it out with my desire z...
thanks!
m1l4droid, you are using the internet passthrough with ubuntu just like that? what am I doing wrong...?
Hello everyone.. I can see that the thread hasn't been updated for some time.. but still, has anyone founded an easy way to use "internet pass-through" option on linux? I have read the thread, but I am not very familiar with the terms "adb" etc. I am using Desire HD rom (InsertCoin HD Port 1.8f), on an "small" Desire... And the linux edition is Ubuntu 10.10... Thanx in advance..
wouldnt you be able to access an ad-hoc wifi network with your custom rom? so the only thing for you to do was to setup the ad-hoc wifi at the pc and connect with your phone...
for the usb-passthrough I still dont have a solution, neither.
I have searched through many microphone issue threads and none seem to help. I have a T-mobile htc g2 which has been unlocked and using my AT&T SIM Card. The phone works perfectly, except no one can hear me during phone calls. The voice search app works perfectly -text,navigation, etc. (so it should not be a hardware problem) which leads to a software problem. I have factory reset the phone several times, but it doesn't fix the problem. I have tried to flash ROM the phone, but I cannot get the phone to ROOT. I have tried Visonary (which failed since I have Android 2.3.4) and the xda wiki page, but my phone is not recognized by HTC Sync or adb.
Either way, I need help figuring out if I can ever fix the microphone issue this phone has. If there is another way to install a ROM, please let me know. I have been trying for days to get my phone rooted.
For more information:
I have tried both versions 3.2.20 and 3.0.5551 of HTC Sync (and neither worked). I've restarted my computer and the phone, turned off antivirus, followed HTC instructions; but nothing worked.
When trying adb, in the command prompt after typing "adb devices" I received this message: " 'adb' is not recognized as a internal or external command, operable program or batch file " To my knowledge I followed all the previous steps correctly, although I have windows 7 and not vista (but I still got to the same properties).
Anyway, please help me with any information.
UPDATE:
I finally rooted and downgraded the phone to 2.2 Android and then flashed a sense 2.0 ROM (although it was force closing applications), but it did not fix the microphone issue. People still cannot hear me during phone calls. So it seems that this must be a hardware problem, but if the mic works for some applications, is it the microphone that is broken? Or could it be something else?
Right now my phone is still in 2.2 Android since I may be flashing the Sense 3.0 ROM soon. But does anyone know what the problem could be and how to fix it?
if adb is not recognized then you are not pointed to it. you need to either
change directories in cmd and point it to the folder adb is in
or
change the path in system variables so when you type "adb" into cmd it will always find the path no matter where you are directing it
or if these steps are above your head,
open the folder adb.exe is located, hold shift and right click in the folder - then choose open command here
once in cmd, type
adb devices
if your phone is plugged in, debugging turned on, proper drivers installed you will see a serial number, that's good - continue
if you see waiting for device, then adb.exe is now working but your phone isn't being detected
if you get the same error as before you need to one of the other ways I mentioned
Sent from my HTC Vision using xda premium
demkantor said:
if adb is not recognized then you are not pointed to it. you need to either
change directories in cmd and point it to the folder adb is in
or
change the path in system variables so when you type "adb" into cmd it will always find the path no matter where you are directing it
or if these steps are above your head,
open the folder adb.exe is located, hold shift and right click in the folder - then choose open command here
once in cmd, type
adb devices
if your phone is plugged in, debugging turned on, proper drivers installed you will see a serial number, that's good - continue
if you see waiting for device, then adb.exe is now working but your phone isn't being detected
if you get the same error as before you need to one of the other ways I mentioned
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That worked perfectly and I guess my phone is seen by adb. However, I realized the link of the xda wiki for the clockwork recovery is not working. I am trying to find another download link, but does anyone know where else you can download the clockwork recovery for htc g2?
go to the cyanogen wiki (just google it)
but I would recommend 4ext recovery, (you can google this too) it far nicer than clockwork for the vision
on a side note, find strawmetal's guide to rooting, its in pdf format and also has all the downloads needed
Sent from my HTC Vision using xda premium
demkantor said:
go to the cyanogen wiki (just google it)
but I would recommend 4ext recovery, (you can google this too) it far nicer than clockwork for the vision
on a side note, find strawmetal's guide to rooting, its in pdf format and also has all the downloads needed
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank you. I will try to strawmetal's guide first since the xda isn't working for me right now.
That Strawmetal's guide worked wonderfully! I finally rooted and downgraded the phone to 2.2 Android and then flashed a sense 2.0 ROM (although it was force closing applications), but it did not fix the microphone issue. People still cannot hear me during phone calls. So it seems that this must be a hardware problem, but if the mic works for some applications, is it the microphone that is broken? Or could it be something else?
the mic is part of the main flex cable, it is possible it cuts in and out because the flex is going bad and the mic is fine.
either way sounds like the only fix will be to replace your flex about 35~40 on ebay and 30~60min depending on how novice/pro you are
Sent from my HTC Vision using xda premium
demkantor said:
the mic is part of the main flex cable, it is possible it cuts in and out because the flex is going bad and the mic is fine.
either way sounds like the only fix will be to replace your flex about 35~40 on ebay and 30~60min depending on how novice/pro you are
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank you for your advice. I flashed the Virtuous Unity ROM and it fixed the microphone, somehow. However, if it shuts off (I pray it wont) I will try to see if replacing that will make a difference.
Mic Not Working in Calls Only
nds623 said:
Thank you for your advice. I flashed the Virtuous Unity ROM and it fixed the microphone, somehow. However, if it shuts off (I pray it wont) I will try to see if replacing that will make a difference.
Click to expand...
Click to collapse
I have qmobile noir a10 which is same as micromax a110.. From few days i have got this mic problem in voice calls. I can hear voice of ppl calling me but they cant hear me.. while microphone is working quite fine in sound recorder application.. i flashed custom ROMS but no success yet.. Plz help me!!
Well I have a question to our devs. Is there any one way to logcat that is preferred over another? I never have done logcat to determine issues for our device and I would like to start. I know there are a couple apps on the play store that are useful like aLogcat or Catlog. I know its best to use adb and even run the command in terminal emulator.
There is a great guide here that I've been referring to http://forum.xda-developers.com/showthread.php?t=1726238
And DONT forget to thank paxChristos for the guide.
In short I want to logcat to help out our devs as much as possible so is there any requirements that you like to see for a logcat? Should I/we try and duplicate the issue a certain amount of times while doing the logcat? Any feedback would be useful.
Thanks to everyone who makes these devices we have just that much better. And keep up the great work.:thumbup::thumbup:
Adb is always the best and easiest way. Always be sure to use -v long when logcatting as it's makes our lives 10 times more easier. Personal favorite log cat guide is this
http://forum.xda-developers.com/showthread.php?t=1378491
Sent from my Nexus 7 using xda app-developers app
sinfulgray said:
Well I have a question to our devs. Is there any one way to logcat that is preferred over another? I never have done logcat to determine issues for our device and I would like to start. I know there are a couple apps on the play store that are useful like aLogcat or Catlog. I know its best to use adb and even run the command in terminal emulator.
There is a great guide here that I've been referring to http://forum.xda-developers.com/showthread.php?t=1726238
And DONT forget to thank paxChristos for the guide.
In short I want to logcat to help out our devs as much as possible so is there any requirements that you like to see for a logcat? Should I/we try and duplicate the issue a certain amount of times while doing the logcat? Any feedback would be useful.
Thanks to everyone who makes these devices we have just that much better. And keep up the great work.:thumbup::thumbup:
Click to expand...
Click to collapse
I think this will work for you
http://forum.xda-developers.com/showthread.php?p=37825398
sent from my htc pico
ADB is a great way to do it. The two guides stated above should help teach you how to logat.
Sent from my Nexus 4 using xda premium
For some reason i can not get my device to connect to adb, Ive never had this problem before and my my old G2x connects just fine. Ive uninstalled the drivers and reinstalled with no luck. Also went as far back as uninstalling the drivers and odin back to stock to try and have them reinstalledwith no luck. Any ideas?
sinfulgray said:
For some reason i can not get my device to connect to adb, Ive never had this problem before and my my old G2x connects just fine. Ive uninstalled the drivers and reinstalled with no luck. Also went as far back as uninstalling the drivers and odin back to stock to try and have them reinstalledwith no luck. Any ideas?
Click to expand...
Click to collapse
Try installing the regular ADB drivers then. I linked a Google search for "Samsung adb drivers".
Damn still can not connect, I've tried to uninstall Google USB driver and Samsung USB drivers and they uninstall and install just fine witj a reboot in between of course but phone is still not connected. I'm my device manager on the PC under other devices it shows 4 android devices all with yellow caution signs.
Now my G2x won't show either lol Going to try and completely remove ADB and reinstall and see what happens.
Sent from my SGH-T989 using xda premium
sinfulgray said:
Damn still can not connect, I've tried to uninstall Google USB driver and Samsung USB drivers and they uninstall and install just fine witj a reboot in between of course but phone is still not connected. I'm my device manager on the PC under other devices it shows 4 android devices all with yellow caution signs.
Now my G2x won't show either lol Going to try and completely remove ADB and reinstall and see what happens.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
If using Windows you must run the command prompt [cmd] as an admin be sure to do the following in Win 7:
click start type cmd in the white box and wait as it searches. When it lists cmd in that list now right click and choose run as admin.
Also you need to enable developer options [go to settings about device and tap the build ID like 7 times [as you tap it, it should count down after the first couple taps once you hit it enough it will say you have enabled developer options if you don't see them in settings already]
Be sure to hit the on off switch in upper right of window when you first tap developer options if the options are greyed out and don't let you change anything
Now in developer options be sure to go to the option where it says enable root access and be sure it says apps AND ADB if it says apps only tap that and change it to Apps and ADB.
Now try again
BTW I love CatLog it has a home screen widget that can start / stop recording for you] so if you know how to produce the problem go to home screen tap the widget go through the steps until the error occurs go back to home screen tap widget again and it stops then look in /sdcard/catlog/ and it will have text files named with the date and time and that will be the entire log cat that happened between the time you started and stopped the recording of your actions.
I know that it was foolish of me to not fully research this set of commands I have copied the before and after of tit all from the command line. I was attempting to mess around with my phone with QPST. I know, I can REALLY REALLY make things hideous if I don't tread carefully with QPST, but I am willing to take the risk in order to learn, even if I do get burned because my phone bursts into flames.
Any who here is the output from my commandline which I ran because using *#0808# and switching to either RNDIS+DM+MODEM or DM+MODEM+ADB didn't make my phone visible for QPST. And I also tried while in recovery, download mode, and all the other settings in the *#0808# menu, plus variations of the menu and then booting into recovery, normal boot, and download mode. All to no avail, then in frustration I tried the following and it's gotten to the point I can't see my phone via adb anymore. So could someone please give me the undo set of commands for typing into my phones terminal as I can't type them via my computer due to adb not seeing it anymore? Thanks
C:\Users\xxxxx>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxxxx>adb shell
$ echo MODEM USB > /sys/class/sec/switch/usb_sel
echo MODEM USB > /sys/class/sec/switch/usb_sel
cannot create /sys/class/sec/switch/usb_sel: permission denied
$ su
su
# echo MODEM USB > /sys/class/sec/switch/usb_sel
C:\Users\xxxxx>adb shell
error: device not found
Oh!, and if anyone can explain either what the commands did or better yet where I can go read about such commands and what they do that would be great too. Thanks
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
crazymonkey05 said:
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
Thank you for the link I haven't tried anything based on the information yet, actually haven't read it all yet. Very complex stuff just lets me know how far I have to go. Odd thing is that I now for some reason have ADB working again. I did a factory reset recently and the other day I reinstalled/refreshed my computer. My computer was infected by a bunch of viruses and malware the phone was just sluggish and I had way more apps I wanted rid of than to keep. Anyway, I don't know if the virus on my system had anything to do with the malfunction or if it was the command I used but for now it is back to working.
I was working on a friends HTC Desire and was having a hell of a time getting fastboot commands to work. I got hboot USB working but when giving a command it would generate a "device connected toi USB has malfunctioned" also the USB ports would shut off untill reboot too intermittantly and even my wifi three or four days ago became disabled and I reset the adapter fine for 5mins then it went a level deeper and deeper till I reinstalled the driver. That being said it is more likely that it was the virus and or the person messing with my system that was causing all the grief. They even triggered email alerts on a couple of my accounts that passwords were input wrong 5 times in a row and that some security settings were being changed. Hopefully I have dealt with that if not I'll have to wait till they get bored. Sorry if that was a little off topic it sort of conencts to my recent problems.