Develop Bugs

Black screen - Bricked

Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.

zk_eu said:
Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.
Click to expand...
Click to collapse
That´s really strange... Will windows detect the phone when you connect it?
Maybe you´re in edl-mode. If yes, you could get out of it by pressing pwr for more then 10 seconds.
If that doesn´t help and you will not be alble to do anything (incl. going to fastboot) you can restore you phone by going to edl by usng the test point method. But thant will break your warranty - you have to open the phone...
If you want to do it you need to do the following.
1. Download latest fastboot rom and MiFlash
2. Install MiFlash, unpack fastboot rom and selct extracted folder in MIFlash.
3. Open your phone: https://www.youtube.com/watch?v=PmpHdqRUlDA
4. Remove the metal cover over the mainboard
5. Remove battery
6. short these both pins: https://www.youtube.com/watch?v=mhsRv42rsqI
7. connect your phone to pc (in device manager you should see "qualcomm qdloader 9008"
8. In MiFlash click on refresh (now you should see something with com-port)
9. On the lower right corner you can selct "clean all", "save user data" and "clean all and lock" - if you were on 10.0.3.0 before, you can select "save user data" if not, you have to wipe by selecting "clean all". Now click "flash"
I did this once and needed a few tries... It´s a bit tricky to connect both pins and then the phone to pc - after the 4th try I got it running.
I had the problem of locked bootloader and a not booting phone...

Hi!
Yes, Windows detects the device. I can see the phone in the device manager by the name Qualcomm HS-USB diagnostics 900E (COM10).
If I hold power on and volume up or down, I can hear via Windows sound that it gets reconnected. So there is some life still in it.
The device is also detectable by MiFlash tool. But unfortunately since I can't get into Fastboot, I can't flash it. I've been trying to flash it, but this is where I get (it just stays here no matter how long I leave the device):
{
"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"
}
I know about the method you posted. I still have a year and a half warranty on the phone. So I will sent it on repair and see what they will say. Maybe the won't notice and I will be able to keep my warranty.

i am in the same situation right now, after try to update the twrp, what tool you use to open the phone?.

I think you can also use the deepflashcable for the same effect.

[GUIDE/TIP]Failed fastboot flashing of stock ROM

I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. If you receive an CRC error, remove 2 lines from flashing script containing words CRCLIST and SPARECRCLIST and re-run it again
3. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
4. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.

_mysiak_ said:
I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
3. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.
Click to expand...
Click to collapse
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
i will try one more time, keep your fingers to me

NeverMind._. said:
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
Click to expand...
Click to collapse
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.

_mysiak_ said:
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.
Click to expand...
Click to collapse
I will do it on my notebook, if it will show error i will show you it, btw thx for helping me

wtf, i flashd with mi flash tool, after 6 minutes, it shows error, phone is showing redmi lol
btw it works, but now i have redmi 10t lite
{
"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"
}

try this program QPST_2.7.496

i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery

kammgl said:
i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery
Click to expand...
Click to collapse
For flashing you need to be in fastboot mode. If your phone is not detected correctly, most probably you have incorrect drivers installed (ADB instead of fastboot). Check from command line "fastboot devices" - you should see your phone connected. If it's missing, check your drivers in Windows device manager.

Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc

tze_vitamin said:
Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc
Click to expand...
Click to collapse
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.

_mysiak_ said:
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.
Click to expand...
Click to collapse
I remove 4 lines but still have the same issue. I reopen MI flash tools, upload ROM again,and still showing the same error, I will upload pics later

I was using my phone normally, I left it charging and when I looked at it again, it would restart non-stop. It's a Xiaomi Mi 10T Lite, I held the power button, but it didn't turn on, it just came back to the bootloader screen, I didn't try to format it as I was trying to recover my files.
So I thought about unlocking the bootloader to get access to my files, I used Mi Unlock Tool, but it doesn't work. I still have access to my account phone number and email address. But I couldn't unlock by this method.
Please I need your help. Thank you

Redmi note 8 wipe all partitions since twrp got bricked

Bien...
I was trying to flash the EU rom on my Redmi Note 8, but I did wype to all the partitions, until that moment I had informed myself about how to flash, how to root and use twrp, but the issue of the partitions still did not know, I selected all the partitions except data and sd and I did wype, in the end my cell phone was completely bricked, I try to turn it on and for a period of less than half a second, I get the Redmi logo, below it says Powred by Android and above I get a padlock open indicating that the bootloader is unlocked, then I get a screen with the message "System has been destroyed" and then it turns off, unless I put it to load, in that case it enters the bootloop state, I cannot enter the recovery but yes I can enter fastboot, I tried to flash it through My Flash Tool and ADB, the problem is that the computer recognizes that the bootloader is unlocked, but when flashing it, a message appears that the bootloader It is locked, so flashing it is not an option, for that reason, I assume that the testpoint method for flashing by EDL would not work either.
That happened three weeks ago, at first I did not know the reason for the problem, later I learned more, I will not make that mistake again, but I am interested in knowing if there is a software solution; I would be interested in being able to download all the partitions and install them on my cell phone using the computer, I don't know if any of those who read this have the opportunity to find the partitions and share them here, I don't know if it is a realistic option, but I have hope, I saw that That solution worked with a OnePlus 3 and that's why I'm looking for information about my cell phone. The only other option I can think of is to change the motherboard, but it's very expensive and with that money, I'd better buy another cell phone.
By the way, my cell phone was in very good condition despite having used it for a year, it was very well cared for and I had no problems with both software and hardware, the reason why I was trying to change to the EU rom is because the Global version was to be a decaf version of the update.
I hope that someone can help to find a solution. Thanks for your understanding.

Diego_Arturo said:
Bien...
I was trying to flash the EU ...
Click to expand...
Click to collapse
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended

loopypalm said:
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
Click to expand...
Click to collapse
I understand what you are saying, the problem is that I deleted all the partitions (/ boot, / system, / misk, and several others that I do not remember), the only ones that I did not delete were sd and data. I read that if you delete the boot partition, you should not restart the cell phone, you must flash a rom with the boot partition, if you don't, the cell phone will not start the operating system
Another thing: I didn't flash any ROMs, twrp didn't read my storage well and couldn't find the .zip file of the EU rom, I just wipe and reboot without flashing anything. I do not know why the cell phone still detects the system for a very brief moment before showing that the system has been destroyed, the problem is that it does not start. And when I try to flash the original ROM, the computer detects that the bootloader is unlocked, but when flashing I get an error saying that it is locked, it occurs to me that possibly the bootloader was one of the first things to be erased, but it was not completely erased Maybe the kernel or ramdisk was deleted and after that everything stopped and the cell phone just bricked, I don't know if I'm correct.

Diego_Arturo said:
I understand what you say, the problem is that I did wipe to all partitions, (/ boot, / system, / recovery, / cache, / misc and several others that I do not remember), I just did not wipe to SD and data partitions. I understand that if you delete the boot partition you must have a ROM ready that comes with a boot partition, or else you would be left with a hardbrick. What I don't know is if I can force the installation of all partitions.
Click to expand...
Click to collapse
-how did you wipe recovery ? did you use flashtool or something ?
-all roms now comes with boot img (boot partition is where the kernel files are stored) , so no problem wiping it (same for dalvik/cache/system/vendor/data)
yes, you can flash img files of partitions using fastboot (if that what you mean with force install a partition)
-what you should try now is reinstalling twrp 1st

nteresting ... It reassures me to know that I don't need to search for the partitions separately and only need to flash the ROM, although I am concerned about the same problem when flashing. I tried to flash using Mi Flash Tool, ADB and XiaoMi Tool V2, but it is always the same problem, it detects the unlocked bootloader, but when flashing it gives me an error.
I deleted all the partitions from TWRP, it was weird, because the videos didn't show many of the partitions that came out for me, that's why I don't remember them. Before doing wipe I made a copy of everything in case something went wrong, but in the end everything went wrong ...
Now that I remember, I deleted the partitions because when I tried to do anything, I got red letters and TWRP wouldn't let me do anything, when I deleted them the letters turned blue.
It seems to me that I tried to install TWRP from XiaoMi Tool v2 although I don't remember correctly, I will try and write again.

I HAVE ADVANCES!
I flashed the partitions one by one because Flash Tool still does not let me flash the ROM, on one occasion I flashed the system, but in the end it did not finish flashing, I still got the error "System has ben destroyed", I kept flashing partitions but there was no Result, in the end I flashed the system again and when it finished flashing, the error system has ben destroyed no longer appeared, now my cell phone is in a permanent bootloop state with the redmi logo, but it already lets me enter TWRP, I can't flash it from the computer, I'm going to try to get an SD card and flash it from recovery, I'm going to try to flash the EU ROM, but it's already a breakthrough, I don't have a hard brick anymore.

Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
I thank you very much for helping me find a solution, I hope this helps someone else and this serves me as my experience, I managed to solve a serious problem that I made and you helped me ... Thank you very much.

Diego_Arturo said:
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
Click to expand...
Click to collapse
Glad it work for you ^........^ !
all sensors are working fine ?
Diego_Arturo said:
Thank you very much.
Click to expand...
Click to collapse
you know what to do
{
"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"
}

For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.

Diego_Arturo said:
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Click to expand...
Click to collapse
Miui roms are resource hungry and lag is not their only problem , battery and performance are also affected ...
i think you should try custom roms

First, I didn't want to, I preferred to wait, but seeing how slow the cell phone was and how fast the battery was draining, I felt that the best in the long run would be to install a ROM that did not consume so many resources, so I installed the latest version of Pixel Experience. I have to say that I did not expect anything from this ROM, I just expected fluidity and more battery, but in the end I liked it. I personally like MIUI, but I think that Pixel Experience could extend the life of my cell phone. I will continue using it and possibly in the future I will return to MIUI to see how it goes.

Partly bricked... SM-N975F

Hey guys.. Ive been a visitor in XDA forums for quite a while... And i been running root and custom FW with more or less every samsung from S2 and up...
But i just got my self a note10+ (atleast thats what ive been told) and i wanted to root it up and throw a custom FW on it to run in Samsung Dex...
So i succeded updating the FW. I unlocked the bootloader in dev. options. and unlocked it again in download mode by holding the vol. up. key!
But since then i had problems... every time i run a FW in Odin... Then if i dont get a error saying
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: B BINARY 7
pit_flash_binary - Unsupported version
Then i succeds but when its going to erase everything after the reboot from download mode then it starts up and stops right after... And then i can only go recovery mode and download mode... How do i just write the correct firmware and have it start up like normal... just wanna undo it all... Do i need some kind of samsung support software in windows? and how do i know if it is a note10+ ... Even though download mode says SM-N975F... But still i get error when i flash a FW downloaded with Frija for that model...
Hope to get some help

oh btw... it connects as this when im in download mode:
"Checking Connected Devices: SAMSUNG Mobile USB Modem #2 ( COM12 )"
is that normal?

bump?

Hey there,
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 8 BINARY 7
Click to expand...
Click to collapse
This, as far as I understand just means that the bootloader on your phone is on a newer version than the one in the firmware you're trying to flash. Usually flashing just stops there.
Then i succeds but when its going to erase everything after the reboot from download mode then it starts up and stops right after...
Click to expand...
Click to collapse
You COULD try to simply boot into recovery and wipe the device once, the phone would usually do that on its own but sometimes fails. Mind describing what exactly happens?
how do i know if it is a note10+ ... Even though download mode says SM-N975F...
Click to expand...
Click to collapse
For that, you either need the original packaging or just trust on what Odin-mode is telling you.
But still i get error when i flash a FW downloaded with Frija for that model...
Click to expand...
Click to collapse
I kinda don't trust Frija. For me, Bifrost always worked like a charm. Use it to download the firmware for your SM-N975F and give it your correct region code.
For flashing, some people use Heimdall, I think Odin is pretty simple (as far as simplicity in modding goes).
By the way, if all fails, you could try installing LineageOS 19.1, throw in openGAPPS for Googles apps and Magisk/Lygisk for root (if needed).
Good luck and have fun!
Cheers!

I found out i got EXACKLY the same issue as the guy writing on this thread:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Nic0_ said:
You COULD try to simply boot into recovery and wipe the device once, the phone would usually do that on its own but sometimes fails. Mind describing what exactly happens?
Click to expand...
Click to collapse
Already tryed still nothing... But what happens after a 100% succes in Odin is:
Then it reboots and after a few secs it says "Erasing device" for like 0.5 sec... And then it only goes black screen... At black screen then i can only go download mode if i press both volume buttons at the same time for 1 sec. Or recovery mode if i press vol up and power. And thats only if i have a USB-C connected ofcourse.
And whats the issue is... when it stops erasing the device... Why does it stops after 0.5 secs? it normally goes like 2-5 secs ... But also ... After it stops and in black screen... If i continue into download mode and open up the bootloader then...
{
"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"
}
I been around TWRP, Original recovery and Lineage recovery... But as the guy writes on the other thread. Then it shows 0 MB on the data partition, and i have to format it before it shows up again with 223 (or something)GB again...

Hey there,
Could you try switching file systems around? TWRP lets you format your partitions with stuff like ext4, f2fs and some other file systems. On several custom ROMs, the file system sometimes is the difference between a system working or bootlooping.
Good luck and have a nice day.
Cheers!

Already tryed exfat and f2fs and then back to ext4

I might have found a solution

I tried to update firmware N9750 android 11 to android 12 with (Ap file + odin patched). I don't flash bl ,cp,csc files . the phone screen shows a software error, need to open the smart switch software on the computer to recover. I open the smart switch on the computer and it does not recognize the phone. odin patched still recognizes the phone is connected. i reset odin and flashed 1 BL file. phone booted again with bootloader + AP file is android12. and modem and csc are android 11
1: Try flash combination firmware?
2 : Try download firmware stock new bootloader
Download odin patched
Try flash firmware files one by one
restart phone go download mode flash file BL ..done
restart phone go download mode flash file AP
restart phone go download mode flash file CP
restart phone go download mode flash file CSC
If ok flash full 5 file
sorry my english is not good

someone could help please?
S20 FE bootloop after security update
So I never posted here but I usually pass by some topics so sorry for any mistake in creating this discussion. Today I deleted some stuff from my S20 FE and downloaded via OTA the march security update in my device, then I was caught by surprise...
forum.xda-developers.com

Question Red Warning and UnWorking Lockscreen. HELP

{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)

Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...

redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?

Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely

i have this error also what should i do?
the phone not boot up
the red warning are stuck

yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.

[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!

yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.

[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!

turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"

izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.