Hi guys,
After a lot of trouble (I will not mention them but it was a long pain for me and my desire!) I've finally unbricked my phone BUT usb doesn't work anymore.
I learn that it's called usb-brick.
Sadly, Exhausted from this fight with my device, I've mistakenly installed RUU from htc with gingerbread. And with the new bootloader 1.02.0001.
Problem: I have not find any method to root the phone without the need of usb link with the installed rom.
I hoped to do it when I read about Gingerbreak but infortunatly, it doesn't work with htc version of GB.
Moreover, because the exploit of revolutionary is not known I can not exploit it directly on the phone.
So, I need root for usb unbrick, but I need usb for having root :'(
Is there a way to root my device without needing this usb link?
(Of course, I can access fastboot usb.)
Have anyone an idea?
I know, it's a tricky question... But I have really no idea what to do...
Thanks,
Dvad'
My problem is solved if I can become s-off.
Do I really need a rom with usb connection working in order to S-off my devices?
Fastboot via USB isn't enough? I tried with revolutionary says "waiting for device" forever.
Try following bortak's Troubleshooting Guide
http://forum.xda-developers.com/showthread.php?t=1275632
ROOT WITHOUT USB CONNECTION
Thank for answering.
I read this method but, it works on froyo build only. And I've gingerbread.
davmoi said:
Thank for answering.
I read this method but, it works on froyo build only. And I've gingerbread.
Click to expand...
Click to collapse
Do this:
-extract this on ur computer (its a "portable" version of adb)
-install this widget from the market, it allow to use adb over wifi (without cable)
-try this local root exploit by revolutionary (its work even on 2.3)
after u get temp root, use the flash_image method to flash the misc partition (as for every guide for usb brick fix)
EDIT: Sorry the widget on the market requires root to work..hmm
send it to htc repair, tell they after the upgrade with their 2.3.3 ruu, ur usb stopped working..maybe u get free repair under warranty
My problem is solved!
In fact andQlimax were right! The idea is to run adb with a wifi connection.
Wifi over adb needs root. I don't understand why because this method doesn't need root:
1° Type this In android terminal. it configure the phone to run adb over tcp.
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Click to expand...
Click to collapse
2°Connect your htc on a wifi network
3° on the pc run:
adb tcpip 5555
adb connect ip-of-the-phone-on-your-wifi-network:5555
Click to expand...
Click to collapse
You can access adb shell, have Temp root with zergRush, and flash your mtd0.img.
Problem solved!
davmoi said:
My problem is solved!
In fact andQlimax were right! The idea is to run adb with a wifi connection.
Wifi over adb needs root. I don't understand why because this method doesn't need root:
1° Type this In android terminal. it configure the phone to run adb over tcp.
2°Connect your htc on a wifi network
3° on the pc run:
You can access adb shell, have Temp root with zergRush, and flash your mtd0.img.
Problem solved!
Click to expand...
Click to collapse
Then u just did that and solved? Cool
I shall bookmark this for future reference
I've got this exact problem, but I can't get the WiFi ADB to work. I've got the official Gingerbread RUU installed and the USB is dead outside of fastboot. The terminal on the phone accepts the commands without issue and connecting to WiFi is fine, but my PC just won't find it for some reason. Ideas? I don't fancy an out-of-warranty repair.
seekified said:
I've got this exact problem, but I can't get the WiFi ADB to work. I've got the official Gingerbread RUU installed and the USB is dead outside of fastboot. The terminal on the phone accepts the commands without issue and connecting to WiFi is fine, but my PC just won't find it for some reason. Ideas? I don't fancy an out-of-warranty repair.
Click to expand...
Click to collapse
any firewall/antivirus blocking the port 5555?
what the result of "adb devices" from ur computer after the above procedure?
andQlimax said:
any firewall/antivirus blocking the port 5555?
what the result of "adb devices" from ur computer after the above procedure?
Click to expand...
Click to collapse
Nope, nothing like that is even installed on my PC at the moment. adb devices gives me "List of devices attached" and then an empty line. Is the terminal on the phone meant to return anything when you enter above commands? For me, it simply goes to an empty line when enter the command and doesn't state whether or not is was successful.
seekified said:
Nope, nothing like that is even installed on my PC at the moment. adb devices gives me "List of devices attached" and then an empty line. Is the terminal on the phone meant to return anything when you enter above commands? For me, it simply goes to an empty line when enter the command and doesn't state whether or not is was successful.
Click to expand...
Click to collapse
well, after searching this on internet seems that to be able to do this:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
you need root...so I don't know how the previous user, davmoi, managed to do that..
so in my opinion there is no way to use adb over wifi without root..and there is no way to root the desire with gb 2.3.3 without adb..and without root there is no way to restore usb brick..
call htc and say they that after the 2.3.3 update ur usb is gone..(as u was just flashing their ruu, u should get repair under warranty)
andQlimax said:
well, after searching this on internet seems that to be able to do this:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
you need root...so I don't know how the previous user, davmoi, managed to do that..
so in my opinion there is no way to use adb over wifi without root..and there is no way to root the desire with gb 2.3.3 without adb..and without root there is no way to restore usb brick..
call htc and say they that after the 2.3.3 update ur usb is gone..(as u was just flashing their ruu, u should get repair under warranty)
Click to expand...
Click to collapse
Pretty much what I figured.
I've spoken to HTC and apparently they consider use of the 2.3.3 update to void the warranty as they've put up several warnings and such on the website... which is pretty crap. I'm guessing it won't be too much work for them to just re-flash it though. As long as I can make this phone last until MSM8960 chips hit the market, I'm happy. Never using Amon Ra again though.
Cant enable adb-WIFI connection. List of devices is empty. Think u need root
Need solution without root!
I have no bill (EBay..) to send it to HTC.
Strange, I swear I was not rooted when I used these command lines. (Superuser and titanium was saying that.And it was on a stock 2.3 rom so....
I simply enter them in Android terminal emulator with a user shell.
Can you ping your phone on your wifi network from your computer?
Dvad'
Edit: I think that if we needed root the phone would say "operation not permitted" when you enter the command. The problem seems to be elsewhere.
davmoi said:
Strange, I swear I was not rooted when I used these command lines. (Superuser and titanium was saying that.And it was on a stock 2.3 rom so....
I simply enter them in Android terminal emulator with a user shell.
Can you ping your phone on your wifi network from your computer?
Dvad'
Click to expand...
Click to collapse
ur phone was rooted, that commands requires root permission
Maybe, but in that case, I was able to root a completly stock Gingerbread RUU without adb... And without knowing it!
:/
And if it is the case I can not say how, because I have done a lot of tries with my phone, and I don't remember all of them..
davmoi said:
Maybe, but in that case, I was able to root a completly stock Gingerbread RUU without adb... And without knowing it!
:/
And if it is the case I can not say how, because I have done a lot of tries with my phone, and I don't remember all of them..
Click to expand...
Click to collapse
out of curiosity ur phone was s-offed when u run the 2.3 ruu?
No... it was not soff anymore. Hboot version was stock 1.02
Sent from my HTC Desire using Tapatalk
I could establish wifi connection on GB 2.3.3, HBoot 1.02, not rootet and s-on as described! ADB Shell worked fine. But: when I try to launch command "flash_image mtd0.img" the permission is denied! In ADB Shell on PC I have the "#" instead of the "$". On phone in Terminal Emulator I have only "$"!
Related
Trying to use the http://forum.xda-developers.com/showthread.php?t=829045
Like a Boss Hboot 2.02 root but got the $ instead of # sign after i went into the shell and its telling me "You Should see a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over.." and at the beginning it tells me to "Make sure you have the drivers installed for your phone (recommend: SDK Drivers, unrevoked hboot drivers" but im not sure exactly what that means or how to do it, i thought i was doing alright but i dont think i have it all quite figured out, anyone know the next step i should take to keep from bricking this thing?
Nothin? I ran Unrevoked3 and put everything into the C:/android-sdk-windows folder so hopefully it put the right drivers in there, if im doing this entirely wrong someone say something please!
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off, ok so i just also read a little more carefully, this method listed in your OP is not unrevoked3, maybe a little more info on exactly what you did would help.
ifly4vamerica said:
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off
Click to expand...
Click to collapse
Permission denied on the SU im afraid to run the wrong unrevoked because of the damn HBoot 2.02 think itll be straight if i do it regardless?
its gotta be the drivers, what am i missing here? this is driving me nuts, i spent 3 hours earlier 2 of which were to turn it back into a phone, it was a brick...
ifly4vamerica said:
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off, ok so i just also read a little more carefully, this method listed in your OP is not unrevoked3, maybe a little more info on exactly what you did would help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045 Im using this guide and ive made it up to step 6, if i go to the device manager i have Android USB Devices and when its plugged in it says My HTC and down lower i have portable devices and its just named G:/ but when i tried to update the drivers it says theyre all up to date, any idea if i need to uninstall the ones i have and use a different set of drivers? like installing HTC Sync then uninstalling it? just not sure whats going on..
Not to sure on this one, what did it do when you typed SU? Also what version of hboot do you have, are you sure it is 2.02? if not just keep trying sometimes the exploit doesnt work the first time.
Yeah def. got 2.02 when i typed SU it said Permission Denied I believe its a problem with not having all the drivers on the computer itself, should i install HTC Sync then uninstall it to get its drivers at least?
you can try that for sure, you did use adb to push all of those files in the zip to your sd card right? or did you just drag and drop them?
Used the adb push method to the absolute T but didnt figure out the right drivers at the beginning so im starting over there, what does it mean by the Unrevoked HBoot drivers, i did the unrevoked3 install and that worked out fine but dont think thats what it meant.
So now the phones labeled differently in the device manager, im supposed to delete the actual HTC Sync program before i begin but leave the driver installer and everything right? and i have all the unrevoked folders and SDK ones together in the file i pushed from like it told me to so im going to try to update all those and make sure the drivers are all correct then start the command prompt over again, its in charge only and debug mode of course.
Any idea if the DIAG drivers have anything to do with it? http://forum.xda-developers.com/showthread.php?t=766374 as said in here where you have to actually pick them through the phone?
uhh i may of been retarded by not clicking the SDK Setup.exe file and running it.. wow... snuck that one right by me >_<
So I'm trying to get into su to run gfree_verify to make sure my permaroot S-off/SIM card unlock/SuperCID was successful, but I'm getting a permission denied error.
What happens is, I type adb shell, then I type su, there's a really long delay, then it tells me Permission Denied. However, when I run the Terminal Emulator from my phone and type in the su command, I get root access just fine.
I used the "official" method that is on the HTC Vision Wiki that is located here. The only thing, however, is that my Android SDK install wasn't installed using any type of installer. I just extracted a zip file and shoved it in a random folder. I did make sure to run the Command Prompt as Administrator before issuing the adb shell command, but I'm still unable to get superuser access through the PC. Trying to use the adb root command gives me an "adbd cannot run as root in production builds" error.
Did I do something incorrectly?
adb kill-server
adb start-server
See if that works. If not, try rebooting your computer.
Sent from a Western Union telegram.
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
steviewevie said:
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
Click to expand...
Click to collapse
I rebooted the daemeon, computer, and also the phone. No dice.
The Superuser app is correctly installed. When I ran Adfree and attempted to go into SU in Terminal, I got the usual Allow Superuser access dialog. Both worked without any problems; like I said, I can get root access from the on-the-phone terminal, it's when I attempted to get root access from the adb shell command on my computer where I have problems.
No special ROMs, completely stock post-November OTA update. The only thing I flashed after permarooting was the Clockwork Recovery mod, but adb shell SU wasn't working before this. I initially used some outdated instructions (involving the use of the dd command, and the wpathis.ko or something). I read some more and learned these were out of dated, so I unrooted. I then used the instructions that are on the wiki using gfree to permroot.
gfree_verify works without any problems if I run it from the Terminal Emulator on my phone. Returns the proper values to indicate I'm SIM Unlocked, SuperCID, and S-off. I'm glad it works, but I still don't like the fact I can't use the adb shell. Typing characters on the G2 is a pain in the ass.
I still want to know why I can't enter superuser from the PC adb shell. Am I doing something incorrectly?
Thanks a lot for your help!
Try clearing data for the SuperUser app?
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
dietotherhythm said:
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
Click to expand...
Click to collapse
This worked perfectly! When I entered su from the command prompt, the SuperUser app popped up on the phone's side and I hit allow. It then let me through.
What exactly was broken though? Why did mounting everything from the Clockwork Recovery menu fix this?
I have S-OFF but now temp root visionary won't work for me and I can't get root access. Can only $ using adb so I can't push files. Any help would be apperciated
Try the method in the Wiki - http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
You should still be able to push files via adb though, I don't understand your comment about getting $ with adb (don't do an "adb shell" before you run "adb push", adb is a command for running on your PC, not your phone).
Same here. I did the wiki instructions. but /data/local/root gave me the cp:not found
and /su no a directory. visionary doesnt work. and rage never works right. my "root shell" doesnt let me do su. i think i might have no su. i'm really confused why this wont work. I've done four factory resets trying the rage method and the visionary method. I have S-OFF but nothing else as far as I can tell.
EDIT: I've read a bunch of threads on this and still can't find a solution
I've read in the Rage thread that there were issues with Visionary seeing root access. I would honestly give rage another shot. It worked brilliantly for me, you just have to have ADB configured first.
I did. i get temp root but gfree wont work. i have cid and sim unlock and s off but not system r/w. and when i run /data/local/tmp/root. also my phone will randomly restart now.
steviewevie said:
Try the method in the Wiki - http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
You should still be able to push files via adb though, I don't understand your comment about getting $ with adb (don't do an "adb shell" before you run "adb push", adb is a command for running on your PC, not your phone).
Click to expand...
Click to collapse
I tried this and it didn't work for me.
Can I reflash somehow to the stock rom? I think visionary somehow messed up my phone.
I reflashed to 1.12 and rage worked!
So if visionary has messed up your /su you need to reflash to stock because your /system is messed up.
http://forum.xda-developers.com/showpost.php?p=10966727&postcount=63
had the same problem. had s-off and all that fun stuff. had to do this.
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App
I should have mentioned that I did that and got the # symbol, am I good to go?
Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.
Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App
Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.
shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.
Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.
Excuse my ignorance, but what exactly do you mean by that? What should I do?
I am trying to sync my DInc with Windows 8 Pro to unlock it through the HTC developer site. Unrevoked wont work due to the version of my baseband being 2.15.10.12.20. Software version 2.3.4.
I have USB debugging enabled, fastboot off, performed a factory reset, cleared cache through HBOOT, and the computer DOES reckognize the phone and I am able to select open files and do whatever I need to do with the phone... it just wont display on HTCSync so I can go through the process of rooting it and getting JB on it.
I have also tried running HTCSync in compatability mode. I have been working on getting this working for days now, and have searched this and many other forums for solutions to no avail.
Any ideas would be greatly appreciated, and any more information you need will be provided asap.
Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.
PonsAsinorem said:
Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.
Click to expand...
Click to collapse
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?
cyborggold said:
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?
Click to expand...
Click to collapse
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I can connect the phone and browse files through Windows explorer, I guess I'm just not familiar with adb yet, ill try to find more information on that and give it a try, thanks!
Still Lost
PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!
cyborggold said:
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!
Click to expand...
Click to collapse
How To Set Up Android ADB & Fastboot On Windows [Tutorial]
The only note on this guide I'd make, is not to use the C:\ drive. It's always a bad idea to put stuff in your root directory. Myself, I installed the sdk (which installed itself to C:\Program Files) then I added that to the system path. Also, you might have to reboot (or at least log off and log back on) to reset your PATH.