Develop Bugs

[Q] Converted M8 to GPE restarting its self

Guys,
Have a problem with my M8 and not sure what's the cause of it all. Its an M8 that's been converted to a GPE edition via: http://forum.xda-developers.com/showthread.php?t=2708589.
Problem:
The phone keeps restarting randomly, comes on for about a minute and then restarts.
How it started:
Just received the phone back from HTC, I sent it in to get a loose speaker grill fixed. Up until then the phone has been fine on GPE (4.4.2). Prior to me sending it in, the phone had an unlocked boot loader, s-off, custom recovery and rooted.
I made HTC aware of the state of my phone as well as telling them that its an original M8 converted into a GPE version, They didn't have a problem with it and fixed the device under warranty. But on receiving the phone back, HTC have relocked the boot loader and put s-on back, its still rooted.
So first thing i did was unlock the boot loader which went smoothly, next up was firewater to get s-off back. That didn't worked as HTC has apparently patched the exploit so im still with s-on.
After that is where its all gone down hill , tried a nandroid backup, worked initially then the restart began. Did a factory reset and that seemed to work until I tried installing apps, and then the problem came back.
Does any one have any idea what might be the cause or solution? If i had s-off id re flash the RUU, but obviously cant do that.

Hey there,
I'm having exactly the same problem i dont have a google play edition but since yesterday Spotify crashed and my phone keeps rebooting. Now i want to try and install Viper to see if it will solve my problem but right now i am on stock rom.

Wickedd said:
Hey there,
I'm having exactly the same problem i dont have a google play edition but since yesterday Spotify crashed and my phone keeps rebooting. Now i want to try and install Viper to see if it will solve my problem but right now i am on stock rom.
Click to expand...
Click to collapse
Let me know how it goes

The reason for the reboots is SuperSU v2.00
after updating SuperSU my phone gone completely crazy and keeps rebooting every 1 or 2 minutes, had to Disable the app and no problem so far
hope ChainFire fix it ASAP

arDr0id said:
The reason for the reboots is SuperSU v2.00
after updating SuperSU my phone gone completely crazy and keeps rebooting every 1 or 2 minutes, had to Disable the app and no problem so far
hope ChainFire fix it ASAP
Click to expand...
Click to collapse
OH i was thinking about something like that, when i check my active processes Right before it reboots, SuperSu is on. I was just about to sideload viper, now i might try this for a sec !
Hang on
Edit : That works, SuperSu is screwed..

Wickedd said:
OH i was thinking about something like that, when i check my active processes Right before it reboots, SuperSu is on. I was just about to sideload viper, now i might try this for a sec !
Hang on
Edit : That works, SuperSu is screwed..
Click to expand...
Click to collapse
im still on SU 1.94 were you on SU2.0 ?

I was on version 2.0, any more questions ? I'm going to flash to Viper in a couple of moments

You might be right, on SU 1.94 and no restarts. Trouble only happens if i get the latest version.:good:

Xposed Installer wont install

When I installed xposed at first it was working and i installed all my modules but then i installed per app hacking cause my battery was draining fast.So i started stopping wakelocks on certains apps I thought was draining my battery and next thing you know my phone started acting crazy so i used odin and flash the stock nb4 firmware in odin but didnt factory reset my phone. So my phone booted up and it was stock firmware and i had re rooted it using cf auto root i already had the xposed installer but the framework wasnt activated so when i activated it said sucess and rebooted but when it rebooted it got all the way to the tmoible 4g lte screen and didnt go past that it didnt bootloop but it like wont turn on just stays on the tmobile 4g lte screen.Can anyone help i used xposed for everything its a main part of my phone i need.When i go into xposed it says "app_process version 58 has been installed previously but version "_" was found now.If you didnt expect an old file to be restored,you might want to try installing via recovery(auto or manual)

Problems with M8 audio very weird

Hey... I've searched extensively and have encountered a problem that makes absolutely no sense to me. Please if anyone can help if be extremely appreciative.
To start im on an m8 from Verizon. My issue is I'm encountering a problem with the audio engine in that I've flashed cm and this exact build I've used previously and the audiofx app worked fine. I later installed v4a and it broke audiofx. So I wiped /cache /data /system and dalvik and reinstalled... Same issue audiofx was no longer working.
So I decided to ruu completely back to stock lollipop using dottat's ruu. I proceeded to run said ruu several times and they all worked perfectly. Exactly as they're supposed to. I then factory reset from the boot loader with stock recovery installed. It went to like the download screen and said something about pulling data from Verizon and rebooted. I then booted into the stock recovery and wiped everything I could. After this I reinstalled cm with working audiofx (again I had had it working before) and it still wasnt working. I tried for an hour trying out nuplayer/awesome player in developers options, changing selinux from permissive to enforcing and vice versa, rebooting, clearing cache, force stopping all sound, and finally out of frustration I reinstalled v4a and it's driver.
V4A wasnt working so I was getting concerned and I decided to uninstall and then reinstall the driver. Once I uninstalled it v4a immediately began to work.... I switched it off and went over to audiofx and it was working finally... Again this is after a full successful ruu to stock. So I decided to reboot. After rebooting I found I had to repeat the install and then uninstall process of v4a to get audiofx and v4a to work. I got so frustrated I decided to use the 4.4.4 ruu and go back to my true stock conditions (outside of s-on and having root). So I restored with dottat's 4.4.4 ruu and tried installing an all carriers build of modified cm12.1 with working audiofx. Yet again audio fx was not working. I tried the cm build from above and same thing.... No audio fx. If I install v4a and remove it they work again. What the hell is going on here?
Please if anyone had any idea for to correct this phase let me know. I've got no clue how after several ruus this can happen. I'm becoming very discouraged... I'm not sure what to try at this point. Is not so much at this point just the sound mod. I want to know wtf I'm missing. Please someone help.
HTC One (M8) ViperOne + Hypernova
Edit: this truly has me perplexed. I did run setenforce 0 at one point because selinux enforcing stops v4a from working. I've corrected selinux by running setenforce 1 since then. It appears AudioFX is unaffected by SELinux though as when it's working it continues to work regardless of said command unlike v4a. I want to emphasize that after my ruu I repeatedly tried to get audiofx working after a fresh install and still no dice. It was only after multiple failures I have in and tried v4a which temporarily corrects the issue.
Another bug that wasn't present but is now on every fresh flash the Swype/gesture typing feature of the aosp keyboard doesn't work. Installation of the Google keyboard allows me to use gesture typing through it.

Random Reboots and other strange things

Hello, I think I have a really strange problem. I'm running Exodus 6.0 (and I made a full and fully functional backup that worked without issues) and yesterday I wanted to install AICP 12.0 (Android 7.0).
So I did a clean flash, but the SIM card detection didn't work and baseband showed up as "unknown" (according to the AICP members, I am the only one with such an issue).
So I tried several times but no success. They told me that it could be a problem of the 20G modem and bootloader. So I decided to revert back and since then I only have problems.
This is what I've done: Firstly, I flashed the 20D kdz. The phone booted fine. So I tried to install TWRP through ADB. (The phone was recognized and I was able to perform ADB commands). So I booted to bootloader, typed in the commands, but....nothing. TWRP didn't boot and I couldn't install it, no matter what I've tried. No I was on stock Rom without root and custom recovery, so I decided to revert back to Lollipop. I flashed the 10c kdz, flashed the rooted system image, wanted to flash TWRP (3.0.2-1) via Flashify, no success. Not until I tried TWRP 3.0.2-0, I had success and TWRP has been flashed. So ok, all fine now I thought, so I flashed the complete 20D stock Rom via TWRP, booted it up, worked. Now I wanted to give AICP a try again. So again installed, again no SIM card detection. With the CM 14 nightly 10/21 flashed afterwards (always clean flashed), success! SIM card was detected fine. So, again AICP tried and surprise, SIM card was detected as well. But now I had new problems: When I flashed SuperSU, SIM card wasnt't detected again.
Without SuperSU and stock AICP kernel, I suffered random reboots while setting up the WiFi connection in setup wizzard. Without SuperSU and Llama Sweet R7 kernel, I suffered a system crash and got a green screen saying something like "App F1Q: XPU Error!". So after some time I gave up and wanted to clean flash Exodus again, again no success, because the setup wizzard stopped (unfortunately:laugh:).
So ok, last rescue: My full backup. So I restored it (Exodus 6.0 10/22 nightly, opengapps pico 10/23, SuperSU SR1 2.78 in systemless mode, systemless xposed v86.2) and seemed to work fine. Today, I wanted to run SafetyNet Helper, and the phone suddenly rebooted. I wanted to run Pokémon Go, the phone suddenly rebooted. Nova Launcher can't get permissions for showing up unread labels correctly (though I have Nova Prime and all permissions are granted for sure!), other apps seem to work correctly. But all in all it's very strange because I have the feeling that somethink went completly wrong. So I don't know what I've done wrong, what do you think about this?

Can't boot to OS; Android is upgrading screen

Hi all.
I have a Note 8 GT-N5110 that's still running Stock 4.4.2. It's rooted and has Xposed 2.6.1 installed along with some modules. Last night I flashed TWRP 3.0.2-0 with the intention of flashing Magisk, forgetting at the time that it only works on Lollipop and up. I did not do a backup (I know) and rebooted back to the Stock OS just fine. I updated some Xposed modules and rebooted. Then I added some new Xposed modules, updated AdAway and its host files, and rebooted.
Now I cannot boot past the Samsung logo screen no matter how long I wait. I've gone into TWRP and wiped Dvalik and Cache, which lets me boot past the Samsung logo and get to a screen that says "Android is upgrading, starting the apps." It's been sitting on this screen for about 1 hour, which makes me think I can't boot past it. Any ideas how to easily fix this? If I need a full refresh, can anyone point me to the US version of the Stock 4.4.2 ROM?

This may help: https://updato.com/firmware-archive-select-model?q=gt-n5110&exact=1