Corruption Warning after bootloader unlock - LG G5 Questions & Answers

Hi all,
I've just unlocked my H850 bootloader "successfully" if I may say. why ? Because once it's was done, I get warnings on boot.
The first one says: "Your device software can’t be checked for corruption." with an Orange triangle.
The I got a second one with a red triangle which says "Your device is corrupt. It can’t be trusted and may not work properly"
The first message appears for about 3 seconds then the second for about 8sec then the LG logo and it boots normally...
I still didn't flash the SuperSU zip file to root since I don't have an external storage.
What might be the effects of those warnings ? Should I be worried ? My phone is still working normally however...
How can I erase them ?
Should I keep going with the rooting process ?
Thanks in advance for your answers.

dbaOCP said:
Hi all,
I've just unlocked my H850 bootloader "successfully" if I may say. why ? Because once it's was done, I get warnings on boot.
The first one says: "Your device software can’t be checked for corruption." with an Orange triangle.
The I got a second one with a red triangle which says "Your device is corrupt. It can’t be trusted and may not work properly"
The first message appears for about 3 seconds then the second for about 8sec then the LG logo and it boots normally...
I still didn't flash the SuperSU zip file to root since I don't have an external storage.
What might be the effects of those warnings ? Should I be worried ? My phone is still working normally however...
How can I erase them ?
Should I keep going with the rooting process ?
Thanks in advance for your answers.
Click to expand...
Click to collapse
This has already been asked many times, just search in the bootloader unlock thread or in TWRP thread...
Back to the "problem", well, it's NORMAL, starting from Android Marshmallow on ALL devices with an unlocked bootloader will boot with those warning, so nope, nothing to worry about, and nope, at the moment is not possibile to remove those warnings

Thanks for your answer. I've seen such threads but no one is talking about the second warning in red. I'm asking specially for that one..

Isn't this just the same as the warning that you get on Samsung devices where it pops up the alert to say "This device is not SE enforcing."
If you're unlocking the Bootloader, you're opening up something that logically (since you're opening the door to rooting the device), you can more easily compromise the device security - only fair that they warn you and stop the warnings from being suppressed, my devices have always worn that "branding" as a badge of honour

BahnStormer said:
Isn't this just the same as the warning that you get on Samsung devices where it pops up the alert to say "This device is not SE enforcing."
If you're unlocking the Bootloader, you're opening up something that logically (since you're opening the door to rooting the device), you can more easily compromise the device security - only fair that they warn you and stop the warnings from being suppressed, my devices have always worn that "branding" as a badge of honour
Click to expand...
Click to collapse
Thanks you make me sure of my device again
Did you root it ? Is it mandatory to use an SD card or you could do it without it ?

After more than 6 months, I'd like to know if there is anything available to remove those message?

dsr250p said:
After more than 6 months, I'd like to know if there is anything available to remove those message?
Click to expand...
Click to collapse
Afaik no

dsr250p said:
After more than 6 months, I'd like to know if there is anything available to remove those message?
Click to expand...
Click to collapse
Alas, not without a custom kernel for the stock firmware. I also have a bootloader unlocked rooted Nexus 6 running MM that doesn't display the warning. Why not? To root the Nexus 6 with MM you had to flash a custom kernel. The developers of the Nexus 6 kernels were somehow able to eliminate the unlocked bootloader warning, but I haven't a clue as to what was needed for them to accomplish its removal.

dbaOCP said:
Thanks you make me sure of my device again
Did you root it ? Is it mandatory to use an SD card or you could do it without it ?
Click to expand...
Click to collapse
You don't need an SD card to root.

Abort said:
To root the Nexus 6 with MM you had to flash a custom kernel. The developers of the Nexus 6 kernels were somehow able to eliminate the unlocked bootloader warning, but I haven't a clue as to what was needed for them to accomplish its removal.
Click to expand...
Click to collapse
But the Nexus 6 is a different device than the LG G5, for some reasons it seems impossible to get rid off the warning message with the LG.

dsr250p said:
But the Nexus 6 is a different device than the LG G5, for some reasons it seems impossible to get rid off the warning message with the LG.
Click to expand...
Click to collapse
You are absolutely correct, and I share your lament that no H850 developer has appeared on the scene with a simple solution for the stock G5. Honestly Annoying has done some very slick work to install a userdebug kernel that permits the disabling of dm-verity, which might therefore eliminate dm-verity warnings. But as you will see at the following link, it is anything but simple. https://forum.xda-developers.com/lg-g5/how-to/guide-adb-root-rw-dm-verity-off-sprint-t3523499

Alright, I see. At this time I will take a distance of using this exploit called "dirtysanta", but hopefully some simple load still coming up.

dsr250p said:
Alright, I see. At this time I will take a distance of using this exploit called "dirtysanta", but hopefully some simple load still coming up.
Click to expand...
Click to collapse
You may want to think twice about DirtySanta. The OP states the following:
Working Devices:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
You'll note the H850 is not listed. Honestly Annoying's work is the only way I've seen to disable dm-verity on the H850, but there are too many drawbacks associated with it for me to try it simply to eliminate the "Your device software cannot be checked for corruption" warning.

I'll get back to this topic during the next 6 months to see if there is a better solution available. I am not in a hurry.

I have never read the about the red triangle warning

Welcome to DM-VERITY
Still_living714 said:
I have never read the about the red triangle warning
Click to expand...
Click to collapse
Here is an article that will tell you about dm-verity and the warnings it presents, including the very familiar orange triangle due to an unlocked bootloader. The red warning is different, and also discussed in the article.
https://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/

Related

Is there something wrong with my phone?

I just bought my vs987 less than a week ago, and when I install my T-Mobile sim card, I'm able to place calls but I'm unable to use the cellular data. I thought these were supposed to be unlocked? My data works fine when I use the Verizon sim card.
Also, when I first started it up I noticed that my "Software status" said "modified." Does that mean that this phone was previously owned/tampered with? I updated to 7.0 Nougat via Uppercut and LGUP, and now it says "Official." So, I'm a bit alarmed by what was there previously...
Can someone address both of these concerns?
Also, in "About Phone" in the settings menu there is no "Update Center" option. I looked in this video and it appears there.
https://youtu.be/gXeKZ6Dk4Fg
Is that normal, too?
I would appreciate the feedback because I'm a bit anxious due to the fact that Best Buy apparently charges $35 for returns or exchanges on phones. -_-
Do you know if the bootloader is unlocked? Because on some phones when the bootloader is unlocked if causes some problems especially on stock firmwares!
DevCharlie17 said:
Do you know if the bootloader is unlocked? Because on some phones when the bootloader is unlocked if causes some problems especially on stock firmwares!
Click to expand...
Click to collapse
How can I go about verifying whether it's unlocked or not? I swear if something is wrong they better not charge me $35. I will dispute them via my CC company if they do.
Well a simple way is when it boots up it says “bootloader unlocked and visit this link” or something in that nature and a nother way of checking is going into settings - about phone - software info - click build number 8 times - back to settings - developer options... And if enable OEM Unlock is checked... Your bootloader is unlocked
DevCharlie17 said:
Well a simple way is when it boots up it says “bootloader unlocked and visit this link” or something in that nature and a nother way of checking is going into settings - about phone - software info - click build number 8 times - back to settings - developer options... And if enable OEM Unlock is checked... Your bootloader is unlocked
Click to expand...
Click to collapse
I checked and there isn't an option for OEM Unlock in the dev options.
Edit: I think this is because the vs987 isn't rootable.
Hmm well I honestly don't know what could be causing this problem I would suggest finding another official KDZ (don't downgrade) from here http://downloads.codefi.re/autoprime/LG/LG_G5/VS987/VS98711A and if possible factory reset before and after
DevCharlie17 said:
Hmm well I honestly don't know what could be causing this problem I would suggest finding another official KDZ (don't downgrade) from here http://downloads.codefi.re/autoprime/LG/LG_G5/VS987/VS98711A and if possible factory reset before and after
Click to expand...
Click to collapse
Since I'm unable to create a backup of my current state I'd like to use this as a last resort. I'll wait a bit for other responses and if things don't seem good I'll give it a go. Thanks for the help so far. I appreciate it.
No Problem!
Does anyone else have any ideas? I'm running low on time with Best Buy's return policy, so I'd really appreciate it.

LG Bootloader warning screen.

Guys, Is there any way to get rid of that ugly bootloader unlock warning when phone is reboot?
EDIT September 11, 2020:
Here you go:
LG V30 Unlocked Bootloader Warning Disabler
I would add it to the WTF Instructions but I've run out of room on that LONG post. It's posted in the mods/themes/apps section. People will just have to find it.
Thats the bootloader, telling you its unlocked.... thats before/during the splash screen i think...
I doubt we can get rid of it, except locking your bootloader again probably? (is that even possible on a H930/US998?)
No,like on the G5 it's not possible to remove it.
Unlocked bootloader = warning screen.
There is nothing we can do.
Regards
mkpcxxl
On my old Moto G was the similar bootloader unlock warrning and someone made the flashable zip that this turn, off but that was message instead of the Motorola logo. This was annoying for everyone.
https://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocked-bootloader-warning-t3294590
SGCMarkus said:
Thats the bootloader, telling you its unlocked.... thats before/during the splash screen i think...
I doubt we can get rid of it, except locking your bootloader again probably? (is that even possible on a H930/US998?)
Click to expand...
Click to collapse
Bootloader unlock warning has always been able to be replaced on Motorola phones. It's simply a static boot logo graphic.
When you unlock a Motorola bootloader, the "regular" M logo gets replaced by a scary "bootloader unlocked warning". Both are simple static graphic files. I've made lots of them for Motorola phones, which could be flashed via ADB or even TWRP. Surely LG is the same?
What do people do for the bootloader unlocked open market LG G5, V20, LG G6? They don't put up with that annoyance do they?
I suppose if the image the bootloader draws for a short time over the splash screen is stored somewhere else than the bootloader itself (aka not hardcoded), im sure it could be replaced, but someone has to find out where its stored how xD
SGCMarkus said:
I suppose if the image the bootloader draws for a short time over the splash screen is stored somewhere else than the bootloader itself (aka not hardcoded), im sure it could be replaced, but someone has to find out where its stored how xD
Click to expand...
Click to collapse
Yes, on some phones it's called the splash screen. Also, called the boot logo, not to be confused with the boot animation.
Surely people have done it. I've not messed with LG phones since LG G2/G3 and then I never really unlocked the bootloader but used exploits to install TWRP and root. But it's common with Motorola phones.
If you want to figure out the format of the raw_resources partition, that is where all the images are stored. It is possible to change them, but if you mess up, then your phone is a brick since abl will not load -- which is why the risk just wasn't worth it for me.
They are RLE so they have no header. There is an index that gives the name and offset for the location of the image, but not the size (either they are all the same size, or the size is stored somewhere else).
-- Brian
runningnak3d said:
If you want to figure out the format of the raw_resources partition, that is where all the images are stored. It is possible to change them, but if you mess up, then your phone is a brick since abl will not load -- which is why the risk just wasn't worth it for me.
They are RLE so they have no header. There is an index that gives the name and offset for the location of the image, but not the size (either they are all the same size, or the size is stored somewhere else).
-- Brian
Click to expand...
Click to collapse
What if you just want a different boot animation?
Is replacing the Zips in system - media safe?
Or just out right delete them? I hate that T-Mobile logo with a passion.
Sent from my LG-H932 using XDA Labs
Edit, I figured it was safe but to be sure I tested on my V20.
Now I customized my v30 .
Perhaps better yet (though I need some more people to help confirm this)...
I have successfully removed the bootloader warning for my unlocked US998.
The process is simple but try at your own risk for other variants more dissimilar to the US998 etc.. etc..
Steps:
Verizon (in their infinite wisdom) thought "Oh hey, no one will ever ever ever get the LG V30 with our software and have an unlocked bootloader, so why even bother having an unlock warning. "
Lets prove them wrong.
Take a backup (of course)
Go grab yourself the latest VS996_20d kdz file (available here on XDA or "LG-Firmwares")
Get your phone in LGUP mode (/w power off hold Vol-UP while inserting USB to computer)
In LGUP select PARTITION-DL and point it to the shiny VS996-20d kdz you waited so long for the download to complete
Click start then in the partitions list ONLY select raw_resources.
Click Ok.
The phone will do its thing and it will reboot and you will notice a black screen instead of annoying warning... Thanks Verizon. :silly:
Hope this helps!
That warning screen is nothing to even care about.
Sent from my LG-H932 using XDA Labs
SaberShip said:
Perhaps better yet (though I need some more people to help confirm this)...
I have successfully removed the bootloader warning for my unlocked US998.
The process is simple but try at your own risk for other variants more dissimilar to the US998 etc.. etc..
Steps:
Verizon (in their infinite wisdom) thought "Oh hey, no one will ever ever ever get the LG V30 with our software and have an unlocked bootloader, so why even bother having an unlock warning. "
Lets prove them wrong.
Take a backup (of course)
Go grab yourself the latest VS996_20d kdz file (available here on XDA or "LG-Firmwares")
Get your phone in LGUP mode (/w power off hold Vol-UP while inserting USB to computer)
In LGUP select PARTITION-DL and point it to the shiny VS996-20d kdz you waited so long for the download to complete
Click start then in the partitions list ONLY select raw_resources.
Click Ok.
The phone will do its thing and it will reboot and you will notice a black screen instead of annoying warning... Thanks Verizon. :silly:
Hope this helps!
Click to expand...
Click to collapse
It does get rid of the bootloader unlock warning, yes. However it now says you have a V30, even if you have a V30+. Depends on if that matters to you.
If someone has a phone under warranty and wants to be really brave -- null out raw_resources and you should just have a black screen.
Again, that is a risk since the loading routine in abl could have bugs and get wigged out and go into a loop or something. If that happens -- 9008 brick.
If someone wants to try it, boot to TWRP and:
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/raw_resources
reboot and tell us what happened
-- Brian
I thought about this because I liked customizing the boot on my old Motorola phones.
But then I thought, how many times do I actually restart my phone to care about how the boot screen looks?
95% of the time, your phone is on standby.
LOL @runningnak3d ^
Considering you can no longer decompile abl since it is encrypted, the only way to find out is to test it
-- Brian
I'd like to, but this phone as of Saturday, is still worth nearly 500 in-store trade. I'm on the fence.
I can tell you that the only thing in raw_resources are the images that you see for things like the big errors and the charging images, and crap like that.
Someone has to do it. I would, but for some reason eBay doesn't want me to have a V30 .. they just want to tie up my money.
-- Brian
runningnak3d said:
I can tell you that the only thing in raw_resources are the images that you see for things like the big errors and the charging images, and crap like that.
Someone has to do it. I would, but for some reason eBay doesn't want me to have a V30 .. they just want to tie up my money.
-- Brian
Click to expand...
Click to collapse
I think I'd rather take my chances poking around in the binary with a hex editor before zeroing the whole partition. Zeroing would be asking for null pointer exceptions in your bootloader. I don't want to speculate what that might do. Who knows with LG... maybe it will re-lock the bootloader bahhaha....
As others have pointed out i'm not sure the reward is worth the time right now. There are a lot bigger problems yet to be solved with this device in terms of development.

Samsung Galaxy A10e - Is this the right place to be???

Hi!
I recently purchased a Verizon-build Samsung Galaxy A10e (the "economy Flagship" / little-brother of the A10) but XDA has very little information on this phone. Would this be the best place to try to find/request information?
Thanks for your help!
where can i get more developer information on this phone
Give it some time before developers start posting, since the phone was released only a couple of monthes ago. It will be a good minute before you start seeing significant posts for the galaxy a10 e. Keep updating by searching on a regular basis. Check howardforums or android central as well.
On another note:
Some of us need to know the a10e galaxy update to android 10, anyone got then lastest news on that yet? I got one with metro pcs.
Thx
Sent from my SM-A102U using Tapatalk
yea like alot of sites keep saying galaxy a10e will not be getting android 10 and one ui 2.0 but the fail to see samsung own site says they will probavly in may or june of 2020
Also using an SM-A102U device, I believe the official Android 10 date is sometime in the first half of 2020. I believe March.
What would really help us is pHH-Treble support for these devices and Android 10, which I can't find any info for, aside from a GSI post on the Galaxy a20, which has (essentially) the same Exynos chip.
timba123 said:
On the metro variant I was trying to figure out bootloader unlock and the phone vibrated and a yellow exclamation ! Appeared at bottom of black screen. What is that?
Click to expand...
Click to collapse
depends on wat u mean by trying to figure it out lol.. if its like any the other usa variants its not unlockable which is why u dont see oem unlock
timba123 said:
This.
Click to expand...
Click to collapse
i dont kno wat that is but seems to be a indicator for your charger.. maybe not fast charging or something.. i assume the device is off when you get this screen.. if its off and plugged in via pc it could simply be indicating its not fast charging as its being charged from the usb port.
Sent from my SM-N976V using Tapatalk
timba123 said:
It's not off exactly. Kinda reminds me of system crash on eng fac roms. I've seen articles about older devices and it meaning no battery or no charging like you say. Guess I got over excited for nothing lol. Though it might be a hackable situation etc or different mode of some kind.
Click to expand...
Click to collapse
Yea.. and fyi, a common misconception is "eng fac" roms are two completely different things lol.. it's a pet peeve of mine which I owe to all the firmware sites and generic "guides" on the web lol.
They always refer to factory/combo roms as "eng" when they are not eng at all.. fac roms are debuggable (ro.debuggable=1) and permissive and adb enabled by default and dmv disabled with a bare bone os mainly used for testing or fixing issues with the device.
Eng on the other hand is typically a stockish build with su binary by default (allows actual adb root shell) is permissive, verity disabled, contains other high level engineering software etc etc that is supposed to be used by engineers to test their software and things of that nature. My sampwnd root for s8/s8+ for example used eng system.img to gain root. Older devices did have eng boot.img many used to root devices but since s8 and newer they are no longer used because samsung implemented security measures to where u cant flash or run them without an eng token and device being in actual eng mode. Eng tokens are hard to find as they are device specific and need to be generated on samsung servers at which if u can find someone willing to make one they are usually expensive since they need to have a legit business, purchase a signing cert from samsung to be able to generate eng tokens as well as they typically need to also pay for each individual token which just the signing cert alone I've heard various prices from thousands to 100k lol. Then after all that if you have an eng token and device is in eng mode then it's not the same as a bl unlock as you would need to flash eng firmware which is another adventure to locate and probably another pretty penny.
Rant on eng/fac differences is over lmao.
On a side note, I'm working on something that "might" work... according to my dev buddies it will work.. it's a process tho as I need to generate some custom files and I never did this before (I mainly use usa locked snaps) .. but if all goes as planned with some trickery could probably unlock the bl and at the very least root the device.. stay tuned lol
timba123 said:
On the metro variant I was trying to figure out bootloader unlock and the phone vibrated and a yellow exclamation ! Appeared at bottom of black screen. What is that?
Click to expand...
Click to collapse
I also tried (with my limited knowledge here) to enable OEM bootloader unlock by changing the settings flag in the phone but have not had luck. I talk about what I tried to do/have a screenshot showing where the system has it looked in this post:
https://forum.xda-developers.com/ga...rint-oem-lock-developer-t3963898/post80909957
I have also looked at using Tasker/other tools to try to change something here or to see if there's an intent or action or something that will trigger the unlock but haven't had luck.
timba123 said:
So since this is the only A10e root thread. I'll post here. After browsing the internet I found out that Samsung changed some security. Now fac combo cant be flashed with 3.14 odin which newer devices like our A10e will not work with odin 3.13 and before patched or not. A new odin needs to be made. Patched. And the new Security for samsung.
Click to expand...
Click to collapse
This isnt new information. I do not think a new/patched odin will work since it uses a token system. Trying to flash will say you need approval to use factory binary.
With that being said you can use a factory bin token which will then allow you to flash combo rom.
There are ways to bypass need for a token but they are not public.
Also tokens are device specific and if you can find someone to get them they are not free.
Side question that's not totally related but I'm finding conflicting answers online:
Does the A10e NOT have USB-OTG capabilities? :-/
I don't have a USB-C OTG cable to test myself. I realize this phone purposely does not have some features/capabilities that I guess are supposedly deemed more "premium," in order to keep this phone in a class I've heard described as "Economy-Flagship," (lol ). Hence: no wireless charging, no fingerprint reader, no gyroscope, no proximity sensor (this exclusion is kind of annoying - surely I can't be the only person experiencing the annoying phenomenon of chronic cheekbone-call-muting? ). But overall, I'm super happy with this phone!
I also wish I could disable Knox but I don't think that's possible without the OEM bootloader unlock setting enabled.
timba123 said:
No not new info but figured alot of people especially new people could use the info. Lol they sure are locking down phones. I wonder what influence the NSA etc have.
Click to expand...
Click to collapse
govt contracts are definitely a big part of it.. every device manufacturer wants that govt money lol
elliwigy said:
govt contracts are definitely a big part of it.. every device manufacturer wants that govt money lol
Click to expand...
Click to collapse
^This makes a lot of sense.
Sorry for my english. I'm looking for help ... i was 3 weeks in US and i lost my phone. So i buyed this A10e with boost mobile but i didn't activate it because they were trying to force me to buy a monthly subscription, wich i didn't... I bring the phone just for wifi use because is a phone with good specs for the price of 90$... and then the horror shows in a form of Harassing message ... trying to make me "accept terms and conditions" and then Boom the phone was restricted from data usage and other things, i tried to unlock the OEM and nothing, also i wipe the phone and it works fine but it keeps harassing with sudden appears of that screen asking if you accept, the icon of that screen is a peace of chess. So my question is ... Can i force an instalation of other rom? in sammobile is a international rom, so, even if i can't unlock the oem , can i install it? is there a way to root the device without the oem unlock? Thanks in advance
reyesergio23 said:
Sorry for my english. I'm looking for help ... i was 3 weeks in US and i lost my phone. So i buyed this A10e with boost mobile but i didn't activate it because they were trying to force me to buy a monthly subscription, wich i didn't... I bring the phone just for wifi use because is a phone with good specs for the price of 90$... and then the horror shows in a form of Harassing message ... trying to make me "accept terms and conditions" and then Boom the phone was restricted from data usage and other things, i tried to unlock the OEM and nothing, also i wipe the phone and it works fine but it keeps harassing with sudden appears of that screen asking if you accept, the icon of that screen is a peace of chess. So my question is ... Can i force an instalation of other rom? in sammobile is a international rom, so, even if i can't unlock the oem , can i install it? is there a way to root the device without the oem unlock? Thanks in advance
Click to expand...
Click to collapse
no.. bl is locked.. only stock official firmware can be flashed
timba123 said:
Found a rooted AP tar but gives SHA error using Odin 3.14
Click to expand...
Click to collapse
doesnt work.. ur getting error bcuz its modified which cant use bcuz bl is locked
timba123 said:
Seems to be verizon firmware by the bootloader number etc. The firmware I posted pics of. I'd upload it but my browser keeps crashing trying to upload it
---------- Post added at 04:42 AM ---------- Previous post was at 04:25 AM ----------
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=200612
Looks like root kernel for metro or tmobile
Click to expand...
Click to collapse
correct.. all it is is stock firmware with a rooted/patched kernel for unlockable variants
Combination File, for FRP & bootloop Repair
http://www.mediafire.com/file/ekejzhig7b9zx7r/ROMProvider.COM_SM-A102USQU1ASF1.rar/file
mark332 said:
Combination File, for FRP & bootloop Repair
http://www.mediafire.com/file/ekejzhig7b9zx7r/ROMProvider.COM_SM-A102USQU1ASF1.rar/file
Click to expand...
Click to collapse
how do you expect people to flash it without a factory binary token?
timba123 said:
Is OTP similar or related to the factory token? Like a password?
Click to expand...
Click to collapse
nope.. otp more of a one time password.. the token is something that uses device specific identifiers that then gets sent to a server where it gets signed and sent back.. then it needs to b physically flashed to the device
Sent from my SM-G977P using Tapatalk

Xiaomi Mi Play -bricked by official update

Hello All,
Hope you and yours are doing fine in these worldwide complicated days.
Regarding the subject, I have a Xiaomi Mi Play mobile that was working fine, with official MIUI, never rooted, never done something else than usual "office" daily usage.
One day, came the famous Security Update notification and as usual, I've confirmed.
Since then big headaches...
Next morning I found the phone in the loop reboot, Fastboot being the only available feature, no more recovery, no more OS, no more personal stuff... Everything has been deleted by the update.
When trying to go to recovery only the magnificent message with the red triangle, saying "The system has been destroyed. Press the power button to shutdown" stays for 10-15 secs and then the whole crap reboots again and again.
No, Developer Settings haven't been enabled, OEM Unlock has not been enabled, USB Debugger neither, bootloader has not been unlocked, MIUI account has not been added in Developer Settings or elsewhere... and no I haven't wrote to Xiaomi support yet.
I've tried around 60-80 different methods to unlock whatever could be unlocked on Xiaomi phone, EDL, bootloader, with dozens and dozens of methods proposed, so far nothing worked. Impossible to install anything, impossible to unlock anything, impossible to do anything.
I've applied for the phone unlock, but since 2 months, impossible to finish the process, it says "Couldn't Unlock - Please add your account in MIUI's Settings > Developer options > Mi Unlock Status"
But I CANNOT access the system anymore at all....
This is it...
Thank you for reading and if you have any other ideas out of everything I've tried, feel free to let me know about.
Take care of you and yours
Kind Regards,
SK
ooophhh no. did you ever get a solution? i had my mi play brick just oputta the blue.. its on communist lockdown fighting the war on capitalism ..... well the hardware wasnt bad for the price and it ran well.,but im not buying a phone from them ever again.
It's very sad. Did you get any update?
Hello All,
No update since March, still looking and trying to unbrick the device....
I'll keep you posted if I find anything that could be called a solution.
Thanks for your support.
Be safe all, you and yours.
Kind Regards,
SK
Same here, bricked device since March by the same update, "The System has been destroyed", fastboot doesn't load.
I guess i've lost 150$.
Produkt87 said:
Same here, bricked device since March by the same update, "The System has been destroyed", fastboot doesn't load.
I guess i've lost 150$.
Click to expand...
Click to collapse
There are many thread for issues like this, for example:
https://forum.xda-developers.com/mi-9-se/help/lock-bootloader-destroyed-help-t3965825
It seems that in some way, same issue was fixed on a different model, but most likely it will work also with Mi Play.
Af far as I have understood, basically the solution is to download the official firmware and flash it back. The main issue is that by default the bootloader is locked so nothing can be written. The point here is how to unlock the phone, and there is an official procedure from Xiaomi:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
I have the same issue for a couple of hours and I am struggling now, so as first step I am trying to unlock the bootloader, but the problem is that per Xiaomi instructions it may take up to 7 days.
So, I will apply for that, while in the meantime I will look for any alternative solutions (if any).
Regards,
Thanks a lot!
But, the're now way to get my phone into fastboot mode.
I've tried all button combinations and there's no response, just the same loop "your system has been destroyed"
Produkt87 said:
Thanks a lot!
But, the're now way to get my phone into fastboot mode.
I've tried all button combinations and there's no response, just the same loop "your system has been destroyed"
Click to expand...
Click to collapse
After some tests on my device, I have found out that it's not easy as I have believed, but if you don't get even in Fastboot mode it's more complicated.
However, can you please clarify what's your cellphone model?
Regards,
I have exactly the same problem since early May, if I just unlock the boot loader before they fall down :c

MiPad 4 stuck on boot- stock and closed bootloader

Hello all,
my Pad 4 does not want to start anymore. It comes the Mi logo for a minute then restarts. I have not done anything. It is stock and closed bootloader.
Is there anything I can do here besides a hard reset? I have already tried this via the Mi-Recovery 3.0 without success.
Edit:
Flashing is not allowed in lock state?
I have now tried MiFlash. With the version V10.3.2.0.ODJCNXM. Does this only work with open bootloader?I thought the original I can flash?
stereo007 said:
Flashing is not allowed in lock state?
Click to expand...
Click to collapse
Hi. Never encountered this error, possibly because I unlock the bootloader of all my devices ASAP.
Yet, I always assumed official tools to be exempt from such restrictions -- how else would one solve a catastrophic device failure?
Well, looks like this isn't the case and your only remaining option is to seek help with Mi Customer Service (if available).
Should the device be sold on European markets (which it isn't...) this alone would be reason for a complaint...

Categories

Resources