Does anyone know of a successful method of full backup and restore of the Google pixel xl?
If so, how?
I've heard twrp isn't ready and I can't find a way to full nandroid backup either. Some clarification would be most appreciated!
prot- said:
Does anyone know of a successful method of full backup and restore of the Google pixel xl?
If so, how?
I've heard twrp isn't ready and I can't find a way to full nandroid backup either. Some clarification would be most appreciated!
Click to expand...
Click to collapse
You cant do a back up through twrp now ? I can on mine and have for months. What happens when you try ?
M9guy said:
You cant do a back up through twrp now ? I can on mine and have for months. What happens when you try ?
Click to expand...
Click to collapse
I heard the restore doesn't actually won't. Have you tried?
prot- said:
I heard the restore doesn't actually won't. Have you tried?
Click to expand...
Click to collapse
I have months ago and worked fine. Are you on the rc1 twrp or the beta ?
M9guy said:
I have months ago and worked fine. Are you on the rc1 twrp or the beta ?
Click to expand...
Click to collapse
Alpha2 still. I heard that rc1 has bootlooped people too. Hmm
[/COLOR]
prot- said:
Alpha2 still. I heard that rc1 has bootlooped people too. Hmm
Click to expand...
Click to collapse
I would flash to rc1 as the beta versions the back ups were not working correctly.
I've restored backups several times and it seemed to go well but the restored rom was killing the battery, not sure why. The phone stayed warm even when off. I didn't spend enough time to see what was going on. Wiping data or a clean reinstall fixed it.
RC 1 been working for me. It's perfect, you don't even need to install TWRP, you can just boot to it via fastboot, backup, reboot and still completely stock. If people are into that.
Sent from my Pixel XL
I'm running rc1 and I have not been able to preform a backup. It tells me that it cannot create the folder to backup... I tried switching boot slots and still can't back up. Is there something I missed?
In TWRP I can't make a back up it says it can't do it, an error message comes up. Will a back up and restore work in flash fire? I know that's from within the ROM I'm just wondering will that work.
Rydah805 said:
RC 1 been working for me. It's perfect, you don't even need to install TWRP, you can just boot to it via fastboot, backup, reboot and still completely stock. If people are into that.
Sent from my Pixel XL
Click to expand...
Click to collapse
How to boot to TWRP via fastboot? do you have a guide?
Ro_man said:
How to boot to TWRP via fastboot? do you have a guide?
Click to expand...
Click to collapse
Literally the first step of its installation.
fastboot boot TWRP.img
Sent from my Pixel XL
Rydah805 said:
Literally the first step of its installation.
fastboot boot TWRP.img
Sent from my Pixel XL
Click to expand...
Click to collapse
Thanks.
dmb219 said:
I've restored backups several times and it seemed to go well but the restored rom was killing the battery, not sure why. The phone stayed warm even when off. I didn't spend enough time to see what was going on. Wiping data or a clean reinstall fixed it.
Click to expand...
Click to collapse
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
robocuff said:
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
Click to expand...
Click to collapse
Thanks, I'll try that next time.
robocuff said:
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
Click to expand...
Click to collapse
I made and restored a backup today using system and vendor images as you suggested and it worked just fine. Thanks again for the help.
I have full backup of stock rooted and Pure Nexus. Works perfectly fine with RC1.
Related
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far
This is confusing the heck out of me. So I realize there's 2 partitions and why they're there. So the B partition is just a fresh blank copy of whatever image you're on? I see posts about flashing to a and b, but when I look in a stock image folder they aren't labeled a and b. My pixel is in the stock October ROM. I flashed TWRP alpha 2 as alpha 1 and rc1 just showed the TWRP splash screen and kept flickering. I backed up my stock os then wiped and flashed pure nexus. Wouldn't flash, some Android binary update error (I've heard my boot.img was the wrong version possibly?). Said okay, just restore my backup. Did that and looked like everything went fine, rebooted and it rebooted right back to TWRP, wouldn't boot to os. Eventually just flashed the stock October image. Am I missing something? Do I need to be on a newer Android version for the rc1 TWRP to work? Any help is appreciated, thank you.
To get out of the bootloop just dl latest factory Image from Google and flash bootimage to slot a and b.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
So my backup restore most likely went fine, I just missed this step?
danielson2047 said:
So my backup restore most likely went fine, I just missed this step?
Click to expand...
Click to collapse
did you first boot to twrp and then flashed twrp zip from twrp?
also, any particular reason for being still at October software?
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
Don't have Verizon edition, but pretty sure it wouldn't lock it.
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention​ tje probable class action lawsuits.
So can i keep my stock rom as is and use twrp to flash to the "b' side? I suppose as soon as i'd update the stock side it would just override the b side huh.
TonikJDK said:
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention​ tje probable class action lawsuits.
Click to expand...
Click to collapse
Good thought. I was thinking in terms of "poor me my phones locked". Never thought about it from the data side.
I keep getting a zram dump pop up that can never got before after flashing in twrp. Does anyone else have this issue? It turns into a boot loop when flashing arise sound mod and sometimes after flashing ROMs. It boot loops between the Google splash and the zram dump screen. Man this is annoying Any help would be highly appreciated!
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
What process did you use when doing the complete factory flash?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
And did you flash the 7.1.2 factory image or 7.1.1?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
If you bought your pixel from google and NOT from verizon, flash the 7.1.2 factory image, then boot twrp RC1 and flash RC2
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Thank you I appreciate it going to do this when I get home
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Guessphx said:
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Click to expand...
Click to collapse
I have the 128GB and never once had an issue. I know with the N6 it happened to it, but I'm not if that happens to our pixels .
Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!
M5devil said:
Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!
Click to expand...
Click to collapse
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...
M5devil said:
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...
Click to expand...
Click to collapse
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .
Dazed No More said:
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .
Click to expand...
Click to collapse
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!
M5devil said:
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!
Click to expand...
Click to collapse
Wifi works?
Dazed No More said:
Wifi works?
Click to expand...
Click to collapse
Yes, Wi-Fi works!
M5devil said:
Yes, Wi-Fi works!
Click to expand...
Click to collapse
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.
Dazed No More said:
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.
Click to expand...
Click to collapse
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!
M5devil said:
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!
Click to expand...
Click to collapse
I won't go back to an Oreo OOS until audio controls for wired and wireless headphones work. I've tried codename phoenix, liquid remix, AICP and validus. I personally liked validus the most and aicp second.
I've downloaded the latest Android Pie stock image, however it seems that once I manual boot to TWRP 3.2.3, it causes the Android system UI to keep crashing. Any guesses on what's going on or what I'm doing wrong? I am flashing with the W removed.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I've downloaded the latest Android Pie stock image, however it seems that once I manual boot to TWRP 3.2.3, it causes the Android system UI to keep crashing. Any guesses on what's going on or what I'm doing wrong? I am flashing with the W removed.
Click to expand...
Click to collapse
So after you fastboot the factory image, and then fastboot into twrp you get a crash???
Reflash factory image but don't install TWRP. Do you still get crashes?
sublimaze said:
Reflash factory image but don't install TWRP. Do you still get crashes?
Click to expand...
Click to collapse
I fastboot into TWRP, backup my phone, rebooted back into system ( on accident) and all the sudden my system UI was broke.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I fastboot into TWRP, backup my phone, rebooted back into system ( on accident) and all the sudden my system UI was broke.
Click to expand...
Click to collapse
Go back to bone stock and don't install/fastboot TWRP, and see if you still get FCs.
sublimaze said:
Go back to bone stock and don't install/fastboot TWRP, and see if you still get FCs.
Click to expand...
Click to collapse
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're backing up a fresh stock install? Is that correct?
Try flashing JUST the factory image, let it boot, boot into bootloader, fastboot into TWRP 3.2.2-0.IMG (previous version of TWRP), and see if you're still crashing.
Az Biker said:
You're backing up a fresh stock install? Is that correct?
Try flashing JUST the factory image, let it boot, boot into bootloader, fastboot into TWRP 3.2.2-0.IMG (previous version of TWRP), and see if you're still crashing.
Click to expand...
Click to collapse
That's what I mean by stock, I'm sorry. I've been installing the factory image (flash-all). I'll try the 3.2.2 when I get home
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Click to expand...
Click to collapse
Are you using Titanium Backup or a similar 3rd party app to restore data? If you are restoring system data, especially across different versions of Android, that is likely the culprit.
TWRP does not modify any system data except the recovery files, so it should not affect system UI. I updated from Oreo to Pie by flashing the Pie factory image, then installed TWRP & Magisk in the same recovery session, and I have yet to experience any system UI errors. I know that doesn't really help your situation, but your it appears to be limited to your phone/setup.
sublimaze said:
Are you using Titanium Backup or a similar 3rd party app to restore data? If you are restoring system data, especially across different versions of Android, that is likely the culprit.
TWRP does not modify any system data except the recovery files, so it should not affect system UI. I updated from Oreo to Pie by flashing the Pie factory image, then installed TWRP & Magisk in the same recovery session, and I have yet to experience any system UI errors. I know that doesn't really help your situation, but your it appears to be limited to your phone/setup.
Click to expand...
Click to collapse
I honestly have not idea what was going on, but I installed twrp 3.2.2, Flash Kernel3.0.3, and the Magisk posted in your post all in the same session and it worked. Im lost, but im good now.
Thank you all.