So I recently got myself an HTC One M8 Google Play Edition.
I tried to root it and unlocked the bootloader with ADB Commands.
Everything worked fine until I tried to install a custom firmware. It kept me in a bootloop and kept going back into TWRP Recovery.
I found out afterwards that my phone was still S ON.
For some reason, I was able to install Skydragon 3.0.1 custom rom for GPE and I finally got the phone working and usable again.
I thought that it was my chance to try and get S OFF with firewater.
Again, I tried doing so with ADB Command and I got the message that my device is patched by HTC, I am out of luck.
So now I'm stuck on Skydragon 3.0.1 rom. Not to say that it's a bad thing. The rom works GREAT!
But I want to revert back into stock rom and restart anew so I can maybe try and get S off from the beginning because SkyDragon has an OTA.
Apparently it's the OTA that is preventing me completely running firewater.
Is there any way to fix this? Can I still get S OFF from where I am or is there a way to go back to factory settings before all the rooting?
I haven't found any other roms that would install on my phone.
Please help!!!!! =(
Did you try installing an old 4.4.2 gpe ruu. You should be able to run it with son.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Deezy_Le said:
So I recently got myself an HTC One M8 Google Play Edition.
I tried to root it and unlocked the bootloader with ADB Commands.
Everything worked fine until I tried to install a custom firmware. It kept me in a bootloop and kept going back into TWRP Recovery.
I found out afterwards that my phone was still S ON.
For some reason, I was able to install Skydragon 3.0.1 custom rom for GPE and I finally got the phone working and usable again.
I thought that it was my chance to try and get S OFF with firewater.
Again, I tried doing so with ADB Command and I got the message that my device is patched by HTC, I am out of luck.
So now I'm stuck on Skydragon 3.0.1 rom. Not to say that it's a bad thing. The rom works GREAT!
But I want to revert back into stock rom and restart anew so I can maybe try and get S off from the beginning because SkyDragon has an OTA.
Apparently it's the OTA that is preventing me completely running firewater.
Is there any way to fix this? Can I still get S OFF from where I am or is there a way to go back to factory settings before all the rooting?
I haven't found any other roms that would install on my phone.
Please help!!!!! =(
Click to expand...
Click to collapse
You're gonna have to use Sunshine and pay the $25 to get S-OFF, firewater won't work now it's been patched (the system, NOT the ROM btw)
Android The Greek said:
Did you try installing an old 4.4.2 gpe ruu. You should be able to run it with son.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey bud, sorry for the noob question. Whats son?
I tried running it with adb command
Fastboot flash zip name_of_ruu.zip
And it kept giving me error.
S-ON (I'm guessing the forgot the - )
EddyOS said:
You're gonna have to use Sunshine and pay the $25 to get S-OFF, firewater won't work now it's been patched (the system, NOT the ROM btw)
Click to expand...
Click to collapse
Is it normal I get an error message that sunshine isnt compatible on my device?
Deezy_Le said:
Is it normal I get an error message that sunshine isnt compatible on my device?
Click to expand...
Click to collapse
Apparently the ROM has to be as stock as possible for it to work (I didn't have to as I used Firewater a few months ago when I first got my M8)
EddyOS said:
Apparently the ROM has to be as stock as possible for it to work (I didn't have to as I used Firewater a few months ago when I first got my M8)
Click to expand...
Click to collapse
It says that I cannot run sunshine because of my kernel/rom combination. I need to flash a sense-based rom.
Problem is, when I read online, I saw that I cannot flash a sense-based rom onto an GPE because of the partition difference or something.
Thus why I wanted to get S-off
I'm on skydragon GPE v3.0.0 with SkyDragon V2.0.1 kernel by the way
Did you try a 4.4.2 ruu? It might be in the gpe conversion thread if not I can send you a Drop box link.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Android The Greek said:
Did you try a 4.4.2 ruu? It might be in the gpe conversion thread if not I can send you a Drop box link.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I could find that in the htc dev website right? But if you could still send me the link so I can see if it's the same, it would be appreciated boss.
but I thought since I'm on 4.4.4, I couldn't downgrade?
Related
I was helping out a friend to flash a custom rom , to update his device to a newer version , as a former LG optimus 3d owner i figured nothing can be more problematic , so we went on to unlock the device with easyunlocker tool , then flashed the latest twrp recovery from fastboot. We first tried Legacycarbon , it was stuck in a bootloop with htc logo without the quietly brilliant bit. Then we tried pac-man 4.2.2 bootloop again , lastly we tried cyanogenmod 10.1 again bootloop... First i thought maybe it's the recovery , i flashed the latest clockwork non-touch and flashed all these roms , still bootloop... My friend accidentally wiped the backup we made of the stock rom. Now the device is soft bricked. I've heard people talk about 4ext recovery , so i thought maybe i should give it a try but as it turns out , the only way to install it is with the play store app. As the device is soft bricked i need a fastboot image.
So my question is , what could be the problem ?
If you think the the problem is with the recovery can you export your recovery partition so i can use it through fastboot?
Sent from my Nexus 4 using XDA Premium 4 mobile app
You can flash the. .img file from fastboot, but recovery is not the problem. Try wiping all partitions (/data /cache and /system), and flashing a rom
Inviato dal mio GT-I9100
totalnoob34 said:
You can flash the. .img file from fastboot, but recovery is not the problem. Try wiping all partitions (/data /cache and /system), and flashing a rom
Inviato dal mio GT-I9100
Click to expand...
Click to collapse
Yeah , i left that out. As a nexus owner i have a habit of wiping my system , data , cache and dalvik-cache partitions. I've managed to get a recovery backup from another friend who owns the same device , and flashed it to the phone , now it's working.
Although i'm very curious as to why it gets stuck in a bootloop...
I think it may be because of the partition size difference , then the ROMs that i downloaded didn't contain partition images , still it was through teamviewer , i couldn't really extract his partition table to take a look at it , i'll do that when i get my hands on the device.
Hi! It seems to be the same problem I met since friday. My HTC DESIRE HD doesn't want to start, it goes on a bootloop at the logo cyanogenmod.. I had the CM 10.1, so I have now tested to make a new installation by replacing it with a newer version of CM 10.1 but it's always the same problem.. bootloop again and again.
Moreover I have flashed the boot.img which was in the folder off CM 10.1 but no result.. I've tried to do it with MIUANDROID rom and it seems to be the same bootlooping again..
Please can someone help me?
Thanks
sosointello said:
Hi! It seems to be the same problem I met since friday. My HTC DESIRE HD doesn't want to start, it goes on a bootloop at the logo cyanogenmod.. I had the CM 10.1, so I have now tested to make a new installation by replacing it with a newer version of CM 10.1 but it's always the same problem.. bootloop again and again.
Moreover I have flashed the boot.img which was in the folder off CM 10.1 but no result.. I've tried to do it with MIUANDROID rom and it seems to be the same bootlooping again..
Please can someone help me?
Thanks
Click to expand...
Click to collapse
Try flashing a RUU. If that is not working and you are still on a bootloop then it might be a motherboard issue.
glevitan said:
Try flashing a RUU. If that is not working and you are still on a bootloop then it might be a motherboard issue.
Click to expand...
Click to collapse
be careful as re installing RUU might not let you re rooting it ...
zinedzine said:
be careful as re installing RUU might not let you re rooting it ...
Click to expand...
Click to collapse
How come?
Sent from my Nexus 7 using xda app-developers app
zinedzine said:
be careful as re installing RUU might not let you re rooting it ...
Click to expand...
Click to collapse
He should be able to unlock with HTCDev and root, or use the AAHK2 to s-off and root. I'm not sure if OP had already unlocked the bootloader, but there's a chance that the ruu won't update it (newer/same version as included in the ruu) meaning he'd keep his BL unlock
Sent from my Desire HD using Tapatalk
from what i've read here on the forum, and if my understanding is correct, ruu are like "original" roms. files that we don't flash from recovry.
it's a différent method and in the end we obtain a stock phone with an "untouched" os like an original one.
if it is the case then you should install a ruu with android 2.3.5 on it, as if you update up to a ruu with android 2.3.7, again from what i've read, it won't be possible to root back the phone then.
i might be wrong but just thought i'll point it out to you so you can research on that.
it's possible that by now there is a way, but i havn't read or heard about it.
Justice™ said:
He should be able to unlock with HTCDev and root, or use the AAHK2 to s-off and root. I'm not sure if OP had already unlocked the bootloader, but there's a chance that the ruu won't update it (newer/same version as included in the ruu) meaning he'd keep his BL unlock
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
glevitan said:
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think I might've completely screwed up what I was trying to say or you may have misunderstood what I was saying. So I'm just going to refer back to what I was trying to explain in context of an older HTC device (Wildfire, in this case).
In some scenarios with the Wildfire, we were able to run an RUU and successfully roll back to a stock rom whilst retaining a S-OFF bootloader (Meaning the ability to use fastboot to flash a recovery and root using a su zip was possible). I think I was trying to say this may be possible/may occur with the DHD. Meaning that OP would just have to use fastboot to flash a recovery and an appropriate superuser zip to get root, and therefore any version would be rootable (even if he rolled back). However at this point I'm not sure if the DHD RUU's overwrite the hboot/bootloader. (I've never really felt like flashing one and I don't feel like getting another sim unlock code at this point)
Justice™ said:
I think I might've completely screwed up what I was trying to say or you may have misunderstood what I was saying. So I'm just going to refer back to what I was trying to explain in context of an older HTC device (Wildfire, in this case).
In some scenarios with the Wildfire, we were able to run an RUU and successfully roll back to a stock rom whilst retaining a S-OFF bootloader (Meaning the ability to use fastboot to flash a recovery and root using a su zip was possible). I think I was trying to say this may be possible/may occur with the DHD. Meaning that OP would just have to use fastboot to flash a recovery and an appropriate superuser zip to get root, and therefore any version would be rootable (even if he rolled back). However at this point I'm not sure if the DHD RUU's overwrite the hboot/bootloader. (I've never really felt like flashing one and I don't feel like getting another sim unlock code at this point)
Click to expand...
Click to collapse
No problem man, but Hboot and S-OFF are not the same. All RUU's have partitions in them including bootloader, however nand partition is not reverted to S-ON by flashing an stock rom, unless you specifically do that. There is no risk to lose the S-OFF state by flashing a RUU.
glevitan said:
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I stand corrected Monsieur :highfive:
??
i dont now .......:cyclops:
I didn't see mention of s-off in your question. If you are not s-off, you have to extract the rom's boot.IMG and fastboot flash it after rom installation.
Sent from my Nexus 5 using xda app-developers app
You can install with RUU, then u can downgrade, root, s-off it with AAHK2. So it's possible to root it
Hi I have tried to go back to stock to do ota, and now I'm s-on can't get s-off again or get the ota to install or flash, I'm stuck and in need of some.Help please
Not enough info. Did you restore stock recovery? Why can't you install OTA (what error messages, etc.)?
Did you turn it back to S-on after doing S-off? If so, you didn't need to, as s-on is not required for OTA.
What is the current state of the phone, is it bootlooping, etc.?
The error.message from htc says the phone is rooted or tampered with and.cannot perform.update, I tried recovery and.relocking, to see if i can do the ota, same.error, I tried to flash the ota by going into the recovery screen after recovery to stock, where hold volume up and.press power brings up a menu to install from device or sd card, no luck there, says invalid cid
Current state of.the phone is rooted twrp, unlocked, s-on (firewater doesn't.work anymore), Harman karman installed, supercid, phone has boot looped but supersu did a update, so far no more boot loop, kit Kat 4.4.2, software #1.55.6664
MAhtc said:
Current state of.the phone is rooted twrp, unlocked, s-on (firewater doesn't.work anymore), Harman karman installed, supercid, phone has boot looped but supersu did a update, so far no more boot loop, kit Kat 4.4.2, software #1.55.6664
Click to expand...
Click to collapse
It's a guess but H/K is a mod changing Kernel and will thus prevent OTA from succeeding as far as I know.
Sent from my HTC One_M8 using XDA Free mobile app
MAhtc said:
Hi I have tried to go back to stock to do ota, and now I'm s-on can't get s-off again or get the ota to install or flash, I'm stuck and in need of some.Help please
Click to expand...
Click to collapse
CID please
HTCNerdYoda said:
It's a guess but H/K is a mod changing Kernel and will thus prevent OTA from succeeding as far as I know.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
How can I fix that ?
MAhtc said:
How can I fix that ?
Click to expand...
Click to collapse
Perform a clean install of a TWRP Backup (of course one that fits your CID/MID, which is why @zhiarw asked for it I think) without this mod. After this reinstall stock recovery and try OTA again.
This should do the job.
Sent from my HTC One_M8 using XDA Free mobile app
zhiarw said:
CID please
Click to expand...
Click to collapse
As stated, supercid at the moment, original cid is saskt001
Go back to clean but older ROM and try Firewater again.
MAhtc said:
As stated, supercid at the moment, original cid is saskt001
Click to expand...
Click to collapse
Ok, then find backup corresponding to your FW for this CID without H/K Mod, install using recovery (e.g. TWRP), go back to stock revocery.
After this you should be abled to perform the OTA.
Thanks, I'll try to find one
MAhtc said:
Thanks, I'll try to find one
Click to expand...
Click to collapse
CID SASKT001 and BM___001 share the same software no.
So you can use 1.55.666.4 under CID BM___001 backup and recovery.
Download from : http://forum.xda-developers.com/showthread.php?t=2 701376
So is there a step by step for a clean twrp install ? Guess I didn't do that since I'm having issues
MAhtc said:
So is there a step by step for a clean twrp install ? Guess I didn't do that since I'm having issues
Click to expand...
Click to collapse
It's quite strait forward:
1) flash stock backup using TWRP
2) flash stock firmware using fastboot commands in bootloader
--> reverted to stock
3) check for OTA in settings menu
Awesome, thanks again, I'm New to this whole thing , came from having a iPhone
MAhtc said:
Awesome, thanks again, I'm New to this whole thing , came from having a iPhone
Click to expand...
Click to collapse
No problem you're welcome. Just don't forget to hit the "Thanks" if someone was of any help to you. They'll do it as well
Congrats, the One is a good choice.
Ya I'll have to try when I get home, I'm hoping it works, and then I'll have to see what benefit there is to rooting since I haven't really done anything since.doing.the Harman kardon
MAhtc said:
Ya I'll have to try when I get home, I'm hoping it works, and then I'll have to see what benefit there is to rooting since I haven't really done anything since.doing.the Harman kardon
Click to expand...
Click to collapse
if you install a room on your phone or use xposed tools there are lots of benefits of rooting
tried this, in twrp tried installing the backup, it failed, so no luck so far
Hello Folks,
I'm helping a friend to mod his m8 , he has installed 4.4.3 OTA I know I can unlock the bootloader via HTC dev then custom recovery and wakesauce to gain su acess, but can I use firewater to SOFF the phone after installing 4.4.3 OTA , I have read somewhere HTC patched stuff and firewater does not work on 4.4.3 devices?
Please advise ...
Use sunshine...firewater already outdated
Sent from my HTC One_M8 using Tapatalk
hdorius said:
Use sunshine...firewater already outdated
Click to expand...
Click to collapse
Yes go for SunShine.
muk12 said:
I know I can unlock the bootloader via HTC dev then custom recovery and wakesauce to gain su acess, but can I use firewater to SOFF the phone after installing 4.4.3 OTA , I have read somewhere HTC patched stuff and firewater does not work on 4.4.3 devices?
Click to expand...
Click to collapse
You don't need HTCDev if you use SunShine, as SunShine gains S-Off AND unlocks the bootloader. Following this way HTC don't come to know that the device has been changed. Thus you would not have any problems regarding warranty
hdorius said:
Use sunshine...firewater already outdated
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
HTCNerdYoda said:
Yes go for SunShine.
You don't need HTCDev if you use SunShine, as SunShine gains S-Off AND unlocks the bootloader. Following this way HTC don't come to know that the device has been changed. Thus you would not have any problems regarding warranty
Click to expand...
Click to collapse
Thanks for your reply mate.Sunshine is the way to go ....however I have used HTC android devices in the past and I want to know can AOSP/GPE ROMS be flashed on m8 with S ON by fastboot flash boot.img after installing ROM ZIP from the recovery ?
muk12 said:
Thanks for your reply mate.Sunshine is the way to go ....however I have used HTC android devices in the past and I want to know can AOSP/GPE ROMS be flashed on m8 with S ON by fastboot flash boot.img after installing ROM ZIP from the recovery ?
Click to expand...
Click to collapse
Yep,still the same like previous HTC phone,S-ON still can flash any custom rom and just flash boot.img after rom zip
Sent from my HTC One_M8 using Tapatalk
muk12 said:
Thanks for your reply mate.Sunshine is the way to go ....however I have used HTC android devices in the past and I want to know can AOSP/GPE ROMS be flashed on m8 with S ON by fastboot flash boot.img after installing ROM ZIP from the recovery ?
Click to expand...
Click to collapse
Yes but to flash AOSP/GPE ROMs could easily lead to problems if it is done wrong. For GPE as far as I know a conversion of the phone is needed, as the partition sizes are different. During this process the hole firmware has to be replaced by the GPE one with the black HBoot as well. So do carefully read the conversion threads if you are coming from a sense ROM!
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Yes but to flash AOSP/GPE ROMs could easily lead to problems if it is done wrong. For GPE as far as I know a conversion of the phone is needed, as the partition sizes are different. During this process the hole firmware has to be replaced by the GPE one with the black HBoot as well. So do carefully read the conversion threads if you are coming from a sense ROM!
Click to expand...
Click to collapse
The partitions are only altered if a full conversion (by RUU) is performed. GPE based custom ROMs will run fine with no conversion (no partition change or hboot change required); as will any AOSP ROMs.
Rooted my HTC m9 (unlocked the boot loader , flashed a custom twrp recovery, installed supersu through it) and I am still getting ota update. But when I try to install the update ( going from 5.1.1 to marshmallow ) the phone restarts and get into the recovery.
I tried to restore the nandroid I have made since I rooted the phone, and tried to update again, but still didn't work !
Actually the phone is working great but all the solution I tried to get back to stock , and take the ota update didn't work ( even with an RUU , which I may not have found the right one).
Below is a pic of the download mode
Any help will be apreciated
imgur. com/avkCxqW
tinypic. com/r/fe3muf/9
Nb: remove the space between "dot" and "com"
You either need to be at "official" status OR buy s-off.
Sent from my HTC One M9 using Tapatalk
shivadow said:
You either need to be at "official" status OR buy s-off.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Please what do you mean by "official" status ,and how ?
And also if I buy s-off (using sunshine app) what next ?
Why on earth are you rooting if you don't know anything about it?.
Official means "as it was from factory" the device knows that it isn't as factory.
S-off means you can flash any rom and brick your device even quicker.
Sent from my HTC One M9 using Tapatalk
Well I forgot to say that I am a beginner.
Anyway, how can I get back to official status, I mean if It's still possible.
And what if I flash a custom rom, will I be able to get ota updates ( even unofficial)
superyacine1994 said:
Well I forgot to say that I am a beginner.
Anyway, how can I get back to official status, I mean if It's still possible.
And what if I flash a custom rom, will I be able to get ota updates ( even unofficial)
Click to expand...
Click to collapse
You have to be 100% stock to take an ota. This is a security feature to prevent bricks, which can and have resulted from people trying to take otas when rooted.
There are multiple threads on how to do this. Start here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
superyacine1994 said:
Well I forgot to say that I am a beginner.
Anyway, how can I get back to official status, I mean if It's still possible.
And what if I flash a custom rom, will I be able to get ota updates ( even unofficial)
Click to expand...
Click to collapse
Official status is a pita, just go s-off. Its worth the $25 to have a working phone at the end.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Official status is a pita, just go s-off. Its worth the $25 to have a working phone at the end.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Indeed! I will !
I guess as soon as I go s-off I will be able to flash any ruu therefore be 100% stock right?
iElvis said:
You have to be 100% stock to take an ota. This is a security feature to prevent bricks, which can and have resulted from people trying to take otas when rooted.
There are multiple threads on how to do this. Start here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Another thing,
After I have unlocked the boot loader, I did a twrp-backup .
So I don't need to download another one ,right ?
So long as you have the 4gb backup of system then you're golden. You can't do another until its stock stock stock because the partition is now modded!!.
S-off will help against bricks. You must still have the official status to flash a signed official stock rom but s-off isn't counted/seen. These are ruu.EXE
Otherwise yes, any rom except signed official while rooted with s-off. You can install unsigned "offical" stock roms and flash them straight away. No messing about resetting official. These are ruu.ZIP.
Sent from my HTC One M9 using Tapatalk
shivadow said:
S-off will help against bricks.
Click to expand...
Click to collapse
This needs some nuance. Being s-off will prevent you from getting into situations where you can't boot because of some security protocol, but can't fix the problem because you can't boot, for example if you relock in bootloader with a custom recovery but don't have "Allow OEM unlock" ticked in the OS.
But being s-off also opens up many other avenues for brickage that don't exist when s-on. A hard brick can be as simple as flashing a custom splash image for the wrong phone.
shivadow said:
So long as you have the 4gb backup of system then you're golden. You can't do another until its stock stock stock because the partition is now modded!!.
S-off will help against bricks. You must still have the official status to flash a signed official stock rom but s-off isn't counted/seen. These are ruu.EXE
Otherwise yes, any rom except signed official while rooted with s-off. You can install unsigned "offical" stock roms and flash them straight away. No messing about resetting official. These are ruu.ZIP.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Got you now !
I just restored my twrp backup ( BTW it's 9.8gb not 4gb) it contains a backup of all the partitions.
Now, instead of going s-off and use ruu to get back to stock, is there another way for so ?
Hello guys, Ive just got new OTA (OTA_M8_QL_UL_M60_SENSE70_MR_HTC_Europe_2.20.401.1) for my m8s. But Iam rooted and have twrp installed, so decided to ask for someone to create a flashable zip for it, because I think Iam not only one who want to flash it. @smeejaytee @leather.face
Sent from my HTC One M8s using XDA-Developers mobile app
I can upload it to cloud if someone can make it
Sent from my HTC One M8s using XDA-Developers mobile app
jonke11 said:
Hello guys, Ive just got new OTA (OTA_M8_QL_UL_M60_SENSE70_MR_HTC_Europe_2.20.401.1) for my m8s. But Iam rooted and have twrp installed, so decided to ask for someone to create a flashable zip for it, because I think Iam not only one who want to flash it. @smeejaytee @leather.face
Sent from my HTC One M8s using XDA-Developers mobile app
Click to expand...
Click to collapse
I can make a firmware.zip for you, but you won't be able to flash one unless you are S-Off.
If you are S-Off, upload the OTA to the cloud and link me. I'll still have to find a M8s RUU to pull the firmware from for a base, but I'm pretty sure I know where to find one.
But be aware that I don't own the M8s model (just regular M8), so you will have to flash this untested and at your own risk.
xunholyx said:
I can make a firmware.zip for you, but you won't be able to flash one unless you are S-Off.
If you are S-Off, upload the OTA to the cloud and link me. I'll still have to find a M8s RUU to pull the firmware from for a base, but I'm pretty sure I know where to find one.
But be aware that I don't own the M8s model (just regular M8), so you will have to flash this untested and at your own risk.
Click to expand...
Click to collapse
Hmm, iam S-on mate, because I didn't paid for unlocking my phone
Sent from my HTC One M8s using XDA-Developers mobile app
jonke11 said:
Hmm, iam S-on mate, because I didn't paid for unlocking my phone
Sent from my HTC One M8s using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, if you are S-On, the only way to update is by official means.
You'll either have to:
1) S-Off and make or find a modified firmware.zip
2) find an RUU for the newest update, backup your stuff (RUU will wipe your phone), relock your bootloader, run the RUU, then unlock your bootloader again, reflash TWRP, etc....
3) restore a TWRP backup of the stock never rooted ROM, flash the stock recovery, and get the OTA to work that way.
xunholyx said:
Well, if you are S-On, the only way to update is by official means.
You'll either have to:
1) S-Off and make or find a modified firmware.zip
2) find an RUU for the newest update, backup your stuff (RUU will wipe your phone), relock your bootloader, run the RUU, then unlock your bootloader again, reflash TWRP, etc....
3) restore a TWRP backup of the stock never rooted ROM, flash the stock recovery, and get the OTA to work that way.
Click to expand...
Click to collapse
Hmm. So I cant flash stock recovery with s-on?
Sent from my HTC One M8s using XDA-Developers mobile app
jonke11 said:
Hmm. So I cant flash stock recovery with s-on?
Click to expand...
Click to collapse
You can flash stock recovery with s-on. I think the problem is that OTA affects some other "protected" partitions (hboot, radio) that (with s-on) can only be modified with a signed (official HTC) zip, OTA, etc. So by putting the OTA in an unsigned zip, you've violated this requirement, and will get a signature fail. S-off bypasses this requirement.
That's my guess, anyway.
Thank you guys! I will try to flash stock recovery and flash ota, because HTC made this, so I think it should work for me
Sent from my HTC One M8s using XDA-Developers mobile app
jonke11 said:
Thank you guys! I will try to flash stock recovery and flash ota, because HTC made this, so I think it should work for me
Click to expand...
Click to collapse
You need the stock, never rooted ROM (unroot doesn't work) otherwise the OTA will fail.
Not sure where you can find a stock TWRP backup for your version; if you didn't make one before rooting (and you always should).
Everything worked perfect, but like did you said, ota didn't worked
Sent from my HTC One M8s using XDA-Developers mobile app