Database Develop

(Help) [LG G3 Sprint Ls990] Secure Booting Error Boot Certification Verify Problem

Hi all,
Recently I wanted to go to Cyanogenmod. I'm used to rooting my phone and doing the whole process. But this time, I'm stuck. When I try to root, everything goes fine until I have to put my phone into download mode manually. I get the error on top: Secure Booting Error! Cause: Boot Certification Verify every time I go into download mode.
I tried going back to stock (can't even more because of download mode). I can turn on my phone just fine and operate it. I can also go into recovery mode (stock lg recovery) if that helps.
Thanks in advance.
EDIT: I finally fixed it by flashing stock

The Error is caused because after flashing SuperSu you didn't bump the bootloader again. SuperSu changes the Bootloader so it needs to be rebumped. You can try running this zip file in recovery and hopefully it works.
https://mirrors.c0urier.net/android/Dadi11/Required files/MR_Bump.zip

Darthsternie said:
The Error is caused because after flashing SuperSu you didn't bump the bootloader again. SuperSu changes the Bootloader so it needs to be rebumped. You can try running this zip file in recovery and hopefully it works.
Click to expand...
Click to collapse
Thank you for this. I tried flashing magisk.

ACViperPro said:
Thank you for this. I tried flashing magisk.
Click to expand...
Click to collapse
Hi ! I'm in the exact same situation except that it's when I try to go on recovery mode that I have the security message - and I'm on a LG G3 D850 (AT&T). I tried your solution - it changes the message to "[610] Fastboot mode started", and then nothing...
Any idea ?
Thomas

kakounet said:
Hi ! I'm in the exact same situation except that it's when I try to go on recovery mode that I have the security message - and I'm on a LG G3 D850 (AT&T). I tried your solution - it changes the message to "[610] Fastboot mode started", and then nothing...
Any idea ?
Thomas
Click to expand...
Click to collapse
This is for sprint. So maybe that is your problem. Idk

Updating to pie keeps failing *FIXED*

Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
FIXED
 @RomLover1999: gave the tip to reboot without a sim card, and that seemed to have fixed the problem!

seend said:
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
Click to expand...
Click to collapse
did you tried a factory reset before updating

galardo_2 said:
did you tried a factory reset before updating
Click to expand...
Click to collapse
Nope, but just tried it and it didnt work.

Try booting without sim card

Same and via fastboot method same. Any solution? We need help its a one mi a2 more????

Unfortunately the error is not informative. I had this error when installing November update. The only way I found to see what went wrong is to check logcat during upgrade, but I think it requires root. In the end I flashed the OTA using fastboot. Still didn't get this update. Try opening shell from adb and reading logcat. I don't think anyone can help you unless we know what is 5he reason for failure

RomLover1999 said:
Try booting without sim card
Click to expand...
Click to collapse
Oh my, that worked! :highfive:
Why would something like that even work?

seend said:
Oh my, that worked! :highfive:
Why would something like that even work?
Click to expand...
Click to collapse
The november update has a bug in it that it only boots in english with a simcard inserted , other languages make the screen bug out ( at least that's what I had ) and only boot without a simcard

Worked greatly
Hey folks, just reinforcing the answer: removing the sim card before restart did the trick, the update went smooth.
Thanks @RomLover1999 and @seend

January update failed
Help! My phone is Mi A2 lite. I can't install January update. My phone is rooted and unlocked.
Thank you!

The same problem....
The same problem....anyone help?

nedjog said:
The same problem....anyone help?
Click to expand...
Click to collapse
did you unlock ? ever run TWRP/Magisk or similiar?

luminoso said:
did you unlock ? ever run TWRP/Magisk or similiar?
Click to expand...
Click to collapse
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?

nedjog said:
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
Click to expand...
Click to collapse
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend

luminoso said:
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
Click to expand...
Click to collapse
Ok, my phone is not rooted.

I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues

luminoso said:
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
Click to expand...
Click to collapse
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks

Mr.Krulez said:
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Click to expand...
Click to collapse
I´m assuming you have xiaomi a2? it must match codename "jasmine"

luminoso said:
I´m assuming you have xiaomi a2? it must match codename "jasmine"
Click to expand...
Click to collapse
fastboot does say that my product is jasmine

Hello!
I just got this phone today and tried to update (8.0 November security update) and keep getting the same error!
I've tried with and without sim card, tried with and without my google acc, and tried with full battery!
Do not really want to unlock/install rom again... Any ideas?

Can I please get some help I think I might of bricked my phone

So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.

trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Was the boot img rooted, is that why you have no recovery? If so, just boot to fastboot mode and flash stock boot instead of root, that should have recovery

trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Can you go to bootloader screen ?
If you can
Just use the full stock Rom
Flash it
---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------
https://drive.google.com/file/d/1M2V1Jh2CS5vt1xbQYlDvhxfu0yB6hmZi/view
Download the Full Rom
Extract it
Use the exe file to install with bootloader screen

Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.

trustedenemy said:
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
Click to expand...
Click to collapse
Did you fix it ?

rowihel2012 said:
Did you fix it ?
Click to expand...
Click to collapse
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.

trustedenemy said:
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
Click to expand...
Click to collapse
But you get fastboot mode, just plug the USB in side port and flash latest raw WW Rom.
Here's the link to 1908.21
https://drive.google.com/file/d/13Mgz9GhopE-DUsGT3N_5qC283cKkUxYb/view?usp=drivesdk
Once in fastboot mode (the first menu you see, before selecting recovery, start, power off etc is fastboot mode) check your device is recognised with fastboot devices cmd and then run flashall_AFT.cmd that'll get back your working rom . But also, delete or move the original zip from that same extracted folder, the raw rom with the same name confuses the flashall_AFT.cmd

So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .

trustedenemy said:
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
Click to expand...
Click to collapse
Did you let the raw rom flash entirely? It should take a minimum of 10 minutes... The phone should reboot twice (I think) as it completes... Maybe try again, but I'm not familiar with that message...
If the phone doesn't reboot, I would let it run for a half hour or so before rebooting...

There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you

trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Excellent, glad you got it working again

trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Yes this way always fix bootloap problem
Thanks asus for this easy flashing

Mi9 Global - Accidentally locked bootloader and stock in recovery/fastboot

Hi,
Recently purchased a Mi 9 Global version, got the OTA update to MIUI 11, and everything was well. It is a superb phone, but I like to have root on my phones (mostly for Adblocking and System2, better control overall). I tried to install TWRP (custom version for Mi9) because I wanted to install Magisk/Root or try a different rom eventually. Anyway... I made a huge mistake. After trying to reboot, I noticed things had gone wrong, and was stuck in a boot loop. I guess I panicked and tried to flash the phone back to the latest global MIUI rom (Version 11, Android 10, from official site), using the Xiaomi Flash App but I did not uncheck the "clean and lock bootloader" checkbox on the bottom right of the app, which is somehow enabled by default. The flash failed at that time, for unknown reason, but it seems like it succeeded in locking my bootloader, with an empty partition, except for fastboot access and Mi Recovery module. I have to admit I've always been pretty lucky with all my previous flashes on other devices, and I guess I got a little careless. That was pretty stupid of me, in retrospect.
Since then, I am stuck in either Mi Recovery or Fastboot, and it seems that my originally Global Mi 9 with unlock bootloader has now a locked bootloader. Any attempt at either using the Xiaomi Flash utility gives me an error message ("Erase boot error"), and if I boot into Fastboot and try to flash TWRP, I get the "Remote:Erase is not allowed in Lock State" error.
From what I understand, my options are pretty limited now. The phone is still powered on, stuck in Recovery mode and rebooting every 5 or 10 minutes by itself (probably a way to avoid screen burn-in?), but I can't seem to be able to shut it down in anyway, as there are no fastboot commands to send a shutdown signal. And no matter what button combination I press, the phone always ends up rebooting.
I tried the Xiaomi Unlocker utility, but it needs the phone to be out of recovery to check the credentials binding the phone to my account. All data on the phone has been wiped already, so that's not an option. Two options I have seen :
1. Open the battery cover (required a heat gun and risky), to short some pins and try to flash while there is a short to circumvent the security. I'm not that brave yet, and since the phone is still running and has probably about 80% battery, I don't want to use a heat gun on the device.
2. Shady stuff involving paying 30 or 40 Euros to a random guy who can somehow make everything work magically by remotely logging in on my computer via Teamviewer (Not happening in a million years).
I'm wondering if there is an alternative, other than bringing the device to an official Xiaomi store (I'm in Bangkok and they do have one official shop at Fortune Town), but even then, I don't know if they'll just tell me I got myself an expensive paperweight.
Any help/insight regarding this issue would be much, much appreciated!

Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.

g_seva said:
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
Click to expand...
Click to collapse
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.

Twomby said:
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Click to expand...
Click to collapse
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.

g_seva said:
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
Click to expand...
Click to collapse
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.

To enter fastboot mode, long press the volume down key and the power key. Then unlock bootloader with Xiaomi app.

zahdekar said:
To enter fastboot mode, long press the volume down key and the power key. Then flash stock rom.
Click to expand...
Click to collapse
I have managed to enter fastboot mode, as described in my initial post. The problem is that when I try to flash, I get the following error: "Flashing not allowed in lock state".

Twomby said:
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
Click to expand...
Click to collapse
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.

g_seva said:
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
Click to expand...
Click to collapse
From what I understand, the "normal mode" needs the tool to be able to access the OS while it's running. I don't have an OS. I will give it a shot tomorrow (3 AM here, exhausted, and don't want to boot into Windows again!), but my hopes are not so high. Anyway, thanks for the help, much appreciated! Will let you know what happens! Cheers!

https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help

zahdekar said:
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
Click to expand...
Click to collapse
I've stumbled upon this link earlier today. But it's 404 on my end. Can you access it from where you are? Thanks!

http://c.mi.com/thread-2251372-1-1.html
This is on page 4

zahdekar said:
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
Click to expand...
Click to collapse
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!

Twomby said:
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Click to expand...
Click to collapse
I have the same problem! "The system has been destroyed" (((
And mi unlock tool not work abount 2 days (authorization not passes)

https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.

zahdekar said:
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
Click to expand...
Click to collapse
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!

Twomby said:
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Click to expand...
Click to collapse
Hello @Twomby did you managed to get it working it the end?

Same issue here
Hi,
I am encouraging the same issue. Does someone found a solution to this?

tago4ever said:
Hi,
I am encouraging the same issue. Does someone found a solution to this?
Click to expand...
Click to collapse
I came across this Mi8 thread, not sure if it's possible on the Mi9, but he seems to have been able to flash it through EDL mode, you might ask him the question: https://xiaomi.eu/community/threads/mi-8-bricked-from-nowhere.55723/#post-543605
There's also this Mi9 thread: https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966

Xiaomi Mi A2 stuck on boot-loop, any method/s to recover device with 0 data loss?

Hey folks,
I'm having trouble regaining access to my device.
I own Xiaomi Mi A2, and sadly it has been stuck on boot loop since around 10 days.
The issue occurred whilst it was being used on split screen mode. Device suddenly lag spiked and froze for a couple of minutes, then restarted and has been boot looping ever since on ‘android one’ screen.
–Device information–
Device: Xiaomi Mi A2
ROM: (system ROM has been untouched)
OS: Android 10
OEM: Locked
Bootloader: Locked
Root access: False
USB debugging: Disabled
Recovery mode: Accessible
Fastboot: Accessible
My question is, are there any method/s which let's regain access to the device whilst keeping all the data (including installed applications and their data) intact as they were prior to the ill-fated incident?
It may or may not affect the further procedures but it should be noted that i have attempted to force restart the device several times from recovery mode and it hasn't been any helpfull at all. The device seems to be bricked.
— I have explored on several other threads and forums, folks who were dealing with similar issues.
Then again, is it possible to fully recover the device with little to no data loss?
Any kind of provided help will be much appreciated!
Regards~

serenity salvation said:
Hey folks,
I'm having trouble regaining access to my device.
I own Xiaomi Mi A2, and sadly it has been stuck on boot loop since around 10 days.
The issue occurred whilst it was being used on split screen mode. Device suddenly lag spiked and froze for a couple of minutes, then restarted and has been boot looping ever since on ‘android one’ screen.
–Device information–
Device: Xiaomi Mi A2
ROM: (system ROM has been untouched)
OS: Android 10
OEM: Locked
Bootloader: Locked
Root access: False
USB debugging: Disabled
Recovery mode: Accessible
Fastboot: Accessible
My question is, are there any method/s which let's regain access to the device whilst keeping all the data (including installed applications and their data) intact as they were prior to the ill-fated incident?
It may or may not affect the further procedures but it should be noted that i have attempted to force restart the device several times from recovery mode and it hasn't been any helpfull at all. The device seems to be bricked.
— I have explored on several other threads and forums, folks who were dealing with similar issues.
Then again, is it possible to fully recover the device with little to no data loss?
Any kind of provided help will be much appreciated!
Regards~
Click to expand...
Click to collapse
You can recover the device but not your data.

KevMetal said:
You can recover the device but not your data.
Click to expand...
Click to collapse
That.. sucks.
Exactly how, which backdoor could have allowed me to regain access to the data?

serenity salvation said:
That.. sucks.
Exactly how, which backdoor could have allowed me to regain access to the data?
Click to expand...
Click to collapse
None that is why the bootloader comes locked.
If you had previously unlocked, maybe flashing twrp you be able to decrypt and adb pull via twrp or use mtp

serenity salvation said:
....Exactly how, which backdoor could have allowed me to regain access to the data?
Click to expand...
Click to collapse
With locked phone all SW backdoors are locked. The major hope is that after numerous reboot attempts phone will finally boot into the other slot, presumably having operative ROM version. The other hope is that it is a minor HW glitch like internal cable disconnection.

C4SCA said:
None that is why the bootloader comes locked.
If you had previously unlocked, maybe flashing twrp you be able to decrypt and adb pull via twrp or use mtp
Click to expand...
Click to collapse
Ah well, guess everyone shall keep 'em enabled incase phone automatically bricks... haha.

Aerobatic said:
With locked phone all SW backdoors are locked. The major hope is that after numerous reboot attempts phone will finally boot into the other slot, presumably having operative ROM version. The other hope is that it is a minor HW glitch like internal cable disconnection.
Click to expand...
Click to collapse
So there is still a hope.. at the very least.
Would that mean manually rebooting via recovery mode or just by holding the power button all day long...

serenity salvation said:
Hey folks,
I'm having trouble regaining access to my device.
I own Xiaomi Mi A2, and sadly it has been stuck on boot loop since around 10 days.
The issue occurred whilst it was being used on split screen mode. Device suddenly lag spiked and froze for a couple of minutes, then restarted and has been boot looping ever since on ‘android one’ screen.
–Device information–
Device: Xiaomi Mi A2
ROM: (system ROM has been untouched)
OS: Android 10
OEM: Locked
Bootloader: Locked
Root access: False
USB debugging: Disabled
Recovery mode: Accessible
Fastboot: Accessible
My question is, are there any method/s which let's regain access to the device whilst keeping all the data (including installed applications and their data) intact as they were prior to the ill-fated incident?
It may or may not affect the further procedures but it should be noted that i have attempted to force restart the device several times from recovery mode and it hasn't been any helpfull at all. The device seems to be bricked.
— I have explored on several other threads and forums, folks who were dealing with similar issues.
Then again, is it possible to fully recover the device with little to no data loss?
Any kind of provided help will be much appreciated!
Regards~
Click to expand...
Click to collapse
I'd try this:
reboot > (fast)boot
load TWRP boot.img
then use the fix boot loop option in advance settings and see what happens.

Exxdeea said:
I'd try this:
reboot > (fast)boot
load TWRP boot.img
then use the fix boot loop option in advance settings and see what happens.
Click to expand...
Click to collapse
In my case, bootloader is locked.. haha.

serenity salvation said:
Ah well, guess everyone shall keep 'em enabled incase phone automatically bricks... haha.
Click to expand...
Click to collapse
Yes for that but no in case it got stolen??

C4SCA said:
Yes for that but no in case it got stolen??
Click to expand...
Click to collapse
Fair point.

C4SCA said:
Yes for that but no in case it got stolen??
Click to expand...
Click to collapse
Stolen locked phone still can be reflashed in EDL/TEST-point. Unlocked bootloader won't expose your data if you are still using encryption and pwd-protection; Magisk still is capable to hide unlocked state (though Google can stop this any moment). So, IMO until Google does not enforce server SafetyNet checks in a way that cannot be tricked by Magisk devs, there are 0 reasons to have phone locked.

if you can get to fastboot mode try to run the "fastboot continue" command from adb.

Hi everyone,
I have similar issue on my xioami a2 lite. The phone stuck on bootloop.
I have UNlocked bootloader and fastboot is accessible. (the devices is rooted)
I think that the problem is "low space", in this days I saw the notification of low space available and often the phone restarted automatically.
Can I fix this? can recover data?
Is the possibility of deleting some files from a PC wrong as an idea? but how?
Very very thanks

Other questions: Can I try to erase cache from fastboot command? It's safe?

Update: I try to boot in TWPR, but I cannot "data" partition. (invalid password)
I noticed that my default slot is "partition B". (I don't remember witch one is right).
So, I chose Slot A and android will boot, all is OK but Magisk doesn't work. (I think that is flashed on partition B).
Now, I have deleted some files, now there is enough space. I try to set back partition B and android will boot OK but magisk app saw that "root permissions are lost, reinstall default apk".
Can Slot switch breaks magisk? what do you recommend to do?