Currently, I'm on April build resurrection remix (25-04). Took a twrp backup. Later tried to install latest build rr ROM , but due lollipop bootloader, it got stuck on get resurrected animation. Now, from twrp, I wiped everything (except microSD) and restored from backup. Each and every thing is working fine, but volte isn't working. Any solutions?
Related
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
tshuford said:
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
Click to expand...
Click to collapse
I've had some issues before regarding actions within the CWM on my d2vzw. I got rid of CWM and installed TWRP 3.0.2-0. I was then able to do much more.
I had also read somewhere that CWM is an abandoned project and TWRP is kept current and is also recommended by Cyanogenmod for all their ROM's and other flashable files.
The link for the d2vzw TWRP is https://dl.twrp.me/d2vzw/
Good luck!
Hey guys, I have TWRP 3.0.2-0 was running 4.4 (i think) got an system update earlier today, and the phone asked to restart to install, (absent minded) I pressed yes.... The phone rebooted into recovery and thats as far as it went. I have all my stuff backed up ( did that last week) since I had intentions of going with a custom rom.
restoring the system didn't work, so i wiped everything and installed RR with gapps. Successfully wiped and installed both however, phone still boots back into recovery, not system.
How can i get it back to boot into system?
I found a fix which worked for me at
http://forum.xda-developers.com/tmob...puter-t2873386
So my problem began when i flashed eu rom latest version my setup was:
TWRP offcial 3.1.0-0
/data and /cache F2FS
previously running android 7.1.2 (Nitrogen OS)
And Franco Kernel and even before that i used MIUI 8.2.20 with ZCX and ext4 patrtions
Flashing EU rom i got a weird intro screen username and password asking to validate the phone (NOT MI ACCOUNT IT WAS AT THE VERY BEGINNING OF THE BOOT)
so i gave my mi account credentials and then nothing so after i that i put my phone away for 15 days.
So yesterday after 15 days my exams ended i edl flashed my phone and then i install miui 8.1.6.0 and then updated to 8.2.3.0 and then i was good and running the s8 theme but within that span i started missing NOS so flashed ZCX Backed UP MIUI 8.2.3.0 and then i flashed Offcial TWRP no probs flashed absolutely fine and then i restored my backup of my rom before i went EU $#!T and i restored upon booting it asked for password i then remebered that miui encrypts the /data patition so i formatted /data and then i thought of restoring the /data partition and then it would stop at copying a certain partition and i would wait for a long time and then i ejected the phone from the computer but still i was not able to delete or do anything in the /data partition as if it is read only partition UPON DELETING ANYTHING I GET "RM -RF ERROR" I AM FLASHING ROMS SINCE 2010 WITH GALAXY S AND I NEVER FACED A ISSUE LIKE THIS !!! i completely freaked out i thought of doing something so i formatted /data and it would get stuck there forever!! because of this i had to flash miui through edl 4 times until i gave up and installed miui and then just installed NOS and Gapps then nos unroot,magisk and at last franco r5 as i didn't had the r6 version then after booting up i restored all my apps from titanium backup and i good to go..........
UNTIL THEN FK Manager Auto flashed r6 version of franco and then AS I REBOOTED I FOUND WIFI NOT WORKING SO I CHECKED MAC ADDRESS IT WAS 00:00:02...... I WAS COMPLETELY SHOCKED I THEN CHECKED BASEBAND IT WAS 'UNKNOWN' I WAS LIKE i was trying to restore modem i got "extractTarFork() process ended with ERROR: 255 " then now i am flashing miui thorugh EDL i will update u all soon...
BUT WHY IS THIS HAPPENING WHY I AM NOT ABLE TO TO NOS WITHOUT DOING ANY $#!T I LOVE NOS AND I WANT TO INSTALL IT AND ALSO CONVERT TO F2FS AND OFFICIAL TWRP PLEASE HELP IN DOING SO!!!!
Wipe everything first of all.
Flash nos
Flash gapps
Install apps from play store.
Forget about the backup. It may not be compatible with latest builds. Too many code mashups. Starting fresh is always considered best option
Flash latest firmware.
Done. Enjoy.
Archit9169 said:
Wipe everything first of all.
Flash nos
Flash gapps
Install apps from play store.
Forget about the backup. It may not be compatible with latest builds. Too many code mashups. Starting fresh is always considered best option
Flash latest firmware.
Done. Enjoy.
Click to expand...
Click to collapse
Update:I flashed using edl in phone booted fine and i was able to use phone network and wifi AND LUCKILY I WAS ABLE TO RESTORE THE BACKUP FROM PREVIOUS ROM AND RESTORED FINE and even copying the backup through offcial twrp worked fine
but still why the errors previously????? extractTarFork() process ended with ERROR: 255
Androbots said:
...process ended with ERROR: 255
Click to expand...
Click to collapse
I started having issues flashing ROMs and restoring backups after updating to the official TWRP 3.1.0.0 and 3.1.1.0
It sounds stupid and paradoxical but the previous 3.0.2.0 (or something) I used (not even sure if it was the official one) was faster and trouble-free in my experience. Don't know why nobody mentions this in the TWRP thread.
Androbots said:
Update:I flashed using edl in phone booted fine and i was able to use phone network and wifi AND LUCKILY I WAS ABLE TO RESTORE THE BACKUP FROM PREVIOUS ROM AND RESTORED FINE and even copying the backup through offcial twrp worked fine
but still why the errors previously????? extractTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
I had the same problem.
Flashed rom trough edl, with zcxrecovery img.
Flashed latest modem.
Restored my TWRP backup and the error was gone. ^^
Kaldrox said:
I started having issues flashing ROMs and restoring backups after updating to the official TWRP 3.1.0.0 and 3.1.1.0
It sounds stupid and paradoxical but the previous 3.0.2.0 (or something) I used (not even sure if it was the official one) was faster and trouble-free in my experience. Don't know why nobody mentions this in the TWRP thread.
Click to expand...
Click to collapse
Kollachi said:
I had the same problem.
Flashed rom trough edl, with zcxrecovery img.
Flashed latest modem.
Restored my TWRP backup and the error was gone. ^^
Click to expand...
Click to collapse
Yeah u all are correct something wrong with latest versions of twrp. Anyways i am up and running my rn3 again thanks for all ur help..!! Good night
Synopsis of Issue:
Currently I have several backups that do not show an error resoring but for some reason will not boot. Everytime I boot the device from a backup it goes into the WIleyfox boot screen and stays like that.
Background Information:
I own a Wileyfox Swift 2x, unrooted and bootloader unlocked. TWRP 3.1.1 is installed. I upgraded the system to Nougat 7.1 [SW46-WF-MARMITE-7.1-TOS089A-RECOVERY[NOUGAT] and everything seemed to function properly albeit with those annoying corruption startup screens. However for some reason I just coudnt get it to ROOT. I took a full backup. So I decided to install Lineage 14.1 [lineage-14.1-20171002-nightly-crackling-signed] with open-gapps. After a wipe I installed Lineage but it woudnt boot despite fixing error7 issue. ...I moved on>>>
I next tried to install Cynogenmod 13.1 [SW33-WF-MARMITE-CM-13.1.5-ZNH2KAS7EB-RECOVERY] with open-gapps and succeeded but later realised there was an issue with ROOTing and phonecall recorder - anyway I needed a working phone so attempted to restore Nougat 7.1 (above) after backing up Cynogenmod 13.1.
This is when i realised that none of my backups would boot after restoring. The phone will not boot and all I am left with is the Wileyfox boot screen. I tried restoring with and without system image, & only restoring with boot, system & data - I have performed all of these after performing the standard wipes but it remains the same.
Help:
Can anyone help me get my phone into working order so that I can restore my backups and boot into them?
PhilosAnthropos said:
Synopsis of Issue:
Currently I have several backups that do not show an error resoring but for some reason will not boot. Everytime I boot the device from a backup it goes into the WIleyfox boot screen and stays like that.
Background Information:
I own a Wileyfox Swift 2x, unrooted and bootloader unlocked. TWRP 3.1.1 is installed. I upgraded the system to Nougat 7.1 [SW46-WF-MARMITE-7.1-TOS089A-RECOVERY[NOUGAT] and everything seemed to function properly albeit with those annoying corruption startup screens. However for some reason I just coudnt get it to ROOT. I took a full backup. So I decided to install Lineage 14.1 [lineage-14.1-20171002-nightly-crackling-signed] with open-gapps. After a wipe I installed Lineage but it woudnt boot despite fixing error7 issue. ...I moved on>>>
I next tried to install Cynogenmod 13.1 [SW33-WF-MARMITE-CM-13.1.5-ZNH2KAS7EB-RECOVERY] with open-gapps and succeeded but later realised there was an issue with ROOTing and phonecall recorder - anyway I needed a working phone so attempted to restore Nougat 7.1 (above) after backing up Cynogenmod 13.1.
This is when i realised that none of my backups would boot after restoring. The phone will not boot and all I am left with is the Wileyfox boot screen. I tried restoring with and without system image, & only restoring with boot, system & data - I have performed all of these after performing the standard wipes but it remains the same.
Help:
Can anyone help me get my phone into working order so that I can restore my backups and boot into them?
Click to expand...
Click to collapse
I have very similar issues. Wileyfox white screen after flashing TWRP. Was there ever any resolution to this?
I have only managed to breathe life in to my phone again by reflashing ALL partitions from the recovery image that's on these forums
Hi,
i have twrp 3.2.3-0 and lineageos 15.1 installed on my sgp311. the bootloader is unlocked and the devices is rooted. i want to test resurrection remix 6.2.1 and created a backup with twrp. the first problem is that after installing RR all my apps from lineageos are still there. i deletes dalvik/cache after flashing resurrection remix. i also deleted 'system', but after that nothings boots anymore. restoring the backup ends up in the resurrection remix boot screen but at the end it boots into twrp. now i flashed lineage os again and all apps are still there.
1.) what's to do to flash a fresh resurrection remix without anything from lineageos? no aps, no settings, completely new.
2.) why isn't the backup working? is there anything i have to do? i made so special settings when i created the backup (default settings).
the only way i know to delete ALL is to flash a new stock rom with flashtool. but this will delete also twrp.
piere mallao
PiereMallao said:
Hi,
i have twrp 3.2.3-0 and lineageos 15.1 installed on my sgp311. the bootloader is unlocked and the devices is rooted. i want to test resurrection remix 6.2.1 and created a backup with twrp. the first problem is that after installing RR all my apps from lineageos are still there. i deletes dalvik/cache after flashing resurrection remix. i also deleted 'system', but after that nothings boots anymore. restoring the backup ends up in the resurrection remix boot screen but at the end it boots into twrp. now i flashed lineage os again and all apps are still there.
1.) what's to do to flash a fresh resurrection remix without anything from lineageos? no aps, no settings, completely new.
2.) why isn't the backup working? is there anything i have to do? i made so special settings when i created the backup (default settings).
the only way i know to delete ALL is to flash a new stock rom with flashtool. but this will delete also twrp.
piere mallao
Click to expand...
Click to collapse
1.you need to make all wipes (system, data, cache, dalvik) to install new ROM.
2. It depends what partitions you have actually backed up (included in backup) and some other settings.