Database Users

Not able to boot any ROM

Hi,
Coming from PureNexus, I wanted to give CM13 a try. Made a nandroid backup so none of my data is lost, and put that backup on pc. I installed CM13 which went fine. It stopped at the CM booting animation and did not go further, so I cleanflashed Purenexus to restore my backup later on. Now PureNexus won't boot either. I'm out of ideas to try, and I want to get my phone back up and running ASAP.
Can anyone help me with this issue?

Riyge said:
Can anyone help me with this issue?
Click to expand...
Click to collapse
When you clean flashed, did you also wipe system? If you did and you're still hung at boot, your best bet would be to flash the factory images via fastboot and start fresh.

Riyge said:
Hi,
Coming from PureNexus, I wanted to give CM13 a try. Made a nandroid backup so none of my data is lost, and put that backup on pc. I installed CM13 which went fine. It stopped at the CM booting animation and did not go further, so I cleanflashed Purenexus to restore my backup later on. Now PureNexus won't boot either. I'm out of ideas to try, and I want to get my phone back up and running ASAP.
Can anyone help me with this issue?
Click to expand...
Click to collapse
Are you wiping properly (system, data, cache, dalvik cache) before installing a ROM? Are you making sure you flash the appropriate vendor image after flashing the ROM? When you made your backup which options did you check? And which options are you restoring?

Heisenberg said:
Are you wiping properly (system, data, cache, dalvik cache) before installing a ROM? Are you making sure you flash the appropriate vendor image after flashing the ROM? When you made your backup which options did you check? And which options are you restoring?
Click to expand...
Click to collapse
When I try to wipe, it's only wiping cache for some reason. My backup consists of everything except cache.

Riyge said:
When I try to wipe, it's only wiping cache for some reason. My backup consists of everything except cache.
Click to expand...
Click to collapse
What do you mean it's only wiping cache? Explain to me how you're doing the wipe. Also, when creating a backup (and restoring it) you should only be selecting system, data, boot, and vendor.
PS. You didn't answer my question about whether you're flashing the vendor after flashing the ROM. If you want help you need to answer the questions that are asked.

Heisenberg said:
What do you mean it's only wiping cache? Explain to me how you're doing the wipe. Also, when creating a backup (and restoring it) you should only be selecting system, data, boot, and vendor.
Click to expand...
Click to collapse
I'll keep that in mind. When I boot up TRWP, I wiped system, dalvik, data, internal storage and cache. After that I pushed CM13 through adb. That's where the problems started.
EDIT: I flashed the most recent vendor after I flashed the ROM.

Riyge said:
I'll keep that in mind. When I boot up TRWP, I wiped system, dalvik, data, internal storage and cache. After that I pushed CM13 through adb. That's where the problems started.
EDIT: I flashed the most recent vendor after I flashed the ROM.
Click to expand...
Click to collapse
Ok, you definitely don't need to wipe internal storage before flashing so don't worry about that part. Only system, data, cache, and dalvik cache. You said before only cache was being wiped, can you please elaborate on that?
Are you sure the ROM zip didn't become corrupt during the download? Did you check the MD5 to ensure that it didn't? That could be what's causing your problems. Also, what gapps are you flashing?
If you want to go back to Pure Nexus just to get your phone working you can just restore that backup, just make sure you only restore system, data, boot, and vendor.

Heisenberg said:
Ok, you definitely don't need to wipe internal storage before flashing so don't worry about that part. Only system, data, cache, and dalvik cache. You said before only cache was being wiped, can you please elaborate on that?
Are you sure the ROM zip didn't become corrupt during the download? Did you check the MD5 to ensure that it didn't? That could be what's causing your problems. Also, what gapps are you flashing?
If you want to go back to Pure Nexus just to get your phone working you can just restore that backup, just make sure you only restore system, data, boot, and vendor.
Click to expand...
Click to collapse
It won't wipe anything other than cache, no matter what I'm trying to do. Now when I'm trying to push a ROM through adb, I can install it but it won't boot.

Riyge said:
It won't wipe anything other than cache, no matter what I'm trying to do. Now when I'm trying to push a ROM through adb, I can install it but it won't boot.
Click to expand...
Click to collapse
I'm trying to help you here but if you keep failing to answer my questions it's impossible for me to do so. At this point I can only think that it's user error, I'd flash the factory images to return to stock and start fresh. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
I'm trying to help you here but if you keep failing to answer my questions it's impossible for me to do so. At this point I can only think that it's user error, I'd flash the factory images to return to stock and start fresh. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I found your guide by googling, thanks for making that! Flashing the factory image worked, and I succesfully restored my backup. The only problem left is that it won't accept my pattern lock. I have used the same one for years across multiple android devices, so I'm absolutely sure I have the right pattern. Any way to bypass this?

Riyge said:
I found your guide by googling, thanks for making that! Flashing the factory image worked, and I succesfully restored my backup. The only problem left is that it won't accept my pattern lock. I have used the same one for years across multiple android devices, so I'm absolutely sure I have the right pattern. Any way to bypass this?
Click to expand...
Click to collapse
You need to remove all security before making a backup because the security information is encrypted and doesn't get backed up or restored properly. You can delete some files using TWRP (see section 3 of my guide) in order to remove the security so you can get into Android. This will cause problems with Smart Lock though.

Heisenberg said:
You need to remove all security before making a backup because the security information is encrypted and doesn't get backed up or restored properly. You can delete some files using TWRP (see section 3 of my guide) in order to remove the security so you can get into Android. This will cause problems with Smart Lock though.
Click to expand...
Click to collapse
Tried that, fixed my phone. Thanks so much! Is it possible to restore these functions or should I clean flash to get it?

Riyge said:
Tried that, fixed my phone. Thanks so much! Is it possible to restore these functions or should I clean flash to get it?
Click to expand...
Click to collapse
I'd be clean flashing.

Problem with LineageOS

Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi

possi.rodrigo said:
Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi
Click to expand...
Click to collapse
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.

echo92 said:
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.
Click to expand...
Click to collapse
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!

possi.rodrigo said:
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!
Click to expand...
Click to collapse
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.

echo92 said:
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.
Click to expand...
Click to collapse
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?

possi.rodrigo said:
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?
Click to expand...
Click to collapse
I recall from what Silesh has mentioned is that the commits from ElementalX are present in his kernel, thus the benefits should be seen in the unofficial stock Lineage OS kernel and so you don't necessarily need the ElementalX kernel. If you wish to use the ElementalX kernel with the latest builds of Lineage OS-OMS, and there is nothing stopping you doing so, you need to flash the sensorhub firmware, else you'll lose sensors like your fingerprint sensor (if you have a G4 Plus, that is - I don't know if other sensors are affected on non-Plus models as well if you don't flash this). The firmware can be found here https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2723
To install said firmware if you need it (credit to rahulsnair for the procedure https://forum.xda-developers.com/showpost.php?p=70716729&postcount=170):
Download the zip and extract, you should get a sensorhubfw.bin file. Copy this .bin file to your adb directory.
Connect your device to your computer and check adb can detect your device using 'adb devices'
Staying in adb, execute the command 'adb push sensorhubfw.bin /etc/firmware' (without the quotation marks). This will copy the sensorhub file to the /etc/firmware directory on your phone.
Reboot and hopefully you should have sensors back.

Stuck in spinning circles after updating to OOS 5.0 Oreo OTA

Hello! I just updated to the latest OTA of OOS 5.0 and now the phone is just stuck on the screen where the white dots spin around I tried clearing cache, wiped "System settings" via Oxygen Recovery and no luck. I sideloaded the zip to my device and flashed it over the one I had on it previously. I followed this guide https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515 without any results! This is ridiculous. I just wanted to update to Oreo. Here are my phone details: https://imgur.com/a/n4rtR I am unsure what to try next. Should I wipe /system and flash the previous ROM zip file and try that? I can see my files but they are completely encrypted thanks to OOS, but only can I see them in Oxygen Recovery; TWRP shows nothing. Suggestions would be appreciated, thank you.

Had the same problem, had to format Data partition to get it working. Lost all data though

I was on OOS 4.5.15 with Magisk root and TWRP. Last night, uninstalled Magisk and I flashed stock recovery to update my phone. Even though I cleared cache and Dalvik, boot loop happened.
Only after a full reset, the phone boot normally. Since I had all important files backed up, I did not loose anything but it still bothers me. There should have been a more streamlined update process.

I completely bricked my device with the update, so i used this tutorial : https://www.androidexplained.com/oneplus-5-unbrick-return-stock/
I lost all my data but now it work like a charm and i was able to update properly to Oreo

hknisl said:
I was on OOS 4.5.15 with Magisk root and TWRP. Last night, uninstalled Magisk and I flashed stock recovery to updated my phone. Even though I cleared cache and Dalvik boot loop happened.
Only after a full reset, the phone boot normally. Since I had all important files backed up, I did not loose anything but it still bothers me. There should have been a more streamlined update process.
Click to expand...
Click to collapse
You have to do a full wipe (system, data, internal storage, and both cache) when going from Nougat to Oreo. That is the only way.

azeem40 said:
You have to do a full wipe (system, data, internal storage, and both cache) when going from Nougat to Oreo. That is the only way.
Click to expand...
Click to collapse
If so, how could they offer an OTA for customers? Don't get me wrong, I am just wondering.

hknisl said:
If so, how could they offer an OTA for customers? Don't get me wrong, I am just wondering.
Click to expand...
Click to collapse
From what I know, you have to be unrooted and on stock recovery for that to work.

azeem40 said:
From what I know, you have to be unrooted and on stock recovery for that to work.
Click to expand...
Click to collapse
I had unrooted my phone using magisk uninstaller and flashed stock recovery. It has something to do with encryption, but I am not quite sure.

hknisl said:
If so, how could they offer an OTA for customers? Don't get me wrong, I am just wondering.
Click to expand...
Click to collapse
Very good question. Even I wanna know how it is working technically.

azeem40 said:
From what I know, you have to be unrooted and on stock recovery for that to work.
Click to expand...
Click to collapse
I was unrooted and having stock recovery, still got bootloop. OnePlus basically messed up.

Can't flash oreo roms

Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?

Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation

Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me

metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?

I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?

devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.

sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...

metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.

Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos

As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).

sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1

Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.

Exact Same issue Here...

I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?

This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.

sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot

Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.

bump

any solution?

The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps

help about /vendor

im having big problems about vendor. for start im giving some info:
device: mi a1 (tissot)
current os: lineage OS 17.1
root: yes
twrp: can install or use just booting .img
i unlocked my device and installed twrp. there is no problem.
i wanted flash lineage OS and i wiped my device. gives error about cannot mount /vendor
i installed treble supported twrp and installed lineage OS. flashed magisk. installed microg...
then i tried flash mapsv1.zip which is recommended for microg. then booom. another /vendor error.
now i can boot device. i can use everything except gps. google maps app cannot found location. yandex maps can found and i can use it until lock screen or going main screen (or another app). then it starts stopping everytime until i clen its data and cache. then again... in chrome when i open google maps and try found my location chrome stops.
i tried to change /vendor/etc/gps.conf. its still same.
what to do now guys? im worrying about if i try re-flash rom it doesnt flash and device bricked. any solution without re-flash rom? what causes to cannot mount /vendor after solved it?

What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.

KaaMyA said:
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
Click to expand...
Click to collapse
Dalvik cache , system, data, and cache. My device is not rebooting too much. Sory if i couldn't explain. Everything working fine except when an app tries use my location, app stops running, i cant flash anything right now.
İ thought anyone knows mapsv1.zip file(microg.org) and which files are replaced or added by this file when flash it. And can i do it manually? Btw i can read and write /vendor file with solid explorer
İf needed to re-flash rom thats ok but i think lineage OS was perfect for me until this error. And a last thing: can i backup my settings. (İ already took backup of everything in stock when unlocked bl)
Thank you for help
Edit: gps problems started when i tried flash mapsv1

ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.

KaaMyA said:
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
Click to expand...
Click to collapse
Okey ilk try it and share the result night. But is it possible to backup settings of phone?

Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).

KaaMyA said:
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
Click to expand...
Click to collapse
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]

Nurullah44 said:
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Click to expand...
Click to collapse
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153

portox said:
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
Click to expand...
Click to collapse
Are you sure? Bcs i can view and change /vendor in root path. Treblizing is updating and repairing system partitions right? İ am using treble support twrp, flashed stock rom via mi flash(said error but worked fine) then how to treblize a device? And is this required for anything(like a rom, an app)?