Just today, I changed this option on my classmate’s Redmi Note 8T (MIUI 11.0.11.0 PCXEUXM, Android 9) as a joke *(double notch simulation at the top and bottom)*, but it rendered the phone unusable.
My best understanding is that it sends the System UI into a crash loop. The phone detects that and doesn’t even let you see your lock or home screen. It will automatically reboot you into the Mi Recovery, where your only option is to **Wipe data** if you want to get your phone back.
This is a major problem that should be resolved, as developers that legitimately want to test their apps with a simulated cutout will also soft-brick their device. This can cause unrecoverable data loss.
Watch out for the **Smallest width** option as well – a value that is too small or huge will also result in a System UI crash loop, from which you can only escape from if you have USB Debugging enabled / authorized, wipe your data, or have an unlocked bootloader.
—–
Theoretical fixes:
1. If you have USB Debugging enabled and authorized, use `cmd overlay list` and `cmd overlay disable` to disable the cutout simulation overlay.
2. If you have an unlocked bootloader but you don’t have ADB enabled / authorized, boot into TWRP, mount system and vendor, then navigate to `/system/system/product/overlay` or `/vendor/overlay`, find and delete any files/folders related to Cutouts, and the phone should boot back up again, hopefully.
**Back up your most important photos with Google Photos (make sure to include folders such as Instagram or others that are important) and other files that you wouldn’t be comfortable with losing.**
How’d your mate handle you wrecking his phone?
The classmate is a girl. They were a little mad, but I helped her set up her phone again (as we wiped data) and once she got home, the photos she took with the regular camera app were backed up (thanks Google Photos!)
However, she mainly used the Instagram app for taking her photos and the Instagram folder wasn’t included in the Google Photos app. While a lot of pictures remain, quite a bit more have been lost anyway.
I’m known for tinkering with phones in this way, but I never expected an option meant for testing applications with simulated cutouts to bootloop a device. It has never crashed for me on either MIUI (Note 5 Pro) or AOSP/Pixel custom ROMs.
Did you have this problem before, or did you just try?
I fully take responsibility for this. Indeed, it was a bad joke that failed. I feel horrible for deleting her personal photos that she now cannot recover.
As someone that loves software and looking into its inner-workings, I sometimes give people advice on certain options such as gesture navigation or the new Control Center option in MIUI 12, but this occasionally involves a few jokes that are usually harmless (such as changing animation speed), or, in this case, what I initially thought to be harmless, simulating a second notch at the bottom of the display.
At the very least, I feel a little glad that I turned on the Google Photos backup for her when she first got her phone, otherwise, every single photo would have been lost.
Lesson learned. Developer options are not meant to be had fun with.
On a similar note, changing the Smallest width option, which a lot of people do to fine-tune the display elements’ size, can also immediately brick a phone if you set an arbitrarily high or low value.
IMO dev options shouldn’t be messed with. I once messed with MIUI optimization. Toggled off & on. It fucked up my sync settings and resetted premissions. Definitely a pain in the arse. I fixed it but it still gives me weird sync error messages
> Have a good day and enjoy tinkering safely
Thanks for the support. I was legit shaking, not knowing what to do in the moment.
Hopefully, she won’t hate me after all this, we’ve known each other for quite some time now. It’s our final year in school and we’re about to graduate next year.
Definitely not touching others’ phones for fun like this anymore.
Yeah it’s hidden for a reason. If it was meant for everyone to use then it would be out in the open.
I totally agree that Developer options aren’t for the regular end-user to mess with. I will definitely stop joking around with them.
However, a legitimate developer would still have to rely on these options to test the apps they’re developing with a simulated notch, to ensure that everything is properly visible and not going into / through the notch.
Not all developers may have an unlocked bootloader, so it would be as much of a data loss to them as a regular end-user.
As someone learning and deeply interested in software development myself, I’m concerned about this not just because it could happen out of a joke like this, but it could also occur when it was meant to be used for legitimate purposes.
It is probably possible to change it with ADB while in recovery. For example, search for “cutout” in this site [Useful ADB Commands (zsmith.co)](https://zsmith.co/adb.php)
EDIT: the Display Cutout option enables an overlay, which could be controlled by the `cmd overlay enable/disable/list` commands. The overlay service would not be running in TWRP or the recovery. If it were instead a prop, your solution could work.
—–
Does ADB automatically work in the Mi Recovery as well? I know it works in TWRP but I don’t think the default Mi Recovery would have it on.
It gives you an option to connect to a Mi Assistant or whatever else it is, but I don’t think that’s very useful aside from also being able to wipe and re-install the firmware.
Note that the bootloader was locked, TWRP couldn’t have been installed.
I tried booting into Safe mode by holding volume buttons during booting, but not only did it not work, it wouldn’t have reset the cutout options anyway.
That’s why we use the simulator that comes with Android Studio. Not to mention that any physical phone being used for testing development isn’t a phone being used as a daily driver. It’s literally a test phone, if anything gets fucked up it’s not a problem.
You’re right, fair point.
Developers that may not be capable of running the Android emulator on a lower-end PC might have to rely on their phone, but that’s probably not very likely.
Regardless, in the odd chance that anyone else thinks it would be a good joke to put a second notch on the display, hopefully, they’ll see this post and not end up doing it. It’s incredibly painful to do this to someone else’s phone.
On my Redmi Note 9S (MIUI 11, Android 10) double cutout si working fine. I wonder why it resulted brick on your classmate’s phone.
It might specifically be a problem with the Note 8T then.
I’ve seen some thread about this on other phones, so I think it depends on some settings.
Saw some threads on the Galaxy Fold while researching it. I have a feeling it might be a device-specific or MIUI version-specific implementation issue in the System UI.
When I switched to the Double cutout, the display went totally black. I could not even blindly tap on the same place and restore it, I tried that immediately.
After rebooting once, the phone would still not display any UI – it was pitch black. After subsequent reboots, I would see a bluish-gray line at the bottom of the display, with a loading spinner in the center, which looked like the one you get when the phone is restarting. Then it would throw me into the recovery.
I could also hold the power button and get to the power menu, which is weird, considering it’s supposed to be hosted by the System UI. If the System UI wasn’t crashing, why would the phone not display the UI / bootloop then? (Unless MIUI doesn’t have the power menu in the System UI)
She doesn’t mess with her settings much, so I don’t think it would have been caused by any of the settings options. Not sure though…
Also add the “smallest width” option in there!. Just don’t accidentally type 4 digit numbers or your phone will fuck up.
Did that once to myself. Thankfully, I have a good routine in flashing ROMs, takes like 30-50 minutes for me to set my phone up again.
Definitely wouldn’t be happy to have done this without backups though! I see lots of people changing the Smallest width. A tiny mistake like this could cost you a factory reset and data loss.
Same goes for dpi, I’ve seen two phones bricking because of that option
Well, you’re right. I was there, accidentally put 4500 instead of 450. Black screen and when restarted, goes to bootloop.
Resorted to factory wipe and some important documents and photos lost.
Learned my lesson, NEVER EVER TOUCH DEV OPTION
I have a Redmi Note 8 (Note 8T without NFC) running on that same UI and Android version and it works fine.
Is it a coincidence that i actually tried those settings randomly on my phone before reading this article.
Actually I was just messing with the animations scale, but this Display Cutout feature intrigued me so tried it and now my phone is in unusable state until it factory reset the phone.
And the most unlucky part is I thought of enabling the developer options but unfortunately I haven’t enabled it, now I am paying the price for that.
What phone do you have?
I’m getting mixed answers from people that have tried it. It works for some while it also crashes for others. It also persists through reboots, so no way to get rid of it unless you had USB debugging enabled or other shenanigans.
Really odd… Must be either some minor version differences or really something being wrong with specific phone configurations.
Thanks for letting me know!
As far as I know, the 8 and 8T share the same internals (they have the same XDA forums page), so that’s very interesting. Have you also set it to the double cutout option? Do you not have updates available?
This exact thing happened to me a month ago. Its not my fault I like to experiment with developer settings, its their fault for pushing an update with this kind of failure.
I also messed with display cutout before and it didnt crash. I messed with it because it would make the notification bell go to the right side instead of unnatural left side its on default because I have a phone with a notch.
I messed with developer settings ever since I got my first Android and not once was something even remotely able to cause a soft brick. Just stupid MIUI things I guess.
I managed to recover the phone without the factory reset. There is a small window of opportunity when it boots where you can press the power button and it will turn off or on the screen even tho the screen is black you notice its not completely black like when the screen is off. Also you can hold the power button and it will show you those power options like airplane, silent, power off etc. But those option are only available for like under 10 seconds, then its reboot time again.
So i just rebooted it 100 times and fucked with power button like that and luckily on one boot I managed to make the screen appear normally. Then went straight to display cutout and switched it back.
Mine is Redmi 7(onclite)
Currently I am banging my head for some alternatives but found none.
Since i haven’t enabled the usb debugging its device not detected but when I am in fastboot mode device is detected, so checking if any alternative is possible through fastboot!
Note 8T doesn’t have android 10…
Yes it’s on the double cutout option, with no updates available. I’m on MIUI 11.0.9.0 Stable (PCOMIXM).
The only difference between the two it seems is the 8T comes with NFC and a fast charger in the box. I got only a 10W charger.
EDIT: Sorry but double checking within my About phone, I actually have Android 9.
I’m glad you managed to solve it that way! Very creative!
I also mess around with Developer options all the time, this was very new to me. I agree with you in a way – experimenting with Android when you know what the options mean is fun in our own way. Messing around inside Developer options on others’ phones is a different question, but still, as a software developer, catching issues like this is, while fatal, still extremely valuable information.
I turned this option on many times, in fact, used it as a way to force rounded corner rendering on Pixel-ported software with a custom cutout simulation overlay.
I do way more technical things with Android, yet a simple cutout overlay caused such chaos…
Well, it happened, lesson was learned, not going to touch developer options on others’ phones anymore.. Nobody should have their memories erased due to such mistakes.
Damn, Hopefully i can also recover from this without formatting the phone.
I will leave the phone for today night and see if there will be any progress
I assume you have a locked bootloader as well :/
[Check this comment:](https://www.reddit.com/r/Xiaomi/comments/iskxed/warning_do_not_change_display_cutout_in_developer/g59jmgw/)
> I managed to recover the phone without the factory reset. There is a small window of opportunity when it boots where you can press the power button and it will turn off or on the screen even tho the screen is black you notice its not completely black like when the screen is off. Also you can hold the power button and it will show you those power options like airplane, silent, power off etc. But those option are only available for like under 10 seconds, then its reboot time again.
> So i just rebooted it 100 times and fucked with power button like that and luckily on one boot I managed to make the screen appear normally. Then went straight to display cutout and switched it back.
I think she might also have Android 9, I think I have just been remembering incorrectly. Thanks for the heads up!
My bad – I was remembering incorrectly. It is on Android 9.
Thanks for the correction!
> MIUI 11.0.9.0 Stable (PCOMIXM)
They’re running MIUI 11.0.11.0 PCXEUXM on Android 9.
Thanks, I am just trying that now.
I was able to find that 10 secs window and select Power Off.
Did you make sure to tell him that is was just a prank, bro?
I don’t have that update yet. Hopefully the next update would be MIUI 12.
The Note 8T is actually quite a solid device. It was my recommendation for this classmate and 4 other people as well. They’re all very happy with the phone, especially for the price they paid. MIUI 12 brings some nice improvements to the gesture navigation and the UI in general, it will probably be an even better of a recommendation for people that want a really cheap phone without missing out.
Yes! I’ve searched so hard for such a cheap phone with good specs. Samsung phones are overpriced when compared with Xiaomi phones spec for spec.
Try it out let us know if it worked for you too
I think its just because this is a MIUI ROM makes it not good for messing because MIUI is unstable buggy ROM. Thats just my experience from owning. Out of nowhere the display cutout option soft bricks your phone, while it didn’t before when I was changing it. So just MIUI things..
fuck me lol, I should’ve seen this earlier, I am not looking for a solution but so far it seems like factory reset is the way to go 🙁
EDIT: I gave up, I just resetted my phone. I’m never touching Developer Options when I’m bored at 4am ever again
just tried this and I managed to power off the phone and boot it up again but the problem still persists. fingers crossed that i’ll access the settings app or something
also try just pressing the power button, or press it a couple of times before it reboots to recovery again.
okay, so when the power options show up, what do you do? do you wait or did you select an option?
It must be on a phone by phone basis because I’ve done it multiple times on my Redmi K20 Pro and i’ve never had a problem. Just doesn’t do anything for me
Im not sure but there’s nothing you can do there except power it off which is nice I guess because you couldn’t even do that.
What I think did it for me was not holding the power button but pressing it to turn of the screen, then pressing again to turn it on. Even though its black you notice it. When you lose that option you try again.
Playing like that with both options for 100 times and somehow it booted normally.
Good luck.
One time I changed the display PPI with adb and got the bootloop crash thing into Mi Recovery. I was able to send `adb shell wm density reset` in recovery and after restarting, it fixed. So, that’s why I think it’s possible to send commands in recovery.
You can change it back in recovery if you have adb on
Oof
Thanks for the warning, i have MI9T, i thought about trying that but im glad i didn’t.
well it didn’t worked out for me, I was only able to Power off the phone.
I have tried it for like some 30 times and got fedup, so finally just formatted the phone and its working fine now.
The first thing i have done is enabling the developer options, just in case 😛
Hope you weren’t interested in her cause you’ve been FRIENDZONED! 😉
Oh, interesting! Had no idea that could work. I stand corrected! If only I would have known this before…
Had no such intentions 🙂 They are taken already.
Make sure you enable USB debugging too
good day sir what command do i use to set it back to normal
settings put secure display\_cutout\_hide\_notch 1 or
settings put secure display\_cutout\_hide\_notch 0
im having this problem right now
Those commands are for hiding the notch.
If you have ADB enabled, use `cmd overlay list` to get the list of overlays on the device. Find the cutout overlay you enabled (enabled overlays have a * before their name), copy its full name, then use `cmd overlay disable` to disable said overlay.
thank you for responding
will this work if i dont have my usb debbuging enabled and my bootloader unlocked? as long as i have an access to adb in my computer?
You must have USB debugging enable beforehand to use the ADB commands.
Otherwise, you need to have the bootloader unlocked and TWRP installed.
If not, I think you’ll have to factory reset.
Can I get confirmation u/xezrunner?
Someone in the comments said regular ADB comments apparently work just fine in Mi Recovery, although I can’t verify that. Try accessing ADB through Mi Recovery first. If that fails, a factory reset seems to be the only way.
If ADB does work in recovery and you can boot into recovery without a passcode, that’s a serious security flaw
WOW great Bug, great write up. Not sure what class you were in but your great at software/hardware quality assurance.
Hey, the same thing happened today with my Redmi Note 7S. I just updated to MIUI v11.0.4.0 i guess and was checking what the update has brought. Now, my phone’s screen is all black and in the same manner as you said, the phone restarts itself automatically in loop, displays blue line with loading spinner. Any way out?
Hi! [Check this comment.](https://www.reddit.com/r/Xiaomi/comments/iskxed/warning_do_not_change_display_cutout_in_developer/g59jmgw/) Good luck!
Hi, I just happened to do the same blunder and now I’m locked out. The exact same thing as OP described is happening with my phone. How do I get the reboot/ power off option as you said? At the very first, I got that option and I pressed power off. Still, the rebooting thing continues and I don’t know how to get the power options again
I hope people commenting on this did not try it out on purpose. I’m very sorry that this is happening to you as well.
I think your only chance is to keep trying the method above – they said it took a lot of trial and error, maybe you’ve got to do it multiple times with different button press combinations.
If you can’t get this to work and you have a locked bootloader, your only option might be to use the Wipe data option in the Mi Recovery.
I’ve been doing as said by the person above. So far, no luck. It’s getting boring now and seems like it won’t be fixed that way. Still gonna try it a few more times. Last resort will be data wipe
Thank you
Please help me. Phone got into bootloop after changing the cutout options.
PS. Device- Redmi note 5 pro
unlocked bootloader, stock recovery
Please help, I don’t have any backup. I need my data.😭
Download TWRP for your phone on a PC and use `fastboot boot` to temporarily boot into TWRP.
Find the Mount option and check system and vendor.
Now go to the File Manager. (in OrangeFox, it’s the first tab)
Navigate to /vendor/overlay and remove the cutout folder you activated.
Good luck! Reply if you have any questions.
It says it can’t be removed as the file is readonly. please help
Make sure you enable modifications to the system partition when TWRP boots and try again.
EDIT: Magisk wasn’t needed.
Thankyou very much. I did not allowed modifications that’s why it didn’t got removed. After deleting phone booted up perfectly fine.
Thankyou again.😁
Very glad you managed to solve it! Good thing you had an unlocked bootloader!
Previously I had changed the dpi to very high, so it got stuck in bootloop like now. Then I had to unlock the bootloader to solve that, but that wiped my data😓 That’s why I have an unlocked bootloader.
I’ve learned a lesson now, that we should unlock the bootloader as soon as we buy the new phone.
I’ve just done this to my Note 8, I’m pissed and it’s half 11 in the night and I can’t sleep because this damn thing won’t turn off, is there no way to?
You can’t connect the phone to the PC Suite to retrieve the data??
You can’t gather data from the stock recovery firmware or any other special modes.
If TWRP can be installed, it can access the internal storage even if the phone can’t be started.
In this case though, the bootloader was locked and the phone couldn’t be modified.
You can turn it off if when it is on you hold the power button and you get the options of airplane mode, mute, restart and turn off.
Then you just have to press turn off.
It was Bootlooping. I can’t get into Android and now the battery is dead
bro i hqve same problem in my note 5 pro device i have turned on the double screen cutout options and my mobile is now in crash mode .i have pitchblqck recovery any suggestions please
Read the bottom of my post specifically mentioning TWRP. It it possible to delete the cutout overlay.
bro i have tried this already but it doesnt work.
i didnt found that you hqve mentioned in your process
Did you delete the right overlay folder? Try deleting all of them, from both places.
If that doesn’t work, try issuing the ADB commands within TWRP.
how to do this pls suggest me
**COPIED FROM MI COMMUNITY THREAD**
I hope this will help, this way you can recover your phone without factory reset.
hello every one, First of all, forgive me for my bad English.
I faced this issue last night and after all day that I search for fix this problem,finally I fixed it. My phone is locked bootloader and unroot. You must download adb and fastboot and install it on your pc then connect your phone to pc, open adb command prompt. Since the phone is in boot loop,recovery menu appear and you mus select restart, after a secound type “adb devices” in command prompt and you must see this result: “List of devices attached
17eea8dc device” ( Note that the phrase device must be written, not sideload.In fact, you have little time to type the command because the phone does not boot and returns to the recovery menu again. ) After the “adb devices” command and make sure that the phone is not in sideload mode, type “adb shell” command and after it type this 3 commands one by one to unistall display cutout settings: (after each command you must see “Success”)
pm uninstall –user 0 com.android.internal.display.cutout.emulation.corner
pm uninstall –user 0 com.android.internal.display.cutout.emulation.double
pm uninstall –user 0 com.android.internal.display.cutout.emulation.tall
after that, type “exit” to exit adb shell, and then type adb reboot and your phone bootup and you can access to your user data. good luck.
Thanks for the information! This is a less brute-force way compared to deleting the APKs themselves.
Should note though, this will only work if ADB was enabled and authorized.
i tried, but adb cant read my devices when its on recovery mode, i also tried spamming adb devices after pressing reboot
but still no luck
Try when it’s booted and showing loader. There you can have your 15 seconds to execute commands.
you can start the phone in safe mode and then go to developer setting and set **Display cutout** to device default. reboot and every thing will be OK!
for start in safe mode select reboot in mi Recovery mode. Once your device initiates the reboot sequence start tapping on where the menu button reside. Keep tapping on it until the lock screen is displayed. You should now be into Android Safe Mode.
Did you get this problem and solved it like that or is it just a theoretical solution ?
Cause i have the exact same issue (double outcut into crashloop), I am able to boot my phone into safe mode, but even though there is this “safe mode” message at the bottom left of my phone, the screen is still completely black except this, and I am not able to do anything more than in normal mode, plus it only lasts for few seconds then my phone reboots back to the recovery menu.
It’s been 5 days since I’m rebooting non stop, trying everything I can do but I didn’t have u/stonded ‘s luck :'(
All I can say is good luck.
Try it out, when you have that window of oportunity where you can press power to view power options when it boots then try pressing shit then, press the screen, do all kinds of shit.
If it doesnt work you still have factory reset in recovery to fall back to I think.
This was the first time the phone fucked up like that on me. And last week was the second when I was just casually listening to Youtube and all of a sudden the phone began bootlooping and restarting but never reaching over the point of mi logo.
I again barely salvaged it by doing all of power button presses. Luckily again.
Ive had it with their shitty software.
Ive installed a CustomROM Lineage OS now, and I am so pleased. Fuck Xiaomi and fuck MIUI worst fucking ROM of all goddamn time.
Good luck again, just try all kinds of combinations when you have that windows of opportunity,. You can just press the power button a couple of times, you dont have to hold it. Swipe on the screen pretend like its viewable. Just be creative and hope for the best.
Well, thanks mate, guess I’ll try my best !
How can i use and apply ADB commands my friend? I have no idea about coding.
Good morning. I had the same problem, but there is a last option, which is to contact Mai. Can this option help without going back to software or wiping the phone data? Please help
This happened to me just now, glad I discovered this thread. I have very important things in my notes and there’s no way I can lose them. Can you explain how you managed to fix it? I read what you said about turning it on and off many times, but I still don’t get what exactly I’m supposed to do. Mine doesn’t even get the black screen anymore, it directly cuts to the loading thing (the spinning circle, which eventually gets the phone to the xiaomi recovery scren).
How do I do that? I’ve tried accessing the fastboot, but no luck in that I guess.
Same problem here, Any updates? Did it work?
Update?
Recovery is accessed by holding the Volume Up + Power buttons together, preferably from an off state.
Any updates?
Yeah I know that, but how do I access adb through that. sorry if that sounded stupid lol ive never messed w adb and all of that stuff before
In that window of opportunity you need to press power button and just get creative with it. You can notice you are doing something because the screen is not completely black when you press power. Also you can hold power button and it will show power options but that doesn’t do much except you can power it off so it doesn’t constantly reboot.
In that window my phone somehow managed to boot normally by pressing the power button countless tries I think I was very lucky.
Good luck.
alright, will try that. i’d reset my phone but months of daily notes in the notes app, including very important shit will be lost, and i dont want that. also i had a cool evie launcher setup which i spent like weeks making. if that method doesn’t work i’m fucked. is there anything else i can do to get the data back? i dont have an unlocked bootloader though
I don’t think you can. Try plugging usb when you’re in recovery mode and see if it recognize it.
Is this how you fixed this problem? How can I access the dev settings if the screen is pitch black
i had to reset my phone. there was no other way.
Has anyone tried this out? Does this work?
alright. also, the 10 second “window” doesn’t always appear, it sometimes gets to the loading circle screen right away. did this happen to you too?
Im not sure it was a while ago and I’m not longer on stock OS.
Hey, just the night before I was messing with these EXACT settings and as soon as I clicked on this Display cutout setting my phone also crashed. I’m a non developer but had my Developer Options enabled. The steps you mentioned are too complicated for me to understand. Please can you brief me through these steps so that I can get back my phone to a working condition without having to Wipe My Data
Nope, it didn’t work for me
Finally I did the factory reset
I too did the same thing….I increase the smallest width to 420 in my Redmi Note 8…..it just let my phone running in a boot loop with a recovery….
I am not sure whether did I enable USB debugging….is there any other way other than factory reset
PLS WELP!?!
Also btw Redmi note 8 users who have not updated from miui11 to miui 12….pls dont do it….the battery drain in so bad…it barely lasts for a day(it lasted for 2 days when I had miui11)…also there is a terrible system slowdown due to the animations…which I had to reduce using the developer’s settings…to make it normal
> I am not sure whether did I enable USB debugging….is there any other way other than factory reset
You should try using your computer and typing the command `adb devices` into a command prompt.
If you get your `device` listed, then you have a chance of fixing it by running the following command:
`adb shell am display-size reset`
If it’s listed as `unauthorized`, `offline` or not listed at all, there’s likely no way to do this without having an unlocked bootloader.
**hii i m done this double display cutout , the same is done with my phone its redmi 6 as you said no home or lock screen just 3 opt wipe data reboot and connect with mi assistant .pls help me i dont know where in my mobile the usb debugging option is enable or disable but i enabled double display cutout unknowingly. i dont know about cmd overlay list but if anyone tell me how to do this step by step .pls tell me i will be very thankful to him.pls tell me about the solutions on this.i have a laptop and i connected my phone with it but nothing done it doesnt detecting my device in mi pc suit too. i will go crazy my work will stop. pls help and tell me about how to use cmd overlay and how to access my device with a usb cable and a laptop.**
can you please tell me about how to do this i mean im facing this right now dated 12 feb 2021 pls tell me about which software to use and i have a laptop a usb cable and pls tell me step by step im so worried my all work stopped without my device redmi 6 pls i will be very thankful just tell me softwares and how to use it cause i cant do anything with my phone its bricked or stucked in ur language all have to do it with a lapi and a half dead phone
Thank you so much for the “repairing guide” it worked very well!
I know this is two years old but thank god you saved me after looking everywhere after doing this on an Android 12 rom!
Thank God for people like you who can point out a lesson that’s already been learned without you, he might not have felt bad enough.
Display cutout and smallest width are both things I played with for fun. Thankfully had no issues.
my phone is fked up i ma scraed as f
Thanks a lot for sharing this man!
I was just about to change the display cut out of my Mi 11 Pro.
But I don’t know why, just something in my head said not to.
So I just didn’t.(was just trying to have fun and as you said I didn’t think a setting like that could do much harm.)
Then I came here to see what others’ experiences are with tinkering the display cut out.
Thank God I passed up on a massive loss! 😵💫
I’m not sure if it has been fixed in newer versions of MIUI, this was quite some time ago, but probably best not to risk it. 😀
Same here, I just found an issue. Because of MiUI
Is it a different issue or the one I describe?
It would be very unfortunate if this is still an issue on some models :/
My phone is a POCO X4 Pro 5G. I just tried to select from the display cutout, it’s unresponsive and different cutout instead I selected. What I did was return to the previous state as long as I selected the device default and then pressed the power button twice, and then it returned to the previous state.
There are 4 options in simulate display cutout in developer options: 1 Double cutout 2 Corner cutout 3 Tall cutout 4 Default. My Redmi 6A was working all right when it was default and was also working all right when I selected corner cutout. Corner cutout only created an empty\blank bar just above the status bar. Don’t know what would have happened if I had selected tall cutout. Anyway, as soon as I selected double cutout the screen turned blank. Although – fortunately – the quick ball is still visible and the visual tap feedback is also visible. I can also reboot or power off the phone through physical power button (which is located on the right side/edge of phone). I can also reboot or power off the phone using 1 of the 5 quick ball shortcuts. Other 4 shortcuts in quick ball also work. But screen stays black\blank. I chatted with customer service. An agent advised me to go to service centre. I wonder if factory reset will solve this black\blank screen issue. It is disappointing\unfortunate that selecting an option in “simulate display cutout” options in “settings: developer options” made the device screen black\blank. Please suggest solutions.
Screen is blank. Safe mode is visible in lower left corner. Can’t see anything so can’t reach developer options to turn display cutout to its original default option.
> I wonder if factory reset will solve this black\blank screen issue.
It will. This is an user-facing preference that a factory reset will erase.
> Please suggest solutions.
I can unfortunately only recommend a factory reset, if losing your data is not a big issue.
I actually put my phone in a crash loop with the Smallest Width setting. That was a pain in the ass.
I made the same stupid mistake but I managed to fix it without loosing all my data. I did not have a working recovery and flashing all partitions (but the userdata) using SPFlashTool did not fix it. It was clear that the settings were stored on the userdata, which is FBE encrypted on my device. Using SPFlashTool, I loaded the whole userdata partition onto my computer, mounted it and had a peek around. Even though the data is encrypted, you could still see three different vendor folders. I renamed all of them (I also renamed the misc folders, don’t know if that was necessary), and flashed the modified partition back onto my phone. It was behaving weirdly at first, but after a while I reckon it recreated these folders. All the app permissions were gone, but that was the whole damage.
So there you go.
I now do regular backups of my userdata.
I’m glad you managed to fix it!
Did you delete the entirety of `vendor` folders, or the `overlay` folders within them?
I’m sure you already know, but `vendor` does contain a few things that are relevant for a functioning system.
I just renamed the vendor and the vendor\_de folders. I know there’s other stuff on there too, but it is not system critical (in fact its not even there in the stock userdata). I left the vendor\_ce alone, because it’s encrypted with my credentials (ce = credential encrypted) and the phone didn’t even ask me for my password before bootlooping
My phone booted just fine afterwards, though I had some problems with the UI at first. It all fixed itself after about 30 minutes.
I couldn’t delete just the overlay folder because that was in the encrypted folder
Еhanks for the topic! I was lucky I had USB debugging enabled and had an authorized computer. The following commands helped me:
adb shell cmd overlay disable –user 0 com.android.internal.display.cutout.emulation.double
adb shell cmd overlay disable –user 0 com.android.internal.display.cutout.emulation.corner
adb shell cmd overlay disable –user 0 com.android.internal.display.cutout.emulation.tall
I’ll write tags for people with a similar problem: Redmi Note 8T developre options cutout overlay
\`cmd overlay disable …\` fixed it for me, however had to enter \`adb shell\` command first.
Thanks for this
sorry for the ultra necro, but did you end up just factory resetting?
hey if i hadn’t used SBFlashTool before this, am i screwed? or can i just get a stock rom equivalent to my version and go off that for scatter files
if i have usb debugging enabled but unauthorized (for some reason, i authorized it before), i’m screwed, right? none of the other options will work
no i don’t have an unlocked bootloader
Yeah.. You can’t authorize it in this state.
Read through the rest of the comments here though, as some people have reported success by spamming reboots.
yeah lol
I think the scatter files should be the same. I suggest you try it — if the scatter files are incorrect you will notice because the mounting of the filesystem will fail
that could’ve happened to a developer too, it’s good that you know that the cutout setting can make devices bootloop, but it is not your fault, that setting is there for testing purposes, it wasn’t meant to bootloop it, for example, my samsung a15 has those cutouts options too, i turned on the “double cutout”, one notch at the top, one at the bottom one time, for shit and giggles, and as i am writing this comment i am using the “tall cutout” just messing around, as you can tell, my phone isn’t bootlooping, because it isn’t made to do that😉