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
Related
Hi,
I have Note 4 DE that I've installed custom recovery (TWRP) and then flashed a SU.zip. Everything went smooth so I started installed my apps.
I also created a backup from TWRP (pre- and after root) and also full partitions backup using EFS Professional as described in this post so I should also have a phone-specific aboot partition backed up.
Today I booted up into recovery to show friend of myne how it looks like, then rebooted the phone and now it is stuck on Verizon red logo screen with slow blinking blue light. My attempt to hook up the cable and fire up EFS Pro ended up with error message saying that I do not have permanent root.
What should I do now? If there is no way to fix this and keep all installed apps, Is there a way to restore the phone to factory (while still keepping unlocked bootloader)?
Thank you in advance.
inseek said:
Hi,
I have Note 4 DE that I've installed custom recovery (TWRP) and then flashed a SU.zip. Everything went smooth so I started installed my apps.
I also created a backup from TWRP (pre- and after root) and also full partitions backup using EFS Professional as described in this post so I should also have a phone-specific aboot partition backed up.
Today I booted up into recovery to show friend of myne how it looks like, then rebooted the phone and now it is stuck on Verizon red logo screen with slow blinking blue light. My attempt to hook up the cable and fire up EFS Pro ended up with error message saying that I do not have permanent root.
What should I do now? If there is no way to fix this and keep all installed apps, Is there a way to restore the phone to factory (while still keepping unlocked bootloader)?
Thank you in advance.
Click to expand...
Click to collapse
Power your phone off. Pull the battery. Put the battery back in and boot into recovery (volume up, home and power). Wipe cache and delvek. While in TWRP recovery select boot system.
jpcalhoun said:
Power your phone off. Pull the battery. Put the battery back in and boot into recovery (volume up, home and power). Wipe cache and delvek. While in TWRP recovery select boot system.
Click to expand...
Click to collapse
Still on VZW red screen after booting up into recovery, selecting "Wipe", then "Advanced Wipe", checkmarking Dalvik Cache & Cache, wiping them out; and then going to "Reboot" -> System. ..
inseek said:
Still on VZW red screen after booting up into recovery, selecting "Wipe", then "Advanced Wipe", checkmarking Dalvik Cache & Cache, wiping them out; and then going to "Reboot" -> System. ..
Click to expand...
Click to collapse
Hmmm, Ok. Don't worry about your bootloader it is alright, not locked. I recommend you restore your backup, either a rooted backup or a stock backup that you made right after you installed TWRP. This time wipe cache, system and delvek. I'm trying to keep you have having to wipe data, but if this doesn't work then you'll need to do a complete wipe and factory reset and then restore your backup. You may loose root, if so then after restoring your backup flash the SuperSU.zip again to regain root.
jpcalhoun said:
Hmmm, Ok. Don't worry about your bootloader it is alright, not locked. I recommend you restore your backup, either a rooted backup or a stock backup that you made right after you installed TWRP. This time wipe cache, system and delvek. I'm trying to keep you have having to wipe data, but if this doesn't work then you'll need to do a complete wipe and factory reset and then restore your backup. You may loose root, if so then after restoring your backup flash the SuperSU.zip again to regain root.
Click to expand...
Click to collapse
OK, once I wipe Delvik, Chache & System, then I have to do restore from a TWRP backup I did after flashing custom recovery, right?
I have these in the list:
Boot
Recovery
System
Data
Cache
EFS
Modem
TWRP gives me a list of partitions above, which ones should I restore? "System" is probably the one since I've wiped it up already, do I need anything else?
Thanks
inseek said:
OK, once I wipe Delvik, Chache & System, then I have to do restore from a TWRP backup I did after flashing custom recovery, right?
I have these in the list:
Boot
Recovery
System
Data
Cache
EFS
Modem
TWRP gives me a list of partitions above, which ones should I restore? "System" is probably the one since I've wiped it up already, do I need anything else?
Thanks
Click to expand...
Click to collapse
Yes, select restore and then select the backup you made. The backup will contain whatever partitions you selected when you made the backup (the partitions you've mentioned above). You won't be given a chance to select the partitions once you enter restore, only the backup file name.
jpcalhoun said:
Yes, select restore and then select the backup you made. The backup will contain whatever partitions you selected when you made the backup (the partitions you've mentioned above). You won't be given a chance to select the partitions once you enter restore, only the backup file name.
Click to expand...
Click to collapse
It actually gives me an option to deselect any of partitions in the list. Which one(s) should I leave selected for restore?
inseek said:
It actually gives me an option to deselect any of partitions in the list. Which one(s) should I leave selected for restore?
Click to expand...
Click to collapse
Ok, well it's been awhile since I restored anything and maybe that is a new option in the latest TWRP. Anyway, do not deselect anything unless you are worried about your apps then in that case deselect data, then restore.
jpcalhoun said:
Ok, well it's been awhile since I restored anything and maybe that is a new option in the latest TWRP. Anyway, do not deselect anything unless you are worried about your apps then in that case deselect data, then restore.
Click to expand...
Click to collapse
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
inseek said:
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
Click to expand...
Click to collapse
The first backup you did after you installed TWRP through ODIN is a factory image with the exception of course of the factory recovery that was replaced by TWRP. Knox will always be part of any backup unless you uninstall Knox using something like Titanium Backup. So installing a custom recovery will not replace or uninstall Knox. I caution you not to flash any factory firmware. There is no factory firmware available for the Developer Edition. If you flash a factory firmware for the Note 4 you will lock your bootloader and what you have left is a very expensive Retail version of the Note 4...locked bootloader and all. The advantage of a Developer Edition is the unlocked bootloader...don't screw that up. As far as "Custom", I don't know how to get rid of that...there is a way I just don't remember how to do it.
I just ordered my Verizon Samsung galaxy note 4.. is there a root method available for the retail version ( non developer edition ) if so can someone point me in the direction .. I'm coming from unlocked rooted note 2.. I've been searching XDA and googling the topic today and all I'm finding is just developer edition is root able .. even searched you tube.. thank you
Sent from my SCH-I605 using XDA Free mobile app
athack said:
I just ordered my Verizon Samsung galaxy note 4.. is there a root method available for the retail version ( non developer edition ) if so can someone point me in the direction .. I'm coming from unlocked rooted note 2.. I've been searching XDA and googling the topic today and all I'm finding is just developer edition is root able .. even searched you tube.. thank you
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Currently no root for Retail/Consumer Edition Verizon Note 4.....
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.1.1 trltevzw
Thank you...
manbat said:
Currently no root for Retail/Consumer Edition Verizon Note 4.....
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.1.1 trltevzw
Click to expand...
Click to collapse
Sent from my SCH-I605 using XDA Free mobile app
inseek said:
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
Click to expand...
Click to collapse
inseek, let me correct a comment I made in a previous post "there is no firmware available for the Note 4". That's not entirely true. It is true that there is not a stock firmware .tar that you can ODIN that returns your phone to stock DE just like it came from Samsung. This thread http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 does provide a few stock .tar files that can safely be ODIN on the DE. These files do not provide the "safety net" that we would like in terms of a complete flashing of the DE back to stock, it only provides stock .tar files for several "pieces" of a complete stock ROM and bootloader. Read the OP and post 2 and 3 very carefully before you use any of those .tar files. There is no .tar for the DE aboot/bootloader. The only way you can have a backup of aboot/bootloader is to follow the instructions here: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
jpcalhoun said:
inseek, let me correct a comment I made in a previous post "there is no firmware available for the Note 4". That's not entirely true. It is true that there is not a stock firmware .tar that you can ODIN that returns your phone to stock DE just like it came from Samsung. This thread http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 does provide a few stock .tar files that can safely be ODIN on the DE. These files do not provide the "safety net" that we would like in terms of a complete flashing of the DE back to stock, it only provides stock .tar files for several "pieces" of a complete stock ROM and bootloader. Read the OP and post 2 and 3 very carefully before you use any of those .tar files. There is no .tar for the DE aboot/bootloader. The only way you can have a backup of aboot/bootloader is to follow the instructions here: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
Click to expand...
Click to collapse
Thank you for this update, jpcalhoun.
I've followed these threads when I first flashed TWRP so I do have a backup made via TWRP (which doesn't include aboot) plus the one created via EFS Professional. I was just wondering if there is a dump of all partitions as they are coming from the factory. I am not a specialist but I was thinking that if I have aboot (which from what I read is unique for my phone), original boot partition + the remaining partitions in my backup then I should be able to restore the phone to factory state.
Is there a way to dump all partitions from a brand new N4 DE that just came from a factory? Obviously, for EFS Professional we need custom recovery + BusyBix + root to work. TWRP is capable of backing up most partitions but not aboot/boot. The way it is now, once we flash custom recovery, there is no way back as if there is something wrong with the phone, Samsung will see that "Custom" sign on the screen and from what I've read, will just re-flash a locked bootloader prior to sending the device back to the owner. I wish I knew all this prior to ordering my N4 DE
inseek said:
Thank you for this update, jpcalhoun.
I've followed these threads when I first flashed TWRP so I do have a backup made via TWRP (which doesn't include aboot) plus the one created via EFS Professional. I was just wondering if there is a dump of all partitions as they are coming from the factory. I am not a specialist but I was thinking that if I have aboot (which from what I read is unique for my phone), original boot partition + the remaining partitions in my backup then I should be able to restore the phone to factory state.
Is there a way to dump all partitions from a brand new N4 DE that just came from a factory? Obviously, for EFS Professional we need custom recovery + BusyBix + root to work. TWRP is capable of backing up most partitions but not aboot/boot. The way it is now, once we flash custom recovery, there is no way back as if there is something wrong with the phone, Samsung will see that "Custom" sign on the screen and from what I've read, will just re-flash a locked bootloader prior to sending the device back to the owner. I wish I knew all this prior to ordering my N4 DE
Click to expand...
Click to collapse
I'm not a Linux guru or a ADB guru, but I think you can do that using command line scripts, but I can't swear to it.
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
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
mr.banana said:
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
Click to expand...
Click to collapse
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
indian84 said:
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
Click to expand...
Click to collapse
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
mr.banana said:
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
Click to expand...
Click to collapse
Backing up all the partitions was the mistake.
Getting your stuff back looks difficult.
If you flash ROM using TWRP, your media files and anything stored on your phone won't be deleted.
But all your apps and stuff will be lost.
Hi,
I recently tried a custom rom on my old phone and it worked pretty well. I liked the OS and now want to also do that on my current phone. But i do still have a few questions i hope you can help me with.
- Can i make a full backup of my phone (with app data) to my PC or maybe to my old phone? I am currently not rooted and tried helium backup but saw that sadly not all apps allow a backup.
- I know about titanium backup. Is there some way (if the above cant be done) i can root my phone without wiping the phone? So i can then use titanium backup to make a proper backup with data, then install the custom rom and after restore the apps+data.
In short: I hope i can somehow make a full backup with app data so i can install the custom rom and restore my app data again.
Looking forward to your replies.
Thanks in advance.
Nothing? No one ? =(
To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.
razr96 said:
To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.
Click to expand...
Click to collapse
Thank you for your reply and thx for the tip. Ill be doing that too from now on when i get a phone.
As long as i can make a full backup with abd (with app data), Im fine with wiping to root it. But just wanted to make sure i can get app data back after the root process.
Do you happen to have a link to a proper backup using abd guide?
Thanks
no
sm00th4f3 said:
https://forum.xda-developers.com/android/general/how-to-backup-restore-android-device-t3602583
You might wanna read this and try it
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Click to expand...
Click to collapse
Well with a few side searches i was able to open the cmd (admin), do a adb devices (which found a device) and then run the app + data command.
('adb backup -apk -shared -all -system -f C:\backup.ab')
I saw the screen on my phone to start it, which i did but it stays on Shared Storage (where before this mentioned the apk's that were being backed up). This is taking pretty long (as in hours). Is this normal or did something went wrong and is it stuck on that part?
Edit (Update): I stopped the whole thing and tried again. Now it finished in about 10 - 15 min. I did get a message "backup finished". However in the folder i gave up, there is nothing to see. folder is still empty
Edit2 (update): Found the backup.ab file. Apparently it was in a different folder i thought it would be. So if i then also make a copy of the internal storage and do this command, i should be good right? After doing that, unlock and root, i can use the 'adb restore C:\backup.ab' and have all apps + app data back as it was before the unlock/root ?
no
sm00th4f3 said:
In a sense. Yes, but you might wanna read some threads about that first.. Otherwise. No one would wanna go back after unlocking his phone. Since restoring a backup from a locked phone on an unlocked phone can cause some issues.
Click to expand...
Click to collapse
I'm not really sure what you mean though.
If i unlock my phone with my code and then make the backup with adb and just in case, a copy of my internal storage, can't i use restore on the unlocked/rooted phone to have the apps + their data back and use them again ?
no
sm00th4f3 said:
No you can't. It will brick your device. The backup can only be used when your phone is still locked. So it is basically not needed at all.
Click to expand...
Click to collapse
So you are saying that there is no possibility to backup my apps+data, unlock/root/custom rom, and then restore my apps+data at all?
That was some what the question of my first post.
So its either, fully wipe with everything lost, then root etc. etc. or just keep it the way i have it now?
no
sm00th4f3 said:
The normal procedure is as follows:
After an unlock.- your data always gets formatted. So a backup is totally wasted time.
The backup isn't wasted time - if it is done after unlocking your phone, while it still has stock rom.
In case flashing goes wrong, make the backup while not having flashed twro etc at all.
You don't have to wipe anything if you just want root, since the phone will reset-wipe your data on its very own.
Just unlock it, let it reboot, Flash twrp, install root zip file. Reboot
In case of flashing a custom rom. Flash twrp, boot to twrp. Use the Reboot menu and reboot again into recovery
Reboot->Recovery (in twrp menu).
Then Wipe-> Factory Reset
Wipe-> Advanced Wipe-> Wipe System partition only
Wipe-> Advanced wipe-> select Data partition-> Change file system to ext4
Reboot Menu in TWRP->Recovery
Wipe Dalvik and Cache
Flash Rom
Flash Gapps if not stated otherwise in Instructions of Rom Thread
Flash Magisk or SUperSu , depends if you want root or not. If you don'T want encryption on older Roms, flash one of the two.
Encryption will later on be optional through Phone Security Options.
Wipe dalvik and cache.
Reboot.
Wait a bit.
Setup phone, done.
Click to expand...
Click to collapse
Yes but as you mentioned, unlocking means a full wipe. And i cant restore apps + their data from a stock phone backup to an unlocked phone as it can cause issues.
In my very first post i asked if i could make a backup of the apps + their data to restore them after unlocking/rooting/custom rom or whatever. Simple answer then is no.
So i either have to just wipe my phone and basically start all over, only unlock/root etc etc first.
Or just keep my phone stock like how it is now and just do nothing and wait until i get a new phone (which will be in a long time still)
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.