Related
Hello all,
I have a friends sprint hero cdma that was rooted with z4root. He was flashing a mod that changed the text from green to orange and the phone froze. He waited quite a while then decided to hard reset. When he put the battery back in and rebooted the phone and the phone would not boot past white HTC bootlogo. The phone will not boot into recovery and the PC will recognize the phone, but the system will not mount so the ruu will not detect the phone either. HTC sync does not detect the phone being connected either. I am using a program called USBDeview and it shows the driver is there and says it is connected but none of the programs detect its connection. Any ideas?
Thanks in advance. Again this is not my phone and I am not familiar with rooting procedures with this phone, but I see a great learning experience in front of me and love these challenges.
this should be in QnA.
Hold power + vol down. will get you into HBOOT. if you flashed the eng-spl that unlocks fastboot you can erase and flash new. Tutorials are somewhere in this forum.
Sorry for the wrong forum. The phone will not hboot or boot into recovery
If it gets that far, you should be able to run the RUU. It'll restore everything to stock ;-)
Sent from my Epic using XDA App
The phone does not connect all the way for some reason. The RUU does not see device and neither does ADB. In device manger, when the device is connected it is assigned a drive letter and I can right click and go to properties and details and the description says android phone. I am out of ideas. Even when the device is connected and assigned a drive letter I can open file explorer and click on the device and the directory is blank. The SD card does not even show up, but if I take sd and put it in an adapter the sd card is still in tact with everything on it.
Sounds like a driver went haywire try searching the dev section for my thread on how to install adb. I know you have it already but try the diffrent drivers. I would post a link but I'm mobile. Hope it helps
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.
Power off
hold vol up and power on
should be in fast boot mode
plug in your USB cable
should now be in fast boot usb mode
run RUU from the computer
RUU should recognise the phone and start installing
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
nordy420 said:
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
Click to expand...
Click to collapse
Yes this is basically true. But if you get the HTC screen, chances are that it is not bricked. I have to ask, did you flash anything like a radio for GSM? If not, then you might need to just let it sit there for an exstended period of time and see if it boots. When I do certain things to my phone, it might take up to 15 minutes to get by the HTC logo screen.
nordy420 said:
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
Click to expand...
Click to collapse
I wish I could take a screen shot and show you but the phone is not recognised at that point except by the RUU when it is waiting for bootloader. Bootloader is another name for fastboot.
It would be a white screen with green letters and it will say fastboot near the top under the green letters. At the bottom of the screen there will be 3 android characters on skate boards.
This is what you should see. Try again
Important: Make sure the USB is not conected at this time
Power off
Hold volume up, then press the red key (power on)
Fastboot screen comes up
At this point plug in the USB. It will change from Fastboot to Fastboot USB
Run RUU .5 or .6 from the computer
It will get to a point where the install says waiting for bootloader
from there it should start installing
If you can't get to the bootloader screen (fastboot) then I am not sure how to help you
Let me know if it works for you.
Edit: If you are not using ENG SPL or have S-Off read this post. You will need a working knowledge of how to use ADB.
http://forum.xda-developers.com/showthread.php?t=958968
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Thank you for the help by the way. I am not the owner of the phone, I am just more patient than the owner and have nothing to lose if it is screwed lol. http://androidforums.com/sprint-hero-all-things-root/259735-bricked.html. Here is his desperate cry for help after it happened. I own a Droid x and have no idea what he was actually trying to do, but maybe after you read what he did then maybe we can come up with a fix. I agree with you supporters that the phone is not bricked but it is sure being stubborn. Please let me know what ya think. Thanks.
unCoRrUpTeD said:
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Click to expand...
Click to collapse
I will try this when I get home. I did do a battery pull but I did not leave it out very long, but the screen never changed for me, just stayed white with HTC logo in the middle.
Be very sure to disconnect the USB. That was the step I was missing and I could not get it to boot to recovery when it was stuck at the logo. Once the USB was disconnected, took the battery out, put it back in, and held down the home button while pushing the power. That worked! Woot!
Lynne
No luck. The phone will not boot into anything to where a PC will recognize it.
nordy420 said:
No luck. The phone will not boot into anything to where a PC will recognize it.
Click to expand...
Click to collapse
Have you downloaded android commander and gave that a shot? androidcommander.com
android commander recognises the phone when it is at the logo screen. it will see all but the sdcard.
within android commander menu, there is a reboot to bootloader command
Ill try it, and report back
So I messed with android commander a little and could not get it to detect the device. I really think that it is a driver issue. I cannot get the HTC driver to install for the phone. A different driver has been installed for the device and windows will not let me manually install one. I can use the install legacy and the HTC driver is there but it will not correlate with the phone when connected.
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
You better wait till january and claim the warranty!
hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .
If the above doesn't work send it to any htc repair center. You have to pay but whatever.
hassanhm said:
hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .
Click to expand...
Click to collapse
Hey hassanhm,
thanks for the reply. I've tried searching the HTC official website for the stock rom, however it is not available for download due to the fact that firmware upgrades are now over the air ..
i've downloaded the RUU rom by optus (RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned
http://www.filefactory.com/file/cfdd...028_signed.exe) found here - http://forum.xda-developers.com/showthread.php?t=1033922 - however it just gets stuck on the booting to bootloader step ...
if there a different stock rom exe file i should be using?
Thanks!
I'm a singaporean. Its uncommon to see this kinda stuff :/
looks like dead motherboard i saw thing like that already
I'm from Singapore. I had this issue, spent a day flashing and rebooting to try and fix it. Then I have up and just flashed an official ROM, I think any one will do, then sent it to HTC. It was still s-off but they didn't care. Took just 3 days and they sent it back, fixed and like brand new. I suggest you don't waste time and just sent to HTC. it will come back s-on but you can just root it again.
Hope this helps!
Sent from my HTC Incredible S using XDA App
There's one but when they put latest Hboot (1.16.0000)then it's harder to flash ROM than 1.13.0000. Hope you get your phone back and it's working
expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
If you claim warranty : YOU LOSS A CHANCE TO HAVE BIG FUN I'm exactly on your situation (may be worse), but probably we feel different. I can only boot into fastboot and hboot ... LOL
expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
Click to expand...
Click to collapse
You must be able to revive, since you did not do anything related to s-off, rooting etc. rooting, s-offing are for modding addict fellow
[/QUOTE]
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
[/QUOTE]
Revolutionary only work on phone with NORMAL BOOTING (Android booting). If you did on fastboot then (I Think) you start create big trouble
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
Click to expand...
Click to collapse
This will only work for UPDATE, mean you must use higher version of ROM than in the phone (if you are s-on) -CMIIW-
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
Click to expand...
Click to collapse
can you post your mainver : FYI, I could NOT resolve my vivo since my situation is worse than you, but probably my experience with unsuccesfull result will give different output ... who knows.
on fastboot (I'm sure You know how to do) fastboot getvar all (windows command) and post the output for our analysing together and help each other.
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
You will loss a big FUN on your life !!! by choosing easy way.
i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard.
ice_pick88 said:
i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard
Click to expand...
Click to collapse
.
what did you do before stuck. Can you boot into bootloader (?) are you S-ON or S-OFF (?) what is Hboot version do you have. To have bootloader state : press power and volume down button SIMULTANEOUSLY if within TEN MINUTES you do not have bootloader status you should stop and let us know here
Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.
ice_pick88 said:
Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.
Click to expand...
Click to collapse
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.
x1123 said:
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.
Click to expand...
Click to collapse
Thanks again for the reply. when i choose the factory reset the phone hangs but when i select recovery it goes to the red triangle logo. Where and how can i know whats RUU of my phone? Sorry im literally a noob.
3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R
programci_84 said:
3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R
Click to expand...
Click to collapse
Just for additional info. If you can not find another android/windows phone to get sdcard CID (you have only one phone and now in trouble). You can use any laptop with Built In card reader at PCI slot and NOT USB STORAGE if you were not have BOTH ... it's time to ask help your neighbour or your friends
Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done
fallenwout said:
Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done
Click to expand...
Click to collapse
Good day,
Thanks for the replies. Im having problem with this step. Im doing the unlocking the bootloader of the phone but when im in the process of inputting the cmd command "fastboot oem get_identifier_token" it gets me the " <waiting for device>
I have installed the latest htc sync version and updated all the drivers but it looks like my pc doesnt detect the incredible s.
Need suggestion guys.
Ill try the Gold card step later maybe it will work.
Thanks again.
Some basic info about my phone-
HBOOT 1.47.0000
Radio 2.42.01.04.23
Carrier- iWireless (Kroger, Sprint subsidary)
S-ON
Alright, so I was just using my phone as normal. Running CM7.2 and ClockWorkMod Recovery. I turned off my phone, everything was fine. When I went to turn it on again, it showed the green HTC logo, as per normal, then it suddenly rebooted. There, it showed the green HTC logo again, and it'll just stay there. So I tried to boot into recovery (pulled the battery, put it back in, held the red end call button + volume down, got into hboot, then pressed home to go to recovery).
The thing is- it did the same thing. Reboot before it gets to recovery, and then stuck at the HTC Logo. I tried using the Sprint RUU, didn't work- it told me to download the right RUU for this phone, and gives me an error 131. I used the flashable RUU found in this thread (found here), in conjunction with this tutorial (found here). It gave me an error that looked like this when I ran "fastboot flash zip *flashable RUU zip path*"
Code:
FAILED (remote: 42 custom id check fail)
I believe it has something to do with the fact that it is NOT a Sprint branded phone. It doesn't even have a Google logo on the back.
Since it's not S-OFF, I can't flash a recovery via fastboot. I'm stuck. Help?
*TO CLARIFY*
I can't get into Recovery, or the actual system. I also can't access adb. The only part I can access is the bootloader and fastboot.
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
laie1472 said:
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
About 75% if I remember correctly. Only light usage. And I just turned it off in school, we were taking a test. Nothing abnormal about turning it off. And yes, several times. Tried flashing recovery/system/boot in every way possible, using that command and not using that command. I noticed something else- it seems like the NAND memory is completely wiped. There is NOTHING on the phone, other than the bootloader.
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
laie1472 said:
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Yes, I tried flashing multiple times. As I said, it fails with a CID check failure. And it doesn't seem that there's anything on the NAND anymore, as it doesn't even get to the boot logo, and recovery will just restart the phone.
My PC recognizes my phone, only in fastboot. And just normal bootloader info- model number, baseband, etc.
Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
cuongcn said:
Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
Click to expand...
Click to collapse
did u update hboot with an unlocked bootloader...thats no good
are u still can access Hboot?
sometimes, u should flash a kernel with ROM to work on it. if you still running Stock ROM, don;t flash MOD kernel like Holiraider. it will couse boot loop.
if u still able to access HBOTT, no need to worry.
@meatwad0222: I unlocked bootloader and updated hboot. It succeeded in rooting the phone. I got problem when I tried to flash a kernel.
@prahasta: I can't do anything. The phone never turned on again, even if I plugged the charger, the LED was not on. Pressing power button with volume down did not work at all. In general, I can't access to hboot.
Hm... It will be difficult.. hope it wasn't couse by hardware.
Sent from my HTC Raider X710e using xda premium
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
austin4913 said:
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
if Bootloop, at least u still can access HBoot, but he can't do that.
try to connect it to PC with Full Battery. then check if your PC still detect it. if PC can detect it, try to flash Official RUU.
My laptop does not recognized it. It said that it can't find a driver for that. I searched in xda-forum and I found the driver. Right now, in the device manager of my laptop, it says Qualcomm HS-USB QDLoader 9008. I tried to flash an office RUU but it stopped at <waiting for device>
Thank for your replies.
good to hear your laptop still detect the phone.
u need to pick right RUU for your device.
used Hanson tools, choose to unlock your bootloader again (hope this work). after unlock bootloader, and u can acces HBOOT, choose fastboot mode then instal CMW/WCXs recovery. once done, try to access CWM. if u can acces CWM recovery, there is no worries anymore, u just need to instal correct ROM and Kernel.
My laptop only detects the phone as a Qualcomm chip, not as a phone. When running Hasooon tool, it stops at <waiting for device>.
Sounds like it's in dload mode.
If your phone is in dload mode then I think that is a soft brick...it is fixable, from what I read on another thread, but is more difficult...but not impossible..I had to download HTC drivers for my laptop...the following 2 sites contain the files.
http://forum.xda-developers.com/showthread.php?t=1450105
http://www.theandroidsource.com/viv...65-latest-htc-vivid-sync-driver-download.html
Sent from my HTC PH39100 using xda premium
I talked to HTC customer service for repairing. After everything was set up, I thought that I lost my warranty since I rooted my phone (in HBoot, it said RE-LOCK"). I will give a try with the "wire trick" in the thread "Juopunutbear S-OFF". Hopefully after wire those holes, I can access to the debug mode and "wake up" my phone. Otherwise, I have to spend $5 more to buy those warranty stickers on eBay and have the phone fixed.
I thought that it would be a jtag, but it was not. I did not succeed. I have to send it to HTC for repair.
I think I know the reason caused my problem. I tried to recover why I was on S-ON. Thus, the firmware will "fight" each other and the hardware will not know what it should do. The result is a software-bricked phone.
I was trying to flash one of the kitkat based new roms i found on this site through the app and it didn't seem to work as i recieved the message saying installation aborted, then my phone buzzed and flashed and restarted but it's stuck on the htc quietly brilliant screen and i cannot get to recovery at all. when i try i see the lights at the bottom menu buttons just flashing.
I did a backup before the install but can't get into recovery now. i've found a proper nandroid backup but my phone wont turn off,restart or go into recovery now, so pissed. please help asap
p.s. the rom i can't even remember the name of it but it said it was one for all versions of htc one.
mine is the canadian version on rogers if it matters.
.and it looks like my computer isn't recognizing it now either
playboypaul said:
I was trying to flash one of the kitkat based new roms i found on this site through the app and it didn't seem to work as i recieved the message saying installation aborted, then my phone buzzed and flashed and restarted but it's stuck on the htc quietly brilliant screen and i cannot get to recovery at all. when i try i see the lights at the bottom menu buttons just flashing.
I did a backup before the install but can't get into recovery now. i've found a proper nandroid backup but my phone wont turn off,restart or go into recovery now, so pissed. please help asap
p.s. the rom i can't even remember the name of it but it said it was one for all versions of htc one.
mine is the canadian version on rogers if it matters.
.and it looks like my computer isn't recognizing it now either
Click to expand...
Click to collapse
What I'm gonna say is ridiculous! BUT IF YOU DIDN'T **** UP YOUR BOOTLOADER you should be able to boot into the bootloader by performing these steps:
First: Press the power and volume up/down button for about two minutes... your phone should respond with vibrate/flashing...
Secondly: Hold your phone under a bright light and press the powerbutton for a minute or so... then try different combinations with the hardwarebutton until it boots into the bootloader.
From bootloader you can perform the following steps to get a OS working on your phone:
This is a quote by me, someone had almost the same problem like you:
Okay, first here you have the correct adb and fastboot files, I uploaded them quickliy for you, I think this way they should work properly:
http://uploaded.net/file/ykwya517
Next thing are these HTC Drivers, in this post are a few of them: http://forum.xda-developers.com/show....php?t=2089508 and on my computer there are the 4.3.0.001 drivers, so I'd recommand downloading those(Credits go to @mdmower):
http://www.mediafire.com/download/n5...+4.3.0.001.exe
Now shut down your phone and boot in into the bootloader with pressing the power button and the volume down button. Then select fastboot and enter this menu. Now if the drivers are installed correctly there should be written FASTBOOT USB. I think you said you are unlocked... so the following command should run just fine. Open a command prompt and navigate to the folder where adb and fastboot are placed. In this folder you copy your custom recovery(TWRP) and you flash it with this command:
Code:
Code:
fastboot flash recovery [recoveryname].img
And DON'T worry about adb in the bootloader! ADB doesn't work with the bootloader. Now you boot into your recovery by chosing Recovery somewhere in your bootloader. If you are in the bootloader you somehow need to push the ROM to your HTC One... This should work with this command...
Code:
adb push "C:\FolderWhereRomIsStored\rom.zip" "/data/media/0/rom.zip"
Click to expand...
Click to collapse
And if this doesn't copy it correctly simply place your zip on your computer to a folder that is empty and push this folder to your HTC One with:
Code:
adb push "C:\FolderWhereRomIsStored" "/data/media/0"
Click to expand...
Click to collapse
Now you are good to go, simply flash the zip form TWRP. I think you know how this works Simply go to install and then chose the zip and flash it.
If you now want to s off... then ask me again. I'll give you an advice
Click to expand...
Click to collapse
Thanks I got it working finally but it was sticking on the HTC screen for over an hr twice and the lamp worked within 10 seconds to get into recovery? I was so amazed that the lamp worked that I did it again and same results, stuck on HTC screen and the light worked again. That's to awesome. Thanks
Sent from my HTC One using xda app-developers app
playboypaul said:
Thanks I got it working finally but it was sticking on the HTC screen for over an hr twice and the lamp worked within 10 seconds to get into recovery? I was so amazed that the lamp worked that I did it again and same results, stuck on HTC screen and the light worked again. That's to awesome. Thanks
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The funny thing is that I don't believe it neither.. but if someone has this kind of error it always works However, nice to know that your device is back alive... if you have any further questions reply/quote this comment so I get notified
LibertyMarine said:
The funny thing is that I don't believe it neither.. but if someone has this kind of error it always works However, nice to know that your device is back alive... if you have any further questions reply/quote this comment so I get notified
Click to expand...
Click to collapse
Hello again I'm glad I found you on find myself with almost the same exact issue as before, this time I've accidentally deleted my OS but I can boot to bootloader and my twrp although my device HTC m7 isn't recognised by my computer or when I try an adb push to the device. I have android sdk installed and the HTC sync manager and the drivers are installed but when I plug device says drivers are Not installed?
playboypaul said:
Hello again I'm glad I found you on find myself with almost the same exact issue as before, this time I've accidentally deleted my OS but I can boot to bootloader and my twrp although my device HTC m7 isn't recognised by my computer or when I try an adb push to the device. I have android sdk installed and the HTC sync manager and the drivers are installed but when I plug device says drivers are Not installed?
Click to expand...
Click to collapse
Hey there. It's quite some time ago since I last "played around" with my HTC One M7 but I think I am still able to help you solve your problem.
Firsr a few questions:
> What OS are you using for adb? Win7/8/10?
> Do you have an USB OTG cable? (would make fixing very easy. You just copy the OS zip onto an USB stick and then plug it into your Cellphone using an OTG cable. Then flashing can be done without any problems)
If you've already solved your problem, notify my anyways
LibertyMarine said:
Hey there. It's quite some time ago since I last "played around" with my HTC One M7 but I think I am still able to help you solve your problem.
Firsr a few questions:
> What OS are you using for adb? Win7/8/10?
> Do you have an USB OTG cable? (would make fixing very easy. You just copy the OS zip onto an USB stick and then plug it into your Cellphone using an OTG cable. Then flashing can be done without any problems)
If you've already solved your problem, notify my anyways
Click to expand...
Click to collapse
sorry i was at work but OS is windows 7 home premium
maybe i should look into the OTG cable.
i get a message saying "cannot read rom.zip" when trying to use command line to push as per the thousands of tutorials online lol.
when i plug in the phone to computer and turn phone on (which is on the HTC splash screen since no OS) then a popup on computer says installing device driver software.
Android Phone X Device Unplugged
USB Composite Device Ready to use
HTC MTP Device X Failed
USB storage devie Ready to use
My HTC Ready to use
HTC android USB Device Ready to use
my cable is really wobbly and none ive tried lately seem to want to fit in the slot snug so HTC MTP Device installed again and now says "Ready to Use also, then cycled the install again and settled on FAILED so only Android Phone has an X for device unplugged since no OS to turn on and HTC MTP has an X for Fail. this is where ill enter fastboot mode or recovery to try push/flash my copy of cm14 and gapps to the device.
i have cmd window open with rom and gapps and an updated version of twrp in adb and fastboot folder.
i entered fastboot mode and pushed recovery through then as per the tutorial i then entered recovery which flashed properly with the new version. then i went to adb sideload and all commands worked like adb kill-sever and adb usb also adb devices came with text saying list of attached devices which theyre is none.
then adb sideload rom.zip came back with:
error: device not found