Develop Bugs

[Q] Failed remote signature verify fail. Phone stops on fastboot

Okay, i have a problem with an old phone, I believe its perm bricked, but wanted to check...
It is currently S-ON, and i have no way to turn off, its has no operating system, and the screen does not turn on. however i can turn the phone on, it does vibrate, and i can use fastboot commands.
Anyone got any idea's or shall i bin it?
C:\and\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: 1.21.405.2
(bootloader) serialno: **************************
(bootloader) imei: ********************
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.006s
C:\and\sdk\platform-tools>

It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before

eddiehk6 said:
It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before
Click to expand...
Click to collapse
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).

mike989e said:
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).
Click to expand...
Click to collapse
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up

eddiehk6 said:
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up
Click to expand...
Click to collapse
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot

mike989e said:
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot
Click to expand...
Click to collapse
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
number 5 on the guide

eddiehk6 said:
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
number 5 on the guide
Click to expand...
Click to collapse
I get a bootloader version error, code 140 when i try to install lol

mike989e said:
I get a bootloader version error, code 140 when i try to install lol
Click to expand...
Click to collapse
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading

eddiehk6 said:
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading
Click to expand...
Click to collapse
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Thanks for your help though, i think it is dead, think i'll just bin it

mike989e said:
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Click to expand...
Click to collapse
no, you don't need to be booted into the OS:
If you dont have a goldcard, you might try to create one at this point. This may work only for some people. Try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
Click to expand...
Click to collapse
the goldcard is just very useful to have in case you have this kind of situation.
i'm still very surprised the 2.3.3 RUU doesn't work. another thing you could try is to use the 2.3.3 GB RUU again, but use the PB99IMG.zip method, by extracting the rom.zip from the RUU
Thanks for your help though, i think it is dead, think i'll just bin it
Click to expand...
Click to collapse
as long as you can get to a bootloader screen, it's almost certainly not dead. your symptoms are EXACTLY as that guide states. it's your device, might as well get it working again
a real brick is literally nothing, no response, no LED, nothing. most people who think their device is 'bricked' is never actually bricked.

as long as you get to fastboot no problem. just download the pb99img from the latest 2.3 official upgrade then throught fastboot (back+power) enter in to fastboot RUU update mode then flash the zip with the command fastboot flash zip rom.zip . you dont need even an sd card to do that. just wait to procces to finish then fastboot reboot and your done. first boot takes few minutes longer but you wont have problems.

theres a couple of problems i have, 1 i have no screen, even when i fastboot. so i wont know if it fails, secondly my issues is that the image version number is to high on my phone. hence why i am getting the 140 error. as i have installed a number of roms off here the version number is to high.
off the top of my head, i cannot remember the number, however, on 2.3.3 is got a .17. in it, mine instead of that has .27. which means mine cannot install the standard 2.3.3 software, if i knew how to change the image number to higher than mine, and repackage it i could install it. but i don't know how. as i recall there was a thread about this years ago, but not sure if it was ever solved. i did look for it.

Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!

mike989e said:
Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!
Click to expand...
Click to collapse
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.

eddiehk6 said:
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.
Click to expand...
Click to collapse
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.

mike989e said:
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.
Click to expand...
Click to collapse
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...

eddiehk6 said:
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...
Click to expand...
Click to collapse
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!

mike989e said:
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!
Click to expand...
Click to collapse
you shouldnt have a custom recovery installed any more, the RUU should overwrite it to stock recovery. you won't be able to do anything with stock recovery per se, but the guide seems to indicate that you may be able to communicate with the device via adb.
still surprised the 2.3.3 RUU didn't work, I thought it's the highest version number so shouldn't have any problem.
I'm running out of ideas tbh, I'd still recommend posting the issue in the droidzone guide, hopefully he'll reply as he'd most likely know how to solve it.

Other way to enable USB Debugging

Hello,
I've recently got a HTC Desire which is stuck on a white screen with the green HTC logo.
So I've decided to flash the ROM, in order to do this operation I have two choice :
- Flash a custom ROM and so switch the HTC Desire in S-OFF mode
- Flash an official ROM so I'll need to build a GoldCard
Anyway, the phone is really stock, I mean even the Debugging option is not enabled on it ... So I'm stuck because I cannot use all the commands with adb (as adb devices or adb shell ...) but fastboot scripts works, with the commands fastboot getvar all I got that :
INFOversion: 0.5
INFOversion-bootloader: 0.80.0000
INFOversion-baseband: 4.06.00.02_2
INFOversion-cpld: None
INFOversion-microp: 031d
INFOversion-main: 1.22.73.1
INFOserialno: HT041PL05***
INFOimei: 35784103124****
INFOproduct: bravo
INFOplatform: HBOOT-8x50
INFOmodelid: PB9920000
INFOcidnum: ORANG202
INFObattery-status: good
INFObattery-voltage: 4109mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6175d920
INFOhbootpreupdate: 11
all: Done!
finished. total time: 0.013s
Click to expand...
Click to collapse
I tried to install a new recovery with the command : fastboot flash recovery but I got an error : " Signature failed ..." (maybe it must be S-OFF to do that)
Actually my one and only question is, is there a way to enable USB Debugging in my situation ? Or an other way to flash de ROM with theses conditions ?

U dont need a goldcard if u use the 2.3gb update from htcdev. U can get the ruu from bortaks troubleshooting guide in my sig. Also to s-off u will need ur phone to be booted for it to work. Once used the ruu, use revolutionary to s-off ur phone.

Actually to update via htcdev, it is required to enable the USB debugging and I can't access to this option.
I follow the link in your sig and I downloaded this RUU :
RUU_Bravo_Froyo_HTC_ARA_2.32.415.3_Radio_32.49.00.32U_5.11.05.27_release_157343_signed.exe
Click to expand...
Click to collapse
Is this one correct ?

val5906 said:
Actually to update via htcdev, it is required to enable the USB debugging and I can't access to this option.
I follow the link in your sig and I downloaded this RUU :
Is this one correct ?
Click to expand...
Click to collapse
Nope thats froyo ruu, u want 2.3 gingerbread. In bortaks guide, go down to resources and ul see it. Then run the ruu from bootloader. If it dont work then google 2.3gb upgrade as PB99IMG and do it that way.
Edit: 2.3gb PB99IMG link below
http://d-h.st/d44
And How to flash PB99IMG (thanks andu)
http://forum.xda-developers.com/showpost.php?p=45298337&postcount=21

I used the RUU from HTCdev 2.3 and the installation took a very long time at "Updating recovery" then the smartphone turned town (after 5-6 hours ^^) and when I tried to restart it I get 4 (!), one in each corner.
I read on your guide that is a common issue when we installed the wrong RUU. To fix it, you said in your guide to use a goldCard but I don't know if I can build one ...
When I tried to relaunch the upgrade, it works but still stuck at the same point

val5906 said:
Argggg I'm so stupid, I used the wrong RUU and the installation took a very long time at "updating radio" then the smartphone turned town (after 5-6 hours ^^) and when I tried to restart it I get 4 (!), one in each corner.
I read on your guide that is a common issue when we installed the wrong RUU. To fix it, you said in your guide to use a goldCard but I don't know if I can build one ...
Click to expand...
Click to collapse
Its not my guide i only suggested the "2.3gb upgrade" because u dont need a goldcard. Read more carefully before jumping into things, things can go very wrong very quick. Anyway the 4 /!\ means ur stuck in ruu mode, so now try the 2.3gb ruu and hope it works

jmcclue said:
Its not my guide i only suggested the "2.3gb upgrade" because u dont need a goldcard. Read more carefully before jumping into things, things can go very wrong very quick. Anyway the 4 /!\ means ur stuck in ruu mode, so now try the 2.3gb ruu and hope it works
Click to expand...
Click to collapse
First, thanks you very much for your help
Actually I said I used the wrong RUU but I don't think it was the wrong one because the first one I used wasn't recognize by the phone and this one works but stuck during the upgrading.
I retried to update with the same update and now it's stuck at updating recovery ... (as soon as it was written "updating recovery" my phone vibrated 7 times and became stuck at this position)
Actually, before flashing and doing something on the phone when I tried for the first time to run the recovery from the bootloader the phone did this strange thing (vibrate 7 times) maybe something wrong happened in the hardware stuff.
EDIT : I managed to finish the updraging (100%) but at the end of the updating I got this message from the software img15.hostingpics.net/pics/616271screen.png (can't post n picture because I'm a new user sorry) My phone showed a result of the updating and everything went right except the radio updating ...
I got the same screen at the boot, 4 (!) in each corner. I'm really wondering which update I have to use ???

Oh rite, yh the 7 vibrations means hardware problem im affraid. The only fix is taking it to repair shop.

Soft-Bricked HTC One M9, no recovery or download mode, need help with factory reload

Hey all. First of all, let me thank you in advance for any and all help. Here's the low-down.
I bought this phone today on craigslist (I know, I know). I confirmed, however, that the phone was not reported lost or stolen and that the IMEI was not blacklisted. The guy I bought it from said he was having issues after an attempted update, but after spending the last 6+ hours combing through forum posts, trying every software combination I can find, etc. I think my issues may be bigger.
Here's what I'm experiencing. When turning the phone on, I see the following:
***Software status: Official ***
*** LOCKED ***
*** S-ON ***
Click to expand...
Click to collapse
I have 5 options at that point:
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
Click to expand...
Click to collapse
If I select Reboot, the phone reboots and the message at the top changes slightly to show:
***Software status: Modified***
*** LOCKED ***
*** S-ON ***
*** Security Warning ***
Click to expand...
Click to collapse
If I select reboot to bootloader, it goes back to "Software status: Official"
If I try to boot to download mode, I get
Failed to boot to download mode
Press volume up or down to back to menu
Click to expand...
Click to collapse
followed then by the HTC Logo and the following text
This build is for development purposes only
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action.
Click to expand...
Click to collapse
If I boot to recovery mode I get the same thing as download mode, with the text saying "Failed to boot to recovery mode" and all of the rest matching.
I have tried signing up for an HTC dev account and going in to get the Identifier token, but because I can't boot the phone into download mode I can't get the token. When I try running the
fastboot oem get_identifier_token.
Click to expand...
Click to collapse
command it just tells me
FAILED: unknown remote command.
Click to expand...
Click to collapse
I've also tried using the HTC One M9 toolkit found here on the forums (though maybe there's some functionality I missed, I tried to be thorough).
I've also tried using the HTC sync software and downloading the RUU but after running the RUU executable nothing happens. I then dug into trying to make sure the MID and CID are correct but again, the command
fastboot oem getvar al
Click to expand...
Click to collapse
returns the "unknown remote command" message.
I'm really hoping someone else has run into something like this. Again- thanks for your time and any help you can give.

I Have the Same issue as you describe, brought Mine Back to the retailer to get it replaced ><

Failed root attempt. Most likely to be a corrupt emmc. When you get to that menu with the mode options, what happens when you immediately select "download mode", does it reboot or go to download mode?.
Beamed in by telepathy.

I have the same issue I can't get to download mode or recovery mode, when I boot to download mode I get the message "Failed to boot to download mode". Please anyone can help with this??

Redfox511 said:
I have the same issue I can't get to download mode or recovery mode, when I boot to download mode I get the message "Failed to boot to download mode". Please anyone can help with this??
Click to expand...
Click to collapse
What model do you have exactly?
OPJA100 or wich?
Android 6.0 or 5.1 ?
Firmware running ?
need some information....

shivasrage said:
What model do you have exactly?
OPJA100 or wich?
Android 6.0 or 5.1 ?
Firmware running ?
need some information....
Click to expand...
Click to collapse
I have OPJA100 before the device crashes I as on android 6.0 now I think there is no firmware on the device as it just boots to bootloader, the thing started with a reboot loop then I did a hard factory reset but it didn't work out so I tried to install a new firmware but I couldn't as S-On after multiple tries I ended up can't boot to download or recovery mode with the message "failed to boot to download/recovery mode". That's everything

I had same problem last week.
I don't have warranty on my device, so I look forward for a user solution.

throcker said:
I had same problem last week.
I don't have warranty on my device, so I look forward for a user solution.
Click to expand...
Click to collapse
same problem

guys, there are so many threads about self-bricking devices...I never saw anything since this month...what's happening?!

throcker said:
guys, there are so many threads about self-bricking devices...I never saw anything since this month...what's happening?!
Click to expand...
Click to collapse
Like the Nexus 5X and Nexus 6P, the M9 has reached the age (~1.5 years old) where hardware issues begin to show.

computerslayer said:
Like the Nexus 5X and Nexus 6P, the M9 has reached the age (~1.5 years old) where hardware issues begin to show.
Click to expand...
Click to collapse
after m9 died I switched to nexus 5x. wrong move ahahah
at least I have warranty on this

I purchased two Nexus 5X phones days before the problems started getting reported. My folks are using them. Ah well. They're great devices and I'll just have to hope that these two don't have the problems they some others do. So far, so good.

socrates23 said:
I've also tried using the HTC One M9 toolkit found here on the forums (though maybe there's some functionality I missed, I tried to be thorough).
I've also tried using the HTC sync software and downloading the RUU but after running the RUU executable nothing happens. I then dug into trying to make sure the MID and CID are correct but again, the command returns the "unknown remote command" message.
Click to expand...
Click to collapse
Hey there, the command is not fastboot oem getvar al, you should try:
Code:
fastboot getvar all
or you can return specific thing like:
Code:
fastboot getvar cidnum
And wow...I'm finding my self reading this topic, because i have the exact same issue with one of my customers phones that brought me his soft bricked M9 device.
You described the problem perfectly and this is the exact troubleshooting results i get too.
I was never a fan of HTC replacing the classic fastboot bootloader with the damn download mode, which bring us to such a situation where we get to dead end when no download mode and no recovery mode with locked bootloader.
If we could just unlock the bootloader, then we could flash easily a recovery and then flash the stock rom or custom rom, but what makes things more complicated is when we are not even able to get there due to that new download mode thingy in htc.
My only solution and work around i can give you regarding this, is finding the exact RUU specific to your model since the current state of the device will ONLY be able to accept the stock RUU firmware since it is S-ON.
Finding the stock RUU for your device can be quiet challenging, since you have to know the cidnum with the command:
Code:
fastboot getvar cidnum
That will basically help you know the right RUU for your device.
But in my case, it didn't display the cidnum since i guess the guy before me tried to flash a wrong software or run some fastboot commands that removed the data partition.
And he can't even tell me to what company it was belongs too, because the whole idea of figuring out what the cidnum is, helps you know the cellular provider that responsible on that device which will basically help you at the end of point finding the right RUU to make the device accepting it.
There are 2 methods flashing RUU's:
1. Downloading the exe file and running as admin and hoping for good.
2. Downloading the zip file and renaming it to the matching name and putting it in the sd-card and letting the device recognize it while you starting download mode(even though it doesn't load download mode).
It would basically flash the whole thing including recovery, download mode, software, firmware and put it into factory setting.
So yea, that's pretty much my direction regarding this problem. I would also really appreciate some of the proffis here to give us a hand here which would be a great help!
Let me know in the comments if you solved it somehow.
That's my getvar all status atm:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54MYJ03126
all:
finished. total time: 0.141s

reichrepairs said:
And wow...I'm finding my self reading this topic, because i have the exact same issue with one of my customers phones that brought me his soft bricked M9 device.
You described the problem perfectly and this is the exact troubleshooting results i get too.
I was never a fan of HTC replacing the classic fastboot bootloader with the damn download mode, which bring us to such a situation where we get to dead end when no download mode and no recovery mode with locked bootloader.
If we could just unlock the bootloader, then we could flash easily a recovery and then flash the stock rom or custom rom, but what makes things more complicated is when we are not even able to get there due to that new download mode thingy in htc.
Click to expand...
Click to collapse
Try to flash the hosd.img (fastboot flash hosd hosd.img) that corresponds to the current firmware of the phone while it's booted to bootloader. If that doesn't work try to flash it as soon as it reaches the error while booting to download mode. If the flash was sucessful, shut off the device and reboot to download mode and flash the RUU that corresponds to the current firmware. (According to this post the whole procedure needs S-OFF but I got told that it's possible with S-ON, as well, some days ago.)
reichrepairs said:
My only solution and work around i can give you regarding this, is finding the exact RUU specific to your model since the current state of the device will ONLY be able to accept the stock RUU firmware since it is S-ON.
Finding the stock RUU for your device can be quiet challenging, since you have to know the cidnum with the command:
Code:
fastboot getvar cidnum
That will basically help you know the right RUU for your device.
But in my case, it didn't display the cidnum since i guess the guy before me tried to flash a wrong software or run some fastboot commands that removed the data partition.
Click to expand...
Click to collapse
There are better ways. If you look at the firmware version (version-main in the getvar output or stated in the line with "OS" at the beginning while the phone is booted to download mode) you know exactly which RUU version you need to look for. This way you don't need to guess the correct RUU from the CID.
reichrepairs said:
And he can't even tell me to what company it was belongs too, because the whole idea of figuring out what the cidnum is, helps you know the cellular provider that responsible on that device which will basically help you at the end of point finding the right RUU to make the device accepting it.
Click to expand...
Click to collapse
This actually is a problem. Unfortunately, I don't have a solution, sorry.
reichrepairs said:
There are 2 methods flashing RUU's:
1. Downloading the exe file and running as admin and hoping for good.
2. Downloading the zip file and renaming it to the matching name and putting it in the sd-card and letting the device recognize it while you starting download mode(even though it doesn't load download mode).
It would basically flash the whole thing including recovery, download mode, software, firmware and put it into factory setting.
So yea, that's pretty much my direction regarding this problem. I would also really appreciate some of the proffis here to give us a hand here which would be a great help!
Click to expand...
Click to collapse
Step by step instructions are already posted several times here on xda. One example can be found here.
reichrepairs said:
Let me know in the comments if you solved it somehow.
That's my getvar all status atm:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54MYJ03126
all:
finished. total time: 0.141s
Click to expand...
Click to collapse
You can't get a proper getvar outputs while the phone is booted to the bootloader. It needs to be in download mode. However, I'm not sure whether the command will give you a proper output if the download mode is broken.

Yeah, there are many, many reports in the last weeks about this "downloadmode" issue
and dying emmc´s
I don´t know if it´s true but I heared somewhere that it´s
happenig to M9 with emmc´s produced by hynix.
Do you think this rumour coud be true?

Appreciate your very detailed reply @Flippy498! Thanks for that.
Long story short, in that case the only solution would be getting one of these JTags tools like XTC 2 Clip and do the S-OFF and only that way we can basically flash any software or RUU.
I was doing some re-search and sadly i had one of those clips 4-5 years ago and too bad i didn't keep it with me. But the price for that xtc2clip is ridiculously expensive that it's better finding someone who owns it and pay for his service just for the S-OFF part.
I found someone in Berlin who actually does that and hopefully he'll help me out.
Because without finding the right RUU, there is no way solving this problem. But the thing is, no matter in what mode i type the getvar all command, i don't get the cidnum number or main version since there is no download mode or recovery which disabling me from finding the right RUU for that specific m9 phone.

Hey everyone, kinda new to the forum. I pop back on every time I funk up a phone lol, started with a windows pocket PC ages ago.....ANYWAYS
Same problem.
Lost the phone for months and booted it up to the *software status modified*locked*s-on*security warning*
as soon as it has power it goes to this screen. reboot to download or recovery end in errors. Powerdown if it has juice just boots it back to the white reboot screen.
I never tried to even unlock the bootloader, flash or root anything, I got this phone for my wife.
Good news, though. I've been working with a 3rd tier HTC tech...whatever that means, and we have been working through everything step by step, soon enough I'll have an answer and I've saved all our logs, so I can share it here. We might even find out what causes this to happen. Stay tuned.

Repair was the only solution
I had the same issue as srqgeek. Worked through some options with HTC tech support and the ended up sending the handset away. Now I have it back it appears that it may have been a software issue as no parts are listed as replaced. I have noticed I have a different version of the ROM installed with the HTC standard global ROM as opposed to the carrier updated version (EE-UK in my case). I've had no issues since the re-image.
srqgeek said:
Hey everyone, kinda new to the forum. I pop back on every time I funk up a phone lol, started with a windows pocket PC ages ago.....ANYWAYS
Same problem.
Lost the phone for months and booted it up to the *software status modified*locked*s-on*security warning*
as soon as it has power it goes to this screen. reboot to download or recovery end in errors. Powerdown if it has juice just boots it back to the white reboot screen.
I never tried to even unlock the bootloader, flash or root anything, I got this phone for my wife.
Good news, though. I've been working with a 3rd tier HTC tech...whatever that means, and we have been working through everything step by step, soon enough I'll have an answer and I've saved all our logs, so I can share it here. We might even find out what causes this to happen. Stay tuned.
Click to expand...
Click to collapse

Deleted all of my HTC One M8 system, and don't know what to do.

So recently I bought used HTC One M8. It operated like new, but I wanted customization... I unlocked the phone's bootloader (watching this video: HTC One M8: How to Unlock Bootloader & Root - Easiest method) I did it successfully. Then I installed TWRP, by using tool kit (also by watching same guy's video: (HTC One M8 : How to Root & Install TWRP Recovery - Easiest method) (sorry i can't post links)(Channel is called: Explore Gadgets)followed everything step by step, so you can check, if you not sure what I did... So I wanted to flash a custom rom, I was scared already of this problem happening, because it happened on my 2 other last phones, but in one of them, somehow I managed to fix it. That HTC is my main phone, I don't have others by now, so I am very interest by fixing it. I uploaded my file, it is cyanogenmod.. Also uploaded gapps on (both files on sd card).. First, I tried to back up all my data, before doing anything. But TWRP stuck on backup.. But I thought why not, and tried to install a rom, without any backup made... Then again TWRP freezed.. Now I'm left with phone with no system.. I can get into that screen, where it says that I'm unlocked.. By the way, my phone is s-on, I don't know if it is because of that... Please help me...

I believe because you followed an outdated guide written in 2014 ?
You should have come to XDA to read guides instead of relying on other sources on the net (as most of them are outdated)
You need to post here fastboot getvar all result (delete the serial & imei no.)
then we'll see what you need to do now.
Most of the failure reason is wrong TWRP version installed (again outdated) and not compatible firmware on the phone.
BTW .. I asked moderator to move this thread to Q&A section

ckpv5 said:
I believe because you followed an outdated guide written in 2014 ?
You should have come to XDA to read guides instead of relying on other sources on the net (as most of them are outdated)
You need to post here fastboot getvar all result (delete the serial & imei no.)
then we'll see what you need to do now.
Most of the failure reason is wrong TWRP version installed (again outdated) and not compatible firmware on the phone.
BTW .. I asked moderator to move this thread to Q&A section
Click to expand...
Click to collapse
I'm not that really good at this type of things so I didn't really understood what information you asked, and from where to get that information.. I would be very thankful if you would guide me what you want to know... But yeah I followed the old directions... I'm ashame of myself for not knowing what you want ..

You still have the toolkit, right ? I never use one but I believe it has fastboot/adb
Is it this one - https://forum.xda-developers.com/showthread.php?t=2699065
On the screenshot I see under commands it has boot to bootloader & getvar all
1. select boot to bootloader (if you're not on bootloader yet
2. select getvar all - this will give you the details needed
Or you can install this : https://forum.xda-developers.com/showthread.php?t=2588979
You need a command prompt from adb/fastboot then type command
fastboot getvar all
then post the details (after you remove serial & imei no.)

ckpv5 said:
You still have the toolkit, right ? I never use one but I believe it has fastboot/adb
Is it this one - https://forum.xda-developers.com/showthread.php?t=2699065
On the screenshot I see under commands it has boot to bootloader & getvar all
1. select boot to bootloader (if you're not on bootloader yet
2. select getvar all - this will give you the details needed
Or you can install this : https://forum.xda-developers.com/showthread.php?t=2588979
You need a command prompt from adb/fastboot then type command
fastboot getvar all
then post the details (after you remove serial & imei no.)
Click to expand...
Click to collapse
Yes, it is the same tool.. But I removed it.. I can download this one, and everything will be the same, right? Or something is needed from earlier, when I did the installation (like logs, or I don't know what else collects information).. I will post the information you asked (b.t.w. I'm so thankful that you're helping me, my knowledge might be annoying, because I don't know everything, but if I will be helped, I will be very happy..)..

Download the one that I linked you above. Install version 1.3 as it is easier.
When it ask :
Do you want to install fastboot & adb - type y
Install adb system-wide - type y
Do you want to install device driver - type n
Then open a command prompt from anywhere it should work.
Open command prompt then type the command fastboot getvar all
You need this adb/fastboot because you're going to rely on it a lot later

Jaris99 said:
I'm not that really good at this type of things so I didn't really understood what information you asked
Click to expand...
Click to collapse
Fastboot is critical to know for modding these phones. If you've modded 3 phones, and don't know how to use basic fastboot commands, you should learn now!
Another primary rule of thumb you should always keep in mind modding these phone: always research that you are using current, latest methods (to root, custom recovery, etc.) or at least that the method which corresponds to the device's firmware.
The world of Android moves quickly. Every time a new Android version is released, a new root method needs to be used. Every time firmware is updated, you usually need to use a new TWRP version. You can't use a toolkit that is 2 years old and expect it to go well.
---------- Post added at 10:20 AM ---------- Previous post was at 10:15 AM ----------
Jaris99 said:
But I thought why not, and tried to install a rom, without any backup made...
Click to expand...
Click to collapse
Well, I think you know now "why not". Because now you don't have a known-good backup or ROM to revert to, and no working phone.
I never mod any Android device without a known-good nandroid backup or known-good ROM to flash.
Jaris99 said:
By the way, my phone is s-on, I don't know if it is because of that...
Click to expand...
Click to collapse
S-on is fine for root, flashing ROMs, kernels, and a great many other mods. S-off is only needed for very specific things (flashing hboot, radio, changing CID/MID, etc.).

ckpv5 said:
Download the one that I linked you above. Install version 1.3 as it is easier.
When it ask :
Do you want to install fastboot & adb - type y
Install adb system-wide - type y
Do you want to install device driver - type n
Then open a command prompt from anywhere it should work.
Open command prompt then type the command fastboot getvar all
You need this adb/fastboot because you're going to rely on it a lot later
Click to expand...
Click to collapse
Tried with both applications, it says that no device is connected... Kit tool says that you need to enable USB debugging, but how can I do that without system ..

Jaris99 said:
Tried with both applications, it says that no device is connected... Kit tool says that you need to enable USB debugging, but how can I do that without system ..
Click to expand...
Click to collapse
You don't need usb debugging enabled for fastboot. usb debugging is only for adb when you have running OS.
Did you put your device on bootloader/fastboot mode before you connect to PC ?
If it is not and you're stuck on htc loading screen, press & hold both volume up & power button. When it turns black, release both buttons but quickly press & hold volume down button only. This will get you to hboot screen, press power once to get to bootloader.
When you connect the cable on phone & PC, you should see "fastboot usb" on the bootloader
When you type command
fastboot devices
it should show your device serial no.
If it says "waiting for device" you need HTC USB drivers installed.
If you are not sure whether you already have it, do this as explained here : https://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
You already done part 1 for adb/fastboot, do part 2 for HTC USB drivers.

ckpv5 said:
You don't need usb debugging enabled for fastboot. usb debugging is only for adb when you have running OS.
Did you put your device on bootloader/fastboot mode before you connect to PC ?
If it is not and you're stuck on htc loading screen, press & hold both volume up & power button. When it turns black, release both buttons but quickly press & hold volume down button only. This will get you to hboot screen, press power once to get to bootloader.
When you connect the cable on phone & PC, you should see "fastboot usb" on the bootloader
When you type command
fastboot devices
it should show your device serial no.
If it says "waiting for device" you need HTC USB drivers installed.
If you are not sure whether you already have it, do this as explained here : https://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
You already done part 1 for adb/fastboot, do part 2 for HTC USB drivers.
Click to expand...
Click to collapse
Ok, so i managed to download the device drivers with Htc sync, from link you have gave. Tried opening that application "ADB setup" pressed Y,Y,N, like you said, it said that "no route is found" or something like that.. So I pressed getvar all in a kit tool, and it worked, so that's what I've got: version-baseband: 1.29.2145000
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

Jaris99 said:
version-baseband: 1.29.2145000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__Y13
security: on
Click to expand...
Click to collapse
As expected, you have a Marshmallow firmware. The version no. is 6.12.401.4 which is now missing from your getvar due to the outdated TWRP that you installed.
Now .. what do you want to do:
a) Restore the stock ROM ?
b) Install a custom ROM ?
First thing that important to fix, is the recovery.
I downloaded the toolkit to see how the layout of it.
To use the toolkit :
a) You need TWRP 3.0.2-0 - download from here : https://dl.twrp.me/m8/
b) rename the downloaded twrp-3.0.2-0-m8.img to TWRP.img
c) in Data/Recoveries folder - delete everything there and place this new TWRP.img in it
d) now you can install TWRP with the toolkit
So you need to answer the above questions, option (a) or (b) ?
Then we'll see what you need to do.
Also delete the SuperSU.zip that in Data/SU folder - it's outdated too.
Download this SuperSU - https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Don't replace the old one .. you're going to need it later after your option (a) or (b).

ckpv5 said:
As expected, you have a Marshmallow firmware. The version no. is 6.12.401.4 which is now missing from your getvar due to the outdated TWRP that you installed.
Now .. what do you want to do:
a) Restore the stock ROM ?
b) Install a custom ROM ?
First thing that important to fix, is the recovery.
I downloaded the toolkit to see how the layout of it.
To use the toolkit :
a) You need TWRP 3.0.2-0 - download from here : https://dl.twrp.me/m8/
b) rename the downloaded twrp-3.0.2-0-m8.img to TWRP.img
c) in Data/Recoveries folder - delete everything there and place this new TWRP.img in it
d) now you can install TWRP with the toolkit
So you need to answer the above questions, option (a) or (b) ?
Then we'll see what you need to do.
Also delete the SuperSU.zip that in Data/SU folder - it's outdated too.
Download this SuperSU - https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Don't replace the old one .. you're going to need it later after your option (a) or (b).
Click to expand...
Click to collapse
Option b... Just can you suggest me a rom.. I want to use both dual cameras, so cyanogemod wont work.. I just wan fast, smooth rom, which got good battery life, because on original software it was crap, and i want to have a root, or you would guide me hot to root, if root not comes with the rom... I really dont care what rom is it, you can choose from youre experience...

Jaris99 said:
.... I really dont care what rom is it, you can choose from youre experience...
Click to expand...
Click to collapse
Haha ... that's one thing I don't experience enough. I don't usually use Sense custom ROM, I make my own ROM.
Anyway .. you can try all those Sense ROMs in development sections .. and you have to decide which is the best that suit your requirement.
You can try Jazz - no more update but it is the same base as your firmware. This the custom ROM that I was on before - https://forum.xda-developers.com/htc-one-m8/development/rom-sense-6-12-401-4-mra58k-stock-t3296066
You also can try ICE - I believe it is a good ROM - https://forum.xda-developers.com/showthread.php?t=2704539
If you want the latest with some port of htc 10 - https://forum.xda-developers.com/ht...the-worlds-first100-m9-port-m8upload-t3064838
You don't need to manually root these ROMs, they are pre-rooted.
If you ever need the stock ROM, you can restore stock non-rooted 6.12.401.4 ROM here :
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
To root a stock ROM - just put the downloaded SuperSU.zip in internal storage or microsd
Boot to TWRP recovery - select install menu and select downloaded SuperSU.zip and install.

You know what would make this board more helpful? Would be a detailed list of exactly how to treat your brand new (or used) android phone device.
Like the first thing it would do is come up when you visit xda. It would force tha playa to download the latest fastboot adb minimal, and then tell tha playa to straight away get your getvar all. Etc etc... Then list phones after that.
Instead of people straightaway tryna root they phones it would put them on a path to download temp the twrp for the device and make a backup first thing.
---------- Post added at 04:23 PM ---------- Previous post was at 03:56 PM ----------
Ithe android devices dont even need a hidden menu. The adb should always be on until its turned off, or a question should be posed at startup instead of the proprietary google account creation.
This is why the peak of android as a system was around two years ago.
Google's gotten so resentful of the competition they have gone and pulled a complete intel with they N system. Made it next to impossible for other corporations to develop for their phones.
Its gone beyond usable. Who knows if my 5th phones current screen flicker glitch is due to attempting s off or the flash I did before that of the DU N ROM.
It is all too questionable.

kruc Ire said:
You know what would make this board more helpful? Would be a detailed list of exactly how to treat your brand new (or used) android phone device.
Click to expand...
Click to collapse
If you think that would be useful, then feel free to write such a guide.
As someone that has spent a lot of time creating and maintaining Index rollup threads for XDA, my experience is that a lot of folks often don't look at the resources provided.
My advice for anyone, even an experienced Android user, is to research for a minimum 2-3 hours before even starting to attempt any mods to a new device. Every device has its own unique nuances and quirks. And if you dive in, without finding out what those things are, you will run into problems. The proper research is critical. All the information is here, even if its not always presented in an obvious manner.
But many folks don't want to do that (research and learn). They just want a one-click root, or to just watch a YouTube video. Then they wonder why the method from 2 years ago doesn't work.
kruc Ire said:
Ithe android devices dont even need a hidden menu. The adb should always be on until its turned off, or a question should be posed at startup instead of the proprietary google account creation.
Click to expand...
Click to collapse
For power users, that may be true. But for the huge majority of Android users, having adb active by default is a bad idea.
kruc Ire said:
This is why the peak of android as a system was around two years ago.
Click to expand...
Click to collapse
Such comments don't add value to the discussion on this forum. Off topic, and hundreds (if not thousands )of users here would probably disagree, and not appreciate such comments.
kruc Ire said:
Who knows if my 5th phones current screen flicker glitch is due to attempting s off or the flash I did before that of the DU N ROM.
Click to expand...
Click to collapse
You attempted an s-off method (rumrunner) which was never intended for this device. Don't blame others for your mistakes and lack of research.

redpoint73 said:
I
You attempted an s-off method (rumrunner) which was never intended for this device. Don't blame others for your mistakes and lack of research.
Click to expand...
Click to collapse
Yeah no blame is necessary, dont tell me what to do.
All day long you been following me around dumping on my comments. Whyontchoo take a hike. You have contributed nothing useful in 4 straight comments.

ckpv5 said:
Haha ... that's one thing I don't experience enough. I don't usually use Sense custom ROM, I make my own ROM.
Anyway .. you can try all those Sense ROMs in development sections .. and you have to decide which is the best that suit your requirement.
You can try Jazz - no more update but it is the same base as your firmware. This the custom ROM that I was on before - https://forum.xda-developers.com/htc-one-m8/development/rom-sense-6-12-401-4-mra58k-stock-t3296066
You also can try ICE - I believe it is a good ROM - https://forum.xda-developers.com/showthread.php?t=2704539
If you want the latest with some port of htc 10 - https://forum.xda-developers.com/ht...the-worlds-first100-m9-port-m8upload-t3064838
You don't need to manually root these ROMs, they are pre-rooted.
If you ever need the stock ROM, you can restore stock non-rooted 6.12.401.4 ROM here :
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
To root a stock ROM - just put the downloaded SuperSU.zip in internal storage or microsd
Boot to TWRP recovery - select install menu and select downloaded SuperSU.zip and install.
Click to expand...
Click to collapse
So i downloaded the ICE rom.. I installed newest TWRP.. But i can't upload the zip to my device... When i'm in TWRP it shows the phone and sd card on the computer, but when i try to upload it, it says that device is not connected... Tried using sd with an adapter, but the pc does not see the sd..

Jaris99 said:
So i downloaded the ICE rom.. I installed newest TWRP.. But i can't upload the zip to my device... When i'm in TWRP it shows the phone and sd card on the computer, but when i try to upload it, it says that device is not connected... Tried using sd with an adapter, but the pc does not see the sd..
Click to expand...
Click to collapse
Not familiar with this kind of thing.
When PC cannot see the sd when connected with an adapter, check whether you have driver correctly installed under "portable devices" in PC device manager.
Try select Mount USB storage on TWRP mount menu and see whether PC will detect the microsd (with microsd in the phone)

Jaris99 said:
So i downloaded the ICE rom.. I installed newest TWRP.. But i can't upload the zip to my device... When i'm in TWRP it shows the phone and sd card on the computer, but when i try to upload it, it says that device is not connected... Tried using sd with an adapter, but the pc does not see the sd..
Click to expand...
Click to collapse
How exactly are you trying to copy the ROM to your phone, adb push or copy/paste to the SD like its a drive (either should work while booted into TWRP)?
If you mean a removable SD, and you have a USB card reader, you can use the card reader to copy the ROM to the phone. Or use an old phone (with SD slot) as a makeshift "card reader" (which I've had to resort to, also).

So i managed to fix my phone.. Thank you all! Only last question, will xposed work on my device? I installed Ice rom, which you gave me...

Unlocked bootloader rom flashing/moonshine

I bought what i think it's an international HTC one M8 from someone and it was sold to me with the bootloader already unlocked (if i enter fastboot it says [unlocked])
So i wanted to change my OS to lineage and root my phone just to find out that i need to pay 25$ to root it or S=off, fine whatever, that's like 500 MXN so i don't think i'll be able to afford that soon for personal reasons. so i had to look for alternatives and i found something called "moonshine" and some videos of people using it it on other HTC devices, so i wanted to know if anyone had done it on a M8 and if it worked.
Or in the worst scenario is there a way to flash a rom without a PC and without root?
because my other problem is with my laptop that won't install the adb drivers.
i recall with another phone i had i tried to do the same but someone said that it was probably a thing with the usb ports.
Thanks in advance.

First of all, and most importantly, you do NOT need s-off to root, flash custom recovery, flash custom ROMs, etc. Don't know why people keep thinking that, this was never mandatory for HTC devices (to need s-off to root, flash custom ROM). S-off is only needed for very specific things, such as changing the device CID/MID, flashing a modified hboot, manually flashing radios. Most mods do not need s-off. And fair to say that most users (even ones that want to do a lot of mods) do not need s-off.
Second, NO moonshine will not work. It is very old and predates the M8. Never worked on the M8, and never will. Understand, that such security measures and their corresponding exploits are time dependent. Meaning that once HTC realizes that a hack/exploit exists, they will plug that hole and a new exploit needs to be developed. Therefore, searching for old, outdated s-off methods is a waste of your time. For that matter, stop wasting your time and understand the simple fact: if you want s-off, you will need to pay for it and use sunshine.
But again, you don't need s-off for the things you describe.
---------- Post added at 09:17 AM ---------- Previous post was at 08:59 AM ----------
LilArmalite said:
Or in the worst scenario is there a way to flash a rom without a PC and without root?
because my other problem is with my laptop that won't install the adb drivers.
i recall with another phone i had i tried to do the same but someone said that it was probably a thing with the usb ports.
Click to expand...
Click to collapse
I would highly suggest working out the adb issue on your PC, rather than resorting to workarounds. Can you flash a ROM without a PC? Possibly (depends on some of the details). But having a PC, and not being able to use adb/fastboot in the case of an emergency, feels to me like a (needless) disaster waiting to happen.
Your description is short on details. Such as:
- Is custom recovery (TWRP) already installed on the device? From bootloader, pick the option to boot recovery, and tell us what happens. If TWRP is installed, tell us what version number.
- What adb package did you try to install? Is it the full Android SDK package? If so, there are much smaller/easier to install adb/fastboot installers available, if you simply use the xda seach function, and search "easy adb".
- What exactly is happening when you try to install adb drivers? Installing adb drivers (or inability to do so) has nothing to do with USB post issues. Connecting to the device is another matter, but that isn't what you posted.

redpoint73 said:
What exactly is happening when you try to install adb drivers? Installing adb drivers (or inability to do so) has nothing to do with USB post issues. Connecting to the device is another matter, but that isn't what you posted.
Click to expand...
Click to collapse
I think it is a problem with connecting to the device, i mean, i can open the cmd and use commands but they just won't recognize the phone, and whenever i try to install the phone drivers by connecting the phone (when windows says it's installing ADB) it fails and says the device was disconnected.
So i don't need S=Off to let's say use "lucky patcher" or "Link2SD" or any other app that requires root?

LilArmalite said:
I think it is a problem with connecting to the device, i mean, i can open the cmd and use commands but they just won't recognize the phone, and whenever i try to install the phone drivers by connecting the phone (when windows says it's installing ADB) it fails and says the device was disconnected.
Click to expand...
Click to collapse
As long as you have a fastboot environment setup, you don't need to install any drivers from the phone. Just ignore those prompts.
Problems with fastboot/adb commands are often pilot error. Note there are two interfaces fastboot versus adb. They are related, but with difference requirements. If you aren't aware of the distinctions, this alone may be causing your connectivity issue.
1) Fastboot: This is the main interface that is needed for installing custom recovery and root; and therefore the interface you should be most concerned with. Fastboot will only work in bootloader-fastboot mode. Make sure the phone is in bootloader, with FASTBOOT highlighted in red near the top of the screen. If it isn't, select FASTBOOT using the volume buttons, and confirm by pressing power button.
2) adb: Device needs to be booted to OS or alternately in TWRP for adb commands to work. adb will not work in bootloader.
So with the above distinctions noted, it is common for instance for folks to try to run a fastboot command while the phone is booted to OS (which intentionally will not work) and think that something is "wrong" with fastboot.
So make sure your phone is in the proper mode for the command intended. Describing (or cut/paste from command prompt) the command intended, state of the phone, etc. will help us troubleshoot what you did wrong (if anything).
LilArmalite said:
So i don't need S=Off to let's say use "lucky patcher" or "Link2SD" or any other app that requires root?
Click to expand...
Click to collapse
S-off has nothing to do with root. As already stated, you don't need s-off to root. You can root s-on. Those apps only require root, so s-on is fine to use apps that require root.
---------- Post added at 09:19 AM ---------- Previous post was at 09:10 AM ----------
Also, I previously asked a number of questions, most of which you did not answer. If you want us to help, please be sure to fully read and understand advice given to you; and answer all questions and requests for further information:
redpoint73 said:
- Is custom recovery (TWRP) already installed on the device? From bootloader, pick the option to boot recovery, and tell us what happens. If TWRP is installed, tell us what version number.
- What adb package did you try to install? Is it the full Android SDK package? If so, there are much smaller/easier to install adb/fastboot installers available, if you simply use the xda seach function, and search "easy adb".
Click to expand...
Click to collapse
In particular, it would be a bit unusual (although possible) for a phone to have a unlocked bootloader, but not have TWRP installed. In other words, it is very possible you already have TWRP custom recovery installed. If you can look into this and verify; and what version (old versions can cause problems, so this is very important) then most of the work in rooting is already done. You would just need to get the SuperSU or Magisk root file on the phone, then flash it from TWRP in order to root.

redpoint73 said:
[/COLOR]Also, I previously asked a number of questions, most of which you did not answer. If you want us to help, please be sure to fully read and understand advice given to you; and answer all questions and requests for further information:
In particular, it would be a bit unusual (although possible) for a phone to have a unlocked bootloader, but not have TWRP installed. In other words, it is very possible you already have TWRP custom recovery installed. If you can look into this and verify; and what version (old versions can cause problems, so this is very important) then most of the work in rooting is already done. You would just need to get the SuperSU or Magisk root file on the phone, then flash it from TWRP in order to root.
Click to expand...
Click to collapse
Sorry i was out of internet for a few days,
Yes i think i do have HBOOT and when i get into recovery it reboots into a black screen with the picture of a phone that displays a warning sign (kinda like a: red triangular sign and a "!" on it) i recall having a similar mode back when i rooted a LGp350f but of course it's been a long time since that and i'm not really sure.
i think the package i installed was the one that i got from the installation instructions to install lineage.
it probably was the full sdk althought i don't know, i remember i had to set some path to "%USERPROFILE%\adb-fastboot\platform-tools" but i think all that did was allow me to enter those modes from the cmd.
sorry if i'm not really sure which one i used i did a bit of cleaning the other day and i erased it because it was not working.

LilArmalite said:
Sorry i was out of internet for a few days,
Yes i think i do have HBOOT and when i get into recovery it reboots into a black screen with the picture of a phone that displays a warning sign (kinda like a: red triangular sign and a "!" on it)
Click to expand...
Click to collapse
That is the stock recovery, so it verifies that custom recovery (needed to root or flash custom ROMs) TWRP is not currently installed (and will need to be in order to root or flash custom ROMs).
So you have a situation where either:
1) Previous owner unlocked the bootloader, but never installed TWRP. Possibly with the intent of doing it someday, but never happened (somewhat unlikely, but possible).
2) Previous owner returned the phone to stock (at least stock recovery) but did not relock the bootloader (more likely).
LilArmalite said:
i think the package i installed was the one that i got from the installation instructions to install lineage.
it probably was the full sdk althought i don't know, i remember i had to set some path to "%USERPROFILE%\adb-fastboot\platform-tools" but i think all that did was allow me to enter those modes from the cmd.
sorry if i'm not really sure which one i used i did a bit of cleaning the other day and i erased it because it was not working.
Click to expand...
Click to collapse
That looks like the full SDK was installed. But doesn't matter too much, if you deleted it.
I'm thinking your adb/fastboot issues are more a matter of pilot error, and/or unclear understanding. As your posts seem a little unsure about a number of things. Don't worry, I'm confident we can get adb/fastboot working, if you bear with me.
My suggestions would be:
1) Use xda seach function with the term "easy adb" and you will find a few lightweight and fast installers for adb/fastboot. I think there are 2-3 different ones. Just pick one, as they all seem to be pretty good.
2) Connect the phone to PC, boot to bootloader, and make sure FASTBOOT is highlighted in red near the top. Otherwise, use the volume buttons to select FASTBOOT, and confirm the choice with the power button.
3) Open a command prompt window. You will need to change directory to the one that contains the fastboot.exe file that was installed in step 1. Let me know if you need help with this.
4) Type command "fastboot devices" (without quotes) and the response should be your phone's serial number. Don't post the number, if you see it (it is personal info). Just tell us whether it works or not.

redpoint73 said:
That is the stock recovery, so it verifies that custom recovery (needed to root or flash custom ROMs) TWRP is not currently installed (and will need to be in order to root or flash custom ROMs).
So you have a situation where either:
1) Previous owner unlocked the bootloader, but never installed TWRP. Possibly with the intent of doing it someday, but never happened (somewhat unlikely, but possible).
2) Previous owner returned the phone to stock (at least stock recovery) but did not relock the bootloader (more likely).
That looks like the full SDK was installed. But doesn't matter too much, if you deleted it.
I'm thinking your adb/fastboot issues are more a matter of pilot error, and/or unclear understanding. As your posts seem a little unsure about a number of things. Don't worry, I'm confident we can get adb/fastboot working, if you bear with me.
My suggestions would be:
1) Use xda seach function with the term "easy adb" and you will find a few lightweight and fast installers for adb/fastboot. I think there are 2-3 different ones. Just pick one, as they all seem to be pretty good.
2) Connect the phone to PC, boot to bootloader, and make sure FASTBOOT is highlighted in red near the top. Otherwise, use the volume buttons to select FASTBOOT, and confirm the choice with the power button.
3) Open a command prompt window. You will need to change directory to the one that contains the fastboot.exe file that was installed in step 1. Let me know if you need help with this.
4) Type command "fastboot devices" (without quotes) and the response should be your phone's serial number. Don't post the number, if you see it (it is personal info). Just tell us whether it works or not.
Click to expand...
Click to collapse
Oh yeah, i went ahead and tried again, i still had the one i dumped in system32
for some reason sometimes when i put "fastboot devices" it just goes ahead and doesn't show nothing like it just skips into the next line for me to input something again, but then i closed and opened it again and after i put on "fastboot help" i put on "fastboot devices again" and now it gives me a 12 digit code and it says fastboot.
so i can just flash a rom in there?

LilArmalite said:
for some reason sometimes when i put "fastboot devices" it just goes ahead and doesn't show nothing like it just skips into the next line for me to input something again, but then i closed and opened it again and after i put on "fastboot help" i put on "fastboot devices again" and now it gives me a 12 digit code and it says fastboot.
so i can just flash a rom in there?
Click to expand...
Click to collapse
That is a little strange, but it seems like fastboot is working.
No, you don't flash ROMs using fastboot. What you need fastboot for, is to flash custom recovery TWRP. But before doing so, I want to see more info about your specific device and it's current condition. Do the command: fastboot getvar all
Then copy/paste the result. Delete IMEI and serial number before posting (personal info). If you don't know how to copy in cmd prompt, it is a little tricky (assuming Windows):
1) In cmd prompt window, right mouse click, and select "Mark"
2) Highlight the desired text you want to copy
3) Press CTRL+C to copy
4) In a forum post, paste with CTRL+V
5) Again, delete IMEI and serial number before posting

redpoint73 said:
That is a little strange, but it seems like fastboot is working.
No, you don't flash ROMs using fastboot. What you need fastboot for, is to flash custom recovery TWRP. But before doing so, I want to see more info about your specific device and it's current condition. Do the command: fastboot getvar all
Then copy/paste the result. Delete IMEI and serial number before posting (personal info). If you don't know how to copy in cmd prompt, it is a little tricky (assuming Windows):
1) In cmd prompt window, right mouse click, and select "Mark"
2) Highlight the desired text you want to copy
3) Press CTRL+C to copy
4) In a forum post, paste with CTRL+V
5) Again, delete IMEI and serial number before posting
Click to expand...
Click to collapse
Here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.631.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Finished. Total time: 0.390s

Okay, good. So we know fastboot is working. I can also verify your firmware is up to date (as it can be - final Marshmallow firmware), as well as see your device version (Rogers).
1) Download TWRP version 3.2.3-1 from here: https://dl.twrp.me/m8/
2) Put the TWRP file in the computer folder that contains fastboot.exe. Then flash TWRP to the phone with command: fastboot flash recovery twrp.img
Where "twrp.img" above (but no quotes) should match whatever the actual downloaded TWRP file is named. Verify in fastboot that the file flashed properly.
3) Put the desired custom ROM zip on the phone's internal storage (or alternately, SD card). Various ways to do this. One is boot to TWRP, then you should be able to browse to the phone's internal storage using your computer, and copy/paste the ROM file.
4) Boot to recovery, pick "Backup" and backup the current (stock?) ROM.
5) Backup whatever personal data you want to keep. Various methods. But you will need to wipe data to install a custom ROM properly.
6) In TWRP, select "Wipe". Do the default wipe (data, cache, Dalvik).
7) In TWRP, go back "Home" and select "Install". Browse to the desire custom ROM file. Then flash it. This may take a couple minutes. Some custom ROMs maybe require an additional Google apps file to be flashed (gapps), check the desired ROM thread. When done, reboot phone to system.
8) Will probably take a few minutes to boot up, than a few more once OS is booted to build app cache. But should be more than 10 minutes or so, or you may have done something wrong.
9) Enjoy