Develop Bugs

[Q] Help!

Hello everyone, I just got a problem last night. I tried to permroot my G2 using Visionary+ and once it rebooted it got stuck on the HTC loadup screen. I have done a factory reset and have gone into recovery mode but when I do go into recovery mode, I get a droid phone with an exclamation mark in the middle and it just stays there.
I don't know many details about the phone other than what I can tell you from the HBOOT menu, I'd rather avoid sending it back in for a warranty repair unless I can just get to the normal screen where I can unroot it, I don't care who you are I just need help on what to do because I have no idea :\
Thanks guys, you're my last hope >:|

First off, this is why you DO NOT use visionary. Well documented to brick phones:http://forum.xda-developers.com/showthread.php?t=1025135
You can start off trying to recover your brick by looking at this thread: http://forum.xda-developers.com/showthread.php?t=842495

You might as well have written that in chinese, I have no idea what any of this means. it's S-ON and it won't go into recovery mode.
Walk me through what I need to do..? :\
So I had a thought, if I could use a friends Android which, Idk the model to, but could I just uninstall Visionary from there? Would that do anything at all?

xTyrant said:
You might as well have written that in chinese, I have no idea what any of this means. it's S-ON and it won't go into recovery mode.
Walk me through what I need to do..? :\
So I had a thought, if I could use a friends Android which, Idk the model to, but could I just uninstall Visionary from there? Would that do anything at all?
Click to expand...
Click to collapse
You cant really uninstall visionary if you cant even boot up your phone. Right now the rom is corrupted and you need to follow an unbricking guide like the one mentioned above
Sent from my HTC Vision using XDA App

xTyrant said:
So I had a thought, if I could use a friends Android which, Idk the model to, but could I just uninstall Visionary from there? Would that do anything at all?
Click to expand...
Click to collapse
What are you talking about? Connecting your phone to your friend's phone? It doesn't work that way.

Alright everyone, I called T-Mobile and I'm having a new phone by tomorrow, there's nothing I can do as, I have no idea how to fix my corrupted ROM,
I tried following the unbricking guide but I can't so much as get my phone detected by my computer to even do anything with it.

And another noob bites the dust
Sent from my SilverBullet 'HTCDesireZ running CM7'

xTyrant said:
Alright everyone, I called T-Mobile and I'm having a new phone by tomorrow, there's nothing I can do as, I have no idea how to fix my corrupted ROM,
I tried following the unbricking guide but I can't so much as get my phone detected by my computer to even do anything with it.
Click to expand...
Click to collapse
You really need to research before you try to root your phone. Like a lot of research.
and when you brick it, you need to research to try and un-brick it. This stuff is easy, but its tedious, and if you're not ready to deal with hours of trying to fix your phone, you shouldn't been rushing into rooting.
All of the info is in that thread. Dozens of people have followed it and recovered their semi-brick.

martonikaj said:
You really need to research before you try to root your phone. Like a lot of research.
and when you brick it, you need to research to try and un-brick it. This stuff is easy, but its tedious, and if you're not ready to deal with hours of trying to fix your phone, you shouldn't been rushing into rooting.
All of the info is in that thread. Dozens of people have followed it and recovered their semi-brick.
Click to expand...
Click to collapse
Agree with everything you said. One click roots can be dangerous and tempting, as they lure people to an easy method, without having to learn the basics . . . and that's how the trouble starts. Especially when the one click root method is known to result in possible semi bricks.
If anybody wonders why HTC tried going to locked bootloaders, or constantly trying to increase the security against rooting, situations like this is why. People not wanting to make an effort to root by proper methods, or fix their mistakes, and claiming a "warranty issue".

[Q] [HELP] Soft Bricked i9505

I rooted my GS4 yesterday and had no issues at all until i tried to flash a MOD to obtain wireless hotspot, but what i didnt notice was the MOD was for a Sprint version GS4. I know know if thats exactly what made my phone brick but im pretty positive because it was during the reboot that the phone got stuck on the TMO screen and apparently remaining soft-bricked. I spent the rest of the night and all of today reading and researching how to fix it myself before coming here to ask for help, so please bare with me.
I have already attempted to flash the official stock firmware using Odin, but it displays an error everytime saying it failed and something about AUTH. Sorry if im sounding vague, i am on a back up phone to use the internet and forgot to right down the exact message.. Anywho, i tried wiping everything and redoing the process and i even tried to flash the appropiate PIT file that i found but it still displays an error and says failed because of some AUTH or SEC problem.
Ive been at this diligently for almost 12 hours. My brain is filled with all these suggestions and methods that i have tried to use to restore my phone back to factory, but none of them have worked. I can still get into recovery and all that, so im assuming that there is still good chance i could fix the problem?
Also i am starting to get myself more and more confused about whether the firmware i downloaded is the right one i need for my phone, it seemed so at first but now i see theres TONS of region codes that can determine the firmware version?
Sorry if im all over the place, but i just dont know which step to take next..
I appreciate any help that is given, and im even willing to pay (some) bucks or maybe even (btc) for someone to walk me through what i need to do or what im doing wrong.
Thanks in Advance

Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?

Toleraen said:
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Click to expand...
Click to collapse
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..

koolbreez12 said:
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
Click to expand...
Click to collapse
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.

Toleraen said:
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Click to expand...
Click to collapse
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.

error post

If you can get into download mode i would suggest flashing stock with that then rerooting that way the program downloads all of the nessacary stuff on its own.

koolbreez12 said:
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
Click to expand...
Click to collapse
Welcome!
Sent from my SGH-M919 using xda premium

[Q] Obviously it is time I ask for help...

Ok, so, I bought an HTC One M8 a couple of months ago. I got it because I had an HTC Evo 4G. I had that phone since release and I loved it. I knew everything about that phone from inside an out. Had my own bootup screens. Had everything the way I wanted it. That phone was with me through it all. I dropped it in the toilet and it was not even phased. I broke the screen a couple times, bought new ones and installed them. I even knew of the super secret instant boot up to the phones app list with a secret button combo. As far as I know this was not published and I could not find any mention of it on the internet. Anyway..I figured it was time to update to a newer phone. Which after this long I am getting kinda frustrated.
Long story short, I want to go back to stock. I installed CM 12, nightly s. I like stock best. The problem is I did not get S-off before i switched. From what I can tell I need it. I figured it would be easy as it was on my Evo. I only can use Sunshine. Which is fine but I need to get back to stock to be able to do that(non debuggable rom). I want to change to super CID but I need S-off. So I can install some of the roms I have. I installed two backups of my stock system but they are both corrupt for some reason. I have tried a couple other methods and have gotten the answers, MD5 not recognized or checksum failed. I am not sure what that means. It seems I need to get S-off to fix. This is a fraction of the stuff I have tried. Want to keep this semi short. I also wrote a better question and the site did not save my work when I tried submitting it. So, sorry if this is not up to par. I dont want to write it all again.
I am only coming her because I truly need help, I have searched far and wide. Have some intermediate knowledge and still cant figure it our after two months. I have used google and the search function on this site. Still need someone to point me in the right direction is all. PLEASE!!!!!!!!

First step -- need to get to know your device better
Post fastboot getvar all result (delete serial no. & imei no.) then we maybe able to find right stock backup or RUU or ROM whichever is available.

What recovery are you trying to use as well. You're still on sense firmware so it shouldn't have any issues going back but the problem I could see is what version of android the Rom is on.
Once you post your getvar as stated above then we can see what firmware you're using.

Really no one will help me? You just have to point me in the right direction. I have no where else to go...I have exausted my skills.

GlassGun said:
Really no one will help me? You just have to point me in the right direction. I have no where else to go...I have exausted my skills.
Click to expand...
Click to collapse
.Ryker said:
What recovery are you trying to use as well. You're still on sense firmware so it shouldn't have any issues going back but the problem I could see is what version of android the Rom is on.
Once you post your getvar as stated above then we can see what firmware you're using.
Click to expand...
Click to collapse
ckpv5 said:
First step -- need to get to know your device better
Post fastboot getvar all result (delete serial no. & imei no.) then we maybe able to find right stock backup or RUU or ROM whichever is available.
Click to expand...
Click to collapse
...?

GlassGun said:
Really no one will help me? You just have to point me in the right direction. I have no where else to go...I have exausted my skills.
Click to expand...
Click to collapse
You either missed the 2 posts previous to your latest; or purposely ignored the questions posed to you. We need more info in order to help you.
Also, its not clear to me that you even need s-off. Its not related to your recovery issues; and its not required to s-off to return to stock. You mention you want SuperCID (for which s-off is required), but you don't mention why you want SuperCID.

HTC Desire 816 without Update Option (SOLVED)

Ok guys i roamed a lot on the internet trying to get a way to fix a not so common problem(but yes a major problem) on the htc desire 816. Finally resolved mine and hope that it will solve yours too (note that having a super CID phone is a plus point, i have that, proceed at your own risk) which means my phone is not region locked
Please note this may lead you to bricking your phone if not done properly.
UPDATEDFollow the steps below:-
Download your version of stock ROM.zip or RUU.exe From HERE
If your one is in .exe format then simply connect your phone and run RUU.exe and don't follow the steps given below
Rename the file to 0P9CIMG only(dont change extension .zip)
Place the file in your Ext. SD Card
Turn off your phone
Enter into bootloader by pressing VOLUME DOWN + POWER
Your phone will automatically recognize the zip file and start flashing it
Be Patient
Delete the zip after your phone has succesfully returned to stock.
HIT THANKS IF I HELPED :good::fingers-crossed::good:

First off, thanks for the post I've been searching this everywhere. Unfortunately though while updating, I got this error message in recovery: "Package expects build fingerprint of htc/htc_asia_wwe/htc_a5dwg:4.4.2/KOT49H/37"a number"983.1:user/release-keys or htc/htc_asia/wwe/htc_a5dwg:5.0.2/LRX22G/510432.1:user/release-keys; this device has htc/htc_europe/htc_a5dug:5.0.2?LRX22G/510432.1:user/release-keys". I'm assuming 'a5dwg' means my phone is a asia wwe model and thus not compatible with the european recovery.img I downloaded from your given link? If so, where can I find a stock recovery.img for asia wwe model? (My phone is a Desire 816 dual sim with 4.4.2 kitkat, sense 6, software number 1.58.707.1, kernel 3.4.0-g4ff7e8c and baseband version 1.31.50.0624_2) Does anybody else know?

I'll post that soon if I find it
Sent from my HTC Desire 816 dual sim using XDA Free mobile app

First Thank you for your effort.i did what you said BUT
1. When i connect my phone in fast boot and type command adb devices it does not show my Device ID . However it flashed the CWM recovery in phone.
2. i backed up my ROM and then restore your Provided ROM it did not ask me to fix root.
3. Everything works great Wi-Fi vibration etc. No Problem at all.Phone was rooted.i tried to unroot but after reboot it reroot device again.
4. Then again i connect my phone in fast boot and type "adb devices" again it doest not show my ID.Again i flashed stock recovery by ignoring this.
5. i reboot my phone and downloaded the SW update which was 151 MB. When download was finished it checked my phone for Verify.
6. i got error there that "your are using modifying system please revert back to your stock ROM" so it did not update.
7. Please give me solution for this Problem.i did everything you said.Now tell me what should i do to overcome this Problem?
8. My device HTC Desire 816w [Unicom] S-ON.

replacing cwm with twrp
Dear
is it ok to replace the cwm with twrp to do the steps?

ade.l said:
Dear
is it ok to replace the cwm with twrp to do the steps?
Click to expand...
Click to collapse
NO dont do this as twrp doesnt work with cwm backups
you might end up failing in restoring the backup

After flashing CM-12, Both SIM are not working. Flashed stock L firmware but still problem is there... any solution?

mr.jxtian
pls help me out,
i did this cwm backup for my htc a5_dug..j_15 with baseband 1.13.3230.27.0303_13.19.3230.00D_F
build number 1.29.708.1 CL342310 release key...kernel version [email protected]#. htc sense6.0, software number 1.29.708.1
when i restore this backup my sims are not working...pls help

HTC Desire 816 dula Sim
Dear, I have HTC desire 816 Dual Sim
Software Information
Android Version 4.4.2
HTC Sense
6.0
Software number
1.56.401.1
HTC SDK API level
6.20
Baseband 1.13.3230.16.05.13.17.3230.00D_F
Build number
1.56.401.1 CL372006 RELEASE-KEYS
I am not able to update to lollipop. Should possible to officially update by this method ...plz reply
---------- Post added at 09:37 AM ---------- Previous post was at 08:50 AM ----------
jxtian said:
pls help me out,
i did this cwm backup for my htc a5_dug..j_15 with baseband 1.13.3230.27.0303_13.19.3230.00D_F
build number 1.29.708.1 CL342310 release key...kernel version [email protected]#. htc sense6.0, software number 1.29.708.1
when i restore this backup my sims are not working...pls help
Click to expand...
Click to collapse
DO hard Reset
I have same problem with Lenovo A6000 solved after reinstall customer recovery and hard reset after that.

Harris777 said:
First Thank you for your effort.i did what you said BUT
1. When i connect my phone in fast boot and type command adb devices it does not show my Device ID . However it flashed the CWM recovery in phone.
2. i backed up my ROM and then restore your Provided ROM it did not ask me to fix root.
3. Everything works great Wi-Fi vibration etc. No Problem at all.Phone was rooted.i tried to unroot but after reboot it reroot device again.
4. Then again i connect my phone in fast boot and type "adb devices" again it doest not show my ID.Again i flashed stock recovery by ignoring this.
5. i reboot my phone and downloaded the SW update which was 151 MB. When download was finished it checked my phone for Verify.
6. i got error there that "your are using modifying system please revert back to your stock ROM" so it did not update.
7. Please give me solution for this Problem.i did everything you said.Now tell me what should i do to overcome this Problem?
8. My device HTC Desire 816w [Unicom] S-ON.
Click to expand...
Click to collapse
IF your phone is not region locked and second that it is s-off then that's what will give you best results in these kind of things.

azhargalaxy said:
Dear, I have HTC desire 816 Dual Sim
Software Information
Android Version 4.4.2
HTC Sense
6.0
Software number
1.56.401.1
HTC SDK API level
6.20
Baseband 1.13.3230.16.05.13.17.3230.00D_F
Build number
1.56.401.1 CL372006 RELEASE-KEYS
I am not able to update to lollipop. Should possible to officially update by this method ...plz reply
---------- Post added at 09:37 AM ---------- Previous post was at 08:50 AM ----------
DO hard Reset
I have same problem with Lenovo A6000 solved after reinstall customer recovery and hard reset after that.
Click to expand...
Click to collapse
what are the problems you are facing?? please state them.
You'll be able to get OTA updates after this method and upgrade to lollipop ver 5.0.2

jakhar13 said:
You'll have to make sure your phone is not region locked and second that it is s-off. That's what will give you best results in these kind of things.
Click to expand...
Click to collapse
To tell someone, that doesn't even know the correct way to flash a device, to get S-OFF (which completely removes ALL security, so the flashing won't stop, even if it is a bad flash) is the most ridiculous thing I've ever heard! I know experienced users that bricked their phone gaining S-OFF and attempting to flash a file, they THOUGHT were for their device. So imagine an unexperienced user trying the same.
Also, maybe you should tell the user that S-OFF costs real money. You need to buy the sunshine app or for MTK variants a dongle to make it work.
It's really nice of you posting this tutorial, but please consider that most of the users in this section of the forums are inexperienced and seek help.

nukaru said:
To tell someone, that doesn't even know the correct way to flash a device, to get S-OFF (which completely removes ALL security, so the flashing won't stop, even if it is a bad flash) is the most ridiculous thing I've ever heard! I know experienced users that bricked their phone gaining S-OFF and attempting to flash a file, they THOUGHT were for their device. So imagine an unexperienced user trying the same.
Also, maybe you should tell the user that S-OFF costs real money. You need to buy the sunshine app or for MTK variants a dongle to make it work.
It's really nice of you posting this tutorial, but please consider that most of the users in this section of the forums are inexperienced and seek help.
Click to expand...
Click to collapse
Yes I do know that but you must also know that there is no other simple method right now to gain S-OFF without the sunshine app which costs 25$ at the time.
I know that they can end up doing it wrong, but the files that i've stated are stock roms or ruu files and are not that much of a problem if they know which one to look out for.
I should have told them that. Sorry my bad.
BUT THANKS TO YOU FOR STATING IT :good:

jakhar13 said:
what are the problems you are facing?? please state them.
You'll be able to get OTA updates after this method and upgrade to lollipop ver 5.0.2
Click to expand...
Click to collapse
Dear My phone is showing
*****Locked ******
A5_Dug PVT SHIP S-Off
CID-1111111
and also it is unrooted phone . Can you plz Pm me Step by step for updating to lollipop and Actually I am new here.

Thanks a lot bro... I done it .. thanks for your kind support.

azhargalaxy said:
Thanks a lot bro... I done it .. thanks for your kind support.
Click to expand...
Click to collapse
On December 27th you posted here that your phone was pure stock and you couldn't update. Now a few months later your phone is now set to S off which by the way requires you to preroot your phone first and now your set to SuperCID which takes even more knowledge to do through ADB/fastboot properly but your still "new" here? Now your saying your phone isn't even rooted and after asking the OP for his "supposed" help(which none of which is documented anywhere here with interactions back and forth between the two of you) your thanking him for what exactly? Coming across the one other "new" guy with an S off and SuperCID set device? This is all sounding very fishy and "real" people are being hurt here who don't have S off and SuperCID and are soft bricking their phones left and right from what I'm reading here. Shame on both of you (OP) for giving such incomplete advice and having more unlocked phone's then the rest and not even sharing your back and forth discussions here in XDA to inform the rest. This forum is one big joke but the people being hurt by it aren't laughing so neither will I !

thoctor said:
On December 27th you posted here that your phone was pure stock and you couldn't update. Now a few months later your phone is now set to S off which by the way requires you to preroot your phone first and now your set to SuperCID which takes even more knowledge to do through ADB/fastboot properly but your still "new" here? Now your saying your phone isn't even rooted and after asking the OP for his "supposed" help(which none of which is documented anywhere here with interactions back and forth between the two of you) your thanking him for what exactly? Coming across the one other "new" guy with an S off and SuperCID set device? This is all sounding very fishy and "real" people are being hurt here who don't have S off and SuperCID and are soft bricking their phones left and right from what I'm reading here. Shame on both of you (OP) for giving such incomplete advice and having more unlocked phone's then the rest and not even sharing your back and forth discussions here in XDA to inform the rest. This forum is one big joke but the people being hurt by it aren't laughing so neither will I !
Click to expand...
Click to collapse
I think you should consider reading my post where I've clearly mentioned "this may lead you to bricking your phone if not done properly & proceed at your own risk"
Nukaru has also already stated in a post above what i should have told regarding s-off and the info i provided.
If you notice i have asked people to post their specific problem in detail and also i had sent them PM's asking them the details of the problem. I've helped them as far as i could. I'm not a developer or someone with great knowledge in these things but what i've written is from my experience of the problems that i faced and how to resolve them.
The original post was completely different from what it is now which is much easier to do. People who were following the steps in the earlier version of my original post faced those problems that you are talking about.
I appreciate your criticism for this post and i also say that what you are saying is not completely incorrect.I'll soon edit this thread to give proper info to people in need.
:good:

http://forum.xda-developers.com/desire-816/help/stuck-htc-logo-screen-t3339751
Can you check this topic and help me? I see you are experienced.. I don't care what Android version I get, I just need my phone working again..
Would flashing Stock ROM help with my situation or not? and what kind of recovery do I need to flash this ROM? I have stock recovery right now..

jakhar13 said:
I think you should consider reading my post where I've clearly mentioned "this may lead you to bricking your phone if not done properly & proceed at your own risk"
Nukaru has also already stated in a post above what i should have told regarding s-off and the info i provided.
If you notice i have asked people to post their specific problem in detail and also i had sent them PM's asking them the details of the problem. I've helped them as far as i could. I'm not a developer or someone with great knowledge in these things but what i've written is from my experience of the problems that i faced and how to resolve them.
The original post was completely different from what it is now which is much easier to do. People who were following the steps in the earlier version of my original post faced those problems that you are talking about.
I appreciate your criticism for this post and i also say that what you are saying is not completely incorrect.I'll soon edit this thread to give proper info to people in need.
:good:
Click to expand...
Click to collapse
I genuinely appreciate your response and your desire to help people I'm sure is genuine but I did read your whole post and every single persons response one after the other. I learned that from my first days here at XDA that sometimes the responses gave me more info than the original post. Plus I'm OCD when it comes to reading. I also am not an expert/dev and have just learned by reading obsessively and dealing with my own device's issues over the years so I'm not saying you don't have the right to help here( we need more people to help.)
What I am saying is maybe you should be "reading" more tutorials from more experienced people and devs to get your information gaps fixed better before "writing" more tutorials that are (and I've read all of them to be fair) incomplete with dead links and more emoji filled than correctly filled. PMing is great and it's commendable that you are taking that much effort into helping people but that doesn't help the next guy that comes across this forum after you've gone to sleep and wants to get the information you and the other person communicated. I guess if the mods are fine with it I have to be but my advice is to read some of the better written tutorials and support forums then compare them to yours and you'll pretty much see what I'm talking about and if you don't then none of what I'm saying matters anyway. Good luck to you and I mean that.

thoctor said:
I genuinely appreciate your response and your desire to help people I'm sure is genuine but I did read your whole post and every single persons response one after the other. I learned that from my first days here at XDA that sometimes the responses gave me more info than the original post. Plus I'm OCD when it comes to reading. I also am not an expert/dev and have just learned by reading obsessively and dealing with my own device's issues over the years so I'm not saying you don't have the right to help here( we need more people to help.)
What I am saying is maybe you should be "reading" more tutorials from more experienced people and devs to get your information gaps fixed better before "writing" more tutorials that are (and I've read all of them to be fair) incomplete with dead links and more emoji filled than correctly filled. PMing is great and it's commendable that you are taking that much effort into helping people but that doesn't help the next guy that comes across this forum after you've gone to sleep and wants to get the information you and the other person communicated. I guess if the mods are fine with it I have to be but my advice is to read some of the better written tutorials and support forums then compare them to yours and you'll pretty much see what I'm talking about and if you don't then none of what I'm saying matters anyway. Good luck to you and I mean that.
Click to expand...
Click to collapse
Thanks you understood me really well. Appreciate your advice, working on it.

Solution for anyone with incoming calls issue after Marshmallow update

Hello everyone, I currently have AT&T HTC M8,
I recently came across this issue after I installed an Android M rom (SkyDragon, CM13 etc), I wasn't able to receive any incoming calls, they were all redirected to voicemail, I tried to change roms, change different settings, nothing worked.
Finally I searched for Android M's firmware and came across 6.12.1540.4, just search for it and flash it in fastboot.
Once you'll flash that firmware, do a clean install of TWRP recovery & ROM of your choice, it should work with all Marshmallow roms.
Not sure if it'll work if you'll restore it back to Android L (may get stuck in boot-loop or something, not sure).
I'm not taking responsibility if anything happens to your device, if you have any questions, feel free to write & I'll try my best to answer.
Thanks.

I think what you experienced is a kernel problem and not a firmware problem.
And even so, not everybody can do this as you need S-OFF.

Mr Hofs said:
I think what you experienced is a kernel problem and not a firmware problem.
And even so, not everybody can do this as you need S-OFF.
Click to expand...
Click to collapse
I never modified the kernel, it was always stock, for some reason, it worked for me after updating the firmware from 4.xx to 6.12.xx.
I agree about S-OFF, we really need that to mess around with the device.

rawfire said:
I never modified the kernel, it was always stock, for some reason, it worked for me after updating the firmware from 4.xx to 6.12.xx.
I agree about S-OFF, we really need that to mess around with the device.
Click to expand...
Click to collapse
That's probably a reason. If you installed international/wwe/gsm roms then AT&T/verizon/sprint it could be a problem. Have you checked the specific AT&T subforum for the M8....it's there for a reason because it holds differences.
I personally think you are one step ahead of the real solution. I think it's kernel related. Check the subforum for some info. See if it comes up with something.
I could be wrong......so don't hold that against me, just giving my thoughts

Mr Hofs said:
That's probably a reason. If you installed international/wwe/gsm roms then AT&T/verizon/sprint it could be a problem. Have you checked the specific AT&T subforum for the M8....it's there for a reason because it holds differences.
I personally think you are one step ahead of the real solution. I think it's kernel related. Check the subforum for some info. See if it comes up with something.
I could be wrong......so don't hold that against me, just giving my thoughts
Click to expand...
Click to collapse
That's really a thought, I'm definitely gonna check it and see if it's something related to kernel. Thanks for the suggestion.
And yeah, firmware upgrade was the last resort I guess lol,
Really appreciate that.

rawfire said:
That's really a thought, I'm definitely gonna check it and see if it's something related to kernel. Thanks for the suggestion.
And yeah, firmware upgrade was the last resort I guess lol,
Really appreciate that.
Click to expand...
Click to collapse
If you find anything please let us know. So we all can learn something if possible