Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
maybe you should tell more info about your device, brand,chipset, etc ?
so people can be more easy to help.
just newbie suggestion, ignore this if its no help xD
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
lolet said:
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
Click to expand...
Click to collapse
The system image is not corrupted, because I can safely flash it using Clockworkmod. The filesystem is yaff2, and I have tried opening it using some software and my file is there. I think the problem lies on fastboot who failed flashing properly.
simple
yokowasis said:
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
Click to expand...
Click to collapse
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
I stuck with my Mate 9 Error mode numbers 11 and 2
MEGHSHAH said:
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
Click to expand...
Click to collapse
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in a tutorial
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Hi, all.
I was messing around with Android Tweaker 2, zipaligning my apps, performing vague system tweaks and the like, when I rebooted my phone for the changes to take effect; however, the phone booted up, finished the booting animation, and where the home screen should be showing up only showed a black screen. From there I can only reboot again, reboot into STOCK recovery, or reboot into fastboot, which has limited function in an Asus device (inability to flash unsigned custom recovery images, inability to flash rom images, stock firmware images are unavailable ANYWHERE, etc.) My device WAS rooted, however, I did a factory reset from the stock recovery in hopes that the problem would be resolved, so I'm not sure if root access was retained. I've tried a lot of things, but what I need is access to adb to push some files, or just figure out what the hell happened to the device.
Any ideas? Thanks in advance.
Details:
Asus Padfone X [4.4.2 stock rom]
WAS rooted
LOCKED bootloader
STOCK recovery
Fastboot is basically useless, given the "safeguards" Asus has implemented
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
daggorlad said:
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
Click to expand...
Click to collapse
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
shattered519 said:
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
Click to expand...
Click to collapse
Glad I was able to point you into the right direction.
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes. Trying different block sizes didn't help neither.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Thunder Storm said:
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Click to expand...
Click to collapse
Try getting rid of the bs part. Flash the image at it's normal size.
Sent from my XT1609 using Tapatalk
Thanks for your reply.
I flashed both TWRP and stock recovery without the bs parameter. Same results as before: it doesn't boot into recovery.
Okay, so I own a Red Magic 6 and it's currently bricked. There is no unbrick tool for this device yet and there isn't going to be one for a while.
My bootloader is unlocked. I have tried reflashing the files using fastboot. However when I go to flash the system, it prints out:
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (786352 KB) OKAY [ 18.114s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
(Phone came with a/b partition just a heads up and it runs on Stock android 11)
I have searched EVERYWHERE, from forums, to tools, to python scripts.... EVERYTHING. No solution.
Yes, my fastboot is on the lastest version and yes I tried the --force command on fastboot. Still no luck.
I have researched everything about sparse images but am still having problems. I tried converting the image to a RAW ext4 img but it fails.
Is there any workaround for this?
chocolote4444 said:
Okay, so I own a Red Magic 6 and it's currently bricked. There is no unbrick tool for this device yet and there isn't going to be one for a while.
My bootloader is unlocked. I have tried reflashing the files using fastboot. However when I go to flash the system, it prints out:
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (786352 KB) OKAY [ 18.114s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
(Phone came with a/b partition just a heads up and it runs on Stock android 11)
I have searched EVERYWHERE, from forums, to tools, to python scripts.... EVERYTHING. No solution.
Yes, my fastboot is on the lastest version and yes I tried the --force command on fastboot. Still no luck.
I have researched everything about sparse images but am still having problems. I tried converting the image to a RAW ext4 img but it fails.
Is there any workaround for this?
Click to expand...
Click to collapse
I am looking for the same thing. Can't find the answer. Have you found a solution?
same here
Out of curiosity, was there ever a resolution to this issue?
Have RM6SP, was rooted- all good. Battery ran empty and shut off. When I rebooted it just boots directly to fastboot. Recovery is useless (wiped user data but no cache to erase(?)).
Extracted payload.bin, tried flashing boot.img, rebooted, only goes to fastboot. Tried flashing everything from payload.bin- some flashed, others had errors. Just endless loading to fastboot.
Curious if anyone has actually SUCCESSFULLY unbricked these devices?
Looks like your partition table may be corrupted... I don't own this device myself but have a fairly good understanding of android partitions and am happy to help.
Please show the output of
Code:
fastboot getvar ptable
and the errors you get when trying to flash
Hello DavidxxxD and thank you for replying.
Execution of "getvar ptable" results in "FAILED (remote: 'Unknown variable')
I then executed "getvar all" and attached the result. Same whether on fastboot or fastbootd.
As for your other question, when I try to flash product, system, and vendor I get the above "Invalid Sparse File Format at Header Magic" error.
Thank you for any suggestions and your time. This is not my daily driver so there is no urgent, pressing need (I'll never get rid of my trusty S7edge, lol).
EDIT: thanks to the unbrick tool in the 6S Pro forum, I have successfully unbricked this phone. Up and running and on way to getting re-rooted.
Thanks to everyone who offered help!
Glad to hear you already got it unbricked!
For the sake of it being an intresting case, here is the more complicated way I put together and what I could find out from looking at the attatchment and a payload file for your device:
Good news - Your device is not too badly bricked.
Like some other new devices, this phone does not use a cache partition. That is why the recovery has no option to wipe cache.
The "invalid sparse header" message gets triggered when using fastboot to send a filesystem image that is not in the expected android sparse format. This can safely be ignored as the images for your device are uncompressed and the program doesn't know what they're suppsed to look like.
The NX669J uses a dynamic partition and the one on yours appears messed up in a way where I have no idea how it got to this point - all partitions for the A-slot are missing and instead there is a "system" (not system_a) and "system_b-cow" (!?) - This is probably why the bootloader is freaking out.
Usually, something like this can be fixed by just reflashing the super partition. However the update payload does not seem to contain one, so - unless you have a super.img from somewhere else - you would have to manually fix the current layout.
- Put the device is fastbootd mode
Code:
fastboot reboot-fastboot
Note: To verify, you can run
Code:
fastboot getvar is-userspace
Note: Didn't expect to have to say this, but don't run these commands on devices with correctly assigned partitions, unless you know what you are doing! They can be used as an example of how to modify dynamic partitions. "system" is also used as an alias for the active system partition. You will likely softbrick your device and have to fix it!!
- Firstly, remove the strange partition entries
Code:
fastboot delete-logical-partition system
fastboot delete-logical-partition system_b-cow
- Next, re-create the missing entries
Code:
fastboot create-logical-partition system_a 1000
fastboot create-logical-partition system_ext_a 1000
fastboot create-logical-partition product_a 1000
fastboot create-logical-partition vendor_a 1000
fastboot create-logical-partition odm_a 1000
Note: 1000 will set the partition size to a kilobyte. This doesn't matter as flashing will automatically resize them.
- After that, you should be able to flash to the newly created partitions
Code:
fastboot flash system_a system.img
fastboot flash system_ext_a system_ext.img
fastboot flash product_a product.img
fastboot flash vendor_a vendor.img
fastboot flash odm_a odm.img
Note: If you get an error saying "not enough space to resize partition", try
Code:
fastboot erase system_b
fastboot resize-logical-partition system_b 1000
- Finally, set the active slot to A and reboot
Code:
fastboot set_active a
fastboot reboot
Note: If it doesn't boot or the system starts crashing, you may have to flash the other firmware images as well or try using slot B.
In case this doesn't work, you can ask someone with a rooted NX669J to dump their super partition and send it to you. If you do, make sure to check it first using lpdump. Flashing a corrupted image is going to make it worse 100% guaranteed.
I hope this gives you a better idea of what was wrong and how to deal with similar issues in the future. Of course, a low-level unbrick tool works fine too - but where's the fun in that?
P. S: I'm actually typing this on a flat S7 - still an amazing device, 6 years after release : )
Thank you, DavidxxxD, for taking the time out and providing a detailed reply. Hopefully this info might come in useful to someone one day.
I have no idea why a dead battery would "zonk" the phone, but it did. I wonder if it might have been something with magisk...?
¯\_(ツ)_/¯
Sadly, these phones are not popular and support from Nubia is painful, at best. Thanks to folks like you there is still help for those in need.
Again, many thanks for your time and help!
DavidxxxD said:
Glad to hear you already got it unbricked!
For the sake of it being an intresting case, here is the more complicated way I put together and what I could find out from looking at the attatchment and a payload file for your device:
Good news - Your device is not too badly bricked.
Like some other new devices, this phone does not use a cache partition. That is why the recovery has no option to wipe cache.
The "invalid sparse header" message gets triggered when using fastboot to send a filesystem image that is not in the expected android sparse format. This can safely be ignored as the images for your device are uncompressed and the program doesn't know what they're suppsed to look like.
The NX669J uses a dynamic partition and the one on yours appears messed up in a way where I have no idea how it got to this point - all partitions for the A-slot are missing and instead there is a "system" (not system_a) and "system_b-cow" (!?) - This is probably why the bootloader is freaking out.
Usually, something like this can be fixed by just reflashing the super partition. However the update payload does not seem to contain one, so - unless you have a super.img from somewhere else - you would have to manually fix the current layout.
- Put the device is fastbootd mode
Code:
fastboot reboot-fastboot
Note: To verify, you can run
Code:
fastboot getvar is-userspace
- Firstly, remove the strange partition entries
Code:
fastboot delete-logical-partition system
fastboot delete-logical-partition system_b-cow
- Next, re-create the missing entries
Code:
fastboot create-logical-partition system_a 1000
fastboot create-logical-partition system_ext_a 1000
fastboot create-logical-partition product_a 1000
fastboot create-logical-partition vendor_a 1000
fastboot create-logical-partition odm_a 1000
Note: 1000 will set the partition size to a kilobyte. This doesn't matter as flashing will automatically resize them.
- After that, you should be able to flash to the newly created partitions
Code:
fastboot flash system_a system.img
fastboot flash system_ext_a system_ext.img
fastboot flash product_a product.img
fastboot flash vendor_a vendor.img
fastboot flash odm_a odm.img
Note: If you get an error saying "not enough space to resize partition", try
Code:
fastboot erase system_b
fastboot resize-logical-partition system_b 1000
- Finally, set the active slot to A and reboot
Code:
fastboot set_active a
fastboot reboot
Note: If it doesn't boot or the system starts crashing, you may have to flash the other firmware images as well or try using slot B.
In case this doesn't work, you can ask someone with a rooted NX669J to dump their super partition and send it to you. If you do, make sure to check it first using lpdump. Flashing a corrupted image is going to make it worse 100% guaranteed.
I hope this gives you a better idea of what was wrong and how to deal with similar issues in the future. Of course, a low-level unbrick tool works fine too - but where's the fun in that?
P. S: I'm actually typing this on a flat S7 - still an amazing device, 6 years after release : )
Click to expand...
Click to collapse
Hi DavidxxxD,
I had a quite a similar problem here, sometimes ago while trying to install TWRP and Magisk onto my nubia Z20 NX627J, unfortunately did not succeed and got myself a bricked phone. Now phone can only go into fastboot mode.
Had been trying to flash everything from scratch via fastbboot, did not get any error messages with flashing all the img, bin except while flashing system. img, it returned with a " Invalid sparse file format at header magic" but went on with the process without issue. However, the phone still enable to boot up normally.
Is it possible that that the rom I have is not the original stock rom?
So while searching for an answer, was happy to found this thread at XDA forum. After going through the thread on your reply to SkylineDriver, i was hoping you can help and enlighten me if I had miss anything.
Attached is the getvar file from my bricked phone after flashing, another file is the fastboot command I followed, except the flash system command, i just did a "fastboot flash system system.img" without the "-S 100M' because I didn't know what "-S 100M" means".
Thanks in advance
@cksy1112 A bit late, but here are some things I noticed:
Are you sure your bootloader is unlocked? The device says it's locked. What happens when you send the unlock command?
You may need to flash vbmeta with the option --disable-verity.
This device has a painful ammount of partitions and whoever designed it should be punished for making my head hurt.
Not sure about the -S 100M thing, haven't seen that before and the system has to be larger than 100 megabytes.
Also, I don't think it's necessary to erase that many partitions before flashing.
It even has UEFI with a partition to store variables - that is very intresting and could have some great potential for multi-booting and other fun stuff - if we can understand how their implementation works.
chocolote4444 said:
Okay, so I own a Red Magic 6 and it's currently bricked. There is no unbrick tool for this device yet and there isn't going to be one for a while.
My bootloader is unlocked. I have tried reflashing the files using fastboot. However when I go to flash the system, it prints out:
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (786352 KB) OKAY [ 18.114s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
(Phone came with a/b partition just a heads up and it runs on Stock android 11)
I have searched EVERYWHERE, from forums, to tools, to python scripts.... EVERYTHING. No solution.
Yes, my fastboot is on the lastest version and yes I tried the --force command on fastboot. Still no luck.
I have researched everything about sparse images but am still having problems. I tried converting the image to a RAW ext4 img but it fails.
Is there any workaround for this?
Click to expand...
Click to collapse
Hello,
Have you find a solution to your pronlem?
is there an unbrick tool for red magic 6s pro?
I think I messed up my phone and it is brick because the super image is not updating for product system etc when I tried to flash the extracted ROM images. system and product coyld not be flashed. and sparse error apperas.
Did you install them in fastbootd mode? (Not regular fastboot)
DavidxxxD said:
Did you install them in fastbootd mode? (Not regular fastboot)
Click to expand...
Click to collapse
Thanks for the quick reply
I can’t boot to fastbootd. It gives an error and boot back to fastboot
You can try to flash the non-dynamic partitions first and then try again.
DavidxxxD said:
You can try to flash the non-dynamic partitions first and then try again.
Click to expand...
Click to collapse
hey so i also deleted cache partition
should i do
fastboot create-logical-partition cache 1000
to make cache partition?
i did do that and now its flashing, its showing less errors then last time lol
edit: what should i do to make cache partition?
Hello, I tried the commands DavidxxxD gave, but my phone is now stucked in a bootloop, I have a Xiaomi 11T. And the commands weren't working, it said "deleting 'system'..." but after it said "command failed".
Try creating it again and flash the image in fastbootd.
Is your device A/B? Use
Code:
fastboot getvar all
to learn more.
solution - Use SDK platform 33.03 instead
I'm trying to boot an image without flashing it to my Xiaomi:
fastboot boot Image
creating boot image...
creating boot image - 35883008 bytes
Sending 'boot.img' (35042 KB) OKAY [ 0.829s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Isn't there a way to do it? It's a Poco M3
Poco M3 has separate recovery partition and TWRP is available too. Why don't you flash it?
You mean flashing the kernel to the recovery partition? How would this work? Flash boot.img to recovery, then do adb reboot recovery, and test the kernel,without rewriting the original kernel?
aIecxs said:
Poco M3 has separate recovery partition and TWRP is available too. Why don't you flash it?
Click to expand...
Click to collapse
You mean flashing the kernel to the recovery partition? How would this work? Flash boot.img to recovery, then do adb reboot recovery, and test the kernel,without rewriting the original kernel?
no I mean flash boot.img to boot and twrp to recovery as usual. I am using this TWRP - encryption only worked on very first boot (don't ask me why) but that was good enough to backup userdata and everything