I've made several backups of my phone on a custom ROM but whenever I restore them in TWRP, I can't boot past the red developer screen. The only backup that seems to work is the backup of Stock. TWRP seems to indicate that the /system folder could not be found. How can I restore these backups? Bootloader is unlocked with S-ON.
Apologies for my ignorance. I'm coming from a LG G3, which was much more user friendly.
Which ROM backups have you done, and which version of TWRP did you use to do them, and which one are you currently using?
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Which ROM backups have you done, and which version of TWRP did you use to do them, and which one are you currently using?
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I've done backups of LeeDroid 2.2.5 at various stages of tweaking (installing different kernels, Viper4Android, Systemless apps, etc). I'm using TWRP 3.0.2-6. I'm currently using Stock 6.0.1 since it's the only one that works at the moment but I was on LeeDroid 2.2.5 prior to this (I haven't had a chance to update to 2.6.1).
macschwag14 said:
I've done backups of LeeDroid 2.2.5 at various stages of tweaking (installing different kernels, Viper4Android, Systemless apps, etc). I'm using TWRP 3.0.2-6. I'm currently using Stock 6.0.1 since it's the only one that works at the moment but I was on LeeDroid 2.2.5 prior to this (I haven't had a chance to update to 2.6.1).
Click to expand...
Click to collapse
Sounds as if there's a problem with the boot/kernel. If it hasn't been backed up and restored properly, it won't boot as expected. The splash with red text just indicates a custom kernel that has been installed, which would be fine in case of LeeDrOiD, as it comes with tbalden's CleanSlate. Weird.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Sounds as if there's a problem with the boot/kernel. If it hasn't been backed up and restored properly, it won't boot as expected. The splash with red text just indicates a custom kernel that has been installed, which would be fine in case of LeeDrOiD, as it comes with tbalden's CleanSlate. Weird.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Any ideas for how to restore or overwrite the boot/kernel, or worse case, erase all of it and start over so that the process will work correctly in the future?
A bit more info after some experimentation.
I can fully restore and boot into Stock ROM backups only. Backups of custom ROMs (such as LeeDroid) will not boot past the silver HTC logo.
I get no errors during the restore process of a custom ROM. Going back into TWRP after the restore fails to boot shows that /system could not be mounted. If I go to the Wipe menu and select System and then Repair or Change System Type, it shows that my System size is 0. Doing the same on a Stock backup tells me that the system size is 3280, which appears to be the full system.
Related
I've tried to search but cant find a guide how to make a backup of my phone... if someone can explain or post me a link, i will be a happy man
Root phone.
Power off.
Hold volume down and power the phone on, and enter recovery mode.
Get into recovery menu (recoverywhatever.sh on *NIX or recovery-windows.bat)
Scroll to backup/restore in recovery menu.
Select backup NAND only - backing up EXT causes errors right now.
Find saved nandroid on your SD card.
Back up your apps separately using Titanium Backup or MyBackup Pro. Restore by wiping the phone, restoring the NAND, and restoring the apps via one of the above apps.
You need root for nandroid. Then it's done in recovery.
its rooted, but when i go into the recovery menu, the phone just shows a picture with a red triangle, is that correct?
No. Get back into the green recovery menu by running recovery-windows.bat or whatever method you used in step 2 of the rooting process to flash the rooted zip file.
ok thnx
one more thing, the titanium backup said i need busybox, how do i install that?... Found out myself
Did you get this problem solved as I have the same problem. I re rooted my desire and the same thing happened. The only time i can go to recovery is when I use recovery-windows.bat from the r5 tools. Any help?
i just use rom manager. choose backup in there, phone reboots itself, backs itself up and done.
used the recovery options a few times when moving from rom to rom.
ClockworkMod Recovery tool
ClockworkMod Recovery tool is really handy. Does everything itself in few clicks. I used Rom manager to backup with no problems without any previous experience.
tommo123 said:
i just use rom manager. choose backup in there, phone reboots itself, backs itself up and done.
used the recovery options a few times when moving from rom to rom.
Click to expand...
Click to collapse
installed rom manager and when choosed backup curret rom it asked for desired name then tap ok and reboots, now its freeze into htc slash screen
A2SD
Edit:
I accidentally posted on the wrong thread...
Are there still problems with this?
"backing up EXT causes errors right now."
I have one question.
If i make a nandroid backup, does it make a FULL nand backup or just certain parts of nand ?
If i for example make a backup of my leedroid rom with all my apps and settings
make wipe and then try a gingerbread rom, will restoring nandbackup actually restore the prevision rom with all the settings and apps ?
hojnikb said:
I have one question.
If i make a nandroid backup, does it make a FULL nand backup or just certain parts of nand ?
If i for example make a backup of my leedroid rom with all my apps and settings
make wipe and then try a gingerbread rom, will restoring nandbackup actually restore the prevision rom with all the settings and apps ?
Click to expand...
Click to collapse
It will restore the entire rom to the exact state as the time before the nandroid. So yes all settings and apps will be there.
Great to know..
Thx
Is it worth rooting for a backup?
Also will a new OTA just remove root if or when another OTA comes out... ?
Sent from my HTC Desire using XDA App
Lothaen said:
Is it worth rooting for a backup?
Also will a new OTA just remove root if or when another OTA comes out... ?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
No there is not a real point in rooting for the ability to back up. And despite what some say, never apply OTA updates on rooted devices! But custom versions will come out at the same time as the OTA so you don't miss out on anything.
Sent from my HTC Desire using XDA App
TheGhost1233 said:
No there is not a real point in rooting for the ability to back up. And despite what some say, never apply OTA updates
Click to expand...
Click to collapse
What's an OTA update?
Just install rom manager then click on back up . Boom you have a nandroid back up.
Sent from my HTC Desire using XDA Premium App
Ota update is
Over the air update so its basically stock updates from phone manufactures
Sent from my HTC Desire using XDA Premium App
I can't get any touchwiz based 4.3 nandroids to restore. The restore process seems normal but as soon as it boots I keep getting force closes. I think it is all Google apps that keep crashing. The only way I can make it stop is by going back into recovery and wiping data/factory reset and clearing caches. Its like setting up a new phone then. If I do an advanced restore I can restore everything but data without problems. Custom Roms backup and restore just fine. What do I need to do to make successful stock ROM backups?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Maybe it's the recovery version you're using? Not sure.
I have tried the latest versions of cwm and twrp. I have tried several versions of each since I took the ota update and rooted a couple months ago.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
You didn't provide enough detail to discern what might be going on.
I had similar issues and found that the older custom recoveries couldn't cope with SELinux or Knox properly. But there also seems to be bugs in the current recovery releases backing up boot partitions. The best result for me was to use the latest TWRP release but only backup /system and /data and that works perfectly.
The current release will not backup /boot and /cache properly and was causing my entire backup volume to fail. Just teething pains dealing with the 4.3 security measures. YMMV
.
.
Hello,
I'm about to install a custom recovery... I'm on stock 4.2.2 & rooted
Is there anyway to backup my current stock recovery??
Titanium backup
Sent from the Galaxasaurous tabalonicus Rex
Deep Nox said:
Titanium backup
Sent from the Galaxasaurous tabalonicus Rex
Click to expand...
Click to collapse
And how??
You could make a complete backup of your current system ( should always do and save to the desktop) or just the recovery. Open TB go to backup and recovery, scroll down til you find the recovery and click on it.
Sent from the Galaxasaurous tabalonicus Rex
absolutely no need
the recovery comes with official roms, are always bundled with the rom itself
samsung have made it quite funny, as every time you flash samsung's original rom
it erase everything and install it's own stuff
(which is including erasing everything in the internal memory)
if you use a custom rom, you don't ever need the old recovery
it's function is too limited
I didn't know that flashing the stock rom will revert also to the stock recovery
Thanks
By the way, I didnt find backing up reovery in TB
Does anyone have the link to download TWRP 2.7.0.0 ? I can't access my USB storage with 2.6.3.0. I need it for the GT-N5110. Thank you in advance.
Sent from my GT-N5110 using XDA Premium HD app
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.
khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.
Click to expand...
Click to collapse
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Thats true - I did read about that. And that would definitely explain being unable to restore a kitkat rom.
However, I cant even restore a lollipop backup after flashing a different lollipop rom! Even if they are both derived from the same FOB6 base! That is what is even more confusing. Try it - backup, wipe all the partitions except int and ext sd of course and then try to restore... it just doesnt work!
Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0
I've had no problem restoring from a TWRP Backup on Lollipop numerous times.
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
I noticed that in every folder in /data/app/ there is an apk called base and a folder lib, can i backup just the apk? Or when i need to share an apk or take an apk i need to take also rhe lib?
dugryce said:
I've had no problem restoring from a TWRP Backup on Lollipop numerous times.
Click to expand...
Click to collapse
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!.
Click to expand...
Click to collapse
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.
senozlu1 said:
Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0
Click to expand...
Click to collapse
Oh I'll try this and report back. Thanks
Sent from my SM-N900T using XDA Free mobile app
yummymango said:
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.
Click to expand...
Click to collapse
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Sent from my SM-N900T using XDA Free mobile app
khanam said:
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Click to expand...
Click to collapse
One of the devs, who runs the Lollipop ROM I've been using, warned against restoring data. He suggested backing up apps + data through Titanium Backup instead. Maybe it depends on the ROM?
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Hi
I have a rooted S4 running Carbon. Im using TWRP 2.8.5.0 and can backup and restore any
KK rom with no issues. I can flash Lollipop and backup but it will not restore this backup.
Its says restore successful but then just boots back into recovery. If someone could resolve
this it would be great
Hello all,
TB doesn't seem to pick up the apk file when backing up which is quite frustrating. Does anyone have a solution?
i had backup using TWRP 2.8.7.0 my stock TW lollipop rom...Now i had flashed Dirty Unicorns v9.5...If i wanted to goto stock rom that nandroid backup wont work??? thats what people are complaining over here??
Currently I'm using a OnePlus 3 on 6.0.1 (OOS 3.1.1) but I would like to update to Oreo (OOS 5.0). How do I do this when my device is rooted?
I've downloaded the latest OS off the oneplus website. Is it as simple as uninstalling SuperSU and then flashing the latest OS through recovery?
I also have TWRP recovery and Xposed installed.
Would appreciate any help.
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
The full zip of oxygen OS will overwrite the TWRP recovery with the stock one?
I can update with the zip in the recovery and root whenever i want or i have to do this at the same time?
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
It's as easy as that? It's not a problem that I have xposed installed or anything?
What should I wipe before I install the new OS?
Sorry for all the questions, newbie here.
@Edo 91
I'm not sure about overwriting recovery, it's been a long time since I've used OOS (currently on PA, before than on LOS). If I remember correctly the recovery should stay if you DON'T boot into system right after flashing. So, flash the ROM, reboot into recovery first, then boot into system. Can't say if anything changed with Oreo, but that's how I remember it from Nougat and Marshmallow. You can however flash recovery again right after ROM, just to be sure.
You can root later down the road, no need to do everything at once.
@scalliant
Generally yes, it as easy as that. Xposed and root methods modify system partition - and that gets overwritten when you flash new ROM. That's why those modifications have to be flashed again after every update (some custom ROMs are exception, but rest assured the stock one will nuke all mods).
Anyways, we're talking about Android version upgrade here and not just a minor system update, so I'd recommend a clean installation (but you can try dirty first and then do a clean one in case you experience issues).
First of all, make a full nandroid backup (check everything except "system image" in TWRP). Copy all of your media content (pictures, videos, music ... whatever you don't wanna lose) to another device - better safe than sorry. Optionally, backup apps with Titanium or something similar.
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
To do it dirty: wipe just /system and /cache. You'll lose just system settings, but will keep apps and everything else. Less hassle, but higher chance of something going south.
Explorer23 said:
@Edo 91
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
Click to expand...
Click to collapse
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
shobuddy said:
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
Click to expand...
Click to collapse
Media is on a (virtually) separate partition and is preserved unless while internal storage is formated. Still, it's never a bad idea to have a backup.
Yes, text messages are lost if not backed up. There are many apps that do that (and can be set to upload to cloud regularly).
Sent from my OnePlus 3 using Tapatalk