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.

biggest root fail of all time!

i rooted my phone with no issues, it was unlocked and s off. i uploaded a custom rom that was intended for kitkat 4.4.4 but my phone was 4.4.2. the phone flips to S-ON and says "Tampered". i've tried downloading the right firmware specifically for my phone. ive tried every method known to man just to get the phone back to stock. including sunshine and firewater. looked up the exact firmware for this phone... flashed. nothing. still the same. phone works great with this Venom custom rom but... i have no wifi. also, when the phone reboots, it takes forever. like, a good 15 minutes. i dont know what else to do. i just want to go back stock with S-OFF, update to 4.4.4. then try rooting again. this has been a massive headache. never had issues like this rooting samsung devices. htc is a whole different ballgame!

MPH33 said:
never had issues like this rooting samsung devices. htc is a whole different ballgame!
Click to expand...
Click to collapse
Every phone is different and has its own learning curve. Comparisons to Samsung are pointless.
How did you s-off originally?
My suggestion would be to unlock the bootloader again (if its now relocked) install custom recovery, than nandroid back to stock. Sunshine s-off, then stock recovery and OTA. Once updated, install custom recovery again and root.

redpoint73 said:
Every phone is different and has its own learning curve. Comparisons to Samsung are pointless.
How did you s-off originally?
My suggestion would be to unlock the bootloader again (if its now relocked) install custom recovery, than nandroid back to stock. Sunshine s-off, then stock recovery and OTA. Once updated, install custom recovery again and root.
Click to expand...
Click to collapse
now my phone is stuck in htc boot. how can i flash a recovery back to the phone with adb? cmd doesnt see device. just stuck in htc boot(white screen with " this build is for development purposes only" in bright red)

Bootloader always works as long as the screen comes on.
Hold down power + vol up until the phone reboots. The moment the screen goes dark to restart, let go of those buttons and just hold vol down. This will get you into bootloader. If it doesn't work, you just did the button combo wrong (either didn't press vol down soon enough, or let go too early). Just try again until you are in bootloader. From there, go into fastboot mode and erase cache and flash recovery.

just find and flash the latest firmware for your m8 from RUU mode. if you can let us know the variant maybe someone here can help.
Also, I am pretty sure Viper ROM's OP says to update to latest firmware else wifi wont work and also warns about long boot times.

im able to go in to recovery, now i need to flash a rom to get the phone going. can this be done through cmd? im unable to access phone storage through fastboot usb in recovery. i was trying to place stock rom on phone but have zero access

MPH33 said:
im unable to access phone storage through fastboot usb in recovery.
Click to expand...
Click to collapse
I think you mean fastboot mode, which is different from recovery. If on a Windows PC, try to uninstall HTC Sync and drivers. Then when the phone connects, go to Device Manager, find the device. Select the option to manually select drivers, and pick the Generic MTP Android device drivers.
MPH33 said:
now i need to flash a rom to get the phone going. can this be done through cmd?
Click to expand...
Click to collapse
Sure, use adb push.
Or put a ROM on your SD card using a USB card reader connected to your computer.

redpoint73 said:
I think you mean fastboot mode, which is different from recovery. If on a Windows PC, try to uninstall HTC Sync and drivers. Then when the phone connects, go to Device Manager, find the device. Select the option to manually select drivers, and pick the Generic MTP Android device drivers.
Sure, use adb push.
Or put a ROM on your SD card using a USB card reader connected to your computer.
Click to expand...
Click to collapse
i want to push "stock 1.12.502.18 - TWRP - CWS__001." through cmd. how do i do this? im not an expert on cmd language. i just want to put any rom on this phone so i can get it working. i have a newborn baby. phone is a must

MPH33 said:
i want to push "stock 1.12.502.18 - TWRP - CWS__001." through cmd. how do i do this? im not an expert on cmd language. i just want to put any rom on this phone so i can get it working. i have a newborn baby. phone is a must
Click to expand...
Click to collapse
I'm assuming you are using a Windows PC (otherwise I can't really help):
1) Put the file in the same folder that contains adb.exe
2) With phone connected, open command prompt. Change directory to your adb folder.
3) Enter command: adb push ROM.zip /data/media/0/
Where ROM.zip is the name of the file. You can actually rename the file ROM.zip if you like (to make it shorter to type). But make sure in Windows that you do not have the option selected to hide file extensions (based on the file you stated, you might in fact have this selected, a ROM file should have extension .zip), otherwise you may accidentally name the file ROM.zip.zip and not know it (common mistake).

finally get the rom on my phone and it failed to install through philz clockwork. im freaking pissed! i cant believe how tough this is! i dont know what else to do! i converted the rar file to zip. still didnt work.

MPH33 said:
finally get the rom on my phone and it failed to install through philz clockwork. im freaking pissed! i cant believe how tough this is! i dont know what else to do! i converted the rar file to zip. still didnt work.
Click to expand...
Click to collapse
A ROM should be a ZIP, not a RAR. What are you trying to flash?
Also, I can't tell if my suggestions are helping or not. You don't indicate whether you have tried the suggestions/steps I gave you; or if they didn't work, or if got here some other way.

redpoint73 said:
A ROM should be a ZIP, not a RAR. What are you trying to flash?
Also, I can't tell if my suggestions are helping or not. You don't indicate whether you have tried the suggestions/steps I gave you; or if they didn't work, or if got here some other way.
Click to expand...
Click to collapse
finally! i found android revolution hd 21.1 in my recovery. sux that i dont have wifi but atleast i have a phone. i sure wish i could go back to stock to start over again. even when i went back to 4.4.2, it never would let me update to 4.4.4. i use an at&t phone with cricket wireless. maybe that has something to do with it. my phone never update even before i rooted

MPH33 said:
finally! i found android revolution hd 21.1 in my recovery. sux that i dont have wifi but atleast i have a phone. i sure wish i could go back to stock to start over again. even when i went back to 4.4.2, it never would let me update to 4.4.4. i use an at&t phone with cricket wireless. maybe that has something to do with it. my phone never update even before i rooted
Click to expand...
Click to collapse
Which firmware version have you got installed now?? U can check it under settings/info/software info

OmniSlyfer said:
Which firmware version have you got installed now?? U can check it under settings/info/software info
Click to expand...
Click to collapse
This is wrong. settings/info/software info shows just the base the ROM is built on, not the actual firmware. his software info will show 3.28.401.7 which is clearly wrong since he doesn't have a working Wifi which shows that he is on older firmware.
The only reliable way to find the firmware is
fastboot getvar all

From what you've said you've a AT&T branded handset, so download the following:
http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
Put your phone into fastboot mode, but powering down and then holding volume down + power until you get to the hboot screen, press power again to enter fastboot mode.
Connect your phone via usb to your pc, (ensuring you've removed htc sync and have the relevant fastboot drivers), run the downloaded .exe file and let the process run until completion.
This should restore your phone to stock rom, your bootloader should still be unlocked and if s-off (if applied) still active.
I've been struggling to follow what it is you had done to put yourself into this problem, I recommend reading through all the guides available development forum before rooting and flashing again.
Many new roms will require a firmware update, or you'll find that wifi won't work.
Let us know how you get along.

OmniSlyfer said:
Which firmware version have you got installed now?? U can check it under settings/info/software info
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXXX
imei: 3587180508XXXXXXXXX
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0

downbringer said:
From what you've said you've a AT&T branded handset, so download the following:
http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
Put your phone into fastboot mode, but powering down and then holding volume down + power until you get to the hboot screen, press power again to enter fastboot mode.
Connect your phone via usb to your pc, (ensuring you've removed htc sync and have the relevant fastboot drivers), run the downloaded .exe file and let the process run until completion.
This should restore your phone to stock rom, your bootloader should still be unlocked and if s-off (if applied) still active.
I've been struggling to follow what it is you had done to put yourself into this problem, I recommend reading through all the guides available development forum before rooting and flashing again.
Many new roms will require a firmware update, or you'll find that wifi won't work.
Let us know how you get along.
Click to expand...
Click to collapse
just tried this. i got an error message about usb. cant read phone. odd. maybe it was my spyware running in the background. this sux. i really wanted this to work. looked very promising

Not likely to be spyware, more likely to be the fact that you don't have the right fastboot drivers installed on your pc.
Download the application from this thread and follow the instructions to set up fastboot.
http://forum.xda-developers.com/showthread.php?t=2588979
After completing that - reboot your pc and then attempt the install of the RUU again following my original instructions.

MPH33 said:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXXX
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Why do you take out your serial number but leave the more important IMEI number there? Take it out of your post.
Also your HBOOT version is still old 3.16, ARHD runs on the 3.28 firmware with HBOOT 3.19. You need to update your firmware in order to run a newer version of ARHD.

downbringer said:
Not likely to be spyware, more likely to be the fact that you don't have the right fastboot drivers installed on your pc.
Download the application from this thread and follow the instructions to set up fastboot.
http://forum.xda-developers.com/showthread.php?t=2588979
After completing that - reboot your pc and then attempt the install of the RUU again following my original instructions.
Click to expand...
Click to collapse
failed ruu. said chose different firmware to update. disappointed. thought for sure this would work
thanx for trying though

[Q] Bricked?! Can't access bootloader, recovery or rom anymore

Hi!
I wanted to update my firmware as some recent lollipop roms refused to flash (I was at AOSPA 4.5 I think). So I looked up, what firmware I had and tried to get back to stock somehow.
It turned out that I had a 1.57.112.2 firmware (T-Mobile AT branding) although I bought an unbranded one (so I should have some x.xx.401.x I think). Nevertheless I looked for stock recovery and backup and found some here (1.57.112.2 recovery) and here (1.57.111.2 twrp backup).
After flashing both, I had a stock ROM running and got an OTA offered which I accepted. After the OTA got downloaded completely, the system said, that it couldn't apply this update. I assume this is because it downloaded the german OTA (1.57.111.2 rom) and wanted to apply it on the austrian firmware (1.57.112.2).
So I thought, maybe I can trick you to download the correct ota by making the rom think, it is the austrian one. I therefor patched the following files:
- system/build.prop
- system/customize/AAInfo.txt
- system/customize/MNS/26201_CS.xml
- system/customize/MNS/26201_Telekom.xml
- system/customize/MNS/default.xml
- system/customize/resource/CCInfo.txt
I basically changed every firmware version or sku occurence from 111 to 112 or t mobile de to t mobile at.
To patch these files I edited them on my pc, pushed to sdcard, booted the phone into recovery, mounted /system and /storage/sdcard1 and then moved the files I had on my sdcard into the correct /system directories.
Then I issued
Code:
adb reboot
to try the OTA once again. But after the htc splash screen, the screen just turns black. I'm not even able to get into hboot/fastboot during this splash screen.
After a few minutes, the phone reboots, thus showing the htc splash screen once again and turning black afterwards.
While the screen is black, I'm not able adb/fastboot into the device. Also the phone doesn't react on pressing some buttons or plugging the power cable.
Do you have some ideas how to get a working base back?
fastboot, recovery, anything?

What you did was a really bad idea. OTA updates are often not complete images (only updated modules are updated). And since you forced the phone to install the 112 OTA over an existing 111 install, its possible there was a bad mixing of components ("old" 111 modules + "new" 112 modules) such as the 3 hboot modules (or some other combination of things that don't play together well). One might not think there would be that much difference between the 1.57.111 versus 1.57.112. But without the proper research, who knows?
The proper sequence would have been to s-off (it probably was already, if in fact it was unbranded with T-Mob firmware applied), change CID and MID, then RUU back to stock. Or if no RUU, restore stock WWE ROM, and firmware.
Try holding down power & vol up, power & vol down, or just power for 30 seconds or more. With or without the charger plugged.
Any response if you plug the phone to a computer?
If none of the above works (and no LED), it probably JTAG for you.

Why so impulsive to try that? Seems like you winged it without looking up any repercussions.

@redpoint73
It is/was S-ON atm.
I've tried RUUs before but either there was a version mismatch or the RUU wasn't able to keep the connection and failed to connect to the device after the first reboot into ruu mode.
The power + volume up + volume down works in terms of rebooting but doesn't bring the device out of the bootloop (or whatever it's looping). I'm having adb and fastboot waiting for a device connection but both didn't fire up yet, so I assume, the phone won't provide any adb or fastboot client.
@jduke05
Well.. For the m7 I read, that the german and austrian version were exchangeable so I hoped something like that would count for the m8 too. (typically me....)
Also the ota said, it can't and won't update. I thought it didn't change anything if it complained that it won't change anything.

Uroc327 said:
@redpoint73
It is/was S-ON atm.
I've tried RUUs before but either there was a version mismatch or the RUU wasn't able to keep the connection and failed to connect to the device after the first reboot into ruu mode.
The power + volume up + volume down works in terms of rebooting but doesn't bring the device out of the bootloop (or whatever it's looping). I'm having adb and fastboot waiting for a device connection but both didn't fire up yet, so I assume, the phone won't provide any adb or fastboot client.
Click to expand...
Click to collapse
When S-on, RUU needs to match your CID and MID, and has to be equal or greater software version than what is on the phone. No exceptions.
The phone boots, that is good, as it means its not bricked.
Although, you're pretty stuck if you don't get adb/fastboot working. Connection issues are usually on the PC side. Try different USB ports, cables. Or try to re-install HTC Sync. Also, adb will only work when booted into OS or recovery. Fastboot will work when booted into bootloader fastboot mode. This alone may be your issue (adb won't work in bootloader/fastboot).
S-on is also a good thing in your case. It means that probably nothing installed anyway, since with s-on the OTA would have failed with wrong CID (and you can only change CID with s-off).
Uroc327 said:
Well.. For the m7 I read, that the german and austrian version were exchangeable so I hoped something like that would count for the m8 too. (typically me....)
Click to expand...
Click to collapse
What applies for another device should never be assumed to be the same for yours.
A lot of things change, even from one software build to the next (same device) so I would erase any assumption that they are interchangeable. Don't ever assume anything, for that matter.

Hmm.. although I don't get any fastboot/adb response, udev (oh yeah, forgot to mention I'm on linux) fires some events when the device reboots. Though I don't know any protocol I can use to speak to the device.
Well the problem with the RUUs was, that Windows tried to install some new drivers as soon as the device rebooted into ruu mode instead of using the already installed drivers.
But, though I'm having S-ON, it installed enough to not enter the bootloader/fastboot/rom/... (whatever the first thing not showing up is).

It seems like it's just an ordinary damaged boot partition.
After having it rebooting the night the battery was finally empty and I was able to get into the (undamaged) bootloader and into the (also undamaged) recovery.. Isn't it great that one can't take out the battery any more?
Anyways.. thanks for your replies

Uroc327 said:
After having it rebooting the night the battery was finally empty and I was able to get into the (undamaged) bootloader and into the (also undamaged) recovery.. Isn't it great that one can't take out the battery any more?
Click to expand...
Click to collapse
If the phone is rebooting, all you need to do is hold vol down, and it will go to bootloader on the next reboot.
Battery pull isn't needed on this phone, but the correct knowledge is.

redpoint73 said:
If the phone is rebooting, all you need to do is hold vol down, and it will go to bootloader on the next reboot.
Battery pull isn't needed on this phone, but the correct knowledge is.
Click to expand...
Click to collapse
That's exactly what I did! I know how to get into the bootloader... But nothing happened.
The only way to influence the device was to hold down power + volume up + volume down. Then it wen't to the white splash screen with the green htc on it (then holding down volume down didn't do anything either) and continued with the loop.

Uroc327 said:
.....it wen't to the white splash screen with the green htc on it (then holding down volume down didn't do anything either) and continued with the loop.
Click to expand...
Click to collapse
when it is on the white splash screen,
Press & hold volume up & power buttons until the screen goes dark (it's rebooting)
then release both buttons, quickly press & hold volume down button. This will take it to bootloader screen.
On method above ... require only one or two buttons press at one time ... there is no three button press at the same time.
If you can get to bootloader, post result of fastboot getvar all minus serial no. & imei no.
I may have the correct TWRP backup for your software version.

ckpv5 said:
when it is on the white splash screen,
Press & hold volume up & power buttons until the screen goes dark (it's rebooting)
then release both buttons, quickly press & hold volume down button. This will take it to bootloader screen.
On both method above ... require only one or two buttons press at one time ... there is no three button press at the same time.
If you can get to bootloader, post result of fastboot getvar all minus serial no. & imei no.
I may have the correct TWRP backup for your software version.
Click to expand...
Click to collapse
Gonna try the volume up + power next time.. (Probably it's the same as both volumes + power but i really don't know).
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA10G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.112.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB102
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It would be awesome, if you could find a twrp version that boots
I've tried versions 2.7.0.1, 2.8.5.0 and 2.8.6.0 and every time I've waited forever on the htc splash screen with the purple 'Entering Recovery ...' without seeing anything happening.
Currently I'm using philz touch (booting fine) for clockworkmod backups and a simple tar -xf in the adb shell and fastboot flash boot for twrp backups

Uroc327 said:
That's exactly what I did! I know how to get into the bootloader... But nothing happened.
The only way to influence the device was to hold down power + volume up + volume down. Then it wen't to the white splash screen with the green htc on it (then holding down volume down didn't do anything either) and continued with the loop.
Click to expand...
Click to collapse
It sounds like you are actually talking about the phone being stuck on the boot splash, not a "boot loop".
A boot loop means the phone is rebooting itself over and over on its own. When this is the case, holding the vol down will send you to bootloader on the next reboot "loop".
If its stuck on the bootsplash, its probably just a timing issue. Power+ vol up reboots the phone. The moment screen goes dark, but before the HTC boot slash appears, let go of those buttons, and only hold vol down, and don't let go until bootloader comes up. Failure to get into bootloader is virtually always a case of not pressing vol down soon enough, or letting go too early. After dozens of claims of this not working, I've seen every single one proven as being a case of not performing the button combo timing correctly. The only exception, is the (very rare) instance of the power button or vol rocker being physically broken.

redpoint73 said:
It sounds like you are actually talking about the phone being stuck on the boot splash, not a "boot loop".
A boot loop means the phone is rebooting itself over and over on its own. When this is the case, holding the vol down will send you to bootloader on the next reboot "loop".
If its stuck on the bootsplash, its probably just a timing issue. Power+ vol up reboots the phone. The moment screen goes dark, but before the HTC boot slash appears, let go of those buttons, and only hold vol down, and don't let go until bootloader comes up. Failure to get into bootloader is virtually always a case of not pressing vol down soon enough, or letting go too early. After dozens of claims of this not working, I've seen every single one proven as being a case of not performing the button combo timing correctly. The only exception, is the (very rare) instance of the power button or vol rocker being physically broken.
Click to expand...
Click to collapse
As I've state in post #4 I don't exactly know what it's actually looping. I just know, that it shows this splash screen over and over again.
The screen goes dark automatically: It was like splash screen (few seconds.. normal time) -> black screen (a few minutes) -> return to splash screen
So the screen turned dark anyways (which indeed indicates a timing issue from my side as you said).

Uroc327 said:
Gonna try the volume up + power next time.. (Probably it's the same as both volumes + power but i really don't know).
Click to expand...
Click to collapse
It is the same. Power + vol up + vol down is not a valid button combo.
Power + vol up (force reboot)
Power + vol down (boot recovery when powered off; vol down only needed when rebooting)
Uroc327 said:
It would be awesome, if you could find a twrp version that boots
I've tried versions 2.7.0.1, 2.8.5.0 and 2.8.6.0 and every time I've waited forever on the htc splash screen with the purple 'Entering Recovery ...' without seeing anything happening.
Click to expand...
Click to collapse
Did you fastboot erase cache before flashing a new TWRP version?

redpoint73 said:
Did you fastboot erase cache before flashing a new TWRP version?
Click to expand...
Click to collapse
Of course

Unfortunately I don't keep 1.57.112.2 (I've deleted most of the 1.xx.xxx.x backups as I thought no one will ever need them anymore)
I have only 2.23.112.3, 3.29.112.9 & 4.19.112.2

ckpv5 said:
Unfortunately I don't keep 1.57.112.2 (I've deleted most of the 1.xx.xxx.x backups as I thought no one will ever need them anymore)
I have only 2.23.112.3, 3.29.112.9 & 4.19.112.2
Click to expand...
Click to collapse
I've found a 2.23.112.x for cwm, too. But is it a good idea to flash 2.23 onto a 1.57 firmware and then downloading an OTA?
I think I somewhere read that those firmware updates are incremental.

Uroc327 said:
I've found a 2.23.112.x for cwm, too. But is it a good idea to flash 2.23 onto a 1.57 firmware and then downloading an OTA?
I think I somewhere read that those firmware updates are incremental.
Click to expand...
Click to collapse
No ... that's not correct. Restore a one version lower backup on a higher firmware is ok but restore a one version higher than the firmware is a no.
Damn .. I don't keep the firmware too. If you can find the 2.23.112.3 firmware then it's good too.
You can restore the 2.23.112.3 then flash 2.23.112.3 firmware, reboot and do OTA

ckpv5 said:
No ... that's not correct. Restore a one version lower backup on a higher firmware is ok but restore a one version higher than the firmware is a no.
Damn .. I don't keep the firmware too. If you can find the 2.23.112.3 firmware then it's good too.
You can restore the 2.23.112.3 then flash 2.23.112.3 firmware, reboot and do OTA
Click to expand...
Click to collapse
I've looked the last two days but I didn't find firmwares for 112 by now.
Does flashing the firmware need s-off already? Do OTAs and RUUs (for this firmware) work with s-on?

Uroc327 said:
I've looked the last two days but I didn't find firmwares for 112 by now.
Does flashing the firmware need s-off already?
Click to expand...
Click to collapse
No need S-Off when flashing a signed firmware.
I will see whether I can find 2.23.112.3 firmware in a day or two
I have 3.29.112.5 & higher firmware but not 2.23.112.3

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