So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
DeviceSettings said:
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
Click to expand...
Click to collapse
I'm not sure what's happening with your computer not seeing the phone, but if you have a microsd adaptor you could get a stock RUU onto your card and flash back to stock.
Edit: or just your boot.img. If you can get into hboot you're not bricked.
Part fix
As previous poster said, put a PH...IMG with boot on it and you'll be able to boot up again. Yours is third phone reported here with USB problem after failed S-0ff.
I can boot my rom, but no radio or wifi, No charging, and no computer can see it for fastboot. Hoping for cure soon.
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Same thing happened to me. I just finished uninstalling HTC Sync and Android SDk, then reinstalled both. Now the drivers are working properly, and computer sees my phone again. This should help.
***edit: this process helped with my computer finding software drivers to connect phone to computer. Before- "Windows could not find drivers for Android device" (device manager in windows)
I could never get it to work in the first place. Cleanflash finds and flashes to it just fine but the s off just can't see my phone once it reboots.
Sent from my ADR6425LVW using XDA
DeviceSettings said:
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Click to expand...
Click to collapse
If the phone is rebooting to the screen with the arrow when you press power to enter fastboot then try going to recovery, your regular recovery will probably not show up but another stock hboot menu will. Then try selecting fastboot there and see if you can run fastboot commands without rebooting to arrow screen.
Sent from my HTC Vigor
Success getting it to reboot with the boot.img from the rom I was running....But unfortunately the usb is fried. Can not charge the phone or connect to a computer. So I guess that is another potential risk with using this method.
Ouuuuch :/
Sent from my ADR6425LVW using xda premium
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
DeviceSettings said:
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
Click to expand...
Click to collapse
Warranty!
(edit: kidding, no need for a ****storm)
Related
I am trying to relock my phone and install the newest RUU to get the firmware updates and I have hit a wall.
When I plug in my phone everything is peachy when its booted up and running. When I reboot into fastboot and plug in the phone it is not being recognized by my computer. I have made sure that while booted debugging is on, charge only, and everything is just as it was when I rooted(besides a different ROM). The phone isn't showing up anywhere, not in device manager and not in the devices/printers area. It will however still power the phone as it will stay on even if I pull the battery. I am running Windows 7 64. Any help would be greatly appreciated.
Also I have tried uninstalling and installing the phone drivers in device manager and restarting everything over and over, nothing is working.
Frosstyx said:
I am trying to relock my phone and install the newest RUU to get the firmware updates and I have hit a wall.
When I plug in my phone everything is peachy when its booted up and running. When I reboot into fastboot and plug in the phone it is not being recognized by my computer. I have made sure that while booted debugging is on, charge only, and everything is just as it was when I rooted(besides a different ROM). The phone isn't showing up anywhere, not in device manager and not in the devices/printers area. It will however still power the phone as it will stay on even if I pull the battery. I am running Windows 7 64. Any help would be greatly appreciated.
Also I have tried uninstalling and installing the phone drivers in device manager and restarting everything over and over, nothing is working.
Click to expand...
Click to collapse
the problem might be from usb cable.
try another one if you have.
Got it, I believe it was a driver issue, but I went through several things so not sure what finally worked...
Hi guys!
I have tried to get Android onto my phone and I'm stuck. I'm using the files/instructions from this thread. (HSPL has been done and confirmed)
I noticed there's a similar thread, but they seem to be talking about a different problem, even though it happened at the same step.
Looking at the step-by-step list from that thread, I am stuck between step 10, step 11 and step 12:
- I successfully flashed RHODIMG.NBH
- Took out the battery, booted up with USB and there's the blue screen of the miniPoopLoader (tee-hee, it says poop ).
- Text scrolls by, ends with -- suspend --.
That's it, nothing happens. I can reboot, and it just goes there again. One of the snippets of text reads "flash_read_image: failed 0 errors"
I thought this might be all fine afterall and that I just had to use Fastboot erase blabla to go ahead. But obviously that doesn't work. Most likely because step 12 says install drivers, but no request to install any drivers comes up on my Windows (using Win 7 64 - also, drivers in the package are all Vista - will those work?), which I assume is either because the phone never boots up "far enough" for windows to detect the device, OR because I'm a retard to all major phone hackers here, because I just have to copy them somewhere. (didn't find anything on the boards to suggest the later is true, but then again, who knows).
So, where's the stupid newbie mistake that I overlooked? This isn't the first flash I'm doing, flashed win 6.1/6.5 onto my Touch Pro (1 ), using a fine how-to on this board, and constantly tweaking my S2 and S3, but this seems to be too much for me to figure out.
Thanks for any help!
What phone are you using?
Basic trouble shooting would be.
Task 29, re-download & reinstall minipooploader.
This video gives some idea of what you should expect.Useful info starts around 7:00
http://www.youtube.com/watch?v=_qNCHqGPofI
I have never heard of a suspend error/dialog. Perhaps someone else can chime in.
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
arrrghhh said:
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
Click to expand...
Click to collapse
To enter fast boot you need to have the phone totally off (not rebooted) with the usb cable removed. Then plug usb cable into the phone with the phone off. Then press and hold the power button until the blue screen is done. Sadly I have been doing this all morning trying to resolve a problem of my own.
Tried that, resulting in a slightly different screen (see attached image). Other than that, no difference. I still don't get any request for the HTC drivers and going Fastboot erase recovery results in "waiting for device".
Could you check the list at the thread I linked in the original posting and tell me if I somehow missed something?
Step 10 worked fine.
Step 11 I guess is what Wizardknight commented on.
Step 12 is what confuses me and what's possibly the culprit here?
I bet it's just that without the drivers my PC can't send the Fastboot commands to the phone.
Everything before that worked fine with no errors and everything after that, is just hammering away at the console.
Thanks guys!
Sent from my GT-I9300 using xda premium
Urgh, no idea why it uploaded the picture sideways, sorry.
When instead I press the power button as soon as I see blue (as opposed to hold it all the time), I get the following (see image)
Sent from my GT-I9300 using xda premium
Looks like it is working ok on the phone. I am assuming you installed fastboot and ADB on the PC.
What happens when you open a command prompt and type fastboot devices?
BTW here are the more official install directions.
Lists nothing. After hitting enter, I'm back at the \android-sdk\platform-tools promt.
Sent from my GT-I9300 using xda premium
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
wizardknight said:
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Click to expand...
Click to collapse
This might be where you're going to have to go next OP. Sounds like it's all OK - so try different cables, different USB ports on the PC, and if you can - an entirely different PC altogether.
Vortagh said:
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
Click to expand...
Click to collapse
Had that problem before too. Glad you got it sorted.
I bought my One with bootloader unlocked but the guy who sold me the phone unrooted the phone before shipping and i've tried to follow the rooting and the unlocking bootloader through fastboot methods but every time i open sdk manager it just says i have to update, i update then it says restart, and no mater what i do, cmd just keeps telling me fastboot is not a recognized command... blah blah... short question is, is there a rooting app i can purchase or if anyone can give me a helping hand?
Edit: I have followed the steps exactly, switched off fastboot in power menu, and powered off entered fastboot from bootloader, plugged in device, entered cmd and tried it but i get the aforementioned error.
Edit 2: I made the folder and placed my files and it seemed to go a little smoothly but it says waiting on device and just hangs there. The computer is still not recognizing the phone, i still get USB not recognized. try reconnecting the device....
Oh also, trying to install a recovery to this, so i can root... but just an easy way
Please help me, someone... the bootloader says unlocked btw. but fastboot does nothing when trying to flash via cmd.
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
sakumaxp said:
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
Click to expand...
Click to collapse
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
HyDRo1X said:
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
Click to expand...
Click to collapse
ok i switched to a win8 an everything seemed fine, but i get a long list of processing cmd after i type the fastboot flash recovery... and then continued as followed but nothing... still get red triangle
Ok got it... Windows 8 problems
Sent from my HTC One using xda premium
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
dilyn said:
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
Click to expand...
Click to collapse
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
bigdaddy619 said:
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
Click to expand...
Click to collapse
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
bigdaddy619 said:
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
Click to expand...
Click to collapse
That's really strange. I had the drivers working prior to this episode. I thought that the device suddenly being unrecognizable had something more to do with it.
Oh well. Today I learned.
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
dg32 said:
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Windows 8.1 recognized my device in normal operation, but in any modified hboot failed miserably. (such that are used in conversions/etc)
I've long since reverted back to Win7 for anything involving Android....just so much less risky at this point.
hi, i tried rumrunner but it keeps giving me a usb connection error when testing the adb. but when i use the adb commands in the sdk it shows up just fine and everything works. and my fastboot works as well. but on rumrunner when it runs fastboot first and then adb the adb doesnt recognize my device. ive uninstalled rebooted and reinstalled the drivers but nothings working. please help!!
this is the error message i get when running rumrunner, and i cant figure out why. on the left is my initial adb test, and then on the right is my rumrunner right afterwards
pRoDiGyXxGiRl said:
hi, i tried rumrunner but it keeps giving me a usb connection error when testing the adb. but when i use the adb commands in the sdk it shows up just fine and everything works. and my fastboot works as well. but on rumrunner when it runs fastboot first and then adb the adb doesnt recognize my device. ive uninstalled rebooted and reinstalled the drivers but nothings working. please help!!
this is the error message i get when running rumrunner, and i cant figure out why. on the left is my initial adb test, and then on the right is my rumrunner right afterwards
Click to expand...
Click to collapse
Check and make sure that when your phone reboots it connects to the computer properly, I had a similar issue when i was using moonshine to flash my phone, you should see that the phone is connected and listed in Explorer when you reboot. also make sure that you UNINSTALLED HTC Sync - if it fails to load the drivers, you may try quickly unplugging and replugging in the usb cable into your computer during the countdown, definitely do not do that after it has connected - doing so will result in a brick. follow this advice at your own risk. if you don't feel comfortable with it, don't try it, try another computer, it just so happens that i tried moonshine on 3 of my pc's before i finally got it to run with out hanging.
you can also try this tool kit to install the drivers separate from sync: http://forum.xda-developers.com/showthread.php?t=2219175
p1droidx said:
Check and make sure that when your phone reboots it connects to the computer properly, I had a similar issue when i was using moonshine to flash my phone, you should see that the phone is connected and listed in Explorer when you reboot. also make sure that you UNINSTALLED HTC Sync - if it fails to load the drivers, you may try quickly unplugging and replugging in the usb cable into your computer during the countdown, definitely do not do that after it has connected - doing so will result in a brick. follow this advice at your own risk. if you don't feel comfortable with it, don't try it, try another computer, it just so happens that i tried moonshine on 3 of my pc's before i finally got it to run with out hanging.
you can also try this tool kit to install the drivers separate from sync: http://forum.xda-developers.com/showthread.php?t=2219175
Click to expand...
Click to collapse
thanks!! i will try the toolkit. i never installed htc sync so i know its uninstalled lol. and i will also try the unplugging the cable. oh and i dont know if this matters or not, but my bootloader is still locked because it said for rumrunner i dont need to have it unlocked. is that correct?