Related
I was flashing jackos s3 radio after the phone finished installing the update it will not start at all any fix for this previously it was stuck at htc screen did the task 29 and flashed the jackos rom will stay stuck at htc screen thanks
Is your device GSM or CDMA?
is gsm tried everything I could think of, I hope you have a suggestion the only thing that I found is the last resource is that riff jtag box ($150 plus shipping) but I don't have it, and I don't think is worth it for one phone.
Try...
Try flashing stock rom....i think hold volume down and press power button..go to bootload screen/ three color screen..
.then insert cable and flash stock rom
that is the biggest problem I don't get a bootloader screen or any screen any longer it seems like the the cellphone is dead, it tried holding the reset button with battery and without and it makes no difference, it just died after flashing the radio and I don't get a screen anymore I tried a different battery I have a separate charger, and it doesn't work either...
Not enough information to work with really, could you say more about the steps you took in this flash. There is a lot of help here on XDA but only IF enough is known. What you describe is not a common failure. Somethings been left out.
Just have to wonder if you were stock rom prior to the flash, were you unlocked, did the device operate properly before ANY flash was attempted ect....Not knowing were you started and the steps taken make it difficult, xda folks love fixing these things TELL US MORE !!!
PS I'm only here once or twice a month but really have gotten nothing less than the best help here when asked for with better information.
Let me see this telephone is not mine is from a friend that gave to me to fix it, the phone it was unlocked and on the bootloader screen it said security disabled I think something like that,
what it was wrong is that it was stuck on the htc white background
everytime you turn the phone on, I read some threads on how to repair this and found out how to get to the bootloader screen,
then I flashed, Rhodium-HardSPL_V2_00R3_185HSPL it completed and then rebooted, I flashed then Jackos S3 JackFULL 1.4.0, it completed 100% but I got the same error, I read on some thread that you somebody fixed that error by using task 29 so I flashed task 29 and then I flashed the same rom, it was stuck on the same htc screen so I checked on the rom folder there was another file recommended radio Radio_Rhodium_4.49.25.91 I flashed that file to see if it fixed the problem, but after it finished the phone turn itself off and did not start again,
then I checked the battery it had charge,
I tried a different battery nothing,
if I remove the battery slowly I see the red low battery light on for an instant
so the phone is getting power,
I pressed the power button and down button nothing
just the power button nothing,
tried holding the reset button nothing,
it is in a brick state,
is there any hardware mod for this phone,
I fixed a samsung captivate with a tool you created using a micro usb head some resistor in order to put it in a state called download mode,
the only thing I found on how to revive this is this box http://www.gsmserver.com/shop/gsm/riff_box_jtag.php the problem I don't have the money for it...
is that enough information? and of course the rom I use it was a gsm rom
I wonder if a hard reset would snap it into doing something...remove the battery, wait a couple of minutes, put the battery back in.. hold the talk and end buttons down and press the power button...I'm really not sure as I have not experienced this, but...I don't think anything would be a waste of time at this point
---------- Post added at 12:16 PM ---------- Previous post was at 11:52 AM ----------
oops...oh yeah...if the device does power on and you get a screen press the volume up next and see what if anything happens
that is right I have to try everything, but it didn't work but thanks anyway any suggestions I am still open to try everything...
I know you say the phone is GSM but...could you please tell us which, if any, carrier information the phone was designed for, and which rhodium version it is by looking at the sticker under the battery?
Ive been looking for a while into a solution for your symptoms and what Ive found thus far indicates a wrong radio was installed...CDMA radio to GSM device, or vice versa....there are people on this site who know everything, I am not one of them, but...it might be the case where you use MTTY...a low level type of command you can send to the phone via usb from your PC...I'm still looking...perhaps try looking too and cut the time in half lol...the low level commands can get to the device without it being in bootload screen...I think...as I said, I'm still looking for solutions
---------- Post added at 09:46 PM ---------- Previous post was at 09:10 PM ----------
read up on this...
http://forum.xda-developers.com/showthread.php?t=371154
and there's an example here
http://www.youtube.com/watch?v=4fQE0P3diKg
I'm not saying this will work and certainly dont try anything without reading up on the process in the first link
---------- Post added at 10:07 PM ---------- Previous post was at 09:46 PM ----------
I've been reading the thread of the link I posted, it's not relative to the Rhodium specifically, but still good reading until some Rhodium specific links can be found
So here's the story ; I bought the phone worked normal , nodo installed , security update installed , i then register a developer account , installed mango beta 1 , then beta 2 , after that the leaked rtm mango, random restarts.I thought its normal since the drivers aren't updated for mango. Reverted back to nodo today so i can get the mango through official channel with the normal driver. I keep checking no mango , i then tried a disconnect trick a discovered on the forums. version 7401 was installed and then random restarts much often than usual. After disconnecting the phone on step 9 and removing battery couple of times phone booted up and stayed on. After that the Zune prompted me to install Mango. After doing everything zune said Step 8 of 9 Restarting your phone. Phone was stucked on HTC logo disconnected phone removed battery like i did before... but now i can't start it up , no logo no nothing , Power + Volume down does nothing... warranty is still valid though , should i send it for repair? Thanks for any reply
If it's a Verizon trophy, look at the leaked HTC roms, they are the same thing.... (version for version they are exactly the same as you get from the Zune download).
Flash that rom and you'll be on Mango final with all the features that you want.
DavidinCT said:
If it's a Verizon trophy, look at the leaked HTC roms, they are the same thing.... (version for version they are exactly the same as you get from the Zune download).
Flash that rom and you'll be on Mango final with all the features that you want.
Click to expand...
Click to collapse
Its an unbraded open market htc trophy , the problem is i can't boot it up...
spyridonas said:
Its an unbraded open market htc trophy , the problem is i can't boot it up...
Click to expand...
Click to collapse
Check in the HTC Trophy area on this site... there is a bunch of roms, find a NODO rom and put your phone in boot flash, flash it, it should get you back to a working phone.
I know about the CDMA version of the phone and you have the GSM, so I can't help you with the exact rom you need but, I am sure you can find it.
DavidinCT said:
Check in the HTC Trophy area on this site... there is a bunch of roms, find a NODO rom and put your phone in boot flash, flash it, it should get you back to a working phone.
I know about the CDMA version of the phone and you have the GSM, so I can't help you with the exact rom you need but, I am sure you can find it.
Click to expand...
Click to collapse
The phone won't power up , no flash boot no nothing...i do have my own backup of nodo rom no need to find another one , the problem is i can't boot it up !!!!
If it won't boot up, and no trick to make it boot up works, then get it swapped. No reason to ask here when no one here works for HTC or whoever you bought the phone through.
From the random reboots you mention, you might have had a semi defective unit from the start as it shouldn't be rebooting that much on you if at all.
Exactly the same problem here. Going to contact htc sav :/ to fix that.
spyridonas said:
After doing everything zune said Step 8 of 9 Restarting your phone. Phone was stucked on HTC logo disconnected phone removed battery like i did before...
Click to expand...
Click to collapse
This was the issue; how long did you wait?
I remember when I last upgraded, the phone ages to reboot. You have to be patient!
Same problem here.
HTC Trophy. Was on NoDo (7392 or something like that) and never installed any pre-release Mango. Phone is not developer unlocked or unbranded (it's VF).
Did the disconnect trick last night to get the update. It installs 2 updates and the first went fine but the second (which I think was the HTC firmware update) took quite a long time and eventually got to step 8 of 9 (restarting phone) but stayed there for at least an hour with the HTC logo on screen.
I left it and went to sleep. Woke up this morning with Zune still saying step 8 of 9 and phone blank.
Phone is completely dead. Whether it's unplugged, connected to PC or connected to the charger it won't power on. It doesn't even show the red or green power light. Camera + Vol Up + Power also does nothing. Checked battery with multi-meter and it has power so it's not a charging issue.
It looks almost like a hardware failure (by the fact that there's no activity at all). Maybe the firmware update taking so long overheated something in the phone.
try with power+down vol+camera = usb mode host
maraver said:
try with power+down vol+camera = usb mode host
Click to expand...
Click to collapse
Tried that too. Still nothing. :-(
Nothing. The Telephone act like there's no battery in it...
---------- Post added at 02:23 PM ---------- Previous post was at 01:54 PM ----------
Nothing. The Telephone act like there's no battery in it...
I have the similar problem while updating to Mango. But my current state is a little bit different (may be a bit better then other people). It is stuck in the HTC logo screen.
I have can get into bootloader, but the official bootloader doesn't allow me to do anything.
dears
i have same problem with my trophy
first step: if your trophy can't enter boot mode you have to go to profisnal tool like Riff Box or ORT Box thay used JTAC method and you have to open your phone to connect JTAC cable then repir Boot area and no way to repir this area without this solution
after repir now you can enter boot mode
sec step : flash your phone with Correct flash files
but my Q is what kind of flash can be correct i try many but still hang on HTC logo
we need some one give us correct info about :
all flash file Brand or unbranded and what the true one
are we need to repir RSPL Or HSPL
These sound like factory faults to me. I've been playing around with different ROMs ever since I got my phone,no problem. The only things I wish I had were usb storage and tethering, I wish they were possible without going through an encyclopaedia of instructions,that's a sure way to brickville.
Sent from my 7 Trophy using XDA Windows Phone 7 App
spyridonas said:
The phone won't power up , no flash boot no nothing...i do have my own backup of nodo rom no need to find another one , the problem is i can't boot it up !!!!
Click to expand...
Click to collapse
IM0001 said:
If it won't boot up, and no trick to make it boot up works, then get it swapped. No reason to ask here when no one here works for HTC or whoever you bought the phone through.
From the random reboots you mention, you might have had a semi defective unit from the start as it shouldn't be rebooting that much on you if at all.
Click to expand...
Click to collapse
suzukube said:
Nothing. The Telephone act like there's no battery in it...
Nothing. The Telephone act like there's no battery in it...
Click to expand...
Click to collapse
Leave the phone to wall charger for at least 30 min and then it will boot up
colossus_r said:
Leave the phone to wall charger for at least 30 min and then it will boot up
Click to expand...
Click to collapse
I tried that a few times. In fact I left it plugged into the wall charger overnight. Still nothing.
I ended up getting a replacement phone from my carrier. Interestingly the battery was completely flat when I put it into the replacement phone. They only replace the main shell (refurb), not battery, charger cable or back cover. I had to leave it plugged into the charger for a minute before it turned on.
The difference between the dead phone and the replacement is that the replacement would charge (immediately showed red light when plugged in) but the bricked phone didn't charge or even seem to recognise that a charger was connected.
I do wonder what would have happened if I had charged the battery some other way and then put it back into the phone. I'll never know because the courier took my phone away when they dropped of the replacement.
The worst part was being without my phone for 4 days (over a weekend) and then having to reconfigure and reinstall everything on the new phone (because stupid Zune does not have any way to restore a backup to a different phone). I think the only thing I really lost was my text messages in the end.
---------- Post added at 06:15 PM ---------- Previous post was at 06:02 PM ----------
Vukile said:
These sound like factory faults to me. I've been playing around with different ROMs ever since I got my phone,no problem. The only things I wish I had were usb storage and tethering, I wish they were possible without going through an encyclopaedia of instructions,that's a sure way to brickville.
Click to expand...
Click to collapse
Well I've had my phone for 7 months without any issues, including the couple of updates we've had since February. I think what caused the problem here was that the Mango update included firmware updates from the manufacturers. It actually applies one update, restarts the phone and then applies a second update which is the HTC Firmware update. That's the one that doesn't complete properly. Looking around online there seems to be a few HTC (Trophy and HD7) users experiencing the same thing.
I applied the Mango update to my replacement phone (also a Trophy 7) without any problems so maybe it only affects certain Trophy phones.
And I agree with you on the tethering - that's one of the main features I seriously miss from my previous phone!
Nomad1011 said:
And I agree with you on the tethering - that's one of the main features I seriously miss from my previous phone!
Click to expand...
Click to collapse
+3 or 4 or 10,000
I miss this so much... (I keep a spare 6.5 phone around to do tethering when I need it, just wish I could do it with my trophy)
most likely its a faulty usb port or some problem with yr pc when transferring the update which bricked yr phone
Magpir said:
most likely its a faulty usb port or some problem with yr pc when transferring the update which bricked yr phone
Click to expand...
Click to collapse
Then a lot of people must have the same problem with their PC or USB port (including 3 people on this thread alone). I can't post links yet but if you do a Google search for "mango bricked HTC windows phone" there are quite a few links, each with multiple people having the exact same problem (completely dead phone, no power or lights at all). I wouldn't call it "widespread" yet but there's definitely an issue affecting certain HTC phones when updating to Mango.
I had done previous updates on that phone (using the same PC, cable, etc) without issues and the first part of this update worked fine (including the restart). Replacement phone (exact same model) updated fine on the same PC with same cable (including the HTC Firmware update).
Hi everybody!
I have an almost 2 years old DHD which I think is completely bricked. It was working for approximately one years perfectly and then suddenly it stopped working. Whenever I tried to turn it on, it only vibrated once and did nothing more. Sometimes it turned on and these working periods were enough to restore to stock condition (It was rooted and had Eng S-OFF before.). I had brought it to service and they said they was not going to repair it as the device got water damaged. I'm pretty sure it was not! After a few weeks, it started working again. I was using it for 3 months then it bricked again and it's the situation today as well.
Previous week I looked into the development thread and saw all of these new amazing roms. So I took my DHD to see if it's working or not. The situation is the same. Everytime I power it on, the phone only vibrates once and nothing happens. I'm not able to get into hboot mode. At some very rare occassions the phone turns on and works flawlessly till reboot. When I connect it with USB, the computer doesn't recognize it. Battery is charged, I even tried another battery.
Does anybody know what happens with the phone? I'm open to any possible solutions to try. Please don't suggest to bring it to service or repair it, because I have another phone, just want to try to recover it and ask your ideas about the problem.
Thanks in advance!
Greetings,
Adam
So you say you cant enter in fastboot or recovery?
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
paescheh said:
So you say you cant enter in fastboot or recovery?
Click to expand...
Click to collapse
I cannot enter into hboot mode. Didn't try recovery, but assume it's the same.
waterbox said:
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
Click to expand...
Click to collapse
I also think it's a hardware problem. Will take a more careful look at the battery.
Sent from my CM10-powered GT-I9103
need help
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
goofed again said:
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
Click to expand...
Click to collapse
Wrong sub forum buddy, post in the One V Forum.
Its possible that there isn't "water damage", but there could be moisture getting into the phone causing it to act erratic. To cancel out that possibility, submerge it in a closed container full of rice for a few days
Sent from a satellite
Today I was in my car sitting in a parking lot, had my phone propped on my steering wheel with the txt app open when the screen when blue then shut down. I tried to power it on but it wouldn't come on, I pulled the battery hit the power button, the LG logo came up for a few seconds then shut off and the only way to turn it on again would be to pull the battery. Holding the power and volume rocker button down will turn it on to recovery. The phone is rooted so when I go to factory reset i've had 2 times it loaded to TWERP recovery but then the blue screen would come up again and I can't do anything. Most of the time it will end up in a green screen with the TC Crash, Demigod crash screen. Plugging it into my computer does load it as a device but I'm not able to access the phones storage. Has anyone ran into this issue and first question, is there anyway to recover data? Second question, is this a hardware related issue? I'm about to try and flash it back to stock since I can't get into TWERP but i'll wait for a response before I do that.
I tried to boot to download mode, I hold the volume up rocker and then plug in a USB, it shows download mode icon for a quick second but the screen goes black. I tried the LG flash tool but it doesn't get past step 1. Any one have any ideas i'm fresh out. Only new thing to report is sometimes instead of the green TZ crash i'm getting an orange RMP crash screen but with the same options as the green screen.
Need to know know a little more before I can reach my decision on where to start.
ROM
Kernel
Thermal mods
Was the phone hot?
Does it get hot upon starting?
Baseband?
I had this happen before but never to the extent that your explaining. Kind of sounds like a kernel panic.
DroidsOnRoids said:
Need to know know a little more before I can reach my decision on where to start.
ROM
Kernel
Thermal mods
Was the phone hot?
Does it get hot upon starting?
Baseband?
I had this happen before but never to the extent that your explaining. Kind of sounds like a kernel panic.
Click to expand...
Click to collapse
I can tell you what ROM it was and thats about it. Resurrection-Remix-LP-v5.5.8-20151027-vs985
Was running sold for months. Phone wasn't hot and didn't notice it getting hot at start up. Phone had 99% battery last time I checked before the blue screen.
I did some research about the LG G3 and blue screen and its a common issue from what i've found. No fix really
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 u could try this
TheMadScientist420 said:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 u could try this
Click to expand...
Click to collapse
WOW, not sure about that. I'll see. Going to call verizon and see if they can do anything first.
Youll have to pay cause ure waranty is voided being rooted its a sure fire fix for almost all hard bricks and everything its not as bad as it looks i have had to myself on my g2 and g3
---------- Post added at 06:07 PM ---------- Previous post was at 06:02 PM ----------
Do u get the screen press up for dl mode. Try a bat pull and boot into recovery if possible
TheMadScientist420 said:
Youll have to pay cause ure waranty is voided being rooted its a sure fire fix for almost all hard bricks and everything its not as bad as it looks i have had to myself on my g2 and g3
Click to expand...
Click to collapse
Are you sure its a hard brick? From all the things i've read about this blue screen is its a hardware issue. My phone is showing up in the device manager under ports. Can I skip the first part?
Itsna kernal panick some people claim its from over heat others other issues if ure phonenshows up as qusb bulk or something like that then i believe u can the pin groung is to reset it to get it into bulk mode so from there u reflash all the primary gtp partitions then u can get to download mode to restore using stock tot. Ive nevernhad this issue happen but no its not technicly a hard brick but so far i cant find a solution but the method ive shown u usaully brings back all bricks and issues it could be a hardware issue but 9 outa 10 times its a software or firmware issue
---------- Post added at 06:20 PM ---------- Previous post was at 06:15 PM ----------
If u got usbbulk mode on com ports not step 4 but num 4 further down the page is where u start but u have to dl wilcracker and ure stock tot file
TheMadScientist420 said:
Itsna kernal panick some people claim its from over heat others other issues if ure phonenshows up as qusb bulk or something like that then i believe u can the pin groung is to reset it to get it into bulk mode so from there u reflash all the primary gtp partitions then u can get to download mode to restore using stock tot. Ive nevernhad this issue happen but no its not technicly a hard brick but so far i cant find a solution but the method ive shown u usaully brings back all bricks and issues it could be a hardware issue but 9 outa 10 times its a software or firmware issue
---------- Post added at 06:20 PM ---------- Previous post was at 06:15 PM ----------
If u got usbbulk mode on com ports not step 4 but num 4 further down the page is where u start but u have to dl wilcracker and ure stock tot file
Click to expand...
Click to collapse
OK thanks. I mean I guess I don't have anything to loose, so i'll give it a shot.
Like i said i couldnt find a solution im no developer ive just been rooting and modding since the first og moto droid ive bricked and fixed a lot of phones this may not be the proper solution i just no its work for a lot of people on a lot of diffrent bricks on both g2 and g3 i know basicly the g2 is unbri kable and sofar so has the g3 since this i wish it was a general sticky
---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------
You can try calling lg but i consider there tecks dumber the crap but they get paid for what they do again 9 outa 10 times they cant help other than u sending it in for repair like i said ure rooted if they find out it is its fixed on ure dime i dont know no cell company has ever helped me out.
What do kind of wire do you suggest using?
I used acouple strands of speaker wire coiled up and a pair of tweezers to hold it end bent it to touch both so i still had a free hand
TheMadScientist420 said:
I used acouple strands of speaker wire coiled up and a pair of tweezers to hold it end bent it to touch both so i still had a free hand
Click to expand...
Click to collapse
This is impossible!
joel71 said:
This is impossible!
Click to expand...
Click to collapse
When u plug into ure pc what ports or coms. What xoez the fone shop up az
TheMadScientist420 said:
When u plug into ure pc what ports or coms. What xoez the fone shop up az
Click to expand...
Click to collapse
After trying for what felt like forever I got it kind of work once. It showed up as QCBATCH on port 6. But once I broke connection it went away and I wasn't able to get it to work again. I'll give it another try sometime today..
Sometimes it takes a bunch of trys
TheMadScientist420 said:
Sometimes it takes a bunch of trys
Click to expand...
Click to collapse
Got it working on the first try today. I used the SIM Card bay for a ground so I didn't have to hold it. Much easier, flashing now, will report back after.
joel71 said:
Got it working on the first try today. I used the SIM Card bay for a ground so I didn't have to hold it. Much easier, flashing now, will report back after.
Click to expand...
Click to collapse
Let me no how it goes
I did the steps but it still booted to a RPM CRASH screen, I couldn't get into download mode. I'm trying to flash Cache, System, Userdata, and SB1 now.
Hi guys. I badly need help.
My m8 wont turn on.
I was chargin it the other night 32% when the phone freezed while downloading facebook from playstore. So i restarted it and it will only show the white background and htc logo. So i tried to boot it into bootloader. It dit boot btw, and when i entered recovery mode it just wont turn back on, the phone was freaking hot and when i listened closely there was a soft whirling sound inside.
I tried every troubleshooting i could find (except for connecting it to a pc, because i am a mac user) but to no avail the phone would not come back to life.
I am so depressed and wouldnt wanna go to the technician yet if i can still find some solutions to bring it back to life again.
Stock android 6.0
Asian 2.5ghz version
Phone age 1yr6mos
Never been dropped
Please help me.
If there is a way to fastboot it using command prompt because someone was suggesting me to do it. But i am a mac user. So helpless here.
up for Ms. Biangka! ed abellon here mentioning @ckpv5 @redpoint73 for some help,
imfuzzyyy said:
mentioning @ckpv5 @redpoint73 for some help,
Click to expand...
Click to collapse
I have been summoned!
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
Purplee said:
I was chargin it the other night 32% when the phone freezed while downloading facebook from playstore. So i restarted it and it will only show the white background and htc logo. So i tried to boot it into bootloader. It dit boot btw, and when i entered recovery mode it just wont turn back on, the phone was freaking hot and when i listened closely there was a soft whirling sound inside.
Click to expand...
Click to collapse
So what is the current status of the phone, exactly? Does the screen turn on at all: white HTC logo screen? Bootloader? Can you get into recovery?
Or the screen won't come on at all?
The whirling sound is a bit disturbing. I haven't heard a report of something like that while trying to boot. The only mechanical components I can think of, that can be making that sound is the camera and vibration motor.
---------- Post added at 09:59 AM ---------- Previous post was at 09:56 AM ----------
Purplee said:
If there is a way to fastboot it using command prompt because someone was suggesting me to do it. But i am a mac user.
Click to expand...
Click to collapse
I don't know jack about Macs, so I can't really tell you much about fastboot or recoverying using a Mac. I know you can do it (adb and fastboot on Mac), and think I remember some kind of guide here; so you may search around for that.
You should also see if there is an RUU zip for your version. If so, you can put in on an SD card and run it, without a PC.
---------- Post added at 10:02 AM ---------- Previous post was at 09:59 AM ----------
Purplee said:
I tried every troubleshooting i could find (except for connecting it to a pc, because i am a mac user) but to no avail the phone would not come back to life.
Click to expand...
Click to collapse
Can you be more specific about what you tried, and the details on the results for each? We have no way of knowing what "every troubleshooting you could find" means.
Also, is the phone modded at all (bootloader unlocked, root, custom ROM, s-off, etc.) and is the bootloader currently unlocked, locked or relocked?
hi
the status of the phone is dead. no power. no led light lit when plugged in charger.
i tried these troubleshooting methods:
1. power + volume up for 20 secs (no response)
2. power + volume down for 10 secs (it should vibrate and boot up but it DID NOT)
3. power + volume up an down for 2-3mins while plugged in a charger (nothing happens)
bootloader is locked, all stock not modded
i did find a tutorial on how to install adb and fastboot in my mac. installation was successful but when i try to enter cmd like adb devices it would reply somewhat like adb: no command found.. so im planning to find a windows based pc. if not just leave it for the technicians to rule out the problem.
is this the first sudden death incident? and can the board of the m8 be easily damaged? i never dropped the phone, ever. it just concerns me if its the board that is defective
Purplee said:
hi
the status of the phone is dead. no power. no led light lit when plugged in charger.
i tried these troubleshooting methods:
1. power + volume up for 20 secs (no response)
2. power + volume down for 10 secs (it should vibrate and boot up but it DID NOT)
3. power + volume up an down for 2-3mins while plugged in a charger (nothing happens)
Click to expand...
Click to collapse
Try power+vol up for a minute or 2, with and without the charger plugged in. A few folks have had success with this.
Also try to leave the charger connected for a few hours, and see if there is any change.
If none of this works, I would likely assume a sudden hardware failure. It would also somewhat explain the sudden freezing and failure to boot on a fully stock device, with no other apparent events or actions that would cause such a failure.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
Purplee said:
i did find a tutorial on how to install adb and fastboot in my mac. installation was successful but when i try to enter cmd like adb devices it would reply somewhat like adb: no command found..
Click to expand...
Click to collapse
This usually means you need to navigate (change directory) in CMD to the proper folder where the adb files were installed.
I'm clueless on how to do that on a Mac. On a PC, you would find where adb.exe is located, than you can press Shift+right mouse button and select "Open command window here" (otherwise, you need to manually change directory in CMD using command "cd" with the proper file path).
Purplee said:
is this the first sudden death incident? and can the board of the m8 be easily damaged? i never dropped the phone, ever. it just concerns me if its the board that is defective
Click to expand...
Click to collapse
This certainly wouldn't be the first incident of an apparent and spontaneous hardware failure. We've seen a a few failures like this (no other apparent cause or fix). And anecdotally , these reports seem to be getting a little more common as the device goes on 2 years old. Folks here with more knowledge than me will often say emmc failure can be the cause. emmc chips just go bad eventually. The device did not necessarily get dropped or damaged.
There is the possibility of a bad capacitor on the motherboard. From the description of the sound that you can hear (although I would consider it a high pitched whining sound), it sounds like it might be possible. Capacitors sometimes will give off a high pitched whining noise when they go bad. I could be wrong but my guess is you have a hardware issue of some kind.
robocuff said:
There is the possibility of a bad capacitor on the motherboard. From the description of the sound that you can hear (although I would consider it a high pitched whining sound), it sounds like it might be possible. Capacitors sometimes will give off a high pitched whining noise when they go bad. I could be wrong but my guess is you have a hardware issue of some kind.
Click to expand...
Click to collapse
That is some brilliant detective work! I've heard of capacitor noise in regards to the AC chargers, but I never would have thought of it happening on the phone. It makes sense. I could only think of mechanical components of the phone making the noise (camera, vibration motor) which didn't really make much sense.
redpoint73 said:
That is some brilliant detective work! I've heard of capacitor noise in regards to the AC chargers, but I never would have thought of it happening on the phone. It makes sense. I could only think of mechanical components of the phone making the noise (camera, vibration motor) which didn't really make much sense.
Click to expand...
Click to collapse
Well, the camera or vibration motor wasn't such a bad idea either. Have no idea if they could get stuck in some way and make a noise like that or not though. My first thought was a capacitor but then reading on I saw you mentioned them. Hadn't even thought of them. Either way, I'm guessing this is a hardware issue from the description of what happened and the noise being heard. I've seen and heard the capacitor issue a few times in my days. It makes me wonder.
redpoint73 said:
Try power+vol up for a minute or 2, with and without the charger plugged in. A few folks have had success with this.
Also try to leave the charger connected for a few hours, and see if there is any change.
If none of this works, I would likely assume a sudden hardware failure. It would also somewhat explain the sudden freezing and failure to boot on a fully stock device, with no other apparent events or actions that would cause such a failure.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
This usually means you need to navigate (change directory) in CMD to the proper folder where the adb files were installed.
I'm clueless on how to do that on a Mac. On a PC, you would find where adb.exe is located, than you can press Shift+right mouse button and select "Open command window here" (otherwise, you need to manually change directory in CMD using command "cd" with the proper file path).
This certainly wouldn't be the first incident of an apparent and spontaneous hardware failure. We've seen a a few failures like this (no other apparent cause or fix). And anecdotally , these reports seem to be getting a little more common as the device goes on 2 years old. Folks here with more knowledge than me will often say emmc failure can be the cause. emmc chips just go bad eventually. The device did not necessarily get dropped or damaged.
Click to expand...
Click to collapse
Thank you so much for your help guys. Ive been to technician he wont open it coz he doesnt even have parts. I will try and look for a PC and my friend who is also a member here will help me walkthrough the process in cmd. That would be my last chance to wake it up.
If not, i think i need to visit singapore soon. Htc repair center here in the philippines is crap, untrustworthy. Thank you sir!
robocuff said:
There is the possibility of a bad capacitor on the motherboard. From the description of the sound that you can hear (although I would consider it a high pitched whining sound), it sounds like it might be possible. Capacitors sometimes will give off a high pitched whining noise when they go bad. I could be wrong but my guess is you have a hardware issue of some kind.
Click to expand...
Click to collapse
Thank you sirs @redpoint73 and @robocuff
I will try and visit manila since the resources there are much broad than the city i live.