Related
First of all sorry for adding yet another question onto the Q&A, but researching around I can not find much information on this problem.
So anyway I've been having the following problems with my HOX, and now to add to it all Im stuck in APX mode. I left my phone powered off in my bag and when I went to look at it later on I noticed it was stuck on the HTC Boot screen, and the back of the device was VERY warm (battery?) I got it home and plugged into USB and the device just came under APX and as I'm sure you've read, nothing seems to get out of it so I am stuck (Cant enter bootloader)
However;
When I have the device plugged in and hold power+vol up I get the USB connection sounds played in windows, first the new device one (DUN DIN) followed after a second by (DUN DUN) the unplugged sound. THIS time I unplugged between sounds and left he phone for about a minute, plugged it back in and I only heard the new device sound, and now instead of APX my phone is listed under USB Controllers>Unknown Device. Not sure if this is an improvement or not? But I'm hoping its gaining charge from this and will attempt to restart in a while and see if I can enter the bootloader.
Does anyone have any suggestions here?
APX mode means it's dead, nobody here has recovered their phone from that.
An actual brick, sorry.
yeah, that's right, APX is = to seriously hard HW damage...
BenPope said:
APX mode means it's dead, nobody here has recovered their phone from that.
An actual brick, sorry.
Click to expand...
Click to collapse
matt95 said:
yeah, that's right, APX is = to seriously hard HW damage...
Click to expand...
Click to collapse
You're kidding? I can't believe this it was powering on and working (slightly) earlier today! I thought I saw a post
saying someone got out of it just by leaving it for a while
GOOD GOD
I plugged it into charge, left it for about 5 minutes and it has booted back into the phone!!
Resolved I guess
[★] said:
I plugged it into charge, left it for about 5 minutes and it has booted back into the phone!!
Resolved I guess
Click to expand...
Click to collapse
Flash it to stock ASAP, I suspect it's on its way out, and you'll want to use the warranty.
BenPope said:
Flash it to stock ASAP, I suspect it's on its way out, and you'll want to use the warranty.
Click to expand...
Click to collapse
I'm on 1.28 so I cant flash it to stock! Or can I?
[★] said:
I'm on 1.28 so I cant flash it to stock! Or can I?
Click to expand...
Click to collapse
You can install a nandroid backup of stock ROM, boot.img, stock recovery, and relock.
BenPope said:
You can install a nandroid backup of stock ROM, boot.img, stock recovery, and relock.
Click to expand...
Click to collapse
Ok thanks, I have a couple questions though:
I have looked around and can't find a nandroid backup for my CID HTC__001, however I did just find this thread which claims it is possible without a nandroid backup! Am I right?
Also, I'm assuming this wont revert hboot to an older version will it? So won't HTC (if i send it in for repair) see the later hboot and
just work out that I have obviously unlocked my bootloader at some point? Also won't the bootloader say Relocked as appose to
Locked?
Cheers pal!
Yes, you're right, but if it gets stuck on APX, none of that'll matter, unless it manages to magically work again whilst at the repair centre, in which case at least you have HTC signed software on it, so it should be covered.
BenPope said:
Yes, you're right, but if it gets stuck on APX, none of that'll matter, unless it manages to magically work again whilst at the repair centre, in which case at least you have HTC signed software on it, so it should be covered.
Click to expand...
Click to collapse
Ok, you say atleast I will have HTC signed software on it, but still redundant considering it will be 'RELOCKED' right?
On on a side note, member Vcek says that my initial issue sounds more hardware related, so if everything goes tits
up again I may just try invoke the hardware warranty, which apparently isn't effected by unlocking the bootloader
[★] said:
Ok, you say atleast I will have HTC signed software on it, but still redundant considering it will be 'RELOCKED' right?
On on a side note, member Vcek says that my initial issue sounds more hardware related, so if everything goes tits
up again I may just try invoke the hardware warranty, which apparently isn't effected by unlocking the bootloader
Click to expand...
Click to collapse
It's not redundant, they have been known to refuse warranty when unsigned software is installed. It'll make your life easier to install stock software before sending it off to HTC.
It depends where you bought it, but often the retailer is responsible, not HTC, so HTC would be within their rights to refuse a repair if you don't meet their terms. The retailer might not be able to refuse, though. Either way, I'm advising you on creating your own luck.
BenPope said:
It's not redundant, they have been known to refuse warranty when unsigned software is installed. It'll make your life easier to install stock software before sending it off to HTC.
It depends where you bought it, but often the retailer is responsible, not HTC, so HTC would be within their rights to refuse a repair if you don't meet their terms. The retailer might not be able to refuse, though. Either way, I'm advising you on creating your own luck.
Click to expand...
Click to collapse
Ok well I bought it off Amazon so I will get in contact with them in terms of hardware faults. Surely they will need some sort of proof?
[★] said:
Ok well I bought it off Amazon so I will get in contact with them in terms of hardware faults. Surely they will need some sort of proof?
Click to expand...
Click to collapse
I dunno, in the UK, you're pretty safe. Great consumer protection laws.
The phone is less than a year old, so HTC won't need any proof of purchase, but ask Amazon what to do with it.
BenPope said:
I dunno, in the UK, you're pretty safe. Great consumer protection laws.
The phone is less than a year old, so HTC won't need any proof of purchase, but ask Amazon what to do with it.
Click to expand...
Click to collapse
Ok will do.
Stuck in APX mode again.
Hello guys!
First and foremost, I'm new to the forum as well as an Android noob (switched from Iphone 5 half a year ago). I have never rooted my phone nor have I flashed a custom ROM before. I have a 32 GB HTC One M9 from Verizon on stock Lollipop Android, and it has been working perfectly until this morning. I woke up to my M9 stuck in a bootloop. It would boot to the HTC logo, stay there for about 10 sec, then go black and constantly restart again (even as I type this). I can access the bootloader, but it seems none of the options work for me! I can't boot to recovery mode or even power off my phone. It just constantly boots again by itself. I've emailed HTC support and hope to hear from them soon, but I figured why not ask a respected forum as well. I've read up on similar issues from other people, but it seems none of their solutions work for me as I cannot access recovery or even do a hard reset! Any help is appreciated! I want to be able to use my phone ASAP!
- John
Johnnyhoboy said:
Hello guys!
First and foremost, I'm new to the forum as well as an Android noob (switched from Iphone 5 half a year ago). I have never rooted my phone nor have I flashed a custom ROM before. I have a 32 GB HTC One M9 from Verizon on stock Lollipop Android, and it has been working perfectly until this morning. I woke up to my M9 stuck in a bootloop. It would boot to the HTC logo, stay there for about 10 sec, then go black and constantly restart again (even as I type this). I can access the bootloader, but it seems none of the options work for me! I can't boot to recovery mode or even power off my phone. It just constantly boots again by itself. I've emailed HTC support and hope to hear from them soon, but I figured why not ask a respected forum as well. I've read up on similar issues from other people, but it seems none of their solutions work for me as I cannot access recovery or even do a hard reset! Any help is appreciated! I want to be able to use my phone ASAP!
- John
Click to expand...
Click to collapse
S-off or no?
andybones said:
S-off or no?
Click to expand...
Click to collapse
My bootloader says S-ON. I have no idea what it means by the way, sorry I'm new to this.
Johnnyhoboy said:
My bootloader says S-ON. I have no idea what it means by the way, sorry I'm new to this.
Click to expand...
Click to collapse
No worries my friend. Htc will be your best help since its not been rooted.
Best of luck.
An update for all those who might have the same problem. I've successfully contacted HTC live chat support and have found out that my device is defective. I have no idea what the cause might be, or if there is even a solution to fix it yourself. I will be receiving a replacement device in two days thanks to HTC's wonderful customer support and exchange program. Thanks to all who provided input!
Johnnyhoboy said:
An update for all those who might have the same problem. I've successfully contacted HTC live chat support and have found out that my device is defective. I have no idea what the cause might be, or if there is even a solution to fix it yourself. I will be receiving a replacement device in two days thanks to HTC's wonderful customer support and exchange program. Thanks to all who provided input!
Click to expand...
Click to collapse
Then when you get it back. S-OFF and root the dang thing!
Make sure you check the replacement phone really well. HTC is likes to send out lemons as replacements. I went through 8 rezounds in 9 months.
Sent from my SCH-I545 using XDA Free mobile app
I'm having the same trouble and am aborad right now and really need to get my phone working as I won't be back stateside until spring. Is there anyway to download a rom or update to my sd card and boot from there? Soft. Official, Locked, S-ON from bootloader screen.
Carcuqua0079 said:
I'm having the same trouble and am aborad right now and really need to get my phone working as I won't be back stateside until spring. Is there anyway to download a rom or update to my sd card and boot from there? Soft. Official, Locked, S-ON from bootloader screen.
Click to expand...
Click to collapse
RUU
https://forum.xda-developers.com/showthread.php?p=65358513
Sent from my HTC6545LVW using Tapatalk
HTC One M9 Sprint, stuck in boot loop
I just checked the Dead NAND post in the FAQ... matches my issue too.
Q17: My phone is completely stock and started bootlooping during normal usage. Now I can only enter the Bootloader since I face booting errors as soon as I try to enter the Download Mode or the Stock Recovery. How can I fix this problem?
A: This seems to be another symptom of the NAND death (c.f. the black download mode error screen in Q8). So far, it's not fixable without HTC's help. In other words: You need to send your phone to HTC's repair service if you want to keep it.
My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?
Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.
Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...
Good luck. Will Google not rma it?
Okay, I'm giving up, I need someone to help me.
I was given my neighbours HTC One M9. It was working just fine. After he gave it to me, first thing I did was a factory reset because he didn't delete anything.
After that, the problems began. When I boot up the phone, even directly after resetting and even before the setup, I get an error "Google App stopped working". And after that, all couple of seconds another "com.google.process.gapps stopped working".
I tried several of the fixes out there on the web, but it didn't go away. I did another factory reset, and again even when I setup the phone I get those errors.
There is still Android 6.0 on the phone, so I wanted to update to 7.1
During install, I got the red triangle screen, on both attemps. Well, f*ck.
So, I went on to install a new OS. Never did this before, so I though this is a good chance to learn some more about Android.
It just got even more strange. When I'm in the bootloader, I saw
***Software status: Modified***
S-ON
LOCKED
***Security Warning***
Especially the modified software was very strange, since my neighbour has neither a clue nor any interested of fiddling with phones.
When I tried to go into Download Mode, it said "failed to boot into download mode".
Recovery mode worked just fine.
Therefore, I couldn't do anything to install a new OS.
Next I bought the Sunshine App and S-OFFd my phone, which worked just fine.
Now I'm S-OFF, unlocked and the Security Warning has gone. The software is apparently still modified.
But when I go into download mode, I get the black screen with the silver logo and red text for a while, then the phone proceeds to boot normally.
What the f*uck? I'm just out of idead what to do now. Please don't let it be a dead nand... it's such a nice phone, and apart from the google app errors, it works perfectly. I used it for some surfing around today and it works really well. I can't imagine it being broken.
Thanks for your help!
What variant do you have? Firmware version?
side_flip15 said:
What variant do you have? Firmware version?
Click to expand...
Click to collapse
Firmware is 3.35.166.12
I don't know exactly about the variant, this is what the IMEI checker says:
SKU , VF , German , CHE , HTC , CH , Swisscom , Bootloader Lock , Dark Gunmetal/Dark Gunmetal , w/o SIM Lock , HIMA#UHL-D1
I have a bug report of the gapps-Error. Would that be helpful?
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Flippy498 said:
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
Click to expand...
Click to collapse
Flippy498 said:
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
I didn't have to revive it, except that Google-error it works beautifully. That' broken download mode the only symptom I have. The phone is (meanwhile after Sunshine) S-OFF
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Click to expand...
Click to collapse
Well, there are two things that leave me hoping it's not a dead nand.
• Apart from that com.google.process.gapps-error, it works like a charm. No crashes, no sudden reboots. I really can't imagine a broken part of a motherboard making no trouble, wouldn't that render the part
useless? And is that Google-App Error really relatable?
• After letting the Sunshine App do its job, I don't get an error message in the download mode (well, it just boots normally after a while), the security warning has gone as well. Only the modified software is
suspicious.
side_flip15 said:
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
Click to expand...
Click to collapse
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue.
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue. Great, thanks!
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
Click to expand...
Click to collapse
Yes, I know. Maybe I just don't want to accept that fact to keep my motivation to try to save the phone...
So what my optimism suspects is that somewhere deep in the firmware there is something corrupted. That leaves the System modified and the Google app confused.
After all, recovery mode works just fine. If you check what other people experience with a dead nand, it's got to do with sudden reboots, bootloops, failed download AND recovery modes et cetera.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Click to expand...
Click to collapse
A little more hope rised in me...
sechsgangschakter said:
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Click to expand...
Click to collapse
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
SAME HERE PROBLEM PLEASE HELP
I HAVE HTC ONE M9 OPJA100 JUST GO ON LOCKED SCREEN WHEN REBOOT TO BOOTLOADER ITS RESTART AGAIN EVEN NOT GO DOWNLOAD MODE OR RECOVERY MODE.
I WAS JUST MAKE ROOT THEN ITS STUCK ON LOGO
NOT GO FASTBOOT MODE TO CHECK CID OR FIRMWARE
WHAT I DO ?????
ITS LOCKED
S-ON ALSO
side_flip15 said:
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
Click to expand...
Click to collapse
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
sechsgangschakter said:
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
Click to expand...
Click to collapse
Glad I helped you:highfive:
side_flip15 said:
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Click to expand...
Click to collapse
Just for the record, that's not my thread. It's owned by Sneakyghost.
@sechsgangchakter: I'm glad to hear that your phone is working, again.
Flippy498 said:
Just for the record, that's not my thread. It's owned by Sneakyghost.
Click to expand...
Click to collapse
Oh god! Sorry
Credits to @Sneakyghost :highfive:
Hello, I am having a very similar issue. I am looking for the hosd.img file for Verizon. I dont see it at https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml. Please help. Thanks
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Flippy498 said:
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Click to expand...
Click to collapse
So no one knows of one available for Verizon m9? What would happen if I used a GSM one?
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Flippy498 said:
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Good idea, ill give that a try. Thanks
Dear Community,
My HTC10 is apparently dead but I trust that someone could have a great idea.
How it happened:
1st my config
- S Off
- Unlocked BL
- Running custom Rom - MHD latest version
- Custom kernel from tbalden
So the phone was at 65% of battery.
I rebooted in download mode to check some info (CID and version Mailly).
Then selected System Reboot.
It rebooted fine but then it became impossible to type in my pin code.
So tried to reboot with hardware combination... No sucess...
Then pressed and hold vol up + power for a while then the button at the bottom of the screen blinked 5 times then nothing.
Now it is not responding at all and even when I plug it to charger the led remains off.
I have also tried adb devices from pc... No success
Sent from my HTC EVO 3D X515m using XDA Free mobile app
Any advises or recommended testing méthod ?
chrisftlse said:
Any advises or recommended testing méthod ?
Click to expand...
Click to collapse
If it's not booting to any mode with all button configurations than we can't suggest or do anything.
Let it charge with the wallcharger for a while and try to power it up, connect the phone to a laptop and try to power it up with various button combinations.
See if the phone is in the devices list of the laptop/pc when you connect it, if you see a Qualcomm device it's probably bricked.
chrisftlse said:
Any advises or recommended testing méthod ?
Click to expand...
Click to collapse
Hold the volume down and Power together until it reboots.
leonardojt said:
Hold the volume down and Power together until it reboots.
Click to expand...
Click to collapse
Like that wasnt suggested in my post
Thanks Guys !
I have tried this but no success...
I am now trying to apply another possible solution as I read somewhere that if I am still able to see my device (even if it is the qualcomm HS-USB QDLoader 9008 plugged in my PC)... Then still chances exists to revive it.
But I still have to dig down this website (http://www.androidbrick.com/kategori/teknik-unbrick/)
I any of you here have reach this success a good experience sharing is more than welcome
BTW : HAPPY NEW YEAR
Can you reboot into TWRP? Re-flash from SD card.
hack14u said:
Can you reboot into TWRP? Re-flash from SD card.
Click to expand...
Click to collapse
No he can't ..... if it would only be that simple
Still no success so far...
I will continue to keep you updated (as it could help others within the same situation).
I have joined a team project from another community to work on the QFIL reflashing using qualcom tools.
But seems difficult as HTC are less open than LG or others manufacturer.
Anyway... Happy New year to you all
Hi community,
I have contacted HTC support and sent them my device, their diagnosis was a mainboard issue.
They have swapped the motherboard and sent it back.
I am sooooo happy.[emoji16]
They have also changed the entire screen...
So pleased with HTC support.
Very happy customer
Sent from my [device_name] using XDA-Developers Legacy app
chrisftlse said:
Hi community,
I have contacted HTC support and sent them my device, their diagnosis was a mainboard issue.
They have swapped the motherboard and sent it back.
I am sooooo happy.[emoji16]
They have also changed the entire screen...
So pleased with HTC support.
Very happy customer
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Glad to hear this story coming to a happy ending.
The 10 is still a wonder device!
andybones said:
Glad to hear this story coming to a happy ending.
The 10 is still a wonder device!
Click to expand...
Click to collapse
It still is a wonderful device.
Now I have to redo all steps to Unlock BL/Root/S-Off...etc..as I am back to 100% pure stock.
But first... Reading activities as these steps have been done like 1.5 year ago and do not remember exactly what to be done in which order.
Currently my system notification is pushing me to update to Oreo but I have read that it is preferable to root and other while in N as in O it will not be possible (yet).
Thanks for your support
chrisftlse said:
It still is a wonderful device.
Now I have to redo all steps to Unlock BL/Root/S-Off...etc..as I am back to 100% pure stock.
But first... Reading activities as these steps have been done like 1.5 year ago and do not remember exactly what to be done in which order.
Currently my system notification is pushing me to update to Oreo but I have read that it is preferable to root and other while in N as in O it will not be possible (yet).
Thanks for your support
Click to expand...
Click to collapse
I can't empirically speak for unlocking the bootloader Oreo since I already unlocked it a long time ago but, unless the process has changed on htc's site, it's still the same.
I can't speak for S-Off; read the Sunshine docs; I can't imagine that changing either. (My _opinion_ is that if one doesn't have a specific need for S-Off, then one only gains the risk of bricking the device, as evidenced by the numerous, redundant oopsie threads that would have been prevented by remaining S-On. This is why htc has S-On.)
I can say from experience that installing TWRP, Magisk, rooting all work the same post-Oreo update. (RUU Nougat, accept OTA/update apps, FDR, follow TWRP/Magisk instructions, install F-Droid/AdAway, clear Dalvik//cache, install everything else, profit). Give battery estimations a few days to get more accurate before thinking, "Oreo battery sucks!". The FDR and clearing caches is necessary to remedy bugginess and sluggishness, which would have also averted the numerous "my phone doesn't work right/is slow" posts.
Rolo42 said:
I can't empirically speak for unlocking the bootloader Oreo since I already unlocked it a long time ago but, unless the process has changed on htc's site, it's still the same.
I can't speak for S-Off; read the Sunshine docs; I can't imagine that changing either. (My _opinion_ is that if one doesn't have a specific need for S-Off, then one only gains the risk of bricking the device, as evidenced by the numerous, redundant oopsie threads that would have been prevented by remaining S-On. This is why htc has S-On.)
I can say from experience that installing TWRP, Magisk, rooting all work the same post-Oreo update. (RUU Nougat, accept OTA/update apps, FDR, follow TWRP/Magisk instructions, install F-Droid/AdAway, clear Dalvik//cache, install everything else, profit). Give battery estimations a few days to get more accurate before thinking, "Oreo battery sucks!". The FDR and clearing caches is necessary to remedy bugginess and sluggishness, which would have also averted the numerous "my phone doesn't work right/is slow" posts.
Click to expand...
Click to collapse
Thanks for feedback,
One of my aim is also to change CID (as it came back with the carrier one ORANG219, and I would prefer to 11111111 or HTC__001
But you are right S-Off could be risky if further actions are not made with caution