Related
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
wiredwrx said:
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
Click to expand...
Click to collapse
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
RMarkwald said:
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
Click to expand...
Click to collapse
Thanks. I will look into that. Any thoughts on the update?
wiredwrx said:
Thanks. I will look into that. Any thoughts on the update?
Click to expand...
Click to collapse
You'd have to get stock Android recovery on there somehow, but if you're doing the official update and you removed any /system/app apps with Titanium Backup or anything, it'll also fail. If you flashed a custom kernel, it'll fail as well. Official updates run system checks to see that the stock files are all there and the correct versions.
You could backup everything you want to save on internal sd card (pictures/music etc), and flash the official factory Google images via fastboot. Or flash custom recovery and flash a 4.2.2 ROM. Either way, you'll have to wipe everything so you'll loose apps and app data, which you'll have to re-install again.
wiredwrx said:
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
Click to expand...
Click to collapse
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
bftb0 said:
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
Click to expand...
Click to collapse
Thanks for the detailed breakdown. I may just update with your instructions. Are you aware of a way to suppress the nag screen.
Hi, planning on rooting the device and installing PA (sticking with PA's kernel). New to this area, I hope the questions are fine.
1. What's the difference between Carbon Backup and WugFresh Toolkit backup?
2. How can I avoid bricking the device?
3. Does the toolkit offers an option to unroot the device? If so, will I have to do something else instead of unrooting with the toolkit?
4. If I decided to unroot and go back to what I have right now (all the apps etc.), how would I do that (restore all the data)?
5. Is unrooting wiping the device?
6. Should I update the ROM via GOOManager directlry or should I download from GOOManager and then flash via the recovery?
7. What do you recommend - PA's built in kernel or Franco's?
8. Do I need the SuperSU app? (PA ROM)
9. From SuperSU description:
NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Click to expand...
Click to collapse
It doesn't say how to uninstall it.
Thanks in advance!
[email protected] said:
Hi, planning on rooting the device and installing PA (sticking with PA's kernel). New to this area, I hope the questions are fine.
1. What's the difference between Carbon Backup and WugFresh Toolkit backup?
2. How can I avoid bricking the device?
3. Does the toolkit offers an option to unroot the device? If so, will I have to do something else instead of unrooting with the toolkit?
4. If I decided to unroot and go back to what I have right now (all the apps etc.), how would I do that (restore all the data)?
5. Is unrooting wiping the device?
6. Should I update the ROM via GOOManager directlry or should I download from GOOManager and then flash via the recovery?
7. What do you recommend - PA's built in kernel or Franco's?
8. Do I need the SuperSU app? (PA ROM)
9. From SuperSU description:
It doesn't say how to uninstall it.
Thanks in advance!
Click to expand...
Click to collapse
XDA Rule 1, use the search button and try finding the answers yourself first. This is not a covenience store where you can order what you want. Don`t want to be rude but lazyness is not apreciated around here
superSU can be set as default superuser app by converting superSU to a system file from within the app and then redownload the superSU app from Play.
Some advice: learn how to use adb instead of toolkits, look here https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNEEKsh9DfW_LuvfJlEbDsWBeAoe1Q
gee2012 said:
XDA Rule 1, use the search button and try finding the answers yourself first. This is not a covenience store where you can order what you want. Don`t want to be rude but lazyness is not apreciated around here
Click to expand...
Click to collapse
I have searched alot but couldn't find exact answers for the questions I've listed here (some of them).
[email protected] said:
Hi, planning on rooting the device and installing PA (sticking with PA's kernel). New to this area, I hope the questions are fine.
1. What's the difference between Carbon Backup and WugFresh Toolkit backup?
2. How can I avoid bricking the device?
3. Does the toolkit offers an option to unroot the device? If so, will I have to do something else instead of unrooting with the toolkit?
4. If I decided to unroot and go back to what I have right now (all the apps etc.), how would I do that (restore all the data)?
5. Is unrooting wiping the device?
6. Should I update the ROM via GOOManager directlry or should I download from GOOManager and then flash via the recovery?
7. What do you recommend - PA's built in kernel or Franco's?
8. Do I need the SuperSU app? (PA ROM)
9. From SuperSU description:
It doesn't say how to uninstall it.
Thanks in advance!
Click to expand...
Click to collapse
1. Pretty much all backup apps are the same, just with some different features, carbon lets you back up to the cloud I know, Titanium backup is also a pretty good/common one. Main difference is just the features, check the play store descriptions for specifics.
2. With a nexus device you don't really have to worry about bricking, you can always just use google's factory images off of their site to restore your phone from the bootloader/fastboot. It is really easy to do and plenty of guides available on it.
3. I don't know for sure if the toolkit will do it or not, but unrooting is pretty easy, just go into the system/apps portion of the internal storage and delete the superuser app that you have.
4. Just restore all your apps with the backup app that you picked, then once they are restored, delete the superuser app like i explained in the last one.
5. Nope, unrooting just removes the superuser app, nothing else
6. Doesn't matter, I use the same rom and I download on my computer then manually flash it in recovery mode, because the rom downloads faster that way. Remember to flash the gapps every time after you install the rom though!
7. I use PA's kernal, I have heard some people get better battery with Franco, but I can get like 2 and a half to 3 hours everyday on the PA one, and the color settings on the PA one look really nice. It is really a personal preference though, try both
8. Nope, it comes installed with PA already, don't have to worry about that.
9. If you go back to stock, you have to wipe the data before you install the stock aosp rom anyways, which will delete the superuser app for you. but just fyi, PA uses superuser, not superSU, it is newer and works a little bit better
Hope this helped, I love everything about PA! you won't be disappointed!
Happy flashing
klinkdawg24 said:
1. Pretty much all backup apps are the same, just with some different features, carbon lets you back up to the cloud I know, Titanium backup is also a pretty good/common one. Main difference is just the features, check the play store descriptions for specifics.
2. With a nexus device you don't really have to worry about bricking, you can always just use google's factory images off of their site to restore your phone from the bootloader/fastboot. It is really easy to do and plenty of guides available on it.
3. I don't know for sure if the toolkit will do it or not, but unrooting is pretty easy, just go into the system/apps portion of the internal storage and delete the superuser app that you have.
4. Just restore all your apps with the backup app that you picked, then once they are restored, delete the superuser app like i explained in the last one.
5. Nope, unrooting just removes the superuser app, nothing else
6. Doesn't matter, I use the same rom and I download on my computer then manually flash it in recovery mode, because the rom downloads faster that way. Remember to flash the gapps every time after you install the rom though!
7. I use PA's kernal, I have heard some people get better battery with Franco, but I can get like 2 and a half to 3 hours everyday on the PA one, and the color settings on the PA one look really nice. It is really a personal preference though, try both
8. Nope, it comes installed with PA already, don't have to worry about that.
9. If you go back to stock, you have to wipe the data before you install the stock aosp rom anyways, which will delete the superuser app for you. but just fyi, PA uses superuser, not superSU, it is newer and works a little bit better
Hope this helped, I love everything about PA! you won't be disappointed!
Happy flashing
Click to expand...
Click to collapse
I appreciate your answer, thank you very much!
So now all I worry about is the backup - There are three ways I know:
1. Carbon Backup
2. Toolkit backup
3. Drag and drop from the SDCard
I just want the apps + app settings to be the same after unlocking the bootloader. Which option is the best?
Thanks again!
BTW
About question 4, the locking of the bootloader wipes the device, so how can I unroot and keep the apps? Also, should I do a Nandroid backup before or after I restore all the apps from Carbon?
[email protected] said:
I appreciate your answer, thank you very much!
So now all I worry about is the backup - There are three ways I know:
1. Carbon Backup
2. Toolkit backup
3. Drag and drop from the SDCard
I just want the apps + app settings to be the same after unlocking the bootloader. Which option is the best?
Thanks again!
Click to expand...
Click to collapse
It would be appreciative and descent to hit the thanks button of klinkdawg24 after answering your questions That`s how we do things around here.
You are absolutely right. Not used to a Thanks button, usually I just say thanks
[email protected] said:
I appreciate your answer, thank you very much!
So now all I worry about is the backup - There are three ways I know:
1. Carbon Backup
2. Toolkit backup
3. Drag and drop from the SDCard
I just want the apps + app settings to be the same after unlocking the bootloader. Which option is the best?
Thanks again!
BTW
About question 4, the locking of the bootloader wipes the device, so how can I unroot and keep the apps? Also, should I do a Nandroid backup before or after I restore all the apps from Carbon?
Click to expand...
Click to collapse
Use carbon backup or titanium backup I would say, I have never used carbon, but there should be a batch option to backup all your apps at once. Also, since the unlocking or locking of the bootloader will wipe all your data, including what is on the phone, make sure you copy the backup to your computer or something after you have completed it.
What I do for nandroid is just to run it before i flash a new rom, that way i always have a restore point that i can get back to.
So I:
1.) reboot to recovery, preform nandroid
2.) factory reset
3.) flash PA and gapps
then after you boot into PA, you can restore your apps and data, then if you wish, you can do another nandroid, but I wouldn't worry about it at that point, just do it before you flash a new rom or update if you would like. That way your nandroid will have all your current app data, not the app data from when you started using the rom. That just works better for me, but again, it is completely up to you
So couple of things I still do not understand:
1. You mean I should do a nandroid backup before I restore all the apps? (right after the root)
2. Right now my bootloader is locked. How can I backup my apps + app's settings so I will recover them after unlocking the bootloader?
3. After I make a nandroid backup, can I just move the whole backup to the computer and when I need it I return it to the SD Card?
Help please? These are the only question I need answer for before I root. I just don't want to be stuck without a backup.
[email protected] said:
So couple of things I still do not understand:
1. You mean I should do a nandroid backup before I restore all the apps? (right after the root)
2. Right now my bootloader is locked. How can I backup my apps + app's settings so I will recover them after unlocking the bootloader?
3. After I make a nandroid backup, can I just move the whole backup to the computer and when I need it I return it to the SD Card?
Click to expand...
Click to collapse
1. Make a backup after you rooted and installed the apps and data (passwords etc)
2. Use Helium Backup or Appmonster (Pro) or adb command: adb backup –apk –noshared –nosystem –f /backup/mybackup.ab
3. Yes.
I wouldn't use a toolkit (apart from backing up) especially if it's your first time rooting, it's always best to do it manually in my opinion; it may take a little longer, but then you'll know the ins and outs of what really happens and it will help if anything goes wrong.
Sent from my CM10.1 Nexus 4
gee2012 said:
1. Make a backup after you rooted and installed the apps and data (passwords etc)
2. Use Helium Backup or Appmonster (Pro) or adb command: adb backup –apk –noshared –nosystem –f /backup/mybackup.ab
3. Yes.
Click to expand...
Click to collapse
1. But then I will have to install all the apps after the root, make a nandroid backup and then factory reset again to install PA rom. Shouldn't I just make a nandroid backup right after I root with no apps and stuff?
2. With adb backup, is it safe to restore to a different ROM than I used when I took the backup?
EDIT:
For some reason, I backed up with "adb backup" and the backup's size is 500MB. When I backed up with Carbon (Helium), I got 40MB. I think I'll unlock bootloader + root, then restore the adb backup, then backup with Titanium and then flash PA rom. Is that the right process?
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
vagos696 said:
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
Click to expand...
Click to collapse
I don't trust TiBU. its a real mess for me. I for one backup my ANDROID folder, and flash all apps through recovery. and then copy back the Android folder on SDCARD.
How did you root your 4.3 image? Many custom kernels break root on 4.3. Try re-flashing SuperSU or re-flash ROM and stick to the stock kernel.
via Nexus Toolkit. I'm still rooted even after applied Franco, but I'll revert back to stock kernel just to check your possibility.
Even the saved TiBU apk's are not getting installed.
How can I re-install the broken apps which were affected from TiBU? As I mentioned even fresh installation from the play store is not processed.
I was hoping to avoid re-flashing and re-rooting from scratch.
Nope even with stock kernel I face the same problems. Any suggestions?
I guess there's something wrong with your /data partition. I'd either start over with flashing the factory image or at least format /data (not wipe, really format). Don't forget to backup your internal sdcard content first, it will be deleted with both methods.
Also I'd recommend not using a toolkit for flashing the factory image and rooting. It's easy enough using fastboot and a custom recovery. This way you'll be on the safe side, not missing any errors etc.
Make sure your TiBU directory is set to storage/emulated/legacy/TitaniumBackup, not storage/emulated/0/TitaniumBackup.
It worked for me, anyway. Well, after having to perform a factory reset, as it screwed up the UUIDs, that is
Thanks for the suggestion. You were right my path was storage/emulated/0/TitaniumBackup.
I revert it to the suggested one but I have the same issue.
Factory reset, start from scratch, initial path storage/emulated/legacy/TitaniumBackup
The same problem which also end up destroying the fresh apk as well.
Hopeless
Tell us exactly what you're doing. Which ROM / image, software, versions, procedure, all the details. Maybe something other well ring a bell.
As already quoted
1. Before updating to 4.3, I updated TiBU to the latest version and kept backup of the apps+data
2. Clean flash of stock 4.3 ROM (JWR66Y) via Nexus Toolkit
3. Root (Busybox, SU etc)
4. Flashing Franco Kernel r178
5. Installation of TiBU
6. Try to restore - PROBLEM
Plan B:
1. Factory Data Reset
2. BusyBox gone but still have root access
3. Stock ROM - Stock Kernel - Rooted
4. Install TiBU
5. Restoring - PROBLEM
Description of the PROBLEM:
I cannot restore apk's is getting into a loop and never ends.
I can restore data to an installed apk, but then the app crashes
I cannot re-install the (restored) app via playstore, I get "unknown error code during installation -24-"
Current situation
1. Factory Data Reset again
2. Franco r178
3. No restores via TiBU
Don't shoot me, but it still sounds like the TiBu 4.3 ROM backup folder path problem. Here's what I do and what works for me:
1. Open TiBu
2. Click on "Menu"
3. Click on "Preferences"
4. Click on "Backup folder location"
5. Click on "DETECT!"
6. Click on "Whole device"
7. Choose "/storage/emulated/legacy/TitaniumBackup"
8. Click on "Use the current folder"
9. TiBu will now ask if it should move the other backups to the new folder, say no.
10. Exit the preferences with the back key
11. TiBu will now reload with the new preferences
Now restoring should work if the path is the problem.
About loosing root with a custom kernel on 4.3 ROMs:
If you lose root by flashing a custom kernel it may still seem like root is active, i.e. the root frontend app will still be there and ask for root permissions etc. Try the following to ensure that TiBu is running with full root privileges: Uninstall some unimportant system application (some Gapp for example, like Google Currents - backup first if you need it). If uninstalling gets cancelled with a message like "Can't find the apk file", it's likely that root doesn't work properly.
Come on man, I hate to give up
Thanks for the inspiration but unfortunately:
1. I can unistall, backup and restore properly Google Currents (hence proper root)
2. Back up folder was set properly also by verifying your steps (2-10)
And again if I try to restore an old app (not the data) it gets to the familiar loop.
Ok. I'd now flash the full factory image, thus resetting every partition (backup internal sdcard first). Please try without a toolkit to be safe. You need the drivers installed (your toolkit should already have taken care of that) and have adb and fastboot ready. There are batch/shell scripts included in the factory image which invoke the fastboot commands in one step.
Next flash a custom recovery with fastboot and use it to flash SuperSU for root access.
Refrain from flashing a custom kernel now and try if you can successfully restore with TiBu at this point.
If you can, the problem was either one of your partitions/filesystems f_cked up or the toolkit doing something wrong.
My phone got stuck in a bootloop since yesterday and now I am trying to get out any data/backup I can. After dozens of tries (most of the times it just reboots when I choose to get into recovery from the bootloader), I managed to get to recovery and get the whole `sdcard` contents with `adb pull`. I am now trying to get backups of some, if not all, apps.
I tried `adb backup -all -apk -f -backup.ab` but since my phone has the `TWRP` recovery, this doesn't work.
1. Is it ok if I just get a backup of the `data` partition? Will I able to restore apps from this partition to a new phone (possibly not a Nexus6P). Do encryption/lock settings have a role in this?
2. Is it a good idea to try and flash a factory image, so that I have the factory recovery, and try running the same `adb` command? I am not even sure I will be able to get into recovery again after that.
I am really afraid to anything at this point, before I know that there is a good chance I'll have any success. I can get to the bootloader easily, but trying to get into recovery fails most of the times.
Any help guys?
lalibi said:
My phone got stuck in a bootloop since yesterday and now I am trying to get out any data/backup I can. After dozens of tries (most of the times it just reboots when I choose to get into recovery from the bootloader), I managed to get to recovery and get the whole `sdcard` contents with `adb pull`. I am now trying to get backups of some, if not all, apps.
I tried `adb backup -all -apk -f -backup.ab` but since my phone has the `TWRP` recovery, this doesn't work.
1. Is it ok if I just get a backup of the `data` partition? Will I able to restore apps from this partition to a new phone (possibly not a Nexus6P). Do encryption/lock settings have a role in this?
2. Is it a good idea to try and flash a factory image, so that I have the factory recovery, and try running the same `adb` command? I am not even sure I will be able to get into recovery again after that.
I am really afraid to anything at this point, before I know that there is a good chance I'll have any success. I can get to the bootloader easily, but trying to get into recovery fails most of the times.
Any help guys?
Click to expand...
Click to collapse
Since you have TWRP, why not just use the built in MTP to navigate your Android file system on your PC and drag off the files you need? TWRP backups can be found in the TWRP folder assuming you have made one. You wont' be able to use this or data from userdata on a different phone.
I did get all contents of the `sdcard` out. I'm just trying to see if I can get app data as well.
How can I run a full backup of my phone without TWRP? I hate setting up everything after I try a new rom and go back. I've tried every TWRP and I can't restore backups. Is there like a fastboot command or adb command to backup everything?
nima0003 said:
How can I run a full backup of my phone without TWRP? I hate setting up everything after I try a new rom and go back. I've tried every TWRP and I can't restore backups. Is there like a fastboot command or adb command to backup everything?
Click to expand...
Click to collapse
I use Titanium Backup.
nima0003 said:
How can I run a full backup of my phone without TWRP? I hate setting up everything after I try a new rom and go back. I've tried every TWRP and I can't restore backups. Is there like a fastboot command or adb command to backup everything?
Click to expand...
Click to collapse
when restoring, are you using _image options? also, are you restoring everything except data and then restoring data? that was the caveat i noticed users reporting in TWRP threads. some still couldn't, but if not, try it like that.
kitcostantino said:
when restoring, are you using _image options? also, are you restoring everything except data and then restoring data? that was the caveat i noticed users reporting in TWRP threads. some still couldn't, but if not, try it like that.
Click to expand...
Click to collapse
I tried but that doesn't work either, I get error 255
nima0003 said:
I tried but that doesn't work either, I get error 255
Click to expand...
Click to collapse
Did you followed this? It's easy to forget....
"Warning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None." https://forum.xda-developers.com/showpost.php?p=77982197&postcount=7
F5:ed said:
Did you followed this? It's easy to forget....
"Warning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None." https://forum.xda-developers.com/showpost.php?p=77982197&postcount=7
Click to expand...
Click to collapse
No I didn't, I'll try that next time.
nima0003 said:
How can I run a full backup of my phone without TWRP? I hate setting up everything after I try a new rom and go back. I've tried every TWRP and I can't restore backups. Is there like a fastboot command or adb command to backup everything?
Click to expand...
Click to collapse
Try migrate app from playstore, magisk needed.
I am trying to backup with adb (not rooted), but I never get the prompt on my phone. The backup file is created with zero bytes, and nothing more happens.
Any suggestions please? USB debugging is turned on, and USB mode is file transfer.