I am using a Poco F4 5G device.
The problem started when I tried to partition my device to install Windows 11. I followed the tutorial on https://renegade-project.tech/en/install, and at first, everything seemed to be going smoothly. The problem arose when I attempted to partition the device. There were some explanations that I did not read carefully because I was feeling very sleepy. In the first explanation, I clicked "Ignore," and in the second explanation, I clicked "Cancel."
{
"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"
}
After I rebooted the system, I received an error message that said "System has been destroyed." Initially, I did not panic because I was used to dealing with such problems. However, after trying several methods that I usually use, none of them worked:
Installing a new TWRP
Using VB Meta
Flashing using PowerShell
Flashing using Mi Flash
when i try boot via twrp again :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img target reported max download size of 805306368 bytes sending 'recovery' (196608 KB)... OKAY [ 7.306s] writing 'recovery'... FAILED (remote: Flashing is not allowed in Lock State) finished. total time: 7.317s
Perhaps someone here has experienced the same problem and can provide some guidance.
ok so the problem is being generated because you haven't unlocked you bootloader, it's locked
you have to unlock it first
maybe your phone's bl got locked while u were installing miui, if it was unlocked earlier
Ok so, i looked into it, the brick happend cause the project you tried installing on poco f4 was made for poco f1
No, I had already unlocked it before I did it."
muzadidil said:
No, I had already unlocked it before I did it."
Click to expand...
Click to collapse
Your SOC Qualcomm Snapdragon 870 Chipset is not supported by this project.
The bootloader was locked following your unsuccessful tests.
Related
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"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"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.
i have a Encrypted BQ Aquaris X2 pro and want to flash los according to this guide https://wiki.lineageos.org/devices/zangyapro/install
oem-unlock = done
debugging mode = done
fastboot flash recovery twrp-3.3.1-0-zangyapro.img
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (63984 KB)...OKAY [ 2.005s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)finished. total time: 2.005s
I also changed the slot to a. That doesn't help either
if i try fastboot boot twrp-3.3.1-0-zangyapro.img, TWRP asking for password
Is there a known problem with TWRP?
May i get some help in here?
thanks in advance, and sorry english is not my first language
presely said:
i have a Encrypted BQ Aquaris X2 pro and want to flash los according to this guide https://wiki.lineageos.org/devices/zangyapro/install
oem-unlock = done
debugging mode = done
fastboot flash recovery twrp-3.3.1-0-zangyapro.img
I also changed the slot to a. That doesn't help either
if i try fastboot boot twrp-3.3.1-0-zangyapro.img, TWRP asking for password
Is there a known problem with TWRP?
May i get some help in here?
thanks in advance, and sorry english is not my first language
Click to expand...
Click to collapse
When German is your native language then study this thread:
https://www.android-hilfe.de/forum/...e-to-device-failed-command-failed.942534.html
In short, you can't flash a recovery that's why you have to boot the recovery directly.
AndroidenKalle said:
When German is your native language then study this thread:
https://www.android-hilfe.de/forum/...e-to-device-failed-command-failed.942534.html
In short, you can't flash a recovery that's why you have to boot the recovery directly.
Click to expand...
Click to collapse
Thanks a lot for your answer.
when i boot twrp directly, twrp asking for password. after cancel and format data i got an error failed to mount /data (no such 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"
}
presely said:
Thanks a lot for your answer.
when i boot twrp directly, twrp asking for password. after cancel and format data i got an error failed to mount /data (no such device).
Click to expand...
Click to collapse
Any news?
AndroidenKalle said:
Any news?
Click to expand...
Click to collapse
im sorry, im late
everything is working fine.
You have to extract the los.img and then install it via
HTML:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot erase userdata
because there is no working twrp for the device, you have to need the lineage recovery.
This is the solution in a german forum.
thanks everybody!
Good morning all.
I've a problem during the flashing of TWRP.img
- adb-Driver installed
- Mi A2 lite booted into fastboot
- computer and phone can't connect
- phone aborted the fastboot mode after some minutes
Phone Mi A2 lite latest Stock ROM
Computer windows 11 pro
Code:
C:\Users\Username>fastboot boot "D:\Username\Downloads\twrp-3.5.2_9-2-daisy-unofficial.img"
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.665s
Have you enabled bootloader unlocking in developer options?
Tech0308 said:
Have you enabled bootloader unlocking in developer options?
Click to expand...
Click to collapse
OEM Unlock
(Allow bootloader unlock)
yes, i did
{
"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"
}
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Tech0308 said:
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Click to expand...
Click to collapse
this command doesn't work, i'll get the output of all aviable commands, that's all
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Tech0308 said:
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Click to expand...
Click to collapse
thank you, that's it
I would like to know how to enter fastbootd! mode???
Enable the USB debug mode in the Developer options, install adb (it's the part of Android Studio, or as a separate tool for Linux available in the official repos) and execute "adb reboot bootloader".
This is FastBootd! mode ??
{
"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"
}
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
uluruman said:
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
Click to expand...
Click to collapse
so I can install GSI by the dynamic partitions
PaulinoBaslio said:
so I can install GSI by the dynamic partitions
Click to expand...
Click to collapse
Probably. May be. From my experience it simply doesn't work. It sorta flashes something but may be it just takes forever to complete or it's really just stuck but there's no response whatsoever. Fastboot mode is absolutely minimalistic, it does not report anything, no progress, nothing, and I guess it's intended to be like that, because it boots before anything else and theoretically allows you to flash even the very first bootloader. Anyway, I tried something like fastboot flash system lir-v316-220325-arm64-bvZ.img and the CLI tool reported Sending 'system' and then nothing else happened for the next 15 minutes or so, after which I just hit Ctrl+C, ran fastboot reboot and observed that nothing changed, the old system booted just like it was, so I guess nothing was really flashed, even partially. I don't know really, may be it's unpacked internally only when the image is fully uploaded and I didn't give it enough time, but for that time Odin would already flash the whole set of firmware. What else is to try, besides waiting more time, is converting the image to/from Android sparse format using the img2simg & simg2img tools, and try other partition names, such as "system_root" but I am sure this latter thing is absolutely wrong. The GSI system partition is called system, it just must be called that, system_root is something else (I guess it's the system root of the recovery mode).
TCL customer service replied as follow when asking about unlock bootloader
{
"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"
}
So there is no official way to unlock bootloader.sometimes there is a unofficial way to unlock bootloader with firehose (edl mode)
Magisk Patched Boot TCL 20 SE
Download
TWRP TCL 20 SE
Download
if you have the ability to unlock bootloader try above
(Sri Lanka) said:
TCL customer service replied as follow when asking about unlock bootloaderView attachment 5649523
View attachment 5649525
So there is no official way to unlock bootloader.sometimes there is a unofficial way to unlock bootloader with firehose (edl mode)
Magisk Patched Boot TCL 20 SE
Download
TWRP TCL 20 SE
Download
if you have the ability to unlock bootloader try above
Click to expand...
Click to collapse
You have tested the TWRP?
mutahharbashir said:
You have tested the TWRP?
Click to expand...
Click to collapse
no i count able to unlock bootloader
smiley9000 said:
TCL customer service replied as follow when asking about unlock bootloaderView attachment 5649523
View attachment 5649525
So there is no official way to unlock bootloader.sometimes there is a unofficial way to unlock bootloader with firehose (edl mode)
Magisk Patched Boot TCL 20 SE
Download
TWRP TCL 20 SE
Download
if you have the ability to unlock bootloader try above
Click to expand...
Click to collapse
Hi, how exactly do you obtain the boot.img? I have unlocked the bootloader but I don't have the stock firmware of it.
Edit: I tried to flash the magisk_patched.img that you've provided, but it has failed to flash, I guess this wasn't because of the image's fault.
Code:
E:\TCL\T671H>fastboot flash boot magisk_patched-25000_08uFS_from_xda.img
Sending 'boot_a' (98304 KB) OKAY [ 2.268s]
Writing 'boot_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed