Develop Bugs

[ROM] /ShieldsMOD/Desire/Port Status = Not Working 22.02.10

I have recently ported Modaco's Desire build to the hero i have managed to flash it successfully but when i reboot the device it freezes at the splash screen and the reboots into recovery ...
any help please
EDIT- i am now uploading my current work shouldn't take long hopefully
i will if it works keep this thread updated
I HOPE IT WORKS
Signed update.zip
http://www.mediafire.com/?myzjmwxymmw

is it possible that the recovery is flashed at ever shutdown and therefore booted at next boot? iirc this was done in the original roms to prevent people from flashing custom recovery images...
edit: btw, plan on sharing that rom? and what did you use as base, pauls desire build for the n1?

Did you remember to wipe the device?

Hope you will find an answer!
Have you really success to port Sense 2.1 to a Hero.. I i understood well, i'm very excited to see it on xda!

yeah sorry should of gave more info the base was pauls desire rom i can only determine that it could be the boot.img but not certain ill upload my attemt shortly

this might be a noobish answer, but have you tried booting with just one normal partition on the sd card?
I know in some roms when u have a partitioned/apps2sd sd card it tends to do weird stuff?

he desire rom cannot be ported to the hero as the desire is ARM7 and the hero is ARM6, the binaries are just not compatible

RaiderX303 said:
he desire rom cannot be ported to the hero as the desire is ARM7 and the hero is ARM6, the binaries are just not compatible
Click to expand...
Click to collapse
Will we have the same issue with Legend ROM?

Have you checked over in the cdma hero forum? theyre pretty hard at work on that at the moment, might find some answers over there.

afaik the legend has the same cpu, only a few mhz faster... same architecture

jshields said:
I have recently ported Modaco's Desire build to the hero i have managed to flash it successfully but when i reboot the device it freezes at the splash screen and the reboots into recovery ...
any help please
Click to expand...
Click to collapse
IMHO flashing means just extracting the image to phone. You can actually put anything in image and "successfully flash". The real success happens when the device actually boots and works ...

You should also note that the desire runs 800x480.
And the Hero does not.
I think that only is more than enough reason why a port wouldn't work.

rdgut said:
You should also note that the desire runs 800x480.
And the Hero does not.
I think that only is more than enough reason why a port wouldn't work.
Click to expand...
Click to collapse
when a build is ported it automatically changes the ratio to fit the screen so thats not the problem

jshields said:
when a build is ported it automatically changes the ratio to fit the screen so thats not the problem
Click to expand...
Click to collapse
Yes, however, the SenseUI *.PNG files aren't.
And as Sense is already rather bulky, they don't include images (launcher, widgets etc) for all resolutions. The code, text and some images do scale, but the framework isn't as forgiving.

RaiderX303 said:
he desire rom cannot be ported to the hero as the desire is ARM7 and the hero is ARM6, the binaries are just not compatible
Click to expand...
Click to collapse
What he said...

Uniqron said:
Yes, however, the SenseUI *.PNG files aren't.
And as Sense is already rather bulky, they don't include images (launcher, widgets etc) for all resolutions. The code, text and some images do scale, but the framework isn't as forgiving.
Click to expand...
Click to collapse
This is what I was referring to with the resolution.
I think we'd better just wait for the official update which should have most of these sense updates anyway.
I can wait a few more weeks

I did that, happy start on Hero. But there is a big problem. Nothing work. Scroll not work... But some reaction with buttons

[Q] Questions about rooting..

Hi all,
Apologies if this sounds like a noob question.
I've done some reading about rooting here on xda forums and have few questions. I have an HTC Desire (2.2) and am very new to the Android platform. Been a Symbian user forever and know pretty well about flashing/hacking wrt to Nokia phones..
Questions:
Say, I plan to root my device, is it mandatory to load it with custom ROM like Cyanogen, etc?? Would not loading a custom ROM only improve phone's performance, etc?
Can I ONLY root the phone and NOT install any custom ROMs? Also, what are the pros and cons of ONLY rooting and NOT installing any custom ROMs?
Also, does rooting really void warranty? There are various threads where different people have different theories? Is the warranty (if rooted) specific to a country?
EDIT: Also, would I still receive Gingerbread update (if it releases anytime soon) on my rooted Desire in the future? Or would I have to un-root it, and is un-rooting the device possible?
Cheers!

Do some more reading, find out why you want to root (not because that is what all the cool kids do:, thats not a good reason) and when you really know what you want and know what you are about to do all your questions should be answered.

unrEVOked only roots the phone and flashed a custom recovery which you can use to flash a custom ROM. You don't, however, need to flash a new ROM
Before you doing anything, though, go to Settings>About phone>Software information and make a note of the software version.
Once you've made a note, try and find the RUU matching it here:
http://shipped-roms.com/index.php?category=android&model=Bravo
If there is one, download it and keep it safe for warranty issues

TheGhost1233 said:
Do some more reading, find out why you want to root (not because that is what all the cool kids do:, thats not a good reason) and when you really know what you want and know what you are about to do all your questions should be answered.
Click to expand...
Click to collapse
Not what I expected. Oh, and yes, I don't wanna be cool whatsoever. I pretty much know the benefits of rooting and custom ROM.. Those were just few questions I wanted an expert opinion, which I wouldn't find anywhere on reading the excellent extensive how-tos.

EddyOS said:
unrEVOked only roots the phone and flashed a custom recovery which you can use to flash a custom ROM. You don't, however, need to flash a new ROM
Before you doing anything, though, go to Settings>About phone>Software information and make a note of the software version.
Once you've made a note, try and find the RUU matching it here:
http://shipped-roms.com/index.php?category=android&model=Bravo
If there is one, download it and keep it safe for warranty issues
Click to expand...
Click to collapse
Thanks mate..

Also you won't receive the gingerbread OTA (that is if it's coming soon or any time :/) You could flash the gingerbread update on a rooted phone but this will probably mess things up so it's better to first unroot (which is possible) to stock rom and then apply the OTA.
Your phone should not be rooted when you are returning it for warranty. Rooting is hacking the OS, so it's not like you have not "played" too much with the device. I've read a few post however that not all repair services check for superuser permissions or a custom rom but you shouldn't rely on that.
What you benefit from using a custom rom are things like:
Code:
[LIST]
[*]Camera is working (no 720p recording yet, dont even try it!!) [B]THANKS TO SNQ-[/B] [B] *New[/B]
[*]Base - WWE 1.32.405.6
[*]Deodexed, thanx Pyr0x64 for that [IMG]http://media.xda-developers.com/images/smilies/wink.gif[/IMG]
[*]2.6.32.15RCKernel_b46 Speed Up to 1300 Thanx Capychimp for that[B] *New[/B]
[URL="http://forum.xda-developers.com/showthread.php?t=815557"]SD read fix, thx frankoid.[/URL]
[URL="http://forum.xda-developers.com/showthread.php?t=818616"]Lzma, thx snq-.[/URL] Lzma means smaller boot.img, should help with the write boot.img issue.
Now the kernel is capable to go up to 1305MHz for real (thanks snq- for pointing out previous bug).
So [B]be cautious when overclocking[/B], my device is stable up to 1190(~1800 quadrant), over that it hangs or reboots.
[COLOR=DarkRed]Overclock with[/COLOR] [URL="http://forum.xda-developers.com/showthread.php?t=505419"]SetCpu[/URL]
[*]Default speed stock [B]254-998.4 MHz.[/B]
[*]DSP Manager[B] *New[/B]
[*]Busybox, Root, Superuser...
[*]Cyanogen A2SD script, moves both apps and dalvik to ext
[*]Automatic ZipAlign by Wes Garner, slightly adjusted by me.
[*]Showing protected apps, i hope [IMG]http://media.xda-developers.com/images/smilies/wink.gif[/IMG]
[*]Modded Power Menu Thanx again snq-
[*]Touch pad unlock, first press wake up, second press unlock [IMG]http://media.xda-developers.com/images/smilies/smile.gif[/IMG] Thanx snq- for that again
[*]Custom Semitransparent Notification area
[*]Rom Manager (can fix permissions now)[B] *New[/B]
[*]Screenstate scaling
- screen on - smartass [B] *New[/B]
- screen off - powersave
[*]ext4, tun, cif, etc... all modules are there, insmod if needed.
[*]Host file moved from system, users with s-on should be able to use AdBlock (need to be tested)[B] *New[/B]
[*]Bootanimation/downanimation and bootsound moved to sd-ext/local for easier customization[B] *New[/B]
(if you want bootsound you have to add it by your self [IMG]http://media.xda-developers.com/images/smilies/wink.gif[/IMG])
[/LIST]
The above is just a quote from the RCMixHD ROM, but as you see there are plenty of tech jargon so you should give it some extensive reading to understand them.

EddyOS said:
unrEVOked only roots the phone and flashed a custom recovery which you can use to flash a custom ROM. You don't, however, need to flash a new ROM
Before you doing anything, though, go to Settings>About phone>Software information and make a note of the software version.
Once you've made a note, try and find the RUU matching it here:
http://shipped-roms.com/index.php?category=android&model=Bravo
If there is one, download it and keep it safe for warranty issues
Click to expand...
Click to collapse
Got a question mate:
My baseband version is - 32.44.00.32U_5.09.05.30_2 and software number is 2.13.720.2
I do not find a matching RUU for the corresponding software number. Although I did locate the RUU for the baseband version..
Is that the one I'd need in future

Flash only new part of the ROM

Hi,
it's possible to flash only new/changed part of the rom?
Now im on ARHD 9.2.0 ( one x), and actual version is 9.3.1, but if i flash it i will loose all flashed mods ( battery icon, sense 4.5 camera, APM and EQS).
Thank you.

nikolasokol said:
Hi,
it's possible to flash only new/changed part of the rom?
Now im on ARHD 9.2.0 ( one x), and actual version is 9.3.1, but if i flash it i will loose all flashed mods ( battery icon, sense 4.5 camera, APM and EQS).
Thank you.
Click to expand...
Click to collapse
If you are coming from older version of a ROM it should not affect current mods. Just remember not to wipe data and everything should be ok

Awt67 said:
If you are coming from older version of a ROM it should not affect current mods. Just remember not to wipe data and everything should be ok
Click to expand...
Click to collapse
Yes it will.
You'll have to flash the mods again.

Awt67 said:
If you are coming from older version of a ROM it should not affect current mods. Just remember not to wipe data and everything should be ok
Click to expand...
Click to collapse
I have to flash all mod's again, after every rom "update". And i didn't wipe data, so everything else is ok, settings, apps, messages, wallpaper, even alarm's. but i have to flash every mod again
BenPope said:
Yes it will.
You'll have to flash the mods again.
Click to expand...
Click to collapse
I know, but I thought that maybe there is another way to update without losing installed mods.
and what about https://www.otaupdatecenter.pro/ ?

Mods are written for a certian base, if you're moving up in base then the mods will have to be re-written unless otherwise stated

EddyOS said:
Mods are written for a certian base, if you're moving up in base then the mods will have to be re-written unless otherwise stated
Click to expand...
Click to collapse
It is the same base 2.17. .
so mods should remain after flashing new rom?
but i always have to flash them after flashing new rom.

The issue is when flashing the new ROM it obviously overwrites the Mods so you'll still have to flash them after flashing the ROM. You won't have to wipe data, though

That's the reason I switched to stock again . I need the Rom which doesnt need full wipe when ever base change . Like how HTC sends OTA
Sent from my HTC One X using Tapatalk 2

EddyOS said:
The issue is when flashing the new ROM it obviously overwrites the Mods so you'll still have to flash them after flashing the ROM. You won't have to wipe data, though
Click to expand...
Click to collapse
I know, so i flash new version of rom, without wipe, then mods, but after flashing mods, their settings are the same as before on old rom
forumhookersdotcom said:
That's the reason I switched to stock again . I need the Rom which doesnt need full wipe when ever base change . Like how HTC sends OTA
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Some roms like viperX have OTA. and it's like stock OTA update, only few MB and not whole rom.

A "mod" is basically a modified framework-file that replaces the original framework-file when flashed. For instance a battery% mod is part of the file systemUI.apk . As you cannot install only parts of that file, the whole file is replaced by the mod. The other way round of course, any new rom will again flash the original version of that file, thus overwriting and deleting the mod.
That is good ofc when the new rom NEEDS another systemui.apk, because the old, modded one would bring trouble. But if you stay on the same base it means additional work.
That is unavoidable unfortunately, at least in general (there are some theming mods that avoid that, but that would work only when the only modded files are graphics, not when code is involved).
I hope that explains the problem and it's reasons a bit.

jotha said:
A "mod" is basically a modified framework-file that replaces the original framework-file when flashed. For instance a battery% mod is part of the file systemUI.apk . As you cannot install only parts of that file, the whole file is replaced by the mod. The other way round of course, any new rom will again flash the original version of that file, thus overwriting and deleting the mod.
That is good ofc when the new rom NEEDS another systemui.apk, because the old, modded one would bring trouble. But if you stay on the same base it means additional work.
That is unavoidable unfortunately, at least in general (there are some theming mods that avoid that, but that would work only when the only modded files are graphics, not when code is involved).
I hope that explains the problem and it's reasons a bit.
Click to expand...
Click to collapse
Thank you. I never thought of it that way

Do I need S-Off for this usage?

Hi everyone!
First of all, forgive me for all my noobish mistakes as I have never had a HTC branded phone.
I'm about to buy this phone for a quite decent price and use it as my main and daily driver so before paying I want to know some basic things beforehand.
My main point is to get the rom "ViperOne" working in the M9 with root as I want the best performance from stock HTC firmware and because I need their drivers to be as good as possible ( sound wise).
I have already read the entire OP on the thread rom of ViperOne and I haven't seen a word about S-on/off so I'm guessing that I will not have to mess around with that kind of security right?
So to sum up things, will I need S-Off for this?
-Custom Recovery (twrp)
-ViperOne rom with root.
-Maybe installing another kernel over ViperOne.
-Thermal (software) mod.
-Audio mods.
Thanks everyone by advance.

Just need to have an unlocked M9
S-off is for downgrade firmware, change CID/MID... (more risk to brick )
dirtyl0lharry said:
Hi everyone!
First of all, forgive me for all my noobish mistakes as I have never had a HTC branded phone.
I'm about to buy this phone for a quite decent price and use it as my main and daily driver so before paying I want to know some basic things beforehand.
My main point is to get the rom "ViperOne" working in the M9 with root as I want the best performance from stock HTC firmware and because I need their drivers to be as good as possible ( sound wise).
I have already read the entire OP on the thread rom of ViperOne and I haven't seen a word about S-on/off so I'm guessing that I will not have to mess around with that kind of security right?
So to sum up things, will I need S-Off for this?
-Custom Recovery (twrp)
-ViperOne rom with root.
-Maybe installing another kernel over ViperOne.
-Thermal (software) mod.
-Audio mods.
Thanks everyone by advance.
Click to expand...
Click to collapse

dirtyl0lharry said:
Hi everyone!
First of all, forgive me for all my noobish mistakes as I have never had a HTC branded phone.
I'm about to buy this phone for a quite decent price and use it as my main and daily driver so before paying I want to know some basic things beforehand.
My main point is to get the rom "ViperOne" working in the M9 with root as I want the best performance from stock HTC firmware and because I need their drivers to be as good as possible ( sound wise).
I have already read the entire OP on the thread rom of ViperOne and I haven't seen a word about S-on/off so I'm guessing that I will not have to mess around with that kind of security right?
So to sum up things, will I need S-Off for this?
-Custom Recovery (twrp)
-ViperOne rom with root.
-Maybe installing another kernel over ViperOne.
-Thermal (software) mod.
-Audio mods.
Thanks everyone by advance.
Click to expand...
Click to collapse
You don't need s-off but it is HIGHLY RECOMMENDED to do so if you're rooting the device and messing with roms. It gives that extra level of recovering the device should you cabbage it.
This but is a slight education into custom roms and why "I" believe you shouldn't do it on ANY device:
Custom roms/firmwares are built using "open source" code. Stock roms/firmwares are built using "proprietary" code. "proprietary" code is code that is specifically written for 'x' device by a team of software engineers using "proprietary" software and hardware specifically built for 'x' brand. For example, htc have their own stuff and samsung have theirs, so on and so forth. This makes the software "married/tailor made" to the hardware so it comes as optimised as it can possibly be while weighing in factors of carrier "bloatware". No-one wants to lose a customer because of a device that is inherently slow. No-one will buy a device that is inherently slow.
Then you have custom roms and firmware. Because proprietary code is private and not for the public domain, this "open source code" is more or less "trial and error" process to get all the features of a rom or firmware to run efficiently and effectively. This results in non optimised bad code, bugs, long processes, excess code and therefore "CAN" be slower than stock roms. Couple this with deodexed and it'll bog the device down in no time.
So as you can see, I don't really like custom roms or firmware just for the fact it is no faster or no better than the software that came with the device in the first place. It was designed specifically.
My advice is to leave the phone stock rooted and s-off if you MUST have them. Otherwise don't touch it at all and continue to get updates as they are released with no hassle!.
Beamed in by telepathy.

I need to correct some of the information that got posted previously in this thread.
First of all: There are only custom roms but no custom firmwares for HTC devices (c.f. the difference between rom and firmware).
Second: S-OFF increases the risk of a hard-brick dramatically since it removes security checks of the phone (c.f. this article, the 5th post/the first page of Sneakyghost's firmware thread and the article that I already linked above). S-ON phones will refuse to accept broken files (e.g. RUUs that got corrupted due to a bad download). A phone with S-OFF on the other hand will get flashed with such a broken file and you won't get notified with any error outputs. Another example are those NoRedText aboots which remove the read warning that appears during the boot if the bootloader got unlocked. You can only flash them with S-OFF but if the hex edits didn't get executed correctly this can actually lead to unrecoverable damages.
Don't get me wrong. I'm using a S-OFF phone, too. However, you need to be aware of the risks and that you don't need S-OFF for recovering a phone. Keeping a RUU at hand for your current firmware version (if one exists) or at least a TWRP backup of the stock rom is more than enough. Damages that can't get repaired with either a RUU or a backup can't get repaired with S-OFF, either, in most of the cases.
Third: You need to differentiate between stock rom based custom roms (e.g. ViperOne or ICE) and those custom roms that are developed from source (those are the roms that shivadow mentioned in his post - e.g. Lineage or Resurrection Remix).
Those roms that are based on the stock rom deliver the same perfomance (or maybe an almost not noticeable better/worse performance) than the stock rom does. There are no differences between the core of these roms and the stock rom. (On the other hands this means that bugs of the stock rom are present in these roms, as well.) Therefore the performance differences are minimalistic. However, you don't flash such roms due to their performance differences (in comparison with the stock rom) but due to the additional features that they provide on top of the stock rom experience.
Causes for disadvantages of the other group of custom roms already got explained by shivadow in his post. A perfect example is the bad perfomance of HTC's cameras (the hardware of the phones not the app) on CM/Lineage roms. Nevertheless, I've never seen an HTC phone being incredibly slower on a custom rom than it was on the stock rom. My One S for example is much snappier on Lineage 14.1 than it would be on its android 4.1.1 stock rom and its battery is lasting much longer (well, android 7 has way more battery optimizations than android 4.1.1 so that isn't such a surprise). The only thing that I can complain about is (as mentioned before) the picture quality of the camera.
In other words, it's not always black and white. The best advice that I can give is to test all roms that are available and to use that custom/stock rom that suits your needs best.
Fourth and last: The M9 is more than two years old. HTC normally doesn't support any phone longer than this time period. There probably won't be any more updates than the nougat updates for those SKUs that haven't received firmware 4.x, yet.
TL;DR: What got written in post #2.

I tried to generalise, thats why i mentioned custom firmwares AND roms as some devices have custom firmware, rather than custom roms. Some have both, some have none.
Absolutely right that s-off is a double edged sword that you don't really want to fall on so I highly recommend that it is best to keep the device as stock but if you must root it it's worth s-off. I've seen plenty of posts for devices being screwed regardless of s-off. Also don't you need s-off to be able to restore your system backup from twrp?.
THE only reason I rooted my phone is to block "intrusive" ads. I don't want ads on my homescreen, lockscreen or really anything but apps that are good enough to warrant being paid for their efforts. Now that there is an abundance of adblocking software that no longer requires root I have absolutely no reason to keep my phone modded. I'd flash back to stock but my luck says I'll f**k the phone beyond recognition. It'll probably burn my house down, crash my car and kill my dog too!.
Nowadays root isn't necessary if you're not a dev. Thats the point I'm trying to get across!.
Beamed in by telepathy.

shivadow said:
Also don't you need s-off to be able to restore your system backup from twrp?
Click to expand...
Click to collapse
No, you don't (and never did). It doesn't make any sense to S-OFF the phone just because you can if you don't need it for any of the purposes that are mentioned in the articles/posts that I linked in my last post. It only highers the risk of bricks due to what I wrote in my last post.
And there are other uses for custom roms/root aside from ad blocking but that would be an off-topic discussion in this thread.
Sent from my HTC One M9 using XDA Labs

@Flippy498 @shivadow thank you guys for all the links and the extra informations. I really appreciate it since there are things about HTC that I haven't seen on any other brands.
To get things clearer, since my Moto G XT1039 is getting old ( low performance and battery barely keeps up with the day) and I'm really into music and sound (spotify premium and lots of flacs) and a Fiio X7 android based mp4 is too expensive, I wanted to get a top sound-chip phone, actually, a phone with a top Digital to Analogic Converter.
Of course I do know that if I want to use all the power and features that the M9 makes for its sound, I need to be on stock firmware because of the drivers. I'm guessing that the audio behaves like the camera once using and AOSP based rom ( LOS, Slim, RRemix...) getting worse.
Thats why I want this phone, it basically is much more powerful than my Moto G SD400, it has way better camera, it has a 64bit SoC and official Nougat update and I'll end up with a great DAP on my pocket to use with Spotify.
As I said, I like to get everything as minimal as possible, I hate when the home screen is full of icons and widgets, I hate having lots of icons and indicatos on the status bar, I hate having all sensor toggled on ( gpu, nfc, bluetooth...), thats why I was looking for a stock rom that let me custom all the things to keep it as minimal as possible.
If you know any other updated, stock based rom, just let me know and link it to me as I'll disable as many things as I can to get extra battery on the phone. Yes, you can guess it, even on battery saving mode, the M9 would beat the hell out of the Moto G, so I'm giving up on everything but the sound, just to get more battery time.
I hope you can understand me now.

HTC 10 Oreo Battery --> SHOULD I ROOT?

Hello, I am new to XDA and I have an un rooted HTC 10 international unlocked model on software 3.16.401.2. My HTC used to have excellent battery before the Oreo update. I did multiple tests and checks to see what the issue could be and have ruled out rogue apps or hardware issues.
I have never rooted any of my phones before but I am desperate as the battery has tanked so badly
NOW TO THE POINT
I am looking for advice on:
1. If rooting my device and using a custom version of Oreo will actually improve battery issues. (Are there others who rooted for the reason I'm considering, if so did you actually notice an improvement?)
2. If so, what is the safest/most newbie friendly method of me doing this.
PLEASE NOTE: I am very satisfied otherwise with the standard features. I have switched between htc sense launcher and smart launcher but otherwise use the phone very conventionally. I am not opposed to different features but I essentially would like to have as close to what I have now without the battery issues.
(Sorry in advance if there are 100 similar threads I'm already very concerned I'll mess
this up and manage to brick my phone so I am just trying to get clear information in a thread that's not oversaturated and is written in a layman friendly (PLEASE ) way)
Thank you everyone!

SMSJA said:
Hello, I am new to XDA and I have an un rooted HTC 10 international unlocked model on software 3.16.401.2. My HTC used to have excellent battery before the Oreo update. I did multiple tests and checks to see what the issue could be and have ruled out rogue apps or hardware issues.
I have never rooted any of my phones before but I am desperate as the battery has tanked so badly
NOW TO THE POINT
I am looking for advice on:
1. If rooting my device and using a custom version of Oreo will actually improve battery issues. (Are there others who rooted for the reason I'm considering, if so did you actually notice an improvement?)
2. If so, what is the safest/most newbie friendly method of me doing this.
PLEASE NOTE: I am very satisfied otherwise with the standard features. I have switched between htc sense launcher and smart launcher but otherwise use the phone very conventionally. I am not opposed to different features but I essentially would like to have as close to what I have now without the battery issues.
(Sorry in advance if there are 100 similar threads I'm already very concerned I'll mess
this up and manage to brick my phone so I am just trying to get clear information in a thread that's not oversaturated and is written in a layman friendly (PLEASE ) way)
Thank you everyone!
Click to expand...
Click to collapse
1: No, routing your OS won't be the fix for your battery problems.
2: it's the way everybody had to do it, unlock the bootloader, flash TWRP with fastboot and flash a custom rom. It's all explained in the guides section.

Mr Hofs said:
1: No, routing your OS won't be the fix for your battery problems.
2: it's the way everybody had to do it, unlock the bootloader, flash TWRP with fastboot and flash a custom rom. It's all explained in the guides section.
Click to expand...
Click to collapse
Thanks for your response! I am currently doing more research now after reading your helpful comment ?. Would I still be able to use the phones default launcher (HTC sense in my case) after unlocking the bootloader and flashing a custom rom or will every part of the UI now be different?

Mr Hofs said:
1: No, routing your OS won't be the fix for your battery problems.
2: it's the way everybody had to do it, unlock the bootloader, flash TWRP with fastboot and flash a custom rom. It's all explained in the guides section.
Click to expand...
Click to collapse
What about gaining S-Off and reverting to Nougat and Nougat firmware? Seems with all the battery complaints that came along with the Oreo update, there is some validity in asking such a question.

SMSJA said:
Thanks for your response! I am currently doing more research now after reading your helpful comment ?. Would I still be able to use the phones default launcher (HTC sense in my case) after unlocking the bootloader and flashing a custom rom or will every part of the UI now be different?
Click to expand...
Click to collapse
Yes as long as you flash a sense based rom the UI will not change.
product26 said:
What about gaining S-Off and reverting to Nougat and Nougat firmware? Seems with all the battery complaints that came along with the Oreo update, there is some validity in asking such a question.
Click to expand...
Click to collapse
You can also downgrade without s-off but it's a bit trickier, there is a dedicated thread in the guides section that covered this. Have a look there for all info, there is also a video in that specific thread that shows how to do it.
https://forum.xda-developers.com/htc-10/how-to/downgrade-problems-downgrading-htc-10-t3735658/page48
But the basic question is also relevant, yes you can gain s-off and downgrade by flashing the firmware and then the ruu or a custom nougat rom.