• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root I really need help figuring this out.. USB Problems

EarlyMon said:
You may be right but I have no idea what you mean when you say it's not detected.

So, you could copy files to your phone in TWRP today so your drivers and usb cable are good.

And your phone says "fastboot" on the screen?
Click to expand...


Yes it shows up but win7 wont detect it I cant run any commands, this is why I been having so much problems. USB can see it as portable drive in twrp when mounted but other than that USB is not detect at all.

And I just tried to flash a different rom and it failed :(

error flashing zip '/sdcard/rom.zip
 
tcbcsm said:
I can go to the bootloader vol down pressing power button and when I plug in the usb the red fastboot usb comes up, but I cant run any command from cmd on it doesn't detect the device. And that option one you told me to follow I have to run the fastboot flash boot boot.img and when I do that it says

< waiting for device >
Click to expand...

Ok, before you plug in USB, it says FASTBOOT above the volume key instructions and above the menu?
 
EarlyMon said:
Ok, before you plug in USB, it says FASTBOOT above the volume key instructions and above the menu?
Click to expand...

Yes.. and when I plug the cord in it say in red FASTBOOT USB so its seeing it and this is where Im confused.

I can adb devices when the drive is mounted in twrp

but I run that same command via FASTBOOT USB I get


F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb devices
List of devices attached


F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>


:confused::confused:
 
tcbcsm said:
Yes it shows up but win7 wont detect it I cant run any commands, this is why I been having so much problems. USB can see it as portable drive in twrp when mounted but other than that USB is not detect at all.

And I just tried to flash a different rom and it failed :(

error flashing zip '/sdcard/rom.zip
Click to expand...

Look, when you're in TWRP / usb mode you can't run any commands because that's right - that's how it's supposed to be.

I get that the fastboot command fail.

You've yet to link me to where you're getting your rom or confirm for me that you're in the fastboot mode of your bootloader.
 
And I thought maybe its my computer so I tried another one and the same thing, its seems ever since that drive was mounted, win7 no longer sees my phone as mobile device it changed the driver to htc mtp device. It was late at night I was really tired I spent all day trying to find a good way to root and unlock, I finally chose the all in one kit follow a youtube vid step by step it all went fine till the rom error and rebooted my phone, bootlooped it and I wiped.
 
EarlyMon said:
Look, when you're in TWRP / usb mode you can't run any commands because that's right - that's how it's supposed to be.

I get that the fastboot command fail.

You've yet to link me to where you're getting your rom or confirm for me that you're in the fastboot mode of your bootloader.
Click to expand...


Yes.. im in bootloader first it says in red FASTBOOT.

When I plug the cord in it say in red FASTBOOT USB so its seeing it and this is where Im confused.

I can run adb devices when the drive is mounted in twrp

but I run that same command via FASTBOOT USB I get in bootloader


F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb devices
List of devices attached


F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
 
Ok - I understand.

Please be patient. Usually I can help fix these but this time I'm missing a step.

So I've sent out a call to my buddies to see if we can get you better help.

Please don't do anything until they get here, they're going to start by reviewing everything here.

I've seen much worse turn around so keep the faith, we'll stick with you and help.
 
EarlyMon said:
Look, when you're in TWRP / usb mode you can't run any commands because that's right - that's how it's supposed to be.

I get that the fastboot command fail.

You've yet to link me to where you're getting your rom or confirm for me that you're in the fastboot mode of your bootloader.
Click to expand...

EarlyMon said:
Ok - I understand.

Please be patient. Usually I can help fix these but this time I'm missing a step.

So I've sent out a call to my buddies to see if we can get you better help.

Please don't do anything until they get here, they're going to start by reviewing everything here.

I've seen much worse turn around so keep the faith, we'll stick with you and help.
Click to expand...


I sent you pm with my US number if you like to call. Thanks for all this, I really hope I can get it working.

:)
 
EarlyMon said:
Ok - I understand.

Please be patient. Usually I can help fix these but this time I'm missing a step.

So I've sent out a call to my buddies to see if we can get you better help.

Please don't do anything until they get here, they're going to start by reviewing everything here.

I've seen much worse turn around so keep the faith, we'll stick with you and help.
Click to expand...


How are things looking?
 
tcbcsm said:
Thanks I saw that and follow the instructions and I got failed to install
Click to expand...

Yeah, I don't know.

It's possible that you need a different driver for your 64 bit Windows 7 to work with fastboot.

Fastboot can be funny that way, that's why I asked for some help for you. I've never used 64 bit Windows with Android, but I know a lot of people do.

Or it could be something else, equally simple. But I bet it's related to that.

Didn't you say that you'd tried another pc? What was that?
 
EarlyMon said:
Yeah, I don't know.

It's possible that you need a different driver for your 64 bit Windows 7 to work with fastboot.

Fastboot can be funny that way, that's why I asked for some help for you. I've never used 64 bit Windows with Android, but I know a lot of people do.

Or it could be something else, equally simple. But I bet it's related to that.

Didn't you say that you'd tried another pc? What was that?
Click to expand...


another win7 machine, thing is this all worked fine until I installed the rom. would superuser have anything to do with it?
 
May I ask the op can u choose another ROM . I think liquid maybe the problem . I am just getting back on reading to see what I can help out with
 
tcbcsm said:
another win7 machine, thing is this all worked fine until I installed the rom. would superuser have anything to do with it?
Click to expand...

Nope.



agentc13 said:
Okay, so you wiped the /system in TWRP? Did you delete the original download of the ROM?

Do you have the HTC Sync drivers installed from this post (http://androidforums.com/one-s-all-...recovery-root-your-htc-one-s.html#post4331626)?
Click to expand...

Our hero, thanks compadre! :party:

Ok, you're in good hands, I'll step back and check in later.
 
I don't use my One S anymore, but I'm trying to remember. I believe that there were some special steps to run any 4.3+ ROMs that are not listed in the site you linked to. I'm trying to find it. So bear with me.
 
BRAINZ2013 said:
May I ask the op can u choose another ROM . I think liquid maybe the problem . I am just getting back on reading to see what I can help out with
Click to expand...


was ice cream sandwich, I have tried many roms but nothing is working it just fails when i try to install. Even the stock one, I even tried a nandroid backup and that didn't work. I have tried everything I can think of regarding the USB drivers, there the lastest ones installed that came with htc sync manager.
 
I'm sorry but I haven't had time to read the whole thread. I assume your device is still s-on.

You will need to flash the boot.img separately after flashing a rom. While s-on, your phone will not flash the boot.img which contains the kernel, thus the phone will not boot until you flash the boot.img contained in the rom.zip


I will elaborate further in just a bit when I get a chance!
 
agentc13 said:
Yes, there was an issue with JB ROMs and newer with the 3.4 kernel. You have to update firmware before flashing those ROMs (hence the bootloops you were getting after flashing). [Firmware Update] For AOSP ROMS-3.4 KERNEL-NEW OFFICIAL CM NIGHTLIES [27June] - xda-developers

So basically, if we can help you get an older ROM (before that kernel) and get you running you can then do the proper steps and be fine flashing the newer stuff.
Click to expand...

I think the Fastboot is used to flash .img file not .zip
 
You must log in or register to reply here.
Back
Top Bottom