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
Related
Hi,
I've been using cyanogen mod 9 without any issues. recently i upgraded to cyanogen mod 9.1 and have been noticing minor glitches. nothing to be worried about. Recently i used Bluetooth to share files ( have used it before). when i powered off the Bluetooth it rebooted and is now stuck at boot animation. Also cannot connect to my PC. any suggestions or workaround to the problem? would be appreciated.
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
MistahBungle said:
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
Click to expand...
Click to collapse
I'm sure there is a bug in Bluetooth implementation in mod 9.1. I did a cache wipe, after that it was stuck in another kind of loop. rebooted normally, immediately Bluetooth turns on and it reboots again.
how do i reboot into recovery? previously i was using adb for that. i restored backup ( it was of mod 9) now it wont even boot.
ok. so i finally managed to get it working. i had accidentally restored mod 9 backup onto mod 9.1 so i used odin to flash ClockworkMod-Recovery_5.5.0.4 booted and now i'm back to a month older backup. Oh well since i have to restore my settings anyway why not try mod 10.1?
Been getting frustrated over the past day.
Currently am up and running on a backup of Hyperdrive RLS 8.1, but I am afraid to reboot because for all of last night, any backup or clean install of any ROM I flashed would either
1) boot up the first time, but any subsequent reboots would result in stuck at the Samsung Custom Lock screen
2) not boot up at all, stuck at the Samsung Custom Lock screen
When I get stuck at the Custom Lock screen, I do a battery pull and then attempt to reboot into recovery. However, trying to boot recovery would not work (phone reboots itself after briefly showing "booting recovery" every time) until I plugged in the charger and tried to boot recovery (not sure if just coincidence?). Currently running TWRP 2.5.0.2
At this point, the recovery asks for a password (I have never set a password, don't know why this happens?). This prevents me from factory resetting (gives me an operation failed) because I need to "decrypt data" or something along those lines, using a password which I am sure I have never set. The internal storage is apparently unable to mount without decrypting data using a password..?
I found that in the WIPE menu I can perform the FORMAT DATA action which is successful and fixes the decrypt data problem, and I am able to factory reset and then restore a working ROM or install a new one (I tried CleanROM 1.6 with patch to 1.6.5 since it was on my sdcard).
This brings me to this position at the current moment. After formatting and factory resetting, I have done the following with such results:
1) Restoring my STOCK, ROOTED TWRP backup from before my install of Hyperdrive 8.1. Booted up fine, but a reboot gave the same results of stuck at the custom lock screen
2) Installing CleanROM, booted up fine the first time, but got stuck on the first reboot at the first bootup screen (it changed it to the original
Samsung Galaxy S4" instead of the custom lock?). I went back to recovery and went through the same process (decrypt by formatting data, factory reset, restore/install new rom)
3) Restoring my Hyperdrive 8.1 TWRP backup (first backup of the ROM while it was apparently running fine, reboots were normal and no problems yet). I am currently running this right now but have not attempted a reboot because I do not have the time for the next few days to mess around with my phone.
Summary: Stuck at initial boot screen (Custom Lock or Samsung Galaxy S4), TWRP 2.5.0.2 asks for password for decrypt?? & cannot factory reset, able to format data which allows factory reset after, restored Hyperdrive 8.1 backup, currently afraid to reboot in fear of getting stuck again.
Any help or suggestions would be appreciated. I am considering ODIN a stock image and completely starting over, but that will have to wait until the weekend.
I seem to have shot myself in the foot with this and I need some help.
My phone is a Samsung Galaxy Alpha, SM-G850W, and I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.
So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )