yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] h-cspu:
But now we don't have a checksum anymore :(. Maybe you can paste them here to verify that the files were downloaded correctly.
[One (M9) Original Android Development] Claymore1297:
yes I can upload this too, but if you're using OTA-app you don't need this anyway ...

EDIT: done
[One (M9) Original Android Development] kall3:
As always: Thank you very much for the continous effort. I just had a try on the last release (190623-himaul). When I flashed this on my M9, the phone was not starting properly and was more or less unuseable. Startscreen did not appear completely. While receiving a call the phone got stuck and froze...

I went back to 190608-himaul and now my phone works as before. :)
[One (M9) Original Android Development] Claymore1297:
the builds have no relevant changes and on my test-devices all behave like expected.

EDIT: booted again and received a call without issues.
[One (M9) Original Android Development] kall3:
I am sorry, but the "no relevant changes" prevent my device from booting. completely The two versions differ in size by about 2 MB. I tried another time. These are my results:

The first time I have flashed the following set

1. ROM

2. Magisk 19.3 (again, was installed already)

3. Latest GAPPS (again, selection "pico" as before)

2nd try:

Now I just flashed the 190623-himaul-ROM (2nd effort) without any additional zip-archives . Magisk was found nevertheless and patched the boot.img. Boot seemed to be successfull but again after unlocking the lock screen for the first time after boot the phone went into an endless loop with the message "smartphone is starting" :(

I once again reverted to the 190608-version and will keep it.

Thank you for your time.
[One (M9) Original Android Development] Claymore1297:
did a clean flash on the 080619-build and flashed the new 230619-build and no issues.

Maybe you should try a clean flash.
[One (M9) Original Android Development] kall3:
I have no time for a clean flash, but I gave it a 3rd "dirty" try. This time I disabled the nova-launcher and replaced it with the stock trebuchet one. Then I went into normal flashing: Same behaviour as before - endless loop saying "smartphone is starting" after unlocking lock screen for the first time (I have to pass the lock screen after every first boot, because of security rules with one of my email-accounts).

In fact, I am using the M9 with your LineageOS16.0-ROM for several months now - without any problems. I am/was very pleased to have i that way. I have also updated the phone several times without any problems in the last months.

In my mind this looks like a bug in the latest release (190623-himaul with german telephony provider) - especially when your recent changes have been "minor".
[One (M9) Original Android Development] Claymore1297:
no, as I said no changes and I could install this without any issues as described below.

If you can provide a log, I can look into.
[One (M9) Original Android Development] drpatrickbarry:
My dirty flash, of 230619-build , worked pefectly OK.
[One (M9) Original Android Development] jmac052002:
I did dirty flash from 060819 to new build and it updated and is running just fine thanks Claymore 1297 we appreciate all your hard work brother, hey I will donate Thursday to the new codebucket link to keep it going so we can keep receiving OTAs thanks and as always so appreciative!!!
[One (M9) Original Android Development] Claymore1297:
Thanks to the donations, I will forward it to the one who granted us the access and space of our OTA's! :)

Btw. brightness slider is fixed and will be included in the next build ... ;)
[One (M9) Original Android Development] kall3:
Hello and thanks a lot for the offer. Finally I succeeded: These are the steps that led me to success:

Extracted the boot.img from 190623-zip

Patched that boot.img with Magisk 19.3

Flashed the magisk-patched boot.img as "boot"

Changed to recovery-mode and...

...dirty flashed the 190623-ROM and so on and finally:

device booted completely

:):):)

So it must have been some kind of interference of Magisk with the new ROM on my device.

Nevertheless, as of now I am using ROM-version 20190623-himaul too without having any problems now :) Once again: Many Thanks!
[One (M9) Original Android Development] wartomato:
You know I don't like to be mentioned, haha...
[One (M9) Original Android Development] chris.mackay:
Hey team, I just flashed this ROM onto my device but am unable to play videos in YouTube, Facebook and Snapchat. Has anyone else experienced this?
[One (M9) Original Android Development] jmac052002:
Man I haven't had any of those issues Facebook and YouTube work great for me , I don't use Snapchat so can't speak to that...hope someone can help you figure it out
[One (M9) Original Android Development] Claymore1297:
which build you are using? we had this is a very early version ...
[One (M9) Original Android Development] chayxe:
Please can any one confirm that the screen cast is working?
[One (M9) Original Android Development] chris.mackay:
It was the latest build available, but I just flashed the latest AICP build available (14.0.?.?) and had the same issue so I flashed the older AICP (13.1.?.?) and still received the same issue. So it must be something with my phone, I am going to go back to the stock ROM and see if the videos were working on there.

Cheers
[One (M9) Original Android Development] alptrek:
[MENTION=8276284]Claymore1297[/MENTION] i'm trying to build resurrection remix for himaul but i have problem.

breakfast himaul

including vendor/rr/vendorsetup.sh

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "rr_himaul".

21:41:54 dumpvars failed with: exit status 1

Device himaul not found. Attempting to retrieve device repository from ResurrectionRemix-Devices Github (http://github.com/ResurrectionRemix-Devices).

Repository for himaul not found in the ResurrectionRemix-Devices Github repository list.

If this is in error, you may need to manually add it to your .repo/local_manifests/roomservice.xml

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "rr_himaul".

21:41:56 dumpvars failed with: exit status 1

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "rr_himaul".

21:41:56 dumpvars failed with: exit status 1

** Don't have a product spec for: 'rr_himaul'

** Do you have the right repo manifest?
[One (M9) Original Android Development] Claymore1297:
yes, the right maifest is in OP of this thread ;)

So add it and try again...
[One (M9) Original Android Development] alptrek:
I've already added. Still same. If we can add RR to the device list himaul problem will be solved but how will we add.

https://github.com/ResurrectionRemix-Devices

https://github.com/AICP/device_htc_hima-common
[One (M9) Original Android Development] Claymore1297:
no, you don't need breakfast any more, because you've added it to your manifest ... this is, what breakfast does...

only brunch himaul and it should work.
[One (M9) Original Android Development] alptrek:
I'm sorry I didn't quite understand what you meant. Now the problem is not to find (rr_himaul)?
[One (M9) Original Android Development] Claymore1297:
no, after you added the repos into your manifest run the following:

1. repo sync -q --force-sync

2. . build/envsetup.sh

3. brunch himaul

breakfast is not needed any more
[One (M9) Original Android Development] alptrek:
When i try breakfast himaul and brunch himaul same error.

---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------

Okay, I'il try one by one and throw a picture of the results.

---------- Post added at 07:51 AM ---------- Previous post was at 07:22 AM ----------

https://i.hizliresim.com/3OaO42.jpg
[One (M9) Original Android Development] Claymore1297:
can't open the URL
[One (M9) Original Android Development] alptrek:
https://imgur.com/a/XCtvKIl
[One (M9) Original Android Development] Claymore1297:
the output in screen 6-8 is this if you call the build/envsetup.sh?

If yes you should ask someone of the RR-project, in my repos the product of course is called lineage_himaul not rr_himaul.
[One (M9) Original Android Development] alptrek:
how to change the lineage_himaul to rr_himaul or add the RR Dev tree github himaul device
[One (M9) Original Android Development] Claymore1297:
https://github.com/Claymore1297/android_device_htc_himaul/blob/lineage-16.0/lineage_himaul.mk

but not sure if this is needed, always thought on RR, they use LOS-repos... but not familiar with RR and don't plan to change this ;)
[One (M9) Original Android Development] alptrek:
what using repos on your AICP project ?
[One (M9) Original Android Development] Claymore1297:
this is off topic here, so please write me a PM and we can discuss this.
[One (M9) Original Android Development] SwitchX1:
Changelog?

Claymore, could we get a changelog from the previous version (20190510) to this, latest one (20190608)?

I'm tempted to update anyway but it would be nice to know the changes from this two builds. Thanks!
[One (M9) Original Android Development] Claymore1297:
Don't remember ... But I think ASB s and kernelside binder update.
[One (M9) Original Android Development] SwitchX1:
Thanks!

So ASB is like NFC?

Do you think it's worth the upgrade?
[One (M9) Original Android Development] Claymore1297:
No ASB are the monthly security patches. Yes it is
[One (M9) Original Android Development] SwitchX1:
Oh, okay! Will do, many thanks!
[One (M9) Original Android Development] Claymore1297:
New build is up!!

the build is containing mainly the following:

- july ASB's

I reorganized the directory-structure a bit on new build location.

If you have installed the last build (20190623), you can simply update via builtin OTA-app.

Enjoy!
[One (M9) Original Android Development] Jupp Pütta:
It seems that this one got my phone bricked completely.

I installed new build with updater, having installed the 20190623 some days ago. First everything went fine. But after entering my password wenn booting after installing the new build, I ended up in TWRP some minutes later. I tried to reboot, with the same effect.

But now TWRP would not accept my decryption password any more. I tried to reboot with backup, but it failed. I tried to give the phone a fresh start, but now it is stuck in the „This build is for development purposes only …“ screen.

Could the new directory-structure produce a problem together with encryption?

Help is appreciated.
[One (M9) Original Android Development] Claymore1297:
I tested it today and no issues. I don't think the build did this and the directory-structure is only on fileserver ... so the answer is no.

EDIT: which TWRP-version are you using?

EDIT2: I did a upgrade via OTA from 2306 to this one
[One (M9) Original Android Development] Jupp Pütta:
I am using the latest release form CaptainThrowback.

The problem occured immediately after installing the new build. I guess I am quite lost though, as I cannot enter TWRP and adb does not even find the device. Pressing power does not shut down the phone, pressing power + volume up and down gets the phone to restart, but it is immediately stuck in the starting screen again …
[One (M9) Original Android Development] Claymore1297:
a ROM installation cannot do such things. can you try do reflash the TWRP?

EDIT: there where no changes on deviceside, which could cause such things.
[One (M9) Original Android Development] Jupp Pütta:
Right now I don’t now how, as I cannt access the phone any way. I try to figure out if there is still a possible solution.

I see that there has to be another problem. However, as the system did not properly start after updating and entering the password, I reckoned there could still be a problem. (however, at this point I still could access TWRP, as it restarted in recovery mode automatically.)
[One (M9) Original Android Development] Claymore1297:
so you are encrypted ... was TWRP able to mount and decrypt the needed partitions in installation process?

I use 3.3.0 and is works, but I'm not encrypted
[One (M9) Original Android Development] Jupp Pütta:
Yes encrypted. Wenn installing I did not see a problem. When I was automatically directed back to TWRP I could enter the password and no errors regarding encryption where shown. I did an aditional back up, I tried to reboot again. After entering the password the system did not start as the first time, instead TWRP opened. Now, when entering the password I was warned that it could not decrypt. After trying for a second and third time I entered TWRP. I tried to recover from backup, but that failed. I tried to start the phone afresh, and then it goot permanently stuck in the starting screen.
[One (M9) Original Android Development] jmac052002:
Man used the updater and it worked great thanks as always Claymore!
[One (M9) Original Android Development] Jupp Pütta:
I finally succeeded to access TWRP again. After entering the password twrp notifies me:

„Missing files needed for vol decrypt: /systems/bin/vold

Failed to decrypt data“.

and later

"Unable to mount /data/media/TWEP/.twrps"

I formatted the partition and start to re-install now.

---------- Post added at 02:53 PM ---------- Previous post was at 01:55 PM ----------

I succeeded by

1. installing the last build without encryption,

2. then updating to the new build and finally

3. restoring from the last backup without "system".
[One (M9) Original Android Development] Claymore1297:
TWRP-fix available

[MENTION=1162986]Captain_Throwback[/MENTION] has fixed an issue, when you are encrypted and using OTA-functionality - like some have reported here.

He has made for us a unofficial build, which can found here:

https://github.com/CaptainThrowback/android_device_htc_hima/releases/tag/3.3.1-1_CPTB-20190704-05

Big thanks to the Captain & Enjoy!
[One (M9) Original Android Development] ayoobelmasry:
Congratulations, Hr. Claymore

You have solved the Bluetooth intermittent problem. I have tested it for 7 times in a row each time is 45 min without a single failure. Thank you very much.
[One (M9) Original Android Development] Cường Hồ:
cannot download

Gửi từ SM-G930F của tôi bằng cách sử dụng Tapatalk
[One (M9) Original Android Development] jmac052002:
Cannot download

You have to scroll to the bottom of the GitHub page on the link and where it says assets click on it and it will be the top file in the list click on that to download the recovery image
[One (M9) Original Android Development] ayoobelmasry:
There is a problem that could be considered as minor, it is with the indicator led. It does not behave as expected: sometimes it comes on red when charger is plugged, sometimes it does not at all. Some other times it comes on green as if the battery is fully charged whereas it is not, and so on. It would be great if this is solved as well. One thing I like of HTC phones is this indicator led that it is not only used for charging performance but is also used for notification indicator when phone is locked and screen is black.
[One (M9) Original Android Development] Claymore1297:
thanks for the feedback, I expected this more or less, but was not sure, because I couldn't replicate the same behaviour but a similar one.

It was a long hard fight :D

So finally fixed another longtime issue - cheers!
[One (M9) Original Android Development] vasya_Vasin:
Something wrong with WiFi tethering, I see WiFi network, I have stable connect, and I have a good internet at my phone, but have no internet at my laptop((
[One (M9) Original Android Development] Claymore1297:
worked here (but testet on AICP) - anybody else having this?
[One (M9) Original Android Development] k4y0z:
Also works fine here on LOS
[One (M9) Original Android Development] Claymore1297:
JamesDSP

Hi folks,

we could include JamesDSP to this ROM -would you like this?

AudioFX would be kicked out in that case...
[One (M9) Original Android Development] kall3:
I don't mind, as I don't use AudoiFX when listening to music on the phone. If the implementation has no side effects, I would appreciate this substitution.
[One (M9) Original Android Development] Max litcher:
Why not viper4android ?
[One (M9) Original Android Development] Death-Penalty-V:
Have also noticed this but as it is minor never felt a need to mention it. Thought it might have been a problem cause of magisk or its modules. This is like the only system tool that I feel might have been responsible outside of the actual rom
[One (M9) Original Android Development] Claymore1297:
V4A is Magisk-based, so no option for us.
[One (M9) Original Android Development] root-expert:
+1 for JamesDSP.
[One (M9) Original Android Development] Khanghtc:
Sense home

How can I install Sense Home for Lineageos 16 ?
[One (M9) Original Android Development] abbas_392003:
Unfortunately, the phone is connected to wifi late, please fix it
[One (M9) Original Android Development] nsirri:
Going S-Off

Hi i've issued some problems with this rom and i'd like to go back to stock, but the phone is S-ON and the passage i've done before (fastboot flash unlocktoken Unlock_code.bin) doesn't work anymore (waiting for device).

Anyone has suggestions ?

Thank you in advance for all ..

Nicola
[One (M9) Original Android Development] ayoobelmasry:
You don't need to lock the device again, you only need to put the stock ROM on the external SD card and boot the phone to the download mode, if it finds the ROM with its proper name it will flash it automatically. In this case you will loose every bit of data that is on the internal memory and will go back also to stock recovery.
[One (M9) Original Android Development] nsirri:
I' m already locked (S-ON), i need to go S-OFF that is required for the installation of the new rom.
[One (M9) Original Android Development] ayoobelmasry:
No, it is not required to be s-off to install any ROM. When I talked about being locked or unlocked I was talking about the bootloader not the S state
[One (M9) Original Android Development] nsirri:
I'm not so sure, here, to return to 100% stock says that S-OFF is required :confused:

https://xdaforums.com/one-m9/general/guide-return-m9-to-100-stock-s-off-t3091730

Thanks
[One (M9) Original Android Development] ayoobelmasry:
I have done this several times from custom ROM to stock ROM and vice versa. I am just telling you my experience. My telephone is HTC one m9, I never had s-off at all and never tried to have it off, at the moment my phone is on the Claymore lineage 16, and can go to stock ROM at will if required.
[One (M9) Original Android Development] nsirri:
Ok, i'll try. ;)

Thanks
[One (M9) Original Android Development] nsirri:
I downloaded RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1.exe but returns Error 170 (the phone is connected and visible).

Maybe depends on TWRP Recovery ?

This is my situation:

Recovery Twrp

Lineage 16

(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) serialno: FA****00845

(bootloader) current-slot:

(bootloader) imei:

(bootloader) version-main: 4.28.401.3

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: HTC__102

Can you suggest me a stock rom to download ?
[One (M9) Original Android Development] ayoobelmasry:
It looks like that you have similar telephone like mine with regard to its stock software level, they are both 4.28.401.3, this means the stock ROM that I got should work on your device. The ROM that you downloaded will not work for you because it is for another device. You can download the ROM that is similar to mine from the HTC website. It must be a zip file then you need to rename it to 0PJAIMG.zip where the first character is a zero not the letter o. This is necessary for the download mode to recognize the ROM and flash it automatically. You need to charge the device fully because it takes sometime to flash, follow the on screen instructions.

If you prefer, I could copy the ROM to my google drive for you to download, but let me know and give me sometime to do it
[One (M9) Original Android Development] nsirri:
Yes, if you could send me link to your rom, i appreciate. Take your time to do it :)

Thanks again.
[One (M9) Original Android Development] nsirri:
I did it, is not necessary that you send your ROM, thanks for your patience. :)
[One (M9) Original Android Development] nsirri:
I have flash twice the rom (0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip) but each time i have found that audio "crushed", it make noise instead of audio, i don't understand why, the first time i've flashed it was regular but after reinstalled all and download an update, and after reflashed it doesn't work :(

Any idea ? Maybe something HW is broken ??

To reflash i've renamed to 0PJAIMG, copied to SD and flashed by booting in download mode.

This is the motive for leaving lineage 16 and returning to stock :(
[One (M9) Original Android Development] ayoobelmasry:
If the 2 ROMs, stock and custom, has same problem with regard to audio, then that suggests that the device has HW problem in the audio system.
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-JamesDSP included

-august ASB's

-minor fixes

*JamesDSP: to activate toggle "Master switch". AudioFX has been replaced by JamesDSP.

you can install manual or via OTA.

Enjoy!
[One (M9) Original Android Development] abbas_392003:
helo .... what is the JamesDSP ?
[One (M9) Original Android Development] Claymore1297:
https://xdaforums.com/android/apps-games/app-reformed-dsp-manager-t3607970
[One (M9) Original Android Development] chayxe:
[/COLOR]

Updated and it kind of broke LIVE DISPLAY.

aside that, every other thing is working
[One (M9) Original Android Development] bikeboy24:
The volume control for the phone (speaker or normal) doesn't appear to be working. Any ideas?

Otherwise, everything is awesome on this!
[One (M9) Original Android Development] Claymore1297:
Good news everyone ... WiFi-Display is back and will included in the next build :)

Enjoy!
[One (M9) Original Android Development] Claymore1297:
long time issue battery/notification-LED will be fixed in next build!

Enjoy!
[One (M9) Original Android Development] chayxe:
Any help with how to increase in-call volume on the MIXER_PATH??
[One (M9) Original Android Development] Claymore1297:
well you can edit file /vendor/etc/mixer_paths.xml - reboot and see.
[One (M9) Original Android Development] chayxe:
Hello Claymore,

Please I have found the Mixer path, but i am confused which path name to edit.

is it voice-handset or voice-speaker?
[One (M9) Original Android Development] Claymore1297:
you can simply try it - I haven't checked it and currently very busy with Android 10
[One (M9) Original Android Development] Claymore1297:
the story continues! :)
[One (M9) Original Android Development] abbas_392003:
When are you coming this rom?
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-WFD

-september ASB's

-blinking camera issue fixed

-battery/notification LED fixed

-minor fixes

Enjoy!
[One (M9) Original Android Development] ayoobelmasry:
There are some google play apps stopped working since the previous build, hoped this one would fix but alas.
[One (M9) Original Android Development] ayoobelmasry:
Battery/notification led is not fixed. Still goes green when the charge is less than 100%
[One (M9) Original Android Development] Claymore1297:
it seems it is broken in LOS, it works properly now on AICP :-/
[One (M9) Original Android Development] kadi0131:
i cant flash the rom .. in twrp have error log
[One (M9) Original Android Development] chayxe:
i do not know but it goes green after it hits 93-100

---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------

tried the CAST feature.......its awesome.

:laugh: :laugh:

my live display is still broken tho.........

but the build is good
[One (M9) Original Android Development] Adi2071:
How to install this software? I have error 7. Please help me.