As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436
What we're your steps exactly? Did you relock your bootloader
a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Does anybody else have some more ideas?
Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?
kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.
Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you
Related
I have a Htc Sensation running on the Tmobile network
i decided to go with a different rom and tried to install the rom from COREDROID SENSATION XE & 4G v5.1.
after installing it was stock on the boot screen.
I tried to SCID and install PG58DOAG.
at this point my phone will not boot.
I can get into the the recovery mode after i select "recovery" it goes to a screen with a red triangle and an exclamation mark.
I the volume up and power and the try to install a update...but non has worked
can get one help??
download this file http://www.filefactory.com/file/c19...00U_10.14.9035.01_M_release_223976_signed.exe
and run it with your phone plugged in your pc, it should do a stock recovery on your phone.
I faced the same issue with another ROM.
The only way I found to reboot was to reinstall the firmware while connected via USB with the PC.
And after that, I reinstalled the ROM.
I couldnt even boot.
primekrieger said:
I couldnt even boot.
Click to expand...
Click to collapse
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Skipjacks said:
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Click to expand...
Click to collapse
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
primekrieger said:
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
Click to expand...
Click to collapse
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
primekrieger said:
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
Click to expand...
Click to collapse
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
primekrieger said:
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
Click to expand...
Click to collapse
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
primekrieger said:
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
Click to expand...
Click to collapse
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
rzr86 said:
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
Click to expand...
Click to collapse
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
walkermoon said:
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
Click to expand...
Click to collapse
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
rzr86 said:
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
walkermoon said:
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
Click to expand...
Click to collapse
hmm,
probably you need to use the temproot remove.bat file to remove temproot
check for troubleshooting in this thread
http://forum.xda-developers.com/showthread.php?t=1661631
also refer you issue there
ganeshp will help you further
or you can install 4ext recovery
enable smartflash from it and flash a custom rom
Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2
Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.
usaff22 said:
Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.
Click to expand...
Click to collapse
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/
dc211 said:
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/
Click to expand...
Click to collapse
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip
usaff22 said:
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip
Click to expand...
Click to collapse
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.
dc211 said:
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.
Click to expand...
Click to collapse
Thanks, I knew it wouldn't work after I saw someone on the One XL forums who tried it on his with a USB Y Cable, and didn't look for the zip on the internal storage. I used to think it would work after doing it on my brother's Sensation, but it was a no go for me.
At this stage I think I will have to visit my carrier. Hopefully they can give me a replacement or get it fixed somehow.
This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade
Fofff said:
This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade
Click to expand...
Click to collapse
I tried that, my partitions won't show so it is of no help to me unfortunately.
Hey everyone. So everything was good for the last couple of days as I was on JellyBAM 6.6.0 evita. This morning after charging my phone I go to open it, view some websites etc. Phone reboots by itself, goes to lockscreen. I try unlocking my lockscreen everything good for about 10 seconds. Try to open facebook up, and boom phone goes black and will not turn on. I know for a fact that is 100% charged as when I woke up I checked the battery as I usually do to see if it charged or not.
I am pretty sure I am on Hboot 1.09 or less as I bought the phone close to the release date. Any thoughts because its weird how I cant turn even turn it on or have a LED light show up when it charges.
Thanks in advance
EDIT: Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium
NerdFurgison said:
have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah I forgot to mention I have tried getting into bootloader using the volume down + power process along with holding the power button. Nothing is working.
This phone has well-known power management issues. Sometimes the battery stats get corrupted and the phone thinks the battery is dead when it isn't. Unfortunately, this sometimes results in a brick.
Plug into your PC and see what pops up in Device Manager. If you get QHUSB_DLOAD, you've been bricked. However, this may be fixable since you're on 1.09.
Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything
Zobabe said:
Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything
Click to expand...
Click to collapse
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.
iElvis said:
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.
Click to expand...
Click to collapse
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?
Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.
iElvis said:
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?
Click to expand...
Click to collapse
I am having trouble downloading ADB drivers atm. Trying to find an article that explains it. Kind of a noob at this type of stuff. As for formatting, I dont see an option in TWRP.
razorc03 said:
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.
Click to expand...
Click to collapse
If you could please link it to me, it would be greatly appreciated. Thanks
I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks
Zobabe said:
If you could please link it to me, it would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
razorc03 said:
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Click to expand...
Click to collapse
in order to this though, my computer has to be able to recognize my htc one x. I cant even get it to recognize. any tips?
Zobabe said:
I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks
Click to expand...
Click to collapse
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.
DvineLord said:
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.
Click to expand...
Click to collapse
haha yeah I realized that once I did it and read it in the sticky in the android development section. Do you have any idea of how I could get windows 8 to recognize my htc one x?
windows 8 is the last thing in the world i would let touch my computer. windows xp for life.
i heard alot of people having issues with win8 and usb 3.0 ports.
Hi everyone,
I am trying to help a buddy out and getting his phone working. The phone is not rooted in any way shape or form.
Here are my issues
The phone will not boot into the stock rom. I can get it into the bootloader. Which I went to htcdev. To unlock the bootloader. Followed the steps and was able to get the phone screen to show unlock bootloader. But when I hit yes it reboots and stays on the white htc screen. Then it will keep rebooting. When I go back into bootloader. It still shows the bootloader as being locked? Any suggestions. I haven't flashed anything in about 3 years. But only Samsung things.
This is my set up
Your best bet is to try latest RUU: http://www.htc.com/us/support/htc-one-sv-boost/news/
I tryed that as well. Thinking it is kinda like Odin for samsungs. But as soon as it try to reboot into bootloader. It stays on the white htc screen
The RUU was running completely through and it still not booting?
I will take a picture of the screen. It does not go all the way through. Also I tryed the Ota. Zip. And changed it to PL80IMG and placed it in my SD card. It looked as if it went through and it told me to reboot. But still nothing.
This is what's happening.
Forget the OTA. It won't solve anything for you.
I also think, your bootloader must be locked to run the RUU.
And i think it is your only chance to get the phone back running, because there is no stock rom or backup for boost (as far as i know).
I am OK with rooting it. But in order for me to do it I have to get the bootloader to unlock which I can't seem to do. It does all the motions to unlock. Until the phone reboots
What i have found in this few minutes, Error 171 should be a driver issue.
So, you should make sure that the correct drivers are running (HTC Sync). Maybe another PC could be also a good try.
And you can't root a phone which is not booting into OS. You need a OS.
Is there different drivers I could try besides tc sync. I have tried both computers that I have one has windows 8. The other has windows vista.both have htc sync on them. Also tried a different cable.
If I type in cmd fast boot devices it shows my device being connected. The error shows up while it is waiting for the boot loader to reconnect
Latest should be this.
I will give it a try thank you for helping me. I'm banging my head against the wall for 2 days trying to figure out why nothing is working on this.
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
old.splatterhand said:
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
Click to expand...
Click to collapse
Yea, my main goal is to get it to boot up. I was hoping it was an easy fix. Like with the Samsung epic I had. Just slap it in with odin and boom. after I couldn't get the RUU to work I figured I would try to root it. but since I can't even get the bootloader to unlock. I am stuck and that's the biggest reason I posted. normally I wouldn't I try to read other post and/or youtube it to find someone with a similar problem.
Quick question. When I go into the RUU can/should be in fastboot?
Yes, you should be in fastboot (USB) mode.
Ok so I downloaded the drivers you recommend. It was different then the ones I had. I also downloaded the RUU from the htc site as well just in case. Will try when I get back home. Thanks again.
So here is what I have. I downloaded driver v4.11.0.001. And installed. Downloaded ruu k2_cl_jb_45_s_sprint_wwe_boost_3.05.653.4......
I went into cmd and type fastboot devices. My device showed up. Ran the ruu. Samething happened. The ruu stops because when the phone reboots. It doesn't reboot to the bootloader.
Also I tried in cmd to get the phone to reboot to bootloader with no luck. Is there any thing else I can try?