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
Related
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!
I just bought a Verizon Galaxy Tab and and did the permanent rooted with z4root, the root seemed to take fine, I have superuser access, other root required apps like adfree work, etc, however when I try to backup the ROM with ROM Manager when it reboots into recover mode a bunch of options including backup are missing, the only options I have are
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
what it looks like is it's rebooting into the standard android/samsung recovery not the clockwork mod one, does anyone know why it would be doing this? I never had any problems like this when I backed up my EVO.
anyone know who to do it???
Hi there,
I've been using Samsung's XWJVI firmware (2.3.3) for a while and decided to have a look at custom ROMs. So I created a backup using CWM Recovery, flashed the latest Darkys ROM, played around with it and found that I'd want my old system back. After I rebooted the phone into recovery mode and chose to restore my backup, I did not exactly get what I expected.
What CWM successfully recovered:
- my wallpaper
- data such as photos taken by the camera
What CWM apparently forgot to restore:
- my launcher
- my apps
- my google account
- my settings
In other words, the current state of my system is close to factory defaults with slight traces of customization. What am I missing? Is my backup corrupt or am I restoring it incorrectly?
Can anyone please help?
I just installed the Ultimate JB ROM XXLSA 4.1.2 v5 upgrade on top of v4.
All went perfectly well and I was able to enter all my setup and account details after the initial boot of the phone.
When I tried to re-install apps from Google Play, however, (Titanium Backup Pro, Quickboot) the phone hangs at the Samsung Splash screen and won't go any further. I re-tried the procedure 3 times but each time the result is the same.
Can anyone tell me what the problem could be? I followed all the instructions about wiping etc. correctly.
Trevor
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Kangal said:
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Click to expand...
Click to collapse
Mystery solved - well partly. Turns out Titanium Backup Pro was causing it on my phone for some reason. This was naturally the first app I wanted to install so I could restore apps one by one from the Nandroid backup. I tried Quickboot too which also caused the same problem so because TB and then QB did the same thing I assumed every app was going to cause trouble. Shouldn't jump to conclusions, I know.
I have JB Ultimate XXSLA v5 installed and am restoring my apps one at a time from Google Play and making new Nandroid backups as I go along.
And now I just tried installing TB free version - the phone boots normally! Then I installed the TB Pro version and again the phone boots normally. When TB was the first app I installed after the ROM upgrade it hung up the phone every time on 6 attempts. I'll try re-installing Quickboot now and see what happens. Conclusion: I must have been doing something in the wrong sequence but can's see what.
Many thanks for your help.
Trevor
sacentre said:
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Click to expand...
Click to collapse
I would like to keep everything else the same on my phone.
- I don't know if that means I'll have to backup/reinstall everything, if that happens automatically, or what.
- I have the following installed: TWRP 3.4.0.0, Titanium Backup Pro, Frija, Odin, ADB (?)
I currently have "ALEXNDR.N960FXXU6FTJ5" that I got here (based on Android 10)
I think it was from this thread: https://forum.xda-developers.com/t/...ase-v7-4-dex-gear-encryption-support.3847061/
If I want to follow those instructions, should I:
1) do a complete TWRP backup *first*?
2) follow the instructions to update the ROM
3) then restore from Titanium Backup?
As I understand it, the TWRP backup is *ONLY* if I want to restore the entire "disk image" and revert back to the ROM I have now, right?
You can use TWRP restore only if you mess something while flashing kernels, magisk modules, Xposed modules, etc .. it is also useful in your first OEM unlock to preserve vendor and ODM images so that you won't have to flash stock ROM again if something go wrong.
If you are asking about restoring apps, SMS and call logs, I highly recommend swift backup. Not for settings though. Personally, I stopped using titanium backup years ago since it is deprecated and last update was in 2019.