[Q] ADB Acting Funny... Help? - EVO 4G Q&A, Help & Troubleshooting

I recently installed adb wirelss and decided I didnt like it becuase whenever I was using adb, it would return things like LS command with a weird format. I figured Id uninstall it and then it would go back to normal but it didnt. Does anyone know if there is a way I can change this back to how it should look??

Related

[Solved] Question: How to root MyTouch Slide using OSX?

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

[Q] USB Bricked

Let me say upfront that yes I did read all of unrevoked replies in the dev section.
They mention that the 8/1 leak (ROM I'm currently running) may also have the same USB issues as SkyRaider.
When I plug my phone into my mac, I get a device error message and the option to ignore or (I think cancel). Anyway, if I click ignore, I can see both the SD card and internal storage just fine. I can also see my SD card from my phone and I know adb is working because I recently went into recovery, /mount systen, to remove the old flash.apk for the hulu hack.
So on the surface it appears like my phone is fine except for this error message. I'm curious if any other mac users receive the same error message (never got it before the 8/1 leak). With s-off coming as early as tonight, I don't want a USB brick. Thanks for any help.
Hey bro I'm a Mac user as well and was getting the same message. This has to do with a file that verizon included in the Rom to auto-run the device like an mp3 player on windows machines. You can remove this by rebooting into recovery-partition menu-mount system....now open up terminal and cd into your Android SDK/tools folders now run ./adb shell hit enter next type rm /system/etc/CDROM.ISO hit enter ....unmount system - reboot and your golden.
HeyItsLou said:
Hey bro I'm a Mac user as well and was getting the same message. This has to do with a file that verizon included in the Rom to auto-run the device like an mp3 player on windows machines. You can remove this by rebooting into recovery-partition menu-mount system....now open up terminal and cd into your Android SDK/tools folders now run ./adb shell hit enter next type rm /system/etc/CDROM.ISO hit enter ....unmount system - reboot and your golden.
Click to expand...
Click to collapse
Hey thanks a lot for the info. I'll run adb shell when I get home and see if this solves the problem. Good to know it wasn't just me.
let me know if that fixes the issue for you
Worked perfect. Thanks!
Glad I could help
i had the same problem, but with a pc. whenever i plug in my phone into my pc, nothing comes up, i hav to go to my computer to open it up. and also i have an extra cd drive that says verizon mobile. do u know if the "rm /system/etc/CDROM.ISO" command works with a PC too?

Evo Stock OTA 2.2 Root; Error: Device Offline

I get this error after typing "./rageagainstthecage-arm5.bin" into the command prompt. I tried deleting files and starting over, I pretty much tried everything and still get this error. Even if I try starting all over I get this error right from the start. Plz help! Thanks in advance!
I get this. It just started happening. I have no freakin clue how i created this problem but I am sorely annoyed by it.
Anyone got any ideas on how to get rid of the "offline" status of my EVO?
C:\android-sdk-windows>adb devices
List of devices attached
HT05THL04973 offline
mindcrime11 said:
I get this. It just started happening. I have no freakin clue how i created this problem but I am sorely annoyed by it.
Anyone got any ideas on how to get rid of the "offline" status of my EVO?
C:\android-sdk-windows>adb devices
List of devices attached
HT05THL04973 offline
Click to expand...
Click to collapse
I'm also getting this on a Droid X running Android 2.2.1, using the Android SDK Tools Revision 8.
It happened after I ran rageagainstthecage-arm5.bin as part of the "DarkOnion Root for Droid2" procedure for rooting the Droid X. This error is preventing me from completing the procedure. Does anyone know how to fix this error?
EDIT: I was able to correct the error by rebooting my phone (powering down and then powering up). Afterwards, I was able to complete the root procedure, although I'm not sure how to test it.
EDIT2: Just tried running the Wifi Tether app for root users. It says I'm still not rooted. :::sigh:::
If you have hboot 2.10 then you have to do things differently. Namely you need to use Android Terminal Emulator on your phone instead of adb on a command prompt after you push the files over.
It seems that adb gets permanently killed by rage exploit. Check the Hboot 2.02 thread for more details in the dev section.

normal cmd commands not working on pc after root

so i sucessfully rooted my DZ but i have a problem with my computer now after i rooted, i have a fair idea of what caused the problem but dont know how to fix it.
CMD commands dont work on my computer (like ipconfig and ping etc) giving an error that "ip config" isnt a recognized as an internal or external command.
i think the issue is due to changing the "Enviroment Variables > Path" on my computer as it was in the guide i was following to make things easier, i removed the default path and replaced it with what i have now being
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\PROGRAMS\Other\HTC\SDK\platform-tools;C:\PROGRAMS\Other\HTC\SDK\tools;C:\Program Files\Windows Live\Shared
however i think there may be a command i deleted that i need.
if anyone has any suggestions please post your advice
thanks in advanced Penfold
Add this to it:
%SystemRoot%\system32;%SystemRoot%;
-Nipqer
Ouch, yeah ... what Nipqer said will fix the cmd problem but if there were any other paths set up by other applications you might run into more problems down the line. The guide wasn't stating to replace the paths but to add to them by adding '; c:\new_path\'.
You might just want to roll back with System Restore if there's a very recent one and then readd the adb path properly.
Sent from my HTC Vision using XDA App
Good Idea with system restore.
Looking at my Path the only other ones neccesary are possibly nvidia drivers.
-Nipqer
ok will do, so i dont have to make a new topic ill ask here...
does any1 know of any app that can give me notifications via the LED light.
ive tried LED me know but i dont think that works (the notification is always the same no matter what option you try)
I tried LED me know without any success on my G2. I currently use MIUI and LED notifications work for all apps.
Sent from my HTC Desire Z using XDA App

[Q] ERM... I tried something without knowing fully what it would do.

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.

Categories

Resources