Related
Hey everyone,
I have read the various topics with a similar title but none helped.
Here is my problem, I bought a used HTC Desire on eBay. It booted just fine on the first start, then I did a factory reset (from within the Android system menu).
Since then, I'm stuck at the white screen with the green HTC logo. I have tried to get into bootloader mode by removing the battery, holding vol down and power, but it just goes straight to the white screen again.
Also connected the phone to the pc, but adb isn't picking up anything...
Any ideas?
Try Power+Back button.
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Goddchen said:
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Click to expand...
Click to collapse
So you bought a Desire with broken volume keys.
Are you s-off?
abaaaabbbb63 said:
So you bought a Desire with broken volume keys.
Are you s-off?
Click to expand...
Click to collapse
looks like...
in fastboot mode it shows that it is s-on.
Goddchen said:
looks like...
in fastboot mode it shows that it is s-on.
Click to expand...
Click to collapse
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
abaaaabbbb63 said:
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
Click to expand...
Click to collapse
Thanks for the advice, I downloaded the 2.3 RUU and it starts the process, sais
rebooting to bootloader
erasing data
sending...
and after ~30 seconds it just shows me a screen that sais "ERROR_UNKNOWN"
On the phone I see a black screen with a silver HTC logo during the process and when I unplug the USB cable after the error it shows the hboot screen that now sais "update failed".
right before the error is shown it display "updating signature"
Goddchen said:
right before the error is shown it display "updating signature"
Click to expand...
Click to collapse
It only says "Error_Unknown"? No error number, anything?
Weird.
This may be the reason:
Now, that may not sound too bad to some of you, but there's more: the 2.3 RUU update is limited regionally, as well. It's not available to users in Germany, North America, South America, South Korea, or Japan.
Click to expand...
Click to collapse
You live in Germany, right?
Use this guide then:
Section 2, S-on
http://forum.xda-developers.com/showthread.php?t=1275632
yes I am in Germany,
made some progress (or not?)
I noticed that the device was "unlocked", so I did "fastboot oem lock" and it was "relocked".
Then the RUU update went through - nearly. At the very end if failed again and now I am stuck at a black screen with the silver HTC logo and triangles in every corner.
AW: Unable to get into bootloader or recovery mode, stuck at white HTC logo screen
Sent from my Nexus 4 using xda app-developers app
wtf... tried again flashing the 2.3 RUU, this time it worked, YEAY
But now I have a bootloop, device starts, vibrates 1 time, waits for 3 seconds, and then vibrates 7 times. And restarts...
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
abaaaabbbb63 said:
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
Click to expand...
Click to collapse
freecer did it, was able to flash the 2.3 RUU again successfully. But now I'm back at the bootloop, but now, it simply does vibrate once (no more 7 vibrations) and reboots after some seconds.
So what can I do now? RUU flashed successfully, I'm running out of ideas...
and again the freezer did it, put it in, normally started via POWER button, it booted right through into Android.
Well, let's see if it keeps running now or if this overheating issue also exists in normal operation mode...
Thanks so much for you help so far, the freezer hint saved this device and hopefully will make my gf very happy tomorrow
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
dethrat said:
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
do you think installing a custom rom of any kind might help?
Goddchen said:
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
Click to expand...
Click to collapse
It's a motherboard fault. If you don't send it to repair, you just got yourself an "Ice-Phone", or a very complex paper holder.
i think a custom rom would help a small bit, like the rom in abaaaabbbb63 sig (mildwild redux) because its small and lite unlike a sense rom. therefor it mite not overheat as quick or as often. but thats only a guess. the only dodgy thing is trying to get ur phone s-off or rooted because if ur phone overheats in the middle of the s-off/rooting progress u could brick ur phone. plus charge ur phone using ur computer coz it uses less power and the phone does'nt heat up as much as plugging into the wall.
Hi guys! I want to send my Nexus 7 (2013) to warranty service because it's bricked and I think the motherboard is destroyed. Will the service understand that the device is unlocked (bootloader) and rooted?
I could be wrong so wait for confirmation from someone else but if it won't even power on I don't think they would know, however if it powers on as far as the white Google logo you can see it is unlocked by the white padlock that is opened at the bottom, or closed lock for locked boot loader.
Sounds like it won't power on though if the main board is dead so I doubt they could know...
If it helps i had an iphone 4 that i jailbroke and it ended up bricked. It wouldnt connect to the computer or anything else. I had the same worry you have and when it was sent off i thought theyd find out. They didnt, and i got a replacement. If it doesnt connect to a computer they just dismantle them for parts. A repair engineer is more expensive to employ than a few idiots with screw drivers.
May be I am wrong about the mainboard. Yeah, I can turn it on, but I can go only to boatloader. It can be connected to computer (only fastboot mode) and there is unlocked padlock.
I guess need to lock the bootloader. But the device does not see any space (free or used) - I was connected it to computer and used a recovery mode with Skipsoft application. May be the memory is dead. It shows that cannot mount any partition. I don't know. Is there any way to lock the bootloader?
I am guessing you used Wug's root toolkit to unlock. I have seen others relock there's when there has been problems similar to yours, maybe check his thread out and ask in there.
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Yeah I know the feeling
I am always worried about devices failing but after I have had it for about a year I wont be so scared and will take more risks with it usually. Only had mine for around 2 weeks and am also worried it could go off at anytime as mine is unlocked and rooted. Lots of people seem to have had problems with this device, my Xperia S never had problems
ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Try this... http://www.android.gs/restore-un-br...4-3-jelly-bean-twrp-and-root-guides-included/
It might at least get it locked for you....
Thank you! I will try that as soon as I go home...
This is pretty much what danvee posted but still..
If you can use fastboot that's a good sign. You probably don't even need to send it in. Try this: http://forum.xda-developers.com/showthread.php?t=2469508&highlight=stock
You say something about no space? If the above link doesn't get you running again try this first: http://forum.xda-developers.com/showthread.php?t=2380913 Worked for me.
You can just flash twrp with "fastboot flash recovery recoveryname.img"(without quotes), wipe, then use the steps in the first link.
If that doesn't work it probably is some kind of hardware problem.
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
ryderbg said:
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
Click to expand...
Click to collapse
heres a funny story but what it resulted in and how i fixed it seem to apply to the problem you have.
i have a cracked screen on my nexus and it was registering a touch at intermittent intervals making the device unusable. i posted in here about the same time you did for help. while i was waiting to see if anyone knew if i could just disconnect the screen and use a bluetooth mouse with a hdmi adapter (slimport not mhl, thanks meekrawb) i connected a usb mouse with an otg cable. the mouse worked but i couldnt see how to turn off touch screen as an imput. as kitkat has been release and i hadnt updated i thought i would give it a try and see if that would reset the screen and stop the touch. It downloaded the update and when it rebooted it opened up a mod recovery screen (i forgot that i had rooted it). it asked me to slide a bar on the bootloader screen to continue. The usb mouse cursor was not present on this screen and the touch screen doesnt work so i couldnt get past it. i turned the device off and on again (what else do you do when your stuck) and it would open the google screen with the unlocked padlock but then just stay on a completely black screen. same as yours. I connected it to the computer and it recognised it. i opened wugfresh's root tool kit (old apple jb's sometimes had recovery abilities built into them so i thought this may aswell) i clicked on flash stock and unroot with the radial button on soft bricked and followed the instructions. now my device is unbricked and even the touch has stopped. Happy days hey. you'll need to unlock your boot loader again but its worth a try before going to the store, you can always lock the bootloader again if it doesnt work.
i know it didnt need all this to say "connect it to the root tool kit and try that" but i thought you would enjoy a laugh
Funny story. But my issue is hardware. The device doesn't show any space in it. No free nor used. I think the memory is dead. Also I relocked the bootloader, but now I cannot unlock it again because there is no space
Now when the tablet is with locked bootloader, it is unrooted, right?
Tommorow I will visit the warranty service and hope they don't understand about rooting and unlocking.
according to an email from "google play support India" , the device will be accepted under warranty as long as it has a stock firmware installed when you send in the device to claim the warranty.
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
raphi809 said:
After many attempts of turning off and doing the power+vol up I got the bootloader to come up
Click to expand...
Click to collapse
Bootloader is power+vol down
raphi809 said:
since everything at this point had failed I picked the factory reset option from the bootloader.
Click to expand...
Click to collapse
I think this is your main problem. Factory reset in bootloader on a modded phone corrupts the internal memory. Use Windows explorer or Device Manager to find the phone's internal memory and format it.
Internal Memory cannot be mounted as USB on the M8 and hence it cannot be formatted from within Windows. Also, no TTY solution talks to the chip afaik. So this way is closed too.
The symptoms described sound like not only the System/Data/Recovery partitions got corrupted but also bootloader to some extend.
Something has happened while your phone was booted that corrupted large portions of your NAND. This does sound like a real hardware failure like a broken RAM to me. But then again RAM would not cause (corrupted) writes to bootloader. That partition only gets overwritten during a flash process. Not from within the phone so i would have no clue how that could get corrupted.
Are you dead sure the drivers on your PC are alright? Are you 101% sure the communication doesnt work because of the phone having an issue?
I would make totally sure drivers for fastboot are ok and then try to run (just any) RUU and try to rewrite the partitions. If you can't get that done, you will have to swallow that bitter pill and send it in. Well i would anyway. No idea what else you could try.
raphi809 said:
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
Click to expand...
Click to collapse
AFAIK, if you can boot into the bootloader, you can still fix it with a full RUU or .zip with all the partitions. (unless you have hardware damage), because if you have corrupt partitions your phone will have a black screen and can be flashed by directly communicating with Qualcomm chip with linux(tried it once on my HTC One X, didnt work as my partition table itself was corrupt)
raphi809 said:
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
Click to expand...
Click to collapse
Don't try to s-on if your s-off. Just get phone in fastboot bootloader mode and run ruu. I've done it several times so it will connect. Just go through the ruu setup and watch it work. If u can't find ruu for latest firmware then try a older one your s-off so u shouldn't have to do anything but plug the phone in fastboot bootloader mode and run ruu.
I never even relock the bootloader when I flash ruu. And I allways flash in fastboot bootloader mode.
I hope this helps. If not I will try to help u figure it out.
Sneakyghost said:
Internal Memory cannot be mounted as USB on the M8 and hence it cannot be formatted from within Windows. Also, no TTY solution talks to the chip afaik. So this way is closed too.
The symptoms described sound like not only the System/Data/Recovery partitions got corrupted but also bootloader to some extend.
Something has happened while your phone was booted that corrupted large portions of your NAND. This does sound like a real hardware failure like a broken RAM to me. But then again RAM would not cause (corrupted) writes to bootloader. That partition only gets overwritten during a flash process. Not from within the phone so i would have no clue how that could get corrupted.
Are you dead sure the drivers on your PC are alright? Are you 101% sure the communication doesnt work because of the phone having an issue?
I would make totally sure drivers for fastboot are ok and then try to run (just any) RUU and try to rewrite the partitions. If you can't get that done, you will have to swallow that bitter pill and send it in. Well i would anyway. No idea what else you could try.
Click to expand...
Click to collapse
Where in Germany do you live, SneakyGhost? My M8 has been giving me nightmares, It is S-Off and today I changed the CID/MID to that of developer edition and installed the relevant Android Marshmallow firmware.zip and then ran the MM RUU from HTC Dev page. No matter what ROM I tried on SuperCID or even on this new MM software, many apps keep on crashing. Unfortunately this has stopped working, unfortunately that has stopped working. I have 3 other friends with M8, never has their phone seen an app crash. I have to restart the phone many times daily to get it to work for some time, while another app randomly crashes. Can you help me?
Thanks
Well if it's crashing a lot after flashing a complete RUU I'm sure the device is faulty. Maybe bad NAND or bad ram. Send it in to HTC. Don't bother setting it back S-ON cuz a.) They'll know anyway and b.) Going back S-ON is dangerous and locks you out from most repair methods you could try in case HTC won't service your device. Just saying because a lot of people seem to be thinking that going back S-ON is increasing their warranty claim chances.
Sneakyghost said:
Well if it's crashing a lot after flashing a complete RUU I'm sure the device is faulty. Maybe bad NAND or bad ram. Send it in to HTC. Don't bother setting it back S-ON cuz a.) They'll know anyway and b.) Going back S-ON is dangerous and locks you out from most repair methods you could try in case HTC won't service your device. Just saying because a lot of people seem to be thinking that going back S-ON is increasing their warranty claim chances.
Click to expand...
Click to collapse
My phone is out of warranty, will HTC entertain me? How much will thay charge for repairs? I think out of warranty repairs cost more than getting a used working phone.
harri2cool said:
My phone is out of warranty, will HTC entertain me? How much will thay charge for repairs? I think out of warranty repairs cost more than getting a used working phone.
Click to expand...
Click to collapse
Super different from country to country. HTC Germany service is worse than it ever was. They contract Regenersis since January 2015 here, same company as in the UK.
You have to keep in mind that HTC's contractors do the checking and validating of your warranty and they go by very tight rules. You can argue and escalate as much as you want, they will charge you if your local HTC is in any way similar.
Globally, HTC has worsened their service approach a lot. I'm waiting for a service/warranty decision regarding an old M7 since half a year. A mate from our team waited six months too, but for HTC to find his M9 which they lost and refused to replace. He only just got it back, unrepaired despite full warranty eligibility.
To sum it up, if your device is older than six months, don't bother. Not worth the hassle and not worth the money. HTC won't do sh!t after six months usually. And the prices, like you guessed, are a nightmare too.
If your NAND turns out to be faulty like I assume, it'll be a mainboard replacement, which equals a new phone. And THAT can be had a lot cheaper on eBay or craigslist.
Motherboard replacement is 200 USD give or take 25 on model (DNA/butterfly was $150 and a m7wlv motherboard was $175. I priced my AT&T m8 and it was $215) for the HTC service centers here in the US. I assume the EU ones are similar in price.
Before blaming hardware, have you changed mid/cid back to stock and ran an ruu to be sure it wasn't a bad flash or compatibility?
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Dlome said:
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Click to expand...
Click to collapse
I would return it
Since I cant do anything until Monday I decided to mess with the phone a little more, I was able to get a custom recovery installed finally so hopefully all I need to do is install a new rom but the problem is the recovery is unable to mount my SD card to perform the install. I can read the sd card when it is in my old phone but not on the HTC One. Currently have Philz Touch installed as the recovery.
Is there any way to fix this or even bypass it all together?
Edit: I have been able to side load CM11 Nightly onto the phone so now it is functioning. I am having an issue with sound though so hopefully I can fix that.
clsA said:
I would return it
Click to expand...
Click to collapse
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
redpoint73 said:
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
Click to expand...
Click to collapse
This sounded like a hardware problem to me
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
Click to expand...
Click to collapse
it's hard to mess the phone up when you can't even get the bootloader unlocked
clsA said:
it's hard to mess the phone up when you can't even get the bootloader unlocked
Click to expand...
Click to collapse
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
redpoint73 said:
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
Click to expand...
Click to collapse
Fair enough ... I read it wrong I guess
clsA said:
Fair enough ... I read it wrong I guess
Click to expand...
Click to collapse
Naw, really looks more like a matter of the OP needs being clear enough, and not giving enough info. If anything, best to get clarification before suggesting warranty service (especially once mods have been started - but again it was hard from the OP's description to know how far it got). Although if it was in fact a hardware defect, of course a warranty claim is valid.
Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
When I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off.
Is there are any way to fix that with out change motherboard ?
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
elween07 said:
Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
Is there are any way to fix that with out change motherboard ?
Click to expand...
Click to collapse
wait why did you run fastboot oem lock??
if you were wanting to lock you need to run an RUU first (for future reference)
by the "phone can't boot anymore" do you mean like nothing. completely dead? (Bricked)
you can't get to bootloader or download mode? Try holding volume up, volume power and power for a few minutes, see if does anything.
does it show charging light?
I am not experienced enough to give more details, esp about motherboard, but if can get to download or bootloader try RUU that matches the firmware on it.
(gotta be very sure about what you're doing when running commands esp. once the device is unlocked. once unlocked it's on you what you flash and run..)
andybones said:
wait why did you run fastboot oem lock??
if you were wanting to lock you need to run an RUU first (for future reference)
by the "phone can't boot anymore" do you mean like nothing. completely dead? (Bricked)
you can't get to bootloader or download mode? Try holding volume up, volume power and power for a few minutes, see if does anything.
does it show charging light?
I am not experienced enough to give more details, esp about motherboard, but if can get to download or bootloader try RUU that matches the firmware on it.
(gotta be very sure about what you're doing when running commands esp. once the device is unlocked. once unlocked it's on you what you flash and run..)
Click to expand...
Click to collapse
Because there is a damn app only can run when the bootloader is locked... so I did that -.-. Now when I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
elween07 said:
Because there is a damn app only can run when the bootloader is locked... so I did that -.-. Now when I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
Click to expand...
Click to collapse
which app?
also why were you trying to lock?
I can't say but it seems like it could be a pain, but I hope not!
elween07 said:
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
Click to expand...
Click to collapse
and some people say natural selection doesn't exist
Oh dear!
I dont like to tell you this, but you have hard bricked your phone and it cannot be fixed using software.
Locking the bootloader is ONLY for when you are on pure stock. Even having a custom recovery (like TWRP) isnt allowed even if the ROM is stock.
In locking it, you have hard-bricked it, and there isnt ANY way to recover this using software. Nobody on XDA has EVER been able to sort this one out.
Your best bet is one of two options:
1. Buy a new phone. Yeah, pain I know, but the HTC 10 is now 3.5 years old and it might be cheaper to just buy a new phone than try to fix it.
2. Get it fixed at a repair shop. I can imagine that a few local places might not be able to do it, but maybe somewhere can. It's worth an ask?
I seem to recall that using a JAVA card or something like that you might be able to fix it, but if you have locked the bootloader with a custom rom on it, then the chances are it is over for you.
Hey, don't beat yourself up too much about it; we've all done stupid things in the past. I reversed my car into a concrete post last month and it cost me a fortune to fix it!
Such is life.....
elween07 said:
Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
When I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off.
Is there are any way to fix that with out change motherboard ?
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
Click to expand...
Click to collapse
Bro, never relock the bootloader. That's just a bad idea. You most likely hard bricked your phone and there is no way back. That's not 100% for sure but if u flashed any non-htc images the bootloader will not boot it. Thats why you keep it unlocked, so it can boot unsigned images. That's why it keeps shutting off.