Hi at all,
with my new phone Xiaomi Mi A2 lite, I wanted doing the backup of my phone with TWRP, because in case of problem I will ready to restored it.
But I have discovery that the partition "data" is not visible because is encrypted and is impossible with TWRP to do the backup of it.
Is impossible use the storage of phone for make the backup beacuse it is also encrypted.
Is there anyone that has found a solution to decrypt and copy the partition in question?
Sorry by poor english and thanks all wonderfull team for the working doing.
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
thorin0815 said:
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
Click to expand...
Click to collapse
Thank you for the reply, I sad to reading this. So we must hope an next update for our TWRP. Now is impossible decrypted the partition entering the correct password or pattern.
So today is impossible do the full backup of app and setting....
liboriof said:
Thank you for the reply, I sad to reading this. So we must hope an next update for our TWRP. Now is impossible decrypted the partition entering the correct password or pattern.
So today is impossible do the full backup of app and setting....
Click to expand...
Click to collapse
i think you flashed the twrp image instead of booting it and then using the zip to install it. just redo the twrp installation exactly how it is written on the thread, encryption will work. restoring a backup however, does not (doesn't boot). for this you have to restore the data backup and then reflash the same rom the backup was made with from fastboot with the "flash_all_except_storage.bat". I would also recommend to do this before you try to reinstall twrp.
thorin0815 said:
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
Click to expand...
Click to collapse
Yes, it is far from usable but at least he built a working tree anyone could build a booting twrp from. it defenitely does not deserve the official status bcs this would mean it is maintained and working propperly.
wertus33333 said:
i think you flashed the twrp image instead of booting it and then using the zip to install it. just redo the twrp installation exactly how it is written on the thread, encryption will work. restoring a backup however, does not (doesn't boot). for this you have to restore the data backup and then reflash the same rom the backup was made with from fastboot with the "flash_all_except_storage.bat". I would also recommend to do this before you try to reinstall twrp.
Click to expand...
Click to collapse
Thank you for reply, I will try to do as you say and later I will write what happened.
I have used the guide by wertus33333 and it working. Thank you for your advice.
Related
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
adbPush said:
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Just press the volume down and power button at the same time. Should get you into TWRP and then transfer the file you want to install the ROM on and flash it. That should do it. Hopefully this helps.
rpalmon said:
Just press the volume down and power button at the same time. Should get you into TWRP and then transfer the file you want to install the ROM on and flash it. That should do it. Hopefully this helps.
Click to expand...
Click to collapse
I did flash the factory image from fastboot successfully without errors but it doesn't boot. Do you mean a custom rom? Im afraid that may do things worse.
adbPush said:
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
If you have your userdata backed up, I suggest you flash everything including letting it factory reset your userdata.
Keep in mind your nandroid backups are on userdata, so move those off the phone first.
One other thing, when you restored nandroid backup, did you use TWRP 3.0.2-1 and did you restore EFS partition? There was a bug in TWRP where it would crash your phone because it overwrote an EFS partition with the contents of another EFS partition due to incorrect filenames.
sfhub said:
If you have your userdata backed up, I suggest you flash everything including letting it factory reset your userdata.
Keep in mind your nandroid backups are on userdata, so move those off the phone first.
One other thing, when you restored nandroid backup, did you use TWRP 3.0.2-1 and did you restore EFS partition? There was a bug in TWRP where it would crash your phone because it overwrote an EFS partition with the contents of another EFS partition due to incorrect filenames.
Click to expand...
Click to collapse
Yes i used TWRP 3.0.2-1 to restore EFS. Was the bug to that version? Is there any way to fix it?
EDIT: I downloaded and installed twrp 3.0.2-2 and when I try to restore the efs it says "efs2 no such file or directory". The previous version of twrp doesn't semm to have backed up this partition. I only find efs1 in the backup folder. @sfhub can you plz help me? How am I going to find the second partition of efs. Can you plz provide me a backup?
adbPush said:
Yes i used TWRP 3.0.2-1 to restore EFS. Was the bug to that version? Is there any way to fix it?
EDIT: I downloaded and installed twrp 3.0.2-2 and when I try to restore the efs it says "efs2 no such file or directory". The previous version of twrp doesn't semm to have backed up this partition. I only find efs1 in the backup folder. @sfhub can you plz help me? How am I going to find the second partition of efs. Can you plz provide me a backup?
Click to expand...
Click to collapse
There is some info about this over on the TWRP thread.
Essentially if you write all zeros into the efs partitions, the phone will recreate the data (if you instead of non-zero data, it will think things are corrupted)
I suggest you read very carefully erverything you can about recovering from the TWRP EFS bug. This post will get you started, but I suggest you read the original thread from the 6p forum that is referenced in this post. I haven't done this myself nor have I read that carefully so don't want to give you bad advice and make your situation worse.
http://forum.xda-developers.com/nex...h-recovery-t3230471/post68595543#post68595543
sfhub said:
There is some info about this over on the TWRP thread.
Essentially if you write all zeros into the efs partitions, the phone will recreate the data (if you instead of non-zero data, it will think things are corrupted)
I suggest you read very carefully erverything you can about recovering from the TWRP EFS bug. This post will get you started, but I suggest you read the original thread from the 6p forum that is referenced in this post. I haven't done this myself nor have I read that carefully so don't want to give you bad advice and make your situation worse.
http://forum.xda-developers.com/nex...h-recovery-t3230471/post68595543#post68595543
Click to expand...
Click to collapse
Thank you very much! I'll read it first thing tomorrow and I'll let you know what happened.
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
adbPush said:
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
Click to expand...
Click to collapse
Glad to hear you got things fixed.
I think i have done the same to my EFS Partition
adbPush said:
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
Click to expand...
Click to collapse
Can you please share the exact command you used for nexus 5x as the link above is for nexus 6p.
saadabbasi said:
Can you please share the exact command you used for nexus 5x as the link above is for nexus 6p.
Click to expand...
Click to collapse
They are the exact same commands as for 6P:
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
Hello
I'm trying to install Resurrection Remix, but everytime the flashing is done (Rom an Gapps) the phone reboots into TWRP only. No Lenovo logo, zero, nada. I thought it was a problem with RR and tried Lineage OS just for kicks but the same thing happened.
I've done the dd if=/ command method which i used some time ago with my beloved nexus 4 and Cyanogenmod nightlies; worked like a charm back then, however this time the path doesn't seem to exist.
Glad i made a nandroid backup. My phone can be brought back as new, no loss there, but i want to try custom ROMs.
What could i possible do to fix this?
Regards
r0ckm4n said:
... the phone reboots into TWRP only. No Lenovo logo, zero, nada.
Click to expand...
Click to collapse
Do you mean you don't see the Lenovo bootlogo during boot? What do you use to make and restore the Nandroid backup? Does everything work well after restoring the Nandroid backup? Also, most importantly, what's the model name of the device you're using?
Droidge said:
Do you mean you don't see the Lenovo bootlogo during boot? What do you use to make and restore the Nandroid backup? Does everything work well after restoring the Nandroid backup? Also, most importantly, what's the model name of the device you're using?
Click to expand...
Click to collapse
The phone never gets to the Lenovo Logo, goes directly into TWRP after Reboot or Power On. Everything works after restoring from TWRP 3.0.3.
Phone model is A6020I36, Hardare Version H201.
Thank you.
r0ckm4n said:
The phone never gets to the Lenovo Logo, goes directly into TWRP after Reboot or Power On. Everything works after restoring from TWRP 3.0.3.
Click to expand...
Click to collapse
All right, time for a little bit of experimentation. Now, this could be dangerous, and I hope you know how to recover a bricked phone using QPST.
Does the Nandroid backup have a backup of the boot partition? If so, I'd like you to reproduce the issue; and when you get to the point of restoring the backup, restore everything but the boot partition. Let me know if you see the Lenovo bootlogo during the reboot sequence that follows.
Droidge said:
All right, time for a little bit of experimentation. Now, this could be dangerous, and I hope you know how to recover a bricked phone using QPST.
Does the Nandroid backup have a backup of the boot partition? If so, I'd like you to reproduce the issue; and when you get to the point of restoring the backup, restore everything but the boot partition. Let me know if you see the Lenovo bootlogo during the reboot sequence that follows.
Click to expand...
Click to collapse
I'll read everything about QPST first and then i'll proceed hopefully this weekend, i'll keep updating here.
Kind Regards
Turns out i just needed to downgrade TWRP from 3.0.3 to 3.0.2 and everything worked as it should have been from the start.
Thank you for your replies. Cheers!
Happened to me one day, Shreps TWRP it's bugged, it have two or three bugs related with F2FS and the bootloop, you always can flash the Russian TWRP for solving this
KiiKeEp said:
Happened to me one day, Shreps TWRP it's bugged, it have two or three bugs related with F2FS and the bootloop, you always can flash the Russian TWRP for solving this
Click to expand...
Click to collapse
I dont get it, can u pls explain it bro
This happened to me when I installed AOKP. Remove the battery and boot again. It works for me and that is how I do it every time there is an update. First boot takes time so don't panic.
My Question is About Twrp, if i make a Back-up of my system completery, and install a ROM and not liked her or bricked my device (Mi a2 Lite) i can take back again, right? without install a ROM stock? Thansk for Answering ? i make one time but Using a Clockwordmod on samsung Old i bricked the device and i Restore a Backup and Back
Sorry about My english bad
Yes, but use unofficial TWRP from ROM section not the official one.
Backup boot, system image, vendor image and data.
Works for custom ROMs, not sure about stock ROM.
Also backup EFS and persist once in case you lost IMEI or sensors.
Pat750 said:
Yes, but use unofficial TWRP from ROM section not the official one.
Backup boot, system image, vendor image and data.
Works for custom ROMs, not sure about stock ROM.
Also backup EFS and persist once in case you lost IMEI or sensors.
Click to expand...
Click to collapse
I unlocked my bootloader yesterday and my user data and files have not been deleted
but my other question is If i install twrp i lose?
[email protected] said:
I unlocked my bootloader yesterday and my user data and files have not been deleted
but my other question is If i install twrp i lose?
Click to expand...
Click to collapse
I'm surprised that unlocking didn't delete your data, for me it did and it usually does.
For TWRP use fastboot boot <filename>.img to boot it and then flash the zip.
Normally that doesn't delete data, but always backup important data first.
I'm not sure how good TWRP handles encrypted data...I'm always unencrypted.
Before TWRP backup people say to remove pins and maybe fingerprints first (there are zip files for that) because then restoring will work better.
Good luck, happy flashing and first search and read if you are unsure.
Pat750 said:
I'm surprised that unlocking didn't delete your data, for me it did and it usually does.
For TWRP use fastboot boot <filename>.img to boot it and then flash the zip.
Normally that doesn't delete data, but always backup important data first.
I'm not sure how good TWRP handles encrypted data...I'm always unencrypted.
Before TWRP backup people say to remove pins and maybe fingerprints first (there are zip files for that) because then restoring will work better.
Good luck, happy flashing and first search and read if you are unsure.
Click to expand...
Click to collapse
before i Unlock the BL i pressed the button "Down" of sound and not deleted My Data :3
Hello
I have a Redmi K30 5G running MIUI by xiaomi.eu (V12.5.7.0.RGICNXM stable - Android 11) with TWRP 3.5.2_10-5 by hadenix.
I am wishing to update rom to xiaomi.eu (V13.0.1.0.SGICNXM stable - Android 12).
Before doing so i wish to take the precaution of making a backup of the phone in case something goes wrong during the update and I need to roll back.
I am not interested in rooting the phone.
What is the best (safest) way to do this?
Am I correct in stating the best way to do this is using my TWRP?
I am considering using the TWRP backup method (something I have never done before).
Most of the online methods show System, Data & Boot as the necessary partitions required to be backed up/restored to roll back the phone.
Is that correct?
In my TWRP I cannot see the System partition listed in the BACKUP partitions.
Yet I can see the system partition listed in the MOUNT partitions.
So I am unsure where to go from here.
I am hoping someone out there has knowledge on this backup/restore procedure (for K30 5G with TWRP 3.5.2_10-5 by hadenix) and can assist.
Thanks.
wmr68 said:
Hello
I have a Redmi K30 5G running MIUI by xiaomi.eu (V12.5.7.0.RGICNXM stable - Android 11) with TWRP 3.5.2_10-5 by hadenix.
I am wishing to update rom to xiaomi.eu (V13.0.1.0.SGICNXM stable - Android 12).
Before doing so i wish to take the precaution of making a backup of the phone in case something goes wrong during the update and I need to roll back.
I am not interested in rooting the phone.
What is the best (safest) way to do this?
Am I correct in stating the best way to do this is using my TWRP?
I am considering using the TWRP backup method (something I have never done before).
Most of the online methods show System, Data & Boot as the necessary partitions required to be backed up/restored to roll back the phone.
Is that correct?
In my TWRP I cannot see the System partition listed in the BACKUP partitions.
Yet I can see the system partition listed in the MOUNT partitions.
So I am unsure where to go from here.
I am hoping someone out there has knowledge on this backup/restore procedure (for K30 5G with TWRP 3.5.2_10-5 by hadenix) and can assist.
Thanks.
Click to expand...
Click to collapse
Backup/Restore will not work with TWRP.
Try with:Micloud,Miphone assistant,Google or third-party apps.
But in general the update goes well using the script included in the zip:windows_fastboot_update_rom.bat
NOSS8 said:
Backup/Restore will not work with TWRP.
Try with:Micloud,Miphone assistant,Google or third-party apps.
But in general the update goes well using the script included in the zip:windows_fastboot_update_rom.bat
Click to expand...
Click to collapse
Thanks for the reply!
In the past I have backed up with MIUI and Google but I am keen to explore the TWRP option as my understanding is that this is a more complete backup. There are guides online showing how to do this, so i am curious as to why you say that "Backup/Restore will not work with TWRP."?
wmr68 said:
Thanks for the reply!
In the past I have backed up with MIUI and Google but I am keen to explore the TWRP option as my understanding is that this is a more complete backup. There are guides online showing how to do this, so i am curious as to why you say that "Backup/Restore will not work with TWRP."?
Click to expand...
Click to collapse
Android 11 to 12.
NOSS8 said:
Android 11 to 12.
Click to expand...
Click to collapse
Thanks for the reply! I take your point.
But in this instance I would be restoring an Android 11 backup with TWRP (TWRP works for Android 11).
Even though I would be restoring the Android 11 backup over an Android 12 rom using TWRP, would that not work?
What would be the reasons that this wouldn't work?
I am trying to learn how all of this stuff works!
Thanks for your advice so far.
wmr68 said:
Thanks for the reply! I take your point.
But in this instance I would be restoring an Android 11 backup with TWRP (TWRP works for Android 11).
Even though I would be restoring the Android 11 backup over an Android 12 rom using TWRP, would that not work?
What would be the reasons that this wouldn't work?
I am trying to learn how all of this stuff works!
Thanks for your advice so far.
Click to expand...
Click to collapse
Twrp for android 12 Cannot decrypt data
System is different
The backup works but not the restore, now you can try with the last TWRP A12, I had tried with the penultimate one.
https://androidfilehost.com/?w=files&flid=318240
"Twrp for android 12 Cannot decrypt data" - Got it. Thanks! Now I understand.