Develop Bugs

bootloop or something like it after updating CM

First, for shortening and simplicity let's use cm versions only last numbers (cm-12.1-20151230-NIGHTLY-nicki will be 30 etc.).
I will arrange my short story in points for better understanding, let's begin here:
- I installed CM 23 (it's 12.1 but the number is for nightly like shown higher) and updated to 26, everything was fine
- quick install of Open Gapps, my apps and doing settings stuff, everything fine
- wild update to 30 appeared, i updated it and it was not very effective
- device rebooted, flashed update automatically, optimized apps aaaaand it got stuck on finishing boot. it was fully ok and responding cause a sound played when i plugged it to charging, it was showing touches ( i set it to show em before update), but it was stuck. So i took battery out and it started to boot, after couple of seconds screen brightness turned down as in every normal booting, boot animation slowed and lagged a few times but then continued to bootloop. Here is a list of things i tried:
- rebooting of course
- clearing cache and dalvik in twrp, then it just optimized apps again and got stuck on starting apps
- wiping data, still bootloop
- wiping everything and installing fresh CM 30
Only the last worked but i lost everything i installed etc. I made a backup of data partition but it restored only some apps ( not even gapps) and settings for some reason.
so after installing everything again i lived it for a while, but because it is a nightly a new update was posted! CM 104
- i downloaded it in cm updater as every other update (btw flashing cm 26 and then 30 from .zip gave the same result), installed it, and it worked soo...
- two days later another update appeared(cm 106), i check every update changelog and this one was big.
- happy of last successful update i just updated it but this time it didn't worked so well
everything is the same as updating 26 to 30, and here we are it got stuck on finishing boot, i took battery out, bootloop, clearing cache and dalvik, optimizing apps, got stuck on starting apps, system fully responding to the same things. i turned the phone down and started this thread.
I have a full backup of everything on another sd with cm 30 and installed apps, but because system is responding i think you guys can help me. i don't want to do a clean install every time a not working update appears. I could stay on last working version, but i'm a type of a person who wants everything updated even if won't give me anything new so staying on last working version from backup is only accepted if you guys won't have any solution or at least idea.
Big thanks for everyone that will bring anything here and probably save some time another happy cm user
EDIT: also, i can restore that backup i have and install version 104, and then figure out how to install it properly

my own idea
so, now i have restored my backup and when i have some free time i'll try to install fresh cm without gapps and update it a few versions, if it'll work problem solved. i will have to just clear cache and dalvik after every update and flash gapps. I only want to ask, if it will work, will flashing gapps with the old ones installed make any issues?

Try to re install rom after full wipe

rohitnegi44 said:
Try to re install rom after full wipe
Click to expand...
Click to collapse
i specially wrote this thread with extra simplicity, but you didn't read that it's working after full wipe, i'm trying to install update AND save my data. read before you post and try to get some easy thank points or whatever this forum has somewhere else.

FIXED IT!!
So for everyone who's looking for answer to this problem here's the fix: after cm flashes and turns off, hold VOL+ button to go to recovery instantly then wipe cache and dalvik, flash gapps, again wipe cache and dalvik reboot. For me it worked.

Sensor issues after installing and wiping "o" beta.

So I installed the beta and decided to go back to 7.1.2.
I did a normal wipe in TWRP then reinstalled SAOSP.
The first problem I noticed was that the phone was slow to turn the screen on after pressing the power button or the fingerprint scanner.
The second problem was that the proximity sensor wasn't working in phone calls. I then checked a few others sensors and noticed that the rotation also want working.
I downloaded a sensor checking app and it showed that the proximity sensor had a value of 5 but it didn't change when covering the sensor.
First thought was a bad flash, so I re-wiped and installed a Nand backup that I knew was good. Same thing happened, so I tried PN. That didn't work.
Downloaded stock zip, backed up personal data, then did a complete wipe with the zip, internal data included. The problems stayed even on stock.
I have since read through whatever threads I could. This seems to be a random issue people have had in the past. Yet is particularly prevalent after the o beta.
Most people have suggested to just re-flash stock but that hasn't worked. The only suggestion I have read otherwise is to also lock and then unlock the bootloader in the process as well.
Who else has this problem and has anyone found a fix yet?

Ok, someone posted in another thread (PN) that the locking and unlocking the bootloader worked for them.
If you have the issue try it out.
Just remember to copy all your internal data to your PC or other storage to save it.

https://forum.xda-developers.com/showpost.php?p=72397601&postcount=10078
Link to solution

To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2

neth15 said:
To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2
Click to expand...
Click to collapse
I tried it this way but after flashing back to 7.1.2 stock, I now get a crash of com.android.phone immediately after booting, followed by a reboot.
Tried clearing cache but didn't help. Anyone know what to try to fix the crash?
UPDATE: Wiped data and now it's fine.

Stuck at "phone is starting", touchscreen not responding.

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.

Realme x2 can't setup fingerprint after rooting on ColorOS

I got my phone just a few days ago, and tried to root it on ColorOS. After all I can't use my fingerprint scanner anymore.
I tried:
-wiping all data
-different ROMs
-unrooting
Nothing worked, I'm curios if anyone got the same problem, and somehow got it working

It was the same with me. With the latest Bootlegger Rom, Fingerprint works for me.
https://sourceforge.net/projects/bi...ble-Unshishufied-20200519-131630.zip/download
If you want to install it, follow the Bootlegger instructions (https://del.dog/X2Flashing.txt). Do not delete the "Vendor" image with Twrp.
The bootlegger links can all be found in the Realme X2 Update Telegram channel
I formatted the data partition with Twrp because it is encrypted with the password. Simple deleting does not help.
I also deleted the internal memory before flashing.
Good luck

ger13 said:
It was the same with me. With the latest Bootlegger Rom, Fingerprint works for me.
Click to expand...
Click to collapse
Which version of Realme x2 do you have?
Mine is RMX1993
And is it working with root?

Just tried...
Only thing that has changed was scanner started to flash on touch, still don't work tho.

I have the xmr1993 EU.
Root works. I have installed Magisk 20.3.
Did you also format the data partition, erase the system and internal memory before installing the custom rom?
Did you hold your finger on the scanner long enough until you were asked to lift your finger?

ger13 said:
Did you also format the data partition, erase the system and internal memory before installing the custom rom?
Did you hold your finger on the scanner long enough until you were asked to lift your finger?
Click to expand...
Click to collapse
I tried two times. I wiped everything, instaled stock A18 and then formated data, wiped everything (not vendor) and flash Bootleger ROM. First time nothing changed, settings stoped working every time I tried to setup fingerprint. Second try it just flashed on touch even when I was in home screen, but still couldn't set it up

Too bad it doesn't work for you yet.
I had installed the A16 when I bought it, later I installed the A18. When I installed Bootlegger with A18 the fingerprint setup did not work either. Unfortunately I locked the bootloader again and it did not boot anymore.
When I got it back from the service center, version C1 was installed. Then I deleted everything except Vendor and formatted the data. Bootlegger installed, fingerprint setup and then Magisk 20.3 installed.
Works fine. Only when the lock screen was on for a few hours I have problems with the fingerprint to log in. Then it works only after a few tries or I have to log in with the password. Otherwise no problems with the fingerprint.
The fingerprint setup took about 5 minutes. You have to press and lift your finger often

ger13 said:
When I got it back from the service center, version C1 was installed. Then I deleted everything except Vendor and formatted the data. Bootlegger installed, fingerprint setup and then Magisk 20.3 installed.
Click to expand...
Click to collapse
Have you checked after you got it if fingerprint was working? Maybe they fixed it.

Yes, as said in the Stockrom, the fingerprint always worked, with the A16, A18 and the C1.
Only when I first installed Bootlegger after the A18 Stockimage the fingerprint setup did not work. I could not setup it.
Now with the new bootlegger it works. Don't know how and why, but maybe it has something to do with the fact that the C1 was installed before. Maybe if the service center had flashed the old A18 I would still have the same problems.
You could try installing Magisk 20.1 again instead of 20.3. On the A18 Rom only Magisk 20.1 worked for me. When installing 20.3 I had a boot loop. Maybe it helps.

ger13 said:
Yes, as said in the Stockrom, the fingerprint always worked, with the A16, A18 and the C1.
Only when I first installed Bootlegger after the A18 Stockimage the fingerprint setup did not work. I could not setup it.
Now with the new bootlegger it works. Don't know how and why, but maybe it has something to do with the fact that the C1 was installed before. Maybe if the service center had flashed the old A18 I would still have the same problems.
Click to expand...
Click to collapse
So for you this works on stock ROMs, for me even on them it doesn't. I checked a few and nothing changed. I thought about relocking bootloader but I didn't want to brick my phone.
Custom ROMs that I've checked are Havoc and Bootlegger. Nothing helped

ger13 said:
You could try installing Magisk 20.1 again instead of 20.3. On the A18 Rom only Magisk 20.1 worked for me. When installing 20.3 I had a boot loop. Maybe it helps.
Click to expand...
Click to collapse
I'm not even trying to install magisk now. I only want to make scanner working

If the fingerprint scanner does not work on stockroms either, I would exchange or return the smartphone. Suggests that it is due to the hardware or it's because you were trying to root the Stockrom. I didn't do that until I installed a custom rom.

OnePlus 5t - Android 10 - com.android.phone has stopped

Ever since updating to A10 on my OnePlus 5t, I can no longer access the "SIM & network" menu within "Wi-Fi & internet". Each time I do, it loads a white page briefly with com.android.phone.oneplusOPMSimActivity as text across the top before kicking back to the previous page. If I try more than once, then the popup for "com.android.phone keeps stopping" comes up with the options for "App info" or "Close app". Each time I try to open this menu, the cell network drops and then reconnects. All of the other options in the "Wi-Fi & internet" menu work as expected.
Yesterday is when I started this whole process. I initially had my phone on the OOS version from late December 2019 (I don't recall the exact version number) with TWRP 3.3.1-0 for recovery and Magisk 20.4. I went into recovery, flashed the A10 OTA full zip, flashed the TWRP 3.3.1-x blu_spark v9.110 recovery, flashed Magisk 20.4, then booted like normal but had no cell connectivity at all (no baseband, IMEI was unknown, etc). After a lot of troubleshooting and reflashing several times, it turns out the one Magisk module that I had installed was not compatible as once I removed it and rebooted, the cell connectivity worked fine.
Fast forward to today and I noticed that I could not access the "SIM & network" menu. I have tried reflashing everything again; removing Magisk and leaving TWRP; going back to full stock without root; booting into safe mode; flashing back to TWRP, wiping Dalvik / ART cache, Cache, and System, then flashing OTA, Magisk, and blu_spark kernel 199; booting into TWRP and wiping Dalvik / ART Cache, Cache, and System, then flashing the OTA without TRWP or Magisk; etc. I could not access the "SIM & network" menu without the app crash at any point, even in safe mode on the factory ROM without root or custom recovery. I also tried clearing the cache and data for com.android.phone, SIM Toolkit, and Phone without any change.
I have not yet tried to take my device completely back to factory state yet (wipe all partitions and start from scratch) as that will take an eternity to restore from. If I have to I will, but I will try every option available to me before I do.
I did a logcat through adb and reproduced the problem. I'm not an Android dev so the logs are of questionable use to me but may point me to something to look at.
Any thoughts on what I should do? Is this something having to do with the previous recovery or root? Is this something caused by existing files on my phone? Is this something broken in the factory OTA and I need to contact OnePlus? The phone is functional otherwise, but man it is annoying not being able to access this menu.

Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).
---------- Post added at 07:32 AM ---------- Previous post was at 07:31 AM ----------
Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).

I had the same problem, dirty flashing the ETA from this xda post has fixed the issue for me for now: https://www.xda-developers.com/oneplus-5-5t-stable-android-10-oxygenos-10-update/

So, I hadn't messed with this for a while and just put it on the back burner. That was until I realized that I could not make calls as I would just get a bunch of chirping, garbled, chipmunk like sound which made the call useless. It worked fine if I answered a call, but not if I made one. I figured it was related to this issue so I went through the process of trying to get things working again. I tried just flashing the A10 OTA again with the blu_spark TWRP and Magisk 20.4, but that didn't fix it. I then proceeded to try and do a full backup of my phone as I was going to try the full wipe and start over fresh, but trying to backup everything is a joke through the USB2.0 connection on this phone let alone trying to get everything just in case I wanted to roll back to how the phone was working prior to the wipe.
At some point I gave up on the backup stuff and just got my user data. Then I got the idea to try going back to the previous working version of Android Pie. I don't recall what my thought process was, but it didn't end up working. For whatever reason, the 53 update was doing the same thing the 54 update did where it would boot up and immediately power off once the lock screen came up. It worked fine before with update 53, but now it wasn't so I flashed back to A10. Now, suddenly, I've noticed that I can access the "Network & SIM" section of the menu without that error from before. I don't know when or what fixed that issue, but it works every time now. Mind you, I did wipe the Dalvik/ART cache, cache, system, and vendor partitions at various points in my attempt to get things working, some of them more than once. I also played around with what partitions were mounted within TWRP though I really did not know what I was doing.
The chipmunk, chirping, garbled thing is still there, but it sounds like many people have had that issue with A10 on other phones. So luckily enough, just turning on and off speaker phone fixes the issue immediately (but I believe for just that call). That is an easy enough work around for me. As much as I want to leave my phone alone, I still have an issue where the phone always boots into recovery first and I have to select reboot > system through TWRP for the phone to boot up normally. I tried reflashing things multiple times, wiping the various partitions, and even some commands from a Nokia forum, but nothing worked. I imagine this is because I messed with the mounted partitions within TWRP and did a flash, but I am not sure on that. I think it could be that the system is booting into recovery because it thinks that is the "normal" partition with the whole A/B partition system, but again, I am not sure on that. I may post again if I end up figuring that all out.