Related
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
theinvid said:
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
Click to expand...
Click to collapse
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Heisenberg said:
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Click to expand...
Click to collapse
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
theinvid said:
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
Click to expand...
Click to collapse
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
tried
Heisenberg said:
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
Click to expand...
Click to collapse
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
Are you flashing the appropriate vendor image for the ROM after you've flashed the ROM? When you say factory reset are you just choosing the factory reset option in TWRP? If so, you should instead go into the advanced wipe section and wipe system, data, cache, and dalvik cache. CM isn't the only ROM out there with customisation, there are other ROMs that have the same or more level of customisation available.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
also simply tried a Factory Reset followed by reboot and that failed in the same way.
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
theinvid said:
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
Click to expand...
Click to collapse
I really don't know, there's no reason it shouldn't install. You must be missing something, or perhaps the zip is corrupt, did you check the MD5?
Hello,
I have a Galaxy s4 i9505 jfltexx. I'm under CWM recovery but I'd rather prefer to have PhilZ Recovery.
I saw that jflexx versions have been stopped and that they recommended to use jflte version... for this OK. But are there some versions that I musn't flash ? Or do I need the last version available ?
Thanks for your help
TWRP is the recommended recovery for us, once you get used to it, it is actually better...
Philz is based on cwm. Since cwm hasn't been updated for a while, neither has Philz.
I also recommend TWRP as many ROMs recommend TWRP.
Ok except that I had a problem with CWM this morning : the Nandroid backups doesn't save the "preload". It was impossible for me to restore it (bootloop). As I understood recently, only PhilZ Recovery has an option to include the preload in the Nandroid backup.
Last but not least, where can I get TWRP on its last version for my phone ? Can you send me a link ?
Here.
TWRP also has a preload backup option if I remember correctly.
Why would you backup preload? As far as I know the partition is empty, for me at least.
Here is a TWRP recovery from autor's website for GT-I9505 (JFLTEXX): https://dl.twrp.me/jfltexx/
GDReaper said:
Here.
TWRP also has a preload backup option if I remember correctly.
Why would you backup preload? As far as I know the partition is empty, for me at least.
Click to expand...
Click to collapse
Because, even if it's not a galaxy S2, I had exactly this problem yesterday with my Nandroid backup : http://forum.xda-developers.com/galaxy-s2/help/bootloop-nandroid-restore-t2337856
Thanks KonowaL !
oldbear3 said:
Because, even if it's not a galaxy S2, I had exactly this problem yesterday with my Nandroid backup : http://forum.xda-developers.com/galaxy-s2/help/bootloop-nandroid-restore-t2337856
Thanks KonowaL !
Click to expand...
Click to collapse
Well, maybe it's a CWM problem.
I never backed up the preload partition, yet I have successfully restored my nandroid backups in the past.
GDReaper said:
Well, maybe it's a CWM problem.
I never backed up the preload partition, yet I have successfully restored my nandroid backups in the past.
Click to expand...
Click to collapse
I just flashed TWRP as you advised. It seems really great (not as the old version I tested by the past)... but there is no preload partition backup option. Or I don't see it. Where do you see it ?
I flashed the 3.0.0 version.
oldbear3 said:
I just flashed TWRP as you advised. It seems really great (not as the old version I tested by the past)... but there is no preload partition backup option. Or I don't see it. Where do you see it ?
I flashed the 3.0.0 version.
Click to expand...
Click to collapse
Hmm..
I think only JDCTeam's TWRP has that option. I know their 2.8.7.2 TWRP had several backup options, including efs and others.
Also note that TWRP backups don't work with CWM backups, so you will have to redo them.
Also, as I mentioned earlier, I never backed up preload (unless TWRP does that on its own) and restored those backups successfully, and without bootlooping.
You might wanna try it yourself in order to believe it.
OK thanks a lot for your help
Hi everyone,
Just got my new G6, after much pain I managed to unlock the bootloader, install TWRP (v3.2.1.0) and to root it with SuperSU (stable release 2.82).
For now I'll keep the stock rom but I wanted to make a backup in case something went wrong with other tweaking I might do and I couldn't because TWRP couldn't "mount /system (device or resource busy)".
So I went into the mount menu and tried checking system but it just won't. I can mount it as read only but I can't mount it as writable.
If it's of any importance, I couldn't get magisk to install to root the phone and had to use SuperSU instead.
I could do the backup while mounting system as read only but I feel like it might be an issue in the future (for custom roms or even restoring the backup maybe ?) if I can't fix this issue.
So does anyone how to get TWRP to mount system as writable ? Thank you
Elvenstar said:
Hi everyone,
Just got my new G6, after much pain I managed to unlock the bootloader, install TWRP (v3.2.1.0) and to root it with SuperSU (stable release 2.82).
For now I'll keep the stock rom but I wanted to make a backup in case something went wrong with other tweaking I might do and I couldn't because TWRP couldn't "mount /system (device or resource busy)".
So I went into the mount menu and tried checking system but it just won't. I can mount it as read only but I can't mount it as writable.
If it's of any importance, I couldn't get magisk to install to root the phone and had to use SuperSU instead.
I could do the backup while mounting system as read only but I feel like it might be an issue in the future (for custom roms or even restoring the backup maybe ?) if I can't fix this issue.
So does anyone how to get TWRP to mount system as writable ? Thank you
Click to expand...
Click to collapse
Have you formatted data trough the dedicated option in TWRP? Format, not wipe, where you have to put "yes".
Anyway you can try with Melina's TWRP which solves many problems of the official one: https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Killua96 said:
Have you formatted data trough the dedicated option in TWRP? Format, not wipe, where you have to put "yes".
Anyway you can try with Melina's TWRP which solves many problems of the official one: https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Click to expand...
Click to collapse
I did try it once after the magisk install failed and I assumed it was because of that issue but I haven't tried yet with superSU correctly installed. Should I immediately try the backup after formatting or boot the phone once before ?
The issue I have with Melina's TWRP is that it's not compatible with fulmics and if I were to install any custom rom I think it would be that one (to keep stock camera mostly)
Elvenstar said:
I did try it once after the magisk install failed and I assumed it was because of that issue but I haven't tried yet with superSU correctly installed. Should I immediately try the backup after formatting or boot the phone once before ?
The issue I have with Melina's TWRP is that it's not compatible with fulmics and if I were to install any custom rom I think it would be that one (to keep stock camera mostly)
Click to expand...
Click to collapse
Format data, reboot recovery, and try to install magisk or mount system.
For Melina's TWRP it has NO problems with Fulmics, Zefie said that "officially" is not compatible because two users said that they have problems with that TWRP only with fulmics, i can assure you that with last version of both Melina's TWRP and Fulmics i never had problems like those two users, anyway you can try to use Melina's TWRP and if you have any problems just flash back the official twrp.
Killua96 said:
Format data, reboot recovery, and try to install magisk or mount system.
For Melina's TWRP it has NO problems with Fulmics, Zefie said that "officially" is not compatible because two users said that they have problems with that TWRP only with fulmics, i can assure you that with last version of both Melina's TWRP and Fulmics i never had problems like those two users, anyway you can try to use Melina's TWRP and if you have any problems just flash back the official twrp.
Click to expand...
Click to collapse
Alright so it's been a rough ride.
I formatted data, reboot TWRP and then indeed I was able to mount system as writable.
I then did my backup, which said it was successful and the only error it showed then was "unable to unmount /system"
I flashed magisk and rebooted into the normal system and the phone of course was back to factory settings and asked me my google account. Except that when I tried logging in it always showed me an error along the lines of "google play services keeps crashing". (making it impossible to get through the installation part of the system)
I'm not sure why that happened. I had frozen some apps but that shouldn't have been saved since I formatted data right ? and the phone was working perfectly fine before that.
But anyway I didn't really know what to do at that point so I just jumped the gun and downloaded and flashed fulmics.
It worked fine but only with supersu. For some reason magisk just doesn't want to get installed at all.
The rom itself worked fine but I had no root access by choosing magisk in the aroma installer so I wiped again and installed it again with supersu which works.
I also flashed xposed which is also working as intended.
So I'm all set for now I think.
Maybe when I need to wipe again I'll figure out why magisk doesn't work but for now I'm satisfied.
In any case, thank you for your help
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
I got the same problem... I did't find the solution. Can someone help ?
k1n9n0th1n9 said:
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
Click to expand...
Click to collapse
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Pupet_Master said:
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Click to expand...
Click to collapse
hi, I had this, try doing the partitions separate, I did data afterwards following a reboot.
Try OrangeFox-R10.0_8-Stable-davinci recovery.
flamedrops said:
Try OrangeFox-R10.0_8-Stable-davinci recovery.
Click to expand...
Click to collapse
Orange fox atm is the worse and most buggy recovery for K20
Pupet_Master said:
Orange fox atm is the worse and most buggy recovery for K20
Click to expand...
Click to collapse
even the latest one?
flamedrops said:
even the latest one?
Click to expand...
Click to collapse
Yeap, it is still in it's infancy, where other TWRPs solved some issues that even the latest OF still has
I have just made a new backup after restore from Titanium Backup, but after flash new firmware and test some new roms, some of apps were crushing after restore and must be installed and configured one again.
im having big problems about vendor. for start im giving some info:
device: mi a1 (tissot)
current os: lineage OS 17.1
root: yes
twrp: can install or use just booting .img
i unlocked my device and installed twrp. there is no problem.
i wanted flash lineage OS and i wiped my device. gives error about cannot mount /vendor
i installed treble supported twrp and installed lineage OS. flashed magisk. installed microg...
then i tried flash mapsv1.zip which is recommended for microg. then booom. another /vendor error.
now i can boot device. i can use everything except gps. google maps app cannot found location. yandex maps can found and i can use it until lock screen or going main screen (or another app). then it starts stopping everytime until i clen its data and cache. then again... in chrome when i open google maps and try found my location chrome stops.
i tried to change /vendor/etc/gps.conf. its still same.
what to do now guys? im worrying about if i try re-flash rom it doesnt flash and device bricked. any solution without re-flash rom? what causes to cannot mount /vendor after solved it?
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
KaaMyA said:
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
Click to expand...
Click to collapse
Dalvik cache , system, data, and cache. My device is not rebooting too much. Sory if i couldn't explain. Everything working fine except when an app tries use my location, app stops running, i cant flash anything right now.
İ thought anyone knows mapsv1.zip file(microg.org) and which files are replaced or added by this file when flash it. And can i do it manually? Btw i can read and write /vendor file with solid explorer
İf needed to re-flash rom thats ok but i think lineage OS was perfect for me until this error. And a last thing: can i backup my settings. (İ already took backup of everything in stock when unlocked bl)
Thank you for help
Edit: gps problems started when i tried flash mapsv1
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
KaaMyA said:
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
Click to expand...
Click to collapse
Okey ilk try it and share the result night. But is it possible to backup settings of phone?
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
KaaMyA said:
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
Click to expand...
Click to collapse
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Nurullah44 said:
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Click to expand...
Click to collapse
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
portox said:
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
Click to expand...
Click to collapse
Are you sure? Bcs i can view and change /vendor in root path. Treblizing is updating and repairing system partitions right? İ am using treble support twrp, flashed stock rom via mi flash(said error but worked fine) then how to treblize a device? And is this required for anything(like a rom, an app)?