Develop Bugs

Cannot install TWRP Recovery

Hi,
My phone got the red triangle and exclamation mark after upgrading my firmware. I believe this was due to it wiping the custom recovery which was TWRP. I have tried to reinstall TWERP but I get stuck on the entering recovery screen.
I have tried to install twrp a couple of times with no joy but I have a copy of philz recovery and this installed 1st time.
Any ideas? I have tried clearing the cache in fastboot but am stuck.
I have no phone as the rom I install is on the ext sd card and Philz touch will not mount the ext sd card.
Thanks in advance
Ugg

uggitt said:
My phone got the red triangle and exclamation mark after upgrading my firmware. I believe this was due to it wiping the custom recovery which was TWRP. I have tried to reinstall TWERP but I get stuck on the entering recovery screen.
Click to expand...
Click to collapse
You reverted to stock recovery, which flashing firmware will always do, unless its a modded firmware which has the stock recovery removed.
Confirm that your bootloader is UNLOCKED (which is needs to be to flash recovery).
Also, if you update to Lollipop firmware (which is usually the reason for updating firmware) you need to use one of the more recent TWRP versions. I recommend TWRP 2.8.7.
Older TWRP versions do not work on LP, and fail to install properly is the mode of failure. Similarly, Philz does not work on LP.
EDIT: To clarify TWRP build.

I have checked and the bootloader is unlocked, s-off and super cid.
The problem is I cannot get twrp to load up. I install it with fasboot and all goes well but when I try to get into recovery it just stays on the entering recovery screen.
I have tried to reinstall the latest firmare using the'Firmware Flashing without the panic attacks' guide as I have always used and this seems to install ok and then tried to install twrp again ( I have tried the latest and the previous copy) but no joy. I can though install philz recovery and that boots up fine.
So still stuck trying to get twrp installed.
Also if I reboot the phone hangs while starting upon the htc screen with red text but the phone is actually working behind this, just cant see the normal desktop/startup screen. If i hold the power button so the screen goes off and the hold the power button to turn it on the screen comes to life.
For information, I am on Android HD 41.0 as this is the only rom I had on the internal sd

What numbers listed on hboot screen:
- hboot number
- radio baseband
- OS
And what version TWRP are you trying to install?

Hi,
Here is the info from getvar and thank you for your help:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA459WM******
(bootloader) imei: ********************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Twrp versions tried are 2.8.7.0 and 2.8.6.1 from https://twrp.me/devices/htconem8gsm.html

redpoint73 said:
Older TWRP versions do not work on LP, and fail to install properly is the mode of failure. Similarly, Philz does not work on LP.
Click to expand...
Click to collapse
I beg to differ, no problems running 2.8.5.0 or 2.8.6.0 on lollipop for me. Installed via fastboot or flashify.

uggitt said:
Here is the info from getvar and thank you for your help:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-main: 1.54.401.10
Click to expand...
Click to collapse
Your firmware flash never properly "stuck".
Your getvar data indicates you are on the original version firmware (1.54) which is over a year old. The current firmware would have updated you to hboot 3.19, radio 1.2xxx, and main version 4.16.401.
This also explains why Philz works, and the current versions of TWRP do not work. The current TWRP versions only work on Lollipop firmware; and only older TWRP versions work with your 3.16 firmware.
Try running the 4.16.401 firmware twice, this is often necessary to get it to flash properly. Then once you've confirmed you are on hboot 4.16, radio 1.2xxx, main version 4.16.401, then try TWRP 2.8.7.
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
ashyx said:
I beg to differ, no problems running 2.8.5.0 or 2.8.6.0 on lollipop for me. Installed via fastboot or flashify.
Click to expand...
Click to collapse
True, a few of the recent builds will work on LP. But older ones than that won't work, trust me. I forget the breakoff point exactly, which is why I recommended the most current version (2.8.7). And once the most current version is known to be stablen (which 2.8.7 is), its usually the best recommendation.
I didn't mean to state that 2.8.7 is the only version that works. But I see how it can be interpreted that way (and have edited the previous post for clarity). For some reason, I constantly see folks still trying to flash much older TWRP builds (2.7 or so) onto Lollipop (which won't work).
And it turns out the OP had the opposite issue (trying to flash newer version TWRP on really old firmware hboot 3.16).

Thank you, I will try and flash the firmware again. Have you a link for this. I have been getting it from the ARHD Firmware page but not sure if its corrupt.

uggitt said:
Thank you, I will try and flash the firmware again. Have you a link for this. I have been getting it from the ARHD Firmware page but not sure if its corrupt.
Click to expand...
Click to collapse
4.15.401 (Euro) firmware is probably the most commonly downloaded and installed firmware from that collection. So it should be fine.
You probably just flashed the firmware once; when twice is often needed.

I managed to get the updated firmware on my phone eventually. I had to download from another link and it flashed first time.
Twrp installed straightaway and I am back on S.Rom.
Thank you for all your help, much appreciated
ugg..

M8 No OS After Flash

Hi,
Having issues trying to put SuperSU on my M8. Heres what I've done:
- Unlocked bootloader
- Fastbooted TWRP on the phone
- Tried Flashing the ROM, says No OS installed. Rebooting stops at Android screen
- Tried downloading RUU and going back to stock, however the RUU tells me that there's an error and it can't continue.
- Tried switching between TWRP and CWM.
- Tried sideloading from my pc with a few different versions of SuperSU
Nothing seems to work.
Can anyone point me in the right direction?
Any help will be greatly appreciated.
If there's any more information you would like me to provide, just let me know.
Thanks Again,
Nick

My responses below in red font:
varioushalifax said:
Having issues trying to put SuperSU on my M8. Are you trying to root the stock ROM, or flash a custom ROM? Because they are 2 different things, with different approaches. And your steps described below contradict each other on this matter..
Heres what I've done:
- Unlocked bootloader
- Fastbooted TWRP on the phone What version TWRP?
- Tried Flashing the ROM, says No OS installed. Rebooting stops at Android screen Which ROM exactly? Did you try another ROM? Did the ROM install properly (any error messages in TWRP when you flashed?
- Tried downloading RUU and going back to stock, however the RUU tells me that there's an error and it can't continue. What RUU (exact file name)? What was the error message and error number? These are important, as they tell you why the RUU failed.
- Tried switching between TWRP and CWM. Not recommended. CWM hasn't been updated in a long time, and can cause some problems in itself.
- Tried sideloading from my pc with a few different versions of SuperSU If you have no OS, flashing SuperSU isn't going to help matters.
Click to expand...
Click to collapse
Additonally, do fastboot getvar all, so we can see more info about the phone. Delete IMEI and serial number before posting.

Are you trying to root the stock ROM, or flash a custom ROM?
Originally I tried to put SuperSU2.37 on there, that didn't work, so I tried SuperSU2.77, which failed. I then tried to RUU to stock, which I'm having issues with also.
- What version TWRP?
3.0.2-0
- Any error messages in TWRP when you flashed?
It doesn't show any errors. After it's finished it says No OS Installed, are you sure you want to reboot?
- What RUU (exact file name)?
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Error 155
Please get the correct RUU and try again.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: HTC__203
(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
Thanks again,
Nick

redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
your method to solve problems to the point by red font is very nice master redpoint. :good:

varioushalifax said:
Originally I tried to put SuperSU2.37 on there, that didn't work, so I tried SuperSU2.77, which failed.
Click to expand...
Click to collapse
SuperSU version 2.37 is really old. Not sure how you even came about it (old toolkit maybe?), that version probably wouldn't work on Lollipop, much less your current Marshmallow firmware.
SuperSU 2.77 should be okay, its current and updated for MM. I might suggest the latest "STABLE" version, which is 2.76 from here. But honestly, they are all pretty stable from what I've seen, and it probably wouldn't make a huge difference wither way (the version 2.77 should be ok). And it seems like the main problem is that we need to solve the "No OS" issue before proceeding.
varioushalifax said:
It doesn't show any errors. After it's finished it says No OS Installed, are you sure you want to reboot?
Click to expand...
Click to collapse
My guess, is that you did something to delete the OS, that maybe you missed when listing the steps you did. Since, I can't see how OS could be wiped/missing with what you indicated. At least up until you tried RUU, since if you relocked the bootloader to RUU (which is a requirement unless you have s-off), that wipes the OS (so maybe you just have the order of steps you tried, mixed up?).
varioushalifax said:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Error 155
Click to expand...
Click to collapse
That RUU isn't for your version. Maybe the "WWE" in the file name has you confused, but its actually for the US Developer's Edition. What you need would have version number with "401" instead of "1540", but you would only know that from experience or reading it somewhere on the forums.
You should be able to use the following RUU (zip format, not exe - so follow the instructions to flash): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, restore the stock TWRP backup 6.12.401.4 using the file and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Not sure whether your bootloader is currently relocked or unlocked, as you haven't indicated, either way. It needs to be relocked to RUU, or alternately it needs to be unlocked to do the TWRP stock backup method.
---------- Post added at 09:35 AM ---------- Previous post was at 09:17 AM ----------
umesh.lk said:
your method to solve problems to the point by red font is very nice master redpoint. :good:
Click to expand...
Click to collapse
Haha, I find that a good way to respond to numerous statements or questions in a previous post; rather than using multiple quotes. And red just seems to stand out well, compared to other colors! But love your observation.

Thanks so much!
I wasn't sure which files i needed for that walkthrough, until you told me which ones.
Phone is back up and working fine.
Thanks again mate

Phone Freezes Upon Booting (Android N ROMS)

Hello XDA,
I've made absolutely no changes to my phone settings, ROMS, Kernal ETC..
Recently, I've decided to upgrade to a new ROM which was CRDroid Android 7.0 (Name may be wrong)
I use Philz CWM recovery, while installing I noticed once it finished it said cannot mount /data.
Though the phone rebooted on it's own and started to boot, but once it reached the boot logo the phone froze.
Directly in the middle of the animation, it stopped and stayed that way for at least 15 minutes before I had to hard reset it.
I noticed I cannot install any type of Android N (7.0) ROM without freezing, I can only install Marshmellow or lower.
Can anyone explain why, is this a firmware issue perhaps?

Use the latest TWRP recovery
Philz is outdated now and most probably won't work
Sent from my HTC M8 using XDA Labs

Regardless of the recovery used, problem still persists. I believe it may be a firmware issue.

Trytohaxme said:
Regardless of the recovery used, problem still persists.
Click to expand...
Click to collapse
Does that mean you tried TWRP or not? And what version(s)?
In TWRP do you still get issue not mounting data? If so, try going to Wipe section of TWRP, and tap "Format data" which will often fix the mount data problem. Obviously, your data will be lost.
Please try to give as much detail and specific as possible when posting. Posting a 2 sentence response is rarely enough for us to work with.
Trytohaxme said:
I believe it may be a firmware issue.
Click to expand...
Click to collapse
We would need to know more about the firmware to say anything about that. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting0

Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 99000499864898
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.098s
I've tried about 3 versions of TWRP, including the latest version.
I'm no longer able to format or install using TWRP which is the reason I have to use Philz.
I have major screen burn issues on the top portion of my phone, so touch is unresponsive so being able to use the volume rocker with Philz recovery is a life saver.
I've heard something about connecting the phone to a windows laptop, and formatting the partitions VIA > Device Manager helps with mounting the /Data partition though because I believe mine may be corrupt as I can only install ROMS that do not touch the data partition.

Trytohaxme said:
(bootloader) version-main: 4.17.605.5
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B20000
Click to expand...
Click to collapse
Your firmware is Lollipop. I'm not a user of the AOSP ROMs (as all Nougat ROMs are), but from what ahmed posted, LP ROMs can indeed cause problems with Hougat: https://forum.xda-developers.com/htc-one-m8/help/upgrade-5-1-1-to-7-x-x-to-firmware-t3580047
Also, your getvar output shows you have the Verizon M8. Did you verify the ROMs support the Verizon version?

redpoint73 said:
Your firmware is Lollipop. I'm not a user of the AOSP ROMs (as all Nougat ROMs are), but from what ahmed posted, LP ROMs can indeed cause problems with Hougat: https://forum.xda-developers.com/htc-one-m8/help/upgrade-5-1-1-to-7-x-x-to-firmware-t3580047
Also, your getvar output shows you have the Verizon M8. Did you verify the ROMs support the Verizon version?
Click to expand...
Click to collapse
I'm currently downloading MM firmware for my device, and yes I verify there is Verizon support.
Though my phones model is Verizon branded, the phone is unlocked and I use it with T-Mobile.

Trytohaxme said:
Though my phones model is Verizon branded, the phone is unlocked and I use it with T-Mobile.
Click to expand...
Click to collapse
What M8 version is important in this case (Verizon) for a variety of reasons, and I'm not talking about what carrier you are using it on. The Verizon version M8 is very unique in that it uses different kernel, partitioning, and antenna hardware due to CDMA support. Plus, you can only flash Verizon firmware or RUU (others won't work, and may even cause a permanent radio brick). The Sprint version has similar aspects (although the firmware is not even interchangeable between Sprint and Verizon M8 versions).

redpoint73 said:
What M8 version is important in this case (Verizon) for a variety of reasons, and I'm not talking about what carrier you are using it on. The Verizon version M8 is very unique in that it uses different kernel, partitioning, and antenna hardware due to CDMA support. Plus, you can only flash Verizon firmware or RUU (others won't work, and may even cause a permanent radio brick). The Sprint version has similar aspects (although the firmware is not even interchangeable between Sprint and Verizon M8 versions).
Click to expand...
Click to collapse
Well, I did a little more research and seem to have come to the conclusion that in order to flash the roms I'm trying to flash I need to use TWRP.
The problem is since my phone top portion of the screen is not touch responsive, I have no choice but to use Philz.
Is there a TWRP that would happen to work in landscape mode, otherwise I'm SOL.

Trytohaxme said:
Well, I did a little more research and seem to have come to the conclusion that in order to flash the roms I'm trying to flash I need to use TWRP.
The problem is since my phone top portion of the screen is not touch responsive, I have no choice but to use Philz.
Is there a TWRP that would happen to work in landscape mode, otherwise I'm SOL.
Click to expand...
Click to collapse
I understand you have some peculiar things going on causing you to use Philz. I don't think there is a harm in trying Philz (to flash an N ROM), after you have the firmware updated. But I just wouldn't expect Philz (which hasn't been updated for 2 years) to work well with the latest ROMs.
No landscape TWRP that I know of.

redpoint73 said:
I understand you have some peculiar things going on causing you to use Philz. I don't think there is a harm in trying Philz (to flash an N ROM), after you have the firmware updated. But I just wouldn't expect Philz (which hasn't been updated for 2 years) to work well with the latest ROMs.
No landscape TWRP that I know of.
Click to expand...
Click to collapse
Each ROM I tried installed give me basically the same output, maybe you can help figure them out.
Code:
detected filesystem ext4 for /dev/block/flatform/msm_sdcc. 1/by-name/system
unmount of /system failed
failed to mount /dev/block/flatform/msm_sdcc. 1/by-name/userdata at /data: device or resource busy
These are the 3 differents errors I receive during installation of a new ROM.
After those errors show the ROM continues with the installation, but as soon as the phone boots it freezes than reboots back to recovery.

Trytohaxme said:
Each ROM I tried installed give me basically the same output, maybe you can help figure them out.
Click to expand...
Click to collapse
Is this with Philz?
Is this on the LP firmware or MM firmware?
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
Maybe adb sideload feature can help you to use TWRP in your condition?
https://twrp.me/faq/ADBSideload.html

redpoint73 said:
Is this with Philz?
Is this on the LP firmware or MM firmware?
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
Maybe adb sideload feature can help you to use TWRP in your condition?
https://twrp.me/faq/ADBSideload.html
Click to expand...
Click to collapse
This is on LP and MM firmware, and the same output occurs even while using sideload sadly
Here is a photo I just took using my laptops webcam, as you see the boot animation starts than completely freezes.
http://imgur.com/BSZ2ZzD

Soft Bricked M8 in need of help badly

Hi there in need of some help. I have really ****ed up my install of twrp and supersu from my htc one m8.
I followed this person tutorial htconeroot com/htc-one-root I followed everything to the letter apart from enabling Dev enable usb debugging.
1st of all I downloaded this twrp file "openrecovery-twrp-2.7.0.2-m8" when I should have downloaded the latest version of twrp. Such a noob mistake I know now : (
2nd I also downloaded a older version of supersu SuperSU-v2.79-201612051815 which I loaded onto my phone and should have downlaoded the latest version.
I followed all the instruction on the video and when I rebooted after instaling supersu my device is now stuck on the HTC startup screen.
I tried to reboot again going into fastboot and recovery and nothing worked. I know I should have just updated supersu to the latest version but I followed some other peoples advice and now I have completelty screwd my phone I think.
I deleted supersu from twrp and wiped the files as well. My computer now does not recognise my phone folder to be able to install any updated version of supersu or install a ROM. My computer OS is windows 10 and it now sees my phone as a cd drive so cannot install anything on the drive at all.
I can get into twrp but nothing seems to work when I try to reset back to factory settings.
Is there a command line way in geting back into my phone and being able to sort this mess that I have made.
In need of some serious help from the experts here at xda developers.
All help is very much appreciated.
Thanks Steve

tartansteve said:
I followed this person tutorial htconeroot com/htc-one-root I followed everything to the letter apart from enabling Dev enable usb debugging.
Click to expand...
Click to collapse
These random "root" websites just copy content from XDA, and have little or no community to help you. All you need is on XDA, so I recommend stick to XDA.
Such "root" websites also don't give enough information, aren't well organized, and don't update it all. So they are very likely to get you into trouble, as you now know.
tartansteve said:
2nd I also downloaded a older version of supersu SuperSU-v2.79-201612051815 which I loaded onto my phone and should have downlaoded the latest version.
Click to expand...
Click to collapse
What version, if it wasn't SuperSU 2.79?
What version of Android was the phone on when you started? Was it Marshmallow?
tartansteve said:
I can get into twrp but nothing seems to work when I try to reset back to factory settings.
Click to expand...
Click to collapse
There is really no such thing as "reset back to factory settings" especially in TWRP. Just going in and wiping things, isn't going to fix the problem.
Try to fastboot flash an updated version of TWRP. If you were on Marshmallow, try current version 3.1.0-0 from there: https://dl.twrp.me/m8/
Once booted into TWRP, see if you can access the internal storage from your PC. If not, make sure internal storage is checked in "Mount".

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: HTC__001
(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
Sorry was this version SuperSU-v2.37.zip. I do appologise thats the latest version that I posted and was ment to be this version SuperSU-v2.37.zip this is the one that I installed.
Yes it was marshmallow.
I downloaded the latest version of twrp and can I ask how to re install twrp ??
I cannot access my phone internal storage for some reason my computer is not recognising my phone now. It was before as I installed supersu straight onto my phone internal storage and tried to boot the phone from that. It's now coming up as a cd drive and I cannot access to install anything on it.
In mount all I have
System >>> not checked
cache >>> not checked
Data >>> is checked
Micro SDcard >> is checked
USB-OTG >>> not checked
Thanks again for your help
Steve

tartansteve said:
I downloaded the latest version of twrp and can I ask how to re install twrp ??
Click to expand...
Click to collapse
Flash with fastboot. Which I would assume is the same way you did it before. Instructions on TWRP's website: https://twrp.me/devices/htconem8gsm.html
tartansteve said:
I cannot access my phone internal storage for some reason my computer is not recognising my phone now.
Click to expand...
Click to collapse
Let's get the right version of TWRP on the phone first, and see if that helps. If not, we'll go from there.

Updated twrp
Hi just to let you know that I have booted into the new twrp. I am using FWUL and using simple-ADB and it installed it no problem.
Just cannot seem to find how to install supersu onto my device as my phone is not showing up FWUL OS.

Sorry, what is FWUL?

Updatefor you
Hi just to say that I installed supersu as well the latest version SuperSU-v2.79-201612051815. After rebooting I am back to the htc page. I have no ROM installed at all on this and it's saying there no OS installed on my phone.
I want to install kali Linux Nethunter and I have downlaod the correct files to install.
WillI have to install another OS like Marshmallow or kitkat before installing Kali Nethunter.
Thanks again for yourhelp : ))

[LIVE-ISO][FWUL][STABLE] adb/fastboot without any installation and driver issues
[F]orget [W]indows se [L]inux
Did you not send me there to download it lol : ))

tartansteve said:
I have no ROM installed at all on this and it's saying there no OS installed on my phone.
Click to expand...
Click to collapse
You must have at some point in trying to "fix" the problem, wiped system in TWRP. System is same as ROM/OS. So if you wiped it, it's pretty obvious that no ROM is the result.
Flashing old SuperSU in itself doesn't result in no ROM/no OS. It just makes the phone stuck on boot screen, and flashing the proper SuperSU will fix it.
tartansteve said:
WillI have to install another OS like Marshmallow or kitkat before installing Kali Nethunter.
Click to expand...
Click to collapse
I've never used it. But reading the thread, it looks like you need a fully working OS. So pick a ROM, put it on the phone, and flash it. Then flash Kali Nethunter.
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
tartansteve said:
[F]orget [W]indows se [L]inux
Did you not send me there to download it lol : ))
Click to expand...
Click to collapse
Ah, I see it's listed as one of the several options for adb/fastboot in the TWRP install instructions. I've never used that specific one, so the acronym confused me. Any fastboot/adb environment will work about the same. You didn't really need to install anything new on your computer. You already had fastboot on your computer to begin with (to unlock the bootloader), and that would have worked fine to install TWRP.

BackUp File
Hi there and thanks very much for your help very much appreciated. Before I did everything I made a back up and have the files on my desktop they are:
0C77AEECE8C258113148C6FB487946BF97B34672
01C669ECF50A775226B15B9F60EEB522AB34BE2F
I have ten of these files and a deafault file as well. Can I restore these to my hpne at all.
I am going to try and install marshmallow on my phone as that was the last OS that I had. Do I have to have the most current and updated version MM.

tartansteve said:
Before I did everything I made a back up and have the files on my desktop they are:
0C77AEECE8C258113148C6FB487946BF97B34672
01C669ECF50A775226B15B9F60EEB522AB34BE2F
Click to expand...
Click to collapse
What did you use to "backup" the phone? Those don't look like TWRP backup folder names. They look like MD5 verification codes?
Individual TWRP backup folders will usually have name format of the date/time the backup was made, such as: 2017-04-22-20-43-56....
tartansteve said:
I am going to try and install marshmallow on my phone as that was the last OS that I had. Do I have to have the most current and updated version MM.
Click to expand...
Click to collapse
There weren't many different official versions (maybe 1 or 2) of Marshmallow for each M8 carrier version. Any version MM should do.

"locked s-on" cant get to unlock and also stuck
ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
I HAVE DONE THE WHOLE PROCESS OF HTC DEV UNLOCKING WITH CODE AND EVERYTHING BUT STILL IT IS LOCKED
PLZ REPLY ON E-MAIL IF U CAN OR WHATSAPPP +92 333 23 63 968
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================

HTC one M8

Hope someone can help. My daughter switched on her HTC One M8 after months of not using and it is showing a page with software status modified, locked and s-on. I know nothing about HTC phones. I have spent 2 days trying to get the answer, but it is beyond me. Here is information I have.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(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: O2___001
(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.

Spontaneously not being able to boot to OS, and "Software Modified" error on a bootloader locked, previously unmodified (far as you know) phone; often means the OS has become damaged/corrupted.
I don't think your version (O2) has an official HTC RUU tool, which would make it pretty easy to get running again. The device can possibly still be recovered, but the process is not trivial. You would need to unlock the bootloader (HTCdev.com process), flash custom recovery TWRP, then install stock TWRP backup 6.13.206.5 from here (with further instructions herein): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
All personal data on the phone will be lost in the process (data on removable SD will remain, if there is one installed). But if your daughter has not used the phone in months, maybe the personal data on it is not important?

redpoint73 said:
Spontaneously not being able to boot to OS, and "Software Modified" error on a bootloader locked, previously unmodified (far as you know) phone; often means the OS has become damaged/corrupted.
I don't think your version (O2) has an official HTC RUU tool, which would make it pretty easy to get running again. The device can possibly still be recovered, but the process is not trivial. You would need to unlock the bootloader (HTCdev.com process), flash custom recovery TWRP, then install stock TWRP backup 6.13.206.5 from here (with further instructions herein): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
All personal data on the phone will be lost in the process (data on removable SD will remain, if there is one installed). But if your daughter has not used the phone in months, maybe the personal data on it is not important?
Click to expand...
Click to collapse
Thank you for your reply, I'll give this a go, and take my time. There is not personal data on the phone that is important, so not a tragedy if I fail. Appreciate your help.

Twinikle said:
Thank you for your reply, I'll give this a go, and take my time. There is not personal data on the phone that is important, so not a tragedy if I fail. Appreciate your help.
Click to expand...
Click to collapse
Hi
I have taken my time and got so far as number 2. I can't find the link to download TWRP backup 6.13.206.5. Where do I access #2,#3, and #4? I have never done this before, and am actually amazed I have got this far! Could you please simplify the procedure for me to complete this?

Twinikle said:
Hi
I have taken my time and got so far as number 2. I can't find the link to download TWRP backup 6.13.206.5. Where do I access #2,#3, and #4? I have never done this before, and am actually amazed I have got this far! Could you please simplify the procedure for me to complete this?
Click to expand...
Click to collapse
TWRP backup 6.13.206.5 is in Post #3 of the same thread (scroll down, third post of that thread), it says that right in the instructions for Step #2.
You don't need stock recovery (step #3). This is only to receive updates, which doesn't apply to this device anymore (updates stopped at Marshmallow) and not useful for what you are trying to so (just restore stock ROM/TWRP backup). So you can skip step #2, as well as stop at Step #9, and just reboot (and hopefully stock ROM will boot). No need to do steps 10 and on. In fact, it is detrimental in doing so, since if you need to use TWRP again, it will be gone if you flash stock recovery.

redpoint73 said:
TWRP backup 6.13.206.5 is in Post #3 of the same thread (scroll down, third post of that thread), it says that right in the instructions for Step #2.
You don't need stock recovery (step #3). This is only to receive updates, which doesn't apply to this device anymore (updates stopped at Marshmallow) and not useful for what you are trying to so (just restore stock ROM/TWRP backup). So you can skip step #2, as well as stop at Step #9, and just reboot (and hopefully stock ROM will boot). No need to do steps 10 and on. In fact, it is detrimental in doing so, since if you need to use TWRP again, it will be gone if you flash stock recovery.
Click to expand...
Click to collapse
Followed all these instructions and it said that the restore was successful. However when I reboot the phone is stuck on the white startup screen. Any further advice?

Twinikle said:
Followed all these instructions and it said that the restore was successful. However when I reboot the phone is stuck on the white startup screen. Any further advice?
Click to expand...
Click to collapse
Some things to try:
- Did you do the wipes as directed in the guide (Dalvik, cache, data, system) before the restore?
- What version of TWRP did you install? If you followed the guide correctly, it should be 2.8.7 (and older versions may not be compatible with your firmware) which is tried and true. But you can also try other versions after 2.8.7 (up to current 3.2.3-1) from here: https://dl.twrp.me/m8/
- Make sure it was the backup version 6.13.206.5 that you restored. Download and restore the backup again, to be sure the files wasn't corrupted. Make sure you restore both system and boot.img partitions.
- After restore, do the default wipe in TWRP (slightly different from what you wiped before: Dalvik, cache, data, but not system), just to be sure.

Twinikle said:
Hope someone can help. My daughter switched on her HTC One M8 after months of not using and it is showing a page with software status modified, locked and s-on. I know nothing about HTC phones. I have spent 2 days trying to get the answer, but it is beyond me. Here is information I have.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(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: O2___001
(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.
Click to expand...
Click to collapse
How do you get this information. I am a noob.
Sent from my HTC One M9 using Tapatalk

redpoint73 said:
Some things to try:
- Did you do the wipes as directed in the guide (Dalvik, cache, data, system) before the restore?
- What version of TWRP did you install? If you followed the guide correctly, it should be 2.8.7 (and older versions may not be compatible with your firmware) which is tried and true. But you can also try other versions after 2.8.7 (up to current 3.2.3-1) from here: https://dl.twrp.me/m8/
- Make sure it was the backup version 6.13.206.5 that you restored. Download and restore the backup again, to be sure the files wasn't corrupted. Make sure you restore both system and boot.img partitions.
- After restore, do the default wipe in TWRP (slightly different from what you wiped before: Dalvik, cache, data, but not system), just to be sure.
Click to expand...
Click to collapse
I was using TWRP 2.8.7 but updated to 3.2.3-1 and downloaded backup 6.13.206.5 again. I got the same result so continued to your original instructions and followed to number 12 and it worked. Thank you so much for your patience and expertise.

Thabto said:
How do you get this information. I am a noob.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
You need to use HTC fastboot and adb files and then on your pc use command prompt fastboot getvar all
Sorry but I now cannot remember where I got this information, I did a lot of searches on google.

Twinikle said:
I was using TWRP 2.8.7 but updated to 3.2.3-1 and downloaded backup 6.13.206.5 again. I got the same result so continued to your original instructions and followed to number 12 and it worked. Thank you so much for your patience and expertise.
Click to expand...
Click to collapse
You're quite welcome. Glad it worked out for you.
Not sure why it didn't work the first or second time. Maybe you missed a step, or did something slightly incorrect. Of just some glitch, that was not any fault of yours (it happens). Persistence is key, sometimes!