yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] blackhawk:
Your initial complaint was it going screen after unplugging the charger?

In pocket turn ons... turn display away from skin.

A good case like the Zizo Bolt helps prevent this too; a good case is mandatory for this phone or it will be destroyed.

I really don't have any of these issues with my N10+'s. They run great, fast with good battery life, are stock, heavily optimized and customized.

They behave almost exactly how I want them to.

An Apple* can't touch them.

You need a basic understanding of the Android variant you own to do this, gained largely by just playing with them, but I read a lot as well.

But by all means go to an iPhone... they work.

*I've used Apples for work... never would have one for personal use. Far too limited and hamstringed... by design.
[Xiaomi Poco F1 Questions & Answers] vXtreniusX:
I'm looking for a way to boot fastboot images from the recovery mode.

I'm using OrangeFox recovery.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.

[*]Your warranty is now void.
[*]We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
[*]You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.

​

NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine.

If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.

CLEAN FLASH :

-Reboot to recovery

-Take Backup (Not Necessary)

-Flash your firmware(If required)

-Reboot To Recovery

-Flash the ROM

-Format Data

-Reboot

-- DOWNLOAD !! --
​

​

​

​

-Lineage OS

-AOSP

-Pixel Experience

-DotOS

-Others, I forgot to mention

WHAT'S WORKING??

WIFI

RIL

Mobile Data

GPS

Camera

Flashlight

Camcorder

Bluetooth

FM Radio

Fingerprint Reader

Face Unlock

NFC

Lights

Sound / vibration

KNOWN ISSUES

You tell me (none)

Bug Report:

As soon as the problem occurs, take a logcat!

For more READ THIS

​

​

​

-- CherishOS Source !! --

-- Kernel Source !! --

-- Support Group !! --

CherishOS for Redmi Note 8 Pro

Device: Begonia

Maintainer: Bishwo

Build Type: Official

Android OS Version: 12L

Security Patch: Sep 2022

Build Author: Bishwo

ROM Developer: Hungphan2001

Version Information

Status: Stable

Current Stable Version: 3.9.5

SELinux Status: Enforcing

Release Date: 2022-09-03​
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
Reserved #1
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
Reserved #2
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
Reserved #3
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] Cornshang:
After Clean Flash cherish-os-v3.7.5-20220520-1253-begonia-official-gapps.zip

My phone went into a bootloop TWRP.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] rrdyt:
hello bro, how can i submit a translation to this rom? Because I found that the Chinese in some places in the settings of this rom is incomplete.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
which rom were you using before you flashed this rom? if you were on 12fw or lower you need to flash 12.5 fw first before flashing the rom
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] saldor:
Is the front camera of newer RN8P is fully supported?
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] Kirasu2080:
After Xiaomi released R-Oss, kernel based on that now supported new front camera sensor.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] PokeHeadroom:
Same, I'm on miui 12.5 global, it uninstalled and replaced my orange fox with twrp which I'm not too fond of.

Update: I wiped everything except the vendor and the SD card. I forgot to wipe the cache and davik cache on my first attempt. Works now that I've done all of this
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
your phone bootlooped? did you format data? or flash dfe if you were using dfe previously?
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] PokeHeadroom:
Yeah, I hadn't completely wiped the cache, so I am assuming that's what caused it, second attempt worked, wiped everything except for the vendor. It's working great so far.

The only thing I'm trying to figure out now is, how do I disable the screen on at all times? I enabled that by accident
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
1. Go to Settings > Display:

Check the 'Screen Timeout'

Also check 'Lock Screen' and turn off 'Wake for notifications' and 'Always on While Charging'
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] shubhamcy47:
Unable to download the ROM and gapps. Download fails during the range 800-1000 MB.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] artscoop:
Hi, and thanks a lot for this ROM. Everything seems to work, **except** fast charging. On a 60W charger, it only charges at 2 to 4.5W. Original MIUI used fast charge (maybe 15W).

Edit: I discovered that fast charging is adaptive; it depends on the current charge. The fuller the battery the slower the charge. At 75% it charged at 10W, and at 95% it charged at 2W.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
this issue has been fixed in the latest build
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] KOOZA0_0:
4.0.5 rom does not work after rebooting, all I can do is screanshot and the only object on the screen is the pulsating battery icon ,time and gestures line on bottom
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
The build is fine. There is latest hotfix released just an hour ago, that has the bluetooth issue fixed. Download the new build and clean flash again.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] Difolt:
4.0.5 when i watch something on webpage then i cant watch anything on youtube, and the same the other way around, when i watch something on YouTube i cant watch anything anywhere else, and can you add QR core scanner to camera, three os an option on camera settings but is greyed out
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] KOOZA0_0:
Nothing change again, black screen , battery icon and time
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
You need to flash MIUI again, then clean flash Cherish.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
The media playback issue will be fixed on next update. QR Scanner to camera can be achieved by using third party camera like GrapheneCamera, but I will look into it.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] KOOZA0_0:
Unfortunately it doesnt work :<
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
What do you mean not being able to watch simultaneously on two different platforms? Can you explain the issue?
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
Can you share your flashing steps?
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] KOOZA0_0:
First I use miui then download rom to sd card, flash twrp, install rom, format data, reboot, configure the system and move files from the cloud, I also tried to delete vendor data cache etc. before installation, install magisk, use different twrp, or even do offline cofingurations with the default language. I tried to do it from miui or previous versions of cherish os, nothing helps. no matter what I do, the first reboot from the system level always fails. However, I don't think the rom is broken, I think it's my fault so thank you in advance for your help
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] artscoop:
Same issue the first time. Then I could not reinstall TWRP, so I installed OrangeFox to retry the installation, after a complete wipe. Then CherishOS worked for some time (maybe 2 days), then I rebooted today, and same error again (Interface program crash looping, so the phone cannot be used. Seems to happen when trying to display some notification)

CherishOS 3.9 worked without any major issue before.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
Use 3.6.1 latest TWRP & reboot to recovery. Then,

1. Wipe System+Vendor+Cache+Data+Dalvik

2. Flash the ROM

3. Format Data [type YES] | This will wipe everything you have in your internal storage

4. Reboot to System

After you setup the rom, go back to recovery and flash Magisk. Don't flash magisk directly after installing the ROM.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
Did u install any weird Magisk modules? Or try to debloat the System?
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] bishwofic:
You should install Magisk after you first boot into the homescreen after following through the setup screen. Don't flash magisk directly after installing the ROM.
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] KOOZA0_0:
Nothing change again :<<<
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] artscoop:
Did you test with the 4.0.5 Hotfix? (I only tested with the 4.0.5, crashes on the top bar interface)
[OnePlus 10 Pro] HessNL:
Hi there

I have installed CPU-z and I found out that we have a new scaling governor called Walt i couldn't found anything in the internet about is so I was wandering that someone know what it was or share a post where I can read about it
[OnePlus 10 Pro] cropaf69:
look into, Window bAsed Load Tracking
[Touch Pro, Fuze ROM Development] schwinny:
hello all.

I've flashed my raphael (touch pro) whit this rom: http://www.megaupload.com/fr/?d=ZSYWWUTZ

but there is a big issue.

My touchflo3D interface is defaillants.

there is no caracters in the sms menu when i wrote a sms.

in attachment, 2 pictures of the problems ;)

there is also a lot of errors like as:

"dw.exe has stop to ....." or "device.exe"

could you help me please?

(sorry for my bad english :( )
[Touch Pro, Fuze ROM Development] schwinny:
another strange thing's.

there is still the logo sfr upon startup that I flashed the phone.

It's normal?
[Touch Pro, Fuze ROM Development] DeepThought:
Where did you get the download-link from? Sounds like a faulty ROM for me or you didn't follow the installation instructions. Did you f.e. hard reset after flashing this ROM?
[Touch Pro, Fuze ROM Development] schwinny:
i forgot the hard reset :s

i test this and i tell you if it's ok or not ;)

For the link, it's a friend of me who gave me ;)

(on forummobiles.com)
[Touch Pro, Fuze ROM Development] schwinny:
apparatly, after a hard reset, it's OK.

Thank's a lot ;)
[Touch Pro, Fuze ROM Development] schwinny:
but there is still sfr screen on startup (and after, htc screen and after wm6 screen)
[Touch Pro, Fuze ROM Development] DeepThought:
You probably have installed some operator branded ROM. But I don't think someone on this board can help you with that since you downloaded the ROM somewhere else.
[Touch Pro, Fuze ROM Development] schwinny:
When i buy my phone, i've directly came here but there is no fr rom ;)

thanks a lot
[Touch Pro, Fuze ROM Development] DeepThought:
Yes there are. How about this for example: http://xdaforums.com/showthread.php?t=432516
[Touch Pro, Fuze ROM Development] schwinny:
i want to say, i want a official htc rom ;)

but thank's for the link

i' have the same probleme... :(
[Realme C25 / C25s] KastomKnuckles:
Let's say I once flashed custom on my C25, and now I've decided to go back to stock firmware. For Xiaomi phones, there is a MiFlashPro program, with which you can download the necessary firmware in a couple of clicks and return the phone to its original state by flashing all possible sections of the phone: system, recovery, etc.

Is there such a possibility for realme phones via other software?
[Realme C25 / C25s] gianonceu:
yes, through sp flash tool or our very own fastboot unbrick which you can get in our telegram group (t.me/even_discussion)
[Realme C25 / C25s] KastomKnuckles:
I ask you once again to give a link to the telegram channel, because I fall into the wrong group
[Realme C25 / C25s] gianonceu:
edited, i put the wrong link. sorry for the inconvience
[Zenfone 5 Q&A, Help & Troubleshooting] superflyboy:
I am faced with entering a password upon turning on this Zenphone 5 - but I don't recall ever configuring one!

I'ts saying: "Warning: Your device will be wiped after 7 more failed attempts to be unlocked!"

Is there any way to reset this - without losing the data? I need to recover some photographs from WhatsApp. (which were never backed up to Google or any other service)

What about connecting it to a laptop via USB? Any possibilities there?

Thanks!
[OnePlus 9 Pro] razercortex:
Hi guys,

Just made a breakthrough discovery!

To gain Widevine:

Crossflash EU firmware to your device with craznazn's MSM here https://androidfilehost.com/?fid=14943124697586337355, unlock bootloader but DO NOT update yet! Then, you want to flash magisk, reboot and turn on Zygisk and do whatever you need to pass SafetyNet.

Afterwards, you can upgrade, it should be a FULL system upgrade, not an incremental. It should detect root and download ~3000 MB. Install the update and reboot, you should get L1 now!
[OnePlus 9 Pro] TheKnux:
Nice find! Too bad I used the Indian MSM on my T-Mobile variant so I can't cross-flash anymore. 😭
[OnePlus 9 Pro] razercortex:
It also seems to survive MSM flashing, updates, custom ROMs, and bootloader locking/relocking :)
[OnePlus 9 Pro] TheKnux:
Do you think it'll work for me when though I use the OP9 Indian MSM?
[OnePlus 9 Pro] razercortex:
Not sure. You'd have to unlock bootloader first, then do a full system upgrade to check.
[OnePlus 9 Pro] TheKnux:
I'm already unlocked. It doesn't really matter though since I haven't given a yit about L1 since, ever. Just didn't know if you knew or not.
[OnePlus 9 Pro] freshlysqueezed:
Thanks! Worked!

Worked!

Thanks
[OnePlus 9 Pro] samdaman91:
I didn't use your method to get to c.63 (a12) for my TMobile OnePlus 9 pro. i dont know i can back to tmobile stock. Now I currently rooted and using magisk. All video apps work but I can't get L1 widedine. Is there another way?
[OnePlus 9 Pro] Appreciative:
Thanks for this. I have a 9 pro coming.

Edited

Thanks
[OnePlus 9 Pro] Reznor7:
I've had success using this method to keep L1 up to A12, but any attempt to upgrade to A13 downgrades Widevine to L3.
[OnePlus 9 Pro] immortalwon:
What is l1? What is widevine?
[OnePlus 9 Pro] TheGhost1951:
It is the security level of the firmware. It effects the certain apps like banking apps etc...
[OnePlus 9 Pro] Appreciative:
L1 is a drm (digital rights content management) state. L1 means the content is being digitally decoded or decrypted in a trusted environment. (I believe some of these are done in hardware with hardware verification only). It is the highest protection level.

In short, some apps will not work or will not play HD content without L1 state of drm. For us, when we lose L1, we go to L3. This could mean apps won't work at all, or they could be reduced in functionality.

Netflix for example, with L3, is limited to 480p video (however some bypass this with casting and get to 720p resolution).

Typically, when you unlock the bootloader of a phone, it will drop drm to L3 as it's considered a not-trusted environment.

This behavior is mixed by device, firmware versions and sometimes region (I have read some devices have shipped without Widevine keys to certain areas). This is bypass-able in some devices. For example, my 9P on oos11 is L1 with bootloader unlocked and rooted, using the standard magisk modules for Safetynet and clearing system cache.

Some phones will not regain L1 with unlocked bootloader (and maybe some versions of firmware also). They will be stuck with L3 Widevine until they relock the bootloader or unroot. And some firmwares are broken and will not have L1 because they implemented drm wrong.

On my 10T, netflix would not launch with unlocked bootloader. That may have been resolved by now but I was limited to L3 in drm checker (play store app) anyway.

For my 9P, I lost L1 (to L3) when I flashed Eu conversion to 11.2.2.2 - someone said that was an issue with early OnePlus firmwares where they implemented drm wrong or the key was problematic somehow. Whether that's true or not, I regained L1 when I temporarily unrooted and took the OTA.

This is likely going to be an increasing problem going forward as more devices go to hardware (only) attestation for everything. I suspect we will eventually see a magisk method of patching these apps and running them as modded apks. There used to be some patched netflix apks around. I think forced updates and signature checking made these obsolete. We may eventually see someone modify the individual apks, perhaps injecting a software mechanism for drm. Like taking the entire process of decoding, from an older device, into the apk itself. That might be overkill for the situation but eventually these bypasses we have currently, will not work anymore. We will be relying on some form of device spoofing, patching apks, standalone or redirected drm decoding, or a combination of all of those things.

That's assuming someone with that much skill is interested in doing all or any of that work.

Perhaps we will reach a point where unlocked bootloader or rooting breaks regular use so much that it's no longer worth the headache. It seems that's what they're going for. 'They' being app developers and phone manufacturers.

Here's a link to drm checker (DRM info) in play store if you'd like to find your current state: https://play.google.com/store/apps/details?id=com.androidfung.drminfo
[OnePlus 9 Pro] Reznor7:
Excellent summary of Widevine! I've tested extensively using every method I could find on XDA, and I've come to the conclusion that it isn't possible to attain L1 status in A13 with an unlocked bootloader on my OP 9 Pro.
[OnePlus 9 Pro] Appreciative:
Have you surveyed others on a13 to see their Widevine state? I have heard some users on custom roms (In crDroid group) using 13, claiming they're L1. I haven't verified that first hand, just saw it in threads and telegram groups.

If it's true that I can't retain or regain L1 in regular stock oos13, I will never make the move to 13
[OnePlus 9 Pro] yanggame:
1. https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_2.0

2. https://github.com/LSPosed/LSPosed.github.io/releases/tag/shamiko-126

3. In Magisk, hide Magisk, enable Zygisk, Configure DenyList (make sure all Google apps and Netflix are selected) and DO NOT enforce DenyList (for Shamiko to work). The Mount Namespace Mode should be Isolated Namespace.

4. Google Play Services, Google Play Store, and Netflix, clear storage. Restart your phone and give it some time. You should be able to search and find Netflix in Google Play Store (may need to try few times to force Google to check your phone), the Netflix should pass L1 too.

5. DO NOT use MagiskHide Props Config, it's not working at all.
[OnePlus 9 Pro] Reznor7:
I'm on stock A13 unlocked and rooted with Magisk. I did all of this exactly as listed and am still stuck at L3.
[OnePlus 9 Pro] yanggame:
You can try to reset you phone and finish all steps without login your account first. See if there is any difference. But it's probably will not work.

The best solution is to go back to stock OOS11 and flash Omega or Arter97 kernel since the leak is probably kernel side and only custom kernels can hide it.
[OnePlus 9 Pro] Reznor7:
I've done enough flashing for a while. I'll leave it to someone else to try. 🙂
[OnePlus 9 Pro] shadabkiani:
I got L1 with unlocked bootloader and Magisk.

I have LE2110. I used MSM tool (Global) to get back to OOS 11. It locked the bootloader; it always does. So I set up the phone offline (without connecting to WiFi or Mobile Data). Then I upgraded to OOS 11.2.10.10 version through local upgrade. Then opened Developer Options for OEM Unlocking. The option was greyed out and it asked to connect to internet. So I connected my WiFi for a minute or two until that OEM Unlocking was available. I enabled it, and disconnected WiFI. I DID NOT login to my Google account or opened Play Store. I rebooted to fastboot, and unlocked bootloader. Then rebooted. Then did the initial setup again (without connecting to WiFi or Mobile Data). Then I turned off and got the boot.img through MSM tool's readback option. (I was on slot_b so I got boot_b from MSM). Patched this boot.img with Magisk. Booted it temporarily and then through Magisk app, gainded permanent root by Direct Install. Rebooted. Enabled Zygisk from Magisk and Enforce Denylist, and rebooted again. Installed Universal SafetyNet Fix through Magisk and rebooted again. Opened Magisk and hid the Magisk app (just named it Settings; it installed and then showed root lost, but I just closed the app, and reopened new hidden Magisk again). Rebooted. Then I went ahead and connected to WiFi, logged in to my Google account and stuff. Checked from YASNAC and DRM Info and found that Safety Net passed as well as got L1.

I did not put any Google related app to Denylist.
[OnePlus 9 Pro] Appreciative:
You're saying you have L1 but still on oos11? If so, oos11 (11.2.10.10) L1 has never been a problem with unlocked bootloader, but thanks for sharing for others. People on oos13 and custom roms seem to be hit and miss
[OnePlus 9 Pro] ffejy462:
Oos 13 f20. Unlocked. Rooted Widevine L1.
[OnePlus 9 Pro] Appreciative:
Since this seems to be a HIT rather than a miss, can you detail the steps you took to arrive on oos13 f20 with L1?
[OnePlus 9 Pro] ffejy462:
I didn't implicitly try, but I've always had Netflix disabled as a system app.

Google services, Google Play store, Netflix and services on denylist in magisk.

I enabled Netflix, updated it, and logged on.
[OnePlus 9 Pro] shadabkiani:
Oh I see.

Update: I have now updated to OOS12 (C.48) through OTA. I still have L1.

I had rooted with Magisk so OTA was failing. I followed the guide on how to keep Magisk as well as OTA but it didn't work (I went to Magisk app, choose uninstall and restore images, DID NOT reboot, but went straight to system update and let it install, when it asked to reboot, I didn't, but went back to Magisk and chose install to other slot, then rebooted from Magisk. This failed to Qualcomm crash dump, so the system reverted to old active slot). Since root was already lost, I just tried OTA again and rebooted when it asked. The system was updated to OOS12 (C.48). As soon as it booted, I just turned off my phone. Backed up my current active slot boot.img from MSM tool. Turned on my phone. Patched that boot.img from Magisk. Booted it temporarily from fastboot. Went to Magisk app and got permanent root by direct install method. Rebooted. I checked from my Magisk app of the Zygisk and modules were active. Cleared data for Google Play Services, Play Store, and Services Framework (that's a system app). Then waited a few minutes for Play Services to download/gather/whatever data from internet. Then I checked from YASNAC and DRM Info, and SafetyNet passed as well as L1.

I will update to OOS13 in a few days, then post the results again.
[OnePlus 9 Pro] Appreciative:
Good info guys.

During your tests, were you orange-state'ing on boot? If so, have you tried the orange-state warning removal here (dropping in F11 abl.img) and seeing if that changes anything with OTA or L1 state in general? I'm not sure if the checks that are missing from F11 abl.img are maybe used elsewhere to check for bootloader state or if there's additional checks taking place and that's ONLY used at boot and never used again. Or if that missing check sets things up/props or similar values, for later, and they'll pass.

Having a reliable and repeatable path to success for L1 on oos13 is still helpful for many. Even if OTAs are not working, maybe that will be sorted out with more testing too