Hi,
I tried to install /e/os on my Fairphone 6 but an issue happened while flashing dtbo.
Here is the message I got in terminal :
Sending ‘dtbo_a’ (30720 KB) OKAY [ 0.727s]
Writing ‘dtbo_a’ FAILED (remote: ‘Error flashing partition : Volume Full’)
fastboot: error: Command failed
ERROR: Could not flash the dtbo_a partition on device 9adb3963.
ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)
ERROR: Aborting now (press Enter to terminate).
I tried to restart the update but the same message appeared…
Now, the phone is unusable…
Does anyone could provide any advice on what happened and how to solve the issue ?
Thanks in advnece for your answers and the time you could spend on my issue.
The script is worded to flash partitions one by one flash or abort. There is the expectation expressed in the error message that you will be able (eventually) to regain Fastboot and start again. Were you able to achieve full power down before reboot to Fastboot?
Some possibilities for the error. Has the PC plenty of RAM to hold the image while flashing, perhaps try to run the terminal alone or at least avoid any significant other load on the PC. The USB cable must be a good quality good capacity DATA cable, avoid USB hubs including any hidden hub in the PC, try to connect to the USB port soldered to the motherboard.
Hi
Thanks for your answer.
I should have been more precise in my situation.
I am able to reach fastboot following the procedure described in the terminal message. That’s the way I used to retry flashing but the issue was the same.
I now have tested each usb port of my computer (c only) but the same error still occures.
I also change the cable with no result.
I can provide the full log (listing all partitions flashed) but i thought only the failing one should be relevant.
Any other idea ?
Thanks again for your time.
I think that is correct. I can think of no exact reason for this partition to fail. (I feel the script can be quite demanding of a home PC with maybe a lack of rests betwen tasks. I don’t know the exact significance of USB C ports only, but USB 2 soldered to the motherboard is more tried and tested; also unknown significance but you might mention PC OS.)
Hi
Sorry for the delay in my aswer, it took some time to acces some other computers.
I tried on macOs and linux, with serveral cables and the same error occured.
I also tried to install official fairphone 6 rom (FP6.QREL.15.148.0.20250913182929_VS1O-factory.zip) following your link and the exact same error happens (volume full when flashing dtbo_a)
I don’t know what else I could check…
According to the error message, i wonder if there is any way to check partitions sizes because maybe it is the root cause ?
I rather agree with your conclusion of the partition corrupted in some way.
Maybe someone will have an idea but if the phone was purchased from Fairphone I would open a support ticket there (not the forum, the sales and support department).
I already read it and it’s one of the threads where I heard about the command I wonder if it is safe to use
Especially this post : Softbrick after repartition - #78 by z3ntu - Fairphone 4 - Fairphone Community Forum
The thread being about FP4 with custom recovery (TWRP) i was wondering if it would work correctly on FP6 and if it would not break anything (worst than it is for now)
I don’t have first hand Fairphone experience so I hesitate to advise but the encouraging thing about that link is that it includes a link to fastbootd.
Once you have an understanding of the significance of
“fastbootd is moving fastboot into userland”
you can begin to get a sense of where adjusting of partition size is perfectly acceptable on a Super partition device with Dymamic partitions.
Sorry but what I simply don’t know (have not read enough) is whether dtbois a dynamic partition.
Because dynamic partitions are implemented in userspace, partitions needed by the bootloader can’t be made dynamic. For example, boot, dtbo, and vbmeta are read by the bootloader, and so must remain as physical partitions.
So I was thinking out loud about the comment in FPF Post #78
And next time please just use fastboot resize-logical-partition <partition> <size> and don’t touch the actual partition table.
Sorry, no further forward. I suggest you are looking for the answer to “what is the effect of fastboot resize on the partition table”
You might see if you can parted to read the partition table without adjustment, but I don’t know if you can possibly do this without TWRP … then is there apparent space for a resize?
I think @mihi that fastboot erase dtbo is just like we erase userdata to remove the contents we don’t change the partition itself.
Assuming that the zip from here is the same that Fairphone might use to flash it back to stock, I could not find any function in flash_fp6_factory.command which would create the partitions, only flash into it…
In the FP4 Postmarket article it was also sating this, why I thought the erase could be helpful: " You can always restore the original dtbo partition by downloading and extracting the dtbo.img from the factory package and then flashing it via fastboot flash dtbo <path/to/dtbo.img>. This works similar for the boot partition." But it is not about the size of the partition rather the content.
resizing from fastboot will not be possible because dtbo is not a logical partition
flashing stock dtbo fails on stock and on /e/os (it’s the step failing on both flashing due to volume full…)
resizing with parted may be possible (not sure) but not from fastboot
but TWRP is not currently available for FP6
also, i can’t access to fastbootD , I get an error : fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot getvar should be capable to report if dtbo is a logical partition.
Side information.
Adjustment of a dynamic partition is relatively easy, it is designed in.
That thread takes a case where the OP made an intervention unsuitable for Fairphone. They were able to guide him to return from his specific mistakes. The post #78 draws attention to this but you are not quite in the same position. We should not be confusing what we can do with a logical vs dynamic. My bad for saying anything to confuse the problem.
That is understandable (loosely speaking userspace does not exist).
I guess you have to decide how much you want to dive into this. You can set this work against having the phone reimaged by Fairphone if their support thought this was the correct way forward @ last price mentioned on the forum of 60€.
Post #78 effectively says “don’t do it”. I might try to explore the partitions with parted. If you ever did this on a PC is good but on Android is very much harder and the XDA guide provided in our thread is totally unsuitable for Fairphone.
