Database Info

Restore TWRP Backup?

Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?

****, good question
Sent from my HTC One X using xda app-developers app

Restore takes care of wiping for you.

Piggybacking off the OP, sometimes when I try to restore my TWRP backup it fails, and then the only way I've found to get it working again is to do a boot loader factory reset, and then essentially start from scratch or load an older working backup. No problem, just a minor annoyance. Is there something I'm doing wrong or any advice someone can give me?
Sent from my HTC One X using xda app-developers app

Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I always wipe everything before a restore, just in case
Better safe than sorry

Restoring a back up !
When restoring a back up from any recovery wipe everything just as if you were installing a new rom. Factory reset, cache, dalvik cache, system just to be safe. Factory reset wipes data and all cache but not system and if you do a factory reset and then try to wipe I think dalvik again you get an error but no harm done it just will not do it again. I usually do them all and then do the superwipe zip and that willl give you a good piece of mind that it is properly wiped. Also, I have noticed that using the external sd card seems to work best for installing roms or backing up and restoring back ups or anything else like mods or themes. Here is the superwipe zip in case anyone needs it.

Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I've done both, but I like not having reinstall all my apps, and reset all my ringtone, and that goes with a full wipe. so when ever i can i flash over. Just make sure your slashing the same rom over the old one.

You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).

XNine said:
You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).
Click to expand...
Click to collapse
Ahh, this is true I recant my statement. I was mistakenly thinking about flashing a new ROM over an older version, not a buck-up. I feel stupid.

when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?

gunnyman said:
when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?
Click to expand...
Click to collapse
Nope. I just flashed a bunch of roms yesterday and did restores with no issue. I think if your using the stock rooted 2.2 you are correct, but any other rom a restore works fine.

Not Restoring = Bad Idea
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I have made the mistake of not wiping everything (excluding sd card) when changing ROMs or when restoring from a backup. This may be a little different because it was when I was switching to a new ROM on my brother's phone, but I tried to take the lazy way out and not restore everything. I really didn't feel like redownloading everything. I soon learned that this was a mistake, and his "phone" app suddenly disappeared. He was also unable to send or receive texts. This soon made the process even longer than I wished it to be because I needed to go back and restore everything again and get it back to normal.

Error While Restoring using twrp
I took a back up of everything using TWRP and then when i tried to restored its giving me error while restoring system E:Unable to extract tar archive . Please help

Are you trying to restore a backup from a different version of TWRP? For example, currently running 2.7.0.8 but backup was originally made using 2.3.3.1?
Sent from my Evita

error on backup restore twrp
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w

WOW! After a good 3/4 days of frustration, thinking I had ruined my device, I finally got my TWRP backup to restore.
It's my first time using this software and the restoration process is truly amazing. I mean, my test messages were still there, even my browser history and last page loaded up in chrome were still there. I'm blown away.
The strange thing is that It didn't work when all 3 partitions were selected. When I tried it this way (as per the many step by step instructions that I read) my phone would load up a black screen with just the notification bar visible. I'd see my voicemail, sms, wifi and battery icons at the top, but absolutely nothing else except for a myriad of pop ups that read 'Unfortunately [app name] has stopped working'.
So I bit the bullet and did some trial and error with the partitions.
Turns out that when I only selected 2 of the 3 (I believe they were 'Boot', 'Data' and deselected 'System') everything loaded up just as it was before the backup, except there were only the stock apps available and no google services at all. .....Very odd.
So I did the boot to recovery method before turning the phone off (vol. up - Home - Power) which restarted the phone and strangely brought back EVERYTHING as mentioned at the start of this post.
You can probably understand my confusion here and while I'm VERY happy that it all worked out, I don't understand why it worked with only 2 of the partitions but not with the recommended 3 of them?
Can anyone shed any light on this?
---------- Post added at 01:16 PM ---------- Previous post was at 01:02 PM ----------
debmikeshan said:
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w
Click to expand...
Click to collapse
Hmmm. I'm definitely no pro at this stuff, in fact i'm very new when it comes to using TWRP, but this is what happened with me.
First of all, the backup that I did was simply a folder of files, not zip.
Transferred that do my PC, wiped my phone with TWRP and replaced the backup folder back into the TWRP/Backup folder. However, after reading up on how to restore on about 10 different android sites/forums, only 1 post shared the most vital piece of information.
You folder has to be in the 'serial' number folder that's located in the 'Backup' folder for TWRP.
When I put my backup folder just into the TWRP/Backup folder, the Restore section would only see the folder itself but the partitions were not available/listed for selection.
Once I placed my Backup folder into the TWRP/Backup/e1oog75 (that alphanumeric name is just a random example made for visual clarity) folder, my partitions were visible and available for selection right away.
Hopefully this helps somewhat.

[Q] Device Hung up on boot screen-SVHD

Hi All,
Today suddenly my device hung up on Android screen and it doesn't go forward. I waited for like 10-15 min,pulled the battery out and rebooted but nothing happens(it still is stuck up on boot screen). I have been on this ROM for more than 8 months from now. What could go wrong suddenly?
Device: Inspire 4G
ROM: SVHD
Can anyone suggest me how to get past it without probably loosing my data?
Thanks!!

Wrong forum

sandy0594 said:
Hi All,
Today suddenly my device hung up on Android screen and it doesn't go forward. I waited for like 10-15 min,pulled the battery out and rebooted but nothing happens(it still is stuck up on boot screen). I have been on this ROM for more than 8 months from now. What could go wrong suddenly?
Device: Inspire 4G
ROM: SVHD
Can anyone suggest me how to get past it without probably loosing my data?
Thanks!!
Click to expand...
Click to collapse
as @maltazar1 said its the wrong forum
as for the problem.. it happened to me after using the same ROM for a long time without wiping cache and dalvik
try to backup the ROM..do a clean install..restore what you can from the Back up using TB
a thanks button would be appreciated

PHOENIX-9 said:
as @maltazar1 said its the wrong forum
as for the problem.. it happened to me after using the same ROM for a long time without wiping cache and dalvik
try to backup the ROM..do a clean install..restore what you can from the Back up using TB
a thanks button would be appreciated
Click to expand...
Click to collapse
Thanks for your suggestion. I am following them,will let you know once done!!

PHOENIX-9 said:
as @maltazar1 said its the wrong forum
as for the problem.. it happened to me after using the same ROM for a long time without wiping cache and dalvik
try to backup the ROM..do a clean install..restore what you can from the Back up using TB
a thanks button would be appreciated
Click to expand...
Click to collapse
Backed up the ROM and installed with clearing everything. Tried to restore the data but it's hanging up again. So,thought to forgot abt the apps data.

sandy0594 said:
Backed up the ROM and installed with clearing everything. Tried to restore the data but it's hanging up again. So,thought to forgot abt the apps data.
Click to expand...
Click to collapse
no no..dont restore the data in recovery
use titanium backup to extract the wanted APKs and data from the backup after installing a clean ROM

May I suggest restoring your broken backup (even if it fails) and reinstall SVHD over it without wiping anything except Dalvik, cache and battery stats. If everything else fails checkout one of the newer kitkat roms and manually restore your data partition or anything else needed. You can manually backup data or any other partition through AROMA file manager through recovery hope I help you out bro. Have a nice day.

PHOENIX-9 said:
no no..dont restore the data in recovery
use titanium backup to extract the wanted APKs and data from the backup after installing a clean ROM
Click to expand...
Click to collapse
Can I know how to achieve this. Usually I restore a backup that's created from titanium backup. But as I don't have TB files, how to restore the data from system backup from Titanium Backup?

sandy0594 said:
Can I know how to achieve this. Usually I restore a backup that's created from titanium backup. But as I don't have TB files, how to restore the data from system backup from Titanium Backup?
Click to expand...
Click to collapse
in TB press menu
extract from nandroid backup
choose your backed up ROM..

PHOENIX-9 said:
in TB press menu
extract from nandroid backup
choose your backed up ROM..
Click to expand...
Click to collapse
When I do the above steps,it says "Sorry this feature requires the Donate version"

sandy0594 said:
When I do the above steps,it says "Sorry this feature requires the Donate version"
Click to expand...
Click to collapse
oh sorry if you cant buy the Donate Version
try @CedArctic method

Please don't shout at me if wrong forum! Frozen boot screen
Deleted for wrong forum

Hello,
My DHD hung up with Cyanogenmod, one week after intallation. the same problem with SVHD.
several roms were tested, some with bugs and others without bugs but slow in using or other reboots when the camera is used.
Finally, I installed a rooted stock rom, (Android 2.3.5), every thing works correctly.
Best regards

Installed Cloudy G3 through TWRP, receivint system ui not responding error

Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?

it0ken said:
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
Click to expand...
Click to collapse
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.

hyelton said:
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
Click to expand...
Click to collapse
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.

it0ken said:
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
Click to expand...
Click to collapse
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.

hyelton said:
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
Click to expand...
Click to collapse
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.

it0ken said:
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
Click to expand...
Click to collapse
Correct

Flashing disaster!

First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).

First of all, I'm impressed that you have done as much as you have (or even wanted to for that matter) at 82. Most older people I know (I'm 42 btw)barely know how to use there phones in the os, much less know what recovery is, lol.
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?

BarrySamuels said:
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
Click to expand...
Click to collapse
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.

b.huss2 said:
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
Click to expand...
Click to collapse
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
MrSteelX said:
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
Click to expand...
Click to collapse
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.

BarrySamuels said:
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.

b.huss2 said:
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
Click to expand...
Click to collapse
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11

MrSteelX said:
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
Click to expand...
Click to collapse
I think that's kind of understood at this point. However, I see no problem with restoring a Oreo backup once he's back on Oreo.

BarrySamuels said:
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
Almost. You are missing one thing.
1. Flash the roll back firmware
2. Install TWRP using fastboot
3. Flash, using TWRP, OxygenOS 5.1.11
4. Before rebooting, FLASH TWRP IN TWRP (This is important, as flashing 5.1.11 will overwrite recovery)
5. Use your TWRP backup
6. Do what you need for files you want on internal storage.
Don't forget to flash TWRP after you update to 5.1.11.

Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.

BarrySamuels said:
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
Click to expand...
Click to collapse
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

Use the fastboot ROM recovery. It works (I've used it twice) no data wipe.

chazey2 said:
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.

BarrySamuels said:
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
Click to expand...
Click to collapse
Your welcome good luck

BootLoop after TWRP restore

Hello,
On Xiaomi Mi 10 Ultra with TWRP 3.4.2b-0623 wzsx150, i did a full backup (all partitions) then after some moding and all on phone. decided to restore the full backup trought TWRP
the phone goes on bootloop and didnt want to start.
i already fixed the phone by flashing rom again, but i'm wondering why a TWRP full restore give a bootloop ? any help to understand to avoid this next time
thanks a lot

This is late but this happened to me before aswell. You have to flash the rom which you've done the backup on and then just restore the data partition.

Does your device keep in a frozen black screen?

Psych0t1c20 said:
This is late but this happened to me before aswell. You have to flash the rom which you've done the backup on and then just restore the data partition.
Click to expand...
Click to collapse
i did it with same rom, but i think the issue is from me restoring all partition, i think i need to choose only ones needed

Rovyo said:
i did it with same rom, but i think the issue is from me restoring all partition, i think i need to choose only ones needed
Click to expand...
Click to collapse
If you are restoring to the same device of the backup, just restore it and then wipe data.
Reboot and it will work perfectly.

VD171 said:
If you are restoring to the same device of the backup, just restore it and then wipe data.
Reboot and it will work perfectly.
Click to expand...
Click to collapse
exactly what i have did, but i checked all partitions when i did the restore i think i need to uncheck some of them in order to avoid the bootloop