I have tried recently to root my DNA running 3.06 and 4.2.2 with rumrunner. My phone gets to the bootloader screen from the rumrunner program, and then on the first step the program says waiting for fastboot but my phone just sits there. It isn't frozen and I can move it around but it doesn't do anything automatically like I know it should. Not sure if it maybe has something do do with ADB or anything along those lines. If anyone has any idea I could really use some help. This is my first android phone and my first root attempt. Thanks.
Mr.Schneider said:
I have tried recently to root my DNA running 3.06 and 4.2.2 with rumrunner. My phone gets to the bootloader screen from the rumrunner program, and then on the first step the program says waiting for fastboot but my phone just sits there. It isn't frozen and I can move it around but it doesn't do anything automatically like I know it should. Not sure if it maybe has something do do with ADB or anything along those lines. If anyone has any idea I could really use some help. This is my first android phone and my first root attempt. Thanks.
Click to expand...
Click to collapse
Sounds like a problem with ADB and or Fastboot.
Fix those and you should be fine.
sdamark said:
Sounds like a problem with ADB and or Fastboot.
Fix those and you should be fine.
Click to expand...
Click to collapse
I believe I fixed my adb, put it in my directory and the path settings. Everything still isn't working. I know fastboot is set up correctly because i can type it in the cmd line and all the info comes up, I'm just lost. Not sure if you know what to do from here.
Mr.Schneider said:
I believe I fixed my adb, put it in my directory and the path settings. Everything still isn't working. I know fastboot is set up correctly because i can type it in the cmd line and all the info comes up, I'm just lost. Not sure if you know what to do from here.
Click to expand...
Click to collapse
In a command prompt, type "adb devices'
response should be device serial # "[FA2CXXXX blah blah] device"
Next in a command prompt, type "adb reboot bootloader"
device should boot into bootloader Fastboot USB
Then type "fastboot devices"
response should be device serial # "[FA2CXXXX blah blah] fastboot"
Then type "fastboot reboot"
Device should reboot into android.
If all this works, then ADB and Fastboot are working. :good:
How is Rumrunner failing? Can you post a screenshot of your computer? Need more info to help.
I had a similar issue, but on step 2. Confirm before any reboots that both adb and fastboot work. If so, run the exe. If they stop working during the program running it could be usb cord or port
I am doing it on my windows 7 computer and everything is working perfectly so far. Thanks for all the help and ill post again if I run into more troubles. While Your'e here, does anyone know the commands to flash a custom recovery onto the devise after I have S-Off?
Thanks for all the help guys! It worked perfectly. Now all I have to do is install some roms and see what else I can do.
Sent from my HTC DROID DNA
Mr.Schneider said:
Thanks for all the help guys! It worked perfectly. Now all I have to do is install some roms and see what else I can do.
Sent from my HTC DROID DNA
Click to expand...
Click to collapse
Do you know how to do that or do you need help?
thayl0 said:
Do you know how to do that or do you need help?
Click to expand...
Click to collapse
I installed cyogen mod, but I'm having an issue wjere y data is being weird and I cannot send text messages. Anyone know any smooth running ROMs I could try? Preferably ones that look similar to stock android and not sense.
Mr.Schneider said:
I installed cyogen mod, but I'm having an issue wjere y data is being weird and I cannot send text messages. Anyone know any smooth running ROMs I could try? Preferably ones that look similar to stock android and not sense.
Click to expand...
Click to collapse
Cm is stable. So that could be another problem we have here
thayl0 said:
Cm is stable. So that could be another problem we have here
Click to expand...
Click to collapse
Would you Happen to have a link to the stable release you know of? Just to be sure I have an updated one? I'll attach a picture.
Mr.Schneider said:
Would you Happen to have a link to the stable release you know of? Just to be sure I have an updated one? I'll attach a picture.
Click to expand...
Click to collapse
You have the latest version for 10.2
ViperDNA is pretty much a stock Sense 5.0 JellyBean 4.2.2 ROM, with a million little things you can tweak on with Venom Tweaks and Venom Hub.
Find download here http://forum.xda-developers.com/showthread.php?t=2475739
This one is Sense 5.5 based, KitKat 4.4.2, pretty much 100% stock from the HTC One.
Find download here http://forum.xda-developers.com/showthread.php?p=50142710
Both are awesome.
Really glad you figured out how to S-Off. :good:
Welcome to the community.
Related
EDIT: Thanks to Steal25 and Ausch30, Your antivirus WILL stop the EXE from running. TURN IT OFF, and obviously back on wants your S-OFF. (thanks from AlphaRev, Unrevoked, and TeamWin)
My Original question...
I for some reason when ever i double click on the Revolutionary exploit, the CMD shows maybe for 4 seconds then ends, and i cant get it open a second time with out re-extracting it.
ADB recognizes my phone.
Ive restarted my CPU
I turned off Firewall.
Still no effect.
This also applies to the drivers exploit and fastboot exploit.
Im running Windows Vista
still no luck ?
is it just insta closing when you click on it or is it waiting for device?
Geeble said:
still no luck ?
is it just inst closing when you click on it or is it waiting for device?
Click to expand...
Click to collapse
nothing man. it opens the cmd, does nothing but read the main title, freezes for 3 seconds and exits
coffeehandle said:
I for some reason when ever i double click on the Revolutionary exploit, the CMD shows maybe for 4 seconds then ends, and i cant get it open a second time with out re-extracting it.
ADB recognizes my phone.
Ive restarted my CPU
I turned off Firewall.
Still no effect.
This also applies to the drivers exploit and fastboot exploit.
Im running Windows Vista
Any suggestions?
Click to expand...
Click to collapse
right click the revolutionary.exe and select run as administrator
ausch30 said:
right click the revolutionary.exe and select run as administrator
Click to expand...
Click to collapse
did that as well
this happened to me also, it seems (atleast for me) norton anti virus didn't like it very much. try shutting off your anti virus and try it again. hope that helps.
have you tried running it from a cmd window ?
start Menu search/run
type cmd
drag file into window press enter
that is if it just keeps closing as soon as you open it.
that is all i got unfortunately .
steal25 said:
this happened to me also, it seems (atleast for me) norton anti virus didn't like it very much. try shutting off your anti virus and try it again. hope that helps.
Click to expand...
Click to collapse
AH didnt think about that. lets see...
steal25 said:
this happened to me also, it seems (atleast for me) norton anti virus didn't like it very much. try shutting off your anti virus and try it again. hope that helps.
Click to expand...
Click to collapse
That was my next suggestion, I had the same issue
Got it to run by turning off Norton. But it wont read my serial code. Is there a way you can copy and paste in a CMD? mine i thought did that but isnt now
My cmd closed trying to install Clockworkmod.....any suggestions?
coffeehandle said:
Got it to run by turning off Norton. But it wont read my serial code. Is there a way you can copy and paste in a CMD? mine i thought did that but isnt now
Click to expand...
Click to collapse
you should be able to, type adb devices and get the s/n again and get a new beta code you may have just written it down wrong.
JOKERx2 said:
My cmd closed trying to install Clockworkmod.....any suggestions?
Click to expand...
Click to collapse
try installing teamwins recovery
put the twrp file in sdk-tools folder
cd into that folder and run the fastboot commands to install it.
JOKERx2 said:
My cmd closed trying to install Clockworkmod.....any suggestions?
Click to expand...
Click to collapse
Mine did the same thing. I told it to install CWM and I didn't quite notice that it had and the command window just closed. I got a little nervous but I just opened the SDK and opened a new CMD window and did adb reboot recovery and I was in CWM recovery
I don't understand one thing people say to uninstall sdk before you root but how would you be able to do adb to check the serial for example without having sdk installed
Sent from my PG86100 using XDA App
iliapiano said:
I don't understand one thing people say to uninstall sdk before you root but how would you be able to do adb to check the serial for example without having sdk installed
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
not sdk, you have to uninstall htc sync.
steal25 said:
not sdk, you have to uninstall htc sync.
Click to expand...
Click to collapse
I didn't and mine worked fine
ausch30 said:
Mine did the same thing. I told it to install CWM and I didn't quite notice that it had and the command window just closed. I got a little nervous but I just opened the SDK and opened a new CMD window and did adb reboot recovery and I was in CWM recovery
Click to expand...
Click to collapse
what i noticed also, don't know if it makes a difference or not, the "y" is capitalized and the "n" is not, like i said don't know if it makes a difference or not, but i caught that and put a capital "y" and everything went smooth.
DONE
steal25 said:
you should be able to, type adb devices and get the s/n again and get a new beta code you may have just written it down wrong.
Click to expand...
Click to collapse
Thanks guys. Ill click the thanks for anyone on my thread =]
steal25 said:
what i noticed also, don't know if it makes a difference or not, the "y" is capitalized and the "n" is not, like i said don't know if it makes a difference or not, but i caught that and put a capital "y" and everything went smooth.
Click to expand...
Click to collapse
The only issue I'm having is when I run adb shell from the command line I get $ instead of #. Anyone know if there something I forgot to do or is this the normal state of this root method at this point? Root apps work, CWM recovery is installed, Superuser app is installed, can't seem to access anything or do much from the command line.
I'm sorry if there is something already posted here somewhere about the rezound, but I haven't seen anything...yet...lol.
I've been trying to root my rezound ALL DAY and can't seem to figure anything out apparently.
If someone could help me out with sending me a link to the best way of unlocking bootloader and then rooting my phone. I had a dinc2 previously and that was not as hard to root compared to the rezound IMO. So please, if someone can take the time for me and help me out with getting my phone unlocked and rooted I would greatly appreciate it a TON!!!
Try this out http://forum.xda-developers.com/showthread.php?t=1648578
http://bit.ly/N3cfpa
hey guys thanks for replying back....I'm still getting no luck whatsoever with unlocking the bootloader.....I'm doing everything (or so I think I am) right with the steps on htcdev.com and when I get to the command prompt and type in fastboot oem get_identifier_token...this is what comes up
'fastboot' is not recognized as an internal or external command,
operable program or batch file.....now I have NO CLUE what the heck to do!! I'm getting pissed off lol. I could really use some help here. thanks
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
EmerikL said:
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
npainter7 said:
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
Click to expand...
Click to collapse
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
kzoodroid said:
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
Click to expand...
Click to collapse
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Fastbird said:
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Click to expand...
Click to collapse
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
npainter7 said:
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Click to expand...
Click to collapse
After you install Android SDK the directions on the HTCdev site tell you to run sdk manager and download the Android SDK Tools and Android SDK Platfrom-tools. What I did was to take this a step further and also install the Google USB Driver which is listed in ADB Manager under Extras and also the API's for GB and ICS. The API's really aren't necessary but I don't think ADB will recognize the phone without the Google USB Drivers.
npainter7 said:
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
Click to expand...
Click to collapse
This may not work for you, but one time my drivers weren't working because I plugged my phone into a USB 3.0 port, so when I used a USB 2.0 port, it worked fine.
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
vectorer said:
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
Click to expand...
Click to collapse
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
superbay said:
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
Click to expand...
Click to collapse
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
vectorer said:
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
Click to expand...
Click to collapse
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
superbay said:
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
Click to expand...
Click to collapse
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
vectorer said:
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
Click to expand...
Click to collapse
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
superbay said:
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
Thanks. It's HTC One X+, I got there from a Google search for sideload as I know zero about it. As it turns out it didn't work, got to 22% then failed every time. I'll check out that link now.
Thanks again.
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
vectorer said:
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
Click to expand...
Click to collapse
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
Click to expand...
Click to collapse
how would i do this operation??
now no matter what i try i get
error: closed
vectorer said:
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
Click to expand...
Click to collapse
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
vectorer said:
how would i do this operation??
Click to expand...
Click to collapse
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
vectorer said:
now no matter what i try i get
error: closed
Click to expand...
Click to collapse
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
superbay said:
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
Click to expand...
Click to collapse
thanks I'll keep trying this weekend
vectorer said:
thanks I'll keep trying this weekend
Click to expand...
Click to collapse
Just keep posting here to see how far your effort is with it. Good luck
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
vectorer said:
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
Click to expand...
Click to collapse
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
superbay said:
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
Click to expand...
Click to collapse
Well nothing is working.
I guess my device is a paperweight even if I can get into recovery.
Can't flash anything, not even the RUU, can't sideload........nothing.
Tried Hassoon's instructions for the RUU but it won't reconise that a device is attached to go into Bootlaoder, sideloading ALWAYS fails at 22%. Others seem to overcome this but I cannot. It's frustrating reading how many problems are solved when nothing works for me.
solved mods delete this as idk how
why don't you share with the rest of us what you on how you did it, instead of deleting your thread.
flashhsalf said:
why don't you share with the rest of us what you on how you did it, instead of deleting your thread.
Click to expand...
Click to collapse
Follow this guide > http://forum.xda-developers.com/showpost.php?p=52170480&postcount=2
before the mods del,ete this, i wanna ask a relative question. I've gotten adb to recognise my dna on my computer, and i can use adb commands, but when I get to fastboot to flash the new firmware, i get a (waiting for device) message where nothing happens. where did i go wrong?
champdr0id said:
before the mods del,ete this, i wanna ask a relative question. I've gotten adb to recognise my dna on my computer, and i can use adb commands, but when I get to fastboot to flash the new firmware, i get a (waiting for device) message where nothing happens. where did i go wrong?
Click to expand...
Click to collapse
In your adb folder press shift + right click and open the command prompt window from there and try that. Try a different USB port?
HTC DNA
Saw and tried both with no better results. I ended up using the recovery flashable zip in santod's closed thread without any problems. I know it's not the full RUU, but whatevs for now. Thanks though!
Beanstalk holds a special place in my heart.
I am facing a weird issue with fastboot not detecting my device.
USB is fine (as in I have other USB-C based devices, and they are detected just fine and am able to flash images just fine with them), ADB is fine, including all commands like sideload, etc...
I just get hung on <waiting on device> when I boot to bootloader mode... I am sure it's possible that I am simply doing it wrong... I generally just run adb reboot bootloader on other devices, and boom I was in fastboot mode.
What I'm trying to do is go back to stock... I'm on The Developer Preview 2 for 13 at the moment and am finding some deal breaking issues with a couple apps that I need.
kevp75 said:
I am facing a weird issue with fastboot not detecting my device.
USB is fine (as in I have other USB-C based devices, and they are detected just fine and am able to flash images just fine with them), ADB is fine, including all commands like sideload, etc...
I just get hung on <waiting on device> when I boot to bootloader mode... I am sure it's possible that I am simply doing it wrong... I generally just run adb reboot bootloader on other devices, and boom I was in fastboot mode.
What I'm trying to do is go back to stock... I'm on The Developer Preview 2 for 13 at the moment and am finding some deal breaking issues with a couple apps that I need.
Click to expand...
Click to collapse
May be a driver problem. Do you have the latest of this installed?
why not show exactly what you are trying to do and what you get. copy paste what you see. then check version numbers of the tools you are using.
Lughnasadh said:
May be a driver problem. Do you have the latest of this installed?
Click to expand...
Click to collapse
had a previous version installed. will check when I fire th PC back up tomorrow
Lughnasadh said:
May be a driver problem. Do you have the latest of this installed?
Click to expand...
Click to collapse
It was exactly that. Going to have to bookmark that. I thought I had the latest installed (it was latest as of December lolol)
I do appreciate the help mate, now back to stock Rom for me... (got sick of A13 DP2's issues), plus now I can finally root this thing
kevp75 said:
It was exactly that. Going to have to bookmark that. I thought I had the latest installed (it was latest as of December lolol)
I do appreciate the help mate, now back to stock Rom for me... (got sick of A13 DP2's issues), plus now I can finally root this thing
Click to expand...
Click to collapse
Awesome! Glad you got it going
Lughnasadh said:
Awesome! Glad you got it going
Click to expand...
Click to collapse
You and me both lololol
I've been around these rooms a long long time, and this is the first device I've ever had issues like this with. Usually it's been a USB cable or port, but never a 3 month old driver lol
Now, that I'm back to stock, and rooted... maybe I can get some dev going