Database Info

[Q] Black vertical stripes on my screen

Hi everyone,
yesterday I flashed this ROM. So far so good, but after the phone booted, my touch inputs were totally messed up. Even in the recovery... So I tryed flashing it again with a different Kernel... Bad idea, it got stuck at the LG logo and it didn't display it as normal (it kinda flashed once in a while). Then I went to download mode and flashed back to stock with an official kdz. I booted my phone up and then I had these stripes on my display! They are everywhere from the recovery to download mode, boot logo and the OS itself. Please tell me, are they permanent or is there ANY way to fix it and get rid of them? I attached a picture :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings
Marvin

M4-NOOB said:
Hi everyone,
yesterday I flashed this ROM. So far so good, but after the phone booted, my touch inputs were totally messed up. Even in the recovery... So I tryed flashing it again with a different Kernel... Bad idea, it got stuck at the LG logo and it didn't display it as normal (it kinda flashed once in a while). Then I went to download mode and flashed back to stock with an official kdz. I booted my phone up and then I had these stripes on my display! They are everywhere from the recovery to download mode, boot logo and the OS itself. Please tell me, are they permanent or is there ANY way to fix it and get rid of them? I attached a picture :crying:
Greetings
Marvin
Click to expand...
Click to collapse
Never heard of that :/
This could be a hardware problem, but weird, how it happened after flashing stuff. You said you flashed a different kernel, I don't know, maybe it wasn't compatible, since you bootlooped. Weird how this happen after reverting back to stock.
Weird how it was caused by flashing. I'm not sure.
But just out of curiosity, I would suggest trying a remote control app, and see if these vertical lines also show up on your PC screen. I've tested Webkey in the past:
https://play.google.com/store/apps/details?id=com.webkey&hl=fr
Also tried DroidAtScreen, which was bit slower in my case, due to USB connection speed, but works.
http://droid-at-screen.ribomation.com/
I say, try both, and mention if the lines appear on the PC first, or not. Could be helpful.
EDIT: This sound hardware related, but it's still weird how it happen after flashing a (incompatible?) kernel, and going back to stock. If these lines also show up in Recovery/Download mode, that is I would say not a good sign.

GameX2 said:
Never heard of that :/
This could be a hardware problem, but weird, how it happened after flashing stuff. You said you flashed a different kernel, I don't know, maybe it wasn't compatible, since you bootlooped. Weird how this happen after reverting back to stock.
Weird how it was caused by flashing. I'm not sure.
But just out of curiosity, I would suggest trying a remote control app, and see if these vertical lines also show up on your PC screen. I've tested Webkey in the past:
Also tried DroidAtScreen, which was bit slower in my case, due to USB connection speed, but works.
I say, try both, and mention if the lines appear on the PC first, or not. Could be helpful.
EDIT: This sound hardware related, but it's still weird how it happen after flashing a (incompatible?) kernel, and going back to stock. If these lines also show up in Recovery/Download mode, that is I would say not a good sign.
Click to expand...
Click to collapse
Hi and thanks for your reply
Basically I was on CloudyG2 2.2 and messing around with xposed (applying settings in G2 Xposed and so on). Then I wasn't able to put the "recent apps" button in the navbar. There was absoluty no way to do it and the option in the stock settings gave me a settings force close. So I searched around and don't ask me how but I landed on the ROM page I mentioned before. I read carefully throughout all of OP's posts and then decided to give this awesome sounding ROM a shot. So I searched for the requiered TWRP (bumped 2.6.8.1 if I remember correctly) and then followed the install instructions. Then it was finally installed and I was scared that I messed my phone up because the touch inputs where crazy like hell... unuseable... Then I checked if it is in TWRP as well.. and it was... then I searched for a lollipop kernel (hoping that a different kernel would fix this issue) and dumb and scared as I was I just flashed one ("efficient kernel" was it...). Well then the part above happened.
The lines do not show on a screenshot I tested earlier because I was courious, but I will try what you said. Gimme a couple of minutes.
But yes it's in download mode, in recovery and at the boot...so that doesn't sound good:crying:
EDIT: Lines are not showing with remote app...

M4-NOOB said:
Hi and thanks for your reply
Basically I was on CloudyG2 2.2 and messing around with xposed (applying settings in G2 Xposed and so on). Then I wasn't able to put the "recent apps" button in the navbar. There was absoluty no way to do it and the option in the stock settings gave me a settings force close. So I searched around and don't ask me how but I landed on the ROM page I mentioned before. I read carefully throughout all of OP's posts and then decided to give this awesome sounding ROM a shot. So I searched for the requiered TWRP (bumped 2.6.8.1 if I remember correctly) and then followed the install instructions. Then it was finally installed and I was scared that I messed my phone up because the touch inputs where crazy like hell... unuseable... Then I checked if it is in TWRP as well.. and it was... then I searched for a lollipop kernel (hoping that a different kernel would fix this issue) and dumb and scared as I was I just flashed one ("efficient kernel" was it...). Well then the part above happened.
The lines do not show on a screenshot I tested earlier because I was courious, but I will try what you said. Gimme a couple of minutes.
But yes it's in download mode, in recovery and at the boot...so that doesn't sound good:crying:
EDIT: Lines are not showing with remote app...
Click to expand...
Click to collapse
You do have a complete Nandroid Backup of the ROM you had before the problem? Including the /Boot partition (Which holds the kernel if I'm correct) ? Maybe you already tried to restore that backup?
You also said you've went back to stock, which also restored a different kernel anyway. But I find it weird, does look like hardware related, but I don't understand why it happen that suddently after flashing...

GameX2 said:
You do have a complete Nandroid Backup of the ROM you had before the problem? Including the /Boot partition (Which holds the kernel if I'm correct) ? Maybe you already tried to restore that backup?
You also said you've went back to stock, which also restored a different kernel anyway. But I find it weird, does look like hardware related, but I don't understand why it happen that suddently after flashing...
Click to expand...
Click to collapse
I had a complete Nandroid Backup, but I didn't copy it to my laptop... so going back to stock wiped freaking everything including internal storage...
Yes I went back to stock JB 4.2.2 and after that to stock KK 4.4.2, both with official kdz and LG Flash Tool.
Well idk why this happened this is totally new for me too. I have been flashing almost everything I can since I got my T-Mobile G1 at release and ofc had some bootloops and so on, but never ever has happened something like this.
EDIT: What if someone on here provides me with a LG G2 D802 Nandroid Backup? Would that work?

Help needed - Stock Firmware reinstallation via KIES caused Boot Loop

Hi guys.
I have a little problem with my tab now . Originally my machine had a little hiccup ever since I upgraded to Lollipop. The problem was that it tried to upgrade apps to Lollipop every time I did a boot cycle. Usually ending with a message that an app called "a...a" closed. I did not bother me much for a while. But Today I thought it was past time I resolved this so I tired to reinstall the firmware with Kies. Bad idea in retrospect, since it caused a boot loop at first (I did not touch it for 1-2 hour) than after seeing that it did not progressed. I tired a forced restart by holding down the power button. Strangely somehow after 2 or 3 tries it did started to do something. Saying that it has to update 190 apps and it did so, after then I found myself at the first setup page. However it did not worked because a lot of warnings come up constantly like: google process stopped, maps stopped, etc... making it unusable to set up anything, since even if you OK the warning the next comes up constantly. Also Kies no longer detects the phone, so I was forced to use Odin to reflash it. But here's the twist: even after reinstalling the same version of the stock image via Odin the continuous boot loop occurs again and again. (The image I got it from samdownloads de). I'm unsure where the problem can be, the only thing I can suspect is that I only used AP with Odin since the rar did not contain any bl cp csc or anything (I also tired full wipe via recovery but it did not help). So if anybody have any idea as to what direction should I take, please say so. I would really appreciate the guidance.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.

quarros said:
Hi guys.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.
Click to expand...
Click to collapse
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21

Beut said:
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21
Click to expand...
Click to collapse
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?

quarros said:
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?
Click to expand...
Click to collapse
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Beut said:
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
Click to expand...
Click to collapse
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again

quarros said:
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again
Click to expand...
Click to collapse
From my experiences, these things have nothing to do with flashing a firmware:
1- Fresh installed windows, I use XP or Windows 7, there is nothing different as long as you have correct Samsung USB driver.
2- Odin versions have no differences, I use old or new, they are both the same.
3- Home button is not needed to access Download or Recovery Mode
Your problem went away probably from fresh install of the system.

Please help me! Freshly softbricked SGS7, SM-G930W8, No OS Installed

I have tried goddamn near everything and lurked everywhere.
This is just me trying to fix a huge mistake. I got this phone yesterday, everything was fine. I just wanted to install a custom recovery so I could back up the phone.
I flashed TWRP with Odin, I may have done it wrong or something... But I'm pretty sure I followed some directions. Odin did it in a snap, my device rebooted into TWRP... but then, I just barely noticed the "No OS installed!" message.
I have attempted, in no particular order:
- Using Kies 3 to initialize my device. It will download to 100% and then stick on 0% going to install the OS. Tells me the device is not supported.
- I then tried SmartSwitch because someone told me that's what you need for Android 4.3+. Same exact thing.
- Tried flashing my stock firmware, both 6.0.1 that it came with and the 7.0 that was available before it was bricked, with Odin 13.2 (I also tried others)
What's interesting here is when I add in the AP, BL, CP and HOME_CSC and press start, I get Odin's log to fail just after cm.bin - every time.
Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At that point, I am no longer able to re-attempt until I restart and re-enter DL mode, and a black-backgrounded red text appears on the Download Mode screen, that says:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
My device is the Canadian version, in the XAC region.
I have downloaded and attempted flashing firmwares G930W8VLU2BQB6_G930W8OYA2BQB6_XAC and G930W8VLU1APG1_G930W8OYA1APG1_XAC.
Both give the exact same errors and so I don't think the firmwares I got are the issue. I just have no idea what it could be, since the only problem with my phone is there's no OS installed.
Actually, I do have a problem with TWRP, as well.
TWRP is unable to do much. It cannot mount /data (among others), and those folders are all still there as I can adb push files to the device, and I attempted pushing the actual firmware to the /data folder and I could see the progress by pressing Install in TWRP and then looking in the /data folder... but that was the only file that told me "No space left on device" once it 100% completed, when there's obviously ~30GB.
The first error TWRP gives is that it cannot find the crypto footer.
Am I screwed here? Is this a harder softbrick? What am I missing? Please reply quickly, working by tomorrow would be very ideal.
Thanks in advance!

The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk

bill_in_mtl said:
The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
I tried many more than four times. Should I be using CSC rather than HOME_CSC, just to wipe everything and maybe that'll work?
You say you got 'errors' in Odin, but it's always different for a different cause. You didn't get an error before cm.bin, did you?
EDIT: Attempting CSC rather than HOME_CSC for both v7 and v6 firmwares.
UPDATE: Ugh... I guess it's not the same every time. Using CSC with the Marshmallow md5s, I got Odin to err earlier this time, before even getting to cm.bin!:
UPDATE2: I have just tried flashing Nougat with Odin, using CSC instead of HOME_CSC, and IT'S WORKING??? WTF. Got past recovery, now going through system... Perhaps I posted too soon? Sorry for wasting anyone's time. I will update this thread if it doesn't work.
I'd say this thread isn't worth deletion because I think somebody could come by, take this information and help themselves with it.

I had similar issue - error would be different with every attempt until finally it just flashed and passed. Glad you got it working .
sent from SGH-1337M using Tapatalk

Yeah, that's the thing though... With this one, I got the same error no matter how many times I tried one specific way.
I suppose just never attempted the 7.0 firmware with CSC instead of HOME_CSC. Thanks anyway

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.

Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....

E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!

Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.

Question Hard brick

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you ever get this glitchy screen there's a high chance that your device is going to get hard bricked soon. The glitches usually get accompanied by system reboots or reboots to fastboot.
We still haven't determined what exactly leads to a brick. All reports so far have been from users on stock MIUI 12.5.x or MIUI 12.5.x based custom ROMs, either with locked or unlocked bootloader. But yesterday we had the first case of a brick on AOSP too. It's probably MIUI 12.5.x firmware's fault so we suggest you to use MIUI 12.0.x if you want to use MIUI and use only 12.0.x firmware if you're an AOSP/CAF custom ROM user.
Also, make sure to take a backup of your internal storage and your apps as soon as possible if you ever encounter these graphical glitches. You'd better take backups regularly either way just to be safe.
In case you get a hard brick, you have to visit a service center to get your motherboard replaced. Do anyone faced this problem?

irmas5 said:
View attachment 5446589
If you ever get this glitchy screen there's a high chance that your device is going to get hard bricked soon. The glitches usually get accompanied by system reboots or reboots to fastboot.
We still haven't determined what exactly leads to a brick. All reports so far have been from users on stock MIUI 12.5.x or MIUI 12.5.x based custom ROMs, either with locked or unlocked bootloader. But yesterday we had the first case of a brick on AOSP too. It's probably MIUI 12.5.x firmware's fault so we suggest you to use MIUI 12.0.x if you want to use MIUI and use only 12.0.x firmware if you're an AOSP/CAF custom ROM user.
Also, make sure to take a backup of your internal storage and your apps as soon as possible if you ever encounter these graphical glitches. You'd better take backups regularly either way just to be safe.
In case you get a hard brick, you have to visit a service center to get your motherboard replaced. Do anyone faced this problem?
Click to expand...
Click to collapse
That's not a hard brick ... you screwed up your GPU/Motherboard (overheating / fake fast charger, water ... etc)
Hard Brick = bootloader relocked with a modified partition / modified firmware = Black Screen ALWAYS
you better go to a service center ... before now !!!
don't waste you time with flashing ...

I've been following this on telegram & youtube, my personal opinion is it is a hardware issue, the frequency of it happening on 12.5.x is because most people have upgraded to 12.5.x, if everyone now downgrade to 12.0.x as a 'precaution', we'll probably see reports on 12.0.x, we'll know soon enough...

No. Mine fine now. Yesterday and today started some flickering, but uninstal magisk. Fully unrooted and disappeared flickering. Just curious.

gringo80 said:
That's not a hard brick ... you screwed up your GPU/Motherboard (overheating / fake fast charger, water ... etc)
Hard Brick = bootloader relocked with a modified partition / modified firmware = Black Screen ALWAYS
you better go to a service center ... before now !!!
don't waste you time with flashing ...
Click to expand...
Click to collapse
this has been happening on all units, randomly. Do you know of any way that it can be fixed without the service centre's help?

meechyy said:
this has been happening on all units, randomly. Do you know of any way that it can be fixed without the service centre's help?
Click to expand...
Click to collapse
this is hardware issue
bricking is related to software

Lu5ck said:
this is hardware issue
bricking is related to software
Click to expand...
Click to collapse
can anything be done?

meechyy said:
can anything be done?
Click to expand...
Click to collapse
No, you send to xiaomi to service to replace the hardware.
Software fix can't cross dimension to reality.

I would expect more attention after months, if this issue were as severe, as it seems. Perhaps these were indeed hardware related issues, that weren't related to the software in any way, at all.