I tried to flash my Wileyfox Swift 1 to Lineage today, from its Android 7.0 rom.
I downloaded twrp-3.1.1-crackling.img and lineage-14.1-20170703-nightly-crackling-signed.zip.
I then followed the instructions on the Lineage OS site for a Wileyfox Swift to the letter to get the Lineage rom flashed (with the one exception being I also "wiped" Internal Storage, along with Cache, System and Data partitions). I didn't try to install, or want to install, the Google Apps.
Everything worked exactly as expected, right down to the absolute final step in the guide. When I chose to Reboot, then System, I just found myself back in the bootloader. No matter what I do, I just keep booting back up to this. I still have full access to recovery mode, but I just can't load an OS or get past the bootloader screen when I restart.
I have an old Cyanogen mod I have been able to revert to in the mean time, but I'm struggling to understand what I did wrong here. Can anyone provide any help/suggestions?
I tried again this afternoon and everything appears to have worked. I've loaded Lineage OS successfully and everything is working well. I'm still not sure what happened the first time, but all is good now.
I had the same issue. After installing an old CM13 release (with TWRP), turning everything off and then start from scratch with LOS 14.1, everything worked. It seems that CM13 does have a side effect that is needed for LOS 14.1.
Related
Hello, I think I have a really strange problem. I'm running Exodus 6.0 (and I made a full and fully functional backup that worked without issues) and yesterday I wanted to install AICP 12.0 (Android 7.0).
So I did a clean flash, but the SIM card detection didn't work and baseband showed up as "unknown" (according to the AICP members, I am the only one with such an issue).
So I tried several times but no success. They told me that it could be a problem of the 20G modem and bootloader. So I decided to revert back and since then I only have problems.
This is what I've done: Firstly, I flashed the 20D kdz. The phone booted fine. So I tried to install TWRP through ADB. (The phone was recognized and I was able to perform ADB commands). So I booted to bootloader, typed in the commands, but....nothing. TWRP didn't boot and I couldn't install it, no matter what I've tried. No I was on stock Rom without root and custom recovery, so I decided to revert back to Lollipop. I flashed the 10c kdz, flashed the rooted system image, wanted to flash TWRP (3.0.2-1) via Flashify, no success. Not until I tried TWRP 3.0.2-0, I had success and TWRP has been flashed. So ok, all fine now I thought, so I flashed the complete 20D stock Rom via TWRP, booted it up, worked. Now I wanted to give AICP a try again. So again installed, again no SIM card detection. With the CM 14 nightly 10/21 flashed afterwards (always clean flashed), success! SIM card was detected fine. So, again AICP tried and surprise, SIM card was detected as well. But now I had new problems: When I flashed SuperSU, SIM card wasnt't detected again.
Without SuperSU and stock AICP kernel, I suffered random reboots while setting up the WiFi connection in setup wizzard. Without SuperSU and Llama Sweet R7 kernel, I suffered a system crash and got a green screen saying something like "App F1Q: XPU Error!". So after some time I gave up and wanted to clean flash Exodus again, again no success, because the setup wizzard stopped (unfortunately:laugh:).
So ok, last rescue: My full backup. So I restored it (Exodus 6.0 10/22 nightly, opengapps pico 10/23, SuperSU SR1 2.78 in systemless mode, systemless xposed v86.2) and seemed to work fine. Today, I wanted to run SafetyNet Helper, and the phone suddenly rebooted. I wanted to run Pokémon Go, the phone suddenly rebooted. Nova Launcher can't get permissions for showing up unread labels correctly (though I have Nova Prime and all permissions are granted for sure!), other apps seem to work correctly. But all in all it's very strange because I have the feeling that somethink went completly wrong. So I don't know what I've done wrong, what do you think about this?
Hi there,
this morning my LG G3 (running one of the latest LineageOS 14.1 nightlies) crashed and then bootlooped for some reason. Since then I've tried to get my phone running again, sadly to no avail. I've wiped the phone (data, system, cache, dalvik) several times with TWRP and tried to reinstall Lineage. But everytime the phone's in the middle of flashing the zip, suddenly the kernel crashes (or TZ crash).
I've managed to install a stable version of Lineage after the first couple of crashes/wipes, used it your a while and then wiped again to reinstall it with GApps (I forgot the 1st time). After even more crashes/wipes I've managed that aswell, sadly Lineage bootlooped after the first minute of using it.
Am I forgetting something (as I'm typing this: do I need to reroot the phone after wiping?) or is there any way I can start completely anew?
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
Try this:
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Read his second post. Wrong TWRP version may lead to this. 3.2.3.1 encryption issues.
Is had the same issue, i ended up with a fastboot installation. Al is working again.
Yesterday I did a dirty flash of Oxygen OS 9.0.10 on my OnePlus 5T which was initially running Oxygen OS 5.1.7 with Oreo 8.1.0. After that I flashed latest Magisk zip. After booting into system, then after the final setup of the update, I flashed franco kernel from TWRP.
Everything went smooth. All apps were functioning fine. Today in the evening, while watching YouTube, the touch stopped responding. I restarted my phone, cleared cache, dalvic, still the touch wasn't responding.
I booted in TWRP, the touchscreen wasn't responsive, therefore I used my mouse to decrypt then copied full zip of OOS 9.1.0 zip via adb from my laptop. After clearing cache, dalvic, I flashed the zip file.
After booting into system, my phone is showing the message, "phone is starting" with animated strip below it. This has been since past 45-50 minutes.
The touch is not functioning even now.
What should I do to resolve this trouble?
Has you debloat something from /system/app or priv-app? On my tablet it prevents to boot completely and stucks in this Android update loop.
Also not everytime a good idea to dirty flash to another Android major version (Oreo > Pie)!
Try a fresh install.
OxygenOS 9.0.10
No-Verity v4 (if a decrypted phone)
Boot.
Then back to TWRP
Magisk & Custom Kernel
Boot.
Restore maybe from Titanium user apps only (except Whatsapp/Threema/Telegram.. GCM/FCM notifications problems).
Flash Magisk modules.
Sent with much love and Android.
I have been having persistent problems with the touchscreen on my 5T becoming unresponsive at random times for no apparent reason for a while now (see this This thread for more info there).
I have found that when the touch screen stops responding, the ONLY thing that will get it working again is flashing back to stock firmware - I have been using 9.0.9 (didn't even realise .10 was out). Sometimes it doesn't work the first go, and I have to reflash again over the top (maybe even a couple of times) but I've never failed to get it working after a few goes.
Problem (on my phone at least) is that phone then hangs on the "just a sec" screen at first boot, but once the screen works again I do a clean flash of LineageOS so the setupwizard hanging is not a problem for me per se, except that the touch screen inevitably flakes out again - sometimes it takes a few days, sometimes it happens within minutes, but nothing I have tried has made it go away completely. I'd say it was a hardware problem except that reflashing the stock OOS ROM can bring it back to life... maybe it's some weird hard+firmware combination that is triggering it.
Anyway, reflash stock a few more times and see if that helps.
Hi there,
Yesterday I rooted my oneplus 5T and installed TWRP 3.2.1 & masgisk. Then, I´ve installed Pixel experience AOSP which seemed like fairly stable from the description. Everything went fine, the OS started I started configuring it then after setting the password I got the OS having always the setting app to crash. So, I thought well, I can just go to recovery and try once again factory reset. Otherwise, I can mount the recovery and install another ROM. I went to recovery and to my surprise it was asking for a password and mine didn´t work. I tried the factory reset and still the encryption stayed. I found that this version has a decryption problem and all my files were encrypted and not accessible, that was fine, since I had everything backed up. So, I have installed the new version of TWRP which seems to fix this issue after loosing all encrypted file. I have formated the data, system, dalvic and cache and installed once again pixel exerience but the OS keeps on bootloop. Have anybody seen something like this? How should I fix it? My best guess was to reinstall stock OS via adb, but in the past I've rooted a couple of devices and I've never seen something like this.
Thanks in advance