Database Users

Stuck on Google Logo after TWRP Backup Restore.

Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.

Tried clearing cache? Also, what things did you precisely backup?

DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache

setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.

DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?

Try it without the system image.

DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.

setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something

setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?

Yes

oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.

setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.

setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through

oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.

Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?

oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.

okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg

setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!

I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.

Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!

Weird Cellular/IMEI/EFS issue.

I installed TWRP 3.0.2-0 on my axon A2017G B03, unlocked the bootloader, installed CM13 after a small hiccup (had to temporarily install A2017G B06 and Bootstack).
All went well, I really enjoyed my phone. The only problem was that I'm an audiophile and there was a big distortion on the speakers.
I tried to install a Dolby zip via TWRP to improve this. Before I did that, I took a full TWRP backup.
The Dolby app didn't help one bit, after which I wanted to rollback by restoring the backup. Appearently, restoring the EFS is a really bad idea, since after that, CM13 wouldn't boot anymore. So, I tried using DrakenFX' B06 bootstack and stock image. When I did that, my phone could not connect to Wi-Fi nor detect my SIM-card.
Using the commands
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I restored my Wi-Fi. My phone now recognises my SIM-card, but I can't connect to the cellular networks. I have no IMEI. It can detect cellular networks, but not connect to them.
I have "efs1.emmc.win" and "efs1.emmc.win.md5" files from the TWRP backup of CM13 from just before I killed my cellular and another EFS backup I took just before unlocking BL and flashing TWRP (A2017G B06).
When I do a clean install of A2017G B06 and restore the TWRP EFS backup I made when on B06, when the phone boots, the phone doesn't detect my SIM.
When I do a clean install of CM13 and restore the TWRP EFS backup I made when on CM, CM13 doesn't boot at all.
I've spent about a day trying just about anything. Nothing seems to work. Can someone pull their modem file? Or would flashing NON-HLOS.bin help? Is there a different way of restoring my EFS backups? I read something about TWRP 3.0.2-0 not playing nice with EFS. Would flashing TWRP 3.0.2-2 and then restoring EFS work? Or is there a way to restore the phone back to "just-out-of-the-box" status? I don't mind losing unlocked BL or TWRP, I can do that all again. I thought as long as I backup everything including EFS, nothing can really go wrong. A user in XDA posted that "shady" guides that "don't get discussed at XDA" can usually help you get IMEI back. I don't want to illicit illegal practices here, but I'm desperate enough to try just about anything.
Thanks a lot for your help. If no-one here can help me, I suppose it's back to amazon. And probably pay a decent amount for it, too

Perhaps try flashing newer twrp version and restore your efs backup?

Controllerboy said:
I installed TWRP 3.0.2-0 on my axon A2017G B03, unlocked the bootloader, installed CM13 after a small hiccup (had to temporarily install A2017G B06 and Bootstack).
All went well, I really enjoyed my phone. The only problem was that I'm an audiophile and there was a big distortion on the speakers.
I tried to install a Dolby zip via TWRP to improve this. Before I did that, I took a full TWRP backup.
The Dolby app didn't help one bit, after which I wanted to rollback by restoring the backup. Appearently, restoring the EFS is a really bad idea, since after that, CM13 wouldn't boot anymore. So, I tried using DrakenFX' B06 bootstack and stock image. When I did that, my phone could not connect to Wi-Fi nor detect my SIM-card.
Using the commands
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I restored my Wi-Fi. My phone now recognises my SIM-card, but I can't connect to the cellular networks. I have no IMEI. It can detect cellular networks, but not connect to them.
I have "efs1.emmc.win" and "efs1.emmc.win.md5" files from the TWRP backup of CM13 from just before I killed my cellular and another EFS backup I took just before unlocking BL and flashing TWRP (A2017G B06).
When I do a clean install of A2017G B06 and restore the TWRP EFS backup I made when on B06, when the phone boots, the phone doesn't detect my SIM.
When I do a clean install of CM13 and restore the TWRP EFS backup I made when on CM, CM13 doesn't boot at all.
I've spent about a day trying just about anything. Nothing seems to work. Can someone pull their modem file? Or would flashing NON-HLOS.bin help? Is there a different way of restoring my EFS backups? I read something about TWRP 3.0.2-0 not playing nice with EFS. Would flashing TWRP 3.0.2-2 and then restoring EFS work? Or is there a way to restore the phone back to "just-out-of-the-box" status? I don't mind losing unlocked BL or TWRP, I can do that all again. I thought as long as I backup everything including EFS, nothing can really go wrong. A user in XDA posted that "shady" guides that "don't get discussed at XDA" can usually help you get IMEI back. I don't want to illicit illegal practices here, but I'm desperate enough to try just about anything.
Thanks a lot for your help. If no-one here can help me, I suppose it's back to amazon. And probably pay a decent amount for it, too
Click to expand...
Click to collapse
It seems that I am having the same kind of issue with the newest version of TWRP. After having some issues with incoming and outgoing phone calls, I stumbled across the above command. After using the command I lost my ability to connect to my network operator. Therefore I tried to do a recovery from TWRP and now I'm stuck with an IMEI which shows "0".
Sadly it seems that I don't have a backup of my efs partition (noob) and now I'm desperately finding possible solutions.
Any ideas? I feel that the trying to connect to the network with no IMEI is the cause of my problem...

Dawacko87 said:
It seems that I am having the same kind of issue with the newest version of TWRP. After having some issues with incoming and outgoing phone calls, I stumbled across the above command. After using the command I lost my ability to connect to my network operator. Therefore I tried to do a recovery from TWRP and now I'm stuck with an IMEI which shows "0".
Sadly it seems that I don't have a backup of my efs partition (noob) and now I'm desperately finding possible solutions.
Any ideas? I feel that the trying to connect to the network with no IMEI is the cause of my problem...
Click to expand...
Click to collapse
Both myself, Controllerboy and many others pretty much tried everything to restore working imei numbers to no avail. Only solution for both of us was to RMA our phones unfortunately.

Tebor said:
Both myself, Controllerboy and many others pretty much tried everything to restore working imei numbers to no avail. Only solution for both of us was to RMA our phones unfortunately.
Click to expand...
Click to collapse
That's exactly not the answer I wanted to hear
I think in that case it would be advisable to go back t stock and lock the bootloader? And have you been presented with a bill from Amazon/ZTE?

Flash modemst won't work anyway, you have to flash full bootstack.
Install TWRP, then flash A2016G bootstack file that DrakenFX provided

tamahouse02 said:
Flash modemst won't work anyway, you have to flash full bootstack.
Install TWRP, then flash A2016G bootstack file that DrakenFX provided
Click to expand...
Click to collapse
Already tried going back to stock with the bootstack and files provided by DrakenFX, but the mobile network connection won't work.
It started of with connecting to the mobile network, at least it showed full bars, but without a data connection. After a few minutes
the connection to the network was lost and I haven't been able to register again.
So it seems that Trebor is right, sadly...

YT-X703F/L Root/ROM on ZA1N US Varient?

Hello all, has anyone attempted to install the YT-X703 TWRP/ROOT/ROM on the ZA1N US varient of the yoga tab 3 Plus? I have been wanting to get one but I can't find the YT-X703 models here in the US. However, not having Nougat on my tablet is a deal breaker for me. So if I can't use the YT-X703 files, ill pass on it. Thanks for any info anyone can provide.

glitchhawk said:
Hello all, has anyone attempted to install the YT-X703 TWRP/ROOT/ROM on the ZA1N US varient of the yoga tab 3 Plus? I have been wanting to get one but I can't find the YT-X703 models here in the US. However, not having Nougat on my tablet is a deal breaker for me. So if I can't use the YT-X703 files, ill pass on it. Thanks for any info anyone can provide.
Click to expand...
Click to collapse
You could test it yourself and return the device if it doesn't support it. Not sure what kind of return policy you have in the US but you could restore the device to its original state. On the YT-X703 model the bootloader is relockable. So once you have the tablet you could do the following:
check if the device can be unlocked in the developer options
if yes unlock the device
try to boot TWRP
if it boots you can send me some hardware details to see if the US version matches the ROW version
if that's the case backup partitions modified by Lineage OS (it has to be the right partitions)
Install Lineage
if it doesn't work well go back to TWRP and restore the backed up partitions and relock the bootloader and you're back to original state
Of course this would have to be done very carefully since you don't have a factory firmware image as a fail safe.
If it works you would probably be the first to have TWRP and Lineage on the US model

matshias said:
You could test it yourself and return the device if it doesn't support it. Not sure what kind of return policy you have in the US but you could restore the device to its original state. On the YT-X703 model the bootloader is relockable. So once you have the tablet you could do the following:
check if the device can be unlocked in the developer options
if yes unlock the device
try to boot TWRP
if it boots you can send me some hardware details to see if the US version matches the ROW version
if that's the case backup partitions modified by Lineage OS (it has to be the right partitions)
Install Lineage
if it doesn't work well go back to TWRP and restore the backed up partitions and relock the bootloader and you're back to original state
Of course this would have to be done very carefully since you don't have a factory firmware image as a fail safe.
If it works you would probably be the first to have TWRP and Lineage on the US model
Click to expand...
Click to collapse
good plan, I may have to try this out. Thanks! I might grab one tomorrow

matshias said:
You could test it yourself and return the device if it doesn't support it. Not sure what kind of return policy you have in the US but you could restore the device to its original state. On the YT-X703 model the bootloader is relockable. So once you have the tablet you could do the following:
check if the device can be unlocked in the developer options
if yes unlock the device
try to boot TWRP
if it boots you can send me some hardware details to see if the US version matches the ROW version
if that's the case backup partitions modified by Lineage OS (it has to be the right partitions)
Install Lineage
if it doesn't work well go back to TWRP and restore the backed up partitions and relock the bootloader and you're back to original state
Of course this would have to be done very carefully since you don't have a factory firmware image as a fail safe.
If it works you would probably be the first to have TWRP and Lineage on the US model
Click to expand...
Click to collapse
Ordered one today. Should be here Wednesday. I'm excited.

glitchhawk said:
Ordered one today. Should be here Wednesday. I'm excited.
Click to expand...
Click to collapse
Good stuff. When you try to boot TWRP after bootloader unlock make sure you just boot and don't flash.
The partitions you have to backup are "System Image", boot and recovery. I'd recommend to do a second backup via command line dd tool to be sure you have a valid backup. The backup should be done onto an external SD card so you can't accidentally wipe it.
Then wipe data before flashing Lineage and hopefully all goes well.
Optionally you could upload your partition backups done with dd so others have them in case something goes wrong.

matshias said:
Good stuff. When you try to boot TWRP after bootloader unlock make sure you just boot and don't flash.
The partitions you have to backup are "System Image", boot and recovery. I'd recommend to do a second backup via command line dd tool to be sure you have a valid backup. The backup should be done onto an external SD card so you can't accidentally wipe it.
Then wipe data before flashing Lineage and hopefully all goes well.
Optionally you could upload your partition backups done with dd so others have them in case something goes wrong.
Click to expand...
Click to collapse
Sorry, command line dd tool? That is something I haven't ever done before. Is that something I need to download or is it embedded in adb?

glitchhawk said:
Sorry, command line dd tool? That is something I haven't ever done before. Is that something I need to download or is it embedded in adb?
Click to expand...
Click to collapse
You just connect with ADB shell in TWRP and then you can use it like that
Code:
dd if=/dev/block/bootdevice/by-name/partition of=/sdcard1/partition.img bs=4096
Replace "partition" with system, boot or recovery to make a raw backup of the respective partition.
Make sure that the external SD card is mounted in TWRP and has lots of free space.
Note that the system partition is stored in raw format. If you want to restore it later with fastboot it has to be in sparse format. For that you need the tool img2simg. If you want to restore with dd, the raw format is used.
Since the system partition is very large you have to check that the IMG file you get has the right size. Should be around 3.8 GB.
When you restore it can happen that it doesn't work in which case you just try again until it works.
Again all this is meant as a fail safe if TWRP backup has problems.

matshias said:
You just connect with ADB shell in TWRP and then you can use it like that
Code:
dd if=/dev/block/bootdevice/by-name/partition of=/sdcard1/partition.img bs=4096
Replace "partition" with system, boot or recovery to make a raw backup of the respective partition.
Make sure that the external SD card is mounted in TWRP and has lots of free space.
Note that the system partition is stored in raw format. If you want to restore it later with fastboot it has to be in sparse format. For that you need the tool img2simg. If you want to restore with dd, the raw format is used.
Since the system partition is very large you have to check that the IMG file you get has the right size. Should be around 3.8 GB.
When you restore it can happen that it doesn't work in which case you just try again until it works.
Again all this is meant as a fail safe if TWRP backup has problems.
Click to expand...
Click to collapse
Okay awesome. Thanks. So if I make up a dd backup for myself or others to use in the future, it's best to convert to sparse? Unless its only for myself then I could leave it in raw basically? Thanks again for all the info.

matshias said:
You just connect with ADB shell in TWRP and then you can use it like that
Code:
dd if=/dev/block/bootdevice/by-name/partition of=/sdcard1/partition.img bs=4096
Replace "partition" with system, boot or recovery to make a raw backup of the respective partition.
Make sure that the external SD card is mounted in TWRP and has lots of free space.
Note that the system partition is stored in raw format. If you want to restore it later with fastboot it has to be in sparse format. For that you need the tool img2simg. If you want to restore with dd, the raw format is used.
Since the system partition is very large you have to check that the IMG file you get has the right size. Should be around 3.8 GB.
When you restore it can happen that it doesn't work in which case you just try again until it works.
Again all this is meant as a fail safe if TWRP backup has problems.
Click to expand...
Click to collapse
turns out when you buy a ZA1N, it still comes as a YT-X703F. so.. looks like im probably set to start TWRPing

How to backup IMEI (efs parition) ?

Hi folks
How to take a backup of the efs partition ? I am not seeing it in twrp partitions list for backup. Any help is highly appreciated.

If you are looking for a quick solution, you can try the app(s) available in play store. Requires root and I believe you are rooted.
Nandroid backup through TWRP will save EFS with other partitions. Or you can try terminal commands through TWRP for backing up the modem files. Don't ask me for commands, I will probably mess up the code !

Two questions about persist partition

Hello,
Two fast questions about persist partition
- Is It possible to backup the persistbak partition and flash to persist partition to fix It without losing widevine L1?
- why Xiaomi includes in official fastboot roms a persist partition that is never flashed by default and if you force flashing It you lose widevine L1? What's the sense of this?

M.N.C. said:
Hello,
Two fast questions about persist partition
- Is It possible to backup the persistbak partition and flash to persist partition to fix It without losing widevine L1?
Click to expand...
Click to collapse
Running these two commands in a terminal will backup 'persistbak' to internal storage as an image (.img):
su
dd if=/dev/block/by-name/persistbak of=/sdcard/persistbak.img
Click to expand...
Click to collapse
Yes, you can use that backup to restore persist.

Having a persist backup is more precious than owning the phone it self
My partition gets glitched every month my selfie cam doesn't pop up anymore (i tried to follow some guys tips and boot into miui and calibrate it but didn't work)
I have 2 imgs (persist and persistbak) sometimes flashing persist fixes it for me and sometimes it does nothing but persistbak fixes it

Badis st said:
Having a persist backup is more precious than owning the phone it self
My partition gets glitched every month my selfie cam doesn't pop up anymore (i tried to follow some guys tips and boot into miui and calibrate it but didn't work)
I have 2 imgs (persist and persistbak) sometimes flashing persist fixes it for me and sometimes it does nothing but persistbak fixes it
Click to expand...
Click to collapse
Thank you for the answer!
So you flash the persistbak partition upon the "corrupted" persist partition without losing widevine L1? And flashing a backup persist partition never risks to brick the phone because of anti rollback, right?
P.S. what recovery do you use to backup/restore those partitions? Regular TWRP will do the job or do I need a specific modded version?

M.N.C. said:
Thank you for the answer!
So you flash the persistbak partition upon the "corrupted" persist partition without losing widevine L1? And flashing a backup persist partition never risks to brick the phone because of anti rollback, right?
P.S. what recovery do you use to backup/restore those partitions? Regular TWRP will do the job or do I need a specific modded version?
Click to expand...
Click to collapse
I doubt that official TWRP 3.4.0 supports backup/restore/flash to persistbak.
The following TWRP 3.4.0.2 (using for months) has some extensions over the official (supporting more partitions), but it supports only for persist, not for persistbak:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
Hence I'm also interested which TWRP supports backup/restore for persistbak
Btw, persist can be disk-dumped from TWRP Terminal:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
You can also disk-dump from ADB, you must use the following two commands before:
adb shell
su
and you must grant root permission (Magisk required) to the shell, when prompted
Edit:
Disk-dump should work for both partitions, just tested in Terminal emulator:
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/persistbak of=/sdcard/persistbak.img
You should then be able to flash from Fastboot:
fastboot flash persist persist.img
fastboot flash persistbak persistbsk.img

zgfg said:
I doubt that official TWRP 3.4.0 supports backup/restore/flash to persistbak.
The following TWRP 3.4.0.2 (using for months) has some extensions over the official (supporting more partitions), but it supports only for persist, not for persistbak:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
Hence I'm also interested which TWRP supports backup/restore for persistbak
Btw, persist can be disk-dumped from TWRP Terminal:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
You can also disk-dump from ADB, you must use the following two commands before:
adb shell
su
and you must grant root permission (Magisk required) to the shell, when prompted
Edit:
Disk-dump should work for both partitions, just tested in Terminal emulator:
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/persistbak of=/sdcard/persistbak.img
You should then be able to flash from Fastboot:
fastboot flash persist persist.img
fastboot flash persistbak persistbsk.img
Click to expand...
Click to collapse
Short answer, Sorry I'm busy ATM: Orange Fox recovery Will do the job

M.N.C. said:
Short answer, Sorry I'm busy ATM: Orange Fox recovery Will do the job
Click to expand...
Click to collapse
For the matter of fact I just installed latest (?) unofficial OranfeFox r11 (Davinci is no more officially supported) and compared which partitions it supports for Backup/Restore (black and orange screenshots), compared to TWRP 3.4.0.2 unofficial by Brigudav (black and blue screenshot)
Neither of them supports Persistbak (!) for Backup/Restore (I'm talking about what is supported by UI - disk-dumping in Terminal can be done for both and in other TWRP versions).
And btw, TWRP supports more partitions for Backup/Restore, e.g VBMeta while OrangeFox doesn't .
Similarly for the partitions offered when flashing an img file (more on TWRP then OF)

Badis st said:
Having a persist backup is more precious than owning the phone it self
My partition gets glitched every month my selfie cam doesn't pop up anymore (i tried to follow some guys tips and boot into miui and calibrate it but didn't work)
I have 2 imgs (persist and persistbak) sometimes flashing persist fixes it for me and sometimes it does nothing but persistbak fixes it
Click to expand...
Click to collapse
Bro my phone camera comes out and goes in and there's error saying couldn't open front camera. And after trying again it says calibrate camera. But after calibrating it says couldn't calibrate. Is it partition issue. I replaced front camera module but it didn't solved my problem

akshay07057 said:
Bro my phone camera comes out and goes in and there's error saying couldn't open front camera. And after trying again it says calibrate camera. But after calibrating it says couldn't calibrate. Is it partition issue. I replaced front camera module but it didn't solved my problem
Click to expand...
Click to collapse
Yup happens to me every 10-20 days it's annoying af, u can flash your persist backup if u have one, if u don't flash someone's persist or the one included in fastboot roms but u will loose L1 (no more netflix in HD)

Stillness said:
Running these two commands in a terminal will backup 'persistbak' to internal storage as an image (.img):
Yes, you can use that backup to restore persist.
Click to expand...
Click to collapse
can i use this for the poco f2 pro?