I own a htc sensation 4G. The phone was S-off and was rooted. I am new to android but i did follow every procedure perfectly till the following happened.
I downloaded the ota update. Whilst updating it, the update was successful but now my phone just shows a blank display. The phones on, i can receive calls too but its a blank black display with no touch capable.
I tried to run recovery (PG58IMG), it was successful, but when rebooting same problem.
From boot(vol down + power), if i go into recovery, nothing happens, phone simply boots up
Same is the result with factory reset. No matter what i try to do, the phone accepts the command and boots up leaving me with an on phone and no screen.
Next i tried RUU , RUU_Pyramid_TMOUS_1.45.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_208218_signed and the RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_signed VERSIONS.
It runs but, when it comes to the point where it says, waiting for fastboot, There is a htc screen(white and black text) and the phone just wont go into fastboot. ten odd mins later i get a msg saying error 177, usb not found on my cpu and the only option on screen is exit. When i pull out the usb from the phone, for abt 5 seconds it shows the fast boot screen with RUU written below the basic information and it goes back to the htc screen. Only way to cancel is to pull out the battery...
Now everything that i could find on the forum and net, i have tried.. Please tell me if there is another option or am i doing something wrong???
My big problem at the moment is that im not in the states, am in India and cant take the phone to a service centre... PLS HELP
Any inputs guys?? really stuck here
Have u tried the tmous 1.50.ruu?
mugetsu666 said:
Have u tried the tmous 1.50.ruu?
Click to expand...
Click to collapse
RUU in general has a problem, the program keeps waiting for fastboot whilst i only have a screen with an htc logo on it. Only after waiting for a couple of hrs and disconnecting the usb cable, i get a fastboot screen with ruu written for abt 5 secs and it automatically goes back to the HTC screen..
I have tried 2 different ruu's and same end result.. so so..
Have u tried talking to a tech at HTC?
mugetsu666 said:
Have u tried talking to a tech at HTC?
Click to expand...
Click to collapse
i did today, they told me that everything possible that he would advice me to do, you have already done so. There is nothing left to be done. Get it over at a service centre to check for hardware defects or a possible re-programing of the phone.
The thing is, In india, htc sells like hot cakes, but their back-end service is horrendous. Service centers are not htc's but third party and they charge crazy sums for a customer doesn't have a 2nd option.
Hence am considering and trying all other options before going to a htc service center.
Is there anything that i have missed out in trying from my end???
Not that I know of, it sounds like the ota bricked ur phone and I'm not that good at that part. My knowledge only goes so far, sorry man.
Have you tried getting the PC to recognise the phone in fastboot?
If you have working fastboot then you can normally recover it.
Pull battery, reinsert, volume down & power then connect to PC.
Open cmd prompt as admin, cd to your fastboot folder, then enter "fastboot devices" and post the result.
Instructions on fastboot/adb if you are unfamiliar in the sticky guide to everything in dev forum.
Sent from my HTC Pyramid using xda premium
#mugetsu666 , i doubt the phones bricked, whilst everything is not working, aka fastboot, recovery, factory restore etc, the phone does boot and is on. How do i know this?? well, when i dial my no, the phone does ring but the screen is dead, as in black.. the 4 tabs below too r lit up but just no response..
#stringer7 , i did all of that already but whilst u asked me to post results, something just struck me.. when the phones put on usb, it charges and i can take it to fastboot too, but, on the task bar far right in devices, the pc is trying to search drivers for usb. Thats always on, even after leaving the phone on load overnight.. The pc is always searching for drivers and when i unplug usb, the no drivers found error does pop up..
"device driver software not successfully installed", is the windows error
Is the above info of any help?? considering the fact that i can take the phone on fastboot usb, but on the pc screen comes the error that usb not found or waiting for fastboot...
help
----------
Can you get a message from "fastboot devices" as above? If so you should be able to run the correct ruu to recover.
Sent from my HTC Pyramid using xda premium
The thing is, that the comps not reading the phone as a android device.
It charges the phone but doesn't read it. Hence cant do anything..
Any RUU doesnt move beyond the usb detection point leaving me with an "ERROR 170", cannot read usb..
Did the ota do this or does this look like an hardware error?
The 1.45 ruu of t-mobile seems like the most common one, but i cant even put that 1 to the test cause it just doesnt go beyond detection
Is there a chance that my problem could have cause a motherboard or other hardware problem???
Related
Hi guys.
After two weeks without wifi, yesterday, my phone decide to update about 20 apps from market. When Beautiful Widgets were downloading, phone suddenly froze and I had to remove my battery after 10 minutes. When it booted again, Angry Birds started to update and phone froze again. So I removed my battery once again and when it booted up, I turned my net connection offline to prevent downloading. As soon as I did so, I canceled all market downloads and turned connection online again. Market started updating on its own and phone froze during night.
So I decided to removed battery once again this morning and when I put it back in, put it back in, phone froze after "Quietly Brilliant" logo with black screen.
It was suitable for factory reset from bootloader. So I did factory reset and same story repeated, except for this, it was a loading loop, HTC Quietly Brilliant and sound which comes with it over and over again.
So in the end, I tried to do the "recovery" option which did no good and again factory reset, but this time, bootloader froze and nothing happened. This is final state of my phone.
So after boring story, there is a question. Is there any way I can do software flash / reset without phone (via USB etc?) before I send it back to HTC for repair?
Device is S ON and never been rooted. I also removed SIM and memory card with no effect.
Thanks a lot!
You should take hope from the fact that you are able to still enter bootloader and perform full reset
Also the fact that you are still s-on means that you should still be covered under warranty
I believe that you should be able to re flash your original rom via your pc using RUU, check to see if your original is in the rom sticky thread within the dev section and if so start downloading
Sent from my HTC Desire S using XDA Premium App
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Hey, thx for reply.
I have no experiences in this but I guess I only need to know this things:
RUU - Stands for ROM Upgrade Utility. What soft should I use?
Also, all I can see in bootloader is following:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011,14:58:38 (<wtf?)
and then just classic boot menu with options like FASTBOOT etc.
Therefore I cant figure out, which ROM is mine in that thread. Also, is there any option to flash ROM from memory card? Does it have to be signed?
Only limitation is warranty which I dont wanna lose. Thx.
InfernalByte said:
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Click to expand...
Click to collapse
See the statement above, I will not do anything to invalidate the warranty.
Yesterday, after attempting the "Update all" for the first time (well, not exactly) the phone froze just as yours did & started encountering the same issues. After coming here to seek assistance, this thread was the first I laid eyes upon.
My case in somewhat more detail, after freezing during the "Update all", I performed a soft reset by removing the battery as well, booted up fine, but as soon as everything was loaded the market tried to continue where it left off (which is updating Opera Mobile @ 98%) and the result was another freeze. I was quickly able to deduct that the update were to be the issue & turned off connectivity. Now, at the present state, Opera Mobile update is still under notifications (at 98% complete but "paused"), as soon as I re-enable either WiFi or 3G it continues & crashes. I cleared all caches & reset all Market applications & rebooted to no avail.
Hard reset was next on my list, but see-ing how the situation got worse for your device hereafter, I am holding it off for now. Is it possible to have market updates, that are ongoing, canceled? Bear in mind that I cant enter Market since it requires connectivity.
Weird stuff.
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Numline1 said:
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Click to expand...
Click to collapse
Thanks! That did the trick, was able to remove everything due to be updated.
Strangely, though, I wasn't able to finish loading the market before it resumed the Opera update. This time, however, instead of crashing it was able to complete it (contrary to the last 10+ attempts yesterday), thus there is a chance it wouldn't have crashed at all. In any case, keeping distance from the Market seems like a valid idea for now.
Reading your thread might've helped to avoid my device turning into a brick, I appreciate it.
Well, update to my current status:
Im still in hboot. Device was recognized as "Android 1.0" in my Windows, so I had to install ADB driver. It is now connected as Android Composite ADB Interface".
I can't get any further, since RUU says my phone is not connected to PC.
Any advices please?
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
//When I connect it in Fastboot, it shows as "MyHTC" in Windows.
Numline1 said:
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
Click to expand...
Click to collapse
Afraid, that I'm well out of my depth with all that, hopefully someone else with more knowledge will post...or else it's warranty return. best of luck
Np, thx for trying, maybe someone else will know
//Update: In Fastboot mode, my device is recognized by RUU!!! Trying to update right now!!!
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
InfernalByte said:
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Click to expand...
Click to collapse
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Numline1 said:
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Click to expand...
Click to collapse
Good luck
(....10 Chars...)
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Numline1 said:
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Click to expand...
Click to collapse
Update.zip will not work, if your determined to try something push a new SPL via fastboot commander, even thought your not S-off if things aren't working maybe the CID check wont check either.
Below will only work if your phone is not branded or you have a goldcard.
Alternatively unzip your RUU on your PC in one of the files called {squigly brackets and a lot of numbers673652435364849483763} you'll find a .zip called rom.zip rename this PB99IMG and put the file into the root directory of your SD card, and boot into Hboot. Just answer yes to any questions. This is the way HTC Tech folk themselves serve an RUU.
Yea, I actually extracted it using advanced system monitor from microsoft, this file was in temp folder. That's where my rom.zip was. Anyway, isn't it PB88IMG.zip? I think DS is checking for this one. Thx.
//Edit: I mean PB88IMG.img
//Edit2: It's PG88IMG.zip It's now updating, don't know if it works yet, still at BOOTLOADER update with status "Updating".
Ok, I think this is my last post, since I no longer know what else to do. When Im trying to flash PG88IMG, it stops at [1]BOOTLOADER - Updating.
For more than one hour. There's something wrong with it and I will claim my warranty, which will be funny, since Im in Slovakia, phone was bought from Amazon with 3 year warranty from SquareTrade and they claim, they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Numline1 said:
they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Click to expand...
Click to collapse
O, bugger!
question is if they do give you the money, will you buy another DS? and if not what would you consider instead? Sensation?
Yea, can't say yet, since I don't know. I just discovered, there may be a chance they will cover my repair costs when I email them all the service documentation from service center.
But if they do, I'd like to stay with HTC, I paid something about 377L for the phone, so I may buy something better now.
Anyway, thanks a lot for help guys, if you come with some new ideas about how to fix it, do not hesitate to tell me I'll be sending it to them first thing tommorow.
Im now stuck on a black screen.
it was running then said
"Radio downgrade complete - starting next process - please be patient...
"
let it stay for maybe 8 minutes then i took battery out phone cause i couldnt turn the phone off.
i read in "EFFIN MANAL" that
Black or White Screen
PC fails to process halfway through and your phone boots to a black or white screen.
so says to reboot phone.
i turn my phone on and it stays on black screen now.
what do i do?
i tried starting up the hack again but says
"Error detecting HTC phone on USB connection.
"
even when in HB Boot loader..
says "HBOOT USB PLUG"
when i take out USB it says "HBOOT" alone
obviously
Then i go to what I think i is the HBOOT loader screen and when i try FASTBOOT, RECOVERY,or FACTORY RESET it goes to the first HTC screen that shows up and then fades out 10 seconds in.
http://forum.xda-developers.com/show....php?t=1396229
will this help or different problem?
SdRasta said:
Im now stuck on a black screen.
it was running then said
"Radio downgrade complete - starting next process - please be patient...
"
let it stay for maybe 8 minutes then i took battery out phone cause i couldnt turn the phone off.
i read in "EFFIN MANAL" that
Black or White Screen
PC fails to process halfway through and your phone boots to a black or white screen.
so says to reboot phone.
i turn my phone on and it stays on black screen now.
what do i do?
i tried starting up the hack again but says
"Error detecting HTC phone on USB connection.
"
even when in HB Boot loader..
says "HBOOT USB PLUG"
when i take out USB it says "HBOOT" alone
obviously
Then i go to what I think i is the HBOOT loader screen and when i try FASTBOOT, RECOVERY,or FACTORY RESET it goes to the first HTC screen that shows up and then fades out 10 seconds in.
http://forum.xda-developers.com/show....php?t=1396229
will this help or different problem?
Click to expand...
Click to collapse
First off guy in the Ace Hack Kit forum there is a channel called IRC chat, that should have been your first stop for help with the Ace Hack. Make a u-turn and head back that way for your issue those guys there are great.
Sent from my Desire HD using xda premium
Yes please hit up the irc before opening threads like this. Its best to go straight to the ones that will help.
"I love my Springfield XD40"
Help needed !!! Urgent -
SdRasta said:
Im now stuck on a black screen.
it was running then said
"Radio downgrade complete - starting next process - please be patient...
"
let it stay for maybe 8 minutes then i took battery out phone cause i couldnt turn the phone off.
i read in "EFFIN MANAL" that
Black or White Screen
PC fails to process halfway through and your phone boots to a black or white screen.
so says to reboot phone.
i turn my phone on and it stays on black screen now.
what do i do?
i tried starting up the hack again but says
"Error detecting HTC phone on USB connection.
"
even when in HB Boot loader..
says "HBOOT USB PLUG"
when i take out USB it says "HBOOT" alone
obviously
Then i go to what I think i is the HBOOT loader screen and when i try FASTBOOT, RECOVERY,or FACTORY RESET it goes to the first HTC screen that shows up and then fades out 10 seconds in.
http://forum.xda-developers.com/show....php?t=1396229
will this help or different problem?
Click to expand...
Click to collapse
Hey mate, I came searching through the entire web and found your post to be the most relevant to the problem I have at hand. Rather, it is the exact same problem. I know that u were directed towards IRC and so I checked #aahkSupport but it asks for invite only. I can't figure out a way to do it or have u got any clue?
Best, do me a favor and tell me how you u got ur HTC DHD working for urself again, considering this post to be now a couple of years old? PM me if u like.
hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again
any ideas please?? or am i completely out of luck?
When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.
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
Hi, I recently started having issues with my Sensation. It would reboot and get stuck in the HTC logo boot loop. The phone has and unlocked bootloader, S-OFF, and Super-CID.
I was using the Elegancia rom, so I thought that was the issue. I was able to get the phone into Fastboot mode with Power+Vol Dn and then connect the USB cable to get to Fastboot USB mode. I downloaded The TMOUS RUU 1.50.531.1 from one of the links in a thread in this forum. I was able to succesfully get the stock rom flashed on the phone. However, I wanted the latest version, so I went and downloaded the ICS TMOUS 3.32.531.14 RUU. I followed the same steps as above, got the RUU to recognize the device and start the flash. It got stuck at 27% saying "Updating System". I left it there for 1 hour and it didn't move. I had to force close the RUU program on my laptop and had to do a battery pull on the phone. Now, the phone doesn't power up at all. I can't even get into HBOOT.
I've tried the following so far:
- Left the phone on wall charge without the battery for 6+ hours
- Charged the battery by blocking the middle 2 prongs
- Tried to "jump start" the phone by removing battery, plugging in charger, inserting battery, and waiting for light
- Tried to remove battery and re-insert and pressed Pwr+Vol Dn multiple times.
- Tried to use adb/fastboot but get device not found
- Laptop won't recognize the phone, dont even get the QHUSB_DLOAD message
Is there anything else left to try? Or am I completely bricked?
intel61 said:
Hi, I recently started having issues with my Sensation. It would reboot and get stuck in the HTC logo boot loop. The phone has and unlocked bootloader, S-OFF, and Super-CID.
I was using the Elegancia rom, so I thought that was the issue. I was able to get the phone into Fastboot mode with Power+Vol Dn and then connect the USB cable to get to Fastboot USB mode. I downloaded The TMOUS RUU 1.50.531.1 from one of the links in a thread in this forum. I was able to succesfully get the stock rom flashed on the phone. However, I wanted the latest version, so I went and downloaded the ICS TMOUS 3.32.531.14 RUU. I followed the same steps as above, got the RUU to recognize the device and start the flash. It got stuck at 27% saying "Updating System". I left it there for 1 hour and it didn't move. I had to force close the RUU program on my laptop and had to do a battery pull on the phone. Now, the phone doesn't power up at all. I can't even get into HBOOT.
I've tried the following so far:
- Left the phone on wall charge without the battery for 6+ hours
- Charged the battery by blocking the middle 2 prongs
- Tried to "jump start" the phone by removing battery, plugging in charger, inserting battery, and waiting for light
- Tried to remove battery and re-insert and pressed Pwr+Vol Dn multiple times.
- Tried to use adb/fastboot but get device not found
- Laptop won't recognize the phone, dont even get the QHUSB_DLOAD message
Is there anything else left to try? Or am I completely bricked?
Click to expand...
Click to collapse
It does not boot at all? What happens when you connect it to your PC? If it boots - what's shown on the display (And I don't mean getting to HBOOT. There is a black screen with warning signs which is reversible)?
astar26 said:
It does not boot at all? What happens when you connect it to your PC? If it boots - what's shown on the display (And I don't mean getting to HBOOT. There is a black screen with warning signs which is reversible)?
Click to expand...
Click to collapse
It doesn't boot at all. Even after connecting it to the PC. I don't get any vibrates either.
Do you know if there's a way for me to test to see if power is getting to the necessary places on the circuit board?
intel61 said:
It doesn't boot at all. Even after connecting it to the PC. I don't get any vibrates either.
Do you know if there's a way for me to test to see if power is getting to the necessary places on the circuit board?
Click to expand...
Click to collapse
It probably does. The problem is probably because of damaged firmware/radio on the phone, so it won't boot. Does the computer recognize anything when the phone is connected? Check in device manager (Could point to an error such a QHSUSB_DLOAD).
If not, it could still be fixed, but it will need to be JTAGed, which is best to be done by a professional repair service, as the equipment is expansive and it requires soldering to the motherboard.
astar26 said:
It probably does. The problem is probably because of damaged firmware/radio on the phone, so it won't boot. Does the computer recognize anything when the phone is connected? Check in device manager (Could point to an error such a QHSUSB_DLOAD).
If not, it could still be fixed, but it will need to be JTAGed, which is best to be done by a professional repair service, as the equipment is expansive and it requires soldering to the motherboard.
Click to expand...
Click to collapse
Yea, nothing in the device manager.
I could perform the JTAG myself if I had the pinout and circuit diagram. I think I should have all the parts necessary. I'll search around for a diagram to see if its available. If you know where to get this information, would you send me a PM or post it? If not, its probably not worth paying to get the phone JTAGed, I could go buy a Nexus 4 or something as a replacement.
intel61 said:
Yea, nothing in the device manager.
I could perform the JTAG myself if I had the pinout and circuit diagram. I think I should have all the parts necessary. I'll search around for a diagram to see if its available. If you know where to get this information, would you send me a PM or post it? If not, its probably not worth paying to get the phone JTAGed, I could go buy a Nexus 4 or something as a replacement.
Click to expand...
Click to collapse
Here is a guide: http://www.jtagbox.com/jtag-news/ri...ick-unlock-modelid-cid-imei-repair-supported/
Are you sure you have the equipment? It's not something easily found...
astar26 said:
Here is a guide:
Are you sure you have the equipment? It's not something easily found...
Click to expand...
Click to collapse
Sorry, I meant to say that I could probably assemble the box itself if I had some knowledge of what the parts list was. I definitely don't have access to the actual Riff box. I'll keep trying to see if the phone boots up as I got my hands on a new battery.