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?
Related
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
I was using my Oneplus 3 on LineageOS for the past few weeks and when I downloaded the latest nightly the phone asked me to go through the setup process again. After I finished setting it up all my apps were crashing and I had to reset the phone. At first, I thought it was a problem with Lineage and so I switched to Ressurection Remix. I installed the rom and set up the phone but as soon I went to flash dolby atmos and reboot I had to set up my phone again and all my apps and settings were gone. I thought it was a bug with lineage so I switched to VertexOS. Again i set up the phone and installed all my apps. I went to flash magisk and the same thing happens. All my apps and settings gone. I am using twrp 3.1.0-0 and this keeps happening whenever I flash something after setting up the rom. I tried only booting to twrp and rebooting the phone but that did nothing so I guess it happens only when I flash something. Has anyone encountered this problem and if so is there a fix? Any help would be appreciated.
ujan1996 said:
I was using my Oneplus 3 on LineageOS for the past few weeks and when I downloaded the latest nightly the phone asked me to go through the setup process again. After I finished setting it up all my apps were crashing and I had to reset the phone. At first, I thought it was a problem with Lineage and so I switched to Ressurection Remix. I installed the rom and set up the phone but as soon I went to flash dolby atmos and reboot I had to set up my phone again and all my apps and settings were gone. I thought it was a bug with lineage so I switched to VertexOS. Again i set up the phone and installed all my apps. I went to flash magisk and the same thing happens. All my apps and settings gone. I am using twrp 3.1.0-0 and this keeps happening whenever I flash something after setting up the rom. I tried only booting to twrp and rebooting the phone but that did nothing so I guess it happens only when I flash something. Has anyone encountered this problem and if so is there a fix? Any help would be appreciated.
Click to expand...
Click to collapse
Try the TWRPs from eng.stk and jcadduono. I think that the official TWRP is ok only for OOS.
do u use custom kernel ??
happened to me.
used elemntalex kernel ( not the cause of the problem )
when i used fusion govener i got that problem
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.
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.