Develop Bugs

device unable to boot Error - mdtp image is corrupted

Hi there,
I have a problem i was try to root my phone.
Now i dont have access to ADB but only fastboot works.
If i start my phone it goes on fastboot mode, and if i try "fast boot twrp-3.3.0-0-daisy.img" i get the error "device unable to boot Error - mdtp image is corrupted"
Can some one help me out, if tried to download the image again but without success..

You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.

a1291762 said:
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
Click to expand...
Click to collapse
Sorry im a little bit noob, but how it works:
flastboot flash a?

fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.

Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
a1291762 said:
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Click to expand...
Click to collapse

mj2o said:
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
Click to expand...
Click to collapse
No OS installed is maybe cause the last rom that you flashed was not flashed in the right slot or correctly flashed.
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.

SubwayChamp said:
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
Click to expand...
Click to collapse
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.

mj2o said:
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
Click to expand...
Click to collapse
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.

I have the same problem, what you have did to fix? please

Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.

mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
hi
same issue here @mj2o: Can you please provide a link to the site in English; it all in Chinese and I cannot read it
Thanks

mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
SubwayChamp said:
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
Click to expand...
Click to collapse
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.

BenG7 said:
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
Click to expand...
Click to collapse
Why do you want to flash the bootloader, what is the issue?

Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Device unable to boot. Error - mdtp is corrupted

BenG7 said:
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Click to expand...
Click to collapse
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread

Thanks SubwayChamp,
Will try as advised and keep you updated.
I m going to look for the fastboot rom for my daisy.

SubwayChamp said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Click to expand...
Click to collapse
@SubwayChamp
dit it and when I
Code:
fastboot reboot
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
[EDIT]
realised I can
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
and I can flash the twrp-installer-daisy-3.3.1-0-offain.zip
but if I want to reboot; it says
Code:
No OS installed! Are you sure you wish to reboot?
so I went on with flashing lineageos 16
but at the end of the flash, I get
Code:
Failed to mount '/system' (permission denied)
please advise

BenG7 said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use and
@SubwayChamp
dit it and when I
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
Click to expand...
Click to collapse
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.

SubwayChamp said:
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
Click to expand...
Click to collapse
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!

BenG7 said:
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
Click to expand...
Click to collapse
This is exactly what I tried to tell you: your issue concerning to this thread was solved.
Now you have an issue regarding how to flash and boot to system attempting to install LOS. TWRP is perfectly capable to mount/remount or unmount partitions if needed, no need an action from the user, this is not the reason why you are not booting but the method and steps is discussed more properly in the same thread.
From here you can take one of hese three routes:
- To insist with trying to flash LOS.
- Flash other rom or a previous known working rom.
- Return completely to stock by flashing a full global rom.
Just I could recommend that for the future when you flash a stock rom take a backup of the most important partitions (without userdata) this could avoid that you need to use EDL anymore.

[GUIDE] How to root your Asus Zenfone 6 without TWRP | Info about A/B

Hey guys and girls,
This is a bit of copy and paste for from my guide for the HTC U12+. I thought it might be helpful to people here too.
If you find mentions of the HTC U12+ please notify me and I will correct them.
I couldn´t find any guide on how to root the Asus Zenfone 6 without twrp yet, so I thought maybe it´s good to have one. It´s also useful for people who don´t like to boot/flash the recovery but want root access.
I also decided now to do a little write up about the A/B slot partition system.
General Information about the A/B slot partition system and seamless updates
Google firstly introduced seamless updates on the Pixel Phones and with it the A/B partition system.
So this means, contrary to non A/B devices, there are two copys of most partitions except userdata.
We have two system (system_a and system_b), two boot (boot_a and boot_b) and two vendor (vendor_a and vendor_b) partitions, amongst others (can be found further down in the partition list but let´s concentrate on these).
When booted in the OS, one slot is actively used and the other is "inactive".
The main advantage that emerges now is, that in case an OTA arrives the "inactive" partitions get updated, while the OS is running. That means while the actual OTA is happening you can use your phone just like you always do.
The following reboot will boot into the former "inactive" slot and use the seamless updated partitions. This happens seamless and just with a reboot. So OTAs are much faster!
If you are interested further here are some links:
https://www.xda-developers.com/list-android-devices-seamless-updates/
https://source.android.com/devices/tech/ota/ab/
https://source.android.com/devices/tech/ota/ab/ab_faqs
Here’s another writeup from the XDA portal!
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But here are a few tips and tricks:
How to reboot to bootloader to be able to use fastboot:
From booted OS with buttons: Press and hold power down until the screen goes black, then press and hold power and vol up to enter bootloader
non responding and the phone isn´t booting: press and hold power plus volume up to enter bootloader
From the OS or recovery via ADB (requires USB Debugging enabled in dev options):
Code:
adb reboot bootloader
How to get the active slot:
Code:
fastboot getvar current-slot
How to set the active slot:
A word of advice. If you don´t know what you´re doing you should probably not change slots. Because my U12+ only has a working A Slot. The B slot is without the first OTA or flashing a RUU unbootable.
Set active slot to a:
Code:
fastboot --set-active=a
Set active slot to b:
Code:
fastboot --set-active=b
How to extract the boot.img from a firmware.zip
1. Download the firmware zip from here : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
2. Follow the steps described here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
3. Obtain your boot.img
How to root your phone without TWRP
Prerequisites:
- unlocked bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries (can always be found here
- working adb and fastboot environment
- magisk-patched boot.img
How to:
1. Download the latest magisk manager from here and install it on your phone: https://github.com/topjohnwu/MagiskManager/releases
2. Get a boot.img that fits your current firmware. Look at the point above, how to extract it from an Asus firmware zip.
Important: if you decide to use a pre-patched boot.img (available below), download it and place it in your fastboot folder, then skip to step 11!
3. Copy the extracted boot.img to your phone
4. Open the magisk manager app and tap two times on install
5. Now choose patch boot.img file and select the previously extracted boot.img you copied to your phone in the upcoming file chooser
6. Wait for the boot.img to be patched
7. Now connect your phone to your pc and make sure usb debugging is enabled in developer options
8. Open up a terminal in your fastboot folder and make sure adb is working by typing
Code:
adb devices
into terminal which should return your serial number
9. Pull the patches boot.img to your fastboot folder via:
Code:
adb pull /sdcard/Download/magisk_patched.img
10. Reboot to bootloader:
Code:
adb reboot bootloader
11. Flash the magisk patched boot.img:
Code:
fastboot flash boot magisk_patched.img
12. Congratulations you´re now rooted.
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609

Is it possible to do this and still get OTA updates from ASUS?

sidamos77 said:
Is it possible to do this and still get OTA updates from ASUS?
Click to expand...
Click to collapse
You need to unlock the bootloader for this which will prevent you from getting ota updates automatically from asus. But you can install updates manually.

Ok, great, thank you.

Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.

Any way to unofficially unlock the Bootloader?

vasra said:
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Click to expand...
Click to collapse
In Europe unlocking the bootloader and rooting doesn't legally void warranty. It was ruled this way a few years ago.

Freak07 said:
[...]
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Click to expand...
Click to collapse
The folder WW_PHONE-16.1210.1904.75-0 which is the firmware my device has, is empty. Do you still have the prepatched boot.img of that version ? ASUS doesn't have that version for download anymore.
Thanks in advance.
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?

GRöder said:
how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-26#post-2433773
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-37#post-2442236
Use Translator.

I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .

GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
the getvar command returns the following output:
Do you have any advice for me ?
Edit:
After being curious and trying which worked, I tried to flash it at the active slot b explicitly: which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.

Freak07 said:
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Click to expand...
Click to collapse
That might have been the the point. In fact, I did download them, but I used (definately outdated, because on my pc since literally years) a minimal adb and fastboot installation.
I didn't think about it, as this is my first A/B device.
I won't try it now with the latest ones, because it worked and I don't want to destroy something (since we still dont have a working TWRP for backup & recovery) but I guess you're right, and the problem were the outdated binaries.
Thank you.

GRöder said:
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.

isthisadagger said:
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
Click to expand...
Click to collapse
In fact, I tried that before I tried the stock-recovery-method (found it at the ASUS FAQ-pages), but it didn't work, even after a reboot, no notification showed up.

GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks

Ya how do we unlock the bootloader without asus knowing it

MirkoMirko9 said:
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Click to expand...
Click to collapse
nikhil18 said:
Ya how do we unlock the bootloader without asus knowing it
Click to expand...
Click to collapse
I used the official app, while the device was connected to the internet. So yes, ASUS knows that I unlocked the device.
The device was still at the -75 firmware, when I did it.
 @MirkoMirko9 If you can live with asus knowing that you unlocked the device, try it again with active internet connection.
As far as I know, there is no other method yet.

unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?

QuazIqbal said:
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79817571&postcount=31

magisk_patched boot.img for .156 firmware is uploaded to the patched boot.imgs folder

restart loop with V10.3.5.0.ODEMIXM after factory reset

I have my MI MIX 2 with official global V10.3.5.0.ODEMIXM. I upgraded to this version via regular OTA update about 2 weeks ago.
After factory recovery I did last day I stuck in restart loop with error.
I picked up language, region, and after that on Just a sec screen I have error Find Device closed unexpectedly and going to restart loop.
Via Mi suite 3 beta I am able to flash same firmware, but this is causing same error and loop. Older firmwares are not possible to flash because of error. (flashing firmware older the nactual firmware on phone)
Via fastboot I am not able to flash anything as phone has locked bootloader and is not assigned to my Mi account so unlock tool is not able to unlock it.
So.. what can I do to fix it ?

hi , if you have access to fastboot look if arb is on , download this => https://androidfilehost.com/?fid=24686681827312411 and copy/paste that => fastboot getvar anti ,, if you get 4, arb is on ..... if you have under , you can flash older firmware
So if you have 4 , search '' Anti-rollback Protection and Fastboot Unlocker '' to download antirbpass dummy.img

So
fastboot getvar anti
anti: 1
fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending 'antirbpass' (8 KB)...
OKAY [ 0.002s]
writing 'antirbpass'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.006s
Mi suite 3.0 still says:
Sorry, I can't support the rollback to a non-newer previous version.
Push Man Brush Pack Version: V10.3.5.0.ODEMIXM

hi you have anti 1 , you can flash older rom without brick , you have unlock bootloader
rom 10.2.2.0 =>http://bigota.d.miui.com/V10.2.2.0....XM_20190109.0000.00_8.0_global_ffb701bb41.tgz ,, you can flash ,, after that make upgrade firmware via update
ps: un flash.bat it will ask for 0 to flash ............. i did mistake ....... you can try flash beta rom , it's under pie , i flashed it to and it's stable
=> https://bigota.d.miui.com/9.5.30/ch...30_20190530.0000.00_9.0_global_6c535734e7.tgz
after flash search update normaly get 9.6.13

I really appreciate your help, but I was not succesfull.
Bootloader is locked and unlocking via MI Unlock is not succesfull because no Mi account is bound to the device.
Flashing via Mi Suite 3 always ends like this:
V9.5.8 (pie) -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V9.6.13 -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V10.2.2.0.ODEMIXM - > ROM Package verification failed Unknown Error[2013]
V10.3.1.0.ODEMIXM -> Sorry, I can't support the rollback to a non-newer previous version.
V10.3.5.0.ODEMIXM -> Succesfull, but always get boot loop with error FIND DEVICE CLOSED UNEXPECTEDLY
I also tried to reboot to EDL with help of this srticle: https://www.xiaomigeek.com/edl-mode-xiaomi.html second option - 2. How to Boot into EDL From Fastboot Mode.
But it always restarts and goes to boot loop.
So is last try open the phone and test point method? http://en.miui.com/thread-1351514-1-1.html

Help with root for Alldocube M5X Pro

I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.

After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.

Question Need help, Can't figure out how to change my ROM

Exactly a year ago I bought Poco F3, unlocked the bootloader and installed ArrowOS. Now I'm trying to figure out how to change my ROM and I can't really find any answers. I have the ArrowOS recovery and it's useless, I can't install another recovery with it. My fastboot also seems to be broken(?), it has a different logo and it's detected on my computer when I do (fastboot devices) but other than that it gives me a bunch of errors
I would like to at least know how to change the recovery. Is it possible that my bootloader got locked? One last thing, when I installed ArrowOS I used TWRP and updated it using OTA updates, now TWRP is gone.
Please help me

You need fastboot for TWRP.

It could not have gotten locked, no.

Arealhooman said:
It could not have gotten locked, no.
Click to expand...
Click to collapse
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?

Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.

Arealhooman said:
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Click to expand...
Click to collapse
I don't have any oem unlock option in ArrowOS and I never locked anything wtf, I just used it as a normal phone and only did OTA updates + sometimes FW updates when required
Is there anyway to fix it?

ADB & Fastboot Binaries: https://developer.android.com/studio/releases/platform-tools
OrangeFox Recovery (recommended): https://orangefox.download/device/alioth
Install the Recovery ZIP by either ADB Sideload in ArrowOS Recovery
or you can extract the "recovery.img" and fastboot boot it ("fastboot boot recovery.img") and select "Install current Recovery"
Then you simply flash the ROM.zip (select "Reflash Recovery after ROM Flash") -> Reboot Recovery -> Format Data
The OTA Update has replaced your TWRP with ArrowOS Recovery, because ROM Updates replace the boot-partition (along with other system related partitions). The boot-partition contains the recovery-environment.
Only install Custom Recoveries from inside the Recovery, because Fastboot can only replace partitions entirely (and boot-partitions contains both bootloader & recovery)
The bootloader of the Poco F3 cannot (or shouldn't) be locked on Custom Software.

gobertel said:
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Click to expand...
Click to collapse
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.

Also, what's the problem with ArrowOS anyway? We've ArrowOS MiPa, it's a good and reliable ROM.

cyanGalaxy said:
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Click to expand...
Click to collapse
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general

Thank you for helping me out by the way

gobertel said:
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Click to expand...
Click to collapse
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.

Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com

cyanGalaxy said:
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot boot recovery.img
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Another thing to add is I still I get the unlock symbol when booting up the phone, I dont know if that makes a difference

cyanGalaxy said:
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I'm using the exact one you gave me and I will try it

gobertel said:
Yes I'm using the exact one you gave me and I will try it
Click to expand...
Click to collapse
Yup try it.
Else, here I have the vendor_boot.img & boot.img from the latest ArrowOS MiPa (February). More up-to-date than the SourceForge links.
Either the 2 files from ArrowOS v12, or the latest v13 ones that I've uploaded here, should definitely work.
Also try rebooting Fastboot Mode.

XDA doesn't let me upload the boot.img ඞ

cyanGalaxy said:
XDA doesn't let me upload the boot.img ඞ
Click to expand...
Click to collapse
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything

gobertel said:
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
Click to expand...
Click to collapse
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.

cyanGalaxy said:
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
Click to expand...
Click to collapse
IT WORKED. Thank you so much, it was a driver issue but the exact version you gave me didn't work, I had to find another one