Database Develop

[Q] Rooting/ CM6 flash last check

As rooting has become so easy these days I am considering to try custom roms (as many hv done lately). I hv read alot since the root with unlocking the bootloader method came out. I am still on stock FRF91 and I'd like to keep my apps and data intact. CM6-RC3 has just released and I m so tempted to try!
Here is the proposed routine:
"Originally Posted by cicrockets"
0. Download the CM6-RC3 ROM with the gapps and put them on SD Card.
1. Plug in the power cable and root using the 1-click root.
2. Back up apps and data with Titanium Backup / MyBackupPro (which is better?)
3. Search for ROM Manager on Market and Install
4. Click the "Flash ClockworkMod Recovery" and wait until the progress bar is finished.
5. Reboot and do a Nandroid backup.
6. Open ROM Manager and "Install ROM from SD Card".
7. Add Zip:
i) update-cm-6.0.0-N1-RC3-signed.zip
ii) gapps-hdpi-20100814-signed.zip
8. When it prompts, choose to backup before flashing and give the backup a name like "Stock N1 Rooted". Also choose to clear data and dalvik-cache.
9. Wait. It'll reboot and go into the clockwork recovery and automatically queue and flash the two zips. Keep waiting until it reboots again.
At this point the phone should hv booted into CM6. Should I do the restore from the backup apps immediately? Or should I wait for 10-15min market sync?
My major concern will be the data. Is there any problem with the above routine? Please bear with me

Technically that is the way to do it. But some people say that they get issues when restoring titanium backups for certain apps and data. So keep that in mind.

Yeah I read about that too. They said it can be fixed by doing an advanced restore, right? Will u recommend MyBackUpPro instead?
Thanks!

[Q] P7-L00 Backup Issues

Hi all, I thought I understood rooting etc. when had my Samsung S5, HTC Desire etc. but a bit stumped here.
I have a rooted (rootgenius) Ascend P7 (Kernel - 3.0.8-00485-ge6e6a9b, EMUI 3.0) that I am happy with. Looking to use Xposed Installer to make some tweaks but cannot seem to backup beforehand...
I've backed up all apps in Titanium Backup. When I go to reboot into recovery (ROM manager) I get the EMUI screen with 3 options (Reboot System Now, Wipe data/Factory Reset, Wipe Cache Partition). ROM manager also allows me to backup, and says that there is a current backup (sdcard/TWRP/backup) but this is blank in a file explorer and when I click on it on the phone, it takes me to the same EMUI screen.
How do I install CWM or TWRP so I see them in recovery and can backup the system in a way that is restorable (guessing that Titanium Backup isn't that useful if stuck in bootloop for example).
Thanks

Any ideas on this as I would love to start using XposedInstaller etc. but only with this backup, many thanks.

Have you tried this yet?
http://forum.xda-developers.com/showthread.php?t=2793247

Does a TWRP Backup completely remove x-posed?

Hello. I have a Galaxy S7 and want to try the latest xposed-framework. I use TWRP and have backup of Boot, System, Data. Now if I change my mind, and restore backup after, will xposed-framework be completely uninstalled?
I know there is the Uninstaller, however I'm interested in keeping two backups, one with xposed installed, and one without, that's why this question is relevant to me.
Very thankful for all information considering this topic.

Teddan Fred said:
Hello. I have a Galaxy S7 and want to try the latest xposed-framework. I use TWRP and have backup of Boot, System, Data. Now if I change my mind, and restore backup after, will xposed-framework be completely uninstalled?
I know there is the Uninstaller, however I'm interested in keeping two backups, one with xposed installed, and one without, that's why this question is relevant to me.
Very thankful for all information considering this topic.
Click to expand...
Click to collapse
Please take NOTE that i am not experienced or i have installed Xposed.
Then this is from my knowledge of Backup made by TWRP (nandroid backup).
As per me Xposed is installed on System partition ie "/system".
rovo89 said:
Does Xposed get disabled if I flash a new ROM?
Yes, because the file it modifies, /system/bin/app_process, is part of every ROM and will be overwritten when you flash a ROM. However, as long as you don't wipe data, the Xposed Installer app will still be installed, so you can just click on "install/update" again in the Framework section and reboot.
Click to expand...
Click to collapse
SO
There are Two case's which you mentioned :
1)TWRP backup before Installing Xposed:
Since Xposed is not installed , Restoring this backup will not have Xposed.
hence Xposed getting Uninstalled question does not arise coz it simply does not exists in Backup.
2)TWRP backup after Installing Xposed:
Since Xposed is installed , Restoring this backup will have Xposed.
hence Xposed will not get Uninstalled , coz it's already there in Backup.
NOW if you install Xposed and then Restore backup from 1st ie "TWRP backup before Installing Xposed",
Then as I have said "Xposed getting Uninstalled question does not arise coz it simply does not exists in Backup",
Since backup will not have Xposed.
UNLESS if you use this method of Systemless(Reff), then above 2nd case FAIL
Because Xposed is not installed on System partition ie "/system".
hence I am GUESSING that Xposed will not get Uninstalled.
Note to Experienced/Experts : If I am wrong please Correct me.
Thank You for reading this
&
WelCoMe for helping You. :silly:

Full image backup without unlocking bootloader?

Hi,
Pls pardon my noob questions...
I just gotten my 3T about a week now and after spending over 3 days setting up everything from scratch (eg installing numerous apps and configuring them one by one, setup emails, sms, contacts, icons packs, settings, etc) and finally gotten the phone to a state where I am very satisfied, a question dawn on me - How can I do a full image backup so that if anything happens, I can do a full image recovery and get back the "perfect" state?
After doing so much reading, it seemed the full image backup is called a "nandroid" backup and I need to first unlock the bootloader and flash TWRP in-order to perform this backup. But my predicament is, if I proceed to unlock bootloader, then all my configurations, setups and data will be wiped. So it became a chicken and egg scenario.
And the 2nd problem is that, worst comes to worst I decide to bite the bullet and proceed with unlocking and flashing TWRP, when booting into TWRP can I select "read only" and not agree with modified system since I have no intention to root. Will this cause boot loop problem if it is "read only"?
Can "read only" state in TWRP allows me to perform nandroid backup and restoration later on?
May I skip the next step of flashing anti dm verity file / root? I don't really want to go root since I am very happy with stock OOS at the moment.
So the big question is, is there anyway out there in the universe where I can do as close as possible to a nandroid backup without going bootloader unlocking route as that is not an option for me as I can't afford to have all the data, settings and configurations wiped. I heard about Helium app which can backup app data but that's about it. Everything else has to be setup from scratch.

Zegnalabel said:
Hi,
Pls pardon my noob questions...
I just gotten my 3T about a week now and after spending over 3 days setting up everything from scratch (eg installing numerous apps and configuring them one by one, setup emails, sms, contacts, icons packs, settings, etc) and finally gotten the phone to a state where I am very satisfied, a question dawn on me - How can I do a full image backup so that if anything happens, I can do a full image recovery and get back the "perfect" state?
After doing so much reading, it seemed the full image backup is called a "nandroid" backup and I need to first unlock the bootloader and flash TWRP in-order to perform this backup. But my predicament is, if I proceed to unlock bootloader, then all my configurations, setups and data will be wiped. So it became a chicken and egg scenario.
Click to expand...
Click to collapse
Yes, a Nandroid backup is what you want, and yes, you need an unlocked bootloader for that, and yes, you need to wipe your data to do that. That's why it's highly recommended that unlocking your bootloader is the first thing you do as soon as you get your phone (though that's obviously too late for you). To help ease the pain, you can do an adb backup as described at http://forum.xda-developers.com/showthread.php?t=1678239. This will preserve most but not all of your stuff, and doesn't need an unlocked bootloader. Once you do that, you can unlock the bootloader, restore the adb backup, then take a nandroid backup.
Zegnalabel said:
And the 2nd problem is that, worst comes to worst I decide to bite the bullet and proceed with unlocking and flashing TWRP, when booting into TWRP can I select "read only" and not agree with modified system since I have no intention to root. Will this cause boot loop problem if it is "read only"?
Can "read only" state in TWRP allows me to perform nandroid backup and restoration later on?
May I skip the next step of flashing anti dm verity file / root? I don't really want to go root since I am very happy with stock OOS at the moment.
So the big question is, is there anyway out there in the universe where I can do as close as possible to a nandroid backup without going bootloader unlocking route as that is not an option for me as I can't afford to have all the data, settings and configurations wiped. I heard about Helium app which can backup app data but that's about it. Everything else has to be setup from scratch.
Click to expand...
Click to collapse
Yes, you should mount /system read-only. You don't need to root or disable dm-verity as long as you do that. (By the way, Helium is pretty much just a nice wrapper around adb backup.)

josephcsible said:
Yes, a Nandroid backup is what you want, and yes, you need an unlocked bootloader for that, and yes, you need to wipe your data to do that. That's why it's highly recommended that unlocking your bootloader is the first thing you do as soon as you get your phone (though that's obviously too late for you). To help ease the pain, you can do an adb backup as described at http://forum.xda-developers.com/showthread.php?t=1678239. This will preserve most but not all of your stuff, and doesn't need an unlocked bootloader. Once you do that, you can unlock the bootloader, restore the adb backup, then take a nandroid backup.
Click to expand...
Click to collapse
Many thanks Joseph for your advice! I really appreciate it! You're totally right, I'll do an adb backup followed by bootloader unlocking and TWRP installation. :good:
Yes, you should mount /system read-only. You don't need to root or disable dm-verity as long as you do that. (By the way, Helium is pretty much just a nice wrapper around adb backup.)
Click to expand...
Click to collapse
May I further check with you what are the limitation bring about when choosing "read only" when first enter TWRP? As in won't be able to flash ROM, flash supersu, etc thereafter?
Once again, thanks for your help, Joseph!

Zegnalabel said:
May I further check with you what are the limitation bring about when choosing "read only" when first enter TWRP? As in won't be able to flash ROM, flash supersu, etc thereafter?
Click to expand...
Click to collapse
All it means is that you won't be able to modify /system with file manager or the shell. Flashable zips almost all contain code that remounts /system read-write (as the TWRP screen warns you about). Also, you can always change your mind and make it read-write later (though the reverse is not true; once you mount it read-write, putting it back to read-only doesn't fix anything unless you reflash the ROM).

Many thanks Joseph for your sound advice.
After taking some time to read through all the links and sub-links getting to know the varied means of backups available, I have decided that my backup strategy will be as follows since non of the methods offer comprehensive backup and a mixed of the lots will be required to get as fool-proof as possible, before embarking on a data wiping journey with bootloader unlocking.
(i) I first perform a backup using google native backup and restore function under setting no matter how limited it is, to be use as a safety net.
(ii) Next, adb backup. The limitation with adb backup is that since Android 6.0, it obeys AndroidManifest.xml and will not backup data of those apps which has android:allowBackup set to false. The challenge is, I will be held in the dark which app falls into this category when performing adb backup and won't know until after I had done the actual restoration. Its like a blackbox you won't know what you gonna face until the aftermath had hit. Therefore to get around this, I'll be using Helium app (a wrapper around adb backup) instead of the actual adb backup since both methods refer to AndroidManifest.xml when deciding which app data it can or cannot backup. And Helium shows exactly which app it can backup vs that which it can't. Good info there for a start.
After installing Helium and activating it via PC client, I found out it does backup:
A) SMS and call logs
B) User dictionary
C) Accounts
D) Bunch of apps and their data
List of apps and data it can't backup:
1) Contacts
2) browser bookmarks
3) Calender
4) System settings
5) APNs
6) Homescreen shortcuts
7) Widgets
8) Alarms
9) Photos
10) Music
11) Videos
12) MMS
13) Google AUTHENTICATOR!!! - I have over 15 profiles that I'll have to re-setup one by one... what a nightmare.
14) Line
15) Whatsapp
16) wechat
17) Signal
18) Nova launcher - luckily its setting can be exported and backup via the app's functionality.
19) QQMusic - all my thousands of songs! - even if I back this up manually using ES explorer the app's internal linkage between playlist to songs will be broken. Will have to re-download all the songs to repair linkage and this means wasting another month of subscription fees for songs re-download. This is one of the most problematic app but it has DTS plagin which makes your music sound fantastic even with cheap earpiece, so I am putting up with it.
20) Skype - not much chat in there so that's fine to start over.
(iii) After backing up the limited stuff using Helium, I shall proceed to use another app to backup (1) to (12). And that app will be "MyBackup" (https://play.google.com/store/apps/details?id=com.rerware.android.MyBackup&hl=en). The app developer confirmed in its app's features that (1) to (12) are supported. Note "MyBackup" does not backup any app data at all when device is not rooted therefore step one using Helium is still necessary.
(iv) Next, to circumvent the limitation with failure to backup app & data for (13) to (20), my initial thought were to patch each app's manifest using this method (https://forum.xda-developers.com/an...g/guide-how-to-enable-adb-backup-app-t3495117). But then, as I studied further, I realized another chicken and egg scenario. That is, the decompiling, editing, recompiling and signing of the patched apk would need to take place first before using the app and not after. So in another word this method with each newly patched app will not seemlessly replace the existing app but rather the existing app will first have to be uninstall before the patched app can be installed, and that very act would mean losing existing data altogether.
To install on android the patched apk, you must first uninstall your previous version, and this is because the key used to sign the apk is different. If you try to install one app itself with a different signing key, you will get this error: [INSTALL_FAILED_ALREADY_EXISTS] [Unquote]
Given this ****ty situation, I guess I am still hesitant and not ready to move forward with bootloader unlocking. Sigh...
Click to expand...
Click to collapse

backing up a rooted phone

I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??

Eggstones said:
I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??
Click to expand...
Click to collapse
Two options:
1. Use TB to backup and restore app data and non-bundled/not split apks. Use SAI https://play.google.com/store/apps/details?id=com.aefyr.sai to backup/restore bundled/split apks.
2. Use Migrate https://forum.xda-developers.com/an...stom-rom-migration-tool-t3862763/post78060823
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Two options:
1. Use TB to backup and restore app data and non-bundled/not split apks. Use SAI https://play.google.com/store/apps/details?id=com.aefyr.sai to backup/restore bundled/split apks.
2. Use Migrate https://forum.xda-developers.com/an...stom-rom-migration-tool-t3862763/post78060823
Click to expand...
Click to collapse
I actually don't understand option one but two sounds just the ticket. Thank you.

Eggstones said:
I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??
Click to expand...
Click to collapse
If you have TWRP, then indeed, adb backup --twrp data should be your friend.
However, extracting TWRP backups on your computer is not that trivial. To do that you need twrpabx, specifically prudy's fixed version. On a Linux computer, it is quick and easy to compile. I haven't tried on Windows.
Else, TWRP backups can only be restored on the same phone (or maybe also on another phone of the same model)

yahya69 said:
If you have TWRP, then indeed, adb backup --twrp data should be your friend.
However, extracting TWRP backups on your computer is not that trivial. To do that you need twrpabx, specifically prudy's fixed version. On a Linux computer, it is quick and easy to compile. I haven't tried on Windows.
Else, TWRP backups can only be restored on the same phone (or maybe also on another phone of the same model)
Click to expand...
Click to collapse
That should be then fine. I just want to try a thing on OOS so no switching of phones intended.
ADB backup I don't think restored the apps data when I tried it which was the main reason for doing the backup

Eggstones said:
That should be then fine. I just want to try a thing on OOS so no switching of phones intended.
ADB backup I don't think restored the apps data when I tried it which was the main reason for doing the backup
Click to expand...
Click to collapse
When you do adb backup --trwp you can add which partitions you want to have backup up:
adb backup --trwp data system boot recovery (haven't checked the names, but data and system should be the most important ones)
Just be mindful that when you do an adb backup --twrp, the backup does not include Internal Files, so make sure to back them up separately or not to wipe them in the first place. I would recommend that after backing up your precious data, you go to "advanced wipe" and there select system, data, cache and dalvik cache. After that, happy flashing..

yahya69 said:
When you do adb backup --trwp you can add which partitions you want to have backup up:
adb backup --trwp data system boot recovery (haven't checked the names, but data and system should be the most important ones)
Just be mindful that when you do an adb backup --twrp, the backup does not include Internal Files, so make sure to back them up separately or not to wipe them in the first place. I would recommend that after backing up your precious data, you go to "advanced wipe" and there select system, data, cache and dalvik cache. After that, happy flashing..
Click to expand...
Click to collapse
I'm doing this with very basic understanding of what I'm doing/being recommended to do. Is adb backup --twrp a command or twice different things as in 'adb backup' to computer and twrp is done on the phone?
My plan is to copy the important data like audio files and photos to my laptop, then use use migrate to make a copy plus twrp backup. I should be fine after that I think.
I'm just hoping my root and magisk doesn't go when I reinstal OOS 9.0.6 as I want to try to edit my system to see if I can force vowife to work.

Eggstones said:
I'm doing this with very basic understanding of what I'm doing/being recommended to do. Is adb backup --twrp a command or twice different things as in 'adb backup' to computer and twrp is done on the phone?
Click to expand...
Click to collapse
That would be a command you have to run in a command line window on your computer. Again, after the --twrp parameter, you can pass the names of the partitions you want to have backed up, which would probably be data, system, recovery and boot.
First, of course, you have to install adb, if you haven't already. But if that's too complicated, it might be easier to make a full backup in TWRP and then copy it over to your computer. adb backup --twrp basically saves a step and you don't have to have sufficient space on your phone for a full backup
My plan is to copy the important data like audio files and photos to my laptop, then use use migrate to make a copy plus twrp backup. I should be fine after that I think.
Click to expand...
Click to collapse
That's always a good idea, even though wiping data in TWRP should not touch your internal files.
I'm just hoping my root and magisk doesn't go when I reinstal OOS 9.0.6 as I want to try to edit my system to see if I can force vowife to work.
Click to expand...
Click to collapse
I don't know, I never used it. I'm happy with LineageOS. I guess you can re-flash Magisk trough twrp and then in your running system, you can re-install the MagiskManager apk. But I haven't tried it.