Moto G5 Plus Error "Camera keeps stopping". - Moto G5 Plus Questions & Answers

I am using Moto G5 plus, My camera is not working. I have downloaded latest update on my phone. Error,"camera has stopped" "camera keeps stopping" "camera busy" Restart Phone"
current error is "camera keeps stopping"
Before week, To enable screencast function i have rooted my phone. But my phone and camera was working perfectly fine, after week my fornt camera stopped working, and now rear camera is also not working
Below method i have tried but camera is still not working.
-checked in safe mode
-uninstalled all the application from mobile
-cleared date, cleared cache, disablled and enabled, download latest camera update.
-i have also removed sd card and tried in normal and safe mode.
Please guide what should i do next?

The update let you pass the root
vipul.vip009 said:
I am using Moto G5 plus, My camera is not working. I have downloaded latest update on my phone. Error,"camera has stopped" "camera keeps stopping" "camera busy" Restart Phone"
current error is "camera keeps stopping"
Before week, To enable screencast function i have rooted my phone. But my phone and camera was working perfectly fine, after week my fornt camera stopped working, and now rear camera is also not working
Below method i have tried but camera is still not working.
-checked in safe mode
-uninstalled all the application from mobile
-cleared date, cleared cache, disablled and enabled, download latest camera update.
-i have also removed sd card and tried in normal and safe mode.
Please guide what should i do next?
Click to expand...
Click to collapse
With my old motorolas if I made a root and try to make an update, the updater failed with a mistake, I supposed that you used magisk, and the root was hide for the system and if you only modify the build.prop to enable screen cast, my only advice to you is to restore a stock firmware that will help you really well with your problem, the easiest option for me is to install a zip based stock firmware to not to have to install RSD flasher and those stuff I will let you the link I hope this will help you.
https://franco28.github.io/stockrom/index.html
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Just in case make a copy of all your internal data, in drive and google fotos.

Thank you so much for the guidance
i do really appreciate your advice. yes you got it right, i have used magisk and build.prop to enable screen cast, but i novice to all this, i did not understand below options. hot do it, you mean, i have to reboot device and wipe system, cache, dalvik-art
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Please guide
tekkaman7 said:
With my old motorolas if I made a root and try to make an update, the updater failed with a mistake, I supposed that you used magisk, and the root was hide for the system and if you only modify the build.prop to enable screen cast, my only advice to you is to restore a stock firmware that will help you really well with your problem, the easiest option for me is to install a zip based stock firmware to not to have to install RSD flasher and those stuff I will let you the link I hope this will help you.
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Just in case make a copy of all your internal data, in drive and google fotos.
Click to expand...
Click to collapse

vipul.vip009 said:
i do really appreciate your advice. yes you got it right, i have used magisk and build.prop to enable screen cast, but i novice to all this, i did not understand below options. hot do it, you mean, i have to reboot device and wipe system, cache, dalvik-art
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Please guide
Click to expand...
Click to collapse
Hi? if I understood your reply is about if you have to make the steps I post on that time, the answer is no, I'm not sure but I was talking about someone returning to stock or something, if you enable the screen cast you'll be able to see the "hamburger menu" in the android screen settings, that let you to make the screen cast, what's your exact problem?

Related

Urgent Help. Somethings

Here I Go
I was on CM11 Snapshot. Then I went to install Lollypop from http://forum.xda-developers.com/nexus-4/development/rom-aosp-build-t2929544. So I go on TWRP and wipe Dalvik Cache, Cache, Internal Storage and System. Then after, I noticed that everything was gone. So I sideload the ROM and my Gaaps. Something went wrong and old system apps like Dialer and Camera were installed and caused problems with the Newer apps and the system. I Wipe again....this time making sure to wipe data. I sideload but....the gaaps did not install. I went into Recover and noticed that TWRP was uninstalled and everytime I installed it VIA Fastboot, it worked but only for the Timebeing. Sideloading was not working and when I tried downloading the GAAPS straight from the browser, it was unsuccessful. Also, everything that I tried to download via browser did not work. Then I connected it to my Computer as an MTP. This was not working either.
Please Help and Thank You

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.
Anyone have any idea?
Thanks
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?
You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes
I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.
you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)
Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.
Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.
I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?

Can't root phone, verification failed everytime

Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
I'd appreciate any advice.
Florad77 said:
Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
I'd appreciate any advice.
Click to expand...
Click to collapse
start phone go to settings/dev settings an enable oem unlock
ever find a fix??? im having the same issue !
Koleboy9 said:
ever find a fix??? im having the same issue !
Click to expand...
Click to collapse
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
I could kiss you right now, thanks!
just wipe cache partition to get to normal system again
Florad77 said:
Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
I'd appreciate any advice.
Click to expand...
Click to collapse
if you experience like this(verification failed) and you dont want to lose your date. just hold and press power+up+home, this will jump to recovery mode, and if you see installing update and got error, just press again power+up+home till you reach the recovery option. after that just wipe cache partition. the verification failed will disappear and youll have the normal system again. i experienced the same issue but i manage to fixed it after doing the rooting twice. i didnt reset my device. you dont need the emergency firmware repair. just wipe the cache partition.
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
I won't kiss you but I will say THANK YOU, THANK YOU, THANK YOU. I was starting to give up on flasing my S7 with TWRP and another ROM.
ah thanks man
could kiss everyone in this thread thanks for all the help u saved my ass
Some things you can try...
Florad77 said:
Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
Click to expand...
Click to collapse
Are you sure you're following the steps correctly? Try some of these tips:
After flashing TWRP, instead of switching volume buttons on the fly (requires dexterity and timing! ), hold the VOLUME DOWN and POWER buttons until the phone turns off. You can then proceed to recovery by holding VOLUME UP + HOME + POWER.
Are you using the latest TWRP for your S7 Edge? Some older versions of TWRP have problems mounting folders and flashing ZIPs.
Did you update to the latest firmware before attempting root? Later Android versions become very finicky about device security, essentially locking you out of your phone.
Note that once your device detects that it has been tampered with, you won't be able to update. Download your stock firmware from some place like SamMobile and flash all the required tar.md5 archives through Odin (keep in mind: HOME_CSC keeps your personal data, while CSC erases it). If that doesn't fix it, backup whatever you can through TWRP and factory reset.
Did you enable OEM Unlock? Once you can access your settings again, if it is on, you may want to tap it off, then back on again. Sometimes it gets buggy.
You did remember to flash something that disables dm-verity, right? You may want to try flashing the dm-verity and force encryption disabler ZIP first before truly rooting.
i am having the exact same issue but i tried wiping cache that didnt work so i dont know what to do
Please Help
suljo94 said:
start phone go to settings/dev settings an enable oem unlock
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data
what do i do?
i am having the same problem on my S8+, it says verification fail, and i click on reset and as phone loads it goes back to the same screen that says Verification fail!
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
I don't mean to necropost, but this is an important detail for anyone out there having trouble with these "verify failed" messages. I knew I was missing something b/c there is an advanced option with formatting options that is not the same as the format button on the main wipe page. This did the trick for me trying to get my SM-G9600 (Chinese Samsung Galaxy S9) up and running with TWRP + Stock Oreo 8.1.
Big ups, @Florad77!
When to format data in rooting process?
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
When do you format data? Before installing supersu or after?
tarocco said:
I don't mean to necropost, but this is an important detail for anyone out there having trouble with these "verify failed" messages. I knew I was missing something b/c there is an advanced option with formatting options that is not the same as the format button on the main wipe page. This did the trick for me trying to get my SM-G9600 (Chinese Samsung Galaxy S9) up and running with TWRP + Stock Oreo 8.1.
Big ups, @Florad77!
Click to expand...
Click to collapse
the "advanced" tab in Odin is primarily used for the PIT file in the firmware zip package. It is not advised to flash the PIT unless necessary. Often times, the "verify failed" message means that your bootloader is still locked or youre flashing the wrong file. Just fwiw.
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
Yeah, and now my Galaxy Tab Active 2 (Android 9.0) , can't boot. Only the Welcome logo appears, and resetting it indefinitely.

Soooo, I deleted engineering mode and it turns out I need it.

Today Iran across a post to turn on VoLTE and it requires onepluslogkit and engineering mode, both of which I have deleted. I found an apk for the log kit, installed it, still no engineering mode.
Not even sure I will be able to turn on VoLTE here in Thailand, but when I am stateside for the 1stQ it would be handy as service SUCKS in Las Vegas.
I deleted the logkit because it's a back door and talks to China way too much. My plan was reinstall, set up VoLTE, delete the app again.
Not a big enough issue to reflash a clean oos and start over.
Any thoughts and suggestions....contructive ones.....are appreciated.
Thanks in advance!
Just dirty flash OOS, it will re-install the system apps you have deleted without removing user data.
Thanks Jager!
Never done that before. Is this what I need to do?
Reboot into TWRP
Click Install and choose my last OOS zip file
Wipe dalvik and cache
Reboot to recovery
Install TWRP
Install Magisk
Reboot system
Thanks in advance, JC
No need to wipe the caches, it just leads to increased battery drain with current versions of Android.
It looks like you have two of those steps in the wrong order. I have underlined the steps that need to be switched switched:
Reboot into TWRP
Click Install and choose my last OOS zip file
Install TWRP
Reboot to recovery
Install Magisk
Reboot system

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)?

Categories

Resources