Develop Bugs

UNRooting

I've been trying to unroot and so far have thoroughly screwed things up. I've tried a few different things but i can't get a base unrooted ROM on the device.
i have currently
HBoot 0.79.0000
microp - 041f
radio-1.39.00.05.31
april 14 2010,15:41:34
can someone help with the proper files that i need to complete this unroot.
right now the device will only keep rebooting. i tried re-flshing my damage control 3.5 rom but its not working.
I think i need to get the device up and running before i can try any other unroot options. i can still get to the clockwork recoveryv2.0.1.3
thanks

I was able to get the device back up and running. It is still rooted. I got it back to its original root state by toastcfh.
I still can't get to non root state.
any help?

search the forums for "RUU" and go run that. it will bring you back to stock. there are tons of threads, please please search before posting.

I have tried 4 Ruu files. None work. They keep giving errors. I've read through many threads. The last change i can think of is to get the zip file from out of the ruu(s) but i dont know how to extract them. They extract as .cab files not .zip files.
Additionally
my image version is apparently 1.47.651.1
does anyone else have any suggestions?

when using the ruu.exe(s) i get to the sending signature phase and after a few seconds i get the error "Error[140]: Bootloader version error"

_sunz said:
when using the ruu.exe(s) i get to the sending signature phase and after a few seconds i get the error "Error[140]: Bootloader version error"
Click to expand...
Click to collapse
http://depositfiles.com/files/2dp2m33kp
download and flash it.

_sunz said:
I was able to get the device back up and running. It is still rooted. I got it back to its original root state by toastcfh.
I still can't get to non root state.
any help?
Click to expand...
Click to collapse
It's always going to have root. What you want is root access. If you don't have a root user, you won't have anything.

Three dot mod fail

Hi,i've downloaded the three dot mode from here:
http://forum.xda-developers.com/showpost.php?p=25063642&postcount=279
The problem is that it isn't working,phone just stucks at the logo(HTC ONE).Is that only made for 1.28?I have 1.26.Can someone please give me the 1.26?
Or else,can anybody tell me how to upgrade from 1.26 to 1.28?
PS:I have stock rom,only CWM and unlocked bootloader (from htcdev).

maybe this mod is only available for 1.28.
i think you have to wait for an OTA to 1.28, or flash a rom with this number?

Yeah,i've seen a lot of custom ROM's out there for One X but i want to stay as stock as possible and this is the only thing i hate at this phone,the three dots are realy annoying.
Yesterday i've downloaded the MILocker.The app is verry great but the three dots apear on the lockscreen and kinda spoils the whole aspect if you know what i mean.
Are there so many diferences between 1.26 and 1.28?

i found this, but idk if this helps you
http://forum.xda-developers.com/showthread.php?t=1551581

I saw that post but honestly i have no ideea what that means.This is my first Android phone and i'm kinda scared not to do anything stupid to it and brick it or something worse.And i've allready unlocked my bootloader and my CID is none...

The three dots mod is available for 1.26 but only for deodexed roms as far as I can see, if you upgrade to 1.28 you'll be able to use it on the stock odexed rom.
If you made a backup in recovery you can restore that to get out of the HTC splash screen, if you don't have a backup then run an applicable RUU to return your firmware to stock.
There are several custom roms available that don't look cosmetically different to the stock rom but will allow you to install the 3 dots mod. You could give those a go if you want, eg Android Revolution HD.

edit: removed

hopscotchjunkie said:
The very first post in the three-dot mod thread has attached links to the mod for 1.26 as well as 1.28 (you need the ones with filename beginning "126_").
Click to expand...
Click to collapse
They're only for deodexed roms, they won't work on the stock rom.

rogersnm said:
They're only for deodexed roms, they won't work on the stock rom.
Click to expand...
Click to collapse
Yeah I know, you quoted me in the seconds between me posting that and realising and removing it. Too quick off the draw.

I didn't had any problems restoring.I've made a nanodroid backup the second i've installed the CWM.Because it's my first time with an Android phone i've made a lot of backups,and daily i am making a backup in Titanium.
Well the post sayd for stock roms(1.26,1.28),but so far for me doesn't work.
Hoping an experienced guy from the forum does a three dot removal for stock roms 1.26.

jeyml said:
I didn't had any problems restoring.I've made a nanodroid backup the second i've installed the CWM.Because it's my first time with an Android phone i've made a lot of backups,and daily i am making a backup in Titanium.
Well the post sayd for stock roms(1.26,1.28),but so far for me doesn't work.
Hoping an experienced guy from the forum does a three dot removal for stock roms 1.26.
Click to expand...
Click to collapse
That odexed version is for 1.28 only. You should get an OTA which will allow you to update to 1.28 and then you'll be able to install the 3 dots mod.

Ok,sorry if i apear to be an idiot(witch i am),but what does OTA means?

It stands for "over the air", it's basically an update package you can download and install. If you go to settings and check for updates it may give you the option to update to 1.28, it depends on whether or not it's been made available for your carrier/region yet.

Oww i understand now.Yes i have a notification witch tells me i can update but i don't know if it's 1.28 and i didn't update because i'm afraid to lose my root.If i update i will have to flash the supersu again for the 1.28 i presume?

That should be the 1.28 OTA, you shouldn't lose root but if you do you can just re-root it again with the same instructions. After you install the update you should be able to install the 3 dots mod (check your version number first though).

Ok,just gave the phone to update.After i update i will make a new nanodroid backup and then i will check if i have the root,if not...well...i will have to do the whole process again.I will post soon.Thank you all for helping a noob like me.
EDIT:After download i gave it to update,phone restarted an then it gives me an error:
E:unnkwown volume for path [INTERNALSDCARD: Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.301.9-1.26.401.2_release_256505w0tk6eiq8g74y4vb.zip]
E:Can't mount (that thing that says upwards)
Installation aborted.
Positive side: I know it's 1.28 update
What do i have to do?

jeyml said:
Ok,just gave the phone to update.After i update i will make a new nanodroid backup and then i will check if i have the root,if not...well...i will have to do the whole process again.I will post soon.Thank you all for helping a noob like me.
EDIT:After download i gave it to update,phone restarted an then it gives me an error:
E:unnkwown volume for path [INTERNALSDCARD: Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.301.9-1.26.401.2_release_256505w0tk6eiq8g74y4vb.zip]
E:Can't mount (that thing that says upwards)
Installation aborted.
Positive side: I know it's 1.28 update
What do i have to do?
Click to expand...
Click to collapse
You need the stock recovery to run the OTA. Hook your phone up to your pc and boot it into fastboot mode like you did when you were rooting it. Download this file: http://www.androidrevolution.nl/ARHD/OneX/Recovery/endeavoru_recovery_signed.img and place it in the same directory as your fastboot exe then navigate to that dir in cmd prompt and enter the command:
Code:
fastboot flash recovery endeavoru_recovery_signed.img
After that try running the OTA again and it should succeed, then you can reflash CWM.

Ok,i understood.After that is this CWM good?
recovery-clockwork-touch-5.8.2.7-endeavoru.img
It's the same i've used the first time i've unlocked my bootloader.

You should flash the latest version of CWM:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.3.1-endeavoru.img
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
It has a few bug fixes and allows you to charge the device whilst it's off

Done with the endeavoru_recovery_signed.img.I am now trying to update,i will edit as i do the steps you told me.
Ok,the update has started,so far so good.
Update finished,now optimizing the applications step.After this i will flash the new CWM,hope it works.
Flashed the CWM,now waiting to power up and check up if i have the root.
I don't have root acces (((.Is this file good: CWM-SuperSU-v0.88.zip?

WIND, Canada M8, lost stock recovery, OTA update

EDIT: wrong section, sorry, please move to Help section or delete
So a mandatory OTA update notification popped up on my phone today, but I can't flash it without the stock recovery, and I can't find the right stock recovery for my phone anywhere.
It keeps bugging me every 4 hours to install it.
Is there anything I can do to get the update (maybe without stock recovery) or am I just boned?
some info:
version-main: 1.12.1500.18
cid: GLOBA001
recovery: philz_touch_6.26.6
rooted, S-OFF, HTCDev bootloader unlocked

SpaceEraser said:
EDIT: wrong section, sorry, please move to Help section or delete
So a mandatory OTA update notification popped up on my phone today, but I can't flash it without the stock recovery, and I can't find the right stock recovery for my phone anywhere.
It keeps bugging me every 4 hours to install it.
Is there anything I can do to get the update (maybe without stock recovery) or am I just boned?
some info:
version-main: 1.12.1500.18
cid: GLOBA001
recovery: philz_touch_6.26.6
rooted, S-OFF, HTCDev bootloader unlocked
Click to expand...
Click to collapse
Take a look at my Reply in this Thread.
http://forum.xda-developers.com/showthread.php?t=2732679
And read the "Questions & Answers" in the second post of this Thread.
COLLECTION of Stock backup's by Mr Hofs
Regards, Toni

Toni10 said:
Take a look at my Reply in this Thread.
http://forum.xda-developers.com/showthread.php?t=2732679
And read the "Questions & Answers" in the second post of this Thread.
COLLECTION of Stock backup's by Mr Hofs
Regards, Toni
Click to expand...
Click to collapse
I've already looked at that collection of stock ROMs, but none of them matched my phone's version-main of 1.12.1500.18. I did try 1.12.1540.17 but no luck.
Fortunately, I think I know what the problem is; the update (with the mismatched 1.12.1540.17 recovery) crashes with the message:
"/system/app/PartnerBookmarksProvider.apk" has unexpected contents.
so I looked up that APK and it doesn't even exist, probably because unlocking my bootloader got rid of it (along with a bunch of others, including the Calculator and Flashlight apps). So if I could find the apps that were removed while unlocking the phone's bootloader, I think it'll work.
I also tried removing the line that checks for PartnerBookmarksProvider.apk from the updater-script, but that changed the hash of the update zip and any attempt to install was aborted almost immediately.

SpaceEraser said:
I've already looked at that collection of stock ROMs, but none of them matched my phone's version-main of 1.12.1500.18. I did try 1.12.1540.17 but no luck.
Fortunately, I think I know what the problem is; the update (with the mismatched 1.12.1540.17 recovery) crashes with the message:
"/system/app/PartnerBookmarksProvider.apk" has unexpected contents.
so I looked up that APK and it doesn't even exist, probably because unlocking my bootloader got rid of it (along with a bunch of others, including the Calculator and Flashlight apps). So if I could find the apps that were removed while unlocking the phone's bootloader, I think it'll work.
I also tried removing the line that checks for PartnerBookmarksProvider.apk from the updater-script, but that changed the hash of the update zip and any attempt to install was aborted almost immediately.
Click to expand...
Click to collapse
Did you try another Recovery, for example 1.12.401.17?
Woud this help?
http://forum.xda-developers.com/showthread.php?t=2703759

HTC One M8s OTA not working

Hi,
I recently managed to root my HTC One M8s with TWRP recovery and everything works perfectly, except that I can't install the new OTA (1.16.401.1).
After searching I have flashed my recovery back to the stock for my version (which is 1.11.401.1) and tried applying the OTA again, but it still fails.
I downloaded the recovery from this website: ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/HTC%20Recovery/ (I can't post URLs yet).
Below is the error I receive when trying to update on stock recovery, TWRP recovery also gave the same error when I tried updating there.
(Code -1)
E:Find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.105.019
Verifying current sytem...
Package expects build fingerprint of htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/531284.2:user/release-keys or htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys;
This device has htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/53128
E:Error in @/cache/recovery/block.map
(Status 7)
From what I can see my build fingerprint is incorrect, but I have no idea how to fix it...

Seems to me it's likely that you've altered some system files while rooted and the Ota doesn't like it.
Now, I don't own an M8s...i have an M8, but I'd say the easiest route would be to flash your stock ruu again. After that the OTA should work.
It's that or figure out what system changes have been made and correct it. Xposed can mess you up, Uninstalled system apps can stop the Ota... MODS that changed system files... Etc. The Ota us looking for a stock system, then it updates it.
Good luck!

Thanks for the answer, I will see if I can try this solution tomorrow. I just have 2 questions:
What does the RUU do exactly? Should I see it as a complete stock reset of my phone?
And can I simply flash it using fastboot or is there a special method for a RUU?
My previous phone had an automated root and I always updated with OTA afterwards so I never flashed before now.

Im on the same boat. Tried to sim unlock by rooting and playing with CID but didnt work, now ive a rooted m8s and no ota. Tried to ruu but kept getting an error something like not enough space although i had 10gb free, cleared cache rebooted. Cant even factory reset. If anyone know how to unroot it and bring it back to stock that would be fantastic. Kind of want to delete the "flag" too make it "LOCKED" and "OFFICIAL" incase for warranty. Any ideas?

You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?

voidzero said:
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
Click to expand...
Click to collapse
When I got my phone I updated with OTA to version 1.11, after that I flashed TWRP recovery and rooted my phone. Now that OTA 1.16 is out I tried to update but couldn't, so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
Manual OTA flash worked on my previous phone with root which was an ASUS Padfone Infinity A80 as ASUS would release them on their own website for you.
Apparently HTC does not do this, or I am not looking in the right place.
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash original recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.

Codyksp said:
(...) so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
(..)
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash custom recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
(...)
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Click to expand...
Click to collapse
If you restore a RUU, and afterwards don't flash your recovery and boot partitions, You will see "Software status: official" in fastboot.
Now here's the trick: if you just boot a custom recovery with "fastboot boot my_recovery.img" (TWRP for example) then it will boot TWRP, but you can make the modifications to your system partition without losing "Software status: official" in fastboot.
So: If you just boot your recovery with 'fastboot boot' and don't flash anything, you can make all the modifications you want and still be able to install OTAs later, I think. I've rooted my phone, even installed XPosed, done all kinds of funky things to it but Fastboot still shows me that I'm on official software.
How does that sound?

So since there is no decent guide at all about flashing RUU for a HTC One M8s (the s makes a difference!). I have assumed that I need to have the bootloader locked first, as I unlocked it. According to all the M8 guides I have to gain S-OFF before I can lock the bootloader again. So I followed a guide to wipe with TWRP and flash a ROM called InsertCoin so that I can S-OFF my phone.
Now after going through the ROM's setup my phone is stuck in a bootloop, constantly trying to boot up. There is NO way at all for me to get it to stop, it just keeps booting the entire time. Not a single combination of buttons is working. Good thing the battery is non removable. How am I supposed to fix this? I've tried every volume up/down/power combination possible. The phone just boots to the HTC - Power by Android screen, shuts off after about 5 seconds and then repeats the same thing over and over. I can't turn it off and I can't get to the bootloader either.
What I need is a guide that tells me all the steps required to get an HTC One M8s (NOT M8!) back to 100% stock. This means, stock ROM, stock recovery, locked bootloader and S-ON. I am getting extremely frustrated by the lack of information and the amount of redicilous things I need to do just so I can root my phone and have OTA as well.
All I want is root on my phone for 1 app that I use with my car radio and I want to be able to update to the newest OTA afterwards, is that really so much to ask?
I am fine with installing a custom ROM with root and easy updates too, as long as the damn phone will boot after installing it and it's actually made for the M8s.

Deleted......

Well I finally managed to get the damn thing to the bootloader, and I've used "fastboot oem lock" to relock my bootloader. It now shows ***Software status: Modified ***, *** RELOCKED *** and ***Security Warning ***.
I will now have to go to my parents where my laptop is to be able to copy the RUU to my SD card, from what I understand it has to be named 0PKVIMG.zip and then it should automatically install.

Now the phone says it can't find the image or the image is incorrect.... It searches for, 0PKVDIAG.zip, 0PKVDIAG.nbh, 0PKVIMG.zip or 0PKVIMG.img. and it seems to find 0PKVIMG.zip and loads it but it cannot find the .img file and does absolutely nothing. Am I supposed to have both?

So it turns out that the RUU zip from http://ruu.lalleman.net/HTC_M8S%28QL_UL%29/RUU/ is actually not correct and I had to use rom.zip which was inside the folder. The phone is now running the "update" as it calls it. Fingers crossed...

Yes, possible you need to use rom.zip inside the zip, depending on the version, but I think this applies to 1.16 which I advice against using for reasons previously specified.
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
By the way, I did write an RUU restoration thread specifically for this subject. Did you not find it?

Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.

Codyksp said:
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Click to expand...
Click to collapse
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.

Mr Hofs said:
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Click to expand...
Click to collapse
So in that case I just unroot it before updating then?

Codyksp said:
So in that case I just unroot it before updating then?
Click to expand...
Click to collapse
Read my post again...... "a never rooted rom" so that means you need a stock rom before its ever been rooted. NOT an unrooted one because it leaves traces which will cause the ota to fail !
People should learn to create a nandroid backup before flashing ANY mods/superuser.zip/roms etc......etc

Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
I would say that M8 roms wouldn't be compatible, and could even mess up your device badly. Sorry!

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
Your point of view is a bit off if you ask me. Developers (in this case HTC) do not have to support custom modding of your phone. They support the device in the state you buy it !
If you want to mod it that's YOUR call not theirs. Do some homework before modding it. Getting a phone back to stock for future updates is relatively easy but many people don't read first how to as they think it's not important.
HTC has no obligation at all towards you regarding custom software !
And indeed M8 roms do NOT work on your M8s !

Updater Bug: Unable to restart to recovery

Hello,
I wanted to install the newest nightly update. But when I tap "Install" it says "Unable to restart to recovery". Ive got a few questions here:
What causes this and why doesnt the errormessage explain itself?
Can I apply the update myself somehow (Where is it located and how can I apply it)?
Greetings,
Ravior

Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.

shivadow said:
Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.
Click to expand...
Click to collapse
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?

can you boot in Recovery via adb (adb reboot recovery)

Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something

RaviorMetal said:
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?
Click to expand...
Click to collapse
If had read anything to do with installing ANY rom it will have detailed instructions on how to install it, usually it will tell you how to get to recovery too. Even if it doesn't tell you how to get to recovery it is a google search away.
Spoon feeding is a no-no. You must try to solve issues yourself before asking and refer to the forum for "obtuse" issues.
As for the detailed output of why it failed, usually you get some sort of error code or phrase as to why. If not then you have to start looking into logcat. You will notice that it failed to boot to recovery so manually doing it will resolve that, then you just follow whatever guide you were using after that step..
I understand that things can get overwhelming when flashing devices but it is all part of the learning curve and knowing how to navigate your device is essential before even considering changing anything.
Further more, I didn't insult you. I didn't intend to. It was an honest opinion because if you don't do the basics you WILL "become a cropper", you'll probably brick your device.
Back to basics is my advice before you proceed to mess with ANY device.
bigjailerman said:
Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something
Click to expand...
Click to collapse
Yup, missing the cid is supercid. No longer valid. Cid and mid must match the firmware you're trying to install.
The bigger issue is not being able to get to recovery at all... Will it go to download mode?.
Obviously you've read flippy's thread and sneakyghosts thread?
Beamed in by telepathy.

Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw

bigjailerman said:
Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw
Click to expand...
Click to collapse
Yes there is, it's done via a command in fastboot but I can't remember if you can do it with just root or if you need s-off too..
Beamed in by telepathy.

So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Aint nobody got time fo dat!. It's confusing for idiots like me.. My attention span is... Oo ice cream!..
Beamed in by telepathy.

Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
No honestly, I re read everything and t is right there, no question and it is appreciated. I was just concentrating on how to get back to a version of TWRP. Finally I was able to do that and still unlocked, S Off and have a TWRP 2.7 but every time I try to go higher I get the cannot boot recovery in the red letters. My bottom line was to install a 7.1.x rom. That is what caused all my original issue, tried to update into 7.1.1 RR Rom and everything crashed. I used a RUU you have in that thread (THANK YOU) and was able to get out of bootloop on RR bootanimation. I am running on stock 5.x, rooted as well.
Is there anyway to still move forward? Do I need to change the CID to match the firmware I choose within the device choices?
Thanks for all your earlier posts and it has become invaluable and thanks for any advice going forward.: good:

TWRP versions above 3.x require your M9 to be at least using firmware 3.x. The same applies to android 6/7 based roms. Either restore the correct CID for your SKU, flash the latest available 3.x RUU for that SKU and then install all missing updates via the software update function of the stock rom or restore the correct CID and look for a full-wipe firmware pack in Sneakyghost's firmware thread (located in the development section). Be aware that his packs don't contain a rom but that shouldn't be a problem at all if you want to install RR, anyway.