Develop Bugs

[Q] What's the right TWRP image for Verizon HTC One?

Does anyone have a link for the right TWRP image for the Verizon HTC One? Looking through the TWRP site, I see custom images for the HTC One on all the other major carriers but not for Verizon
Is just the generic one labeled [m7] the right one to use? Or is there no longer a TWRP image for this phone?

Try the twrp thread in original development...
Sent from my Ecliptic One.

brymaster5000 said:
Try the twrp thread in original development...
Sent from my Ecliptic One.
Click to expand...
Click to collapse
Thanks. Will try.
One more question. I'm using rumrunner to try and S-Off my HTC One. I'd ask this question in that thread but don't have enough posts.
I ran rumrunner and after a bunch of reboots and stuff it looked like it was working but then gave an error "temproot failed" and told me to hit enter to exit. I rebooted the phone into hboot and it still says S-On. So I tried running it again but all it does is constantly reboot the phone and repeat:
Waiting for the device
heh, just a shot glass for this one.....
........................
Click to expand...
Click to collapse
each time it reboots the phone. I let it go for 30 minutes and then waited until the phone was booted before yanking the cord.
Any ideas? Fastboot is off and USB debugging is on.

What OS version is on your phone. The method has to match...ie .10, .15 etc. If you took the 4.3 update you can't root until beaups updates rum runner
Sent from my Ecliptic One.

Managed to get it worked out. I deliberately did not update my phone so I was still on 4.2, but I was using the .15 version instead of the .10 version. Fixed that and we're all good. S-Off, rooted, TWRP, and running latest Cyanogen nightly. WOOT.

How do I remove apps for good?

Hi, first post in a long while.
I've got myself the HTC One M8 on contract with EE (Orange/T Mobile convergence here in the UK), after having it for a few weeks I've really got to the point where I want to mod it, remove apps and the like. So I went through the ballache that is the non root way of backing it up, HTCDev unlocked the bootloader and attempted to root it. Root doesn't stick it seems. I can't get S-off as I get the Whelp error. Sunshine says nope.
I've tried to extract the backups and mod them before restoring and they're either multipart tar archives that 7zip refuses to fully extract or with TWRP, the folders show up as files?!.
Reflashing to ARHD gives me a white screen with red text telling me it's internal software and shouldn't be public.
How do I gain control of my device? I'm fed up with having freaking kid mode on my power menu. I don't want Deezer on my phone.
Please, for the love of any deity that may or may not exist, please help me!

So no one knows how to get rw access on 4.4.3?

mrme01 said:
Hi, first post in a long while.
I've got myself the HTC One M8 on contract with EE (Orange/T Mobile convergence here in the UK), after having it for a few weeks I've really got to the point where I want to mod it, remove apps and the like. So I went through the ballache that is the non root way of backing it up, HTCDev unlocked the bootloader and attempted to root it. Root doesn't stick it seems. I can't get S-off as I get the Whelp error. Sunshine says nope.
I've tried to extract the backups and mod them before restoring and they're either multipart tar archives that 7zip refuses to fully extract or with TWRP, the folders show up as files?!.
Reflashing to ARHD gives me a white screen with red text telling me it's internal software and shouldn't be public.
How do I gain control of my device? I'm fed up with having freaking kid mode on my power menu. I don't want Deezer on my phone.
Please, for the love of any deity that may or may not exist, please help me!
Click to expand...
Click to collapse
mrme01 said:
So no one knows how to get rw access on 4.4.3?
Click to expand...
Click to collapse
I would try to get root working 100% first of all, as it sounds like something isnt right. I know you're not s-off but that should not stop you from unlocking your bootloader (which you appear to have done alright) and having root. Which guide did you follow to get where you are? Have you flashed SuperSU from recovery, did you check with a rootchecker app?
When did you try sunshine? Before you had made any modifications? I would have thought sunshine would have worked ok, it seems it requires a device running stock to run properly though, so I would use it before changing/flashing anything else.

gsmyth said:
I would try to get root working 100% first of all, as it sounds like something isnt right. I know you're not s-off but that should not stop you from unlocking your bootloader (which you appear to have done alright) and having root. Which guide did you follow to get where you are? Have you flashed SuperSU from recovery, did you check with a rootchecker app?
When did you try sunshine? Before you had made any modifications? I would have thought sunshine would have worked ok, it seems it requires a device running stock to run properly though, so I would use it before changing/flashing anything else.
Click to expand...
Click to collapse
Here's what I've done so far,
I downloaded the toolkit, used that once I had unlocked the bootloader, flashed a recovery (can't remember which one now), made a backup (multipart tars), flashed the root zip, tried to remove apps and realised I don't have RW access even with root, chmod in FX Explorer didn't take with an access denied. Got fed up, attempted to flash ARHD 11.1 as I used it on my old Sensation, didn't work (sat there for 20 minutes with red text telling me it's confidential), investigated to no avail how to extract the tars from the backup,tried Firewater and got several Whelps in a row (screen goes off just before the Whelp, like it wants to reboot but doesn't). Got the nope from firewater twice, reflashed the recovery to TWRP, tried to extract that (got errors on the APK directories, folders showed up as files). Got annoyed again and posted here.
I had ORD from my Sensation for a long time, almost weekly I was trying out new ROMs, but this is just deflatingly humiliating as I don't have the foggiest to get RW access. And what's worse is I don't know who I should complain to, HTC or EE for making it as watertight as a ducks bum.
Hopefuly this should shine some light on what to do next.

Can you give the outcome of :
Fastboot getvar all
And delete the serial and imei before posting the picture !

Mr Hofs said:
Can you give the outcome of :
Fastboot getvar all
And delete the serial and imei before posting the picture !
Click to expand...
Click to collapse
Is there anything I can give from the device itself? I'm at work and I don't have the right to install ADB or plug in any unknown devices into their machines.

mrme01 said:
Is there anything I can give from the device itself? I'm at work and I don't have the right to install ADB or plug in any unknown devices into their machines.
Click to expand...
Click to collapse
Getting your software numbers from the OS will do. But that's only needed now if you are on your original stock rom. Custom roms are usually based on .401 wwe versions so that could lead to wrong info !

mrme01 said:
Here's what I've done so far,
I downloaded the toolkit, used that once I had unlocked the bootloader, flashed a recovery (can't remember which one now), made a backup (multipart tars), flashed the root zip, tried to remove apps and realised I don't have RW access even with root, chmod in FX Explorer didn't take with an access denied. Got fed up, attempted to flash ARHD 11.1 as I used it on my old Sensation, didn't work (sat there for 20 minutes with red text telling me it's confidential), investigated to no avail how to extract the tars from the backup,tried Firewater and got several Whelps in a row (screen goes off just before the Whelp, like it wants to reboot but doesn't). Got the nope from firewater twice, reflashed the recovery to TWRP, tried to extract that (got errors on the APK directories, folders showed up as files). Got annoyed again and posted here.
I had ORD from my Sensation for a long time, almost weekly I was trying out new ROMs, but this is just deflatingly humiliating as I don't have the foggiest to get RW access. And what's worse is I don't know who I should complain to, HTC or EE for making it as watertight as a ducks bum.
Hopefuly this should shine some light on what to do next.
Click to expand...
Click to collapse
Very strange, I can understand firewater not working as its seems to only work on pre-4.4.3 firmware, so sunshine should really work (its the one that costs $25). Its up to the individual whether they want to go down the sunshine route or not, but it seems going fully s-off is the best way to go to make sure you don't have any problems flashing etc. I found this on the Sensation also.
I s-off'd my sensation and the process seemed ridiculously dodgy and involved hooking up to a pc to run a program, whilst using a thin piece of wire on the back of the phone. Essentially it tricked the phone into thinking it was going into a certain service mode so an exploit could be ran to gain s-off.
Sunshine s off:
http://forum.xda-developers.com/showthread.php?t=2792487

Mr Hofs said:
Getting your software numbers from the OS will do. But that's only needed now if you are on your original stock rom. Custom roms are usually based on .401 wwe versions so that could lead to wrong info !
Click to expand...
Click to collapse
Running stock.
As I can't do anything outside ot the browser here,
https://drive.google.com/folderview?id=0B-L4hmzi8YQScV9rZ0ZlcVVXTWM&usp=sharing

gsmyth said:
Very strange, I can understand firewater not working as its seems to only work on pre-4.4.3 firmware, so sunshine should really work (its the one that costs $25). Its up to the individual whether they want to go down the sunshine route or not, but it seems going fully s-off is the best way to go to make sure you don't have any problems flashing etc. I found this on the Sensation also.
I s-off'd my sensation and the process seemed ridiculously dodgy and involved hooking up to a pc to run a program, whilst using a thin piece of wire on the back of the phone. Essentially it tricked the phone into thinking it was going into a certain service mode so an exploit could be ran to gain s-off.
Sunshine s off:
http://forum.xda-developers.com/showthread.php?t=2792487
Click to expand...
Click to collapse
I never did S-off my Sensation and it did everything I wanted it to do. I had 4EXT on there with some strange flashing mode that seemed to make it work.
I've noticed dumlock on TWRP. Would that work for flashing the SU zip?

Your firmware definitely supports the latest roms. Try some custom roms. Easiest way to get it working. Maxumus HD is also a "stock" rom. Maybe that's worth a shot. And with the stock recovery it also works to get s-off via sunshine.

Mr Hofs said:
Your firmware definitely supports the latest roms. Try some custom roms. Easiest way to get it working. Maxumus HD is also a "stock" rom. Maybe that's worth a shot. And with the stock recovery it also works to get s-off via sunshine.
Click to expand...
Click to collapse
When I tried ARHD, all I got was a white screen and some red text like it was refusing to boot. What do I do if it happens? Dumlock? I always do a cache/dalvik wipe so it's not that.

When you install a custom rom you always need to perform a full wipe before installing it !

Mr Hofs said:
When you install a custom rom you always need to perform a full wipe before installing it !
Click to expand...
Click to collapse
It could be that, it's been months since I've played with ROMS as I stuck with CM on the Sensation since the release of the M8 as I knew I was going to upgrade to it.

Mr Hofs said:
When you install a custom rom you always need to perform a full wipe before installing it !
Click to expand...
Click to collapse
Nope, that didn't work. Still got the red text with ARHD 11.1 as it's the only ROM I have to hand.

I didn't say to try arhd again take another rom when you have time.

mrme01 said:
Nope, that didn't work. Still got the red text with ARHD 11.1 as it's the only ROM I have to hand.
Click to expand...
Click to collapse
Where do you get the red text? When flashing in recovery or does it flash ok but not boot up?

gsmyth said:
Where do you get the red text? When flashing in recovery or does it flash ok but not boot up?
Click to expand...
Click to collapse
I get the red text stratight after rebooting it Power and volume to do a battery disconnect. It seems to flash okay, sometimes it crashes and turns offafter exiting AROMA, other times it takes me back to TWRP. I just tried to reflash with Dumlock, no difference.

Turn off screen timeout option in the recovery. You got a pic from the bootloader and the red text

Mr Hofs said:
Turn off screen timeout option in the recovery. You got a pic from the bootloader and the red text
Click to expand...
Click to collapse
I don't have a 2nd phone to take a picture on. I doubt the screen timeout will do much as I can unlock it and when it comes back to recovery it works fine. But I'll try both of those suggestions when I get home in 5ish hours.
Thank you for your help so far, both of you. Much appreciated

HTC One M8 - Stuck at Boot Screen after SkyDragon Flash.

Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.

Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.

redpoint73 said:
Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.
Click to expand...
Click to collapse
Hello,
I've actually tried flashing another ROM "Android HD Revolution" I believe. The phone shows the HTC Screen along with some red text at the bottoms saying "this build is for developer purposes only....". The phone then stays on the HTC screen for ~3mins then reboots and continues to boot loop.

You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app

OLEO34 said:
You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Hello Thanks for the reply.
However, I am currently S-ON, I have searched ways to achieve S-OFF but they all require installing a ROM. However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.

Default-G8way said:
... However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.
Click to expand...
Click to collapse
Start with fastboot getvar all command in fastboot/bootloader, put the result here (delete serialno and imei no.) .. then we'll see whether is there any stock ROM available for your device.

Default-G8way said:
Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.
Click to expand...
Click to collapse
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.

lilbigdude1 said:
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.
Click to expand...
Click to collapse
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.

Mr Hofs said:
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=53838669

So ? Just like i said.....no need for gpe

Issue Resolved!
Hello Everyone.
The issue is resolved. Through many flashes, wipes and commands. Its done. I was able to flash the rom, let the rom sit for ~20mins, and it finally booted up into Lollipop. I now have no wifi. However, I should be able to follow the FAQ to get S-OFF and fix my wifi!. Thanks team. I really appreciate it.

Is it worth waiting for S-off?

IIRC on my m7 s off was required to be able to switch to stock GPE android. But I read somewhere google has no plans to make a play edition of the m9 so is it even worth waiting to do s-off on the m9 or just start flashing away with Roms?
Waiting because previously I didn't and wait and I remember it being a PITA to do s off if you were already rooted and flashed a rom

The s-off method will be sunshine.
It will cost $25 and will be simple... Your phone will need to be rooted I believe.
So... No. Dont wait for S-off... get your flash on.
S-off is really only needed if you wish to upgrade your firmware (recommended) without going back to stock and using the official RUU / OTA method.
After flashing custom roms, you should be able to s-off anytime when sunshine is released for the m9 without any major issues. The process should be no different on stock rooted or custom ROM.

Downloaded the sunshine app and it says the phone is compatible even though the site says up to 5.0.1 (I have 5.0.2). Seems like they got it... anyone used it yet?
Edit: nm. Found the thread that confirms s-off.

sunshine
Sunshine s off works smoothly and is so easy to use great app well worth $25

minyaen said:
Downloaded the sunshine app and it says the phone is compatible even though the site says up to 5.0.1 (I have 5.0.2). Seems like they got it... anyone used it yet?
Edit: nm. Found the thread that confirms s-off.
Click to expand...
Click to collapse
I just used it on my AT&T M9 with 5.02 and worked without a problem!

I had my Developer Edition M9 for 2 week's never rooted it I jus waited for 's-off via Sunshine and Saturday morning I rooted it and got s-off . But I'm still stock rom as I haven't felt the need to flash any others.
Sent from my HTC One M9 using Tapatalk

scoot0073 said:
I had my Developer Edition M9 for 2 week's never rooted it I jus waited for 's-off via Sunshine and Saturday morning I rooted it and got s-off . But I'm still stock rom as I haven't felt the need to flash any others.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
hi i installed twrp but now want to go back to stock. i havenr rooted i just want to go back to stock recovery and relock my bootloader for now. every time i try and fastboot the original recovery method it asks for s-off
how do i go back to stock recovery and s-off?
does sunshine allow us to turn s-off off and on and unroot?

mikey_sk said:
hi i installed twrp but now want to go back to stock. i havenr rooted i just want to go back to stock recovery and relock my bootloader for now. every time i try and fastboot the original recovery method it asks for s-off
how do i go back to stock recovery and s-off?
does sunshine allow us to turn s-off off and on and unroot?
Click to expand...
Click to collapse
Are you trying to flash recovery from hboot ? if so do it from download mode.

gffmac said:
Are you trying to flash recovery from hboot ? if so do it from download mode.
Click to expand...
Click to collapse
sorry im coming from a nexus where flashing using fastboot was easy as pie. i go into download mode and run the necessary fastboot scripts, i just get an error that s is ON etc and cannot flash the stock recovery.
hboot? am i missing something?

mikey_sk said:
sorry im coming from a nexus where flashing using fastboot was easy as pie. i go into download mode and run the necessary fastboot scripts, i just get an error that s is ON etc and cannot flash the stock recovery.
hboot? am i missing something?
Click to expand...
Click to collapse
Are you still unlocked? It should let you flash the recovery with s-on 'fastboot flash recovery recovery.img' - while in download mode.

xxquicksh0txx said:
Are you still unlocked? It should let you flash the recovery with s-on 'fastboot flash recovery recovery.img' - while in download mode.
Click to expand...
Click to collapse
yes u are correct, i must have been using a non signed or corrupt image, downloaded the developer edition recovery and that worked fine.
first time with a HTC so havent really had to deal with this layer
i think i will wait and stick to stock and keep the warranty intact for now until development becomes more mature.
just saw the M9+ feel a tad ripped off. The mediatek processor PRETTY MUCH MIRRORS THE 810!!!!! qhd screen and fingerprint scanner to boot

I am using custom ROMS with unlocked bootloader and S-ON. So what is the benefit of S-OFF ??

mikey_sk said:
yes u are correct, i must have been using a non signed or corrupt image, downloaded the developer edition recovery and that worked fine.
first time with a HTC so havent really had to deal with this layer
i think i will wait and stick to stock and keep the warranty intact for now until development becomes more mature.
just saw the M9+ feel a tad ripped off. The mediatek processor PRETTY MUCH MIRRORS THE 810!!!!! qhd screen and fingerprint scanner to boot
Click to expand...
Click to collapse
It's even changed coming from the M7/M8, they changed the way a few things work and it's thrown everyone through a little loop.
Your warranty will basically always be intact. They warn you that it *could* be voided when you unlock-- Which stays "voided" even if you go back to stock. HTC always seems to honor the warranty if it actually is due to a manufacturer defect.
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
dream_fun said:
I am using custom ROMS with unlocked bootloader and S-ON. So what is the benefit of S-OFF ??
Click to expand...
Click to collapse
You can get rid of that red text on boot-up that says it's for developmental purposes only.
You could make your device any version(carrier > WWE/Dev)
It's just a nice thing to have.

xxquicksh0txx said:
It's even changed coming from the M7/M8, they changed the way a few things work and it's thrown everyone through a little loop.
Your warranty will basically always be intact. They warn you that it *could* be voided when you unlock-- Which stays "voided" even if you go back to stock. HTC always seems to honor the warranty if it actually is due to a manufacturer defect.
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
You can get rid of that red text on boot-up that says it's for developmental purposes only.
You could make your device any version(carrier > WWE/Dev)
It's just a nice thing to have.
Click to expand...
Click to collapse
and this is my main question is all the WWE custom roms that are made are already compatible with us carriers versions of the m9 without us having to s-off and change firmware.
so whats the reason to soff and change firmware when all wwe custom roms are already compatible?

For example to be simply able writing into aboot LOCKED instead of RELOCKED.. or full transformation into another region ROM capable taking the intended OTAs.. and many other things, Bro!

jauhien said:
For example to be simply able writing into aboot LOCKED instead of RELOCKED.. or full transformation into another region ROM capable taking the intended OTAs.. and many other things, Bro!
Click to expand...
Click to collapse
I came from a nexus 5 so dealing with these different ROM variants is new to me. I have an at&t m9 and do I need to s off and change my super cid before flashing one of these Roms? Also to be able to get another region ota will that change my radios? The reason why im asking is would I loose my LTE from at&t?
Sent from my Nexus 9 using XDA Free mobile app

cables2590 said:
I came from a nexus 5 so dealing with these different ROM variants is new to me. I have an at&t m9 and do I need to s off and change my super cid before flashing one of these Roms? Also to be able to get another region ota will that change my radios? The reason why im asking is would I loose my LTE from at&t?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
You can flash any rom simply by being unlocked with a custom recovery. Most of the GSM roms are compatible with every carrier. I know there were some data issues at first(Mainly not having the correct APN's), but they all should be worked out by now.
Should note: S-off is not needed to have a custom rom. It's only needed for those users who want a little *more*

xxquicksh0txx said:
You can flash any rom simply by being unlocked with a custom recovery. Most of the GSM roms are compatible with every carrier. I know there were some data issues at first(Mainly not having the correct APN's), but they all should be worked out by now.
Should note: S-off is not needed to have a custom rom. It's only needed for those users who want a little *more*
Click to expand...
Click to collapse
So if I wanted to update the firmwares is as easy as replacing cid with 11111111 and can I update parts of the firmwares... I don't want to lose my at&t LTE
Sent from my Nexus 9 using XDA Free mobile app

mikey_sk said:
sorry im coming from a nexus where flashing using fastboot was easy as pie. i go into download mode and run the necessary fastboot scripts, i just get an error that s is ON etc and cannot flash the stock recovery.
hboot? am i missing something?
Click to expand...
Click to collapse
I got the same message when using fastboot in the WHITE bootloader screen... you need to be in the BLACK download screen and then the fastboot recovery works fine.
---------- Post added at 03:10 PM ---------- Previous post was at 03:06 PM ----------
cables2590 said:
So if I wanted to update the firmwares is as easy as replacing cid with 11111111 and can I update parts of the firmwares... I don't want to lose my at&t LTE
Click to expand...
Click to collapse
You won't lose your LTE, you will just lose their pre-installed apps and bootup-logos. Everything will work fine. SuperCID (11111111) to flash developer RUU is what you get with S-OFF, that plus custom pre-boot logo, and ability to return to true-stock without it saying "modified" or "re-locked".
Do you think anyone will ever make a free one down the road, or should I just pay the $25 now?

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.