Develop Bugs

Tampered, ReLocked, Security Warning

my bootloader reads Tampered, Relocked, Security Warning. I'm just trying to install the latest OTA from Virgin Mobile. 249 .06 MB should be a substantial update, right??? unrooted my a5_chl. flashed stock Recovery from here http://forum.xda-developers.com/devdb/project/?id=3490#downloads . I even flashed my stock TWRP Backup (unfortunately, i only backed up System and Boot). I even flashed the stock_rooted backup from here at the forum to get the data (stock apps) back. unrooting and relocking the bootloader failed again. Unlocked the bootloader again just to wipe the data furthermore. Red Triangle when installing the OTA. Were any of you Virgin Mobile Users able to update to this version? Anyone with a Pure Stock nandroid Backup (TWRP or CWM)??

SOLVED
SOLVED! An official RUU.exe was released

great
jayblaze406 said:
SOLVED! An official RUU.exe was released
Click to expand...
Click to collapse
can you please provide the link of the official RUU
as i am experiencing a similar problem

If anyone will provide the solution here. I think we're all looking for a way to go back to a5chl stock. Anyone have a method? Link the stock RUU? Is that the one provided by HTC or something else?

marth141 said:
If anyone will provide the solution here. I think we're all looking for a way to go back to a5chl stock. Anyone have a method? Link the stock RUU? Is that the one provided by HTC or something else?
Click to expand...
Click to collapse
go to http://www.htc.com/us/support/rom-downloads.html and find the Virgin Mobile Desire 816. Just follow the .exe and your good!

the_Victorian said:
go to http://www.htc.com/us/support/rom-downloads.html and find the Virgin Mobile Desire 816. Just follow the .exe and your good!
Click to expand...
Click to collapse
Thanks man. This was incredibly useful. I was about to write everything I did here to get the RUU.exe to work until I realized that FoxyDrew had written basically everything here http://forum.xda-developers.com/desire-816/general/ruu-t2952058
For the sake of redundancy, I'm going to post my steps here.
1. Install CWM recovery and download the nandroid backup.
CWM Recovery.exe for ease
https://docs.google.com/file/d/0Bwq9Di4bqEXkMndWSjNBZjViTjA/edit
This guy has a nandroid uploaded for VM HTC Desire 816.
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470
Now to go through with this. Reboot to bootloader and go to fastboot usb. Run the recovery exe and let it flash on. Then make a clockworkmod backup. Part of this is because we like to have back ups to be safe, part of this is to make the backup folder where you're putting the nandroid backup.
2. Flash the nandroid backup
To clarify, this will not flash like a standard zip file. You'll need to extract it into that Clockworkmod backup folder that we would have made when you made the backup (This will be in your SD-Card). Extract the nandroid zip folder into the clockwork backup folder. DO NOT NAME IT TO ANYTHING ELSE. Here is why... How you'll flash this is by running it as a backup. Inside of your recovery you'll go to backup/restore and restore it. If you name it anything other than what it is named when you extract it, Clockworkmod will not get the right MD5s and will fail restoring every time. This is just how an MD5 work. (If the name is different, then it's clearly a "different file" so the MD5 just doesn't match.)
3. Reboot into the system and remove SuperSU.
This step may be a little annoying. You're going to go back into the operating system and it should be the stock VM rom. However, it'll be out of date. Because of all of our rooting/flashing goodness, we just aren't able to install OTA updates (or at least I never could). So, what you're going to do now is find the SuperSU app, go to settings, and tell it to go through with clean up for a permanent unroot. Let it do it's thing. If it takes longer than a 2 or 3 minutes, reboot your phone and do it again. SuperSU should close and be removed from your phone if the uninstall went right. Now, go back to bootloader.
3. Flash stock recovery, lock, and run RUU.exe
We're getting to the final stretch. In FoxyDrew's post here http://forum.xda-developers.com/desire-816/general/ruu-t2952058 he has the stock recovery listed. Download that and flash it with fastboot. Protip for Command prompt noobs, use win+r and cmd to open a command prompt, find your fastboot folder location and copy it then in command prompt type in cd and paste in the location. This way you'll be able to do everything there. Basically you're writing "cd c:/user/fastbootlocation" so your command line will always stay in that directory.
Anyways, flash on the recovery with "fastboot flash recovery [recovery file].img" let it flash. Once that is done, reboot back to bootloader (you don't have to, but I would just to be safe.)
Once back in bootloader run the command "fastboot oem lock" to relock your device. Now staying in bootloader fastboot-usb, run the RUU.exe that you can download from here http://www.htc.com/us/support/rom-downloads.html (Find the desire 816 from virgin mobile/sprint)
Run the RUU.exe and click through the prompts. Wait for it to finish it's job and viola you'll back onto an updated stock rom without root. Your bootloader will stay say that it is "RELOCKED" however, it will not have tampered or security warning on it.

marth141 said:
Thanks man. This was incredibly useful. I was about to write everything I did here to get the RUU.exe to work until I realized that FoxyDrew had written basically everything here http://forum.xda-developers.com/desire-816/general/ruu-t2952058
For the sake of redundancy, I'm going to post my steps here.
1. Install CWM recovery and download the nandroid backup.
CWM Recovery.exe for ease
https://docs.google.com/file/d/0Bwq9Di4bqEXkMndWSjNBZjViTjA/edit
This guy has a nandroid uploaded for VM HTC Desire 816.
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470
Now to go through with this. Reboot to bootloader and go to fastboot usb. Run the recovery exe and let it flash on. Then make a clockworkmod backup. Part of this is because we like to have back ups to be safe, part of this is to make the backup folder where you're putting the nandroid backup.
2. Flash the nandroid backup
To clarify, this will not flash like a standard zip file. You'll need to extract it into that Clockworkmod backup folder that we would have made when you made the backup (This will be in your SD-Card). Extract the nandroid zip folder into the clockwork backup folder. DO NOT NAME IT TO ANYTHING ELSE. Here is why... How you'll flash this is by running it as a backup. Inside of your recovery you'll go to backup/restore and restore it. If you name it anything other than what it is named when you extract it, Clockworkmod will not get the right MD5s and will fail restoring every time. This is just how an MD5 work. (If the name is different, then it's clearly a "different file" so the MD5 just doesn't match.)
3. Reboot into the system and remove SuperSU.
This step may be a little annoying. You're going to go back into the operating system and it should be the stock VM rom. However, it'll be out of date. Because of all of our rooting/flashing goodness, we just aren't able to install OTA updates (or at least I never could). So, what you're going to do now is find the SuperSU app, go to settings, and tell it to go through with clean up for a permanent unroot. Let it do it's thing. If it takes longer than a 2 or 3 minutes, reboot your phone and do it again. SuperSU should close and be removed from your phone if the uninstall went right. Now, go back to bootloader.
3. Flash stock recovery, lock, and run RUU.exe
We're getting to the final stretch. In FoxyDrew's post here http://forum.xda-developers.com/desire-816/general/ruu-t2952058 he has the stock recovery listed. Download that and flash it with fastboot. Protip for Command prompt noobs, use win+r and cmd to open a command prompt, find your fastboot folder location and copy it then in command prompt type in cd and paste in the location. This way you'll be able to do everything there. Basically you're writing "cd c:/user/fastbootlocation" so your command line will always stay in that directory.
Anyways, flash on the recovery with "fastboot flash recovery [recovery file].img" let it flash. Once that is done, reboot back to bootloader (you don't have to, but I would just to be safe.)
Once back in bootloader run the command "fastboot oem lock" to relock your device. Now staying in bootloader fastboot-usb, run the RUU.exe that you can download from here http://www.htc.com/us/support/rom-downloads.html (Find the desire 816 from virgin mobile/sprint)
Run the RUU.exe and click through the prompts. Wait for it to finish it's job and viola you'll back onto an updated stock rom without root. Your bootloader will stay say that it is "RELOCKED" however, it will not have tampered or security warning on it.
Click to expand...
Click to collapse
:good:

[Q] Help With Unrooting HTC One M8

Hey everyone, here's the situation that I am in right now:
I rooted my phone and flashed an Insert Coin ROM but wanted to return it back to complete stock form.
I have a HTC One M8 thats currently locked to T-Mobile. The CID is T-MOB010 and the Build Number is 2.22.401.4
There is TWRP installed on this phone, version 2.8.1.0.
The problem that I am having is this: when I boot into TWRP recovery mode, I go to restore and look for the stock ROM, but it does not show up in the menu. I looked in both internal storage and SD Card storage, but it does not show up in either. I also tried moving the files manually through TWRP, but no luck.
I looked through the phones files using the File Manager App and I see the files are there, but once again I cannot see them when I use TWRP recovery mode.
Does anyone know why this is happening?

http://forum.xda-developers.com/showthread.php?t=2701376
read that all...hint 1 : your OFFICIAL build number is NOT 2.22.401 !

Not sure I follow. I checked the build number on my phone to confirm.

MW2 said:
Not sure I follow. I checked the build number on my phone to confirm.
Click to expand...
Click to collapse
That's the ROM base (software build). What you need to know is your firmware version. Boot into your bootloader (turn off phone, then hold power + vol down). What it says under OS is your firmware version.
You can also hook up to your PC/ADB in fastboot, and issue the command fastboot getvar all. What it says under version-main is your firmware.

xunholyx said:
That's the ROM base (software build). What you need to know is your firmware version. Boot into your bootloader (turn off phone, then hold power + vol down). What it says under OS is your firmware version.
You can also hook up to your PC/ADB in fastboot, and issue the command fastboot getvar all. What it says under version-main is your firmware.
Click to expand...
Click to collapse
I have done that and the OS version is not stated.

MW2 said:
I have done that and the OS version is not stated.
Click to expand...
Click to collapse
That is caused by your recovery being out of date. It`is also reported to be caused with TWRP 2.8.1.0. Update to TWRP 2.8.0.3. There is another newer version, but 0.3 seems to be the most stable.

Updated TWRP, still no OS version listed.

In order to explain fully I need to show the process I tried using.
I followed the instructions from this site: http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
I boot my phone into recovery mode and select the Restore option in TWRP. I try to find the Nandroid backup that I transferred to my phone but it does not show up. I try looking through both the internal storage and SD card but nothing shows up there either.

MW2 said:
Updated TWRP, still no OS version listed.
Click to expand...
Click to collapse
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 3.32.531.2
Just do an RUU and get back to stock, seeing as you are T-Mobile US yes? T-MOB010 is T-Mobile US...
There you'll get RUU, recoveries, radios, nand backups and OTA's (Which contains firmware already).
I don't get what the problem is?

The problem is when I boot into TWRP Recovery and go to the Restore option, the files are not showing. I checked both internal and SD Card storage but it does not show either. I am using TWRP 2.8.0.3

MW2 said:
The problem is when I boot into TWRP Recovery and go to the Restore option, the files are not showing. I checked both internal and SD Card storage but it does not show either. I am using TWRP 2.8.0.3
Click to expand...
Click to collapse
Try making a backup of just the boot to either internal/sdcard, so that TWRP can create the directory for you. Maybe you didn't unpack it into the right directory.
Make sure you have your devices "serial number" folder and not the one from the person that backed it up(If you're using a downloaded nand). When it's unpacked you have to place just the backup folder into the directory, if they kept it "default" it'll start with the date--time--release for example: 2014-12-06--05-20-22-KTU84P release-keys The highlighted area can ofcourse change depending on the version it has backed up, as will date and time(Logically). Inside that folder you'll have plenty of files like boot.emmc.win, system.ext4.win000 (etc) data.ext4.win etc etc. You need to place that folder inside the TWRP Backups folder.
Like I said, make backup of boot so that TWRP can create the directory for you, then it'll end up something like:
/storage/ext_sd/TWRP/BACKUPS/yourserialnumberfolder/2014-12-06--05-20-22-KTU84Prelease-keys/

Thanks for the advice.
I managed to fix the issue using RUU. I don't know why TWRP was acting this way, but my I'm ok now.
Thank you everyone for the help
Here is the method I used just for future references: http://www.android.gs/downgrade-t-mobile-htc-one-m8-to-official-stock-firmware-with-ruu/

[Q] Need advice on the final stages of back to stock

Ive successfully gone through every stage of converting my M9 from EE to an unbranded M9.
Im stuck on the CID... My ORANG001 wont accept the compatible CIDs for wwe 401.8.. 001 or 002, benups on SS Live chat says its an EE app.
is it safe to use super su to remove them...
Any advice there please?
Then whats next, how do i flash the ruu as theres so many threads on what to do with the ruu, sd card (ntfs or exfat) or adb flash and how should i flash it..
Please keep it simple..
Theres so much info... Its all confusing.

NightOrchid said:
[...]
Click to expand...
Click to collapse
First, it's hard to help with that little information you give. I have to assume some things so some assumptions may be wrong.
Your current state is:
Security: S-OFF? (since you already changed your CID and mentioned that you talked to beaups)
CID: ORANG001
Firmware: 1.32.401.8 or 1.40.401.8? (x.xx.401.8 is all you mentioned)
And your device doesn't boot into android and keeps rebooting if you change your CID
Well, I don't think that you converted you phone successfully to the international unbranded version since your phone doesn't accept the different CIDs.
Please read my whole answer before you start flashing since I'm describing more than one solution.
Solution using signed HTC files (inludes the stock rom):
If I were you I would convert the CID to HTC__001 and run a RUU. It's actually quite simple and afterwards your phone should boot even if you don't use your original CID. Just be aware of the fact that all your data and files are going to be deleted during this process. So backup everything that is important for you (e.g. SMS or contacts). Since you seem to be S-OFF and I don't know your current firmware version I'm going to use the 1.32.401.8 version in my instructions. It might downgrade your system but since it's a signed HTC file it won't harm your device and you can update your device using the OTA function of the stock system afterwards.
If your bootloader is unlocked you can leave it like that. There is no need to relock if you are S-OFF.
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Change your CID using
Code:
fastboot oem writecid HTC__001
in download mode.
Download this RUU.
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %; around 100 % might be better since you'll have to do some updates later).
Boot into download mode (reboot the download mode if you didn't leave it since the CID change).
Follow the instructions on the screen.
Wait some minutes.
Done.
After you followed these steps you only need to download and install the official updates via the settings menu. After that you can start flashing TWRP and SuperSu or you install a custom rom if you like.
Don't forget: 1.32.401.8 is the first officially published firmware version so your phone might get quite hot until you downloaded and installed the first update.
For being able to install later updates you either have to flash the corresponding RUU (version 1.40.401.8 if you followed the above instructions) or you need to create a backup of your untouched system:
Do not install the latest update (1.40.401.8). Only download the file.
Copy the update from /data/data/com.htc.updater/files/ to your pc.
Get the recovery from the firmware folder of that zip-file.
Format your SD-card to exfat and put it back into your phone.
Install the update.
Flash the latest TWRP version.
Boot into TWRP and mount the system as read-only. (Look at the instructions of your m9's screen.)
Create a backup on your SD-Card that contains a system image and the recovery, too.
Copy the backup to your pc and delete the "recovery.emmc.win" file. If you created md5-files you need to delete the corresponding file, too.
Copy the recovery you grabbed from the update earlier into your backup folder.
Rename the recover file to "recovery.emmc.win".
If you now want to get back to stock you simply need to copy your backup back onto your SD-card, boot into TWRP, mount the system as read-only again (mount menu) and restore the backup. TWRP will replace itself with the stock recovery then so that you can install any upcoming update. Nevertheless you need to redo this procedure every time you want to update your system.
Solution using unsigned files (you need to flash a rom afterwards):
Follow the instructions in Sneakyghosts thread.

Thanks Flippy498..
ALL SORTED )
Thanks for the clear instructions and taking the time.. Im now on unbranded WWE 1.40.401.8. When I flashed the 1.32 through download mode I flashed the same rom twice, just to make sure it got everything. Then took the 2 OTAs up to 1.40 "camera" update, updated and setup play store apps so everything is working great now, wow that was a tough flash.. as so many things can go wrong.
I alsokept s-off and unlocked.. so i can jump between roms if i want
Thanks for the patience and thanks to all who helped as Ive learned so much.. Appreciated

Flippy498 said:
First, it's hard to help with that little information you give. I have to assume some things so some assumptions may be wrong.
Your current state is:
Security: S-OFF? (since you already changed your CID and mentioned that you talked to beaups)
CID: ORANG001
Firmware: 1.32.401.8 or 1.40.401.8? (x.xx.401.8 is all you mentioned)
And your device doesn't boot into android and keeps rebooting if you change your CID
Well, I don't think that you converted you phone successfully to the international unbranded version since your phone doesn't accept the different CIDs.
Please read my whole answer before you start flashing since I'm describing more than one solution.
Solution using signed HTC files (inludes the stock rom):
If I were you I would convert the CID to HTC__001 and run a RUU. It's actually quite simple and afterwards your phone should boot even if you don't use your original CID. Just be aware of the fact that all your data and files are going to be deleted during this process. So backup everything that is important for you (e.g. SMS or contacts). Since you seem to be S-OFF and I don't know your current firmware version I'm going to use the 1.32.401.8 version in my instructions. It might downgrade your system but since it's a signed HTC file it won't harm your device and you can update your device using the OTA function of the stock system afterwards.
If your bootloader is unlocked you can leave it like that. There is no need to relock if you are S-OFF.
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Change your CID using
Code:
fastboot oem writecid HTC__001
in download mode.
Download this RUU.
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %; around 100 % might be better since you'll have to do some updates later).
Boot into download mode (reboot the download mode if you didn't leave it since the CID change).
Follow the instructions on the screen.
Wait some minutes.
Done.
After you followed these steps you only need to download and install the official updates via the settings menu. After that you can start flashing TWRP and SuperSu or you install a custom rom if you like.
Don't forget: 1.32.401.8 is the first officially published firmware version so your phone might get quite hot until you downloaded and installed the first update.
For being able to install later updates you either have to flash the corresponding RUU (version 1.40.401.8 if you followed the above instructions) or you need to create a backup of your untouched system:
Do not install the latest update (1.40.401.8). Only download the file.
Copy the update from /data/data/com.htc.updater/files/ to your pc.
Get the recovery from the firmware folder of that zip-file.
Format your SD-card to exfat and put it back into your phone.
Install the update.
Flash the latest TWRP version.
Boot into TWRP and mount the system as read-only. (Look at the instructions of your m9's screen.)
Create a backup on your SD-Card that contains a system image and the recovery, too.
Copy the backup to your pc and delete the "recovery.emmc.win" file. If you created md5-files you need to delete the corresponding file, too.
Copy the recovery you grabbed from the update earlier into your backup folder.
Rename the recover file to "recovery.emmc.win".
If you now want to get back to stock you simply need to copy your backup back onto your SD-card, boot into TWRP, mount the system as read-only again (mount menu) and restore the backup. TWRP will replace itself with the stock recovery then so that you can install any upcoming update. Nevertheless you need to redo this procedure every time you want to update your system.
Solution using unsigned files (you need to flash a rom afterwards):
Follow the instructions in Sneakyghosts thread.
Click to expand...
Click to collapse
great details. Just wanna clarify, using the SD card method, after flashing the 0PJAIMG.zip, does the recovery go back to stock if the person was on twrp before? because I noticed you mentioned "After that you can start flashing TWRP"? Just asking.
also was there a reason not to suggest supercid in this case? tia.

simonbigwave said:
great details. Just wanna clarify, using the SD card method, after flashing the 0PJAIMG.zip, does the recovery go back to stock if the person was on twrp before? because I noticed you mentioned "After that you can start flashing TWRP"? Just asking.
also was there a reason not to suggest supercid in this case? tia.
Click to expand...
Click to collapse
Yes, flashing RUUs overwrites TWRP with the stock recovery. Of course you can use the SupcerCID for the RUU but I'm not sure if you are able to install offcial updates afterwards since I always stay on my original CID. That's the reason why I suggested HTC__001 because as far as I know it is the corresponding unbranded CID to ORANG001.

Flippy498 said:
Yes, flashing RUUs overwrites TWRP with the stock recovery. Of course you can use the SupcerCID for the RUU but I'm not sure if you are able to install offcial updates afterwards since I always stay on my original CID. That's the reason why I suggested HTC__001 because as far as I know it is the corresponding unbranded CID to ORANG001.
Click to expand...
Click to collapse
I wasnt aware about corresponding cids. So how do we know what is the 'corresponding unbranded cid' for our device? (Is it just the numerals eg 001 have to match from ORANG001 to HTC_001 or how?) Tia.

There are many CID lists on the internet. Just google "HTC CID list". All CIDs with HTC__*** are unbranded ones. It's actually not necessary to use the corresponding one since all of them can be used with the x.xx.401.xx firmware versions. It's just my personal preference to change CIDs to the corresponding ones.

Reverting back to older stock firmware

I have a Zenfone 2 (ZE551ML) with the latest WW firmware (2.20.40.97) which is obviously causing trouble with my phone. I want to revert back to the older firmware version (2.20.40.90 or even 2.20.40.63).
Is something like that possible on my phone? I've tried every resource that I could find online and nothing seems to work. It's not rooted - it's as is from the shop just with the latest update. I've tried sideloading but that obviously works only when updating firmware not downgrading. I've tried downloading recovery images and using fastboot to flash them but nothing happens.
So I ask again is it possible to downgrade stock firmware and if yes are there reliable tested instructions on how to do it?

Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.

kanagawaben said:
Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.
Click to expand...
Click to collapse
Thanks for the info! However I need help with the last part. I have no problem following up to the part about sending fastboot flash commands but what exactly does "Erase your data" mean? After I send the fastboot commands I am still in the bootloader screen. Do I proceed perhaps to the recovery mode to wipe/erase the cache? I am also wondering is it enough to just put the MOFD_SDUPDATE file in the root of the SD card? And do I need an unlocked bootloader to perform all these actions?
I understand that these questions might seem a bit noobish to experienced Android hackers but my experience on that field is limited to just doing one "unofficial" upgrade of my Nexus 4 to Lollipop so I would be grateful for any help.
EDIT: It seems I managed to figure out the correct order of things however when I reboot to bootloader I get the following error.
Code:
E:file path:/sdcard/MOFD_SDUPDATE.zip
E:failed to map file
SD installation aborted.
EDIT 2: It was actually an error on my end. I had my Windows set in a way to display file extensions so I accidentally named the file MOFD_SDUPDATE instead of MOFD_SDUPDATE.zip. Renaming the file did the trick.

I had to make a separate post just to thank you kanagawaben. Thanks! You are a life saver :victory: I've managed to successfully revert my phone to stock 2.20.40.90.
The best part is it resolves an issue with the proximity sensor which was obviously introduced with 2.20.40.97 (http://forum.xda-developers.com/zenfone2/help/proximity-sensor-inconsistently-t3224700/)

Android 6.0 1/2 Update problem

Hello XDA, hello M9 users!
So, i rooted my phone back in September just to use some simple apps like Greenify, AdAway, etc. Yesterday the official Android 6.0 update arrived and I wanted to update. So I flashed the stock recovery and relocked my bootloader aaaand that was it. Everything was going ok untill the phone got in to the recovery. When it started to update the loading bar filled like 1/4. After that the red sign appeared on my screen. After that i just hard reseted my phone and everything was working ok and tried again but the same problem persisted. I started looking here on forums but i didn't find exact answeres except one. The guy sad: "The problem was solved. It took me 6 hours to manage this. All you need to do is re flash the stock backup with TWRP. ". Sadly I don't have the stock backup from my phone. And I'm thinking to reinstall TWRP recovery and flash version 1.32.401.8* from the thread called "HTC ONE M9 Stock File Collection (RUUs, Backups, etc.) - with linked Instructions" because I think that's the most stock version of this phone. So i have this question: should I do this or not? I am kinda noob, I am definetly not a pro with these things. I only know the basics and I am kindly asking for help. I will attach photos with phone info and everything that I mentioned here in the text. (sorry for my english, I'm trying my best)
If you guys find any solution I will be pleased to hear them!
Phone status:
-Rooted
-Bootloader: Relocked
-S ON
-Stock recovery (recovery version 2.10.401.1)
-SD Card capacity: 8GB only (i don't know if this helps)
-Stock 5.1 HTC Sense 7.0 (Software nr. 2.10.401.1)
-CID number: HTC__102
Thank you in advance!

Remember any changes with system such as root will cause OTA not work well.All you need to do is flash a RUU with right version.Or you can restore from TWRP with stock backup and flash stock recovery then you can get OTA.

If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.

Flippy498 said:
If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.
Click to expand...
Click to collapse
So the only thing i need to do is download "2.10.401.1.zip" RUU from your google sheet, copy it to my SD Card and enter in download mode and just wait untill it's done? Is this working with S-On?

It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.

Flippy498 said:
It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.
Click to expand...
Click to collapse
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?

strikercs said:
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?
Click to expand...
Click to collapse
Flippy498 said:
With S-ON you can use RUUs that have the same or a higher version than your phone.
Click to expand...
Click to collapse
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.

Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong?

Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong? I attached a screesnshot.

Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.

Flippy498 said:
Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.
Click to expand...
Click to collapse
I told you that I'm a noob. That's exactly what happened..

strikercs said:
I told you that I'm a noob. That's exactly what happened..
Click to expand...
Click to collapse
Thank you @Flippy498! Succesfully updated to Android 6.0!

So @Flippy498 saved my day with #3.
After getting to his really nice collection which can be found here and here I downloaded a TWRP Backup for my CID.
Remember fastboot getvar cid ?
Then I followed his nice tutorial until Step 5, but skipped 1 - 3.
Flippy498 said:
01. Format your SD card with a PC to exfat and put it back into your phone.
02. Boot to TWRP.
03. Create a backup on your external SD card. (Backing up "Boot" is more than enough. We only want TWRP to create the needed directories on your SD card.)
04. Download the correct backup for your firmware version. (It is stated in the line with "OS" at the beginning when you boot to download mode. The "firmware version" in "settings>about>software information>more" is only the base of the rom you are running.)
05. Unzip the downloaded backup.
06. Copy the unzipped backup folder to "TWRP/BACKUPS/<YourSerialnumber>/"on your SD card. Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
Click to expand...
Click to collapse
So here was my problem, I have no external sd-card in my phone and trying to copy the 4.2 GB File via "Android Transfer" brought up the error, that files largen then 4GB are not supported to copy.
So I first made sure I prepared the following steps:
Flippy498 said:
07. I recommend wiping everything except "Micro SDcard", "USB-OTG" and "SD-Ext".
08. Check the "Mount system as read-only" box in the Mount menu.
Click to expand...
Click to collapse
Now make a folder structure like in Step 6 (if you are still in TWRP, no problem use the "mkdir <foldername>" command via the advanced tools tab. (read on, I tell you where it is)
So then, instead I copied the 2GB zip file in that folder and went to advanced tools in TWRP. There I chose the "execute command" tool, went inside the folder with the serialnumber and clicked select.
Now a command line appears and I entered "unzip" and the name of the zipfile ... well that took some time ... dont tend to klick kill ... you can make 3 coffees in that time (I advise you to drink only two :silly: otherwise you get overexcited)
After that another folder with the name of the zipfile shows up. Go back and click restore - then check that folder and three X Marks will appear, showing you that these mounts will be overwritten.
Now swipe to restore and go on:
Flippy498 said:
09. Restore the backup.
10. Boot to system (ignore the warning that no OS is installed). This process may actually take a while!
11. Congrats! Your system is now stock and able to receive and install official OTAs, again.
Click to expand...
Click to collapse
and thats's it. Worked like a charm. Thanks again @Flippy498 :highfive: !!