Develop Bugs

[HELP] Stuck in qualcomm diagnostic mode

So while trying to get wifi working on my CM7 install I tried to install the radio update from http://forum.xda-developers.com/showthread.php?t=1363547
It was successful but when I reboot I get stuck in what people call "Qualcomm Diagnostics Mode." I'm not even sure of that though, when I turn it on it vibrates 3 times, no LED or anything. I've tried the following solution:
http://forum.xda-developers.com/showthread.php?t=1345273
but it doesn't work.
I have my microsd, I tried putting my old ROM on there but that didn't do anything. I don't have access to the internal storage as I can't turn on the phone. ._.
And for me turning the phone on while holding vol - NEVER worked to go into the bootloader, I'd have to reboot from the OS into the bootloader. I have a backup of all my files.
Is there any way I can recover it?
Unfortunetly rooting it voided my warranty, though I'm sure they wouldn't even know about it if I sent it to HTC?
I'm running it on virgin mobile unactivated...
EDIT: I bought the phone from ebay.

Try the 5th post (i think) it should say something about this mess you're in and click thanks if I was able to help
http://forum.xda-developers.com/showthread.php?t=1432425
Sent from my HTC_A510c using Tapatalk

Alright I'll try that but what sucks is I tried something like that but when I hold volume down and power it would never go into the bootloader, I had to do adb reboot bootloader. (but obviously I can't do that when I can't connect to the device, maybe with the mem card?)

Kingherring said:
Alright I'll try that but what sucks is I tried something like that but when I hold volume down and power it would never go into the bootloader, I had to do adb reboot bootloader. (but obviously I can't do that when I can't connect to the device, maybe with the mem card?)
Click to expand...
Click to collapse
did you follow all the steps as described, putting out your memory card, formating, putting the file on it then continuing to follow steps, and patiently waiting ?

Yes I did all of those steps. My friend advised me to just sent it back to HTC.
(But they say that they can detect if it is rooted)

Kingherring said:
Yes I did all of those steps. My friend advised me to just sent it back to HTC.
(But they say that they can detect if it is rooted)
Click to expand...
Click to collapse
well, if you gave that a shot... i read somewhere that there is a way to go out of qualcomm diag mode, i can't find it... you just send it back to your service provider, and act dumb... hopefully they will have too much job and won't bother checking too much your phone...

[Q] htc wildfire s boot loop problem

So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:

a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue

rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.

alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.

rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.

Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you

Softbricked, locked bootloader ... HELP!!

I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.

Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?

Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools

Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.

Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.

Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.

Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.

Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks

Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.

Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.

Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?

Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/

After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...

Are you going to be able to RMA it? Is it still under warranty?

Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha

Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.

Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse

Good news! I got an RMA!!
Thanks for your help everyone!

Google Pixel 3XL fastboot locked and Recovery not working

Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you

try sideloading the full OTA.
https://developers.google.com/android/ota

robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?

v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!

Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you

v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable

robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?

sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes

robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.

sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.

robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.

sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer

i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,

Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.

Any way to fix Bootloader ?

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.