Develop Bugs

Dual boot but keeping old data?

Hi xda,
I recently was looking into dual booting my Desire HD with Vodafone, I'm currently on Sense 3.0 and on Android 2.3.5
I'm looking to dual boot in order to get a newer version of Android, I've seen http://forum.xda-developers.com/showthread.php?t=1173309 but was wandering how I could dual boot whilst keeping the files on my current ROM on the same memory stick as the files for the other ROM

You could try bootmanager to install some newer roms and try them out, this way you wouldn't lose any of your original files.
https://market.android.com/details?id=com.drx2.bootmanager&hl=en
Always do a nandroid backup first and click 'setup phone' in the actual program before attempting to try a new rom.. that way if anything goes wrong you can just boot into recovery > install zip from sdcard > bootmanger/phoneRom/update.zip and you will boot back in to your normal phone.
Also just switching between nandriod backups works well for me. Do a nandroid, follow instructions for new rom (wipe/install/etc.), when you are done just restore the nandroid backup and all your files/apps/settings will be restored.

[Q] TWRP help

The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.

Not much help here, and at the risk of sounding like a Negative Nelly, I gave up on image-based backups several devices ago. The only device that I could get reliable nandroids was my HTC EVO 4G running AmonRA recovery. Since then, I've owned/rooted 4 or 5 other Android devices, and every single one of them have been completely unreliable with nandroid restores to the point that I just gave up, use Titanium Backup, and then just flash the ROM again. That's been with CWM and TWRP, all versions (and I've probably tried them all) on all of my devices.
I would love it if someone could enlighten the both of us on how to be successful with nandroid backups/restores. Again, sorry I'm not of much help, but consider me a confirmation of what you're encountering (a "yeah, what he said").

dante32278 said:
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Click to expand...
Click to collapse
What I have found out the hard way is that every device is different. Some prefer CWM Recovery, some TWRP Recovery. If TWRP is not working for you, try CWM. A stable Custom Recovery is a must have.
TEAM MiK
MikROMs Since 3/13/11

[Q] Need to recover file from nandroid backup?!

Hi all,
I need to recover some information from my phone from before I flashed a new ROM, and wondering what's the easiest way about it based on the scenario given below;
I was running a rooted stock ROM (LB) with TWRP. I used titanium to batch backup my apps ( but seem to have overlooked my notepad app which had info in it that I now need.)
I installed resurrection remix which comes with CWM so can't just do a new nandroid, then restore the old one to get the info, then re-restore the newer backup.
Is there a way to extract the info direct from my twrp backup on my SD/ laptop or do I need to/is it possible to flash TWRP to replace CWM and keep the rest of the ROM as-is?
TIA

If you are just recovering a file, and not restoring the backup itself, try using nandroid manager. I can extract a file from my nandroid backup (created by cwm). I never tried it with twrp nandroid backup though.

Other option is to try to flash the Dual Recovery on your phone.
Then you have TWRP and CWM on your phone.
-> http://forum.xda-developers.com/showthread.php?t=2261606

Is there a way to Backup Stock Boot, Recovery and ROM without custom recovery?

Hey guys. It's been a while since the HTC 10 has been out and just throwing the question out there if anyone has figured out a way to make a backup of the stock Boot, Recovery, and System without flashing a custom recovery first ?
The reason:
I originally rooted my phone but couldn't get any of the OTA updates. Upgraded stock recoveries weren't available at the time and there were no RUU files for my carrier either. Eventually some of the upgraded stock recoveries became available but now we are on version 1.95.710.3 and again, no stock recovery is available for this version.
I want to be able to make a full backup (without flashing a custom recovery) so that I can flash TWRP to Boot, make a TWRP backup of Recovery and Rom, then do a restore from the original backup, flash TWRP to recovery and backup Boot as well. Then merge the 2 to make a full TWRP backup file to upload and post up on these forums for people with the same CID.
So, has anyone figured out a way to make a full backup without altering any of the boot, recovery or system partitions ?

What TWRP are people using for curtana?

Hi all, I'm currently running miui EU rom 11.0.11 with bootloader unlocked and TWRP installed. However there are so many different twrp recoveries available all with different things working....
So far I've only flashed one rom since I've got the phone but with all these amazing looking custom ROMs around, I'd like to try out a few but it seems backup and restore is currently not possible.
TLDR: anyone know of a TWRP with working backup for Xiaomi redmi note 9s CURTANA?
Cheers

1qazwsx4 said:
Hi all, I'm currently running miui EU rom 11.0.11 with bootloader unlocked and TWRP installed. However there are so many different twrp recoveries available all with different things working....
So far I've only flashed one rom since I've got the phone but with all these amazing looking custom ROMs around, I'd like to try out a few but it seems backup and restore is currently not possible.
TLDR: anyone know of a TWRP with working backup for Xiaomi redmi note 9s CURTANA?
Cheers
Click to expand...
Click to collapse
You should use the latest recovery version available, I think now is the OrangeFox recovery, it's the unified (miatoll) version. To can make backup, the recovery need to able to handle the encryption installed by ROM. To restore the backup... another challenge. I using only data backup and when want to restore, I wipe data, flash the rom, wait for first boot (set same pin code as used in backup), than restore the data in recovery. In case of unlucky situation (encryption difference between "restored" and previous rom, the rom stuck at first boot and need to format data partition (will delete internal storage too!!).

I use ofox recovery, having stock rom in an sd card and migrate backup I just flash new rom and when I want to come back, I flash stock and restore migrate. Nandroid backups are a bit risky I think.