yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] pbergonzi:
Cannot clean flash N22. Clean flash N23.

---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------

https://xdaforums.com/showpost.php?p=71103972&postcount=4075

---------- Post added at 08:47 AM ---------- Previous post was at 08:45 AM ----------

Backup your user files first.

Download N23 and carefully follow instructions in OP to flash.
[ONE Android Development] Dward40:
pls link on n22 pls
[ONE Android Development] Mathorlaz:
I'm sad to report that I believe encryption and N22/N23 have some problems:

- Yesterday night I had installed N23 and got the black-screen-on-boot problem, being reported multiple times. When I flashed the firmware, it corrupted the encryption of the data partition, and I had to do a clean flash.

- Clean flash resolved the problem and I was able to get N23 back up and running. That is, until I tried to encrypt the device again. When I did, the black-screen-on-boot returned, rendering the device unusable. I can still access the TWRP and whatnot, but the ROM never fully loads.

I'm going to try to flash N21, because I think encryption worked there. I don't want to try to flash the firmware again, as I believe it could corrupt the encryption again.

I'll report back.
[ONE Android Development] WaAaOw:
can i dirty flash this rom ? i'm currently on latest stock rom.
[ONE Android Development] tpuserhp:
Thanks. I don't know much using manual control on camera. PMS camera is more suitable for me.
[ONE Android Development] fastleo63:
If coming from Lollipop ROMs (Cyanogen OS / CyanogenMod 13.x) you will need a full wipe.
[ONE Android Development] danieldmm:
It could be the problem of encryption, some commits entered related to that on latest build, the same is happening on my OP3 /OP3T builds... They have the same source this one, probably its that the issue.

Send with my OnePlus 3T
[ONE Android Development] Varinder Sahota:
Great rom ...... Nice to see the network traffic customisation .......Please add Carrier label as well ......
[ONE Android Development] xyomguix:
Sorry if this has been already asked :

Just upgrade from 18 to 22. But Magisk is not getting the root request from applications. What shall I do to make root work again ?
[ONE Android Development] Aditya Srinidhi:
You have to unhide root from magisk settings. Once you grant permission forever, you can hide it again
[ONE Android Development] mongoosesRawesome:
Unfortunately I'm still getting WiFi dropouts. Running latest n23 and have done the firmware flash.
[ONE Android Development] bernbutt:
Same here and I have reflashed 3 times
[ONE Android Development] Mathorlaz:
Hello again,

I've flashed N21 over the N23 I had, and I'm sad to report I wasn't successful in my attempts to get back to a functioning ROM. Even wiping system doesn't fix the problems. I now have a neverending boot animation instead of the black-screen-on-boot.

To give some context:

- I had clean flashed N21 and flashed N22 afterwards. I don't remember in which I had encrypted, but once I installed N23 I wasn no longer able to boot.

- I tried to flash the firmware and it broke encryption, even though it managed to fix the boot problems.

- So, since I had to wipe Data, I clean flashed N23 and got everything setup again. This was yesterday.

- After some hours of use, today, I decided to encrypt my device again, getting right back where I started, with the black-scree-on-boot problem.

I'll have to clean flash again, but I'm still trying to decide which version, or even ROM I should try now.
[ONE Android Development] capt.ron:
I get a permission denied error when using setenforce 0 command in terminal emulator. Suggestions?
[ONE Android Development] Redicus:
Flashing which firmware?

The c7 one? or the one in OP (Page 1)?

---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------

Which instructions? I have n22, should i update via OTA?

And by user files you mean my personal files?
[ONE Android Development] Ernestly:
I updated to N23 via OTA. Whenever I tap the battery toggle in quicksettings, System UI stops working. And ever since N19, everytime I awake my phone, the brightness changes to the max, but changes back to original brightness level. The auto rotate quicktoggle also toggles by itself.
[ONE Android Development] mongoosesRawesome:
Where do you find c7? I was trying the one in the OP
[ONE Android Development] shelby92:
So guys, I've had problems regarding the wifi as I said before. Now I'm starting to see some problems when I'm in 3g! To make it simple, the signal bar under the battery graph is 1/3 red and 2/3 green even though there is exceptional reception here.

I understand that I need to change modem but, I'm not sure what to do:

-do I need a full wipe to change modem?

-will changing modem change also my firmware? If so, how can I do it to keep on using this awesom rom (I'm worried about the firmware)?

-which modem should I use considering that I'm in Italiy for now?

Thanks in advance to anyone willing to help.
[ONE Android Development] red5pade:
not sure what happened but was on 23 and sat my phone on my bed ad then when i picked it back up it wouldnt turn on. i tried to clear the cache in twrp and still wouldnt, it would just go through the loading screen and then just a black screen. i tried a clean flash of 23 and still nothing. been letting it sit on the black screen for 30mins at least. gonna try flashing 17 and see if i can at least boot up. figures it would happen right before i go to sleep

---------- Post added at 05:33 AM ---------- Previous post was at 04:49 AM ----------

nope, tried multiple roms as a clean install and nothing is working. whatever happened, it screwed my ohone. gonna try returning to stock oxygen and then reflashing everything again.
[ONE Android Development] pbergonzi:
There are flash instructions in the OP. (Original Post--the thread owner's First Post--danieldmm the developer wrote instructions on how to flash the rom)

If N22 is working right now, then you can install the N23 OTA through the updater, and disregard what I said about following instructions.

By user files, yes--personal files. Always good to have a backup just in case.
[ONE Android Development] pbergonzi:
What rom you had before this one?

---------- Post added at 10:24 PM ---------- Previous post was at 10:21 PM ----------

https://www.androidfilehost.com/?fid=24389512218018449
[ONE Android Development] Mak_47:
M getting charge current of max 400ma. What can be done to solve this?

I'm on n23.

Can anyone Please Help!!!!!
[ONE Android Development] bernbutt:
N21 and N22 and now N23. WiFi and 4G problems. I had to restart the phone several times.
[ONE Android Development] red5pade:
well phone is bricked now. tried letting oxygen os format data all night because it wasnt finishing formatting. tried turning my phone off and now i cant do fastboot or recovery and the msm tool isnt picking my phone up. seriously concerned as to what happened last night. was on 23 watching a youtube video and the next phone wouldnt turn on
[ONE Android Development] o-l-a-v:
Sounds like hardware failure :S
[ONE Android Development] red5pade:
oneplus 3t :good:

honestly though, i have to pay taxes this weekend so i really dont want that just yet

im getting firehose communication failure in the msm tool. trying to google around on how to fix that crap now. idk if ill get it before work though
[ONE Android Development] lamchungning:
Am on N21.0. Set an alarm clock and turned off the phone during sleep. However, the phone was in a bootloop just before the alarm time that's set (the phone wants to switch on by itself and notify when the alarm time is reached but failed). Luckily can force switch off the phone by pressing power button for 10s and then it boots normally. Anyone else experiences this issue?
[ONE Android Development] Apfelsack:
Had the exact same problem on N19, I think. Phone was super hot when I woke up to my rebooting OPO. Haven't tried this on any other ROM version.
[ONE Android Development] pbergonzi:
Turn the phone off with charger plugged in and wait for the charge anim to start and to finish. Unplug phone and restart.

After completely booted plug charger in and check.

---------- Post added at 07:30 AM ---------- Previous post was at 07:28 AM ----------

Try official Lineage OS 14.1 and test phone without installing any other apps.

After a day or so or testing, you can re-flash TugaPower N23.
[ONE Android Development] nonoperez:
Don't know if this might help, but I read some time ago about a Chinese tool to flash hidrogen os to restore bricked devices. It was the last try for a guy and it worked for him, only that the oneplus bootloop image letter changed to Chinese. Sorry I can't be more specific, that's all I remember.
[ONE Android Development] counterfeit187:
I've used it.restored even when I couldn't fastboot. The only way to tell you connected is by Windows making a sound when you plug in the usb
[ONE Android Development] red5pade:
actually just got it. just finished reflashing tuga. took me forever and i still dont know what caused this and do not know why msm tool wasnt working. thanks for pointing me to the hydrogen thing though... might need to try that one next time because this gave me a crap ton of problems.

@op, im not sure what caused the issue to cause my system to fully collapse like that but i didnt have anything done besides f2fs. gonna give 23 another shot. more than likely it was something that will never happen again. prolly something was saving and got corrupt maybe... i have no clue.
[ONE Android Development] counterfeit187:
One issue that could cause these problems is when people think their phone is taking too long to boot after flashing a ROM and hard reset it in the middle of its boot process while it's actually setting up stuff
[ONE Android Development] milomak:
Are the rest of you getting the Google search using that high battery? Also why would there be 2 separate accounts of WhatsApp and gms
[ONE Android Development] mongoosesRawesome:
Have been on the c7 version since last night - it seems much better - thanks.
[ONE Android Development] red5pade:
Normally I'd agree but I'd let it got for a long time. When it first happened, I sat it down and let it turn on on its own for Prolly aabout 2 hours while I played ps4. Idk, oh well, good now
[ONE Android Development] rpereira77:
One small issue I have noticed is that Bluetooth is turned off when I reboot the phone.

Anybody else having the same issue?

Besides this I have no other issues.

All I can say is great work [MENTION=1427327]danieldmm[/MENTION]
[ONE Android Development] DjDiabolik:
When i dirty flash n21 over n16.1 i have need to be install magisk manager from playstore. You have installed this app ? I don't know if it's already included in latest rom.....
[ONE Android Development] milomak:
N23 - is do not disturb working?
[ONE Android Development] X-Nemesis:
Does selinux need to be permissive for Arise4Viper to work? If so, I can't run selinuxmodechanger because the phone in n23 isn't rooted. Is there a workaround for this?
[ONE Android Development] zaoms:
is there any option for flash this rom with no root access?
[ONE Android Development] Dicky Pratama:
Anyone find latest instagram app crash on tuga n23 ?
[ONE Android Development] pbergonzi:
No option for that. You can install latest Magisk over included Magisk then use latest Magisk uninstaller from Magisk forum.

If you're only concerned with hiding Magisk from root-detection apps, you can tell Magisk to hide itself and it ought to work for anything you want.

---------- Post added at 11:37 PM ---------- Previous post was at 11:36 PM ----------

Viper4Arise works out of the box, as this ROM is rooted with Magisk root already included.

---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------

That's an easy one--type "instagram" into the "Search this thread" box.

---------- Post added at 11:39 PM ---------- Previous post was at 11:38 PM ----------

That's correct--you need to manually install Magisk Manager. N23 has Magisk Manager already installed.

---------- Post added at 11:45 PM ---------- Previous post was at 11:39 PM ----------

I don't know, but if you type "do not disturb" into the "Search this thread" box, you'll get a really good idea.

I think.
[ONE Android Development] X-Nemesis:
Confused, I've installed magisk manager but it's saying my phone is not rooted. What do I do to get root back?

Running N23
[ONE Android Development] danieldmm:
Did you activated root for apps on Magisk Manager? By default it's set to adb only

Send with my OnePlus 3T
[ONE Android Development] androidarmy:
Hi every 1 one question, I want to install this firmware cuz It keep losing signal when on lte https://xdaforums.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907

But It said to use that specific TWRP so I downloaded and install flashily to install it but it said no root. When I flash SuperSU zip it end up in bootloop but I had a backup. Any1 know y it end up in bootloop when flash SuperSU?:confused:

Thanks
[ONE Android Development] danieldmm:
You only a need a proper twrp that can handle the modem flash, check link in OP for one TWRP that can handle that, tip: use -2 version of twrp

Send with my OnePlus 3T
[ONE Android Development] androidarmy:
Thanks Denieldmm. I'm already using the version of twrp that u made but I don't know y it still loses the signals the green bar is when I'm on 3g as soon as I switch to LTE its red.
[ONE Android Development] Manholas:
Its a big confuse. With magisk manager i havent root.
[ONE Android Development] X-Nemesis:
Definitely did not do that, whereabouts do I find that toggle? I cannot see it in Magisk Manager settings.
[ONE Android Development] danieldmm:
Wich version of Magisk you guys have installed? And version of Magisk Manager? The root option it's on Magisk Manager settings, called Superuser, superuser acess, there you need to allow apps to get root, by default it's settled to adb.

Send with my OnePlus 3T
[ONE Android Development] X-Nemesis:
I figured it out Danieldmm, looks like I didn't flash the phhsuperuser.zip so I did that and then was able to give magisk adb and apps root access.

Thanks for your help.
[ONE Android Development] Manholas:
Magisk 11.1. / manager 4.2.6. In settings i cant find this option, superuser.
[ONE Android Development] capt.ron:
Launch Magist Manager > Select Settings > Scroll down > Select Superuser Access under the Superuser heading
[ONE Android Development] Manholas:
Where can i find this zip?

---------- Post added at 06:07 PM ---------- Previous post was at 05:33 PM ----------

After a few tries and turns, I went to recovery and came back, and uppss became light !!! This Magisk got the full settings, all the options, with root and safe net. How to understand this !!! It will be magisk or will it be magic ??? !!! Mystery. Daniel Thanks for your answer and all your good work.
[ONE Android Development] ashwin.kj:
Workaround for the long boot time in the last few builds:

Since N21 or N22 the Magisk module responsible for ARISE/Viper was also setting the props needed to make it fully functional. But apparently when the flag for build.prop is set in Magisk, it takes a long time to boot. I am partly to blame for this as I had supplied the Magisk module from ARISE team. The workaround is to just let the Magisk module handle the selinux policy and add the props manually. The steps required are as follows:

In Magisk Manager, go to Modules and delete the current ARISE4Magisk module and add this View attachment ARISE4Viper2.84.zip one instead.

Make a back up of the current build.prop in '/system'. This is important, don't skip.

Modify the build.prop to add the lines in this View attachment arisesound_setprop.txt into it.

I have made the necessary changes to the N23 build.prop, so you can simply replace the current one with this one View attachment build.prop.txt after renaming it to 'build.prop'.

You should have significantly faster boot time now, but the downside is that if there is any error/incompatibly in the entries in the build.prop it will likely cause a bootloop and your only way out will be to replace it with the backup you have from TWRP or to restore a nandroid backup. So it's not elegant but it works for now and gives a much better boot time. Enjoy!

EDITED:

Sorry, but the build.prop I had attached had an error that was pointed out to me recently. I am updating the files accordingly. Basically both of them were missing equal signs. The View attachment CORRECTED_arisesound_setprop.txt and View attachment CORRECTED_build.prop.txt corrects them.
[ONE Android Development] binuraj82:
It takes a long while to boot
[ONE Android Development] zboq:
Hahaha can you belive this guy ?

binuraj82: read a post above yours

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] X-Nemesis:
Here you are

https://superuser.phh.me/superuser.zip
[ONE Android Development] radium22:
Not working for me. I received notification during DND hours and DND did not end per schedule, either.
[ONE Android Development] user334:
Hi guys!

I'm on N23 flashed over the N22 and experiencing some issues:

1) Scheduled disabling of notifies is not working. Only if I recreate the rule it will be activated but next time it won't.

2) Automatic brightness has brcame crazy. Escpecially when it's dark outside and there is some bright\dark things on the screen changing each other.

3) Mobile network started to dissapear. It might be fixed only by the reboot.

Can someone confirm this issues?

upd: I see the 1 is a common thing here. I did search wrong words...
[ONE Android Development] androidarmy:
3) if you mean losing signal when on LTE I can confirmed that look at screen shot

The first one didn't have any signal while the sim card is in.On the 2nd the green bar is when I'm on 3g n it turns red when on LTE
[ONE Android Development] ProjekterX:
Hi

I am on 23N and I can't open the color control app. It crashes immediately.

Also I have very often disconnects with the mobile network.

What can I do?
[ONE Android Development] androidarmy:
For mobile network use 3g instead of LTE and reboot that should solve the problem.
[ONE Android Development] pbergonzi:
Try N21. or LineageOS 14.1

---------- Post added at 04:17 PM ---------- Previous post was at 04:15 PM ----------

For Color Control type "color control" into the little "Search this thread" box.
[ONE Android Development] binuraj82:
Seriously after the N23 ota the boot time has significantly increased on my one plus one dunno about others, hence I posted it to know if anyone else has faced the same.
[ONE Android Development] user334:
What do you mean by "try"? I was using N21 before N22 which was before N23 obviously. And there was no such problems back then.
[ONE Android Development] red5pade:
[MENTION=1427327]danieldmm[/MENTION] my phone crashed again today while at work. i was just listening to pandora for about 4hrs and then my phone turned off and kept boot looping at the oneplus logo. i was able to go into recovery and clear the cache and it booted. i do not have anything done like kernels or mods and is a clean install from cm11s (after the hard brick i had happen monday) and went straight back to tuga. ill try and start recording a long log just in case it happens again.

i just wanted to bring it to you attention just in case you know what it was till i get a log if it crashes like that again. im using your 23 version too btw
[ONE Android Development] pbergonzi:
Well there you go.

---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------

Prolly gotta flash interim stuff coming from CM11. Go back to the OP and find the CM firmware and flash that first.

Then flash the version of Tuga you like and reboot to recovery. Then flash it again and reboot to recovery. Then flash the proper Nano Gapps, and reboot to system.

---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------

Did you catch that part "read the post above yours?" I think he is trying to say, that just the tiniest modicum of effort would have you do a search, or scan over a few posts along with the OP.

Scanning over a few posts, would have provided an answer to your question in the post placed blindingly immediately slap-on-the-forehead right before yours.
[ONE Android Development] user334:
I don't understand what are you trying to say to me :(
[ONE Android Development] pbergonzi:
N21 worked for you. Go back to it. Wait for N24 or something else.
[ONE Android Development] binuraj82:
Am extremely sorry dint read the post with replacing modules in magisk
[ONE Android Development] red5pade:
Did all that honestly. Everything worked fine for a day. May be my phone for all I know. May have something wrong with it physically... But I'll try and log if it happens again just in case
[ONE Android Development] pbergonzi:
If it don't work and ain't easily fixable, you can go back to the most recent stable setup you had and wait for another update. Danieldmm typically updates once a week.

I'm still on N21--mostly because it runs my beloved Dolby Atmos without issue.
[ONE Android Development] mikemaxe:
I use Dolby Atmos without problem with the n23
[ONE Android Development] ProjekterX:
Okay, thanks for the help. I fixed both problems. But still I think there is something wrong with wireless and mobile connection, because I also lose wireless from time to time and every time I lose wireless I also lose mobile connection.
[ONE Android Development] pbergonzi:
Thank you. I got other minor issue or two on N23 also, Dolby was the most important. Tried the Magisk module (b) and the apk (a) that is part of it, but never could find the Dolby App in my drawer.
[ONE Android Development] bernbutt:
How to install Dolby Atmos without losing root? I have tried on N21, N22 and N23 but ewery time I lose root!
[ONE Android Development] fastleo63:
I switched SElinux to permissive. Color Control opened and Magisk asked me root permission. I granted it, but when I set SElinux back to enforcing Color Control restarted to crash...
[ONE Android Development] jukyO:
Do I neednto delete superSu app after upgrading from v19 to v23? Install something in addition?
[ONE Android Development] strayedsoul2003:
Update and use magisk manager to allow,, or dl SuperSU sr3 (2017) and see if either addresses.
[ONE Android Development] ashwin.kj:
From his answer it seems he is installing it as a Magisk module. You can find it in Magisk manager under Download section. Haven't tried it, so don't know if it is currently working.

When you say color control restarted, did you mean that you opened it again? The app needs the permissive kernel every item it is opened. But if you make a change and have given it "Forever" access in Magisk then on every phone restart it will apply the setting on enforcing kernel. Repeating here, but to make any change or open the app you have to be on permissive.

Nothing needs to be installed. N23 installs the Magisk manager which all you need. As for uninstalling SuperSU app, you are right. The actual root is removed on installing N23, but the user app remains which you can simply remove.
[ONE Android Development] fastleo63:
Yes. If SElinux is set to permissive, Color Control opens correctly. I don't understand if is possible to make it work in enforcing mode... I have Magisk Manager.
[ONE Android Development] ashwin.kj:
It works in enforcing mode. But you can't interact with it. What I am trying to say is that whatever setting you have in the app is applied on reboot or as set, but if you want to make a change or use the app GUI itself you have to temporarily change to Permissive. But after making the changes you can go back to enforcing and the setting would be applied without any problem (even on reboot, or when it is required to apply it). Hope that makes it clear?
[ONE Android Development] fastleo63:
Absolutely yes. What I didn't understand was the difference between running Color Control app and applying its settings. Thanks a lot!