yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Yeah, my intent was to get the fastboot getvar info about your device version (which you have now given), so we can further direct you from there. Figuring it out yourself is not that easy, for a number of reasons. You probably got signature verify fail, since the firmware must be the specific to your device version's CID (carrier ID) or else it will fail by design.

My suggestion would be:

a) Flash firmware fw_6.13.666.7 from here: https://xdaforums.com/showpost.php?p=60218734&postcount=5

Using instruction near the bottom of the post.

b) Restore stock TWRP backup (stock ROM) from here: https://xdaforums.com/showpost.php?p=60211240&postcount=3

Using the instruction in Post #1 of that same thread: https://xdaforums.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

Only need to Steps 1-9 of that guide (and skip step 3 of that guide).

c) Then you can do steps 4-6 of what I posted in my earlier reply above: https://xdaforums.com/showpost.php?p=78750946&postcount=2

Keep in mind that the TWRP backup (stock ROM) in step "b" above, is not the same as the "firmware" in step "a" above. The firmware in this case, is not a full ROM, but a small file which contains radio, hboot, and some other small partitions, needed to make the ROM work, but does

not

contain the ROM itself. This is a little confusing I know, but moral of the story, is that you should update

both

the firmware and the ROM to get the phone working again, than backup and root.

---------- Post added at 09:57 AM ---------- Previous post was at 09:47 AM ----------

Yeah, name calling and belittling folks is not my style. And also against xda's rules of conduct. There are a lot of toxic forums on the internet, and I agree xda is a cut above that; at least most of the time.

We all had to start somewhere with this stuff. And for a device this old, there is a lot of outdated and contradictory info out there. The only reason I understand all this the way I do, is that I've been here on the M8 forum section, since practically the start. And I've learned a lot from other folks in the community; and have benefitted from great resources like ckpv5's thread I linked above.
[One (M8) Q&A, Help & Troubleshooting] Neku DHack:
So, I did the first step, and flashed the OS twice because it gave me an error, now its stuck on the white boot screen with the htc o1ne logo in the middle, and its been like that for hours now. gonna wait for the battery to die, and see what happends. Can't hold the power to shut it down.

Edit:So, It died, and now it won't charge, and red/orange light at the top is blinking... the battery logo pops up and says its charging, but it isnt.

Edit 2:Fixed the charging issue
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Power + vol up will force a reboot, in cases where holding power alone doesn't do it. Or you possibly didn't hold power long enough. In some "stuck" situations, you may have to hold the button(s) for about a minute, before it reboots.

The button combos are hardwired into the device, so they will always work unless the phone is truly bricked.

Also, flashing the firmware twice is normal, as is the error message. So you did the right thing in flashing it again.
[One (M8) Q&A, Help & Troubleshooting] Neku DHack:
So, after leaving it for a few days, and trying to reboot it, it got stuck in the boot screen again, so I did the power+vol up, and now its black screened and wont charge... Is it bricked?

Edit:Not bricked, if I hold down every button it flashes the htc boot screen, then it goes to black again
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Try power+vol down.

The phone isn't bricked. I already said, you can't brick this phone doing what you did (trying to flash recovery, root file). Those partitions are separate from the bootloader, which is also protected by s-on (you couldn't overwrite it, even if you wanted to).The fact that the HTC logo screen comes on, also means bootloader is still working properly (no bootloader = dead screen) and that you just need to execute the proper button combo to get to the bootloader screen. As long as bootloader works, the phone is recoverable.

Also, have you been charging the device? Since you let the battery die, you should charge it fully again (overnight on wall charger, not connected to PC).
[One (M8) Q&A, Help & Troubleshooting] saiyansection:
in my case bootloader is working even i cn can access recovery( but to access recovery it takes 20 minutes) /data is not mounting

tried every solution to flash even ran RUU , but no luck

I did nothing to device as such , device rebooted and i think EMMC blown itself!
[Xiaomi Mi A2 / 6X Questions & Answers] Sid.Boi:
Recently i am facing an issue whenever i dial a no and as soon as the other person atends the call my screen goes off without even puting my celphn to my ear and i cant cut it until the persn on other side of the cal cuts the call and as soon as call get cut screen turn on automaticaly. And same is the case while somebody cals me and as soon as i pick up the call without even puting celphn to the ear same happens until cal is finished.i hope u guys undrstands what i am tryng to say here.sory for my bad english as it is not my native lnguage. Do any of u guys faces this issue or is this jst happening with me only.
[Xiaomi Mi A2 / 6X Questions & Answers] Njaiker:
I don't have this issue on my phone. Maybe try calibrating the proximity sensor in the HW test menu(*#*#64663#*#* in the dialer).

If that doesn't work maybe turn on the option of "power button ends call" under accessibility settings as a temporary fix while you search for a fix.
[Xiaomi Mi A2 / 6X Questions & Answers] Sid.Boi:
Thnx bro i have calibrated as u have told me to do. Now i will test it during calls. I hope this will work.
[Xiaomi Mi A2 / 6X Questions & Answers] Vhishma:
I am also facing the same problem.

I am also facing the same problem.

If you find any solution please do let us know.
[Xiaomi Mi A2 / 6X Questions & Answers] xxqxpxx:
same. i'm on havoc
[Xiaomi Mi A2 / 6X Questions & Answers] jayaphani1993:
I think you should get your display replaced

I think it an issue with the display. I faced a similar problem where my display was registering touches during calls and most of the time my microphone got muted because of it. I took it to the service center and got my screen replaced & now the problem is gone.
[SuperSU] elesbb:
First, the details:

Phone: Samsung Galaxy S7 Sprint - Eng boot image flashed - Bootloader v4

The problem:

I have a script that I can hijack at boot, using the eng boot image allows me to have a root adb shell. I can place all necessary files needed for root and have done so. I can chcon the root files to match what they need to be.

I add the following to the boot script that the kernel runs:

./system/xbin/supolicy --live --sdk=26 > /dev/kmsg 2>&1 <---- This is where the errors happen.
./system/xbin/daemonsu --auto-daemon&

Everything runs but supolicy cannot open the target file. I know it exists because of the output from ls -l

I also know I am a root user in the script due to whoami returning root.

[ 82.936270] WHOAMI
[ 83.009546] ss_platform_log: !@Boot: Data SVC is acquired
[ 83.215499] root
[ 83.860941] -r--r--r-- 1 0 0 0 Jan 1 1970 /sys/fs/selinux/policy
[ 83.947108] supolicy v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT\x0a
[ 83.947856] File [/sys/fs/selinux/policy] does not exist!

I can successfully use the adb shell with root access to execute supolicy and it works. So I have no idea what is going on. My only guess is selinux is preventing supolicy from accessing the file. But I thought changing contexts with chcon would fix that? EDIT: Current context of the hijacked script at boot: context=u:r:qti_init_shell:s0

If anyone can give me pointers, I sure would love that.

PS: I know I can root with the eng boot, but my attempt is to have supolicy working so I can flash the original boot img back due to eng boot consuming abhorrent amounts of ram. I also want stock kernel with supolicy working to allow viper4android to run.
[SuperSU] Ibuprophen:
It looks like you may just need a Custom Kernel that's SEAndroid Capable which allows for the Sepolicy to be freely changed.

I don't have this device nor this Kernel but, it looks like the following thread may be helpful for what you need.

Note the phrase on the OP "Set SELinux to Permissive or Enforcing". Don't be afraid to ask for some member guidance within it.

https://xdaforums.com/showthread.php?t=3462897

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[SuperSU] elesbb:
Hey! Thanks for the reply. Sadly I am on Sprint with the Sprint variant S7. This has a locked boot loader and I cannot use custom kernels. If so, I would have zero issues with root or selinux lol.

But, I did figure out it IS the context that the script I am hijacking is using that prevents the supolicy from finding the necessary file for patching. So, either I need to find another script, or I need to give up :crying:
[SuperSU] Ibuprophen:
I can't state anything that's device specific but, your situation is pretty much "in general terms" that applies to many/most devices in regards to what your trying to do.

The unfortunate situation you're in regarding the Locked Bootloader and such does prevent the ability for what your trying to do.

It's one thing to manually change to and from Enforcing and Permissive...

It's another thing for the ability to access the devices SEAndroid Policy freely in a type of "R/W Permission" (Modifiable) way.

Currently you are able to Change the SELinux State but, this is only a Temporary Change since it'll immediately default back when your device has rebooted.

As of right now, to my knowledge, you can't do what you are looking to do (unless there's something I'm missing or don't know about) but, you seem to have been pretty clear with the information that you had provided.

I hope that I had explained this okay via text...

Sorry for the bad news... :eek:

I do wish you the best of luck! :)

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[SuperSU] texlui:
Hi,

try to switch selinux in permissive mode before you run your script.

So , you can log all the Selinux denied.
[8525, TyTN, MDA Vario II, JasJam General] dparm:
So I just picked up an AT&T 8525 (HTC TyTN) and love it so far. A strange quirk has come up though...with the screen brightness at maximum, it still seems rather dim. When I switch to camera mode, it suddenly gets brighter.

Is there some option somewhere I've missed?
[8525, TyTN, MDA Vario II, JasJam General] zecoj:
http://xdaforums.com/showthread.php?t=279365
[8525, TyTN, MDA Vario II, JasJam General] mrpiggae:
I use that all the time. Great for watching movies and what not. Will drain your battery pretty quickly, though, if you leave it on all day like I've done before.
[General Topics] tgall-foo:
One of the things that we do at Linaro is testing Linux Kernels to look for kernel regressions. Ideally we want a world where those that make use of Long Term Support Kernels (LTS) are able to depend on and trust the stream of fixes that are being provided such that they end up on devices.

Mobile phone companies, Linux Distros, embedded Linux deployments, etc all generally like the idea of installing one major version of Linux (e.g. 4.9) and sticking with it for the lifetime of their product.

This, and following stories tell how week to week testing of Linux kernels is going, what we’ve found, or better, not found as the kernel versions tick by.

We test using two host user spaces, open embedded and Android.

Open Embedded

2019–01–21

4.9.152, 4.14.95, 4.20.4

Reported crashes in v4.20.3–15-g5592f5bf010b which were intentional ‘canaries’ (the canary successfully died)

Reported no regressions in <24h

4.19.17

Reported no regressions in <48h

Bug Status — 57 open bugs

2019–01–22: Anders Roxell sent allmodconfig patches 1 2

2019–01–18: Naresh Kamboju reported kselftest bpf test_netcnt failure re: bug 4245

2019–01–16: Daniel Díaz sent 4 kselftest patches upstream that are being carried in OE

Android

Android 9 / P — 4.4, 4.9, 4.14, 4.19 on HiKey

4.14.94 — no regressions

4.19.16 — Note USB OTG regression and potential eMMC issue documented in the bugs section

4.4.170 — no regressions

4.9.150 — no regressions

Android 8.1–4.4 on HiKey, Android 8.1, 4.14 on X15

4.14.94 / X15 no regressions

4.4.170 / HiKey no regressions

Android 9/P + automerged latest version of LTS 4.4, 4.9, 4.14, 4.19 + HiKey + Latest LTP

This new combination is a work in progress to pull in latest LTP from AOSP-master, as well as using the combination of Android Common + HiKey Linaro (auto merged). It triggers automatically when Android Common is updated right after a new LTS release is merged. This combo thus gives everyone great visibility to test results nearly immediately after an new LTS is available.

We have initial data but are not sharing them as part of this report yet.

AOSP-master tracking with 4.4, 4.9, 4.14, 4.19 on HiKey

These builds are being reworked / repackaged so we’ll have data to report next week.

Bugs

18 — +2 WtW

New: 4258 OTG with 4.19.17 (and prior) not flipping modes to allow USB keyboards etc

New: 4259 4.19.17 eMMC issue?
[Moto Maxx Android Development] fgl27:
[IMG="rrbugs"]https://resurrectionremix.com/assets/rrbugs.png[/IMG]​

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.

Always post a bug with [MENTION=5747496]fgl27[/MENTION] and a log .zip generated by the app

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP, even after a random reboot share a log

If is a Reboot/Power off related bug make the log as soon the device finishes boot up
[Moto Maxx Android Development] LifeAsADroid:
Awwww yiiiiiiissssssss!

Thanks for all your hard work bringing relevancy to our very dated phones!
[Moto Maxx Android Development] masterfemhp:
Thanks, man!

One question though: in the opengapps download page says '9.0 requires a patched ROM to proper WebView support'.

I haven't found in changelog or anywhere else mention of this patch.

Is the ROM patched to support WebView properly?

Enviado desde mi Moto MAXX mediante Tapatalk
[Moto Maxx Android Development] FlavioV:
I used the aroma package with both LOS test roms in the past week and I had no problem with WebView. Plus, the opengapps website shows the same message if you pick Nougat (7.x) or Oreo (8.x).

I'm no dev but I'm pretty sure this ROM is already patched.
[Moto Maxx Android Development] fgl27:
I never notice that, all custom ROM come with building WebView support, they update it here...

https://github.com/LineageOS/android_external_chromium-webview

You can choose/check what WebView you use in developer options, of course to change you need to have installed another WebView app like chrome .
[Moto Maxx Android Development] Marky__Mark:
[MENTION=5747496]fgl27[/MENTION] Thanks for the sexy rom. No problems so far and everything works except Subsratum.
[Moto Maxx Android Development] pankaj72:
How to install viper4android on RRpie
[Moto Maxx Android Development] Mrpookie:
Anyone tried magisk yet? Still have magisk hide issue where unable to install apps?
[Moto Maxx Android Development] mrkhigh:
A device that had KitKat is installing pie.

Thanks man!

I'm off work today (sick) but at least it gives me plenty of time to try this.

Will download shortly

Edit: all good so far! I don't use a sim in this device anymore but it seems snappy.
[Moto Maxx Android Development] Marky__Mark:
An annoyance i found so far is theres an app is running in the background message that keeps popping up whenever i open the messaging app. I know this is an Android thing, but i googled the solution which is open the Android System app and turn off the "apps using battery" notification. This is already turned off. So if someone has a solution, please advise.
[Moto Maxx Android Development] mrkhigh:
[MENTION=5747496]fgl27[/MENTION] how do I unroot?
[Moto Maxx Android Development] Marky__Mark:
Developer options i imagine.

---------- Post added at 11:07 AM ---------- Previous post was at 11:01 AM ----------

I think its the "app running" notification and its selected and read only.
[Moto Maxx Android Development] mrkhigh:
A full unroot.... Normally I use Los root and unroot but I do not see that for Los 16.

Also having trouble finding an app that will move an app to system. I'm going to have to do that manually in twrp I guess.
[Moto Maxx Android Development] enigma1400:
You could use the Magisk app systemizer module

https://xdaforums.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851
[Moto Maxx Android Development] FlavioV:
Try this module it's meant for Magisk but it also supports direct install into system via TWRP.

Rebooted with Magisk Hide on and tried to install Netflix... It works!

The issue we had on Oreo doesn't seem to affect Pie.

If you're rooted you can use Link2SD. I use it to uninstall system apps but it can also move (convert) them to system. Can confirm it works on RR-P.

There's no LOS Pie yet so the remove su addon is outdated. In the meanwhile you can just install and uninstall Magisk. It'll remove the native root during installation so the uninstaller should levae you completely unrooted.

---------- Post added at 19:09 ---------- Previous post was at 19:01 ----------

I have the battery notification disabled and I haven't seen that message yet. Maybe it's because I upgraded all the way from RR Oreo?

The next time that notification appears tap and hold it to see where the notification came from and disable it if it's the case.
[Moto Maxx Android Development] Marky__Mark:
Its coming from the messaging app. SMS
[Moto Maxx Android Development] mrkhigh:
Link2sd worked, app "impactor" successfully unrooted.

Very happy now with my slice of pie.
[Moto Maxx Android Development] Davi_15:
The rom is generally quite complete. A single detail is the battery life, which compared to the latest version of LOS 16, is draining faster.
[Moto Maxx Android Development] Unreal_man:
fgl27, what governor do you use? Is it planned to add such a governor as smartass V2, smartass H3 and so on to the core? Generally wonders why navigation slows down for example in YouTube if you scroll down? In the settings for developers there is the inclusion of gpu for drawing 2D graphics, but this does not help to get rid of the friezes. The GPU is used for a maximum of 300-400 MHz. How to make the GPU responsible for drawing graphics, not the CPU? To the frequency of the GPU rose to the limit of 800 MHz.
[Moto Maxx Android Development] thatoneguy-tog:
Yes, I use bluetooth all the time. Thank you so much for your quick response and future fix!!
[Moto Maxx Android Development] fgl27:
ROM update! RR-P-v7.0.0-20190306-quark-Official.zip​

Changelogs:

Device specific (Click Here)

Resurrection Remix OS - Pie source and Quark Changelog (Click Here)

Download Links :

ROM:

Main:

get.resurrectionremix.com - ROM Main Link Click Here (This is the server used by the Updates app in Setting>System>Updater)

Secondary:

Gdriver - ROM Mirror link Click Here (This contains current and previously version)

AFH - ROM Mirror link Click Here (This contains all old versions, but may not show last version as soon as update post comes up)

Gapps:

Open GApps:

Open Gapps Click Here

Choose Platform: ARM, Android: 9.0, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.

Open GApps old releases Click Here, in case latest version is NOK

Gapps recommendations from LineageOS Google apps options (click here)

TWRP For Quark:

TWRP Use laste Mod version that I release Click Here

Installation instructions:

Download the latest build and GApps.

Reboot to recovery (recommended make a backup)

Coming from different ROM? Then Always wipe Data (without media aka without internal memory)

Wipe System*

Flash the latest build and GApps **

Reboot and enjoy!

* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update

** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.

Always start a post with a bug report with [MENTION=5747496]fgl27[/MENTION] and always attached a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

** If the device Random reboot also share the log made as sone as the device finished the random reboot

Bugs without logs, without [MENTION=5747496]fgl27[/MENTION] will probably not be read, there is too much posts on the thread sometimes and I don't have time to read it all, anyone can post as much as is need of course as long is a things related to this thread
[Moto Maxx Android Development] asoler:
This compilation haves an error, no boot.

Check this please, thanks.
[Moto Maxx Android Development] CCaseXX:
I second this issue.
[Moto Maxx Android Development] EVNS:
So isn't me haha, already try install 6x this lastest and it just stop at Motorola Logo.
[Moto Maxx Android Development] fgl27:
I'm running it

Download from were?
[Moto Maxx Android Development] EVNS:
[MENTION=5747496]fgl27[/MENTION] downloaded by OTA and direct RR Oficial Link, i believe it is the same link... Tried it.
[Moto Maxx Android Development] eddebolacha:
Error on boot here either,

Ota install , and today gapps
[Moto Maxx Android Development] CCaseXX:
From the link mate.
[Moto Maxx Android Development] fgl27:
Will push a new one later... something bugout when uploading...
[Moto Maxx Android Development] FlavioV:
I had no issues with today's build, but I manually flashed BHB27-Kernel on top of the ROM (don't know if it's built-in but I always flash it just in case due to Magisk). If your device won't boot after updating give the custom kernel a try or wait for the next ROM update.

I still prefer manual flashing over OTA as it's easier to flash my stuff at once. Basically I follow the same steps as OP but I flash my stuff in the following order:

*wipe system*

RR

Magisk

BHB27-Kernel

Clean modem status from post #2

Open GApps Aroma (removes AOSP apps, installs some gapps)

*wipe dalvik & cache*
[Moto Maxx Android Development] fgl27:
new build is up, same file name but now it boots and sleeps :victory:
[Moto Maxx Android Development] eddebolacha:
Ok now, thanks again
[Moto Maxx Android Development] CCaseXX:
I am having an issue when flashing where I do not have an option to type other than using google voice. This is not going to work as I can not complete the welcome process. Has anyone had this issue?

UPDATE:

Turns out it is due to the error 70 insufficient space in system....how do I fix?
[Moto Maxx Android Development] FlavioV:
Are you trying to update via OTA?

Follow installation instructions from OP, put rom/gapps in internal storage and flash one by one, just remember to wipe system before flashing to avoid error 70.
[Moto Maxx Android Development] Marky__Mark:
Appears all is well. Thanks [MENTION=5747496]fgl27[/MENTION]
[Moto Maxx Android Development] EVNS:
Im loosing too Google Keyboard after flash ROM keep just voice, Maybe u can help me [MENTION=8542292]CCaseXX[/MENTION]

UPDATE: Ok Google Keyboard are with problem in Gapps, fail of Gapps Install, maybe they repair it son.