yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Marcolo88:
Is strange that before it worked without problem with this rom.

In any case i can flash ruu with s-off? if i remember i can, but maybe i make mistake with my previous htc.

I don't have phone issued by a service provider, the phone is no brand and is from Europe (i'm from Italy).

If can help, in my old backup files of phone i have the original RUU installer dowloaded (is from 2017). I think i made before flash the custom rom in android 6 of this phone! The name of file is: RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4

Maybe can help for undestand the last correct RUU

Again thank you!
[One (M9) Android Development] OGdroidster:
Is there a nogout firmware for your device. We are running on nogout firmware
[One (M9) Android Development] Marcolo88:
I did of course the upgrade to android N. I remember that i flashed the stock rom and made alla HTC official upgrade to Android N.

So i think i have the last firmware. I need to check the last RUU
[One (M9) Android Development] OGdroidster:
OK cool. Just do ruu. Good luck.
[One (M9) Android Development] Marcolo88:
I checked that the last RUU available is what i have now:

version-main: 4.28.401.3

What i can try to do?

maybe is some hardware problem or battery?

But twrp works without problem

---------- Post added at 12:07 PM ---------- Previous post was at 12:04 PM ----------

I'll try to flash again the ruu and i hope if fix something.
[One (M9) Android Development] OGdroidster:
OK RUU it and then let me know what happens..4.28 is nogout in America but our versions of some thing are greater than yours. So you should be fine. Once you RUU it try commenting out a certain line in your update script in the custom ROM before flashing. So it flashes correctly on your device. I just read that somebody did that. But first just RUU and let me know what happens.
[One (M9) Android Development] Marcolo88:
So, i flashed RUU and now it works!!

I flashed twrp, AICP and gapps and it works

If i flash magisk it make bootloop!!!!!

I need to remove magisk (with magisk unistaller) and after flash again all with format (or it doesn't work in any case).

What version of magisk i need to install? i took the last from github of magisk and installed from twrp.

What is wrong? i all time did it.

In any case now i know the culprit!

Thank you!
[One (M9) Android Development] OGdroidster:
The latest version is 21.0 and mamager version 8.02 bootloops. Use manager before or beta 8.03. Which version of Magisk are you using?
[One (M9) Android Development] Marcolo88:
I used the last stable 20.4 from https://github.com/topjohnwu/Magisk

I need to use beta?
[One (M9) Android Development] OGdroidster:
Use 21 and see If it works. Download the uninstaller to just in case
[One (M9) Android Development] Marcolo88:
With 21.1 It works!

After, with application, i upgrade to latest canary and It stil work
[One (M9) Android Development] OGdroidster:
Cool, Everything is working:good: :laugh:
[One (M9) Android Development] penguin Lin:
I try many version of rom,

it seems only [ROM][7.1.2[OFFICIAL] LineageOS 14.1 support F2FS file system.

But I saw the wording "F2FS" in the kernel source, I don't know whether kernel or rom did not support this...

Thanks a lot!
[One (M9) Android Development] Claymore1297:
currently f2fs code in kernel in broken - that's why
[One (M9) Android Development] CyanRose:
Excellent rom is one of the best roms I've tried is very stable but it needs some improvement for more stability and you have given a new youth to my cell phone and your james dsp gives me a feeling of audiophile and sounds like a 400 usd headset

my problems are

1-the cell phone lags and does not respond when I use several apps and up to two apps because the cell phone does not respond sometimes when I open several apps in this case is the case when I listen to music and check twitter this forces me to turn off the phone

2-the speaker quality when I make a call does not answer me and hangs up alone I do not hear the calls well this forces me to use the speaker nor can I change the speaker volume is very limited in the original htc rom is I heard the sound very well and was stable

3-Always a warning appears as "advanced settings not responding".

4- the fm radio doesn't work my cell phone is htc m9 t-mobile i have installed spirit fm but only listen to the microphone

5-mobile data does not work even with free operator services e.g. freebasics by facebook I always have to turn the data off and on again but it stays on
[One (M9) Android Development] riro56:
Excellent ROM ! Any Camera MOD available for the M9 under AOSP ?
[One (M9) Android Development] Bitackk:
double tap 2 wake(dt2w) wont work most of times.any solution?
[One (M9) Android Development] Bitackk:
problem solved after the last update
[One (M9) Android Development] madmatt2024:
I just had a major problem. I've been running this ROM for months, just now when I plugged my phone in to charge I clicked the power button to view the screen and it was stuck in HTC dot view mode. I haven't put it near any magnets nor do I own that case. The only thing that worked to bring it out of dot mode was to hold power and volume up. After that, it refuses to boot unto android but I can get into recovery mode. I tried clearing cashes and data but it still won't boot. Now its almost 1AM, I have work in the morning, and I'm stuck flashing my phone. To say I'm pissed off right now would be an understatement. Has anyone had this happen? I'm pretty sure it was on the 04/02/2021 weekly when this happened because I forgot to update it last week.
[One (M9) Android Development] Claymore1297:
I can't imagine, that triggering the Dot view can cause the behaviour, you describe here. And I also don't think any never versions of the ROM caused this (on Q we have more or less zero code changes anymore, besides the ASB's). A log would be helpful in any case. Does it boot directly into recovery or whats the default behaviour on normal startup? But as you already wiped data, I would recommend flash RuU and then ROM+gapps.
[One (M9) Android Development] madmatt2024:
I have no idea what triggered this. That night I checked a few discord notifications an hour or so before this happened and it was functioning normally then. I only noticed the issue when I plugged it in to charge and do one final notification check before I went to bed, saw the dot view screen and after not being able to get out of it I decided to hold down the power button to force a reboot, that didn't work. At the advice of Google I tried holding power + vol up while holding the phone under a lamp. That worked and it booted into the boot loader. I selected "restart" and every time it would go back to the boot loader. Then from the boot loader I selected "recovery" and selected "restart" in TWRP. After doing that it would get to the white HTC screen with the red warning message, go black after probably 15 sec, and come right back to it (boot loop). Then I got back into TWRP, cleared cash and delvik, no change. Went back in an cleared cash, delvik, and data (factory reset), no change. Then I tried flashing the latest weekly over the top of it, that got it to boot but wifi was broken and after 2 boot cycles it was looping again. Went back into TWRP, cleared cash, delvik, and data again, and flashed the latest weekly + Gapps and that gave me a functioning phone, minus the default launcher that the ROM comes with and my Magisk install. If there is still a way to get the log after all of that I will try to get it for you. I did click "save log" in TWRP before flashing but I think that might just be the TWRP log. I would have dug into it a lot more at the time if I didn't need to get to bed and have a function phone in the morning.
[One (M9) Android Development] madmatt2024:
Whelp, unless anybody has any ideas it looks like simply rebooting the phone deletes all logs. I absolutely HATE Android for stuff like this, it makes trying to diagnose anything impossible for a person with a life. Windows at least saves something if it bluescreens, Android deletes it, how intelligent of Google...

Sorry, I just had to get this off my chest.
[One (M9) Android Development] Sohot2000:
This rom still supports MHL for M9?
[One (M9) Android Development] madmatt2024:
I reinstalled the ROM again, this time the correct way. I wiped data, system, cash, and delvik, flashed ROM + GAPPS, then wiped cash + delvik again. It's running fine however now Android Auto doesn't work. When you first install it, it gives the error: "Something went wrong. Something went wrong" I tried installing an older version of of it that I downloaded from APKPure and this time got an "Android Auto requires one or more Google Play services that are not currently available. Please contact the developer for assistance." when starting it. Clearing the cash and data for Google Play Services gets rid of both of these errors and allows the app to launch. It goes through its usual first time setup and then stays on this screen until I hit back:

Usually when I get in my car and bluetooth connects I get a notification that Android Auto is available on my phone, this no longer happens. When I actually connect my phone to the USB and activate Android Auto on my headunit I get this error on my phone: "Android Auto: No installed apps work with this usb accessory". If it matters, the head unit is one of the new Joying UIS7862 based head units. I know these Chinese Android units can be sketchy but everything worked fine before I had to reinstall the ROM on my phone. In the first log I restarted my phone, connected it to my pc and did an adb tcpip 5555, went out to my car, turned the key on, allowed bluetooth to connect, plugged in the phone, started the connection on the head unit, got the aforementioned error, then started the Android Auto app on my phone. Then I closed the app, unplugged my phone, turned off the car, went inside, and saved the log. After saving the log I uninstalled the Android Auto app.

In the second log I restarted the phone, did adb tcpip 5555 once again, installed the Android Auto app from the playstore, and opened it. It gave the "Something went wrong. Something went wrong" error. I hit OK, the app closed, I saved the log.

Edit: I guess the forum won't let you upload .txt files so I hosted them elsewhere.

logcat.txt

drive.google.com

logcat2.txt

drive.google.com
[One (M9) Android Development] platinumthis:
What for gapps u used ?
[One (M9) Android Development] madmatt2024:
Open GApps mini 20210213, same as I used with my initial install only the latest version. Yes, I used the Android 10 ARM64 version. I also noticed that hotspot doesn't work now too. I can activate it and other devices can see it but either they can't connect to it or can connect but can't get internet through it.
[One (M9) Android Development] platinumthis:
Did you tryed a larger version of gapps ?
[One (M9) Android Development] madmatt2024:
No, I shouldn't need to. It worked before on that size of GApps so that most likely isn't the issue unless you see something in the logs to suggest otherwise.
[One (M9) Android Development] madmatt2024:
Just wiped and reflashed, used "stock" level GApps this time, no change. Android Auto and Wi-Fi hotspot still broken.

:edit: Hotspot was broken because I forgot to reset my APN... (bangs head against wall).
[One (M9) Android Development] zendilar:
I am using the rom for several months now on my htc M9 and it looks good. but there is one problem with the bluetooth audio that it is very important and it needs to be solved.

I already searched the thread but didn't find anything.

The first thing is that when the multimedia sound is enabled on bluetooth headset all notifications are going there which means that you have to have it on your ear all the time or else you miss them.

The second and more important is that the volume level on regular phone calls is very low even if is set to maximum.

the problem is only on phone calls - in skype, whatsapp or any other app the volume is ok.

If there is a solution please point me to the right direction.

thanks in advance.
[One (M9) Android Development] madmatt2024:
After sitting overnight the "Something went wrong. Something went wrong" error is gone and Android Auto now opens on the phone. It still doesn't connect with the head unit and gives the same "Android Auto: No installed apps work with this usb accessory" error. This log is with the phone already connected to the head unit via USB and Bluetooth and me pushing the button on the head unit that starts the Android auto connection, resulting in the "No installed apps" error on the phone. I can't really find much info on this problem.

logcat_02-21-2021_13-21-41.txt

drive.google.com
[One (M9) Android Development] madmatt2024:
Anybody have any clues about my Android Auto issue? Claymore1297 maybe?
[One (M9) Android Development] platinumthis:
You tried older Versions of Android auto ?

Maybe this will fix
[One (M9) Android Development] madmatt2024:
Tried it about 10 posts back, it didn't fix it. Tried it again today with an even older version, still didn't fix it, it actually made it worse. Now its stuck at this screen again

The newest version actually gets to the menu when you launch the app but it still won't connect to the car.
[One (M9) Android Development] madmatt2024:
Tried reinstalling the ROM again, this time wiping everything and installing "stock" Gapps, still no go. Android Auto is integrated into the ROM at this point and is still broken. Still no advice or help from the developer.
[One (M9) Android Development] Claymore1297:
can you try in permissive SELinux state? DOn't see much related in logs
[One (M9) Android Development] madmatt2024:
I tried wiping and installing the 04/02/2021 weekly I was running when everything worked, still no go. Here is the log in permissive SELinux state. Bluetooth was connected when I started recording, I plugged the USB into the head unit, waited a few sec, hit the connect button on the head unit, then let it sit for a few sec. before stopping the log.

logcat_03-07-2021_15-18-02.txt

drive.google.com
[One (M9) Android Development] madmatt2024:
So... I decided to start fresh and see if it fixed the issue. I RRUed the phone back to 100% stock, installed TWRP, and flashed the ROM as directed. No change, Android auto still has the same issue. Also, before doing all of this I tried to make a Google Drive backup and discovered that it also no longer works, neither does going into adb and doing bgmr backup --all, it gives a transport error. Logs indicate a token error. Issue is still there after RRU and reflash. The odd part is that I managed to manually initiate a backup on Feb 28 but now for some reason its broken. I tried some the stuff in this thread and none of it worked. https://xdaforums.com/t/forcing-pixel-2-xl-backup.3691071/page-6

I think I either need to try a different ROM, live with stock Android, or give up on this phone and buy a different one. I just don't understand how, after the HTC dot view incident, these issues can persist on this ROM even after an RRU and installing everything from scratch, unless there is some odd hardware issue.

Edit: I ended up flashing LineageOS 17.1 and now backup is working correctly, Android auto still isn't working though. I think I'm going to continue using that rom because while I can live without Android Auto, not being able to backup my device is a HUGE deal and I won't live without that ability.
[One (M9) Android Development] darenceang:
Hi.

Im currently using

AICP r16.1-Weekly

NikGapps Core Arm64 20210607

When I try to install something from play store, it gives me the error not enough disk space and ask me to free up space. Anyone encountered this issue? Storage settings shows more than enough space though.

Thanks in advance!

And thanks for bringing back my m9 to life. ( again )

Edit: stupid me. Rewipe and reinstall. With nikgaps 20210130 ver and play store is working. Thanks!
[One (M9) Android Development] phaelkyn:
Kudos to the AICP devs!

I followed the instructions and booted into a current Android experience. My device was rooted a long time ago and already had TWRP recovery. Updated TWRP first and flashed from a clean SD card using TWRP.

The current weekly actually turned out to be Android 11 and its like my M9 is now a Pixel. Note that I had to find a different version of Gapps than what is linked in the OP.

Only issue I am experiencing is the Clock app fails to load, which could be a related to Gapps? 🤷‍♂️

Clock Version: 6.4 (361440548) (64001698)
[One (M9) Android Development] Cuonghmm:
Update, please
[One (M9) Android Development] blksith0:
Anyone having issues getting the download on the website to work?
[One (M9) Android Development] Claymore1297:
Well downloadpage has Android 11 builds ;-)
[One (M9) Android Development] blksith0:
Hmm.

Well clicking on the link for the M9 just displays a loading bar at the bottom of the screen with no change.

Nevermind - it was the adblocker. Rom works well.
[One (M9) Android Development] victorxstc:
Can I use this for my HTC One M9 PLUS (M9+)?
[One (M9) Android Development] Areck83:
Incredible ROM. It worked fine on HTC One M9 0PJA11000 Dev Edition (himaulatt). The only issue that I've found is the battery drain :c
[One (M9) Android Development] phaelkyn:
Are there any specific settings to ensure that VZW service works?

Issue is I am no longer able to make or receive phone calls. Sms and mms also fail to send or receive. Data works as it should.

Other custom ROM users have reported the same behavior. https://xdaforums.com/t/verizon-network-issues-on-aosp-roms.4013557/
[One (M9) Android Development] blksith0:
I had v16.1 installed and it was better, stable, but of course that version has vanished from the cloud, so now I had to grab v17.1.

I flashed magick and one module, acc.

The phone can't stay booted for long, constant system crashes/shutdowns.

Good.
[One (M9) Android Development] Marko Indaco:
Try to look if you find the old rom inside the official Telegram channel.
[One (M9) Android Development] NoChill:
Damn, good work!

You've patching out every single major bug and so fast :)

I have a weird issue, when restarting my phone I wont automatically get carrier signal. I have to dial an emergency number and cut the call after which my mobile signal and data will work fine
[One (M9) Android Development] kunalxda:
How to get root(magisk) access in this rom
[One (M9) Android Development] Kenneth_1989:
As far as i know there´s no official support from magisk yet.

Greetings.
[One (M9) Android Development] The_Walking_Playground:
Hi,

You can flash the latest Canary build of Magisk for root. It works fine. It was confirmed working here. It might be working on the Beta channel too, depending on when the Beta was pushed.

TWP
[One (M9) Android Development] mehdifirefox:
Thank you very much for your efforts...

I have a ViperOneM9 right now

Please tell your friends their experience

Is everything this great rom?
[One (M9) Android Development] shadowalker2014:
The ROM super smooth with no major issue, and is good to go for daily driver
[One (M9) Android Development] NoChill:
Anybody know of a solution to this?

Thanks
[One (M9) Android Development] tiratored:
Hello to all! I want to say that this firmware works perfectly in terms of energy saving. There were no problems in daily use. All the basic and necessary functions are in place. Compared to AICP 14.0, the sound is better. And in general, everything is somehow better and more convenient.
[One (M9) Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-JamesDSP

-minor fixes

AICP features added:

-DT2S

-DT2S on lockscreen

-Screenrecord fixed

Note: you have still to reflash GAPPS and regrant permissions. As soon as this issue is fixed, we will provide unofficial OTA's :)

Enjoy!
[One (M9) Android Development] kunalxda:
How can I flash latest magisk, getting error unsupported/unknown image format
[One (M9) Android Development] The_Walking_Playground:
Hi,

You flash the zip in TWRP. You can't use Magisk Manager to flash it as you're not rooted.

TWP
[One (M9) Android Development] kunalxda:
Tried flashing magisk through TWRP but same error as in magisk manager.
[One (M9) Android Development] The_Walking_Playground:
Hi,

Are you using the correct TWRP from the OP? Are you using the Canary channel for Magisk? Both of those things are required.

TWP
[One (M9) Android Development] kunalxda:
Using TWRP version-3.3.1_CPTB

and magisk version-19.5-578a50b4

As you can see in attachment, Still no luck of getting root
[One (M9) Android Development] ayoobelmasry:
What is DT2S?
[One (M9) Android Development] k4y0z:
DoubleTap2Sleep
[One (M9) Android Development] The_Walking_Playground:
Hi,

Can you pull the recovery log of the flash of Magisk in TWRP?

TWP
[One (M9) Android Development] Biggie_still:
The fact that I can't use pixel launcher on this rom is really driving me nuts..and I think I will just stick with lineage 16
[One (M9) Android Development] kunalxda:
TWRP logs in attachment
[One (M9) Android Development] Claymore1297:
Your Magisk tries to mount /system - which doesn't exist anymore - it is /system_root now due SAR.

So it seems it is no SAR compatible..

************************

* Magisk v19.5-578a50b4 Installer

************************

- Mounting system

Mount is denied because the NTFS volume is already exclusively opened.

The volume may be already mounted, or another software may use it which

could be identified for example by the help of the 'fuser' command.

mount: mounting /dev/block/mmcblk0p66 on /system failed: Device or resource busy

! Cannot mount /system

- Unmounting partitions
[One (M9) Android Development] The_Walking_Playground:
Hi,

I'm really not sure why your installation isn't working. It's working fine for me and I haven't seen anyone else with an issue. Maybe you can try wiping system, cache & data, reflashing the ROM, then GApps, and then reboot recovery and flash the latest Magisk Canary? That's what I did and it worked fine.

TWP
[One (M9) Android Development] k4y0z:
#### New build is up!! ####

the build is containing mainly the following:

-JamesDSP Icon fixed

-Camera fixed

-minor fixes

AICP features added:

-Changelog

-addon.d/backuptool support

Note: This means starting with this build you don't need to reflash gapps, magisk etc.

Enjoy!
[One (M9) Android Development] ayoobelmasry:
I installed Magisk Canary without any problem, but there is not a single module that I tried to install works, in addition any app. that requires SU does not work either even though it is in the Magisk SU list. Is this what expected from this ROM given the fact that it is still in its early stage?
[One (M9) Android Development] The_Walking_Playground:
Hi,

I'm using Magisk with Root Explorer and it's working fine.

TWP
[One (M9) Android Development] Biggie_still:
Again Okay let me drop this here and see if I can get help..

In system/product is it possible to edit that build.prop in order to get pixel launcher working on this Rom?? Or what's the other way round?
[One (M9) Android Development] Salbull:
Why is netflix not working on this rom? Is it supported on the rom?

I'm rooted with magisk and everything else works fine :confused:
[One (M9) Android Development] The_Walking_Playground:
Hi,

If you need to add or modify props, you can do this via a Magisk module. Either create your own module with the additional/modified props you need, or use the "MagiskHide Props Config" module from the repo to set up the props. What props make Pixel Launcher work? Also, have you tried the Lawnchair v2 (Beta) launcher? It works well on this ROM and has similar features to the Pixel launcher. That's what I'm currently using.

TWP
[One (M9) Android Development] k4y0z:
Netflix will be fixed in the next release.
[One (M9) Android Development] Kenneth_1989:
Thanks

Thanks a lot for the hard work you are doing. I love this phone among other things because of your work.
[One (M9) Android Development] NoChill:
Not sure if you are aware of this, but advanced reboot does not work.

Adding any additional options to the power menu does not show up