How to fix - cannot boot into system after /vendor changed file system (ext2, ext4) - Android Q&A, Help & Troubleshooting

Hi there,
The phone data was somehow disabled for no reason, I tried to enable mobile data and roaming, but it did not work.
In addition,
- "Developer options" was also disabled -- the options in "Developer options" disappeared within second after I entered it and the screen went blank, except "Developer options" remaining on the top;
- centre (homescreen) and right (opened apps) buttons in the navigation on the bottom of the phone were stuck, but left button (return) was still working.
To fix this issue, I booted into recovery mode and tried
- wiping cache and dalvik cache;
- repairing and resizing system, vendor, userdata, cache, dalvik cache partitions;
- (re)mounting the above 5 partitions,
but to no avail.
I checked the debloater and made sure that no system apps were removed via debloater.
I changed vendor partition to "ext2" and back to "ext4". And I rebooted the device to system, which subsequently booted into fastboot mode instead.
How to fix it?
Recovery is still usable.
Thanks in advance.
May you need any further information, please feel free to contact me.
Regards,

---

change of file system is same as formatting. restore vendor from backup

---

aIecxs said:
change of file system is same as formatting. restore vendor from backup
Click to expand...
Click to collapse
Unfortunately, I do not have vendor backup of this OS...

---

Would it be possible to flash / reinstall
- vendor.new.dat.br;
- vendor.patch.dat;
- vendor.transfer.list;
from the rom
or other ways to fix it?

---

Why do you have TWRP in first place? Next time backup beforehand, thats the purpose of TWRP
you need to convert into raw vendor.img first
https://github.com/xpirt/sdat2img
Code:
brotli --decompress vendor.new.dat.br -o vendor.new.dat
python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img
then you can flash from fastboot or adb
Code:
fastboot flash vendor vendor.img
or flash the whole ROM from stock recovery and start from scratch.

---

python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img
produced an error
Code:
File "sdat2img.py", line 1
Python 3.11.1 (v3.11.1:a7a450f84a, Dec 6 2022, 15:24:06) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin
^
SyntaxError: invalid syntax

---

maybe wrong line encoding, or that python is too new? can't tell you why it failed. probably not your fault. ask in support thread. https://forum.xda-developers.com/t/...-7-o-unpack-re-pack-android-dat-files.2978952
meanwhile you can send me link to firmware so I can convert for you.

---

Following hours of work, I was finally able to reboot into system after flashing vendor.img created by sdat2img.
Thank you very much for your help.
Code:
Sending sparse 'vendor' 1/1 (414215 KB) OKAY [ 9.252s]
Writing 'vendor' OKAY [ 68.242s]
Finished. Total time: 78.368s
But the issues remained in the system newly accessible
- I cannot use data network;
- two buttons (centre and right) at the bottom are not usable either.

---

I used the same method to restore system.img.
adb push failed
Code:
adb: error: failed to copy 'system.img' to '/dev/block/bootdevice/by-name/system': remote write failed: No space left on device
system.img: 1 file pushed, 0 skipped. 32.3 MB/s (3221225472 bytes in 95.099s)
But fastboot flash system system.img was ok.
Code:
Sending sparse 'system' 1/3 (515380 KB) OKAY [ 13.746s]
Writing 'system' OKAY [ 4.438s]
Sending sparse 'system' 2/3 (510053 KB) OKAY [ 13.414s]
Writing 'system' OKAY [ 3.462s]
Sending sparse 'system' 3/3 (264688 KB) OKAY [ 7.015s]
Writing 'system' OKAY [192.959s]
Finished. Total time: 240.702s
But even after system.img was restored back, data and navigation bar problems were not solved.

---

the adb error 'No space left on device' is strange. I guess it tried to copy a file into a dir (/dev/block/bootdevice/by-name/system/system.img) instead of writing partition. maybe some bug in adb. I have never tested. but it seems bootloader is unlocked so you can just flash from fastboot, as you finally did.
you can try to flash other partitions from stock firmware, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msadp. exist there some txt or xml file with mapping, partition label = file name?
if that doesn't help, maybe it is related to bootloader unlocking?
https://forum.xda-developers.com/t/how-do-i-recover-the-imei-after-unlocking-the-bootloader.4536397

---

aIecxs said:
the adb error 'No space left on device' is strange. I guess it tried to copy a file into a dir (/dev/block/bootdevice/by-name/system/system.img) instead of writing partition. maybe some bug in adb. I have never tested. but it seems bootloader is unlocked so you can just flash from fastboot, as you finally did.
you can try to flash other partitions from stock firmware, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msadp. exist there some txt or xml file with mapping, partition label = file name?
if that doesn't help, maybe it is related to bootloader unlocking?
https://forum.xda-developers.com/t/how-do-i-recover-the-imei-after-unlocking-the-bootloader.4536397
Click to expand...
Click to collapse
In the stock rom, it seems that there were not many flashable files, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msad...
{
"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"
}

---

that is only update ROM. what you need is full firmware for blank flash.

---

I re-downloaded and extracted the rom and it seems it is just the same.

---

yes, that's the difference between update ROM and full firmware. crystal ball says, you want firmware for OnePlus2?
https://www.full-repair-firmware.com/p/oneplus-2.html

---

or Xiaomi maybe?
https://xiaomifirmwareupdater.com/miui
there is always two files. smaller one is OTA update ROM (tag: recovery)
bigger file is full ROM/firmware bundle (tag: fastboot)

---

wenyendev said:
In the stock rom, it seems that there were not many flashable files, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msad...
View attachment 5814327
View attachment 5814329
View attachment 5814331
View attachment 5814333
Click to expand...
Click to collapse
It looks like what you're showing is a custom ROM, you may need to flash a stock ROM, that contains a stock vendor image too, to fix things.

---

yeah we might able to provide link, but OP won't tell us what device brand/model he's talking about...