Database Develop

HTC One NFC missing after Flashing ARHD 8.0

Hi,
I've installed ARHD 8.0, and am absoloutely loving it so far, it is running like a treat, a particularly beastly one mind you! . My only problem is, since I flashed 7.4, which was my first ever Custom ROM, I haven't been able to get NFC. I clean flashed 8.0, hoping that would resolve the issue, but unfortunately I still have no NFC capability on my phone. I have enabled it in the settings, and I have also checked in my list of apps in order to see my Tags, but unfortunately that seems to have been wiped from the phone also, with no hope of getting it back.
I am on an International HTC One, which was previously locked to EE, on an ORANG001 CID, unlocked bootloader and have installed the ARHD 8.0, and flashed the same kernel in the boot.img file of the .zip for ARHD 8.0.
If anyone could help, it would be greatly appreciated, I would have asked about this in the ARHD thread but unfortunately I don't have enough posts and this same post didn't get much love in the Q&A thread .
Many thanks,
Omar

My NFC just works fine with ARHD 8.0.
I think you should ask in the ARHD thread itself.
Have you done a full wipe (data/system/cache/davlik cache) before installing it?

joshoon said:
My NFC just works fine with ARHD 8.0.
I think you should ask in the ARHD thread itself.
Have you done a full wipe (data/system/cache/davlik cache) before installing it?
Click to expand...
Click to collapse
Hi,
Yeah, I attempted to put this in the ARHD thread, but unfortunately I don't have enough posts to make any contribution in that thread atm.
Yeah, I did a full backup aswell of my 7.4, and also a full system reset of the davlik cache, cache, data, before I installed 8.0...
I am totally at a loss as to why my NFC has just gone, its not a urgent matter but I would like to try and get it back as it is undoubtedly going to be an important feature as contactless payment becomes more prominent.

[Q&A] [ROM][PORT][11.10] OnePlus One Stock ROM | CM11S | v8 | All Variants Supported

[Q&A] [ROM][PORT][11.10] OnePlus One Stock ROM | CM11S | v8 | All Variants Supported
Q&A for [ROM][PORT][11.10] OnePlus One Stock ROM | CM11S | v8 | All Variants Supported
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Will support 802w or 802d? I hope it so much!

Hi dd98,
Is it possible, port this rom's audio libs and all other audio stuff to other roms like sense based or aosp? Sound is very loud and clear. I never heard sound like that on my M7 before. Lots of rom,mod,irs tried but this is amaaaazing :highfive:

Waiting for 8.5
Hi DD,
I can confirm that v8.1 wont flash on TWRP 2.7.1.1
fyi,

I have rooted my 64 GB oneplus one and I only have xposed module but all of a sudden when I went into twrp and tryed to flash another ROM it kept saying error data storage or something like that so I turned my phone off and went back into twrp and restored my phone to the cyanogenmod main ROM and for some odd reason my service doesn't work... I used every method I factory reset my rom and still no service got a new sim card still nothing but I found out that the airplane mode keeps flicking on and off .. My WiFi works but not my data .. Idk if I should format the data in twrp .. Idk what to do HELP...
Sent from my A0001 using XDA Premium 4 mobile app

[Deleted]

JustCreateYou said:
I have rooted my 64 GB oneplus one and I only have xposed module but all of a sudden when I went into twrp and tryed to flash another ROM it kept saying error data storage or something like that so I turned my phone off and went back into twrp and restored my phone to the cyanogenmod main ROM and for some odd reason my service doesn't work... I used every method I factory reset my rom and still no service got a new sim card still nothing but I found out that the airplane mode keeps flicking on and off .. My WiFi works but not my data .. Idk if I should format the data in twrp .. Idk what to do HELP...
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have an actual OnePlus1 phone your in the wrong place
this is a Rom thread for the HTC One

wz11123 said:
Will support 802w or 802d? I hope it so much!
Click to expand...
Click to collapse
no i dont intend to support dual sim variants

What firmware do people use with this rom, and asop roms in general?
I am in the latest firmware available but get some WiFi issues on lots of roms. I wonder if my firmware is the problem.
Thanks.
Sent from my One

v8.0
nedd1 said:
What firmware do people use with this rom, and asop roms in general?
I am in the latest firmware available but get some WiFi issues on lots of roms. I wonder if my firmware is the problem.
Thanks.
Sent from my One
Click to expand...
Click to collapse
Currently i/we are on v8.1 just follow the instruction of DD on the first page dont need gapps its pre-installed on his ROM.

Work without s-off?
Is there any chance this rom will work without s-off? I have like the newest version of hbboot and I can never seem to get s-off to work. Really wanted to try this rom out.

patrickboston said:
Is there any chance this rom will work without s-off? I have like the newest version of hbboot and I can never seem to get s-off to work. Really wanted to try this rom out.
Click to expand...
Click to collapse
Well if you have twrp installed, why not backup your current ROM and give it a whirl.

Play service error
I've problems with Gapps. every time i reboot my phone i've a "google play service stopped working" error. now i cant connect to the store. some solutions?

Hulu issue with this rom?
I have tried this rom several times and I have found that everything works great except for Hulu. When I resume a movie or show, instead of starting where I left off, it starts to buffer then it starts back at the beginning. I have only had this happen with this rom. Has anyone else had this problem?

Gapps FC =(
Hello All, I just flashed TWRP 2.7.1.1, mounted system and cache, and Flashed this rom. Bootup was phenomenal. Once I got in, I got Google Location and Gapps FC. I dismissed them and proceeded into the rom. Everything else was perfect besides the occasional gapps FC popup. I attempted to connect to my google account in settings->accounts->google, but it keeps showing FC. Anybody have any idea what to do? Thanks a lot in advance, take care all.

How to install add-ons
I've installed the rom in my HTC M7, but I don't really know how to install the add-ons. In literally new in this, and I think I should flash the kernel using fastboot, but I'm not so sure. Could you please guide me through? Thank you

I don't see any option to customize lock screen. It's supposed to be on settings / lock screen / customize lockscreen, right?

Intermittent Mobile Signal
*** Tampered ***
*** Unlocked ***
M7_ UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 22 2014,01:10:58.1743
I am running a unlocked ATT M7_UL on T-mobile's network with CM11S which is just a beautiful and stable rom, I followed the intructions on installing CM11S, I wiped date/calvik cache, etc and flashed it using TWRP and everything works perfect on it except sometimes I lose signal and I am unable to change the network manually. When I check the APN sometimes the list of APN's is visible and sometimes there are none listed. But, when I try to manually set it and save it, it wont save. Wifi works grea, but no mobile data or ability to make or receive calls or text. I have tried wiping data and reflashing ROM and again it only works temporarily and then I lose signal again. Sometimes it does not read my sim card. I have tried the sim card on other phones and it works great. So i know its not the sim card. I did not install a custom Kernel, I am just using what came with ROM. Any one else experiencing this problem? Any suggestions?
TWRP v2.8.5.0
CM11S v8.5

best ROM
I've installed it and I really enjoy it! Great work. Its better than CM12 based od Lollipop...

New Update - BLU 06/01/2016 ??

Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01

Just got my phone in and yes i have that updates. so far it fails on the recovery screen on reboot. luckly holding power button and force reboot fixed it, not going to install the update again until i see its resolved..

hamilLewiston said:
Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01
Click to expand...
Click to collapse
I updated yesterday and all I see different is that radio app got updated to Nextradio

help.
I installed the update and now my phone doesn't boot. I go straight to recovery. Not quite sure what to do. Anyone have any suggestions?
The thing is that I just rooted with KingoRoot other day, voiding the warranty.

hamilLewiston said:
Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01
Click to expand...
Click to collapse
I've rooted and flashed tWPR recovery , so don't think can do such OTA update directly.
If anybody has latest ROM tWPR backup, I would like to try.

I restored y phone to original recovery and ROM, but after download and enter recovery, it shows ERROR

Im rooted. Unless its a big difference i dont see any means to uodate

Take out the SD card and then download the update. The phone get's funky if you have an SD card
---------- Post added at 11:22 AM ---------- Previous post was at 11:18 AM ----------
Insane PPC said:
Just got my phone in and yes i have that updates. so far it fails on the recovery screen on reboot. luckly holding power button and force reboot fixed it, not going to install the update again until i see its resolved..
Click to expand...
Click to collapse
If you have an SD card inserted to the phone, remove it before downloading the update. The phone doesn't react too well with an SD card.

AqueousBor said:
I updated yesterday and all I see different is that radio app got updated to Nextradio
Click to expand...
Click to collapse
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.

The Remedy said:
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.
Click to expand...
Click to collapse
Ditto. But I think we both know that's never going to happen.

xphyle1971 said:
Ditto. But I think we both know that's never going to happen.
Click to expand...
Click to collapse
tbh it looks that way but idk their was an official android 6.0 update for another BLU phone I saw on a website the other day but I cant think of which BLU model it was. So i'm still hopeful.

jason4962 said:
Im rooted. Unless its a big difference i dont see any means to uodate
Click to expand...
Click to collapse
Android security updates?
HandsomeFatty said:
Take out the SD card and then download the update. The phone get's funky if you have an SD card
If you have an SD card inserted to the phone, remove it before downloading the update. The phone doesn't react too well with an SD card.
Click to expand...
Click to collapse
Will the update go through even if using TWRP? Will it break root or cause a soft brick? I'm still running the original build that it shipped with (dated 26-12-2015 with 2015-11-01 security patch level).
The Remedy said:
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.
Click to expand...
Click to collapse
When did "they" (Gionee or BLU?) promise the Vivo XL would get MM?

rczrider said:
Android security updates?
Will the update go through even if using TWRP? Will it break root or cause a soft brick? I'm still running the original build that it shipped with (dated 26-12-2015 with 2015-11-01 security patch level).
When did "they" (Gionee or BLU?) promise the Vivo XL would get MM?
Click to expand...
Click to collapse
1. It wouldn't be Gionee doing anything even those this phone is based off of it. 2. Look at the sites that reviewed it, it's been posted many times that it was planned to get Android 6.0 . Android Central....check gsmarena it's out there if you look.

The Remedy said:
1. It wouldn't be Gionee doing anything even those this phone is based off of it. 2. Look at the sites that reviewed it, it's been posted many times that it was planned to get Android 6.0 . Android Central....check gsmarena it's out there if you look.
Click to expand...
Click to collapse
I can't imagine BLU is doing much ROM development. Gionee almost certainly has to provide them with the MM ROM since the Vivo XL is the Gionee Elife S Plus. BLU makes some changes, sure, but they likely aren't developing a MM ROM from scratch.
Anyway, I was just curious and not that interested in reading up on it. I got this phone to be a bedside clock (AMOLED screen FTW) and as a backup in case my DD runs into problems. It was $100 and a good deal at that price, but I have no belief that it will see anything but security patch updates (and even then, I don't expect much).

They arent going to update to 6.0. It used to say that on the Blu website but after the phone launched it was removed from the Blu Vivo XL and Vivo 5 pages.

Can anyone make a flashable zip? I'm using TWRP. I tried modifiing the updater-script, but no luck so far.

I updated the radio but went to an error and now the phone is stuck on boot menu. I can't flash it because it won't connect to any computer.

lemur394395 said:
I installed the update and now my phone doesn't boot. I go straight to recovery. Not quite sure what to do. Anyone have any suggestions?
The thing is that I just rooted with KingoRoot other day, voiding the warranty.
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/vivo-xl/how-to/rooted-kingroot-replaced-supersu-twrp-t3432078 .
Flash TWRP recovery and then load the backup from 2016-03. Then root with SuperSu.

any mm update ?

BLU on Google +
min1968 said:
I've rooted and flashed tWPR recovery , so don't think can do such OTA update directly.
If anybody has latest ROM tWPR backup, I would like to try.
Click to expand...
Click to collapse
If you check with these folks, they can help immensly!! BLU Development Team on Google+ a small community of BLU users that share information and have ALL kinds of information and links to STOCK, CUSTOM, and other ROM's, plus rooting tips, guides, and links to TWRP and CWM recoveries.

garbage display after flashing MM

Dear friends.
i have this n6 came from USA was running lollipop fine.
i tried to update MM 31E. all partitions flashed ok but now the display is weird. its not split screen but sorta garbage with 3 splits (see attached images)
i am sure its not hardware because the display is ok in recovery or fastboot mode even google logo looks ok.
i have tried to downgrade to 5.1.1 and upgrade to N but still the same.
tried to update qualcomm gpu driver update still no use.
flashed with FI roms and all carriers rom too but still the same.
please help me as am searching everywhere for a solution but no one seems to have this kind of problem.

instructor2 said:
Dear friends.
i have this n6 came from USA was running lollipop fine.
i tried to update MM 31E. all partitions flashed ok but now the display is weird. its not split screen but sorta garbage with 3 splits (see attached images)
i am sure its not hardware because the display is ok in recovery or fastboot mode even google logo looks ok.
i have tried to downgrade to 5.1.1 and upgrade to N but still the same.
tried to update qualcomm gpu driver update still no use.
flashed with FI roms and all carriers rom too but still the same.
please help me as am searching everywhere for a solution but no one seems to have this kind of problem.
Click to expand...
Click to collapse
Actually, I have read on these forums about a good amount of people having this problem. It seemed to happen to early iterations of this device, like purchased within 3-6 months after launch. From what I can remember about this situation is that running some custom kernels can fix it. I believe it might be Francos kernel and/or ElementalX kernel that alleviates this problem.
Also try using a kernel managing app like Kernel Auditor or EX kernel manager and change the CPU governor to Interactive, if it is not already.

christianpeso said:
Actually, I have read on these forums about a good amount of people having this problem. It seemed to happen to early iterations of this device, like purchased within 3-6 months after launch. From what I can remember about this situation is that running some custom kernels can fix it. I believe it might be Francos kernel and/or ElementalX kernel that alleviates this problem.
Also try using a kernel managing app like Kernel Auditor or EX kernel manager and change the CPU governor to Interactive, if it is not already.
Click to expand...
Click to collapse
thanks for the reply.
i will try when i get back to work.
will reply back

thanks for the reply.
i tried Francos kernel as well as ElementalX with all default in Aroma, still no success
i am trying to install Kernel Auditor cause screen. trying hard to press here and there in hope to get to file browser and install apk
anymore suggestions ?

Install custom ROM

instructor2 said:
thanks for the reply.
i tried Francos kernel as well as ElementalX with all default in Aroma, still no success
i am trying to install Kernel Auditor cause screen. trying hard to press here and there in hope to get to file browser and install apk
anymore suggestions ?
Click to expand...
Click to collapse
Log into the play store on your desktop and install the app from there.
---------- Post added at 09:31 AM ---------- Previous post was at 09:26 AM ----------
Looks like something in the display settings is off.

Lawstorant said:
Install custom ROM
Click to expand...
Click to collapse
tried cm13 . its giving error excuting updater binary in zip.
right now i am flashing 5.1.1 (currently on N) and starting from scratch.
stevemw said:
Log into the play store on your desktop and install the app from there.
Click to expand...
Click to collapse
it also requires to enter google account info into the phone
---------- Post added at 09:31 AM ---------- Previous post was at 09:26 AM ----------
[/COLOR]Looks like something in the display settings is off.
Click to expand...
Click to collapse
i thinks its maybe bootloader issue. not sure.

instructor2 said:
it also requires to enter google account info into the phone
But logging into the device manager will show which account was configured on the phone.
Click to expand...
Click to collapse

nope. after 48I, CM13 still giving same error.

so i m back. i flashed chroma but the problem remains same.

Just to clarify something, based upon the pictures, this device is an Engineering sample, isn't it? Does it work correctly when you reinstall the stock Android 5.x ROM on it?

Strephon Alkhalikoi said:
Just to clarify something, based upon the pictures, this device is an Engineering sample, isn't it? Does it work correctly when you reinstall the stock Android 5.x ROM on it?
Click to expand...
Click to collapse
yes, its a not for sale engineering device.
it was working just fine on LP. it all happend after the first upgrade attempt to MM.
after that, even the downgrade doesn't work.

instructor2 said:
yes, its a not for sale engineering device.
it was working just fine on LP. it all happend after the first upgrade attempt to MM.
after that, even the downgrade doesn't work.
Click to expand...
Click to collapse
Sounds like a hardware problem.

[Help] Unable to use custom ROMs on brand new 3T (touch non responsive once woken)

So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know

Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.

Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119

@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.

Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?

redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.

hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help

Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.

SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.